These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Requirements Management
- Data model
The tables behind Requirements Management
Requirements Management ships with 13 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 13
- Features
- 6, plus shared settings
- Change it
- Add fields and tables in Proto
How the model is organised
Organization and delivery context
Organizations, Projects and team members identify the business, engagement and people.
Requirement work
Requirements hold the requested outcome and revision; requirement items carry assigned work; Baselines capture acceptance criteria and target dates.
Verification and change
Verification findings and change impacts describe project concerns and their owners.
Time and evidence
Time entries, review decisions, operation receipts and record attachments document work and its outcome; Users holds user records.
Every table, by feature
- Project context8
- Requirement register6
- Requirement items5
- Baselines and acceptance7
- Verification and change7
- Time and evidence7
- Shared and settings1
- Organizations
Client and internal business organizations that projects are delivered for.
- Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Requirements
Requirement records, each with revision, baseline and lifecycle status.
Linked to Projects, Team members, Organizations - Baselines
Dated requirement baselines and whether their target date was met.
Linked to Projects, Team members, Requirements, Organizations - Verification findings
Findings raised while verifying requirements to a revision.
Linked to Projects, Team members - Change impacts
Assessed change impacts and their mitigation for a project's requirements.
Linked to Projects, Team members - Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Requirement items
- Requirements
Requirement records, each with revision, baseline and lifecycle status.
Linked to Projects, Team members, Organizations - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Organizations
Client and internal business organizations that projects are delivered for.
- Team members
Delivery staff with role, practice and weekly capacity.
- Requirement items
Line items that decompose a requirement and carry its acceptance detail.
Linked to Requirements, Team members, Projects - Baselines
Dated requirement baselines and whether their target date was met.
Linked to Projects, Team members, Requirements, Organizations
- Requirement items
Line items that decompose a requirement and carry its acceptance detail.
Linked to Requirements, Team members, Projects - Requirements
Requirement records, each with revision, baseline and lifecycle status.
Linked to Projects, Team members, Organizations - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Requirement items
- Baselines
Dated requirement baselines and whether their target date was met.
Linked to Projects, Team members, Requirements, Organizations - Requirements
Requirement records, each with revision, baseline and lifecycle status.
Linked to Projects, Team members, Organizations - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Organizations
Client and internal business organizations that projects are delivered for.
- Team members
Delivery staff with role, practice and weekly capacity.
- Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members, Requirements - Record attachments
Files attached to delivery records.
Linked to Team members, Requirements
- Verification findings
Findings raised while verifying requirements to a revision.
Linked to Projects, Team members - Change impacts
Assessed change impacts and their mitigation for a project's requirements.
Linked to Projects, Team members - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Requirements
Requirement records, each with revision, baseline and lifecycle status.
Linked to Projects, Team members, Organizations - Baselines
Dated requirement baselines and whether their target date was met.
Linked to Projects, Team members, Requirements, Organizations - Team members
Delivery staff with role, practice and weekly capacity.
- Record attachments
Files attached to delivery records.
Linked to Team members, Requirements
- Time entries
Hours booked by a team member against a task and project.
Linked to Team members, Projects, Requirement items - Requirement items
Line items that decompose a requirement and carry its acceptance detail.
Linked to Requirements, Team members, Projects - Projects
Engagements delivered for an organization, with budget and schedule.
Linked to Organizations, Team members - Team members
Delivery staff with role, practice and weekly capacity.
- Review decisions
Recorded approval decisions on delivery subjects.
Linked to Team members, Projects, Requirements - Operation receipts
Evidence that a delivery operation was executed.
Linked to Team members, Requirements - Record attachments
Files attached to delivery records.
Linked to Team members, Requirements
Keys and references
A Requirements record requires a Projects reference. Each requirement items record requires a Requirements parent, and may also reference Projects and team members. Baselines require Projects and may reference their parent Requirements record. Time entries require a team members person and Projects project, with an optional requirement items task. Verification findings and change impacts require Projects. Review decisions can link to a related project and parent requirement. Operation receipts can point to a parent requirement and carry a stable operation key and expected revision.
Migration order
- Import Organizations and team members, then map Users and access.
- Add Projects with their organization and owner references.
- Add Requirements with project, owner and revision.
- Add requirement items and Baselines beneath the correct requirement and project.
- Add verification findings, change impacts and time entries after their parent records exist.
- Import review decisions, operation receipts and record attachments only after their referenced work is resolved.
Set up Requirements Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.