| (A) Project Management Process:
A brief outline of our Project Management is described here. Typically there are five stages.
a: Project Initiation : Here project objective and scope are defined. Identification of requirements is carried out
b: Project Planning: Project efforts estimation
Risk mitigation Strategy
Quality assurance plan
Test plan
c. Project Execution:
In this step, we will monitor the project and track progress of the project.
The progress report of the project is regularly sent to client.
d: Project Control :
We have project board meetings, scheduled quality reviews and progress control procedures. One important aspect is
Change control. All Change requests either from our domain team or from the client is tracked and
its implementation status is updated. Details of every client meeting and follow-up are recorded.
Normally client discussions are held through messenger board, emails or voice calls on IP.
e: Project Closure:
Final Project evaluation is done by the quality experts, to ensure that the project has been completed and necessary documentation is prepared.
(B) Software Development Process:
At Netwin we follow a process oriented development methodology designed to minimize project risks and development time. With our spiral methodology approach each and every stage of the project is reviewed thoroughly. We have defined processes for requirements 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.
a. Requirement Gathering
In requirement gathering phase, Netwin's business consultants interact with the clients to understand the user requirements.
We study the information provided by the client in the form of documents, existing systems & process specs, on-site analysis interviews with end-users and market research. Also our domain experts and technical experts are involved to freeze the design and platform requirements. The initial scope of the project is defined in terms of cost, effort, schedule and deliverables.
b. Requirement Analysis
In this stage, a detailed analysis is carried out from the information gathered in project scope document and feature list. The following steps are executed in this stage.
Analysis and generation of detailed Software Requirement Specification (SRS) document
Creation of Use Case Specification & Diagram and generating the Use Case Model
Forming business rules and create information flow diagrams
Validation of the Scope is done.
c. Design
This is very important stage in software development life cycle. The software application is designed from the SRS document, use case specification, business rules & flow diagrams and the project scope defined.
We have adopted 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 Diagram
User Interface - The prototype is developed and validated against the requirements 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
The Test Model is generated from use cases
d. Development and Testing
Actual coding based on the design document is done and tested against the test cases. We follow V-model for software design, development and testing.
|