IRQA Web benefits - Complete Requirements web tool

IRQA Web addresses common problems to different team members.
Engaging key stakeholders in the process is a step towards project success. 

IRQA Web addresses this problem providing specific features for each one of the needs. 
 

Non technical Stakeholders 

• Problems
  • Make their needs clear
  • Be capable of posting change request over the needs
  • Follow and review the status of their requests
  • Prioritize their needs
     
• Reasons
  • Inefficient communication capabilities
  • No use of centralized database for the stakeholder requests
  • Lack of skills and of a mature process
  • Review cycles are not included
  • Key stakeholders are not involved in decisions
     
• Benefits
  • Increased user acceptance and satisfaction
  • Reduced rework and cost
  • Delivery of correct systems the first time and on budget
     
•  What IRQA Web provides to solve these problems 
  •  Easy to use tool, with access rights by role
  • Centralized web access so that all the stakeholders can participate and share information.
  • Possibility of establishing validation procedures for the approval by the user, including workflows.
  • Categorization of requirements by user defined types and attributes.
  • Functionalities to establish clear communications, including discussion forums for each single request
  • Export to MS Word and MS Excel to create understandable documents
     

Business Analysts 

• Problems
  • Capture exact and complete requirements 
  • Specify and document requirements understandably
• Reasons
  • No participation of key stakeholders
  • Requirements not captured using an understandable language
  • Inefficient capture techniques
  • Review cycles are not included
  • Support of the solution to information capture techniques
  • Lack of skills and of a mature process
  • Impossibility of creating requirements documents with all the information
     
• Benefits
  • More exact and complete requirements, allowing the delivery of correct systems the first time and on budget
  • Better quality. Delivery the expected application
     
•  What IRQA Web provides to solve these problems: 
  • Web access so that all the stakeholders can participate.
  • Possibility of establishing validation procedures for the approval by the user, including workflows
  • Easy to use tool, with access rights by role
  • Functionalities to establish clear communications, including discussion forums for each single requirement
  • Export to MS Word and MS Excel to create understandable documents
  • Support and automation of the process through blocks and traceability restrictions
  • IRQA Quality Analyzer to validate the semantic correction of the requirements, and make it available to the users
     

Project Managers 

• Problems
  • Carrying out impact analysis and change prioritization
  • Communicate requirements throughout the life cycle
  • Effectively manage the scope of each project
  • Reuse requirements, rules and standards.
     
• Reasons
  • Need to track appliances in the different phases of the life cycle, maintaining associations, relationships and dependences
  • Lack clear and transparent traceability reports
  • Lack of change control and versioning
  • Lack of a change management process
  • Need for a common language for the definition of requirements
  • The requirements are not sufficiently detailed
  • The requirements are out of context
  • The requirements are expressed only as text
  • There is no baseline support
  • Lack of support for the change management process
  • Lack of visibility and control in response to changes
  • Need to start from scratch because of inability to reuse previous analysis
  • Assure that all non-functional requirements are met.
     
• Benefits
  • Improve the quality of the appliaction
  • Reduce development time and faster delivery
  • Reduce rework
  • Delivery of the correct application
  • More reliable estimates
  • Better response to change
  • Reuse of successful projects
     
• What IRQA Web provides to solve these problems: 
  • Web access so that all the stakeholders can participate
  • Support and automation of the process through blocks and validation workflows
  • Functionalities to establish clear communications, including discussion forums for each single requirement
  • Reuse of rules and standards, including requirements
  • Propagation of the changes in the components reused to the target projects
  • Capacity to create traceability among all requirements
  • Traceability and validation matrix for the graphic monitoring of traceability and the detection of non related elements
  • Relationships by motive view for textual review of the traceability
  • Complete configuration management of requirements (version and history, with version comparisons)
  • Role-based access control with granularity down to the level of elements
  • Common hardware and software infrastructure (standard databases)
     

Quality/Methodology Managers 

• Problems
  • Assure that only a mature and common process is used 
• Reasons
  • Standardize Requirements Engineering in the Organization
  • Standardize improvement initiatives (CMMI, …)
  • Demonstrate maturity to the end client
  • Assure that the best practices defined are used
  • Standardize deliverables and documentation
  • Metric-based improvement
     
• Benefits
  • Reduce rework
  • Increase efficiency and efficacy
  • More reliable estimates
  • Lower development time
  • Reuse of successful projects
  • Predictable results
  • Ease of moving from one project to another
     
•  What IRQA Web provides to solve these problems: 
  • Support and automation of the process through blocks and validation workflows
  • Web access so that all the stakeholders can participate in the process
  • Possibility of establishing validation procedures for the approval by the user, including workflows
  • Reuse of rules and standards, including requirements.
     

Development Managers
 

• Problems
  •  Deliver applications that cover the real needs for time and costs
  • Impossibility of correctly communicating form with the business lines
  • Having to use different tools for each project
     

• Reasons
  • The problems in the requirements are discovered too late
  • Absence of the required skills
  • No automated process and impossibility of establishing common processes
  • The roles of the IT Department and business side speak different languages
  • Lack of Validation and Approval by the end user
  • Conflicting objectives
  • Having to negotiate with various suppliers
  • Training costs
     
• Benefits
  • Reduce reworking
  • Reduction of development costs
  • A reusable common language for requirements
  • Reduction of development costs
  • Lower cost of licenses and services
  • Greater expertise resulting in less need for reworking and a shorter Time-To-Market.

• What IRQA Web provides to solve these problems:
  • Web access so that all the stakeholders can participate in the process
  • Support and automation of the process through blocks and validation workflows
  • Reuse of rules and standards, including requirements
  • Functionalities to establish clear communications, including discussion forums for each single requirement
  • Export to MS Word and MS Excel
  • IRQA Quality Analyzer to validate the correct semantics