Diagram representing the system architecture for ALFA A/S :-
Client interface
Application
Database
Client Interface: The Client Interface architecture interacts with the application
layer. By communicating with application it gives information to application and
retrieves the response from the application layer.
Application Layer: The application layer communicates with both the client
interface as well as with the database server. It takes the information from client interface
and transfers to the database making some implementations and can also retrieve
information from the database, make executable operations and gives back to the client
interface.
Database: The database contains secured data which is linked to the programming
(application layer). The data will be passed to different parts of the system. It is also
possible sometimes to update the data in the database through the application layer by
implementing the program.
USE CASE DESCRIPTIONS:
1) User login
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
User login
User, system
Check the authenticity of the user.
-User enters his own login identity and the password in
GUI. The database is checked for authenticity.
If the correct match is found in database GUI allows the
user to enter into the system.
-If login is failed , an error message will be displayed and
then GUI allows the user to re-enter the login name and
password.
Only registered employee can login. The user id and
password should be present in the database of ALFA A/S
organization
None
Upon successful login the user can have access to the
system.
Primary
None.
2) User logout
Use case name
Actors
Purpose
Flow of events
a)Basic Flow
User logout
User, system
To save the changes and exit the user access.
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
- None
-None
The user must be logged in
Logout message is displayed on the GUI. A link appears
through which the user can login again.
Secondary
None.
Priority
Extension Points
-GUI allows the user to exit the system and a message is
displayed confirming his status.
3) EmployeeInfo
Use case name
Actors
Purpose
Flow of events
b) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
EmployeeInfo
Employee, Database
To maintain the employee details
-Authorized user requests the database to retrieve the
particular employee information by giving the employee
name.
-If the database finds no match an error message will be
displayed.
Employee information, name, employee id, status, email,
etc., must be present in the database
-user must be logged in
Employee information will be displayed on the screen with
a link to go back to employee search.
Secondary
None
4) CreateNewEmployee
Use case name
Actors
Purpose
Flow of events
a)Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
CreateNewEmployee
Manager, database.
To create a new employee database by the manager only by
adding the employee information to the database.
-Manager can find link to create the new employee
information which consists an html page asking for all the
details of the new employee. The database will be updated
-None.
Only the manager can add the information of the new
employee to the database, so the user must be manager.
-The logged in user id must be of manager.
The database will be updated with the new employee
information and corresponding message will be displayed
Primary
None.
5) UpdateEmployee
Use case name
Actors
Purpose
Flow of events
a)Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
UpdateEmployee
Particular employee, Manager, Database.
To update the employee information.
-User goes to an html page to check the database and edits
his personal information. Manager can alter some
information like employee status.
-If any unauthenticated update is being done (like employee
can not change his employee id), an error message will be
displayed.
An employee can update his personal information only.
Manager can update only the status of the particular
employee.
-User must be logged in.
Employee information will be updated and a message
concerning the updated information will be displayed.
Secondary
None.
6) DeleteEmployee
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
DeleteEmployee
Manger, Database
Delete employee information from the database
b) Alternate Flow
Special Requirements
Pre-conditions
- None
Only Manger can delete an employee.
1) Manager login.
2)Availability of info in database
Deletion of entire info of employee and updated database.
secondary
None.
Post- conditions
Priority
Extension Points
- Particular employee’s entire info is retrieved from the
database and deleted from the database.
7) BookingPC
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
BookingPC
employee, administrator,database
To book a PC by a part-time employee
-An html page containing all systems status for booking is
viewed. The precondition ( 15 hrs a week limit ) is checked
before the user can book the pc, if available, by clicking on
the check box and there by saving the info of updated
systems status in the database..
- If precondition is failed an error message will be
displayed.
Precondition evaluation.
User login
The slot is not booked previously by other users
The updated system info is saved in the database. A
message is displayed confirming the booking.
Primary
None.
8) CancelBooking
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
CancelBooking
Employee,system
To cancel booking of an employee.
b) Alternate Flow
Special Requirements
Pre-conditions
- none
none
User login
Previous booking status.
Database updated. The cancelled slot is now open for
booking for all users.
Secondary.
None.
Post- conditions
Priority
Extension Points
-An html page containing the details of the employees own
bookings is displayed with cancel option. Upon canceling
the corresponding details are stored in the database .
9) VacationRequest
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
VacationRequest.
Employee, system, manager
To book Vacation by an employee
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
- None
Employee should be full-time employee
User login
-Full time employee sends request to manager for vacation.
Secondary.
None.
10) VacationAccept
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
VacationAccept.
Employee, administrator, manager
To accept/deny employee request of vacation ,if the employ
I sanctioned vacation, the new system slots are allotted for
part-time employees for booking.
-Manager sends accept to the employee. Extra slots (of a
single system) are added in the database on the dates of
vacation.
- If Manager denies request, the message is sent to
employee. No update is done to the database.
Employee should be full-time employee
User login
Database update( incase of accept)
None (incase of deny)
Secondary.
None.
11) ListRules
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
ListRule
Employee, system
To see all the rules
b) Alternate Flow
Special Requirements
Pre-conditions
- none
none
User login
Post- conditions
Priority
Extension Points
none
Secondary.
None.
-User sends the request to see all the rules. System evaluates
the request and displays the rules retrieving from the
database..
12) CreateRules
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
createRule
Employee, system
To Create new rules
-User sends the request to manger to create new rule.
Manager evaluates the rule and sends accept or deny
message.
- Error message is raised when manager denies the rule and
the rule is sent back for correction
none
User login
The rule should not already exist in the database
A new rule is added to the database.
primary
None.
13) UpdateRules
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
UpdateRule
Employee, system
To Update the rules
b) Alternate Flow
Special Requirements
Pre-conditions
- when update rule is denied.. error message is displayed
none
User login
The rule must exist in the database for update
Updated Rule is added to the database.
Secondary.
None.
Post- conditions
Priority
Extension Points
-Employee sends update request to manager, manager has to
approve it.
14) DeleteRules
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
DeleteRule
Employee, system
To delete a rule from the database.
b) Alternate Flow
Special Requirements
Pre-conditions
- none
none
User login
Rule existence in the database
The database is Updated with the deletion of Corresponding
Rules
Secondary.
None.
Post- conditions
Priority
Extension Points
- Employee can delete a rule with the consent of Manager .
The corresponding rule is deleted from the database.
15) SearchByKeyword
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
SearchByKeyword
User, System.
To search the database and display the contents indexed by
the given keyword
- User enters the keyword in the html page. The whole
database is searched for the entries corresponding to the
index entered.
- if entered index is not found, an error message is raised
none
User login
Result display
main
None.
16) ListCategory
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
ListCategory
User, System.
To list the categories in hierarchical form
-User can see the category list in desired hierarchical
manner. Each time the corresponding sub hierarchy is
displayed
- None
none
User login
Display Category.
secondary
None.
17)Calendar
Use case name
Actors
Purpose
Flow of events
a) Basic Flow
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
Calendar
User, System.
To list the categories in hierarchical form
-User can see the category list in desired hierarchical
manner. Each time the corresponding sub hierarchy is
displayed
- None
none
User login
Display Category.
secondary
None.
18)Newsletter
Use case name
Actors
Purpose
Newsletter
User,Database
To list the recent News.( updated rules , Alpha A/s
growth,holidays,etce)
Flow of events
a) Basic Flow
-User gets to see the news retrieved from the database.
b) Alternate Flow
Special Requirements
Pre-conditions
Post- conditions
Priority
Extension Points
-None
none
User login
Display News
secondary
None.
Sequence Diagrams for the organization ALFA A/S unit:For understanding the use cases of the organization ALFA A/S clearly sequence diagrams
are needed.
Login Sequence Diagram:
User
Home page
Login check
Database
start
open alfa login page
press login
user info
validate login
login query
execute
query
authorized(if emp)
open application page
Create new employee, update employee, delete employee:Employee
(manager)
login
Login check
Create/update/
delete
Database
press login
click create/update/delete
Update/delete/create query
process
query
updated info.
Booking PC:
Employee
Database
Booking
Request booking
validate
send booking query
Process query
Get booking
Create rule:Employee
(manager)
strart
New rule
Full time
employee
Rule request
Datebase
confirm user
validate
accept
Create rule
save
execute
query
redirect
Sequence diagram for search:-
User
Home page
Search
Database
login
click search
give keyword
Validate keyword
Keyword query
execute
query
Displays the URLs