Benefits

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.
     
• Our answer
  • Support and automation of the process through block diagrams and validation workflows.
  • Standardization of the process using project templates.
  • Standardization of the documentation using Corporate Reports.
  • Dashboards and metrics for projects and requirements.
  • Reuse of rules and standards, including requirements and their corresponding tests.
  • Possibility of working with clients that use different tools while maintaining the same process, thanks to the exchange mechanism.

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.
     
• Our answer
  • Support and automation of the process through block diagrams and validation workflows.
  • Standardization of the process using project templates.
  • Standardization of the documentation using Corporate Reports.
  • Dashboards and metrics for projects and requirements.
  • Functionalities to establish clear communications, visually capturing scenarios with greater quality, such as the Problem Domain Models.
  • Reuse of rules and standards, including requirements, use cases, tests and the relationships among them.
  • Propagation of the changes in the components reused to the target projects.
  • Possibility of working with clients that use different tools while maintaining the same process, thanks to the exchange mechanism.
  • Capacity to create trails among all the elements, including requirements, use cases, tests and external elements (tests, model, tasks, etc.).
  • Traceability and validation matrix for the graphic monitoring of traceability and the detection of orphan elements.
  • View the relationships by reason for textual monitoring of traceability.
  • View indirect traceability.
  • Complete management of the configuration of requirements (version and history, with version comparisons).
  • Complete management of the configuration of project using baselines.
  • Manage distributed requirements and work off-line.
  • Support Change Management.
  • UDAs for the prioritization of requirements.
  • Configuration and management of the interface, views and filters by role.
  • Role-based access control with granularity down to the level of elements.
  • Web client access for key stakeholders.
  • Common hardware and software infrastructure (standard databases).

Business Analysts

• Problems
  • Capture exact and complete requirements.
  • Specify and document requirements understandably.
     
• Reasons
  • Requirements not captured using an understandable language.
  • Inefficient capture techniques.
  • Visualization of use scenarios.
  • Review cycles are not included.
  • No participation of key stakeholders.
  • 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.
     
• Our answer
  • Support and automation of the process through block diagrams.
  • Possibility of establishing validation procedures for the approval by the user.
  • Capacity to define the requirements using different techniques.
  • Functionalities to establish clear communications, visually capturing scenarios with greater quality, such as the Problem Domain Models.
  • Report Manager to create understandable documents.
  • Easy to use tool, with an interface that is configurable by role.
  • Client web so that all the stakeholders can participate.
  • Distributed and off-line work.
  • Prototyped through integration with third party tools (Just in Mind Prototyper).
  • IRQA Quality Analyzer to validate the semantic correction of the 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.
     
• Our answer
  • Support and automation of the process through block diagrams and validation workflows.
  • Standardization of the process using project templates.
  • Standardization of the documentation using Corporate Reports.
  • Reuse of rules and standards, including requirements and their corresponding tests.
  • Functionalities to establish clear communications, visually capturing scenarios with greater quality, such as the Problem Domain Models.
  • Import / Export with other tools, included MS Office.
  • Prototyped through integration with third party tools (Just in Mind Prototyper).
  • IRQA Quality Analyzer to validate the correct semantics.
  • Web client access for key stakeholders.
  • Common hardware and software infrastructure (standard databases).