Download Nyumbani Restaurant Information System: A Case Study in Waterfall Model Implementation and more Thesis Computer System Design and Architecture in PDF only on Docsity!
TABLE OF CONTENT
- 1 INTRODUCTION........................................................................................
- 1.1 REASONS FOR CHOOSING WATERFALL MODEL........................................
- 1.2 ADVANTAGES OF WATERFALL MODEL.......................................................
- 2 WATERFALL MODEL DIAGRAM..................................................................
- 2.1 STAGES OF THE WATERFALL MODEL........................................................
- 2.2 REASONS FOR CHOOSING CONTEXT DIAGRAM........................................
- 2.3 ADVANTAGES OF USING CONTEXT DIAGRAM...........................................
- 2.4 DATA FLOW DIAGRAM ( level 0)................................................................
NYUMBANI RESTAURANT SYSTEM
INTRODUCTION.
Nyumbani Restaurant is a business establishment which prepares and serves food and drink to customers in return for money, either paid before the meal, after the meal, or with a running tab (bill).
Nyumbani Restaurantis located at Kihonda in Morogoro Municipal.
Formally we had many challenges in controlling and tracking products since we used to run it manual in selling, purchasing, procurement, and ordering. After facing that problem we came up with a new idea to design and implement a desktop based system which will come with a solution to the problem facing.
It is providing customer tracking, labor management, kitchen productivity and much more every day.
2.0. METHODOLOGY / TECHINIQUE /METHOD: - is a set of standards for systems analysis and application design.
In order to implement the desktop Restaurant system the waterfall model is a most method to use.
The waterfall model is a sequential design process, often used in software development processes in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.
REASONS FOR CHOOSING WATERFALL MODEL
- It is very simple to understand and use.
- In a waterfall model, each phase must be completed fully before the next phase can begin.
- At the end of each phase, a review takes place to determine if the project is on the right path and whether or not to continue or discard the project.
- In waterfall model phases do not overlap.
ADVANTAGES OF WATERFALL MODEL
- Easy to manage due to the inflexibility of the model – each phase has specific deliverables and a review process.
- Phases are processed and completed one at a time.
- The system will provide the report of overall of purchasing and sales from date to date.
- SOFTWARE REQUIREMENT:- Identify, select and document the software features necessary to satisfy the system requirements.
- The software that we should use are Window Seven, Wamp server 2.0, Notepad ++, PHP (Script). HTML (Web designing). CSS, Java Scripts, Mysql.
- We are going to use window seven because in our system we will use Web Server which is called Wampserver.
- Wamp server version 2.0 web server that used to save web pages is manufactured for Microsoft Windows.
- Notepad ++ used for Php and Html code.
- In order to design this software the following three components are needed-:
(i) User Interface
(ii) Business Logic
(iii) Database
- In User interface we are going to use HTML, CSS and Java Scripts. This make the interface look very interactive.
- In Business Logic we are going to use PHP(Script). It is among of the programming where most of the scripts are written here to do some computations
- In Database , we are going to use Mysql. Mysql is a database management system.
- Lastly we are going to use Web server (WAMP Server). Web Server is a just a container where you can put web pages.
ANALYSIS:- Is a process of gathering information for the system.
System enhances the administrator to access the system information for the daily selling, purchasing and be able to get thereport on profit / loss of the entire sells.
DESIGN:- is a physical construction of the system like design, configuration of programming to be tested for performance.
Design phase is based on Context Diagram Model.
CONTEXT DIAGRAM is a diagram that defines the boundary between the system, or part of a system, and its environment, showing the entities that interact with it. This diagram is a high level view of a system.
REASONS FOR CHOOSING CONTEXT DIAGRAM
We are choosing the Context Diagram because it gives a clear summary of a whole system. (Easy to understand the system how will it be.)
ADVANTAGES OF USING CONTEXT DIAGRAM
- (^) Shows the scope and boundaries of a system at a glance including the other systems that interface with it.
- No technical knowledge is assumed or required to understand the diagram.
- Easy to draw and modify due to its limited notation.
- Easy to expand by adding different three levels of Data Flow Diagram.
1... CONTEXT DIAGRAM.
2.2.3. DATA FLOW DIAGRAM ( level 1)
Level 1:- Identify and draw the processes that make up the Level 0 process
I. Coding:- is the phase of Software Development project where developer’s actually input the source code into a computer that will be compiled into the final software program.
- Implement the program as designed in the earlier stages.
- The deliverable at the end of this stage is the Nyumbani Restaurant System.
II. Testing:- is the process of evaluationa software item to detect differences between given input and expected output.
- Test the software and record the results.
- A deliverable at the end of this stage is the updated test plan.
- (^) Another deliverable is the updated design specification.
III. Maintenance:- is used to describe various forms of computer or sever maintenance required to keep a computer system running properly.
Once the system is running in production environment, problems come up. The issues that are related to the system are solved only after deployment of the system. The problems arise from time to time and need to be solved. Provide maintenance and support of the software after every six month.
1.. CONCLUSION.
COMPUTER CENTER
COURSE TITLE: SYSTEM ANALYSIS & DESIGN
COURSE: 0221
TITLE: NYUMBANI RESTRAURANT INFORMATION SYSTEM
DOCUMENTATION
GROUP MEMBERS REG NO
1.MENLEY MGATA DIT/D/11/T/
2. MWAKIPITI VICTORIA REX DIT/D/12/T/
3. LULI MORIS ANTONY DIT/E/12/T/
4. FIDEL JOSEPHAT DIT/D/12/T/
5. LUZINGO JOSEPH DIT/D/12/T/
6. MATEMBO VERONICA JOSEPH DIT/E/12/T/
7. LIMATUKA SHAHAME ABDALLA DIT/D/12/T/
INSTRUCTOR NAME: NEEMA SUMARI.
