5 System Design

5.1 Database Dictionary

A Database Dictionary contains metadata i.e data about the database. The data
dictionary is very important as it contains information such as what is in the
database who is allowed to access it, where is the database physically stored etc.
The users of the database normally don’t interact with the data dictionary , it is
only handled by the database administrators.
The data dictionary in general contains information about the following:
1. Names of all the database tables and their schemas.
2. Details about all the table in the database, such their owner.
3. Physical information about the table such as where they are stored and how.
4. Table constrains such as primary key attributes.
5. Information about the database views that are visible.

1. User:

2. Cancelation:

1
3. Category:

4. Customer:

5. Designation:

2
6. Employee:

7. Feed_Back:

8. Food Items:

Order

3
9. Type:

10.Order:

11.Order Details:

12.Tables:

4
 13.Table Booking:

14.Vegetables:

5.2 Entity Relationship Diagram

The relation upon the system is structure through a conceptual ER-Diagram, which
not only specifics the existential entities but also the standard relations through
which the system exists and the cardinalities that are necessary for the system state
to continue.
The Entity Relationship Diagram (ERD) depicts the relationship between the data
objects. The ERD is the notation that is used to conduct the date modeling activity
the attributes of each data object noted is the ERD can be described resign a data
object descriptions.
 The set of primary components that are identified by the ERD are
 Data object
 Relationships
 Attributes
 Various types of indicators.
 The primary purpose of the ERD is to represent data objects and their

5
Entity-Relationship model is used to represent a logical design of a database to be
created. In ER model, real world objects (or concepts) are abstracted as entities,
and different possible associations among them are modeled as relationships.
For example, student and school -- they are two entities. Students study in school.
So, these two entities are associated with a relationship "Studies in".

6
5.3 Data Flow Diagram
Data flow diagrams are commonly used during problem analysis. Data flow
diagrams are quite general and not limited to problem analysis for software
requirement specification. A DFD shows the flow of data through a system. It
views a system a function that transforms the inputs into desired outputs. Any
complex system does not perform this transformation into a single step and a data
will typically undergo a series of transformation before it becomes an output. The
DFD aims to capture the transformations that take place within a system to the
input data so that eventually the output data is produced.
The agent that performs the transformation of data from one state to another is
called a process. So, a DFD shows the movement of data through the different
transformations or processes in the system. Named circles show the processes and
data named arrows entering or leaving the bubbles represent flows.

Process Activity

The rectangle represents a source and sink and is a net originator or consumer of
data. A source or sink is typically outside the main system of study.

Originator

7
5.3.1 Context level
As the inherited feature of the function oriented design, we worked on the top-
down approach. According to this approach the main module (context diagram of
this software)
Is further decomposed into several lower level modules that perform distinct
functions.
As. A user (our client) can express his query in several forms like
 He wants to know about the reservation position i.e. confirmed or not
confirmed
 He is interested in the details of any flight of any airline
 He requests to reserve a seat in any of the flight of any airlines

5.3.2 First level DFD

In this module we are concerned with the attribute of any person, seeking
reservation in any flight.
Including his date of flight i.e. his name, address, seniority, etc

8
5.3.3 Second level DFD
The third sub module is of automated billing. It greatly ease out the problem of
manual calculation. The DFD of this sub module is

9
5.4 Activity Diagram
Activity diagrams fall under the category of behavioural diagrams in Unified
Modeling Language. It is a high level diagram used to visually represent the flow
of control in a system. It has similarities with traditional flow charts. However, it is
more powerful than a simple flow chart since it can represent various other
concepts like concurrent activities, their joining, and so on.
Activity diagrams, however, cannot depict the message passing among related
objects. As such, it can't be directly translated into code. These kind of diagrams
are suitable for confirming the logic to be implemented with the business users.
These diagrams are typically used when the business logic is complex. In simple
scenarios it can be avoided entirely.

10
From the given problem we can identify at least four different functionality offered
by the system:
• New User Login
• Book a ticket
• Update inventory

5.4.1 Activity Diagram of Login User

Customer Submit info

[Already registeared]

Not registeread

Verify information
Create new account
provided

Incorrect information
Correct information

Figure-01: Activity diagram for new user login

A new user login form for Online food shop System (either online or in paper), and
submits to the Administrator. Of course, an already login user can't create another
account for himself (or, herself). For users' who don't have an account already and
have submitted their registration forms, the Administrator verifies the information
provided, possibly against the central database used by the institution.If all
information have been provided correctly, administrator goes on with creating a

11
new account for the user. Otherwise, the user is asked to provide all and correct
information in his (her) login the account. Once a new account has been created for
the user, he (she) is being issued an ID , which is to be provided for any future
transaction in the web site.

5.4.2 Activity Diagram for food order

Search food

Existing customer

Not a customer

Availble
Show detailes

Not availble

Figure-02: Activity diagram for food order

One of the major events that occur in any customer is place food order to it's
members. Figure-02 tries to depict the workflow involved while order food.
Now let's focus on figure-03, which shows the typical workflow of inventory
update by the user. Note that since these are the tasks performed only by the user
(and no one else plays a role), we skip the swim lanes.

12
5.4.3 Activity Diagram of Update Food

No pending order

Order pending to add/remmove

Add new order Remove order

Update food

Figure-03: Activity diagram for updating new food

Addition of new ticket and cancel a food taken off from the shelves could be done
parallely. This means, one doesn't have to complete the task of addition of all new
food before doing any cancel. Merging of these two activities and the subsequent
Update inventory activity indicates that it is not required to complete all addition
and cancel before proceeding to update the database. That is, a few food could be
added, then update the database, then again continue with the tasks.

13
5.5 Sequence Diagram
The sequence diagram for the Customer of the Airline Reservation System would
be as follows:

14
 6 Testing

6.1 Test Case

Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. In fact,
testing is the one step in the software engineering process that could be viewed
as destructive rather than constructive.
A strategy for software testing integrates software test case design methods into
well planned series of steps that result in the successful construction of
software. Testing is the set of activities that can be planned in advance and
conducted systematically. The underlying motivation of program testing is to
affirm software quality with methods that can economically and effectively
apply to both strategic to both large and small-scale systems.

 Test Case 1- User Login

15
 Test Case 2- Create new system user:

16
 Test Case 3-Add new food category to the menu

17
 Test Case 4-Add new food to the menu

 Test Case 5- Payment for the ordered items:

18
19
 7 Scope, Limitations and Future Enhancement

7.1 Scope of the Project

Scope of this project is to replace the manual work of movie shop mgmt. system
with the new advanced computerized system. User does not need much training to
use this software, as this software is very user friendly and easy to use. It replaces
all the paper work also. In this software we can store thousands of records. It
replaces all the calculation works also as it automatically calculate and print the
bill. Some main advantages are:-

 Customer numbers are generated automatically by system itself.

 If any invalid entry done by the users which is nature of human being but checks
by the machine so this software gives the error message to the users to indicate
about the invalid entry.
 While transfer of any customer such as incoming customer, it will update both
the file and incoming customer so that if we want to know number of incoming
customer, it will be very easily for us.

7.2 Future Enhancement

Our future plan is to give a new form to our project which is a desktop application
.Making more reliable, realistic with many extra features such as:

 Make our online food ordering project more informative, attractive and
interactive to the user.

20
  Analyzing and designing software based on scientific survey rather than
ordinary survey.

 Converting our desktop based project into website based with feature
enriched which can support many more features that is not provided by an
ordinary website.

 During project enhancement we will never forget to make software from

user’s point of view rather than programming point of view.

 Providing user more entertainment such that they will not feel bore and can
spend more time with enthusiastically and willingly.

 Try to make a web based application

7.3 limitation
The Existing system includes problems like lack of time consuming, accuracy,
high cost, security problem, etc.
There are many problems in existing systems like:
 Manpower
 High cost
 Time and speed
 Security
 Complexity
 Maintenance

21
 Accuracy
 Storing

22
 8 Bibliography

8.1 Conclusion

It has been a great pleasure for me to work on this exciting and challenging project.
This project proved good for me as it provided practical knowledge of not only
programming in VB.NET application and no some extent Windows Application
and MSACCESS Server, but also about all handling procedure related with
“Airline Reservation System”. It also provides knowledge about the latest
technology used that will be great demand in future. This will provide better
opportunities and guidance in future in developing projects independently

Our futures plan is to make more features enriched software that can fulfill the
users demand

ADVANTAGES

 RMS will stores all the records permanently and also gives the raises and
deviations in the status of the restaurant in the markets.
 All the records of the current and ex-staffs will be stored in the database
 All the shift timings of staffs, salary, extra working time and charge etc. are also updated
daily.
 Managers can view the kitchen side, floor side and the counter side details
simultaneously and also can get details and updates from various branches.
 Any cancelations of parties are also updated.
 All the expenses per day will updated in the database daily.
 Also keeps the record of food items prepared and the sales of food and also the record of
balance food.
 Less use of manual work.

8.2 Bibliography

23
REFRENCE BOOKS

E. Balagurusamy , Object Oriented Programming with C++ , Tata McGraw-Hill

Publishing house , Copyright 1998.

The ‘C’ Programming language by Kernighan & Ritchie, Prentice Hall Publishing
house,Copyright 1988.

Teach yourself C by Yashwant Kanetkar, BPb Publishing house edition-6th.

Software engineering , K.K. Aggrawal, new age international publisher.

WEB REFERENCES

www.cprogramming.com/tutorial.html

www.cplusplus.com/doc/tutorial/

www.coronadoenterprises.com/tutorials/cpp/index.html/

24