Modeling and Analysis of Complex System with UML: A Case Study

Abstract:

The Unified Modeling Language - UML - is the most used specification language, and the way the world models not only application structure, behavior, and architecture, but also business process and data structure. In this paper, we aim to demonstrate a system development methodology by generating the UML diagrams from the requirements of the Automatic Banking Machine (ABM) System and discuss their relationships, differences and suitability. The high-level requirements of the system are specified by using use-case diagram, activity diagram, state chart diagram, collaboration diagram, sequence diagram, and component diagram, and the low-level requirements of each component using class diagrams. We briefly introduce each diagram, their usage, their advantages and some limitations, and then we discuss the relationships and differences between two or more diagrams, and suitability for modeling the different parts of the system.

• Periodical: Applied Mechanics and Materials (Volumes 513-517)
• Pages: 1346-1351
• DOI: https://doi.org/10.4028/www.scientific.net/AMM.513-517.1346
• Online since: February 2014
• Authors: Munina Yusufu*, Hai Jun Zhang, Gulina Yusufu, Zhan Dong Liu, Pen Cheng, Dilidaer Dilisati
• Keywords: Class Diagram Component, High-Level Requirements, UML Diagrams, Unified Modeling Language (UML)

References

[1] M. Satpathy, R. Harrison, C. Snook, and M. Butler, A Comparative Study of Formal and Informal Specifications through an Industrial Case Study, " Proc. IEEE/ IFIP Workshop on Formal Specification of Computer Based Systems (FSCBS, 01), (2001).

[2] M. Ardis, J. Chaves, L. Jagadeesan, P. Mataga, C. Puchol, M. Staskauskas, and J. Olnhausen, A Framework for Evaluating Specification Methods for Reactive Systems, IEEE Transactionson Software Engineering, 1996, 22(6), p.378–389.

DOI: 10.1109/32.508312

[3] M. Frappier and H. Habrias, Software Specification Methods: An Overview Using a Case Study, Springer, (2001).

[4] Munina Yusufu and Gulina Yusufu, Comparison of Software Specification Methods using a Case Study, Proc. International Conference on Computer Science and Software Engineering (CSSE2008), 2008, p.784–787.

DOI: 10.1109/csse.2008.1493

[5] Munina Yusufu and Gulina Yusufu, Comparative Study of Formal Specifications through a Case Study, Proc. 2012 IEEE International Conference on Information Science and Technology, 2012, p.318–321.

DOI: 10.1109/icist.2012.6221659

[6] Ian Sommerville, Software Engineering, Addison-Wesley, 2001, 6th edition.

[7] G. Sindre and A.L. Ophad, Eliciting Security Requirements by Misuse Cases, Requirements Engineering, 2005, 45, p.34–44.

DOI: 10.1007/s00766-004-0194-4

[8] Donald G. Firesmith, Security Use Cases, Journal of Object Technology, 2003, 2(3), p.53–64.

[9] Joshua J. Pauli and Dianxiang Xu, Misuse Case-based Design and Analysis of Secure Software Architecture, Proc. International Conference on Information Technology, 2005, p.398–403.

DOI: 10.1109/itcc.2005.199

[10] Sutherland, Developing Complex Systems using DOORS and UML, Proc. Telelogic 2004 User Group Conference – Americas and Asia/Pacific, (2004).