This Chapter is all about Drawing Practice 🤣

A structured set of activities is required to develop a software system.

• Specification
• Design and Implementation
• Validation
• Evolution

Plan-driven and agile processes

• Plan-driven processes are processes where all the process activities are planned and progress is measured against this plan.
• In agile processes, planning is incremental and it is easier to change the process to reflect changing customer requirements.

Software Process Models

• The Waterfall Model

  Plan-driven model. Separate and distinct phases of specification and development

  

  ⇒ The main drawback of the waterfall model is the difficulty of accommodating change after the process is underway. In principle, a phase has to be completed before moving on to the next phase.

• Incremental Development

  → Reduction of cost in a change of requirement.

  → Easier to get Customer Feedback

  → Rapid Delivery and Deployment

  

  ⇒ The main drawback is that the process is not visible and the system structure tends to degrade as new increments are added.

• Integration and Configuration

  ⇒ Low Cost, Fast Delivery

  

  ⇒ The drawback is may not meet the real needs of users, a loss of control over the evolution of reused system elements.

Types of Reusable Software

• Stand-alone application systems that are configured for use in a particular environment
• Collection of objects that are developed as a package to be integrated with a component framework such as .NET or J2EE
• Web Services that are developed according to service standards and which are available for remote invocation.

The Requirements Engineering Process

A General Model of The Design Process