The Past, Present, and Future for Software Architecture

Kruchten, Philippe; Obbink, Henk; Stafford, Judith A.

doi:10.1109/ms.2006.59

Cited by 179 publications

(107 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Software Architecture. Software architecture involves the structure and organization by which modern system components and subsystems interact to form systems; and the properties of systems that can be better designed and analysed at system level (Kruchten et al, 2006). Component-Based Development (CBD).…”

Section: The Foundationsmentioning

confidence: 99%

A Domain Engineering Process for RFID Systems Development in Supply Chain

Campos¹,

Almeida²,

Zorzo³

et al. 2009

Supply Chain the Way to Flat Organisation

View full text Add to dashboard Cite

Section: The Foundationsmentioning

confidence: 99%

A Domain Engineering Process for RFID Systems Development in Supply Chain

Campos¹,

Almeida²,

Zorzo³

et al. 2009

Supply Chain the Way to Flat Organisation

View full text Add to dashboard Cite

“…Despite these benefits, and although ADLs have received much attention from the architecture research community, they have not been applied much in industry [11].…”

Section: Software Architecturementioning

confidence: 99%

Visualisation of Domain-Specific Modelling Languages Using UML

Graaf

Deursen

2007

14th Annual IEEE International Conference and Workshops on the Engineering of Computer-Based Systems (ECBS'07)

View full text Add to dashboard Cite

Currently, general-purpose modelling tools are often only used to draw diagrams for the documentation. The introduction of model-driven software development approaches involves the definition of domain-specific modelling languages that allow code generation. Although graphical representations of the involved models are important for documentation, the development of required visualisations and editors is cumbersome. In this paper we propose to extend the typical model-driven approach with the automatic generation of diagrams for documentation. We illustrate the approach using the Model Driven Architecture in the domains of software architecture and control systems.

show abstract

“…Software Architecture design artifacts were posited in software development methodologies to cope with the increasing complexity of large-scale software design [6,7]. Given that Software Architecture artifacts are concerned with high-level system structures and system properties [8], Software Architecture artifacts determine the overall quality and performance of software products [9,10,5]. A Software Architecture design artifact is expected to be elaborated during the Design activity in a software engineering process (SEP).…”

Section: Introductionmentioning

confidence: 99%

The strengths and weaknesses of software architecture design in the RUP, MSF, MBASE and RUP-SOA methodologies: A conceptual review

Reyes-Delgado¹,

Mora

Durán-Limón

et al. 2016

Computer Standards & Interfaces

View full text Add to dashboard Cite

The importance of Software Architecture design has been acknowledged as a very important factor for a high-quality software development. Different efforts in both industry and academia have produced multiple system development methodologies (SDMs) that include SA design activities. In addition, standardization bodies have defined different recommendations regarding Software Architecture design. However, in industry Software Architecture best practices are currently poorly employed. This fact constrains the benefits that industry can potentially obtain from Software Architecture design in software development. In this paper, we analyze the degree to which the four main recognized SDMs -RUP (Rational Unified Process), MSF (Microsoft Solutions Framework), MBASE (Model-Based System Architecting and Software Engineering), and RUP-SOA (Rational Unified Process for Service-oriented Architecture) -adhere to the best practices of Software Architecture design. Our analysis points out some of the most important strengths and weakness regarding Software Architecture design and highlights some of the most relevant issues of Software Architecture design that need to be incorporated into such methodologies.

show abstract

The Past, Present, and Future for Software Architecture

Cited by 179 publications

References 15 publications

A Domain Engineering Process for RFID Systems Development in Supply Chain

A Domain Engineering Process for RFID Systems Development in Supply Chain

Visualisation of Domain-Specific Modelling Languages Using UML

The strengths and weaknesses of software architecture design in the RUP, MSF, MBASE and RUP-SOA methodologies: A conceptual review

Contact Info

Product

Resources

About