Download Operational Concept Description for California Science Center Volunteer Tracking System and more Study Guides, Projects, Research Aerospace Engineering in PDF only on Docsity!
OCD_LCA_F06a_T03_V3.7.doc (^) i Version Date: 12/2/
Operational Concept Description (OCD)
California Science Center Volunteer Tracking System
Team
Phongphan Danphitsanuphan Project Manager
Charlie Lormanometee Project Coordinator / QA
Deepak Pandey Software System Requirements Analyst
Pongtip Aroonvatanaporn System Architect / Programmer
Natachart Laoteppitak Software Architect / Programmer
Ritesh Kothari Tester / Programmer
Amit Shah IV & V
Jerome Wan IV & V
Jeremy Stoller Client
Raul Pereyra User
Vincent Tsan Maintainer
OCD_LCA_F06a_T03_V3.7.doc (^) ii Version Date: 12/3/
Version History
Date Author Version Changes made Rationale
09/13/06 PD, NL 0.1 (^) • OCD outline template with section 1
included
09/14/06 PD, DP,
RK
0.2 (^) • Added section 3 • Section 3 was added to show capability goals, relation to the current system, levels of service, and traceability of business workflows and entity relationship. 09/15/06 PD, CL, PA
0.3 (^) • Added section 2 • Section 2 was added to provide the shared visions of stakeholders and the traceability of system boundary and environment and benefits chain. 09/16/06 PA 0.4 (^) • Redrew system boundary and
environment, business workflows, and entity relationship diagrams.
- Revised grammatical errors.
- Revised correctness of requirements and diagrams. - Diagrams were redrawn to provide consistency. - Details were added to diagrams for correctness and clarity. - Some system requirements have been adjusted and added to better fit with the project scope. - Wordings and grammatical errors were corrected for readability. - These defects were found after the inspection. 09/17/06 PA 1. (Released)
- Revised entire OCD document to follow the LeanMBASE OCD Guideline v.1.
- Added section 3.
- Use LeanMBASE OCD template instead of original one.
- Section 3.2 was added to provide the operational goals. 10/2/06 PA 1.1 (^) • Added sections 3.3.4, 3.4, and 4 • Section 3.3.4 provides the
information on the initial prototype of the proposed system
- Section 3.4 includes the organizational and operational transitions.
- Section 4 was added to provide the report on the Easy Win-Win negotiation. 10/03/06 PD 1. (Released)
- Change key word in session 2.4 • Developer to Development team
OCD_LCA_F06a_T03_V3.7.doc (^) iv Version Date: 12/3/
Date Author Version Changes made Rationale
10/23/06 PA 3. (Released)
- Added LeanMBASE Guideline v1.7 in reference
- Added reference to SSRD
- Changed “Web Engineer” to “Vincent Tsan” in Stakeholders (Maintainer)
- Edited OC-8. Scheduling is no longer automatic assignment but automatic matching for viewing purposes.
- Clarified OC-
- Edited Business Workflows Diagram for correctness - Changes made after inspection
11/5/06 PA 3.2 (^) • Removed OC-
- Removed “discussion board” in OG-
- Section 3.3.3. For reliability, changed “downtown” to “downtime”
- Added tracking volunteer hours to benefits in Section 2.
- Added “Submit Job Request” to System Boundary diagram - Changes made based on the LCO Package evaluation by the IV&Vers
11/18/06 PA 3.3 (^) • Added document version to the
introduction.
- Added “maintainer” to the Benefits Chain in section 2.
- Added teaching staffs to the list of success critical stakeholders in section
- Added Newsletter System and Event RSVP System (Projects of teams 1 & 2) to the system boundary in section 2.
- Edited the Relation to Current System table in section 3.1.1 to follow the guideline.
- Edited the Entity Relationship Diagram in section 3.3.1 to show the layer of the application.
- Edited the Interoperability level of service goals in section 3.3.3 to make “acceptable” level more measurable. - Changes made based on the graded LCO Package.
OCD_LCA_F06a_T03_V3.7.doc (^) v Version Date: 12/3/
Date Author Version Changes made Rationale
11/19/06 PA 3. (Released)
- Added document versions to the references
- Edited OC-7 and OC-9 in section 3. for clarification purposes
- Changed Future Capabilities in Section 3.1.1 to N/A
- Added time period to Reliability Level of Service in section 3.3.
- Edited the Screen Navigation Flow in Prototype. Added “Manager” to the chart.
- Added OC-13: Error Detection in section 3. - Changes made after inspection
12/1/06 PA 3.5 (^) • Renamed OC-2 to Cross Platform
Compatibility
- Added Future Capability in section 3.1.
- Added in section 2.2 – PDF format report
- Added California Science Center Staff as also Domain Experts
- Removed “No learning experience” in section 3.1. - Changes made based on IV&V review
12/2/06 PA 3.6 (^) • Reworked the Benefits Chain diagram
in section 2.3. Changed the initiative to be more descriptive and to represent the actual initiatives.
- Update the Prototype section. Added the following: o Application Approval Page o Job Scheduling Page o Manager’s Main Page
- Updated the Screen Navigation Flow diagram to include the Job Scheduling feature.
- Update the Win conditions in the prototype to better correspond with the EasyWinWin Report - Changes based on LCA ARB comments - Updated the Prototype section with further prototyping.
12/3/06 PA 3.
(Released)
- Updated OC-2 in Section 3.1. The cross platform capability needs to be stated clearer.
- Updated the prototypes for volunteer coordinator’s main page, supervisor’s main page, and certificate generation page
- Update reference section
OCD_LCA_F06a_T03_V3.7.doc vii Version Date: 12/3/
Table of Tables
Table 1: Relation to Current System Table .............................................................................. 17 Table 2: Table of Level of Service Goals................................................................................. 20
Table of Figures
- OCD_LCA_F06a_T03_V3.7.doc vi Version Date: 12/3/
- Introduction.......................................................................................................... TABLE OF FIGURES VIII
- 1.1 Purpose of the OCD .........................................................................................
- 1.2 References ....................................................................................................
- Shared Vision
- 2.1 System Capability Description
- 2.2 Expected Benefits
- 2.3 Benefits Chain (Initiatives, Expected Outcomes, and Assumptions)
- 2.4 Success Critical Stakeholders..........................................................................
- 2.5 System Boundary and Environment
- System Transformation
- 3.1 Capability Goals............................................................................................
- 3.1.1 Relation to Current System
- 3.2 Organizational Goals......................................................................................
- 3.3 Proposed New Operational Concept
- 3.3.1 Entity Relationship Diagram
- 3.3.2 Business Workflows
- 3.3.3 Level of Service Goals
- 3.3.4 Prototype
- 3.4 Organizational and Operational Implications
- 3.4.1 Organizational Transformations
- 3.4.2 Operational Transformations
- Easy Win-Win Results...........................................................................................
- OCD_LCA_F06a_T03_V3.7.doc viii Version Date: 12/3/
- Figure 1: Benefits Chain Diagram
- Figure 2: System Boundary and Environment Diagram
- Figure 3: Entity Relationship Diagram
- Figure 4: Business Workflows Diagram
- Figure 5: Login Page
- Figure 6: Online Application Form
- Figure 7: Application Approval Page
- Figure 8: Volunteer’s Main Page
- Figure 9: Supervisor’s Main Page
- Figure 10: Volunteer Coordinator’s Main Page
- Figure 11: Volunteer Listing Page
- Figure 12: Report Generation Page......................................................................................
- Figure 13: Certificate Generation Page
- Figure 14: Job Request Page
- Figure 15: Job Scheduling Page
- Figure 16: Screen Navigation Flow Chart...............................................................................
OCD_LCA_F06a_T03_V3.7.doc - 10 - Version Date: 12/3/
2. Shared Vision
2.1 S ystem C ap abilit y D escr ip tio n
The Volunteer Tracking System will simplify as well as lessen the processing time in the
volunteer management process. The proposed web-based application will allow volunteer applications to
be processed online and automatically assign them to appropriate departments based on their interests and
skills. Supervisors will have the abilities to view and manage the current assignments of volunteers,
comment logs, volunteer profiles, and amount of volunteered time. In addition, the system is capable of
generating statistical reports of volunteers working information and produces notifications as volunteers
work time exceed certain number of hours.
Our approach to differentiate our system from our competitors is the customized web-based
application available throughout intranet, which will be more user-friendly, faster, and better integration
with other CSC projects.
2.2 E xpect ed B e nefi ts
- The supervisors will spend less time to deal with the volunteers; thus, increasing
productivity in other areas of work.
- Volunteer candidates can fill out the application online and information will be
automatically store in the database.
- Customized reports are generated in single easy-to-read text format as well as PDF
format as opposed to combining multiple reports.
- Volunteer coordinator can view and edit volunteers’ information through the system.
- System will automatically track working hours of each volunteer.
OCD_LCA_F06a_T03_V3.7.doc - 11 - Version Date: 12/3/
2.3 B enefit s C ha in (I nitia tive s, E x pect ed O utc om es, a nd
A ssum pti on s)
Figure 1: Benefits Chain Diagram
OCD_LCA_F06a_T03_V3.7.doc - 13 - Version Date: 12/3/
MAINTAINERS (Client/Customer):
California Science Center
Jeremy Stoller
Vincent Tsan
The web and system administrator of the CSC who will update and upkeep the system.
OCD_LCA_F06a_T03_V3.7.doc - 14 - Version Date: 12/3/
2.5 System Boundary and Environment
Figure 2: System Boundary and Environment Diagram
OCD_LCA_F06a_T03_V3.7.doc - 16 - Version Date: 12/3/
OC-11 Database backup/restoring : The system should have the ability to back up the
database and restore in case of system crashes or network failure. This is done by the system
administrator.
OC-12 Generate Certificates : Volunteer coordinator has the ability to generate
certificates for volunteers who have completed their requirements. Requirements differ for each
volunteer.
OC-13 Error Detection: The system should have the capability of detecting errors
caused by users’ mistakes in the use of the system or errors that the system encounters during
execution. The system administrator should be notified of the errors.
OCD_LCA_F06a_T03_V3.7.doc - 17 - Version Date: 12/3/
3. 1. 1 R e l a t i o n t o C u r re n t S y s t e m
Table 1: Relation to Current System Table
Capabilities Current System New System
Roles and
Responsibilities
coordinator’s machine and only
available to volunteer
coordinator
- Significant amount of paper
work
- Significant amount of volunteer
coordinator’s responsibilities
- Internet based
- Significantly less paper work
- Less work for supervisors and
volunteer coordinator.
- Processes are mainly automated
User Interactions • Less user friendly
- Manually entered time in/out
data.
volunteers to clock in and out
- Hours counter
- Automatic notification
- Customized report generation
Infrastructure • Windows based software • Web-based application
- Platform independent
- Browser independent
Stakeholders
Essentials and
Amenities
- Assures accuracy of volunteers’
hours worked
- User error notifications to
volunteer coordinator.
report generations.
- Accessible to all users with
authentication required.
Future Capabilities • Automatic scheduling of
volunteer job requests
OCD_LCA_F06a_T03_V3.7.doc - 19 - Version Date: 12/3/
3. 3. 2 B u s i n e s s Wo r k f l o w s
The new business workflow for the proposed Volunteer Tracking System for the
California Science Center is shown in the diagram below.
Figure 4: Business Workflows Diagram
OCD_LCA_F06a_T03_V3.7.doc - 20 - Version Date: 12/3/
3. 3. 3 L e v e l o f S e r v i c e G o a l s
Table 2: Table of Level of Service Goals
Level of Service
Attribute (units)
Desired Acceptable
Notes
Reliability
100% of system service
uptime in 1 year time
period
95% of system service
uptime in 1 month time
period
Network and server
downtime do not count
towards system
reliability
Response time for page
advancing
Less than 1 second 1 second
Sever/web connection
dependent
Response time for
report generation
5 sec 10 sec
Sever/web connection
dependent
Response time for
database searching
3 sec 3 sec
Sever/web connection
dependent
Interoperability
All necessary modules
can be shared with
projects of Teams 1 &2.
Emailing module can be
shared.
Will be determined
during LCA phase
