$ $ > 4 3 Topic Tniroduetion LL] | Introduction to System 112) | Scope of System 13 Proposed System System Analysis 2.1 Requirement Analysis 2.27” Fact Finding Techniques 2.3 Feasibility Study 4 Hardware and Software Requirements System Design 3.1) ER Diagram 3.2 Context Level Di Data Flow Diagram 3.4 Data Dictionary Form Design Report Advantages and Limitations Future Enhancement Conclusion Bibliography" s 3 $ awiaih h 7 ee eh be 1. Introduction 1.1 Introduction to System The “Pizza Shop Management System” has been developed to This override the problems prevailing in the practicing manual system: xd to eliminate and in some cases reduce the hardships software is suppor faced by this existing system .Moreover this system is design for the particular need of the company to carry out operations in a smooth and effective manner Pizzas are one among the favorite and most popular food items that lot. There are many pizza corners in and the modern day people love around the city. The pizza delivery/ordering system is an application that As the allows a person to online the pizzas through the online mode. intemet users are increasing day by day, the pizzerias are including a the online mode. Ithelps in the savior service in ordering the pizzas throug of time, The application is reduced as much as possible to avoid errors while hile entering invalid It also provides error messag entering the data is needed for the user to use this system data. No formal knowled; by this all it proves itis user-friendly. Pizza Shop Management System, as rast Thus. described above, can lead to error free, secure, reliable and management system It can assist the user to concentrate on their other activities rather to concentrate on the record keeping. Thus, it will help organization in better utilization of resources. Scope of System The application is reduced as much as possible to avoid errors while age while entering invalid 1.2 entering the data. It also provides error me data. No formal knowledge is needed for the user to use this system. Thus, by this all it proves it is user-friendly. Online Pizza Delivery System, as described above, can lead to error free, secure, reliable and fast management system.stem or small, has challenges to order, pizza, order 1.3 nization, whether big janaging the information of online status, payments and coupons. Every pizza ordering system has different pizza needs, therefore we design exclusive employee management system nts. This is design to assist re adapted to your managerial requireme and will help you ensure that your organization is equipped with the right level of information and details for your future2. System Analysis A complete understanding of the requirement is essential for the suc software development efforts. The analysis task is a process of discovery, initially established refinement, modelling and specification. The software scop by the system engineer and refine during software project planning, is refining in detail. Model of required data, information and control flow, and operational behavior are created 2.1 Requirement Analysi Requirement analysis enables the system engineer to specify te software's interface software function and performance, indi with other system elements, and establish constraints that software must meet. Requirement analysis allows the software engineer to refine the software allocation and build model of data, functional, behavioral domains that will be treated by software. Requirement ner with models that can be nd procedural design e developer and the analysis provides the software desi translated into data, architectural, interface, Finally the requirements specification provides t customer with the means to access quality once software is build. ided as follows: Requirement analysis may be (1)The first is the Problem recognition (user requirements) such as the followings: ‘© What type of input/output user want? What type of report user want to generate? What type of interface user want? This type of many questions arise at requirement phase (2)Problem Evaluation and Synthesis is the second area of efforts for analysts (3) The next area of effort is Modelling .Da of specific questions that area relevant to any data processing application for a Modelling answers a se a set of specific questions that are relevant to any data processing application. For example: What are the primary data objects to be proc: each data object? What attributes describe the object? What r the relations among the objects and the processes that transform them? sed? What is the composition of (4) The next is area of effort is the Specificationay (5) The next is area of effort is the Review. Q System analysis is therefore, the process of gathering and interpreting facts, nN diagnosing problem and using the information to recommended improvement in E~ TF _system, System analysis is conducted with the following objects in mind LO ely 5 J ee! ey a oe! ~~! . s a a, ame Dt ! J 2 fo ] : e ae 2.2 Fact Findin; Identify the organization need. Evaluate the system concept for feasibility Perform economic and technical analysis Alllocate function to hardware, software, people, database and other system element, Establish cost and schedule con: System analysis refers to the process of examining a situation with the intent of improving it through better procedures and methods. The main objective of the system is to provide comprehensive, online. reliable and fast information service to all the receipt activities in the int nization. The other objectives includes: - User friendliness and ease of work. Generation of reports. Flexibility to incorporate various levels of security measures System design is the process of planning a new system to either repla system, But before the planning is done, the old Jerstood and the requirement must be complement the existing system must be thoroughly u determined. ‘echniques * Definition of Fact-finding Techniques Fact finding is process of collection of data and information based on techniques which contain sampling of existing documents, research, observation, questionnaires, interviews, prototyping and joint requirements planning, System analyst uses suitable fact-finding techniques to develop and implement the current existing system, Collecting required facts are very important to apply tools in System Development Life Cycle because tools cannot be used efficiently and effectively without proper extracting from facts. Fact-finding techniques are used in the early stage of System Development Life Cycle including system analysis phase, design and post implementation review. Facts included in any information 8system can be tested based on three steps: data- facts used to create useful information, process- functions to perform the objectives and interface- designs to interact with users. > Fact-finding techniques There are seven common fact-finding techniques + Sampling of existing documentation, forms and databases * Research and Site visit + Observation of the work environment + Questionnaires ® Interviews Prototyping + Joint requirements planning ° Sampling of existing documentation, forms and databases The best way to analyze the existing system is to collect facts from existing documentation rather than from human sources. There are various kinds of documents to collect facts from existing documents. These include: e-mails, customer complaints, suggestion box notes and reports that document the problem area problem performance reviews System analyst uses sampling techniques in order to organize the above documentation. Sampling technique is the process of combing a representative sample of documents, form and records Research and Site visits Research and site visits, second technique, is the process of examining the problems which had previously solved by other sources that can be either human or documents. To solve the requirements of problem, the analyst visits to other organization that had previously experienced for similar problems. In addition, the analyst can also find the information from database, reference books, case studies and Internet. + Observation of the work environment ‘Another fact finding technique is observation. In this technique, system analyst participates in the organization, studies the flow of documents, applies theexisting system, and interacts with the users. Observation can be a useful technique when the system analyst have user point of view. Sampling technique called work sampling is useful for observation, By using this technique, system analyst can know how employees spend their days. Questionnaires Questionnaires are also one of useful fact-finding technique to collect information from large number of users. Users fill up the questions which are given by the system analyst and then give the answers back to the system analyst. Questionnaires can save time because system analyst does not need to interview each of users and if the time of interview is short, questionnaires are more useful > Interviews Interview is the most commonly used technique to collect information from the face-to face interviews. The purpose of interview is to find, verify, clarify facts, motivate end users involved, identify requirements and gather ideas and opinions. + Prototyping ‘Another fact-finding technique is known as prototyping which collects the requirement facts of the system. Prototyping is sampling a small working model and it is more related to pre-design of the information system + Joint requirements planning. TRP is the structured group work meeting to identify, analyze problems and define the requirements of system. 2.3 Feasibility Study Feasibility test basically focuses on answer to, how well our project does satisfy the three dimensions: 1, Operational Feasibility 2. Technical Feasibility 3, Economic Feasibility 2.3.1 Operational Feasibility ‘This projects fulfilled a need required by the business. And itis created forthe user to easily access and understand the system.Tid ial a lof dk 4 Ah ee 2.3.2 Technical Feasibility The project needs knowledge of windows platform. As we have enough resources of development with powerful text editor, so we are capable to satisfy the technological need of the project completely as well as do not need additional software or hardware to develop application 2.3.3 Economic Feasibility This project does not need any special hardware or licensed software. Moreover the organization already has enough infrastructure to support this application well so there is no need for any extra finance So application is also economic feasible. 2.4. Hardware and Software Requirements 2.4.1 Hardware Requirements | Processo: 300MHz Intel Pentium III or equivalent or new RAM ‘(| 128 MB > a HardDisk «(| 20GB aa ‘Monitor | VGA/SVGA ikepboaralis 0 0s)|102Keysy Mouse 2 buttons/ 3 buttons 2.4.2 Software Requirements Operating System Windows 2000/XP Front End Visual Basic, Net Back End 4 ‘MS-Access 2013 aVISUAL BASIC.NET: VB.NET has complete support for object-oriented concepts. Everything in VB.NET is an object, including all of the primitive types and user-defined types, events and even assemblies. All objects inherit from the base class object. Visual Basic .NET provides the easiest, most productive language and tool for rapidly building Windows and Web application. Visual Basic.NET comes with enhanced visual designers, increased application performance and a powerful Integrated Development Environment (IDE). It also supports creation of applications for wireless, Internet-enabled hand-held devices, MICROSOFT OFFICE ACCESS 2013: Microsoft Office Access previously known as Microsoft Access is a relational database management system from Microsoft that combines the relational Microsoft Database with a graphical user interface and software-development tools. It is a member of the Microsoft Office suite applications, included in the professional and higher editions or separately.} 5 id. T7797 % rrT bee ebe ddd db ddddddhhdddddddd PPFPPRPPPPRREPROR PTE? Cr Breck 3. System Design 3.1 E-R Diagram E-R Diagram for Pizza Shop Management SystemPE ww ahh of of bd th hh ld dd 3.2 Context Level Diagram Context Level Diagram for Pizza Shop Management System 3.3 Fe rneae Delivery |, _Dytivery Person | Information Data Flow Diagram Data Flow Diagram for Pizza Shop Manag. conan ne Ss Onlceoo eee 6 Adee ee = Abd Sa Oa nn wo bh 1. Admin. Sr.No | Column Name 1 "| Username Password 2. Employee Sr.No | Column Name 1 Taare 2 ‘emp_name_ emp_sal 3. Pizza [Sr.No | Column Name 3.4 Data Dictionary Type Short Text Short Text Data Type Number Shor T t Shor Text Data Type Constraint | Primary Key Not Null Constraint Primary fot Null Not Null Constraint Password Description | Unique Admin 1D | | Description Employee Name Employee Salary Description I | pizza id Number Primary Key | Unique Pizza ID ppeeitraa Tong Text | Not Null. | Pizza Name 3. [pizza price NotNull_ | Pizza Price 1 > 7 sa 4, Beverages cs {Sr.No | Column Name Data Type | Constraint Description 1 drink id Number | Primary Key | Unique Drink ID I drink_name [Short Text |NotNull | Drink Name 3 Price [Number [Neen | Denk PricerhhA*AhbEN HA Hd BHAA E SE 2 b bb » wm 4 bh n\n 2, Data Type | Ovder_no [Number Order date ine [DateTime] | Cust ph_no ‘Number TNo_of items Number Order details ToogiTeR [Total ant. Coleaated Constraint | Description Primary Key Unique Order Number NotNull [Time & Date of Order Not Null Name of Cus mer Not Null Customer Ph. No NotNull [Number of tems ordered | Not Null Name ofpiza | | Not Null Amount to be paid |“TT rT??? —_— —_ eb hh th th th | 4. Form Design 1. Welcome Page Form 2. Login Form3. Admin Login Form 4. Employee Login Form ata A EBSA AS PF EF BHM NII AaOrder Receipt PIZZA DELIGHT | (l 5. Report6. Advantages and Limitations 6.1 Advantages 62 Li It overcomes all the problems of existing system. Pizza can be ordered in more convenient way. Payment can be easily done using various online mode or cash It makes system very effective for ordering a pizza. Admin can view sales report which can be helpful for decision making, Easy add/update/delete process of pizza Sear hing process is an easy task. tations ‘© System may provide inaccurate results if data not entered correctly. ‘© The existing system is manual system, Needs to be converted into automated system. Less Security. Not in reach of distant users. Risk of mismanagement of data. Fewer Users-Friendly.7. Future Enhancement > Nothing is perfect. Likewise, our current system provides all the basic functionalities along with existing features. However some enhanements areas follows: 5 Payment Options: Add different payment options such as PayPal, Gift Cards, Cash, ete. Allow to save payment details for future use. 5 Order Status: Show only Active orders to Restaurant Employees Order Tracking: Let customer track his/her current order 6 Order Ready notification: Send an Order Ready notification to the customer. + Delivery Options: Add delivery option. © In future it can be extend for network computers by adding ADO database connectivity to the visual basic.8. Conclusion ‘This project work is highly important for me, as this project has given me a great experience. My aim of developing this project is to have an understanding about the “PIZZA SHOP MANAGEMENT SYSTEM” and Visual Basic NET and to get well acquainted with the efforts and hard work that is required for developing a project. The output of this project is the forms, reports and views which have being developed for the end user which will provide all the relevant details. This project is very flexible and it can be modified if the need arises. We hope that the user will find this project work quite pleasing in its functionality. We are sure that the users of this project will like our effort.9. Bibliography » Website Reference © www.google.com ‘© www.scribd.com w.tutorialspoint.com o ww © www freeprojectz.com © www projectworlds.in ‘© www stackoverflow.com © wwwslideshare.net © www projectabstra Book Reference A complete guide to Visual Basic NET Advance Visual Basic.NET MS Access programming with VB NET Mastering in VB NET VB NET Programming (Black Book) Developing Desktop Application Using VB NET NET Programming ~ Meenakshi Thalor