{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T05:02:23Z","timestamp":1750309343105,"version":"3.41.0"},"reference-count":24,"publisher":"Association for Computing Machinery (ACM)","issue":"3","license":[{"start":{"date-parts":[[2024,7,17]],"date-time":"2024-07-17T00:00:00Z","timestamp":1721174400000},"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":[[2024,7,17]]},"abstract":"<jats:p>There are seemingly many advantages to being able to identify, document, test, and trace single or \"atomic\" requirements during system development and maintenance. Ongoing work with Agile development has focused on \"user stories\" that can capture individual features for implementation. However, it is still difficult to evaluate the quality of such requirements and teaching their creation is difficult.<\/jats:p>\n          <jats:p>Based on a working definition of atomic requirement, this paper proposes a set of metrics for their evaluation. Ten metrics designed to measure atomic requirements are presented here: five used on individual requirements statements and five applied to a requirements document or set of requirement statements.<\/jats:p>\n          <jats:p>Example metrics for individual requirements include Requirement Atomic Completeness and Requirement Atomic Verifiability. Requirement Traceability is a proposed metric for a set of atomic requirements (such as a traditional requirements specification document.)<\/jats:p>\n          <jats:p>Further work is needed to make the suggested metrics more consistent and precise, including exploring the use of tools that may automate some of the measures. However, a first step is to refine the metrics themselves and ensure they adequately measure atomic requirement quality.<\/jats:p>\n          <jats:p>Hence this note shares the proposed metrics to encourage discussion and to recommend experimentation. The author is applying the metrics in software engineering courses doing team software development.<\/jats:p>\n          <jats:p>The goal is the eventual acceptance of a set of requirements metrics specifically designed to evaluate atomic requirements. Better metric definitions may lead to wider utilization of atomic requirements and improved requirements engineering in general.<\/jats:p>","DOI":"10.1145\/3672089.3672096","type":"journal-article","created":{"date-parts":[[2024,7,18]],"date-time":"2024-07-18T20:23:37Z","timestamp":1721334217000},"page":"23-26","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Establishing Metrics to Encourage Broader Use of Atomic Requirements - A Call for Exchange and Experimentation"],"prefix":"10.1145","volume":"49","author":[{"given":"William L.","family":"Honig","sequence":"first","affiliation":[{"name":"Loyola University Chicago, Chicago, IL, USA"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2024,7,18]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"publisher","DOI":"10.1109\/SAM.2015.18"},{"key":"e_1_2_1_2_1","doi-asserted-by":"publisher","DOI":"10.1109\/METRIC.1993.263792"},{"key":"e_1_2_1_3_1","doi-asserted-by":"publisher","DOI":"10.1145\/3202710.3203145"},{"volume-title":"Exploring Requirements -- Quality Before Design","author":"Gause Donald","key":"e_1_2_1_4_1","unstructured":"Donald Gause, Gerald Weinberg, 1989. Exploring Requirements -- Quality Before Design. Dorset House."},{"key":"e_1_2_1_5_1","doi-asserted-by":"publisher","DOI":"10.1145\/3379177.3388895"},{"key":"e_1_2_1_6_1","doi-asserted-by":"publisher","unstructured":"S. Gregory. Requirements engineering: the quest for meaningful metrics: time for a change? IEEE Software 36 6 (Dec. 2019) 7--11 doi: 10.1109\/MS.2019.2933685.","DOI":"10.1109\/MS.2019.2933685"},{"key":"e_1_2_1_7_1","doi-asserted-by":"publisher","DOI":"10.1109\/ICORIS.2019.8874888"},{"key":"e_1_2_1_8_1","doi-asserted-by":"publisher","DOI":"10.1109\/RE48521.2020.00014"},{"key":"e_1_2_1_9_1","doi-asserted-by":"publisher","DOI":"10.1145\/2967307.2967315"},{"key":"e_1_2_1_10_1","doi-asserted-by":"publisher","DOI":"10.1145\/2381716.2381786"},{"key":"e_1_2_1_11_1","doi-asserted-by":"publisher","DOI":"10.5555\/317498.317687"},{"key":"e_1_2_1_12_1","doi-asserted-by":"publisher","unstructured":"IEEE Standard 29148 2011. Systems and software engineering - life cycle processes - requirements engineering. doi: 10.1109\/IEEESTD.2011.6146379.","DOI":"10.1109\/IEEESTD.2011.6146379"},{"key":"e_1_2_1_13_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.2002.1027796"},{"key":"e_1_2_1_14_1","doi-asserted-by":"publisher","DOI":"10.1080\/12460125.2016.1187390"},{"key":"e_1_2_1_15_1","doi-asserted-by":"publisher","DOI":"10.1007\/978--3--540--45242--3_41"},{"key":"e_1_2_1_16_1","volume-title":"Proc. Intl Workshop on Model-Driven Web Engineering.","author":"Nguyen K.","year":"2005","unstructured":"K. Nguyen, T. Dillon. 2005. Atomic use case as a concept to support the MDE approach to web application development. In Proc. Intl Workshop on Model-Driven Web Engineering."},{"key":"e_1_2_1_17_1","doi-asserted-by":"publisher","DOI":"10.1145\/336512.336523"},{"key":"e_1_2_1_18_1","doi-asserted-by":"publisher","DOI":"10.1109\/ICORIS.2019.8874920"},{"key":"e_1_2_1_19_1","doi-asserted-by":"publisher","DOI":"10.5555\/3463952.3464076"},{"key":"e_1_2_1_20_1","volume-title":"Requirements atomization in software engineering education. Research proposal","author":"Salzer Hanania","year":"2003","unstructured":"Hanania Salzer. Requirements atomization in software engineering education. Research proposal, Tel Aviv University (May 2003)."},{"key":"e_1_2_1_21_1","volume-title":"Proceedings of Quality Week (QWEE '99)","author":"Salzer Hanania","year":"1999","unstructured":"Hanania Salzer, 1999. ATRs (atomic requirements) used throughout development lifecycle. In Proceedings of Quality Week (QWEE '99)."},{"key":"e_1_2_1_22_1","first-page":"1","article-title":"Atomic requirements in teaching logic control implementation","volume":"20","author":"Salzer Hanania","year":"2004","unstructured":"Hanania Salzer, Ilya Levin. 2004. Atomic requirements in teaching logic control implementation. In Intl. J. of Engineering Education 20, 1. 46--51.","journal-title":"Intl. J. of Engineering Education"},{"key":"e_1_2_1_23_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.2005.97"},{"key":"e_1_2_1_24_1","doi-asserted-by":"publisher","DOI":"10.1109\/2.348001"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3672089.3672096","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3672089.3672096","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T00:04:29Z","timestamp":1750291469000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3672089.3672096"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2024,7,17]]},"references-count":24,"journal-issue":{"issue":"3","published-print":{"date-parts":[[2024,7,17]]}},"alternative-id":["10.1145\/3672089.3672096"],"URL":"https:\/\/doi.org\/10.1145\/3672089.3672096","relation":{},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2024,7,17]]},"assertion":[{"value":"2024-07-18","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}