SysRS > Nonfunctional (Quality) Requirements Specification

Release Information

Project: Phoenix Systems Architecture and Engineering
Internal Release Number: X.Y.Z
Attached worksheets:
LINKS TO WORKSHEETS
Related Documents:
Project proposal [LINK TO BE PROVIDED]
LINKS TO RELEVANT STANDARDS
LINKS TO OTHER DOCUMENTS

Development-Oriented Concerns

TODO!

ONE PARAGRAPH OVERVIEW

List of subtopics:

Change Concerns

TODO!

ONE PARAGRAPH OVERVIEW

List of subtopics:

Flexibility
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Expandability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Analysis framework must be adaptable to chronobiology scenarios other than blood pressure

Portability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Scalability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Maintainability
TODO! Concern: aptitude to undergo repairs and evolution

ONE PARAGRAPH OVERVIEW

Details:

What are the maintainability and upgradability requirements?

Maintainability is our ability to make changes to the product over time. We need strong maintainability in order to retain our early customers. We will address this by anticipating several types of change, and by carefully documenting our design and implementation.

Upgradability is our ability to cost-effectively deploy new versions of the product to customers with minimal downtime or disruption. A key feature supporting this goal is automatic download of patches and upgrade of the end-user's machine. Also, we shall use data file formats that include enough meta-data to allow us to reliably transform existing customer data during an upgrade.

Details:

  • DETAIL
  • DETAIL
  • DETAIL
Re-usability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Management Concerns

TODO!

ONE PARAGRAPH OVERVIEW

List of subtopics:

Designability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Installability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Manageability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Verifiability
TODO!

ONE PARAGRAPH OVERVIEW

Details:

Usage-Oriented Functional Concerns

TODO!

ONE PARAGRAPH OVERVIEW

List of subtopics:

Accessibility

TODO!

ONE PARAGRAPH OVERVIEW

Details:

Auditability

TODO!

ONE PARAGRAPH OVERVIEW

Details:

Configurability

TODO!

ONE PARAGRAPH OVERVIEW

Details:

Correctness

TODO!

ONE PARAGRAPH OVERVIEW

Details:

Dependability

Dependability: that property of a computer system such that reliance can justifiably be placed on the service it delivers.

Sources of taxonomy:

  • Barbacci, Mario; Klein, Mark H.; Longstaff, Thomas A.; and Weinstock, Charles B. "Quality Attributes", SEI Technical Report, CMU/SEI-95-TR-021. December 1995.
  • Weigers, Karl E. Software Requirements. 2nd ed. 2003, Microsoft Press.
  • Withall, Stephen. Software Requirement Patterns. 2007, Microsoft Press.

Taxonomy of Concerns
IDAttributeConcern
DE-01 Availability
  • Operational availability
  • Readiness for usage.
  • The degree to which a system, subsystem, or equipment is operable and in a committable state at the start of a mission, when the mission is called for at an unknown, i.e., a random, time.
  • A measure of the planned up time during which the system is actually available for use and fully operational.
DE-02 Biocompatibility
  • The ability of a device to perform its intended function, with the desired degree of incorporation in or application to the (biological) host, without eliciting any undesirable local or systemic effects in that host.
DE-03 Privacy
  • Ensurance that information about a person is free from any intrusion not sanctioned by the person.
DE-04 Reliability
  • Continuity of service.
  • The rate of failure in the system that renders the system unusable.
  • The ability of the system to keep operating over time.
DE-05 Robustness
  • Graceful handling of invalid inputs.
  • Ensurance that user input cannot crash the system or corrupt data, even if that user input is abnormal, unexpected, or malicious.
DE-06 Safety
  • Non-occurrence of catastrophic consequences on the environment
DE-07 Security
  • Ensurance that information is accessible only to those authorized to have access.
  • A condition of not being threatened, especially physically, psychologically, emotionally, or financially.
Integrity
  • Non-occurrence of improper alterations of information.
  • Ensurance that data is "whole" or complete.
  • The condition in which data is identically maintained during any operation, such as during transfer, storage or retrieval.
DE-08 Survivabilty
  • The degree to which a system can fulfill its mission, in a timely manner, in the presence of attacks, failures, or accidents.

Interoperability

TODO!

ONE PARAGRAPH OVERVIEW

Details:

Performance

Performance: that attribute of a computer system that characterizes the timeliness of the service delivered by the system.

Sources of taxonomy:

  • Barbacci, Mario; Klein, Mark H.; Longstaff, Thomas A.; and Weinstock, Charles B. "Quality Attributes", SEI Technical Report, CMU/SEI-95-TR-021. December 1995.
  • Weigers, Karl E. Software Requirements. 2nd ed. 2003, Microsoft Press.

Taxonomy of Concerns
IDAttributeConcern
PE-01 Response Time How long does it take the system to satisfy requests?
PE-02 Latency How can the demand and resources change over time? What happens when system capacity is exceeded and not all events can be responded to in a timely manner?
PE-03 Throughput To how many events can responses be produced over a given interval of time?
PE-04 Dynamic Capacity How much demand can be placed on the system while continuing to meet latency and throughput requirements?
PE-05 Static Capacity How many entities of a particular type can the system store?
PE-06 Modes How can the demand and resources change over time? What happens when system capacity is exceeded and not all events can be responded to in a timely manner?

Usability

TODO!

ONE PARAGRAPH OVERVIEW

Details:

What are the usability requirements?

Our main criteria for making the system usable is the difficulty of performing each high-frequency use case. Difficulty depends on the number of steps, the knowledge that the user must have at each step, the decisions that the user must make at each step, and the mechanics of each step (e.g., typing a book title exactly is hard, clicking on a title in a list is easy).

The user interface should be as familiar as possible to users who have used other web applications and Windows desktop applications. E.g., we will follow the UI guidelines for naming menus, buttons, and dialog boxes whenever possible.

PARAGRAPH

Details:

Easier to use than current:
  • Blood pressure cuffs
  • Home BP monitors
Patient can:
  • Ignore device
  • Determine that device is functioning normally
  • Observe a blood pressure and heart rate measurement
Device:
  • Is automatic
Measurements taken regardless of patient behavior
  • Allows manually initiated measurements

This page is maintained by Christopher J. Adams. It was last updated 9 January 2011.

Copyright (c) 2011 Christopher J. Adams
Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 Unported License