key activities in requirements analysis (week 2) Flashcards
1
Q
what are the 6 different types of activities in requirement analysis
A
- gather detailed information
- identify functional requirements
- identify non functional requirements
- define non functional requirements
- prioritise requirements
- evaluate requirements
2
Q
what happens in activity 1 : gather detailed requirements
A
- -> talk to the users of new system or similar systems
- -> read the documentation on existing system
- -> develop expertise in business area of the system
- -> collect technical information = ie understand computer usage, work locations software packages, etc
3
Q
what happens in activity 2: identify functional requirements
A
- -> system requirements that describe what the system must perform
- -> needed to support the business process
4
Q
what happens in activity 3 : identify non functional requirements
A
- -> constraints or characteristics expected from the system
- -> PURS
- -> scalability
- -> performance
- -> usability
- -> reliability
- -> security
5
Q
what happens in activity 4 : define non functional requirements
A
- -> development constraint = system should be written in java
- -> system constraint = validate the pin number in 3 seconds
6
Q
what happens in activity 5 : prioritise requirements
A
- -> manage users requests according to user needs, urgency, etc
- -> balance between user needs and limitation of resources
- -> scope creep is the tendency of a function list to grow in an uncontrollable manner and is a challenge when managing requirements.it leads to cost overruns and implementation delays
7
Q
what happens in activity 6 : evaluate requirements
A
–> evaluate the requirements until an acceptable requirements model
–> evaluate all possibilities in the design and implementation of the system
–> validate the accuracy and correctness of the requirements
–> iterative process