Scribd
Upload
68 views3 pages

Project Guideline 2011

The document outlines the required format for project reports for MCA III commercial system projects and MCA-III technical projects. It specifies that commercial system project reports should follow a format including an introduction, proposed system, analysis and design, user manual, and annexures sections. The technical projects report format also includes these sections but specifies additional design diagrams and specifications that should be included, such as object diagrams, class diagrams, and interface diagrams. Both formats require blank title and ending pages, as well as sections on introduction, proposed system, analysis and design, user manual, and annexures.

Uploaded by

Abhishek Wakharkar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
68 views3 pages

Project Guideline 2011

The document outlines the required format for project reports for MCA III commercial system projects and MCA-III technical projects. It specifies that commercial system project reports should follow a format including an introduction, proposed system, analysis and design, user manual, and annexures sections. The technical projects report format also includes these sections but specifies additional design diagrams and specifications that should be included, such as object diagrams, class diagrams, and interface diagrams. Both formats require blank title and ending pages, as well as sections on introduction, proposed system, analysis and design, user manual, and annexures.

Uploaded by

Abhishek Wakharkar
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

MCA III ( COMMERCIAL SYSTEM PROJECTS )

Project Report should be submitted in following format for Commercial Application Projects viz. Payroll, Sales, Purchase, Inventory, Book Shop, Examination system etc. Where VB, Access, Oracle, ASP and Java is used. 2 Blank Pages at beginning Title Page Certificate from Company Certificate from Guide Acknowledgement Index with printed Page Numbers CHAPTER 1 : INTRODUCTION 1.1 Company Profile 1.2 Existing System and Need for System 1.3 Scope of Work 1.4 Operating Environment Hardware and Software CHAPTER 2 : PROPOSED SYSTEM 2.1 Proposed System 2.2 Objectives of System 2.3 User Requirements CHAPTER 3 : ANALYSIS & DESIGN 3.1 Data Flow Diagram (DFD) 3.2 Functional Decomposition Diagram (FDD) 3.3 Entity Relationship Diagram (ERD) 3.4 Data Dictionary 3.5 Table Design 3.6 Code Design 3.7 Menu Tree 3.8 Menu Screens 3.9 Input Screens 3.10 Report Formats 3.11 Test Procedures and Implementation CHAPTER 4 : USER MANUAL 4.1 User Manual 4.2 Operations Manual / Menu Explanation 4.3 Forms and Report Specifications Drawbacks and Limitations Proposed Enhancements Conclusions Bibliography ANNEXURES : ANNEXURE 1 : INPUT FORMS WITH DATA ANNEXURE 2 : OUTPUT REPORTS WITH DATA ANNEXURE 3 : SAMPLE CODE 2 Blank Pages at the end.

MCM-III SEM IV

*** TECHNICAL PROJECTS ******

Project report should be submitted in following format for project using OOAD, Embeded System, WAP and other technologies and Web Deployed Systems where C, C+ +, J2EE, .NET, OOAD and JAVA, SDKs, APIs are used. 2 Blank Pages at beginning Title Page Certificate from Company Certificate from Guide Acknowledgement Index with printed Page Numbers CHAPTER 1 : INTRODUCTION 1.1 Company Profile 1.2 Existing System and Need for System 1.3 Scope of Work 1.4 Operating Environment Hardware and Software 1.5 Detail Description of Technology Used CHAPTER 2 : PROPOSED SYSTEM 2.1 Proposed System 2.2 Objectives of System 2.3 User Requirements CHAPTER 3 : ANALYSIS & DESIGN 3.1 Object Diagram 3.2 Class Diagram 3.3 Use Case Diagrams 3.4 Module Hierarchy Diagram 3.5 Component Diagram 3.6 Deployment Diagram ( in case of Web Deployment ) 3.7 Module Specifications 3.8 Interface Diagram ( in case of WAP and Embedded Systems ) 3.9 Web Site Map Diagram ( in case of Web Site ) 3.10 User Interface Design ( Screens etc. ) 3.11 Table specifications ( in case back end is a database ) 3.12 Test Procedures and Implementation CHAPTER 4 : USER MANUAL 4.1 User Manual 4.2 Operations Manual / Menu Explanation 4.3 Program Specifications / Flow Charts Drawbacks and Limitations Proposed Enhancements Conclusions Bibliography ANNEXURES : ANNEXURE 1 : USER INTERFACE SCREENS ANNEXURE 2 : OUTPUT REPORTS WITH DATA ( if any ) ANNEXURE 3 : SAMPLE PROGRAM CODE ( which will prove sufficient development is done by the student ) 2 Blank Pages at the end.

You might also like