NFC INSTITUTE OF ENGINEERING AND TECHNOLOGY
Department of Computer Science
(Batch 2k21-2k25)
Outline for FYP report
Introductory Pages:
● Title Page
● Acknowledgements
I begin this project in the name of Allah the Wisest & All Knowing ….
Credit to the institute, head of department and supervisors….
● Undertaking
The requirement gathering & analysis, design and development of the
project have been conducted methodically with the work free of any
plagiarism by your teammates…
● FINAL YEAR PROJECT UNDERTAKING FORM
(to be attached at the end with signatures. Do not change the FORMAT)
● Abstract
8-12 Lines summary of your project
● Logo
Center aligned on a blank page
● Content Page
● List Of Figures
● List Of Tables
Note:
● The format for the introductory pages should be followed strictly. Title page
should be the same as the reference documents attached- center aligned
and same data format as per your project.
● Do not directly copy paste / plagiarise the above mentioned data from the
reference documents
Chapters
Note: Each chapter should start with a blank page consisting of the chapter name
and number only as per the reference documents.
● CHAPTER 1: INTRODUCTION
○ 1.1 Domain
■ Subdomain(if any)
○ 1.2 Problem Statement
(What is the major problem your project is solving, the problems and issues
in previous systems)
○ 1.3 Motivation
(The reason behind your projects creation)
○ 1.4 Definition of Terms
(the technical terminology used with their definitions. )
For example:
○ 1.5 Workflow
(MSproject gantt chart with timelines Image/Screenshot)
○ 1.6 Goal of Project
(bullet points with headings)
● CHAPTER 2: EXISTING SYSTEM
○ 2.1 Relative Work
(summary of the already existing systems)
○ 2.2 Existing Systems and their features
○ (in the form a table with their names and links with short description)
○ 2.3 Novelty
(whats new in your project)
○ 2.4 Solution Available in ___your project name__
○ 2.5 SRS
■ User Interfaces
(main interfaces for user interaction e.g admin portal)
■ Hardware Interfaces
(minimum hardware requirements)
■ Software Interfaces
For example
● Functional Requirements
(bullet points with headings and description)
○ Use Cases
○ Requirement Shells
● Non functional requirements
○ Requirement Shells
● CHAPTER 3: SOFTWARE PROCESS MODEL
○ 3.1 Software Process Model
○ 3.2 Proposed Model with diagram
(what model did you use -with diagram and why)
■ Reason
○ 3.3 Implementation of Agile Scrum
(With description in what did you achieve in each phase of the
model)
● CHAPTER 4: PROPOSED SYSTEM
○ 4.1 Need for the proposed system
○ 4.2 Features of Proposed System
(with subheadings and description)
○ 4.3 Business Context
(Your project with business point of view)
■ 4.3.1 Advantages in Business
■ 4.3.2 Stakeholder’s Profiles
● 4.3.3 Project Priorities
● 4.4 Operating Environment
● CHAPTER 5: SYSTEM DESIGN
○ 5.1 Brief Description
○ 5.2 UI/UX Design
(With images)
○ 5.3 ER Diagram
○ 5.4 DFD Diagram (Level0-Level2)
○ 5.5 Activity Diagram
○ 5.6 Class Diagram
○ 5.7 Sequence Diagram
○ 5.8 Software Architectural Design
● CHAPTER 6: DEVELOPMENT
○ 6.1 Selection of Tools & Technology
○ 6.1.1 Hardware (what did you use for development)
○ 6.1.2 Software (what did you use for development, IDEs, Tech stack)
● CHAPTER 7: SOFTWARE TESTING
○ 7.1 Software Testing ( in terms of your project and why was it imp)
○ 7.2 Testing Process (what was your testing process)
○ 7.3 Black Box Testing
○ 7.4 Test Cases (in the form of table)
● CHAPTER 8: IMPLEMENTATION AND TRAINING
○ 8.1 Implementation
○ 8.2 Project Overview
(Key Features only)
○ Expected Outcome
○ 8.3 Training
(what skillset is required to operate your software and how to train
users on them)
● Conclusion
(a 8-10 line paragraph concluding your project, features, benefits and how
it works)
● References
( For the research and resources you used in your project. With links)
Requirements: (to be read and followed carefully)
Follow these requirements even if any of the attached reference reports of the
prior students violate them.
● Do not plagiarise or copy data from any other reference document.
● Each heading and subheadings , descriptions and any other form of data
including but not limited to the tables, figures should be according to your
project.
● The format for all the diagrams mentioned in the above should be in the
correct format without extra colors or background grid. Use transparent
background pngs. For reference, read the UML document attached as a
reference. For requirement shells, the volere reference document is
attached.
● All the pages should be numbered starting from the chapters. The position
of page number should be in the bottom left corner.
● All the headings should be numbered and added in the content page
● The figures and tables should be followed by a subtitle of what it is and
should be listed with a number in the list of figures/tables.
● Use moderate and consistent margins throughout the document.
Font Requirements:
● The font for chapter’s title page should be 20pts
● Each Heading should be bold and 14px for the normal headings .
● Subheadings may have 12 px but should be bold
● The subtitles below figures and tables should be 11 px , dark grey and in
italics.
● Normal text should be 12 px.
● Avoid using any fancy font. All text should be in Times New Romans
Reference Documents:
[Link]
sp=sharing
(Reference1 is recommended to follow for the formatting except for the outlines)