VU Process Model
For making our software we adopted VU Process Model which is a combination of waterfall and spiral models. The idea behind this model is that to get the benefits of both these models. Essentially, Water Fall Model is a framework for software development in which development proceeds sequentially through a series of phases, starting with system requirements analysis and leading up to product release and maintenance, whereas the key characteristics of spiral model is risk management at regular stages in the entire software development cycle.In VU Process Model we will be working in phases to complete our given project. Some of the phases are described below:
Requirement Analysis & Definition:
All possible requirements of the system to be developed are captured in this phase. We will define the functional, non functional requirements in this phase. These requirements are analyzed for their validity and the possibility of incorporating the requirements in the system to be development is also studied. Finally, a Requirement Specification document is created which serves the purpose of guideline for the next phase of the model, in which we define the use cases for our system and their scenarios here too.
Risk analysis & Work Plan:
In this phase we will be defining time line in which this project should be completed, the cost which will be allocated for our project and all the basic planning activities will be done in this phase. All possible risks associated with the project are identified and analyzed here. The aim is that all risks are resolved.
System Design
In this phase we will understand what we are going to create and what it should look like? The requirement specifications from first phase will be studied in this phase and system design will be prepared. System Design helps in specifying hardware and system requirements and also helps in defining overall system architecture. We will be defining all the aspects of design of system. We will work on the architecture of the system, the internal and external entities, their relations among each other and to the others, etc. After completing the basic design phase we will build our system here.
Implementation
This step consists of actually constructing the product as per the design specification(s) developed in the previous step. Typically, this step is performed by a development team consisting of programmers, interface designers and other specialists, using tools such as compilers, debuggers, interpreters and media editors. The output of this step is one or more product components, built according to a pre-defined coding standard and debugged, tested and integrated to satisfy the system architecture requirements.
Verification/Testing
In this phase we will verify and test our system. We will perform different type of testing here and if got some problem, we will solve that out. There are mostly three steps of testing….
i) unit testing
ii) system testing
iii) acceptance testing
This is also the stage at which product documentation, such as a user manual, is prepared, reviewed and published.
