Software Engineering

This document provides study material on software engineering, including software requirement specification, use case diagram, use case description, class diagram, and user interface. It covers topics such as purpose, scope, constraints, assumptions, functional and non-functional requirements, stakeholders, project management, quality, risk, cost, and bibliography.

Running head: SOFTWARE ENGINEERING
Software Engineering
Name of Student-
Name of University-
Author’s Note-

1SOFTWARE ENGINEERING
1. Software Requirement Specification
1. Introduction
1.1 Purpose
The purpose of this project is to develop a mobile based application system that would
help the users to find out restaurants in the local area they stay in. The application that is being
proposed in this requirement specification is a mobile application that would help the users to
book table in the restaurants available, to select their preferred dish before vising the restaurant
to avoid the waiting time and the users can even manage to pay for the process online so that
they do not have to pay at the restaurant.
1.2 Scope
The scope of the project is develop a mobile based application system that would be
secured and safe to store the data of the customers and the restaurants in the database. This
project will detail the design of the application system that would help the users to search all the
nearby restaurant and the service that are offered by the restaurants.
1.3 Definitions
SRS: The SRS is known as detailed description that is to be provided in developing the
application software. The SRS will include the function requirement of the system along with the
non-functional requirement with the system (Lewis, 2017). The SRS includes agreement
between the developers and the contractors who are included in the system development.
2. Constraints
The constraints that are considered for this project are:

2SOFTWARE ENGINEERING
1. The project should be completed within scheduled time and budget that is fixed as the
project schedule by the project manager.
2. The project will only include the resources who are specified in the project schedule.
3. The project should also support all the functional and non-functional requirements that
are assumed for the project.
3. Assumptions
1. The application system should be robust and is expected to be secured from any type
of data breach.
2. The project is assumed to be completed using the agile approach of project
management.
3. It is assumed that the users in the testing phase will provide valid response to the
application system.
4. The system will be efficient for the users as it would find all the restaurants in the areas
of search.
4. Requirements
4.1 Functional Requirements
The mobile application functional requirements are:
1. The system will be able to take the details of the customer at the time of login in the
system.
2. The system will also take the input of the restaurants from the owners stating the
details of the restaurants.

3SOFTWARE ENGINEERING
3. The system will provide the administrator an interface so that they can verify the
restaurants and can approve the information uploaded by the restaurant owners.
4. The system can also take the access of the live location of customer so that it can show
the restaurants in that location.
4.2 Non-Functional Requirements
The mobile application non-functional requirements are:
1. The system will be robust and will support all the users.
2. The system will be available all the 24 hours until when the restaurants will be
serviceable.
3. The system will be secured and safe to keep the customer and the restaurant in the
system.
4. The system will also have a good interface so that the users and admin can access the
system efficiently.
5. Stakeholders
The stakeholders who are associated with the project are project sponsors, project
manager, the business advisors, supervisors, team lead, suppliers, testing manager, testers, the
users, developers, programmers, quality manager, system administrators, and communicators.
6. Project Management
6.1 Time
The total time that is scheduled for the developing the Dinning Closely mobile
application is 50 days. The project will be developed with project management approach and the

4SOFTWARE ENGINEERING
particular approach that will be used to develop this application system will be agile
methodology. This methodology is mainly used for developing this project because it includes
higher customer satisfaction while developing the project. There are six phases in the developing
process of the application and 50 days are divided into different phases of the project life cycle.
6.2 Deliverables and Milestones
The project deliverables that states the project completion is shown below in the diagram.

5SOFTWARE ENGINEERING
Figure 1: Gantt chart for development
(Source: Created by Author)

6SOFTWARE ENGINEERING
The project milestones that are included in the project are given below in the table.
Task Name Duration Start Finish
Developing the project charter 4 days Fri 9/08/19 Wed 14/08/19
Developing the WBS 1 day Fri 16/08/19 Fri 16/08/19
Security analysis 1 day Fri 13/09/19 Fri 13/09/19
Documenting the testing 2 days Mon 30/09/19 Tue 1/10/19
Managing Changes 1 day Thu 10/10/19 Thu 10/10/19
Project Signoff 0 days Fri 11/10/19 Fri 11/10/19
6.3 Quality
The quality of the project should be checked with the quality manager associated with the
project. The project quality manager will be able to test the quality of the application by the
testers and update the system accordingly.
6.4 Risk
The risks that are included in developing the mobile application are:
1. For developing the mobile application software, the time and the schedule cannot
remain the same. The schedule and the budget might change with the development process.

7SOFTWARE ENGINEERING
2. The requirement of the user might also change in the testing phase that is done by the
users. The users might add some features in the application so enhance the features of the
application.
3. There might be risks that the stakeholders or the key personnel in the project might
leave the project in middle. This will result in delaying in the project schedule.
6.5 Cost
The total cost of completing the project within schedules time and with the schedule
resources allocated is $73,040. The initial budget provided to the project management to
complete the project will be the estimated budget. If the project gets complete within the
specified budget, the project will be considered to be as the ideal project.
7. Bibliography
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Becker, C., Betz, S., Chitchyan, R., Duboc, L., Easterbrook, S. M., Penzenstadler, B., ... &
Venters, C. C. (2015). Requirements: The key to sustainability. IEEE Software, 33(1),
56-65.
Brhel, M., Meth, H., Maedche, A., & Werder, K. (2015). Exploring principles of user-centered
agile software development: A literature review. Information and software
technology, 61, 163-181.
de Vasconcelos, J. B., Kimble, C., Carreteiro, P., & Rocha, Á. (2017). The application of
knowledge management to software evolution. International Journal of Information
Management, 37(1), 1499-1506.

8SOFTWARE ENGINEERING
Grønbæk, K., Grudin, J., Bødker, S., & Bannon, L. (2017). Achieving cooperative system
design: shifting from a product to a process focus. In Participatory Design (pp. 79-97).
CRC Press.
Laplante, P. A. (2017). Requirements engineering for software and systems. Auerbach
Publications.
Lewis, W. E. (2017). Software testing and continuous quality improvement. Auerbach
publications.
Shah, U. S., & Jinwala, D. C. (2015). Resolving ambiguities in natural language software
requirements: a comprehensive survey. ACM SIGSOFT Software Engineering
Notes, 40(5), 1-7.
Wang, C., Pastore, F., Goknil, A., Briand, L., & Iqbal, Z. (2015, July). Automatic generation of
system test cases from use case specifications. In Proceedings of the 2015 International
Symposium on Software Testing and Analysis (pp. 385-396). ACM.

9SOFTWARE ENGINEERING
2. Use Case Diagram
Figure 2: Use Case Diagram
(Source: Created by Author)

10SOFTWARE ENGINEERING
3. Use Case Description
3.1 Use Case
Name
Search Restaurants
Scenario The search restaurant use case provides the customer the access to search
for restaurants they like to in the local area they are presently in. The
search is done by the customers based on different constraints. The price
of the dishes, the type of restaurant cuisine they are in search for, and the
type of dish they want to have. This search restaurant extents three use
cases, price, type of restaurants and type of dish.
Pre-Conditions 1. The customer should login in the system of Dinning Closely mobile
app so that they can search for the restaurants as per their wish.
2. The customer should have their GPS system on to track the restaurants
in that area.
Post-Conditions 1. After the search of restaurant being completed, the customer needs to
book a table or order food before they reach the restaurants.
2. The customers can also make the payment of the order before they
reach the restaurant.
3. If customer order food before reach the place, they need to specify the
time they would visit the restaurant.
3.2 Use Case
Name
Oder Food
Scenario The customer can order their food online before reaching the restaurant to

11SOFTWARE ENGINEERING
avoid the waiting time in the restaurant. They can order the food they like
to have but they need to set the arrival time in the restaurant so that the
staffs in the restaurant knows about the arrival time of the customer and
make arrangement accordingly.
Pre-Conditions 1. The customer needs to select a particular restaurant in that locality so
that they can order the food beforehand.
2. The customer also has the check the availability in the restaurant at the
time they would visit the restaurant.
Post-Conditions 1. The customer after ordering the food can make the payment instantly to
avoid payment at the time of visiting.
3.3 Use Case
Name
Add details of Restaurants
Scenario The restaurant owner needs to add the details of the restaurants including
the address details of the restaurants, the type of restaurant it is, their
opening hours, the restaurant type, the prices of the dishes they offer and
all such details. They also need to point their restaurant on the map.
Pre-Conditions 1. The restaurant owner needs to login in the system so that they can input
the details of the restaurant in the system.
Post-Conditions 1. The administrator needs to update the information in the system so that
they customers can view them accordingly.
3.4 Use Case Manage User Information

12SOFTWARE ENGINEERING
Name
Scenario The administrator needs to manage the information of all other users in
the system. The admin needs to update the database of the system so that
the other users get the updated data on the system.
Pre-Conditions 1. The customer and the restaurant has to change the data so that the
admin can update the data in the database of the system.
Post-Conditions 1. After the data being updated in the system, the customer can view the
updated data and the restaurant can view their own updated data.

13SOFTWARE ENGINEERING
4. Class Diagram
Figure 3: Class Diagram
(Source: Created by Author)
5. User Interface

14SOFTWARE ENGINEERING
Figure 4: Customer Login Page
(Source: Created by Author using Balsamic)

15SOFTWARE ENGINEERING
Figure 5: Admin login page
(Source: Created by Author using Balsamic)

16SOFTWARE ENGINEERING
Figure 6: Customer search page
(Source: Created by Author using Balsamic)

17SOFTWARE ENGINEERING
Figure 7: Admin add dish page
(Source: Created by Author using Balsamic)