Online Membership and Event Registration System (Sport)

Develop an online members? registration system that allows athletes, coaches, officials or volunteer? to register as? a member as well as register in an event (race, training course, etc). The registration of the individual would be based on a variety of parameters (age, gender, personal preferece, ability, etc). Along with collecting demographic information through the registration process,? the system would need to process payment to our bank using a system like Bean Stream, Moneris, or Visa Desjadins.? The system would need a reporting feature that allowed an administrator to produce excel or csv reports based on a variety of criteria (e.g, prouduce a list of male athletes with a date of birth greater than October 1st, 1990). The system would need to retain each year of information so that reports can be based on multiple years of data. The system would also need to allow a user to register in a sports competition. This woulkd be similar to a system like <[login to view URL]> or ? <[login to view URL]> . ## Deliverables ? **Scope** *(This is just the general description of the project, including the goals and objectives of the application at a high level, i.e. just use plain English to describe what this is and what it should do.? Be brief.? It’s just to answer the “what are we building??? "what does it need to do or address?" type of questions.)* ? 1. A database to store information about members, customers, events, and race series 2. A web-based front-end for database modifications and reporting 3. A web-based registration system to deal with the following: 1. Registration of new members 2. Registration of new clubs and teams 3. Membership renewals 4. Entry in events 5. Accepting payment for all of the above ? **Functional Partitioning** *(A description of each function required in the application; the following sections will attempt to separate each “piece?? (or page or screen) into a module to focus on and provide description.? e.g. "mountain biking section would contain the following features, etc...".? This ideally, is the largest and most detailed section of the requirements.? Provide a breakdown of each specific function or module (numbered lists are practical to sort and use for easy reference); you would break down each page or screen shot here, while including all details, descriptions of functions, screen shots, and mockups associated with what this )should and should not do… the more detail you provide here will be less hassle down the line, and will reduce overall risk.* *? * Here’s an overview. Further detail for each item is supplied in a later version of the document. *? * 1. Database 1. Individuals ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? i.? ? ? Licensed Members 1.? ? ? ? Racing Licenses 2.? ? ? ? Technical Licenses 3.? ? ? ? Both Racing & Technical Licenses ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii.? ? ? Associate Members ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iii.? ? ? General Members ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iv.? ? ? Non-Member Customers 1.? ? ? ? UCI License Holders from other Jurisdictions 2.? ? ? ? Single Event License Purchasers 1. Groups ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? i.? ? ? Cycling Clubs ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii.? ? ? Trade Teams ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iii.? ? ? Event Promoters ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iv.? ? ? Partners ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? v.? ? ? Sponsors 1. Events ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? i.? ? ? Races ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii.? ? ? Courses ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iii.? ? ? Camps / Clinics ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iv.? ? ? Meetings ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? v.? ? ? Miscellaneous 1. Series ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? i.? ? ? Race Series ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii.? ? ? Clinics / Courses / Workshops 1. Event Registration (public) 1. Member Registration (public) 2. Individual Member Services (private) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? i.? ? ? Member Information Update ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii.? ? ? Buy & Sell Forum ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iii.? ? ? Obtain a print / facsimile of your license ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iv.? ? ? Event Management (for those listed as the ‘organizer’ for an event) 1. Group Member Services (private) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? i.? ? ? Member Information Update ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii.? ? ? Web Content Management for Group Web Space ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iii.? ? ? Event Management (for those listed as the organizing group for an event) 1. Administration (private) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? i.? ? ? Database reporting ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii.? ? ? Member Registration Review & Approval ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iii.? ? ? Member Search & Update ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? iv.? ? ? Create New Member ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? v.? ? ? Event Creation and Management ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? vi.? ? ? Series Creation and Management ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? vii.? ? ? Buy & Sell Forum Management ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? viii.? ? ? Web Content Management ? ? **General Constraints** *List some of the system considerations that must be met… be it performance limitations, or usage issues… something that the developer can keep in mind when building this.? e.g. min. screen resolution, security aspects, download times, etc.* ? 1. **Speed:** Any section of the web site where there is user input other than following hyperlinks should be simple, and free of large images or other sizeable content; page reloads where data is entered must be swift ? 1. **Page Reloads:** Minimize the number of page reloads when entering data, producing reports, traversing lists, or searching for members ? 1. **Task Flow:** is important… for instance, when updating member records, it would be handy to have a “next member in the list?? button or “search for next record?? feature so that we don’t have to back track to a search function ? 1. **Security:** there needs to be a strict division between the public, private, and administrative sections of the web site ? ? **Design Constraints** *(List any visual and product constraints that must be adhered to (color schemes, real estate usage, content standards, etc.).? This is also a good section to include screen mockups and storyboards at a general level, if they can’t be provided in detail in each of the functional partitions.)* ? Unknown at this time. Factors may include the redesign of our logo. ? In the event that our logo and association colors change, it’s desirable that we should be able to change this fairly easily. Perhaps a simple, clean design is best, with most pages using the same style sheets? **Maintenance and Reliability Requirements** *(Describe the uptime considerations that must be met (e.g. 7x24) and/or the post-launch maintenance issues (e.g. administrator will update content weekly in x,y,z areas).)* ? 1. Content Updates: Web content is updated by staff and key volunteers on a continuous basis. 2. The Content Management System and Web Site need to be available 24x7 3. Backups ??" Database & Web Content; at least weekly **Special Considerations** *(Consider this a miscellaneous section to detail any special quirks relating to this project.? Be specific.)* ? 1.? ? ? ? **Persistence:** All member data must persist in the database until changed or deleted; the database is not wiped clean after each year. There should be an archive and purge feature that will let us clear records older than a date we set. 2.? ? ? ? **Forms:** Data entry forms need to be relatively simple, with auto-completion of fields where the context makes it possible… for example, UCI code should be generated from Nationality and Birth Date 3.? ? ? ? **Data Entry Restrictions by Field:** Some fields will need to have a particular format; dates, uci codes, categories, etc. 4.? ? ? ? **Membership Expiry:** At the end of the year (midnight, December 31), all members’ status is set to ‘expired’ 5.? ? ? ? **Record Transfer:** All data from Karelo needs to be ported to the new database 6.? ? ? ? **Member Identification:** Cycling BC needs to assign a unique member identifier that never changes to each member 7.? ? ? ? **Member Duplication:** When approving membership renewals, a list of members with similar names should be produced in case a member has forgotten his username and simply registered as a new member, rather than a renewal ??" basically, we need a system to prevent duplicate members 8.? ? ? ? **Category History:** A category history and credential history needs to be maintained for all license holders (racing and technical) 9.? ? ? ? **Address Restrictions:** Cycling BC is only able to sell memberships to BC residents; as such, any non-BC address in a membership application or renewal must be refused 1. **Bar Coding: Persistence:** All member data must persist in the database until changed or deleted; the database is not wiped clean after each year. There should be an archive and purge feature that will let us clear records older than a set date. 2. **Forms:** Data entry forms need to be relatively simple, with auto-completion of fields where the context makes it possible… for example, UCI code should be generated from Nationality and Birth Date 3. **Data Entry Restrictions by Field:** Some fields will need to have a particular format; dates, uci codes, categories, etc. 4. **Membership Expiry:** At the end of the year (midnight, December 31), all members’ status is set to ‘expired’ 5. **Record Transfer:** All data from Karelo needs to be ported to the new database 6. **Member Identification:** Cycling BC needs to assign a unique member identifier that never changes to each member 7. **Member Duplication:** When approving membership renewals, a list of members with similar names should be produced in case a member has forgotten his username and simply registered as a new member, rather than a renewal ??" basically, we need a system to prevent duplicate members 8. **Category History:** A category history and credential history needs to be maintained for all license holders (racing and technical) 9. **Address Restrictions:** Cycling BC is only able to sell memberships to BC residents; as such, any non-BC address in a membership application or renewal must be refused 10. **License Printing:** Currently, we print directly to license forms on card-stock. As early as 2007 or 2008, CCA may introduce plastic ID cards for licenses; the license report will likely need to be modified at some point to allow for this.