Chapter 19, Problem 3CCO

Program Plan Intro

Software development methodologies:

• The different software methodologies include:
  • Agile methodology:
    • Agile methodology aims for satisfaction of customers through continuous delivery of software components.
    • It is an iterative process that uses minimum requirements.
    • It has individual as well as team interactions over tools and processes.
    • It responds to change over following a plan.
    • Collaboration of customer over negotiation of contract.
  • Waterfall methodology:
    • Each phase is performed sequentially.
    • It is an activity based process.
    • It is less iterative and non-flexible approach.
    • The phases of conception includes:
      • Analysis
      • Design
      • Construction
      • Testing
      • Deployment
      • Maintenance.
    • Designers may not be aware of difficulties that may arise in future.
  • Rapid action development methodology(RAD):
    • It is based on prototyping as well as iterative development without any planning involved.
    • It involves planning for product development.
    • It gathers requirements of customer through focus groups.
    • The function modules are been developed in parallel as prototypes.
    • The modules are been integrated to make complete product.
  • Extreme programming (XP) methodology:
    • It denotes a method that is been used in case of changing requirements.
    • It checks frequent product releases in short intervals that improve performance.
    • It introduces a checkpoint where customer requirements could be easily implemented.
    • Requirements are been collected in terms of stories.
    • The phases include planning, analysis, design, execution, closure and wrapping.
  • Rational Unified Process (RUP):
    • It denotes a framework for breaking down software development into four gates.
    • The phases include:
      • Inception:
        • Project ide is been stated.
        • Implementation team decides requirements.
      • Elaboration:
        • The architecture of project is evaluated further.
        • Developers would consider possible applications of software and associated costs.
      • Construction:
        • The project is completed and developed.
        • The software is been written and tested.
      • Transition:
        • The software is been released to public.
        • Changes are made based on feedback.
  • SCRUM
    • It makes use of small teams for producing small software modules using sprints or one month interval to achieve goal.
    • Much detail is not given, implementation team knows how to solve problem.
    • The team is having better idea of entire project.
    • There is no team leader for assigning tasks.
    • Each of team members is responsible from idea to implementation.