Reference no: EM132289675 , Length: word count:10000

Assignment -

Background - The purpose of this project report is to provide a complete record of all the work carried out by you.

Learning Outcomes - After completing the project report task students should be able:

• To manage their time effectively so as to carry out their plan.
• To locate and make use of information relevant to their project.
• To evaluate in a critical fashion the work they have done, and to place it in the context of related work.
• To structure and write a dissertation describing their project.

Description of the Task - Your task is to produce the project report for your project. It is recommended that you follow this template for the title page of your dissertation.

The content of the project report is at your discretion, and will depend on the nature of the project, but for a typical project involving the development of a piece of software, the elements of the dissertation would be expected as described below.

Project report: Content and Structure

The content of the dissertation is at your discretion, and will depend on the nature of the project, but for a typical project involving the development of a piece of software, the following elements of the dissertation would be expected:

1. ABSTRACT - A one-page summary of the project as a whole. This MUST be included for all projects.

2. INTRODUCTION - This will give a brief overview of the project including What problem is addressed by the project? What are the aims and objectives of the project? What are the challenges of the project? What is the solution produced? How effective is the solution / how successful has the project been?

3. BACKGROUND - This will give all the background of the project including Background of the problem to be solved. Existing solutions/approaches to the problem, if any exist, and a comparison with the solution produced in the project. Reading and research done to understand existing approaches, acquire the necessary information and skills to carry out the project. A clear statement of the project requirements. References to all sources consulted are expected.

4. DATA REQUIRED - What data were needed for the project and where it was obtained from; ethical use of data, including use of human data & human participants: ethical use of data explicitly specify whether you used Synthetic data, or Real Non Human data explicitly confirm an ethical source of the data, confirm the University or a relevant Professional Body Ethical approval has been obtained for the use of the data in your project. Where applicable, include into appendix the University Ethical approval obtained by your 1st supervisor for the project on your behalf. Or Real Human data: explicitly confirm an ethical source of the data explicitly confirm that the University Policy on ethical use of human data has been followed: here is the flow chart for the University Ethical approval. Explicitly confirm that the University or a relevant Professional Body Ethical approval has been obtained for the use of the data in your project. where applicable, include into appendix the University Ethical approval obtained by your 1st supervisor for the project on your behalf be aware that only the following types of data do not require Research ethics approval: information freely available in the public domain; anonymised records and data sets that exist in the public domain ethical use of human participants (other then project 3rd party evaluation) explicitly state if human participants were involved in the project; if human participants were involved in the project, explicitly confirm that the University ethical procedure has been followed: here is the flow chart for the University Ethical approval; explicitly confirm that the University or a relevant Professional Body Ethical approval has been obtained for the use of human participants in your project; include into appendix human participants information sheet and consent forms completed and signed by the human participants on your project.

5. DESIGN: This will give a description of the design. The organisation of this section should be the same as for the design documentation, and full details of the design are required. Typically it will comprise a description of the anticipated components of the system and how they are to be organised; a description of data structures used by the system; algorithms to manipulate these data structures; a design of the intended interfaces. Depending on the project and approach used, the followings are expected (refer to the guideline of the design stage for details): Object-oriented design methodology: Use-case diagrams; An interaction chart; The objects to be used in the system; Attributes and methods of objects; Pseudo-code for the key methods; Interface design. Traditional design methodology: Data dictionaries; System boundary diagrams; Entity-relationship diagrams; Logical table structures; Physical table structures; Transaction matrix; Pseudo-code for the key methods; Interface design. Empirical investigation of hypothesis: in addition, the following is expected A statement of the hypotheses to be tested; A description of the test data to be used; An experiment design, the experiments to be performed, any control to be used; A description of how the results will be analysed, including any statistical techniques that will be used; Anticipated conclusions. Devising new algorithms: in addition, the following is expected A description of the approach used to solve the problem; A description of how the new algorithms will be analysed, including mathematical and experimental analysis. All design documentation, representing the final design used on the project should be supplied. Any modifications made to the design presented in the design documentation and presentation should be stated and justified.

It is often best to include the full details of the design as an appendix. In such a case, the design chapter in the main part of the project report should only discuss the most important elements of the design to your design report and state clearly what other elements will be given in the appendix. Keep in mind that examiners might not look at all the details of the material included in the appendices. So, make sure that the really important points of the design are explained here.

6. REALISATION - This will give a description of how the design was implemented and a description of the testing of the implementation. The following is expected: Description of how the design was implemented for each stage and each component of the system. Description of problems encountered during implementation and the solutions to these problems. Changes made to the design in the course of implementation and the justification.

Description of various testing of the implementation of each stage and each component of the system including test cases used, expected results, and actual results. Snapshot of code listing of key methods and a small number of screen shots may be included. However, typically, full code listings, detail screen shots, and test runs will appear as appendices. Again, keep in mind that examiners might not look at all the details of the material included in the appendices. So, make sure that the really important points of the implementation and testing are explained here. Typically, there are two cases of modifications as compared with the design stage: If the design has been revised since the design stage and the implementation now follows this revised design, the DESIGN section should present the revised design together with comments explaining and justifying the changes. If the design has not been revised since the design stage, but the implementation differs to a lesser or greater extent from that design, the DESIGN section would be pretty much identical to the original design documentation but the REALISATION section would explain the differences between design and implementation.

7. EVALUATION - This gives an evaluation of the project, including A description of how the project is evaluated, including What criteria are used to evaluate whether the system is successful? How these criteria are assessed? Who is involved in the evaluation? Your critical evaluation of your project results/outcomes. Your critical evaluation of the strengths and weaknesses of your project as carried out. Where appropriate, 3rd party evaluation of the software/computer system/application developed on the project, and/or customer feedback, be obtained in strict accordance with ethical use of the project 3rd party evaluation human participants explicitly state if human participants were involved for the project 3rd party evaluation; if human participants were involved for the project 3rd party evaluation, explicitly confirm that the CS Department ethical procedure for Comp39x projects 3rd party evaluation has been followed. Include into appendix the 3rd party evaluator information sheet and consent forms completed and signed by the 3rd party evaluators on your project.

8. LEARNING POINTS - At least one page of summary of the key learning points in the project.

9. PROFESSIONAL ISSUES - At least one page of discussion of how your project related to the codes of practice and conduct issued by the British Computer Society.

10. BIBLIOGRAPHY - A properly cited list of books, articles and other materials consulted during the project and/or referred to in the dissertation.

11. APPENDICES - Appendices are meant to contain detailed material, required for completeness, but which are too detailed to include in the main body of the text. Typically they should contain code listings, details of test data, screen shots of sample runs, a user guide, full design diagrams, instructions for unpacking and mounting any software included with the dissertation and similar material. A zip file containing the project archive material (including source codes, instructions on how to run the software, pictures used, etc.) should be submitted through the E-project system. If your system is available on-line, you should provide instructions of how to access the system via the internet.

The project topic is Indoor Navigation App, Attach the developed app because you will also need to write some pages about it e.g. problems faced, implementation, why this method was chosen, how the app works, or diagrams etc.

This is a short description of the project: With the increase in the student population at Liverpool a student may find themselves with a lecture or meeting anywhere across campus. Similarly, staff may find themselves in an unfamiliar location when delivering a lecture or presentation. In the event of an emergency, having knowledge of the layout of a building and the location of the best exit is essential and yet it is easy to be confused in an unfamiliar setting. This issue is even worse for students with a disability, who may, in the event of an emergency, require the use of support in order to leave a building safely. This project proposes the development of an iOS App that can potentially be consulted for information about any building on campus. The App would be able to suggest a route between locations within a building. Typically this would be the user's current location and the exit. The student will need to explore algorithms for route finding.

Instructions: Need 10000 words.

Attachment:- Assignment Files.rar