q1:New System development requires first to understand the system AS-IS, identif
ID: 3800703 • Letter: Q
Question
q1:New System development requires first to understand the system AS-IS, identify improvements, and propose the system TO-BE. This new system can be simple change or complex. It is classified by three techniques: BPA, BPI, and BPR
Explain the three abbreviations above, and talk about the development effort required by each. Support your answer by examples.
q2:
Case Study: Suppose you are a project manager using the Waterfall development methodology on a large and complex project. Your manager has just read the latest article in Computerworld that advocates replacing the Waterfall methodology with Prototyping and comes to your office requesting you to switch. What do you say?
Discuss what is the difference between the two methodologies, and what are the advantages and disadvantages (or limitation) of each?
Explanation / Answer
Q2.Answer:
Waterfall Model is not suitable for large and complex project.It is suitable for small project. Project Manager advice to replace Waterfall development methodology with prototype Model was best because for large and complex project prototype Model is best suited.
Waterfall Model:1.It is the first process model to be introduced.
2.It is also called as linear sequential life cycle model.3 In this model,each phase must be completed before the next phase can begin and there is no overlapping in the phases.
Different phases of Waterfall Model are:1.Requirement Analysis .2.System Design 3.Implementation.4.Testing.5.Deployment 6.Maintenance.Advantages of Waterfall Model :1.This model is simple and easy to understand and use.2.In this model phases are processed and completed one at a time. 3.It works well for smaller projects where requirement are very well understood. Disadvantage of Waterfall Model :It is not a good model for complex and object oriented projects. It is also not suitable for the projects where requirement are at a moderate to high risk of changing.once an application is in testing stage it is difficult to go back and change something that was not documented in requirements phase.very less customer interactions is involved during the development of product. Once the product is ready then only it is given to end users for use. Once the product is developed and if any failure occurs then the cost of fixing such issues are very high because we need to update everything from documentation to implementation.Where to use Waterfall Model:This model is used only when the requirements are very well known, clear and fixed. Project is small.About Prototype Model:The basic idea of this model is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is built based on the currently known requirement. By using this model, client can get an actual feel of the system, since the interaction with prototype can enable client to better understand the requirements. Prototyping is an attractive idea for complicated and large systems. The prototype are not complete systems and many of the details are not built in the prototype.
Phases are 1.Requirement Gathering 2.Quick Design 3.Building Prototype 4.Customer Evaluation 5.Refining Prototype 6.Engineer Product.
Advantages of Prototype Model1.Users are actively involved in the development .2.Since in this methodology a working model of the system is provided, users get a better understanding of the system being developed. 3.Missing functionality can be identified easily. 4.Quicker user feedback is available leading to better solution .Disadvantag of Prototype Model :If the user is not satisfied by the developed prototype then a new prototype is developed. This process goes on until a perfect prototype is developed. This model is time consuming and expensive. The developer loses focus of the real purpose of Prototype and hence may compromise with quality of the software Where to use prototype Model :Prototype model should be used when the desired system needs to have a lot of interaction with end users.2.Typically,online systems Web interfaces have a very high amount of interaction with end users are best suited for prototype Model. prototyping ensures that the end users constantly work with the system and provide a feedback which is incorporated in the prototype to result in a usable system.
Difference between Waterfall and Prototype Model :
In Waterfall Model, client can only preview the system only after the final version of the software ideveloped because there is no feedback loop where as in prototype Model client can have a preview of the system from the quick design and the prototype developed early at time of process.
In Waterfall Model, developers encounter a freezing requirement where they are not allow to modify the requirements or specification of the previous phase until the next iteration whereas in prototype model developers can refine or add requirements and specifications to the system after the prototype is built.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.