Generic Process Model in Software Engineering
Generic Process Model:
The Generic process model is an abstraction of the software development process. It specifies the stages and order of a process. The generic Process Model will define the following:
i. The tasks to be performed.
ii. The input and output of each task.
iii. The pre and post-conditions for each task.
iv. The flow and sequence of each task.
It is a set of activities, methods, practices, and transformations that people use to develop and maintain software and its associated products. As a Software Organization, the software process becomes better defined and more consistently implemented throughout the organization.
Example: Project plans, Design-Documents, Code, Test cases, and User-manuals
Generic Process Framework Activities:
It establishes the foundation for a complete software process by identifying a small number of framework activities. It also includes a set of umbrella activities that are applicable across the entire software process. Each framework activity is populated by a set of software engineering actions. A Generic Process Framework for Software Engineering encompasses five activities.
1. Communication: This framework activity involves heavy communication and collaboration with the customer. It encompasses requirements gathering and other related activities.
2. Planning: This activity establishes a plan for the software engineering work that follows. It describes the technical tasks which are conducted. The resource requires and the work products are produced with a work schedule.
3. Modeling: It encompasses the creation of models that allow the developer and the customer. It is easy to better understand Software requirements and the design that will achieve those requirements.
4. Construction: This activity combines code generation and the testing that is required to uncover errors in the code.
5. Deployment: The software delivered to the customer who evaluates the delivered product. It also provides feedback based on the evaluation.