Term
| what's requirement engineering? |
|
Definition
a systematic approach to eliciting, organizing, and documenting requirements of the system
a process that maintains agreement between customer and project team on changing requirements of the system |
|
|
Term
|
Definition
| capability, physical characteristic, behavior, etc |
|
|
Term
|
Definition
| a document that describes physical element in terms of requirements |
|
|
Term
| what are 3 steps of requirement engineering? |
|
Definition
1. idea of new product
2. requirements development
3. requirements specification |
|
|
Term
| what is the 2 highest reason a project will fail? |
|
Definition
| because of lack of user input, incomplete requirements and specs |
|
|
Term
| draw diagram for software life cycle activities |
|
Definition
|
|
Term
| what is software life cycle? |
|
Definition
| set of activities to support development of software |
|
|
Term
| what is first step in identifying requirement? |
|
Definition
|
|
Term
| in system identification, what are 2 questions that needs to be answered? |
|
Definition
1. what's the purpose of the system?
2. what's the boundary |
|
|
Term
| what's the difference between requirement and analysis? |
|
Definition
| requirement gives definition of a system from user's view but analysis gives definition of a system from developer's view |
|
|
Term
| what are 4 techniques to elicit requirements? |
|
Definition
1. Scenario
2. Task analysis
3. Use cases
4. Questionnaires
STUQ |
|
|
Term
| give 4 criteria of a good requirement |
|
Definition
1. consistent
2. unambiguous
3. verifiable
4. design-free |
|
|
Term
|
Definition
| ideal users for the system |
|
|
Term
|
Definition
| a textual description of usage of system from user's point of view |
|
|
Term
| what is scenario based design? |
|
Definition
| use of scenarios in a software life cycle activify |
|
|
Term
| what does scenario based design focus on? |
|
Definition
| focus on concrete descriptions and particular instance |
|
|
Term
| what types of scenario are there? |
|
Definition
1. as-is scenario: describes current situation
2. visionary scenario: describes future system
3. evaluation scenario: used in acceptance testing
4. training scenario: used in training |
|
|
Term
|
Definition
1. primary tasks
2. data
3. changes |
|
|
Term
| list 6 criteria for good user interface specification |
|
Definition
1. clear
2. consistent
3. simple
4. direct
5. tolerance
6. behaves exactly as expected |
|
|
Term
| what are difficulties of requirement elicitation |
|
Definition
1. tradeoffs
2. accurate communication
3. unambiguous specification
4. unintended features
5. identification |
|
|
Term
| what are 3 types of requirements? |
|
Definition
1. functional
2. non-functional
3. constraint |
|
|
Term
| what's the difference between functional and non-functional requirement? |
|
Definition
functional requirement describes what should system do
non-functional requirement describe properties of the system |
|
|
Term
| give 3 example of what should not be functional requirement |
|
Definition
1. system structure
2. implementation technology
3. development technology |
|
|
Term
| what's requirement validation? |
|
Definition
validates requirement from 6 point of view
1. correctness
2. completeness
3. consistency
4. clarity
5. realistic
6. traceability |
|
|
Term
| what is requirements management system? |
|
Definition
|
|
Term
| what are 3 different types of requirement elicitation? |
|
Definition
1. start from scratch
2. reengineer
3. interface |
|
|
Term
| there are three priorities for requirements, when should each be addressed? |
|
Definition
1. high priority: all
2. medium priority: no implementation
3. low priority: just analysis |
|
|
Term
| what are steps in elicitation activities? |
|
Definition
1. identify users
2. identify scenarios
3. identify use cases
4. refine use cases
5. identify relationships
6. identify non-functional requirements |
|
|
Term
| what is project agreement? |
|
Definition
| acceptance of analysis model |
|
|
