17. Budget list
Main Budget £1,000
Software Budget
Office; Dreamweaver; Notepad; Web server software and URL
£250
Hardware Budget
Computer and small server
£500
HR Budget
Man hours
£250
Editor's Notes
Analyse was the next stage where I created did quality checks to help manage the project to make sure that the project met national standards; I looked at similar projects to see where they failed to help improve mine.
The next stage was to look at the database side of things and make sure that I could design the database and manage the security around the website. Here was where the DFD were planned and ERD were drawn up.
Investigation stage was a successful stage setting up a suitable project; here I was able to produce a direction for my project. The investigation stage was where I was offered three plan’s for the project.
The literature helped me move in a further direction by giving me the chance to research the background areas for the projects. This part of the assignment gave me the choice to develop my understanding on the three project choices.
The feasibility started off with a clear understanding of the three project where I created a scoring system to help choose the right project to achieve the grades. I also developed the literature review; to give me an understanding of more of the background for the assignment. I also looked into the languages which could be used distinguishing the difference between client side and server side. The final part of the feasability was to look at authorising the project and analysing it to see if it is actually do able.
Analyse was the next stage where I created did quality checks to help manage the project to make sure that the project met national standards; I looked at similar projects to see where they failed to help improve mine.
The next stage was to look at the database side of things and make sure that I could design the database and manage the security around the website. Here was where the DFD were planned and ERD were drawn up.
This section looked at planning for the actual creation of the website. I planned each page and what it would look like with the page sketches. Then I planned the way it would work with the storyboard and site map. This section was the most interesting as it was a simple task.
When actually creating the website I had to think about error handling which I did through the use of a form at the bottom of the website. The user is able to enter the details and send an e-mail to admin team. I also had to think of notifications so users using the site knew when something had happened. Every day I worked on the website I wrote it down in my log. This log was carried through out the project.
To start with when coding I was doing small tests to make sure things worked as I went along; I wrote this down on the continual test log. These test tested general things like the divs and making sure things were working as they were meant to. The end testing looked at details making sure there was no errors or minimal errors on the site at all.
This section I did a self evaluation made sure I wrote down what went well and how it went well but also what went wrong and how I worked to fix it. The User feedback was where I got two people to look at my website and give me feedback to see how well they thought it went.
Both me and the other users suggested where we could improve the website if it was done again. Then I reflected on their views and the entire project.
This section I wrote a maintenance report for the admin users to follow and help maintain the website after I hand the project over; the user guide is for the customers on how they are able to use the website and make sure they know how to use the website. There will also be a section on how to error handle the website and what to do if the error handling from the site doesn’t work.
So moving on further into this presentation there will be review of the project which I have just done then we will talk about the project as a whole a summary of the evaluation. Then the procedures which have been followed and the tools which have been used during the project.
The appendix’s have been part of the project I have used appendix’s to keep my word count down; these have been in the form of tools to help manage the time; help for the management of the overall project or reaching decisions and extra room when I have been restricted in certain area’s for the project.
The project as a whole was really enjoyable it felt like there was a process which had to be followed to reach a final target. The website is one of the best website I feel I have ever designed; the reason behind this is the use of a template. However I feel that the template caused some trouble when some of the div’s wouldn’t work and cause the website page to jump about a bit. The best part of the project for me was the database analysis stage giving me an understanding of database analysis and DFD how to move to different level’s; this will help me in the future. The worst part was making the code work; I spent a few hours trying to make sure the code was working correctly to find a simple spelling mistake had been causing an issue. If I was to do it again in the future I would improve the time management and work a lot harder in bigger chunks rather than small sprints; the reason for this I have tied myself up doing smaller stuff and having to rush the larger parts now. So defiantly time management can be improved.
The procedures followed to reach the final result was to make small sprint by doing sub task’s to reach the main task. The gantt chart helped me to reach this final goal. The plan was as close as I though it could be however I didn’t follow this much and fell behind a little. The resource list and budgets were set in the feasability task and helped me to understand how much It would cost me to do this project also the items I have to complete the task. The templates were another tool to help produce the final plan.