Scribd
Upload
69 views3 pages

Table of Contents

This document outlines the contents and structure of a project report for developing a new software system. It includes sections on problem definition and feasibility analysis, software requirements specification, system analysis of existing and proposed systems, system design considerations for inputs, outputs and screens, coding, testing and implementation, and conclusions and opportunities for future enhancements. The report will define the problem and need for the new system, specify functional and technical requirements, design the system, code and test it, then evaluate the results and quality of the new system.

Uploaded by

Manimala Selvam
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 DOCX, PDF, TXT or read online on Scribd
69 views3 pages

Table of Contents

This document outlines the contents and structure of a project report for developing a new software system. It includes sections on problem definition and feasibility analysis, software requirements specification, system analysis of existing and proposed systems, system design considerations for inputs, outputs and screens, coding, testing and implementation, and conclusions and opportunities for future enhancements. The report will define the problem and need for the new system, specify functional and technical requirements, design the system, code and test it, then evaluate the results and quality of the new system.

Uploaded by

Manimala Selvam
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 DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

TABLE OF CONTENTS TITLE ACKNOWLEDGEMENTS SYNOPSIS 1. INTRODUCTION 1.1 About the Organization 1.2 About the Project 1.

3 Plan of the report 2. PROBLEM DEFINITION AND FEASIBILITY ANALYSIS 2.1 Introduction 2.2 Problem Definition 2.3 Feasibility Analysis 2.3.1 Operational Feasibility 2.3.2 Technical Feasibility 2.3.3 Economical Feasibility 3. SOFTWARE REQUIREMENTS SPECIFICATION 3.1 Introduction 3.1.1 Purpose 3.1.2 Overview 3.1.3 Defintions, Acronyms and Abbreviations 3.2 Product Perspective 3.3 Assumprions and Dependencies 3.4Specific Requirments 3.4.1 Functional Requirements 3.4.2 Client side Functions 3.4.3 Administrator side Function 3.4.4 Hardware Recommended 3.4.5 Software Recommended PAGE NO

4. SYSTEM ANALYSIS 4.1 Introduction 4.2 Existing System 4.3 Proposed System 4.4 System Requirements Specifications 5. System Design 5.1 Introduction 5.1.1 Purpose 5.1.2 Scope 5.2 Input Design 5.2.1 Effectiveness 5.2.2 Accuracy 5.2.3 Ease of use ` 5.3 output Design 5.3.1 Objectives for Output Design 5.4 Screen Output design 6. CODING, TESTING AND IMPLEMENTATION 6.1 Coding 6.2 Testing 6.2.1 Test Plan 6.2.2 Types of testing 6.3 Results and evaluation 6.3.1 Adequacy and Coverage 6.3.2 Efficiency and Effectiveness 6.3.3 Productiveness 6.3.4 Elegance and User-Friendliness 6.3.5 Quality assurance 6.3.6 Critical evalution

7.CONCLUSION AND FUTURE ENHANCEMENTS 7.1 Conclusion 7.2 Future Enhancement

BIBLIOGRAPHY APPENDIX A APPENDIX B

You might also like