SEG 3101 Fall 2018 Requirements Management Daniel Amyot

SEG 3101 (Fall 2018) Requirements Management Daniel Amyot, University of Ottawa Based on material from: Kotonya & Sommerville, Z. Zhang, IBM, S. Somé 2008, D. Amyot 2008 -2017, G. Mussbacher 2009, 2017, J. Maxwell 2012

Table of Contents • Introduction to Requirements Management • Traceability • Baselines • Change Management • Requirements Management Tools SEG 3101. Requirements Management. 2

Introduction to Requirements Management

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Change is Inevitable • Better understanding of the domain: new requirements become apparent • Everything else is changing (business, context, technologies, markets…) • • Changing customer priorities, new needs, new competitors • Collaborating systems may change • Changing laws, regulations, polices, etc. Requirements errors, conflicts, and inconsistencies Technical, schedule, or cost problems Technical or business opportunities (cloud, Io. T, blockchains…) • As difficult to control as it is inevitable! • Possible responses to change • Ignore it… • Add, modify, or remove requirements SEG 3101. Requirements Management. 4

Introduction Traceability Baselines Change Management Requirements Management Tools Feature Survival Chart K. Wnuk, B. Regnell, L. Karlsson: Visualization of Feature Survival in Platform ‐Based Embedded Systems Development for Improved Understanding of Scope Dynamics, 3 rd International Workshop on Requirements Engineering Visualization REV 08, Barcelona, Spain SEG 3101. Requirements Management. 5

Introduction Traceability Baselines Change Management Requirements Management Tools Quantitative Analysis of Feature Survival Charts Reasons for scope exclusion resources SEG 3101. Requirements Management. 6

Increasing U. S. Healthcare Regulation HIPAA CCHIT MU Stage. Meta 1 Stage 2 MU HITECH Standards (ARRA) Rule 1996 2007 2008 2009 DEA EPCS Various State Laws 2010 2011 2012 Nw. HIN HIPAA Data Governance Omnibus Regs Breach Notification … and each of these laws evolves too (multiple versions!) J. C. Maxwell, A. I. Antón, P. Swire, "Managing Changing Compliance Requirements by SEG 3101. Requirements Management. Predicting Regulatory Evolution", Intl. Conf. on Requirements Engineering, 2012.

Introduction Traceability Baselines Change Management Requirements Management Tools Some Problems Due to Changing Requirements • Requirements changing towards the end of development without any impact assessment • Also known as requirements/feature creep • Unmatched/outdated requirements specifications causing confusion and avoidable rework • “Which version is the right one already? ” • Time spent coding, writing test cases or documentation for requirements that no longer exist SEG 3101. Requirements Management. 8

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Management • A systematic approach to eliciting, organizing, and documenting the requirement of the system, and a process that establishes and maintains agreement between the customer and the project team on the changing requirements of the system. 1 [1] Leffingwell & Widrig 1999, p. 16 SEG 3101. Requirements Management. 9

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Management Activities • Requirements management includes all activities intended to maintain the integrity and accuracy of expected requirements • Manage changes to agreed requirements • Manage changes to baseline (increments) • Keep project plans synchronized with requirements • Control versions of individual requirements and versions of requirements documents • Manage relationships between requirements • Managing the dependencies between the requirements and other documents/artefacts produced in the systems engineering process • Track requirements status SEG 3101. Requirements Management. 10

Introduction Traceability Baselines Change Management Requirements Management Tools From Management to Tools • Changes lead to a need for management • There is no management without: • Traceability • Baselines enabling comparisons • From a practical point of view, there is no traceability or management without appropriate tools In theory, practice and theory are similar… But in practice they are different SEG 3101. Requirements Management. 11

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Volatility • Measure: number of requirements changes (addition, deletion, modification) in a specified time interval • Some requirements are usually more subject to change than others • Stable requirements are concerned with the essence of a system and its application domain • Derived from the client’s principal business activities or the domain model • They change more slowly than volatile requirements • E. g. , a hospital will always have doctors, nurses, patients to deal with… • Volatile requirements are specific to the instantiation of the system in a particular environment for a particular customer at a particular time • E. g. , in a hospital, a nurse may want the software system to support the a specific way of inputting and getting information. SEG 3101. Requirements Management. 12

Introduction Traceability Baselines Change Management Requirements Management Tools Expectations of Requirements Management (1) • Identification of individual requirements • Traceability from highest level requirements to implementation • Established via links through a requirements database • Links between requirements and design models, tests, code… • Coverage and consistency analysis • What are the traceability policies? What types of links? From where? To where? • Impact assessments of proposed changes • Analysis tools let you see which other requirements (and other linked artifacts) will be affected by a change SEG 3101. Requirements Management. 13

Introduction Traceability Baselines Change Management Requirements Management Tools Expectations of Requirements Management (2) • Controlled access to current project information • A shared database ensures that all users are working with current data (consistency, parallel access) • A central repository allows all users to see the information that they need to see (visibility) • Change control • Change proposal system implements controlled process for managing change • How do we collect, document, and address changes? • Deployment of required tool support All of this requires planning! SEG 3101. Requirements Management. 14

Introduction Traceability Baselines Change Management Requirements Management Tools Identification of Requirements • It is essential for requirements management that every requirement has a unique identification • The most common approach is requirements numbering based on chapter/section in the requirements document (2. 1, 3. 2. 4, …) • There are several problems with this approach • Numbers cannot be unambiguously assigned until the document is complete • Assigning chapter/section numbers is an implicit classification of the requirements may mislead readers of the document into thinking that the most important relationships are with requirements in the same section SEG 3101. Requirements Management. 15

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Identification Techniques • Dynamic renumbering • Some word processing systems allow for automatic renumbering of paragraphs and the inclusion of cross references • As you reorganise your document and add new requirements, the system keeps track of the cross references and automatically renumbers your requirements depending on its chapter, section, and position within the section. But… • Database record identification • When a requirement is identified, it is entered in a requirements database and a database record identifier is assigned which is then used for all subsequent references to the requirement • Symbolic identification • Requirements can be identified by giving them a symbolic name which is associated with the requirement itself (e. g. , SEC 1, SEC 2, SEC 3… may be used for security requirements). But… it is difficult to give only one category to a requirement • Conclusion: avoid encoding information in the ID! SEG 3101. Requirements Management. 16

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Have Attributes! • Apart from an identifier, requirements should have attributes that establish context and background, and go beyond the requirement description • For filtering, analysis, metrics… • Creation date, Last update, Author, Stakeholders (Owners / Source) • Version number • Status, Priority, Importance, Stability • Rationale, Comments • Acceptance criteria • Subsystem / Product release number • … • The more complex the project, the richer the attributes… • Many attributes are predefined in RM tools, others are defined by requirements engineers as required by the project SEG 3101. Requirements Management. 17

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Attributes • Classes and attributes of a requirements management database • Select only the necessary attributes! SEG 3101. Requirements Management. 18

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Objects and Attributes SEG 3101. Requirements Management. 19

Introduction Traceability Baselines Change Management Requirements Management Tools Confidence/Certainty Attribute • One must distinguish requirements that are fully certain from the others • Otherwise: too many constraints, or loss of trust in all requirements • Confidence: Scale sample • Full, High, Average, Low, Very low • Low-confidence requirements: • Might be delayed until more certain • Will provide more freedom to designers for being creative • Creativity at the design level is also important! • See this presentation: How Google Works… • R. Mohanani et al. : “Requirements Fixation” (ICSE 2014 version: http: //dl. acm. org/citation. cfm? id=2568235) SEG 3101. Requirements Management. 20

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Statuses • Help manage the requirement lifecycle • Their number and nature depend on the process in place • Example of a set of statuses: • Proposed: by some stakeholder • Approved: part of baseline, committed to implement • Rejected: after evaluation • Implemented: designed and implemented • Verified: Relevant tests have passed • Deleted: Removed from list • RM includes amongst its tasks the tracking of the status of all requirements during the project SEG 3101. Requirements Management. 21

Introduction Traceability Baselines Change Management Requirements Management Tools Version Control • Another essential aspect of requirements management • Every version of a requirement needs to be uniquely identified • The last version of a requirement must be available to all team members • Changes need to be documented and clearly communicated • A version identifier must be updated with every change to the requirement • Requirements documents should include • A revision history: changes, dates, by whom, why. . . • Standard markers for revisions (e. g. , strikethrough or underlined text, coloring, line markers…) • Version control tool may be used • To store and manage the revision history • To store justifications (to add, modify, delete, reject a requirement) SEG 3101. Requirements Management. 22

Introduction Traceability Baselines Change Management Requirements Management Tools Dilbert on Requirements Management SEG 3101. Requirements Management. 23

Traceability

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability? • "Can I ask you some questions? " • "By all means. " • "Okay. Well, for starters I'll have who, what, when and where and then wither, whence and wherefore for a follow-up, and then one bit side-order of why. " Source: Zaphod Beeblebrox & Zarniwoop, The Hitchhiker's Guide to the Galaxy SEG 3101. Requirements Management. 25

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability Quotes (1) • A link or relationship defined between entities. 1 • Requirements traceability refers to the ability to describe and follow the life of a requirement, in both forwards and backwards direction (i. e. , from its origins, through its development and specification, to its subsequent deployment and use, and through all periods of ongoing refinement and iteration in any of these phases)”. 2 • A software requirements specification is traceable if the origin of each of its requirements is clear and if it facilitates the referencing of each requirement in future development or enhancement documentation. 3 [1] Watkins and Neal, 1994; [1] Gotel & Finkelstein, 1994; [3] IEEE Standard 830 -1998 SEG 3101. Requirements Management. 26

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability Quotes (2) • Traceability is often mandated by contracts and standards. 1 • E. g. , military and aerospace • One cannot manage what cannot be traced. 2 • A requirement is traceable if you can discover who suggested the requirement, why the requirement exists, what requirements are related to it, and how that requirement relates to other information such as systems designs, implementations and user documentation • Traceability information helps assess the impact of changes to requirements, connecting these requirements as well as requirements for other representations of the system. 3 [1 -2] Watkins and Neal, 1994; [3] Kotonya and Sommerville, 1998; SEG 3101. Requirements Management. 27

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability in the HIPPA Law (USA) SEG 3101. Requirements Management. 28

Introduction Traceability Baselines Change Management Requirements Management Tools Benefits of Traceability • Impact analysis now possible! • Change control • Process monitoring (e. g. , missing links indicate completion level) • Improved software quality (make changes correctly and completely) • Reengineering (define traceability links is a way to record reverse engineering knowledge) • Risk reduction (e. g. , if a team member with key knowledge leaves) • Supports the verification process (certification, localization of defects and conflicts…) SEG 3101. Requirements Management. 29

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability and Legal Conflicts [Maxwell et al. , RE 2011] SEG 3101. Requirements Management. 30

Introduction Traceability Baselines Change Management Requirements Management Tools Typical Project Data Change Requests Regulatory Codes System Requirements User Requirements Design Documentation Sub-System Requirements Component Requirements Fault Logs Project Plans Stakeholders Source Code in packages, components, and versions. . SEG 3101. Requirements Management. 31

Introduction Traceability Baselines Change Management Requirements Management Tools Project Intelligence: Challenges Necessary support for Software Analytics Distributed data Data Connectivity SELECT DISTINCT regulatory_code. * FROM ((regulatory_code LEFT OUTER JOIN tm_regulatory_code 2 software _requirement ON (regulatory_code. id = tm_regulatory_code 2 software _requirement_id)) LEFT OUTER JOIN software_requirement ON (software_ requirement. it=tm_regulatory_ code 2 software_requirement. software_re quirements_id WHERE regulatory_code. relevant='true' AND software_requirement. id IS NULL; Heterogeneous data Queries SEG 3101. Requirements Management. 32

Introduction Traceability Baselines Change Management Requirements Management Tools Queries: Regulatory Control Regulatory Codes System/subsystem level requirements Satisfies relevant codes Which regulatory codes are relevant to my system? Are all relevant regulatory codes fully addressed in the as-built system? How do changes in the updated codes impact my system? Realizes Validates Code Tests Test cases (unit, integration, acceptance) SEG 3101. Requirements Management. 33

Introduction Traceability Baselines Change Management Requirements Management Tools Queries: Project Test Status What percentage of acceptance tests have passed? Should we invest further time testing? Source Code in packages, components, and versions. . Fault Logs Have any components repeatedly failed acceptance tests? Do any of the reused components have a history of post-release faults? Project Plans Who is a domain expert for this problematic component? SEG 3101. Requirements Management. 34

Introduction Traceability Baselines Change Management Requirements Management Tools Queries: Project Management Are there any bottlenecks in the continuous integration? How well are we performing on the current project? How did the recent process change impact the delivery stream? SEG 3101. Requirements Management. 35

Introduction Traceability Baselines Change Management Requirements Management Tools What questions do you have? Project ROI Safety Architecture Process Triage Code Quality Compliance Tests Quality Faults SEG 3101. Requirements Management. 36

Introduction Traceability Baselines Change Management Requirements Management Tools What Practitioners Say About Traceability Isn’t it some heavyweight thing? I think it is a made-up problem. We need traceability for certification! We often construct all of the links after development is over. Fast paced agile/ business-oriented projects Benefits extend to non-safety critical projects Support for safety-critical agile-projects and/or for continual certification Slower-paced, carefully planned safety-critical projects Traceability Techniques SEG 3101. Requirements Management. 37

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability Difficulties • Various stakeholders require different information • Huge amount of requirements traceability information must be tracked and maintained • Manual creation of links is very demanding • Likely the most annoying problem • Specialized tools must be used • Integrating heterogeneous models/information from/to different sources (requirements, design, tests, code, documentation, rationales…) is not trivial • Requires organizational commitment (with an understanding of the potential benefits) SEG 3101. Requirements Management. 38

Introduction Traceability Baselines Change Management Requirements Management Tools Representation – Traceability Matrix • Visualize/define links between pairs of elements • E. g. , requirements to requirement, requirement to use case, requirement to test case… • One matrix per defined relationships between pairs • E. g. , depends on, refines, prevents, implements, tests. Depends On R 1 R 2 R 1 R 3 R 4 * * R 2 R 3 R 4 R 5 * R 5 R 6 * * * R 6 SEG 3101. Requirements Management. 39

Introduction Traceability Baselines Change Management Requirements Management Tools Sample Traceability Matrix SEG 3101. Requirements Management. 40

Introduction Traceability Baselines Change Management Requirements Management Tools Representation – Traceability List • Traceability matrices become more of a problem when there are hundreds or thousands of requirements as the matrices become large and are sparsely populated • A simplified form of a traceability matrix may be used where, along with each requirement description, one or more lists of the identifiers of related requirements are maintained Requirement Depends On R 1 R 3, R 4 R 2 R 5, R 6 R 3 R 4, R 5 R 4 R 2 R 5 R 6 SEG 3101. Requirements Management. 41

Introduction Traceability Baselines Change Management Requirements Management Tools Example – DOORS Links • A relationship between two objects in the DOORS database is established using a link • One source object and one destination object • Links can be followed in either direction • Possible to have many links between the same two objects • Links also have types and attributes! SEG 3101. Requirements Management. 42

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Creating and Accessing Links SEG 3101. Requirements Management. 43

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Exploring Traceability Links SEG 3101. Requirements Management. 44

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Link Matrix View SEG 3101. Requirements Management. 45

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Hierarchical Link View SEG 3101. Requirements Management. 46

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Filtering View (Query on Attributes) SEG 3101. Requirements Management. 47

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Types of Analysis • Impact Analysis • Analyze out-links (which objects in other modules are affected when this module is changed) • Traceability Analysis • Analyze in-links (changes in these objects will affect this module) • May involve multiple levels of objects/documents SEG 3101. Requirements Management. 48

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Multi-Module Traceability User Reqts Technical Reqts Design Test Cases SEG 3101. Requirements Management. 49

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Analysis with Wizard Orphans indicate missing links SEG 3101. Requirements Management. 50

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Traceability and Software Artefacts DOORS: Requirements Management & Traceability SYNERGY/Change: Work Orders TAU/Architect & TAU/Developer: System Modeling & Code Generation SYNERGY/CM: Engineering Tasks Active. CM: Controlled Code Modules SEG 3101. Requirements Management. 51

Introduction Traceability Baselines Change Management Requirements Management Tools What are Suspect Links? If documents are linked … … a change by this user here… … shows up as a warning flag to this user here. • Proactively know when changes effect your requirements • Suspect link indicates that element may have been affected by a change • Help ensure that ripple effects of changes are considered SEG 3101. Requirements Management. 52

Introduction Traceability Baselines Change Management Requirements Management Tools Suspect Links • Visible as indicators or with change notes (added/deleted) SEG 3101. Requirements Management. 53

Introduction Traceability Baselines Change Management Requirements Management Tools Link Creation: Manual Effort! Fault F 2. 1: Velocity sensors fail to sense excessive velocity. Hazard H 2: Moving the patient’s arm at excessive velocity. Fault F 2. 2: Configuration component fails to update correct velocity constraints. R 1: A system test must be run prior to each use to check that the sensors are operating correctly. R 2: All sensors must be duplicated. R 3: The robotic arm must stop automatically if arm sensors disagree on current velocity by more than x mps. R 9: Current velocity constraint is displayed on the monitor. R 10: Movement must be disabled if current velocity constraint fails to match patient’s personal record. R 11: Current velocity constraint must fall under maximum allowed velocity. Test Case T 1 Test Case T 2 Test Case T 3 Test Case T 4 Test Case T 5 Test Case T 6 Test Case T 7 Test Case T 8 Manual link creation is very demanding (likely the most annoying problem) Includes trace links created using Requirements management tools such as DOORS The goal is the total automation of high-quality trace link creation and maintenance! SEG 3101. Requirements Management. 54

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability Planning • Planning traceability? Yes, just like any other project! • Who are the stakeholders? • What are the needs (analysis, reports…)? • Useful, measurable, feasible objectives • Definition of links and attributes • Can some be inferred automatically? • Process (who collects and when to collect traceability information) • Roles, access • Data/link input and updates • Exceptional situations (e. g. , lack of time) • Representations, queries, tools • … • Traceability policies define what and how traceability information should be maintained SEG 3101. Requirements Management. 55

Introduction Traceability Baselines Change Management Requirements Management Tools Factors to Consider during Planning (1) • Number of requirements • The greater the number of requirements, the more the need formal traceability policies • Expected system lifetime • More comprehensive traceability policies should be defined for systems which have a long lifetime • Maturity level of organization • Detailed traceability policies are more likely to be implemented and used properly in a cost-effective way in organizations which have a higher level of process maturity • Size of project and team • The larger the project or team, the greater the need formal traceability policies SEG 3101. Requirements Management. 56

Introduction Traceability Baselines Change Management Requirements Management Tools Factors to Consider during Planning (2) • Type of system • Critical systems such as hard real-time control systems or safetycritical systems need more comprehensive traceability policies than non-critical systems • Additional constraints from customer • E. g. , compliance to military standard • Traceability links should be defined by whoever has the appropriate information available Source Target Information Source System requirement Software requirement System engineer Use case Functional requirement Requirements analyst Functional requirement Test case Test engineer Functional requirement Software architecture element Software architect Functional requirement Other design element Designer or Developer Business rule Functional requirement Requirements analyst SEG 3101. Requirements Management. 57

Introduction Traceability Baselines Change Management Requirements Management Tools Dilbert and Planning SEG 3101. Requirements Management. 58

Introduction Traceability Baselines Change Management Requirements Management Tools Simple Example of Traceability Links SEG 3101. Requirements Management. 59

Introduction Traceability Baselines Change Management Requirements Management Tools Modeling Traceability • The types of links to use (and their attributes) must be defined for different types of requirements • It is a design problem! • May be modeled with a UML class diagram (metamodel) • Object types (classes) • Object attributes (typed attributes) • Structure of folders, modules, objects • Stereotypes, composition… • Link types (associations) • Satisfies, tests, refines, contains, contributes to, threatens, justifies… • Link attributes (association classes) • Link cardinalities/multiplicities • … SEG 3101. Requirements Management. 60

Introduction Traceability Baselines Change Management Requirements Management Tools Example – One Traceability Information Model (TIM) SEG 3101. Requirements Management. 61

Introduction Traceability Baselines Change Management Requirements Management Tools DSL for Model Traceability [Rahman, 2013] - FYI Traceability Information Model (TIM) SEG 3101. Requirements Management. 62

Introduction Traceability Baselines Change Management Requirements Management Tools Types of Traceability Links • Note the types of links in the previous examples, as well as the types of objects they relate • Satisfies, Tests • Refines, References, Contains. . . • Others could be created • Contributes, Contradicts, Justifies, Depends on. . . SEG 3101. Requirements Management. 63

Introduction Traceability Baselines Change Management Requirements Management Tools Trace Usage You don’t expect us to actually use the trace links we create – do you? SEG 3101. Requirements Management. 64

Introduction Traceability Baselines Change Management Requirements Management Tools Query Approaches SELECT DISTINCT regulatory_code. * FROM ((regulatory_code LEFT OUTER JOIN tm_regulatory_code 2 software _requirement ON (regulatory_code. id = tm_regulatory_code 2 software _requirement_id)) LEFT OUTER JOIN software_requirement ON (software_ requirement. it=tm_regulatory_ code 2 software_requirement. software_ requirements_id WHERE regulatory_code. relevant='true' Visual Queries Give me a list of all Java classes associated with high risk preliminary hazards which have failed test cases in the past month. AND software_requirement. id IS NULL; SQL (with or without query builders) Natural Language SEG 3101. Requirements Management. 65

Introduction Traceability Baselines Change Management Requirements Management Tools Traceability Queries and Reports • Just like any other database • Structures queries, à la SQL • Natural language • List all preliminary hazards that have a high level of risk, and which are not covered by a software requirement of type "mitigating“ • Queries exploiting a visual language • Queries exploiting speech-recognition • E. g. , via a mobile phone! • Recent studies suggest that users prefer written natural language • P. Pruski et al. : Ti. Qi: Towards natural language trace queries. RE 2014: 123 -132 • Important advice: If you are to support traceability in some way, then do it early! Otherwise, if done too late, you will incur all the costs without any return… SEG 3101. Requirements Management. 66

Introduction Traceability Baselines Change Management Requirements Management Tools Tracing Mistakes People Make Requirements 1. Failure to plan: Most projects do not include a TIM Test Cases 2. Ill-defined trace granularity leads to unacceptably high / low or mismatched links 4. Lack of unique project-wide IDs 5. Missing trace links 6. The DOORS dump – i. e. , massive unstructured dumps of trace data 7. Traceability as an after-thought 3. Redundant Trace Paths SEG 3101. Requirements Management. 67

Introduction Traceability Baselines Change Management Requirements Management Tools Advice for DOORS Links • Direction of links • From the most concrete to the most abstract • To avoid access rights issues • To make use of the integrated analysis routines of DOORS • Link Modules • One module per type of link • NEVER use default module (should not even be offered) • To avoid maintenance problems • Specific types facilitate analysis and filtering SEG 3101. Requirements Management. 68

Baselines

Introduction Traceability Baselines Change Management Requirements Management Tools Baseline • Non-modifiable (read-only) version of a document • Describes a moment in time • May include multiple documents at the same time • Enables document comparison and management • Comes with a change history for the document • Information on objects, attributes, and links created, deleted, or edited since the creation of the baseline • Often also contains information on user sessions (when the document was opened, by whom…) • Requires access control • It is advisable to establish a baseline for a new document that is imported into the document management system • In order not to lose any changes SEG 3101. Requirements Management. 70

Introduction Traceability Baselines Change Management Requirements Management Tools Baseline for Requirements • Represents the set of functional and non-functional requirements that the development team has committed to implement in a specific release • Before going into the baseline, the requirements should be reviewed and approved by stakeholders • Once in the baseline, all changes should follow a defined change control process Baseline l Different viewpoints l No formal documents l Always changing l Shared understanding l Configuration management l Change management SEG 3101. Requirements Management. 71

Introduction Traceability Baselines Change Management Requirements Management Tools Baseline Usage • Baselines may be • Created • Complete image of requirements state at a given time • Deleted • Visualized • Possibility to go back • Compared • To see changes since a certain time • Copied • Signed • For authorization, contract SEG 3101. Requirements Management. 72

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Baseline Compare SEG 3101. Requirements Management. 73

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Module Compare • Change analysis between versions SEG 3101. Requirements Management. 74

Change Management

Introduction Traceability Baselines Change Management Requirements Management Tools Change Management (1) • The more things change… • If you see change not as an enemy, but as a welcome friend, you will secure the most valuable prize of all – the future… SEG 3101. Requirements Management. 76

Introduction Traceability Baselines Change Management Requirements Management Tools Change Management (2) • Concerned with the procedures, processes, and standards which are used to manage changes to a system requirements • Change management policies may cover • The change request process and the information required to process each change request • The process used to analyse the impact and costs of change and the associated traceability information • The membership of the body that formally considers change requests • Software support (if any) for the change control process • A change request may have a status as well as requirements • E. g. , proposed, rejected, accepted, included. . . SEG 3101. Requirements Management. 77

Introduction Traceability Baselines Change Management Requirements Management Tools Change Request Form • Proposed changes are usually recorded on a change request form which is then passed to all of the people involved in the analysis of the change • Change request forms may include • Date, Customer, Requester, Product including version • Description of change request including rationale • Fields to document the change analysis • Signature fields • Status • Comments • … SEG 3101. Requirements Management. 78

Introduction Traceability Baselines Change Management Requirements Management Tools Change Analysis and Costing – Example customers may misunderstand requirements and their context and suggest unnecessary changes with the help of traceability information risk is too high consequential changes may be unacceptable to user/customer Source of figure: Kotonya and Sommerville negotiations with customers cost/time required for the implementation of change is too high/long SEG 3101. Requirements Management. 79

Introduction Traceability Baselines Change Management Requirements Management Tools Different Management Aspects • Change Management • How does a customer submit change requests? • How is this request being monitored, prioritized, and implemented? • Configuration Management • Versioning, labelling, and tracking code and other components during the development cycle of software • Release Management • Defines how and when different hardware and software will be made available together as a product SEG 3101. Requirements Management. 80

Introduction Traceability Baselines Change Management Requirements Management Tools Tool Support for Change Management • May be provided through requirements management tools or through configuration management tools • Tool facilities may include • Electronic change request forms which are filled in by different participants in the process • A database to store and manage requests • A change model which may be instantiated so that people responsible for one stage of the process know who is responsible for the next process activity • Electronic transfer of forms between people with different responsibilities and electronic mail notification when activities have been completed • Electronic signatures • Discussion forums • In some cases, direct links to a requirements database SEG 3101. Requirements Management. 81

Introduction Traceability Baselines Change Management Requirements Management Tools Example – DOORS Change Proposal System (1) • The Change Proposal System (CPS) allows people to access DOORS modules and to propose changes (without immediately changing the modules) • This allows for feedback and the application of changes in a controlled manner • An administrator controls the visibility of data as well as who is allowed to propose change requests • DOORS can also be integrated with version/change management systems SEG 3101. Requirements Management. 82

Introduction Traceability Baselines Change Management Requirements Management Tools Example – DOORS Change Proposal System (2) E-mail Changes from all users including DOORSnet ted t i m ed Sub Read-only user submits “Change Proposal” • Manage change • No surprises Changes reviewed on-line ew A pt e c c her t r Fu arch e Res evi R In On ld Ho t Nex se ea Rel R ted c e ej SEG 3101. Requirements Management. 83

Requirements Management Tools

Introduction Traceability Baselines Change Management Requirements Management Tools What Kind of Tool Do We Need? • Different companies will use different tools, which may or may not be tailored to the requirements management task • Word processor (Microsoft Word with templates…) • Spreadsheet (Microsoft Excel, Google Sheets…) • Industrial-strength, commercial RM tools • IBM DOORS, IBM Requisite Pro, Jama Contour… • Internal tools • Gen. Spec (Hydro-Quebec)… • Open source RM tools • a. Nimble, Polar. Sys Req. Cycle, Eclipse Pro. R • Bug tracking tools • Bugzilla, Github… • Collaboration tools (free or not) • Assembla, Fos. Wiki, … SEG 3101. Requirements Management. 85

Introduction Traceability Baselines Change Management Requirements Management Tools What Is the Best Tool? SEG 3101. Requirements Management. 86

Introduction Traceability Baselines Change Management Requirements Management Tools What Should We Look For in a Tool? • Types/attributes for requirements and links • Specifications and models • Version and change management • Database repository • Traceability • Analysis (impact, completeness, style, differences…) • Automatic inspection of requirements (according to rules) • Visualization and reports • Automated inspections • Requirements document generation • Monitoring of requirements statuses • Access control • Import/export • Interchange (OMG Req. IF) • Communication with stakeholders • Scripting language (for automation) • Reuse of requirements, models, projects • Collaboration • … SEG 3101. Requirements Management. 87

Introduction Traceability Baselines Change Management Requirements Management Tools Requirements Management Implies Integration! SEG 3101. Requirements Management. 88

Introduction Traceability Baselines Change Management Requirements Management Tools Approaches – Document or Database? (1) • Requirements have to be stored in such a way that they can be accessed easily and related to other requirements • Document (e. g. , Word) • Easy to use, easy to access, simple training • Requirements are all stored in the requirements document • It is easy to produce the final requirements document • But: Traceability? Status reports? Granularity of requirements? Search and navigation facilities? Change management? Version control? Analysis? Simultaneous access control? . . . SEG 3101. Requirements Management. 89

Introduction Traceability Baselines Change Management Requirements Management Tools Approaches – Document or Database? (2) • Database (e. g. , DOORS) • Good for management, controlled access, links, analysis, reports • Good query and navigation facilities • Support for change and version management • But: hard (and costly) to configure, manage, and use; link between the database and the requirements document must be maintained (final requirements document must be generated) • Ideally: Target the benefits of both • E. g. , DOORS offers integrations with Word (import/export) as well as document-oriented views (for the “look and feel”…) SEG 3101. Requirements Management. 90

Introduction Traceability Baselines Change Management Requirements Management Tools How About Evolving the Process Itself? • Evolution of requirements types • Adding / modifying / deleting • Attributes • Link types • Requirements status • … • Evolution of change management • Adding / modifying / deleting • Attributes • Lifecycle status • Forms • … • Is this well supported in the tool? SEG 3101. Requirements Management. 91

Introduction Traceability Baselines Change Management Requirements Management Tools Thinking About Getting a RM Tool? • The list of potential criteria and the list of products can be rather long… • Evaluation of 21 RM tools, with many good papers available at Seilevel (Joy Beatty et al. , 2016) • Lists of Requirements Management Tools and of Requirements Engineering Tools • Survey of Requirements Tools Lists! • Which ones are relevant to you, in your context (project, organization…)? SEG 3101. Requirements Management. 92

Introduction Traceability Baselines Change Management Requirements Management Tools Jama and DOORS: Overview • Jama Overview https: //www. youtube. com/watch? v=zz. ZRxo. AZ 7 k. I • Requirements Traceability in Jama https: //www. youtube. com/watch? v=Xx 5 i. Sdgr 148 • Jama Tutorials on RE (~1 hour each) https: //www. youtube. com/watch? v=uq. IDC 97 j. Ib. A https: //www. youtube. com/watch? v=pm 40 Tgd. NNu 0 • IBM Rational DOORS (5 min) http: //www. youtube. com/watch? v=Reff 4 ELfwr. M • IBM Rational DOORS Linking and Traceability (10 min) https: //www. youtube. com/watch? v=2 t. N_c. VQP 214 • IBM Rational DOORS 9. 6 tutorial (90 min) https: //www. youtube. com/watch? v=-i. RWMbn. DLi. A SEG 3101. Requirements Management. 93

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Database View Deleted Folders Formal Modules Projects Link modules SEG 3101. Requirements Management. 94

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Displayed Information Column “No change since baseline” Heading change-bar (green / blue) Object or Section Number Object Heading Use in Graphical view Use as Data. Tip Object Identifier Link Indicator “Changed this session” change-bar, unsaved (red) Object Text “Changed since baseline” change-bar, saved (yellow) Current Object SEG 3101. Requirements Management. 95

Introduction Traceability Baselines Change Management Requirements Management Tools DOORS – Integration with URN • Linkable URN diagrams and element objects, via the DXL export plug-in for j. UCMNav SEG 3101. Requirements Management. 96

Introduction Traceability Baselines Change Management Requirements Management Tools Twiki/Fos. Wiki Overview • A generic Wiki tool (TWiki. org, Fos. Wiki. org) • Promotes collaboration • Database-driven • Access and version control • Forms and queries • State-based workflows (processes) • Text and graphics • Lightweight, extensible (plug-in architecture) • Example of Forms and Queries • Requirements: http: //cserg 0. site. uottawa. ca/twiki/bin/view/Projet. SEG/UCMNav. Requirements • Library: http: //cserg 0. site. uottawa. ca/twiki/bin/view/UCMVirtual. Library • Use Cases: http: //cserg 0. site. uottawa. ca/seg/bin/view/CSI 4900/Use. Cases SEG 3101. Requirements Management. 97

Introduction Traceability Baselines Change Management Requirements Management Tools TWiki for Requirements Management SEG 3101. Requirements Management. 98

Introduction Traceability Baselines Change Management Requirements Management Tools TWiki – Requirement Example SEG 3101. Requirements Management. 99

Introduction Traceability Baselines Change Management Requirements Management Tools TWiki – Requirement Form Example SEG 3101. Requirements Management. 100

Introduction Traceability Baselines Change Management Requirements Management Tools Using TWiki… • We have: • Requirement types description with configurable statuses & attributes • Bidirectional links (Wiki. Words) • Configurable requests, filtering, reports • Access control and version management (showing differences) • Change management (again with forms, process, etc. ) • Discussions, attachment of documents/images • Export (HTML) • Scripting language (Perl) • But do we really have: • Graphical view of traceability? • Editables (à la Excel/Word)? • Baselines? Tool integration? Imports? Analysis? … SEG 3101. Requirements Management. 101

Introduction Traceability Baselines Change Management Requirements Management Tools Conclusions • Description, importance, and illustration of • Requirements Management • Activities, attributes, statuses • Traceability • Modelling, visualization, analysis • Baselines • Comparison • Change management • Principal steps • Requirements Management tools • Criteria, integration, variety (from DOORS to Fos. Wiki!) SEG 3101. Requirements Management. 102

Introduction Traceability Baselines Change Management Requirements Management Tools And the Future? • Jane Cleland-Huang et al. : Software traceability: trends and future directions. FOSE 2014: 55 -69 SEG 3101. Requirements Management. 103

Introduction Traceability Baselines Change Management Requirements Management Tools Link Creation: Just in Time (IR) Poirot: De. Paul University No common term problem RETRO: University of Kentucky Automated approaches leverage the fact that text is found across almost every model and use information retrieval (IR) methods to compute similarity between artifacts and hence identify related artifacts SEG 3101. Requirements Management. 104

SEG 3101. Requirements Management. 105

Quiz! 1. Is a high requirements volatility a good thing? 2. What should a good requirements identifier look like? 3. Why is confidence a good requirements attribute? 4. Why is traceability difficult? 5. What do we find in a traceability model? 6. Why are baselines important? 7. Can a change request have a status? 8. What are important functionalities expected from an RMS? 9. What is the best RMS: Word or DOORS? 10. How are links exploited in DOORS? 11. In a requirements management context, what are some important benefits of Google Sheets over MS Excel? SEG 3101. Requirements Management. 106