{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:10:31Z","timestamp":1750306231254,"version":"3.41.0"},"reference-count":23,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2016,8,19]],"date-time":"2016-08-19T00:00:00Z","timestamp":1471564800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[2016,8,19]]},"abstract":"<jats:p>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.<\/jats:p>","DOI":"10.1145\/2967307.2967315","type":"journal-article","created":{"date-parts":[[2016,8,26]],"date-time":"2016-08-26T12:25:39Z","timestamp":1472214339000},"page":"1-5","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":2,"title":["Lack of Attention to Singular (or Atomic) Requirements Despite Benefits for Quality, Metrics and Management"],"prefix":"10.1145","volume":"41","author":[{"given":"William L.","family":"Honig","sequence":"first","affiliation":[{"name":"Loyola University Chicago, Chicago, Illinois"}]},{"given":"Natsuko","family":"Noda","sequence":"additional","affiliation":[{"name":"Shibaura Institute of Technology, Minato, Tokyo, Japan"}]},{"given":"Shingo","family":"Takada","sequence":"additional","affiliation":[{"name":"Keio University, Hiyoshi, Yokohama, Japan"}]}],"member":"320","published-online":{"date-parts":[[2016,8,19]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"BA Times 2014. New Age Requirements Capturing Methodologies- Are Requirement Documents Dead?  BA Times 2014. New Age Requirements Capturing Methodologies- Are Requirement Documents Dead?"},{"key":"e_1_2_1_2_1","doi-asserted-by":"publisher","DOI":"10.5555\/2821327.2821333"},{"volume-title":"Proceedings of the First International Software Metrics Symposium (May 21-22, 1993","year":"1993","author":"Davis A.","key":"e_1_2_1_3_1"},{"key":"e_1_2_1_4_1","doi-asserted-by":"publisher","DOI":"10.1109\/AIRE.2015.7337622"},{"key":"e_1_2_1_5_1","unstructured":"IBM Press 2007. Requirements Management Using IBM Rational RequisitePro. http:\/\/www.ibmpressbooks.com\/articles\/article.asp?p=1152528. Accessed 2016-06-01.  IBM Press 2007. Requirements Management Using IBM Rational RequisitePro. http:\/\/www.ibmpressbooks.com\/articles\/article.asp?p=1152528. Accessed 2016-06-01."},{"key":"e_1_2_1_6_1","unstructured":"IEEE Standard 29148. 2011. Systems and software engineering -- Life cycle processes -- Requirements engineering. ISO\/IEC\/IEEE. DOI= 10.1109\/IEEESTD.2011.6146379.  IEEE Standard 29148. 2011. Systems and software engineering -- Life cycle processes -- Requirements engineering. ISO\/IEC\/IEEE. DOI= 10.1109\/IEEESTD.2011.6146379."},{"key":"e_1_2_1_7_1","doi-asserted-by":"publisher","DOI":"10.1145\/71633.71641"},{"key":"e_1_2_1_8_1","unstructured":"Mitre 2016. Analyzing and Defining Requirements. https:\/\/www.mitre.org\/publications\/systems-engineering-guide\/se-lifecycle-building-blocks\/requirements-engineering\/analyzing-and-defining-requirements. Accessed 2016-04-22.  Mitre 2016. Analyzing and Defining Requirements. https:\/\/www.mitre.org\/publications\/systems-engineering-guide\/se-lifecycle-building-blocks\/requirements-engineering\/analyzing-and-defining-requirements. Accessed 2016-04-22."},{"key":"e_1_2_1_9_1","doi-asserted-by":"publisher","DOI":"10.1007\/978-3-540-45242-3_41"},{"volume-title":"Proceedings of International Workshop on Model-Driven Web Engineering","year":"2005","author":"Nguyen K.","key":"e_1_2_1_10_1"},{"key":"e_1_2_1_11_1","doi-asserted-by":"publisher","DOI":"10.1108\/17440080680000098"},{"key":"e_1_2_1_12_1","unstructured":"Planet Project 2009. Writing atomic functional requirements. http:\/\/planetproject.wikidot.com\/writing-atomic-functional-requirements. Accessed 2016-03-16.  Planet Project 2009. Writing atomic functional requirements. http:\/\/planetproject.wikidot.com\/writing-atomic-functional-requirements. Accessed 2016-03-16."},{"key":"e_1_2_1_13_1","unstructured":"Planet Project 2009. How to determine if a requirement is atomic. http:\/\/planetproject.wikidot.com\/how-to-determine-if-a-requirement-is-atomic. Accessed 2016-03-16.  Planet Project 2009. How to determine if a requirement is atomic. http:\/\/planetproject.wikidot.com\/how-to-determine-if-a-requirement-is-atomic. Accessed 2016-03-16."},{"key":"e_1_2_1_14_1","unstructured":"Pressman R and Maxim B. 2014. Software Engineering -- A Practitioner's Approach. McGraw-Hill Education New York NY.   Pressman R and Maxim B. 2014. Software Engineering -- A Practitioner's Approach. McGraw-Hill Education New York NY."},{"key":"e_1_2_1_15_1","unstructured":"Robertson S. and Robertson J. 2013. Mastering the Requirements Process -- Getting Requirements Right 3rd ed. Addison-Wesley Upper Saddle River NJ.   Robertson S. and Robertson J. 2013. Mastering the Requirements Process -- Getting Requirements Right 3rd ed. Addison-Wesley Upper Saddle River NJ."},{"key":"e_1_2_1_16_1","first-page":"46","article-title":"Atomic requirements in teaching logic control implementation","volume":"20","author":"Salzer H.","year":"2004","journal-title":"Int. J Engineering Ed"},{"key":"e_1_2_1_17_1","doi-asserted-by":"publisher","DOI":"10.1109\/SwSTE.2010.11"},{"key":"e_1_2_1_18_1","unstructured":"Sommerville I. 2015. Software Engineering. Pearson Education Limited Harlow England.   Sommerville I. 2015. Software Engineering. Pearson Education Limited Harlow England."},{"key":"e_1_2_1_19_1","unstructured":"Stumpf R. and Teague L. 2005. Object-Oriented Systems Analysis and Design With UML. Prentice-Hall Upper Saddle River NJ.  Stumpf R. and Teague L. 2005. Object-Oriented Systems Analysis and Design With UML. Prentice-Hall Upper Saddle River NJ."},{"key":"e_1_2_1_20_1","unstructured":"The Atlantic Systems Guild 2009. Atomic Requirements: where the rubber hits the road. http:\/\/www.volere.co.uk\/pdf%20files\/06%20Atomic%20Requirements.pdf. Accessed 2016-03-16.  The Atlantic Systems Guild 2009. Atomic Requirements: where the rubber hits the road. http:\/\/www.volere.co.uk\/pdf%20files\/06%20Atomic%20Requirements.pdf. Accessed 2016-03-16."},{"key":"e_1_2_1_21_1","unstructured":"Tynerblain.com 2006. Atomic requirements. http:\/\/tynerblain.com\/blog\/2010\/09\/14\/atomic-requirements\/. Accessed 2016-03-16.  Tynerblain.com 2006. Atomic requirements. http:\/\/tynerblain.com\/blog\/2010\/09\/14\/atomic-requirements\/. Accessed 2016-03-16."},{"key":"e_1_2_1_22_1","unstructured":"Tynerblain.com 2010. Writing atomic requirements. http:\/\/tynerblain.com\/blog\/2006\/06\/14\/writing-atomic-requirements\/. Accessed 2016-03-16.  Tynerblain.com 2010. Writing atomic requirements. http:\/\/tynerblain.com\/blog\/2006\/06\/14\/writing-atomic-requirements\/. Accessed 2016-03-16."},{"key":"e_1_2_1_23_1","unstructured":"Zielczynski P. 2007. Requirements Management Using IBM Rational RequisitePro. Pearson \/ IBM Press.   Zielczynski P. 2007. Requirements Management Using IBM Rational RequisitePro. Pearson \/ IBM Press."}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2967307.2967315","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/2967307.2967315","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T04:23:13Z","timestamp":1750220593000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2967307.2967315"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2016,8,19]]},"references-count":23,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2016,8,19]]}},"alternative-id":["10.1145\/2967307.2967315"],"URL":"https:\/\/doi.org\/10.1145\/2967307.2967315","relation":{},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2016,8,19]]},"assertion":[{"value":"2016-08-19","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}