Model Library Consultation Solution Tool Course Member  
 
Order | Case| Learning Resources | Training & Consulting | Solution | Model Framework | User group | Customer Area | Contact us
作者：俎涛     
ReqManager
Videos & Articles
 EA-DOORS plug-in

Product Manual: Requirements Manager - ReqManager
Author: Zhuo Tao, Dragon Fruit Software Engineering

catalogue

Product manual: Requirements Manager -ReqManager

1. Why model-based requirements management

2. What is model-based requirements management

3. What does model-based requirements management have

4. Model-based demand management tool solution

5. Model-based tracking

5.1. Requirement Trace tree

5.2. Requirements tracking table

5.3. Requirements tracking Matrix

6. Requirements change

7. Progress tracking

8. Requirement reuse library

8.1 Importing the multiplexed library

8.2 Model Reuse
1. Why model-based requirements management
Requirements are one of the most difficult things to manage in development. Requirements management involves a variety of requirements, relationships between these requirements, and the establishment of a complete traceability relationship. This involves tracking the full cycle: Requirements -> Design -> Implementation -> Test -> Deployment -> Application. In order to manage needs, people generally go through the following process:
1. Manage documents related to requirements well: However, the content of documents is unstructured and difficult to track and manage.
2. Adopt the method of itemized requirements list: establish requirements tracking. However, itemization is difficult to describe the complex content clearly.
3. Use model-based management requirements: At present, more and more people use models for analysis and design, and establish demand models, design models, implementation models and test models. The model has the characteristics of visualization, specialization, refinement and structure, which is suitable for the basis of demand management.
The form of requirements determines the ability to analyze and design complex systems, and then determines the ability to manage them. So the way requirements are managed basically determines the capability of requirements management, and the engineering team should evolve from document-based or item-based requirements management to model-based requirements management.
2. What is model-based requirements management
Model-based demand management is to model the demand, clarify the relationship between various requirements, and then transition from the demand model to the design model, the implementation model and the test model, to achieve the full cycle of demand tracking and management, including:
  • Change management: Versioning requirements. When requirements are changed, impact analysis is carried out based on the requirement tracking relationship, and then the change handling strategy is decided.
  • Schedule management: estimate workload based on requirements, assign personnel, make time plans, and track the completion status of requirements。 See the article《 Model-based Project Management》
  • Quality management: Establish quality evaluation indicators based on the demand model, perform related reviews, find problems, and give quality evaluation reports.See the article《 Model-based Quality Review 》
    • 3. What does model-based requirements management have
    What exactly does model-based requirements management entail?
  • First, there should be a model that establishes a full-cycle tracking relationship: requirements model -> Design model -> Implementation model -> Test model
  • You can then document the model and establish an association between the model and the document. Because many teams still have to deliver documentation to users or collaborators.
  • It is important that the requirements model be able to be turned into items to facilitate itemized trace management, such as the creation of trace tables and trace matrices. When you find the corresponding requirement or design through the entry, you can also switch to the model view to understand the details of the requirement and design.
  • Model-based requirement tracing: When selecting a requirement model element, the model tracing relationship can be used to find the design components that implement the requirement, the associated code files, and can be associated with the test cases that validate the requirement.
  • Requirements change management: When requirements change occurs, it is possible to quickly locate other requirements, related design, implementation, and testing based on requirements tracking relationships.
    		•
    4. Model-based demand management tool solution
    Dragon Fruit Software offers a variety of tool solutions for model-based demand management:
    Tool Function
    Modeling Tools EA:
  • Build a full cycle model: requirements model, design model, implementation model, test model.
  • Establish requirement model tracking: Establish the tracking relationship between various models.
  • Requirements version management: Build versions of the requirements model and compare the differences between the versions.
  • Requirement state management: Requirements of various states can be listed in a kanban way and the status of requirements can be tracked.
    • Demand Management plugin -ReqManager:
  • Generate a tracking view based on the model：
  •      √ Trace tree: 1
  •      √ Tracking table (fixed number of columns) - Assistant
  •      √ Tracking table (extensible)
  •           • Trace table (element type), generate trace table
  •           •  Tracking table (package location), can generate documentation
  •      √ Trace matrix: 1
  • Use case realization analysis
  • Model list, generate documentation
  • Document generation based on requirements model - Document generator
  • Requirements change management: You can submit changes, review changes, and track the status of changes
  • Requirement reuse: Establish a requirement reuse template library to reuse existing requirements.
  • Requirement review: It can establish evaluation indicators for requirements, perform review, and give demand quality reports. // Based on Qualitor- Quality Manager.
    		•
    Requirements management tool WebEA based on Model library:
    Video: Model-based requirements management using Web+EA
  • Browse the requirements model and transform it into a requirements list view
  • Relate and manage requirements
  • Track the status of requirements
  • Trace demand relationships: trace tree, trace table, trace matrix
  • Quality review of requirements
  • Change management of requirements
  • Develop work plans for requirements and track progress.
  • Create tasks based on requirements, make plans, and track progress.
  • Provide requirements reuse library, reuse requirements.
  • Perform statistical analysis of requirements and provide demand reports.
    		•
    Document Generator -DocGenerator:
    Video: Model documentation Generator
    Video: Model + document association and management
  • Define the mapping between the requirements model and the requirements document
  • Automatically generate requirements documents
  • Associate requirements documents and requirements models for association management.

    • MBSE Platform -iSpace:
    Video: Requirements Management based on iSpace
  • Establish requirements work guide and generate requirements work guide document
  • Establish the capability model of the required personnel and generate the capability guide document.
  • Manage requirements related artifacts: models, documents, articles.
  • Conduct requirement modeling, design modeling, implementation modeling, and test modeling
  • Associate the requirements model to the document
  • Quality review of requirements
  • Provides requirements for tracking view: tracing tree, tracing table
  • Provides a template library that allows you to reuse requirements models.

    • Here is a brief introduction to the requirements management functions supported by ReqManager:
    5. Model tracking
    Establish a tracking relationship based on the model: Requirements -> Design -> Implementation -> Test.
    You can transform the requirements tracking model into trace views: trace tree, trace table, trace matrix.
    In this way, based on the requirements tracking view, you can: Forward analysis: Confirm whether the requirements are implemented and tested.
  • Confirm whether the requirements are implemented and tested.
  • Reverse analysis: Software and hardware implementation of what requirements.
  • Change impact analysis: What implementations and tests are affected by changes in requirements.
  • Defect impact analysis: Which requirements are affected by software defects.
    		•
    Here are the three requirements tracking views provided by the requirements Manager ReqManager:
    5.1 Requirement Tracing Tree
    Using the requirements management tool ReqManager, you can select a requirement and then analyze the associated design, implementation, and test model elements to generate a requirements tracking Tree. The user selects an element and can:
  • Locate the location of the element in the model,
  • Browse the diagram associated with the element.
    • 5.2 Requirement Tracking Table
    In the requirements manager ReqManager, users can specify the type of elements filtered by the columns of the trace table, and then perform trace table analysis, output a trace table with multiple columns, select one of the elements, you can locate the corresponding element in the model.
    5.3 Requirement Tracking Matrix
    ReqManager's trace matrix is used to show the trace relationships of two types of model elements. If you can specify the types of elements filtered by rows and columns of the trace matrix, the trace matrix displays the trace relationship between these two types of elements. The user double-clicks a row or column of the trace matrix to locate the corresponding element in the model.
     
    6. Change management
    Requirement change is one of the main challenges of requirement management. When the requirement changes, it is necessary to implement the change control process to ensure that the change is controllable. The impact analysis of the change is the main basis for deciding whether to accept the change, and model-based tracking can provide strong support for the impact analysis of the change. The requirement manager ReqManager provides support for the whole process of requirement change management, as shown in the following figure:
    7. Progress tracking
    In a project, it is common to orchestrate the implementation plan for the requirements and then track the implementation progress of the requirements. ReqManager offers two modes of progress tracking:
  • Time progress tracking: Make a time plan for each requirement and provide a Gantt chart to track progress.
  • Status tracking: Assign states to each requirement, then set different states for the requirement as the work phase unfolds, and track progress.
    		•
     
    8. Requirement reuse library
    Many of the requirements and design models of multiple products or projects are similar. ReqManager provides model template library, which can save existing models to the model library, reuse the model library models in subsequent modeling, and quickly establish a complete set of project models.
    8.1 Importing the multiplexed library
    Models can be saved in a reusable model library as a reusable resource for future projects.
    8.2 Model Reuse
    When building a new model, you can use the existing model library model as a template, through reuse, quickly create a new model.