A SMARTer way to manage requirements quality
Knowledge Manager is a tool designed to manage all knowledge around your requirements intensive projects. It stores this knowledge into a well-designed repository, a System Knowledge Repository (SKR) and allows an easy access and maintenance. The Requirements Quality Analyzer (RQA) or the Requirements Authoring Tool (RAT) are the main consumers of this knowledge.
Knowledge Manager (KM)
Knowledge is, nowadays, the most valuable asset for modern organizations. An appropriate management of the organization’s knowledge is a key success factor. Knowledge must be gathered from many sources, stored into secure repositories and accessed by the granted people at the right time. It will become a reusable component in the systems and software projects.
When it comes to mix both, knowledge and requirements, it is extremely important to treat requirements as knowledge items, to get new knowledge from requirements, to transform knowledge into new requirements…
kM allows you to manage knowledge from the requirements engineering point of view, thus getting the best of both kinds of assets.
kM allows the management of the System Knowledge Repository (SKR) management, including its System Knowledge Base (SKB) as well as all the Assets involved in the requirements improvement process.
Ontologies : Requirements knowledge Model
Ontologies may store the controlled vocabulary needed for a business domain. Those vocabulary items can be linked together, or even clustered from a semantic point of view. Terms, clusters, syntactic tags are the building blocks to define patterns as sequential lists of those items. Patter matching makes a seamlessly trans-formation into a formal language (RSHP in this case), what is the starting point for the inference layer, i.e. consistency and completeness.
A Requirement Pattern represents the grammar structure (boilerplate or statement level template) a text has to follow according to the policies of an organization. We apply patterns to state which set of grammars should be followed by the requirements in our projects.
For example, the requirement
“The Radar shall be able to detect hits at a minimum rate of 10 units per second” fulfills the following pattern:
THE <OBJECT DETECTION> SHALL <DETECT> <ITEMS> AT <MINIMUM> <RATE VALUE>
New knowledge tool... new knowledge roles
Managing knowledge is an activity not covered yet in many organizations or IT departments. Therefore, aside of new tools such as Knowledge Manager, new roles are also necessary to cover those activities and support the activities of other roles such as quality manager, project manager, system engineer, business analysts…
Knowledge Base architect is the role suggested by the Requirements Quality Suite to lead those important activities. The main responsibilities of this role are the following:
- Agreeing, together with other roles, the borders of the domains to be modeled
- Finding sources that could help in the creation of the knowledge base
- Creating and evolving one or more knowledge models within the business domain
- Defining the right structure (patterns) of the requirements to be written
- Attending the suggestion of system engineers and business analysts to evolve the models
Knowledge Repository Manager is the role suggested by the Requirements Quality Suite to represent the responsibility for the whole Knowledge Repository.
Knowledge Manager into the Requirements Quality Suite
Knowledge Manager represents the core tool for the Requirements Quality Suite:
Requirements Knowledge Model:
- The semantics and concepts of the knowledge model consumed by RQA and RAT are easily generated here
- New concepts of the knowledge model can be generated out of the requirements managed by RQA
- The patterns used by RAT and RQA are created and managed in Knowledge Manager
- Knowledge Manager includes stats of use of every pattern, thus alerting of missing requirements or wrong patterns
Quality: The integration of Knowledge Manager into the Requirements Quality Suite represents the link between knowledge, requirements and Quality.
Time: Requirements can rapidly be used to generate new pieces of knowledge. Create patterns just by typing an example of use.
Money: Knowledge is directly translated into money (it’s an asset for the organization). Properly managing knowledge means wisely managing money.