Follow a manual added link
The Essential Guide to Requirements Management and Traceability
Chapters
- 1. Requirements Management
- Overview
- 1 What is Requirements Management?
- 2 Why do you need Requirements Management?
- 3 Four Fundamentals of Requirements Management
- 4 Adopting an Agile Approach to Requirements Management
- 5 Conquering the 5 Biggest Challenges of Requirements Management
- 6 Three Reasons You Need a Requirements Management Solution
- 2. Writing Requirements
- Overview
- 1 Functional requirements examples and templates
- 2 Product requirements document template and examples
- 3 How to write system requirement specification (SRS) documents
- 4 Adopting the EARS Notation to Improve Requirements Engineering
- 5 Jama Software Requirements Advisor
- 6 Frequently Asked Questions about the EARS Notation and Jama Connect Requirements Advisor
- 7 How to Write an Effective Product Requirements Document
- 8 Functional vs. Non-functional requirements
- 9 What Are Non-Functional Requirements and How Do They Impact Product Development?
- 10 Characteristics of Effective Software Requirements and Software Requirements Specifications (SRS)
- 11 8 Do’s and Don’ts for Writing Requirements
- 3. Requirements Gathering and Management Processes
- 4. Requirements Traceability
- Overview
- 1 What is Requirements Traceability and Why Does It Matter for Product Teams?
- 2 How to Create and Use a Requirements Traceability Matrix
- 3 Live Traceability vs. After-the-Fact Traceability
- 4 How to Overcome Organizational Barriers to Live Requirements Traceability
- 5 Requirements Traceability, What Are You Missing?
- 6 Four Best Practices for Requirements Traceability
- 7 Requirements Traceability: Links in the Chain
- 8 What Are the Benefits of End-to-End Traceability During Product Development?
- 5. Requirements Management Tools and Software
- 6. Requirements Validation and Verification
- 7. Meeting Regulatory Compliance and Industry Standards
- 8. Project Management
- 9. Measuring Requirements
- 10. Systems Engineering
- Glossary
Meeting Regulatory Compliance and Industry Standards
Building complex products and software is a complicated process – and one that oftentimes involves complying with a variety of regulations and industry standards from governing bodies. Ideally, compliance management involves both people and a system that is fully integrated across functions of the organization. The more integrated the compliance management in the development lifecycle, the more likely it is to detect potential compliance issues before they cause long-term harm to companies or consumers.
In this chapter, we look at:
- Best practices for compliance management
- Understanding ISO standards, including their purpose and intention
- Creating a design history file (DHF)
- Failure Modes and Effects Analysis (FMEA)