St Josephs College of Engineering, Chennai

Department of Computer Science and Engineering Guidelines for project work

First Review Scope:

1. 2. 3. 4. 5. To study about the existing system Problem Identification Describe the functional modules of the project work Analysis of each functional module(apply any modeling technique) Identify the performance evaluation metric for each module

Output: A report in the prescribed format and PPT presentation

Report format:
1. Student name Reg No: 2. Supervisor name Joint Supervisor name with address (if any) 3. Title of the Project 4. Problem Statement 5. Related work 6. Proposed system 7. Literature survey 8. Modeling for System Analysis 9. List of Reference Signature of the Student Signature of the Supervisor(s)

Slide Content:
1. 2. 3. 4. 5. 6. Slide 1 - Project Title, Student name with register number, name of the guide (1) Slide 2 - Objective (1) Slide 3 - Existing system (2) Slide 5 - Problem Identified (1) Slide 6 - Proposed solution (1) Slide 7 - Literature survey (min. of 2 slides and you should be survey min. of 10 papers related to your project 7. Slide 9 - System Analysis (minimum of 5) 8. Slide 14 Conclusion 9. Slide 15 References with hyperlink (arranged in alphabetical order)

St Josephs College of Engineering, Chennai

Department of Computer Science and Engineering Guidelines for project work

Second Review Scope:

1. 2. 3. 4. 5. Problem Description Design the Overall Architecture Designing each functional module Algorithm/procedure for each functional module implementation Test Plan for each module

Output: A report in the prescribed format and PPT presentation

Report format:
1. Student name Reg No: 2. Supervisor name Joint Supervisor name with address (if any) 3. Title of the Project 4. Problem Statement 5. Architecture Design 6. Functional module design 7. Methodology for each functional modules 8. Test plan for each functional modules 9. List of Reference Signature of the Student Signature of the Supervisor(s)

Slide Content:
(Maximum of 25 slides) 1. 2. 3. 4. 5. 6. 7. 8. 9. Project Title, Student name with register number, name of the guide Objective Proposed system Architectural Design Functional Modules Design(max .of 10 slides) Algorithmic/ Mathematical Design for each module Testing plan for each module Conclusion Reference with hyperlink

St Josephs College of Engineering, Chennai

Department of Computer Science and Engineering Guidelines for project work

Attendance sheet Date Topics discussed Signature of the Supervisor

St Josephs College of Engineering, Chennai

Department of Computer Science and Engineering Guidelines for project work

Standard Report Format

Introductory Pages Before the chapters of your report, there should be a number of introductory pages. These should include:

the title page (cover and first page) Bonafide certificate page an acknowledgements page a table of contents. List of abbreviations List of tables (annexure I) List of figures (annexure II) a page giving an abstract of your work,

1. Introduction This should briefly describe the problem which you set out to solve and should essentially summarize the rest of your report. The aim of an introduction is to convince the reader that they should read on, so it is very important that excessive detail is avoided at this stage. The introduction should include the list of objectives for the project that you identified, and brief overview of the outcome. In its final part the introduction will usually outline the structure of the rest of the report. 2. Related Work You should survey and critically evaluate other work which you have read or otherwise considered in the general area of the project topic. The aim here is to place your project work in the context of the related work. 3. Problem Description and Specification Describe in detail, with examples if appropriate, the problem which you are trying to solve. You should clearly and concisely specify the problem and should say how the specification was arrived at. You should also provide a general discussion of your approach to solving the project problem. As part of this chapter - or more likely in a related appendix - you should also normally include the original plan which was submitted as part of your Project Specification & Plan deliverable in the first

St Josephs College of Engineering, Chennai

Department of Computer Science and Engineering Guidelines for project work

semester, although you should not be particularly concerned if your project deviated from this plan somewhat.

4. System Design In this chapter, you should describe how the project was designed, including the design method, design process and final design outcome. This is where you include the high level description of the architecture of your project's product, and if appropriate the design of the user interface and data management. 5. Detailed Design / Implementation Explain your design in more detail, taking the most interesting aspects right down to the implementation details. You should include detailed design decisions and trade-offs made, such as the selection of algorithms, data structures, implementation languages and appropriate tools to support the development process, together with justifications for these choices. You should also describe how you have tried to address relevant qualities of the product produced, such as maintainability, reliability, user-friendliness. It is not necessary to describe all aspects of your system in detail, but you should describe the most demanding aspect or aspects of your design and implementation. 6. Verification and Validation Outline the verification and validation procedures that you have adopted throughout the project to ensure that the final product satisfies its specification. In particular, you should outline the test procedures that you adopted during and after implementation: your aim is to convince the reader that the product has been thoroughly and appropriately verified. Detailed test results should of course form a separate appendix at the end of the report. 7. Results and Evaluation The aim of this chapter is twofold. On one hand, it aims to present the final outcome of the project, i.e. the system developed, in an appropriate way so that readers of the report can form a clear picture of the system operation and provided functionality without the need for a live demo. This would normally require the inclusion of screenshots and/or images of the system in operation, and indicative results generated by the system.

St Josephs College of Engineering, Chennai

Department of Computer Science and Engineering Guidelines for project work

On the other hand, this chapter also aims to present an appropriate evaluation of the project as whole, both in terms of the outcome and the process followed. The evaluation of the outcome is expected to be primarily evidence-based, i.e. the result of either an experimental process, like usability tests and evaluations, performance-related measurements, etc, or a formal analysis, like algorithmic and mathematical analysis of system properties, etc. The precise nature of the evaluation will depend on the project requirements. The evaluation of the process is expected to be primarily a reflective examination of the planning, organisation, implementation and evaluation of the project, normally including the lessons learnt, and an explanation of any significant deviations from the original plan. 8. Summary and Conclusions In the final chapter of your report, you should summarise how successful you were in achieving the original project objectives, what problems arose in the course of the project which could not be readily solved in the time available, and how your work could be developed in future to enhance its utility. Be a bit upbeat, especially if you are pleased with what you have achieved! Appendix 1 - References This should be a list of papers and books referred to in the body of your report; most text- and wordprocessors provide useful assistance with referencing, for example latex uses bibtex. As you know, there are two principal reference schemes. In one, the list is ordered alphabetically on author's surname and within the text references take the form (Surname, Date). For example, a reference to work by McGettrick would be written (McGettrick, 1998). In the other, the list is ordered in the sequence in which a reference first appears in the report. For both schemes, each reference in the reference list should contain the following information: Author, Date, Title, Journal or Publisher (if book), Volume and Part. For examples of the first style, see the way in which references are laid out in "Software Engineering: A Practitioner's Approach" by Roger Pressman. Appendix 2 - Detailed Specification and Design Details of project specification and design relegated to an appendix. Appendix 3 - Detailed Test Strategy and Test Cases

St Josephs College of Engineering, Chennai

Department of Computer Science and Engineering Guidelines for project work

Details of test strategy with test results tabulated and commented. Appendix 4 - User Guide You should provide a detailed description of how to use your system; in some cases, it may also be appropriate to include a second guide dealing with maintenance and updating issues. Appendix 5 - Program Listing A full program listing should be provided in a CD accompanying both copies of the report.

ANNEXURE-I List of Tables Table no. 1.1 1.2 2.1 2.2 Description of Tables Page no.

Note: the first number indicates the Chapter number and the second number after the dot refers the number of the tables in that chapter. ANNEXURE-II List of Figures Figure no. 1.1 1.2 2.1 2.2 Description of figure Page no.

Note: the first number indicates the Chapter number and the second number after the dot refers the number of the figures in that chapter