RequirementONE The Sign-in Sheet Project worksheet

The Sign-in Sheet Project worksheet let's you step through a requirement management example using a selection of the core features available in RequirementONE.

Part 1 – Setup a Project

Set up a RequirementONE Project called “Sign-in Sheet Project - <Name>” where <Name> is your name.           

Edit the project details and add the following overview information about the project.

The purpose of the project is to product a draft Word template for a sign-in sheet used to track class attendance.

In the same setup page, invite at least one colleague ("user") to your project. Ideally invite between three and five.

Part 2 - Plan

Under the Project's Plan App, create the basic steps for the project.

Use one category or task for the Plan.

Under this top level category, add sections, or tasks, which are the seven basic steps of the the systems development life cycle (SDLC) and putting at least one subtask in each section.

Assign the tasks to different members of your project. If you only have one member of your project, then assign all the tasks to yourself.

Part 3 – Functional Requirements

In the Specifications App set up a Specification called Functional Requirements. Now add a field called Priority with three values:

  • High
  • Medium
  • Low

Use these Guidelines:

  • Create your own ID.
  • For Name, enter the statement of the requirement in the below list.
  • For Description, make up some suitable details.
  • Enter a value of “High” for requirements 1 to 4.
  • Enter a value of “Low” for requirement 5.

Add the following requirements:

The sign-in sheet shall:

  1. Have a field for students to enter their first and last name.
  2. Include the name of the course.
  3. Have fields to specify the date and the week number of the class.
  4. Provide sufficient space on one page to allow 60 students to sign in.
  5. Fit on a standard US Letter or A4 page

Part 4 – Use Cases

In the Specifications App create a second specification and within that specification, invent two Use Cases, such as these:

  • ID: UC1
  • Name: Set up template
  • Description: Instructor prepares a template for a particular week and sets it on the table for students to sign
  • ID: UC2
  • Name: Sign Sign-in Sheet
  • Description: Students enter the class and sign the sign-in Sheet

Part 5 – Issues

From the Issues App, create a Review called All Issues and put these issues / clarifying questions in that Review:

  1. Who will the users be?
  2. What are reasons why you or other people would use the sign-in sheet?
  3. What problems do you expect this sign-in sheet to solve for you?
  4. Where do you need access to the sign-in sheet from?
  5. When do you need the sign-in sheet to be available, realistically?


Here are some things you can do to enhance your project.

Create Custom Fields

Within a specification, Custom fields are a great way to organise and assign owners to your data. You can use these fields to filter your work.

  • Actor
  • Trigger

Organize data

Use the Table of Contents for the Use Case Family to organize your records as the number of Use Cases increases.

Include Attachments

Consider using an attachment to provide more details, such as activity charts, for your Use cases and other requirements, including:

  • Project Vision
  • Business Process Specification
  • SRS – System Requirements Specification
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk