Abstract
Extension of the modeling notations and formal languages for use case description are the commonly suggested solutions for adding precision to use case models. Practitioners have often argued against adoption of such techniques citing reasons like the steep learning curve for formal languages; and the quickness in using imprecise use case descriptions for communicating to different stake-holders of the system. In this paper we introduce the Archetest modeling environment, which through a unique bi-layer approach accepts use case descriptions in their imprecise form and then assists in adding precision through a wizard driven process. Thereby, it lends itself to both quick and precise modeling. Also the two forms of the use case models are self contained and cross-linked. This allows different modelers, the precise and the imprecise, to collaborate and also supports stake-holder specific feedbacks of the automated analysis. We describe the structure of Archetest’s use case models, and show how these models are amenable to automated processing. We present a case study which reports on typical modeling times using Archetest and demonstrates its scalability.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Carroll, J.M.: Five reasons for scenario-based design. In: HICSS (1999)
Firesmith, D.G.: Modeling the Dynamic Behavior of Systems, Mechanisms and Classes with Scenarios, pp. 32–36. SIGS Publication, New York (1994)
Hsia, P., Samuel, J., Gao, J., Kung, D., Toyoshima, Y., Chen, C.: Formal approach to scenario analysis. IEEE Softw. 11(2), 33–41 (1994)
Jacobson, I.: Object-oriented development in an industrial environment. In: OOPSLA 1987: Conference proceedings on Object-oriented programming systems, languages and applications, pp. 183–191. ACM Press, New York (1987)
Rosenberg, D., Scott, K.: Use case driven object modeling with UML: a practical approach. Addison-Wesley Longman Publishing Co., Inc., Boston (1999)
Rubin, K.S., Goldberg, A.: Object behavior analysis. Commun. ACM 35(9), 48–62 (1992)
Potts, C., Takahashi, K., Anton, A.: Inquiry-based requirements analysis. IEEE Software 11(2), 21–32 (1994)
Blain, T.: Use case series: Formal use case, http://tynerblain.wordpress.com/2005/12/19/use-case-series-formal-use-case/
Regnell, B., Kimbler, K., Wesslen, A.: Improving the use case driven approach to requirements engineering. re 00, 40 (1995)
Kösters, G., Pagel, B.U., Winter, M.: Coupling use cases and class models. In: BCS FACS/EROS Workshop on Making Object-oriented Methods more Rigorous (1997)
Lee, W.J., Cha, S.D., Kwon, Y.R.: Integration and analysis of use cases using mod- ular petri nets in requirements engineering. Software Engineering 24(12), 1115–1130 (1998)
Moreira, A., Jo a.A.: Generating object-z specications from use cases, pp. 43–50 (2000)
Hausmann, J.H., Heckel, R., Taentzer, G.: Detection of conicting functional re- quirements in a use case-driven approach: a static analysis technique based on graph transformation. In: ICSE, pp. 105–115 (2002)
Bures, F., Rysav, O.: Formal abstract architecture for use case specications. In: Proceedings of the 11th IEEE International Conference and Workshop on the Engineering of Computer-Based Systems, pp. 203–211. IEEE Computer Society Press, Los Alamitos (2004)
Jorgensen, J.B., Bossen, C.: Executable use cases: Requirements for a pervasive health care system. IEEE Softw. 21(2), 34–41 (2004)
Li, X., Liu, Z., He, J.: Consistency checking of uml requirements. In: ICECCS 2005: Proceedings of the 10th IEEE International Conference on Engineering of Complex Computer Systems (ICECCS 2005), Wasshington, DC, USA, pp. 411–420. IEEE Computer Society, Los Alamitos (2005)
Whittle, J., Jayaraman, P.K.: Generating hierarchical state machines from use case charts. In: Proc. of the 14th IEEE International Requirements Engineering Conference (RE 2006), Washington, DC, USA, pp. 16–25. IEEE, Los Alamitos (2006)
Glinz, M.: A lightweight approach to consistency of scenarios and class models. In: ICRE, pp. 49–58 (2000)
Sinha, A., Paradkar, A., Williams, C.: On generating efsm models from use cases. In: SCESM 2007: Proceedings of Sixth InternationalWorkshop on Scenario and State Machines, pp. 1–9 (2007)
Hayes, J.H.: Building a requirement fault taxonomy: Experiences from a nasa verication and validation research project. In: ISSRE 2003: Proceedings of the 14th International Symposium on Software Reliability Engineering, Washington,DC, USA, p. 49. IEEE Computer Society, Los Alamitos (2003)
Miller, L., Mirsky, S., Hayes, J.H.: Guidelines for the verication and validation of expert system software and conventional software. Technical Report NUREG/CR- 6316, U.S. Nuclear Regulatory Commission and Electric Power Research Institute (March 1995)
Buhr, R.J.A.: Use case maps as architectural entities for complex systems. IEEE Trans. Softw. Eng. 24(12), 1131–1155 (1998)
Briand, L.C., Labiche, Y., O’Sullivan, L.: Impact analysis and change management of uml models. In: ICSM, Washington, DC, USA, p. 256. IEEE Computer Society, Los Alamitos (2003)
Egyed, A.: Fixing inconsistencies in uml design models. In: ICSE 2007: Proceedings of the 29th International Conference on Software Engineering, Washington, DC,USA, pp. 292–301. IEEE Computer Society, Los Alamitos (2007)
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2008 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Sinha, A., Kaplan, M., Paradkar, A., Williams, C. (2008). Requirements Modeling and Validation Using Bi-layer Use Case Descriptions. In: Czarnecki, K., Ober, I., Bruel, JM., Uhl, A., Völter, M. (eds) Model Driven Engineering Languages and Systems. MODELS 2008. Lecture Notes in Computer Science, vol 5301. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-87875-9_7
Download citation
DOI: https://doi.org/10.1007/978-3-540-87875-9_7
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-87874-2
Online ISBN: 978-3-540-87875-9
eBook Packages: Computer ScienceComputer Science (R0)