University Of Palestine. Department of Information Technology. Presents. Balmiera Restaurant. 1 st Quadmaster 2006. Introduction. Overall Description. Specific Requirements. Appendix. 1. 2. 3. 3. Contents. 1. Introduction.
1st Quadmaster 2006
1.1 Purpose of project:
We will mention in this part more detailed problems about the past system used in the restaurant:
Classical system, may found in any other restaurants.
Few processes done by computer.
Bills are stored as hardcopies, and they wait their own accountant to insert them into the PC
Their database (present system) isn't suitable for their large processes and their accounting department.
What also information we could gather in this small period of time, is that the restaurant consists of one manager and about eleven employees divided into three departments which are:
Management (Manager only)
Customer Reception & orders.
Update Goods sold file & Inventory.
The system has traditional processes which followed by the employees, manager and customers in order to make the system life cycle for example:
Customer orders there orders from reception workers.
Kitchen orders are done by cookers.
Daily Goods sold data and Daily inventory depletion amounts are formatted by the accountant.
All formatted data are submitted to the manager.
The system will be used in the specified place which the group has assigned, the system may be ready to use in about two to three months starting from this report date.
system users include the Manager, accountant, restaurant workers and may include a secretary as additional part to be familiar with the new system and finish the live treatment and action that should be done without waiting the accountant.
2.1 Product Perspective:
Daily goods sold amount
(Fig. 1.1.)2. Overall Description
2.1 Product Perspective:
Software items which are represented by database, data flow and programming codes; makes the relations between the different part of the system.
This Diagram shows Data flow for fast food of the system:
System interfaces are different, depends on the way of getting the order, the webpage on the web represents the system interface when getting the order by the web, in the other hand, reception employee is the system interface when getting the order by personally coming or by phone.
2.2 Product Functions:
Below is a list of all functions that found in the system with a description of every function and its priority.
2.3 User Characteristics:
As known, any system has constraints which limits its usage and benefit.
2.5 Assumptions and Dependencies:
2.6 Apportioning of Requirements:
The system software requirements that is needed for the system to be developed are parted to three main parts:
3.1 External Interfaces:
3.1.1 Navigation list:
Include the main parts and pages links of the website, it allows you to move between different pages.
3.1.2 Links an Think list:
Display some collection of restaurant news links and other entertainment links.
3.1.3 Login table:
From this table registered clients and users could login to the system.
3.1.4 Explanation column:
This column displays a detailed information related to the part where you are.
3.2 External Interface Requirements: There is no needed for any external software or hardware, the system is independent that can be run with no external support
3.3 Performance Requirements: Using the system in its top performance requires a best internet connection, Microsoft Windows XP and the Latest version of internet explorer program.
3.4 Design Constraints: Our system designing work didn’t have any constraints that limits its ranges and environment.
3.5 Logical Database Requirements: The main logical database program used in developing this system is Microsoft Office Access, where we store all related date required to run the system and storing dataflow
Ahmed Al Toul
Hassan Abu Daqen
Miss. Eman Al Ajrami
Miss. Yassmen El Bobo