GSPM (General Software Process Model)
Download as DOC, PDF0 likes378 views
The GSPM (General Software Process Model) is a framework that describes the activities performed at each stage of a software development project. It has three modes of working depending on requirements clarity. Mode 1 is used when requirements are unclear, Mode 2 when requirements are known but the product is new to the market, and Mode 3 when requirements are clear and the project is large-scale. The GSPM has seven phases: communication/requirements analysis, planning, modeling, construction/coding, testing/verification, operation & maintenance. It is useful for both beginners and experts on small and large projects but runs linearly without going back and has only one-time planning.
GSPM (General Software Process Model)
- 1. GSPM General Software Process Model Prepared By : Muhammad Naeem
- 2. GSPM (General Software Process Model) A framework that describe the activities performed at each stage of a software development project. This GSPM deal with all kinds of client requirements measure and unmeasured requirements. GSPM have three modes of working on any type of software. First if client and software team don’t know or understand our software/product requirements so using mode1 in this mode analyses take continuous feedback of client then done the requirements on software. Second if client sure about our requirements of software / product and the product target is market business , so the team make a basic version of product and given to client then client get positive response from market then again say to team for next version so using of this mode loss criteria is less. Third in this mode both client and team confirm sure about our requirements, in this mode work only experts and use for large scale projects .so in this mode project head divide the project and make teams and all teams work in parallel. IN this process model seven phases and three modes of working in GSPM. 2
- 3. GSPM Diagram Measure Requireme nts Software Requirements Hardware Requirements Unmeasured Requirement s Planning Process Modes Mode 1 Mode 2 Mode 3 Team 1 Modeli ng Modeli ng Code Code Stabilizing Deployment Team 2 Team 3 3
- 4. GSPM Phases 1. Communication / Requirement / Analysis & Definition: All requirements of the system which has to be developed are collected in this step. Like in other process models requirements are split up in functional requirements and constraints which the system has to fulfill. Requirements have to be collected by analyzing the needs of the end user(s) and checking them for validity and the possibility to implement them. Our aim is to generate a Requirements Specification Document which is used as an input for the next phase of the model. 2. Planning: Software cost estimation is the process of predicting the amount of effort needed to build a software project. The software equation is a multi-variable model that supposes a definite distribution of effort over the duration of a software development project. Outsourcing describes the allocation of software development responsibilities to a third party. The project manager has the responsibility to plan the project according to the project requirement so that project duration and cost of estimation can be calculated. 3. Modeling: 4
- 5. Modeling is a kind of technical design done by project designer in which two steps involves. 3.1 System / Architecture Modeling: The system has to be properly designed before any implementation is started. This involves an architectural design which defines and describes the main blocks and components of the system, their interfaces and interactions. By this the needed hardware is defined and the software is split up in its components. E.g. this involves the definition or selection of a computer platform, an operating system, other peripheral hardware, etc. The software components have to be defined to meet the end user requirements and to meet the need of possible scalability of the system. The aim of this phase is to generate a System Architecture Document this serves as an input for the software design phase of the development, but also as an input for hardware design or selection activities. Usually in this phase various documents are generated, one for each discipline, so that the software usually will receive a software architecture document. 3.2 Software Modeling: Based on the system architecture which defines the main software blocks the software design will break them further down into code modules. The interfaces and interactions of the modules are described, as well as their functional contents. All necessary system states like startup, shutdown, error conditions and diagnostic modes have to be considered and the activity and behavior of the software has to be defined. The output of this phase is a Software Design Document which is the base of the following implementation work. 4. Construction / Coding: Based on the software design document the work is aiming to set up the defined modules or units and actual coding is started. The system is first developed in smaller portions called units. They are able to stand alone from a functional aspect and are integrated later on to form the complete software package. 5. Software Test/Verification (Integration): Each unit is developed independently and can be tested for its functionality. This is the so called Unit Testing. It simply verifies if the modules or units to check if they meet their specifications. This involves functional tests at the interfaces of the modules, but 5
- 6. also more detailed tests which consider the inner structure of the software modules. During integration the units which are developed and tested for their functionalities are brought together. The modules are integrated into a complete system and tested to check if all modules cooperate as expected. 6. Operation & Maintenance: The system is handed over to the customer and will be used the first time by him. Naturally the customer will check if his requirements were implemented as expected but he will also validate if the correct requirements have been set up in the beginning. In case there are changes necessary it has to be fixed to make the system usable or to make it comply with the customer wishes. All the problems which did not arise during the previous phases will be solved in this last phase. 6
- 7. GSPM Uniqueness : Advantages: 1. Useful for both beginners and expert’s teams. 7
- 8. 2. Apply on small and big projects. Disadvantages: 1. GSPM run in a linear way, don’t go back. 2. One time planning. GSPM Example: 8
- 9. GSPM is a general software process model and they apply of almost all kind of market software many software example apply GSPM process model easily like. 1. School management System. 2. Shop inventory System. 3. Software Product (i.e. MS Office). 9
- 10. GSPM is a general software process model and they apply of almost all kind of market software many software example apply GSPM process model easily like. 1. School management System. 2. Shop inventory System. 3. Software Product (i.e. MS Office). 9