Академический Документы
Профессиональный Документы
Культура Документы
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
2.3.2
Safety Requirements - The database
may crash at any certain time due to a virus
or operating
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
1.CONTEXT MODEL
2. SEQUENCE DIAGRAMS
3. USE-CASE DIAGRAM
AUTHENTICATION
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
LOGI
N
UNDO
DO: Undo
Room
Assignment
And Redirect
LOGOUT
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]
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
Entity
Attribute
Last Name
Attribute
Staff ID
Primary Key
Dormitory
Name
Attribute
Address
Attribute
Dorm ID
Primary Key
Room
Entity
Room ID
Primary Key
Room
Description
Room Type
Attribute
Entity
Room Price
Attribute
Student
Entity
Student ID
Primary Key
Reservation
Details of reservation
Entity
Booking ID
Primary Key
Payment
Credit Card
Number
Expiry Date
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
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
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
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