Education / IBM DOORS / Level 02
IBM DOORS advanced course
Three days to go from using DOORS to administering it: permissions that do not turn against you, a project schema that survives growth, and traceability evidence that is already there when the audit arrives.
- Duration
- 3 days (flexible)
- Prerequisites
- Regular DOORS use
- Version
- DOORS 9.7.2, DWA and ReqIF
- Group
- Small
- Format
- On site or live online
- Lab
- Three labs on one programme
- Language
- English, Spanish or French
- Materials
- SIXE's own
01 Who it is for
You are the one they call when DOORS misbehaves
The course starts where daily use ends: when you have to decide the permission structure of a programme with three suppliers, when to break inheritance, which attributes must be mandatory, and how to send an OEM a ReqIF package that will not wreck their database.
DOORS administration
You manage users, groups, permissions and the health of the database.
Configuration management
You define the baseline strategy, milestone versioning and the delivery packages.
Senior requirements engineering
You design the attribute schema and the linking rules the whole team will then use.
02 Structure
Three days on a single programme
Sessions are closed and built for each team, so how much weight each block gets is agreed with you when the dates are set. The working case is a programme with one OEM, two suppliers and safety requirements. It is administered end to end, and every afternoon is a lab on that same scenario.
Administration and access controlDay 1
Who gets in, what they see and what they can touch. The day covers the functional administration of the tool and the design of the access model for a programme where several organisations coexist without being allowed to see each other.
Project modelling and change managementDay 2
The structural decisions: how the project information is modelled and how traceability across levels is defined, so that a customer change turns into an impact analysis instead of a manual search.
Configuration, exchange and evidenceDay 3
The delivery day: milestone versioning strategy, requirements exchange with suppliers and OEMs, and producing the evidence package your sector's certification asks for.
The detailed syllabus is sent on requestFull programme, lab briefs and attendee material. We send it to the training manager along with a proposed set of dates.
Request the syllabus03 Outcomes
Decisions you will be able to take and defend
Design the permission model
Decide who sees and who edits each part of the programme, and diagnose access problems without guesswork.
Define a schema that holds
Model the project information so that two teams on the same programme do not end up with two different vocabularies.
Design the linking strategy
Define how information connects across levels. It is the decision that costs most to change later.
Turn change into a process
Make change review a flow with owners and states, rather than a list somebody clears in bulk before delivery.
Exchange with suppliers over ReqIF
Send and receive third-party requirements without every round trip leaving the database worse than before.
Produce audit evidence
Have the evidence your sector's standard requires ready in advance, instead of rebuilding it before the audit.
Functional safety standards require bidirectional traceability between requirements, design and verification, but each one defines a different depth of evidence: ISO 26262 asks for a safety argument and Automotive SPICE for process conformance records, even though they share the same links. Day three tunes the attribute and link schema to whichever standard applies to your programme. SIXE has been delivering IBM technology training for over fifteen years.
04 Learning path
Where this level sits
Back to the IBM DOORS training hub to compare the three levels.
05 Frequently asked
Before you sign your team up
01Do I need the fundamentals course first?
+
No, if you already work with DOORS daily. The check is concrete: if you can create a formal module, link objects across modules and read a traceability matrix, you can come straight in. If not, start with fundamentals.
02Is there any DXL in this course?
+
DXL attributes and DXL layout are used as a tool, but programming in DXL is not taught here. That is the expert level, which spends all three days on the language and on automation.
03Does it cover server and OS administration?
+
It covers functional administration: licences, sessions, users, permissions, backups and database health. Installation and platform sizing we handle as a consulting service, not as classroom training.
04Can it be adapted to our programme's schema?
+
Yes, and that is the norm for closed corporate training. We start from an anonymised copy of your attribute schema and your linking rules, so the labs run on your real structure.
05Is ReqIF covered in depth?
+
Yes. It is a full block on day three, with the supplier round-trip lab, attribute mapping and conflict resolution on re-import. That is where most real problems concentrate on programmes with an OEM.
06What if our environment is DOORS Next?
+
This course is about classic DOORS 9.7.2. The DOORS Next model is different: components, streams and global configurations. It is covered at expert level, and we approach migration as a consulting project.
Tell us how your DOORS is set up
Seeing the project structure and the attribute schema is enough for us to tell you which parts of the course to expand and which ones your team does not need.
Or by phone: +34 91 198 02 43
