Software Development

Question 1

What is the waterfall lifecycle?

Answer 1

Sequential software development process divided into distinct phases

Question 2

What happens during analysis in the waterfall lifecycle?

Answer 2

All possible system requirements to be developed are captured and documented clearly

Question 3

What happens during design in the waterfall lifecycle?

Answer 3

Requirements from analysis are translated into a design.
Designers define overall structure and main concepts

Question 4

What happens during implementation in the waterfall lifecycle?

Answer 4

Actual code is written based on design documents turning design into a functional program

Question 5

What happens during testing in the waterfall lifecycle?

Answer 5

All components and modules are integrated(brought together)and tested to make sure system works as expected

Question 6

What happens during deployment in the waterfall lifecycle?

Answer 6

The product is released to the client
May involve installation, customisation and training

Question 7

What happens during maintenance in the waterfall lifecycle?

Answer 7

Post-release the system needs regular maintenance to fix bugs, improve performance and add new features

Question 8

What are the benefits of the waterfall lifecycle?

Answer 8

Easy to understand and follow as each stage progressive linearly to next
Clear stages and milestones making progress easy to measure
Suitable for well defined projects as works best when requirement are clearand unlikely to change during development

Question 9

What are the drawbacks of the waterfall cycle?

Answer 9

Inflexible as changes are difficult to implement once project has started and cant revisit previous stages
Expensive to fix late problems
Long development cycle as sequential nature may lead to longer development time

Question 10

What is the waterfall model suitable for?

Answer 10

Projects where requirements are well understood and unlikely to change
Clear understanding of project goals and constraints

Question 11

What is extreme programming?

Answer 11

A type of agile software development methodology that promotes adaptability and high customer involvement

Question 12

What happens during planning in the Agile(XP)
development?

Answer 12

Customer and developers define the scope and priorities
Includes writing user stories

Question 13

What happens during design in the Agile(XP)
development?

Answer 13

Developers create a simple design for the system that can evolve over time

Question 14

What happens during coding in the Agile(XP)
development?

Answer 14

Coding done in small increments with frequent integration(bringing together) and pair programming to ensure quality

Question 15

What happens during testing in the Agile(XP)
development?

Answer 15

Continuous testing throughout the coding process with automated tests developed before or alongside code

Question 16

What happens during Iteration and Feedback in the Agile(XP)
development?

Answer 16

Constant feedback from stakeholders is used to guide future development cycles leading to iterative and incremental development

Question 17

What are the benefits of Agile(XP) development?

Answer 17

Highly adaptable as it can respond quickly to changes
Frequent communication encourages constant communication between developers and users
Quality focus
Customer collaboration encourages working closely with customers and ensure it meets their needs

Question 18

What are the drawbacks of Agile(XP) development?

Answer 18

Requires experienced team members
Intensive collaboration can lead to burnout as constant communication can be tiring
May lack documentation as it focuses on adaptability and immediate coding
Scope creep flexible nature may lead to uncontrolled changed in requirements

Question 19

What is Agile(XP) development suitable for?

Answer 19

For small to medium-sized projects where requirements can change and customer involvement is high

Question 20

What is the spiral model?

Answer 20

Software development methodology that combines aspects of both iterative and sequential processes

Question 21

What happens during planning in the spiral model?

Answer 21

Defines the objective, alternatives and constraints for current phase of project

Question 22

What happens during analysis in the spiral model?

Answer 22

Identifies and assess potential risks, and plan mitigation(reduce risk) strategies

Question 23

What happens during engineering in the spiral model?

Answer 23

Develop the next version of the project including design, coding, testing and integration(bring together smaller components)

Question 24

What happens during evaluation and feedback in the spiral model?

Answer 24

Review the progress with stakeholders, and plan next iteration

Question 25

What are benefits of spiral model?

Answer 25

**Flexibility**-Allows for changes and adaptations at any stage **Risk management**-Emphesises risk assessment helping to identify issues **Strong customer involvement** **Incremental releases**-Provides early and partial working solutions, enabling early usage and feedback

Question 26

What are drawbacks of spiral model?

Answer 26

**Complexity** **Time-consuming**-Emphasis on planning, risk management etc. may lead to longer development process **Expensive** as it requires more resources **Not suitable for small project** - Extensive planning and risk management might be overkill for small projects

Question 27

What is a spiral model suitable for?

Answer 27

Large, complex projects where requirements may change, and risk management is essential

Question 28

What is RAD (Rapid Application Development)?

Answer 28

Software development methodology that emphesises **fast** and **iterative development**

Question 29

What happens during requirement planning in RAD?

Answer 29

**Gather** general **system** **requirements,** define system **constraints**

Question 30

What happens during user design and prototyping in RAD?

Answer 30

**Collaborate** with **users** to **develop prototypes**, **ensuring alignment** with **user needs**

Question 31

What happens during construction or iterative development in RAD?

Answer 31

**Build** the **system incrementally**, with **continuous user feedback** and adaptation

Question 32

What happens during maintenance and updates in RAD?

Answer 32

Continues to **adapt** and **improve** the **system** **based on user feedback** and needs

Question 33

What are the benefits of RAD?

Answer 33

**Speed**-Enables rapid development and delivery of high quality **User involvement**-Clients are involved throughout the development process, ensuring system aligns with user expectations **Flexibility**-Allows for changes and adaptations to be made quickly as requirements change **Incremental development**-Promotes development in small increments with feedback

Question 34

What are drawbacks of RAD?

Answer 34

**Dependent on strong team collaboration**-Requires skilled and collaborative team members **Potential lack of quality**-Speed may lead to skipping testing or documentation **Not suitable for small projects**-Intense collaboration and iterative approach may be overkill **Can lead to scope creep**-leads to uncontrolled changes in requirments

Question 35

What is RAD suitable for?

Answer 35

Projects where rapid delivery is required and where requirements can be developed and refined on the go

Question 36

What are the 5 steps of the waterfall cycle?

Answer 36

Requirement Design Development Testing Deployment Maintenance

Question 37

What are the 7 steps of the agile model?

Answer 37

Requirements Design Development Testing Deployment Review Repeat

Question 38

What are the steps in the spiral model?

Answer 38

Planning Risk analysis Engineering Evaluation and feedback

Question 39

What are the 5 steps in the RAD model?

Answer 39

Requirement planning User design and prototyping Construction or iterative development Deployment Maintenance