1.2.3 Software Development

Question 1

Stages

Answer 1

Analysis
Design
Development
Testing

Implementation
Evaluation
Maintenance

Question 2

Alpha vs Beta testing

Answer 2

Alpha: in-house by software dev teams
Beta: end users

Question 3

White vs Black box testing

Answer 3

White: Carried out by dev team, all possibilities are tested (knowledge of internal structure)

Black: Software is tested without testers being aware of internal structure, by company or end-users

Question 4

Waterfall

Answer 4

Analysis
Design
Implementaion
Evaluation
Maintenance

Analysis: TELOS
Technical (Possible)
Economic
LEgal
Operational (Can it be implemented and maintained)
Scheduling (Completed in time)

Question 5

Agile

Answer 5

Broken into sections which are developed in parallel.
Prototype produced early on, prototypes are improved upon interatively.

Analysis -> (Loop of: Design, build, feedback, refine) -> Final

Question 6

Extreme

Answer 6

An agile model
Pair of programmers (written by one, critiqued by other) and end-user.
Built on “user storeis” generates each cycle which produces a working version

Question 7

Spiral

Answer 7

Heavy risk: Risk assessors can advise termination

4 stages:
Analysis
Risk assessment
Implementation
Evaluation

Question 8

RAD

Answer 8

Iterative methodology using partially functioning protoypes that are continually built upon.
User feedback used to generate the next, used when initial requirements are unclear.

Question 9

Writing and following algorithms

Answer 9

Inputs clearly defined
Must always produce valid output
Must deal with invalid inputs
Must reach a stopping condition
Must be well-documented
Must be well-commented

Question 10

Waterfall Merits Drawbacks and Uses

Answer 10

+ Documented well
- Not flexible

Low-risk, little user input

Question 11

Agile Merits Drawbacks and Uses

Answer 11

+ High quality code
+ Flexible to user input
- Poor documentation
- Requires much communication with end user

Small to medium with unclear requirements

Question 12

Extreme programming Merits Drawbacks and Uses

Answer 12

+ High quality code
- Two people is expensive and might not work well

Small to medium with unclear requirements

Question 13

Spiral Merits Drawbacks and Uses

Answer 13

+ Risk analysis
- Expensive to hire risk assessors

Large, risk-intensive projects

Question 14

RAD rad rad

Answer 14

+ Caters to changing user requirements
- Poor documentation

Small projects with low buget and short timeframe