Bygg en hemsida

Website for managing sponsors/pleeds to jogging events Short description: On this website it shall be possible to create a jogging event where runners will run a number of laps and their sponsors will pay a sum for each lap. Runners shall be part of teams, e.g. different ages. Sponsors shall be able to sponsor laps for one or many runners/teams or/and the complete event. The graphical layout is not that important for version 1.0 but it shall be possible to update the layout in an easy way for coming releases. Templates of contents of reports and content+layout of invoices and diplomas can be provided upon request. Proposed information objects are only proposals. Deliverables: implementation according to requirements below, all code and binaries, installation instruction for a standard web hotel, installation instruction of the development environment Non functional Requirements: - The solution may not be reused for any other customer, it shall be owned by me. - It shall be easy to change graphical design of all pages on the website - The website shall be adapted to be easily and nicely opened in a mobile phone - It shall be easy to change all texts within the website to another language - It shall be easy to manage default proposals of descriptions and sponsor texts on event-, team- and runner level. - It shall be easy to deploy the solution at a standard webhotel (e.g. PHP, MySQL etc) - The development environment shall be as cheap as possible - The solution shall use all best practice security checks to prevent access to data and corruption of data (e.g. code inception, robot creation of events…) - Confirmation of email address shall be done when a person is registering on the site as event admin, team admin, runner or sponsor. - Access: o event_admin shall have access to CRUD* event, team, runner, sponsor o team_admin shall have access to CRUD team, runner o runner_admin shall have access to CRUD runner o sponsor_admin shall have access to CRUD sponsor *CRUD = Create, Read, Update, Delete   Page one: Setup event (before event) Description: This is where the event organizer create and manage the event. The organizer shall be able to invite teams and sponsors to participate in the event. Use cases: Create event, Change profile content of event, Manage teams in event (Create, Read, Update, Delete) Create teams in event from cvs list Send email invite to sponsors Send email invite to teams Send link to event’s page via SMS to invite sponsor Send “thank you” email to runners Send “thank you” email to event/team/runner sponsors Information objects: event = event_name, event_admin (= user) event_logo, event_date, event_description, event_sponsor text, event_sponsor_prospect_list, event_sponsor_list, event_profile_picture_library, event_race_picture_library event_sponsor_prospect_list = list of event_sponsor_prospects event_sponsor_prospect = email address, number_of_invites event_sponsor_list = list of sponsor sponsor_sum_per_lap sponsor_sum_fixed event_profile_picture_library = list of event_profile_pictures event_race_picture_library = list of event_race_pictures   Page two: Setup Team (before event) Description: This is where the team responsible manage his/her team. The team responsible shall be able to invite runners and sponsors to participate in the event. Use Cases: Create team to participate in event, Change profile content of team, Manage runners in team (Create, Read, Update, Delete) Create runners in team from cvs list Send email invite to runners Send email invite to sponsors Send link to team’s page via SMS to invite sponsor Information objects: team = team_admin (= user) team_name, team_description, team_sponsor_text, team_sponsor_prospects_list, team_sponsor_list, team_profile_picture, team_race_picture team_sponsor_prospects_list = list of team_sponsor_prospects team_sponsor_prospect = email address, number_of_invites team_sponsor_list = list of sponsor sponsor_sum_per_lap sponsor_sum_fixed   Page three: Setup runner (before event) Description: This is where the runner manages his/her profile data. The runner shall be able to invite sponsors to participate in the event. Use Cases: Create runner Add runner to team in event, Change profile content of runner, Send email invite to sponsors Send link to runner’s page via SMS to invite sponsor Information objects: runner = runner_admin (= user), runner_description, runner_sponsor_text, runner_sponsor_prospect_list runner_sponsor_list runner_profile_picture, runner_picture_from_race runner_sponsor_prospects_list = list of sponsor_prospects sponsor_prospect = email address, number_of_invites runner_sponsor_list = list of sponsor sponsor_sum_per_lap sponsor_sum_fixed   Page four: Setup Sponsor (before event) Description: This is where the Sponsor manages his/her profile data. The sponsor shall be able to select event, teams and/or runners to sponsor. Use Cases: Add sponsor to event, View runners, teams and events that I sponsor (with sums) Select to sponsor event, Select to sponsor team, Select to sponsor runner Information objects: sponsor = sponsor_admin (= user), sponsor_description, sponsor_profile_picture,   Page five: Manage event (during event) Description: This is where the event organizer manage the event during the event day. It is here start lists are generated, laps are counted and race pictures are taken. Use cases: Assign start number to runner Generate start list Register number of laps for runner Collect race picture of runner (via USB-attached camera) Information objects: startlist = runner, number_of_laps   Page six: Manage event follow-up (after event) Description: This is where the event organizer follow-up the event and can see statistics on number of teams, runners, sponsors and sponsor sums. It is also here that the event organizer can generate, distribute and follow-up invoices to sponsors. Use cases: Generate summary for event (export to excel) Generate summary for each team (export to excel) Generate summary for each sponsor (export to excel) Generate invoice for each sponsor Remove event/teams/runners from a sponsors list Generate PDF diploma for each sponsor Send invoice via email to each sponsor Mark invoice as paid Mark invoice as canceled Generate report on paid invoices between two dates Information objects: invoice_list = list of invoice, receiver (= user), sum, number of invoice emails.   Generic information objects: user = first_name, family_name, street address, post_code, town, mobile_phone_number, email_address, password (encrypted)