System Analysis And Design Art Essay

Published:

This assignment will allow me to demonstrate an understanding of the modeling of a data driven system. We will analyse and design a system for a hostelling association that provides budget holiday accommodation in our country, primarily for young adults, many of whom will have travelled from abroad. The system I design will include a prototype user interface for the new system.

ACKNOWLEDGEMENT

I am now studying in IADCS and I do my assignment and project. In this assignment, I got much knowledge. In this assignment, we do about the national hostelling association provides budget holiday accommodation in cities and tourist destinations throughout our country. It currently has 40 hostels of varying sizes that can accommodate between 10 and 40 guests at any one time.

Task 1

Create a process model for the hostelling association's bed booking system comprising:

  1. A Context Diagram of the bed booking system.(4 marks)
  2. A statement of the aims and objectives of the bed booking system. (2 marks)
  3. A Data Flow Diagram for the bed booking system (6 marks) including:
  • Process description (2 marks)
  • Dataflow description (2 marks)
  • Data store contents (2 marks)
  • External entity definition (2 marks)

(a)CONTEXT DIAGRAM

(b) AIMS AND OBJECTIVES

Lady using a tablet
Lady using a tablet

Professional

Essay Writers

Lady Using Tablet

Get your grade
or your money back

using our Essay Writing Service!

Essay Writing Service

The National Association of Hostels (NHA) provides holiday accommodation in the cities and tourist destinations. Currently has 40 shelters of different sizes with capacity of between 10 and 40guest in running time and customers should make a reservation directly to the hostel partners. These shelters have to produce monthly reports and send money every month and submit them to headquarters. And the NHA wants his bed centralized reservation system in a single office national reserve where all reservations will be taken by telephone and centralize the payment of the booking fee. In order to manage the centralized system, the NHA needs a new computer system.
The new system should record the reserves, and the ability to search for free beds on a given date, recording payments and shall have characteristics centralized. And you must also send an email to the hostel automatically associated with the reservation and payment information. The main features to be included in the centralized system registering reservations are bed capacity in real time with the customer name, name of the hotel, start date, number of nights and the amount paid, the ability to search for free under beds to the location, number of nights and the date, the ability to record customer information and the ability of the financial records of reservations

(c) DATA FLOW DIAGRAMS

PROCESS DESCRIPTIONS

Process Description

Process No

Process Name

Description

1

Registration

The records of the central office branches hostel information including room type, room information and shelter information.

2

Enquiry

the customer enquiry about the hostel information in the enquiry process

3

Searching

the customer ask the required hostel, location and room type, Size, no of night, start date, the process will search the hostel which is valid with the customers requirements

4

Booking

the customer does booking, the staff will record booking information in the booking process

5

Payment

When the client confirms the booking by giving 10% deposit, the staff will be recorded as payment and when the customer makes full payment of staff will also update the payment in the payment process

6

Send Email

central office sent booking information and customer information to the hostel in this process

7

Report

central office makes monthly report to submit the management level staff for all the process.

DATA FLOW DESCRIPTIONS

DATA STORE CONTENTS

EXTERNAL ENITITY DEFINITIONS

  1. EINTITY RELATIONSHIP DIAGRAM
  2. ENTITY DESCRIPTIONS
  3. ATTRIBUTES

EINTITY NAME - Member

Primary Keys -

Foreign Keys -

Attributes

Data Type

Size

Comments

  1. OPTIONALITY AND DEGREE OF RELATIONSHIP
  2. ENTITY LIFE HISTORY
  3. NORMALIZATION
Lady using a tablet
Lady using a tablet

Comprehensive

Writing Services

Lady Using Tablet

Plagiarism-free
Always on Time

Marked to Standard

Order Now

Create a database design for the bed booking system including:

  • A set of fully normalized tables showing the normalization process for each. (10 marks)
  • Data Dictionary entries for all items included in the database design. (10 marks)

(a) NORMALIZATION

Normalization

I. UNFV. 3NF

Hostel ID Hostel ID

Hostel Name Hostel Name

Address Address

Division Division

Phone Phone

Fax Fax

Email Email

Date Date

Room No

Room type Hostel ID

Room Description Room No

Facilities Room type

Cost Cost

Room No

Room Description

Room type

Facilities

Choose the key

Hostel ID

III. 1 NFVI. Optimization

Hostel ID [Hostel]

Hostel Name Hostel ID

Address Hostel Name

Division Address

Phone Division

Fax Phone

Email Fax

Email

Hostel ID [Hostel Detail]

Room No Hostel ID

Room type Room No

Room Description Room type

Facilities per day Cost

Cost

[Room]

Room No

Room Description

[Room type]

Room type

Facilities

VI. 2 NFVIII. Data Model

Hostel ID

Hostel Name

Address

Division

Phone

Fax

Email

Date

Hostel ID

Room No

Room type

Cost

Room No

Room Description

Room type

Facilities

(b)DATA DICTIONARY

Title: National Hostelling Association

Type: Element

Author: Thida Hlaing

Date: 9th April 2010

No

Name

Alias

Definition

Occurrence

Picture

Note

1.

Hostel ID

-

-

1 value for hostel, many value for booking

Pic +-999

Range= H-001 to H-999

-

2.

Hostel Name

-

-

1 value for hostel, many value for booking

Pic +++++++++++++

Range= +-+++++++++++++

-

3.

Address

-

-

1 value for hostel, many value for booking

Pic

+++++++++++++++

Range= +-+++++++++++++++

-

4.

Division

-

-

1 value for hostel, many value for booking

Pic

+++++++++++++++

Range=+-+++++++++

-

5.

Phone

-

-

1 value for hostel, many value for booking

Pic ++++++++++++++

Range= x-++++++++++++++

-

6.

Fax

-

-

1 value for hostel, many value for booking

Pic ++++++++++++++

Range= x-++++++++++++++

-

7.

Email

-

-

1 value for hostel, many value for booking

Pic ++++++++++++++

-

8.

RoomNo

-

-

One value for room, many value for hostel, many value for booking

Pic +-+++++++++++

Range= R-00001 to R-99999

-

9.

Room Description

-

-

One value for room, many value for hostel, many value for booking

Pic

+++++++++++++++

Range= +-+++++++++++++++

-

10.

Room type

-

-

Lady using a tablet
Lady using a tablet

This Essay is

a Student's Work

Lady Using Tablet

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Examples of our work

Many value for room, many value for hostel, many value for booking

Pic ++++++++++++++

Range= x-+++++++++++++++

-

11.

Facilities

-

-

Many value for room type, many value for room, many value for hostel, many value for booking

Pic

+++++++++++++++

Range= +-++++++++++++++

-

12.

Customer ID

-

-

One value for customer, one value for booking

Pic= +++++++++

Range= C-00001 to C-99999

-

13.

Customer Name

-

-

One value for customer, one value for booking

Pic +++++++++++++++

Range= +-+++++++++++++++

-

14.

Address

-

-

One value for customer, one value for booking

Pic

+++++++++++++++

Range= +-+++++++++++++++

-

15.

Phone

-

-

One value for customer, one value for booking

Pic +++++++++++++++

Range= +-+++++++++++++++

-

16.

Email

-

-

One value for customer, one value for booking

Pic +++++++++++++++

Range= +-+++++++++++++++

-

17.

Fax

-

-

One value for customer, one value for booking

Pic ++++++++++++++

Range= +-+++++++++++++++

-

18.

Booking ID

-

-

One value for booking

Pic= +++++++++++++++

Range= Bk-000001 to Bk-999999

-

19.

Booking Date

-

-

One value for booking

Pic= Date/Time

20.

No of nights

-

-

Many value for booking

Pic= 9999

Range=0-9999

-

21.

Start date

-

-

Many value for booking

Pic= Date/time

-

22.

Must confirm date

-

-

Many value for booking

Pic= Date/Time

-

23.

Per day cost

-

Many value for room, many value for hostel, many value for booking,

Many value for room type

Pic= 999999

Range= 0 to 999999

-

24.

Payment ID

-

-

Many value for booking, one value for payment

Pic= ++++++++++++

Range= P-000001 to P-999999

-

25.

Payment

-

-

Many value for payment, many value for booking

Pic= 999999

Range= 0 to 999999

-

26.

Payment Date

-

-

Many value for payment, many value for booking

Date/ Time

-

27.

Left to pay

-

-

Many value for payment, many value for booking

Pic= 999999

Range= 0 to 999999

-

Title: National Hostelling Association

Type: Structure

Author: THIDA HLAING

Date: 9th April 2010

No

Name

Allias

Definition

Occurrence

Picture

Note

1

Hostel

-

Hostel=Hostel ID+ Hostel Name+ Address+ Division+ Phone+ Fax+ Email

-

-

-

2.

Room

-

Room= Room No+ Room Description

-

-

-

3.

Room Type

-

Room Type=Room Type+ Facilities

-

-

-

4.

Hostel Detail

-

Hostel Detail= Hostel ID+ Room No+ Room Type+ Per Day Cost

-

-

-

5.

Booking

-

Booking= Booking ID+ Customer ID+ Booking Date

-

-

-

6.

Booking Detail

-

Booking Detail= BookingID+HostelID+RoomNo+RoomType+NoOfNight+StartDate+MustConfirmDate

-

-

Confirm Date= 1 week later

7.

Customer

-

Customer=Customer ID+ Customer Name+ Address+ Phone+ Email+ Fax

-

-

-

8.

Payment

-

Payment=Payment ID+ Booking ID+ Left To Pay+ Payment Date

-

-

-

Title: National Hostelling Association

Type: Data store

Author: THIDA HLAING

Date: 9th April 2010

No

Name

Allas

Definition

Occurrence

Estimated size

Expected size

Picture

Note

1

Hostel

-

Hostel=Hostel ID+ Hostel Name+ Address+ Division+ Phone+ Fax+ Email

40

40

3% per year

-

Flow in: 1)Hostel Registration

Flow out: 2) Enquiry,

2

Room type

-

Room= Room No+ Room Description

5

5

1% per year

-

Flow in : 1) Hostel Registration

Flow out: 2) Enquiry,

3

Room

-

Room Type=Room Type+ Facilities

1600

1600

3% per year

-

Flow in : 1) Hostel Registration, 4) Booking

Flow out: 3) Searching

4

Hostel Detail

-

Hostel Detail= Hostel ID+ Room No+ Room Type+ Per Day Cost

1600

1600

-

Flow in: 1)Hostel Registration, 4)Booking

Flow out: 3) Searching

5

Booking

-

Booking= Booking ID+ Customer ID+ Booking Date

1400

1400

3% per year

-

Flow in: 4) Booking, 5)Payment

Flow out: 5) Payment

6

Customer

-

Customer=Customer ID+ Customer Name+ Address+ Phone+ Email+ Fax

1300

1300

5% per year

-

Flow in :4)Booking

Flow out: 4) Booking

7

Booking detail

-

Booking Detail= BookingID+HostelID+RoomNo+RoomType+NoOfNight+StartDate+MustConfirmDate

1400

1400

3% per year

-

Flow in: 4) Booking,

Flow out: 6) Send Email,

8

Payment

-

Payment=Payment ID+ Booking ID+ Left To Pay+ Payment Date

2800

2800

6% per year

-

Flow in:5) Payment,

Flow out: 5)Payment,


Title: National Hostelling Association

Type: Data flow

Author: THIDA HLAING

Date: 9th April 2010

No

Name

Alias

Definition

Occurrence

Picture

Note

1

Ask hostel information

-

Hostel ID+ Hostel Name+ Address+ Phone+ Room Type+ Room No+ Price

Monthly, seasonal variations

-

Source: 1 Hostel Registration

Destination: Hostel

2

Hostel information

-

Hostel ID+ Hostel Name+ Address+ Phone

Monthly, seasonal variations

-

Source: Hostel

Destination: 1 Hostel Registration

3

Write hostel information

-

Hostel ID+ Hostel Name+ Address+ Phone

Monthly, seasonal variations

-

Source: 1 Hostel Registration

Destination: D1 Hostel

4

Write Room type information

-

Room Type+ facilities+ Price

Monthly, seasonal variations

-

Source: 1 Hostel Registration

Destination: D2 Room Type

5

Write Room information

-

Room No+ Room description

Monthly, seasonal variations

-

Source: 1 Hostel Registration

Destination: D3 Room

6

Create Hostel Detail

-

Hostel ID+ Room type+ Room+ Cost

Monthly, seasonal variations

-

Source: 1 Hostel Registration

Destination: D4 Hostel Detail

7

Enquiry about hostel

-

Hostel Name+ Address+ Room Type

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: Customer

Destination: 2 Enquiry

8

Give hostel detail

-

Hostel Name+ Address+ Room Type

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: 2 Enquiry

Destination: Customer

9

Read Hostel information

-

Hostel Name+ Address+ Room Type

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: D1 Hostel

Destination: 2 Enquiry

10

Read Room type information

-

Room Type+ Facilities

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: D2 Hostel

Destination: 2 Enquiry

11

Ask available booking

-

Hostel Name+ Address+ Room type, start date, No of night

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: Customer

Destination: 3 Searching

12

Available booking information

-

Hostel Name+ Address+ Room type, start date, No of night, Price

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: 3 Searching

Destination: Customer

13

Read Hostel information

-

Hostel Name, Address

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: D1 Hostel

Destination: 3 Searching

14

Read Room type information

-

Room type+ Facilities+ Price

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: D2 Room Type

Destination: 3 Searching

15

Read Room information

-

Room No

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: D3 Room

Destination: 3 Searching

16

Read Hostel detail

-

Hostel ID+ Room type+ Room+ Cost

20 times per day, maximum 30, minimum 1, seasonal variations

-

Source: D4 Hostel Detail

Destination: 3 Searching

17

Make booking

-

Customer ID+ Hostel ID+ Room Type+ Room+ Start Date+ No of Nights

15 times per day, maximum 20, minimum 1,

Seasonal variations

-

Source: Customer

Destination: 4 Booking

18

Ask customer information

-

Customer ID+ Customer Name

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 4 Booking

Destination: Customer

19

Give Customer information and booking information

-

Customer ID+ Customer Name

Hostel ID+ Room Type+ Room+ Start Date+ No of Nights

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: Customer

Destination: 4 Booking

20

Read customer information

-

Customer ID+ Customer Name

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: D5 Customer

Destination: 4 Booking

21

Record new customer information

-

Customer ID+ Customer Name

7 times per days, maximum 15, minimum 1

-

Source: 4 Booking

Destination: D5 Customer

22

Read hostel information

-

Hostel ID+ Hostel Name

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: D1 Hostel

Destination: 4 Booking

23

Read room type information

-

Room type+ Facilities

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: D2 Room Type

Destination: 4 Booking

24

Read room information

-

Room No

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: D3 Room

Destination: 4 Booking

25

Update room information

-

Room No

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 4 Booking

Destination: D3 Room

26

Read Hostel detail

-

Hostel Name+ Address+ Room Type

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: D4 Hostel Detail

Destination: 4 Booking

27

Update Hostel detail

-

Hostel Name+ Address+ Room Type

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 4 Booking

Destination: D4 Hostel detail

28

Record booking

-

Booking ID+ Room type+ Room No

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 4 Booking

Destination: D6 Booking

29

Record booking detail

-

Booking ID+ Room type+ Room No+ Hostel ID+ No of night+ Start date

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 4 Booking

Destination: D7 Booking Detail

30

Pay deposit 10%

-

Booking ID+ Customer ID+ total amount

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: Customer

Destination: 5 Payment

31

Accept payment

-

Booking ID+ Customer ID + total amount

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 5 Payment

Destination: Customer

32

Ask full payment

-

Booking ID+ Customer ID+ total amount

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 5 Payment

Destination: Customer

33

Pay Full payment

-

Booking ID+ Customer ID+ total amount

15 times per days, maximum 20, minimum 1, seasonal variations

-

Source: Customer

Destination: 5 Payment

34

Read booking information

-

Booking ID+ Customer ID

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: D6 Booking

Destination: 5 Payment

35

Update booking information

-

Booking ID

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 5 Payment

Destination: D6 Booking

36

Write deposit information

-

Booking ID+ Customer ID

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 5 Payment

Destination: D8 Payment

37

Read deposit information

-

Booking ID+ Payment ID +Customer ID+ deposit

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: D8 Payment

Destination:5 Payment

38

Record full payment

-

Booking ID+ Payment ID+ Customer ID+ total amount

15 times per day, maximum 20, minimum 1, seasonal variations

-

Source: 5 Payment

Destination: D8 Payment

39

Send e-mail about booking information

-

Booking ID+ Payment ID+ Hostel ID

One per day

-

Source: 6 Send Email

Destination: Hostel

40

Read booking information

-

Booking ID

One per day

-

Source: D6 Booking

Destination: 6 Send Email

41

Read booking detail information

-

Hostel ID+ Booking ID

One per day

-

Source: D7 Booking detail

Destination: 6 Send Email

42

Read payment information

-

Payment ID

One per day

-

Source: D8 Payment

Destination: 6 Send Email

43

Submit hostel report

-

Hostel ID

Monthly

-

Source: 7 Report

Destination: Management

44

Submit room type report

-

Room type

Monthly

-

Source: 7 Report

Destination: Management

45

Submit room report

-

Room No

Monthly

-

Source: 7 Report

Destination: Management

46

Submit Hostel Detail report

-

Hostel ID+ Room type+ Room

Monthly

-

Source: 7 Report

Destination: Management

47

Submit customer report

-

Customer ID

Monthly

-

Source: 7 Report

Destination: Management

48

Submit booking report

-

Booking ID

Monthly

-

Source: 7 Report

Destination: Management

49

Submit booking Detail report

-

Booking ID+ Hostel ID+ Room type+ Room + Cost

Monthly

-

Source: 7 Report

Destination: Management

50

Submit payment report

-

Payment ID

Monthly

-

Source: 7 Report

Destination: Management

51

Read hostel information

-

Hostel ID

Monthly

-

Source: D1 Hostel

Destination: 7 Report

52

Read room type information

-

Room Type

Monthly

-

Source: D2 Room Type

Destination: 7 Report

53

Read room information

-

Room No

Monthly

-

Source: D3 Room

Destination: 7 Report

54

Read Hostel detail

-

Hostel ID+ Room Type+ Room

Monthly

-

Source: D4 Hostel detail

Destination: 7 Report

55

Read customer information

-

Customer ID

Monthly

-

Source: D5 Customer

Destination: 7 Report

56

Read booking information

-

Booking ID

Monthly

-

Source: D6 Booking

Destination: 7 Report

57

Read booking detail information

-

Booking ID+ Hostel ID+ Room type+ Room

Monthly

-

Source: D7 Booking detail

Destination: 7 Report

58

Read payment information

-

Payment ID

Monthly

-

Source: D8 Payment

Destination: 7 Report

(a) DRAFT SCREEN DESIGN

(b) PROTOTYPE

(c) VALIDATION RULES

Create a comprehensive, professional standard report (3 marks) describing in detail your system design for the bed booking system (3 marks). This should include the detail of Tasks 1-5 plus a discussion of the privacy/security issues relating to the taking and recording of customer payments during the booking process (6 marks). You should also include a discussion of any assumptions and choices you have made during process (3 marks) plus a review of your work including any weakness and suggested improvement (5 marks).

SYSTEM DESIGN FOR BED BOOKING SYSTEM

The NHA is currently running 40 hostels and want centralized reservation system and payment system. To check that the centralized system of the new IT system need to have all the information of the 40 shelters. The new system should record all information hostel, room type and room information in a data file or store data in one place. Due to the centralized system, the customer asks about the lodge in the reserve in the main office of free beds. There are too many shelters to verify that the request for which hostel room rate is free. So in the new system search process should be done in real time the location, number of nights and the date. On the other hand, for the booking process, the system needs to record all the booking information for 40 shelters in a file, reservation. In the reservation process, the system needs to record information about reservations, as the guest name, room type, room information, starting date, no of nights and customer information such as customer name, customer number and so on. Due to the centralized system, the system needs to record detailed information about the hostel booking and also send an email to the hostel where the client associated with full payment. If the client is new, the system needs to create the customer record. In the system of payment, the customer will pay at least 2 times and the registration system is the first series with the payment amount and the client makes the second set, the system will read out the payment form easily and accurately.

DETAILS OF TASK 1- 5 AND SECURITY ISSUE

This paper discusses the design of a new computerized system for the National Association of shelters. The NHA wants to centralize its own processing. So first, we need to do the context diagram to know about the NSA new computer system and know the extent you have to do computer functions. Then we have to define what the system wants to change the new computerized system and decide what to participate in the new system. After doing this, we design diagrams DFD know when and who will carry out the associated process and decide if the data is being stored. When we know where to store the data, these data stores must be connected together to perform the process as accurately define the relationship between them through the ERD diagram. And decide primary key and foreign key for each table in order to connect to each other. Then ELH diagram design for bed reservation for when the principle of reserve, operation and when you're done. To cross-check we also make the standard for the new system and decide which fields should be involved and define the name of the table. When the cross-check is OK, we designed the data dictionary for all elements in the design of databases to store and manage information needed to support an information system. Finally, we produce a prototype of new system of national health accounts and to define the validation rules for the system to ensure that the system will be complete and correct information, which are essential for the system.

ASSUMPTIONS

To change the computer system, it is assumed that all information hostel is centrally stored in the office and the information shelter. type of room, briefing room. When the client requests for search, the office of searches using these stored records. In addition, the office also takes the information from customers of all hostels and give ID to facilitate the search. We assume that each customer record to win at least one reservation. For payment, the payment is supposed to have at least twice, the first deposit and full install and the office will allow more than two times. And once the customer makes in installments, the office records the payment in the form of payment. Moreover, the client does not need to know your payment ID or ID slip, but only needs to know the booking number when you own the second series. We assume that there will be new customer reservation system and no new hostel booking system. New hostel will not be in the registration process hostel.

REVIEW OF WORK

Looking through the general allocation, we designed the system to the CNS hostelling association. There may be some weakness and some good points in this allocation model I've done. First, the system records all the information shelter and to request free search of the bed, we designed the system to find the bed free of automatically based on criteria that we have. When the customer makes the reservation, the system will record customer information, booking information completely. And users can book with many shelters at a time. During the checkout process, allow the user to pay at least two installments. For the design of the system to record the payment information on the particular file. To send email to shelters partners, the system will fill the information associated with reading the associated files. For the reporting process, the design of the system to inform the process.

WEAKNESS AND IMPROVEMENTS

To model hostelling system NHA, there is weakness and improvement in our system. The weakness is that the system does not display the information secretary of reserve records the booking process. So if something is a problem with the booking process, all problems will be taken by the director of the reserve of the central office. Therefore we suggest that all reservation clerk shall ensure that records the correct information of booking and payment. And the new system is a computer, so there may be some attack on the computer as a virus or lost data. Therefore we suggest that all records must be backed up daily and save on other means of backup such as CD.

REFERENCES

Books

Title :

Author Name :

ISBN :

Year :

Websites

URL :

Access date & Time: