2006
DOI: 10.1007/11767718_38
|View full text |Cite
|
Sign up to set email alerts
|

Refinement of Software Architectures by Recursive Model Transformations

Abstract: The main aim of this paper is to present how to refine software logical architectures by application of a recursive model-based transformation approach called 4SRS (four step rule set). It is essentially based on the mapping of UML use case diagrams into UML object diagrams. The technique is based on a sequence of steps that are inscribed in a tabular representation that is used to derive the software architecture for a focused part of the global system.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
27
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
6
1

Relationship

2
5

Authors

Journals

citations
Cited by 25 publications
(27 citation statements)
references
References 6 publications
(11 reference statements)
0
27
0
Order By: Relevance
“…There are approaches to support the design of software architectures, like RSEB [12], FAST [13], FORM [14], KobrA [15] and QADA [16]. The product-level perspective of the 4SRS method [17] also promotes functional decomposition of software systems. The result of the application of the 4SRS method is a logical architecture.…”
Section: Multiple Scrum Teams For Implementing Logical Software Archimentioning
confidence: 99%
See 2 more Smart Citations
“…There are approaches to support the design of software architectures, like RSEB [12], FAST [13], FORM [14], KobrA [15] and QADA [16]. The product-level perspective of the 4SRS method [17] also promotes functional decomposition of software systems. The result of the application of the 4SRS method is a logical architecture.…”
Section: Multiple Scrum Teams For Implementing Logical Software Archimentioning
confidence: 99%
“…We applied filtering and collapsing techniques [17] to the border that relates to the architectural elements within the module. These techniques redefine the system boundaries, which now regards only the given module as a subsystem for design.…”
Section: Fig 2 Architecture Modularization Examplementioning
confidence: 99%
See 1 more Smart Citation
“…In [24] the authors deal with refining a software architecture for a specific, focused part of a global application architecture. Their approach is based on the UML and recursive refinement of UML use case diagrams to UML object diagrams.…”
Section: B System Design Supportmentioning
confidence: 99%
“…The detail of the transition rules is subject of future publications. Like in [2,14], we propose the usage of the 4SRS by recursive executions with the purpose of deriving a new logical architecture. The transition steps are structured as follows: (1) Architecture Partitioning, where the Process-level Architectural Elements (AEpc's) under analysis are classified by their computation execution context with the purpose of defining software boundaries to be transformed into Product-level (software) Use Cases (UCpt's.…”
Section: Process-to Product-level Transitionmentioning
confidence: 99%