A model for capturing and tracing architectural designs

Software architecture constitutes the primary design of a software system. Consequently, architectural design decisions involved in architecture design have a key impact on the system in such aspects as future maintenance costs, resulting quality, and timeliness. However, the applied knowledge employed and the design decisions taken by software architects are not explicitly represented in the design despite their important role; consequently, they remain in the mind of designers and are lost with time. In this work, a model for capturing and tracing the products and architectural design decisions involved in software architecture design processes is proposed. An operational perspective is considered in which design decisions can be modelled by means of design operations. The basic ontology of situation calculus is adopted to formally model the evolution of a software architecture.1st International Workshop on Advanced Software Engineering: Expanding the Frontiers of Software Technology - Session 1: Software Architecture.Red de Universidades con Carreras en Informátic

A model for capturing and tracing architectural designs

Software architecture constitutes the primary design of a software system. Consequently, architectural design decisions involved in architecture design have a key impact on the system in such aspects as future maintenance costs, resulting quality, and timeliness. However, the applied knowledge employed and the design decisions taken by software architects are not explicitly represented in the design despite their important role; consequently, they remain in the mind of designers and are lost with time. In this work, a model for capturing and tracing the products and architectural design decisions involved in software architecture design processes is proposed. An operational perspective is considered in which design decisions can be modelled by means of design operations. The basic ontology of situation calculus is adopted to formally model the evolution of a software architecture.1st International Workshop on Advanced Software Engineering: Expanding the Frontiers of Software Technology - Session 1: Software Architecture.Red de Universidades con Carreras en Informátic

A model for capturing and tracing architectural designs

Software architecture constitutes the primary design of a software system. Consequently, architectural design decisions involved in architecture design have a key impact on the system in such aspects as future maintenance costs, resulting quality, and timeliness. However, the applied knowledge employed and the design decisions taken by software architects are not explicitly represented in the design despite their important role; consequently, they remain in the mind of designers and are lost with time. In this work, a model for capturing and tracing the products and architectural design decisions involved in software architecture design processes is proposed. An operational perspective is considered in which design decisions can be modelled by means of design operations. The basic ontology of situation calculus is adopted to formally model the evolution of a software architecture.1st International Workshop on Advanced Software Engineering: Expanding the Frontiers of Software Technology - Session 1: Software Architecture.Red de Universidades con Carreras en Informátic

Tradition and Innovation: From Worksite Plans to Digital Models

The study and analysis of archaeological elements often ranges from very large sites to small objects. This difference in size and type is also present during survey and representation. This idea sparked the proposed study of worksite plans that constitute the only firm link between historical architecture and its representation. The objective is to develop a new interpretation of worksite plans merging massive acquisition technologies with digital representation. The topic is associated with studies on the origins of architectural drawing based on the interdisciplinary union between architecture and archaeology. The objective is to critically interpret worksite plans in order to establish and classify a study methodology. Based on these premises, we examined the key relationship between the metric/formal construction of a 2D drawing (plan) with a 3D model (ideal model). The study is part of the now consolidated drawing/survey/design process which is based on objective/real drawings and leads to a 3D/ideal mode

(SAKM) Software Architecture Knowledge Management and its recent Practices, Models, Tools and Challenges

Management of knowledge for software architecture means to capture convenient experience and then translating it in generalized architectural knowledge. For refining the organizational architectural competences, architectural knowledge management is very much important. Architectural knowledge is valuable in the Software Architecture design process. This knowledge will help the stakeholders for communication in different phases of software development life cycle(SDLC). Properly managing the architectural knowledge is very much important as it is progressively more regarded the same as an organizational positive feature and that is why so many researchers around the world are proposing tools, methods, models and different frameworks for the effective knowledgemanagement [1]. This article contributes in exploring current work in field of software architectural knowledge management (AKM) from 2010 to 2017. This article highlights recent architectural AKM challenges and issues which are still not settled and here we also discuss different AKM tools, practicesand models

Visualizing practices in project-based design : tracing connections through cascades of visual representations

Project-based design involves a variety of visual representations, which are evolved to make decisions and accomplish project objectives. Yet, such mediated and distributed ways of working are difficult to capture through ethnographies that examine situated design. A novel approach is developed that follows cascades of visual representations; and this is illustrated through two empirical studies. In the first case, Heathrow Terminal 5, analysis starts from paper- and model-work used to develop design, tracing connections forward to an assembly manual that forms a ‘consolidated cascade ’ of visual representations . In th e second, the Turning Torso, Malmö, analysis starts from a planning document, trac ing connections backward to the paper - and model - work done to produce this consolidated cascade . Th is work makes a twofold contribution : First, it offer s a methodological app roach that supplements ethnographies of situated design. This allows the researcher to be nimble, tracing connections across complex engineering projects; reconstructing practices through their visual representations; and observing their effects. Second, it articulate s how , in these empirical cases, interaction with a cascade of visual representations enabled participants in project - based design to develop and share understanding. T he complexity of projects , and their distributed and mediated nature makes this approach timely and important in address ing new research questions and practical challenges

Adaptive development and maintenance of user-centric software systems

A software system cannot be developed without considering the various facets of its environment. Stakeholders – including the users that play a central role – have their needs, expectations, and perceptions of a system. Organisational and technical aspects of the environment are constantly changing. The ability to adapt a software system and its requirements to its environment throughout its full lifecycle is of paramount importance in a constantly changing environment. The continuous involvement of users is as important as the constant evaluation of the system and the observation of evolving environments. We present a methodology for adaptive software systems development and maintenance. We draw upon a diverse range of accepted methods including participatory design, software architecture, and evolutionary design. Our focus is on user-centred software systems