Editing
Final Report 2010
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Project Management== ===Work Allocation and Structure=== To make the most efficient use of time the work load was initially broken into two different streams. This allowed us to work in parallel for a significant amount of the project. Working in parallel on the initial software components also allowed for much more efficient use of our time by bypassing the need for any serious version control. The actual tasks performed where almost identical to the following diagram with a small exception in producing the wild card pattern matching algorithm where both members of the group contributed. [[File:WorkloadBreakdown blockdiagram.jpg|250px|centre]] ===Schedule=== To keep track of the project schedule a Gantt chart was used. The project ran very close to the estimated schedule and there were no changes made to the Gantt chart throughout the project. As the exact due dates for the deliverables were not known at the start of the project, they are not shown correctly however all deliverables were met on time. [[Image:cipher_gantt.jpg|1200px|centre]] ===Risk Management=== The risks associated with the project were low because the project was majorly software based and there were no issues that arose. Since we did not need any hardware, the project was not impacted with any long term delays. The table below was developed to highlight some of the most likely risks that could have become an issue and their estimated impact levels on the project progression. <center> {| class="wikitable" border="1" |- ! Risk ! Probability ! Impact ! Comments |- | Project member falls sick | 4 | 6 | Could leave 1 member with a huge amount of work to complete |- | Unable to code pattern matching algorithm | 2 | 8 | Additional time might have to be spent, delaying the project |- | Unable to contact project supervisors | 2 | 6 | If it is at a critical time problems may arise |- | Crawlers not effective at parsing data | 3 | 5 | A different web crawler may have to be used, delaying the project |- | Run out of finance | 1 | 7 | Has the potential to be a problem if software needs to be purchased |- | Somebody else cracks the code | .009 | 5 | The project may lose its "x" factor but the web crawler will still be useful |} </center> ===Budget=== Once again, as the project was highly software based the expenses for the project were very low. Although the project had up to $500 available, there were very little expenses and the project fell under budget by a large amount. The total expenses for the project are: *The Secrets of Codes: Understanding the World of Hidden Messages by Paul Lunde - $50
Summary:
Please note that all contributions to Derek may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Derek:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information