{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:41:44Z","timestamp":1750308104563,"version":"3.41.0"},"reference-count":19,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2005,5,21]],"date-time":"2005-05-21T00:00:00Z","timestamp":1116633600000},"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":[[2005,7]]},"abstract":"<jats:p>Today the lack of deliveries from suppliers to automotive OEMs in early phases of software development cause a number of problems such as misinterpreted requirements and difficulties in keeping deadlines. We have identified use cases as a means to communicate and visualize requirements. A well defined standard is needed to enable communication between different organizations.In this paper we propose a two level use case standard for embedded systems. The standard consists of a template and guidelines specifying how to write consistent and unambiguous use cases while capturing the necessary requirements.<\/jats:p>","DOI":"10.1145\/1082983.1083193","type":"journal-article","created":{"date-parts":[[2005,11,7]],"date-time":"2005-11-07T19:28:32Z","timestamp":1131391712000},"page":"1-6","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Automotive use case standard for embedded systems"],"prefix":"10.1145","volume":"30","author":[{"given":"Fredrik","family":"Pettersson","sequence":"first","affiliation":[{"name":"Chalmers University of Technology, Gothenburg, Sweden"}]},{"given":"Martin","family":"Ivarsson","sequence":"additional","affiliation":[{"name":"Chalmers University of Technology, Gothenburg, Sweden"}]},{"given":"Peter","family":"\u00d6hman","sequence":"additional","affiliation":[{"name":"Chalmers University of Technology, Gothenburg, Sweden"}]}],"member":"320","published-online":{"date-parts":[[2005,5,21]]},"reference":[{"key":"e_1_2_1_1_1","first-page":"72","volume-title":"Software Engineering Project Management, Thayer and Yourdon eds","author":"Thayer R. H.","year":"1997"},{"key":"e_1_2_1_2_1","first-page":"80","volume-title":"Harvard Business Review","author":"Mackenzie R. A.","year":"1969"},{"key":"e_1_2_1_3_1","doi-asserted-by":"publisher","DOI":"10.5555\/309683"},{"volume-title":"Object-Oriented Software Engineering - A Use Case Driven Approach","year":"1992","author":"Jacobson I.","key":"e_1_2_1_4_1"},{"volume-title":"Use Cases: Requirements in Context","year":"2000","author":"Kulak D.","key":"e_1_2_1_5_1"},{"key":"e_1_2_1_6_1","unstructured":"OMG 2003 \"UML 2.0 Superstructure Specification\" Object Management Group http:\/\/www.omg.org\/docs\/ptc\/03-08-02.pdf 2003.  OMG 2003 \"UML 2.0 Superstructure Specification\" Object Management Group http:\/\/www.omg.org\/docs\/ptc\/03-08-02.pdf 2003."},{"volume-title":"Writing Effective Use Cases","year":"2001","author":"Cockburn A.","key":"e_1_2_1_7_1"},{"volume-title":"Applying Use Cases","year":"2001","author":"Schneider G.","key":"e_1_2_1_8_1"},{"volume-title":"http:\/\/members.aol.com\/acockburn\/papers\/usecases.htm","year":"2000","author":"Cockburn A.","key":"e_1_2_1_9_1"},{"volume-title":"Proceedings of the Seventh International Workshop on Object-Oriented Real-Time Dependable Systems (WORDS 2002","year":"2002","author":"Nasr E.","key":"e_1_2_1_10_1"},{"volume-title":"Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design","year":"1998","author":"Larman C.","key":"e_1_2_1_11_1"},{"key":"e_1_2_1_12_1","doi-asserted-by":"publisher","DOI":"10.5555\/832317.837764"},{"key":"e_1_2_1_13_1","doi-asserted-by":"publisher","DOI":"10.5555\/882515.885531"},{"key":"e_1_2_1_14_1","doi-asserted-by":"publisher","DOI":"10.5555\/374133"},{"key":"e_1_2_1_15_1","unstructured":"IEEE \"IEEE Recommended Practice for Software Requirements Specifications\" IEEE Std. 830-1998  IEEE \"IEEE Recommended Practice for Software Requirements Specifications\" IEEE Std. 830-1998"},{"key":"e_1_2_1_16_1","first-page":"402","volume-title":"ECOOP 2001","author":"Anda B.","year":"2001"},{"key":"e_1_2_1_17_1","doi-asserted-by":"publisher","DOI":"10.1007\/11497455_29"},{"volume-title":"Dept. of Computer Engineering","year":"2004","author":"Ivarsson M.","key":"e_1_2_1_18_1"},{"volume-title":"Hewlett-Packard Software Initiative","year":"1998","author":"Coleman D.","key":"e_1_2_1_19_1"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1082983.1083193","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1082983.1083193","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T16:08:05Z","timestamp":1750262885000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1082983.1083193"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2005,5,21]]},"references-count":19,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2005,7]]}},"alternative-id":["10.1145\/1082983.1083193"],"URL":"https:\/\/doi.org\/10.1145\/1082983.1083193","relation":{"is-identical-to":[{"id-type":"doi","id":"10.1145\/1083190.1083193","asserted-by":"subject"}]},"ISSN":["0163-5948"],"issn-type":[{"type":"print","value":"0163-5948"}],"subject":[],"published":{"date-parts":[[2005,5,21]]},"assertion":[{"value":"2005-05-21","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}