Scribd
Upload
75 views2 pages

Annex-IV - ContentFormat For FYP Report 2017

This document outlines the standard format for final year project reports for computer science degrees, including sections for introduction, requirements analysis, software design, project management, implementation, testing, and conclusion. It specifies the typical preliminary pages and chapter structure, with emphasis on introduction, requirements analysis, software design, and testing sections. Supervisors may suggest modifications to the given report format.

Uploaded by

Engr. Madeeha Saeed
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
75 views2 pages

Annex-IV - ContentFormat For FYP Report 2017

This document outlines the standard format for final year project reports for computer science degrees, including sections for introduction, requirements analysis, software design, project management, implementation, testing, and conclusion. It specifies the typical preliminary pages and chapter structure, with emphasis on introduction, requirements analysis, software design, and testing sections. Supervisors may suggest modifications to the given report format.

Uploaded by

Engr. Madeeha Saeed
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/ 2

Format for FYP Report (BSCS-BSIT-MIT-MCS)

Please Note: - Following is the generic format for the FYP documentation.
Supervisor and project evaluators may suggest modifications to the given report
format.

The preliminary/prefatory pages may appear in the order given below:


• Title Page
• Title Page2 with degree requirement
• DEDICATION
• PROJECT IN BRIEF
• ACKNOWLEDGEMENT
•DECLARATION
•CERTIFICATION
•ABSTRACT (250-300 WORDS)

• TABLE OF CONTENTS
• LIST OF ABBREVIATIONS (WHERE APPLICABLE)
• LIST OF FIGURES (WHERE APPLICABLE)
• LIST OF TABLES (WHERE APPLICABLE)

1. INTRODUCTION
1.1. Project Overview
1.2. Project Aims
1.3. Project objectives
1.4. Project Scope
1.5. Problem Statement
1.6. Proposed Solution
1.7. Proposed System Components
1.8. Proposed System Output
1.9. Methodology And Software Lifecycle For This Project
1.10. Introduction to tools and technology used
1.11. Deliverables And Development Requirements
1.12. Project Background / Literature Review
1.13. Critical Analysis From Project Background /Literature Review
1.14. Chapter Summary
2. REQUIREMENT ANALYSIS
2.1. Project Description
2.2. Functional Requirements
2.3. Non-Functional Requirements
2.3.1. Usability
2.3.2. Reliability
2.3.3. Integrity
2.3.4. Performance
2.4. External Interface requirements
2.5. Performance requirements
2.6. Chapter Summary
3. SOFTWARE DESIGN
3.1. Use Cases (Fully Dressed)
3.2. Use Case Diagram
3.3. ERD
3.4. Normalization
3.5. Class Diagrams
3.6. Sequence Diagrams
3.7. Activity Diagrams
3.8. Collaboration Diagrams
3.9. Component Diagrams
3.10. Deployment Diagrams
3.11. Data Dictionary
3.12. Chapter Summary
4. PROJECT MANAGEMENT
4.1. Milestones
4.2. Project closeout report
4.3. Operation and management plan
4.4. Project Resources
4.5. Risk Analysis
4.6. Risk Response
4.7. Chapter Summary
5. PROJECT IMPLEMENTATION
5.1. Programming Language
5.2. Framework
5.3. System Requirement
5.4. Chapter Summary
6. SOFTWARE TESTING
6.1. Deriving Test
6.2. Test Environment
6.3. Testing identification
6.4. Test Procedure
6.5. Testing techniques
6.6. Chapter Summary
6.7. Test Cases
6.8. Chapter Summary
7. CONCLUSION AND FUTURE WORK
7.1. Discussion
7.2. Conclusion
7.3. Limitations
7.4. Future work

REFERENCES (in IEEE Format)


APPENDICES (where applicable)
USER GUIDE (where applicable)
--------------------------------------------------------------------------------------------------------
Note: Need more focus on the topics in bold.

You might also like