Guidelines for Project Report

Project Documentation should minimum of 40 pages, covering following points. 1. Project report should be neatly typed only on one side of the paper with 1.5 line spacing on an 4 si!e bond paper. ". #he margins should be$ %eft 1.&5'', right 1."5, top ( bottom 1.5). *. +efore ta,ing the final printout, the approval of the project coordinator is mandatory ( suggestions, if any, must be incorporated. 4. -very page must contain page number at center on bottom of page along with header ( footer on right side of top of page. 5. #e.t $font si!e/1" ,#imes new roman,1.5 line spacing ,justified, 0. sub heading/// 1" #imes new roman, +old &. Paragraph 1eadings /font si!e/14, #imes new roman, +old, underline ,left aligned,1" points above ( below spacing 2. chapter heading$ font si!e12, #imes new roman, +old, centre aligned,*0 points above ( below spacing 3. coding $font si!e 10,courier new 10. -very copy of the report must contain 4uter title page with embossing ( hard binding. 5ertificate of approval 65ertificate6 on letter head of college c,nowledgment Preface #able of 5ontents

Contents as given in following format.

4. Problem definition ( scope of project. 5. 7e8uirement analysis 0. -stimation ( planning &. Development tools9 operating environments 2. Designing 3. :mplementation 10. #esting 11. %imitation ( enhancements -ach student should submit 1 hard copy of project report to college, 1 hard copy for self reference and 1 soft copy in 5D ;properly labeled< to the college.

Abstract

=ynopsis, preferably, should be of about */4 pages. #he content should be as brief as is sufficient enough to e.plain the objective and implementation of the project that the students are going to ta,e up. #he students must adhere to the guidelines and should include the following in the given order. Topic of the Project: #his should be e.plicitly mentioned at the beginning of the =ynopsis. =ince the topic itself gives a peep into the project to be ta,en up, students are advised to be prudent on naming the project. #his being the overall impression of the future wor,, the topic should corroborate the wor,. Objective Aim !ision: #his should give a clear picture of the project. 4bjective should be clearly specified. Process "escription #ethodolog$ Adopted: #he development process of the entire proposed software system has to be stated in brief. =ummari!e the methodology that has to be adopted for the project development. #his may be supported by D>D6s 9 >lowcharts. Resources: #he re8uirement of the resources for designing and developing the proposed system must be given. #he resources have to be in the form of the hardware 9 software or the data from the industry. %imitations$ ll the possible limitations of the proposed system in terms of a bigger and comprehensive system must be included.

"uration$ =pecify the time duration ;in wee,s< which the project will ta,e to complete. References$ ?ention about the boo,, @7%'s or journals that students are going to refer for project in standard format.

"omain &nowledge
?ention the 4rgani!ation Profile :n detail e.plain the domain used which you are wor,ing ;eg. :f it is ban,ing e.plain the entire ban,ing operations< :nnovations and @sefulness A ;what new are you going to do here apart from the ones available in the mar,et< #echnologies needed to implement/mention each and every technology used here in detail ;along with the architecture and usefulness< Bew learning while developing the system ;software and 9 or domain< 4verview of the e.isting =ystem 5urrent =ystem 4verview >low of Data 5urrent >low of :nformation ; what are the reports currently, how are they developed where all they are delivered and how< ; should e.plain it diagrammatically< Proposed =ystem Proposed >low 4verall >unctionalityACou should mention the organi!ation hierarchyD the tiers of the system you are going to developD what is the hierarchy of your systemD ;in short the different levels of usage and what all is available to the various users< 4verall features of the current system %imitations of the current =ystem 1ow are you going to overcome the limitations

'(isting )$stem

Problem "efinition
Problem statements typically defining the domain of the problem.

description of the various entities and actors and how they interact with one another. Define the overall reason why you need this project in the first place. Describe the problem. #he problem statement must include$ o description of the decisions that must be made or the elements of the system that is to be adjusted. o #he criteria that measure how good your solutions are i. e., performance measurements to evaluate the system, the current level of performance, and the target levels to be achieved. #o the e.tent possible these measures should be 8uantitative.

o 5onstraints that limit the decisions or control actions that can be ta,en.

Re*uirement Anal$sis
-nsure that the business process is understood first. :dentify process steps. :dentify e.pected inputs, outcomes, measures, business rules. :dentify re8uirements in three types as o +usiness re8uirements o >unctional re8uirements o #echnical re8uirements :dentify functional and business re8uirements.

"esigning
>or Development Projects you need to follow any of the software development approaches with their phases. rchitecture Design$ -7D Design process Database Design o #ables schemas o #ables data Eueries Fraphical @ser :nterface

'stimation + planning

-stimation of si!e, cost and effort 5ost +enefit nalysis Fantt 5hart Project =cheduling 1ardware =oftware Platform @sed =creen shots and source code ?ajor ?odules =ecurity and Privacy #raining 7e8uirements Percentage of #esting Planned in your development Project Percentage of #esting done in your development Project

"evelopment tools operating environments

,mplementation

Testing

%imitation + enhancements

+rief about limitations of your project and discuss about future enhancement of the same.