1.2.3 Software development

Question 1

Waterfall model?

Answer 1

The Waterfall Model is a linear, sequential software development process divided into distinct phases where each phase must be completed before the next one begins.

Question 2

Steps in the waterfall lifecycle model?

Answer 2

Requirement gathering and analysis

System design

Implementation

Integration and Testing

Deployment

Maintenance

Question 3

1st stage of waterfall lifecycle?

Answer 3

Requirement Gathering and Analysis: All possible system requirements to be developed are captured and documented clearly

Question 4

2nd stage of waterfall lifecycle?

Answer 4

System Design: The requirements are translated into a design.

Architects and designers define the overall architecture and identify the main components

Question 5

3rd stage of waterfall lifecycle?

Answer 5

Implementation: The actual code is written based on the design documents

Turning the system design into a functional program

Question 6

4th stage of waterfall lifecycle?

Answer 6

Integration and testing: All the components and modules are integrated and tested to ensure that the entire system works as expected

Question 7

5th stage of waterfall lifecycle?

Answer 7

Deployment: The product is released to the market or handed over to the client.

It may involve installation, customization, and training

Question 8

6th stage of waterfall lifecycle?

Answer 8

Maintenance: Post-release, the system needs regular maintenance

In order to fix bugs, improve performance, or add new features

Question 9

Benefits of waterfall model?

Answer 9

Simple and linear

Clear stages and milestones- progress is easy to measure

Suitable for well-defined projects

Question 10

Drawbacks of waterfall model?

Answer 10

Inflexible: changes are hard to implement once the project has started

Expensive to fix late problems

Long development cycle

Question 11

What is the waterfall model most suitable for?

Answer 11

Projects where requirements are unlikely to change and clear to understand

When high quality is essential

Question 12

What is the agile extreme programming model?

Answer 12

A type of agile ITERATIVE software method that promotes adaptability and high customer involvement

Question 13

Stages of extreme programming?

Answer 13

Identify user stories and requirements

Plant the sprint

Design the solution

Develop new features

Test continuously

Review sprint progress

Sprint retrospective

Release

Repeat

Question 14

1st stage in the extreme programming model

Answer 14

Identify user stories and requirements

Work closely with stakeholders to gather functional and non-functional requirements

Requirements are often written as user stories

Question 15

2nd stage in the extreme programming model

Answer 15

Plan the sprint (Sprint Planning)

Break down requirements into tasks

Choose a set of tasks (features) for the current sprint (a short time-boxed development period, usually 1–4 weeks)

Define the sprint goal

Question 16

3rd stage in the extreme programming model

Answer 16

Design the solution

Decide how the selected features will be built

Focus is on simple and adaptable design, not heavy upfront documentation

Question 17

4th stage in the extreme programming model

Answer 17

Develop the features

Write code for the selected tasks in the sprint

Developers often work in pairs or small teams

Question 18

5th stage in the extreme programming model

Answer 18

Test continuously

Perform unit testing, integration testing, and acceptance testing during the sprint

Testing is ongoing, not saved for the end

Question 19

6th stage in the extreme programming model

Answer 19

Review progress (Sprint Review)

Demo the working software to stakeholders

Collect feedback and identify changes or improvements

Question 20

7th stage in the extreme programming model

Answer 20

Reflect on process (Sprint Retrospective)

The team reflects on what went well and what needs improving in the next sprint

Focus is on team performance and process optimisation

Question 21

Last 2 stages of the extreme programming model

Answer 21

Release (may happen after every sprint or set of sprints)

Deploy working software to users or staging environment

Repeat

Move to the next sprint with updated priorities and feedback

Question 22

Benefits of the extreme programming model?

Answer 22

Highly adaptable- responding quickly to changes

Frequent communication

High quality focus

Customer Collaboration

Question 23

Drawbacks of the extreme programming model?

Answer 23

Requires experience team members

Intensive collaboration can lead to burnout

May lack documentation due to a focus on immediate coding

There can be uncontrolled changes in requirements

Question 24

What is extreme programming most suitable for?

Answer 24

Small to medium-sized projects

Because requirements can change and customer involvement is high

Question 25

Spiral model?

Answer 25

A CYCLIC software development method that combines aspects of both agile and waterfall processes.

Question 26

Stages in the spiral model?

Answer 26

Planning Risk analysis Engineering Evaluation and Feedback The process repeats, spiralling through these stages, with each spiral loop representing a development phase until the final product is ready

Question 27

1st stage of the spiral model?

Answer 27

Planning: Define the objectives, alternatives, and constraints for the current phase of the project

Question 28

2nd stage of the spiral model

Answer 28

Risk analysis: Identify and assess potential risks, and plan mitigation strategies

Question 29

3rd stage of the spiral model

Answer 29

Engineering: Develop the next version of the product, including design, coding, testing, and integration

Question 30

4th stage of the spiral model

Answer 30

Evaluation and feedback: Review the progress with stakeholders, and plan the next iteration

Question 31

Benefits of the spiral model?

Answer 31

Flexibility-Allows for changes Risk management- address issues early Strong customer involvement Incremental releases- early usage and feedback

Question 32

Drawbacks of the spiral model?

Answer 32

Complexity Time consuming Expensive Not suitable for small projects

Question 33

Suitability of the spiral model?

Answer 33

Most suitable for large complex projects Where requirements may change, and risk management is essential

Question 34

What is rapid application development?

Answer 34

A phase-based software development method that emphasises fast and iterative development

Question 35

Stages of rapid application development?

Answer 35

Requirement planning User design and prototyping Iterative development (Construction) Cutover / deployment Maintenance and updates

Question 36

1st stage of rapid application development?

Answer 36

Requirement planning: Gather general system requirements, define constraints and assumptions

Question 37

2nd stage of rapid application development?

Answer 37

User design and prototyping: Collaborate with users to develop prototypes, ensuring alignment with user needs

Question 38

3rd stage of rapid application development?

Answer 38

Construction or iterative development: Build the system incrementally, with continuous user feedback and adaptation

Question 39

4th stage of rapid application development?

Answer 39

Cutover or deployment: Transition the product into the live environment, including user training, support, and documentation

Question 40

5th stage of rapid application development?

Answer 40

Maintenance and updates: Continue to adapt and improve the system based on user feedback and needs

Question 41

Benefits of rapid application development?

Answer 41

Speed User involvement Flexibility Promotes development in small increments, with constant feedback and adaptation

Question 42

Drawbacks of rapid application development?

Answer 42

Dependent on strong team collaboration Potential lack of quality Not suitable for small projects- overkill Can lead to scope creep

Question 43

Scope creep?

Answer 43

When the flexible nature of a model leads to uncontrolled changes in requirements.

Question 44

Suitability of rapid application development?

Answer 44

Most suitable for projects where rapid delivery is required Where requirements can be developed and refined on the go