As the name suggests, the cake ordering system is an application that will help in maintaining the sales activity in the cake shops. It will be very difficult to manually calculate the daily sales taken place if the calculation is very huge. This application is designed to reduce the manual work involved in calculating the sales activity. The sales activity can be got in just one mouse click through the use of this application. This will be one of the applications that will help the owners of the cake shop to manage their sales activity with great ease. The sales servicing activity will take place in a quicker manner through this application. The cake ordering SRS is an application that will give the SRS of the cake ordering system.

This application is based on the ordering and selling the cake for each customer. Each customer can have a unique id through this application. This will also ensure to allow discounts to the customer who buys the cakes from the particular cake shop. The user interface must be simple and easy to understand even by the common man. The user should enter the date of delivery of the cake to the customer. The flavor of the cake can also be selected through this application. The modules that are included in this application are as follows:
- Login module: The users can login to the application using the username and password.
- Registration module: The admin provides the username and password for the registered users.
- Report module: This module will allow the user in generating the sales reports with great ease.
- Cake module: This module will contain the name of the cake and the rate of the cake that is ordered by the customer.
- Flavor module: This module will allow the user to select the inside or the outside stuffing that is done.
- Order module: Through this module the customers can order the cake by entering the name, address etc.
- Sales module: This module will deal with the total sale of the cake that has taken place in a day, week, month or year.
Software requirements:
- Language: Microsoft Visual Studio 2008
- Database: Microsoft SQL server 2008
FUNCTIONAL REQUIREMENT:
Login Module:
Introduction: Authorized users are allowed to access.
Input: User enters the User type, Username and password.
Process Definition: Checks User type, Username and password is valid or not.
Output: User is directed to next page or shows the message box “Login Failed”.
Registration module:
Introduction: Only Admin can access the page.
Input: Admin has the authority to provide username and password for new users
Process Definition: Checks same username and password exists or not and also checks whether all the fields are entered.
Output: Employee gets the username and password.
Report Module:
Introduction: Only Admin can access the page and check the report.
Input: Username, from date, to date
Process Definition: It retrieve’s all the information stored from different tables.
Output: Requested report is generated.
Cake Module:
Input:cake name, rate
Process Definition:A new type of cake is added which includes the name of the cake and the rate. Also the details can be edited if necessary only by the admin. Along with this any of the details can easily be deleted by him.
Output:A new cake and a rate is added to the system.
Flavour Module:
Input:outside stuffing, inside stuffing, rate
Process Definition:2 types of cake flavour are added namely outside stuffing and inside stuffing and separate rate is added for flavours’. The admin has the authority to modify the details added and he also has the right to delete those details. .
Output:A new cake and a rate is added to the system.
Order module:
Input: Orderno, name, contact, cake name, stuffing’s, quantity
Process Definition:Here the customer orders for cake by providing his name and contact for identification and a unique order number will be generated from the software.
Output: A separate bill is generated for the confirmationpurpose. All the information is being saved in the database.
Sales module:
Input: Order no
Process Definition:On the day of delivery, as soon as the customer produces the bill of order and his unique order number, the user checks in the system whether that order number and order is available or not. If so he will pass the bill of order to the production counter.
Output: As soon as this procedure is done, ticket can be generated. All the information is saved in the database including the ticket no.
Download Project Source code:
₹299Add to cart
🔥1.1 K Views