Operational Concept Description (OCD) COSMIC SYSTEM. Team 02. Sam Lehardi Project Manager/ Life Cycle Planner/ Trainer

Transcription

1 Operational Concept Description (OCD) COSMIC SYSTEM Team 02 Sam Lehardi Project Manager/ Life Cycle Planner/ Trainer Mishaal Aleem Prototyper/ Trainer/ Implementer Rachel Inouye Operational Concept Engineer/ Trainer/ Implementer Terence Williams Software Architect/ Implementer Sitan Gao Feasibility Analyst/ Tester Sam Villarreal Requirements Engineer/ IIV & V/ Tester Nick Kwong Quality Focal Point/ IIV&V/ Tester 12/01/17

2 Version History Date Author Version Changes made Rationale 10/16/17 RI 1.0 Creation of the document; All sections completed; 12/01/17 RI 1.1 Updated System Boundary & Environment Diagram To complete for DC package Incorporated DC package feedback ii

3 Table of Contents Operational Concept Description (OCD)...i Version History... ii Table of Contents... iii Table of Tables...iv Table of Figures... v 1. Introduction Purpose of the OCD Status of the OCD Shared Vision Benefits Chain System Capability Description System Boundary and Environment System Transformation Information on Current System System Objectives, Constraints and Priorities Proposed New Operational Concept Organizational and Operational Implications iii

4 Table of Tables Table 1: The Program Model... 2 Table 2: Capability Goals... 7 Table 3: Level of Service Goals... 7 Table 4: Relation to Current System... 8 iv

5 Table of Figures Figure 1: Benefit Chain Diagram... 3 Figure 2: System Boundary and Environment Diagram... 4 Figure 3: Current Business Workflow Diagrams (Check Out, Check In, Reorder an item)... 6 Figure 4: Element Relationship Diagram of COSMIC-System Figure 5: Proposed Business Workflow Diagram (Reserve an Item) Figure 6: Proposed Business Workflow Diagram (Check-out an Item) Figure 7: Proposed Business Workflow Diagram (Check-in an Item) v

6 1. Introduction 1.1 Purpose of the OCD This document describes the key stakeholders shared vision and goals of the COSMIC-System. The key stakeholders are Darin Gray, as the project owner; USC Viterbi s STEM Education Outreach Programs (EOP) Inventory Manager, as the maintainer; STEM EOP student volunteers, as users; student organizations and schools, as users. The OCD will be constantly referred to throughout the project s life cycle. The proposed system is being developed based on the operational concepts described in this document. It will be referenced heavily during the beginning phases of the project for requirements gathering and design. 1.2 Status of the OCD The status of the OCD is currently at the version number 1.0. Section 1 Introduction, Section 2 Shared Vision, and Section 3 System Transformation were all completed in this version. 1

7 2. Shared Vision Table 1: The Program Model Assumptions Client and users will use the system once it s deployed Inventory Manager will keep the system up to date with current inventory Stakeholders Initiatives Value Propositions Beneficiaries Developers: Team Members Client: Darin Gray Maintainers: Inventory Manager Users: Volunteers Organizations Developers: Develop the inventory management system Client: Provide Requirements Win Conditions Feedback / Input Hosting System Users Use the system Maintainers Test the system Use the system Provide Feedback Provide spreadsheet to import current inventory Increase time efficiency through inventory organization, tracking item location, and automated reorder s. Save costs by tracking inventory stock instead of over-ordering items due to disorganization. Easier lesson planning for volunteers & organizations through our searchable interface. USC STEM-EOP Director STEM Staff Inventory Manager Volunteers People that STEM- EOP affect Organizations 2

8 2.1 Benefits Chain Below is the Benefit Chain Diagram for the COSMIC-System. It illustrates the relationships between the elements in the program model above. Figure 1: Benefit Chain Diagram 2.2 System Capability Description The COSMIC-System is an inventory tracking system for USC Viterbi s STEM Educational Outreach Programs. It will enable STEM EOP to have a much more organized, efficient, and accountable workflow. Our client should use the system because it will help them to save time through its easy to use interface for reserving, checking in, and checking out inventory items. Our system will also save our client money through its inventory stock tracking capabilities leading to less over-ordering of items. 3

9 2.3 System Boundary and Environment Below is the System Boundary and Environment Diagram for the COSMIC-System. It shows the services provided, supporting infrastructure as well as the interfacing stakeholder and system. Figure 2: System Boundary and Environment Diagram 4

10 3. System Transformation 3.1 Information on Current System Infrastructure Currently, there is a storage room on the USC campus where the STEM EOP inventory is stored. There is a part-time inventory manager who tries to organize the room as much as possible and carries out any inventory related tasks that Darin Gray requests. As far as borrowing and returning items, there is no system in place. Student volunteers, student organizations, and schools borrow supplies to facilitate their STEM projects, and return them when they can (and sometimes they do not return them at all). If an item is not returned, there is no way to figure out where it is, who borrowed it, or when it was borrowed. Also, there is no good way to determine if an item needs to be reordered. In some cases, Darin will reorder an item because he is not able to find it, but ends up finding it after the fact Artifacts None. There are currently no artifacts used for inventory tracking. This is because there is no system in place for tracking inventory. 5

11 3.1.3 Current Business Workflow Below are the current business workflows for checking out, checking in, and reordering an item. These workflows are very simple and do not allow for accountability or organization. Figure 3: Current Business Workflow Diagrams (Check Out, Check In, Reorder an item) 6

12 3.2 System Objectives, Constraints and Priorities Capability Goals Below is a table of the core capabilities of the COSMIC-System. Table 2: Capability Goals Capability Goals OC-1 Login/Logout: User can login using the address and password they registered for their account with. OC-2 User Privileges: User access to features is determined by the privilege level of their account assigned when they register. OC-3 Search: Users can search the inventory by any field including item name, tag name, availability, or description. OC-4 Reserve: Users can reserve an item in advance by ing the Inventory Manager their request. Only the Inventory Manager can enter reservations. OC-5 Check-out: Users can check-out an item they reserved, or check-out any item that is available. OC-6 Check-in: Users must check-in items they have checked-out and enter any relevant information in the notes fields Level of Service Goals Priority Level High High High Medium Highest Highest Below are the specific level of service goals for the COSMIC-System and their referred win conditions. Table 3: Level of Service Goals Level of Service Goals Priority Level Referred WinWin Agreements Browsers Supported: Safari High WC-13.1, WC , WC- 11, Firefox 56.0, Chrome 61, Chrome 60 RWD / Mobile Compatibility: Desktop, Laptop, Smartphone Highest WC-13, WC-13.2, WC

13 3.2.3 Organizational Goals Here is a list of the organizational goals for USC STEM EOP. These align with the value propositions from the Program Model as well as the outcomes in the Benefit Chain Diagram. OG-1: Improved inventory tracking system. OG-2: Increase time efficiency through inventory organization, tracking item location, and automated reorder s. OG-3: Increased cost efficiency by tracking inventory stock instead of over-ordering items due to disorganization. OG-4: Easier and more efficient lesson planning process Constraints Below is a list of constraints on the COSMIC-System. CO-1: Database language: Database limited to MySQL because we are hosting the system on our client s GoDaddy account. CO-2: Sever side language: Server side language limited to PHP because we are hosting the system on our client s GoDaddy account Relation to Current System The table below illustrates the relationship between the current system and the COSMIC-System. Table 4: Relation to Current System Capabilities Current System New System Roles and Responsibilities Currently, the USC STEM EOP Director Darin and his Inventory Manager are responsible for keep track of inventory, handling reservations, coordination borrowing and returns, as well as reordering. The new system will handle all of these responsibilities. The Inventory Manger just needs to keep the COSMIC-System up to date with current inventory data, and to manage reservation requests he gets from Student Volunteers. Darin will have a lot less responsibility (as far as inventory tracking), and will mainly be responsible for reordering items when he gets the 8

14 User Interactions Infrastructure Stakeholder Essentials and Amenities Future Capabilities Currently, all user interactions are manual. These include, student volunteers checking out items (by going to the storage room and taking them), Darin re-ordering items if he can t find them in the storage room, and the inventory manager trying to organize the inventory manually. There is no supporting infrastructure in place in the current system. Our client has described to us that each new Inventory Manger he hires has a different system for organizing the inventory, but that none have worked very well so far. The current system does not meet stakeholder essential capabilities and does not have any amenities. The current system does not have any future capabilities that could potentially be added. The current system does not work as desired, which is why our client has asked us to develop the new system for him. re-order from the system. In the new system, all user interactions will involve logging into the system. Through the website, they can login/out, search for items in the inventory, checkin/check-out items, and make reservations (if they have admin privileges). The infrastructure supporting the new system is HTML, CSS, Bootstrap, JavaScript, and AngularJS on the frontend. As well as PHP and a MySQL database on the backend. The website it hosted on GoDaddy. The new system will meet stakeholder essentials outlined in the Table 2: Capability Goals. It also has amenities including an appealing UI and the convenience of mobile compatibility. The new system already has the core capabilities of login/logout, user privileges, inventory search, advanced reservations, and checkin/check-out. Some potential future capabilities are a logging system as well as reports on user trends. 9

15 3.3 Proposed New Operational Concept Element Relationship Diagram The Element Relationship Diagram shows the various elements involved in the COSMIC- System and how they relate to each other. It illustrates the different user privilege levels and which elements of the system each user privilege type has access to. Figure 4: Element Relationship Diagram of COSMIC-System Business Workflows Below are the proposed business workflows for reserving, checking out, and checking in an item in the COSMIC-System. These allow for a lot more accountability and organization in the inventory tracking process. 10

16 Figure 5: Proposed Business Workflow Diagram (Reserve an Item) 11

17 Figure 6: Proposed Business Workflow Diagram (Check-out an Item) Figure 7: Proposed Business Workflow Diagram (Check-in an Item) 12

18 3.4 Organizational and Operational Implications Organizational Transformations Below is a list of organizational transformations resulting from the COSMIC-System: The need for the Inventory Manager to keep the new system up to date will current inventory data. The elimination of over-ordering items, leading to increased cost efficiency. Darin Gray (Director of USC STEM EOP) having less responsibility and time consuming busy work related to inventory tracking. The ability to lend STEM materials to more schools and student organizations because the system implements accountability and allows for resources to be more efficiently allocated Operational Transformations Below is a list of operational transformations resulting from the COSMIC-System: The ability to reserve an item in advance and be confident that no one else will check-out the item in the meantime. Student volunteers having to go through the system in order to check-in or check-out items (increased accountability). Reservation requests having to go through the Inventory Manager via . Automatic re-order s triggered when stock gets below a certain threshold. The ability for organizations to remotely browse inventory instead of physically visiting the storage room or contacting Darin. 13