1 / 45

High School Sports Scoring and Analysis

By James Sheets Brian Rodriguez Mike Kinnel. High School Sports Scoring and Analysis. Project Scope. Keep records of sporting events Competition between school 'houses‘ Boys and Girls teams Authorized user updating Authorized user rankings and totals Public Display.

kirby-robbins
Download Presentation

High School Sports Scoring and Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. By James Sheets Brian Rodriguez Mike Kinnel High SchoolSports Scoring and Analysis

  2. Project Scope • Keep records of sporting events • Competition between school 'houses‘ • Boys and Girls teams • Authorized user updating • Authorized user rankings and totals • Public Display

  3. Major Software Functions • Database – Tournament Related • Tournaments • Sporting Events • Finish Listings • Participants • Houses • Teams • Finishing Places

  4. Major Software Functions • Database – Administration Related • Authorized Members • Website • Public Pages • Authorized Only Pages

  5. Performance and Behavior Issues • Display in popular web browsers

  6. Management and Technical Constraints • Integration with existing web server and student records database

  7. Project Estimates • Historical Data Used For Estimates • LOC Cost = $13 • Burdened Labor Rate = $8,000 • Average FP's Per Month = 15

  8. Lines of Code Modules LOC per Estimation Techniques and Applied Results • Functionality Points • Number • Types • Complexity

  9. Modify Authorized Members Tournament Information Sporting Event Information Finish Listings Participant Information Team Information House Information Finishing Place Estimation For Technique:Functionality Points External Inputs

  10. Website Homepage Authorized Member Login Estimation For Technique:Functionality Points External Outputs

  11. Display Tournament Information Display Sporting Events Display Teams Display Rankings By Event and Team Display Total Points For Each House Estimation For Technique:Functionality Points External Inquiries

  12. Authorized Members Database Table Tournaments Table Sporting Events Table Participants Table Teams Table Houses Table Finishing Places Table Estimation For Technique:Functionality Points Internal Logic Files

  13. none Estimation For Technique:Functionality Points External Interface Files

  14. Function Point Score Chart

  15. VAF Adjustment Questions

  16. FP Estimate • FP's: = 101 * [ 0.65 + ( 0.01 * 41 ) = 108 • Cost Per FP: = $8,000 / 15 = $533 • PM's: = 105 / 15 = 7.2 • Estimated Cost: = $533 * 108 = $57,564

  17. 14 web pages * ( 40 | 70 | 90 ) loc8 web forms * (40 | 70 | 100 ) loc 14 web pages * 3 database calls * (12 | 20 | 30 ) loc Estimation For Technique:Lines of Code

  18. Estimated Lines Of Code

  19. LOC Estimate • LOC per person: $8,000 / 13 = $616 • Person Months: 2375 / $616 = 3.8 • Cost: $13 * 2357 = $30,641

  20. Reconciled Estimate • Function Points Cost Estimate: $57,564 • Lines of Code Estimate: $30,641 ----------- $88,205 • Development Cost: $88,205÷2 ----------- $44,102

  21. James Sheets Brian Rodriques Mike Kinnel Project Resources People Hardware • Server–Class PC • 1-ghz processor • Raid-1 config • 1 gig hard drive

  22. Zend 5.0 Poisedon UML Project Resources Tools Software • Apache 2 Web Server • PHP 5.0 • MySQL 5.0 • MyPhpAdmin 2.4.6

  23. Lack of Team or Member Experience With Tools Probability: Low Severity: Medium Project Risks • Team member will be chosen based on past experience if possible. • Tools chosen will be in common use and open-source if possible. • Training should be provided for member who are determined to be lacking.

  24. Loss of Team Member During Project Probability: Medium Severity: High Project Risks • The project manager will need to monitor developer progress and team communications without undue pressure that may cause stress to the team. • Make sure that changing circumstances are documented and risks are tracked. • Short technical review and status meeting should be held to allow developers to report task status and bring concerns to the team.

  25. Customer – Developer Communications Probability: Medium Severity: Medium Project Risks • All developers will have a copy of all customer needs documentation. • Customer should be available to team member if needed to clarify needs / changes. • Developers or liaisons should be available to answer customer questions and continue to clarify and refine requirements as needed.

  26. Poor Intranet / Internet Performance Probability: Low Severity: Medium Project Risks • Redundant High-speed Internet connection to provide high availability for external website. • Perform load testing on customer infrastructure and Internet connections. • Recommend Hardware changes if necessary to customer to improve performance.

  27. Poor Database Performance Probability: Medium Severity: Medium / High Project Risks • Perform load testing on the databases applications on customers servers. • Perform load testing on customer servers connections and check available space to hold data. • Recommend Hardware changes if necessary to customer to improve performance.

  28. Poor Computer Security Probability: Medium Severity: High Project Risks • Follow up with the Internet service provider to assure proper security provisioning. • Check that Anti-virus and firewall systems are in place on customers systems. • Recommend that customer schedules automatic virus definition and patch download and installation on systems.

  29. System Does Not Meet Customer Expectations Probability: Medium Severity: Medium Project Risks • Make sure developers have a clear understanding of requirements. • Provide users with prototypes to ensure that needs are being met or addressed.

  30. Loss of Customer Probability: Low Severity: Medium Project Risks • Ensure clear communication. • Frequent updates on progress of the project to senior management. • Keep the manager happy.

  31. Risk Table

  32. Overview of Risk Management • Risk Identified • Risk Tracked • Risk Evaluated

  33. Task Set • High Level Analysis • Functionality Breakdown • Select Hardware / Software • Identify Integration Requirements • Perform Risk Assessment • Estimate Project Cost

  34. Task Set • Database Prototyping • Create Database Diagram • Database Development • Define Tables and Columns • Create Table Indexes • Database Testing • Test Cases

  35. Task Set • Website Prototyping • Define Layout • Custom Style Sheets • Website Development • Home Page • Authorized User Login Page • Authorized User Updating Pages • Authorized User Data Display Pages • Public Data Display Pages • Website Testing • Web Links • Authorized User Login • Data Insertion • Database Return Results

  36. Task Set • Security Testing • Firewall Setup • Access Logs • Deployment and Integration • Hardware / Software Installation • Database Setup • Live System Test • Training

  37. Functional Decomposition • Authorized Member Login • Create Authorized Member • Modify Tournament Information • Modify School Houses • Modify Sporting Events • Modify Sporting Event Finish Listings • Modify Finishing Place Listings • Display House Point Totals • Display Tournament Information • Display Teams • Display Team Finishing Places • Display Sporting Event Finish Placings

  38. Estimation Breakdown

  39. Critical Path Chart

  40. Technical Staff James Sheets Brian Rodriguez Mike Kinnell Team Structure Management • Dan Dollars • Barbara Bean

  41. Management Reportingand Communication • Weekly Meetings • Resource Access • Client Collaboration

  42. Tracking and Control Mechanisms SQA Plan • Team, product, environment evaluations. • Audits and reviews. • Project standards. • Error tracking and reporting procedures • SQA responsible documents • Amount of feedback provided

  43. Change Management Control Change Handling Process • Change request submitted • SCM evaluation • ECO is generated • SCI is checked out • Change is made • SQA reviews modified SCI • Modified SCI checked back in • SCR is generated

More Related