Department of Computer Engineering Bilkent University

Senior Design Project

Project short-name: project title

Analysis Report

Project Group Member Name, Project Group Member Name …

Supervisor: Supervisor Name

Jury Members: Jury Member Name and Jury Member Name

…. Report
May 3, 2020

This report is submitted to the Department of Computer Engineering of Bilkent University in partial fulfillment of the requirements of the Senior Design Project course CS491/2.

Contents

1	Introduction	3

2	Current System	3

3	Proposed System	3

3.1	Overview	3

3.2	Functional Requirements	3

3.3	Non-functional Requirements	4

3.4	Pseudo Requirements	4

3.5	System Models	4

3.5.1	Scenarious	4

3.5.2	Use-Case Model	4

3.5.3	Object and Class Model	4

3.5.4	Dynamic Models	4

3.5.5	User Interface	4

4	Other Analysis Elements	4

4.1	Consideration of Various Factors in Engineering Design	5

4.2	Risks and Alternatives	5

4.3	Project Plan	5

4.4	Ensuring Proper Teamwork	6

4.5	Ethics and Professional Responsibilities	6

4.6	Planning for New Knowledge and Learning Strategies	6

5	Glossary	6

6	References	6

Analysis Report

Project Short-Name: Project Title

Introduction

This report template is for your convenience. Feel free to use it in your CS 491-2 reports. It might be a good opportunity to learn and practice the use of Microsoft Word in a more professional manner.

Each paragraph, title, caption, etc. should be given a proper “style”, which will result in a consistent formatting. This will also allow you to automatically produce and update table of contents and cross references to figures, tables, and references.

Current System

Remove this section if your project is a “greenfield project”, where you start from scratch.

Proposed System

This is where you provide the details of the results of your analysis work.

Overview

This is how you cross-reference something from the list of references [1]. As the number of a reference changes, use right-click | “Update Field” to update it.

Functional Requirements

Provide a number and caption for every figure as below. This is how you reference a figure (Figure 1). If you happen to insert a new figure before this one, right-click on the reference and select “Update Field” to update its figure number.

Figure 1. An example figure.

Non-functional Requirements

A bulleted list is below:

An item

An item

…

Pseudo Requirements

A numbered list is below:

An item

An item

…

System Models

Scenarious

A hyperlink is here.

Use-Case Model

A code segment is below:

for (i=1; i<=5; i++)

System.out.println(“report to write”);

If you need to inline code, use “this” style

Object and Class Model

Table 1 is an example table.

Table 1. An example table.

Key	Value
key	Value

Dynamic Models

User Interface

Other Analysis Elements

Consideration of Various Factors in Engineering Design

Risks and Alternatives

Project Plan

Below you can see various tables that you will make.

Table xx: Factors that can affect analysis and design.

Effect level	Effect
Public health
Public safety
Public welfare
Global factors
Cultural factors
Social factors

Table xx: Risks

Likelihood	Effect on the project	B Plan Summary
Risk ..
Risk ..
Risk ..

Table xx: List of work packages

WP#	Work package title	Leader	Members involved
WP1
WP2
…

WP 1: <write the name of the work package title>
Start date: <write the start date> End date: <write the end date>
Leader:	<write the name of the work package leader>	Members involved:	<write the names of all team members working in this work package excluding the work package leader >
Objectives: <briefly explain the objectives of this work package (3-5 sentences) >
Tasks: Task 1.1 <write the name of the task/subtask> : <briefly explain the purpose of this task (1-3 sentences)> Task 1.2 <write the name of the task/subtask> : <briefly explain the purpose of this task (1-3 sentences)> …
Deliverables D1.1: <write the name of the deliverable> D1.2: <write the name of the deliverable> D1.3: <write the name of the deliverable> … (the number of the tasks and deliverables could be different)
WP 2: <write the name of the work package title> --- repeat it for each work package
Start date: <write the start date> End date: <write the end date>
Leader:	<write the name of the work package leader>	Members involved:	<write the names of all team members working in this work package excluding the work package leader >
Objectives: <briefly explain the objectives of this work package (3-5 sentences) >
Tasks: Task 2.1 <write the name of the task/subtask> : <briefly explain the purpose of this task (1-3 sentences)> Task 2.2 <write the name of the task/subtask> : <briefly explain the purpose of this task (1-3 sentences)> …
Deliverables D2.1: <write the name of the deliverable> D2.2: <write the name of the deliverable> D2.3: <write the name of the deliverable> … (the number of the tasks and deliverables could be different)

Ensuring Proper Teamwork

Ethics and Professional Responsibilities

Planning for New Knowledge and Learning Strategies

Glossary

Glossary for any domain-specific terms you use in your report.

References

Object-Oriented Software Engineering, Using UML, Patterns, and Java, 2nd Edition, by Bernd Bruegge and Allen H. Dutoit, Prentice-Hall, 2004, ISBN: 0-13-047110-0.