1. aras.comCopyright © 2013 Aras. All Rights Reserved.
DOMOREA C E 2 0 1 3

2. aras.comCopyright © 2013 Aras. All Rights Reserved.
A C E 2 0 1 3
REQUIREMENTS MANAGEMENT DEEP DIVE
Dig into the technical details and get
started managing multi-discipline
requirements for complex products

3. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 3
Agenda
 Product Overview
 How RM ties into PLM
 Brief Product Demonstration
 New grid and html editor
 Data Model
 New Itemtypes and Relationships
 Dependencies
 Customization
Slide 3

4. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 4Slide 4
Concept
Requirements
Design
Architecture
Implementation
Mechanical
Software
ElectricalProcesses
Standards
Practices
Application
System
Subsystems
Components
PLM
(Mechanical)
Access
Access
Requirements
System
ALM
?

5. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 5Slide 5
Concept
Requirements
Design
Architecture
Implementation
Mechanical
Software
ElectricalProcesses
Standards
Practices
Application
System
Subsystems
Components
validation
verification
traceability
Concept
Requirements
Design
Architecture
Implementation
Mechanical
Software
ElectricalProcesses
Standards
Practices
Application
System
Subsystems
Components
Integrate RM Across Disciplines
PLM
(Mechanical)
Access
Access
Requirements
System
ALM

6. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 6
Why RM Embedded in PLM?
 Verification - Are we designing the correct system/product?
 Have we listened to our customers and captured their needs?
 Are we making what’s ideal for the market?
 Versioning - Are we still making the correct system/product?
 Keep our requirements synchronized as the system evolves
 See how our requirements have historically evolved
 Traceability - Have we developed the system/product correctly?
 Do the systems/products/documents satisfy the requirements?
 Have we missed anything?
 Close the Loop - Validate with our customers that we are meeting
their needs
Slide 6

7. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 7
Anything as a Requirement
Slide 7
http://www.url.com

8. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 8
Aras Requirements Management
 RM + PLM = Unified Data Model
 Multi-Discipline Requirements Hierarchy
 Secure Extended Enterprise Requirements Gathering
 Requirements in Documents, Chapters, and Content
 Requirements as part of Configurations
 Requirements under Change Control
 Requirements as Affected Items on a Change
 Requirements Verification & Validation
 Requirements Trace Matrix
Requirements Integrated
Slide 8

9. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 9
Demonstration
Slide 9

10. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 10
Data Model - Itemtypes
 Requirement
 The item that defines a requirement, test case step, spec
paragraph, etc.
 Building block of a Requirement Document
 Requirement Document
 A collection of requirements
 Represents a Specification, Test Plan, etc..
Slide 10

11. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 11
Data Model – Relationships
 Requirement Doc Requirement
 Link between RM Doc and Requirement
 Requirement Doc RM
 UI Relationship for grid
 Requirement Doc Files
 Requirement Doc RM
 UI Relationship- reverse item lookup
Slide 11

12. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 12
Data Model- Relationships
 Requirement External Link
 Link to URL’s
 Requirement Out Link
 Link to other Requirement item
 Requirement In Link
 UI relationship- reverse item lookup
 Part Requirement
 Relationship from Part to Requirement
 Dependency on PE
Slide 12

13. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 13
Customization
 Methods
 40 New methods
 All start with rm_
 Reports
 Reporting Services reports- Community Download
 XSLT Reports included
Slide 13

14. aras.comCopyright © 2013 Aras. All Rights Reserved. Slide 14
Discussion & Tech Talk
Slide 14