You are on page 1of 26

HW2-6 DESIGN, ACTIVITY

NETWORK AND TIMELINE


Submitted to:
Ms. Mina Farmanbar
By
Zainab Sada - 149190
Yakubu Abdulrazak - 138859
Oyinbobola Shalom Owojori - 128236

CMSE 201 Introduction to Software Engineering


Instructor: Assoc. Prof. Dr. ALEXANDER G.
CHEFRANOV
in
Faculty of Engineering
Department of Computer Engineering
Eastern Mediterranean University

1. FUNCTIONAL REQUIREMENTS
1.1 USER REQUIREMENTS
1.1.1 The user shall be able to identify oneself as a
registered student on the campus at the present
time.
1.1.2 The user shall have access to view all
available rooms/bed spaces in all dormitories on
campus.
1.1.3 There shall be a means of reserving, secure
payment and verification of rooms.
1.1.4 The system shall store details of old
occupants in a database for purposes like rent
discount and emergencies.
1.1.5 The user shall have a means of
communicating complaints to the managerial staff.
1.2 SYSTEM REQUIREMENTS
1.2.1 The system shall be equipped with a secure
server technology to protect customer details.
1.2.2 The system should be able to accept various
image file as uploads but preferably jpeg files.
1.2.3 The maximum size per documents shall be
35 megabytes to ensure speed of operation.
1.2.4 The system shall be compatible with any
computer device or smartphone of various operating
systems.

2. NON-FUNCTIONAL REQUIREMENTS
2.1 PRODUCT REQUIREMENTS:
2.1.1 Usability Requirements - The system
shall allow users to access the system from
the Internet using HTML or derivative
technologies like XML/CSS. The system uses a
web browser as an interface.
Since all users are expected to be familiar with
the general usage of browsers, no special
training is required. The system shall be user
friendly, the system will also support multiple
languages such as Turkish and English.
The system shall be available 100% for the
user and is to be used 24 hours a day and 365
days a year.
2.1.2 Efficiency Requirements - Even if the
system fails, it will be back up after a
short while
2.1.3 Performance Requirements - The
information is to be refreshed at regular
intervals depending upon whether some
updates have occurred or not
2.1.4 Reliability Requirements - The
system has to be 100% reliable due to the
importance of data and the damages that

can be caused by incorrect or incomplete


data.
2.1.5 Portability Requirements - Changes
shall be verified at least once a day. The
system shall provide automatic
notification to dorm admins by e-mail
about room reservations, overstays and
etc.

2.2 ORGANIZATIONAL REQUIREMENTS:


2.2.1
Implementation Requirements - The
implementation involves dormitory system
installation, user training and maintenance,
ability to cope with any number of rooms,
admins, students, room categories,
currencies, intuitive navigation, and
extensive permissions for staff accounts.

2.3 EXTERNAL REQUIREMENTS:


2.3.1

Legislative Requirements - Personal


information shall be protected. The system
shall comply with quality assurance
standards.

2.3.2
Safety Requirements - The database
may crash at any certain time due to a virus
or operating

system failure, therefore, it is required to


take the database backup and recover
after some time.

3. DOMAIN REQUIREMENTS
3.1 Security
The management system must have an
authorization module to prevent unauthorized
access.
Any authorized user should be able to access the
system 24/7 except the system is under
maintenance
The systems server and database should be
secure
3.2 Performance
The server response speed should be fast
The Graphical User Interface for the management
system should be responsive and easy to use

3.3 The system requires an active internet


connection to be used

1.CONTEXT MODEL

2. SEQUENCE DIAGRAMS

Sequence Diagram To Check if Student is Dormitory Resident

3. USE-CASE DIAGRAM

AUTHENTICATION

EMU DORM SYSTEM LOGIN DATA FLOW DIAGRAM

STATE DIAGRAM
OPERATION

VALIDATE

REGISTERED STUDENT

DO: Check If
The Student Is
Registered
ROOM
AVAILABLE

STUDENT
NOT
REGISTERED

CHECKING
DO: Check For
Available
Rooms

PAYMENT
RECIEVED

RESERVE
DO: Assign
Requested
Room To
Student

CALCULATE
FEE
DO: Calculate
Fee Of Room
And Wait For
Payment

PAYMENT
NOT
RECIEVED

IDLE
ROOM NOT
AVAILABLE

System Waiting For


Instruction

LOGI
N

UNDO
DO: Undo
Room
Assignment
And Redirect

LOGOUT

EMU ONLINE DORMITORY


MANAGEMENT SYSTEM - VALIDATE
VALIDATE

INPUT

SEND

DO: Enter
student name
and student
number

DO: Send
name and
number to the
database

CHECK
DO: Check
name and
number in the
database

NOTREGISTERED
DO: Send denial

REGISTERE
DO:D
Send

from database to
system

STUDENT NOT
REGISTERED
IDLE

confirmation
from database
to system

ROOM
AVAILABLE
CHECKING

REGISTERED
STUDENT
RESERVE

PROBLEM DEFINITION
1.Semantic ER Diagram:An entityrelationship diagram, or ERD, is a chart that visually
represents the relationship between database entities. ERDs model an organizations data
storage requirements with three main components: entities, attributes, and relationships
2.A data dictionary is a collection of descriptions of the data objects or items in a data model for
the benefit of programmers and others who need to refer to them. A first step in analyzing a
system of objects with which users interact is to identify each object and its relationship to other
objects.
3.In objectoriented programming,a class is an extensible programcodetemplate for creating objects,
providing initial values[1][2]
for state (member variables)and implementations of behavior (member
functions or methods).
In many languages, the class name is used as the name for the class (the
template itself), the name for the default constructorof the class (a subroutinethat creates objects), and
as
the typeof objects generated by instantiatingthe class these distinct concepts are easily conflated.
[2]

4.Inheritance (OOP) is when an objector classis based on another object (prototypal


inheritance)or class (classbased inheritance),using the same implementation (inheriting from an
object or class) specifying implementation to maintain the same behavior (realizing an interface
inheriting behavior). It is a mechanism for code reuseand to allow independent extensions of the
original software via public classes and interfaces. The relationships of objects or classes through
inheritance give rise to a hierarchy. Inheritance was invented in 1967 for Simula.
5.In UML, aggregation is shown by an open diamond on the end of the association line
that points to the parent (aggregated) class. There is an implied multiplicity on this end
of 0..1, with multiplicity of the other end shown in the diagram as usual. To describe this
association, we would say that each system is composed of one or more components and
each component is part of zero or one system..

SEMANTIC ENTITY-RELATIONSHIP
DIAGRAM

ADMINISTRAT
OR
Staff ID
First Name
Last Name
Date Of Birth
Email Address
Phone Number
Password
Dorm ID

STUDENT
Student ID
First Name
Last Name
Department
Home Address
Email Address
Phone Number
Password

DORMITORY
Dorm ID
Name
Address

RESERVATION
Booking ID
Student ID
Room ID
Date Of
Reservation
Check In Date
Check Out Date

PAYMENT
Payment ID
Student ID
Booking ID
First Name
Last Name
Credit Card
Number
Expiry Date
Payment Date

ROOM
Room ID
Room Type
Room Description
Dorm ID

ROOM TYPE
Room Type
Room Name
Room Price

DATA DICTIONARY
NAME

DESCRIPTION

TYPE

Administrato
r
First Name

The person that manages the dorms and


registered students
First Name of the administrator

Entity
Attribute

Last Name

Last Name of the administrator

Attribute

Staff ID

Primary Key

Dormitory

Unique identification number for the


administrator
Details of the dorms available

Name

Name of the dormitory

Attribute

Address

Address of the dormitory

Attribute

Dorm ID

Unique identification number for the dorm

Primary Key

Room

Details of the rooms available in each dorm

Entity

Room ID

Unique identification number for the room

Primary Key

Room
Description
Room Type

Specification of the room

Attribute

Details of the types of rooms in each dorm

Entity

Room Price

Price of the room

Attribute

Student

The person that reserves and pays for a room

Entity

Student ID

Unique identification number for the student

Primary Key

Reservation

Details of reservation

Entity

Booking ID

Primary Key

Payment

Unique identification number for the reservation


with reference to student
Details of payment made by the student

Credit Card
Number
Expiry Date

Credit card number the student used to pay for


the room
Date that the credit card will expire

Attribute

Entity

Entity

Attribute

3.

Classes Definition
Student
First name: String
Middle name:
Student
String
Last name: String
Date of Birth: Date
Department: String
Student number: Integer
Nationality: String

Register()
Signin()
Signout()
Checkroom()
Reserveroom()
Checkprice()
Pay()

Staff
Admin
First name: String
Middle
name: String

Last name: String


Date
of Birth: Date
Signin()
Nationality:
Signout() String
Marital
Status: {Married,
Checkresidentstatus()
Single}
Addresident()
Status:
{current, left,
Removeresident()
retired}
Assignroom()
Salary:
Integer
Viewcomplaints()
Updatestaff()
Updateresident()
Signin()
Signout()
Join()
Leave()
Retire()

4. Inheritance Diagram

Use
Employee

Student

salary
employmentSt
atus

residencyStat
us

Manager

Cleaners

Technicians

responsibilit
ies

roomsAssig
ned

appliancesMaintai
ned

Admin
Manager
staffControlle
d
budgetsContr

System
Manager
repairs

AGGREGATION DIAGRAM

EMU DORM MANAGEMENT SYSTEM SPECIFICATION(EDM).


EDM is a system which allows registered students in EMU to login and gain access to
information about the dormitories on campus.information collected by the system from
the users(students or administration)and other sources such as the university
database.information is only displayed in response to user request.
The system after receiving a request checks requirements,analyzes it then finally
verifying it before granting access to services provided by EDM based on type of
user.student users can view available rooms,reserve a room,make payments.lay
complaints etc.administrative users and dorm employees can check complaints , check
for repairs,shifts etc.

PERFORMANCE
The load time for user interface screen takes no longer two seconds.
The login information is verified within five seconds.
The systems consumes very little primary memory.
SECURITY
Access to various subsystems are protected by a user login screen which requires a
valid user-id.
AVAILABILITY
The system is available 24/7 during the academic session.
MAINTAINABILITY
EDM is developed in java,java is an object oriented programming language and is
easy to maintain.
PORTABILITY
EDM run on any pc,tablet or phone that contains java Runtime.

ACTIVITY NETWORK

LOGIN

ACCOUN
T
INQUIRY
ABOUT
ROOM
CHECK
AVAILABILITY
OF ROOM
NOT

AVAILABLE

VALIDATE
STUDENT

STUDENT
REGISTERED

STUDENT
NOT
REGISTERED

RESERVE
ROOM

REQUES
T
PAYMEN
UPDATE
ROOM
STATUS

NOT RECIEVED
RECIEVED

ROOM NOT
AVAILABLE

NO

ACTIVITY

TIME
(SECON
DS)

DEPENDENCI
ES

Login

Account

Inquiry About
Room

18

Check Availability

40

5,6

Room Not
Available

Validate Room

5,7

Reserve Room

60

Request Payment

15

5,9

Update Room
Status

ACTIVITY TIMELINE
Secon
ds

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

Start
Login
Account

Inquiry about
room
Check Availability

Room not available

Validate room

Reserve
room
Request
payment
Update room
status
Finish

Secon
ds

Bob

10

20

30

40

50

60

70

80

90

100

110

120

130

140

150

Login
Account

Michae
l

Inquiry about
room
Check Availability
Room not available
Validate room

Ekrem

Reserve
room

Yasemi
n

Request
payment

Update room
status

STAFF ALLOCATION