+ All Categories
Home > Documents > Coursework Distributed System _ Greenwich

Coursework Distributed System _ Greenwich

Date post: 22-Jul-2016
Category:
Upload: todd-nguyen
View: 42 times
Download: 0 times
Share this document with a friend
Description:
this document presents the Distributed System Coursework which is used for Greenwich student.
76
The University of Greenwich DISTRIBUTED SYSTEM 1 A Coursework Report On Design and Building a Distributed Information System Course: COMP1303 DISTRIBUTED INFORMATION SYSTEM Submitted by Nguyen Anh Truong Student ID: GT60583 Class: GT0874 Date of Submission: April 17, 2014
Transcript
Page 1: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

1

A Coursework Report On

Design and Building a

Distributed Information System Course: COMP1303

DISTRIBUTED INFORMATION SYSTEM

Submitted by Nguyen Anh Truong

Student ID: GT60583

Class: GT0874

Date of Submission: April 17, 2014

Page 2: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

2

TABLE OF CONTENT I. System Objectives and Guidelines ......................................................... 3

II. Introduction ............................................................................................ 8

III. Assumption ........................................................................................... 9

IV. System Design ...................................................................................... 10

1. Entity Relationship Diagram ....................................................... 10

2. Database Relational Schema ...................................................... 10

3. Database Table Design ................................................................ 11

4. Use Case Diagram ...................................................................... 15

5. Class Diagram ............................................................................. 45

6. Deployment Diagram .................................................................. 48

V. System Implementation ......................................................................... 50

1. Login ............................................................................................. 50

2. Food/ Beverage Management ....................................................... 51

3. Room Management ...................................................................... 56

4. Customer Management ................................................................. 59

5. Staff Management ......................................................................... 64

6. Invoice Management .................................................................... 68

7. Report Management ..................................................................... 73

VI. Student Conclusion ..................................................................... 76

VII. References ................................................................................. 76

Page 3: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

3

I. System Objective & Guidelines The 3-tier architecture will be applied in developing the resort

management system on this coursework.

The 3 tiers are as

follows: the Data Tier (the

Data Server), Logic Tier (the

RM.DataService which

include my use of WCF Data

Service) and the Presentation

Tier (RM.Client which include

my use of MVC3).

All the local system functionalities are also

operated using the web services.

I have used the WCF Data service technology

to design the Service Tier. This technique provides a

more efficient way to get data from Database Server.

This is called the Entity Framework which is defined

within the Service Tier. Data Service Tier defines web

services used to call these methods within the Entity

Framework. Those services are then uploaded to the

internet in order to be used

I have used the MVC3 technology to develop the

Presentation Tier. This tier access the data by using

the provided web services from the Data Service Tier.

Page 4: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

4

I also have used one supported software call “Developer Express”

which helps me in generating a proper view of user interface as well as better

creating the report.

It is because that the library of the Developer Express software is quite

big referenced to my project, so that I did not attached them to the project

package when upload my coursework. It is required that the client will download

this software and follow my instruction to successfully run the system.

I have used the trial version of this supported software which is illegal.

The Client is also expected to download the trial version.

Tips for setting up the DevExpress Library.

This is where we can have a free trial version of the Developer Express

Software. https://www.devexpress.com/

Step 1: download and install the software choosing the trial version

- If the installation is succeeded, we can see it as follow

Step 2: follow the photos as your instructions:

Choose DEVEXPRESS – Project Converter – Project Converter…

Page 5: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

5

Choose Browse to navigate to the package need to add the software library

Page 6: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

6

We have two packages which need to add the addition library, pick any of it

to process the next state. You are required to do the process again to pick the other.

I choose the

RM.Local first. Then you

click “Upgrade”

Page 7: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

7

When it finish importing the DevExpress Library, click “Finish” and you are

all done. The final step is to run the project.

Remember to repeat the whole process with another package name

RM.National as I have mentioned above. We need the two package with supported

library to run.

Page 8: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

8

II. Introduction

The coursework has placed a situation wherein the developer is required to

build a resort management distributed system. As stated in the case study that this

company has three resorts in various places. The main purpose of distributed

system here is that National resort, hosted by one of these three resorts will be able

to run the other reports by connecting to each of the local resort’s provided service.

There are also requirements to each of the local resort in the purpose of managing.

The system consists of three kind of staff: Sales Staff, Local Manager and

National Manager. Each of them own the right to be able to run a series of system

functions. That means there are some functions that are required the higher staff

role. The work is as follow:

- Sales staff, local manager, national manager

o Manage the sales of room (booking, payment)

o Manage the sales of food/ beverage (booking, payment)

- Local manager, national manager

o Produce weekly/ monthly local report of room occupancy

o Produce weekly/ monthly local report of the staff sales statistics

o Produce weekly/ monthly local report of the food/ beverage and room

sales.

- National manager

o Produce weekly/ monthly national report of room occupancy

o Produce weekly/ monthly national report of the staff sales statistics

o Produce weekly/ monthly national report of the food/ beverage and

room

Page 9: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

9

III. Assumption The sales staff is only able to access several fields as follows:

o Food/ Beverage and Room invoice management (create, edit invoice)

o Food/ Beverage and Room payment management (edit payment)

o Food/ Beverage and Room management (create, edit item)

o Customer Management (create, edit customer)

Local Manager does not have the right in Staff Management due to the

developer rule and policy. They have the same access like the sales staff

and plus one more right is that to access the local report field.

The National Manager get all the rights in any resort. They have one unique

account in each resort with the highest priority.

- There might include multiple items within an individual invoice. Each item

is a complete process of creating, so that user is expected to choose just one

Staff Code during the process of generate a complete invoice.

- Those payments with their status of “Waiting” can be edited to “Paid”

Page 10: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

10

IV. System Design 1. Entity-relationship Diagram

The ERD of a Resort Management Distributed System

2. Database Relational Schema

Page 11: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

11

Customer

CustId

CustCd

FullName

DOB

Email

Phone

FoodBeverage

FBId

Name

Price

StatusId

FoodBeverageInvoice

FBIId

InvoiceId

FBId

StaffId

Quantity

FITotal

FoodBeverageStatus

StatusId

SDescription

Invoice

InvoiceId

CustId

PaymentMethod

PaymentDate

Total

StatusId

TypeId

InvoiceStatus

StatusId

SDescription

InvoiceType

TypeId

TypeName

Role

RoleId

RoleName

RoleDescriptionRoom

RoomId

Name

StatusId

Price

RoomInvoice

RIId

RoomId

InvoiceId

StaffId

DateIn

Dateout

RITotal

RoomStatus

StatusId

SDescription

Staff

StaffId

StaffCd

UserName

Password

FullName

DOB

Email

Phone

StaffRole

StaffRoleId

StaffId

RoleId

3. Database Table Design

Table Customer

Page 12: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

12

Table Food/ Beverage

Table Food/ Beverage Status

Table Room

Table Room Status

Table Invoice

Page 13: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

13

Table Invoice Type

Table Invoice Status

Table Food/ Beverage Invoice

Table Room Invoice

Table Staff

Page 14: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

14

Table Role

Table Staff Role

Page 15: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

15

4. Use Case Diagram

Use Case Diagram 1

Use Case Specification 1:

Identifier U01 – Login to the system

Description This Use Case allows actors to access into the system.

Actor Sales Staff, National Manager, Local Manager

Preconditions System identifies actor as a common guest that need to be authenticated.

Post Conditions Actors account are recognized by the system and are recorded to its

memory section. From that system interacts with actor with appropriate

views and information.

Flow of events

Basic Path

Page 16: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

16

The Use Case begins when the actor indicates to access the login

section of system.

1. System requires actor to fill up all login fields (username and

password).

2. Actor inputs username and password onto appropriate field

mentioned above and choose to login.

3. System starts to authenticate the required fields, making sure that

the inputs match with a unique account in the system, and both

username and password is correct.

4. The actor will be navigated to appropriate destination and is

indicated that is currently signed in by the system specific

displayed content.

5. The use case ends.

Alternate Path

Field(s) is left

blank

System warns actor with red message that require them to have to input

enough fields before clicking Login button.

Wrong

Username or

Password

System shows error login screen to actor with message about the failure of

their input information. System then prompts actor to do the login process

again.

Exception Path

Failure in Login

over 5 times

System does not allow actor to do any login process within 10 minutes.

Use Case Specification 36

Identifier U36 – Logout of the system

Description This Use Case allows actors to logout of the system

Actor Sales Staff, National Manager, Local Manager

Preconditions System is in used of a specific actor who want to log out

Post Conditions System remove the current account session on all of its fields and return to

the login screen

Flow of events

Basic Path

The Use Case begins when the actor indicates to log out of the

system.

1. System erase all current account sessions and navigates to the login

screen

2. Actor is logged out of the system

3. The use case ends.

Alternate Path

Exception Path

Page 17: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

17

Use Case Specification 42

Identifier U42 – Change Password

Description This Use Case allows actors to change the account password.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System updates the actor account with new password

Flow of events

Basic Path

The Use Case begins when the actor indicates to change the

account password

1. System navigates to the section used to change the password

account

2. Actor provides following fields:

- Current account password

- New account password

- Re input new account password

3. Actor choose “Update” to change the account password

4. System update the account with new password.

5. The use case ends.

Alternate Path

Old password

input failed

System notifies actor with the wrong input of the old password. Actor is

expected to re input it again

Confirm new

password does

not match the

new password

System notifies actor with the error in matching the two new password.

Actor is expected to re input those fields again.

Exception Path

Actor choose to

cancel the

process

System does not change the current account password.

Use Case Specification 2

Identifier U02 – View List of Food/ Beverage

Description This Use Case allows actors to see a list of all food/ beverage belongs to a

specific resort

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the list of all food/ beverage to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the list of all

Page 18: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

18

food/ beverage of the resort

1. System navigates to the section used to perform this list

2. Actor receive the information

3. The use case ends.

Alternate Path

The list might

not be loaded

In this case, actor is expected to reload the current page.

Exception Path

none

Use Case Specification 3

Identifier U03 – View List of Room

Description This Use Case allows actors to see a list of all rooms belong to a specific

resort

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the list of all rooms to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the list of all

room of the resort

1. System navigates to the section used to perform this list

2. Actor receive the information

3. The use case ends.

Alternate Path

The list might

not be loaded

In this case, actor is expected to reload the current page.

Exception Path

none

Use Case Specification 4

Identifier U04 – View List of Customer

Description This Use Case allows actors to see a list of all Customer belongs to a

specific resort

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the list of all Customer to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the list of all

customer of the resort

1. System navigates to the section used to perform this list

2. Actor receive the information

Page 19: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

19

3. The use case ends.

Alternate Path

The list might

not be loaded

In this case, actor is expected to reload the current page.

Exception Path

none

User Case Specification 5

Identifier U05 – View List of Payment

Description This Use Case allows actors to see a list of all payment (generated invoice)

belongs to a specific resort

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the list of all payment to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the list of all

payment of the resort

1. System navigates to the section used to perform this list

2. Actor receive the information

3. The use case ends.

Alternate Path

The list might

not be loaded

In this case, actor is expected to reload the current page.

Exception Path

none

Use Case Specification 6

Identifier U06 – Create new Food/ Beverage Invoice

Description This Use Case allows actors to create an invoice of Food/ Beverage bases

on the customer order.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System record the current customer invoice.

The invoice is ready to become a payment

Flow of events

Basic Path

The Use Case begins when actor receives a customer order and that

indicates to create a new food/ beverage invoice.

1. The system navigates to the section used to create an invoice of

food/ beverage.

2. Actor is required to provide information about the invoice

- Customer (available or create a new one)

Page 20: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

20

- Staff (choose the staff code which belongs to the current

staff who is placing this invoice)

- List of food/ beverage to be in the invoice as well as its

quantity for each of the item.

3. Choose to “Update” the invoice till it has enough customer’s

food/ beverage requirement.

4. System records the current invoice with a list of items belong to

a specific customer and an individual staff.

5. The use case ends.

Alternate Path

Missing the field

of customer

In this case the invoice is still able to be created but it cannot become a

payment at the end. Actor is expected to provide the customer who own

the invoice

Different Staff

detected in a

current single

invoice

As said that a specific invoice is belonged to just one staff, so that actor is

expected to provide the same staff code on each item input to that invoice.

Otherwise, the process might be unable to run normally.

Exception Path

none

Use Case Specification 7

Identifier U07 – Create new Room Invoice

Description This Use Case allows actors to create an invoice of Room bases on the

customer order.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System record the current customer invoice.

The invoice is ready to become a payment

Flow of events

Basic Path

The Use Case begins when actor receives a customer order and that

indicates to create a new room invoice.

1. The system navigates to the section used to create an invoice of

room.

2. Actor is required to provide information about the invoice

- Customer (available or create a new one)

- Staff (choose the staff code which belongs to the current staff

who is placing this invoice)

- Adjust the date the customer begin to check in and that the day

to check out.

- Browse for an appropriate room base on the customer

requirement. There is different price for different kind of room

3. Choose to “Update” the invoice till it has enough customer’s room

requirement.

Page 21: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

21

4. System records the current invoice with a list of items belong to a

specific customer and an individual staff.

5. The use case ends.

Alternate Path

Missing the field

of customer

In this case the invoice is still able to be created but it cannot become a

payment at the end. Actor is expected to provide the customer who own

the invoice

Different Staff

detected in a

current single

invoice

As said that a specific invoice is belonged to just one staff, so that actor is

expected to provide the same staff code on each item input to that invoice.

Exception Path

none

Use Case Diagram 2

Page 22: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

22

Use Case Specification 8

Identifier U08 – Create new Food/ Beverage

Description This Use Case allows actors to create a new Food/ Beverage added to the

list of the resort.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System record the new Food/ Beverage and perform it on the list of all

food/ beverage.

Flow of events

Basic Path

The Use Case begins when actor indicates to create a new food/

beverage added to the list of it.

1. The system navigates to the section used to create a food/ beverage

2. Actor provide information of the new item

- Name

- Price

- Status: Available or Unavailable (the new item might be

just added but will be available later)

3. Actor choose to create the food/ beverage.

4. System records the added item and performs it on the list to the

actor.

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the create process to be accomplished.

Exception Path

Use Case Specification 9

Identifier U09 – View a Food/ Beverage Detail

Description This Use Case allows actors to see the detail information of a specific

food/ beverage.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the information of the item to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the detail

information of a food/ beverage.

1. The system navigates to the section used to perform the

information

2. Actor receive the information

3. The use case ends.

Alternate Path

Page 23: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

23

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the create process to be accomplished.

Exception Path

Use Case Specification 10

Identifier U10 – Edit a Food/ Beverage Detail Information

Description This Use Case allows actors to change the information of a food/ beverage

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System records the new information of the chosen food/ beverage

Flow of events

Basic Path

The Use Case begins when actor indicates to edit the information of

a food/ beverage

1. The system navigates to the section used to change the information

2. Actor provide new information for the current food/ beverage

- Name

- Price

- Status: available or unavailable

3. Actor chooses to save the process.

4. System records the new information and apply for the chosen item

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the update process to be accomplished.

Exception Path

Use Case Specification 11

Identifier U11 – Search for a Food/ Beverage

Description This Use Case allows actors to search for a particular food/ beverage

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs food/ beverage base on the actor input information

Flow of events

Basic Path

The Use Case begins when actor indicates to search for a food/

beverage

1. The system navigates to the section used to search for a food/

beverage

2. Actor choose which field that the system will apply the searching

process for

Page 24: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

24

- Search by Name

- Search by Price

- Search by Status

3. System performs appropriate food/ beverage base on the actor

provided information.

4. Actor receive the necessary information

5. The use case ends.

Alternate Path

None

Exception Path

None

Use Case Diagram 3

Page 25: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

25

Use Case Specification 12

Identifier U12 – Create new Room

Description This Use Case allows actors to create a new Room added to the list of the

resort.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System record the new Room and perform it on the list of all rooms.

Flow of events

Basic Path

The Use Case begins when actor indicates to create a new room

added to the list of it.

1. The system navigates to the section used to create a room

2. Actor provide information of the new item

- Name

- Price

- Status: Available or Unavailable (the new item might be

just added but will be available later)

3. Actor choose to create the room.

4. System records the added item and performs it on the list to the

actor.

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the create process to be accomplished.

Exception Path

Use Case Specification 13

Identifier U13 – View a Room Detail

Description This Use Case allows actors to see the detail information of a specific

Room.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the information of the item to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the detail

information of a room.

1. The system navigates to the section used to perform the

information

2. Actor receive the information

3. The use case ends.

Alternate Path

Missing some System notifies actor with providing enough information to the required

Page 26: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

26

required fields fields for the create process to be accomplished.

Exception Path

User Case Specification 14

Identifier U14 – Edit a Room Detail Information

Description This Use Case allows actors to change the information of a room

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System records the new information of the chosen Room

Flow of events

Basic Path

The Use Case begins when actor indicates to edit the information of

a room

1. The system navigates to the section used to change the

information

2. Actor provide new information for the current room

- Name

- Price

- Status: available or unavailable

3. Actor chooses to save the process.

4. System records the new information and apply for the chosen item

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the update process to be accomplished.

Exception Path

Use Case Specification 15

Identifier U15 – Search for a Room

Description This Use Case allows actors to search for a particular room

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs room base on the actor input information

Flow of events

Basic Path

The Use Case begins when actor indicates to search for a room

1. The system navigates to the section used to search for a room

2. Actor choose which field that the system will apply the

searching process for

- Search by Name

- Search by Price

Page 27: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

27

- Search by Status

3. System performs appropriate room base on the actor provided

information.

4. Actor receive the necessary information

5. The use case ends.

Alternate Path

None

Exception Path

None

Use Case Diagram 4

Use Case Specification 16

Identifier U16 – Create new Customer

Description This Use Case allows actors to create a new Customer added to the list of

the resort.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System record the new Customer and perform it on the list of all

customers.

Page 28: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

28

Flow of events

Basic Path

The Use Case begins when actor indicates to create a new customer

added to the list of it.

1. The system navigates to the section used to create a

customer

2. Actor provide information of the new item

- Full Name

- Date of Birth (DOB)

- Email

- Phone

3. Actor choose to create the new customer.

4. System records the added customer and performs it on the list to

the actor.

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the create process to be accomplished.

Exception Path

Use Case Specification 17

Identifier U17 – View a Customer Detail

Description This Use Case allows actors to see the detail information of a specific

Customer.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the information of the customer to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the detail

information of a customer.

1. The system navigates to the section used to perform the

information

2. Actor receive the information

3. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the create process to be accomplished.

Exception Path

Use Case Specification 18

Page 29: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

29

Identifier U18 – Edit a Customer Detail Information

Description This Use Case allows actors to change the information of a Customer

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System records the new information of the chosen Customer

Flow of events

Basic Path

The Use Case begins when actor indicates to edit the information of

a customer

1. The system navigates to the section used to change the

information

2. Actor provide new information for the current Customer

- Full Name

- Date of Birth (DOB)

- Email

- Phone

3. Actor chooses to save the process.

4. System records the new information and apply for the chosen

customer

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the update process to be accomplished.

Exception Path

Use Case Specification 19

Identifier U19 – Search for a Customer

Description This Use Case allows actors to search for a particular customer

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs customer base on the actor input information

Flow of events

Basic Path

The Use Case begins when actor indicates to search for a customer

6. The system navigates to the section used to search for a

customer

7. Actor choose which field that the system will apply the

searching process for

- Search by Full Name

- Search by Birthday

- Search by Email

- Search by Phone

8. System performs appropriate customer base on the actor provided

Page 30: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

30

information.

9. Actor receive the necessary information

10. The use case ends.

Alternate Path

None

Exception Path

None

Use Case Diagram 5

Use Case Specification 20

Identifier U20 – Edit a Food/ Beverage Invoice

Description This Use Case allows actors to change the inner item information in a

specific food/ beverage invoice.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System updates new information of a changing item within an invoice

Flow of events

Basic Path

The Use Case begins when actor indicates to edit formation of an

item located in a specific food/ beverage invoice.

1. The system open the section used to change the information

2. Actor provides new information replace to the old.

Page 31: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

31

- Other Food/ Beverage

- Other Staff Code

- Food/ Beverage Quantity

3. System updates the chosen item with new information and

performs to the actor

4. Actor receive the necessary information

5. The use case ends.

Alternate Path

Actor choose to

delete a specific

item instead of

edit it

In this case the chosen item will be delete from the current food/ beverage

invoice. The system updates the invoice and performs to actor.

Exception Path

Actor choose to

cancel the

process of edit

the invoice

In this case, the system does not change any of the invoice information

Use Case Specification 21

Identifier U21 – Create a Food/ Beverage Payment

Description This Use Case allows actors to export a Food/ Beverage invoice to a

payment

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs a list of recently exported payment

Flow of events

Basic Path

The Use Case begins when actor indicates to export a food/

beverage invoice to a payment. The use case is the extension part of

the create Food/ Beverage Invoice Section.

1. After create a food/ beverage invoice with a list of all

required item, actor further provide some more

information to export it to a payment

- Payment Method: the method of payment that the customer

will apply to pay for the invoice (Credit Card, Cash, etc…)

- Payment Date: the date of the payment

- Status: Waiting or Paid

2. Actor choose “Create” to export the current invoice into payment

list.

3. Actor click on “Payment” tab to switch into the payment section.

4. System performs a list of all payment.

5. Actor see the recent exported payment.

6. The use case ends.

Alternate Path

Page 32: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

32

None

Exception Path

None

Use Case Diagram 6

Use Case Specification 22

Identifier U22 – Edit a Room Invoice

Description This Use Case allows actors to change the inner item information in a

specific room invoice.

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System updates new information of a changing item within an invoice

Flow of events

Basic Path

The Use Case begins when actor indicates to edit formation of an

item located in a specific room invoice.

1. The system open the section used to change the

information

2. Actor provides new information replace to the old.

Page 33: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

33

- Other Room

- Other Staff Code

- Other Date In, Date Out

3. System updates the chosen item with new information and

performs to the actor

4. Actor receive the necessary information

5. The use case ends.

Alternate Path

Actor choose to

delete a specific

item instead of

edit it

In this case the chosen item will be delete from the current room invoice.

The system updates the invoice and performs to actor.

Exception Path

Actor choose to

cancel the

process of edit

the invoice

In this case, the system does not change any of the invoice information

Use Case Specification 23

Identifier U23 – Create a Room Payment

Description This Use Case allows actors to export a Room invoice to a payment

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs a list of recently exported payment

Flow of events

Basic Path

The Use Case begins when actor indicates to export a Room

invoice to a payment. The use case is the extension part of the

create Room Invoice Section.

1. After create a Room invoice with a list of all required item, actor

further provide some more information to export it to a payment

- Payment Method: the method of payment that the customer

will apply to pay for the invoice (Credit Card, Cash, etc…)

- Payment Date: the date of the payment

- Status: Waiting or Paid

2. Actor choose “Create” to export the current invoice into payment

list.

3. Actor click on “Payment” tab to switch into the payment section.

4. System performs a list of all payment.

5. Actor see the recent exported payment.

6. The use case ends.

Alternate Path

None

Exception Path

Page 34: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

34

None

Use Case Diagram 7

Use Case Specification 25

Identifier U25 – Edit Payment

Description This Use Case allows actors to edit a payment information

Actor Sales Staff, National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System update the selected payment with new information

Flow of events

Basic Path

The Use Case begins when actor indicates to change a payment

information.

1. System open the section used to edit the payment

2. Actor change the information of a payment. Notice that actor can

only change the following fields:

- Payment Method

- Payment Date

- Status: can only change from Waiting to Paid.

3. Actor click on “Update” to save the process.

4. System records the information and performs the edited payment

Page 35: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

35

5. Actor see the recent edited payment.

6. The use case ends.

Alternate Path

None

Exception Path

None

Use Case Diagram 8

Use Case Specification 37

Identifier U37 – View List of Staff

Description This Use Case allows actors to see a list of all Staff belongs to a specific

resort

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the list of all Staff to the actor

Flow of events

Basic Path

Page 36: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

36

The Use Case begins when actor indicates to view the list of all

Staff of the resort

1. System navigates to the section used to perform this list

2. Actor receive the information

3. The use case ends.

Alternate Path

The list might

not be loaded

In this case, actor is expected to reload the current page.

Exception Path

none

Use Case Specification 38

Identifier U38 – Create new Staff

Description This Use Case allows actors to create a new Staff added to the list of the

resort.

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System record the new Staff and perform it on the list of all Staff.

Flow of events

Basic Path

The Use Case begins when actor indicates to create a new Staff

added to the list of it.

1. The system navigates to the section used to create a Staff

2. Actor provide information of the new item

- Username ( the username of the staff account used to login

to the system)

- Password (the password of the staff account used to login to

the system)

- Full Name

- Date of Birth (DOB)

- Email

- Phone

- Staff Role (Sales Staff, Local Manager, National Manager)

3. Actor choose to create the new staff.

4. System records the added staff and performs it on the list to the

actor.

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the create process to be accomplished.

Exception Path

Page 37: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

37

Use Case Specification 39

Identifier U39 – View a staff Detail

Description This Use Case allows actors to see the detail information of a specific staff.

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the information of the staff to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the detail

information of a staff.

1. The system navigates to the section used to perform the

information

2. Actor receive the information

3. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the create process to be accomplished.

Exception Path

Use Case Specification 40

Identifier U40 – Edit a Staff Detail Information

Description This Use Case allows actors to change the information of a staff

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System records the new information of the chosen staff

Flow of events

Basic Path

The Use Case begins when actor indicates to edit the information of

a staff

1. The system navigates to the section used to change the information

2. Actor provide new information for the current staff

- Full Name

- Date of Birth (DOB)

- Email

- Phone

- Staff Role

3. Actor chooses to save the process.

4. System records the new information and apply for the chosen Staff

5. The use case ends.

Alternate Path

Missing some

required fields

System notifies actor with providing enough information to the required

fields for the update process to be accomplished.

Page 38: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

38

Exception Path

Use Case Specification 41

Identifier U41 – Search for a Staff

Description This Use Case allows actors to search for a particular Staff

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

Post Conditions System performs the Staff base on the actor input information

Flow of events

Basic Path

The Use Case begins when actor indicates to search for a staff

1. The system navigates to the section used to search for a staff

2. Actor choose which field that the system will apply the searching

process for

- Search by Staff Code

- Search by Username

- Search by Full Name

- Search by Birthday

- Search by Email

- Search by Phone

- Search by Staff Role

3. System performs appropriate customer base on the actor provided

information.

4. Actor receive the necessary information

5. The use case ends.

Alternate Path

None

Exception Path

None

Page 39: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

39

Use Case Diagram 9

Use Case Specification 26

Identifier U26 – View List of Local Report

Description This Use Case allows actors to see a list of all local report

Actor National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

The system authenticate the role of the logged account

Post Conditions System performs the list of all local report to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the list of all

local report of the resort

1. System navigates to the section used to perform this list

2. Actor receive the information

3. The use case ends.

Alternate Path

The list might

not be loaded

In this case, actor is expected to reload the current page.

Exception Path

Page 40: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

40

none

Use Case Specification 27

Identifier U27 – View Food/ Beverage Sales Local Report

Description This Use Case allows actors to see the report of local Food/ Beverage Sales

Actor National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the local report of the food/ beverage sales to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

local Food/ Beverage Sales

1. System navigates to the section used to perform this report

2. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

3. Actor receive the report

4. The use case ends.

Alternate Path

Exception Path

none

Use Case Specification 28

Identifier U27 – View Room Sales Local Report

Description This Use Case allows actors to see the report of local Room Sales

Actor National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the local report of the Room sales to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

local Room Sales

1. System navigates to the section used to perform this report

2. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

3. Actor receive the report

4. The use case ends.

Alternate Path

Exception Path

none

Page 41: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

41

Use Case Specification 29

Identifier U27 – View Staff Sales Local Report

Description This Use Case allows actors to see the report of local Staff Sales

Actor National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the local report of the Staff sales to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

local Staff Sales

1. System navigates to the section used to perform this report

2. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

3. Actor receive the report

4. The use case ends.

Alternate Path

Exception Path

none

Use Case Specification 30

Identifier U27 – View Room Occupancy Local Report

Description This Use Case allows actors to see the report of local Room Occupancy

Actor National Manager, Local Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the local report of the Room Occupancy to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

local Room Occupancy

1. System navigates to the section used to perform this report

2. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

3. Actor receive the report

4. The use case ends.

Alternate Path

Exception Path

none

Page 42: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

42

Use Case Diagram 10

Use Case Specification 31

Identifier U31 – View List of National Report

Description This Use Case allows actors to see a list of all national report

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

The system authenticate the role of the logged account

Post Conditions System performs the list of all national report to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the list of all

national report of the resort

1. System navigates to the section used to perform this list

2. Actor receive the information

3. The use case ends.

Alternate Path

The list might

not be loaded

In this case, actor is expected to reload the current page.

Exception Path

none

Page 43: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

43

Use Case Specification 32

Identifier U32 – View Food/ Beverage Sales National Report

Description This Use Case allows actors to see the report of national Food/ Beverage

Sales

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the national report of the food/ beverage sales to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

national Food/ Beverage Sales

1. System navigates to the section used to perform this report

2. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

3. Actor receive the report

4. The use case ends.

Alternate Path

Exception Path

none

Use Case Specification 33

Identifier U33 – View Room Sales National Report

Description This Use Case allows actors to see the report of national Room Sales

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the national report of the Room sales to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

national Room Sales

1. System navigates to the section used to perform this report

2. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

3. Actor receive the report

4. The use case ends.

Alternate Path

Exception Path

none

Page 44: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

44

Use Case Specification 34

Identifier U34 – View Staff Sales National Report

Description This Use Case allows actors to see the report of National Staff Sales

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the national report of the Staff sales to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

national Staff Sales

1 .System navigates to the section used to perform this report

6. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

7. Actor receive the report

8. The use case ends.

Alternate Path

Exception Path

none

Use Case Specification 35

Identifier U27 – View Room Occupancy National Report

Description This Use Case allows actors to see the report of national Room Occupancy

Actor National Manager

Preconditions Actor is required to do the login to access the system feature.

System authenticate the role of the logged account

Post Conditions System performs the national report of the Room Occupancy to the actor

Flow of events

Basic Path

The Use Case begins when actor indicates to view the report of the

national Room Occupancy

1. System navigates to the section used to perform this report

2. Actor adjusts the Start Date and End Date for the system to

generate appropriate information.

3. Actor receive the report

4. The use case ends.

Alternate Path

Exception Path

none

Page 45: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

45

5. Class Diagram

- Entities Class Diagram

Page 46: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

46

- System Controller Class Diagram

Page 47: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

47

- Model Class Diagram

Page 48: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

48

6. Deployment Diagram

The illustration for the 3 tier-architecture

of the current developing system

Data Tier: or called database server, contains the external data source. As in

here we use the Microsoft SQL Server.

Logical Tier: contains two inner sub layers: the Data Access Layer and the

Service Layer.

- We use the technology of WCF Data Service which include the entity

framework as place to state all accessing method to the Data Tier. The

Data Access Tier is used to store the entity framework library as well

as the data from database server.

Page 49: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

49

- The Service layer defines services that retrieve data from the data

access tier in order to avoid connection from the Presentation Layer to

the Data Access Layer.

Presentation Tier: define the connection to the public services from the

Logical Tier.

Page 50: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

50

V. System Implementation 1. Login

Picture: Login screen

The login process is required whenever there is appropriate user who

wants to access with the system in order to user its features.

Provided account:

National Manager

Username: nationalManager

Password: 123456

Local Manager

Username: localManager

Password: 123456

Sales Staff

Username: staff003

Password: 123456

Case of success:

System navigates user to the default web page wherein display the

content of Generating Invoice process.

System performs username of the current accessing user account at

the top left of the screen as shown in the picture.

Page 51: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

51

Case of failure:

System warns user with information about wrong inputting account

username or password.

User are expected to do the login again.

2. Food/Beverage Management

Main active screen

System performs a list of all foods and beverages within each resort. The sale

staff base on the food and beverage status (Available or

Unavailable) to inform Customer with their order.

As user chooses to sort the list by status, system returns

only food and beverages that are suitable with the selected state.

Page 52: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

52

Create a new Food/Beverage

User chooses “Create” on the main Food/Beverage screen

System navigates to the create food/beverage page with performing of

necessary fields. Those fields include: name of new food/beverage, price and

whether it is in service or not (status).

Case of failure: system requires user to

input enough fields before pressing the “Create”

button, otherwise the button is disabled.

Page 53: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

53

Case of success: system updates the food/beverage list with new item

which user has already successfully created.

View a Food/Beverage Detail

Select “Details” the item which user want to view

System performs item detail information

Edit Information of a Food/Beverage.

Page 54: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

54

Select “Edit” the item which user want to update information

User changes the item information with appropriate fields

Case of success:

Before

After

Case of failure:

System will notifies user if the

item Name and Price are left blank

during the update process.

Page 55: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

55

Search and Filter

System provides smart search solution as well as filter for performing

necessary items.

User types the name of the item that are looking for and the list will be

appropriately filtered like shown on the above picture.

User can also

search with price by

typing the first

number of the item

price.

User can also merge three types of search into one in order to look for an

exact item with the name, price and status are as expected.

Page 56: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

56

NOTICE: There is no term that calls remove food/beverage. Each

food/beverage here carries itself a specific state:

Available: food/beverage in service

Unavailable: food/beverage out of service

3. Room Management

Main active screen

System performs a list of all rooms within the resort. As the interface and

management solutions here are quiet the same as they are in Food/Beverage

section. User can refer to Food/Beverage Management section to understand

clearly how to use this Room Management section.

Create new room

Page 57: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

57

View a room information

Edit a room information

Before

After

Page 58: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

58

Case of failure in creating and updating a room

Search and Filter

User can search

for a room by its name

Search for a room with its Price

Page 59: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

59

More advanced search with the merge of three fields

NOTICE: There is no term that calls remove room. Each room here carries

itself a specific state:

Available: room in service

Unavailable: room out of service

4. Customer Management

Main active screen

Page 60: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

60

System performs a list of all customers who have purchased room or food or

both in the past. The information of customers is stored for reusability if they come

back to use the resort services in the future.

View Customer Detail Information

By clicking the “Detail” link at the beginning of each record, user is able to

view Customer detail information

Once in the customer detail

page, user can choose to edit the

information as well as go back to the

previous list.

The “Edit” sign is also located

next to the “Detail” on the Customer

“Main active screen”.

Edit Customer Detail

Case of success

Before

Page 61: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

61

After

Create a New Customer

By clicking “Create” link located on the top left of the list, user is able to

create a new Customer for further contact and support

After complete filling in all required fields, user click “Create” for the system to

record that new customer

Case of success

Page 62: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

62

Case of failure in Creating and Editing Customer a Customer

information. As in here, user is expected to do the processes again.

Search and Filter

System provides various way for user to look for potential customer.

User can search for a customer by Code

Search by Name

Page 63: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

63

Search by Birthday

Search by Email

And search by Phone

Page 64: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

64

5. Staff Management

Main active screen

Create new staff

Case of success

Page 65: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

65

Case of failure

View staff detail

Page 66: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

66

Edit staff

Case of success

Case of failure

Page 67: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

67

Search and Filter

Search staff by Code

Search staff by Username

Search staff by Full Name

Search staff by Birthday

Search staff by Email

Page 68: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

68

Search staff by Phone

Search staff by Role

6. Invoice Management

Invoice management is the most important feature of the whole resort

system. As in here, we provide a proper way to maintain and monitor the

Food/Beverage and Room invoice.

Food/Beverage Invoice

Main active screen

Page 69: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

69

Each invoice of this kind can contain from one to many kind of foods and

beverages.

Each food/beverage invoice is associated with only 1 customer and 1 staff

To create a new food/beverage invoice, first to select the customer

If the customer has used the resort service before, there will be customer’s

detail information stored on the system. User only need to select customer name as

the owner of the invoice. Otherwise, user clicks on “Create” located under the

Customer box to store a new one.

Secondly, user click on “New” to start ordering the food and beverage.

There is a rule as mentioned above that, each invoice contains one or many items

but is only belonged to 1 customer and 1 staff who place it.

Each item is followed with its own

price which is automatically shown up when

user browse for a specific food/ beverage.

Page 70: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

70

After that, user adjusts the item quantity incase the customer wants more

than just one for each item. System will immediately perform the total of this item

as shown below.

User then selects his/her staff code as the one who is in charge of the

current invoice.

Then user click on “Update” to temporary finish ordering an specific item of

the invoice.

Page 71: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

71

Normally, the customer will order more than an item one time, and that

means user is expected to repeat the process again to add one or more items to the

current invoice.

By click on the “New”

located at the beginning of

each item row, user can

achieve the purpose. User can

also choose “Edit” to adjust

the quantity of the item, or

simply choose “Delete” to

remove the chosen item out of

the current invoice.

The picture on the left

shown that, the current food/

beverage invoice has 5 items.

It is belongs to a customer

name “Todd Nguyen” and the

staff who is in charge of

placing it has the code “S005”

Finally, user inputs the

information of “Payment

Method”, “Payment Date” and

“Invoice Status” to export the

current invoice.

Payment Method can be

Cash, Credit Card or whatever

the user define to get benefit.

There are two status: “Paid”

means customer done with

solving the invoice, and

Page 72: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

72

“Waiting” means customer not

yet pay for the invoice.

Room Invoice

It is quite the same of Room Invoice to the one of Food/ Beverage. User then

needs to adjust the time that customer need to use the room service. The “NoD”

indicates the number of days from the time customer move in to the time move out

Once User click on “Create” the invoice (Food/ Beverage or Room) will be

exported into “Payment” section.

Page 73: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

73

Those invoices which are already Paid cannot be modified, the remains

waiting invoices can be changed with information about Date, Payment Method

and Status.

7. Report Management

There are 4 kinds of report that we design for the system to perform.

The report of Room Occupancy

User needs to adjust the time period wherein the Rooms which are in service

within will be performed. There is the information about a number of day a

specific room is rented.

Page 74: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

74

User base on the total number of item displayed on the report to calculate the

occupancy rate by dividing it to the total number of owned room and multiply with

100%. The process of calculating will be made manually as we did not provide to

the system.

The Report of Food/ Beverage Sales

User adjusts the time period for the system to perform which food and

beverage within this time.

The report show the total number of quantity of each food and beverages

that has been sold out during the expected time period. There is also the total

amount of each item and the final total of all item belong to the adjusted time.

The Report of Room Sales

User adjusts the time period for the system to perform which room within the

the time

The report shows the price of each room per day, the total amount of money

for each room and the final total of all room listed in the report

Page 75: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

75

The report of Staff Sales

User adjusts the time period for the system to perform which staff within the

the time.

The report shows the total amount of money an individual staff has made

during the specified time period. There is also the final total of all staff during this

time.

NOTICE: We develop a distributed system with multi resort located in

different areas. In order to illustrate for the term of distributed system, there are

two main kind of the report process, the “National report” and “Local Report”. As

said in the Case Study, there is one that stands for a national resort wherein the

national manager can access into other resorts system and generate the list of all

report.

The National manager can access to any resort system belongs to that resort

brand. So that they can easily manage the information of customer, staff, food and

room as well as the sales statistic. Base on the national resort system, national

manager does not have to login into other system to get report. It is the primary

function that allow the manager to get those report right at one place and one time

conveniently.

Page 76: Coursework Distributed System _ Greenwich

The University of Greenwich DISTRIBUTED SYSTEM

76

VI. Student Conclusion

1. System functionalities:

The system has covered enough required fields for all user: Sales

Staff, Local Manager and National Manager. However, it still

contains some logic mistake when running these system function as if

user does not follow the right path, it can throw out a new error which

I have not figured out yet.

2. Security:

The authentication of the system is pretty good as it does not allow

any staff with inappropriate role to access and use the important

system features. Only one staff with highest right (national Manager)

can access onto those features and run them to collect data.

3. Performance:

The system performance is rather slow. Personally, the access through

the web service takes more time than the direct connection between

presentation layer and business layer. However, the use of web service

is safer.

4. Scalability

The attributes of each object developed on the system is quite wide

and that there is almost unnecessary when adding more new resources

that required the change in system architecture.

5. Transparency

All the Staff will not know where the service come from.

6. Failure

The chance of failure to this system is rather low. I have caught

almost all the error which can be thrown out.

VII. References

http://www.codeproject.com/Articles/434282/A-N-Tier-Architecture-

Sample-with-ASP-NET-MVC-WCF

Thanks for reading.


Recommended