Final Year Project Report

Project Title

Project Advisor:

Submitted By:

Session

University of Management and Technology

C-II Johar Town Lahore Pakistan

“Project Title”
Page | 1
CONTENTS

New paragraphs formatted as Heading 1, Heading 2, and Heading 3 will be added to the table
automatically. To update this table of contents in Microsoft Word, put the cursor anywhere in the
table and press F9. If you want the table to be easy to maintain, do not change it manually.
CONTENTS...................................................................................................................................................3
DEFINITIONS AND ACRONYMS...................................................................................................................4
LIST OF FIGURES..........................................................................................................................................5
LIST OF TABLES............................................................................................................................................6
1. INTRODUCTION...............................................................................................................................7
1.1 MOTIVATIONS....................................................................................................................................7
1.2 PROJECT OVERVIEW..........................................................................................................................7
2. DOMAIN ANALYSIS........................................................................................................................8
2.1 CUSTOMER.........................................................................................................................................8
2.2 STAKEHOLDERS..................................................................................................................................8
3. REQUIREMENTS ANALYSIS..........................................................................................................9
3.1 REQUIREMENTS..................................................................................................................................9
3.2 LIST OF ACTORS...............................................................................................................................10
3.3 LIST OF USE CASES...........................................................................................................................10
3.4 SYSTEM USE CASE DIAGRAM...........................................................................................................10
3.5 USE CASES.......................................................................................................................................11
4. DATA FLOW DIAGRAM (OPTIONAL)......................................................................................12
4.1 DATA FLOW DIAGRAM LEVEL 0....................................................................................................12
4.2 DATA FLOW DIAGRAM LEVEL 1....................................................................................................12
4.3 DATA FLOW DIAGRAM LEVEL 2....................................................................................................13
5. SYSTEM DESIGN.............................................................................................................................14
5.1 CLASS DIAGRAM.............................................................................................................................14
5.2 SEQUENCE DIAGRAMS....................................................................................................................15
5.3 OTHER UMLS..................................................................................................................................15
6. TESTING.............................................................................................................................................16
6.1 TEST CASES......................................................................................................................................16
6.2 TRACEABILITY MATRIX...................................................................................................................17
6.2.1 RID vs UCID (requirements vs use cases)..............................................................17

“Project Title”
Page | 2
Definitions and Acronyms
Provide definitions or references to all the definitions of the special terms and acronyms used
within this document
e.g
Acronym Definition
UMT University of Management and Technology
POS Point of Sale

Table 1: table of acronyms and definitions

“Project Title”
Page | 3
List of Figures

Figure 1: sample use case diagram with explanation....................................................................10

Figure 2: System Architecture......................................................................................................16

“Project Title”
Page | 4
List of Tables
Table 1: table of acronyms and definitions.....................................................................................3
Table 2: list of stakeholders............................................................................................................7

“Project Title”
Page | 5
1. INTRODUCTION

1.1 Motivations
This section deals with the motivation behind choosing this project.

1.2 Project Overview

Give a short summary of the project objective and the system to be developed.
Following are the sample artifacts for this section:
 Problems or Overview Statement
 Customer
 Goals
 System functions
 System attributes

“Project Title”
Page | 6
2. DOMAIN ANALYSIS

2.1 Customer
A brief description of the client with whom you are working (or the potential customers). The organization,
its products/services etc.You will fill this section only if you have a client (contracted) .

2.2 Stakeholders
List of all stakeholders along with their roles in making of the system e.g

Table 2: list of stakeholders

“Project Title”
Page | 7
3. REQUIREMENTS ANALYSIS

3.1 Requirements
3.1.1 Function Categories

RID description Priority

R1.1 Record the underway sale – the items purchased non-functional

R1.2 Reduce inventory quantities when a sale is committed non-functional

3.1.2 Non Functional Requirements

RID description Priority
R1.1 Record the underway sale – the items purchased non-functional

R1.2 Reduce inventory quantities when a sale is committed non-functional

3.2 List of Actors

Define the system boundary and list all actors with the use cases.all the actors must also be mentioned in
your list of stakeholders
For example:
Cashier; this person performs all the financial activities
Account Manager; this person supervises all financial activities

3.3 List of use cases

List all the use cases, with a brief description (should not exceed two lines):
Buy Item; captures a sale and its payment
Log In; allow user to provide account information and access the restricted services

“Project Title”
Page | 8
3.4 System use case diagram

Figure 1: sample use case diagram with explanation

3.5 Use Cases

Every use case form the list must be elaborated here. E.g
Use Case ID: Enter a unique numeric identifier for the Use Case. e.g. UC-1.2.1
Use Case Enter a short name for the Use Case using an active verb phrase. e.g. Withdraw Cash
Name:
Created By: Last Updated By:
Date Created: Last Revision Date:
Actors: [An actor is a person or other entity external to the software system being specified
who interacts with the system and performs use cases to accomplish tasks. Different
actors often correspond to different user classes, or roles, identified from the customer
community that will use the product. Name the actor that will be initiating this use
case (primary) and any other actors who will participate in completing the use case
(secondary).]
Preconditions: [List any activities that must take place, or any conditions that must be true, before the
use case can be started. Number each pre-condition. e.g.
1. Customer has active deposit account with ATM privileges

“Project Title”
Page | 9
 2. Customer has an activated ATM card.]
Post conditions: [Describe the state of the system at the conclusion of the use case execution. Should
include both minimal guarantees (what must happen even if the actor’s goal is not
achieved) and the success guarantees (what happens when the actor’s goal is
achieved. Number each post-condition. e.g.
1. Customer receives cash
2. Customer account balance is reduced by the amount of the withdrawal and
transaction fees]
Normal Flow: [Provide a detailed description of the user actions and system responses that will take
place during execution of the use case under normal, expected conditions. This
dialog sequence will ultimately lead to accomplishing the goal stated in the use case
name and description.
1. Customer inserts ATM card
2. Customer enters PIN
3. System prompts customer to enter language performance English or Spanish
4. System validates if customer is in the bank network
5. System prompts user to select transaction type
6. Customer selects Withdrawal From Checking
7. System prompts user to enter withdrawal amount
8. …
9. System ejects ATM card]
Alternative [Document legitimate branches from the main flow to handle special conditions (also
Flows: known as extensions). For each alternative flow reference the branching step number
[Alternative of the normal flow and the condition which must be true in order for this extension to
Flow 1 – Not in be executed. e.g. Alternative flows in the Withdraw Cash transaction:
Network] 4a. In step 4 of the normal flow, if the customer is not in the bank network
1. System will prompt customer to accept network fee
2. Customer accepts
3. Use Case resumes on step 5
4b. In step 4 of the normal flow, if the customer is not in the bank network
1. System will prompt customer to accept network fee
2. Customer declines
3. Transaction is terminated
4. Use Case resumes on step 9 of normal flow
Note: Insert a new row for each distinctive alternative flow. ]

“Project Title”
Page | 10
4. DATA FLOW DIAGRAM (OPTIONAL)

4.1 Data Flow Diagram Level 0

Identifies sources and sinks only e.g

4.2 Data Flow Diagram Level 1

Identifies actual data flows and data storese.g

“Project Title”
Page | 11
4.3 Data Flow Diagram Level 2

“Project Title”
Page | 12
5. SYSTEM DESIGN

5.1 Class Diagram

“Project Title”
Page | 13
5.2 Sequence Diagrams

5.3 Other UMLs

This is optional. You may include any other UML to support your system.

“Project Title”
Page | 14
6. TESTING

6.1 Test Cases

“Project Title”
Page | 15
6.2 Traceability Matrix
6.2.1 RID vs UCID (requirements vs use cases)
UCID/ R R R R R R R R R R R R R R R R R R R R R
RID 1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2
0 1 2 3 4 5 6 7 8 9 0 1
UC 1  
UC 2 
UC 3   
UC 4   
UC 5    
UC 6    
UC 7    
UC 8    
UC 9     
UC 10     
UC 11     
UC 12     
UC 19     
UC 20     
UC 21   
UC 22   
UC 23    
UC 24    
UC 25     
UC 26     
UC 27     

“Project Title”
Page | 16