Browse > Article
http://dx.doi.org/10.3745/KIPSTD.2008.15-D.4.505

A Single Requirement Modeling with Graphical Language for Embedded System  

Oh, Jung-Sup (아주대학교 대학원 컴퓨터공학과)
Lee, Hong-Seok (아주대학교 대학원 전자공학과)
Park, Hyun-Sang (아주대학교 정보통신전문대학원 정보통신공학과)
Kim, Jang-Bok (아주대학교 정보통신전문대학원 정보통신공학과)
Choi, Kyung-Hee (아주대학교 정보통신전문대학원)
Jung, Ki-Hyun (아주대학교 전자공학부)
Abstract
In order to do requirement-based testing of embedded system, we must have correct requirement specifications. But, natural language requirements of a client have ambiguity, inaccuracy, and inconsistency. To solve these problems, natural language requirements are modeled with modeling language such as UML and Simulink. During a modeling phase, the requirements are rearranged and retranslated in use-case. These activities are disadvantages of modeling. In this paper, we propose the technique, which is how to model a embedded system requirement into a model without rearranging and retranslating. This technique 1) represent a embedded system requirement with graphical language, and 2) model a requirement into a model. Because this technique only describes "what-to-do" of the requirement, this technique is useful to not only the low-level requirements but also the high-level requirements. We show some example systems modeled by REED, which has adopted this technique.
Keywords
Requirement; Modeling; Single Requirement; REED; RBT;
Citations & Related Records
연도 인용수 순위
  • Reference
1 Compuware, “How Compuware Optimal Trace helps business analysts meet the business challenge,” Fact sheet, 2006
2 Telelogic, “Key Enabling Technologies of Telelogic Rhapsody,” http://modeling.telelogic.com/products/rhapsody/index.cfm
3 A Pnueli, “A temporal logic of programs.” Theoretical Computer Science, 13:45-60, 1981   DOI   ScienceOn
4 E.M.Clarke and E.A.Emerson. “Synthesis of synchronization skeletons for branching time temporal logic,” In D. Kozen, editor, Logic of Programs Workshop, number 131 in LNCS. Springer Verlag, 1981
5 Mor Peleg and Dov Dori, "The Model Multiplicity Problem: Experimenting with Real-Time Specification Methods,” IEEE Transactions on Software Engineering, Vol.26, No.8, pp.742-759, AUGUST, 2000   DOI   ScienceOn
6 INCOSE Requirements Management Tools Survey, http://www.paper-review.com/tools/rms/read.php
7 Telelogic AB, http://www.telelogic.com/products/doors/doors/index.cfm
8 Borland Software Co., http://www.borland.com/us/products/caliber /index.html
9 Compuware Co., http://www.compuware.com/products/optimaltrace/
10 Matthias Hoffmann, Nikolaus Kühn, and Margot Bitner, “Requirements for Requirements Management Tools,” Proceedings of the $12^{th}$ IEEE International Requirements Engineering Conference(RE'04), pp.301-308, 2004
11 The MathWorks, Inc., http://www.mathworks.com/products/simulink/
12 J. Martin, An information Systems Manifesto, Prentice Hall, 1984
13 Telelogic, “Datasheet : Telelogic DOORS,” http://www. telelogic.com/download/get_file.cfm?id=3726, 2005
14 Borland, “Integrating Requirements into Software Development,” http://www.borland.com/resources/en/pdf/solutions/rdm_in tegrating_reqs_into_software_dev.pdf, White paper, June 2006
15 Object Management Group, “Unified Modleling Language (UML), Version 2.1.2”, http://www.omg.org/spec/UML/2.1.2/,November 2007
16 James Bach, “Risk and Requirements-Based Testing,” IEEE Computer, Vol.32, No.6, pp.113-114, June, 1999   DOI   ScienceOn