|
Project Startup:
|
|
|
In IntraAction Software, the beginning of a project lays the groundwork for the
project. The purpose of this phase is to set the framework for the project, which
involves:
|
|
|
Selecting a methodology
Identifying goals and objectives
Defining success measures
Establishing project scope
Selecting a project team
Securing sponsorship
|
|
|
Business Prototype & Requirement:
|
|
|
One of the less visible, but nonetheless important aspects of a good software engineering
process is the requirement documentation and verification. The only way to ensure
that a system satisfies its requirements is to develop and apply a mechanism to
track requirement compliance from system inception through final delivery and system
maintenance. The key points in the requirement phase are:
|
|
|
Communicate/Coordinate with the Customer
In-depth clarity on the requirements
Requirements Change Management
|
|
|
|
|
|
Analysis & Design:
|
|
|
The primary output of the design phase is a design document. The design document
is to give all internal constituents (developers and management) a clear delineation
of how the features described in the specification will accomplish the desired tasks.
The design document should clearly convey the key elements of the proposed system
to both the technical developers and the planners. A larger project typically requires
a preliminary design and a detailed design. A complete design includes identification
of:
|
|
|
Modules
Units
Data elements
Communications
Messages
Data structure
|
|
|
|
|
|
Implementation, Testing and Project Completion:
|
|
|
At Intraaction, Implementation phase is the core process workflow where-in the design
document is used to produce code and the Functional and Technical Specifications
documents to produce Unit/Integration/Regression Test Cases. During this phase,
the actual work of the project is undertaken to produce the project's deliverables
according to the chosen solution and make it ready for testing team. The test phase
of the project answers the question "Does the system do what it is supposed to do?"
Software testing begins with the Unit Testing phase where-in the Quality people
unit test the code produced by the developers based on the Unit Test Cases.
|
|
|
After the defects found in the Unit Testing phase are fixed by the developers, another
phase of testing is carried out, the cycle repeated till all the defects found
in testing
are found, fixed and tested.
Then begins the Integration testing phase which integrates the individual units
coded and tested during the implementation phase and ends with acceptance
testing of
the finished system.
All problems and change requests should be handled according to the Software Problem
Procedure documentation.
|
|
|
In the Testing phase,
|
|
|
Test plans and procedures are developed to ensure that all requirements are being
tested and verified.
Units are combined into modules, and modules are combined to make up a build, which
is tested in turn and certified.
Multiple builds may be integrated and tested before a deliverable release is produced.
|
|
|
|
|
|
Maintenance:
|
|
|
Softwares can undergo changes once delivered to the customer because of the changing requirements or some unexpected input values into the system. These changes could directly affect the software operations. At
Intraaction, applications are developed such that they can accommodate changes that could happen during the post implementation period. Upon request by the customer, Maintenance support is provided to the softwares developed.
|
