Citation Context

...ments description. For instance, a requirement may be decomposed to multiple requirements. These changes are semantics-preserving according to [40] and we consider their rationale as refactoring (see =-=[82]-=- for refactoring). Evolution of requirements also fosters changes to the requirements model. We name these changes and their rationale domain changes. With the term ‘domain’ we mean problem/business d...

Citation Context

...encoded in the architectural model [242]. They are not for implicit properties which are inferred by human from the non modeled existing information. Architecture description languages such as Wright =-=[9]-=-, Aesop [89], and MetaH [115] support model-based analysis. � Simulation-Based Analysis. It is used to analyze the behavior of software architectures by using an executable architecture model of a giv...

Citation Context

...rature for requirements models. There are several commonly used approaches to define and represent requirements: goal-oriented [250] [186], aspect-driven [216], variability management [183], use-case =-=[54]-=-, domain-specific [200] [143], and reuse-driven techniques [164]. Goal-oriented62 Chapter 4 Semantics of Requirements Relations requirements engineering [250] [186] defines a model for decomposing a ...

Citation Context

...iable is the number of states. We also compare the scalability test results of the tool using Maude with the results of the tool using different simulation and verification environments such as Alloy =-=[126]-=-. The same execution semantics of AADL in Maude is encoded in Alloy. The first part of the performance test is done in Maude with 10000 architectural elements (see Table 6.3(a)). Then, the second part...

Citation Context

...f AADL models [221]. For the verification, architectural significant functional requirements are reformulated as formalized scenarios and then properties are checked using linear temporal logic (LTL) =-=[14]-=-. Application of verification techniques for requirements is not the main focus of this chapter. The details can be found in [212]. � Generating and validating traces. We use semantics of traces and r...

Citation Context

...taining consistency between software development artifacts. It is the ability to link requirements back to stakeholders’ rationales and forward to corresponding design artifacts, code, and test cases =-=[100]-=-. When changes for the requirements of the software system are proposed, the impact of these changes on other requirements, design elements and source code is traced in order to determine parts of the...

Citation Context

...ctual and the generated traces for a requirement. Figure 6.11 Venn Diagram for Generated and Actual Satisfies Traces for a Requirement The interpretation of Figure 6.11 is given in a confusion matrix =-=[78]-=- in Table 6.1.6.6 Generating and Validating Traces 193 Table 6.1 Confusion Matrix of Generated and Actual Traces for Satisfies Relation Actual ‘Satisfies’ Traces (AST) Generated ‘Satisfies’ Traces (G...

Citation Context

...the architectural model [242]. They are not for implicit properties which are inferred by human from the non modeled existing information. Architecture description languages such as Wright [9], Aesop =-=[89]-=-, and MetaH [115] support model-based analysis. � Simulation-Based Analysis. It is used to analyze the behavior of software architectures by using an executable architecture model of a given system. T...

Citation Context

...tion of Requirements and Relations 65 Let F be a set of function symbols and P a set of predicate symbols, each symbol with a fixed arity. A model M of the pair (F, P) consists of the following items =-=[118]-=-: � a non-empty set A, the universe of concrete values � for each f � F with n arguments, a function f M : A n � A � for each P � P with n arguments, a set P M � A n. The details of the definition of ...

Citation Context

...arch has been devoted to relating requirements and design artifacts with source code. Most approaches focus on generating traces between requirements and source code or between design and source code =-=[13]-=- [70] [102] [109]. Less attention has been paid to relating requirements with architecture by using well-defined semantics of traces. Designing architecture based on requirements is a creative and man...

Citation Context

...sign, compared to the traceability impact analysis. Dependencies in detaileddesign and source code are used in order to determine the impacted parts of source code or detailed design. Program slicing =-=[85]-=- and impact analysis on UML models [35] [36] are examples of dependency impact analysis. � Experimental Impact Analysis. Review processes, informal discussions and the application of engineering judge...

Citation Context

...e a tool that translates requirements given in the form of “if then else” rules into the disjunctive normal form for classical logic reasoning and cluster prioritization is provided. Heitmeyer et al. =-=[113]-=- propose consistency checking in requirements specifications for automatic detection of errors, such as type errors, non-determinism, missing cases, and circular definitions. The technique is based on...

Citation Context

...ult, the requirements engineers and software architects cannot precisely locate the impacted requirements and architectural elements and as such traces become useless.1.3 Research Questions 3 Bohner =-=[22]-=- [23] [25] formulates the situation where all elements might be impacted, as explosion of impacts without semantics. He states that change impact analysis must employ additional semantic information t...

Citation Context

...of changes at the end of the section. 5.3.1 Structure of a Textual Requirement We need to consider the structure of a requirement to determine the granularity of changes that can be applied. Heninger =-=[114]-=- mentions about six criteria which a software requirements document should satisfy: � It should only specify external system behavior � It should specify constraints on the implementation � It should ...

Citation Context

...hitecture According to [264], Wright language proposed by Allen and Garlan [9] can be considered as the first work on model checking techniques for software architecture. The extension of the work in =-=[8]-=- addresses the problem of specifying and analyzing dynamic behaviour of architectures. Dynamic behavior is distinguished from the steady-state behavior where the computation performed by a system with...

Citation Context

...ts to architecture which define trace types. Some of these approaches are summarized in [86] as:6.3 Trace Metamodel 177 goal-oriented [250], model bridging [103], problem frames [105], use case maps =-=[41]-=-, rule-based decision making [158], architecting requirements [157], object-oriented transition [137], and weaving requirements and architecture processes [193]. For example, goal-oriented requirement...

Citation Context

...agee and Kramer [170] outline examples of language features for dynamic structure. There are approaches for analyzing dynamic behaviour: Darwin [171] [168], Chemical Abstract Machine (CHAM) [56] [57] =-=[125]-=-, dynamic architecture verification using DynAlloy [39] [38], reconfiguration analysis in service oriented architectures [15], and behaviour preservation in dynamic architectures [112]. Our approach d...

Citation Context

...voted to relating requirements and design artifacts with source code. Most approaches focus on generating traces between requirements and source code or between design and source code [13] [70] [102] =-=[109]-=-. Less attention has been paid to relating requirements with architecture by using well-defined semantics of traces. Designing architecture based on requirements is a creative and manual process. The ...

Citation Context

...gement. The size and complexity of software systems make change management costly and time consuming. 85 to 90 percent of software system budgets goes to operation and maintenance of software systems =-=[74]-=-. To reduce the cost of changes, it is important to apply change management as early as possible in the software development cycle. Requirements traceability is considered crucial in change management...

Citation Context

...d style- specific ADLs are as follows [242]: Koala [203]. It was developed by Philips Electronics to model the architecture of consumer electronics devices such as televisions and DVD players. Weaves =-=[99]-=-. It is used to model data-flows characterized by high-volume of data and realtime requirements.2.4 Software Change Management 23 The Architecture Analysis and Design Language (AADL) [225] [79]. It i...

Citation Context

... models to trace requirements throughout abstraction levels. Change impact analysis in requirements is deferred to future work. 2.7.1.1.2 Event Based Traceability (EBT) Event-Based Traceability (EBT) =-=[50]-=- is a method for automating trace generation and maintenance. In EBT, requirements and other traceable artifacts, such as design models, are no longer directly related, but linked through publish-subs...

Citation Context

...resent traces. There is also a standard stereotype for traceability in UML [201].38 Chapter 2 Background and Definitions 2.7.1.2.1 Scenario Driven Approach to Trace Dependency Analysis (SDTDA) Egyed =-=[70]-=- presents an automated approach for generating and validating traces. He addresses the problem that the absence of trace information or the uncertainty of trace correctness limits the usefulness of so...

Citation Context

...le of requirements changes in order to determine the impact of changes in the whole requirements model. We classify rationale of requirements changes as refactoring and domain changes. Buckley et al. =-=[40]-=- classifies changes in general as semantics-preserving and semantics-modifying. However, they focus more on semantics of software components, such as type hierarchy, scoping, visibility, accessibility...

Citation Context

... instance, requirements changes are categorized as high effort, medium effort, low effort and no effort changes based on the magnitude of effort involved criterion by the practitioners. Harker et al. =-=[107]-=- describe a classification of changing requirements where each changing requirement type could be reformulated as a change type. Lam et al. [150] propose a change maturity model that reflects an organ...

Citation Context

...ition from requirements to architecture which define trace types. Some of these approaches are summarized in [86] as:6.3 Trace Metamodel 177 goal-oriented [250], model bridging [103], problem frames =-=[105]-=-, use case maps [41], rule-based decision making [158], architecting requirements [157], object-oriented transition [137], and weaving requirements and architecture processes [193]. For example, goal-...

Citation Context

...resentations. The Architecture Description Markup Language (ADML) [234]. It is an XML based ADL. It provides meta-properties which are used to specify user-defined properties and property types. xADL =-=[60]-=-. It is build upon XML and schemas. The default schema provides the basic elements: component, connector, interface and configuration. The default schema is extended for modeling different types of sy...

Citation Context

...approaches about transition from requirements to architecture which define trace types. Some of these approaches are summarized in [86] as:6.3 Trace Metamodel 177 goal-oriented [250], model bridging =-=[103]-=-, problem frames [105], use case maps [41], rule-based decision making [158], architecting requirements [157], object-oriented transition [137], and weaving requirements and architecture processes [19...

Citation Context

... metamodels but MDE approaches that use requirements metamodels are summarized and reviewed. 4.8.3 Requirements Reasoning A number of approaches describe reasoning about requirements. Giorgini et al. =-=[93]-=- propose a formal framework for reasoning with goal models. A precise semantics is given for all goal relationships in a qualitative and numerical form. Label propagation algorithms that are shown to ...

Citation Context

...behaviour: Darwin [171] [168], Chemical Abstract Machine (CHAM) [56] [57] [125], dynamic architecture verification using DynAlloy [39] [38], reconfiguration analysis in service oriented architectures =-=[15]-=-, and behaviour preservation in dynamic architectures [112]. Our approach does not support the analysis of dynamic behaviour. There are works [64] [73] [187] about extending architectural description ...

Citation Context

...iber manager. The subscriber manager resolves event notifications and restores related artifacts and traces to a new state if necessary. 2.7.1.1.3 Goal Centric Traceability (GCT) Cleland-Huang et al. =-=[52]-=- introduce a goal-centric approach for managing impact of a change in non-functional requirements. Goal Centric Traceability (GCT) models non-functional requirements and their dependencies using a Sof...

Citation Context

...e types.218 Chapter 6 Traces between Requirements and Software Architecture 6.10.2 Generating and Validating Traces A number of approaches provide generating and validating traces. Egyed et al. [72] =-=[71]-=- [70] provides an automated traceability approach that uses a small number of traces as input. In [72] [70], the source code is executed according to some scenarios and then traces are generated betwe...

Citation Context

...lized and represented? How can trace semantics be used to achieve traceability goals such as change impact analysis? � Open Issue 3: Incremental model transformation. Incremental model transformation =-=[65]-=- [110] [132] [146] is an active research topic in MDE. The use of traces with incremental model transformations is partially known. There are still some questions not answered. For instance, how can t...

Citation Context

...alysis. Dependencies in detaileddesign and source code are used in order to determine the impacted parts of source code or detailed design. Program slicing [85] and impact analysis on UML models [35] =-=[36]-=- are examples of dependency impact analysis. � Experimental Impact Analysis. Review processes, informal discussions and the application of engineering judgement are defined as experimental impact anal...

Citation Context

...the formula contains free variables. 6.4.2 Formalization of Architecture A software architecture model AM is a model conforming to the AADL metamodel. There are different works in the literature [12] =-=[28]-=- [29] [221] that provide a formal semantics of the following notions: metamodel, model, and conformance of a model to its metamodel. We do not repeat the formalization of these notions in this thesis....

Citation Context

...e on software104 Chapter 4 Semantics of Requirements Relations development activities such as change management are stated. However, there is no formal semantics for the relations. Carlshamre et al. =-=[43]-=- run an industrial survey of requirements in software product release planning. Their aim is to learn about the nature of interdependencies in general, to be able to classify them, and to assess the r...

Citation Context

...the software architect based on previous experience. The main difference with our approach is that the approach in [241] provides only impacted architectural elements without any proposed change. Han =-=[106]-=- introduces an approach for7.6 Related Work 261 impact analysis and change propagation based on dependencies of software artifacts. Propagation rules are defined based on change patterns. A change pa...

Citation Context

...eaves [99]. It is used to model data-flows characterized by high-volume of data and realtime requirements.2.4 Software Change Management 23 The Architecture Analysis and Design Language (AADL) [225] =-=[79]-=-. It is developed by Software Engineering Institute in Carnegie Mellon University to specify system architectures for a wide variety of embedded and real-time systems such as automotive, avionics and ...

Citation Context

...erification of architecture is done by the Lesar model-checker [217]. Abdoul et al. [2] propose an AADL model transformation which provides a formal model for model checking activities. Hugues et al. =-=[116]-=- present a tool suite for analyzing AADL models. In [116], it is considered that subprograms in AADL encapsulate the behavior of architecture. Similar to [197], Benammar et al. [18] [19] propose the u...

Citation Context

... models is ensured with crossmodel rules which actually check the preservation of properties between two models. There are other conformance assessment approaches by Egyed [69], Abi-Antoun et al. [3] =-=[4]-=-, Moriconi et al. [184], Heckel et al. [112] and Oquendo [205]. Most of these works focuses on the conformance assessment for architecture and detailed design. Our approach does conformance assessment...

Citation Context

...lysis in AADL models. Delanote et al. [63] explore the use of AADL in model driven development. However, the authors do not adapt any architecture analysis technique to AADL models. Berthomieu et al. =-=[20]-=- [21] give an approach for formal verification of AADL specifications. A subset of AADL is translated into an extension of Petri nets called Fiacre language [21]. Chkouri et al. [46] propose another a...

Citation Context

...ion [8]. Magee and Kramer [170] outline examples of language features for dynamic structure. There are approaches for analyzing dynamic behaviour: Darwin [171] [168], Chemical Abstract Machine (CHAM) =-=[56]-=- [57] [125], dynamic architecture verification using DynAlloy [39] [38], reconfiguration analysis in service oriented architectures [15], and behaviour preservation in dynamic architectures [112]. Our...

Citation Context

... and represented? How can trace semantics be used to achieve traceability goals such as change impact analysis? � Open Issue 3: Incremental model transformation. Incremental model transformation [65] =-=[110]-=- [132] [146] is an active research topic in MDE. The use of traces with incremental model transformations is partially known. There are still some questions not answered. For instance, how can traces ...

Citation Context

...ents model from a given requirements document. Requirements relations are not typed and lack semantics. Consistency checking and inferencing for requirements relations are not supported. Some authors =-=[111]-=- [236] use the UML profiling mechanism in a goal-oriented requirements engineering approach. Heaven et al. [111] introduce a profile that allows the KAOS model [250] to be represented in UML. They als...

Citation Context

...epresented? How can trace semantics be used to achieve traceability goals such as change impact analysis? � Open Issue 3: Incremental model transformation. Incremental model transformation [65] [110] =-=[132]-=- [146] is an active research topic in MDE. The use of traces with incremental model transformations is partially known. There are still some questions not answered. For instance, how can traces betwee...

Citation Context

...t sequences, general trends, or range of values rather than specific results [242]. An example simulation analysis platform is the eXtensible Tool-chain for Evaluation of Architectural Models (XTEAM) =-=[68]-=- which is a model driven architectural description and simulation environment for mobile software systems. Not all architectural models are available for simulation-based analysis. Available architect...

Citation Context

...een devoted to relating requirements and design artifacts with source code. Most approaches focus on generating traces between requirements and source code or between design and source code [13] [70] =-=[102]-=- [109]. Less attention has been paid to relating requirements with architecture by using well-defined semantics of traces. Designing architecture based on requirements is a creative and manual process...

Citation Context

...On the contrary, in [18] [19], the behavior of a thread is specified directly in Maude. Varona-Gomez et al. [253] translate AADL models to SystemC models for performance analysis. Bozzano et al. [34] =-=[33]-=- present an AADL analysis approach which supports Error Model Annex for modeling faults and repairs. Li et al. [155] propose the use of Communicating Sequential Processes (CSP) for simulation of AADL ...

Citation Context

... trace types.218 Chapter 6 Traces between Requirements and Software Architecture 6.10.2 Generating and Validating Traces A number of approaches provide generating and validating traces. Egyed et al. =-=[72]-=- [71] [70] provides an automated traceability approach that uses a small number of traces as input. In [72] [70], the source code is executed according to some scenarios and then traces are generated ...

Citation Context

...ation analysis in service oriented architectures [15], and behaviour preservation in dynamic architectures [112]. Our approach does not support the analysis of dynamic behaviour. There are works [64] =-=[73]-=- [187] about extending architectural description languages with statechart semantics to analyze the internal component behavior. These works are similar to the behavioral annex for thread and subprogr...

Citation Context

...ed for Web systems. They identify the general structure of Web systems in order to define the requirements metamodel. The requirements metamodel for web requirements, presented by Escalona and Aragon =-=[75]-=-, is divided into two packages: the Behavior and the Structure. In the behavior package, concepts such as WebActor and WebUseCase related to the behavior of the system presented. In the structure pack...

Citation Context

...hreads and no modes). Jahier et al. [127] provides an AADL analysis approach in which the behavior of software components are developed as AADL subprogram execution. In [127] the testing tool Lurette =-=[128]-=- is used for simulation; verification of architecture is done by the Lesar model-checker [217]. Abdoul et al. [2] propose an AADL model transformation which provides a formal model for model checking ...

Citation Context

...aude. We illustrate our approach in an example. 6.1 Introduction In Chapter 5, we presented a change impact analysis approach in requirements models. To overcome the explosion of impacts addressed in =-=[23]-=-, we provide semantics of requirements changes together with formal semantics of requirements relations given in Chapter 4. We use the formalization of relations and changes for propagating and consis...

Citation Context

...languages provide basic constructs for describing common architectural elements with extending these elements for user-defined constructs [242]. Examples of extensible ADLs are as follows [242]: Acme =-=[90]-=-. It is designed to be an interchange language for several existing ADLs. It has a base of constructs to be extended: components, connectors, ports, roles, attachments, systems, and representations. T...

Citation Context

... an evolutionary framework. The interaction of consistency and completeness with correctness during requirements evolution is discussed. Duffy et al.108 Chapter 4 Semantics of Requirements Relations =-=[67]-=- propose a logic-based framework for reasoning about requirements specifications based on goal-tree structures. The framework is based on goal decomposition supported by automated reasoning. Rodrigues...

Citation Context

...Berthomieu et al. [20] [21] give an approach for formal verification of AADL specifications. A subset of AADL is translated into an extension of Petri nets called Fiacre language [21]. Chkouri et al. =-=[46]-=- propose another analysis approach using translation between AADL and6.10 Related Work 221 BIP (Behavior Interaction Priority) language. The analysis technique [197] we use gives a formal executable ...

Citation Context

...anguages. Similar to [197], Yang et al. [263] propose a formal semantics in Timed Abstract State Machine (TASM) for a limited set of AADL behavior annex (periodic threads and no modes). Jahier et al. =-=[127]-=- provides an AADL analysis approach in which the behavior of software components are developed as AADL subprogram execution. In [127] the testing tool Lurette [128] is used for simulation; verificatio...

Citation Context

...figuration analysis in service oriented architectures [15], and behaviour preservation in dynamic architectures [112]. Our approach does not support the analysis of dynamic behaviour. There are works =-=[64]-=- [73] [187] about extending architectural description languages with statechart semantics to analyze the internal component behavior. These works are similar to the behavioral annex for thread and sub...

Citation Context

...rthermore, the literature survey for existing traceability approaches in MDE is given in general and also in particular for change impact analysis. The literature survey is based on work published in =-=[87]-=-. Chapter 3 Analysis of Impacts Explosion in Traceability. This chapter motivates the need for semantics of traces between requirements, and requirements & architecture for change management by addres...

Citation Context

...264], CHARMY [209], using the SPIN model-checker, is one of the most recent architecture analysis approaches. A similar approach that uses SPIN for verifying software architecture is proposed by Bose =-=[31]-=-. The works in [209] and [31] use UML-based notations instead of architecture description languages.220 Chapter 6 Traces between Requirements and Software Architecture According to [264], Wright lang...

Citation Context

...lation: A requirement R1 refines a requirement R2 if R1 is derived from R2 by adding more details to its properties. The refined requirement can be seen as an abstraction of the detailed requirements =-=[59]-=- [250]. � Definition 4.4. Partially refines relation: A requirement R1 partially refines a requirement R2 if R1 is derived from R2 by adding more details to properties of R2 and excluding the unrefine...

Citation Context

...ules that characterize how the footprint graph relates to the hypothesized traces and artifacts to which they are linked. 2.7.1.2.2 Operational Semantics for Traceability (OST) Aizenbud-Reshef et al. =-=[6]-=- present an approach which defines an operational semantics for traceability in UML. Three main issues for traceability are stated: querying (e.g. impact analysis, coverage queries), following traces ...

Citation Context

... have the notion of requirements relations. On the other hand, our approach covers the static aspects of requirements including non-functional requirements and reasoning on requirements relations. In =-=[37]-=-, a model-driven mechanism is proposed to merge different requirement specifications and reveal inconsistencies between them by using a requirements metamodel. The requirements metamodel is mainly use...

Citation Context

...nts and architecture identified in the literature. There are several approaches about transition from requirements to architecture which define trace types. Some of these approaches are summarized in =-=[86]-=- as:6.3 Trace Metamodel 177 goal-oriented [250], model bridging [103], problem frames [105], use case maps [41], rule-based decision making [158], architecting requirements [157], object-oriented tra...

Citation Context

...odel [52] has partial tool support. Despite of the fact that the retrieval algorithm uses probability to return traces, user’s appraisal is required to manage traces. EBT-DP: A few features of EBT-DP =-=[51]-=- (generation of traces) are implemented. RMRT: The reference metamodels for traceability by Ramesh and Jarke [215] are encoded in a knowledge-based meta database management system called ConceptBase. ...

Citation Context

...onitoring, and machine learning to generate traces. Relations between program entities are compared with corresponding relations between elements in UCDs only to validate traces. Cysneiros and Zisman =-=[58]-=- describe an approach to support traceability for agent systems. Although it is claimed that the approach uses six types of traces and semantics of these types, no semantics for the trace types is pro...

Citation Context

...ysis method to evaluate requirement changes. Complementary to our approach, O’Neal addresses the identification of the consequences of a change, such as how much change should be done. Hassine et al. =-=[108]-=- provide change impact analysis approach for requirements described as detailed scenarios. Dependencies between scenarios are used to identify the impacted scenarios. However, the approach does not pr...

Citation Context

...orm specific and independent models is ensured with crossmodel rules which actually check the preservation of properties between two models. There are other conformance assessment approaches by Egyed =-=[69]-=-, Abi-Antoun et al. [3] [4], Moriconi et al. [184], Heckel et al. [112] and Oquendo [205]. Most of these works focuses on the conformance assessment for architecture and detailed design. Our approach ...

Citation Context

...vior is specified outside AADL. Apart from simulating and verifying AADL models, de Niz et al. [61] propose the use of AADL models to analyze potentially unintended system behavior. Gilles and Hugues =-=[91]-=- [92] present a domain specific language (REAL – Requirement Enforcement Analysis Language) for AADL. Contrary to our approach, the approach in [91] [92] does not focus on simulation and verification ...

Citation Context

...ows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined. This chapter is based on work published in =-=[96]-=- and [98].10 Chapter 1 Introduction Chapter 5 Change Impact Analysis in Requirements. This chapter discusses problems related to change impact analysis in requirements and provides the approach for t...

Citation Context

...understand requirements in more detail. The following subsections present five requirements-driven approaches. 2.7.1.1.1 Requirements Traceability and Transformation Conformance (RTTC) Almeida et al. =-=[11]-=- aim at simplifying the management of traces between requirements and various design artifacts. They propose a framework as a basis for tracing requirements, assessing the quality of model transformat...

Citation Context

...). In the requirements metamodel, there are three types of trace links between requirements: DependenceTrace, InfluenceTrace, and ParentChildTrace. The relations are defined informally. Baudry et al. =-=[17]-=- introduce a metamodel for requirements and present how they use it on top of a constrained natural language for requirements definitions. The requirements metamodel captures functional requirements a...

Citation Context

...pports generating traces between design models and code specification by checking synonyms. Instead of checking synonyms our approach uses semantics of traces and requirements relations. Bonde et al. =-=[26]-=- describe an interoperability approach based on generating a trace model by using model transformations. This work focuses on traces between platform independent and platform specific models in MDA co...

Citation Context

...ormula contains free variables. 6.4.2 Formalization of Architecture A software architecture model AM is a model conforming to the AADL metamodel. There are different works in the literature [12] [28] =-=[29]-=- [221] that provide a formal semantics of the following notions: metamodel, model, and conformance of a model to its metamodel. We do not repeat the formalization of these notions in this thesis. We c...

Citation Context

...res for dynamic structure. There are approaches for analyzing dynamic behaviour: Darwin [171] [168], Chemical Abstract Machine (CHAM) [56] [57] [125], dynamic architecture verification using DynAlloy =-=[39]-=- [38], reconfiguration analysis in service oriented architectures [15], and behaviour preservation in dynamic architectures [112]. Our approach does not support the analysis of dynamic behaviour. Ther...

Citation Context

... we rely on the semantics of requirements and relations previously given in Chapter 4. In addition, in this chapter we successively provide the followings: � Trace metamodel. We use a trace metamodel =-=[66]-=- to structure the traces. The metamodel includes most commonly found entities in literature, and requirements & architecture specific traces (Section 6.3). � Semantics of traces. We formalize traces b...

Citation Context

...hich actually check the preservation of properties between two models. There are other conformance assessment approaches by Egyed [69], Abi-Antoun et al. [3] [4], Moriconi et al. [184], Heckel et al. =-=[112]-=- and Oquendo [205]. Most of these works focuses on the conformance assessment for architecture and detailed design. Our approach does conformance assessment for requirements and architecture design. 6...

Citation Context

...dencies are modeled with a Softgoal Interdependency Graph (SIG). The impact detection in [52] is limited to identifying a set of directly impacted SIG elements without any change type. Ibrahim et al. =-=[121]-=- present an approach for change impact analysis of object oriented software. Change impact analysis is performed from requirements to design, test case or source code. Ibrahim et al., however, do not ...

Citation Context

...dent models is ensured with crossmodel rules which actually check the preservation of properties between two models. There are other conformance assessment approaches by Egyed [69], Abi-Antoun et al. =-=[3]-=- [4], Moriconi et al. [184], Heckel et al. [112] and Oquendo [205]. Most of these works focuses on the conformance assessment for architecture and detailed design. Our approach does conformance assess...

Citation Context

...e Assessment Conformance assessment is the act of checking whether a requirement is satisfied [11]. The assessment can be testing, inspection, model checking or conformation transformation usage (see =-=[10]-=- for conformation transformation usage). The usage of architecture verification with requirements relations in our approach can be considered as a conformance assessment of properties in the requireme...

Citation Context

...ween SLOs in order to limit the detection of impacts (see Figure 3.2). The notion of distance in Figure 3.2 explains how the number of impacts explodes. Figure 3.2 Impacts Explosion without Semantics =-=[25]-=- After a change is introduced to SLO0, 3 impacts are introduced at a distance of 1. The number of impacts jumps to 10, 115, 1132 and 46203 at the distances of 2, 3, 4, 5 and 6 with only approximately ...

Citation Context

...onents are developed as AADL subprogram execution. In [127] the testing tool Lurette [128] is used for simulation; verification of architecture is done by the Lesar model-checker [217]. Abdoul et al. =-=[2]-=- propose an AADL model transformation which provides a formal model for model checking activities. Hugues et al. [116] present a tool suite for analyzing AADL models. In [116], it is considered that s...

Citation Context

...emiautomatic process of applying our approach. In such a process, the software architect can gradually improve the quality of the traces and the requirements. Case studies conducted with the industry =-=[47]-=- shows that it is hard to reformulate requirements as LTL/CTL formulas. Domain-specific languages can be used for requirements of certain type that allow compilation of LTL/CTL formulas [47]. Starting...

Citation Context

...zing schedulability with a behavior of a subset of AADL. All these approaches assume that the thread behavior is specified outside AADL. Apart from simulating and verifying AADL models, de Niz et al. =-=[61]-=- propose the use of AADL models to analyze potentially unintended system behavior. Gilles and Hugues [91] [92] present a domain specific language (REAL – Requirement Enforcement Analysis Language) for...

Citation Context

...els In the previous subsection, we give the literature about general architecture analysis techniques. There are also works particularly studying architecture analysis in AADL models. Delanote et al. =-=[63]-=- explore the use of AADL in model driven development. However, the authors do not adapt any architecture analysis technique to AADL models. Berthomieu et al. [20] [21] give an approach for formal veri...

Citation Context

...al changes caused by changes in requirements. Zhao et al. mainly focus on the questions such as ‘If a change is made to a component c, what other components might be affected by c?’. Feng and Maletic =-=[80]-=- address the propagation of architectural changes within the same architecture. Their approach can be considered as both dependency analysis and slicing technique. Interface and method slicing are use...

Citation Context

...rmula relations are defined for formulas in CNF. Since the rules of set theory and formula relations can be directly mapped to the Web Ontology Language (OWL) [62], we use an OWL reasoner called Jena =-=[130]-=- in our implementation. The Web Ontology Language (OWL) is a family of knowledge representation languages for specifying ontologies. OWL ontologies are serialized using RDF/XML syntax. Our formalizati...

Citation Context

...ity. The user interface is implemented by using the Eclipse Rich Client Platform (RCP) [218]. The output of the consistency checking and inferencing is represented in a table form. The JGraph library =-=[131]-=- is used for the graphical visualization of this output. The layer provides the following: � A form-based editor to enter and modify requirements � An editor to enter and modify relations between requ...

Citation Context

...e explicit connection of goals, requirements, and measures. Moon et al. [183] propose a methodology for producing requirements that can be considered as a core asset in the product line. Ceron et al. =-=[44]-=- discuss requirements modeling in the context of product lines. They propose a metamodel for requirements that contains both the common and variable parts. Lopez et al. [164] propose a metamodel for r...

Citation Context

...f relation types and change types enables proposed changes to be propagated and contradicting proposed changes in requirements to be determined. This chapter is an enhancement of results published in =-=[95]-=- and [243]. Figure 1.3 Thesis Map Chapter 6 Traces between Requirements and Software Architecture. This chapter presents the approach that provides trace establishment by using semantics of traces bet...

Citation Context

...rovided with three main types of change: screen change, report change and data change. The change classification in [150] is specialized for Customer Complaints Systems (CCCs). Ackermann and Lindvall =-=[5]-=- classify change requests as data flow change, program flow change and application domain change. Contrary to our approach, none of these change classifications given above except the work in [6] has ...

Citation Context

...that the formula contains free variables. 6.4.2 Formalization of Architecture A software architecture model AM is a model conforming to the AADL metamodel. There are different works in the literature =-=[12]-=- [28] [29] [221] that provide a formal semantics of the following notions: metamodel, model, and conformance of a model to its metamodel. We do not repeat the formalization of these notions in this th...

Citation Context

...es. Hugues et al. [116] present a tool suite for analyzing AADL models. In [116], it is considered that subprograms in AADL encapsulate the behavior of architecture. Similar to [197], Benammar et al. =-=[18]-=- [19] propose the use of rewriting logic in Maude as a formalism for modeling behavior in an AADL architectural description. On the contrary, in [18] [19], the behavior of a thread is specified direct...

Citation Context

... uses in Figure 6.7). These properties are checked for the architecture by the model checker. The requirement is first described as a formalized scenario, and then described as property specification =-=[32]-=- [209] [212]. The formalized scenario is a pair of predicates <pre, post> encoding the precondition pre and the postcondition post for the architecture. The property specification uses any logic such ...

Citation Context

...f the conceptual foundation of a language, consisting of a set of basic concepts, and a set of rules2.6 Model Driven Engineering 33 determining the set of possible models denotable in that language” =-=[76]-=-. Seidewitz [230] defines a metamodel as “a model of models expressed in a given modeling language”. We use the definition by Seidewitz as our working definition for metamodel in the thesis. Models ar...

Citation Context

...s in a very formal way in order to detect inconsistencies. The main focus is determining inconsistencies among requirements instead of inconsistencies among requirements relations. Finkelstein et al. =-=[81]-=- [194] describe a technique for inconsistency handling in requirements documents developed using multiple methods and notations for the same system. They combine the ViewPoints framework for perspecti...

Citation Context

... do not couple source code with architecture. Apart from behavioral analysis, there are static analysis techniques for architecture verification. Allen and Garlan [9] use the static analysis tool FDR =-=[84]-=- to check deadlock and component-connector compatibility. Naumovich et al. [188] use static analysis tools based on flow equations. One of the drawbacks of using static analysis is that some dynamic f...

Citation Context

...is specified outside AADL. Apart from simulating and verifying AADL models, de Niz et al. [61] propose the use of AADL models to analyze potentially unintended system behavior. Gilles and Hugues [91] =-=[92]-=- present a domain specific language (REAL – Requirement Enforcement Analysis Language) for AADL. Contrary to our approach, the approach in [91] [92] does not focus on simulation and verification of AA...

Citation Context

...requirements and their relations is carried out by requirements engineers. However, the requirements engineer does not need to know the details of the formalization. He/she can be guided by tutorials =-=[94]-=- that provide an informal explanation of the relations. The requirements model is used to obtain new knowledge about the requirements relations by automated reasoning, for example, inferred relations ...

Citation Context

...ysis approach which supports Error Model Annex for modeling faults and repairs. Li et al. [155] propose the use of Communicating Sequential Processes (CSP) for simulation of AADL models. The works in =-=[104]-=- and [232] focus on analyzing schedulability with a behavior of a subset of AADL. All these approaches assume that the thread behavior is specified outside AADL. Apart from simulating and verifying AA...

Citation Context

...l model [242]. They are not for implicit properties which are inferred by human from the non modeled existing information. Architecture description languages such as Wright [9], Aesop [89], and MetaH =-=[115]-=- support model-based analysis. � Simulation-Based Analysis. It is used to analyze the behavior of software architectures by using an executable architecture model of a given system. The results of the...