ITPM515 Business Analysis Fundamentals Sample Assignment

Requirements Format and Traceability

The user story format for Egrants project shall be like:

As a user, I need log in credentials, so that I can submit my Egrants application

The Use Case format for Egrants project shall be like:

Actors

• User
• System

Brief Description

The web portal for eGrants shall allow users to print the confirmation page for submission

Flow of Events

Preconditions

• The user shall have an account with the Egrants website.
• The user shall have filled in all the required details for submitting the application.
• The user shall have successfully submitted the application.

Basic Flow

1. The system shall let the user submit the application for Egrants.
2. The system shall prompt the user the application has been submitted successfully.
3. The system shall provide the user with Application number.
4. The system shall prompt user to print the confirmation page for their records.

Alternative Flows

1. The system shall prompt the user that the application could not be submitted successfully.

Post conditions

• The user shall be able to use the application number to track their status.

Requirements Traceability: Each Business requirement shall be identified by a unique id and a corresponding user requirement; system requirement and test requirement will be documented in the requirements traceability matrix. Thus, at any given point, requirements can be tracked and corresponding development and test cases can be referred.

Change Management Process

The process to manage change is to access the scope of the change and defining the impact on the organizational goals. The problem is then analyzed to check if it is valid. This analysis is forwarded to change requestor who may request for detailed requirements. The proposed change is then analyzed based on system requirements. A decision is then taken if the change is to be processed or rejected.

To implement the change, the Change Request document is documented and signed off before the requirements specification document is modified.

Business Process

Customer Classes or Actors

Individuals

Businesses

Agencies

Functional Requirements

Goal: To develop a grants management web portal which will serve as an enterprise approach for state agencies to apply for grants online and maintain grants information within individual customer state agencies. The system shall further automate application handling process by enabling SMEs of individual agencies to evaluate and approve the applications by applying their own business rules using standardized templates and scoring mechanisms

Attributes: The web portal shall be user-friendly, simple, secure and intuitive so that users can easily navigate and find solution. 

Use Case 1

Actors

• User
• System

Brief Description

The web portal for eGrants shall allow users to register on the website using a valid SSN, Email id and Password

Flow of Events

Preconditions

• The user should have a valid email account.
• The user shall have a valid phone number.
• The user shall have a valid SSN.

Basic Flow

1. The system shall prompt user to enter personal information like Name, DOB, SSN, phone number and email id on the registration form to register.
2. The system shall prompt the user to provide with the code sent through text message.
3. The system shall prompt the user to create a password which must have 8 characters, at least one Capitalized letter and at least one symbol.
4. The system shall prompt user to select 2 secret questions from the pick list and provide their answers for security.

Alternative Flows

1. The system shall prompt the user if the Email id is not valid.
2. The system shall prompt the user that code provided through text message does not match.
3. The system shall not accept the password created if the 3 conditions are not met.

Post conditions

• The user shall be able to provide with the email id that is registered, every time he/she tries to log in.
• The user shall be able to provide the unique password, every time he/she tries to log in.

Use Case 2

Actors

• User
• System

Brief Description

The web portal for eGrants shall allow user to provide with Bank account details.

Flow of Events

Preconditions

• The user shall have a valid bank account with a nationalized bank.
• The user shall have a valid routing number.

Basic Flow

1. The system shall prompt user to provide Bank account number where the funds needs to be transferred.
2. The system shall prompt the user to provide with the routing number associated with that bank account
3. The system shall prompt the user that the bank account information is saved to their account.

Alternative Flows

1. The system shall prompt the user if the bank account number is not valid.
2. The system shall prompt the user if the routing number is not valid or associated with the bank account number provided.

Post conditions

• The bank account shall be credited with the funds once the application is approved.

Use Case 3

Actors

• User
• System

Brief Description

The web portal for eGrants shall allow user to check their account status.

Flow of Events

Preconditions

• The user shall log in to the system using their registered Email id and Password.

Basic Flow

1. The user shall click the account status button.
2. The system shall prompt the user to provide answers to the secret questions.
3. The system shall provide user with the account status saying Approved, Rejected or Pending

Alternative Flows

1. The system shall prompt the user that the email id is not registered with the system.
2. The system shall prompt the user if the Password is wrong.

Post conditions

• The Account status shall be updated as soon as there is a change in the status of the application.

Use Case 4

Actors

• User
• System

Brief Description

The web portal for eGrants shall allow user to Edit/Add Bank Account details.

Flow of Events

Preconditions

• The user shall log in to the system using their registered Email id and Password.

Basic Flow

1. The user shall click the Edit/Add Bank Account button.
2. The system shall prompt the user to provide answers to the secret questions.
3. The system shall allow user to edit the existing bank account or add new Bank Account details.
4. The system shall notify the user through Email and text message regarding change in Bank Account information.

Alternative Flows

1. The system shall prompt the user if the bank account number is not valid.
2. The system shall prompt the user if the routing number is not valid or associated with the bank account number provided.

Post conditions

• The system shall be update the account holder’s information with new Bank Account details.

Use Case 5

Actors

• User
• System

Brief Description

The web portal for eGrants shall allow user to submit application for approval of funds requested.

Flow of Events

Preconditions

• The user shall log in to the system using their registered Email id and Password.
• The user shall have a valid Bank Account associated with their Egrants portal account.

Basic Flow

1. The user shall click the Apply for grants.
2. The system shall provide the user with the form to be filled out.
3. The user shall fill in all the required fields.
4. The user shall click the submit Button

Alternative Flows

1. The system shall prompt the user to fill in the required details.

Post conditions

• The system shall prompt the user that the application has been submitted.
• The system shall provide the user with requisition number.

Use Case 6

Actors

• User
• System

Brief Description

The web portal for eGrants shall allow users to Log Out of their account.

Flow of Events

Preconditions

• The user shall log in to the system using their registered Email id and Password.

Basic Flow

1. The user shall click the Log Out button.
2. The system shall prompt the user that they have been logged out.
3. The system shall allow user to Log In again.

Alternative Flows

1. The system shall prompt the user to save the changes before logging out.

Post conditions

• The system shall be log out the account holder from the web portal.

Non-Functional Requirements Defined

1. Response time to the web portal shall be minimum.
2. The background color of the website shall be Blue in color.
3. The website shall be developed using responsive web designing.
4. The user data shall be recorded and maintained into the database.

Management Report

Approval Report

Pending Report

Denial Report

Approvals