back

Requirments for "Requel"

Client: Harvard University
Revision: 22

Table of Contents

Actors

Automated Assistant

The automated assistant is part of the system, but interacts with the requirements part of the system like a project user adding issues and notes during analysis. The automated assistant will be a stakeholder on all projects.

Interactive User

Project User

Project users use the system to create requirments in projects.

System Admin

System administrator users create other users and manage the system level user permissions.

Goals

Goals

  • Automated Assistance

    The system analyzes the requirements as they are added to a project and makes suggestions by adding issues to the elements.
  • Collaborative Elicitation of Requirements

    A team of technical and business stakeholders can use the system to create accurate, precise and unambiguous system requirements.
  • Discussion of Requirements

    The system supports integrated discussion of the requirements such that stakeholders can identify issues with the project elements, state multiple solutions to each issue, and pros and cons of each solution.
  • Easy to Use

    The system is easy to use so that non-technical users can contribute to the requirements without the need for specialized skills or training.
  • Flexible Process and Deliverables

    The system does not force a specific requirements elicitation process on the stakeholders. The system does not require the stakeholders to use all the features of the system.

    Goal Relations

  • Improved Understanding

    Using the system improves understanding of the requirements by all the stakeholders compared to non-integrated tools such as emails and spreadsheets.
  • Manage Users

    Create and edit user accounts.
  • Notification of Project Changes

    The system notifies the stakeholders of changes to the project. The user can customize how the notifications occur: every time a change is made, or a periodic summary.
  • Requirements defined in Natural Language

    The requirements are defined in natural language such that non-technical users do not need specialized skills to understand the requirements.

    Goal Relations

  • Secure data access

    The system secures project content from unauthorized access by users not assigned to a project or non-users of the system.
  • Work is your own

    The work done on the thesis is exclusively done by the student.

Stories

Success Story - Poor Communication in Requirements

Buddy the controller of Bailey Pet Supply has a problem; it takes over a month to close the books each quarter. Due to new disclosure requirements, Alex the CFO needs to submit quarterly results to the board of directors one week after the end of the quarter. Buddy tells Theresa, the accounting manager, that they need to close the books each quarter in less than a week. Theresa tells Buddy that the problem stems from the order processing system not being integrated with the accounting package and at the end of each month data must be entered into both systems to reconcile them manually. Buddy decides that the systems must be integrated before the end of the next quarter so that the one week turn-around for reporting can be met. Buddy meets with Dave the IT manager to discuss the work. Dave assigns Tim, one of the IT project managers, to work with Buddy to determine the requirements and estimate the work. Tim meets with Buddy and they generate a list of high level requirements. Tim gives the requirements and a rough estimate of two months to Dave, who in turn gives them to Ron, an MIS programmer, to design and develop. Ron reviews the requirements and goes back to Dave and tells him there are a lot of vague areas and he needs to get clarification from Tim and Buddy. Ron and Tim have a meeting to discuss the requirements. Ron asks Tim "What is a purchase order?" Tim response "It's a record in the purchase system that Linda enters based on information from a sales person." Ron asks "What information is in the purchase order?" Tim doesn't know and tells Ron he will ask Buddy and get back to him. Tim sends an email to Buddy and calls it a day. Buddy replies to Tim's email that he should talk to Linda to get the details of a purchase order. Tim has a meeting with Linda and gets the details on the data for a purchase order. Tim sends Ron an email with the information. Ron replies to Tim's email "Is there a database with data that I can look at for a sample?"

Success Story - Rich creates a new project

Rich logs in to the system and it displays a list of his active projects and the option to create a new project. Rich chooses to create a new project and the system displays the new project interface. Rich enters "Mobile Media Portal" for the project name and enters a short description. Rich looks over the list of existing customers and doesn't see what he's looking for and enters "Virile Mobile". The system creates the new project and adds Rich as a stakeholder with permission to edit all project entities and grant permission to other users to edit entities. The system closes the new project interface and adds the new project in the project navigation interface.

Success Story - Rich logs in to the system

Rich opens a web browser to the Requel system address. The system doesn't detect an existing user session and presents the login screen. Rich enters his username and password. The system verifies the username and password combination is correct. The system logs that Rich has successfully logged into the system and shows him a list of his open projects and an overview of recent project changes.

Exception Story - Ron fails to log in to the system

Ron opens a web browser to the Requel system address. The system doesn't detect an existing user session and presents the login screen. Ron doesn't have a username and password yet so he chooses the help option. The system displays a message that the system requires a distinct username and password and that the user should contact Dave at extension 500 or via email to dave@requel if they need a new account or are having a problem connecting. The system also displays a help message describing what to do if the user forgot their account information. Ron sends Dave an email to create him a new account.

Success Story - Theresa creates a new project

When Theresa logs in, the system determines that she has permission to create projects and displays the "Create Project" option in the system interface. Theresa chooses to create a new project and the system displays the new project interface. Theresa enters "Purchase Order System" for the project name, leaves the description blank, and leaves "Bailey Pet Supply", her default automatically supplied, as the customer. The system creates the new project and adds Theresa as a stakeholder with permission to edit all project entities and grant permission to other users to edit entities. The system closes the new project interface and displays the project navigation interface to add and edit the project's entities.

Success Story - Theresa logs in to the system

Theresa connects to the Requel system via a web browser from a link in an email message sent by the Requel system when Dave the system administrator created an account for her. The system displays the new user setup interface, prompting Theresa to confirm the personal information Dave entered about her and filling in any missing information, such as name, phone number, email address, a username and a password. When Theresa completes entering the information the system forwards her to the login screen. Theresa enters her username and password, and the system verifies it as correct. The system logs that Theresa has successfully logged into the system, and because Theresa is a novice user, the system displays the novice user interface to help her get started.

Use Cases

A user creates a new project

Stories

Primary Actor: System Admin

Scenario

  1. Primary - The system verifies that the user is authorized to create a new project and displays the option to the user in the interface.
  2. Primary - The user chooses to create a new project.
  3. Primary - The system displays an interface prompting the user for a project name, a short description, and the customer name, defaulted to the user's company name.
  4. Primary - The system verifies the project name and customer name
    1. Exception - The system informs the user the project name and customer name combination is not unique and prompts the user to change either.

A user logs in to the system

Goals

Stories

Primary Actor: Interactive User

Scenario

  1. Primary - The user access the system.
  2. Primary - The system determines the user doesn't have an active session and displays a login interface prompting the user for a username and password. The system interface includes a help option that the user can choose if they need help.
  3. Primary - The user enters her username and password and submits them.
    1. Alternative - The user chooses the help option.
      1. Primary - The system displays a helpful message of whom to contact to get a user account and instructions of what to do if they forgot their password.
  4. Primary - The system verifies the user supplied a correct username and password combination, logs the successful login and presents the user with an interface to use the system.
    1. Exception - The system informs the user that the username and password combination supplied is not valid and displays the login interface.

Glossary

Term Definition
non-technical users users of the system that are not information technology specialists or software developers.

Project Web Hosted by SourceForge.net

About - Legal - Help