214417
Beschreibung
Karteikarten von nina.evangelou, aktualisiert more than 1 year ago
|
Erstellt von nina.evangelou
vor etwa 11 Jahre
|
|
| Frage | Antworten |
| acceptance tests | A series of tests devised to demonstrate that a completed system can meet all the behavioural requirements set out as use cases in the requirements document. |
| acceptance testing | Testing which aims to convince the client that the system works as specified. |
| analyst | A generic term for a person who takes on the role (or a combination of the roles) of a business analyst, systems analyst or requirements analyst |
| behavioural requirement | A specific task that the system being developed must be able to do. |
| business analyst | A person who understands the business systems within a organisation. |
| business area | The real-world context within which the system is required to operate. |
| business system | A business system is a combination of people and software working together to meet a particular set of business objectives. |
| constraint (on the system) | A limitation on the system or its development. |
| requirements analysis | The process of analysing and distilling the information from requirements elicitation into a clear and coherent description of the system and specification of its behaviour |
| requirements analyst | A person who is an expert in eliciting and analysing the requirements of a new software system. |
| requirements creep | A situation where the software developers come under pressure to deliver in excess of what was originally agreed. |
| requirements document | The specification of the requirements of the system produced after negotiation between the client and the analyst |
| requirements elicitation | The act of finding out the requirements of a system by consulting with the stakeholders |
| scope | The breadth of services that the system is expected to provide |
| stakeholder | Anyone who has an interest in a system including the client, the future users, analysts and developers. |
| system domain | The real-world context specific to the software system being developed. |
| use case | A concise description of a specific task that a user of the system must be able to perform. |
Möchten Sie mit GoConqr kostenlos Ihre eigenen Karteikarten erstellen? Mehr erfahren.