質問  |
答え |
|
学び始める
|
|
Descriptions of what the system should do: the services that it provides and the constraints on its operation
|
|
|
what are user requirments? 学び始める
|
|
features the user needs the software product to support
|
|
|
What are system requirements? 学び始める
|
|
things the software needs to function
|
|
|
what are functional requirements? 学び始める
|
|
defines a function of a system or its component. A function is described as a set of inputs, the behavior, and outputs.
|
|
|
what are non functional requirements? 学び始める
|
|
a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. They are contrasted with functional requirements that define specific behavior or functions.
|
|
|
What is requirements engineering? 学び始める
|
|
The process of gathering, analysing, documenting, and checking requirements
|
|
|
what are teh 4 stages of Requirements engineering? 学び始める
|
|
▶ Feasibility study ▶ Requirements elicitation ▶ Requirements specification ▶ Requirements validation
|
|
|
What is a feasibility study? 学び始める
|
|
an assessment of the practicality of a proposed plan or method.
|
|
|
What is requirments elicitation? 学び始める
|
|
the practice of collecting the requirements of a system from users, customers and stakeholders. AKA "requirement gathering" Commonly used elicitation processes are the stakeholder meetings or interviews.
|
|
|
Whata re the 4 stages of Requirements Elicitation? 学び始める
|
|
1) discovery and understanding 2) clasification adn organisation 3) prioritisation and negotiation 4) documenttation
|
|
|
what are the main methods of requirements elicitation? 学び始める
|
|
interviews, focus groups, scenarios, use cases, ethnography
|
|
|
|
学び始める
|
|
wtaching how people work and understanding based on observation
|
|
|
