Introduction

ENOVIA's design review apps allows you to thoroughly review your designs and identify issues from Dashboard apps that can be accessed anytime, anywhere, and using any device.  

These apps are:

1. 3D Markup app:
   1. Enables lightweight reviews using graphical markers and text annotations.
2. Design Validation and Design Review apps:
   1. Facilitates a comprehensive, collaborative, and robust product review process with the real-time visibility and complete traceability.

However, reviewing the non-CAD objects that are part of the overall product development process is equally important. This is vital to eliminate associated costs and bring products to the market faster.

Following are some of these non-CAD objects:

1. Documents [Process Documents, Attachments, Specifications, Reports etc.]
2. Product Requirements [Created in the 3DEXPERIENCE Platform as Requirement or Requirement Specification objects using the Requirement Engineer (TRM) role]

In this blog, we will see how you can also seamlessly review such non-CAD objects.

Reviewing Documents using the 3D Markup app

Documents play a pivotal role in every stage of the product development process. Essential documents such as Design Documents, Specifications, and Standard Operating Processes (SOPs) require meticulous review before releasing them for a downstream usage. 

WHAT: 

In the 3D Markup app, you can review the PDF and Microsoft Office documents available in the 3DEXPERIENCE Platform. Note that, the capability to review Microsoft Office documents is available on cloud only.

HOW: 

This app allows you to review documents and record discrepancies. You can use the comments feature to effectively describe your concern. Comments are available in the Rich Text format that allows you to: 

• Use Bullets or Numbering for ease of understanding and improved clarity of the review.
• Add a Hyperlink of external or internal references to quickly access the relevant data.
• Tag any stakeholder to easily notify them about further actions.

You can also use markers of various shapes to highlight specific text or parts of the document. Further, you can raise a formal issue and assign it to the stakeholders without leaving the app.

Refer to the following video for more information

Reviewing Product Requirements using the Design Validation and Design Review apps

Following are some of the commonly found issues during requirement reviews: 

• Ambiguity, Incompleteness, Inconsistency
• Unrealistic Requirements or Scope Creep
• Misalignment with Stakeholder Needs
• Poorly Defined Acceptance Criteria

Reviewing product requirements to ensure its correctness is critical for an efficient product development process. In this section, we will see how you can use the Design Validation and Design Review apps to conduct a collaborative review process with the complete traceability, identify issues and communicate it to the Requirement Engineer, and trace the issue until its resolution.

The following image illustrates this process:

STEP 1: Review Preparation

You can use the Design Validation app to orchestrate the collaborative review on requirements. To begin, you can define the following important review elements:

• Context: When you begin a review on the Requirement Specification, it is automatically marked as the Context of the review.
• Validated Object: This section allows you to define the objects to be validated during the review. From your context Requirement Specification, you can drag-and-drop specific Requirement, Chapter or a Comment in this section.
• Checks: This section allows you to define the objectives of the review.
• Markups: Markups are placeholders to accommodate specific types of review observations (Comments).
• Assignment: You can leverage the Comments tab in the Information Panel to mention reviewers and assign them a specific part of the review.

STEP 2: Collaborative Review

Reviewers can use the Design Review app to document their review observations on requirements using various shape markers and comments. All the comments are consolidated under the selected markup in the comments panel. Further, reviewers can also collaborate and respond to each other’s comments using the Reply option. Once the review is complete, you can promote the maturity of the review to the Frozen state.

STEP 3: Decision Making

Upon going through all the comments from each reviewer, you can highlight a specific review comment and further raise a formal Issue or Change Action for it, in case the requirement requires a further investigation/resolution. The Issue or Change Action that you create for a specific Highlight is displayed in that Highlight section.

When you raise an Issue, the Affected Items and Context of the issue are automatically populated based on the Review details. In addition, the Highlight is automatically added in the Attachment section of the issue. After completing the issue definition, you can assign it to relevant stakeholders.

STEP 4: Issue Resolution

Stakeholders (Requirements Engineer) is automatically notified about the assigned issue. You can open the attached Highlight in the 3DPlay app to understand issue of the requirements thoroughly. After modifying the affected Requirement/Chapter/Comment, you can attach it in the Resolved By section of the issue and promote the issue to the In Validation state for further approval.

STEP 5: Issue Validation

The Validation Management app provides you to a centralized access to all the review elements. You can find out the status of the issues raised against each highlight and further open them to validate. You can mark the Issue as Completed after validating the updates in the Requirements.

Once all the outstanding issues raised during the review are completed, you can promote the Checks status to Passed, Validation status to Passed and the Review status to Released. This indicates successful completion of the review.

Refer to the following video for more information.