Prototype Reportversion 1.0

Prototype ReportVersion 1.0

Prototype Report

Transportation Grant Fund

Team 14

Full Name / Primary Role / Secondary Role
Muruganantham Raju / Project Manager / Feasibility Analyst
Kirill Khistyaev / Software Architecture / Project Manager
Karim Sacre / Prototyper / Requirements Engineer
Reza B’Far / IIV&V / Quality Focal Point Secondary
Stephan Rice / IIV&V / System Requirements Engineer
Zhanna Seitenova / Life Cycle Planner / Requirements Engineer
Ayman Khalil / Operational Concept Engineer / Software Architecture

Version History

Date / Author / Version / Changes made / Rationale
09/22/11 / Karim Sacre / 1.0 /

Changes made from initial prototype template

Initial prototype report

Prototype Report...... i

Version History...... ii

Table of Contents...... iii

Table of Tables...... iv

Table of Figures...... v

1.Introduction...... 1

1.1Purpose of the prototype report...... 1

1.2Status of the prototype...... 1

1.3Tools used for the prototype...... 1

2.Navigation Flow...... 2

3.Prototype...... 3

4.System Description...... 11

Table of Tables

Table 1: User home page

Table 2: Create/Update Project

Table 3: Project listing

Table 4: Generate reports

Table 5: Admin delete/edit user

Table 6: Add user account

Table 7: Financial information

Table 8: Upload Signed documents

Table of Figures

Figure 1: Navigation Flow of LADoT Database System

Figure 2: Home page

Figure 3: Create/Update Project

Figure 4: List projects

Figure 5: Generate reports

Figure 6: Edit/Delete User account

Figure 7: Add User Account

Figure 8: Add Financial Information

Figure 9: Accountant upload of document

Prototype ReportVersion 1.0

Introduction

1.1.Purpose of the prototype report

The prototype report gives the client a better understanding about how his product is going to turn out.
The current version of prototype document provides the following:
- Navigation flow diagram that shows the different functionalities of each user in thesystem. Each user is given different privileges.
- Screenshots to allow the client to have a better view of the final product and thus allow him to make changes early in the development.

The following prototype mitigates the risk of misunderstanding/misinterpretation of customers’ expectations for the proposed web based interface system. It also provides a base to start our engagement with wide spectrum of stakeholders in LADOT.

1.2.Status of the prototype

This is an initial prototype so no previous versions were created.
The requirements were not clear during the first client meeting, that's why we decided to present some screenshots of the system in our perspective. During our next client interaction, we will be able to show these drawings and discuss more on the client’s understanding of the system.
The client has still not given their first evaluation on this initial prototype.

1.3.Tools used for the prototype

Two tools were used to build the initial prototype document:

1. Balsamiq Mockups ( We had decided to use Blsamiq tool because we found that it was very user friendly and free. However, after more careful consideration, we found out that the tool only offers mock-ups which will not be enough for us for our next prototype document. In the new prototype report and after our meeting with the client, we will be implementing some solution to the riskiest modules in the system.

2. Microsoft Visio: That tool was used to create the navigation flow diagram.

Navigation Flow

Figure 1: Navigation Flow of LADoT Database System

3.Prototype

Table 1: User home page

Description / When a project manager logs in, he gets 5 options to choose from.
List all projects and list my projects (table 3), Create Project (table 2), Generate reports (table 4) and log out.
Related Capability / List all the options that a project manager has access to.
Pre-condition / If the user successfully logs in, he gets to this screen shot.
Post condition / The post condition in that case depends on the user’s input. If he presses any of these buttons he will be redirected to the specific page.

Figure 2: Home page

Table 2: Create/Update Project

Description / Figure 3 shows how the user would be able to create a project or update information of a specific project. The user has to enter the project name, status, date of completion, description, and add a file to the database for it to be completed.
Related Capability / Create or update a project.
Pre-condition / User entered create project from the home page or from the navigation bar on the left of the screen. This screen also appears if the user clicked on edit a project in the project list page.
Post condition / The project is updated or created

Figure 3: Create/Update Project

Table 3: Project listing

Description / This page lists all the projects in the LADoT system.
List my projects is a subset of List all projects in the sense were only the project that the logged in user is responsible of are shown.
The user can only edit the projects he is signed up to. If he is not signed up to the project then he can only see the details of it and the edit button will be grayed out.
Related Capability / List all and my projects to be able to edit or see more details about each project.
Pre-condition / User entered list all projects or list my projects from the home page or from the navigation bar on the left of the screen
Post condition / If the user pressed the edit button he will be redirected to the create/update page (table 2). Else if the user pressed the details button, more details about the selected project will be shown.

Figure 4: List projects

Table 4: Generate reports

Description / Project Managers and Program managers can generate reports about a certain project. All they have to do is choose the project name and the report type (these details are still not specified by the client) and the date and then press the generate button.
Related Capability / Generate project reports or other types of reports
Pre-condition / User entered generate reports from the home page or from the navigation bar on the left of the screen
Post condition / A report will be generated with all the details asked for in the form shown in figure 5.

Figure 5: Generate reports

Table 5: Admin delete/edit user

Description / Figure 6 shows how the admin has access to all the user accounts information. Admin can edit and delete any user on the system. The accounts are placed in a table to facilitate the administrator’s view of the users information.
Related Capability / Edit and delete user accounts
Pre-condition / Admin has to log in to the system and he will get full access to the system accounts.
Post condition / Changes are made to the user account list. For example if a user has been deleted, the table gets updated and 1 row gets deleted from the table.

Figure 6: Edit/Delete User account

Table 6: Add user account

Description / Figure 7 shows how the admin creates a new user account and adds it to the system. The admin has to enter all the information needed and has to create the username and password (once created the information will get sent to the added user by email). Generate username creates the username for the new user (the username will be generated last_firstname for example). Once the button is pressed the username will appear in the text field.
Related Capability / Add an account
Pre-condition / Admin has to log in to the system and click on the add user on the left navigation bar
Post condition / A user will be added to the user accounts table and can be seen once the admin enters the list users page (left navigation bar)

Figure 7: Add User Account

Table 7: Financial information

Description / Figure 8 shows how the accountant adds financial information into a project. The project name is grayed out because the accountant shouldn’t be able to change the name of the project but it is there to know what project she is entering information to.
Related Capability / Add financial information to the project’s file
Pre-condition / The user has to go to List Projects (similar to the project managers list project’s page figure 4) and choose the project to add financial information to.
Post condition / The project will get updated with the new information added by the accountant.

Figure 8: Add Financial Information

Table 8: Upload Signed documents

Description / In figure 9, the accountant choosesfrom a drop down list the name of the project she wishes to upload the file to. The user then browses for the file on their computer and uploads it.
Related Capability / Attach the signed document to the given project.
Pre-condition / Press Upload Signed Document from the left navigation menu.
Post condition / The file will be uploaded and added to the projects details.

Figure 9: Accountant upload of document
4. System Description:

There are four types of user accounts in this system (Figure 1). Each type has its own functionality and its own features:

Project/Program Manager account:

These users are the most important users in that system. As it shows in figures 2,3,4 and 5, PMs are allowed to create and edit reports.

Administrator account:

The administrator like always has full control of the system. He makes sure all the accounts are running correctly, he adds and delete accounts and manages the projects as well (only if asked to).

Accountant account:

Accountants cannot change the project details. They can only attach signed reports to the project and add or edit financial information.

Guest account:

Guests are all users that did not log in to the system but are still in the LADoT secure connection. Guests can access the projects list but cannot modify or add anything to the projects. They are only able to see project details.