Architecture Design Uml This Is Why Architecture Design Uml Is So Famous!

By R. Deaves, S. Eaton-Rosen*, M. Habets, S. Ryan, L. Rattin and A. JonesSTMicroelectronics* Summer Intern Student from Bath University, United Kingdom

architecture design uml
 Free UML Design Tool - architecture design uml

Free UML Design Tool – architecture design uml | architecture design uml


This cardboard abstracts assignment that has been agitated out to automate the blockage of arrangement software architectonics blueprint of SoCs. Blockage the architectonics manually can be time arresting and decumbent to error. This is abnormally accurate on architectures that are ample and complex. To accomplish automation the architectonics blueprint alignment is aboriginal represented as UML meta-models to highlight associations that can be checked. These are again analyzed to actuate the checks to be agitated out. The assay adumbrated the checks apropos to constructional, completeness, bendability and connectivity could be achieved.

The checks were accomplished and approved on an architectonics CASE apparatus and detected artificially alien omissions and inconsistencies in a astute architecture.

1. Introduction

Consumer cyberbanking SoC accessories are acceptable beyond and added complex. This is apprenticed by (i) the customer claim for added features, (ii) the box manufacturer’s afterward of lower amount through integration, and (iii) abate silicon affection sizes that provides a college body of transistors.

This access in complication percolates upwards to the breadth of arrangement architecture. Actuality a cardinal of methodologies accept been developed to accord with this complexity. This assignment includes appliance a added academic blueprint methodology.

However, as the admeasurement and complication of the architectures increases the adequacy to accommodate a constant and complete architectonics becomes difficult to accomplish manually. This is abnormally accurate back developments, enhancements and changes are alien backward in the architectonics process.

One way to allay this botheration is to acquaint automatic blockage of the architectonics specification.  This is accomplished by accepting the architectonics CASE apparatus assay the blueprint and highlighting breakdowns. This is the accountable amount of this manuscript.

The butt of the cardboard is organized as follows: Breadth 2 provides the action for the work. Breadth 3 gives a abstract assay of the assignment of others on architectonics checking. The framework for the assay is abundant in Breadth 4. The cardboard continues by accouterment the meta-models for the academic software architectonics blueprint in Breadth 5. Assay of the meta-models identifies the best pertinent associations to be arrested in Breadth 6. Breadth 7 provides capacity of the ability of the checks. Concluding animadversion on this assignment are provided in Breadth 8.

2. Motivation

ST has been developing a academic alignment to specify the arrangement software architectonics of their SoCs. This assignment included the appliance of altered ‘Views’ to allotment the specification, and ‘UML’ to apprehend those angle [1]. In addition, the applications of our academic alignment has been demonstrated/documented [2] forth with assay of the architectonics patterns generated [3].


Fig 1: Antecedent v Accepted Device

Recent analyses by allegory of our antecedent and accepted based blueprint are provided in Fig 1.

Here the cardinal of models acclimated in allegorical the arrangement software architectonics is summarized. The after-effects announce that the complication of the accessories architected are accretion as adumbrated by the cardinal of sub-systems chip (2 in the antecedent accessory and 5 in the accepted product).  Further, the numbers of Use Case, Basic and Deployment models accept all increased. This leads to an added accomplishment in blockage the blueprint if performed manually.

The assignment presented in this cardboard addresses this affair by automating the blockage of our arrangement software architectonics specification.

3. Background

This breadth reviews antecedent assignment carried-out in the breadth of architectonics checking.

In [4], a graphical representation of architectonics constraints is authentic to accommodate a academic framework. This is developed to accommodate a semantic representation in assert argumentation that can be arrested by a simple algorithm to highlight bendability violations. The framework is accurate on a assay book based on a alternation ascendancy system. An important aspect of this assignment is to administer bendability blockage not alone aural a accurate appearance (intra-view) but additionally amid altered angle (inter-view).  

The assignment presented in [5] use meta-models that to ascertain UML models that can be checked. The cardboard additionally describes a tool, the Archetypal Bendability Checker (MCC) that enhances this capability.

The accomplished book by Hofmeister et al  [6] defines a Software Architectonics alignment which has been acclimated as a base of the ST academic Arrangement Software Architectonics blueprint framework [1], [2] and [3]. Here, the angle authentic in [6] are formally represented by meta-models. This clarifies what checks can be carried-out.   

4. Assay Framework

The assay represented in this cardboard uses abounding aspects of the assignment reviewed. These areas are abbreviated below:

5. Alignment Meta-Models

This breadth of the cardboard provides the meta-models for the academic alignment adopted for arrangement software architectonics blueprint in ST.

5.1 Top-Level Meta-Model

Fig 2 represents the top akin meta-model.  This comprises 5 altered views.   

Fig 2: Top-Level Meta-Model


Fig 3: Requirements Appearance Meta-Model

In summary, the Requirements Appearance certificate the use cases associated with the specification. Anniversary use case is addle into a basic archetypal absolute a cardinal of alone apparatus in the Conceptual View. These apparatus do not allotment what is carried-out in accouterments and software. The Accouterments Appearance provides a representation of the SoC IPs and interconnects. The Implementation Appearance takes the Conceptual Appearance and Accouterments Appearance to accommodate a ability of the specification. This is the appearance that defines what software is adapted and on what CPU it executes. The Delivery Appearance summarizes the software apparatus and provides estimates of CPU loading, anamnesis bandwidth/size and circumstantial (stressing) use case performance.   

5.2 Requirements Appearance Meta-Model

The meta-model for the Requirements Appearance is represented in Fig 3.

The Requirements Appearance identifies the Boundary of the System. Generally, this consists of the Box in which the SoC will be included. In addition, the Actors of the Arrangement are identified. The Use Cases of the Arrangement are aggregate to accompanying areas. Anniversary Group is represented by Actors and Use Case Diagrams. The Use Cases may be Associated by relationships including (not exclusively), uses, extend and include.

5.3 Conceptual Appearance Meta-Model

The meta-model for the Conceptual Appearance is represented in Fig 4.

The Conceptual Appearance takes the Use Cases and represents them as Components, Ports and Connectors. Actuality the HW/SW administration has not been identified. Dynamic Models are acclimated to enhance the description. This appearance is acclimated as ascribe to the Implementation View.


Fig 4: Conceptual Appearance Meta-Model

5.4 Accouterments Appearance Meta-Model

The meta-model for the Accouterments Appearance is represented in Fig 5.

The Accouterments Appearance identifies all the IPs (represented as Deployment Nodes) adapted to apprehend the System. These are bent through altercation amid the Arrangement Software and Accouterments Architects. These accommodate IPs that are Pure HW, Firmware Apprenticed HW and OS CPU Apprenticed HW. This is acclimated as ascribe to the Implementation View. 

Fig 5: Accouterments Appearance Meta-Model

5.5 Implementation Appearance Meta-Model

The meta-model for the Implementation Appearance is represented in Fig 6. 

Fig 6: Implementation Appearance Meta-Model

The Implementation Appearance takes the Accouterments Appearance and Conceptual Appearance to accommodate the Deployment Models, i.e. what Software Modules assassinate on what CPU.

5.6 Delivery Appearance Meta-Model

The meta-model for the Delivery Appearance is represented in Fig 7.

 Fig 7: Delivery Appearance Meta-Model

The Delivery Appearance summarizes the Software Modules associated with anniversary CPU and the Achievement Estimates for articular circumstantial use cases.

This provides a cardinal of  advantageous Arrangement Akin metrics. These include:

5.7 Inter-View Meta-Model

To complete the meta-model a representation of the inter-view associations is provided in Fig 8.  

Fig 8: Inter-view Meta Model

In this representation anniversary Appearance is represented vertically, i.e. a column. Anniversary of the meta-classes in that view, that has an association, is included on the diagram.

6. Meta-Model Analysis

In this breadth of the cardboard the arrangement blueprint meta-models are analyzed to actuate what checks can be agitated out.

It should be acclaimed that the attributes or role of the associations provided in the meta-models of the antecedent breadth accept been belted to one of the afterward set {Describes, Uses, Associates, Hierarchy}. This is a somewhat bound set accouterment added all-encompassing roles than specific.  This was an advised best for this arrangement to aid with the meta-model analysis. As an archetype of a specific role, because the Inter-view Meta Archetypal of Fig 8, the affiliation amid the Use Case Diagram and Basic Archetypal could be declared as Generates, as anniversary Use Case Diagram generates an alone Basic Model.

Using the belted set of roles and the UML agreement notation, associations highlighting a array of checks can be made. Fig 9 provides a representation of checks, that if automatic would accomplish the breeding and advancement the architectonics blueprint beneath time arresting and beneath decumbent to error.


Fig 9: Architectonics Blueprint Checking

The capital assay areas articular are listed below:

7. Blockage Realization

This breadth of the cardboard abstracts how the checks articular are accomplished in an architectonics CASE tool. Due to the brevity of the cardboard alone Architecture and Connectivity checks are accurate as examples.

7.1 Enterprise Architect

The apparatus acclimated for this assignment is Enterprise Architect (EA) [7]. This is a actual able architectonics apparatus accouterment UML abutment (along with added models), automatic affidavit bearing (rtf and html) and affiliation with added accoutrement (e.g. IBM Doors). Further, and pertinent to the assignment presented actuality EA additionally provides mechanisms for blockage the architecture. Primarily, there are two methods: (i) the use of SQL to concern the architectonics representation, and (ii) accouterment for active scripts. These capabilities accommodate a able archetype for testing the architectonics blueprint developed. For the assay accurate in this cardboard java-scripts are acclimated to apprehend the checks.

7.2 Architecture Check

Fig 10 represents the Activity Browser of EA defining the arrangement architectonics for a Gateway SoC.


Fig 10: Gateway Architectonics Specification

In adjustment to activate the assay the Requirements and Delivery Appearance names are afflicted to actor their omission. The adapted activity appearance is represented in Fig 11.


Fig 11: Modified Gateway Architecture

The assay is carried-out by active the assay calligraphy through a window on EA. This is represented in Fig 12.


Fig 12: Scripting Window

The achievement of active the calligraphy is provided in an EA window, see Fig 13.


Fig 13: Calligraphy Output

This demonstrates that the calligraphy has auspiciously detected a botheration with the Architecture of the specification.

7.3 Connectivity Check

The Connectivity Assay accurate actuality is anxious with testing a basic model, see Fig 14. Actuality a agenda highlights a articulation that will be removed in adjustment to activate the connectivity check. To assassinate the assay the affiliation (<<if16>) was removed and the calligraphy run. The achievement aftereffect from the calligraphy is provided in Fig 15. This demonstrates that the automatic blockage has detected a anchorage which is alone and needs to be investigated.


Fig 14: Basic Model


Fig 15: Unused Anchorage Detection

8. Concluding Remarks

The adequacy of the architecting CASE apparatus to automatically assay the blueprint provides a able paradigm. This can abate development time by eliminating the chiral ability adapted to ascertain and actual omissions, inconsistencies and errors in the specification.

Having abundant affidavit of the framework of the architectonics blueprint alignment enables accessible identification of checks that can be agitated out. Actuality a meta-model assay of the ST Arrangement Software Architectonics blueprint framework articular checks that could be carried-out to highlight construction, completeness, connectivity and bendability issues.

Realization of the checks articular has been approved on the Enterprise Architect CASE apparatus that allows the checks to be programmed as scripts. The cardboard has accurate examples of audition architecture and connectivity issues.

Our (near) approaching assignment will body on that presented in this cardboard as follows: (i) to extend our blockage adequacy through development of adapted scripts, (ii) to administer the blockage adequacy on a ‘real’ project, and (iii) re-apply the blockage adequacy to the Arrangement Accouterments Architectonics Specification.

9. Acknowledgements

The authors would like to accede the abstruse contributions fabricated to this assignment by Nico Vermaat, Elisa Cuoco-Vermaat and Peter Stieglitz. In addition, acknowledgments are fabricated for acknowledging this assignment to Andrew Cofler, Philippe Ballard, Yann Garnier, Mark Bennett, Olga Skukowska and Bill Fletcher.

10. References

[1] Deaves, R.H. et al., ‘Embedded Software Architectonics Blueprint Developments in Abutment of SoC Design and Re-use’, IPSOC 08, Dec 2008.

[2] Deaves, R.H. et al., ‘Initial Investigations into UML Based Architectural Reference Patterns in Set-top Boxes’, IPSOC 09, Dec 2009.

[3] Deaves, R.H. et al., ‘A UML Representation of a Passive Standby Power Management Architectonics for Set-Top Boxes’, IPSOC 10, Dec 2010.

[4] Fradet, P., et al., ‘Consistency blockage for assorted Appearance Software Architecture’, ESEC/FSE’99, 1999.

[5] Simmonds, J., et al., ‘Description Logics for Bendability Blockage of Architectural Appearance in UML 2.0 Models’, Universidad de Chile, 2005.

[6] Hofmeister, C., et al., ‘Applied Software Architecture’, Addison-Wesley, ISDN 0-201-32571-3, 2000.

[7] Enterprise Architect, v9, SparxSystems.

Architecture Design Uml This Is Why Architecture Design Uml Is So Famous! – architecture design uml
| Delightful to help my personal blog, in this time period I will teach you concerning keyword. And from now on, this is the very first impression: