Example:
London Underground
Cash based to computer based.
Problem
Identify a problem.
Analyse
Design
Needs to meet specification.
Implementation
Implement at multiple levels.
Test
System test
User Acceptance Testing (UAT)
Install
Maintain
Evaluate
Successful?
2 main methodologies:
Waterfall method:
Spiral method:
This is very useful for identifying the data requirements, as well as the input and output required.
- Can be more reliable as parts of the design process are built on top of each other (require affective base work).
- The user can review at each stage.
- Difficult to review complex projects afterwards.
- No REAL prototyping (LONG time for visible results).
Spiral method:
- Can review sections of the design process multiple times.
- Avoids risk.
- Lots of prototyping (keeps the user involved).
- Gets feedback.
- 'Baby steps' slow but steady.
- Prototype tends to go live.
- Low level of communication.
Information Gathering:
- Interview.
This can be time consuming, but it does allow you to probe for answers and get first hand information.
- Questionnaire.
This is useful when there are lots of users, although there is a limit to how much you will find out.
- Observe the current system.
Although time- consuming, this is objective rather than subjective and you might spot things that the user doesn't.
- Examine the existing documentation.
No comments:
Post a Comment