10 points to consider in relation to requirements - Visure Solutions
1. 10 POINTS TO CONSIDER IN
RELATION TO REQUIREMENTS
Jordi Borja - jborja@visuresolutions.com
Business Development and Solution Strategy Manager
2. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact your business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. A development methodology is not enough.
6. Having good analysts is not enough.
7. Is our Requirements process mature?
8. What technicians do we need?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
2
3. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
3
4. Visure Solutions, The Requirements Company
• A Spanish company specialising in Requirements Engineering.
• Experience of over 10 years in Requirements Management and Definition projects.
• Manufacturer and distributor of the IRQA tool, leading solution in Europe with more
than 200 clients in 20 countries.
• Offices in Spain, Sweden, Germany and the US.
Process Human
Support for CMMI, Resources
Spice (ISO) Qualification
Ad hoc processes and consulting
Software Engineering Systems Engineering
4
5. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
5
6. Investing in Requirements is critical to success
• Symptoms:
• Unsatisfied users.
• High degree of rework.
• Unpredictable planning and extra charges.
• Non-compliance with standards and non-functional Requirements.
• Lack of visibility and control.
• Difficulty to manage change.
• The CIO’s key role is:
• To diagnose whether the Requirements process is mature.
• To assume the challenge of improving Requirements Management and
Definition.
• To internally “sell” the importance of Requirements:
‒ To the Technology and Business departments.
– To assign the necessary resources for improvement.
– To assign the budget for the improvement.
6
8. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
8
9. 1.- Yes: projects fail because of inadequate Requirements
Causes of deficiency Effort dedicated to correcting defects
Requirements
Errors Design Errors
(82%) (13%)
Other Errors (4%) Coding Errors (1%)
Relative cost of resolving a defect The importance of Requirements
200 Project Analyzed
180
0- 5% invested in Req.
160 Management results in 80-200%
% Overcost
140 overcost
8-14% invested in Req.
120
Management results in 0-60%
100 overcost
80
60
40
20
0
0 5 10 15 20 25
% Requirements Management Cost compared to total project cost
Source: James Martin, Barry Boehm
9
10. 1.- Yes: projects fail because of inadequate Requirements
Incomplete Requirements 13.1%
Users not involved 12.4%
Lack of resources 10.6%
Unrealistic expectations 9.9%
Lack of executive support 9.6%
Changes in specifications 8.7%
Planning failures 8.1%
There is no future need 7.5%
Source: IT Toolbox y Standish Group
10
11. 1.- Yes: projects fail becuase of inadequate Requirements
Failure to achieve the senior
management’s commitment to the project
Failure to achieve the users’ commitment.
Misunderstood requirements
Failure to register or include the user
Failure to administrate the end users’
expectations
Changes in scope
Lack of knowledge/skills of project members
Lack of stable requirements
Introduction of new technology
Insuficient/inadequate project team
Conflict between user departments
Less Important More Important
RISK FACTORS IDENTIFIED FOR THE 3 PANELS, SORTED BY RELATIVE IMPORTANCE
Source: Keil, Cule, Lyytinen, Schmidt.
11
12. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
12
15. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
15
16. 3.- Investing in Requirements provides significant benefits
Nivel 1 Nivel 4
Coste estimado por proyecto $ 250.000,00 $ 250.000,00
Sobrecoste medio (preproducción) $ 72.000,00 $ 4.200,00
Coste medio post-producción $ 34.400,00 $ 2.800,00
Coste Total Proyecto $ 356.400,00 $ 257.000,00
Sobre coste total por proyecto $ 106.400,00 $ 7.000,00
• 32.4% increase in Analysts’ production
• >30% reduction in time required by Stakeholders
16
18. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
18
19. 4.- Immediate return on investment
Investments - Year One
Software / Hardware
Licenses (IRQA + IRQA Web) 14.100 €
Maintenance - Year One 0€
Hardware 0€
Services
Training 4.000 €
Consulting 8.000 €
People
Labor Related Investment 7.800 €
Grand Total: Year One Investments 33.900 €
Labor Savings
Low High
Total Project Staff Headcount 20 20
Total Labor Hours Saved - Year One 1.598 2.340
Less - Startup Labor Hours Invested 260 260
Net Labor Hours Recovered - Year One 1.338 2.080
Total Annual Labor Euros
40.144 € 62.400 €
Recovered In Year One
Return on Investment
Low High
Investment Payback Period (Months) 8,5 5,8
NPV (over 2 years, discounted at 7%) 12.899 € 54.129 €
First Year ROI 41% 107%
19
20. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. No es suficiente con tener buenos analistas.
7. ¿Somos maduros en Requisitos?
8. ¿Qué técnicas debemos utilizar?
9. Capacitación de las personas: el mejor activo.
10. ¿Estamos usando las herramientas adecuadas?
20
21. 5.- Having a development methodology is not enough
• Adopting agile development methodologies or prototyping and
simulation-based methodologies does not guarantee success.
21
22. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Return on investment is immediate.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
22
23. 6.- Having good analysts is not enough
• A good analyst also needs:
• A mature and institutionalised process in the organisation.
• A set of well-defined techniques.
• Expertise.
• A tool that supports the process and techniques.
3 Analysts in Level 2
organisations
2 Analysts in Level 3
organisations
23
24. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Return on investment is immediate.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
24
25. 7.- Do we have a mature Requirements process?
Process
Current and Asset
legislative context Library
Maturity
models Adaptation of processes
(3.1)
Initial Improve Solution
ment Ongoing
Diagnosis Solution development Implementati
Plan Improvement
Phase 1 Phase 3 on
Phase 2 Phase 5
Phase 4
Requirements
Capability Adaptation of Technological Solution
Model (3.2)
Evaluations Technical Visure
Asset University
Library
25
26. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Return on investment is immediate.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
26
27. 8.- What techniques should we use?
• The key to success in Requirements Engineering is to use techniques
which are:
– Mature Creative
Brainstorming
– Proven Walt Disney
Other people’s view (OPV)
– Adjust to the organisation’s current needs Observation
Field Observation
– Based on project typology Learning
Interviews
• Choosing the adequate techniques is not easy: Interviews
Questionnaires
Osborn checklist
– Requirements definition Log-based
Archaeology
– Prioritisation / Release Management / Planning Reuse
Other
– Requirements writing Prototypes, simulations,
storyboards.
– Requirements modelling Card sorting.
– Testing Prioritisation
MoSCoW
– Change management Kano
Wieger matrices
– Impact analysis User stories
Release Management
Computer speed
– Configuration and baseline management Story Points
Maximisation / Minimisation
– Requirements taxonomies Planning and Estimation
Monte Carlo simulations
– Identification of stakeholders COCOMO
Function points
– … 27
28. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: the projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Return on investment is immediate.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
28
29. 9.- Qualification of human resources: your organisation’s best asset
• The persons involved in Requirements Engineering need specialised
training:
1. Courses in Requirements Engineering Theoretical and Methodological Concepts
Management Methodology and Requirements Definition
Mastering the Requirements Process
Requirements Modelling
2. Courses in Techniques and Skills
How to write quality requirements
Requirements capture and analysis techniques and skills
Metrics, dashboards and skills
Service Centre and Skills
Project Management and Leadership Skills
Supplier Management Skills
3. International official certification of the Requirements Engineering Board (IREB)
IREB (International Requirements Engineering Board) Professional Certification Course in
Requirements Engineering
4. Courses in the IRQA Requirements Management and Definition Solution
Advanced IRQA course
Basic IRQA course
5. Tailored Requirements Engineering courses
29
30. Contents
• Visure Solutions, the Requirements Company
• Investing in Requirements is critical to success
• 10 points to consider in relation to Requirements:
1. Yes: the projects fail because of inadequate Requirements.
2. Deficient Requirements impact the business.
3. Investing in Requirements provides significant benefits.
4. Immediate return on investment.
5. Having a development methodology is not enough.
6. Having good analysts is not enough.
7. Do we have a mature Requirements process?
8. What techniques should we use?
9. Qualification of human resources: your best asset.
10. Are we using the adequate tools?
30
31. Products
IRQA IRQA IRQA
IRQA Report IRQA
Activity Subactivity IRQA read-only Quality Prototyper
Manager Prototyper
Analyzer Server
Requirements capture and analysis techniques x
Requirements modelling X
Requirements specification and documentation X
Management of requirements baselines X
Management of requirements traceability X
Version control of individual and group requirements X
Requirements taxonomy
Requirements engineering X
in projects and
Management of requirements attributes X
maintenance (requirements
Consultation and search for requirements X
capture, modelling,
documentation and Digital signature X
validation) Reuse of requirements, testing scenarios and use cases X
Distributed and offline work X
Integration with Microsoft Office X
Requirements quality revision activities X
Management of change requests for maintenance X
Management of business rules X
Integration with other activities and tools for
X
requirements development
Requirements reading Requirements reading and monitoring X
Creation of prototypes X
Creation of prototypes and
simulations Creation of simulations X
Consultation of prototypes
Consultation of prototypes and simulations
and simulations
Administration of Management of requirements monitoring and
X X
requirements administration workflows
(administration of
configuration, design of Generation of reports and dashboards
reusable templates, design
of report and dashboard Administration of profiles and permissions X
templates, definition of Requirements monitoring X
requirement quality rules, Administration of reusable templates X
monitoring of
requirements) Definition of rules for revising requirements quality X
Creation of testing scenarios X
Definition and
administration of test Monitoring of testing scenarios X
scenarios Creation and monitoring of the requirements acceptance
X
criteria
Consultation of reports and
Consultation of reports and dashboards X X
dashboard
31
32. Having a process is not enough
Prioritise the Revise
requirements Request requirements
based on creation of
profile baseline
require-
require-
Export
ments
ments
Select
block
Click on
Click on
Development
Send scope
Department
Introduce
require-
ments
to the
Maintenance Project
START
Automatic Project
Configuration creation
project
of users IRQA support request Open IRQA
Capture configuration
32
33. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
33
34. Automate the process
- Visually define your corporate
Requirements Engineering processes,
including:
• Types of Requirements.
• Inheritance relationships
between Requirements.
• Traceability relationships
between Requirements (what
requirements can be traced to
each other and which user can
create the trace).
• Indirect traceability paths.
• Traceability motives.
• Unidirectional or bidirectional
traceability.
- Visually define workflows for your
change requests, requirements or tests.
- Define who can perform a status
transition.
- Define status change alerts.
34
35. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
35
39. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
39
44. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
44
46. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
46
48. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
48
49. Traceability and impact analysis
Quickly obtain reports on
traceability between
requirements, tests and
use cases
Analyse indirect
traceability relationships,
e.g. what tests have
failed in a change
request
Analyse traceability
information between
requirements, tests and
services, with powerful
filters
49
50. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
50
51. Integration examples
Traceability between artifacts of different tools
The block diagrams can contain elements the origin or destination of which can be another lifecycle
tool in order to leverage IRQA’s powerful analysis capabilities.
Synchronisation Synchronisation
Third-party tool
Export requirements,
services, tests and
traceability to IRQA
Third-party tool
Import requirements,
services, tests and
traceability from IRQA
51
52. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
52
53. Exporting to Office
Buttons for exporting to MS Word and MS Excel
Fast export buttons to MS Word and MS Excel, directly on the IRQA interface, accessible to all users
53
54. Importing Requirements
Automated import Comparison
Automated import of multiple Find new, modified and identical
elements elements, and compare the
differences between them
MS Word/Excel
Import existing requirements
documents or even offline
work
Import to IRQA
Accept or reject the elements to be imported
54
58. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
58
59. Reuse
Save time and enhance quality by reusing components
Requirements, use cases, tests and the relationships there between can be packetised in components
that can be reused between projects
Component version Projects
Selection of the version to be used Selection of the projects in which the
component will be published
Reused elements
The elements are
imported and
marked
Selection of component Importing and
Importing and
Non-functional requirements, updating
updating
e.g. security or performance, Import to the destination
Import to the destination
functionalities and all the project inin the following
project the following
associated tests are modes: modes:
-Read-only with update
-Read-only with update
examples of components -Write-only with update
-Write-only with update
available in the code -Copy -Copy
59
60. Reuse
Project 2
Project 1 Reusable component
Test 1
Test 1 Requir
ement
Test 3
1
Copy
Test 2 Requir
ement Serv
2 ice
3
Test 3
Reusable component
Create
Requirement
1
reusable Test 1
Test 4 component Project 3
Requirement Requirement Copy Reusable component
2 1 Test 3
Service Test 1
1 Requir
ement
Requirement Requirement Test 3
1
3 2
Service Notification
Service Requir
3 ement Serv
2 2 ice
Requirement 3
4
Service
3
Reference
Project 4
• Reuse artifacts (requirements, tests and services), creating your own
components and keeping traces (optional). Reference to component
• Publish them in the desired projects:
-Copying the component to another project.
-Referencing the component from another project.
-Copying the component to another project, but being notified of
the changes.
• Control the version of the component being used in each project.
• Identify, in each project, the artifacts that are shared between projects.
60
61. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
61
62. Configuration management
Management of baselines and versions of individual elements
Element configuration management is performed individually through the elements log or at project level
via the baselines, which enable full control by comparing the versions
Comparison of baselines
Full comparison
Baseline virtualisation
Users can use previous baselines Comparison of
from the user interface descriptions
Baseline virtualisation
Users can use previous
baselines from the user
interface
Comparison of individual
elements
Comparison of two versions
62
63. Electronic signature
Electronic signature of baselines
Administrators can ensure and justify the conformity or non-conformity of a specific set of elements or
baseline by the users
Visualisation of baselines
Once inside the project, the user can
see the baseline pending signature
Signature
The user selects the
reason for the signature
and includes an
Pending signatures explanatory comment
The menu indicates the projects with together with the
baselines pending signature by the confirmation of the
signature
user
63
64. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
64
65. Report Manager
Advanced reports
Users can execute both predefined reports and reports defined by the users themselves directly from
IRQA’s interface in multiple formats, including HTML, PDF, RTF or XML, in order to represent metrics,
coverage reports and traceability, among other things
Predefined reports
IRQA provides a full list of predefined reports
Corporate reports
Users can design new reports
and include them in the list of
corporate reports
65
66. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
66
70. What should a tool offer?
• Automation of the process.
• Support for requirements definition techniques.
• Help to correctly write requirements.
• Facilitate the communication of Requirements to the Technology Department.
• Support for advanced techniques.
• Support for changes and impact analysis thereof.
• Integration with other lifecycle tools.
• Provide adequate interfaces for each user profile.
• Allow reuse of Requirements between projects.
• Version and configuration management.
• Capacity to generate reports that reflect the current status of the Requirements.
• Management of RFIs, RFPs and contracts, tracing the Requirements to their origin
• Support Requirements Based Testing.
70