Scribd
Upload
3 views3 pages

Project Report Layout for Industry Projects-Testing & ERP

The document outlines the requirements for a project report on Testing, ERP Implementation & Services for MCA IV Semester, specifying that it should be 150 to 250 pages long and focused on the specific project rather than generic theories. It includes detailed sections such as system analysis, design, testing, and maintenance, along with necessary documentation like student declaration and company certificates. The report must adhere to formatting guidelines, including single line spacing, page numbering, and inclusion of tables and figures.

Uploaded by

divyachauhan8500
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views3 pages

Project Report Layout for Industry Projects-Testing & ERP

The document outlines the requirements for a project report on Testing, ERP Implementation & Services for MCA IV Semester, specifying that it should be 150 to 250 pages long and focused on the specific project rather than generic theories. It includes detailed sections such as system analysis, design, testing, and maintenance, along with necessary documentation like student declaration and company certificates. The report must adhere to formatting guidelines, including single line spacing, page numbering, and inclusion of tables and figures.

Uploaded by

divyachauhan8500
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Concept Note for MCA IV Semester

Project Category (Testing, ERP Implementation & Services)

Title: Project report on Testing, ERP Implementation & Services

The project documentation may be about 150 to 250 pages. The project documentation details
should not be too generic in nature. Appropriate project report documentation should be done,
like, how you have done the analysis, design, coding, use of testing techniques/strategies, etc., in
respect of your project. To be more specific, whatever the theory in respect of these topics is
available in the reference books should be avoided as far as possible. The project documentation
should be in respect of your project only. The project report should normally be printed with
single line spacing on A4 paper (one side only). All the pages, tables and figures must be
numbered. Tables and figures should contain titles.

The project documentation should include the topics given below.

Table of Contents with page numbering

Student Declaration

Certificate issued by the company where project were carried out

About Company

Objectives of Project

List of Abbreviations used

List of Figures

List of Tables

Chapter-1

System Analysis

Identification of Need

Preliminary Investigation

Feasibility Study

Project Planning

Project Scheduling (PERT Chart and Gantt Chart both)

Project Estimation Model


Software requirement specifications (SRS)

Software Engineering Paradigm applied

Data models (like DFD), Control Flow diagrams, State Diagrams/Sequence diagrams, Entity
Relationship Model, Class Diagrams/CRC Models/Collaboration Diagrams/Use-case
Diagrams/Activity Diagrams depending upon your project requirements

Chapter-2

System Design

Modularisation details

Data integrity and constraints

Database design, Procedural Design/Object Oriented Design

User Interface Design

Test Cases (Unit Test Cases and System Test Cases)

Chapter-3

Testing

Testing techniques and Testing strategies used

Testing Plan used

Test Cases

Test reports for Unit Test Cases and System Test Cases

Debugging and Code improvement

Chapter-4

Reports (sample layouts should be placed with brief explaination)

Chapter-5

Software Maintenance

Chapter-6

Future scope and further enhancement of the Project

Conclusion
Bibliography

Appendices (if any)

Glossary

You might also like