Kovair’s Requirements Management solution provides a rich and configurable, global platform for capturing a set of Requirements; collaborating on their development; and tracing implementation back to the original specs. As project goals and deliverables are shared by diverse team members (customers, analysts, software architects and designers), proper collaboration among each is a necessity to manage Requirements locally or globally.
The Kovair Requirements Management tool ensures that all developers are working from the same playbook, no matter where they are located, and that there are no costly last minute surprises - whether the project was developed in the office next door, or by an offshore partner 10,000 miles and 10 time zones away. The result is a top-quality application that matches with what the customer asked for and complies with all the internal and external requirements.
Kovair supports Requirements Management of many flavors - Standard as well as Proprietary methodologies or processes. All the capabilities necessary for effective and effortless Requirements Management are built-in in Kovair and are accessible through a highly user-friendly interface. Kovair’s rich implementation of requirements gathering, parsing, management, traceability, base lining and intelligent reporting in a process-driven, methodology enables project teams to effectively manage and map requirements.
Requirements Management Workflow
In Kovair, requirements can be gathered in a multiple formats as given below:
Kovair being a 100% web based tool provides all the facilities of a repository system. Once the requirements become a part of it, users can use different types of views, filters, and text based search to view the records.
Group by View
View with different metrics
In absence of a proper Requirements Management Tool, most of the organizations maintain their Requirements within a Word document. Microsoft Word can capture requirements in a very efficient way by including rich text and images. On adoption of a Requirements Management tool, we need to make sure that we do not lose any functionality of Word and therefore, need to augment those tools instead of removing them. To facilitate this, Kovair allows users to import requirements from a word document in two different ways as described below.
a. By uploading the document directly into the application
In Kovair, application users can upload the document containing Requirements into the application and define parsing logics based on Style, Keyword & Table. Based on the defined parsing logic, Kovair converts the document items into Requirement records. The imported document can also be maintained and managed within the application. This way of importing Requirements from Word does not require any client side installation.
b. By installing an Add-in for Word
This option of Word import requires installation of an Add-in in the client machine, and gives advanced options for import as compared to the previous one. Using this option, users can import the whole document or selected sections of the document. The document also gets uploaded and managed as a part of this import option. Users can also create, remove, and modify relationships from within the word document without even having to log in to the application. This supports bidirectional synchronization between the document and the application. Read More
Different types of diagrams/models are used while gathering requirements, and during systems analysis. Whether eliciting requirements is considered to be a separate activity, or a part of systems analysis, the importance of capturing correct requirements is extremely important. The correctness of requirements increases with the accuracy of the corresponding models like UI Mock-up, Class Diagram, and Flowchart.
Kovair allows users to draw these different types of models and embed them within description.
View with different metrics
View with different metrics
The Kovair Requirements Management tool has the most comprehensive traceability relation features compared to its competitors. It allows multiple types of relationships including custom ones between Requirements, thus enabling you to create logical links (‘depending’, ‘affecting’, and ‘bidirectional’) between Requirements and view them in a number of visualizing tools. These include folder hierarchy report of Requirement Traceability, Traceability Matrix and Traceability Relation Network Diagram. Moreover, Kovair allows both proactive and reactive impact analysis. Impact of changes is forwarded to stakeholders automatically to ensure synchronization and to undertake corrective actions at the earliest to minimize the cost of changes at the end of the lifecycle.
a. From inside the form
In Kovair, one can create a record of the related entity and relate to it right inside the form. Also, there is a provision for associating or relating existing items.
b. Using Traceability Matrix screen
Every entity has a traceability matrix form. Using this form, relationship can be achieved among records of different artifacts. Relationship between records of Business Requirement and Use Cases has been shown in the sample screenshot below. You can filter the records as per the need. The green tick mark (✓) indicates that in the relationship between Business Requirements and Use Cases, nobody impacts each other. By double clicking on any cell, relationships can also be created. Users can click on any cell being in relationship, and avail different options for editing and deleting the relationships.
Kovair provides different ways to view traceability relationships. These include folder hierarchy report of Requirement Traceability called as Traceability View, Traceability Matrix and Traceability Relation Diagram. Some sample screenshots are given below.
This type of view can be defined by users based on the relationships among different artifacts. These views can start from any point and can go to any point in the total chain. In between, steps in the relationship can also be skipped to view nested level relationships.
This is a matrix type view which shows the type of relationships established between records of different artifacts. Relationships between records of Business Requirement ad Use Case have been shown in the sample screenshot below. You can also filter the records as per the need. The blue arrow pointing towards top indicates that Business Requirements will impact Use Cases. The blue arrow () with a thunderbolt sign indicates that the particular Use Case has been impacted by the corresponding related Business Requirement. By double clicking on any cell, relationships can be created. Also, by clicking on any cell being in relationship, you may view different options for editing and deleting the relationships
c. Relation Diagram
This is a graphical representation of the relationships between records of different artifacts. It shows the relationships for a particular record.
Kovair allows users to view impacts both before and after the impact occurs. After a Change Request record is associated to any requirement, users can analyze the impact of the change on the total chain of records. Once the impact is raised by any record of any artifact, Kovair also allows viewing the impacted records against it. This impact can be seen both by record as well as from a central location.
During the lifecycle requirements get changed as well are removed or altered. Versioning of requirements aims at providing access to the specific change states of individual requirements over the course of the lifecycle. A version of a requirement gets defined by its specific content of the change state and is marked by a unique version number.
Versioning capability of Kovair provides the user an option to view the different versions in a pictorial format. Kovair allows users to compare two versions side by side and merge them if needed. Using the version capabilities of Kovair, users can rollback versions and reconstruct requirements.
Kovair, through its built-in Omni process Workflow engine, facilitates complete automation of the Requirements Management workflow - the way it happens in your organization- by facilitating the creation of a Step-based or more complex Task-based process.
Unlike Kovair, most of the Requirements Management tools in the market today do not come with the built- in Process Workflow Engine. This capability helps simplifying task management across the time zones by replacing manual task assignment with automatic handoff - such as during the review of Requirements i.e. before including them in a product roadmap. For instance, when the developer in Bangalore is finished with his or her coding, the designated tester in Dublin is automatically notified and assigned the next step of ensuring test case creation and testing. This process configurability and automation support any methodology or process (RUP, Agile Methodology, Scrum, and CMMI) as required. If a development team is distributed globally, this process automation can eliminate loads of email transfer, phone calls, and coordination of task meetings across different time zones. Thus, it enhances productivity in a considerable manner. The scenario is similar to a fully automated "lights out" manufacturing facility.
The following is an example of the type of process flow that can be created in Kovair with built-in graphical drag and drop capabilities that embed business rules under each process step.
Kovair produces reports and requirements documents of various kinds. They include:
These reports can be generated by a number of different reporting engines that Kovair supports as mentioned below: