Prototype Report Version 2.0

Prototype Report

Transportation Grant Fund

Team 14

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

Version History

Date / Author / Version / Changes made / Rationale /
10/07/11 / Karim Sacre / 1.0 / ·  Changes made from initial prototype template / ·  Initial prototype report
10/14/11 / Karim Sacre / 1.1 / ·  Updated the status of the project 1.2
·  Updated the Navigation flow diagram
·  Removed the secondary role of each team member from the first page
·  Removed section 1.3 (tools used for prototype)
·  Updated some of the screen shots / ·  Applied the teachers remarks
·  Added new features that the client asked for.
10/19/11 / Karim Sacre / 1.2 / ·  Updated the navigation flow diagram
·  Updated some of the screen shots / ·  Applied teachers remarks
10/24/11 / Karim Sacre / 1.3 / ·  Updated status of the project (1.2)
·  Added a note for navigation flow
·  New Projects View Screenshot (Figure 2) / ·  Review of the ARB comments
·  Navigation flow note just a clarification
11/07/11 / Karim Sacre / 1.4 / ·  Updated the project Status
·  Commented on the TA’s review comments (Figure 5)
·  Added a comment on Description (sect 4) / ·  Clarified some aspects of the screenshots to answer to the TA’s reviews
11/21/11 / Karim Sacre / 2.0 / ·  New Sharepoint screen shots added
·  New navigation flow
·  Status of the prototype / ·  Got input from the client
·  Finalized all the fields needed for filling the forms
·  Some pages were added and some deleted after we have started to explore sharepoint features

Table of Contents

Prototype Report i

Version History ii

Table of Contents iii

Table of Tables iv

Table of Figures v

1. Introduction 1

1.1 Purpose of the prototype report 1

1.2 Status of the prototype 1

1.3 Tools used for the prototype 1

2. Navigation Flow 2

3. Prototype 3

4. System Description 11


Table of Tables

Table 1: Projects View 3

Table 2: Create Project 4

Table 3: Generate reports 5

Table 4: Site Permissions 6

Table 5: Add user account 7

Table 6: Financial information 7

Table 7: Project details 8

Table 8: Edit Project 9

Table of Figures

Figure 1: Navigation Flow of LADoT Database System 2

Figure 2: Projects View 3

Figure 3: Create Project 4

Figure 4: Generate reports 5

Figure 5: Site Permissions 6

Figure 6: Add Financial Information 7

Figure 7: Project details 8

Figure 8: Edit Project 9

PRO_DCP_F11a_T14 v Version date: 11/21/11

Prototype Report Version 2.0

1.  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 the system. 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 the version 2.0 of the prototype document.

Our last meeting with the client was designated to finalize all questions and final remarks regarding the prototype. We now finalized the fields that the client wants to add in their system and they even pointed out what type of fields they want (drop down list, date, and text boxes…)

While we were still exploring Sharepoint, we managed to put together an HTML form for creating a project. We then showed this form to the client and got input from them. They clarified what fields were still missing.

We got a lot of feedback from the client concerning the finalized fields that they need in the system.

At the meeting we made sure to accentuate on speeding up the process of giving us a sharepoint server to test with. We are actually testing on our server that is set up at USC.

This prototype deals mainly with the create project, edit project, view project, generate report, edit report and user permissions. These are our riskiest modules so we started prototyping them. Section 3 has the new screenshots taken from sharepoint.

2.  Navigation Flow

Figure 1: Navigation Flow of LADoT Database System

3.  Prototype

Table 1: Projects View

Description / This page lists all the projects in the LADoT system.
The user can only edit the projects if he has permission to do so. If he is not signed up to the project then he can only see the details and download attachments.
Related Capability / List all and my projects to be able to edit or see more details about each project.
Pre-condition / User entered Projects View from the Home page or the top link bar or the navigation bar
Post condition / You can create a project, edit a project and view a project once in Projects view

Figure 2: Projects View

Table 2: Create Project

Description / Figure 3 shows how the user would be able to create a project. The user has to enter the project name and project ID. He could also add files to the system.
Related Capability / Edit project, view project
Pre-condition / User entered View Projects from the home page or from the navigation bar on the left of the screen.
Post condition / The project is created and appears in the projects view page.

Figure 3: Create Project


Table 3: Generate reports

Description / The user enters all the information needed to generate the report. When the user selects the project he wants to generate a report for, the information already in the system gets populated directly in the appropriate fields (figure 4a -> figure 4b).
Related Capability / Generate 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 and pressed on add new report
Post condition / A report will be generated with all the details asked for in the form shown in figure 4a-b


Figure 4: Generate reports (a)


Table 4: Site Permissions

Description / Figure 5 shows how the system has different permission levels: Contribute, Full Control, Read, Design, Limited access, view only… This will allow us to give different permissions to different users depending on their job title and project assignment.
Related Capability / Add user permissions, add user, edit user, delete user
Pre-condition / Admin has to log in to the system and he will get full access to the accounts permissions.
Post condition / Different permissions will have different access to the website.

Figure 5: Site Permissions


Table 5: Add user account

Description / Add user account is one of the features offered by sharepoint. It is found in the administration panel. The administration can create a user directory which allows us to include everyone in our system.
Related Capability / Assigning permissions, editing user accounts
Pre-condition / Log in as administrator and access the administrator panel and add a new user.
Post condition / A new user will be available in the system and will have access to whatever permissions were set to him by the administrator

Table 6: Financial information

Description / Figure 7 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 he is entering information to.
The clients are still not sure whether they want to include the accountants in the system. I am keeping this screenshot for now.
Related Capability / Add financial information to the project’s file
Pre-condition / The user has to go to add financial information page from the navigation tab or the top level.
Post condition / The project will get updated with the new information added by the accountant.

Figure 6: Add Financial Information


Table 7: Project details

Description / Figure 7 shows the project details. It has all the information of the selected project and all the attached documents. Anyone in the system can access this page. The only difference between users is the edit details button it is only available for program and project managers, edit financial information is only available for accountants.
Related Capability / Create Project, Edit project
Pre-condition / Press details button in Projects view page on a specific project
Post condition / It depends on the users input. Either go to the financial edit information if it was an accountant or edit the basic details if user is Program or project manager.

Figure 7: Project details


Table 8: Edit Project

Description / Edit project is a separate page in sharepoint. It allows us to disable the fields that we don’t want the project managers to edit such as the project name and the project ID since they are not supposed to change.
Related Capability / View project information, Create project
Pre-condition / Press edit item on the selected projected that we wish to edit
Post condition / The project information gets updated in the system

Figure 8: Edit Project


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:

1.  Project/Program Manager account:

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

2.  Administrator account:

The administrator like always has full control of the system. He makes sure all the accounts are running correctly, he adds and deletes accounts and approves user registrations.

3.  Accountant account:

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

4.  General account:

General accounts are all other users that are logged in the system and want to access projects information but don’t have any rights of changing anything. General users can access the projects view page, can download attachments and can generate reports. They don’t however have any privileges of editing any information.

All the users in the system can do whatever a general user can make.

PRO_DCP_F11a_T14 10 Version date: 11/21/11