OMNITRACKER Requirements Management Center is a software tool that manages the entire requirements management and engineering (RM&E) process from requirements elicitation through implementation release. It provides a common platform to specify, link, and track requirements across multiple levels of abstraction. The tool is based on the generic HOOD INSIDE RM&E information model and supports the V-Model system development process. It allows requirements to be entered quickly in a grid view and provides workflow management, documentation, and reporting throughout the RM&E lifecycle.
Nell’iperspazio con Rocket: il Framework Web di Rust!
OMNITRACKER Requirement Management
1. http://www.omninet.biz
http://www.omnitracker.biz
OMNITRACKER Requirements Management Center
OMNITRACKER Requirements Management By integrating OMNITRACKER Systems Engineering Center
Center the system development process as a whole according to
V-model can be administrated and controlled.
The development of complex systems and products requires
consistent and efficient management of requirements. With The Information Model
the OMNITRACKER Requirements Management Center, you
will receive an application to control the entire Requirement OMNITRACKER Requirements Management Center is
Management & Engineering (RM&E) process from the elicita- based on methods and process descriptions as defined by
tion of requirements up to the release of their implemented the generic HOOD INSIDE RM&E information model. HOOD
functions by the contractor. INSIDE is an initiative of HOOD Group.
Contractors and customers can communicate with each other OMNITRACKER Requirements Management Center en-
throughout the entire process and a mutual understanding hances structures among requirements along several levels
exists of the system to be developed. Overall communication of abstractions, e.g.:
between contractor and customer is documented and can be
completely tracked. Customer Requirements: Describe from a customer´s
point of view what functionality the system has to support
Benefits and define specific objectives, which have to be fulfilled
by implementation.
Benefits of OMNITRACKER Requirements Management
Center include: System Requirements: Describe what has to be deliv-
Generic information model: Easy adaptable and exten- ered to satisfy the Customer Requirements.
sible to customer processes.
Design Requirements: Define in detail how to realize the
Specifying and implementing specifications using a
common platform: All steps beginning from the elicita- System Requirements.
tion of requirements to the systems respectively those
functions and features up to the release of their imple-
mentation are administrated in one application.
Fast entry of requirements: Fast entry of requirements
and derived requirements in a grid view - without chang-
ing the form.
Tracking of all activities: OMNITRACKER Require-
ments Management Center defines workflows for specifi-
cations and requirements reflecting the current state of
progress.
Transparency: Quality control, review- and release pro-
cedures as well as versioning of specifications and re-
quirements ensure a traceable process improvement.
Web login for external access
OMNITRACKER Requirements Management Center in the context
of the V-Model and the generic HOOD INSIDE Model
1
2. OMNITRACKER Requirements Management Center
Technical features Requirements Specification Process
General OMNITRACKER Requirements Management Center controls
Requirements Management and Engineering process tool,
and monitors the process of requirements specification as a
easy and quick implementation, fast ROI whole.
Generic information model, easy adaptable to customer´s
needs Specification process includes:
Support of several levels of abstraction (e.g. Customer-, Sys- Definition of system scope (Scoping)
tem- and Design Requirements)
Definition of requirements
Providing a common understanding about a system, which
has to be developed, whose functionality and technical fea-
tures for customer and contractor
Definition of System Scope (Scoping)
Grouping and structuring of requirements in specifications
(documents) The objective is to outline the item to be developed, to iden-
Efficient OMNITRACKER data structures support linking of tify any interfaces and to define its function blocks and sub-
requirements and whose visualization about levels of abstrac- systems. In order to allow flexible stakeholder management,
tion
one person may be assigned several roles. Roles may be
Control of the completeness of derivation (traceability) via freely defined.
extensible filtering and searching capabilities
Automatically creation of documentation with report/print-out
function for specifications, requirements, use cases
Any customer - contractor interaction will be documented
HOOD INSIDE certified
Definition of Requirements
Define system scope (Scoping)
Management of roles and interests of all stakeholders
Elicitation, specification and analysis of requirements
Fast entry of requirements and derived requirements in grid
view (without changing the form)
Management of review- and release process
Management and versioning of requirements
Recording and administration of use cases
Realization/Implementation Treeview of a system referencing sub-systems and
Management of the implementation of requirements function blocks
Providing requirements for approval by the customer Definition of Requirements
Recording and communicating test results
Approval of the implementation by the customer's project Defining requirements includes the following activities:
manager
Elicitation
Process Control
Specification
Role-based authorization concept
Analysis
Workflow-based process control of specifications, require-
Review
ments and use cases
Workflow-based escalations The process includes all levels of requirements (e.g. Cus-
Miscellaneous
tomer, System and Design Requirements). Usually, all steps
will be iterated several times. Thereby the parallel specifica-
Web login to provide access to external stakeholders
tion of Customer and System Requirements is possible. The
Integration of further OMNITRACKER solutions process´ progress can be derived from the workflow state.
Elicitation
The objective of the elicitation is the recording of requests
and possible requirements, referring ideas, comments and
2
3. generic & easy adaptable
documents. During the elicitation the Customer Require-
ments are recorded firstly.
Specification
Referring to the elicitation requirements are specified. Its goal
is to provide a structure documentation and classification of a
requirement (e.g. stakeholder, priority, state) of requirement.
Requirements and derived requirements may be created and
processed from within a single form - including several levels
of abstraction.
Workflow Requirement
Realization of Requirements
OMNITRACKER Requirements Management Center imple-
ments the HOOD INSIDE certified processes. Hereby, the
Linking requirements of different levels of abstraction
whole requirement specification process from the elicitation
up to the release of requirements is administrated.
Analysis
Realization Process
In order to ensure a requirements´ quality regarding certain
quality criteria (e.g. complete, identifiable, consistent). Beyond, HOOD INSIDE processes, OMNITRACKER Re-
Requirements are analysed with regard to effort, correct in- quirements Management Center features further steps of
terpretation of wording as well as technical feasibility. The requirement mangement:
users are supported by powerful search functions and filter
options during analysis. Implementation
Test
Review Approval of Implementation
Objective of the review is the decision, if an requirement can Implementation
be accepted, has to be revised or rejected. The processing is
carried out by all stakeholders of the requirements with re- This phase refers to the development process, i.e. the imple-
view permission. These receive an automated ticket with the mentation of defined requirements to the developed system
request to verify the requirement regarding its description, respective sub-system. Any technical realisation will be
implementation approach and estimated effort and to ap- based on Design Requirements. After completion of imple-
prove the implementation of the requirement. mentation and internal tests by the contractor the system
respective sub-system are delivered in agreed development
status for test.
Test
Responsible employees of the customer, usually technical
experts, carry out the approval test. Testers comment on a
test´s status, attach measure protocols and set the workflow
state of requirements regarding to the test result to “Test
successful” or “Test failed”. In the case a test fails, a brief
3