chapter4

• What do functional requirements describe?

  Functionality or system services
• What factors do functional requirements depend on?

  Type of software, expected users, system type
• What are functional user requirements?

  High-level statements of system functionality
• What should functional system requirements describe?

  System services in detail
• What is a requirement for the MHC-PMS regarding appointments?

  User can search appointment lists for clinics
• How should staff members be identified in the MHC-PMS?

  By an 8-digit employee number
• What problems arise from imprecise requirements?

  Ambiguous requirements can be misinterpreted
• How can the term 'search' be interpreted differently?

  User may mean searching all clinics
• What should requirements ideally be?

  Complete and consistent
• What does completeness in requirements mean?

  All required facilities are described
• What does consistency in requirements imply?

  No conflicts or contradictions exist
• Why is it impossible to produce a complete requirements document?

  Real-world complexity and changing needs
• What do non-functional requirements define?

  System properties and constraints
• Why might non-functional requirements be more critical?

  If unmet, the system may be useless
• How can non-functional requirements affect system architecture?

  They may require minimizing component communication
• What can a single non-functional requirement generate?

  Multiple related functional requirements
• What are product requirements?

  Specify behavior like execution speed
• What are organizational requirements?

  Consequences of policies and procedures
• What are external requirements?

  Arise from external factors like legislation
• What is a product requirement for the MHC-PMS?

  Available during normal working hours
• What is an organizational requirement for the MHC-PMS?

  Users authenticate with health authority ID
• What is an external requirement for the MHC-PMS?

  Implement patient privacy provisions
• What is a goal in requirements engineering?

  A general intention of the user
• What is a verifiable non-functional requirement?

  Can be objectively tested with measures
• Why are goals helpful to developers?

  They convey user intentions for the system
• What topics are covered in requirements engineering?

  • Functional and non-functional requirements
  • Software requirements document
  • Requirements specification
  • Requirements engineering processes
  • Requirements elicitation and analysis
  • Requirements validation
  • Requirements management
• What should usability requirements ensure?

  System is easy to use and minimizes errors
• What is a testable non-functional requirement for medical staff?

  Errors should not exceed two per hour
• What metrics can specify non-functional requirements?

  • Speed: Processed transactions/second
  • User/event response time
  • Size: Mbytes
  • Ease of use: Training time
  • Reliability: Mean time to failure
  • Availability: Probability of unavailability
  • Portability: Number of target systems
• What do domain requirements impose on a system?

  Operational constraints and specific computations
• What happens if domain requirements are not satisfied?

  The system may be unworkable
• What is a domain requirement for a train protection system?

  Deceleration computed as $D_{train} =$$D_{control} +$$D_{gradient}$
• Why is it difficult for non-specialists to understand domain requirements?

  They may lack knowledge of the application domain
• What is a key point about software system requirements?

  They define what the system should do
• What is the purpose of the software requirements document?

  Official statement of system requirements
• What should the software requirements document include?

  User requirements and system requirements specification
• What is the difference between user and system requirements?

  User requirements are understandable by non-technical users
• Why is it important for requirements to be complete?

  They may be part of a contract for development
• What is a structured specification?

  Requirements written in a standard way
• What is a form-based specification?

  Defines function, inputs, outputs, and actions