Software Engineering: SRS Document, Process Model, Use Cases, and More

This article discusses software engineering process models, requirement verification methods, use cases, and more. It includes a detailed SRS document, context diagram, activity diagram, sequence diagram, and class diagram. The article also covers user requirements, system specifications, software testing, and deployment strategies. The subject is software engineering and the course code and college/university are not mentioned.

Software Engineering

Table of Contents
1 SRS Document...................................................................................................................2
2 Software Engineering Process Model.............................................................................2
3 Requirement Verification Method..................................................................................4
4 Context Diagram...............................................................................................................5
5 Use Cases...........................................................................................................................6
6 Use Case Description........................................................................................................7
7 Activity Diagram.............................................................................................................14
8 Sequence Diagram..........................................................................................................16
9 Class diagram..................................................................................................................17
10 User Requirements......................................................................................................19
10.1 High level user requirements..............................................................................19
10.2 Sub-system Level Requirements.........................................................................19
10.3 Segment Level Requirements.............................................................................20
10.4 Functional requirements.....................................................................................22
10.5 Non-functional requirements..............................................................................23
11 System Specification....................................................................................................24
11.1 Technical Feasibility............................................................................................24
11.2 Economic Feasibility............................................................................................25
11.3 Operational Feasibility........................................................................................26
12 Software Testing and Acceptance Criteria...............................................................27
13 Proposed Deployment Strategy..................................................................................29
References...............................................................................................................................31
1

1 SRS Document
This project aims to prepare the consolidated version of extended SAS analysis and
Design. This project is based on Assignment 1 that is restaurant in the fast food industry.
This project update the existing SRS document by discusses the software engineering
process models, requirement verification method, UML diagram like Context diagram, class
diagram, description of use case, sequence diagram, activity diagram and the Software
testing. These are will be discussed and analysed in detail.
2 Software Engineering Process Model
A software process (otherwise called software strategy) is an arrangement of related
exercises that prompts the generation of the software. Such exercises might include
software improvement right from the beginning, or, adjusting a current framework. Any
kind of software process should incorporate accompanying the following exercises [1]:
1. Software specification: Defining software’s fundamental functionalities and
obliges around them.
2. Software designing and implementation: Software must be composed and
customized.
3. Software check and approval: Software should fit within its determination and
must meet the needs of the customer.
4. Software advancement: Software will be altered for meeting the customer as
well as the market prerequisite changes.
Practically speaking incorporates sub-exercises, for example, necessities approval,
compositional outline, unit testing, and so on. There are additionally supporting exercises,
for example, design and change administration, quality affirmation, venture administration,
customer encounter. Alongside different exercises expect to enhance the above exercises
by presenting new strategies, apparatuses, following the best practice, process
institutionalization (so the assorted variety of software forms is diminished), and so on.
When we discuss a procedure, we more often than not discuss the exercises in it. Be that as
it may, a procedure additionally incorporates the procedure portrayal, which incorporates:
• Software: The results of a movement. For instance, the result of engineering plan
possibly a model for the software design.
2

• Roles: The obligations of the general population engaged with the procedure. For
instance, the undertaking director, developer, and so forth.
• Pre and post conditions: The conditions that must be valid when a movement. For
instance, the pre-state of the building configuration is the necessities have which
the customer affirms, when the post condition refers the graphical representation
the engineering will be explored.
Here, we are utilizing the proto typing software process model.
Generally, model denotes a rendition of framework or framework’s part which
instantly created for checking the needs of the customer or possibility of certain sketched
options. Similarly, model is valuable if the customer or the designer are not sure enough
about the necessities, or the proficiency, calculations, reaction time, business rules etc. For
prototyping, the whole procedure of advertisement, the customer is involved and this
improves the customer’s acceptance probability, for the final execution. When some of the
models are developed based on the longing of getting disposed, sometimes it is conceivable
to create the model as the framework that works well.
Usage of software model is possible:
For building the prerequisites, a model could be helpful with elicitation and for the approval
of framework’s needs. It enables customers to try various things with the framework, hence
it refines the necessities. It is possible to get new ideas about the needs, and explore the
territories of software’s quality and its limitations. Moreover, as the model is produced, it
could disclose the errors in the prerequisites. The determination possibly can be altered
later for reflecting the progressions. The model could complete condescend examinations
for checking the proposed plan’s possibility, in the framework [2].
The periods of a model are:
• Establish goals: The targets of the model ought to be made express from the
beginning of the procedure.
• Define model Functionless: Decides the list of information sources along with the
model’s normal outcomes. For diminishing the cost of prototyping and speeding up
the plan of conveyance, you could disregard certain Functionless. For instance,
reaction time and memory use except if they are pertinent to the model’s goal.
• Model Designing: Underlying model is produced which incorporates only the UIs.
3

• Model Evaluation: As the customers are ready for utilizing the model, they must
find the prerequisites blunders. By using the both input the determinations and
model could be improved. When the progressions will be presented, a rehash of
stage-3 and may be needed.
• Prototyping is more independent, complete the improvement procedure, yet
rather a method for dealing with the utilized regards for full techniques.
3 Requirement Verification Method
The requirement verification method are,
Confirmation by Test includes uncommon test gear and additionally instrumentation.
It additionally includes running different "tests" to gather information on the framework
that will indicate evidence the prerequisite has been met. Since there are different
arrangements of information gathered, we at that point need to dissect the information to
make an assurance regardless of whether the check achievement criteria has been met to
state the confirmation by Test was fruitful. Before running these tests we may examine the
confirmation aftereffects of the necessities to this prerequisite. For this situation, the
strategy for confirmation is Test.
Confirmation by Demonstration likewise includes running no less than one "test"
without uncommon test hardware or instrumentation to gather the arrangements of
information that we dissect to demonstrate the framework meets a necessity. Once more,
before running these tests we may assess the confirmation aftereffects of the necessities to
this prerequisite. For this situation, the technique for check is Demonstration [3].
Check by Analysis is utilized when one of alternate strategies isn't suitable or you
can't stand to utilize Verification by Test for each prerequisite or you can't complete a
conclusion to-end test yet just on parts of the framework. For this situation you gather
information on parts of the framework by means of test. At that point in light of this
information and your insight into the framework outline, you make a designing judgment
regardless of whether the characterized achievement criteria has been met keeping in mind
the end goal to reason that confirmation by Analysis was fruitful. For this situation, despite
the fact that I may have run a few tests to gather the information, the strategy for check is
Analysis.
4

Confirmation by Inspection is the point at which you can utilize one of your faculties to
demonstrate if the framework meets a prerequisite. You don't need to practice the
framework, you can watch the aftereffects of your perceptions or reviews to demonstrate
the framework meets a necessity.
4 Context Diagram
A system of the context diagram that can used for the diagram of the engineering
explains the limitations among the systems, system parts, entities and its environment’s
representation, which allows interaction. The system of the diagram that can use for the
high levels view of the context diagram. It is similar to a block diagram. The external entities’
system context diagrams can represent the system interaction. Such system that can used of
the requirement functional specification. The context diagram that used for the picture and
the data center with hardly any details about the individual structure surrounding all its
interacting systems, and the environmental activities. The system context diagram’s
objective refers to concentrate on the events and the external factors which must be
considered for the development of a whole set of system prerequisites and limitations of
the diagram.
The Content Diagram is represented as follows.
5

In context diagram, the customer should be able to register to create an account in the
information system. The customer able to login into their account. Once customer login
successfully, make an order. A customer or staff should be able to view orders to track the
status of the pending order for example getting the remaining waiting time. A staff updates
the status of the order to either ready when the order is ready for pickup and complete
when the order is has been picked up by the customer. A staff adds payment for an order
when the customer comes to pick up the order. Update or delete an order, Delete a
customer record from the system, an admin adds, updates or deletes a branch and an
admin adds a staff member to a certain branch. Finally, admin generate the report for the
order [4].
5 Use Cases
Use case diagram refers to a representation which is easy to understand for showing
the user's interaction with the system that shows the relationship between the user and the
different use cases in which there is involvement of the user. This diagram describes the
actions in terms of the behaviour diagrams where certain system or the subject must or
could perform the actions based on collaboration with a single or multiple external system
users or called as the actors. The use case diagram’s primary objective includes, showing the
interactions with your system, and shows the major goals which the system achieves with
them. The stakeholder is referred as the primary actor of the use case diagram, who is called
on the system for delivering its services. The use case analysis denotes to a method which is
utilized for identifying the system requirements that are linked with the software or the
process design. The information is utilized for both defining the utilized processes as well as
defining the classes. The classes are the collection of actors and processes that are utilized
in both in the use case diagram and the complete overall use case diagram. For
demonstrating various methods for the user to interact with the system, the use case
analysis diagram in UML for is used.
The section provides the details of the identified use cases.
Requirement Description
Customer registration The customer should be able to register to create an account in the
6

information system
Customer login The customer should be able to login into their account
Make order A customer should be able to make an order
View order A customer or staff should be able to view orders to track the
status of the pending order for example getting the remaining
waiting time
Staff login A staff logins
Process order A customer process an order made by a customer. Processing an
order means accepting the order so that the order can be prepared
and packaged. When the order is ready the status of the order is
updated to ready for customer pickup.
Update order status A staff updates the status of the order to either ready when the
order is ready for pickup and complete when the order is has been
picked up by the customer
Add payment A staff adds payment for an order when the customer comes to
pick up the order
Manage order Update or delete an order
Manage customer Delete a customer record from the system
Manage branch An admin adds, updates or deletes a branch
Add staff An admin adds a staff member to a certain branch
Generate Generate reports for orders. Report can be a daily or monthly
report
6 Use Case Description
Use case Description of overall system is shown below.
Requirement Actor Description Inputs Outputs
Customer
registration
Customer The customer
should be able
to register to
create an
Customer
details; First
name, last
name, email,
Success: if the
registration is
successful
Fail; if the
7

account in the
information
system
password registration was
not successful
Customer login Customer The customer
should be able
to login into
their account
Email and
password
Login successful or
login failed if the
login credentials
are not correct
Make order Customer A customer
should be able
to make an
order
Order Order ID,
expected waiting
time
View order Customer A customer or
staff should be
able to view
orders to track
the status of the
pending order
for example
getting the
remaining
waiting time
Order ID Order status
Staff login staff A staff logins staffID:
password
Login successful or
login failed if the
login credentials
are not correct
Process order Staff A customer
process an order
made by a
customer.
Processing an
order means
accepting the
OrderID Order processed
successfully
8

order so that
the order can be
prepared and
packaged. When
the order is
ready the status
of the order is
updated to
ready for
customer
pickup.
Update order
status
staff A staff updates
the status of the
order to either
ready when the
order is ready
for pickup and
complete when
the order is has
been picked up
by the customer
orderID, status Order status
updated
Add payment staff A staff adds
payment for an
order when the
customer comes
to pick up the
order
oderID, amount Payment received
if the amount is
equal or greater
than the cost of
the order
Manage order Admin Update or
delete an order
OrderID Update successful
Manage
customer
Admin Delete a
customer record
customerID Customer record
removed
9

from the system successfully
Manage branch Admin An admin adds,
updates or
deletes a branch
branchID,name,
location
Branch added,
updated or
deleted
successfully if the
operation is
successful
Add staff Admin An admin adds a
staff member to
a certain branch
staffID, name,
email, password
Generate Report Generate
reports for
orders. Report
can be a daily or
monthly report
Type Report is
displayed in a
tabular format
Use Case diagram is shown below.
For customer
The customer should be able to register to create an account in the information system. The
customer able to login into their account. Once customer login successfully, make an order.
A customer or staff should be able to view orders to track the status of the pending order
for example getting the remaining waiting time [5].
10

For Staff
A staff updates the status of the order to either ready when the order is ready for
pickup and complete when the order is has been picked up by the customer. A staff adds
payment for an order when the customer comes to pick up the order [6].
11

For Admin,
Update or delete an order, Delete a customer record from the system, an admin
adds, updates or deletes a branch and an admin adds a staff member to a certain branch.
For Report
This use case is used to generate the report for the order.
12

The below figure illustrates the overall Use case diagram.
13

In the use case diagram, customer needs to register to create an account in the
information system. After, customer login to their account. Once customer login
successfully, view the food items and make the order. A customer or staff should be able to
view orders to track the status of the pending order. A staff updates the status of the order
to either ready when the order is ready for pickup and complete when the order is has been
picked up by the customer. A staff adds payment for an order when the customer comes to
pick up the order. The customer needs to Update or delete an order. The admin and staff
are needs to delete a customer record from the system, an admin adds, updates or deletes
a branch and an admin adds a staff member to a certain branch. Finally, admin generate the
report for the order.
7 Activity Diagram
It is another significant diagram representation used in UML for describing the system’s
dynamic aspects. This type of diagram actually provides the flowchart for representing the
beginning flow of an activity to the other activity. The system operation is what referred as
activity. From one operation to the other, the control flow will be drawn. In Unified
Modelling Language, the activity diagram refers to a graphical representation of the
procedural system activities that are executed and considers the variation of the state chart
diagram. It is a diagram which describes the parallel activities and the conditional activities,
use cases and system functions in a full detailed level of software system, to analyze the
process of the whole diagram.
Activity diagram for Customer process is illustrated as below.
14

The above activity diagram is used to show the customer process. The customer
needs to register to create an account in the information system. After, customer login to
their account. Once customer login successfully, view the food items and make the order. A
customer should be able to view orders to track the status of the pending order. A staff adds
payment for an order when the customer comes to pick up the order. The customer needs
to Update or delete an order.
Activity diagram for staff process is shown below.
15

The above activity diagram is used to provide the staff process. The staff needs to
login to their account. Once staff login successfully, view the food items and process the
order. A \ staff should be able to view orders to track the status of the pending order. A staff
updates the status of the order to either ready when the order is ready for pickup and
complete when the order is has been picked up by the customer. A staff adds payment for
an order when the customer comes to pick up the order. The staff are needs to delete a
customer record from the system.
Activity diagram for admin process is illustrated as below.
The above activity diagram is used to provide the admin process. The admin login to
their account. Once admin login successfully, view the food items and process the order.
16

The admin and staff are needs to delete a customer record from the system. An admin adds,
updates or deletes a branch. And, also admin adds a staff member to a certain branch.
Finally, admin generate the report for the order.
8 Sequence Diagram
It is a diagram that represents the object interactions that is arranged in terms of time
sequence. It represents the involved classes and objects in the scenario. The sequence of
messages exchanged among the objects are required to conduct the scenario’s
functionality. This diagram is basically linked with the use case diagram, in the Logical View
of the system under development. It is a model that is used for the flow of logic inside the
system, which is represented visually that enables you both to document and also validates
the logic. Moreover, it is mainly, and are utilized for both designing purpose and for
conducting analysis. The sequence diagram that can used for the good diagram to use for
the document a system requirements and to flush out a systems design. The reason the
sequence diagram is so useful is because it shows the interaction logic between the objects
in the system in the time order that the interaction take place of the workflow diagram.
Sequence diagram is shown below.
17

In sequence diagram, the customer needs to register to create an account in the
information system. After, customer login to their account. Once customer login
successfully, view the food items and process the order. A staff should be able to view
orders to track the status of the pending order. A staff updates the status of the order to
either ready when the order is ready for pickup and complete when the order is has been
picked up by the customer. A staff adds payment for an order while the customer returns
for picking up the order. Then, admin and staff are needs to delete a customer record from
the system. And, also admin adds a staff member to a certain branch. Finally, admin
generate the report for the order.
9 Class diagram
It is mainly used for illustrating the relationship between the class dependencies in the
unified modelling languages. The class can be used for defines as the variables and methods
in an objects which used in the context, in which is a specific unit of code representing the
18

entity in the program diagram. In the class diagram, class can arranged in the groups which
share common characteristics, functions and attributes. It is a diagram which denotes the
work flow, where the classes refers to the boxes which will be portrayed, in every single box
containing three rectangles boxes inside it. Top rectangle comprises the class name; then
middle rectangles has the class attributes. The lower rectangles contain methods, which are
also known as class operations. The lines defining the relationships are known as
associations, where the association between the classes are represented [6].
Class diagram is shown below.
In class diagram, the customer needs to register to create an account in the information
system. After, customer login to their account. Once customer login successfully, view the
food items and make the order. A customer or staff should be able to view orders to track
the status of the pending order. A staff updates the status of the order to either ready when
the order is ready for pickup and complete when the order is has been picked up by the
customer. A staff adds payment for an order when the customer comes to pick up the order.
Finally, admin generate the report for the order.
19

10 User Requirements
10.1 High level user requirements
 Framework underpins local dialect of the nation and other usually talked dialects.
 Customer must ought to have the capacity to put arrange as indicated by his
decisions
 Customer ought to have the capacity to make payment utilizing
money/credit/debit.
 Customer ought to get a receipt and a token number in the wake of making the
payment.
 The framework ought to have the capacity to take any kind of information
sources, once he contacts the individual catch.
 The framework ought to have the capacity to compute the bill and provoke the
customer for the method of payment and create a receipt.
 The framework ought to have the capacity to pass on the request in the kitchen
for preparing.
 The framework ought to be anchored to confine the quantity of individuals to
enter the framework to roll out improvements in the menu and its things.
 The framework ought to be strong for unpleasant utilization.
 Framework has a money return system which surrenders discount to 5 $ in coins.
 Framework ought to have the capacity to convey to the focal database to check
the validness of the credit [7].
 Framework ought to permit Store supervisor to include/erase/modify framework
things.
 The framework must be a graphical UI for simple utilize and comprehension.
 The framework must have the capacity to provoke the customer for the following
stage to be performed amid the way toward utilizing the framework.
10.2 Sub-system Level Requirements
Beginning at the sub-framework level, other partner necessities are considered, maybe in
light of the fact that the subsystem components will be utilized over a software offering.
20

Originators taking a shot at the sub-framework components give input to the framework
level fashioners.
Requesting and Processing System
 The framework will give line administration by passing requests successively to
kitchen (FIFO) by allocating request numbers to them.
 Client ought to have the capacity to arrange thing either by name or by number (for
combo bargains).
 Framework will bolster local and other regularly talked dialect in the nation.
 A normal request takes around 1 moment to finish with a change of 10 seconds.
 Client takes 2 minutes on a normal to finish and requesting process.
 Framework will be furnished with a standard QWERTY console for taking sources of
info.
Payment System
 This Order number will be imprinted on the bill that client gets.
 Framework will have the capacity to acknowledge money and coins.
 Framework ought to have the capacity to acknowledge charge/Visas.
 Framework will acknowledge just $1, 5, 10, 20 bills and nickel, dime, quarter
category of coins.
 Framework will dismiss pennies and $50, $100 bills.
 Framework won't permit putting in $1 coin.
 Money return will return change just in coins [8].
10.3 Segment Level Requirements
Card Acceptor/Reader
 Framework will be outfitted with a card peruser with constructed it keypad
(containing all digits and extraordinary capacity keys comparing to CANCEL, OK, #
and so on).
 This card peruser ought to have the capacity to peruse the card data whenever
swiped at a speed > 1 m/s.
 Card peruser will have a vertical space on the correct hand side of the keypad.
Display
 Framework will show all the menu things in symbols/designs organize for choosing.
21

 Framework will provoke the client for method of payment.
 Request will be exchanged to the kitchen contact screen momentarily once the client
does the payment.
 Framework will show the request successively on the kitchen screen with a forward
and back catch at the base.
 Contacting a request on the kitchen screen will provoke the framework that the
request has been conveyed and the screen will be moved forward.
 Any blunder message amid such a procedure will be accounted for to the client on
the touch screen educating him to make any further move.
 There will be a high complexity between the forefront and the foundation of the
showcase for simple perusing capacities [9].
 All through the requesting procedure all the content showed on the screen will be
either more prominent than 10 or under 18 text dimension with the goal that all
clients (youthful, grown-up, old) can read it.
Modem
 Modem ought to have the capacity to finish an exchange (dialling, sending data,
accepting data) in 15 seconds or less consistently.
 When associated with the bank framework will supply the card data to the bank
database, will question the card legitimacy and will supply the sum to be charged to
the card.
Software
 Framework will be anchored to give get to rights just to the framework chairman.
For this a login ID and a secret phrase will be allotted which could be changed. Secret
phrase won't be obvious to spectators while composing for expanded security.
 Framework will deny access to change the substance if the login/secret word both
are off base by giving a mistake message [10].
Requirements of the information system describe what is expected of the system by the
customer and what standard expectations that the information system should meet [3].
Thus there are two types of requirements;
 Functional requirements
 Non-functional requirements
22

10.4 Functional requirements
Functional necessities of the data framework depict the normal conduct of the
framework in light of the business rules got from the customer's prerequisites and
prerequisites gathering results. In this manner to think of the necessities the improvement
group should do prerequisites assembling by utilization of various systems. A portion of the
strategies that can be utilized for the proposed data framework incorporate;
 Interviews-Requirements can be assembled utilizing interviews where by the
improvement group utilizes semi-organized meetings on the staff of the business to
gather prerequisites about the normal data framework. Semi-organized meetings
are a mix of organized and unstructured meeting which include following an
arrangement of inquiries addresses and yet enabling the respondent to veer off
from the inquiries in order to get more data. The outcomes gathered from every
one of the meetings are then assessed and investigated to think of the
prerequisites report.
 Observation-Observation is another great necessity gathering method that can be
utilized to accumulate prerequisites about the proposed data framework. The
commonplace procedure of social occasion prerequisites for the proposed
framework will include sending advancement colleagues to each branch for a
couple of days. Each colleague can go about as a staff of the business for a couple
of days amid which they will watch the business procedure and afterward they can
set up a necessities report in view of their perceptions of the business procedure.
Every one of the records from each colleague are then investigated to get the
necessities of the data framework. This system is critical as a complimentary
procedure to interviews since it guarantees that the improvement group gets direct
understanding of the business procedure therefore guaranteeing that any
prerequisite missed by the customer is seen on the beginning times of the
procedure life cycle.
Examination of the outcomes accomplished from the two strategies makes up the
Functional necessities of the data framework. The Functional necessities can be appeared as
far as the info expected by the framework and the yield expected by the client.
23

10.5 Non-functional requirements
Non-Functional prerequisites of a data framework are utilized to indicate activity of
Functional necessities. They indicate the criteria through activity of Functional necessities is
judged. Non-Functional necessities of the proposed framework are;
 Performance-The proposed framework ought to have the capacity to play out all
activities utilizing minimal measure of time conceivable. For instance while
checking the status of a request, the client ought to have the capacity to get the
status of the request inside 3 seconds and for an administrator producing a
report ought not take over 5 seconds for the answer to be shown in an
unthinkable arrangement [11].
 Scalability-The versatility of a data framework is the capacity of the framework to
deal with or process various tasks without falling flat or encountering
bottlenecks. This is essential for the proposed framework for the most part in
light of the fact that the framework will keep running in excess of one place while
utilizing one focal database along these lines the framework ought to have the
capacity to deal with all tasks both amid the pinnacle and lean long stretches of
business activity.
 Reliability-The proposed data framework ought to be dependable consistently.
Unwavering quality indicates that the application ought to have the capacity to
perform what is anticipated from it at some random time. For instance for a
director producing a report the framework ought to have the capacity to create
the predetermined report without disappointments.
 Robustness-the proposed data framework ought to be vigorous and ought to
have a high level of recoverability. This guarantees the application can recoup if
there should be an occurrence of any mistakes. The application ought to be
produced while considering probability of mistakes so as to ensure that the
framework does not stop in the event of an error. This implies the advancement
group should uphold instruments that ensure there is proceeded with task in the
event of a blunder to forestall pulverizes by the framework.
 Availability-The proposed framework ought to be accessible consistently. This
implies the any client ought to have the capacity to utilize the framework
whenever of the day.
24

 Maintainability-The proposed framework ought to be viable. Viability guarantees
that the framework can be refreshed if there should be an occurrence of any
bugs or updates in shape on patches. Guaranteeing viability of the framework
makes it simple to refresh the framework after its organization.
 Usability-The data framework ought to be usable to every one of the clients. The
outline and task of the framework ought to take after a short-sighted way to deal
with ensure that all clients can utilize it. The program ought not to be too difficult
to utilize making it harder than the past framework which is being supplanted.
 Data uprightness - The information produced and handled by the framework
ought to be the right information to ensure the reports created anytime are the
right reports.
 Secure-The framework ought to be secure consistently. Vital security
components ought to be executed to ensure malignant clients are not capable
access the application. This may incorporate utilizing of encryption and solid
secret phrase strategies like changing the secret word for the staff like clockwork.
11 System Specification
The system specification are discussed in below.
11.1 Technical Feasibility
Considered technical Feasibility thinks regarding the new proposed framework’s
specialized prerequisites for the restaurant, as it would viably fulfil the needs of the
workers. Contemplations of the specialized necessities are later contrasted with the
specialized ability of the restaurant. Is the task conceivable with current innovation? The
present need of building the new framework is conceivable with the present innovation
accessible. The online brought together application for Le Diner Restaurant can be executed
in view of J2EE system. As of now the new framework innovation is accessible with different
outsider merchants and which is likewise perfect with different frameworks yet this new
gadget along with a framework would add certain new highlights and refreshed highlights
which would be advantageous for each of the gatherings included. Certain things must be
considered, for thoroughly considering this Feasibility incorporate labour, for example,
debuggers, analysers, framework investigator and software engineer. Additionally need to
25

view the software and equipment as utilized. Obviously, the analyst needs to look at the
money related variables since it may require a gigantic speculation. Asset limitations is vital
in specialized Feasibility, it is critical on arranging and oversee on normal premise are
individuals, hardware, materials, and the general population include similar to the capital of
working. Obviously, in case the provided assets imperatives are realistic, then the new
framework’s creation work can be increased to achieve the shorter venture length. This will
naturally influence the Feasibility of the timetable. The framework could be learnt, as it
contains no dialect boundary. Because, it is introduced with an uncommon all dialect
interpreter which would make English interpretations to various other languages. The
gadget as well as the new framework would be easy to use and the language can be hardly
difficult, particularly for more established age where essentially they would prefer not to
learn much contrast with the more youthful age [12].
11.2 Economic Feasibility
Monetary Feasibility includes a strategy and furthermore a push to ensure regardless of
whether it is steady and liable to finish. This plausibility essentially assessing the software
activity of the new framework, where it examined the new framework expenses and wages
and in addition advantages of the framework that is proposed. Then, whether it will be
more prominent than its lifetime costs, as such it must be an exact weigh for the expense
versus the advantages previously making any move is examined. For deciding aggregate
expense of the proprietorship, the estimation costs should be improved:
• The administration, Information Technology group and workers.
• Staff for providing the training.
Equipment, for example, required work area, CPU and programming, for example, the
expected application to assemble the new framework asks about the stock control
programming along with the purpose to offer the programming.
The assessed costs to put off the venture are listed below:
• License and expenses
• Costs of Consultation.
• Costs for the service.
• Installation of framework
• To convert the record
26

The investigation which should be viewed are as follows:
• Will the new framework be savvy? Which means will it be justified regardless of the
cost to be spent for the new framework to be actualized?
• Providing a reason for contrasting improvements. Examination between the
aggregate expected expense of each segment against the aggregate expected
advantages, to see whether the advantages exceed the expenses and by how
much.
• Will the framework be promising or conceivable with the given asset limitations,
Resource requirements is an essential assets that IT groups need to design and
oversee on normal premise are machines, materials, individuals and working
capital. Clearly, if these assets are accessible in plenitude then the undertaking
could be quickened to accomplish shorter venture term.
• Other than the significance of costs, monetary Feasibility additionally assesses
substantial and impalpable advantages to the restaurant [13].
11.3 Operational Feasibility
For restaurant’s workers, it is critical to get included and then remove a portion of
making a framework that is new. Would the client utilize such a framework after its ready?
This goes to the servers and furthermore Frank will utilize it. At the end, the framework
would be easy to understand and simple access for them to utilize and won't set aside quite
a while for them to figure out how to utilize it. The workplace of the restaurant will change
to solid and quick administration. The client will get their nourishments on a most punctual
purpose of time subsequent to putting in their requests, this could impact on how the
framework will be gainful for the end client. Again framework is easy to use, and the
framework client will rapidly adjust to change. The framework will contain simple access
and distinctive dialect framework also so unique individuals with various foundation will
comprehend and will rapidly see how the framework functions. Subsequently the
framework really will lessen the remaining burden whenever utilized viably.
27

12 Software Testing and Acceptance Criteria
Here, we are using the acceptance testing. Acceptance Tests are models of
programming application conduct from at least one client purpose of perspectives. The tests
for acceptance are made from the client’s stories. For deciding whether the software
application fulfils the required Acceptance Criteria, it is just a formal test that is used.
Furthermore, it assists clients with deciding on acknowledging the framework or not. The
Acceptance tests are executed by the client for checking whether the client story is
completed along with accuracy and actualization. The application could contain numerous
Acceptance tests to make certain that the usefulness of the programming work. It is an
approach called discovery approach tests. In relation to the Unit tests, the Acceptance tests
are unique, where the Acceptance tests are composed by client and won’t be demonstrated
when the unit tests are being composed by the designers, and until they are displayed.
Therefore, the mentioned details provide the complete specification of the software
application conduct for all the situations that are present for the current programming
circumstance, for discovering its accuracy. Customer Tests and Customer Acceptance Tests
are the other names for Acceptance Tests. The Acceptance tests are top notch prerequisites
relics since they portray the criteria by which the partners will decide if the framework
addresses their issues [14].
Acceptance Criteria are conditions which a software application should fulfil to be
acknowledged by a client or client. It says the characterized norms of a software item should
meet. These are an arrangement of standards which cover the framework conduct and from
which we can make acceptance situations. Acceptance Criteria is an arrangement of
explanations which says the outcome that is pass or come up short for both utilitarian and
non-useful prerequisites of the task at the present stage. These utilitarian and non-useful
necessities are the conditions which can be acceptance. There is no incomplete acceptance
in acceptance criteria, it is either passed or fizzled. In Agile, it characterizes the limits of a
client story and along these lines it is utilized to see whether the client story is finished and
functioning as it ought to be. It is otherwise called test fruition criteria and fit criteria. It
ought to be specified is an extremely basic dialect like a client story which a client can get it.
It ought to have the normal outcome or the result composed obviously with no vagueness.
The acceptance conditions and rejection conditions ought to be obviously specified in the
28

acceptance criteria. The Acceptance Criteria ought to be an abnormal state report and
further provide the points of interest for comprehending the valuable. Acceptance Criteria is
shown below.
Criteria 1. Place Order
The user does the following:
• For the session, selects his dialect inclination.
• Makes choices from the provided menu.
• Makes choices from the provided beverages menu
• Makes choices from the provided combo bargains
• Affirms request
Criteria 2. Make Payment
• The method of payment is entered by the user (Credit card or the Debit card or the
Cash card payment).
• The payment is made using only cash.
• Cash authority gathers cash and then returns the change if needed.
• The payment is made by the user using credit card or the check card.
• The token number is given to the user along with the last bill.
Criteria 3. Update Menu
• The Admin enters the framework with some secret phrase.
• The Admin rolls out the needed improvements.
• Admin spares progressions and then logs out.
• Some of the menu probably don’t need any kind of change.
• Client might fill the invalid password and require to return.
Criteria 4. Monitor Inventory.
• Staff notices an item out of stock
• Updates the menu accordingly.
Criteria 5. Read Order.
• Internal request framework peruses the request
• Communicates the request to the sustenance readiness individual
29

13 Proposed Deployment Strategy
The proposed deployment strategy is automated fast food ordering System on
restaurant. These process are shown below [15].
Goals
The framework contains UI which can be used easily.
 Particular customer of the framework could have issue to peruse the content in
terms of presentation.
 Framework is traversable by instinct.
 Introduction of Menu decisions is done in different catch types, which contain
message and also little pictures representing the decision for better understanding
[16].
The framework underpins multi lingual capacities.
 User is certifiably not a local speaker of the regular talked dialect in the nation.
 System obliges English (all around acknowledged dialect for correspondence) and
other local dialects, which are generally talked in the nation where the framework is
agent.
Framework accepts arrangement from customer based on his or her decision.
 User selects the combo bargain (i.e. mixed principle nourishment, drink along with
side dish).
 User could require to make his very own requests with the selection of dishes.
Figures of the framework represents the last bill for the request which is set.
 System computes last bill’s amount for the increased things based on its unit cost
bested up by the material charges assuming any.
 User is given the alternative to either pay for the request or amend the request [17].
Framework handles the payment for the customer characterized arrange.
 User chooses to pay money and framework requests that customer enter trade out
the space.
 System confirms the money sum and gives discount if any subsequent to deducting
the sum.
 User chooses credit or check card for making payment. Framework illuminates
customer for swiping the card via, card per user.
30

 The framework confirms the card along with measuring the bills’ charges to the card.
On the marking cushion, requests the customer to sign the bill.
 The framework will print out the receipt which contains the points of interest of the
request, token number, charge and the technique of payment with a terminal
message stating, “Thank you. Visit again / Store address”.
 System imparts the request to the kitchen through the inside requesting framework.
Framework offers the decision to change the menu things to the store supervisor.
 Store administrator chooses to include/erase a thing from the menu.
 Store administrator needs to put bubbly offers on a few things on account of which
there is an adjustment in the cost of a portion of the things.
 Store supervisor sees that a few dishes are out of stock. Subsequently he refreshes
the menu so those things are erased briefly erased from the showcase displayed to
the customer [18].
The framework is impervious to dynamic/thorough taking care of.
 Customer should be minor or programmer who should require getting into the
framework for its transformation. It ought to give security to such regions.
 The framework will be utilized by various customers and might encounter some
unpleasant hand from time to time.
Benefits
 At the back counter, it would limit the quantity of representatives.
 Framework will lessen work’s expense.
 Framework will be less plausible for committing error, as it is a machine.
 At the counter, it stays away from the long lines because of the execution speed and
number of ideal screens for suiting the highly extreme throughput.
 Framework would be accessed 24 hours and 365 days, where the machine couldn't
take any debilitated or excursion clear out.
31

References
[1]R. Zahari, "A Case Study in the Design of a Restaurant Management
System", Academia.edu, 2018. [Online]. Available:
http://www.academia.edu/11432665/A_Case_Study_in_the_Design_of_a_Restaurant_
Management_System. [Accessed: 01- Oct- 2018].
[2]"The Software Development Process", Sce2.umkc.edu, 2018. [Online]. Available:
http://sce2.umkc.edu/BIT/burrise/pl/software-process/. [Accessed: 01- Oct- 2018].
[3]V. Mayank and D. Saraf, "Project: Fast Food Automated Ordering System", Isr.umd.edu,
2018. [Online]. Available: https://isr.umd.edu/~austin/ense621.d/projects04.d/project-
food-ordering.html. [Accessed: 01- Oct- 2018].
[4]J. Parker, "Acceptance Criteria for Business Analysts - Enfocus Solutions Inc", Enfocus
Solutions Inc, 2018. [Online]. Available: http://enfocussolutions.com/acceptance-
criteria-for-business-analysts/. [Accessed: 01- Oct- 2018].
[5]"Difference between Acceptance Criteria Vs Acceptance Tests", Software Testing Class,
2018. [Online]. Available: https://www.softwaretestingclass.com/difference-between-
acceptance-criteria-vs-acceptance-tests/. [Accessed: 01- Oct- 2018].
[6]"Feasibility Study On Le Diner Restaurant", UKEssays, 2018. [Online]. Available:
https://www.ukessays.com/essays/computer-science/feasibility-study-on-le-diner-
restaurant-computer-science-essay.php. [Accessed: 01- Oct- 2018].
[7]"UML 2 Use Case Diagrams: An Agile Introduction", Agilemodeling.com, 2018. [Online].
Available: http://www.agilemodeling.com/artifacts/useCaseDiagram.htm. [Accessed:
01- Oct- 2018].
[8]"Software Engineering — Software Process and Software Process Models (Part
2)", Medium, 2018. [Online]. Available:
https://medium.com/omarelgabrys-blog/software-engineering-software-process-and-
software-process-models-part-2-4a9d06213fdc. [Accessed: 01- Oct- 2018].
32

[9]"Introduction to Context Diagrams > Business Analyst Community & Resources | Modern
Analyst", Modernanalyst.com, 2018. [Online]. Available:
https://www.modernanalyst.com/Resources/Articles/tabid/115/ID/1355/Introduction-
to-Context-Diagrams.aspx. [Accessed: 01- Oct- 2018].
[10]"The sequence diagram", Ibm.com, 2018. [Online]. Available:
https://www.ibm.com/developerworks/rational/library/3101.html. [Accessed: 01- Oct-
2018].
[11]"UML 2 Class Diagrams: An Agile Introduction", Agilemodeling.com, 2018. [Online].
Available: http://www.agilemodeling.com/artifacts/classDiagram.htm. [Accessed: 01-
Oct- 2018].
[12]"Software Testing", Users.ece.cmu.edu, 2018. [Online]. Available:
https://users.ece.cmu.edu/~koopman/des_s99/sw_testing/. [Accessed: 01- Oct- 2018].
[13]"Software Process Models - Waterfall Model, V Model, Spiral Model", The-software-
experts.com, 2018. [Online]. Available: http://www.the-software-experts.com/e_dta-
sw-process.php. [Accessed: 01- Oct- 2018].
[14]S. PUROHIT, B. MICZEK, A. THIRKATEH and R. FAIGAO, "SYSTEM REQUIREMENTS
SPECIFICATIONS FOR THE PROJECT INVENTORY CONTROL SYSTEM", Cs.uic.edu, 2018.
[Online]. Available: https://www.cs.uic.edu/~spurohit/documents/Requirements
%20Document.pdf. [Accessed: 01- Oct- 2018].
[15]J. Mishra and A. Mohanty, Software engineering. New Delhi, India: Dorling Kindersley,
2012.
[16]R. Pressman, Software engineering. New York: Mcgraw-Hill, 2016.
[17]E. Tyugu and T. Yamaguchi, Knowledge-Based Software Engineering. Amsterdam: IOS
Press, 2016.
[18]D. Zowghi, Requirements Engineering. Berlin: Springer, 2015.
33

34