1. USC Football Recruiting Database System. Team 6 Client: Jared Blank with USC Football. Revati Kadu Natasha Karnik Akshay ArasMike Nicosia (IV & V) Abhishek Venkatesh Aishwary Kumar (IV & V) Amruta Chitnis Aditya Shukla (IV & V)

2. Transition Readiness Review Outline Operational Concept Overview Demo of the Product Support Plan Data Reporting and Archiving Summary of Transition Plan Feedback

3. Operational Concept Overview - Abhishek Venkatesh

4. Project Background Current System Developed System Success Critical Stakeholders Organizational Goals

5. Project Background USC Football program: large number of people involved during the recruiting process. The idea : develop a program to efficiently support this process. High Level Impact:  Better management of prospective applicants & players  Better client participation in other administrative activities.  Improved online repository of classified player information

6. Current System Personal records of player’s information are stored in Excel. There are more than 150 records, hence, lot of time is spent in searching for the recruit’s information. Jared uses information stored in Excel to make phone calls. Spends approx. 2 hours for 150 phone calls regarding updates.

7. Developed System  The new system provides a database which stores information of potential recruits. The user obtains information using this database. The new system can send text messages to the recruit’s mobile phone. There are 2 sets of users – Executive and Standard, each with different privileges.

8. Success Critical Stakeholders Jared Blank – Client Standard User: Football Coaches, supporting staff System maintainers Developers  Revati Kadu ( Project Manager)  Natasha Karnik (Life Cycle Plans and Prototypes)  Akshay Aras (Project Coordinator)  Amruta Chitnis (Systems Architecture and Project Tracking)  Abhishek Venkatesh (Operational Concept and Analysis)  Potential Recruits

9. Organizational Goals OG1: Better way of storing information and improved way of searching by having information stored in a database OG2: Efficient operational capability via text messaging functionality.

10. New and changed requirements Data reporting: Printout of important content (already satisfied) Issue of budget discussed with the client. Hence a particular COTS was chosen.

11. Product Demo - Natasha Karnik - Amruta Chitnis

12. Support Plan - Natasha Karnik

13. Hardware Requirements A hard disk. Monitor or display device, and graphics card Standard 101/102 key keyboard Standard mouse Built-in Network Card

14. Software Requirements Windows XP Professional 2005 IIS Server.NET Framework MS Access Microsoft Visual Studio 2005 Internet Explorer/ Mozilla Firefox

15. Support Responsibilities The development team IV&V Client Users Maintainers

16. Data Reporting - Revati Kadu - Akshay Aras

17. Based on Business Case Analysis Project Duration: 24 weeks, 2 semesters. Positive ROI (0.62) starting year 2006. Number of Developers for 577a: 6 577b: 5

18. Effort for Developers Effort* from start of 577a for 6 developers till date. Planned: 1183 Actual: 1212 Effort* from start of 577b for 5 developers till date. Planned: 697 Actual: 723  *Person Hours Above information is based on calculations done using progress reports of each semester. Till date: 4/11/2006

19. Source Code Estimates Revised COCOMO (v1.4) Estimate: 1601 Current Code Count estimate (hand count method): 1802

20. Project Issues Configuration Management. COTS Re-analysis.

21. Transition Plan Summary - Akshay Aras

22. Changes in Transition Plan Transition Strategy Transition Process

23. Changes in Transition Plan Identification of Maintainers Addition of Maintenance Prospective IDE Un-Installation

24. Transition Strategy Fault Free Installation Decision on Multiple Nodes Maintenance Readiness

25. Transition Process Pre-Deployment Maintenance Data Pre-Loading Staged Training Operation Guides

26. Feedback / Q & A

27. Thank You!!