Introduction to Software engineering

[joseph755]

(1) propose the most appropriate generic software process model that might be use as a basis for the development of following systems give reasons for your answer

 A waterfall model is an appropriate approach to use perhaps with formal transformation between different development stages.

(A) A complex real-time system whose requirements can be relatively easily identify and are stable

  It has an eliciting, collection and developing stages for it to be stable for the system.

(B)A website for a local library requirements are vague and are likely to change in the future

      The risk associated with the cost, schedule, security and other important factors are low. This makes significant changes in requirements during the project highly unlikely. It is produced to inform the customer during requirements collection, especially before finals approval. The requirements changes in project using waterfall model can be costly.

(C)An order processing system with a website for a local business. Requirements are vague but stable unlikely to change in the nearest future

The initial phase is often the requirements task. The milestone occurs when the user and stakeholders have documented, validated and approved a complete set of functional performance. Phase that are follow here are design, implementation, testing, integration, operation and maintenance. Each phase is formally documented, validated and approved .This will make it unlikely to change in the nearest future.

(2) Describe the software process model that you have proposed in question 1(a) highlighting it strength and weaknesses

    A waterfall model is a relatively low risk model and progress through series of phases and milestones in the linear fashion over time. In this model,the initial phase is often the requirements task, design, testing, implementation,intergration, operation and maintenance. Each stages is formally documented, validated and approved. This type of model is feasible when the customer mission is fairly static. The risk, schedule cost, security and other important factors are at low cost.

This model has the following strength
The model is simple to use and easy to understand. It is easy to manage due to the rigidity of the model.
This model work well for smaller project where requirements are clearly defined and very well understood.

It weaknesses are

  -No working software can be produced until late during the life cycle.
  - There's the high amount of risk especially over the requirements task.

_ This model is not suitable for the the project where requirements are at a moderate to high risk of changing.