Recipe Management System Project: Software Engineering

Desklib provides solved assignments and past papers for students.

SOFTWARE ENGINEERING -
ASSIGNMENT -1
Student ID:
Student Name:

Table of Contents
Introduction................................................................................................................................3
Requirements..............................................................................................................................4
Functional Requirements.......................................................................................................4
Non-Functional Requirements...............................................................................................4
Architecture Design...................................................................................................................5
Database Design.........................................................................................................................6
GUI Design................................................................................................................................7
Class Diagram............................................................................................................................8
Test Plan.....................................................................................................................................9
Conclusion................................................................................................................................10
References................................................................................................................................11
1 | P a g e

Introduction
The XYZZY Software company wants to develop the system for managing the recipes. It is
the software designed only for the personal use. It is developed with the help of Java
technology and the platform used for developing the system is NetBeans IDE. The
architecture of the system is completely segregated with the following classes used. For
storing and managing the data or information, the database is also designed on the basis of
requirements.
2 | P a g e

Requirements
Functional Requirements
It is the type of technical requirements which depends on the coding and implementation part
of the system. This system will help food lovers to select the recipes of different food item
according to their categories. This application is based on Java programming language and
GUI of application is designed using the Swing characteristics of Java. All the recipes and
their details are added into the database and the connectivity is done using JDBC drivers
(Khan, et al., 2016).
Most of the functional requirements are:
 Database connection should be done.
 All the recipes should be displayed in a particular category.
 User should be able to add new recipe into the database.
 User should be able to clear the screen which is displayed to him.
Non-Functional Requirements
These requirements are based on the user’s perspective and these are the key points which are
required for the success of the system. Non-functional requirements are based on the
functional requirements of the system.
Most of the non-functional requirements are:
Security: This requirement is the most concerned requirement of a user towards the system
they are using. The system must be secure and consistent for the users of it. User should have
login functionality in the system. The password and other personal details should be secure in
the proposed system.
Usability: The system design and user interface are very simple as the user can easily access
every detail from the system.
3 | P a g e

Architecture Design
This system is designed using MVP architecture. This image is displaying the MVP
architecture of the system. MVP stands of Model View Presenter and the presenter work as a
middle man in the system. All the logic of presentation will be pushed to the Presenter of the
system. This architecture is used to define the variants among the application data, presenter
(controller) and user of the system.
Figure 1: Design Architecture
4 | P a g e

Database Design
For storing and retrieving the data or information regarding the recipes, the database is
designed where the single table will be created named as Recipes and the five records were
inserted in the table (Johnson, 2016).
CREATE TABLE RECIPES
(
ID INT NOT NULL GENERATED ALWAYS AS IDENTITY,
RECIPENAME VARCHAR (60) NOT NULL,
CATEGORY VARCHAR (10) NOT NULL,
MAININGREDIENT VARCHAR (10) NOT NULL,
PREPARATIONTIME INT NOT NULL,
COOKINGTIME INT NOT NULL
);
INSERT INTO RECIPES (RECIPENAME, CATEGORY, MAININGREDIENT,
PREPARATIONTIME, COOKINGTIME)
VALUES
('steak tartare','meat','steak',10,0),
('roast chicken','meat','chicken',15,60),
('fish and chips','fish','fish',5,10),
('grilled steak and salad','meat','steak',15,5),
('baked beans on toast','vegetarian','beans',0,5);
5 | P a g e

GUI Design
Figure 2: GUI Design
In the above figure, it shows the GUI design of the software that is been developed by the
organization. The system is designed for managing the recipes. It shows the input screen and
the output screen. It is designed in the NetBeans platform with the help of Java Application.
For giving the user input, text fields are provided. There are many components used in the
GUI design of the software. The components are Label, Text Fields, Buttons, and Text Area.
The text area is works as an output screen where the user input will be displayed (Jackson,
2017).
6 | P a g e

Class Diagram
This class diagram is designed on the basis of the classes used in the Java application. All the
classes have their own attributes and methods. All the classes are connected with each other
so the functionality can be done properly. The class diagram is used to define the classes
from the database used in the application (Sulaiman, et al., 2019).
Figure 3: Class Diagram
7 | P a g e

Test Plan
S. No. Test Case Expected Outcome Actual Outcome Result
1. All categories in
the output
screen.
After clicking on the
category option, it will
display all categories
present in the system.
The list of available
categories will be
displayed in the
output screen.
Pass
2. All categories
and preparation
time.
After clicking on the
“Category and
Preparation time”
button, it will display
the category with
preparation time.
The list of
Categories and
Preparation time
will be displayed in
the output screen.
Pass
3. All categories
and Combined
time.
After clicking on the
“Category and
Combined time” button,
it will display the
category with combined
time.
The list of
Categories and
Combined time will
be displayed in the
output screen.
Pass
4. Add button
functionality
After clicking on the
add button, the entered
detailed will be shown.
The details entered
will be displayed in
the output screen.
Pass
5. Clear button
functionality
After clicking on the
clear button, the data
entered will be cleared.
The empty text
boxes will be
displayed.
Pass
6. Exit button
functionality
The system will be
closed after clicking on
the exit button.
The system will be
closed after clicking
on the exit button.
Pass
8 | P a g e

Conclusion
In this report, it is concluded with the whole description of the designed system for managing
the recipes. It is designed in the NetBeans platform of IDE with the help of Java technology.
For a proper explanation of the system, the functional and the non-functional requirements
are described. In this report, the complete architecture, database design, class diagram, GUI
Design, and the test cases are also explained on behalf of the system requirements.
9 | P a g e

References
Khan, F., Jan, S.R., Tahir, M., Khan, S. and Ullah, F., 2016. Survey: dealing non-functional
requirements at architecture level. VFAST Transactions on Software Engineering, 9(2), pp.7-
13.
Johnson, R.A., 2016. Java Database Connectivity Using Java DB (Apache Derby): A
Tutorial. International Journal of Information, Business and Management, 8(3), p.295.
Jackson, W., 2017. Setting Up Your Java 9 IDE: An Introduction to NetBeans 9. In Pro Java
9 Games Development (pp. 135-150). Apress, Berkeley, CA.
Sulaiman, N., Ahmad, S.S.S. and Ahmad, S., 2019. Logical Approach: Consistency Rules
between Activity Diagram and Class Diagram. International Journal on Advanced Science,
Engineering and Information Technology, 9(2), pp.552-559.
10 | P a g e