|
|
|
|
| |
|
|
|
| |
|
|
|
|
|
| |
|
 |
|
|
|
| |
| Our Methodologies |
|
|
|
|
| Development Process |
| |
At EPB Consulting we follow a process
oriented development methodology designed to minimize project
risks and development time. We focus on business solutions that
fulfill business goals, instead of merely providing technical
solutions. All our applications are built on the basis of this
philosophy.
The approach that we adopt is the spiral iterative methodology,
where the project goes through one or more iterations of all
project stages. The above presentation gives a brief overview of
the process.
We have defined processes for requirement capture, analysis,
design, development, testing and deployment. We generate UML
diagrams representing the Use Case Model, Analysis Model, Design
Model, Implementation Model and Test Model. |
| |
| |
| Requirement Definition |
| |
In this stage, the requirements of the clients
are gathered. This is done on the basis of information provided
by the client in the form of documents, existing systems &
process specs, on-site analysis interviews with end-users,
market research and competitor analysis. This stage has the
following steps:
The Test Model is generated from use cases
1) Requirements analysis with business application goal and high
level requirement gathering
2) Creation of visual scope document and feature list
3) Providing technical recommendations and high level
requirement specification |
|
|
| Analysis |
| |
In this stage, a detailed analysis is carried
out from the information in the vision & scope document and
feature list. This stage has the following steps:
1) Analysis and creation of Software Requirement Specification
2) Creation of Use Case Specification & Diagram and generating
the Use Case Model
3) Design business rules and flow diagrams
4) Establishment of Requirement Traceability Matrix
5) Validation of the Scope and Estimates against the contract
and revisions made if necessary |
| |
| |
| Design |
| |
In this stage, the application design is
developed on the basis of the Software Requirement
Specification, Use Case Specification, Business Rules & Diagrams
and the scope agreed upon in the Requirement Definition stage.
This stage has the following steps:
• Designing Architectural Diagrams
• Creation of High Level Design and Low Level Design class
diagrams
• Establishment of Entity Relationship Diagram, Data Flow
Diagram and Deployment Diagrams
• User Interface -The prototype is developed and validated
against the requirement and presented to the client for approval
• The use cases elaborated in the analysis model are represented
using collaboration diagrams
• Design model elaborations are made from the analysis model.
Validation of the scope, estimates against the contract and
revisions are made if necessary
• The Implementation Model is generated from design |
| |
| |
| Development |
| |
In this stage, the actual code based on the
design is created and tested against design requirements and
test cases. This stage has the following steps:
1) The development of code base proceeds as per implementation
and design models
2) The application source code is tested according to the test
cases and test plan
3) Documentation of processes
4) Creation of Use Case Test results |
| |
| |
|
|
|
Integration and Testing |
|
| |
|
|
| |
In this stage, the developed application is tested through test cases,
test plans and user acceptance criteria in the deployed environment.
• Integration and quality testing is carried out resulting in test
reports.
• Client acceptance tests carried out.
• Client feedback and debugging.
• Client acceptance |
|
| |
|
|
| |
|
|
| |
Deployment and Acceptance |
|
| |
|
|
| |
In this stage, the developed application is deployed on the live server.
• Integrated application and deployment plan
• Implementation on client premises or hosting server.
• Implementation signoff by client.
• Creation of archived software artifacts
• Transition of application to the maintenance team.
The steps above are iterated through until the final deliverable is
completed.
We will submit a detailed project schedule in accordance with the above
deliverables. The project schedule will clearly indicate the
responsibility of the client and the developer and indicate the dates by
which each person will submit their deliverables. |
|
|
|
|
| |
|
|
|
|
|
|
