cryptography

Closed Posted Jan 4, 2007 Paid on delivery
Closed Paid on delivery

**This is an undergraduate desirtation.

Web Cryptography Demo: AES

****Description**The student will study a common cryptosystem and make a web site describing it for the general public. The site should include a detailed demo, showing every step of the algorithm in visual way. This will involve implementation of the cryptosystem, probably using server-side executables, and web publishing. The site should be as platform-independent as possible. The student can choose any suitable tools available at the department. The cryptosystem to be presented is AES. the project also requires a 10,000 word report.

**9.3** **Assessment Criteria for Project Viva** **

**In the viva the student conducted an excellent critical review of the completed work and highlighted the skills gained during the project. The student demonstrated an excellent appreciation of the difficulty and relevance of the work involved in the project. The student fully engaged in a mature and insightful discussion of the technical issues raised during the viva. Assessment Criteria for Project Viva

## Deliverables

* It should cover the objectives, methods and achievements of the project. It should conclude with a critical appraisal of your own work, and reflections of what you have learnt in the process.

* See the *Marking Criteria* for details of the assessment criteria for the report. In summary, marks will be awarded to reflect the technical presentation of your work - that is the English structure, grammar, layout and so on - and achievements and argumentation presented in the report.

* You should include code in your report in order to add clarity to the discussion in the text, or you need to show how different versions were produced. It will be different for everyone. For example, it would be sensible to show how a difficult algorithm was coded up but maybe not all the GUI code needs to go in it. You are **NOT** required to print out your code and include it all in an appendix. You **MUST** include all your code on the CD-Rom.

* You do **NOT** need to include a copy of your memorandum of agreement as an appendix. You do need to discuss in the report how you met your objectives and critically evaluate your achievements with respect to the aims noted in the memorandum.

**You need to attend to the details in the report**.

1. Make sure you have broken the material down into chapters, sections.

2. Make sure you have a caption below each diagram, graph or figure and table to say what they are.

3. Number sections, figures, tables and important equations so that you can cross-reference them.

4. Make sure that the material in each section fits together coherently and that the section titles etc are an accurate description of the content.

5. Make sure the spelling is correct.

6. Make sure that you proof read the report.

7. Make sure references are accurate, dates are correct, and so on.

8. Give your report to friends and colleagues for comment and constructive criticism.

**_9_** **_Marking Criteria_** **_9.1_** **_Assessment Criteria for Project Presentation_**

**0-39%**

: Project lacks clarity of overall objectives. Little technical work has been completed so far and the discussion of what is to be achieved during the remainder of the project was limited.

**40- 49%**

: Project lacks some clarity of overall objectives. Some limited technical knowledge appropriate for the chosen project topic had been gained so far. The student appropriately discussed during the viva what is to be achieved during the remainder of the project.

**50-59%**

: Project has clear objectives. During the viva the student demonstrated an appropriate technical awareness supported by some discussion of design issues. The student demonstrated an appreciation of the likely outcomes of the work.

**60-69%**

: Project has clear objectives. During the viva the student demonstrated an appropriate technical awareness supported by a comprehensive discussion of design issues. The student had an appreciation of the likely outcome of the work and how to validate it. The student has already made good progress towards achieving the project objectives.

**70-79%**

: Project has clear and challenging objectives. During the viva the student demonstrated good technical knowledge supported by an excellent discussion of design issues. The student had a good appreciation of the outcomes of the work and how to validate it. The student has already made good progress towards achieving the project objectives.

**80-100%**

: Project has clear and challenging objectives. During the viva the student demonstrated excellent technical knowledge at an imaginative level which was supported by an excellent discussion of design issues. The student had an excellent appreciation of the outcomes of the work and how to validate it. The student has already made significant progress towards achieving the project objectives.

_**9.2**_ _**Assessment Criteria for Project Report**_

**0-39%**

: Project contains serious errors and/or is poorly constructed. A project report in this band is characterised by complete lack of relevance to the topic and where there is little or no evidence of the student having studied at an appropriate level.

**40-49%**

: Project completed at a technical level but with little discussion of design issues or significant outcomes of the work. A project in this band makes an attempt to approach the topic but without fully understanding its implications. It may be characterised by insufficient or low quality implementation and theory.

**50-59%**

: Project completed at an appropriate technical level with some discussion of design issues and outcomes of the work. A project in this band should reflect the fact that the student has demonstrated an understanding of the project topic. This class is also appropriate where much of the content merits a higher mark but the implementation lacks thoroughness. A project report in this band may lack depth with a tendency to generalise in the discussion sections and may be unbalanced in presentation.

**60-69%**

: Project completed to a good technical level. A project report in this class should contain little or no irrelevant material and be generally well constructed. The report may contain a comprehensive discussion of design issues and outcome of the work compensating for some weakness in style or some incoherence of argument. Alternatively, the report may be well written and insightful even though the range of issues addressed is narrow.

**70-79%**

: Project completed to an excellent technical level. The report should be clear, consistent in style, and provide an excellent discussion of design issues and outcomes of the work. The report should also demonstrate an excellent knowledge of appropriate reference material, techniques, and relevant theoretical perspectives where appropriate. It is important to consider the full use of this band so that first class marks make their proper contribution to the final average.

**80-100%**

: Project completed to an excellent and imaginative technical level showing some element of originality. The project should have an excellent report (meeting the criteria from the 70-80% band). Furthermore, a mark of 80% or more should only be given for projects where the student has achieved one of the following:

* The achievement of the student would be a very good basis for continuing research in the area.

* The practical work is of such a high professional standard that it could be distributed without significant extra effort.

* The student has worked independently, exceeded expectations, and clearly demonstrated a very deep understanding of their results.

**All the material and arguments in a report should be presented in a way that makes their development clear to a computer scientist who is not a specialist in the project topic.**

**Any final grade falling just below a boundary should lead to a review of the major components (viva + report).**

:

## Platform

The site should be platform independent as possible. The web tutorial needs to have a php tag so it gets implemented on to the university webserver.

:

Engineering MySQL PHP Software Architecture Software Testing Web Hosting Website Management Website Testing

Project ID: #3973290

About the project

2 proposals Remote project Active Jan 25, 2007

2 freelancers are bidding on average $574 for this job

datapointvw

See private message.

$637.5 USD in 14 days
(5 Reviews)
1.3
SarfarazNaz

See private message.

$510 USD in 14 days
(0 Reviews)
0.0