Supporting Information Document (SID) Version no 3.3
Supporting Information Document (SID)
Transportation Grant Fund Database
Team 14
Muruganantham Raju – Project manager
Ayman Khalil – Operational Concept Engineer
Karim Sacre - Prototyper
Kirill Khistayev – System Architect
Reza B’Far – IIV&V
Stephen Rice – IIV&V
Zhanna Seitenova – Lifecycle Planner
December 12, 2011
Version History
Date / Author / Version / Changes made / Rationale /10/3/11 / ZS / 1.0 / · Original template / · Initial draft
10/7/11 / ZS / 1.0 / · Edited sections 1.1, 1.2, 1.3 / · Core FCP
10/14/11 / AK / 1.1 / · Fixed document format
· Updated References section
· Updated Traceability Matrix (Table 1) / · Draft FCP
10/23/11 / ZS / 1.2 / · Updated Section 1.3 References / · FCP
11/25/11 / ZS / 3.0 / · Updated the document version to 3.0 / · Draft DCP
11/30/11 / RM / 3.1 / · Updated Table 1 / · Preparing for ARB
12/11/11 / RM / 3.2 / · Document footer is updated
· Introductory note added in Section 4 / · Footer was reading FCP instead of DCP.
· To improve readability and provide more clarity an introductory note is added in section4
12/12/11 / RM / 3.3 / · Updated status of SID / · DCP review comments
Table of Contents
Version History ii
Table of Contents iii
Table of Tables iv
Table of Figures v
1. Introduction 1
1.1 Purpose of the SID Document 1
1.2 Status of the package 1
1.3 References 1
2. Traceability Matrix 2
3. Glossary 3
4. Document Tailoring 5
SID_DCP_F11a_T14_V3.3.doc 5 Version Date: 12/12/11
Feasibility Rationale Description (FRD) Template Table of Contents
Table of Tables
Table 1: Traceability Matrix for NDI/ NCSTeam 2
Table 2: Document Tailoring 5
SID_DCP_F11a_T14_V3.3.doc 5 Version Date: 12/12/11
Feasibility Rationale Description (FRD) Template Table of Contents
Table of Figures
No table of figures entries found.
SID_DCP_F11a_T14_V3.3.doc 5 Version Date: 12/12/11
Supporting Information Document (SID) Version 3.3
1. Introduction
1.1 Purpose of the SID Document
The SID Document ties all other Foundations Commitment Package documents together and provides any necessary supplemental information.
1.2 Status of the package
This Document is a part of the Development Commitment Package. As of right now, it only contains the core information necessary to move forward into the Foundations phase. The document will be fully filled out by the end of this phase.
1.3 References
All of the following documents can be found on the project’s website under the following link: http://greenbay.usc.edu/csci577/fall2011/projects/team14/index.php?page=valuation
· Operational Concept Description Version 2.2: OCD_FCP_F11a_T14_V2.2.doc
· Prototype Version 1.1: PRO_FCP_F11a_T14_V1.1.doc
· WinConditions_Prioritization: WinConditions_Prioritization.xls
· System & Software Architecture Definition Version 1.2: SSAD_FCP_F11a_T14_V1.2.doc
· Life Cycle Plan Version 2.3: LCP_FCP_F11a_T14_V2.3.doc
· Feasibility Evidence Description Version 2.3: FED_FCP_F11a_T14_V2.3.doc
Quality Management Plan Version 1.0: QMP_FCP_F11a_T14_V1.0.doc can be found under
http://greenbay.usc.edu/csci577/fall2011/projects/team14/IIVV/
2. Traceability Matrix
Table 1: Traceability Matrix for NDI/ NCSTeam
OCD / Win Agreement / SSAD / Test CaseOC-1 Role-based access control (RBAC) / WC_397 / UC-1: Login
UC-2: Logout
UC-3: Add User
UC-4: Edit User
UC-5: Delete User / TC-02-01,TC-02-02, TC-02-03
OC-2 Administrators approved user registration / WC_398 / UC-3: Add User / TC-03-01,TC-03-02, TC-03-03
OC-3 Electronically storing all project information / WC_372 / UC-6: Create Project
UC-7: Edit Project
UC-8: Delete Project
UC-9: Get Project Information
UC-10: View Projects / TC-05-01,TC-05-02,TC-05-03, TC-05-04,TC-05-05,TC-04-01, TC-04-02,TC-04-03,TC-04-04, TC-04-05, TC-04-06
OC-4 Attaching documents / WC_392 / UC-13: Attach Document
UC-14: Download Document
UC-15: Delete Document / TC-06-01,TC-06-02,TC-06-03, TC-06-04,TC-06-05,TC-06-06
OC-4 Report Generation / WC_370 / UC-12: Generate report / TC-05-02
OC-6 Export project data / WC_382 / UC-17: Request Projects Information / TC-07-01
OC-7 Scheduling & notifications / WC_379 / TBD / TBD
OC-8 Sending emails / WC_376 / UC-16: Send Mail / TC-08-01,TC-08-02
3. Glossary
LADOT
Los Angeles Department of Transportation
DBA
Database Administrator
TGF
Transportation Grant Fund
DOT
Department of Transportation
DA
Department of Transportation Accounting
PM
Project Manager
MA
Management Analyst
SMS
Supply Management System
PW
Public Works
MA
Management Analyst
MTA
Metropolitan Transportation Authority
PL
Probability of Loss
PM
Potential Magnitude of Loss
ROI
Return On Investment
FED
Feasibility Evidence Description
LCP
Life Cycle Plan
OCD
Operational Concept Description
SSAD
System and Software Architecture Description
NDI
Non Developmental Item
NCS
Net Centric Services
IIS
Internet Information Services
MS SQL
Microsoft Structured Query Language
IDE
Integrated Development Environment
CMS
Content Management System
UML
Unified Modeling Language
OC
Operational Capability
UC
Use Case
FCP
Foundation Commitment Package
VCP
Valuation Commitment Package
RBAC
Role Based Access Control
WC
Win Condition
TBD
To Be Determined
NA
Not Applicable
ICASE
Integrated Computer Aided Software Environment
MOU
Memorandum of Understanding
LOA
Letter of Agreement
SVN
Subversion (a software versioning and revision control software distributed under free license)
4. Document Tailoring
This section lists the documents in which the default template has been tailored (new section added or existing section removed) to fit the project needs. The intended change and rationale is given here. Note that only tailored documents are listed here. All other documents have no changes from initial default template.
Table 2: Document Tailoring
Initial Prototype PRO_FCP_F11a_T14_V1.0· Added a new section to the document: Section 4. Description
Rationale: This helps the client get a better understanding of the system as an entity. It provides the written general description of the system.
Lifecycle Plan LCP_FCP_F11a_T14_V2.0
· “Table 5: Business side Stakeholders’ Roles and Responsibilities” was added.
Rationale: The roles and responsibilities of stakeholders from business were identified.
· Table 6 was renamed from “Stakeholder's Responsibilities in each phase” to “Development team’s Responsibilities in each phase”.
Rationale: Development team’s responsibilities were differentiated from all stakeholders.
· Numeration and name for the table in section 3.3 were added.
Rationale: There was no number and name for the table in the template.
· The table in section 3.3 was divided into 2 tables.
Rationale: to identify roles and skills for 577a and 577b.
· Numeration and name for the table in section 4.2 were added.
Rationale: They were missing in the template.
Feasibility Evidence Description FED_FCP_F11a_T14_V2.1
· “Table 1: Modified the criteria and rationale
Rationale: Table is changed as per process decision driver criteria setting
SID_DCP_F11a_T14_V3.3.doc 5 Version Date: 12/12/11