GUIDELINES FOR WRITING PROJECT REPORT Certificate Acknowledgement Preface Abstract Contents Chapter-1 Introduction Introduction of the Project

t Objectives Literature Survey Over view of the Organization (not more than four pages) Chapter-2 Analysis Existing System Draw back of the Existing System Proposed System Proposed System Environment Project Planning & Project scheduling. SRS. Data model, Flow diagram & other similar models & Data Dictionary Chapter-3 Design

Program Structures Table Design / Data Structure Data integrity & Constraints, Procedural Design User interface Design (Input / Output Design)

Chapter-4 Coding Comments & Description Standardization of Coding Error handing, Parameter passing & Calling Chapter-5 Security Database or Data Security User and access rights Steps taken against hacking of system Chapter-6 Testing Test case design Test reports Debugging and code improvement Chapter-7 Conclusion and Future scope for further development

References

Project Planning

Cost and effort estimation is to be done with the help of functional point analysis. Project Scheduling : (i) Pert Chart Proper decomposition of Stages. (ii) Gantt Chart Time line structure and validity of chart. Software requirement specification documents (SRS) Use IEEE standards or any other international standard. Makes SRS with proper structure based on S.E. concepts Makes SRS in running text, no structure. ERD (i) (ii) OR Class diagram for projects which does not use any DBMS but developed in an object oriented programming Language. (i) Class diagram indicating hierarchies. OR For project which neither use any DBMS nor any object oriented programming language but new a procedural language. (i) System should be modular. (ii) Each module should control the functions of appropriate member of subordinate modules at the sent level. (iii) Module should be independent. (iv) Each module should perform one function. (v) Each module should be of reasonable size. OR Modelling diagrams consist of data models. DFD (i) All Data flow should be leveled and should have proper input and output. (ii) Relationship of dataflow to data dictionary. Context diagram, level 1, level 2. OR Any other Behavior model and / or state transition diagram Data Dictionary It should explain each entity and relationship in ER diagram and data flow in DFD. (i) Data element definitions. (ii) Data base schema with reference keys. OR Project which does not use any DBMS but developed in an object oriented programming language. (i) Data objects definition and description. (ii) Relationship between data objects. OR Details on various Data Structures used. Design Program Structure It should have the proper modularization of software and specification of each module. Schema Design and Normalized tables Normalize the table to minimum SNF. If any demand of Denormalization explain clearly the reasons. Proper symbol of attributes, entities and relationship. Relationship of ER diagram to SRS with strong association.

OR Program architecture and explanation an suitability of data structure used. Data Integrity and Constraints Explain the referential diagram. Define referential integrity with should include keys, alternate keys and other keys. OR Value constraints and ranges. Procedural Design Explain using flow charts / Pseudo code /PDL User interface design Coherence with data flow and processor, consistency of interface and naming convention. Coding Comments description Should have comments with functional description-input, output, total function calls to / from other function, function parameters, description of main variables, data type, logic description etc. Standardization of coding Naming convention of variables and functions Nested depth Naming constants Use of data structure and style Parameter passing and Calling Check the technique used for this purpose, how it optimize the coding Security For data base security Use of views Use of Revoke and grant For data security Proper encapsulation leading to secure data Use and Access rights Steps taken again having of system Testing Testing Case design Unit testing Integration testing System testing Black box Testing White base Testing Testing Reports Unit Testing Integration testing System Testing Black box testing White box testing Debugging and code improvement.