Final Report Format for UK Univ.
-
Hello :)Developers, Could anybody tell me the format for the Final Year Project...University said it should not exceed 60 pages. So I am creating a Software and i want to know what all details is necessary to include in Report. At any cost i want to get lot more than 2:1 in my Project. Software coding is going on fine but the main weightage is of Report i.e. 60% ...So please suggest me the correct and impressive way of doing that and scoring well. Thanks :) James.
-
Hello :)Developers, Could anybody tell me the format for the Final Year Project...University said it should not exceed 60 pages. So I am creating a Software and i want to know what all details is necessary to include in Report. At any cost i want to get lot more than 2:1 in my Project. Software coding is going on fine but the main weightage is of Report i.e. 60% ...So please suggest me the correct and impressive way of doing that and scoring well. Thanks :) James.
james_dixon_2008 wrote:
Could anybody tell me the format for the Final Year Project...University said it should not exceed 60 pages
Really - Mine was around ~100 pages in all. And, there isn't a specific format. Your university should be giving you guidance. As a general rule it will probably contain: * Table of Contents * Table of diagrams * Table of figures * The content * Bibliography and other references (This bit is probably important)
Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
-
Hello :)Developers, Could anybody tell me the format for the Final Year Project...University said it should not exceed 60 pages. So I am creating a Software and i want to know what all details is necessary to include in Report. At any cost i want to get lot more than 2:1 in my Project. Software coding is going on fine but the main weightage is of Report i.e. 60% ...So please suggest me the correct and impressive way of doing that and scoring well. Thanks :) James.
james_dixon_2008 wrote:
Software coding is going on fine but the main weightage is of Report
Just a thought - As it is the beginning of the academic year, I'm wondering why you are coding already. You should be at the design phase (and that is also an important part of the report).
Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
-
Hello :)Developers, Could anybody tell me the format for the Final Year Project...University said it should not exceed 60 pages. So I am creating a Software and i want to know what all details is necessary to include in Report. At any cost i want to get lot more than 2:1 in my Project. Software coding is going on fine but the main weightage is of Report i.e. 60% ...So please suggest me the correct and impressive way of doing that and scoring well. Thanks :) James.
Shouldn't your professor / academic advisor be able to tell you that? Taking a guess, you should include the following items: - A problem statement: With student projects, you are usually posed a problem; describe it. - Background material: 'Prior art' in the problem area. This is a short description of previous solutions to the problem, if there are any. Include information on their shortcomings or constraints. - Solution description: A description of your solution to the problem. This is more of an algorithm description, rather than a description of your code. Try to include information on where you think this solution improves on the prior art discussed in the background material. - Implementation details: This is where you can describe portions of your code. Note that this should be limited to the 'interesting' parts (those specifically related to the problem) and shouldn't include boilerplate, utilities, etc. If it's pertinent, describe your implementation environment (tools, operating system, etc.). - Test description: How did you verify your solution? Did it succeed or fail? List your test cases or procedure. - Conclusion: Summarize your conclusions about your solution to the problem. List any 'lessons learned' and opportunities for future efforts or research. - References.
Software Zen:
delete this; -
james_dixon_2008 wrote:
Software coding is going on fine but the main weightage is of Report
Just a thought - As it is the beginning of the academic year, I'm wondering why you are coding already. You should be at the design phase (and that is also an important part of the report).
Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
He may not be at the beginning of the academic year. When I was a senior, my schedule was totally screwed up due to curriculum changes. I took a special projects course in the fall, and then had to take a freshman chemistry course in the spring due to an accreditation change.
Software Zen:
delete this; -
Hello :)Developers, Could anybody tell me the format for the Final Year Project...University said it should not exceed 60 pages. So I am creating a Software and i want to know what all details is necessary to include in Report. At any cost i want to get lot more than 2:1 in my Project. Software coding is going on fine but the main weightage is of Report i.e. 60% ...So please suggest me the correct and impressive way of doing that and scoring well. Thanks :) James.
I thought there was a report on the End of The World. I was woried for a while.:-D
-
james_dixon_2008 wrote:
Software coding is going on fine but the main weightage is of Report
Just a thought - As it is the beginning of the academic year, I'm wondering why you are coding already. You should be at the design phase (and that is also an important part of the report).
Upcoming FREE developer events: * Glasgow: Agile in the Enterprise Vs. ISVs, db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
It is beginning of year.. No Doubt.. but i have started doing few modules. And also managing the design part for the final output at the moment. Later on it would be easy to sum it up under one roof....
-
Shouldn't your professor / academic advisor be able to tell you that? Taking a guess, you should include the following items: - A problem statement: With student projects, you are usually posed a problem; describe it. - Background material: 'Prior art' in the problem area. This is a short description of previous solutions to the problem, if there are any. Include information on their shortcomings or constraints. - Solution description: A description of your solution to the problem. This is more of an algorithm description, rather than a description of your code. Try to include information on where you think this solution improves on the prior art discussed in the background material. - Implementation details: This is where you can describe portions of your code. Note that this should be limited to the 'interesting' parts (those specifically related to the problem) and shouldn't include boilerplate, utilities, etc. If it's pertinent, describe your implementation environment (tools, operating system, etc.). - Test description: How did you verify your solution? Did it succeed or fail? List your test cases or procedure. - Conclusion: Summarize your conclusions about your solution to the problem. List any 'lessons learned' and opportunities for future efforts or research. - References.
Software Zen:
delete this;Great...Thanks for the info...:) Yeh Uni is starting in 2 weeks time and then i could ask them aswell..But its always better to know things before hand...
-
Great...Thanks for the info...:) Yeh Uni is starting in 2 weeks time and then i could ask them aswell..But its always better to know things before hand...
You're welcome, and good luck.
Software Zen:
delete this;