|
OBJECTIVE
The objective of this document is to provide an overview of the development methodology that is followed by Jhelum Technologies. This methodology is selectively customized for each client based on the client’s requirements and expectations. This document details each phase of the Software development lifecycle and the associated deliverables and metrics.
DEVELOPMENT METHODOLOGY
The following are the various phases of the development cycle. For each of these phases the corresponding deliverables, tools and applicable metrics are provided. Status reports at predefined intervals are provided for the complete lifecycle.
REQUIREMENTS DEFINITION PHASE
This phase involves Requirements gathering, analysis, clarifications, review, specification and signoff.
The approach that will be followed to gather requirements is defined initially. Functional and non-functional requirements are gathered. The collected information is collated and reviews are conducted on the same. The outcome of the reviews will be a Requirements document that captures the scope of the solution and identifies aspects, which do not form a part of the scope. Upon final review a signoff is obtained. Acceptance criteria is defined and documented
Any additional requirements that need to be implemented will only be accepted through the change management process.
Tools like Rational Rose could be used for Requirements management.
The deliverable from this phase are
- Signed Requirement Document
- Resource plan
- Communication plan, which includes predefined escalation criteria
- Acceptance plan
|
ANALYSIS PHASE
This phase involves analysis of business requirements and mapping of the same to system requirements. It also involves the following
- Establishment of technology architecture for the solution
- Identification and assessment of risks
- Risk mitigation and contingency plans.
- Establishment of configuration management plan
- Estimating the effort involved in delivering the solution
- Tools identification for development and testing
- High-level design document.
- Establishment of test strategy
- Project plan and project organization chart
- Roles & responsibilities
- Logical database design
- Defect tracking plan.
|
Corresponding documents will be delivered at the end of this phase. A review of these documents is conducted with the client and signoff is obtained on the design. The tools that can be used during this phase are Rational Rose, Erwin, CVS or PVCS for Configuration management an MS-Project.
DESIGN PHASE
During this phase the high level designs, which were defined in the Analysis phase, are exploded and units of work identified and allocated. The previously identified risks are reviewed. If new risks are identified then corresponding assessment is done and the mitigation and contingency plans are updated. The required development environment is established. The first version of user manual is prepared. This is a live document that will continue to be updated during the development and implementation phase.
The deliverables of this phase will be
- Low-level design
- Program specifications
- Physical database design
- Test plans – Unit, Module, System, Integration
- Test Scripts
- User interface designs
- Detailed project plan
- Updated Risk mitigation and Contingency plan
|
Tools that can be used in this phase are Rational Rose, Erwin, MS-Project. Automation tools for testing will be evaluated in this phase. Metrics, which provide time and slippage information will be established.
DEVELOPMENT PHASE
During this phase the solution is developed and tested.
Various tools like Visual age for Java, Rational’s suite of code generators and testing tools, Testing tools like Astra Quicktest, Winrunner, Silktest, etc, are used. Bug tracking is done using tools like Bugzilla, PP-Tracker, etc.
The deliverables of this phase are
- Tested solution including documented source code and executable
- Test results
- Test coverage analysis reports
- Updated Issues list
- Verified and updated final bug report
- Document detailing known defects
|
IMPLEMENTATION PHASE
This phase includes acceptance testing of the delivered solution by the client. Issues that arise during this phase are resolves and the solution is implemented at the client’s production location.
Deliverables for this phase are
- User manual
- System manual
|
POST IMPLEMENTATION PHASE
During this phase training is provided and onsite support is provided.
|
