What do the shaded, colored areas represent? Why does implementation extend acro
ID: 3736523 • Letter: W
Question
What do the shaded, colored areas represent?
Why does implementation extend across all project phases? How is this different
from Classical systems development methodologies?
Why don’t we see the word Maintenance on this illustration?
Phases Inception Elaboration Construction Transition Production Project Management Business Requirements Requirements Analysis Mapping and Configuration Analysis Design Implementation Testing Performance Management Technical Architecture Data Acquisition and Conversion Documentation Organizational Change Management Training Transition Operations and Support Iterations Milestones Elab LO LA Oc sP so 8. What do the shaded, colored areas represent?Explanation / Answer
Answer)What do the shaded, colored areas represent?
The shaded and colored ares which make a graph in the above image represent the amount of the particular task put in or the effort put in that particular area over time and over different development and progress phases of a project, such as Inception, Elaboration, Construction, Transition, Production. For example, we take the Business Requirements part as an example.
During Inception of the project the business requirements and understanding them play a vital part, so the effort has gone into that and the graph is steeply high. So most of the effort got put in the Business Requirements part at first. That gradually decreases once you understand the business requirement and start working on the project. In Elaboration there is still some good amount of business requirements work done and it depletes from Construction to Transition where there is very few work to be done in that area.
Why does implementation extend across all project phases? How is this different from Classical systems development methodologies?
Classical development methodologies such as a Waterfall model will consider that separate steps such as Requirements Analysis and only after that the System development should begin. This is not the case since, there may be involvement in the Requirements Analysis even on the Development phase and Elaboration phase. Thus, this image approach of implementation of the project considers that every job works in parallel and not after one another. Thus the implementation extends across all project phases as long as the implementation is required for the particular project.
Why don’t we see the word Maintenance on this illustration?
We don’t see the mar Maintenance here but we do see Operations and Support in the Production phase when the project goes and runs into Production environment for the client and fulfill the purpose of the client. This illustration concentrates on the project development more than the maintenance phase of the post project part.
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.