Reemali 201000542

Bachelor of ICT Assessment Cover Sheet
Complete and attach this cover sheet to your assessment before submitting
Assessment Title
Project in Systems Analysis and Design
Programme Title:
Bachelor of Information and Communication

Technology
Course Code:
ITB6001
Course Title:
Systems Analysis and Design
Student Name:
Student ID:
Mohammed Abdulla
Reem Alattar
Ebrahim Rajab
201000228 201000542 201101376
Tutor:
Momir Radicevic
16/6/2013
Due Date:
16/6/2013
Date submitted:
By submitting this assessment for marking, either electronically or as

hard copy, I confirm the following:
This assignment is my own work
Any information used has been properly referenced.

I understand that a copy of my work may be used for moderation.
Do not write below this line. For Polytechnic use only.
Assessor:
Grade/Mark:
Comments:
Date of Marking:
Contents
...........................................................1
1.
The code for the database................................................................................... 4
2.
Design use case narrative for Trigger Fire Alarm..............................................11
3.
Design use case narrative for Disarm Security System....................................13
4.
Design use case narrative for Notify Fire Department......................................14
5.
Sequence diagram for Trigger Fire Alarm.........................................................16
6.
Sequence diagram for Disarm Security System...............................................17
7.
Sequence diagram for Notify Fire Department.................................................18
8.
State-chart Diagram for the Fire Sensor object................................................19
9.
State-chart Diagram for the Position object.....................................................20
10.
One state-chart diagram for the Security System object..............................21
11.
Design class diagram for Trigger Fire Alarm..................................................22
12.
Design class diagram for Disarm Security System........................................22
13.
Design class diagram for Notify Fire Department..........................................23
14.
Form prototype Maintain Employee..............................................................24
15.
Form prototype Maintain Fire Detectors........................................................25
16.
Form prototype Maintain Intrusion Sensors...................................................26
17.
Project Request + Problem Statement Matrix.................................................27
18.
Ishikawa Diagram for the problem of your choice...........................................29
19.
Problems, Opportunities, Objectives and Constraints Matrix..........................30
20.
Requirements Model Diagram of the system..................................................31
21.
Actor Glossary................................................................................................. 32
22.
Use Case Glossary.......................................................................................... 33
23.
Analysis Use Case Model Diagram of the system............................................35
24.
Use case narrative for the Trigger Fire Alarm use case.................................36
25.
Use case narrative for the Disarm Security System use case.......................38
28.
Activity diagram for Trigger Fire Alarm..........................................................42
29.
Activity diagram for Disarm Security System................................................43
30.
Activity diagram for Notify Fire Department..................................................44
31.
Potential Object List + Refined Object List + Proposed Object List.................45
32.
Domain Class Diagram of the system.............................................................53
33.
Fully attributed database model of the system (ERD).....................................54
34.
Cost/Benefit analysis for the system (Net Present Value, Payback Period)......55
35.
MS Project file which outlines the schedule, deliverables and resources........56
36.
Interview form/forms....................................................................................... 57
1. The code for the database

CREATE TABLE Department (
Department_ID NUMBER NOT NULL,
Department_name VARCHAR2(10) NOT NULL,
CONSTRAINT DEPARTMENT_PK PRIMARY KEY (Department_ID)
);
CREATE TABLE System_Failure (

Failure_ID NUMBER NOT NULL,
Failure_Description VARCHAR2(10) NOT NULL,
Failure_Time DATE NOT NULL,
Failure_Date DATE NOT NULL,
CONSTRAINT SYSTEM_FAILURE_PK PRIMARY KEY (Failure_ID)
);
CREATE TABLE Employee (

Employee_ID NUMBER NOT NULL,
Employee_Address VARCHAR2(10) NOT NULL,
Employee_Email VARCHAR2(10) NOT NULL,
Employee_LastName VARCHAR2(10) NOT NULL,
Employee_FirstName VARCHAR2(10) NOT NULL,
Employee_Position VARCHAR2(10) NOT NULL,
Employee_PhoneNumber NUMBER NOT NULL,
Department_ID NUMBER NOT NULL,
CONSTRAINT EMPLOYEE_PK PRIMARY KEY (Employee_ID)
);
CREATE TABLE Full-time_Employees (

Hourly_Salary NUMBER NOT NULL,
Working_Hours DATE NOT NULL,
Employee_ID NUMBER NOT NULL
);
CREATE TABLE Part-time_Employees (
Hourly_Salary NUMBER NOT NULL,

Working_Hours DATE NOT NULL,
Employee_ID NUMBER NOT NULL
);
CREATE TABLE System_Modes (

Mode_ID NUMBER NOT NULL,
Mode_Description VARCHAR2(10) NOT NULL,
Mode_Type VARCHAR2(10) NOT NULL,
CONSTRAINT SYSTEM_MODES_PK PRIMARY KEY (Mode_ID)
);
CREATE TABLE Fire_Brigade (

FireDep_ID NUMBER NOT NULL,
FireDep_Address VARCHAR2(10) NOT NULL,
FireDep_Location VARCHAR2(10) NOT NULL,
FireDep_Name VARCHAR2(10) NOT NULL,
CONSTRAINT FIRE_BRIGADE_PK PRIMARY KEY (FireDep_ID)
);
CREATE TABLE Detection_Log (

Log_ID NUMBER NOT NULL,
Log_date DATE NOT NULL,
Log_description VARCHAR2(10) NOT NULL,
Log_time DATE NOT NULL,
CONSTRAINT DETECTION_LOG_PK PRIMARY KEY (Log_ID)
);
CREATE TABLE Fire_Detection (

Fire_ID NUMBER NOT NULL,
Fire_Description VARCHAR2(10) NOT NULL,
Fire_Location VARCHAR2(10) NOT NULL,
FireDep_ID NUMBER NOT NULL,
CONSTRAINT FIRE_DETECTION_PK PRIMARY KEY (Fire_ID)
);
CREATE TABLE Workshop (

Workshop_ID NUMBER NOT NULL,
Workshop_Date DATE NOT NULL,
Workshop_Name VARCHAR2(10) NOT NULL,
Workshop_Time DATE NOT NULL,
CONSTRAINT WORKSHOP_PK PRIMARY KEY (Workshop_ID)
);
CREATE TABLE Exhibition (

Exhibition_ID NUMBER NOT NULL,
Exhibition_Date DATE NOT NULL,
Exhibition_Name VARCHAR2(10) NOT NULL,
Exhibition_Time DATE NOT NULL,
Employee_ID NUMBER NOT NULL,
CONSTRAINT EXHIBITION_PK PRIMARY KEY (Exhibition_ID, Workshop_ID)
);
CREATE TABLE Hall (

Hall_ID NUMBER NOT NULL,
Hall_name VARCHAR2(10) NOT NULL,
Hall_Location VARCHAR2(10) NOT NULL,
Mode_ID NUMBER NOT NULL,
CONSTRAINT HALL_PK PRIMARY KEY (Hall_ID, Exhibition_ID, Workshop_ID)
);
CREATE TABLE Detector (

Detector_ID NUMBER NOT NULL,
Detector_Description VARCHAR2(10) NOT NULL,
Detector_Name VARCHAR2(10) NOT NULL,
Detector_type VARCHAR2(10) NOT NULL,

CONSTRAINT DETECTOR_PK PRIMARY KEY (Detector_ID)
);
CREATE TABLE INTRUSION_DETECTION (

Intrusion_ID NUMBER NOT NULL,
Intrusion_Description VARCHAR2(10) NOT NULL,
Intrusion_Location VARCHAR2(10) NOT NULL,
Detector_ID NUMBER NOT NULL,
CONSTRAINT INTRUSION_DETECTION_PK PRIMARY KEY (Intrusion_ID)
);
CREATE TABLE Sensor (

Sensor_ID NUMBER NOT NULL,
Sensor_Description VARCHAR2(10) NOT NULL,
Sensor_Type VARCHAR2(10) NOT NULL,
Sensor_Name VARCHAR2(10) NOT NULL,
Fire_ID NUMBER NOT NULL,
CONSTRAINT SENSOR_PK PRIMARY KEY (Sensor_ID)
);
CREATE TABLE Artist (

Artist_ID NUMBER NOT NULL,
Artist_Address VARCHAR2(10) NOT NULL,
Artist_Name VARCHAR2(10) NOT NULL,
Artist_Email VARCHAR2(10) NOT NULL,
CONSTRAINT ARTIST_PK PRIMARY KEY (Artist_ID)
);
ALTER TABLE Employee ADD CONSTRAINT DEPARTMENT_EMPLOYEE_FK
FOREIGN KEY (Department_ID)

REFERENCES Department (Department_ID)
NOT DEFERRABLE;
ALTER TABLE Sensor ADD CONSTRAINT SYSTEM_FAILURE__SENSOR_FK
FOREIGN KEY (Failure_ID)
REFERENCES System_Failure (Failure_ID)
NOT DEFERRABLE;
ALTER TABLE Detector ADD CONSTRAINT SYSTEM_FAILURE__DETECTOR_FK
FOREIGN KEY (Failure_ID)
REFERENCES System_Failure (Failure_ID)
NOT DEFERRABLE;
ALTER TABLE Exhibition ADD CONSTRAINT EMPLOYEE_EXHIBITION_FK
FOREIGN KEY (Employee_ID)
REFERENCES Employee (Employee_ID)
NOT DEFERRABLE;
ALTER TABLE Part-time_Employees ADD CONSTRAINT
EMPLOYEE_PART_TIME_EMPLOYEE70
NOT DEFERRABLE;
ALTER TABLE Full-time_Employees ADD CONSTRAINT
EMPLOYEE_FULL_TIME_EMPLOYEE170
NOT DEFERRABLE;
ALTER TABLE Hall ADD CONSTRAINT MODE_HALL_FK
FOREIGN KEY (Mode_ID)
REFERENCES System_Modes (Mode_ID)
DEFERRABLE INITIALLY DEFERRED;
ALTER TABLE Fire_Detection ADD CONSTRAINT FIRE_BRIGADE_FIRE_DETECTION_FK
FOREIGN KEY (FireDep_ID)
REFERENCES Fire_Brigade (FireDep_ID)
NOT DEFERRABLE;
ALTER TABLE INTRUSION_DETECTION ADD CONSTRAINT

DETECTION_LOG_INTRUSION_DET4
FOREIGN KEY (Log_ID)
REFERENCES Detection_Log (Log_ID)
NOT DEFERRABLE;
ALTER TABLE Fire_Detection ADD CONSTRAINT DETECTION_LOG_FIRE_DETECTIO643
FOREIGN KEY (Log_ID)
REFERENCES Detection_Log (Log_ID)
NOT DEFERRABLE;
ALTER TABLE Sensor ADD CONSTRAINT FIRE_DETECTION_SENSOR_FK
FOREIGN KEY (Fire_ID)
REFERENCES Fire_Detection (Fire_ID)
NOT DEFERRABLE;
ALTER TABLE Exhibition ADD CONSTRAINT WORKSHOP_EXHIBITION_FK
FOREIGN KEY (Workshop_ID)
REFERENCES Workshop (Workshop_ID)
NOT DEFERRABLE;
ALTER TABLE Hall ADD CONSTRAINT EXHIBITION_HALL_FK
FOREIGN KEY (Workshop_ID, Exhibition_ID)
REFERENCES Exhibition (Workshop_ID, Exhibition_ID)
NOT DEFERRABLE;
ALTER TABLE Sensor ADD CONSTRAINT HALL_SENSOR_FK
FOREIGN KEY (Exhibition_ID, Workshop_ID, Hall_ID)
REFERENCES Hall (Exhibition_ID, Workshop_ID, Hall_ID)
NOT DEFERRABLE;
ALTER TABLE Detector ADD CONSTRAINT HALL_DETECTOR_FK
FOREIGN KEY (Exhibition_ID, Workshop_ID, Hall_ID)
REFERENCES Hall (Exhibition_ID, Workshop_ID, Hall_ID)
NOT DEFERRABLE;
ALTER TABLE INTRUSION_DETECTION ADD CONSTRAINT
DETECTOR_INTRUSION_DETECTIO376
FOREIGN KEY (Detector_ID)
REFERENCES Detector (Detector_ID)

NOT DEFERRABLE;
2. Design use case narrative for Trigger Fire Alarm

USE CASE NAME:
USE CASE ID:
Trigger Fire Alarm

TFA-001
PRIORITY:
High
SOURCE:
ACTORS:
USE CASE TYPE

Business Requirements:
System Analysis:
System Design:
Fire sensors
OTHER
PARTICIPATING
ACTORS:
STAKEHOLDERS:
DESCRIPTION:
PRE-CONDITION:
TRIGGER:
TYPICAL COURSE
OF EVENTS (FLOW
OF ACTIVITIES):
ALTERNATE COURSES
(EXCEPTION
This use case describes the event of Triggering Fire Alarm.

The system is active; there is smoke, flame, or fire in the
building.
Receive Signal from sensor.
Actor Action
System Response
Step 1: the sensors is

triggered
by
smoke,
flame, or fire
Step 2: the sensors Step 3: System receives the
send a signal to the signal from the sensors.
system.
Step 4: System converts the
voltage signal to digital signal.
Step 5: search in the database
and check if the signal match
the system signal.
- 0 for false signal.
- 1 for correct signal.
Step 6: The system identifies
the type of sensor and location.
Step 7: activate the local alarm
if the signal equal to 1.
Step 8: invoke Notify Fire
Department use case.
Step 9: the system will Invoke
Create
detection
Log.
Step 3a: if the system cannot receive signal from the
sensors, system invoke System Failure log use case.
CONDITIONS):
Step 4a: if the signal received is 0, system invokes

System Failure log use case.
CONCLUSION:
POST-CONDITION:
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS:
OPEN ISSUES:
3. Design use case narrative for Disarm Security System

USE CASE NAME:
USE CASE ID:
Trigger Fire Alarm

TFA-001
PRIORITY:
High
SOURCE:
ACTORS:
USE CASE TYPE

System Analysis:
System Design:
Fire sensors
OTHER
PARTICIPATING
ACTORS:
STAKEHOLDERS:
DESCRIPTION:
PRE-CONDITION:
TRIGGER:
TYPICAL COURSE
OF EVENTS (FLOW
OF ACTIVITIES):
ALTERNATE COURSES
(EXCEPTION

The system is active; there is smoke, flame, or fire in the
building.
Receive Signal from sensor.
Actor Action
System Response
Step 1: the sensors is

triggered
by
smoke,
flame, or fire
Step 2: the sensors Step 3: System receives the
system.
Step 4: System converts the
voltage signal to digital signal.
Step 5: search in the database
and check if the signal match
the system signal.
- 0 for false signal.
- 1 for correct signal.
Step 6: The system identifies
the type of sensor and location.
if the signal equal to 1.
Step 8: invoke Notify Fire
Department use case.
Create
detection
Log.
sensors, system invoke System Failure log use case.
CONDITIONS):
Step 4a: if the signal received is 0, system invokes

System Failure log use case.
CONCLUSION:
POST-CONDITION:
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS:
OPEN ISSUES:
4. Design use case narrative for Notify Fire Department

USE CASE NAME:
USE CASE ID:
PRIORITY:
SOURCE:
ACTORS
STAKEHOLDERS:
DESCRIPTION:
PRE-CONDITION:
TRIGGER:
TYPICAL COURSE
OF EVENTS
(FLOW OF
ACTIVITIES):
Notify Fire Department

NFD-001
High
USE CASE TYPE

System Analysis:
System Design:
No actors, all process will be in the system

This use case describes the event of notify fire department
after triggering the fire alarm.
The building is on fire, local alarm and remote alarm are
activated.
A call from Trigger fire alaram use case.
Actor Action
System Response
Step 1: A call from Trigger fire
alarm use case.

Step 2: The system will search in
the database for the fire
departments numbers.
Step 3The system will dial the
number
Step 4: the system will notify

the fire department with
building address, time the fire

started.
Step 5: the system will invoke
Create detection Log.
ALTERNATE
COURSES
(EXCEPTION
CONDITIONS):
Step 2 a: if there is no response from the fire department.

The system will call the next closest fire brigade, and
invoke Create log of system failure.
Step 2 b: if the fire departments not responded, the
system Notify employee or Manager.
CONCLUSION:
Fire department, one of the employee, or the manager

response to the system notification.
POST-CONDITION:
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS
AND
SPECIFICATIONS
ASSUMPTIONS:
OPEN ISSUES:
5. Sequence diagram for Trigger Fire Alarm
6. Sequence diagram for Disarm Security System
7. Sequence diagram for Notify Fire Department
8. State-chart Diagram for the Fire Sensor object
9. State-chart Diagram for the Position object
10.
One
state-chart diagram for the Security System object
11.
class diagram for Trigger Fire Alarm
Design
12.
class diagram for Disarm Security System
Design
13.
class diagram for Notify Fire Department
Design
14.
prototype Maintain Employee
Main Switchboard
Maintain Employee Form
Form
15.
prototype Maintain Fire Detectors
Main Switchboard
Maintain Fire Detectors
Form
16.
prototype Maintain Intrusion Sensors.

Main Switchboard
Maintain Intrusion Sensors
Form
17. Project Request + Problem Statement
Matrix
Brief Statements of
Problem, Opportunity,
or Directive
1.
Between the
periods from
midnight to 6 am
there is no security
guard.
Urgency
Visibility
Annual
Benefits
Priority
or Rank
Proposed
Solution
6 months
High
21,600 in
security
guard
salaries and
3,000 in
insurance
premiums
New
computeri
zed
security
system
21,600 in
security
guard
salaries and
3,000 in
insurance
premiums
New
computeri
zed
security
system
New
computeri
zed
security
system
New
computeri
zed
security
system
New
computeri
zed
security
system.
2.
We cant employee
a new guard.
5 months
Low
3.
In future in cause of
any fire there is no
protection.
5 months
Medium
4.
Between 12 to 6
there is big
possibility of
exposure to theft
6 months
High
High
5.
1.
The owner has

concern regards to
the feasibility of
the project.
The Modern Art Gallery

Phone:
DATE OF REQUEST
23/3/2013
SERVICE REQUESTED FOR DEPARTMENT(S)

Administration department
SUBMITTED BY (key user contact)
Name
Title
Office
Phone
Fax:
Reem Alattar
Ms
Polytechnic
174446334
EXECUTIVE SPONSOR (funding authority)
Name
Title
Office
Phone
Momir
Mr
TYPE OF SERVICE REQUESTED:
Information Strategy Planning

Existing Application
Enhancement
Business Process Analysis and Redesign
Existing Application
Maintenance (problem fix)
New Application Development
Not Sure
Other (please specify
_______________________________________________________________________
BRIEF STATEMENT OF PROBLEM, OPPORTUNITY, OR DIRECTIVE (attach additional
documentation as necessary)
Between the periods from midnight to 6 am there is no security guard.

We cant employee a new guard.
In future in cause of any fire there is no protection.
Between 12 to 6 there is big possibility of exposure to theft
BRIEF STATEMENT OF EXPECTED SOLUTION

-new computerized security system
ACTION (ISS Office Use Only)

Feasibility assessment approvedAssigned to _<Reem Abdulla>_
Feasibility assessment waived Approved Budget
$ 30,000
Start Date __ _____

Request delayed
Deadline _ ___
Backlogged until date: ______________
Request rejected
Reason:
________________________________________________
Authorized Signatures:
_____________________________________
_________________________________________________
Project
Executive Sponsor
18. Ishikawa Diagram for the problem of your
choice
19. Problems, Opportunities, Objectives and
Constraints Matrix
PROBLEMS, OPPORTUNITIES, OBJECTIVES AND
CONSTRAINTS MATRIX
Project: The Modern Art Gallery (MAG)
Project Manager:ebrahim
Created by:
Last Updated by:Reem
Mohammed
Date Created: 23-3-2013

CAUSE AND EFFECT ANALYSIS
Problem or
Opportunity
6.
Between
the periods
from
midnight to
6 am there
is no
security
guard.
7.
We cant
employee a
new guard.
8.
In future in
cause of
any fire
there is no
protection.
9.
Between 12
to 6 there
is big
possibility
of exposure
to theft
10. The owner
has
concern
regards to
the
feasibility
of the
project.
Date Last Updated:24-3-2013

SYSTEM IMPROVEMENT OBJECTIVES
Causes and
Effects
System Objective
System
Constraint
1. Cause: The
security contract
doesnt cover this
period of time.
Effect: the rate of
exposure to theft.
2. Cause: the cost of
guarding will
increase.
Effect: the gallery
will need to pay
more for hiring
new guard.
3. Cause: not having
anti-fire system.
Effect: the gallery
will be More
vulnerability to
fire.
4. Cause: not having
security system.
Effect: the gallery
will be more
vulnerability to
theft.
1. New security
system will
prevent the
gallery from
thiefs.
2. The insurance
fees will slightly
decrees.
3. The gallery will be
less vulnerability
to fire.
4. New security
system will
prevent the
gallery from
thiefs.
5. new security
system must be
efficient to
satisfied the
owner.
1. The system should

have doors and
windows sensors
and motion
detector and
perimeter. The
system has the
ability to notify
the police
department.
have doors and
windows sensors
and motion
detector and
perimeter. The
system has the
ability to notify
the police
department.
have smoke
detectors and
heat activated
detectors and flam
activated detector.
And the system
has the ability to
notify the fire
department, the
manager or one of
the employees.
5. Cause: Owner
cannot see the
benefit of
developing the
software for the
system.
effect: it may
postponed the
developing of the
project.

have doors and
windows sensors
and motion
detector and
perimeter. The
system has the
ability to notify
the police
department.
5. the system should
have all features
the owner asked
for working
efficiently
20. Requirements Model Diagram of the
system
Functional Requirements:
Non-Functional Requirements:
21. Actor Glossary

Actor Glossary
Actor Name
Employee
Actor Description
This Actor represents each person who
worked in the MAG different
departments which includes
(receptionist, hostess, and accountant)
Sensor
Detector
Administration(Manager)
Fire Department
This Actor represent the sensors which

are connected together within the
system.
This Actor represent the detector which
are connected together within the
system.
This actor represents the manager or
the Owner of the MAG gallery.
This actor represents each of the fire
department when one of them reply on
any fire notification.
22. Use Case Glossary

Use-Case Glossary
Use-Case Name
Login
Trigger Fire Alarm
Trigger Intrusion Alarm
Create detection Log
View detection Log

Maintain detection Log
Disarm security system
Store data on the

employees
Use-Case Description
This use case describes the event of login
into the system by one of the employee.
This use case describes the event when
the system trigger the fire alarm in the
building.
This use case describes the event when
the system trigger any intrusion alarm in
the building.
This use case describes the event of
recording a log of intrusion or fire the
system. E.g.: location, date, time, and
mode of the system.
viewing the detection logs.
updating the detection logs.
deactivate the security system,
notifying the closest and available fire
department.
storing data of the employees in the
system.
Participating
Actors and Roles
Employee
System
Sensors
System
detectors
System
System
Administration
System
Administration
System
Authorized person
system
System
Fire department
Administration
System
Maintain data on the

employees
View data on the
employees
Store data on the
departments
Maintain data on the
departments
View data on the
departments
Create Log of system
failures
Maintain Log of System

Failures
View Log of system
Failures

maintaining data of the employees in the
system.
viewing data of the employees in the
system.
storing data of the departments in the
system.
maintaining data of the departments in the
system.
viewing data of the departments in the
system.
recording system failures, for example
inability to receive a signal from the
sensors
updating system failures.
viewing system failures.
Administration
System
Administration
System
Administration
System
Administration
System
Administration
System
Administration
System
Administration
System
Administration
System
23. Analysis Use Case Model Diagram of the
system
24. Use case narrative for the Trigger Fire
Alarm use case

USE CASE NAME:
USE CASE ID:
Trigger Fire Alarm

TFA-001
PRIORITY:
High
SOURCE:
ACTORS:
USE CASE TYPE

System Analysis:
System Design:
Fire sensors
OTHER
PARTICIPATING
ACTORS:
STAKEHOLDERS:
DESCRIPTION:
PRE-CONDITION:
TRIGGER:
TYPICAL COURSE
OF EVENTS (FLOW
OF ACTIVITIES):
ALTERNATE COURSES
(EXCEPTION
CONDITIONS):

The system is active, there are smoke, flame, or fire in the
building.
the sensors trigger smoke, flame, or fire.
Actor Action
System Response
Step 1: the sensors

trigger smoke, flame, or
fire
Step 2: the sensors Step 3: system receive the
system.
and
the
remote
alarm
simultaneously
Step 3 : invoke Notify Fire
Department use case
Step 4: Turn-On the Exit Sign
light.
Step 5: activate the water
sprinklers for fire
Record
Fire
Detection.
sensors, system invoke Create System Failure use case.
CONCLUSION:
POST-CONDITION:
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS:
OPEN ISSUES:
25. Use case narrative for the Disarm Security
System use case

26.
USE CASE NAME:
USE CASE ID:
Disarm Security System

DSS-001
PRIORITY:
High
SOURCE:
ACTORS:
OTHER
PARTICIPATING
ACTORS:
STAKEHOLDERS:
DESCRIPTION:
PRE-CONDITION:
TRIGGER:
TYPICAL COURSE
OF EVENTS
(FLOW OF
ACTIVITIES):
USE CASE TYPE

System Analysis:
System Design:
Authorized Person (Employee or a manager)
This use case give a brief description when one of the

employees attempt to disarm the system
The alarm is activated,
authorized person will swap a card.
Actor Action
System Response
Step 1: authorized
person will swap a card
Step 2: the system verify the

card.
Step 3: enter a PIN

number
Step 4: verify authentication.
Step 6: the authorized

person choose Disarm
Secure Mode.
Step 8: the authorized
person choose to
continue with disarm the
Secure Mode
Step 5: the system display

greeting message to the
authorized person.
Step 7: the system display
confirmation message Are you
Sure You want to Disarm the
Secure Mode?
Step 9: the system disarm the
Secure Mode
Step 10: The system Back To

the "Normal Mode" Security
System Automatically.
ALTERNATE
COURSES
(EXCEPTION
CONDITIONS):
Step 1a: if the authorized person does not have a card,

this person use a computer to enter a PIN number to
disarm the Secure-Mode.
Step2a: if the card is not verified, the system send an
email and SMS to the manager for trying to break the
gallery system.
Step 4a: if the pin-Number is written incorrect for three
times, the system block access on the wall mounted
interface for 10 minutes.
Step 8a: if the authorized person choose Cancel, the
system return to greeting message display.
CONCLUSION:
The Security System will disarm from the Secure-Mode and

return Automatically to the Normal-Mode.
POST-CONDITION:
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS
AND
SPECIFICATIONS
ASSUMPTIONS:
OPEN ISSUES:
27.
Use case
narrative for the Notify Fire Department use case
USE CASE NAME:
USE CASE ID:
PRIORITY:
SOURCE:
ACTORS
STAKEHOLDERS:

NFD-001
High
Fire department
USE CASE TYPE

System Analysis:
System Design:
DESCRIPTION:
PRE-CONDITION:
TRIGGER:
TYPICAL COURSE
OF EVENTS
(FLOW OF
ACTIVITIES):
This use case describes the event of notify fire department

after triggering the fire alarm
The building is on fire, local alarm and remote alarm are
activated.
The system will search in the database for the fire
departments numbers
Actor Action
System Response
Step 1: The system will search in
the database for the fire
departments numbers
Step 2: the system will notify

the fire department
Step 3: the system will invoke
Create detection Log
Step 4: Fire department
response to the system.
ALTERNATE
COURSES
(EXCEPTION
CONDITIONS):
Step 2 a: if there is no response from the fire department.

The system will call the next closest fire brigade.
CONCLUSION:
Fire department, one of the employee, or the manager

response to the system notification.
POST-CONDITION:
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS
AND
SPECIFICATIONS
Step 2 b: if the fire departments not responded, the

system Notify employee or Manager.
ASSUMPTIONS:
OPEN ISSUES:
28. Activity diagram for Trigger Fire Alarm
29. Activity diagram for Disarm Security
System
30. Activity diagram for Notify Fire
Department
31. Potential Object List + Refined Object List
+ Proposed Object List

Potential
Object
exhibition
Workshop
Artists
Administration
Accounting
Library
Visitors
Departments
Employees
Librarian
Notes
The fully-detailed
class about the
exhibition been hold
in the gallery.
The fully-detailed
class about the
workshop been hold in
the gallery.
The fully-detailed
class about the
participant artists in
the workshops or the
exhibition.
The name of one
department in the
gallery.
The name of one
department in the
gallery.
The fully-detailed
class about the
Library in the gallery.
The visitors who are
attend the gallery
the fully-detailed class
about each
departments the
employees works in
Details about each
employee who worked
in the gallery
Type of employee who
worked in the library
Obje
ct
Reason
The description of
department name
attribute.
The description of
department name
attribute.
The description of
department name
attribute.
Does not necessary to
save visitors
information.
We will include position

attribute in the
Receptionist
Hostesses
Full-time
Employees
Part-time
Employees
Manager
Accountant
Shift
Guards
Positions
Hardware

worked in the
reception
worked in the gallery
The class consist of

working hours, and
employee id
The class contain of
working hours, and
employee id
worked in the
administration.
worked in the account
department.
shift id , and the
working hours.
The security guards
that are working to
protect the gallery
It contain the different

type of positions the
employees are in
The hardware being
used in the gallery
employee class instead

of it.
attribute in the
of it.
attribute in the
of it.

attribute in the
of it.
attribute in the
of it.
Cannot save the

information of the
guards, because the
gallery contact with
security guards
company.
Attribute of Employee.
X
X
Not been asked by the

manager to include
details about it.

Salary
Door
The salary that each

employee takes
The class that consist
of the details about
the insurance
payments, and a fullydescription about it.
intrusion ID, intrusion
location, and a
description about
each of intrusion
detection.
fire ID, fire location,
and a description
about each of fire
detection.
the types of the alarm
being triggered while
detect fire or
intrusion.
Type of sensors.
Window
Insurance
Intrusion
detection
Fire detection
Alarm
Attribute of Employee.
Attribute of Sensors and

Detectors.
Attribute of sensors.
Type of sensors.
Motion
Type of sensors.
Perimeter
Type of sensors.
Smoke
Type of detectors.
Attribute of detectors.
Heat
Type of detectors.
Flame
Type of detectors.
Sensors
The class that

contains the name of
sensors, type, ID, and
location.
The name of the fire
department.
Fire-department
Attribute of fire brigades.
Failure
Modes
Interface
PIN-Number
Location
detectors
Date
Time
Fire brigades
Employee ID
Employee First
Name
Employee Last
Name
Employee Email
Employee
Address
The class save the

failures been
happened to the
system.
The modes of the
system, would consist
of mode id , mode
name, and a
description.
The wall mounted
interface
The pin-number
entered by the
employee while
disarm the system.
Location of the
sensors and detectors
The class that
contains the name of
detectors, type, ID,
and location.
Date of failure of the
sensors or detectors.
Time of failure of the
sensors or detectors.
It consist of details
about the fire
department.
A unique ID identified
each employee.
Consist of Employee
first name.
Consist of Employee
last name.
Consist of Employee
email address.
Consist of Employee
address.
Not necessary to save

the interface into the
system.
It is an attribute of the
interface.
Attribute of sensors and

detectors.
X
X
Attribute of Failure.
X
X
X
X
X
Attribute of employee.
Employee Hire
Date
Employee
Position
Employee Phone
Number
Department ID
Department
Name
Shift ID
Shift Hours
Full-Time Working
Hours
Part-Time
Working Hours
Insurance ID
Insurance
Payment
Insurance
Description
Intrusion ID
Intrusion location
Intrusion
description
Fire ID
Fire location
Consist of Employee
hire date
Consist of Employee
position in the gallery
Consist of Employee
phone number
each department.
Consist of department
name.
each shift.
Consist of period of
each shift hours
Consist of the working
hours for the full-time
employees.
Consist of the working
hours for the parttime employees.
each insurance.
Consist of the each
payment to the
insurance company
Description about
name of the company,
contract,.
Intrusion ID
The location where
the intrusion done,
and other information
if necessary.
Description about
what been stolen.
each Fire detection.
Location where the
X
X
X
X
X
X
X
Attribute of department.
Attribute of department.
Attribute of Shift.
Attribute of Shift
Attribute of Full-Time
X
Attribute of Part-Time.
X
X
Attribute of Insurance.
X
X
X
X
X
X
Attribute of Intrusion
detection.
detection.
detection.
Attribute of fire
detection.
Attribute of fire
Fire description
Sensor ID
Sensor type
Sensor name
Sensor
description
Detector ID
Detector type
Detector name
Detector
description
Failure ID
Failure Time
Failure Date
Failure
Description
Mode ID
fire happened in the

building
Description about how
the fire happened,
what been burned and
other information if
necessary.
each sensor.
Sensors type which
can be: door,
window, perimeter, or
motion.
The name of the
sensor and its brand.
For example SE012
Description about the
specified sensor.
each detector.
Detector type which
can be: flame,
smoke, or heat.
The name of the
detector and its brand
for example SONYHeat 766
Description about the
specified detector.
each failure.
The time the failure
been happened.
The date the failure
been happened
Description of the
failure if necessary.
detection.
Attribute of fire
detection.
X
Attribute of sensor.
X
X
X
X
Attribute of detector.
X
X
X
X
X
X
X
X
Attribute of Mode.
each Mode.
Mode Type
Mode Description
Fire brigade ID
Fire brigade
Name
Fire brigade
location
Fire brigade
phone number
Exhibition ID
Exhibition Name
Exhibition Date
Exhibition Time
Workshop ID
Workshop Name
Workshop Time
Workshop Date
Artist Name
The type of the

security mode which
can be either
Normal-Mode or
Security-Mode.
Description about
each mode and how
they can armed and
disarmed.
each fire brigade.
The name of the fire
department
The location of the fire
department.
Phone numbers of the
fire brigades
Unique identifier for
each exhibition being
hold in the gallery.
The name of the
exhibition
Date when the
exhibition being hold
in the gallery.
Time when the
exhibition being hold
in the gallery.
each workshop being
hold in the Exhibition .
Name of the workshop
Time when the
workshop start
The date when the
workshop being hold.
Artist Full name
Attribute of Mode.
X
Attribute of Mode.
X
X
X
X
X
Attribute of Fire Brigade.

Attribute of Exhibition
X
X
X
X
Attribute of Workshop
X
X
X
X
X
Attribute of Artist
Artist ID
Artist Email

each artist
Artist contact emails
Artist Phone
Number
Artist address
Artist contact
numbers
Artist home address.
Hall
Information about
each hall in the
gallery and their
locations.
each hall.
The location of the
hall in the building
Hall name
Hall ID
Hall Location
Hall Name
Detection Log
Log Date
Log ID
Log Time
Log Description
Consist of data about

any detection (Fire or
Intrusion) been
happened in the
gallery.
Date when log created
each detection log.
Time when the log
created
X
X
X
X
Attribute of Artist
Attribute of Artist
Attribute of Artist
Attribute of Artist
X
X
X
Attribute of Hall
Attribute of Hall
Attribute of Hall
X
X
X
Attribute of Detection
Log
Log
Log
32. Domain Class Diagram of the system
33. Fully attributed database model of the
system (ERD)
34. Cost/Benefit analysis for the system (Net
Present Value, Payback Period)
Cost-Benefits
Analysis
Cash Flow Description
Costs
Development Costs
New Hardware for the computrized system
Year 1
Year 2
Year 3
Year 4
Year 5
-2,400
-1,000
-3,400
-2,400
-1,000
-3,400
-2,400
-1,000
-3,400
-2,400
-1,000
-3,400
-2,400
21,600
3,000
21,600
3,000
21,600
3,000
21,600
3,000
Total Benefits
24,600
24,600
24,600
21,600
3,000
24,60
0
24,600
Net before tax
21,200
21,200
21,200
21,20
0
21,200
17,596
17,596
17,596
17,596
17,596
0.8849
56
0.7561
44
0.6575
16
0.5717
53
0.49717
7
15571.
13305.
11569.
10060.
8748.32
3 Systems Analysts(41 hours/ 2.00 euro)

Total Development Cost
Year 0
-30,000
-246
30,246
Operational and Maintenance Costs

annual maintenance fee
Training Employees on The New System
Total Costs
30,246
Benefits
Saving in Security Guards Salaries
Saving in Insurance premiums
Net After Tax (the tax on profit in this case

is 17%)
-30,246
Discount factors for 13%
Net Present Values
-30,246
-1,000
-3,400

0
-30,246
Years
Accumulated NPV of the Project
1,369
10,200
11,569
964
1.4
68
1
-14,674
1
2
-1,369
66
3
10,200
57
4
20,261
< Change per

year
<Change per
Month
< Month to make value
equal 0
The payback period needs 2 years and 1.4

month
Payback Period
1
35. MS Project file which outlines the schedule,
deliverables and resources

*In the attachments.
2
5
29,009
36. Interview form/forms
INTERVIEW PLAN
PROJECT:
MAG new system
PROJECT MANAGER:
CREATED BY:
Mohammed Abdulla
LAST UPDATED BY:

Alattar
DATE CREATED:
9/5/2013
DATE LAST UPDATED:
Date
9/5/2013
Categor
y
Make Sure
you cover
the PIECES
framework
Question
Reem
10/5/2013
Time
Participant
3:45 PM
MR Momir, Reem
Alattatr
Answer
Requirement
Are they any other

benefits for the gallery
Informati
than the saving in
No there are not
on
guards salaries and
insurance premiums?
How much does the
Informati government apply tax
Apply 17% on the profits
on
on the MAG company
profits?
Informati Is there any discount
Yes, 13%
on
rate factors?
Informati How much do the
on
developers of the new
system get per hour?
Is there any cost of
training employees on
Informati
how to use the new
on
computerized
system ?
Mr. Momir
It depended on you, you can

say around 2 euro.
Yes, 1000 euro annually

Reemali 201000542

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Reemali 201000542

Загружено:

Авторское право:

Доступные форматы

Bachelor of ICT Assessment Cover Sheet

Project in Systems Analysis and Design

Bachelor of Information and Communication

Systems Analysis and Design

By submitting this assessment for marking, either electronically or as

Any information used has been properly referenced.

The code for the database................................................................................... 4

Design use case narrative for Trigger Fire Alarm..............................................11

Design use case narrative for Disarm Security System....................................13

Design use case narrative for Notify Fire Department......................................14

Sequence diagram for Trigger Fire Alarm.........................................................16

Sequence diagram for Disarm Security System...............................................17

Sequence diagram for Notify Fire Department.................................................18

State-chart Diagram for the Fire Sensor object................................................19

State-chart Diagram for the Position object.....................................................20

One state-chart diagram for the Security System object..............................21

Design class diagram for Trigger Fire Alarm..................................................22

Design class diagram for Disarm Security System........................................22

Design class diagram for Notify Fire Department..........................................23

Form prototype Maintain Employee..............................................................24

Form prototype Maintain Fire Detectors........................................................25

Form prototype Maintain Intrusion Sensors...................................................26

Project Request + Problem Statement Matrix.................................................27

Ishikawa Diagram for the problem of your choice...........................................29

Problems, Opportunities, Objectives and Constraints Matrix..........................30

Requirements Model Diagram of the system..................................................31

Use Case Glossary.......................................................................................... 33

Analysis Use Case Model Diagram of the system............................................35

Activity diagram for Trigger Fire Alarm..........................................................42

Activity diagram for Disarm Security System................................................43

Activity diagram for Notify Fire Department..................................................44

Potential Object List + Refined Object List + Proposed Object List.................45

Domain Class Diagram of the system.............................................................53

Fully attributed database model of the system (ERD).....................................54

MS Project file which outlines the schedule, deliverables and resources........56

1. The code for the database

CREATE TABLE System_Failure (

CREATE TABLE Employee (

CREATE TABLE Full-time_Employees (

CREATE TABLE Part-time_Employees (

Hourly_Salary NUMBER NOT NULL,

CREATE TABLE System_Modes (

CREATE TABLE Fire_Brigade (

CREATE TABLE Detection_Log (

CREATE TABLE Fire_Detection (

CREATE TABLE Workshop (

CREATE TABLE Exhibition (

CREATE TABLE Hall (

CREATE TABLE Detector (

Exhibition_ID NUMBER NOT NULL,

CREATE TABLE INTRUSION_DETECTION (

CREATE TABLE Sensor (

CREATE TABLE Artist (

ALTER TABLE Employee ADD CONSTRAINT DEPARTMENT_EMPLOYEE_FK

FOREIGN KEY (Department_ID)

ALTER TABLE INTRUSION_DETECTION ADD CONSTRAINT

REFERENCES Detector (Detector_ID)

2. Design use case narrative for Trigger Fire Alarm

Trigger Fire Alarm

USE CASE TYPE

This use case describes the event of Triggering Fire Alarm.

Step 1: the sensors is

Start Date ___