Restaurant Billing System

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 7
At a glance
Powered by AI
The key takeaways are that the document discusses a restaurant billing system and describes the incremental model of software development.

The incremental model is a process where requirements are broken down into modules that each pass through requirements, design, coding and testing phases, with each iteration adding functionality to the previous release. The main phases discussed are requirements analysis, design, coding, and testing.

Some advantages are that it generates working software quickly, is flexible to changes, and risks can be identified and addressed early. Disadvantages include needing good upfront planning and design, and total costs may be higher than other models.

RESTAURANT BILLING SYSTEM

INTRODUCTION:
Restaurant billing system is the profession of managing a restaurant
billing. It includes the major function of planning, organizing; efficiently
and effectively plan menus at profitable prices. This system will help to
manage the restaurant billing system systematically; we will provide
software that can be used by the cashier.

This is a software package to facilitate ordering within a restaurant. The


customer is able to view the menu in an electronic gadget and organize a bill
through that electronic gadget.

Some key points are:

 It helps the restaurant manager to manage the restaurant more efficiently and
effectively by computerizing Meal Ordering, billing and many more things.
 It Increases the Security.
 It avoids Paper work.

SOFTWARE DEVELOPMENT LIFE CYCLE


The Software development life cycle (SDLC) is a conceptual model which is used
in project to describe the stages involved to build a project .There are some
methods work better for specific types of projects .But we all know that in the final
analysis, the most important factor for the success of a project that what type of
software model we should use to build our software and how closely the plan was
followed.
THE INCREMENTAL MODEL

Incremental Model is a process of software development in which the requirements


are broken down into multiple standard modules of software development cycle.

Each iteration passes through the requirements, design, coding and testing
phases. And each times it adds function to previous release until all designed
functionality has been implemented.

Incremental Phases Activities performed in


incremental phases
Requirement Analysis Requirements and specification of the
software are collected.
Design Some high-end function is designed
during this stage.
Code Coding of software is done during this
stage.
Test Once the system is deployed, it goes
through the testing phase.

It is mentioned that we are supposed to choose incremental model for our


restaurant billing system software to develop an accurate system. In traditional, the
system is time consuming, so for better understanding we are using digital billing
system which is easy to understand using latest techniques and ideas.

Each increment creates an extension of the system, building on the previous step.
One example for such an approach is the creation of a LOGIN system in two steps.
First we create a login page for admin and customers.
Advantages of Incremental model:

 Generates working software quickly and early during the software life cycle.
 This model is more flexible – less costly to change scope and requirements.
 It is easier to test and debug during a smaller iteration.
 In this model customer can respond to each built.
 Lowers initial delivery cost.
 Easier to manage risk because risky pieces are identified and handled during
iteration.

Disadvantages of Incremental model:

 Needs good planning and design.


 Needs a clear and complete definition of the whole system before it can be
broken down and built incrementally.
 Total cost is high among waterfall model.

Reasons for choosing model:

 Requirements of the complete system are clearly defined and understood.


 Major requirements must be defined; however, some details can evolve with
time.
 There is a need to get a product to the market early.
 A new technology is being used,
 Resources with needed skill set are not available,
 There are some high risk features and goals.
Comparison among different process model

Concerns Waterfall Model Evolutionary Agile Model


Model
Requirement Formal System Requirement and User stories and
Elicitation Specification prototyping scenario

Change Management Changes are Accept changes Accept changes


minimum or and will introduce and re-prioritize
ignored. changes at future with current
increment version. objective for
future.
Validation Testing left to the Testing done at the Testing done in
end project. end of each parallel with
iteration. development in
each iteration.
Delivery Slow and delivered Delivers Always delivers
the whole project at increasingly incremental
the end of the complete software working software
project. when requirements with prioritized
and designs are features.
defined.
Design Modeling Excessive and Limited but may Minimum with just
lengthy. grow quickly. enough details to
meet current need.

You might also like