DOCSLIB.ORG

Cameo EA Userguide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

cameo Enterprise Architecture UPDM / DoDAF / MODAF / SysML / BPMN / SoaML USER GUIDE version 17.0 No Magic, Inc. 2010 All material contained herein is considered proprietary information owned by No Magic, Inc. and is not to be shared, copied, or reproduced by any means. All information copyright 2009-2010 by No Magic, Inc. All Rights Reserved. CONTENTS 1 GETTING STARTED WITH UPDM 12 What is UPDM 12 UPDM Architecture Viewpoints 12 UPDM Architecture Views 13 Summary of UPDM Views 14 View Taxonomy 16 2 DODAF 2.0 VIEWPOINTS AND VIEWS 17 All Views Viewpoint 17 AV-1 Overview and Summary Information 17 AV-2 Integrated Dictionary 18 Capability Viewpoint 19 CV-1 Vision 19 CV-2 Capability Taxonomy 20 CV-3 Capability Phasing 22 CV-4 Capability Dependencies 24 CV-5 Capability to Organizational Development Mapping 25 CV-6 Capability to Operational Activities Mapping 27 CV-7 Capability to Services Mapping 28 Project Viewpoint 29 PV-1 Project Portfolio Relationships 29 PV-2 Project Timelines 30 PV-3 Project to Capability Mapping 32 Operational Viewpoint 33 OV-1 High-Level Operational Concept Graphic 34 OV-2 Operational Resource Flow Description 35 OV-3 Operational Resource Flow Matrix 38 OV-4 Organizational Relationships Chart 40 OV-5 Operational Activity Model 42 OV-6a Operational Rules Model 45 OV-6b Operational State Transition Description 46 OV-6c Operational Event-Trace Description 48 Data and Information Viewpoint 50 DIV-1 Conceptual Data Model 50 DIV-2 Logical Data Model 52 DIV-3 Physical Data Model 53 Services Viewpoint 55 SvcV-1 Services Context Description 55 SvcV-2 Services Resource Flow Description 58 SvcV-3a Systems-Services Matrix 59 SvcV-3b Services-Services Matrix 61 SvcV-4 Services Functionality Description 62 SvcV-5 Operational Activity to Services Traceability Matrix 64 SvcV-6 Services Resource Flow Matrix 66 SvcV-7 Services Measures Matrix 67 SvcV-9 Services Technology and Skills Forecast 68 SvcV-10a Services Rules Model 70 SvcV-10b Services State Transition Description 71 SvcV-10c Services Event-Trace Description 73 Systems Viewpoint 74 3 CONTENTS SV-1 Systems Interface Description 74 SV-2 Systems Resource Flow Description 77 SV-3 Systems-Systems Matrix 79 SV-4 Systems Functionality Description 81 SV-5a Operational Activity to Systems Function Traceability Matrix 83 SV-5b Operational Activity to Systems Traceability Matrix 85 SV-6 Systems Resource Flow Matrix 87 SV-7 Systems Measures Matrix 88 SV-8 Systems Evolution Description 89 SV-9 Systems Technology & Skills Forecast 89 SV-10a Systems Rules Model 91 SV-10b Systems State Transition Description 92 SV-10c Systems Event-Trace Description 94 Standards Viewpoint 95 StdV-1 Standards Profile 95 StdV-2 Standards Forecast 97 3 MODAF VIEWPOINTS AND VIEWS 98 All Views Viewpoint 98 AV-1 Overview and Summary Information 98 AV-2 Integrated Dictionary 99 Strategic Viewpoint 100 StV-1 Enterprise Vision 101 StV-2 Capability Taxonomy 102 StV-3 Capability Phasing 103 StV-4 Capability Dependencies 105 StV-5 Capability to Organization Deployment Mapping 106 StV-6 Operational Activity to Capability Mapping 107 Acquisition Viewpoint 108 AcV-1 Acquisition Clusters 108 AcV-2 Programme Timelines 109 Operational Viewpoint 111 OV-1 High-Level Operational Concept Graphic 111 OV-2 Operational Node Relationship Description 112 OV-3 Operational Information Exchange Matrix 115 OV-4 Organizational Relationships Chart 116 OV-5 Operational Activity Model 117 OV-6a Operational Rules Model 119 OV-6b Operational State Transition Description 120 OV-6c Operational Event-Trace Description 121 OV-7 Information Model 123 Service Oriented Viewpoint 125 SOV-1 Service Taxonomy 125 SOV-2 Service Interface Specification 126 SOV-3 Capability to Service Mapping 127 SOV-4a Service Constraints 128 SOV-4b Service State Model 129 SOV-4c Service Interaction Specification 130 SOV-5 Service Functionality Flow 131 Systems View 132 4 CONTENTS SV-1 Resource Interaction Specification 133 SV-2 Resource Communications Description 135 SV-3 Resource Interaction Matrix 137 SV-4 Functionality Description 139 SV-5 Function to Operational Activity Traceability Matrix 140 SV-6 Systems Data Exchange Matrix 141 SV-7 Resource Performance Parameters Matrix 142 SV-8 Capability Configuration Management 144 SV-9 Technology & Skills Forecast 144 SV-10a Resource Constraints Specification 145 SV-10b Resource Constraints Specification 146 SV-10c Resource Event-Trace Description 148 SV-11 Physical Schema 149 SV-12 Service Provision 151 Technical Standards Viewpoint 152 TV-1 Standards Profile 152 TV-2 Standards Forecast 153 4 UPDM ELEMENTS 155 All Views Viewpoint 155 Actual Measurement 156 Actual Measurement Set 156 Alias 156 Architecture Metadata 157 Architectural Description 157 Architectural Reference 159 Climate 159 Defines Architecture 159 Definition 160 Environment 160 Environment Property 161 External Individual 161 External Type 162 Light Condition 162 Location 162 Measure Of Performance 163 Measurement 163 Measurement Set 164 Metadata 164 Performance Parameter 165 Performs 165 Physical Location 166 Same As 166 Capability Viewpoint and Strategic Viewpoint Elements 167 Achieves 167 Capability 168 Configuration No Longer Used 169 Configuration Deployed 170 Desired Effect 170 Enduring Task 171 5 CONTENTS Enterprise Goal 171 Enterprise Phase 172 Enterprise Vision 172 Exhibits Capability 173 Maps to Capability 173 Mission 174 Realizes Capability 174 Realizes Vision 175 Structural Part 175 Temporal Part 176 Vision 176 Vision Statement 177 Whole-Life Enterprise 177 Project Viewpoint and Acquisition Viewpoint Elements 177 Actual Project 178 Actual Project Milestone 179 Capability Increment Milestone 179 Manifests 180 Milestone Sequence 180 Out Of Service Milestone 181 Project 181 Project Milestone Type 182 Project Sequence 182 Project Status 183 Project Theme 183 Operational Viewpoint Elements 184 Actual Organization 185 Actual Organization Relationship 186 Actual Organization Role 186 Actual Person 187 Actual Post 187 Agreement 188 Arbitrary Relationship 188 Commands 188 Compatible With 189 Competence 189 Concept Role 190 Configuration Exchange 190 Energy 190 Energy Exchange 191 Entity Item 191 Entity Relationship 192 External Node 192 Fills Post 193 Guidance 193 High-Level Operational Concept 193 Needline 194 Information Element 195 Information Exchange 195 Known Resource 196 Logical Architecture 196 6 CONTENTS Logical Data Model 197 Materiel Exchange 197 Movement Of People 198 Node 198 Node Port 199 Node Role 199 Operational Activity 200 Operational Activity Action 201 Operational Activity Edge 201 Operational Constraint 202 Operational Event Trace 202 Operational Message 202 Operational Node 203 Operational Parameter 203 Operational Rule 204 Operational State Machine 204 Organization 204 Organizational Exchange 205 Owns Process 206 Performer 206 Performer Role 207 Performs At 207 Person 207 Post 208 Problem Domain 209 Provides Competence 209 Provides Skill 209 Requires Competence 210 Rule 210 Skill 210 Standard Operational Activity 211 Services Viewpoint and Service Oriented Viewpoint Elements 211 Expose 212 Material 212 Service Attribute 213 Service Channel 213 Service Function 214 Service Function Action 214 Service Interaction 215 Service Interface 215 Service Message 216 Service Operation 217 Service Operation Action 217 Service State Machine 218 Supports Operational Activity 218 Service Parameter 219 Service Policy 219 Systems Viewpoint Elements 220 Capability Configuration 221 Controls 222 Data Element 222 7 CONTENTS Data Exchange 223 Equipment 224 Fielded Capability 224 Forecast 225 Function 225 Function Action 226 Function Edge 227 Function Parameter 227 Hosted Software 227 Human Resource 228 Implements Operational 228 Internal Data Model 229 Part 229 Physical Data Model 230 Platform 230 Post Role 231 Protocol 231 Request Point 232 Resource Artifact 233 Resource Component 233 Resource Connector 234 Resource Constraint 234 Resource Event Trace 235 Resource Interaction 235 Resource Interface 236 Resource Message 236 Resource Port 237 Resources State Machine 237 Service Point 238 Software 238 Standard 239 Sub Organization 240 Sub System Part 241 System 241 System Connector 242 System Function 242 System Function Action 243 System Function Edge 243 Systems Node 243 Technology Forecast 244 Used Configuration 244 Standards Viewpoint and Technical Standards Viewpoint Elements 245 Entity Attribute 245 Protocol Layer 245 Standard Configuration 246 5 USING UPDM 247 Generic Procedures 247 Handling tables 247 Generating reports 249 8 CONTENTS Using libraries 252 Using SysML elements in UPDM 253 Applying Actual Measurements 253 Applying Military symbols 254 Converting model between Enterprise Architecture Frameworks 256 Filtering Operational Activities, System Functions, and Functions 256 View-specific Procedures 257 AcV-1 procedures 258 Creating AcV-1 diagram 258 Building AcV-1 matrix 259 AcV-2 procedures 260 Creating AcV-2 diagram 260 Applying DLOD status 261 Removing DLOD Status 262 CV-1 procedures 262 Creating CV-1 diagram 262 CV-2 procedures 262 Creating CV-2 diagram 263 CV-4 procedures 263 Creating CV-4 diagram 263 CV-6 procedures 263 Building CV-6 matrix 263 CV-7 procedures 264 Building CV-7 matrix 264 DIV-1 procedures 264 Creating DIV-1 diagram 264 DIV-2 procedures 264 Creating DIV-2 diagram 265 DIV-3 procedures 265 Creating DIV-3 diagram 265 OV-1 procedures 265 Creating OV-1 diagram 265 OV-2 procedures 266 Creating OV-2 diagram 266 Creating Operational Exchanges in OV-2 diagram 267 OV-3 procedures 267 Creating OV-3 table 267 OV-4 procedures
Recommended publications
  • A System Model for Managing Requirement Traceability Matrices Via Statistical Artifact Change Analysis Benjamin J

    A System Model for Managing Requirement Traceability Matrices Via Statistical Artifact Change Analysis Benjamin J

    A System Model for Managing Requirement Traceability Matrices via Statistical Artifact Change Analysis Benjamin J. Deaver and LiGuo Huang, Southern Methodist University, Dallas Introduction and Motivation Requirement Traceability Matrix – Gantt Open Source Software Project The Value of the Requirements Traceability Matrix The system Requirement Traceability Matrix (RTM) is primarily used for ensuring Our initial dataset for evaluation is taken from the Gantt Open Source PROCEDURE Kannenberg et al identify the underlying necessity of the Requirements Traceability Matrix and the underlying effect on that all requirements are fulfilled by the system artifact deliverables and the Software Project (http://www.ganttproject.biz). The initial trace data 1. Identify the taxonomy of change for a given domain (Systems Engineering, project management, process visibility, verification and validation, as well as project maintainability. Over time, the management of change to deliverables with respect to impact on other systems. In has been provided to us by Dr. Alexander Egyed at the Institute for SoS Engineering, Software Engineering). the systems engineering and system of systems (SoS) engineering landscapes, the Systems Engineering and Automation at Johannes Kepler University. Requirements Traceability Matrix provides significant insight in to the internal workings of the relationships between RTM is a tool that is useful at time of creation, but requires constant maintenance in Additional traces of requirements to code for subsequent Gantt versions 2. Identify and classify changes between static versions of the product. requirements and deliverable artifacts. a frequently changing landscape to maintain the original level of validity. The are being created using similar methods to the original collections 3. Generate Requirements Trace Matrixes for each static version of the product dynamic nature of systems and SoS engineering landscapes requires that a RTM be performed by Dr.
  • Traceability Establishment and Visualization of Software Artefacts in Devops Practice: a Survey

    Traceability Establishment and Visualization of Software Artefacts in Devops Practice: a Survey

    (IJACSA) International Journal of Advanced Computer Science and Applications, Vol. 10, No. 7, 2019 Traceability Establishment and Visualization of Software Artefacts in DevOps Practice: A Survey D. A. Meedeniya1, I. D. Rubasinghe2, I. Perera3 Dept. of Computer Science and Engineering, University of Moratuwa, Sri Lanka Abstract—DevOps based software process has become the artefacts in the SDLC [2][3]. There are different forms of popular with the vision of an effective collaboration between the relationships between the homogeneous and heterogeneous development and operations teams that continuously integrates software artefacts. Some artefacts may be highly coupled, and the frequent changes. Traceability manages the artefact some may depend on other artefacts in different degrees, consistency during a software process. This paper explores the unidirectionally or bidirectionally. Thus, software artefacts trace-link creation and visualization between software artefacts, consistency management helps to fine-tune the software existing tool support, quality aspects and the applicability in a process. The incomplete, outdated software artefacts and their DevOps environment. As the novelty of this study, we identify the inconsistencies mislead both the development and maintenance challenges that limit the traceability considerations in DevOps process. Thus, artefact management is essential such that the and suggest research directions. Our methodology consists of changes are accurately propagated to the impacted artefacts concept identification, state-of-practice exploration and analytical review. Despite the existing related work, there is a without creating inconsistencies. Traceability is the potential to lack of tool support for the traceability management between relate artefacts considering their relationships [4][5]; thus, a heterogeneous artefacts in software development with DevOps solution for artefact management.
  • Requirements Traceability Practices Guide

    Requirements Traceability Practices Guide

    CDC UNIFIED PROCESS PRACTICE GUIDE REQUIREMENTS TRACEABILITY Document Purpose The purpose of this document is to provide guidance on the project management practice of Requirements Traceability and to describe the practice overview, requirements, best practices, activities, and key terms related to these requirements. In addition, templates relevant to this practice are provided at the end of this guide. Practice Overview Requirements traceability is an activity that is one part of an overarching requirements management practice and extends from requirements definition through to implementation. Requirements tracing is used to ensure that each step of the product’s development process is correct, conforms to the needs of prior and next steps, and conforms to the defined requirements. Requirements tracing is a technique that helps to ensure that the project delivers what stakeholders expect. If applied correctly requirements tracing is a practice that can greatly increase the quality and reliability of a project’s final product while minimizing costly rework resulting from requirements errors. Requirements tracing defines the ability to describe and follow the life of a requirement, in both a forward and backward direction, ideally through each step of the entire product’s life cycle. This is done by documenting and tracking traceability relationships between requirements. A traceability relationship is a dependency relationship between project and/or product elements. Similar to the way a dynamic project schedule may react to a change in one task, a change to a requirement element may also have a rippling effect on other elements. A well documented traceability relationship clearly defines requirement dependencies and allows for analysis of how changes in requirements affect other requirements and the project as a whole.
  • Systems Engineering Guided Tour

    Systems Engineering Guided Tour

    Systems Engineering Guided Tour Copyright © 1993–2007 Vitech Corporation. All rights reserved. No part of this document may be reproduced in any form, including, but not limited to, photocopying, translating into another language, or storage in a data retrieval system, without prior written consent of Vitech Corporation. Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.277-7013. Vitech Corporation 2070 Chain Bridge Road, Suite 100 Vienna, Virginia 22182-2536 703.883.2270 FAX: 703.883.1860 Customer Support: [email protected] www.vitechcorp.com CORE® is a registered trademark of Vitech Corporation. Other product names mentioned herein are used for identification purposes only, and may be trademarks of their respective companies. Revised Date: August 2007 ii Table of Contents Creating External Systems ................................ 32 ................... 1 1 Getting Started with CORE Defining the Context Component ...................... 34 The Benefits of CORE ....................................... 1 Adding Detail to the External Systems .............. 35 Installing CORE................................................. 2 Viewing a Physical Hierarchy ............................ 36 Overview of the CORE Product Family ............. 2 Creating Function Elements .............................. 37 Key Concepts .................................................... 3 Establishing
  • Managing Project Requirements

    Managing Project Requirements

    MANAGING PROJECT REQUIREMENTS Course Materials The causes of the majority of failed IT projects can be traced to poor definition and understanding of requirements. Changing requirements causes more delays than any other cause. If you want to improve project performance you must improve the way you define and manage requirements. Requirements must be a clear description in a common language. They are the bridge between the customer who will describe, pay for, and use the solution and the technical community who will specify and provide the solution. Requirements must be unique, normalized, linked, complete, consistent, bounded, modifiable, configurable and granular. Participants will cultivate the skills needed to elicit full business information from the right stakeholders and, learn structured techniques to identify and present business requirements clearly and effectively. Table of Contents Lesson 1: Introduction to Requirements Management ......................................................................... 1 Topic 1: Requirements Definition ....................................................................................................... 2 Exercise 1.1 Evaluating Requirements ............................................................................................... 5 Topic 2: The Project Environment ...................................................................................................... 6 Topic 3: Understanding the Project Charter .....................................................................................
  • Verification and Validation

    Verification and Validation

    Requirements Verification and Validation In4Mtx 113 February 2010 Agenda Definitions of V&V Why do we care? Verification Methods VCRMs Verification Techniques Success Criteria Early Verification Planning in the RE Process What Makes Requirements Verification Difficult 2 Definitions Verification: The process of determining whether or not the products of a given phase of the software development cycle fulfill the requirements established during the previous phase. Validation: The process of evaluating software at the end of the software development process to ensure compliance with software requirements. These definitions are taken from : Verifying and validating software requirements and design specifications. Boehm, B W IEEE Software. Vol. 1, no. 1, pp. 75-88. 1984 3 Basically… Verification: "Am I building the product right?" Validation: "Am I building the right product?" 4 Why do we care? Outputs Data/Models In Requirements Database Directly Drives Verifies 5 Remember this process? Inspection Individual Defect evaluation RD planning reviewing at review meetings consolidation Figure 5.1 – Requirements inspection, review, and consolidation Your testers are key stakeholders 6 Verification Methods Industry accepted methods are: Test Analysis Demonstration Inspection S Any guesses to the “S” in T.A.D.I.S? 7 VCRM Verification Cross Reference Matrix Supplemental to the RD This will be required on any RD you’ll ever produce. Guarantee it: 100% Can be combined with the Requirements Traceability Matrix 8 Sample VCRM Req ID Requirement Verification Allocation Success Criteria Method 1 The train doors shall remain D, T Controller SW Once ground speed >= 1mph, closed during all operational train doors lock and remain activities. closed.
  • EPRI TR 107330, "Requirements Compliance Traceability Matrix,"

    EPRI TR 107330, "Requirements Compliance Traceability Matrix,"

    HF Controls HF CONTROLS CORPORATION HFC-6000 Product Line U--Nuclear Qualification Project ERD 111 EPRI TR 107330 REQUIREMENTS COMPLIANCE TRACEABILITY MATRIX RR901-000-10 Rev C Effective Date: 12/14/2009 Author: Ivan Chow Reviewer: Jonathan Taylor Approval: Allen Hsu Copyright© 2009 HF Controls Corporation 1 of 66 ERD i 11 EPRI TR 107330 Requirement Compliance Traceability Matrix Revision History Date Revision Author Changes 2/3/05 A0 J Taylor Draft 3/1/05 A J Taylor Incorporate review comments 11/19/09 B I. Chow Resolved the inconsistencies about undetectable errors and remedial implementations in RR901-000-01 Rev. B and PP901-000-01 Rev. C SCR 2612, CR 2009-0540 12/9/09 C I. Chow Revised and based on new documented information from the qualification summary report and reconstructed requirement documentations. Table of Contents 1.0 Introduction ...................... ............................................................................... 3 2.0 Traceability M atrix ....................................................................................... 3 3.0 Glossary .................................................................................................... 3 3.1 Traceability M atrix Com pliance ................................................................ 3 3.2 .Abbreviations .............................................................................................. 4 4.0 R eferences .................................................................................................... 5 List of Tables Table 1 - EPRI
  • Software Requirements Specification (SRS) Tailoring Standards

    Software Requirements Specification (SRS) Tailoring Standards

    CS 330 Software Engineering Software Requirements Specification (SRS) Tailoring Standards The following description provides the basic document organization, and required information (see the Document Style Guidelines and Standards for information about format). The main thing to remember is that the SRS must contain a Requirements Traceability Matrix (RTM). Each requirement is uniquely identified (using a number) in the body of the document and must be called out in the RTM. Each requirement will use the verb “shall.” Otherwise the statement shall not be considered a requirement. Each item below should be considered required as a major element or section in the SRS. The standard referred to here is IEEE Std. 830-1993. Title Page Abstract1 Frontmatter 1. Introduction (see section 5.1 of the standard for details) 1.1. Purpose 1.2. Scope 1.3. Definitions, acronyms, and abbreviations 1.4. References 1.5. Overview 2. Overall description (see section 5.2 of the standard for details) 2.1. Product perspective 2.2. Product functions 2.3. User characteristics 2.4. Constraints 2.5. Assumptions and dependencies 3. Specific Requirements (see section 5.3 and/or appendix A of the standard for details) 4. References Appendixes Definitions, Acronyms and Abbreviations Requirements Traceability Matrix Schedule (with a description of milestones and deliverables) Walk-through Check List Coding Standards Special Purpose Items: Description of the external items pictured in context diagram Other Special Purpose Items (e.g. JAVA / C++ API; Screen Shots of a GUI) Index (optional) 1 Include in the abstract a complete overview of the product (purpose, goals, and design constraints) including your chosen design methodology, any exceptions to the stated requirements.
  • ALS V&V Plan

    ALS V&V Plan

    Westinghouse Non-Proprietary Class 3 ALS V&V Plan 6002-00003-NP Rev. 8 January 2013 APPROVALS Function Name and Signature Author Simon Lowenfeld* Fellow Engineer, Independent Verification and Validation II Reviewer Jim Pak* Principal Engineer, Independent Verification and Validation I Approver Marci Maher* Manager, Independent Verification and Validation I *Refer to Release Record for Electronic Approval WESTINGHOUSE NON-PROPRIETARY CLASS 3 © 2013 Westinghouse Electric Company LLC All Rights Reserved ALS V&V Plan LIST OF CONTRIBUTORS Revision Name and Title 7 Marci Maher Acting Manager, Independent Verification and Validation I 7 Secil Karaaslan Senior Engineer, Independent Verification and Validation I 7 Jeff Vance Senior Engineer, Independent Verification and Validation I 7 Jim Pak Principal Engineer, Independent Verification and Validation I 8 Marci Maher Manager, Independent Verification and Validation I 8 Warren Odess-Gillett Fellow Engineer, Licensing 8 Marsha White Senior Technical Writer, Technical Communications Template Version 2.2 6002-00003-NP Rev. 8 i Westinghouse Non-Proprietary Class 3 ALS V&V Plan REVISION HISTORY RECORD OF CHANGES a, c , , e 6002-00003-NP Rev. 8 ii Westinghouse Non-Proprietary Class 3 ALS V&V Plan REVISION HISTORY (cont.) RECORD OF CHANGES (cont.) DOCUMENT TRACEABILITY & COMPLIANCE Created to Support the Following Document(s) Document Number Revision N/A OPEN ITEMS Item Description Status None 6002-00003-NP Rev. 8 iii Westinghouse Non-Proprietary Class 3 ALS V&V Plan TABLE OF CONTENTS Section Title Page
  • Traceability in Agile Software Projects

    Traceability in Agile Software Projects

    Traceability in Agile software projects Master of Science Thesis in Software Engineering & Management VUONG HOANG DUC University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering Göteborg, Sweden, May 2013 The Author grants to Chalmers University of Technology and University of Gothenburg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Traceability in Agile software projects VUONG.HOANG DUC VUONG. HOANG DUC, May 2013. Examiner: CHRISTIAN.BERGER University of Gothenburg Chalmers University of Technology Department of Computer Science and Engineering SE-412 96 Göteborg Sweden Telephone + 46 (0)31-772 1000 ABSTRACT Context: Software applications have been penetrating every corner of our daily life in the past decades. This condition demands high quality software. Traceability activities have been recognized as important factors supporting various activities during the development process of a software system with the aim of improving software quality.
  • On Human Analyst Performance in Assisted Requirements Tracing: Statistical Analysis

    On Human Analyst Performance in Assisted Requirements Tracing: Statistical Analysis

    On Human Analyst Performance in Assisted Requirements Tracing: Statistical Analysis Alex Dekhtyar∗, Olga Dekhtyar†, Jeff Holden∗, Jane Huffman Hayes‡, David Cuddeback∗, and Wei-Keat Kong‡ ∗ Department of Computer Science, Cal Poly, San Luis Obispo, CA, USA Email: {dekhtyar, jholden}@calpoly.edu, [email protected] †Department of Statistics, Cal Poly, San Luis Obispo, CA, USA. Email: [email protected] ‡Department of Computer Science, University of Kentucky, Lexington, KY, USA. Email: [email protected], [email protected] Abstract—Assisted requirements tracing is a process in what tests to rerun. With all the advantages that tracing could which a human analyst validates candidate traces produced offer to NDFC, why are they not using such a tool/process? by an automated requirements tracing method or tool. The First, many organizations undertake manual tracing, per- assisted requirements tracing process splits the difference between the commonly applied time-consuming, tedious, and haps with the assistance of a word processing tool or error-prone manual tracing and the automated requirements spreadsheet. Such a process is boring, tedious, and time- tracing procedures that are a focal point of academic studies. consuming. As a result, it is also error prone [11]. Second, In fact, in software assurance scenarios, assisted requirements once traceability is established for a project, the project arti- tracing is the only way in which tracing can be at least partially facts quickly change, thus necessitating traceability updates. automated. In this paper, we present the results of an extensive 12 month study of assisted tracing, conducted using three Third, there is a lack of an industry-accepted tracing tool.
  • 5 Tips on Traceability to Skillfully Control Change and Improve Quality

    5 Tips on Traceability to Skillfully Control Change and Improve Quality

    INNOVATION IN ACTION Connect the Dots: 5 Tips on Traceability to Skillfully Control Change and Improve Quality. Overview Traceability Helps You Stay Connected, Manage Change & Improve Quality. Yes! What is traceability? It sounds complicated. Why do teams do it? It sounds like a lot of work. Is it really worth the effort? Good questions. The short answer: Yes. And, here’s why it’s so important: Change happens. If managed poorly, change will wreak havoc on even the most talented and experienced development teams. If managed skillfully, using tools like traceability, teams are better equipped to assess the impact of changes, track the full history, keep everyone in sync and (deep breath) consistently improve the quality of the products being built – every project, every release. Sign me up. In some industries, traceability isn’t an option, it’s mandated. Did You Know? “Companies We’d recommend that regardless of the industry you’re in or the process you use – whether you’re building components for with mature requirements commercial airplanes using waterfall or designing the next management and traceability killer iPhone app using an agile method –traceability is a best practice that will benefit your team greatly. processes achieve 75% higher In this paper, our goals are to demystify traceability and its success rates.” – IAG, Business related concepts, and provide five practical tips to help you Analysis Benchmark, 2009 take control and keep everyone in sync. The Five Tips for Mastering Traceability: 1. Create relationships to connect everyone and everything together with Trace Relationships 2. Ensure you have proper coverage using a Traceability Matrix 3.