Software architecture has emerged as an important field of software engineering for managing the realm of large-system development and maintenance [1-4]. The main intent of software architecture is to provide intellectual control over a sophisticated system of enormous complexity [5]. There are many definitions of software architecture [6]. The Rational Unified Process (RUP) [7], building upon [8], defines a software architecture “as the set of significant decisions about the organization of a software system: selection of the structural elements and their interfaces by which a system is composed, behavior as specified in collaborations among those elements, composition of these structural and behavioral elements into larger subsystem, architectural style that guides this organization. Software architecture also involves usage, functionality, performance, resilience, reuse, comprehensibility, economic and technology constraints and tradeoffs, and aesthetic concerns. Software architecture is developed during the early phases of the software development process. Therefore, it significantly constrains and facilitates the achievement of requirements and business goals. Hence, reviewing the software architecture represents a valid means to check the system conformance and to reveal any potentially-missed objectives early on [9]. Every software system has a software architecture; it can be implicit or explicit, i.e., documented and specifically designed to fulfill predefined business goals and quality requirements. When a system needs to be maintained it may be necessary to spend considerable effort in documenting the underlying software architecture even if it has to be recovered (reverse engineered) [10].

Barbi, E., Sabbatino, V., Cantone, G., D'Angiò, A., Falessi, D. (2012). Interoperability among UML tools: an industrial case study. In Industry Day 2012. Proceedings of the 2012 ACM SIGSOFT symposium on Industry Day. (pp.5-8). New York : ACM [10.1145/2304636.2304639].

Interoperability among UML tools: an industrial case study

CANTONE, GIOVANNI;FALESSI, DAVIDE
2012-06-01

Abstract

Software architecture has emerged as an important field of software engineering for managing the realm of large-system development and maintenance [1-4]. The main intent of software architecture is to provide intellectual control over a sophisticated system of enormous complexity [5]. There are many definitions of software architecture [6]. The Rational Unified Process (RUP) [7], building upon [8], defines a software architecture “as the set of significant decisions about the organization of a software system: selection of the structural elements and their interfaces by which a system is composed, behavior as specified in collaborations among those elements, composition of these structural and behavioral elements into larger subsystem, architectural style that guides this organization. Software architecture also involves usage, functionality, performance, resilience, reuse, comprehensibility, economic and technology constraints and tradeoffs, and aesthetic concerns. Software architecture is developed during the early phases of the software development process. Therefore, it significantly constrains and facilitates the achievement of requirements and business goals. Hence, reviewing the software architecture represents a valid means to check the system conformance and to reveal any potentially-missed objectives early on [9]. Every software system has a software architecture; it can be implicit or explicit, i.e., documented and specifically designed to fulfill predefined business goals and quality requirements. When a system needs to be maintained it may be necessary to spend considerable effort in documenting the underlying software architecture even if it has to be recovered (reverse engineered) [10].
2012 ACM SIGSOFT symposium on Industry Day: CompArch 2012
Bentinoro (Italy)
2012
3.
Vincenzo Grassi, Università di Roma Tor Vergata, Italy ; Raffaela Mirandola, Politecnico di Milano, Italy
Rilevanza internazionale
contributo
27-giu-2012
1-giu-2012
Settore ING-INF/05 - SISTEMI DI ELABORAZIONE DELLE INFORMAZIONI
English
Software architecture;
http://dl.acm.org/citation.cfm?id=2304636&coll=DL&dl=GUIDE
Intervento a convegno
Barbi, E., Sabbatino, V., Cantone, G., D'Angiò, A., Falessi, D. (2012). Interoperability among UML tools: an industrial case study. In Industry Day 2012. Proceedings of the 2012 ACM SIGSOFT symposium on Industry Day. (pp.5-8). New York : ACM [10.1145/2304636.2304639].
Barbi, E; Sabbatino, V; Cantone, G; D'Angiò, A; Falessi, D
File in questo prodotto:
Non ci sono file associati a questo prodotto.

I documenti in IRIS sono protetti da copyright e tutti i diritti sono riservati, salvo diversa indicazione.

Utilizza questo identificativo per citare o creare un link a questo documento: https://hdl.handle.net/2108/75547
Citazioni
  • ???jsp.display-item.citation.pmc??? ND
  • Scopus 0
  • ???jsp.display-item.citation.isi??? ND
social impact