‫| كلية الحوسبة والمعلوماتية‬

College of Computing and Informatics

College of Computing & Informatics (CCI)

SENIOR PROJECT-I REPORT

<Project Title>
Author(s):
Student Reg# Student Name
Student Reg# Student Name
Student Reg# Student Name
Student Reg# Student Name
Student Reg# Student Name
Student Reg# Student Name

Project Supervisor:
<Supervisor Name>

1
 ‫| كلية الحوسبة والمعلوماتية‬
College of Computing and Informatics

Topic of Project (28 Pts. Bold)

By: NAME OF PARTICIPTANT(s) (14 Pts. Normal)

Thesis/Project submitted to:

College of Computing & Informatics, Saudi Electronic University, Riyadh, Saudi Arabia.

In partial fulfillment of the requirements for the degree of:

BACHELOR OF SCIENCE IN INFORMATION TECHNOLOGY

Project Supervisor Project Committee Chair

2
ABSTRACT
Include a 2-3 paragraph brief about the project, its utility and your contribution. Also highlight
how the project has helped in your professional growth. It should briefly explain the problem and
why you need to solve it, what method did you use and what is the advantages of your proposed
method with reflection on the findings or results.
DEDICATION
This work is dedicated to…<names of people that have great impact on your success, with little
thank you note for each>
PREFACE
The preface content comes here. Make sure it is not more than one page. Preface should be used
to describe any special clarifications regarding project report. You may also include
acknowledgment paragraph in this section.
REVISION HISTORY
Name Date Reason For Changes Version

6
 TABLE OF CONTENTS

CHAPTER 1: INTRODUCTION............................................................................................7
1.1 Project Background/Overview:...........................................................................................7
1.2 Problem Description:...........................................................................................................7
1.3 Project Scope:......................................................................................................................7
1.4 Project Objectives:...............................................................................................................7
1.5 Project Structure/Plan:........................................................................................................7
CHAPTER 2: LITERATURE REVIEW..................................................................................8
CHAPTER 3: METHODOLOGY............................................................................................9
CHAPTER 4: SYSTEM ANALYSIS......................................................................................10
4.1 Product Features:..............................................................................................................10
4.2 Functional Requirements:..................................................................................................10
4.3 Nonfunctional Requirements.............................................................................................11
4.4 Analysis Models.................................................................................................................11
CHAPTER 5: SYSTEM DESIGN..........................................................................................12
CHAPTER 6: DISCUSSION & CONCLUSION....................................................................13
6.1 Discussion..........................................................................................................................13
6.2 Conclusion.........................................................................................................................13
REFERENCES.....................................................................................................................14
APPENDIX: Glossary...........................................................................................................15

7
CHAPTER 1: INTRODUCTION
The introduction should set the context for the project and should provide the reader with a summary of
the key things to look out for in the remainder of the report. When detailing the contributions it is helpful
to provide pointers to the section(s) of the report that provide the relevant technical details. The
introduction itself should be largely non-technical. It is useful to state the main objectives of the project as
part of the introduction. Should have the following headings:

1.1 Project Background/Overview:

1.2 Problem Description:

1.3 Project Scope:

1.4 Project Objectives:

1.5 Project Structure/Plan:

CHAPTER 2: LITERATURE REVIEW

Literature review is a systematic method of identifying, evaluating and interpreting the work (similar to
yours) produced by others. This chapter should set the project into context and give the proposed layout
for achieving the project goals. It is an important chapter especially if the project involves significant
amount of ground work. Review prior work critically, identify gaps in knowledge/areas of application and
build an argument for your own work. When referring to other pieces of work, cite the sources where they
are referred to or used, rather than just listing them at the end.

<Discuss and describe at least 25 literature resources relating to the project being carried out. At least
70% of resources cited must be from past 03 years. The resources can include peer reviewed journal and
conference papers, books, product manuals and product websites. All resources must be cited in text and
described in detail in section 1.6. The template to be used would be APA style. Newspaper articles are not
allowed to be cited.

8
CHAPTER 3: METHODOLOGY
<This section describes the methodology/approach selected for the project. In case of a research project
(in which the core outcome will be a research publication), explain the research methodology being
selected, and the rationale behind this selection. For software development projects (in which the core
outcome is a software application), explain the software development process being selected and rationale
behind this selection. >

9
CHAPTER 4: SYSTEM ANALYSIS

1.1 Product Features:

List and explain major product features to be developed in the section.

1.2 Functional Requirements:

All functional requirements (in relation with the production features identified in the section above) are
expressed as use-cases as well as analysis models and deign models are included in this chapter. Fill out
the following template for each use-case. Don’t really say “Use-Case 1.” State the use-case name in just a
few words e.g. “Withdraw Cash from ATM”. A use-case may have multiple alternate courses of action.
Use-Case 1

Identifier UC-1

Purpose …

Priority <Choose one from {High, Medium, Low}>

Pre-conditions …

Post-conditions …

10
 Typical Course of Action

S# Actor Action System Response

Alternate Course of Action

S# Actor Action System Response

1 Step 1 System Response 1

2 New response 1 Trigger 2

Use-Case 2 (and so on)

1.3 Nonfunctional Requirements

Performance Requirements
<If there are performance requirements for the product under various circumstances, state them here and
explain their rationale, to help the developers understand the intent and make suitable design choices.
Specify the timing relationships for real time systems. Make such requirements as specific as possible.
You may need to state performance requirements for individual functional requirements or features.>
Safety Requirements
<Specify those requirements that are concerned with possible loss, damage, or harm that could result from
the use of the product. Define any safeguards or actions that must be taken, as well as actions that must be
prevented. Refer to any external policies or regulations that state safety issues that affect the product’s
design or use. Define any safety certifications that must be satisfied.>
Security Requirements
<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect the
product. Define any security or privacy certifications that must be satisfied.>
Software Quality Attributes
11
<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness, flexibility,
interoperability, maintainability, portability, reliability, reusability, robustness, testability, and usability.
Write these to be specific, quantitative, and verifiable when possible. At the least, clarify the relative
preferences for various attributes, such as ease of use over ease of learning.>
Other Requirements (Optional)
<Define any other requirements not covered elsewhere in the SRS. These might include database
requirements, external (hardware, software, or communication) interface requirements,
internationalization requirements, legal requirements, and reuse objectives for the project.>

1.4 Analysis Models

<Include the following analysis models: use-case diagram>
Note: Every model should be described under separate level 03 heading and with brief description.

12
CHAPTER 5: SYSTEM DESIGN
< Include the following design model: component diagram, deployment diagram, design level sequence
diagram, complete class diagram, entity-relationship diagram.>

Note: Every model should be described under separate level 03 heading and with brief description.

13
CHAPTER 6: DISCUSSION & CONCLUSION
<The previous Chapters seem to focus mainly around the technical and implementation part of the
project. This chapter will aim in revisiting previous chapters (SPI) and express any changes leading to
improving the project development and execution. Also, to develop the student’s ability to express and
reflect his project to the wider academic audience.

Describe in 2-4 paragraphs the crux and importance of your project, its novelty and its current
applications. Also, within the same text suggest what future work can be derived out of your project>

1.5 Discussion

1.6 Conclusion

14
REFERENCES
<List all books, conference papers, journal articles, websites, etc. used in preparing the content of this
SRS. Provide enough information so that the reader could access a copy of each reference, including title,
author, volume/edition number, page number(s), and publication year. Mention complete URLs for
websites.>

15
APPENDIX: Glossary
<Define all the terms necessary to properly interpret the SRS, including acronyms and abbreviations. You
may wish to build a separate glossary that spans multiple projects or the entire organization, and just
include terms specific to a single project in each SRS.>

16