1 / 11

Roster Management System

Roster Management System. Ben Helppi Jaclyn Hoke Aaron Johnson Nathan Peterson. Business Need. Customer: Iowa City Girls Softball League (ICGSL) Unfair distribution of skill across teams Detracts from the fun of the game Poor representation for the ICGSL

wynona
Download Presentation

Roster Management System

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. Roster Management System Ben Helppi Jaclyn Hoke Aaron Johnson Nathan Peterson

  2. Business Need • Customer: Iowa City Girls Softball League (ICGSL) • Unfair distribution of skill across teams • Detracts from the fun of the game • Poor representation for the ICGSL • New process for assigning teams has been created

  3. Process Part 1: Data Entry • Collect player registrations • Coaches enter player evaluation data • Separate ‘Core’ players • Calculate average skill score per team

  4. Process Part 2: Core Players • Keep last year’s teams together • Make sure children of coaches/sponsors are on appropriate teams • Balance teams • Balance pitchers

  5. Process Part 3: Free Agents • Distribute free agents with skill assessments • Distribute free agents without assessments • Verify teams have required roles • Verify teams meet ‘fairness’ criteria • Average • Deviation from average • Pitching • Age/Experience

  6. Requirements • Coaches can submit data directly to application • Manual override • Ability to change skill assessment criteria • Ability to change ‘fairness’ criteria

  7. Development Plan • Lifecycle model • Modified Design-to-Schedule • Allows for revision of requirements and architecture • Non-essential phases late in schedule help ensure project completion by deadline • Configuration management • Google Code subversion (SVN)

  8. Scheduling

  9. Risks • Overly Optimistic Schedules (Inaccurate Estimation) • Poor Schedule Management • Friction with Customer • Changing Requirements • Loss of Personnel • Hardware and/or Software Setbacks (Crashes) • Lack of Skills or Knowledge • Inadequate Design • Initial Server not Supporting Chosen Toolset

  10. Risk Management • The first ten minutes of the team meetings will be spent discussing any risks that have come up and what measures will be taken if any have occurred. • Also, if any additional risks are identified, they will be discussed and plans for avoiding it will be made.

  11. Technology Choices • Microsoft ASP .NET for web interface • Model-View-Controller architecture with .asp pages and C# for control • ICGSL choice of web server may dictate database options • Microsoft SQL Server, MySQL, or equivalent ideal

More Related