16 Questions
What is the purpose of defining requirements in a sufficiently abstract way when letting a contract for a large software development project?
To ensure that several contractors can bid for the contract
Which of the following best describes User Requirements?
Natural language statements with diagrams of services provided
What is the responsibility of Health Care Managers in relation to a system?
Obtaining management information from the system
What is included in System Requirements?
Detailed descriptions of system functions
What is the primary purpose of requirements engineering according to the passage?
To establish the services that the customer requires from a system and the constraints under which it operates and is developed
What is the relationship between requirements and system development according to the quote by Louis Srygley?
Requirements and design are the foundation for programming, without which it becomes the art of adding bugs to an empty text file
According to the passage, what are the key purposes that requirements serve in the system development process?
Requirements serve as the basis for project planning, risk management, trade-offs, change control, and acceptance testing
What is the key difference between 'requirements' and 'requirements engineering' according to the passage?
Requirements are the services and constraints that the customer requires, while requirements engineering is the process of establishing those requirements
According to the passage, what are the key characteristics that requirements should possess?
Requirements should be complete and consistent, with no conflicts or contradictions in the descriptions of system facilities
What is the key role of the system stakeholders in the requirements engineering process according to the passage?
System stakeholders are responsible for establishing the services they require from the system and the constraints under which it operates and is developed
What is the primary purpose of the 'System Architecture' chapter in a Software Requirements Document?
To present a high-level overview of the anticipated distribution of functions across system modules
Which section of the Software Requirements Document typically includes graphical system models?
System Models
What is the primary purpose of the 'System Evolution' section in a Software Requirements Document?
To outline the fundamental assumptions on which the system is based, and any anticipated changes due to hardware evolution or changing user needs
Which section of the Software Requirements Document typically includes information about hardware and database descriptions?
Appendices
What is the primary purpose of the 'System Requirements Specification' section in a Software Requirements Document?
To describe the functional and nonfunctional requirements in more detail, and potentially define interfaces to other systems
Which of the following is not typically included in a Software Requirements Document?
A detailed design of the system's user interface
Study Notes
IT System Stakeholders
- IT Staff: responsible for installing and maintaining the system
- Medical Ethics Manager: ensures the system meets current ethical guidelines for patient care
- Health Care Managers: obtain management information from the system
- Medical Records Staff: responsible for ensuring system information can be maintained and preserved, and record keeping procedures are properly implemented
Requirements Abstraction
- A company must define its needs in a sufficiently abstract way to allow multiple contractors to bid for the contract
- The requirements must not pre-define a solution, allowing contractors to offer different ways of meeting the client's needs
User REQs versus System REQs
- User Requirements: statements in natural language, diagrams of services and operational constraints, written for customers
- System Requirements: structured document, detailed descriptions of system functions, services, and operational constraints
Importance of Requirements
- Requirements form the basis for project planning, risk management, trade-off, change control, and acceptance testing
- Without requirements, programming is the art of adding bugs to an empty text file
Defining Requirements Engineering
- The subset of systems engineering concerned with discovering, developing, tracing, analyzing, qualifying, communicating, and managing requirements
- The process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed
Requirements Completeness and Consistency
- Requirements should be both complete and consistent
- Complete: descriptions of all facilities required
- Consistent: no conflicts or contradictions in the descriptions of system facilities
System Architecture
- Presents a high-level overview of the anticipated system architecture
- Shows distribution of functions across system modules
- Highlights architectural components that are reused
Software Requirements Document
- Typical structure includes:
- System description
- Requirements
- Specification
- Interfaces to other systems
- System models
- System evolution
- Appendices (detailed, specific information related to the application)
- Hardware requirements define minimal and optimal configurations for the system
Explore the high-level overview of system architecture and the typical structure of a software requirements document in this quiz. Learn about the distribution of functions across system modules and the detailed description of functional and nonfunctional requirements.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
