High SchoolSports Scoring and Analysis

ByJames Sheets

Brian RodriguezMike Kinnel

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

Major Software Functions

● Database – Tournament Related– Tournaments– Sporting Events– Finish Listings– Participants– Houses– Teams– Finishing Places

Major Software Functions

● Database – Administration Related– Authorized Members

● Website– Public Pages– Authorized Only Pages

Performance and Behavior Issues

● Display in popular web browsers

Management and Technical Constraints

● Integration with existing web server and student records database

Project Estimates

● Historical Data Used For Estimates– LOC Cost = $13– Burdened Labor Rate = $8,000

– Average FP's Per Month = 15

Estimation Techniques and Applied Results

● Functionality Points

– Number– Types– Complexity

● Lines of Code

– Modules– LOC per

Estimation For Technique:Functionality Points

External Inputs

● Modify Authorized Members● Tournament Information● Sporting Event Information● Finish Listings● Participant Information● Team Information● House Information● Finishing Place

Estimation For Technique:Functionality Points

External Outputs

● Website Homepage● Authorized Member Login

Estimation For Technique:Functionality Points

External Inquiries

● 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

Internal Logic Files

● Authorized Members Database Table● Tournaments Table● Sporting Events Table● Participants Table● Teams Table● Houses Table● Finishing Places Table

Estimation For Technique:Functionality Points

External Interface Files

● none

Function Point Score Chart

Information Domain Value CountWeighting Factor

Simple Average Complex8 * 3 = 322 * 5 7 = 85 * 6 = 127 * 15 = 490 * 5 7 10 = 0

Count Total 101

External Inputs (EL's) 4 6 External Outputs (EO's) 4 External Inquiries (EQ's) 3 4 Internal Logical Files (ILF's) 7 10 External Interface Files (EIF's)

VAF Adjustment Questions

No. Question Score1 Does the system require reliable backup and recovery? 22 Are specialized data communications required to transfer information to or from the application? 03 04 Is performance critical? 35 Will the system run in an existing, heavily utilized operational environment? 46 Does the system require on-line data entry? 57 Does the on-line data entry require the input transaction to be built over multiple screens or operations? 18 59 Are the inputs, outputs, files, or inquiries complex? 5

10 Is the internal processing complex? 411 212 313 214 5

Total 41

Are there distributed processing functions?

Are the ILF's updated on-line?

Is the code designed to be reusable?Are conversion and installation included in the design?Is the system designed for multiple installations in different organizations?Is the application designed to facilitate change and for ease of use by the user?

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

Estimation For Technique:Lines of Code

14 web pages * ( 40 | 70 | 90 ) loc

8 web forms * (40 | 70 | 100 ) loc

14 web pages * 3 database calls * (12 | 20 | 30 ) loc

Estimated Lines Of Code

ModuleWeighting Factor

Optimal Likely Pessimistic Weighted AvgUser Interface and Control Facilities 480 980 1260 943Error Checking 320 560 800 560Database Management 504 840 1260 854Total 2357

LOC Estimate

● LOC per person: $8,000 / 13 = $616

● Person Months: 2375 / $616= 3.8

● Cost: $13 * 2357 = $30,641

Reconciled Estimate

● Function Points Cost Estimate: $57,564● Lines of Code Estimate: $30,641

-----------$88,205

● Development Cost: $88,205

÷ 2-----------$44,102

Project Resources

People ● James Sheets● Brian Rodriques● Mike Kinnel

● Server–Class PC– 1-ghz processor– Raid-1 config– 1 gig hard drive

Hardware

Project Resources

Tools ● Zend 5.0● Poisedon UML

● Apache 2 Web Server● PHP 5.0● MySQL 5.0● MyPhpAdmin 2.4.6

Software

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.

Lack of Team or Member ExperienceWith Tools

Probability: LowSeverity: Medium

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.

Loss of Team Member During Project

Probability: MediumSeverity: High

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.

Customer – Developer Communications

Probability: MediumSeverity: 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.

Poor Intranet / Internet Performance

Probability: LowSeverity: Medium

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.

Poor Database Performance

Probability: MediumSeverity: Medium / 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.

Poor Computer Security

Probability: MediumSeverity: High

Project Risks

●Make sure developers have a clear understanding of requirements.●Provide users with prototypes to ensure that needs are being met or addressed.

System Does Not Meet CustomerExpectations

Probability: MediumSeverity: Medium

Project Risks

●Ensure clear communication.●Frequent updates on progress of the project to senior management.●Keep the manager happy.

Loss of Customer

Probability: LowSeverity: Medium

Risk Table

Risk Probability SeverityCustomer-Developer Communication 65% MediumSoftware Schedule Delay 50% MediumLoss of Team Member During Project 35% HighPoor Computer Security 35% HighPoor Database Performance 35% Medium / HighSystem Does Not Meet Customer Expectations 30% MediumLack of Team or Member Experience With Tools 20% MediumPoor Intranet / Internet Performance 15% MediumLoss of Customer 5% High

Overview of Risk Management

● Risk Identified

● Risk Tracked

● Risk Evaluated

Task Set

● High Level Analysis

● Functionality Breakdown

● Select Hardware / Software– Identify Integration Requirements

● Perform Risk Assessment

● Estimate Project Cost

Task Set

● Database Prototyping– Create Database Diagram

● Database Development– Define Tables and Columns– Create Table Indexes

● Database Testing– Test Cases

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

Task Set

● Security Testing– Firewall Setup– Access Logs

● Deployment and Integration– Hardware / Software Installation– Database Setup

● Live System Test

● Training

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

Estimation Breakdown

Task Estimate Task EstimateHigh Level Analysis 2 days Website Development 16 daysFunctionality Breakdown 2 days Home Page 1 daySelect Hardware / Software 3 days Authorized User Login Page 1 day

Identify Integration Requirements 1 day Authorized Data Modification Pages 10 daysRisk Analysis 1 day Authorized Data Display Pages 1 dayEstimate Cost 2 days Public Data Display Pages 6 daysDatabase Prototyping 3 days Website Testing 4 days

Create Database Diagram 1 day Test Web Links 1 dayDatabase Development 2 days Test Authorized User Login 1 day

Define Tables and Columns 2 days Test Data Insertion 1 dayCreate Table Indexes 1 day Check Database Return Results 1 day

Database Testing 3 days Security Testing 2 daysTest Cases 3 days Firewall Setup 1 day

Website Prototyping 4 days Access Logs 1 dayDefine Layout 2 days Deployment and Integration 2 daysCreate Custom Style Sheets 1 day Hardware/ Software installation 1 day

Database Setup 1 dayLive Systems Test 1 dayTraining 2 days

Critical Path Chart

Task Duration EST EFT LST LFT SlackHigh Level Analysis 2 0 2 0 2 0Functionality Breakdown 2 2 4 2 4 0Select Hardware / Software 3 2 5 2 5 0Risk Analysis 1 4 5 4 5 0Estimate Cost 2 2 7 27 29 22Database Prototyping 3 5 8 21 24 16Database Development 2 8 10 24 26 16Database Testing 3 10 13 26 29 16Website Prototyping 4 5 9 5 9 0Website Development 16 9 25 9 25 0Website Testing 4 25 29 25 29 0Security Testing 2 5 7 22 29 22Deployment and Integration 2 29 31 29 31 0Live Systems Test 1 31 32 32 33 1Training 2 31 33 31 33 0

Task Duration Start Date End Date

March April

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 1 2 3 4 5 6 7 8 9 10 11 12 13

High Level Analysis 2 days 03/01/06 03/03/06

Functionality Breakdown 2 days 03/03/06 03/04/06

Select Hardware/Software 3 days 03/03/06 03/08/06

Identify Integration Requirements 1 day 03/03/06 03/04/06

Perform Risk Assessment 1 day 03/07/06 03/08/06

Estimate Project Cost 2 day 03/08/06 03/10/06

Database Prototyping 3 days 03/08/06 03/11/06

Create Database Diagram 1 days 03/10/06 03/11/06

Database Development 2 days 03/13/06 03/15/06

Define Tables and Columns 2 days 03/13/06 03/15/06

Create Table Indexes 1 day 03/14/06 03/15/06

Database Testing 4 days 03/15/06 03/21/06

Test Cases 3 days 03/15/06 03/18/06

Website Prototyping 4 days 03/08/06 03/14/06

Define Layout 2 days 03/08/06 03/10/06

Create Custom Style Sheets 1 day 03/10/06 03/11/06

Website Development 16 days 03/14/06 04/05/06

Create Home Page 1 day 03/14/06 03/15/06

Create Authorized User Login Page 1 day 03/15/06 03/16/06

Create Authorized Data Modification Pages 10 days 03/15/06 03/29/06

Create Authorized Data Display Pages 1 day 03/29/06 03/30/06

Create Public Data Display Pages 6 days 03/28/06 04/05/06

Website Testing 4 days 04/05/06 04/11/06

Test Web Links 1 day 04/05/06 04/06/06

Test Authorized User Login 1 day 04/06/06 04/07/06

Test Data Insertion 1 day 04/07/06 04/08/06

Check Database Return Results 1 day 04/10/06 04/11/06

Security Testing 7 days 03/08/06 03/17/06

Firewall Setup 1 day 03/09/06 03/10/06

Access Logs 1 day 03/01/06 03/30/06

Deployment and Integration 2 day 04/11/06 04/13/06

Hardware/ Software installation 1 day 04/11/06 04/12/06

Database Setup 1 day 04/11/06 04/12/06

Live System Test 1 day 04/13/06 04/14/06

Training 2 days 04/13/06 04/14/06

Team Structure

Management

● Dan Dollars

● Barbara Bean

Technical Staff

● James Sheets

● Brian Rodriguez

● Mike Kinnell

Management Reportingand Communication

● Weekly Meetings

● Resource Access

● Client Collaboration

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

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