Revise plan to create controllable activities Adjust overall plans and estimates to take account of risks Revise plans and estimates to take into account resource constraints Total views 31, On Slideshare 0. From embeds 0. Number of embeds Downloads Shares 0. Comments 0. Likes You just clipped your first slide! Clipping is a handy way to collect important slides you want to go back to later.
Now customize the name of a clipboard to store your clips. Visibility Others can see my Clipboard. Cancel Save. Exclusive 60 day trial to the world's largest digital library. Computer Organization.
Discrete Mathematics. Ethical Hacking. Computer Graphics. Web Technology. Cyber Security. C Programming. Control System. Data Mining. Data Warehouse. Javatpoint Services JavaTpoint offers too many high quality services. Need of Software Project Management Software development is a sort of all new streams in world business, and there's next to no involvement in structure programming items. Software Project Manager Software manager is responsible for planning and scheduling project development.
The system is installed and put into practical use. In principle, the result of each phase is one or more documents which are approved. No phase is complete until the documentation for that phase has been completed and products of that phase have been approved. The following phase should not start until the previous phase has finished. Real projects rarely follow the sequential flow that the model proposes. In general these phases overlap and feed information to each other.
Hence there should be an element of iteration and feedback. A mistake caught any stage should be referred back to the source and all the subsequent stages need to be revisited and corresponding documents should be updated accordingly.
This feedback path is shown in the following diagram. Because of the costs of producing and approving documents, iterations are costly and require significant rework. It therefore generates complete and comprehensive documentation and hence makes the maintenance task much easier. It however suffers from the fact that the client feedback is received when the product is finally delivered and hence any errors in the requirement specification are not discovered until the product is sent to the client after completion.
This therefore has major time and cost related consequences. Rapid Prototyping Model The Rapid Prototyping Model is used to overcome issues related to understanding and capturing of user requirements.
Once the user requirements are captured in the prototype to the satisfaction of the user, a proper requirement specification document is developed and the product is developed from scratch. The developer should endeavour to construct the prototype as quickly as possible to speedup the software development process.
For this reason, the internal structure of the rapid prototype is not relevant. One solution to this is to combine rapid prototyping with the waterfall model. In this approach, rapid prototyping can be used as a requirement gathering technique which would then be followed by the activities performed in the waterfall model.
Incremental Models As discussed above, the major drawbacks of the waterfall model are due to the fact that the entire product is developed and delivered to the client in one package.
This results in delayed feedback Because of the long elapsed time, a huge 15 new investment of time and money may be required to fix any errors of omission or commission or to accommodate any new requirements cropping up during this period. This may render the product as unusable. Incremental model may be used to overcome these issues. In the incremental models, as opposed to the waterfall model, the product is partitioned into smaller pieces which are then built and delivered to the client in increments at regular intervals.
Since each piece is much smaller than the whole, it can be built and sent to the client quickly. This results in quick feedback from the client and any requirement related errors or changes can be incorporated at a much lesser cost.
It is therefore less traumatic as compared to the waterfall model. It also new investment of time and money may be required to fix any errors of omission or commission or to accommodate any new requirements cropping up during this period. It also required smaller capital outlay and yield a rapid return on investment.
However, this model needs and open architecture to allow integration of subsequent builds to yield the bigger product. A number of variations are used in object-oriented life cycle models. In the first case, the requirements, specifications, and architectural design for the whole product are completed before implementation of the various builds commences. When this has been completed, the specification team turns to the specification of the second build while the design team designs the first build.
Thus the various builds are constructed in parallel, with each team making use of the information gained in the all the previous builds.
This approach incurs the risk that the resulting build will not fit together and hence requires careful monitoring. It is a high speed adaptation of the linear sequential model in which fully functional system in a very short time 2- This model is only applicable in the projects where requirements are well understood and project scope is constrained.
Because of this reason it is used primarily for information systems. Synchronize and Stabilize Model This is yet another form of incremental model adopted by Microsoft. In this model, during the requirements analysis interviews of potential customers are conducted and requirements document is developed. Once these requirements have been captured, specifications are drawn up.
The project is then divided into 3 or 4 builds. Each build is carried out by small teams working in parallel. At the end of each day the code is synchronized test and debug and at the end of the build it is stabilized by freezing the build and removing any remaining defects. Because of the synchronizations, components always work together. The presence of an executable provides early insights into operation of product. Spiral Model This model was developed by Barry Boehm.
The main idea of this model is to avert risk as there is always an element of risk in development of software. For example, key personnel may resign at a critical juncture, the manufacturer of the software development may go bankrupt, etc.
In its simplified form, the Spiral Model is Waterfall model plus risk analysis. In this case each stage is preceded by identification of alternatives and risk analysis and is then followed by evaluation and planning for the next phase. If risks cannot be resolved, project is immediately terminated. This is depicted in the following diagram. Radial dimension represents the cumulative cost to date and the angular dimension represents the progress through the spiral.
Each phase begins by determining objectives of that phase and at each phase a new process model may be followed. A full version of the Spiral Model is shown below : Because of the spiral nature of development it is easy to judge how much to test and there is no distinction between development and maintenance.
It however can only be used for large-scale software development and that too for internal in-house software only. There are a number of these models. All of these models incorporate some form of iteration, parallelism, and incremental development. Extreme Programming It is a somewhat controversial new approach. Create a free Team What is Teams? Learn more. Who developed Stepwise project planning? Ask Question.
Asked 4 years, 4 months ago. Active 4 years, 4 months ago. Viewed times. Improve this question.
0コメント