|
 |
- Identifying
Commitments made to Client
- Is done on the basis of Specifications in Contract.
- Quality
assurance plan
- Is detailed before each Phase in the Project's Life Cycle.
- Examination
of Existing System
- Study of Existing Documentation and Discussions with Client.
- Preparation
of Plans for honoring Commitments
- Preparing the Documentation what we can do.
- Review
of Plans
- Checking the documentation thoroughly and is done by Analysts
- Filling
Requirement Checklist
- Done by Analysts with Client's Representative
- Preparation
of Software Requirements Document
- Complete User Requirements and Analysis. Details of Included
Software.
- Preparation
of System Test Plan and Acceptance Test Plan
- Lists activities to test Developed Software vs. Requirement
done by Analysts.
- Software
Design
- Follows a "How To" approach. Uses Software Requirements
Document as input Software Construction
- Using the specified software the target is developed by the
programmers under the guidance of Project leaders and managers.
- Software
Testing
- Subjects Software to - Code Walkthrough; Unit Testing; Integration
Testing; System Testing; Acceptance Testing.
- Software
Installation
- Installing the software and hardware what they have done under
the guidance of Project leader at the client's office.
- User
Training
- Day-wise / Session-wise Training is given to clients team by
the project leader.
Joint Review
- A review must be taken by the client team to the project leader.
- Future
Services
- In case any future problem or any new implementations is given
to the clients.
|
|