Safaltek - Software Development Methodology

Our Methodology

Safaltek adopts a standardized methodology for defining, designing and developing software projects - called SEPITS.

S	-	Safaltek project acquisition (Requirements & Analysis)
E	-	Estimation
P	-	Planning and Processing
I	-	Implementation
T	-	Testing
S	-	Sign-Off

SEPITS - life cycle development model

SEPITS Strengths

	Dramatic time savings on the systems development efforts.
	Project plan document.
	Strong user stake and ownership of system.
	Can save time, money and human effort.
	Tighter fit between user requirements and system specifications.
	Works especially well, where speed of development is important.
	Ability to rapidly change system design as demanded by users.
	System optimized for users involved in SEPITS process.
	Concentrates on essential system elements from user viewpoint.

Key Phases of SEPITS

Requirements Analysis & Specifications

Establishes a high-level view of the intended project and determines its goals. Study the existing system and prepare a System Specifications document containing the following:

	Functional requirements
	User interface and data requirements
	Security aspects
	Acceptance criteria

Estimation

Effort Estimation In Terms of:

	Cost estimation
	Time estimation

Planning & Processing

Study the existing system and prepare a Design document containing the following:

	Architectural Design (using either Object Oriented Design or Structured System Design.)
	Project Plan Document
	Data Design (using either Entity-Relationship modeling or Object Oriented Database modeling.)
	Primitive Program Specifications (using either English syntax, pseudo-code, tree based structure or a combination.)
	Program Sequencing (or control flow), validations, error handling, etc.

Implementation

The real code is written here.

Integration & System Testing

Brings all the pieces together into a special testing environment, and then checks for errors, bugs and interoperability.

Delivery & Maintenance

The final stage of initial development, where the software is put into production and runs actual business. What happens during the rest of the software's life: changes, correction, additions, moving to a different computing platform and much more.