Results and Discussion : Mini Project

How to deal with Mini Projects?

Test Reports: Explain the test results and reports based on your test cases, which should show that your software is capable of facing any problematic situation and that it works fine in different conditions. Take the different sample inputs and show the outputs. 

User Documentation: Define the working of the software; explain its different functions, components with screen shots. The user document should provide all the details of your product in such a way that any user reading the manual, is able to understand the working and functionality of the document. 

Chapter 7: Conclusions

Conclusion:The conclusions can be summarised in a fairly short chapter (2 or 3 pages). This chapter brings together many of the points that you would have made in the other chapters. 

Limitations of the System: Explain the limitations you encounterd during the testing of your software that you were not ableto modify. List the criticisms you accepted during the demonstrations of your software. 

Future Scope of the Project describes two things: firstly, new areas of investigation prompted by developments in this project, and secondly, parts of the current work that were not completed due to time constraints and/or problems encountered. 

REFERENCES

It is very important that you acknowledge the work of others that you have used or 

adapted in your own work, or that provides the essential background or context to 

your project. The use of references is the standard way to do this. Please follow the 

given standard for the references for books, journals, and online material. 

GLOSSARY 

If you use any acronyms, abbreviations, symbols, or uncommon terms in the project 

report then their meaning should be explained where they first occur. If you go on to 

use any of them extensively then it is helpful to list them in this section and define the 

meaning.

APPENDICES 

These may be provided to include further details of results, mathematical derivations, 

certain illustrative parts of the programcode (e.g., class interfaces), user 

documentation etc.

In particular, if there are technical details of the work done that might be useful to 

others who wish to build on this work, but that are not sufficiently important to the 

project as a whole to justify being discussed inthe main body of the project, then they 

should be included as appendices.