operational concept description (ocd) · web viewdiamond_ocd.docx version date: 1 1 /23/20...

● Operational Concept Description (OCD)Data Information Analytics-Managed Online Network Database

DIAMOND

Team 1

Haiwen Chen Requirements Engineer

Sam Cote Project Manager, Life Cycle Planner

Danny Diaz Ayon V&V, Quality Focal Point

Shijie Ding Software Architect/UML Modeler

Meghana Kolasani Prototyper

Dzung Phan Software Architect, Prototyper

Derek Wang Feasibility Analyst

Drew Webb Operational Concept Engineer

November 23, 2020

DIAMOND_OCD.DOCX 2 VERSION DATE: 11/23/20

1 Version HistoryDate Author Version Changes made Rationale

9/20/20 DWe & DWa

1.0 Initial version Initial Draft of OCD for ARB package # 1

10/13/20 DWe 3.1 Update the Benefits chain, business workflow and goals / constraints

filling in the initial data

10/21/20 DWe 3.2 Update and finalize Benefits chain, business workflow and goals. Update system transformation

finalizing the diagrams and system transformation section

10/22/20 DWe 4.0 Completed all deliverables in this document

Finalized information in tables and diagrams

10/23/20 DWe 4.1 Completely re-formatted the document to fix mismatches

Finalized format for the document

10/23/20 DWe 4.2 Updated format of tables to match theme and added Operational Screenshots

Finalized document for submission for ARB.

11/16/20 DWe 5.0 Updated the stakeholders, system boundary to match new agreed upon values.

Finalizing document for final ARB.

11/23/20 DWe 6.0 Updated benefits chain, and other documents to update the stakeholder labels. Also updated the LOS goals.

Bring all language up to date and finalized for DC package.


Table of Contents

Operational Concept Description (OCD) 1

1 Version History 2

2 Table of Tables 4

3 Table of Figures 5

4 Introduction 6

4.1 Purpose of the OCD 6

4.2 Status of the OCD 6

5 Shared Vision 7

5.1 Success-Critical Stakeholders 7

5.2 Program Model 8

5.3 Benefits Chain 9

5.4 System Capability Description 9

5.5 System Boundary and Environment 10

6 System Transformation 11

6.1 Information on Current System 116.1.1 Infrastructure 116.1.2 Artifacts 116.1.3 Current Business Workflow 126.1.4 Relation to Current System 13

6.2 System Objectives, Constraints and Priorities 146.2.1 Capability Goals 146.2.2 Level of Service Goals 156.2.3 Organizational Goals 156.2.4 Constraints 15

6.3 Proposed New Operational Concept 166.3.1 Element Relationship Diagram 166.3.2 Business Workflows 17

6.4 Organizational and Operational Implications 216.4.1 Organizational Transformations 216.4.2 Operational Transformations 21


2 Table of TablesTable 1 – Success-Critical Stakeholders …………………………………………………………. 7Table 2 – The Program Model ………….……………………………………………………….. 8Table 3 – Relation to Current System ……………………..……………………………………. 13Table 4 – DIAMOND System capability goals ………………………..…………………………. 14Table 5 – Level of Service Goals ……….……………………………………………………….. 15


3 Table of FiguresFigure 1 – Benefits Chain Diagram of the DIAMOND System ……………..……………………. 9Figure 2 – DIAMOND System Boundary and Environment Diagram …..………………………. 10Figure 3 – Viterbi STEM Center Current Business Workflow Diagram …...……………………. 12Figure 4 – Element Relationship Diagram for DIAMOND system ………………....…………… 16Figure 5 – Business Flow for new Programs, Instructors and Instructor Assignment ………..... 17Figure 6 – Business Workflow Diagram for new Participant, Guardian and Enrollment Entry ... 18Figure 7 – Business Workflow Diagram for Student Instructor Query and Reviews .………..… 19Figure 8 – Business Workflow Diagram for Demographic Data Query ……....………………… 20Figure 9 – New Participant Entry Front End Form ……………………………..………………. 22Figure 10 – Front End Search Form …………………………………….………………………. 23Figure 11 – Front End Participant Search Results …………………………………………..….. 24


4 Introduction

4.1 Purpose of the OCDThis document provides, in detail, the shared visions and goals of the stakeholders of the Data Information Analytics-Managed Online Network Database (DIAMOND) for the K-12 STEM Center. The success-critical stakeholders of the project are Dr. Darin Gray, as the project client; the STEM center staff and volunteers, as users; the Fall 2020 CS577A Team 1, as the developers.

4.2 Status of the OCDThe status of the OCD is current at version number 6.0 in the finalized phase. This is the finalized version of the OCD. Initial core capabilities and goals will be documented in this version. The Benefits chain, business workflows and system transformation have been updated and finalized.


5 Shared Vision

5.1 Success-Critical StakeholdersListed below are the current success-critical stakeholders.

Table 1: Success-Critical Stakeholders

Stakeholder Authorized Representative

Organization Relations to Benefit Chain

STEM Center Co-Director (Client)

Dr. Darin Gray STEM Center Responsible for querying demographic data from the new database system.

Maintainer TBD STEM Center Responsible for maintaining, updating and controlling access to the new system.

Student Worker Sydney Nguyen STEM Center Responsible for back porting all historical participant and program data into new systemResponsible for entering new participant and program data into new system

Student Instructor TBD STEM Center Responsible for querying participant roster for their specific programResponsible for entering participant

Development Team Samatha Cote USC - Team1 Responsible for developing the new database and front end system

Program Teacher TBD STEM Center Responsible for querying participant roster for their specific programResponsible for entering participant


5.2 Program ModelTable 2: The Program Model

Assumptions: - that only STEM Center staff will access the solution- Continuous growth of participants- Increasing number of programs- Stable network and database systems- System users correctly identify duplicates within the system

Stakeholders Initiatives Value Propositions Beneficiaries

● STEM Center Student Workers

● STEM Center Director

● Developers (us)

● System Maintainers

● Program Teachers

● Student Instructors

● Back port all current participant, program and review data to new database

● Develop new database and front end for participant & program tracking

● Input new participant and program data into system

● Update database with required fields and user accounts

● Query program participant information from new system

● Input new participant reviews into new system

● Extract

● Create a central database for all STEM center program and participant information to improve participant tracking

● Save time for STEM Center Employees to enter and maintain records

● Save time for STEM Center Employees to query data across programs

● Consolidated data access to participant enrollment data and entry for review for Program Managers

● Increase

● STEM Center Student Workers

● STEM Director

● System Maintainers

● Viterbi Administration

● Funders / Donors

● The University (USC)

● Program Teachers

● Student Instructors


participant demographic information

Donor support with faster, more accurate queries

5.3 Benefits Chain

Figure 1: Benefits Chain Diagram of DIAMOND System

5.4 System Capability DescriptionThe DIAMOND centralized database and front end system will be built using the currently available and flexible Salesforce platform. This platform will be used by all of the Viterbi STEM Center employees to allow them to enter participant and program information as well as query this data. The Viterbi STEM Center will benefit from this centralized data solution as it makes querying their data as easy as a few clicks. Fast data access will


improve productivity and allow the Viterbi STEM Center to quickly provide statistics to current and potential donors, resulting in more donations. The benefit of the Salesforce solution is the clients familiarity with the solution, customization, and ease of maintaining that comes native in the Salesforce platform. Other solutions could require a customized software solution that would be hard to maintain and be costly to develop.

5.5 System Boundary and Environment

Figure 2: DIAMOND System Boundary and Environment Diagram


6 System Transformation

6.1 Information on Current System6.1.1 Infrastructure

The Viterbi STEM Center is currently using a combination of MS Access databases, excel documents and paper records to keep track of all of the participating students and programs that are offered through the STEM Center. They also use a combination of systems to hold all of the participants' reviews for each program. This fragmentation is due to the merging of all of the programs from originally independent departments into one entity, The Viterbi STEM Center.

6.1.2 Artifacts

AF-1: Microsoft Access Database for Program Data: This is one of the ways that previous

program and participant data was stored. A database in Access was created to store all

the personal participant and program information.

AF-2: Google Drive Document for Program and Participant Data: This is another way that

data about participants and programs was stored for some programs. There are

Wordpress documents and Spreadsheet documents stored in Google Drive.

AF-3: Paper forms: Another way data for participants and programs was paper forms

that stored personal information and program specific information.

AF-4: Paper review form: Participants fill out this form to give a review of the program

after the program completes. This is either stored as is or entered into a Google drive

document.


6.1.3 Current Business Workflow

The current business workflow is visualized below. A combination of different data sources and stores ranging from MS Access databases to paper forms are used to accomplish this.

Figure 3: Viterbi STEM Center Current Business Workflow Diagram


6.1.4 Relation to Current System

Table 3: Relation to Current SystemCapabilities Current System New System

Roles and Responsibilities

● The student worker inputs data into multiple data storage solutions

● Significant amount of paper forms / work

● Querying data is complicated mix of multiple data sources and must be onsite to complete

● Internet based● Available to all authorized

users● Less paperwork;

paperwork is scanned into new solution

● Less work for student workers to enter data

● Significantly less work to query accurate results from participant and program data

User Interactions ● Hard to understand data entry and query process

● Context switching between different data storage solutions

● Easy to navigate feature to enter participant and program data

● Download queried data quickly through a few clicks

Infrastructure ● Data is fragmented; stored in several locations

● Data is stored in centralized Salesforce cloud platform

Stakeholder Essentials and Amenities

● Centralized program and participant data

● Remote access● Ensures accurate queried

data● Tracks participants across

different programsFuture Capabilities

● Native statistics on programs and participants in the Salesforce platform


6.2 System Objectives, Constraints and Priorities6.2.1 Capability Goals

Table 4: DIAMOND System capability goalsCapability Goals Priority Level

OC-1 Data Storage: The system is capable of storing program data from the STEM Center

Must have

OC-2 Authentication and Access Control: The various accounts of the STEM Center will have varying access controls to the database. There will be an admin account with full permissions, and a program manager account and a student worker account

Must have

OC-3 OCR recognition: the system is capable of analyzing handwriting and converting it

Should have

OC-4 General Statistics: The system is capable of showing basic statistics about the data on a overview dashboard

Should have

OC-5 Front End Interface: The system has a front end that allows STEM employees without specific technical knowledge to interact with the database

Must have

OC-6 Backup Capability: The system has redundancy and can restore critical data through backups in case of failure

Must have

OC-7 Error Detection and Duplicate Management: The system is able to detect errors in the data and also identify duplicate data entries.

Should have

OC-8 Maintenance: The system is able to be to maintained simply by a dedicated employee and should be cost efficient while in use for a number of years

Must have


6.2.2 Level of Service Goals

Table 5: Level of Service GoalsLOS Level of Service Goals Priority

LevelReferred WinWin

Agreements1 Performance: The performance of the

system should ensure that it takes less than 3 seconds to search the database and less than 5s to process uploaded data

High This will be achieved by the backend Salesforce Platform.

2 Reliability: The system should be reliable

High This will be achieved by the Salesforce Platform. Salesforce states that they have had a 99.9% availability in the past.

3 Scalability: The system will be scalable to support up to 5 million participants

Medium Duplicates will be accounted for. OCR will request validation from the user.

4 Availability: The system should have 24/7 availability

Medium This will be achieved by the Salesforce Platform. Salesforce states that they have had a 99.9% availability in the past.

5 Recoverability: The system should have recoverability options

Low Backup capability of the platform

6 Maintainability: The system should be maintainable

Low Maintainer has access to source code to update schema and fix issues.

6.2.3 Organizational Goals

OG-1: Decreases the management time and effort required for the student employees

to manage STEM center program and participant information.

OG-2: Simplifies analysis of the data across programs and allow for simple queries on

the data to be processed.

OG-3: Allow program teachers, student instructors and directors to easily view the data

and simple statistics about the programs and participants.DIAMOND_OCD.DOCX 17 VERSION DATE: 11/23/20

6.2.4 Constraints

CO-1: Salesforce as a cloud platform: The new system needs to be developed and

deployed off of the Salesforce platform.

CO-2: Budget only includes Salesforce: No budget for other COTS in addition to

Salesforce platform.

CO-3: Utilization of student workers to back port historical data: We need to rely on the

student workers to import the historical data into the new system.


6.3 Proposed New Operational Concept6.3.1 Element Relationship Diagram

Figure 4: Element Relationship Diagram for DIAMOND system


6.3.2 Business Workflows

Figure 5: Business Flow for new Programs, Instructors and Instructor Assignment


Figure 6: Business Workflow Diagram for new Participant, Guardian and Enrollment Entry


Figure 7: Business Workflow for Student Instructor Query and Reviews


Figure 8: Business Workflow Diagram for Demographic Data Query


6.4 Organizational and Operational Implications6.4.1 Organizational Transformations

OT-1: The Viterbi STEM Center will need to hire a new system maintainer to manage the

data flow in the back end, add/remove user accounts, and to backup the data in the

new system.

OT-2: The STEM Center will need to change the process of paper documents. They need

to confidentially destroy them after they have been entered into the new system.

OT-3: Elimination of all of the fragmented data stores and need to be onsite to query

complete participant and program data.

6.4.2 Operational Transformations

PT-1: Ability to run queries from anywhere you have an internet connection.

PT-2: The ability for Program Teachers to query enrollment data on their own.

PT-3: Student workers will need to backport all of the current program and participant

information into the new system.

PT-4: All STEM center employees will need to be trained to use the new system.

PT-5: Student workers will spend less time with data management and entry

6.5 Operational ScreenshotsThis section provides the screenshots and brief explanation of the prototype for the DIAMOND system.


6.5.1 Add New Participant

The Front End of the new system allows entry of new Participants using the paper form and OCR feature, or manual entry using the Front End form.

Figure 9: New Participant Entry Front End Form


6.5.2 Search Participants

The Front End allows the users to search current participants and programs using built in filters. It presents the data in an easily digestible format.

Figure 10: Front End Search Form


Figure 11: Front End Participant Search Results


operational concept description (ocd) · web viewdiamond_ocd.docx version date: 1 1 /23/20...

Documents