Development of Fantasy Football Website

Development of Fantasy Football WebsiteChapter 1. IntroductionProject OverviewLast year a drift was completed for Mr. Starkey (hereinafter referred to as knob) to design a family website. The website was centered on a partiality football league created for family and friends from around the world. Many former(a) feature of speechs were involved in the creation of this website including games, events, family news and many more. With all these and an advanced fantasy football competition, more than just a website site was created. In fact a summon from the invitee stated The website has brought everyone together into a kind of Family Intranet or in other words, a Virtual Community has been created (Starkey A.J. 2006).Chapter 2. DesignProject AimsWith the success of the operate on out, the Client has asked for improvements to be made to the fantasy football feature of the website. For next seasons competition the Client would like the entrants to be able to register on-line. Th e Clients reasons for this argon numerous-To serve in the ease of entering the competitionTo save on postage for managers in disparate countriesTo gift one official route for applications, instead of entries approach in from different ways and therefore getting lost and misledTo allow alterations to be made by the entrant without contacting the ClientTo improve the quality of the website and to always bring the website forward with new and innovative ideasProject ObjectivesTo fulfil this take to and create the on-line fantasy football application I will have to meet some(prenominal) objectives.1. To enable the entrant to-Create a put onr name and passwordLog in with correct detailsView fantasy football rulesScroll through the imposters in different classes i.e. defence, midfield and forwardsPick and list their selected teamProcess their chosen team electronic mail their application to the germane(predicate) addressError messages to be given in these circumstances-Wrong log -in details are suppliedSelected team breaks any fantasy football rules comply the CSS guidelines set in the website structure, and to consider all HCI aspects throughout the design and implementation.To have the new system installed by 11Dec 2006.Project ConsiderationsDuring all aspects of designing and building this feature the following considerations will be taken into account-SuperstructureGraphicsColourContent readabilityPage LayoutLinksProject MethodologyThere were several possible methodologies to help with this project. The ones considered were-5 STEPS (Steps to Ensure Project Success) where it helps an individual deliver the project on time within budget. The focus is on growing a realistic schedule for a project and then managing it.AIS (Administrative Information System) which uses 7 structured components.PRINCE (Projects IN Controlled Environments) this was produced by the Central Computing and Telecommunications Agency (CCTA) for the increase and implementation of IS/IT projects.WebE Process WebApps are often delivered additively. That is, framework activities will occur repeatedly as each increment is engineered and delivered (Pressman RS 2005, p 507). apply the WebE Process represents an incremental design structure. The project is split up into increments to be tried and tested individually. This process model is adaptable to fit most tasks or implements.The one I have decided to go with is a methodology called PROMPT (Project Resource Organisation Management Planning Techniques) which although is the predecessor to PRINCE, it is the methodology more meet to my project than the others. PROMPT was knowing in an attempt to set down guidelines for a computer project to avoid serious over-running of time limits, which I feel is rattling in this project to keep me from falling behind. Even though the WebE process is specifically intentional for web applications our project is not incremental.The stage flow guidelines are as follows-Feas ibility Study to determine whether the project should be done/can be done/will work if it is done.Initial stage where the project organisation is set up.Specification Stage in which the user specification was detailed.Design Stage where the logical and from this the physical design of the computer system was designed in detail.Development Stage the system is built and tested.Installation stage the user accepts a working system.Operation Stage when the system is tuned for the work in hand.Interface designsThe overall design of the interface has to run along the same lines as the original website, while the log-in and selection pages can follow different routes. There are several different ways of approaching the interface. One option is a simple one click system where you click on a sham and it appears in your team. Another option, and the one which will be applied to the feature, is a drag and drop system. Both options are simple for the users to work but the drag and drop s ystem brings little extra to the process. It doesnt have to be just the name that is dragged it can be an icon. This will create a real manager feel to the program. Fig 2 shows an practice session of this drag and drop procedure. The icon being a impostors face.User CaseThe two use case diagrams show how the system will function. Diagram 1 shows how the Entrant will create his account, while Diagram 2 shows what option will be available to the registered manager.StoryboardStoryboarding not only improves your site navigation system but also helps design your website properly.Interface html/css design and layoutsThe majority of the pages in this theatrical role of the website will follow the same guidelines, with the slight exception of the team selection, seen below.Database DesignThere are several military personnels of information required on each player for the database. Each subject data needs to be sorted properly to aid in the running of the database. Normalisation is part of successful database design. Without normalisation, database systems can be inaccurate, slow and inefficient and they might not produce the data you expect (databasedev.co.uk). To enable us to follow the normalisation rules to need to find a piece of information that uniquely identifies that player. As team name, player name player position etc can quite easily be duplicate a player ID has been created for each player. The creation of this ID will be automatically created by the database software (mysql) so does not need to be of a concern. The information held an each player are as followsFieldExampleID1001Team NameArsenalPositionGoalkeeperPlayer NameLehmannCost7.5mFurther developmentsThe program has been designed so that any future enhancements that are required can be easily implemented. The program is reusable for the fantasy football competition every year. totally that needs to be changed each year is the player information. As the database doesnt carry very much data ther e is plenty of room for extensions or other ideas and new innovations. The program can in future be used for any other fantasy games the client has in mind for future events. coefficient of reflectionI found that the project, although not impossible to complete in the time limit, the ideas I had to solve the project objectives were over ambitious. The reasons for this soon became clearMy knowledge of PHP was not satisfactory at the start of the project to complete my ambitious objectives.The plan to keep to the main website theme, instead of aiding in the building of the fantasy football member made the project harder to complete. This was that I could not express myself for this project and therefore were limited in the way I could develop it.Considering this, the objectives and aims did not change as I feel that I quiet down completed them moderately. The problem was that the php was very basic in the whole. Although this doesnt help with the time limit available, I can still im prove this in the future as I improve my php knowledge. A good example of this is the team selection process. Diagram 6 shows one example of how I would have liked it to have been done.Chapter 3. Project TrackingProject RisksDue to the small size of this project, the hazards are few, although I have included a few extra. These need to be considered even though the probability is very low, as they applied to the original project and so also concern the menstruum one.Risk IdentityRisk ProbabilityRisk ImpactAssessment of riskRisk mitigation management1. BudgetUnlikelyImportant land and monthly web server costs exceed expectationskeep within budget where possible2. enrolmentPossibleImportantMismanagement of workload honour with schedule planed in the Gantt chart3. DesignUnlikelyMarginalUnable to design to specification and considerationsResearch thoroughly and seek aid if required4. executingPossibleMarginalSoftware and hardware problemsPrepare for this by having a second pc and al ternative software available5. PersonnelUnlikely well(p)Illness to myself that halts the procedureSeek extensions if requiredReflectionProject RisksAs already reflected on earlier, concerning the objectives that were unfulfilled this also comes under the project risk category. The risk identity here was schedule.Risk IdentityRisk ProbabilityRisk ImpactAssessment of riskRisk mitigation management2. SchedulePossibleImportantMismanagement of workloadKeep with schedule planed in the Gantt chartHere although it says that the assessment of the risk is Mismanagement of workload I would be inclined to say that it was Misinterpretation of expectationsProject MethodologyThe Project Proposal stated that the methodology WebE was going to be used. This was changed when it became clear that that Methodology wasnt completely suited for this project. The WebE is used for incremental applications, while the PROMPT although outdated was more suited this time.Chapter 4. TestingSoftware examination is fundamentally concerned with demonstrating that observed (actual) program conduct corresponds with specified (expected) program behaviour (Jorgensen. P. 2002). What this means is that you build your test conditions to match what the expected outcomes of the software are. The best way of doing is to split your software into manageable sections. This is called building block testing.This does not cover all the testing required, as our software needs to meet accessibility requirements and also pass a validation test. For all these and more we need to decide on a test strategy.Test StrategyThe test strategy will include four different types of testing as described below.Sight testingThis test will be used throughout the development and implementation of the website, and will be ongoing over niggling periods. This will spot simple errors before they become bigger.Usability testingThis will be used to test every aspect of the website as defined in the website considerations. The tests and results can be seen in the Test plan. The website will then be put through the W3c Mark-up Validation Service test.Accessibility testing Accessibility testing involves measuring the ease with which users with special needs can complete common tasks on your website. The tests and results can be seen in the Test plan.Acceptance testingThe Client will then be involved and asked to test all the features of the website to ensure that everything is designed to the clients expectations. This testing may result in further refinements.Usability TestingUsing the list from the project consideration, we will test the web site thoroughly. These tests will be completed using different computers, browsers and internet speeds.Below is the test plan, which gives a table of the tests that were carried out, their expected results and their actual results.Test PlanTest No.TestExpected ResultsActual ResultsSuperstructure1Is the site layout easy to understand?YesYes2Is the navigation around the site easyYesYes3Is the loading time quick and efficientYesYes4Is the site accessible to users with inferior hardwareYesYes5Is the site accessible to users with inferior softwareYesYes6is the site accessible for short-sighted peopleYesYesGraphics7 be they clear and attractiveYesYes8Are they necessaryYesYes9Do they contribute or just a distractionContributeContribute10Will they unjustifiable add to excessive loading timeNoYes11Consider alternatives for people with lower spec browsers and softwareYesYesColour12Is there an attractive mix of workYesYes13Do they add to the appearance of the siteYesYes14Do the colours follow web standardsYesYes15Have I considered colour sightlessnessYesYes, See Accessibility test.Content16Is the content interesting and of use to the userYesYes17Is the spelling correctYesYes18Is interaction possibleYesYesReadability19Are the pages readableYesYes20Does the site load correctly using different browsersYesNo See note 102Page Layout21Is each page in the site consis tentYesNo See note 10122Use of Cascading style sheetsYesYesLinks23Are the cerebrate easy to spotYesYes24Do they work correctlyYesYes25If they follow the links can they return easilyYesYes26Is there a site map, breadcrumbs or similarYes, exampleYes, Site mapProgram Registration27Accept names and usernameYesYes28Accept Correct E-mailYesYes29Incorrect E-mailErrorError30Passwords EncryptYesYes