0% found this document useful (0 votes)
2 views

FYP Documentaion Sample

This document outlines the thesis submission process for students in the Bachelor of Science in Information Technology program at Government College University, Faisalabad. It includes sections for declarations, certifications by the supervisory committee, acknowledgments, a table of contents, and detailed chapters covering software requirements, analysis, project design, implementation, system testing, user interfaces, and code implementation. The document serves as a formal record of the students' work and adherence to academic standards.

Uploaded by

shahzaibch70007
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
0% found this document useful (0 votes)
2 views

FYP Documentaion Sample

This document outlines the thesis submission process for students in the Bachelor of Science in Information Technology program at Government College University, Faisalabad. It includes sections for declarations, certifications by the supervisory committee, acknowledgments, a table of contents, and detailed chapters covering software requirements, analysis, project design, implementation, system testing, user interfaces, and code implementation. The document serves as a formal record of the students' work and adherence to academic standards.

Uploaded by

shahzaibch70007
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/ 20

TITLE OF THESIS (FONT SIZE 16 (NOT BOLD)

By

Student Name

(Reg. #)

Student Name

(Reg. #)

BACHOLAR OF SCIENCE
IN
INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY


GOVERNMENT COLLEGE UNIVERSITY, FAISALABAD.
June 2024
DECLARATION

The work reported in this documentation was carried out by me/us under the supervision
of [Supervisor Name] Department of Information Technology Government College
University, Faisalabad, Pakistan.
I/We hereby declare that the title of project [Project Title] and the contents of the
documentation are the product of my own work and no part has been copied from any
published source (except the references, standard mathematical or genetic models
/equations /formulas/protocols etc.) I/we further declare that this work has not been
submitted for award of any other degree /diploma. The University may take action if the
information provided is found inaccurate at any stage.

Signature of the Student


[Student Name]
2020-GCUF-xxxxx

Signature of the Student


[Student Name]
2020-GCUF-xxxxx

ii
CERTIFICATE BY SUPERVISORY COMMITTEE

We certify that the contents and form of documentation submitted by Mr. Muhammad
Awais Akram Registration No: 2020-GCUF-05215 and by Mr. ATIF AZHAR
Registration No: 2020-GCUF-09355. Has been Found satisfactory and in accordance with
the prescribed format. We recommend it to be processed for the evaluation by the
External Examiner for the award of Degree.

Signature of Supervisor …………………….


Name.……………………………………….
Designation with stamp…………………….

Member of Supervisory Committee


Signature ……………………………………
Name.………………………………….........
Designation with stamp…………………......

Member of Supervisory Committee


Signature ……………………………………
Name.………………………………….........
Designation with stamp…………………......
Chairperson

Signature ……………………………………
Name.………………………………….........
Designation with stamp…………………......

iii
DEDICATED

TO

Write at least one paragraph for dedication Here

iv
ACKNOWLEDGEMENTS
All praise to ALMIGHTY ALLAH, the most merciful and the most compassionate and
his Holy Prophet ‘MUHAMMAD’(Peace) be upon him) the most perfect and exalted
among and even born on the surface of earth, who is, forever a torch of guidance and
knowledge for the humanity as a whole.

[Name of Student 1]

[Name of Student 2]

v
TABLE OF CONTENTS
1. Software requirement specification..............................................................................1
1.1 Introduction.........................................................................................................1

1.2 Stakeholders.........................................................................................................1

1.3 Users of the System..............................................................................................1

1.4 Functional Requirements....................................................................................1

1.4.1 List of Functional Requirements....................................................................1

1.4.2 Description of each requirement in Requirement Shell.................................1

1.5 Non Functional Requirements............................................................................1

1.6 Schedule of the Project........................................................................................1

2. Analysis........................................................................................................................2
2.1 Use Case Model....................................................................................................2

2.1.1 Description Of Each Use Case.......................................................................2

2.2 System Sequence Diagram (SSD) of each use case...........................................2

2.3 Domain Model......................................................................................................2

3. Project Desing..............................................................................................................3
3.1 Introduction.........................................................................................................4

3.2 Design Class Diagram.........................................................................................4

3.3 Entity Relationship diagram..............................................................................4

3.4 Sequence Diagram...............................................................................................4

4. implementaion..............................................................................................................7
4.1 Code/Algorithm of Main scenarios and Main units of systems.......................7

5. System testing..............................................................................................................8
5.1 Test Case Template.............................................................................................8

6. User Interfaces..............................................................................................................9
7. Code IMPLEMENTATION.......................................................................................10

vi
vii
LIST OF FIGURES

Figure 1: Agile Model..........................................................................................................1


Figure 2: Data Flow Diagram..............................................................................................4

viii
LIST OF TABLES

Table 1: Manage Users.........................................................................................................5


Table 2: Add caption............................................................................................................6

ix
ABSTRACT

x
CHAPTER 1

1. SOFTWARE REQUIREMENT SPECIFICATION

Write one paragraph.

1.1 Introduction

Write few paragraphs related to Introduction.

1.2 Stakeholders

Write few paragraphs related to stakeholders.

1.3 Users of the System

Write few paragraphs related to Users of the system.

1.4 Functional Requirements

1.4.1 List of Functional Requirements


1.4.2 Description of each requirement in Requirement Shell

1.5 Non Functional Requirements

1.6 Schedule of the Project

Figure 1: Agile Model

1
CHAPTER 2

2. ANALYSIS

This chapter is about the

1.7 Use Case Model

The traditional

1.7.1 Description Of Each Use Case

The

1.8 System Sequence Diagram (SSD) of each use case


1.9 Domain Model

2
CHAPTER 3

3. PROJECT DESING

This chapter include the project design

3
1.10 Introduction

1.11 Design Class Diagram

1.12 Entity Relationship diagram

1.13 Sequence Diagram

Figure 2: Data Flow Diagram

4
Requirement Name: Manage Users

Table 1: Manage Users

Requirement #: Req01 Requirement Type: Functional

This requirement enables users to manage users of the system. Admin can
Description: add new users, delete old users and update users info.

To manage users
Rationale:

Administrator of the system


Originator:

User is added in the system. And database is updated.


Fit Criterion: User is deleted and

Customer 5 Customer 10
Satisfaction: Dissatisfaction:

Priority: 3 Conflicts: Nil

Supporting NA
Materials:

History:

5
(Sample of Fully dressed Format of Use Case)

Use Case Name: Name of the use case (Ref. ………..)

Table 2: Add caption


UC # Ref: Req. #

UC Name

Level (Abstract or Detailed)

Description

Actor (s)

Stakeholders

Preconditions

Success Guarantee

Main Success Action Response


Scenario
1.

2.

Extensions

Special requirements

Frequency of
Occurrence

Miscellaneous

6
CHAPTER 4

4. IMPLEMENTAION

Add details of implementation

1.14 Code/Algorithm of Main scenarios and Main units of systems

7
Chapter 5

5. SYSTEM TESTING

1.15 Test Case Template


Test Case #: Test Case Name:
System: Sub System:
Designed By: Design Date:
Executed By: Execution Date:
Short Description:

Pre-Condition:

Operating System: Environment:


Software Tools &
Technologies with
version
Steps Strategy Action Input Actual Expected Status Remarks
(Test-to- Result / Result/ (Pass/Fail)
Pass) / System Expected
(Test-to- Response System
Fail) Response
(T-T-P)
Or (T-
T-F)

Comments -----------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------

8
Chapter 6

6. USER INTERFACES

9
Chapter 7

7. CODE IMPLEMENTATION
Code not more than 3 pages.

10

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy