1. COSMIC-SYSTEM
PROTOTYPE
TEAM 2

2. PROJECT OVERVIEW USC Viterbi STEM Educational Outreach Programs
Mission: increase the number of educationally disadvantaged and historically underrepresented K- 12 students who matriculate to four-year universities and graduate with degrees in science, technology, engineering, and mathematics (STEM).
Engage K-12 students with hands-on, problem-based learning projects, experiments and activities as well as interactions with STEM professionals, STEM faculty and STEM near peer mentors.
Central Office STEM Materials Inventory Coordinating System (COSMIC-System)
Create a system to track the inventory of the STEM-EOP supplies, materials and equipment that support STEM activities for over 3000 students and teachers.
[2 min]

3. CORE CAPABILITIES
Keeps track of each item’s status and quantity available
Ability to search the available inventory by keyword / tag name
Check-in / check-out functionality
Advanced reservation capability
s alerts when an item needs to be reordered
Different user access modes based on user privileges
[1 min]

4. PERSONA 1 – JENNY MILLER
Basic Demographics: 20, Female, USC Undergraduate Student
Background: Jenny grew up in Pasadena, CA. She is a Sophomore at USC majoring in Computer Science and living in the on-campus dorms. She is an excellent student, and in her free time she works as one of the student volunteers for USC Viterbi’s STEM-EOP.
User Scenario: Jenny is going to facilitate a robotics project at a nearby high school. She wants to reserve 8 robot kits to bring with her to the school next Wednesday. She will need to check out the robots on Wednesday morning, and plans on returning them Thursday morning.
Computer Literacy: Jenny is a computer science student, and is very technically fluent. Her browser of choice is Chrome, but she can use any web browser easily (desktop or mobile).
[1 min]

5. PERSONA 2 – SPENCER LEE
Basic Demographics: 28, Male, USC Graduate Student
Background: Spencer grew up in Seattle, WA. He did his undergraduate degree in Biology at The University of Washington, and is now getting his PhD in Biology at USC. He works part-time as the Inventory Manager for USC Viterbi’s STEM EOP.
User Scenario: Spencer receives an from a student volunteer with a list of items and quantities they would like to reserve for an upcoming project, along with their reservation dates. Spencer needs to confirm that those items and quantities are available, and then reserve each item for the specified date and quantity.
Computer Literacy: Spencer has average technical fluency relative to his peers. He exclusively uses Safari as his browser of choice on his MacBook and iPhone.
[1 min]

6. PROTOTYPE - UI Value Added:
Flow of website application and hierarchy of visual elements
Key features developed (search, keywords/tags, view inventory, and thumbnails)
Determine responsiveness of system through multiple avenues
Gain feedback early regarding usability issues
Risk Reduction:
Details -Developing a mock user interface reduces the chance of usability issues in regards to users properly being able to use the system. Developing UI early allows us to gain feedback from success critical stakeholders to determine if the system is intuitive and easy to use. Also, able to buy information on responsive web design, utilizing a mobile phone to access the COSMIC inventory system. Additionally, laying out an initial structure will reduce risk of gold plating as we determine our most important features and how they interact with each other, gaining feedback from the client in the process.
Reduce risk of usability issues
Reduce risk of cross-platform support (desktop/mobile)
Reduce risk of gold plating
Value added:
Details-Developed features such as search, keywords/tags, view inventory, and thumbnails which client rated with high business value. Able to gain feedback from critical stakeholders regarding ease of use on the system,
Determine responsiveness of the system and ability to use with mobile phones.
Creating the user interface will provide us with a general structure for our project determining hierarchy of different elements.
-Key features developed (search, keywords/tags, view inventory, and thumbnails)
-Responsiveness of the system
-Flow of website application and hierarchy of visual elements

7. PROTOTYPE - UI

8. PROTOTYPE - UI

9. PROTOTYPE - MYSQL DATABASE
Risk Reduction:
Reduce risks from lack of domain knowledge
Reduce risks from scalability issues
Reduce risk of security issues
Risk Reduction:
Details:With little background knowledge in using MySQL, there was high risk that skill deficiencies in incorporating MySQL would cause the inability to use database. Knowing MySQL can be used, it would lessen the risk for scalability issues when the system grows as more schools participate in the STEM outreach program. Reduce risk of security by being able to store user information in MySQL. Able to use tools given in hosting package???
Reduce risks from personnel shortfalls
Reduce risks from scalability issues
Reduce risk of security issues ????
Value added:
Details:MySQL provides data security as it is able to store user information safely in the database. Allows for higher performance if amount of users increases, allowing website application to be more scalable for the future. Able to incorporate reservation system feature with use, and does not require use of more expensive cloud databases. Open-source free software will save on costs.
Increased security ???
Scalability
Save costs

10. PROTOTYPE - MYSQL DATABASE

11. PROTOTYPE – USER PRIVILEGES
Risk Reduction:
Reduce risks of misuse by unauthorized users
Reduce risks of value conflicts by incorporating multiple stakeholders
Reduce risks of scheduling issues and project delays
Risk Reduction:
Details- Reduce risks of misuse of system by unauthorized users by restricting features available only to admins or part-time volunteers. Prototyping this feature allows for feedback from different levels of users early in system development. User privileges is ranked as a high business value feature by client, and ability to implement the system in a timely manner reduce the risks of scheduling issues from delays in implementing feature.??
Reduce risks of misuse by unauthorized users
Reduce risks of value conflicts by incorporating multiple stakeholders
Reduce risks of scheduling issues and project delays ??
Value Added:
Details: Adding user privileges, allows the system to have multiple types of users, authorizing users for specific uses. Prototyping this feature early allows for feedback from different stakeholders with different roles and backgrounds. ??
Allow different access levels between users
Early feedback from success-critical stakeholders of various user roles ??

12. DEMO

13. Back-Up Slides

14. Login

15. UI

16. Login

17. UI

18. User Privileges