On Foundation for Certification of Model Driven Architecture (MDA) Tools: Defining a Specification
A modern approach to software development includes a wide variety of processes, which are used to regulate and manage the entire development life cycle. One of the main aspects to be considered during the preparation stage of software development is the selection of the right tools. Nowadays when software systems become more and more complex, an inappropriate selection of the tools may cause project not to succeed at all. That is why the main challenge of the industry is still aimed on the simplification, optimization, and automation of software development process. One of the ways to deal with an increasing complexity, as well as not to dig into the details of the source code, is to use modeling. A model-driven approach, mainly represented by OMG's Model Driven Architecture as the most advanced and popular one, purports to be the next evolutional milestone for the whole software industry. In fact, most of the tools currently available on the market are claimed as "MDA complaint," though have never been checked or analyzed for that compliance. Therefore, there should be a certification program defined to figure out the main features of each tool in accordance with OMG standards. The original article proposes a foundation for certification of MDA tools. In particular, this includes the specification of the most common features and options defined to clarify the accordance level of each tool from various perspectives.
Role of UML Class Diagram in Object-Oriented Software Development
UML is an industrial standard for object-oriented software specification which offers a notation for class modeling during object oriented software development. Since the UML class diagram is a so-called "bridge" between software specification at the user side and software realization at the developer side, it requires strong guidelines for identification of class objects from the problem domain and notational conventions for modeling of the class diagram for its further usage in system coding. This paper presents a discussion on problematic stages and possible element transformations into software components. Several conclusions are drawn on potential usage of the class diagram in industry.