Computation independent representation of the problem domain in MDA

• Autorzy: Osis J. , Asnina E. , Grave A.
• Języki publikacji: EN

Abstrakty

EN

The object-oriented analysis suggests semiformal use-case driven techniques for problem domain modeling from a computation independent viewpoint. The proposed approach called Topological Functioning Modeling for Model Driven Architecture (TFMfMDA) increases the degree of formalization. It uses formal mathematical foundations of Topological Functioning Model (TFM). TFMfMDA introduces more formal analysis of the problem domain, enables defning what the client needs, verifying textual functional requirements, and checking missing requirements in conformity with the domain model. A use case model of the application to be build is defned from the TFM using a goal-based method. Graph transformation from the TFM to a conceptual model enables defnition of domain concepts and their interrelation. This paper also outlines requirements to the tool to support TFMfMDA.

Słowa kluczowe

EN

object-oriented analysis; Topological Functioning Modeling (TFM); MDA

• Wydawca: Oficyna Wydawnicza Politechniki Wrocławskiej
• Czasopismo: e-Informatica Software Engineering Journal
• Rocznik: 2008
• Tom: Vol. 2, nr 1
• Strony: 25--40
• Opis fizyczny: Bibliogr. 24 poz.

Twórcy

autor

Osis J.

autor

Asnina E.

autor

Grave A.

• Faculty of Computer Science and Information Technology, Institute of Applied Computer Systems, Riga Technical University

Bibliografia

• [1] A proposal for an MDA foundation model. ORMSC White Paper ormsc/05-04-01, OMG, www.omg.org/docs/ormsc/05-04-01.pdf, Apr 2005. V00-02.
• [2] J. Arlow and I. Neustadt. UML2 and the Unifed Process: Practical Object-Oriented Analysis and Design. Addison-Wesley, Pearson Education, second edition, 2005.
• [3] E. Asnina. Formalization aspects of problem domain modeling within model driven architecture. In O. Vasilecas, editor, Databases and Information Systems. 7th International Baltic Conference on Databases and Information Systems. Communications, Materials of Doctoral Consortium, pages 93{104, Vilnius, Lithuania, 2006. Vilnius Gediminas Technical University, Technika.
• [4] E. Asnina. Formalization of Problem Domain Modeling within Model Driven Architecture.PhD thesis, Riga Technical University, RTU Publishing House, Riga, Latvia, 2006.46 Janis Osis, Erika Asnina, Andrejs Grave
• [5] W. F. Basener. Topology and Its Applications. John Wiley and Sons, Inc., New Jersey, USA,2006. p. 339.
• [6] A. Cockburn. Structuring use cases with goals. http://alistair.cockburn.us/crystal/articles/sucwg/.
• [7] A. Dardenne, A. van Lamsweerde, and S. Fickas. Goal-directed requirements acquisition. The Science of Computer Programming, 20(November):3{50, 1993.
• [8] Z. Diskin, B. Kadish, F. Piessens, and M. Johnson. Universal arrow foundations for visual modeling. In Proc. Diagramms'2000: 1st Int. Conference on the theory and application of diagrams, pages 345{360. Springer LNAI, 2000. No. 1889.
• [9] Eclipse. Eclipse - an open development platform. http://www.eclipse.org.
• [10] S. Ferg. What's wrong with use cases? http://www.ferg.org/papers/, Feb 2003.
• [11] D. Firesmith. Use cases: the pros and cons. http://www.ksc.com/article7.htm.
• [12] D. Frankel. Model Driven Architecture : Applying MDA to Enterprise Computing. Wiley Publishing, Inc., Indiana, 2003.
• [13] T. Gorschek and C. Wohlin. Requirements abstraction model. Requirements Engineering, 11:79{101, 2006.
• [14] M. Jackson. The real world. http://www.ferg.org/papers/, Jul 2003.
• [15] M. Jackson. Problem frames and software engineering. Information and Software Technology,47(November):903{912, 2005.
• [16] I. Jacobson, M. Christerson, P. Jonsson, and G. Overgaard. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, 1992.
• [17] C. Larman. Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development. Prentice Hall PTR, 3rd edition, 2005.
• [18] D. Lefngwell and D. Widrig. Managing Software Requirements: a use case approach.Addison-Wesley, 2nd edition, 2003.
• [19] OMG, http://www.omg.org/. MDA Guide Version 1.0.1, Jun 2003.
• [20] J. Osis. Extension of software development process for mechatronic and embedded systems.In Proceeding of the 32nd International Conference on Computer and Industrial Engineering,pages 305{310. University of Limerick, Limerick, Ireland, Aug 2003.
• [21] J. Osis. Software development with topological model in the framework of MDA . In Proceedings of the 9th CaiSE/IFIP8.1/EUNO International Workshop on Evaluation of Modeling Methods in Systems Analysis and Design (EMMSAD'2004) in connection with the CaiSE'2004, Vol. 1, pages 211{220, Riga, Latvia, 2004. Riga Technical University, RTU.
• [22] J. Osis. Formal computation independent model within the MDA life cycle. In International Transactions on Systems Science and Applications, pages 159{166. Xiaglow Institute Ltd,Glasgow, UK, 2006. ISSN 1751-1461, V. 1, Nr. 2.
• [23] H. Podeswa. UML for the IT Business Analyst: A practical Guide to Object-Oriented Requirements Gathering. Thomson Course Technology PTR, Boston, 2005.
• [24] E. S. Yu. Towards modelling and reasoning support for early-phase requirements engineering. In International Symposium on Requirements Engineering, pages 226{235, Annapolis,Maryland, 1997.