UML Requirements for Distributed Software Architectures (original) (raw)

Using UML to Model Distributed System Architectures

Computer Applications in Industry and Engineering, 2005

Distributed system configuration is a complex process, since it involves solving interrelated issues, corresponding to different configuration stages usually supported by automated or semiautomated independent tools. A common model for distributed system representation in all configuration stages enables the identification of unclear application specific dependencies between discrete stages. It should also be easily realized in various software tools used to automate discrete configuration stages and facilitate the designer to efficiently provide system specifications. We propose to use UML to model all aspects of distributed system configuration process by extending and integrating different diagram types. Alternative views of the system emphasizing specific configuration stages are offered through the realization of extended UML diagrams. Rational Rose software platform is used for implementation purposes.

Modeling Software Architecture with UML

2015

Abstract: Software Architecture is being widely used today to describe a very high level design methodology of large & heterogeneous software systems. A good Architectural representation scheme holds the key to the effectiveness of a Software architecture description and usage. In this paper, we look at UML (unified modeling language) as a prospect for a generalized architecture description language. UML also “unifies " the design principles of each of the object oriented methodologies into a single, standard, language that can be easily applied across the board for all object-oriented systems and a scheme AND-OR DFD method is introduced and developed.

An approach to software architecture description using UML

2004

This document presents a practical way of describing software architectures using the Unified Modeling Language. The approach is based on a "3+1" structure in which three viewpoints on the described system are used -module, component & connector, and allocation -are used to describe a solution for a set of architectural requirements.

UML ( Unified Modeling Language ) : Standard Language for Software Architecture Development

2011

A solid architectural vision is a key discriminator in the success or failure of a software project. This paper discusses how to describe architecture through a set of design viewpoints and how to express these views in the UML. In this paper we mainly focused on the standardization of UML for software development process with the discussion of benefits of UML. Object-oriented analysis (OOA) is concerned with developing software engineering requirements and specifications that expressed as a system's object model (which is composed of a population of interacting objects), as opposed to the traditional data or functional views of systems. The goal of this paper is to combine the respective strengths of powerful, specialized (architectural-based) modeling approach (UML) with a widely used general (design-based) approach. Also some weaknesses have been discussed so that existing modeling can be optimized for better architecture development.

Towards an UML Profile for the Description of Software Architecture

Existing ADLs (architecture description languages) have an advantage of formally specifying the architecture of component-based systems. But ADLs have not come into extensive use in industries since ADL users should learn a distinct notation specific to architecture, and ADLs do not address all stakes of development process that is becoming diversified everyday. On the other hand, UML is a de facto standard general modeling language for software developments as UML provides a consistent notation and various supporting tools during the whole software development cycle. A number of researches on architecture modeling based on UML have been progressed. In particular, many research results have been introduced that specialize UML by its extension mechanism in order to explicitly represent core architecture concepts that UML does not fully support. In this paper, we examine architecture modeling elements that can be represented in UML2.0 and discuss how to extend and specialize UML2.0 in order to make it more suitable for representing architectures.

Towards a software architecture specification language based on UML and OCL

2001

The development of a system's software architecture is a very complex and important issue. Existing description and modeling techniques do not fit the requirements of architecture centric system development. In this paper we are proposing the basic concepts and notions of software architectures. Furthermore, we provide a proposal for a new description and modeling technique for software architectures based on UML and OCL.

A UML-based Approach for Multi-scale Software Architectures

Proceedings of the 17th International Conference on Enterprise Information Systems, 2015

Multi-level software architecture design is an important issue in software engineering. Several research studies have been done on the modeling of multi-level architectures based on UML. However, they neither included the refinement between the levels nor clarified the relationships between them. In this paper, we propose a multiscale modeling approach for multi-level software architecture oriented to facilitate adaptability management. The proposed design approach is founded on UML notations and uses component diagrams. The diagrams are submitted to vertical and horizontal transformations for refinement; this is done to reach a fine-grain description that contains necessary details that characterize the architectural style. The intermediate models provide a description with a given abstraction that allow the validation to be conducted significantly while remaining tractable w.r.t. complexity. The validation scope can involve intrinsic properties ensuring the model correctness w.r.t. the UML specification. To achieve this, we propose a set of model refinement rules. The rules manage the refinement and abstraction process (vertical and horizontal) as a model transformation from a coarse-grain description to a fine-grain description. Finally, we experimented our approach by modeling an Emergency Response and Crisis Management System (ERCMS) as a case of study.

Bridging the gap between IEEE 1471, an architecture description language, and UML

Software and Systems Modeling, 2002

A lot of attention has been paid to software architecture issues in both the software engineering research community and standardization organizations working in the software area. On one hand, IEEE 1471 makes a clear distinction between the architecture and the architectural description of a software system. The software architecture research community, on the other hand, has focused on the creation and improvement of special-purpose languages, architecture description languages (ADLs). ADLs have the advantage of being mathematically founded, facilitating analysis of architectural models, but they have also the disadvantage of lacking adequate support for separating various kinds of stakeholders' concerns along different viewpoints. ADLs do not address the clear difference between software architecture and its representations, as does the IEEE 1471. To help improve the situation, we propose a UML-based approach to software architecture that instantiates the conceptual framework defined in IEEE 1471 and complements the abstractions and mechanisms found in current ADLs. In this paper, we introduce the ConcernBASE approach to software architecture description and discuss how to integrate it with SADL, a particular ADL. We validate the mapping in ConcernBASE Modeler, a UML-based tool prototype, by integrating SADL tools.

UML as an Architecture Description Language

2000

Architecture Description Languages (ADLs) are specialized formal languages supporting modeling and reasoning on software architectures. Although number of ADLs counts in the tens, their popularity and usage by practitioners is very low. The object- oriented Unified Modeling Language (UML), which has become the OMG standard, offers a great variety of concepts for the definition of the structure and the expected

A UML Profile to Support the Formal Presentation of Software Architecture

International Computer Software and Applications Conference, 2002

We present a UML profile that accommodates the specialized dynamic models that support the Oikos_adtl approach to software architecture. The profile reflects some core modeling Oikos_adtl concepts in the UML framework. We propose the related notations and diagrams, which map into the new models. Since we rely on the standard UML extension mechanisms, we are also setting the requirements for