Podcast Beta
Questions and Answers
User requirements are typically written in a technical language that is difficult for end-users to understand.
False
A design description approach uses natural language to specify system requirements.
False
Structured language natural is a notation that uses a language similar to a programming language.
False
The design description approach is commonly used for interface specifications.
Signup and view all the answers
System requirements are typically less detailed than user requirements.
Signup and view all the answers
Requirements specification is the process of writing down only user requirements in a document.
Signup and view all the answers
UML use case and sequence diagrams are used to define non-functional requirements for the system.
Signup and view all the answers
Mathematical specifications are based on ambiguous concepts and are understood by most customers.
Signup and view all the answers
Graphical notations are used in conjunction with natural language to define system requirements.
Signup and view all the answers
Requirements and design are always separate in systems engineering.
Signup and view all the answers
Natural language specifications are expressive, intuitive, and universal.
Signup and view all the answers
A system architecture is never designed to structure the requirements.
Signup and view all the answers
A self-test routine can only discover software problems.
Signup and view all the answers
Structured specifications are always too rigid for writing business system requirements.
Signup and view all the answers
Form-based specifications include a description of the side effects of a function.
Signup and view all the answers
Tabular specification is a replacement for natural language.
Signup and view all the answers
A structured specification only includes a description of inputs and outputs.
Signup and view all the answers
Requirements Engineering is not related to system architecture.
Signup and view all the answers
Study Notes
Requirements Specification
- Photos are visible to the moderator and the user who uploaded them.
- Requirements specification is the process of writing down user and system requirements in a requirements document.
User and System Requirements
- User requirements must be understandable by end-users and customers without a technical background.
- System requirements are more detailed and may include technical information.
- Requirements may be part of a contract for system development, making it important to be as complete as possible.
Ways of Writing a System Requirements Specification
- Natural language: requirements are written using numbered sentences in natural language, each expressing one requirement.
- Structured language (natural): requirements are written in natural language on a standard form or template, each field providing information about an aspect of the requirement.
- Design description: uses a language like a programming language to specify requirements by defining an operational model of the system (rarely used).
- Graphical notations: graphical models, supplemented by text annotations, are used to define functional requirements for the system (e.g., UML use case and sequence diagrams).
- Mathematical specifications: based on mathematical concepts, such as finite-state machines or sets, but may not be understood by customers.
Requirements and Design
- In principle, requirements state what the system should do, while design describes how it does it.
- In practice, requirements and design are inseparable, with system architecture influencing requirements and design.
Natural Language Specification
- Requirements are written as natural language sentences, supplemented by diagrams and tables.
- Natural language is expressive, intuitive, and universal.
Structured Specifications
- An approach to writing requirements where the freedom of the requirements writer is limited, and requirements are written in a standard way.
- Works well for some types of requirements (e.g., embedded control systems), but may be too rigid for writing business system requirements.
Form-based Specifications
- Definition of the function or entity.
- Description of inputs and where they come from.
- Description of outputs and where they go to.
- Information about the information needed for the computation and other entities used.
- Description of the action to be taken.
- Pre and post conditions (if appropriate).
- The side effects (if any) of the function.
Tabular Specification
- Used to supplement natural language.
- Particularly useful when defining a number of possible alternative courses of action.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Description
Test your knowledge on structured specifications, which is an approach to writing requirements with limited freedom and in a standard way. Explore how structured specifications are used for different types of requirements such as embedded control systems and business systems.
