NDLI: Lack of Attention to Singular (or Atomic) Requirements Despite Benefits for Quality, Metrics and Management

Please wait, while we are loading the content...

Lack of Attention to Singular (or Atomic) Requirements Despite Benefits for Quality, Metrics and Management

Content Provider	ACM Digital Library
Author	Takada, Shingo Noda, Natsuko Honig, William L.
Abstract	There are seemingly many advantages to being able to identify, document, test, and trace single or "atomic" requirements. Why then has there been little attention to the topic and no widely used definition or process on how to define atomic requirements? Definitions of requirements and standards focus on user needs, system capabilities or functions; some definitions include making individual requirements singular or without the use of conjunctions. In a few cases there has been a description of atomic system events or requirements. This work is surveyed here although there is no well accepted and used best practice for generating atomic requirements. Due to their importance in software engineering, quality and metrics for requirements have received considerable attention. In the seminal paper on software requirements quality, Davis et al. proposed specific metrics including the "unambiguous quality factor" and the "verifiable quality factor"; these and other metrics work best with a clearly enumerable list of single requirements. Atomic requirements are defined here as a natural language statement that completely describes a single system function, feature, need, or capability, including all information, details, limits, and characteristics. A typical user login screen is used as an example of an atomic requirement which can include both functional and nonfunctional requirements. Individual atomic requirements are supported by a system glossary, references to applicable industry standards, mock ups of the user interface, etc. One way to identify such atomic requirements is from use case or system event analysis. This definition of atomic requirements is still a work in progress and offered to prompt discussion. Atomic requirements allow clear naming or numbering of requirements for traceability, change management, and importance ranking. Further, atomic requirements defined in this manner are suitable for rapid implementation approaches (implementing one requirement at a time), enable good test planning (testing can clearly indicate pass or fail of the whole requirement), and offer other management advantages in project control.
Starting Page	1
Ending Page	5
Page Count	5
File Format	PDF
ISSN	01635948
DOI	10.1145/2967307.2967315
Journal	ACM SIGSOFT Software Engineering Notes (SOEN)
Volume Number	41
Issue Number	4
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	1979-04-01
Publisher Place	New York
Access Restriction	One Nation One Subscription (ONOS)
Subject Keyword	Atomic use cases Requirements creation Requirements verification and validation Atomic requirements Development process Requirements metrics Singular requirements Software engineering
Content Type	Text
Resource Type	Article

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in

Verification and Validation for Trustworthy Software Systems

MaramaAIC: tool support for consistency management and validation of requirements

Capturing the benefits of requirements engineering

Effective Quality Management: Value- and Risk-Based Software Quality Management

Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications

Task descriptions versus use cases

Enhancing Defect Tracking Systems to Facilitate Software Quality Improvement

An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects

Software Quality, Metrics, Process Improvement, and CMMI: An Interview with Dick Fairley

Lack of Attention to Singular (or Atomic) Requirements Despite Benefits for Quality, Metrics and Management

Similar Documents

Verification and Validation for Trustworthy Software Systems

MaramaAIC: tool support for consistency management and validation of requirements

Capturing the benefits of requirements engineering

Effective Quality Management: Value- and Risk-Based Software Quality Management

Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications

Task descriptions versus use cases

Enhancing Defect Tracking Systems to Facilitate Software Quality Improvement

An Empirical Study on the Relationship Between Software Design Quality, Development Effort and Governance in Open Source Projects

Software Quality, Metrics, Process Improvement, and CMMI: An Interview with Dick Fairley

Lack of Attention to Singular (or Atomic) Requirements Despite Benefits for Quality, Metrics and Management