Support Document for Requirements NDSi
New Direction in Staffing Interface – Project Requirements: Supporting Documentation
BACKGROUND INFORMATION
The information contained in this workbook was compiled and developed by the New Direction in Staffing Interface (NDSi) project team. The requirements were gathered directly from users in an effort to inform Government of Canada (GC) modernization and/or improvement initiatives.
This workbook contains a Requirements worksheet which contains all of the in-scope requirements that the NDSi project team developed through direct interaction with users. It also contains a non-exhaustive list of current-state GC staffing requirements that the NDSi project leveraged to begin our discovery journey.
The requirements can be filtered based on any of the variables listed at the top of the spreadsheet in order to identify a user’s goal, what it will take to achieve this goal, and the associated conditions for success.
GLOSSARY
Variable Name |
Brief definition |
ID# |
Identification number: A unique alphanumeric value used to identify a use case. For example, in this case, the “Apply for a Job” use case is identified as UC7. |
Stakeholder |
The actor or role directly implicated in the requirement. |
Use Case |
A use case represents the main reason why a stakeholder will interact with a solution or system. It is the user’s goal. For example, in the context of the NDSi project, one of the main reasons a job seeker will access the New Direction in Staffing Interface is to apply for a job. |
ID#2 |
Identification number 2: A unique alphanumeric value used to identify a user story. For example, in this case, the first user story within the “Apply for a Job” use case; “I need to be able to fill out the job application”, is identified as US7.1. |
User Story |
User stories describe what a stakeholder needs to be able to do in order to accomplish a goal when interacting with a solution or system. Use cases are made up of related user stories. |
ID#3 |
Identification number 3: A unique alphanumeric value used to identify an acceptance criteria. For example, in this case, the first acceptance criteria of the first user story; “I need to be able to fill out the job application”, for the “Apply for a Job” use case is identified as AC7.1.1. |
Acceptance Criteria |
Acceptance criteria describe the requirements, outcomes, or conditions that must be met in order to successfully complete a user story en route to completing a goal for a solution to be acceptable. |
Page details
- Date modified: