Itb6001 Project Part 1 Class 01 Idesign System

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:
Taiba Husain Abeer Alrumaidh Wejdan Yusuf
Student ID:
201200394 201100984 - 201100025
Tutor:
Momoir Radicevic
Due Date:
27/04/2014
Date submitted:
27/04/2014
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.
I have kept a copy of this assignment
Do not write below this line. For Polytechnic use only.
Assessor:
Date of Marking:
Grade/Mark:
Comments:
Contents
Introduction.............................................................................................................................................4
1.
Request for Systems Services ..........................................................................................................5
2.
Problem Statement Matrix..............................................................................................................7
3.
Ishikawa Diagram ............................................................................................................................8
4.
Problems, Opportunities, Objectives and Constraints Matrix ........................................................9
5.
Functional and non-functional requirements .......................................................................... 1011

5.1
Functional requirements diagram ........................................................................................ 11
5.2
Non-Functional requirements diagram ................................................................................ 11
6.
Actor Glossary .............................................................................................................................. 12
7.
Use Case Glossary......................................................................................................................... 13
8.
Analysis Use Case Model Diagram ............................................................................................... 16
9.
Analysis use case narrative........................................................................................................... 17

9.1 Use case narrative for the Add Maintenance Request use case .............................................. 17
Actor Action.......................................................................................................................................... 17
System Response .................................................................................................................................. 17
9.2 Use case narrative for the Assign Job use case ........................................................................ 18
Actor Action.......................................................................................................................................... 18
System Response .................................................................................................................................. 18
9.3 Use case narrative for the Resolve Maintenance Request use case ........................................ 19
Actor Action ...................................................................................................................................... 19
System Response ........................................................................................................................... 19
10.
Activity diagram........................................................................................................................ 21
10.1 Activity diagram for Add Maintenance Request .................................................................... 21

10.2 Activity diagram for Assign Job .............................................................................................. 22
10.3
Activity diagram for Resolve Maintenance Request .......................................................... 23
11.
Potential Object List + Refined Object List + Proposed Object List .......................................... 24
12.
Domain Class Diagram of the system ....................................................................................... 26
13.
Fully attributed database model of the system (ERD) ............................................................. 27
14.
Cost/Benefit Analysis................................................................................................................ 28
2
15.
MS Project file ...................................................................................................................... 3029
16.
Interview forms .................................................................................................................... 3131
Conclusion ........................................................................................................................................ 3333
Introduction
This project was requested by Mr. MomoirRadicevic an ICT tutor within Bahrain Polytechnic. Its due
date is on Sunday 27/04/2014.
The project is about a company called The House Maintenance Ltd (HML) which provides various
maintenance services to householders. The existing system of the company is based on the use of
spreadsheets. This system caused many problems for the company including loss of time and
money. Therefore, the company needs to replace the existing system with a new computerized
system. The new system should be able to provide the maintenance of position records and
employee records. Moreover, it should be able to track the status of workers.
1. Request for Systems Services

The Home Maintenance Ltd (HML)
Phone:00973-17586999
Fax: 00973-17607080
DATE OF REQUEST
01/04/2014
SERVICE REQUESTED FOR DEPARTMENT(S)

-
Service department
SUBMITTED BY (key user contact)
EXECUTIVE SPONSOR (funding authority)
Name: Abeer
Title: Coordinator
Office: 109, Bldg. 36A
Phone: 00973-17552544
Name: Momir Radicevic

Title: Tutor
Office: Bldg.26
Phone:00973-33478826
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)
The Home Maintenance Ltd (HML) uses a spreadsheets based system. Due to the growth in number of new customers, service
requests and newly employed workers, the existing system became incapable to handle the growth. This causes several problems.
Firstly, the time to record a maintenance request and the time to assign a job to a worker was increased which leads to loss of time.
Moreover, the administrative tasks are done after the regular working hours and it costs the company more as overtime is paid
which leads to loss of money.
BRIEF STATEMENT OF EXPECTED SOLUTION

Develop a computerized system for HML to replace the existing spreadsheets based system to provide services
effectively and save time and money. The system should also provide the opportunity to maintain position records
and employee records. In additions, it should provide the opportunity to track the status of workers.
ACTION (ISS Office Use Only)

Feasibility assessment approved
Assigned to _ Abeer _
Feasibility assessment waived
Approved Budget $ _______3000______

Start Date 01/04/2014 Deadline 25/05/2014
Request delayed
Backlogged until date: ______________
Request rejected
Reason: ________________________________________________
Authorized Signatures:
_Abeer, Taiba, Wejdan______________________
________ Momir Radicevic____________________

Project Executive Sponsor
2. Problem Statement Matrix
PROJECT: HML property maintenance system
PROJECT MANAGER: MomirRadicevic
CREATED BY:
LAST UPDATED BY: Wejdan Yusuf
Wejdan Yusuf
DATE CREATED: 02/04/2014
Brief Statements of Problem,
DATE LAST UPDATED: 08/04/2014
Urgency
Visibility
Opportunity, or Directive
1. The growth in number of
new customers, service
requests and newly
employed workers.
Annual
Priority
Proposed
Benefits
or Rank
Solution
Develop new
3 months
High
In the
system
thousands.
2. Assigning each service

request requires 14
minutes.
3 months
3. Anna cannot get a worker

on the phone for assigning
a job.
3 months
4. The administrative tasks

are done after the regular
working hours.
3 months
High
In the
computerized
Develop new
computerized
thousands.
system
High
In the
Develop new
computerized
thousands.
system
High
In the
thousands.
Develop new
computerized
system
3. Ishikawa Diagram
Ishikawa Diagram Template (6 Ms )
Manpower
Machines
Methods
Traditional old system
Shortage of workers
Database system
Based on spreadsheets
Incensement of customers
Poor management skills
No enough space
in the system
System is incapable
to handle The growth
The database system is
Limited to 2000 properties
and not enough
Improper system design
Poor maintenance
Growth in service
requests per day
The database not enough
They didn't take into

account the future expansion
Poor management
Materials
Mother Nature
Measurements
Problem growth in number of

Customers, service request,
workers
4. Problems, Opportunities, Objectives and Constraints Matrix

Project:The Home Maintenance Ltd
Project Manager:MomirRadicevic
Created by: Taiba Husain
Last Updated by: Taiba Husain
Date Created: 31-Mar-2014
Date Last Updated: 08-April-2014
CAUSE AND EFFECT ANALYSIS
1.
SYSTEM IMPROVEMENT OBJECTIVES
Problem or Opportunity
Causes and Effects
The growth in number of

new customers, service
requests and newly
employed workers.
Causes:
1. The existing system is based on
the use of spreadsheets.
2.
3.
System Objective
1. Develop a new computerized
system that use the relational
DBMS to efficiently capture,
store, process and retrieve
data on properties, owners of
the properties, property
maintenance contracts the
owners signed with the
company, and the
maintenance requests.
The company has a database of

2000 properties which is limited
and not enough.
The system is incapable to handle
the growth.
Effects:
2.
Assigning each service

request requires 14
minutes.
1.
The time to record a single

maintenance request increased for
more than five minutes.
2.
The time to assign a particular job

to a skilled worker rose from two
to four minutes.
Causes:
1. 35 service requests per day.
2.
Old system.
Effects:
1.
Consumes all of Annas daily

time.
1.
New computerised system that use

Oracle11g, Standard Edition
DBMS or Microsoft SQL Server
DBMS.
System Constraint
1. Development
time
2. Costs
3. Success metrics
2.
Development
time
3.
Costs
3.
Success metrics
3. Anna cannot get a

worker on the phone for
assigning a job.
Causes:
1.
1.
Old style system.
2.
Unavailable workers.
2.
Effects:
4.
The administrative tasks

are done after the regular
working hours.
1.
Confusion among the

workers and contributes
to the company
embarrassment.
2.
Waste of money because

of unnecessary trips.
3.
Four multiple trips per

week each of them
costing the company $40.
1.
Causes:
1.
The maintenance services are

of the highest priority.
Develop a new system that

provides the maintenance of
position records and employee
records.
The system should track the
workers status to avoid
confusion.
The new system will provide

saving of 70% in Annas salary.
Effects:
1.
The administrator Anna works

for two additional hours per
day.
2.
It costs the company more as

overtime is paid at 1.5 times
the regular hourly rate.
5. Functional and non-functional requirements
10
1.
2.
3.
2.
3.
4.
Development
time
Costs
Success metrics
Development
time
Costs
Success metrics
5.1 Functional requirements diagram

EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version
req Functional
EA 10.0 Unregistered Trial Version

EA 10.0
Unregistered Trial Version
Add maintenance
request
New computerized
system
Assign job to worker
EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version
Resolve maintenance
request
Create new client

EA records
10.0 Unregistered Trial Version
Maintain position
Maintain employee records
Edit client details
Edit employee's
detailsUnregistered Trial Version
EA 10.0 Unregistered
Trial Version
EA 10.0
Trial Version
10.0 Unregistered
Trial Version
EA 10.0
Unregistered
Trial
VersionE
Trial Version
EA 10.0 EA
Unregistered
Trial Version
EA 10.0
Unregistered
Trial
Version
5.210.0
Non-Functional
requirements
diagram
EA
Unregistered Trial
10.0
Unregistered Trial Version EA 10.0 Unregistered Trial Version
Trial Version Version
EA 10.0 EA
Unregistered
Trial Version EA 10.0 Unregistered Trial Version E
req Non Functional

EA system
10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version E
New computerized
EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial Version E
Opportunity to track status of
workers
EA 10.0 Unregistered Trial Version EA 10.0 Unregistered Trial
Able Version
to store different
employee details
Access rights
Trial Version
EA 10.0 EA
Unregistered
Trial Version
EA 10.0
Unregistered
Trial
Version
Trial Version
10.0 Unregistered
Trial Version
EA 10.0
Unregistered
Trial
VersionE
Trial Version
EAto10.0
Unregistered
Trial Version
EA 10.0
Unregistered
Trial
Version
Trial easy
Version
EA
10.0 Unregistered
Trial Version
EA 10.0
Unregistered
Trial
VersionE
use
Cost and benifit
Trial Version
EA 10.0 EA
Unregistered
Trial Version
EA 10.0
Unregistered
Trial
Version
Trial Version
10.0 Unregistered
Trial Version
EA 10.0
Unregistered
Trial
VersionE
Trial Version
10.0 Unregistered
Trial Version
EA 10.0
Unregistered
Trial
VersionE
Trial Version
EA 10.0 EA
Unregistered
Trial Version
EA 10.0
Unregistered
Trial
Version
Trial Version
10.0 Unregistered
Trial Version
EA 10.0
Unregistered
Trial
VersionE
Trial Version
EA 10.0 EA
Unregistered
Trial Version
EA 10.0
Unregistered
Trial
Version
EA 10.0 Unregistered Trial Version EA 10.0 11
Unregistered Trial Version EA 10.0 Unregistered Trial Version
6. Actor Glossary
Actor Name
Manger
Administrator
Actor Description
Manager is a kind of employees , The Manger in this system will be
able to login the system , Maintain financing , Maintain Marketing and
managing HML company
Administrator is a kind of employees , This Administrator in this system
will be responsible on Maintaining employees , assigning jobs to
workers , Maintaining owner , Maintaining property , Maintaining
request , Maintaining skills , Maintaining positions and she will have
the ability to log into the system
Quality Inspector
Quality Inspector is a kind of employees , this inspector will check the

quality of work and will observe the workers
Worker
Worker is a kind of employees , the worker will be the one who work
on the maintenance job in the property based on the jobs that are
assigned to him by administrator and after he is done with the job , he
will resolve it
Owner
He is the person who place a maintenance job request from the

company
12
7. Use Case Glossary

Use-Case Glossary
Use-Case Name
Use-Case Description
Login
This use case describes the event of

logging in to the system.
Hire worker
This use case describes the event of hiring

new workers in the company.
editing details of existing worker.
deleting worker.
displaying the details of an existing worker.
storing details of workers.
tracking worker status.
assigning a job to a skilled worker.
sending a message to worker of assigning
job.
adding a new maintenance request.
deleting a maintenance request.
retrieving maintenance request.
updating maintenance request.
resolving a maintenance request.
adding new owner to the system.
editing owner details.
Edit worker details

Delete worker
Display worker details
Store worker details
Track worker status
Assign job
Send message
Add Maintenance Request

Delete Maintenance
Request
Retrieve Maintenance
Request
Update Maintenance
Request
Resolve Maintenance
Request
Add new owner
Edit owner details
13
Participating
Actors and Roles
Manager\ Admin
clerk\ Quality
inspector\Worker
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Worker
Admin clerk
Admin clerk
Delete owner

deleting an existing owner.
retrieving owner.
tracking workers status.
Admin clerk
Manage HML
This use case describes the event of managing

the HML company.
Manager
Create financing

creating financing.
accounting receivables and financing.
updating financing.
deleting financing.
creating marketing.
retrieve marketing.
updating marketing.
This use case describes the event
ofdeleting marketing.
This use case describes the event ofadding
position.
retrieving position.
updating position.
deleting position.
checking quality of work.
watching and observing workers.
placing maintenance request.
adding skill.
Manager
Retrieve owner
Track worker status
Retrieve financing
Update financing
Delete financing
Create marketing
Retrieve marketing
Update marketing
Delete marketing
Add position
Retrieve position
Update position
Delete position
check quality of work
Observe workers
Place maintenance request
Add skill
14
Admin clerk
Admin clerk
Manager
Manager
Manager
Manager
Manager
Manager
Manager
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Quality inspector
Quality inspector
Owner
Admin clerk
Delete skill
Retrieve skill
Update skill
Add property
Retrieve property
Update property
Delete property

deleting skill.
retrieving skill.
updating skill.
adding property.
retrieving property.
updating property.
deleting property.
15
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
Admin clerk
8. Analysis Use Case Model Diagram
uc Use Case View

HML System
Edit worker
details
Display worker
details
Hire worker
Delete worker
extend extend
extend
extend
Add new owner
include
Retriev e owner
extend
extend
Maintain
employee
Admin clerk
Assign job to
worker
Store worker
details
extend
extend
Track worker
status
Send message
Update owner
Maintain owner
extend
extend
Delete owner
Update property
Add property
Employee
extend
Login
extend
Create financing
record
extend
Maintain
property
retriev e financing
record
extend
Maintain financing
extend
extend
extend
Update financing
record
extend
extend
Delete maintenance
request
Retriev e
property
Retriev e
maintenance request
Delete property
Maintain
requests
extend
extend
Delete financing
record
Add Maintenance
Request
extend
Manager
Update marketing
record
Maintain
marketing
Update
maintenance
request
extend
Maintain positions
extend
Delete marketing
record
extend
extend
Create marketing
record
extend
Retriev e
marketing record
extend extend
extend
Maintain skills
Add position
extend
extend
Retriev e position
Delete position
extendextend
Update position
Add skill
Update skill
Retriev e skill
Manage HML
company
Delete skill
Quality inspector
Observ e workers
check quality of work
Owner
Worker
Place maintenance
request
Resolv e Maintenance
Request
16
9. Analysis use case narrative

9.1 Use case narrative for the Add Maintenance Request use case
{Add Maintenance Request}
Author (s):
Wejdan Yusuf
Date:
10/04/2014
Version: 1
Version: 1
USE CASE NAME:
Add Maintenance Request
USE CASE ID:
HML 001
PRIORITY:
High
USE CASE TYPE
SOURCE:
ACTORS:
Business Requirements:
System Analysis:
System Design:
Admin clerk
OTHER PARTICIPATING
ACTORS:
STAKEHOLDERS:
DESCRIPTION:
This case will describe how to add maintenance request for the owner.
PRE-CONDITION:
The system is already logged in.
TRIGGER:
How to add a new maintenance request in the system.
TYPICAL COURSE
Actor Action
System Response
OF EVENTS (FLOW OF
Step 1: Choose Add maintenance
Step 2: The system displays the list of
ACTIVITIES):
request option from the main
information that the user should enter into the
menu.
system.
Step 3: Fill the information of the

request (request id, request type,
request date, owner id and etc.).
Step 4:press ok to confirm.
Step 5: The system will add the maintenance

request into the database system.
ALTERNATE COURSES
Step 3a: If the owner id is not registered, The clerk will invoke the add owner use case.
(EXCEPTION CONDITIONS):
CONCLUSION:
Maintenance request had been successfully implemented in the database system.
POST-CONDITION:
Maintenance request and maintenance request must be created.

Maintenance request must be add in the database system.
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS AND
SPECIFICATIONS
17
ASSUMPTIONS:
OPEN ISSUES:
9.2 Use case narrative for the Assign Job use case
Assign job
Author (s):
Taiba Husain
Date:
10/04/2014
Version: 2
USE CASE NAME:
Assign Job
USE CASE ID:
HML11002
PRIORITY:
High
USE CASE TYPE
SOURCE:
ACTORS:
System Analysis:
System Design:
Administrator Anna
OTHER PARTICIPATING
ACTORS:
STAKEHOLDERS:
DESCRIPTION:
PRE-CONDITION:
This use case describes the event of assigning a job to a skilled worker. When
administrator choose assign job the system display the requests list, display employees
list, assign job to the employee and finalize the process.
The administrator must be logged in to the system.
TRIGGER:
Starts when the administrator select assign job option from main menu
TYPICAL COURSE
Actor Action
System Response
OF EVENTS (FLOW OF
Step 1: The administrator selects
Step 2: The system invokes Load list of
ACTIVITIES):
Assign job option from the main
requests use case and then displays the list of
menu.
the requests on the assign job screen.
Step 3: Administrator selects the
Step 4: System displays the details of the
required request from the list.
request form (the required skills and

qualifications).
Step 5: System displays list of all employees
with the required skills.
Step 6: Administrator pick up an
Step 7: the system displays the employees
employee from the list.
details.
Step 8: Administrator verifies the

employees details.
Step 9: Administrator press Assign
Step 10: The system assign the employee with
button.
the job request and end the use case.

Step 11:Display successful message and send a
message to the worker.
18
ALTERNATE COURSES
Step 3.a: if the request is not exist, then the administrator invokes Add maintenance
(EXCEPTION CONDITIONS):
request use case. Resume at Step 4.

Step 6.a: if the status of the selected employee is not available, then the administrator
picks up another available employee. Resume at step 7.
Step 8.a: if any changes are required, the administrator invokes Edit employee details
use case. Resume at step 9.
CONCLUSION:
The system will assign the selected employee with the job request.
POST-CONDITION:
The job assigned to the worker successfully.
BUSINESS RULES
None
IMPLEMENTATION
The job should not be assigned to two workers to avoid confusion.
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS:
None
OPEN ISSUES:
None
9.3 Use case narrative for the Resolve Maintenance Request use case
HML
Author (s):
AbeerAlRumaidh
Date:
10/04/2014
Version: 001
USE CASE NAME:
Resolve Maintenance job
USE CASE ID:

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

System Analysis:
System Design:
Worker
The Worker will resolve the maintenance job by entering the end date of the project
The System is Working
The worker is already logged in
Select Resolve Maintenance job
Actor Action
System Response
Step 1:Click on Resolve Maintenance job

from the main menu
Step 2: Ask the Worker to enter the record ID
Step 3: Enter the record ID
Step 4 : check the Status of the job

Step 5 : Display the list of all the information of record with
the information that are needed to be filled
Step 6: Enter all the required information into

the system
Step 7: Click Ok to update the record
Step 8 : Information will be saved in the record

Step 9 : Confirmation will be displayed The information
record is updated
ALTERNATE COURSES
(EXCEPTION
CONDITIONS):
Confirm the update by displaying The information record is updated
Step 3A : if the record ID dose not exists then the user should re-enter the ID again
19
Step 4A : if the record is already done , a message will be displayed for the user (Record ID that that you
have chosen is already done) then take him back to step3
CONCLUSION:
POST-CONDITION:
BUSINESS RULES
IMPLEMENTATION
CONTRAINTS AND
SPECIFICATIONS
ASSUMPTIONS:
OPEN ISSUES:
The Employee will resolve the maintenance job by filling all the important informations
The Quality investigator will check the quality of the work
None
None
20
10. Activity diagram

10.1 Activity diagram for Add Maintenance Request
sd Dynamic View
Actor
System
ActivityInitial
Displays the list of information required
Choose: 'Add Maintenance Request' from the main

menu
Fill the information of the request
Is the owner registered?

[Yes]
[No]
Press 'Ok' to confirm
Inv oke: the add ow ner

use case
Add the maintenance request into the

database system
Add successfully in the datasbase
ActivityFinal
21
10.2 Activity diagram for Assign Job

sd Dynamic View
Administrator
System
Select "Assign j ob" option

from the main menu
Inv oke "Load list of requests" use case and display the
list of requests on assign j ob screen
ActivityInitial
Select the required

request from list
request
exist?
[No]
[Yes]
Inv oke "Add

maintenance request"
use case
Display the details of the request form(the

required skills and qualifications)
Display list of all employees

w ith the required skills.
Pick up an employee
from the list
[No]
Is the
employee
available?
[Yes]
Pick up another
av ailable
employee
display the employee's details: ID,

name, status and his skills
v erify the employees details
[Yes]
require
changes?
inv oke Edit employee

details use case and
make changes
[No]
Press Assign button

assign the employee w ith the j ob
request and end the use case
Display successful message and

send a message to the w orker.
ActivityFinal
22
10.3 Activity diagram for Resolve Maintenance Request

sd Dynamic View
Worker
System
ActivityInitial
Choose Resolv e Maintenance j ob

from main menu
Promote the user to enter record ID
Enter the record ID
[NO]
Message (Record ID that

that you hav e chosen is
already done)
Record ID dose exists ?
[Yes]
Dispaly all the information of the record

w ith the needed information to be filled
check the Status of the j ob
Record is already done
Fill all the requeired informations
Click 'OK'
Sav e the inforamtion in the system
Confirm the update by displaying The

information record is updated
ActivityFinal
23
[Yes]
11. Potential Object List + Refined Object List + Proposed Object

List
Potential Object
Object
Notes
Reason
Worker
A person who is working in the company
Worker ID
A unique identifier for each worker
Attribute of Worker
Worker Full Name
The name of the worker
Attribute of Worker
Worker Phone
The worker phone number
Attribute of Worker
Worker Email
The email of the worker
Attribute of Worker
Owner
The person who request a maintenance job
Owner ID
A unique identifier for each Owner
Attribute of Owner
Owner Full Name
The Owner name
Attribute of Owner
Owner Phone
The Owner phone number
Attribute of Owner
Owner Email
The Owner email
Attribute of Owner
The request will be used by the company to know what is
Maintenance Request
the maintenance job
Request ID
A Special number to identify the requests from each other
Attribute of Maintenance Request
Request Date
The date of the request
Request Type
The type of the request (Paint,Flooring,etc)
Property
It is a place that the owner may live in or just own
Property ID
The Property Special number
Attribute of Property
Property Type
The property type ex (flat, house, etc.)
The number of rooms in the Property (rooms, bathrooms,
Where is the Property is located
It is the record that will save the whole details of the
Number Of Rooms
Property Location
Maintenance Job Record
etc.)
processes of the job
Record ID
An exclusive identifier for each recorded
Attribute of Maintenance Job Record
Start Date
That start date of the job
End Date
The end date of the job
Hours Worked
The number of hours that the worker work in this job
The rate of money that the user will receive after
Hourly Rate
Job Description
completing the job

Is brief information about the job
24
Skill
It the skill that is required for the job
Skill ID
Each skill will have an ID so that the user identify the skill
Attribute of Skill
The skill name to know what is the required skill (Flooring,
Attribute of Skill
Skill Name
Painting, etc.)
The person who have access to the database, manage all
Administrator
the workers and requests details and handle all the
company responsibilities.
Company Owner
Quality Inspector
Laptop
Desktop
Server
Processor
RAM
Operating System
Standard Tools
Internet Browser
Email
Monitor
Virus Protection
Optical Drive
Printer
LAN
The person who owns the company and handle the

company's financing and marketing functions
The person that check the quality of the maintenance work
that is done by the workers
It is a portable personal computer , suitable for mobile use.
It is a personal computer , that can be used in a specific
place due to its size

It is a system that responds to all the requests from the
computer network or provide a network service
The Processing unit of the device
Attribute of Laptop , Desktop and Server
Random access memory that save the data while the device
Attribute of Laptop and Desktop
It is an application that protect the computer from viruses
A device that use light to read and write information
Attribute of Server
is working (Temporary Memory)

It is a collection of software that control the device
hardware and manage the computer programs
It is the application that the device need such as (MS
Windows 7 pro)
It is a software that help the user to browse the world wide
web
It is an electronic mail that is used to exchange digital
messages
Its a display device that display a visual display of the
computer operations
(Storage device)
It is a device the transform an electronic document to
physical media
A Computer network that link computers network in a
limited area
25
12. Domain Class Diagram of the system
class Class Model
Manager
Maintenance_Request_record
1..* -
Add
Employee
1..* -
brief_description :String
end_date :date
request_id :int
Request_title :String
start_date :date
Admin clerk
Employee_email :String
Employee_id :int
Employee_phone :int
F_name :String
L_name :String
1
1
create
Job_Request
1..* -
assign
0..1
Date_Of_Request :Date
Date_Of_Resolution :int
Request_Desc :String
Request_ID :int
1..*
1..*
Login Credentials
0..*
Job_assignment
call and place
-
Date :date
job_assignment_ID :int
worker_information :String
1
Property
Ow ner
include
-
Message
Owner_Email :String
Owner_FullName :String
1
Owner_ID :int
Owner_Phone_Number :int
own
1..*
-
address :String
property_description :String
property_id :int
held by
Worker
Skill
Quality inspector
has
Observe
1
1..* -
1..*
1..*
skill_id :int
skill_title :String
1..*
w orker_skill
1
Position
need
0..*
26
13. Fully attributed database model of the system (ERD)
27
14. Cost/Benefit Analysis
28
29
15. MS Project file
30
16. Interview forms

Interviewee:MomirRadicevic
Date: 09/04/2014
Time: 1:00 pm to 1:30 pm
Place: 26-106
Subject: project interview
Time
Interviewer questions and objective
Allocated
1 minute
Interviewee
Response
Objective
Open the interview
2 minutes
Introduce ourselves
Thank Mr. Momir for his
valuable time
State the purpose of the
interview
Question1
What is the allocated budget
Development costs $3000 in year 0
of the new computerized

system?
3 minutes
Question2
Do your own calculations
In the problem statement

matrix, how can we calculate
the annual benefit?
3 minutes
Question3
Anna and employees, same rights
For the new system, who will

be able to manage the
employee records? The
employees will have the same
access rights?
4 minutes
Question4
ID, first name, last name, status, salary,
What are the details that will

be stored about the
employees?
31
etc
2 minutes
Question5
39%
What is the tax rate?

2 minutes
Question6
What is the discount factor?
3 minutes
Question7
17%
Yes about the new system, you can do it
Are the functional and non-
with word or enterprise.
functional requirements will

be about the new system?
And do we have to do it on
Enterprise Architecture or in
a table?
5 minutes
2 minutes
Question 8
Select the request and look at the required
On the new computerized system,
skills, pick up the employee with the right
how will be the method of assigning a
skills from combo box and assign it with
job to a worker?
request.
Question 9
There are 40 license, you have to search
What are the costs of Oracle lessons?
about the oracle license price and calculate

the fees for each license.
2 minutes
Question 10
$18 hourly rate
What are the operating salaries?

1 minute
Objective
Conclude the interview
30
Thank Mr. Momir for his

cooperation and help.
Assure Mr. Momir that he will
receive a copy of a letter
summarizing the interview
Time allocated for questions and
objectives
Time allocated for follow-up
questions
30 minutes
Time allocated for interview

32
Conclusion
To conclude, the HML Company is able now to create the new computerized system and to replace
the existing traditional system.
33

Itb6001 Project Part 1 Class 01 Idesign System

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Itb6001 Project Part 1 Class 01 Idesign System

Hochgeladen von

Copyright:

Verfügbare Formate

Bachelor of ICT Assessment Cover Sheet

Project in Systems Analysis and Design

Bachelor of Information and Communication Technology

Systems Analysis and Design

Taiba Husain Abeer Alrumaidh Wejdan Yusuf

201200394 201100984 - 201100025

This assignment is my own work

Do not write below this line. For Polytechnic use only.

Request for Systems Services ..........................................................................................................5

Problem Statement Matrix..............................................................................................................7

Ishikawa Diagram ............................................................................................................................8

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

Functional and non-functional requirements .......................................................................... 1011

Functional requirements diagram ........................................................................................ 11

Non-Functional requirements diagram ................................................................................ 11

Actor Glossary .............................................................................................................................. 12

Use Case Glossary......................................................................................................................... 13

Analysis Use Case Model Diagram ............................................................................................... 16

Analysis use case narrative........................................................................................................... 17

10.1 Activity diagram for Add Maintenance Request .................................................................... 21

Activity diagram for Resolve Maintenance Request .......................................................... 23

Domain Class Diagram of the system ....................................................................................... 26

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

MS Project file ...................................................................................................................... 3029

Interview forms .................................................................................................................... 3131

Conclusion ........................................................................................................................................ 3333

1. Request for Systems Services

SERVICE REQUESTED FOR DEPARTMENT(S)

SUBMITTED BY (key user contact)

EXECUTIVE SPONSOR (funding authority)

Name: Momir Radicevic

TYPE OF SERVICE REQUESTED:

Information Strategy Planning

Existing Application Enhancement

Business Process Analysis and Redesign

Existing Application Maintenance

Other (please specify

BRIEF STATEMENT OF EXPECTED SOLUTION

ACTION (ISS Office Use Only)

Feasibility assessment waived

Approved Budget $ _______3000______

Backlogged until date: ______________

________ Momir Radicevic____________________

2. Problem Statement Matrix

PROJECT: HML property maintenance system

PROJECT MANAGER: MomirRadicevic

LAST UPDATED BY: Wejdan Yusuf

DATE CREATED: 02/04/2014

Brief Statements of Problem,

DATE LAST UPDATED: 08/04/2014

2. Assigning each service

3. Anna cannot get a worker

4. The administrative tasks

Ishikawa Diagram Template (6 Ms )

Poor management skills

Improper system design

They didn't take into

Problem growth in number of

4. Problems, Opportunities, Objectives and Constraints Matrix

Created by: Taiba Husain

Last Updated by: Taiba Husain

Date Created: 31-Mar-2014

Approved Budget $ _3000

Momir Radicevic____________