Lightweight Behavior-Based Language for Requirements Modeling
- 1 College of Computer and Software Engineering, Shenzhen University, Shenzhen, China
- 2 School of Computer, Wuhan University, Wuhan, China.
- 3 School of Computer, Wuhan University, Wuhan, China.
Abstract
Whether or not a software system satisfies the anticipated user requirements is ultimately determined by the behaviors of the software. So it is necessary and valuable to research requirements modeling language and technique from the perspective of behavior. This paper presents a lightweight behavior based requirements modeling language BDL with formal syntax and semantics, and a general-purpose requirements description model BRM synthesizing the concepts of viewpoint and scenario. BRM is good for modeling large and complex system due to its structure is very clear. In addition, the modeling process is demonstrated through the case study On-Line Campus Management System. By lightweight formal style, BDL & BRM can effectively bridge the gap between practicability and rigorousness of formal requirements modeling language and technique.
- Object Management Group, “OMG Unified Modeling Language (OMG UML) Version 2.0,” 2005.
- J. E. Hopcroft, R. Motwani, and J. D. Ullman, “Introduc- tion to automata theory, languages, and computation,” 2nd Edition, Pearson Education, 2000.
- “Information technology—Z formal specification nota- tion—Syntax, type system and semantics,” ISO/IEC 13568, 2002.
- “Information processing systems—Open systems inter- connection—Enhancements to LOTOS—A formal des- cription technique based on the temporal ordering of observational behavior,” ISO/IEC 15437, 2001.
- J. L. Peterson, “Petri net theory and the modeling of systems,” Prentice Hall, 1981.
- R. Milner, “Communicating and mobile systems: The Pi-calculus,” Cambridge University Press, 1999.
- J. P. Bowen and M. G. Hinchey, “Ten commandments of formal methods... ten years later,” IEEE Computer, Vol. 39, No. 1, pp. 40–48, January 2006.
- J. Kong, K. Zhang, J. Dong, and D. Xu, “Specifying behavioral semantics of UML diagrams through graph transformations,” Journal of Systems and Software, Vol. 82, No. 2, pp. 292–306, April 2009.
- C. Attiogbe, P. Poizat, and G. Salaun, “A formal and tool-equipped approach for the integration of state diagrams and formal datatypes,” IEEE Transactions on Software Engineering, Vol. 33, No. 3, pp. 157–170, March 2007.
- M. Hinchey, M. Jackson, and P. Cousot, J. P. Bowen, and T. Margeria, “Software engineering and formal methods,” Communications of the ACM, Vol. 51, No. 9, pp. 54–59, September 2008.
- G. Kotonya and I. Sommerville, “Requirements engineer- ing with viewpoints,” Software Engineering Journal, Vol. 11, No. 1, pp. 5–18, January 1996.
- A. Sutcliffe, “Scenario-based requirements engineering,” in Proceedings of the 11th IEEE International Conference on Requirements Engineering, Monterey, California, pp. 320–329, September 2003.
- A. Isazadeh, D. A. Lamb, and G. H. MacEwen, “View- charts: A behavioral specification language for complex systems,” Proceedings of the 4th International Workshop on Parallel and Distributed Real-Time Systems, Honolulu, Hawaii, pp. 208–215, April 1996.
- A. Isazadeh and J. Karimpour, “Viewcharts: Syntax and semantic,” Informatica, Vol. 19, No. 3, pp. 345–362, March 2008.
- A. E. Ansary, “Requirements definition of real-time system using the Behavioral Patterns Analysis (BPA) approach: The elevator control system,” Proceedings of the Second International Conference on Software and Data Technologies, Barcelona, pp. 371–377, July 2007.