1.2.3 Software Development

Question 1

Identify the common stages of software development life cycles (SDLCs)

Answer 1

Analysis
Design
Development
Testing
Implementation
Evaluation
Maintenance
(ADD TIE M)

Question 2

Define white box testing:

Answer 2

A form of testing carried out by software development teams in which the test plan is based on the internal structure of the program. All of the possible routes through the program are tested.

Question 3

What is TELOS

Answer 3

A method of analysis used by designers to evaluate the feasibility of a project. It considers:

Technical
Economic
Legal
Operational
Scheduling

aspects of the project

Question 4

What are agile methodologies?

Answer 4

A collection of methodologies which aim to improve flexibility of software development. They respond quickly to changes in user requirements.

Question 5

Identify the advantages of waterfall programming methodologies:

Answer 5

• Straightforward to manage
• Clear structure
• Clearly documented

Question 6

Give 3 disadvantages of extreme programming methodologies:

Answer 6

• High cost due to 2 people working on one project
• Teamwork and good communication is essential
• End-user must be present throughout the duration of the project

Question 7

What type of projects are spiral programming methodologies suited to?

Answer 7

Large, risk-intensive projects with high budget

Question 8

What type of projects are Rapid Application Development (RAD) programming methodologies suited to?

Answer 8

Projects where high usability is required and user requirements may not be clear from the outset or are continually changing. Suited to projects of a small to medium size with a relatively low budget and short time-frame.

Question 9

Define an algorithm:

Answer 9

A set of instructions used to solve a problem

Question 10

State key qualities or considerations good algorithms should make:

Answer 10

• Inputs must be clearly defined (what is valid and invalid?)
• Must always produce a valid output for any defined input
• Must always be able to deal with invalid inputs
• Must always reach a stopping condition
• Must be well-documented for reference
• Must be well-commented so modifications can easily be made