1. COSMIC - SYSTEM TRR PRESENTATION
TEAM 2

2. OUTLINE OCD Demo of Operational Capability
Test Cases, Procedures, Results
QFP
Transition Plan
Write out OCD

3. Operational Concept Overview  
5 min - Terence
Operational concept overview, TRR specific outline, transition objective & strategy

4. SYSTEM PURPOSE
The COSMIC-System is an efficient and organized inventory tracking system for USC Viterbi’s STEM Education Outreach Programs.
Provides an easy to use interface for managing and tracking inventory.
Designed to increase time and cost efficiency for the STEM Educational Outreach Programs.

5. CORE CAPABILITIES Login/Logout View Log User Privileges Search
Admin, Student, Organization
Search
Reserve Item
Check Out
Check In

6. Levels of Service Goals
Browsers Supported
Safari 11, Firefox 56.0, Chrome 61, Chrome 60
RWD / Mobile Compatibility
Desktop, Laptop, Smartphone
Database Scalability
Should LOS be quantifiable?

7. Organizational Goals Improved inventory tracking system
Increase time efficiency
inventory organization
tracking item location
automated reorder s
Increased cost efficiency
mitigate over-ordering
More efficient lesson planning

8. Transition Objective Hand off system to client Provide source code
Update system s to client specified s
Provide user manual for the system
Admin
Student
Organization (One-Pager)

9. Transition Strategy
System has already been transferred to client’s hosting package
CCD feedback has already been implemented into the system
Provide client and inventory manager with the user manuals we have already created

10. Demo
25 min - Mishaal + Rachel
Demo of Initial Operational Capability (Product status demonstration)

11. Operational Capabilities
☑ All Win Conditions have been addressed.
☑ All core functionalities have been created.
☑ The system has been transferred to the final hosting service.
☑ Changes from the CCD have been incorporated.
☐Hardware item checkout feature is not as sophisticated as desired. Item IDs must be entered manually upon Check Out / Check In rather than selected from a list of options

12. Product Status ☑ COSMIC-System finished ☑ Admin Manual
☐ Student Manual
☑ Organization Manual
☐ Transition system completely to client’s contact information
Might as well check student manual

13. Demo http://eccla.org/cosmic/ Personas Spencer Lee (Admin)
Jenny Miller (Student)
25 min - Mishaal + Rachel
Demo of Initial Operational Capability (Product status demonstration)

14. Reservation Request Email (External)
25 min - Mishaal + Rachel
Demo of Initial Operational Capability (Product status demonstration)

15. Check In Notification Email
25 min - Mishaal + Rachel
Demo of Initial Operational Capability (Product status demonstration)

16. Reorder Notification Email
25 min - Mishaal + Rachel
Demo of Initial Operational Capability (Product status demonstration)

17. Password Reset
25 min - Mishaal + Rachel
Demo of Initial Operational Capability (Product status demonstration)

18. Test Cases, Procedures, Results
10 min - Sam V. + Sitan
Test Cases, Procedures and Results

19. Test Cases TC-01 Request an Account Only Admin can create account
Newly Created account
login
delete
Manage Password
Forgot
Change
TC-02 Reserve an Item
Only Admin can make reservations
Same day reservations
Cannot exceed 3 weeks in advance
Cannot exceed max quantity
Reservations held by valid users
First half Sam

20. Test Cases TC-03 Add new Item Only an admin can add new item
Required Fields
Admin can set item properties
Admin can set item type
Admin can delete item
TC-04 View Log
Only admin can view log
Reservations are dated
Check outs are dated
Hardware Checkouts have IDs
Check in are dated
Hardware Check in have IDs
Note description required but then allowed to be empty

21. Test Cases TC-05 View Item Availability and Location
All users can view item Availability
Only admin and students can see location
TC-06 Update Item Details
Only admin can update properties
TC-06 Status gets auto updated upon check out / in
should this be update item “details”?

22. Test Cases TC-07 View Own Items Only admin and student can check out
View items currently checked out to user
TC-08 Return Items
Admin and student can return checked out items
Admin and student can cancel their reservations
Specify returned and consumed quantity
Hardware return require IDs
Note warn before delete?

23. Test Cases TC-09 Change Item Status
If the quantity is positive, the status will be available
If the quantity is 0, the status will be unavailable
The status will change as the quantity change from one side to another by checking out, reserving or return
TC-10 Automatic Reorder Notifications
Admin users are notified when an item’s total quantity is below the item’s reorder threshold amount
Test cases continued by Sitan

24. Test Cases TC-11 View Item Details
All users can view item details by clicking the item
Organization restricted from viewing location
TC-12 Website is Cross-Platform
Website is fully functioned on Windows with Chrome & Firefox
Website is fully functioned on Android with Chrome
Website is fully functioned on iOS with Safari
Website is fully functioned on Mac with Safari & Firefox
Test cases continued by Sitan

25. Test Cases TC-13 Search for an Item
All users can search for an item by name
All users can search for an item by tags
All users can see results on inventory page
TC-14 Browse Inventory
All users can see all items in inventory page
Test cases continued by Sitan

26. Test Cases TC-15 Show Item Images
All items have related thumbnail images when browsing
All item details include an image
TC-16 Manage Reservations
Admin and student can view reservations on dashboard
Admin and student can cancel reservations
Admin and student can check out reservations
Test cases continued by Sitan

27. Procedures Procedure is provided with V2 being newest Date
Test Identifier
Responsible Person
Resources
Training Needs
11/21/17
TC-01~TC-16 (all cases)
Sam Lehardi
Laptop with Safari
N/A
11/30/17
Sitan Gao
iPhone with Safari
11/24/17
Sam Villarreal
Android with Chrome
11/26/17
Nick Kwong
Laptop with Chrome
Table headers?
Firefox?

28. Results Functional Manual Testing Regression All PASS Selenium python
Chromedriver
All Pass

29. Quality Focal Point (Solved & Remaining)Technical Debt  
5 Minutes - Nick
(Solved & Remaining)Technical Debt
Traceability Matrix
2 selected Metrics

30. Traceability Matrix 1/3 OCD Requirements SSAD Test Case
OC-1 Login/Logout
WC-1 User can request an account
ATF-5 User Profile
TC-01-01, TC-01-02, TC-01-03
UC-1, UC-2, UC-10, UC-11
WC-13 Website is usable on multiple platforms
TC-12-01, TC-12-02, TC-12-03
UC-1, UC-2
OC-2 User Privileges
WC-3 Admin can add new items to the system
ATF-7 User Access Level
TC-03-01, TC-03-02, TC-03-03, TC-03-04
UC-12
WC-7 Admin can change an item's status
TC-06-01
UC-12, UC-13, UC-14
WC-11 Admin notification for out of stock items
TC-10-01
“Operational concepts”?
Update this to match OCD Section: Add View Log OCD

31. Traceability Matrix 2/3 OCD Requirements SSAD Test Case OC-3 Search
WC-6 Check current item availability and location
ATF-1 Items
TC-05-01, TC-05-02
UC-3, UC-4
WC-12 Users can view item details
TC-11-01
UC-3
WC-14 Users can search for an item
TC-13-01, TC-13-02
UC-4
WC-15 Users can browse the inventory
TC-14-01
WC-16 Website should show item images
TC-15-01, TC-15-02
OC-4 Reserve
WC-2 Admin can reserve an item
ATF-2 Reservations
TC-02-01, TC-02-02, TC-02-03, TC-02-04, TC-02-05, TC-02-06
UC-7, UC-8, UC-9
WC-18 Students can manage their reservations
TC-16-01, TC-16-02, TC-16-03

32. Traceability Matrix 3/3 OCD Requirements SSAD Test Case OC-5 Check-out
WC-8 Users can view their checked-out items
ATF-3 Checked Out Items
TC-07-01, TC-07-02
UC-5
WC-10 Item status changes with quantity
TC-09-01, TC-09-02
OC-6 Check-in
WC-9 Users can return their checked-out items
ATF-4 Checked In Items
TC-08-01, TC-08-02, TC-08-03, TC-08-04
UC-6
OC-7 View Log
WC-5 Admin can read item logs
ATF-6 User Activity Log
TC-04-01, TC-04-02, TC-04-03, TC-04-04, TC-04-05, TC-04-06
UC-15

33. Burndown Chart
blurry chart

34. Created vs. Resolved Issues Report
This chart shows the number of issues created vs. the number of issues resolved in the last 100 days.
Shows development progress.
Shows the team is quickly resolving issues.
Shows backlog is not growing.

35. Average Age Report
This chart shows the average number of days issues were unresolved for on a given day over the past 100 days.
Shows backlog is being kept up to date.
Shows team is keeping up with incoming work.

36. Pie Chart of Issues and Tasks
Most issues and tasks came from team activities, meetings, and documentation, followed by development.
Shows what kind of issues and tasks represent the majority of the project.

37. Technical Debt 1/2 # Description Category1 Category2
Has it been fixed?
How did you fix it/mitigation plan
No. of weeks active 1
The team has different developers working on different areas of the system code. This poses code integration issues when different programmers have to integrate their code with existing code from someone else.
Personnel Shortfalls
Reckless Deliberate
Yes
This debt will be paid back by actively having the different developers meet (in person or online) to discuss with the owner of the existing area of system code. This ensures that they have full understanding of what is currently happening before they integrate their own code. This will help to mitigate errors due to ignorance and also eliminate the inability to fix something that breaks due to not being the owner of the code area causing the problem. This mitigation plan will take approximately 4 hrs in total. It will be comprised of in person meetings as well as s, and texts. 8 2
Since some team members have less experience on web developing, many kinds of bugs may be generated during the development.
Reckless Inadvertent
The mitigation plan starts by studying web technology such as PHP during the development. Also, taking more measures to code and carrying out more tests during this period is necessary. The time expectation is that for each person, there will be 15 hours on studying, 20 hours on coding and 8 hours on testing.

38. Technical Debt 2/2 # Description Category1 Category2
Has it been fixed?
How did you fix it/mitigation plan
No. of weeks active 3
Team chose to use MySQL since it was included in client hosting package and it is easy to import items via csv format for the database, but for images of the items, they can’t be implemented as easy. MySQL is not image friendly and it would be more time efficient storing the images elsewhere. Team will need to come up with efficient way to have images aligned with items on the system.
Methods, Processes and Tools (MPT) Shortfalls
Prudent Deliberate
Yes
Researching potential options and using open source software or developing a script to automatically upload images to have them correspondent to correct item. The images do have to have ideal image file names prior to executing the script or open source software to make sure the files correspond. Estimated 4 hours to research and implement feature. 7 4
Before passing on the as-built project, we should schedule a meeting with the client to train them and familiarize them with the system we developed. We should also give them a training manual or user guide that they can reference in the future when we are no longer available.
Life Cycle Management Shortfalls
Reckless Inadvertent
I estimate it will take about 1 hour to discuss and assign a team member or team members the task of creating a user guide for the client. I estimate it will take approximately an additional 8 hours to create the training manual and an additional hour to train the client in person. 5
We have delayed working on the logging module feature because of requirement priorities. Delaying it will cause problems integrate it with the system as many other components are already built in. Time needs to be taken to fully integrate logging module to current system.
The team needs to develop a prototype for the logging system and discuss methods to integrate it. The time it will take is an estimated 15 hours to develop a prototype and 10 hours to integrate it to the system. Testing will take approximately 2 hours.

39. Transition Plan Summary of Transition Plan (as appropriate)
10 min - Sam L.
Summary of Transition Plan (as appropriate)
HW, SW, site, staff preparation
Operational testing, training, & evaluation
Stakeholder roles & responsibilities
Milestone plan
Required resources
Software product elements (code, documentation, etc.)

40. Preparation Hardware Preparation
Desktop/ Laptop/SmartPhone with Safari 11, Firefox 56.0, Chrome 61, or Chrome 60
Hosting Preparation
GoDaddy
Delegate Access
phpMyAdmin
File Manager/ FTP Account
FileZilla (Software)
FTP Account Credentials
Host
Port - leave empty or try 21
username/password

41. Testing, Training, and Evaluation
Testers performed test cases to determine functionality and possible bugs
Team test session to test multiple admin users accessing system at once
Training
One page summary manual for organizations, manual for student, and detail admin manual
Technical support as needed
No formal training session, but informal sessions as required
Evaluation
Core Capability Drive-through feedback with client
All the comments were addressed and implemented to system
Manage logs, database, s, file structure, phpmyadmin, navigating godaddy

42. Stakeholder Roles & Responsibility
Stakeholders
Responsibilities
Darin Gray - Director
STEM Educational Outreach Program
Provide delegate access to GoDaddy accounts
Assess capabilities and provide comments
Understand maintenance needs and structure of system
Gain basic understanding of phpMyAdmin
Xue Fei Lin - Inventory Manager
Finalize inventory of items in storage
Add items into database/system
Development Team - Implementers
Adjust code post testing to fix bugs and defects
Address comments from CCD and make suggested changes
Finalize website for hosting on client’s hosting package
Development Team - Testers
Ensure win conditions are met and test cases passed
Provide feedback of the system and list any concerns and bugs
Development Team - Trainers
Develop training manual and technical manuals for the system
Provide technical support and training as needed
Manage logs, database, s, file structure, phpmyadmin, navigating godaddy

43. Milestone Plan

44. Required Resources & Products
Manuals
Summary User’s Guide - Organization
Introduction to system & basic capabilities
Privileged User Manual - Student
Introduction to system & privileged capabilities
Admin User Manual - Admin
All capabilities
Automatic Functions
GoDaddy Guide - (Navigation & Access)
Maintenance - (Logs, phpMyAdmin/Database, File structure, Backups)
Products
GitHub Private Repository with source code
Team class website with project archive and documentation
Online Web Application - COSMIC - System hosted on
github private repo - is this really what we’re providing tho?

45. Questions?