Case

Workshop
Requirements

Case
Workshop - Requirements
 Table of Contents
1. Workshop - Requirements............................................................................................................. 3
1.1. Assignment 1a – High-level Process Flow..............................................................................4
1.2. Assignment 1b – Define risks.................................................................................................5
1.3. Assignment 1c – Define steps to be supported by system.....................................................6
1.4. Assignment 1d – Define SMART (process) requirements.......................................................7
1.5. Assignment 1e – Define (regulatory / technology) requirements..........................................8
1.6. Assignment 1f (optional) – Prioritize requirements...............................................................9
1.7. Submit results......................................................................................................................10

Case
Workshop - Requirements

Date: 20 April 2022 CONFIDENTIAL Revision: 1.0

Document ID: Case - Workshop - 01 - RequirementsPage 2 of 5
 1. Workshop - Requirements
During this workshop you will practice the creation of SMART Requirements.

The activities for this workshop are planned in the following way:

- Assignment is shared with the workshop attendees (this document)

- Workshop attendees work in the same groups as for Assignment 1.
- For the assignment, the casus is the Hospital Transportation Device.
- Input for the assignment is the output from Assignment 1.
- Workshop attendees execute the assignment with their group and present their group’s
results at the end of the workshop.

Case
Workshop - Requirements

Date: 20 April 2022 CONFIDENTIAL Revision: 1.0

Document ID: Case - Workshop - 01 - RequirementsPage 3 of 5
 1.1. Assignment 2a – Login to RC-SLM
Login to the RC-SLM system, in which you will execute the following assignments.

Address: https://workshop.rescop.com

Login details will be shared with you by a teacher.

1.2. Assignment 2b – Define SMART (process) requirements

Output: List of SMART (process) requirements
Assignment: From the colored, marked high-level process flow from assignment 1c define SMART
process requirements for the marked steps.

Use the following sentences:

- The system must be able to… <process step (noun verb)>
o for all steps that have to be executed by the system
o for all steps that require information (output) from the system
- It must be possible to… <process step (noun verb)>
o for all steps that require input to the system
o for all steps that require interface between systems

Ensure that:
- Requirements are system independent
- Individual
- Testable

In case requirements have to be written as a solution (functional specification level), ensure these
belong to a User Requirement.

Example:
ID Requirement / Specification Priority

REQ-01 It must be possible to register the identified patient Mandatory

The patient must be identified by scanning the patient’s

REQ-01.01 Mandatory
barcode wristband

It must be possible to register what is wrong with the patient

REQ-01.02 Nice to have
after the wristband is scanned

A user must confirm in the system that the scanned patient is

REQ-01.03 Desirable
indeed the patient to be registered

Enter the requirements into the RC-SLM system as instructed by the teacher.

Case
Workshop - Requirements

Date: 20 April 2022 CONFIDENTIAL Revision: 1.0

Document ID: Case - Workshop - 01 - RequirementsPage 4 of 5
 1.3. Assignment 2c – Define (regulatory / technology) requirements
Output: List of SMART (process) requirements + SMART (regulatory / technology) requirements
Assignment: From regulations and the own quality management system (procedures / policies),
including IT policies and procedures, define requirements / constraints which are generic for any
system used within your organization. Add these to the list of SMART (process) requirements.

Consider the following types of requirements / constraints:

- Data Integrity (ALCOA)
- Security
- Single Sign-on
- Physical Environment
- IT Environment
- …

In case requirements have to be written as a solution (functional specification level, i.e., Single Sign-
on), ensure these belong to a User Requirement (what do you want to achieve with this functionality).

Enter the requirements into the RC-SLM system as instructed by the teacher.

Case
Workshop - Requirements

Date: 20 April 2022 CONFIDENTIAL Revision: 1.0

Document ID: Case - Workshop - 01 - RequirementsPage 5 of 5