Riaz Ahmed Id to the Department of Software Engineering, Daffodil International University has been accepted as satisfactory in partial fulfillment of the requirements for the degree of Bachelor of Science in Software Engineering and approval of its style and content. It hereby declares that this project has been carried out by us under the supervision of MR. It also declares that neither this project nor any part thereof has been submitted elsewhere for the award of any degree.
I am exceptionally obliged to Daffodil International University for their guidance and constant supervision by Md. Shariful Islam and furthermore for providing the necessary information regarding the venture and furthermore for their assistance in completing the task. I would like to express my gratitude to my parents, my batchmate and member of DIU for their kind cooperation and comfort that helped me in completing this task.
Project Overview
Project Purpose
Background
Benefits & Beneficiaries
Restaurant management system approaches vary depending on the type of business, but all restaurants have one thing in common: they exist to make money. Restaurant management software helps managers increase revenue, reduce costs and provide a superior customer experience. Increased efficiency and reduced mismanagement are two benefits of using the right restaurant management software.
Goals
Stakeholders
Project Schedule
Gantt chart
Release Plan/Milestone
SOFTWARE REQUIREMENT SPECIFICATION
- Functional Requirements
- Data Requirements
- Performance Requirements
- Speed and Latency Requirements
- Precision or Accuracy Requirements
- Capacity Requirements
- Dependability Requirements
- Reliability Requirements
- Availability Requirements
- Robustness or Fault-Tolerance Requirements
- Safety-Critical Requirements
- Maintainability and Supportability Requirements
- Maintenance Requirements
- Supportability Requirements
- Adaptability Requirements
- Scalability or Extensibility Requirements
- Security Requirements
- Access Requirements
- Integrity Requirements
- Privacy Requirements
- Usability and Human-Interaction Requirements
- Ease of Use Requirements
- Personalization and Internationalization Requirements
- Understandability and Politeness Requirements
- Accessibility Requirements
- User Documentation Requirements
- Training Requirements
- Look and Feel Requirements
- Appearance Requirements
- Style Requirements
- Operational and Environmental Requirements
- Expected Physical Environment
- Requirements for Interfacing with Adjacent Systems
- Projectization Requirements
- Release Requirements
- Legal Requirements
- Compliance Requirements
- Standards Requirements
Reliability is an important non-functional requirement for most software products, so the Software Requirements Specification (SRS) must include a reliability requirement, and most do. it fails every time until the cause of the failure is fixed. This project idea is unique, but the number of food availability will increase according to the increase in the number of users. This project currently has the smallest user tolerance as it is now on localhost so it can manage datasets based on computing requirements and configuration.
At least one backup server with the same configuration as in the main server is also recommended for fault tolerance and better performance. The appearance of the environment system for your information center must ensure that each system will function faithfully, while, at intervals, the difference from its operating specifications remains. We ensure the privacy and security of the database that will be stored in the restaurant management database.
The structure of your e-commerce system, including the software itself, the externally visible features of the user interface and the relationships between them. Also, examine what is in your site's code that needs to be changed to support the markets. Once the necessary information is gathered, it is documented in a URD, which is intended to specify what the software must do and becomes part of the contractual agreement.
A customer cannot claim features that are not in the URD, while the developer cannot claim that the product is ready if it does not conform to an item of the URD. The explicit nature of the URD allows clients to show it to multiple stakeholders to make sure all necessary features are described. The look and feel requirements describe the intended spirit, mood or style of the product's appearance.
These requirements specify the intent of the appearance and are not a detailed design of an interface. At a minimum, you should test your site in the latest versions of Internet Explorer (currently versions 8 and 9), as well as Firefox and Safari. It is a one-stop place to see all the visual styles of the website, such as headings, links, buttons, color palettes and any visual language used on the website.
We start with a discussion of the need for and the methods used to set requirements based on the concept of user-centered design. These methods are grouped under design because their most significant contribution is made in the design phase; however, it is important to note that they are also used to define the context of use and to evaluate design results as part of system operation.
SYSTEM ANALYSIS
- Use Case Diagram
- Use Case Description (for each use case)
- Activity Diagram (for each use case)
- System Sequence Diagram (for each use case)
Related use case: System login, see profile Stakeholders: System management Prerequisites: User logged in. The customer enters the keyword for a product and clicks the search button on the personal home page. The customer selects the desired products and clicks on the add to cart button on the web page.
The system displays the products in the customer's order table on the website. If the customer does not log into the system, he cannot check the product. If the customer does not provide information about the payment method, he cannot check the product.
If the customer does not provide information about the delivery location, he cannot check the product. Related use case: system login, system view. Stakeholders: System Management. Prerequisites: User is logged in.
System Design Specification
- Class Responsibilities Collaboration (CRC) Cards
- Sequence Diagram (for each use case)
- Class Diagram
- Entity-Relationship Diagram
- Development Tools & Technology
- User Interface Technology
- Implementation Tools & Platforms
JavaScript is one of the most popular programming languages in the developer community. As a beginner in the developer world, you would often come across that even the brief you received for your project mentions the simplicity of its user interface that it should feature. What users see and experience must be a flawless and smooth execution.
Some of the most popular and successful companies like Netflix, Facebook, and Instagram operate on the principle of prioritizing their UI above all else. Take any one of them, and you will find that the platform is powerful yet simple with a brilliant user interface. However, it is not denied that the ever-increasing demand of the customers and the market, in general, requires a constant need to perform high quality functionality and usability.
As this responsibility piles up on the developer, many developers find themselves in a quandary and confused about which framework to choose among so many. Laravel tries to alleviate development problems by facilitating common tasks used in most web projects, such as authentication, routing, sessions, and caching. Laravel aims to make the development process pleasant for the developer without sacrificing the functionality of the application.
To make a beautiful website we need different front styles, super font is a font database where we all collect fonts and connect them in our project work. Get vector icons and social logos to your site with Font Awesome, the most popular icon set and toolkit on the web. Font Awesome has a 20% market share among websites that use third-party scripts on their platform, placing it second only to Google Fonts.
We used MySQL Community Server 5.5 for the database as taught in our university. Apache HTTP server to connect to the database, otherwise no performance can be performed from the admin to the user interface. In the design phase, the user admin login form is designed to login and access the database connection.
SYSTEM TESTING
- Testing Features
- Features to be tested
- Features not to be tested
- Testing Strategies
- Test Approach
- Pass/Fail Criteria
- Suspension and Resumption
- Testing Schedule
- Traceability Matrix
- Testing Environment (hardware/software requirements)
- Test Cases
It is important to understand that if a bug is discovered at the point after which testing continues, it turns out to be useless, then the use of testing resources will be wasted. The reason for stopping the test activities must be determined and an acceptable level of defects must be defined that allows the testing process to overcome these defects. A test plan is a detailed document that describes the test strategy, objectives, schedule, estimation, deliverables, and resources required to perform testing for a software product.
Test plan helps us determine the effort required to validate the quality of the application under test. The test plan serves us as a blueprint for carrying out software testing activities as a defined process, which is meticulously monitored and controlled by the test manager. The main agenda of any tester should be to understand the customer's requirements and ensure that the final product is free from defects.
To achieve this goal, every QA must thoroughly understand the requirement and create positive and negative test cases. This would mean that the software requirements provided by the client need to be further broken down into different scenarios and further tested. An easy way is to trace the requirement with relevant test scenarios and test cases.
The traceability matrix is usually a worksheet that contains the requirements with all possible scenarios and test cases and their current status, so this would help the testing team to understand the level of testing activities performed for the specific product. Food added to cart .. 1.user can use a payment method to check out food.
USER MANUAL
User Manual (type A user)
User Manual (type B user)
User Manual (type C user)
PROJECT SUMMARY
- GitHub Link
- Critical Evolution
- Limitations
- Obstacles & Achievements
- Future Scope
There was a critical situation for the development of this project. The most important thing was the database connection and then the responsiveness of all the pages and finally the checkout process. This project is internet based, you will not be able to access it if your internet connection goes down. With software-based restaurant management system, there are recurring costs. Most restaurants can calculate their return on investment in terms of cost savings, which is mostly due to increased staff productivity and resource consumption.
Revenue growth can also be quantified based on the restaurant's management system, which is generally the result of greater guest satisfaction and, in certain situations, faster table turn times – and in some situations, the ability to reach and serve large numbers of people.
