Midterm Exam Reviewer Flashcards
Quizzes (85 cards)
A problem which occur when functional and non-functional requirements tend to be mixed-up
Requirements confusion
The process of writing down the user and system requirements in a requirements document.
Requirements specification
A kind of scenario that are included in the UML.
use case
A description of how a system may be used for a particular task.
Stories and scenarios
Several different requirements may be expressed together.
Requirements amalgamation
Statements in natural language plus diagrams of the services the system
user requirements
It is the process of managing changing requirements during the requirements engineering process and system development.
Requirements management
Several different requirements may be expressed together.
Requirements amalgamation
The document is difficult to read
Lack of clarity
An approach to writing requirements where the freedom of the requirements writer is limited and requirements are written in a standard way
Structured specifications
The descriptions of the system services and constraints that are generated during the requirements engineering process.
system requirements
Requirements which should describe the system services in detail.
Functional system requirements
Constraints on the system from the domain of operation
Domain requirements
Constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards
Non-functional requirements
The process of establishing the services that a customer requires from a system and the constraints under which it operates and is developed.
requirements engineering
It involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system’s operational constraints.
Requirements elicitation
It is effective for understanding existing processes but cannot identify new features that should be added to a system.
Ethnography
Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations.
Functional requirements
It is concerned with demonstrating that the requirements define the system that the customer really wants.
Requirements validation
Any person or organization who is affected by the system in some way and so who has a legitimate interest
system stakeholders
Which of the following is NOT an advantage of having an explicit architecture?
Guaranteed performance of all system components
What is a common criticism of simple, informal block diagrams used for documenting software architectures?
They lack semantics and do not show types of relationships.
What is one benefit of using architectural models in system design discussions?
They facilitate communication by presenting a high-level view.
What is a key aspect of architectural design decisions?
They vary based on the type of system being developed.