Citation Context

...pecification is introduced, and finally in section 4, a number of conclusions are provided. 2 Analysis of Traceability Approaches One of the aims of the analysis has been to identify a number of features that are the baseline for the available literature. The following features will be the starting point for the analysis and assessment and will be studied more in depth in the following subsections. 1. The link may be process-related or product-related (concepts defined by Jarke and Ramesh [15]). 2. The Pre-RS 1 and Post-RS traceability relations categories, as defined by Gotel and Finkelstein [8]) 3. The traceability link purpose introduced by Jarke and Ramesh [15]). The link purpose must provide information on the reason or justification of the link existence as project artifact, in order to justify the project resources that will be spent on the link (resources such as, for example to monitor, to save, and to analyze it in order to make project decisions, etc). 4. The items or objects which the traceability link will relate. It is desirable the objects can be specifically defined, in order to make the most automatically possible the linkage tasks. 1 Requirement Specification 2.1 Pro...

Citation Context

... to obtain relevant features and identify overlaps and inconsistencies among the approaches. Then, and based on the analysis, it provides an initial approach for a Traceability Specification Scheme. This scheme is expected to facilitate traceability specification for a given project, to improve the traceability management, and help to automate some traces management processes. 1 Introduction and Motivation Traceability is widely recognized as a concern in software and systems engineering, this is reflected by an extensive literature, multiple tools, and a growing research interest in the area [15]. The benefits of a well managed traceability activity are widely accepted nowadays, however, several issues still make difficult the adoption of a wide-scale traceability activity in the software\system engineering practice. There is a lack of a commonly accepted traceability definition, further than the scope of the term definition as in [2]; also a standard way of specifying traceability among items does not exist. It is interesting to notice that standards such as [9] and [10], widely used in industry, do not provide a definition for traceability. A broadly accepted traceability type class...

Citation Context

...and Dependency links are qualified by authors, as product-related. – Gotel and Finkelstein in [8] introduce the Post-RS links, defined to trace the requirements from and back to RS, through artifacts in which they are distributed. Therefore, it is clear that those links include the Satisfies and Dependency links which are product-related. – Jarke in [11] also presents a classification which considers the Post-RS relations defined as relations among requirements to design and implementation. Post-RS links include the Satisfies and Dependency links which are productrelated. – Spanoudakis et al. [16] define the Overlap and Requires Feature In which are Dependency links and Requires Execution Of and Can Partially Realize which are Satisfies links, as authors themselves assure. Therefore, those four ones are product-related. – Van Vliet et al. [12] define a three type classification, more oriented to product family traceability: • Traceability between PF2 feature and Product feature is an Association relation of the Supports type and is divided into subtypes: ComposedOf (that is a Derived link, because the composed objects were derived from its father) and Requires-Excludes (that is a Depen...

Citation Context

...an still be qualified as emerging. 2.2 Pre and Post-traceability issue Some authors, such as Jarke [11] and Finkelstein et al. [8] are interested on pre-traceability issues, in order to provide the media to reopen and to rework previously closed issues and to management the requirements analysis process for producing a Requirement Specification, which really satisfies customer needs. However many other authors are more interested on post-traceability issues, as it is shown by approaches such as, Jarke et al. [15], Spanoudakis et al. [16], Van Vliet et al. [12], Cerbah et al. [5], Egyed et al. [7], Macfarlane et al. [14], Watkins et al. [19]. 2.3 Links Purpose The traceability relation existence must be justified in a system development project. Each trace must have a reason to be a system artifact to analyze, to save, to monitor, and to present to the project decision makers. Then, the following objectives have been identified: – From the business view point, to provide the often demanded linkage between the business and IT [11], to manage the contributions made by the stakeholders and to manage the system development responsibilities assigned to them [13]. – From the technical view p...

Citation Context

...order to make the most automatically possible the linkage tasks. 1 Requirement Specification 2.1 Process and Product-related Link Type – Jarke and Ramesh [15] present the Satisfies, Dependency, Evolution and Rationale classification. The Satisfies and Dependency links are qualified by authors, as product-related. – Gotel and Finkelstein in [8] introduce the Post-RS links, defined to trace the requirements from and back to RS, through artifacts in which they are distributed. Therefore, it is clear that those links include the Satisfies and Dependency links which are product-related. – Jarke in [11] also presents a classification which considers the Post-RS relations defined as relations among requirements to design and implementation. Post-RS links include the Satisfies and Dependency links which are productrelated. – Spanoudakis et al. [16] define the Overlap and Requires Feature In which are Dependency links and Requires Execution Of and Can Partially Realize which are Satisfies links, as authors themselves assure. Therefore, those four ones are product-related. – Van Vliet et al. [12] define a three type classification, more oriented to product family traceability: • Traceability bet...

Citation Context

...nd Post-traceability issue Some authors, such as Jarke [11] and Finkelstein et al. [8] are interested on pre-traceability issues, in order to provide the media to reopen and to rework previously closed issues and to management the requirements analysis process for producing a Requirement Specification, which really satisfies customer needs. However many other authors are more interested on post-traceability issues, as it is shown by approaches such as, Jarke et al. [15], Spanoudakis et al. [16], Van Vliet et al. [12], Cerbah et al. [5], Egyed et al. [7], Macfarlane et al. [14], Watkins et al. [19]. 2.3 Links Purpose The traceability relation existence must be justified in a system development project. Each trace must have a reason to be a system artifact to analyze, to save, to monitor, and to present to the project decision makers. Then, the following objectives have been identified: – From the business view point, to provide the often demanded linkage between the business and IT [11], to manage the contributions made by the stakeholders and to manage the system development responsibilities assigned to them [13]. – From the technical view point, the purposes are to ensure the requirem...

Citation Context

...nd is divided into subtypes: ComposedOf (that is a Derived link, because the composed objects were derived from its father) and Requires-Excludes (that is a Dependency link). • Traceability between Product FM3 and Product CM4 is an Association relation of Realizes type, thus is clear that is a Satisfies link. • Traceability between Product CM and Implementation is an Association relation of Implements type. Then is inferred this traceability relation is a Satisfies link. Therefore, the all three last links include the Satisfies and Dependency links which are product-related. – Letelier et al. [13], also consider satisfies links with the validatedBy, verifiedBy and assignedTo relations. They also consider the rationale link type with the rationaleOf relation. Even more, they consider modifies and reponsibleof traceability relations which are relations among stakeholders (system’s actors) and the different system specifications. Those relations are process-oriented. As the analysis shows, authors have developed traceability relations to cover goal, task and resources dependencies and requirements satisfaction issues, which are product-related links. Another issue that is starting to be a...

Citation Context

...s that work as an umbrella either for platform dependent (MDA) or, in our case, specific traceability models. An essential input for the work is the analysis of the current available literature since the traceability scheme should gather those common features of the traceability approaches analyzed, together with some proposals, in order to improve the process control of the traceability management. Under the MDA approach advantage of the models can be taken through roundtrip engineering between an abstract model of the system and describing the system architecture and or design, and the code [3]. Roundtrip is also as necessary in verification and validation processes and non-conformance management [9]. To provide automated support to these processes is one of the high level objectives of the research group where this work has been performed including general purpose software engineering environments and validation environments such as TOPEN [1]. Section 2 of this paper, Analysis of Traceability Approaches presents a summary of the analysis of several traceability proposals. Section 3, An Initial Proposal for a Traceability Scheme Specification is introduced, and finally in section 4,...

Citation Context

...s emerging. 2.2 Pre and Post-traceability issue Some authors, such as Jarke [11] and Finkelstein et al. [8] are interested on pre-traceability issues, in order to provide the media to reopen and to rework previously closed issues and to management the requirements analysis process for producing a Requirement Specification, which really satisfies customer needs. However many other authors are more interested on post-traceability issues, as it is shown by approaches such as, Jarke et al. [15], Spanoudakis et al. [16], Van Vliet et al. [12], Cerbah et al. [5], Egyed et al. [7], Macfarlane et al. [14], Watkins et al. [19]. 2.3 Links Purpose The traceability relation existence must be justified in a system development project. Each trace must have a reason to be a system artifact to analyze, to save, to monitor, and to present to the project decision makers. Then, the following objectives have been identified: – From the business view point, to provide the often demanded linkage between the business and IT [11], to manage the contributions made by the stakeholders and to manage the system development responsibilities assigned to them [13]. – From the technical view point, the purposes are t...

Citation Context

... have developed traceability relations to cover goal, task and resources dependencies and requirements satisfaction issues, which are product-related links. Another issue that is starting to be analyzed by several authors is product evolution and system development rationale such as [13, 15, 16]. 2 Product Family 3 Feature Map 4 Component Map Evolution issue is, at present, partially covered by configuration management tools, which are more focused on system object history and system configuration history. There are some research initiatives oriented to capture the rationale information as in [4, 17, 18]. The objectives are to maintain the rationale that is behind a product, to justify the actions taken and why and how the product development items have been introduced. But the status of this kind of work can still be qualified as emerging. 2.2 Pre and Post-traceability issue Some authors, such as Jarke [11] and Finkelstein et al. [8] are interested on pre-traceability issues, in order to provide the media to reopen and to rework previously closed issues and to management the requirements analysis process for producing a Requirement Specification, which really satisfies customer needs. Howeve...

Citation Context

...ar that those links include the Satisfies and Dependency links which are product-related. – Jarke in [11] also presents a classification which considers the Post-RS relations defined as relations among requirements to design and implementation. Post-RS links include the Satisfies and Dependency links which are productrelated. – Spanoudakis et al. [16] define the Overlap and Requires Feature In which are Dependency links and Requires Execution Of and Can Partially Realize which are Satisfies links, as authors themselves assure. Therefore, those four ones are product-related. – Van Vliet et al. [12] define a three type classification, more oriented to product family traceability: • Traceability between PF2 feature and Product feature is an Association relation of the Supports type and is divided into subtypes: ComposedOf (that is a Derived link, because the composed objects were derived from its father) and Requires-Excludes (that is a Dependency link). • Traceability between Product FM3 and Product CM4 is an Association relation of Realizes type, thus is clear that is a Satisfies link. • Traceability between Product CM and Implementation is an Association relation of Implements type. Th...

Citation Context

... have developed traceability relations to cover goal, task and resources dependencies and requirements satisfaction issues, which are product-related links. Another issue that is starting to be analyzed by several authors is product evolution and system development rationale such as [13, 15, 16]. 2 Product Family 3 Feature Map 4 Component Map Evolution issue is, at present, partially covered by configuration management tools, which are more focused on system object history and system configuration history. There are some research initiatives oriented to capture the rationale information as in [4, 17, 18]. The objectives are to maintain the rationale that is behind a product, to justify the actions taken and why and how the product development items have been introduced. But the status of this kind of work can still be qualified as emerging. 2.2 Pre and Post-traceability issue Some authors, such as Jarke [11] and Finkelstein et al. [8] are interested on pre-traceability issues, in order to provide the media to reopen and to rework previously closed issues and to management the requirements analysis process for producing a Requirement Specification, which really satisfies customer needs. Howeve...

Citation Context

...rocess control of the traceability management. Under the MDA approach advantage of the models can be taken through roundtrip engineering between an abstract model of the system and describing the system architecture and or design, and the code [3]. Roundtrip is also as necessary in verification and validation processes and non-conformance management [9]. To provide automated support to these processes is one of the high level objectives of the research group where this work has been performed including general purpose software engineering environments and validation environments such as TOPEN [1]. Section 2 of this paper, Analysis of Traceability Approaches presents a summary of the analysis of several traceability proposals. Section 3, An Initial Proposal for a Traceability Scheme Specification is introduced, and finally in section 4, a number of conclusions are provided. 2 Analysis of Traceability Approaches One of the aims of the analysis has been to identify a number of features that are the baseline for the available literature. The following features will be the starting point for the analysis and assessment and will be studied more in depth in the following subsections. 1. The ...

Citation Context

... have developed traceability relations to cover goal, task and resources dependencies and requirements satisfaction issues, which are product-related links. Another issue that is starting to be analyzed by several authors is product evolution and system development rationale such as [13, 15, 16]. 2 Product Family 3 Feature Map 4 Component Map Evolution issue is, at present, partially covered by configuration management tools, which are more focused on system object history and system configuration history. There are some research initiatives oriented to capture the rationale information as in [4, 17, 18]. The objectives are to maintain the rationale that is behind a product, to justify the actions taken and why and how the product development items have been introduced. But the status of this kind of work can still be qualified as emerging. 2.2 Pre and Post-traceability issue Some authors, such as Jarke [11] and Finkelstein et al. [8] are interested on pre-traceability issues, in order to provide the media to reopen and to rework previously closed issues and to management the requirements analysis process for producing a Requirement Specification, which really satisfies customer needs. Howeve...

Citation Context

...o a link set which specifies all the needed links for a specific development step baseline, and a set of traceability metrics in order to verify some quality requirements such as, completeness, functionality, reliability, usability, efficiency, etc. 3 An initial proposal for a Traceability Scheme Specification A Traceability Scheme Specification (TS) is an approach to specify the characteristics and needed items in order to be able to adequately support issues such management process, and facilitate maintainability, and project control. Some of the ideas could be in line with those underlying [6]. This issue will be further worked in the future. The Traceability Scheme Specification should include the following items: – A Traceability Link Dataset that will provide a wide basis to define traceability links, applicable a different kind of projects performed using different process models. – A Traceability Link Type Set (TYS), in order to define which kind of information each traceability link type will contain. – A Minimal Set of Traceability Links (MINS), in order to define all traceability link types, for a specific project or traceability baseline. – A MEtriCs Set for the MINS (MECS...