[서평]「The Unified Modeling Language User Guide」

The Object Management Group's (OMG) Model Driven Architecture (MDA) strategy envisages a world where models play a more direct role in software production, being amenable to manipulation and transformation by machine. Model Driven Engineering (MDE) is wider in scope than MDA. MDE combines process and analysis with architecture. This article sets out a framework for model driven engineering, which can be used as a point of reference for activity in this area. It proposes an organisation of the modelling 'space' and how to locate models in that space. It discusses different kinds of mappings between models. It explains why process and architecture are tightly connected. It discusses the importance and nature of tools. It identifies the need for defining families of languages and transformations, and for developing techniques for generating/configuring tools from such definitions. It concludes with a call to align metamodelling with formal language engineering techniques.

Model Driven Engineering

Thank you for reading software product line engineering foundations principles and techniques. Maybe you have knowledge that, people have look numerous times for their favorite books like this software product line engineering foundations principles and techniques, but end up in malicious downloads. Rather than reading a good book with a cup of coffee in the afternoon, instead they are facing with some infectious bugs inside their desktop computer.

Software Product Line Engineering Foundations Principles And Techniques

The authors design and demonstrate a process for carrying out design science (DS) research in information systems and demonstrate use of the process to conduct research in two case studies. Several IS researchers have pioneered the acceptance of DS research in IS, but in the last 15 years little DS research has been done within the discipline. The lack of a generally accepted process for DS research in IS may have contributed to this problem. We sought to design a design science research process (DSRP) model that would meet three objectives: it would be consistent with prior literature, it would provide a nominal process model for doing DS research, and it would provide a mental model for presenting and appreciating DS research in IS. The process includes six steps: problem identification and motivation, objectives for a solution, design and development, evaluation, and communication. We demonstrated the process by using it in this study and by presenting two case studies, one in IS planning to develop application ideas for mobile financial services and another in requirements engineering to specify feature requirements for a self service advertising design and sales system intended for wide audience end users. The process effectively satisfies the three objectives and has the potential to help aid the acceptance of DS research in the IS discipline.

The Design Science Research Process: A Model for Producing and Presenting Information Systems Research

Autonomous Agents and Multi-Agent Systems www.springer.com/10458 Michael Luck and Carles Sierra, Editors-in-Chief Published by Springer. About this Issue Learning is a critical component for autonomous agents so that they can discover novel behaviors, adapt to a nonstationary world, and handle unanticipated events. As virtual and physical agents become more common, these learning agents need to handle interactions not only with an environment, but also with other agents. Multiagent learning thus becomes an indispensable component of building intelligent systems, even though much of the current learning research focuses on single-agent settings.

Autonomous Agents and Multi-Agent Systems

The main concern of this paper is measuring the quality of the architectural design. The goal of this work is to use the architectural design process proposed in the unified process framework, adapting and detailing it to include the quality requirements specification at architectural level. There is general agreement on the fact that in modern applications the selection of the architecture must be addressed early in the development process, to mitigate risks. Moreover, the integration of enterprise applications is a component-based development requiring quality values associated to the services offered by the components. The services depend mostly on the architecture. In consequence, methods arise for guiding the selection or for constructing software architectures. Our approach allows associating the quality requirements (nonfunctional properties) for the architecture expressed using the ISO 9126-1 standard quality model, with the use cases, to facilitate the selection of the “key” use cases. Measures for the architecture's quality characteristics are specified in details, precising attributes, units, numerical systems and scale types. A case study of a real-time application for monitoring stock exchanges illustrates our approach. We hope that our results will be particularly useful for practitioners, such as software architects, analysts and designers.

ISO quality standards for measuring architectures

A specification pattern for use cases

Great interest in model-driven approaches that are based on the automatic transformation of models has emerged. In this software development paradigm, the models and their transformations are specified at a high abstraction level supporting evolution, refinement and code generation. One of the benefits that these approaches try to achieve is improving the software quality through the reusability of well proven patterns. In order to achieve this goal, this paper presents an approach that defines patterns to transform use case models into interaction models. This approach uses roles to capture the linguistic abstractions on the use case text as well as to describe the corresponding interaction. The roles are defined as model elements to guarantee genericity. In this way, the transformation patterns are independent of a specific domain or a technological platform. The defined patterns have been validated. Some of the validation results are also presented in this paper.

Modeling interactions using role-driven patterns

Object-oriented analysis and design have been more concerned with system functionality, neglecting non-functional aspects; the result is code which is tangled and dicult to maintain, contradicting main principles of object orientation. Aspect Oriented Software Development (AOSD) proposes the early specification of non-functional requirements. However, a standard and homogenous vision of the AOSD terminology is still missing. The goal of this work is to integrate AOSD concepts, classic requirements engineering notions, and the new standard ISO/IEC 25030 on software quality requirements.The main result of this study is the REASQ (REquirements, Aspects and Software Quality) conceptual model, expressed in UML. All the modelling concepts are formalized into three related ontologies, representing the ambits of aspect-orientation, software quality and requirements engineering. The ontologies can be used as an umbrella to specify quality requirements in aspect-oriented engineering processes.

http://www.jot.fm/issues/issue_2010_07/article4.pdf

Alfredo Matteo

Papers

ISO quality standards for measuring architectures

ISO quality standards for measuring architectures

A specification pattern for use cases

Modeling interactions using role-driven patterns

REquirements, Aspects and Software Quality: the REASQ model