Software Development

1. defining the problem and establishing the requirements of the project

1. considering which algorithms, data structures, user interfaces etc. should be used

1. Black box/functional
   1. looking at the program spec. and a creating set of data that covers all inputs and outputs and program func..
      1. doesn't look at the code
2. White box / structural
   1. SOFTWARE DEV. TEAMS -> program code is studied -> tests are devised which test each possible path at least once.
3. Alpha
   1. IN-HOUSE SOFTWARE DEV. TEAMS reveals both errors and omissions in the system requirements definition
4. Beta
   1. giving a newly developed software package to a number of potential users who agree to use the system and report any problems to the developers

1. After testing stage has been used to make the appropriate changes to the software, it is installed onto the users’ systems

1. effectiveness of software is evaluated against the system req. defined during analysis stage to evaluate its suitability in solving the problem. Different criteria are considered -> robustness, reliability, portability and maintainability.

1. iterative, regularly develops prototypes
2. collection of methodologies
3. aim to improve the flexibility of software development
4. adapt to changes in user requirements faster.
5. builds software incrementally from the start of the project, instead of trying to deliver all at once.
6. Small - medium projects + unclear initial requirements
7. Agile

1. large complex projects
2. req. well understood
3. stages carried out sequentially

1. focus of effectively managing risk-heavy projects
2. Analysing system requirements
   1. Pinpointing and mitigating risks
      1. Development, testing and implementation
         1. 1. Evaluating to inform the next iteration
3. Large, risk-intensive projects with a high budget
4. Spiral

1. pair of programmers alongside a representative end-user
   1. built on ‘user stories’:
      1. system reqs. are specified by end-user + used when designing the program.
2. XP
3. high quality code

1. user requirements made in focus groups
   1. prototype made and developed along with the reqs.
      1. continuously until the final product is reached
2. Small - medium, low-budget projects with short time-frames.
3. RAD

Attachments:

• System Development methods comparisons

1. sequence of instructions that result in a desired outcome