Case Study – EasyBook Appointment Software

In our last discussion, we spoke about clearly defining requirements. 

What I’d like to talk with you about today is a case study demonstrating such requirements.

Enter EasyBook

Back in early 2012, we had a request from a court reporting company to design simplified, lightweight booking appointment software. Their main requirements stated that the application was to be as easy-to-use and as lightweight as possible. Some of their detailed requirements included:

-Automatically generating a custom Microsoft Word document based on manually entered fields.
-Having lawyer, reporter and offices directories
-Importing client directories from a 3rd party commercial off the shelf (COTS) platform
-Limiting the number of bookings per office.

There were a whole host of other requirements, but I think you get the gist of it.

We were able to track the requirements in a RVTM – A Requirements Verification Traceability Matrix. A RVTM basically traces requirements to other documents, such as requirements documents, detailed design documents and architectural documents. 

Requirements Verification Traceability Matrix

Requirements Verification Traceability Matrix


 We were quick to gather all requirements and come up with a first-pass solution within a few weeks. After some additional back and forth, tweaking features and adding others that were within scope – we came up with a polished product. Here’s our finished application – Easybook:

Note that we got full permission from Discovery Transcript Services prior to creating this video. They were more than willing to allow us to share some of our previous work with the world!

If you have requirements for a software platform, please contact us describing the details. We’re always willing to help!

Case Study – EasyBook Appointment Software was last modified: May 11th, 2014 by Paulo R

Leave a Reply

%d bloggers like this: