Waiters and Wheels Essay Example

Waiters and Wheels Essay Example Waiters and Wheels Essay Waiters and Wheels Essay BANGALORE MANAGEMENT ACADEMY .Assignment On WAITER ON WHEELS Submitted by: Ivneet Singh(081301221 ) Table of Contents Sr. No| Topic| Pg. No| 1. | Abstract | 3| 2. | Introduction| 4| 3. | Analysis of current system| 4| 4. | Solutions for problems| 5| 5. | Feasibility study| 5| 6. | Feasibility report| 6| 7. | Operational feasibility PIECES Framework| 7| 8. | Schedule Feasibility | 8| 9. | Economic Feasibility| 9| 10. | Stages of SSADM| 10| 11. | Detail business specification| 11| 12. | Flowchart| 12| 13. | Context Level Diagram| 13| 14. | Data Flow Diagram| 14| 15. ER-Diagram| 16| 16. | Physical Design | 17| 17. | Individual reports| 24| Abstract The main objective of the project is to identify the different framework of activities associated with methodologies and describe how the techniques are used together to develop a system. The project includes the standard methodology to develop the system and documenting of project as well. The methodology selected by our team is SSADM which stands for structured system analysis and design. The selected methodology has been clearly justified and compared to other related methodology. All the mandatory requirement and specification for creating the system design are explained briefly. Physical and logical designs are mapped accurately having clear and detailed documentation of designing phase. To complete this project in effective way . had contributed their best so that all criteria can be covered efficiently. Anyone can understand easily as there is a good command on language through the whole documentation of project. Introduction They were two students Sue Tom Bickford studying in college who also worked as part time job in a restaurant and always dreamt to open their own restaurant. Their initial investment was always out of reach so they noticed many restaurants that offer home delivery service . They got an idea of opening their own restaurant without high investment . This idea came to their mind after meeting many people who wanted home delivery service with their complete food selection. By this, they opened a restaurant â€Å"Waiter on Wheels† in 1997. This restaurant provides food delivery to the customers by gathering the meals form different restaurants and providing under one roof. Customers liked this service very much and their business waiter on wheels was increasing day by day. As there was increase in the number of customers and their orders they started facing some problems to run their business effectively. Analysis of current system Now we are going to analyze the current system of waiter on wheels. Customer calls waiter on wheels to place the order, waiter on wheels will then inform to related restaurants and to driver to take the delivery form the restaurant and place it to the desired customer address. The driver picks the order form restaurants and delivers to the customer and comes back to waiter on wheels. Problems faced in existing system * Limited user involvement Inadequate resources requirement * Business requirement have changed between commencement and deliverance * Absence of CASE support for analysis and design * Low level of involvement of users was due to lack on ownership and assurance of the system * Inadequate techniques * Inadequate designing and tools * No updating of database management system Solutions for the existing problems: The only solution for the problem is to adapt the computerized customer support system to support their business operations which will help them with the accurate and faster calculations to produce * End of day deposit slip Weekly report of restaurants * Sales report as per their desire i. e. weekly or monthly * Able to record orders effectively and informing end user efficiently * Inform drivers and restaurants at a click of button. * Increase delivery performance by flow of data in an efficient way Feasibility study Feasibility is defined as the viability of project feasibility does not solve any problem but it gives a scope of solving a problem. The aim of our feasibility report is to find out the problem of the current system in waiters on wheels and meet the end users requirements. Realism of project To decide whether the aims stated in the project are realistic within the given constraints. Scope of improvements In current system there are lots of problem with recording order, producing day and weekly sales report which leads to inconsistency in delivering the meals ordered on time and running the restaurant. We are developing a system which will help sorting out such problems effectively and efficiently. Specialist assistance We are developing a user friendly system so that no specialization is equired to operate the system, even a person with little bit knowledge in computers will be able to operate it. Principle work area To determine whether the principle work areas relating to the aims stated in the project permit planning of full investigation including the project teams departments and application involved. Feasibility report Our feasibility report consists of: * Technical feasibility * Operational feasibility * Schedule feasibility * Economic feasibili ty Technical Feasibility: Technical feasibility address three major issues * Is the proposed system technology is practical Does the organization currently possess the necessary technology * Does the organization possess the necessary technical expertise * And if the technology is not present then is it affordable by the organization Generally, the technology for the any defined solution is available. The question which should be considered is whether that technology is mature enough to be easily applied to the problem. Some firms like to use latest technology, but most of the firms prefer a mature and proven technology . A mature technology has a larger customer base for obtaining advice concerning problems and improvements. Assuming that the solution’s technology is practical, the next step is to determine whether it is available in the organization has the capacity to use it? If the answer to nay of the above questions is no, then the possibility of getting it from outside should be considered. If it is available outside, but is too costly for the organization to purchase it, then the alternative that requires the technology is not practical and is technically infeasible. Operational feasibility: In operational feasibility study measures the urgency of the problem or the acceptability of a solution . There are two aspects of operational feasibility which should be considered. * Is the problem worth solving, or will the solution to the problem work? * What do the end users, and the management feels about the problem? This feasibility was carried to get the answer to the question whether the system will be used and implemented if developed. Would there be any resistance from its users. PIECES FRAMEWORK * Performance: Receiving customer order till delivering Order. Information: How the information is passed from WOW – Driver Restaurants * Economy: It is cost beneficial * Control: Installing password, firewall and antivirus , so that there is no unauthorized access * Efficiency: System is time efficient and effective, providing the information on single click * Services: System will provide desirable and reliable service to customer and end users Schedule Feasibility: Schedule feasibility is an analyzing the time for a project to be completed. The schedule feasibility consists of: Work Load Matrix Tasks| Ivneet| Ivneet| Ivneet| Ivneet| Identifying the existing system| * | | | | Analysis of current system| * | * | | | Problems in existing system| | * | | * | Feasibility report| | * | * | | Work load matrix| * | | | | Gantt chart| | | | * | Operational feasibility| | | * | | Selection of methodology| * | * | * | * | Justification | | | * | | Investigation techniques| | | | * | Logical design| * | | * | | Physical design| | * | | * | Conclusion | * | | | | Economic feasibility The economic feasibility underlies the whole system development effort. We assume the Economic feasibility to analyze the cost of the project in order to know whether it is worth spending to develop the system. The system that we are going to design is flexible and less expensive which will provide immediate access to records that are only periodically updated. Cost – benefit analysis This to analyze, The cost to develop the system Which includes man power costs, and the technology used to build the system etc. The business cost If the system is developed then what will be its maintenance costs? Selecting the methodology In this we have to select the methodology for our project i. e. Waiter on Wheels customer support system. Basically there are two types of methodology used for the projects Structured System Analysis and Design Methodology and Object Oriented Methodology. We have chosen Structured System Analysis and Design Methodology (SSADM) Reasons for selecting this methodology It provides measurable, reviewable and definable product specification. At the end, the process draws on more system personnel resources as well as user involvement. It increases involvement and communication between system and users. It also allows allocation of simpler tasks to junior personnel which mean each and every . member is equally distributed among tasks. A great impact of this methodology is that the total time and cost are greatly reduced, if system developed by this methodology is implemented in the organization. Stages that should be followed SSADM * Analysis of the current system * Detailed business specification * Logical data design * Logical process design * Physical design. Detailed business specification Customer calls waiter on wheels to place the order, Waiter on wheels then informs to the related restaurants for the order. Waiter on wheels then checks the availability of the driver and informs driver to pick the order from the restaurants then restaurants will give the order to the driver The driver will take the order and deliver it to customer, after delivering the order driver will come back and give the bill to waiter on wheels. Now waiter on wheels keeps the record of each and every restaurant, what are the orders taken from them and on which date and time. Weekly or monthly waiter on wheels will pay the bill payment as per the wholesale price or the deal what they have done. Flowchart A flowchart is a formal graphic demonstration of a logic sequence, work or built-up process, organization chart, or similar formalized structure. Flowcharts are used for designing and managing a program. It is represented by various symbols to show the flow of data in a logical manner, each and every symbol has different meaning. Payment To driver Customer Driver STOP Restaurant Detail of order Detail of customer Waiter On wheels Customer Oder START Flowchart Context level diagram:   A context Diagram shows the system boundaries, external entities that interact with the system, and the relevant information flows between the external entities and the system. It helps to: * Define the scope of a project, * Project benefits and risk factors. Orders Informs the restaurant Send delivery driver Supply food Send Bill Pay the Bill Cancel order Payment Restaurants Waiter On Wheels Customer Data flow diagram Data flow diagram (DFD) is a picture of the movement of data between external entities and the processes and data stores within a system. It shows relationship between following business processes: External systems, External organizations, Customers Other business processes. Data flow diagrams are used to describe how the system transforms information. It defines how the information is processed and stored and its flow throughout the process. 0 levelAvailability of driver Order placed Deliver Meal Restaurant Order Details Driver Waiter On Wheel Customer Sending order details Collecting meal Call for driver Invoice Order processing Informing restaurant Payment Accounts data Invoice Accounts Accounts Invoice details 1 level Restaurant Details Customer Details Restaurant Data Customer Data Availability of driver Order placed Deliver Meal Restaurant Order Details Driver Waiter On Wheel Customer Sending order details Collecting meal Call for driver Invoice Order processing Informing restaurant Payment Accounts data Invoice Accounts Accounts Invoice details ER-Diagram: is just the entity relationship diagram which shows the different entity’s and the attributes connected to it, it gives a brief description of the flow of logic of the system. ER- Diagram Reporting time Owners ID Owners Name Bank Delivery Charge Service Charge Sales Tax Whole Sale Price Pay Invoice Whole Sale Price No. of Items Menus Restaurants Picking Delivery Contains Available Unavailable Address Driver ID Name Contact No. Closing time Driver Informs No. of Items Related Restaurants Name Order Places/Cancels Customer Name Address Contact Details Customer ID Physical Design Physical Design: Physical design takes this logical design blueprint and produces the program specifications, physical file or database definition and user interface for a selected target hardware and software. These programs and files will fulfill the logical design requirements but may be subject to some constraints and compromises. Design objectives The system is designed based on the objectives set for the new information system in the strategic plan. Organizational objectives such as: * Increasing the business profit * Securing a larger market share * Improving customer service There are three main objectives which the designer has to bear in mind while evolving and evaluating design * Performance, how fast the design is secure against human error, machine hardware resources * Control, the extent to which the design is secure against human errors, machine malfunction, or deliberate mischief. Changeability, the ease with which the design allows the system to be changes to, for example meeting the user’s needs to have different transactions types processed. Individual Reports . Ivneet Singh (. leader and system analyst) Ivneet Singh (Logical Designer) Ivneet Singh (Physical Designer) Ivneet singh (Assistant Physical Designer) Ivneet Singh Registration no: 081301212 Role: . leader and System Analyst Abstr act I have played the role of system analyst, logical designer, and . leader and had contributed where ever the . was facing problem by conducting . eetings. The main objective of the project is to identify the different framework of activities associated with methodologies and describe how the techniques are used together to develop a system. The selected methodology SSADM has been clearly justified and compared to other related methodology. Logical designs are mapped accurately having clear and detailed documentation of designing phase with physical design by the physical designer of the group. To complete this project in effective way . had contributed their best so that all criteria can be covered efficiently. Introduction They were two students Sue Tom Bickford studying in college who also worked as part time job in a restaurant and always dreamt to open their own restaurant. Their initial investment was always out of reach so they noticed many restaurants that offer home delivery service . They got an idea of opening their own restaurant without high investment . This idea came to their mind after meeting many people who wanted home delivery service with their complete food selection. By this, they opened a restaurant â€Å"Waiter on Wheels† in 1997. This restaurant provides food delivery to the customers by gathering the meals form different restaurants and providing under one roof. Customers liked this service very much and their business waiter on wheels was increasing day by day. As there was increase in the number of customers and their orders they started facing some problems to run their business effectively. So they decided to have a computerized system to manage all the difficulties in their business. For the same they hired a consultancy. We are working on the same and have clearly documented in the project. How to overcome the existing problem? By making use of System Development Life Cycle (SDLC). System Development Life Cycle (SDLC) Systems Development Life Cycle (SDLC) is any logical process used by a systems analyst to develop an information system, including requirements, validation, training, and user ownership. Any SDLC should result in a high quality system that meets or exceeds customer expectations, reaches completion within time and cost estimates, works effectively and efficiently in the current and planned Information Technology infrastructure, and is inexpensive to maintain and cost-effective to enhance Intelligence Problem identification Feasibility study Analysis Logical design Design Implementation Physical design Implementation Maintenance System analyst In an organization or for a project system analyst is required to carry the project effectively in a well planned manner. System analyst must possess some necessary skills as System thinking: Must be aware of inter-related object or elements of the system. Once we have identified system, must be able to understand the principles and concepts about system to guide the design of information system and can easily co-relate with the environment. Organizational knowledge: Must understand working procedures and function of the organization. Problem identification: Must be able to understand the current situation of the organization or project concerned. Problem analyzing and solving: Once the problem has been identified, then analyze the problem how to solve it with the proven methods and documents. For analyzing and solving problems some approaches need to be followed as: intelligence, design, choice and implementation. Technical skills: Must know to develop computer-based information system, further be practical to adept with different notations for representing or modeling the various aspects of information systems. Management skills: As a system analyst must be able to manage work and use the resources of organization in efficient and effective way. System analyst is almost the member of project team and is frequently asked to lead the team. In spite of working in a technical field system analyst must possess interpersonal skills such as communicational skills (interviewing, listening and questionnaires). Analysis of current system For this project Waiter on Wheels current existing system has been analyzed in an effective way as: * Customer calls waiter on wheels to place the order, then waiter on wheels informs to related restaurants they have contract with * Then send the driver to take the delivery form the restaurant and place it to the customer address * The driver picks the order form restaurants and delivers to the customer and comes back to waiter on wheels * Driver took the payment including retail price and service charge from the customer and reports to waiter on wheels office. Problem identification The major problem with waiter on wheel was they were not able to manage the extending business as they keeps record manually. * Not able to manage database of customers * Not able to get the delivery on time specified by the customer as they were having only one delivery driver Solution for the problem To have a computerized system so that it can keep the records and saves time and human energy as well. This will also help to get the customer details such as address, contact number, etc†¦; if the customer calls next time to place an order. Selecting the methodology In this we have selected the methodology for our project i. . Waiter on Wheels customer support system. Basically there are two types of methodology used for the projects Structured System Analysis and Design Methodology and Object Oriented Methodology. We have chosen Structured System Analysis and Design Methodology (SSADM) After having meetings with the team the methodology was selected with the clear justification to other related methodologies. Reasons for selecting this methodology * It includes portioning a large system into a manageable smaller ones and organizing the details into an understandable by utilizing a top of structured methodology An integral part of this methodology is the modular concept. Under which frame work can be separated in a detailed management information system. For example the finance system of an organization can be divided into minor and basic modules. Finance Source Of fund Cash Management Capital budgeting Accounts payable management Cash disbursement management Accounts receivable management Cash receipt management Sales discounts management Other receivable management Trade receivable management Other income anagement Customers management Drafts management Checks management Purchase discounts management Capital expenses management Taxes management Payroll management Other payable management This is a top-down approach of a finance department from which anything can be seen regarding finance and employee can be called easily by the management. Logical design A logical design is conceptual and abstract. The process of logical design involves arranging data into a series of logical relationships called entities and attributes * An entity represents a chunk of information. In relational databases, an entity often maps to a table. An attribute is a component of an entity that helps define the uniqueness of the entity. In relational databases, an attribute maps to a column. I have contributed to make context level and 1-level data flow diagram; Context level diagram: A context level diagram shows the system boundary, external entities that interact with the system, and relevant information flows between the external entities and the system. It helps to * Define the scope of the project * Benefits and risk factors of the project Orders Waiter On Wheels Informs the restaurant Cancel order Restaurants Send delivery driver Customer Supply food Pay the Bill Send Bill Data flow diagram: Data flow diagram (DFD) is a picture of the movement of data between external entities and processes and to store within a system. It shows relationship between following business process * External system * External organization * Customers * Other business processes 1-level data flow diagram Restaurant Details Customer Details Restaurant Data Customer Data Availability of driver Order placed Deliver Meal Restaurant Order Details Driver Waiter On Wheel Customer Sending order details Collecting meal Call for driver Invoice Order processing Informing restaurant Payment Accounts data Invoice Accounts Accounts Invoice details Work load matrix Tasks| Ivneet| Ivneet| Ivneet| Ivneet| Identifying the existing system| * | | | | Analysis of current system| * | * | | | Problems in existing system| | * | | * | Feasibility report| | * | * | | Work load matrix| * | | | | Gantt chart| | | | * | Operational feasibility| | | * | | Selection of methodology| * | * | * | * | Justification | | | * | | Investigation techniques| | | | * | Logical design| * | | * | | Physical design| | * | | * | Conclusion | * | | | | Conclusion While doing this project I have reached to conclusion that SDLC is one of the best methods to carry a project in order to save time and to learn the project management. Among this one of the most important phase feasibility study taught us to do researches on various Technical and operational issues that are required for almost all project. The methodology that we have choose for developing the system required by waiter on wheel is also an one of best among other related methodologies. Which teaches different techniques for developing an information system? References Modern System Analysis and Design second edition Jeffrey A. offer University of Dayton Joey F. George Louisiana State University Joseph S. Valacich Washington State University google. co. in/search? hl=enq=+define+system+development+life+cyclemeta=aq=foq= Ivneet Singh Registration no: 081301224 Role: Logical Designer Abstract I have played the role of logical designer, and had contributed mainly in logical designing an d operational feasibility as well. The main objective of the project is to identify the different framework of activities associated with methodologies and describe how the techniques are used together to develop a system. The selected methodology SSADM has been clearly justified and compared to other related methodology. Logical designs are mapped accurately with physical design by the physical designer of the group. Operational feasibility: Operational feasibility is dependent on human resources available for the project and involves projecting whether the system will operate and be used once it is installed. In our project we have analyzed that the contents of operational feasibility in this project are:- * Implementation * Processing * People oriented * Government agencies Implementation: Implementation consists of three parts: Taking order- in this process we are designing our system that will be able to receive orders from customers it is going to work like this when a customer calls on phone or orders online the system is going to record the call by the name and address and the order specified, when the order is recorded by name and address the system is going to make beep sound which will alert the operator and he will be able to hear the voice call directly on the desktop. Order delivery: in this process the system is concerned about how the order is going to be delivered this comes under processing which I will explain further. Reporting back to office: in this process the system will keep a record of the drivers who are reporting back in office after delivery. The next step of operational feasibility is processing:- processing contains following contents:- 1. Receiving the call from customer: which I have already explained that the system will be able to record the call from customer according to their name, address and specifically the order. 2. Informing the driver: In this process we have given the facility that ystem will be able to inform driver according to the given database , we will store the names of driver in accordance with their areas our system will be able to check the availability of driver by following methods when a driver calls to the office and says that he is available the system will immediately record his message and the time of call so it will be easy or the operator to check the availability of driver and when he clicks the option call in front of the names of driver then the syste m will immediately call the driver and the operator will be able to inform him or leave him a message. And as the driver conforms that he is ready to pick the order the system will be able to store his out time on the request of operator clicking on the button out time. 3. Informing the restaurant: The next main step after informing the driver is to inform the restaurant so we have done the following we will give the data base of all the contacted restaurants in the system so the operator will be able to inform the restaurants according to the requirements and the order specified just on a click. 4. Picking the order: Next is all manual process in case the customer wants to change his order then we have decided a time limit for changing the order it is 15 minutes after the original order if the customer calls in between fifteen minutes of his first order then our system will be able to recognize the customers voice and in case voice does recognition does not work system will recognize according to name and address of the customer and it will be able to eradicate the first order and will beep with a voice message that the order of this customer has been changed 5. Delivery: It is a manual process which will be carried by drivers. 6. Collecting money from the customer 7. Reporting back to office: In this process when the driver reports back to the office then the operator will click on his name and on the button in time then the system will immediately notify his time and store it. 8. Calculation of number of orders per day: This will be calculated by the number of orders delivered which is done when the driver enters his in and out time which means that the order has been delivered the system will calculate the number of orders delivered . . Sending statements and paying the money to the restaurants by checks: This is done by the accountant when he checks that how many orders are delivered from which restaurants which will be stored in the system. People oriented: this consists of the following- 1. Receptionist will be the operator of the system she will take orders from the customers and inform drivers and the restaurants. 2. Drivers the peop le who will deliver the orders 3. Restaurants manager 4. Waiters on wheels manager . Customers 6. Accountant will keep track of the accounts Government agencies: government agencies include tax and service charge. Operational feasibility seen through PIECES framework: The PIECES frame work helps identify operational problems to be solved and their urgency. PIECES stand for: * Performance: Receiving customer order till delivering Order. * Information: How the information is passed from WOW – Driver Restaurants * Economy: It is cost beneficial Control: Installing password, firewall and antivirus , so that there is no unauthorized access * Efficiency: System is time efficient and effective, providing the information on single click * Services: System will provide desirable and reliable service to customer and end users Economic feasibility: The economic feasibility underlies the whole system development effort. We assume the Economic feasibility to analyze the cost of the proje ct in order to know whether it is worth spending to develop the system. The system that we are going to design is flexible and less expensive which will provide immediate access to records that are only periodically updated. Cost – benefit analysis This to analyze, The cost to develop the system Which includes man power costs, and the technology used to build the system etc. The business cost If the system is developed then what will be its maintenance costs? Economic feasibility as per system perspective: our system is economically beneficial because it will save time and money by storing and transforming the data in an effective and efficient way. End user will be able to inform restaurants and driver for the delivery directly by sending message he will also be able to check out the availability of drivers, so he can save the cost of telephone charges the system will be able to produce end of the day slip in which it will show total sales and profit done by sales both weekly and daily, by this manager of WOW need not to keep an accountant, this will save money. Selection of methodology: we have selected structured system analysis and design methodology. Structured analysis is one of the most popular methodologies that are being used to define system specification. Because of problems faced in traditional system development life cycle approach structured advancement have come up whose purpose is to provide more closely controlled more industrious development surroundings. These include structured analysis and design methodology along with structured programming. A structured approach to the analysis and design of systems differs from the traditional SDLC approach where it calls for the systems analyst to look beyond a physical view of the current system. The result of SDLC is generally inflexible and unmaintainable system. This methodology uses logical process design. The structured system development cycle consists of: * Structured methodology * Structured tools ,and * Structured process Structured methodology: the structured methodology of systems analysis, analysis, design, and implementation centers on building a logical model of the system in order to provide systems analysts, programmers and users a common picture of the system and its interrelationships. Structured process: it provides clear understanding of the system to system analysts. It consists of the following: * Objective: organization, scope, and schedule of new system. * Output requirements approved by users. * Database and data dictionary. * Inputs need to produce outputs * Processing via methods, procedures, data communications to tie output to inputs as described by a leveled set of data flow diagrams * Internal control to satisfy control and security requirements other considerations as deemed appropriate, such as new policies consistent with objective. ER diagram: In ER diagrams representation of data is done graphically by connecting entities and their relationships. There are three types of relationships between entities * One to one * One to many * Many to one Reporting time Owners ID Owners Name Bank Delivery Charge Service Charge Sales Tax Whole Sale Price Pay Invoice Whole Sale Price No. of Items Menus Restaurants Picking Delivery Contains Available Unavailable Address Driver ID Name Contact No. Closing time Driver Informs No. of Items Related Restaurants Name Order Places/Cancels Customer Name Address Contact Details Customer ID In ER diagrams attributes I gave for customer are name, customer id, address, contact details. I used this customer ID in customer form next one is address I used this in customer form to record the address of costumer, next is contact details and name to record the details of costumer. Next is the attributes for order that is number of items and related restaurants these attributes I used in invoice details form Next one is the attributes of driver that is name, driver ID, address, contact no. , reporting time this one is mentioned in driver details in physical design . this will record driver details in the form. Now we come to invoice details there is whole sale price, sales tax, service charge, and delivery charge. These attributes are used in the invoice form to record the invoice details. Next entity is restaurants which have the following attributes menus, wholesale price and number of items this is used in transaction per day. And the last one is bank which have owners name and owners ID this we used in weekly sales report. Data flow diagram 1 level Restaurant Details Customer Details Restaurant Data Customer Data Availability of driver Order placed Deliver Meal Restaurant Order Details Driver Waiter On Wheel Customer Sending order details Collecting meal Call for driver Invoice Order processing Informing restaurant Payment Accounts data Invoice Accounts Accounts Invoice details References: System Analysis and Design, VK Jain, fourth edition Ivneet Singh Registration no: 08130 Role: Physical Designer Abstract I have played the role of Physical designer and had contributed mainly in physical designing of the project based on the logical design. Physical design is clearly mapped to the logic given by logical designer. The main objective of the project is to identify the different framework of activities associated with methodologies and describe how the techniques are used together to develop a system using SSADM. Introduction Tom Bickford and Sue were two students in the college they always wanted to open their own restaurant which should provide meal delivery service to the customers. They started the restaurant â€Å"Waiter on Wheels† with very low initial investment in 1997 . When customer calls waiter on wheels and places the order, then waiter on wheels will inform the related restaurant for the order and send the driver to pick up the order from the restaurant and deliver it to customer. There business was increasing day by day as customer liked their food delivery services. Now as there was increase in number of customer’s waiter on wheels started facing some problems to run their business. System Development Life Cycle Structures of SSADM 1. Feasibility Study – in this we decide which and what are the methods or techniques that we can adopt , what will be the cost of the project and how much time will project take to accomplish 2. Requirements Analysis – in this we analysis the requirements for our system, do we have enough technology or resources to fulfill the client requirements. 3. Requirements Specification detailed functional and non-functional requirements are identified and new techniques are introduced to define the required processing and data structures. 4. Logical System Specification – for each and every project we need to have a logical design so that we can get entire idea for the project and it will help in the implementation. 5. Physical Design a physical database design and a set of program specifications are created using the logical system specification Problem Identification Planning Analysis Logical Design Physical Design Implementation Maintenance Problems faced in existing system * Limited user involvement: There were very few people involved in running this meal delivery system. They were having only one driver for the night shift, contract with only two restaurants in that area. According to increasing demand of customers, they need to get more drivers and contract with more restaurants in order to deliver the variety of food on time. * Inadequate resources requirement: As initial investment in opening restaurant was quiet less, they were not having adequate resources like delivery vehicles, mobile phones as waiter on wheels was meal delivery service. They need to get more delivery motorcycles and mobile phones so that they might contact with the driver on the way if there is any change in order or driver has to pick the order form some other restaurant. * Business requirement have changed between commencement and deliverance: As waiter on wheels was a meal delivery service which provides food from different related restaurants and deliver it to customer at one place. As this delivery business started by only contract with two restaurants and few customer. Customers were increasing day by day there was change in business functions which lead to problems like they were not able to deliver orders on time, not able to get in touch with the customer, delivering wrong order. Then they realized to input computerized customer support system. * Absence of CASE support for analysis and design: Tom and Sue started waiter on wheels without analyzing the current business situation and future planning . They didn’t do any feasibility study before starting this meal delivery system which later on started causing them problems. Low level of involvement of users was due to lack on ownership and assurance of the system: As there was low level of involvement in the entire delivery system, there were few people involved in this business. Their business was running smooth with limited number of customers and restaurants. But when the customer demand increased they were not able to manage the business effectively. * Inadequate tools and techniques: For each and every business some tools and techniques are required to run it in effective way . But in waiter on wheels they didn’t use any techniques to run the business that was the reason why they were not able to manage their business properly. When all things started messing up, then they realized to input some technique in order to manage their business and implemented computerized customer support system which will help them in managing the details of orders, customers and sales report etc†¦ * Inadequate designing: As waiter on wheels was a restaurant they need to have a menu and forms for the customers, so that customer can place the order easily. But they were having nothing like that when customer calls to place the order they just tell the lists of items on the phone and receive the order. But as per the customer needs they start designing the forms, bills, menu cards for the ease of customer. * No updating of database management system: They do not keep track of the sales report, drivers, customers, order. Selecting the methodology In this we have to select the methodology for our project i. e. Waiter on Wheels customer support system. Basically there are two types of methodology used for the projects Structured System Analysis and Design Methodology and Object Oriented Methodology. SSADM stands for Structured Systems Analysis and Design Method. It was developed for the stages of system analysis and design of system development. This method is most established and widely adopted. SSADM uses a mixture of text and diagrams in system development life cycle, from the starting of the project till physical design SSADM is waterfall-based methodology. It flows like the waterfall starts from initial stage and then moves forward step by step till reaches the goal state , if there are any changes to be made it will again start from the first and then carry on with the entire task . We have chosen Structured System Analysis and Design Methodology (SSADM) because this methodology is very helpful to systems analyst. It makes sure that they are not floundering in deep of complexity but can beneficially work on a system . This methodology often results in method for each project; it provides a firm basis for project controlling and scheduling. The project can be broken in several steps of the methodology and a variety of individuals and teams can set different steps to perform their task. This makes it easier for the project manager to estimate the duration and cost of the project. Gantt chart: Techniques used by SSADM SSADM uses a combination of three techniques: * Logical Data Modeling * Data Flow Modeling * Entity Behavior Modeling Investigation techniques The investigation techniques are * Questionnaires * Interview * Survey * Studying Documentation * Observation For our project I followed two investigation techniques from the among above listed i. e. * Interview * Studying Documentation Interview: As the project is concerned with the restaurant which provides service as home delivery I went to some restaurants providing the same service as waiter on wheels and I conducted short interview with manager of Dominos Restaurant to know what are the procedures tools and techniques followed by them in order to run their restaurant effectively. This information was very helpful throughout the project and also gave us idea about the meal delivery systems. After the interview in Dominos I went to other restaurants to know about their current delivery system followed by them. As I concluded form this that almost all the restaurants adopt same procedure and techniques for the meal delivery system. Studying Documentation: In order to find some different delivery system I referred to many journals, magazines, newspapers and internet, but there also I found almost the same system used by the restaurants. * Articles on restaurant delivering system ezinearticles. com/? id=1412254 * Magazine of Waiter on Wheels wowrestaurantmarketing. com/publications. shtml * How to start restaurant delivering system www. startupbizhub. om/how-to-start-a-restaurant-delivery-service. htm Physical Design: Physical design takes this logical design blueprint and produces the program specifications, physical file or database definition and user interface for a selected target hardware and software. These programs and files will fulfill the logical design requirements but may be subject to some constraints and compromises. Design objectives The system is designed based on the objec tives set for the new information system in the strategic plan. Organizational objectives such as: * Increasing the business profit Securing a larger market share * Improving customer service There are three main objectives which the designer has to bear in mind while evolving and evaluating design * Performance, how fast the design is secure against human error, machine hardware resources * Control, the extent to which the design is secure against human errors, machine malfunction, or deliberate mischief. * Changeability, the ease with which the design allows the system to be changes to, for example meeting the user’s needs to have different transactions types processed. Logical to physical design Files or database: Based upon the entity-relationship model and supported by the entity life history and the data dictionary * Processes and programs: Based upon the processes of the data flow diagram and supported by the entity life history and data dictionary * Input and output: Based upon the flow of the data flow diagram and supported by the data dictionary * Interfaces : Underpinned by understanding of requirements and skills level explored within the context of the data flow diagram * Controls: Supported by the data flow diagram On the basis of logical designing i. e. ER-diagram and data flow diagram I have designed the forms that are required by our develop system to keep the records of customers, drivers, orders, sales report and weekly reports for the convenience of waiter on wheel employees. Customer Information Form This is customer information form which will store customer details such as: * Customer ID * Customer Name * Customer Address Driver Information Form This is driver information form which will store driver details such as: * Driver ID * Driver Name * Contact No: * Reporting Time: * Delivery Time: * Closing Shift Time: Invoice Bill Form This form will print the amount of bill to be paid by the customer, this form consists of: * Date / Time : * Customer Name : * Customer Address : * Customer Phone Number : * Order Details : * Total Amount to be paid : This form will store and print the sales report at the end of day, this form consists of: * Order Details : * Total Number of Orders in a day: * Total Sale of day: Transaction per Day Report This form will store and print weekly sales report at the end of week, this form consists of: * Order Details : * Payment Details: * Restaurant Name: * Bill to be paid: * Status: * Cheque No: Weekly Report Conclusion While doing this project I have concluded that system development life cycle (SDLC) is one of the best ways to carry a project which also helps me in learning the skills of project management. Among this there are seven phrases followed by a project manager or an organization to develop the information system. One of the phases is designing under which logical and physical design are mentioned. In physical designing I came to know how attributes and entities are related to each other and finally to real life. References: * Analysis and Design of Information System, Second Edition (V. RAJARAMAN) System Analysis and Design Implementation (S. K Jha) * nos. org/htm/sad1. htm Ivneet singh Registration no. 081301217 Role: Assistant Physical Designer Abstract I have played the role of Assistant Physical designer and had contributed in feasibility report for the project. As feasibility is an important phase while working on project through SSADM. Analysis of the current system Th e system on which we are working is a system on waiter on a wheel. Our system processes in the following manners: First, the customer call waiter on the wheel to place the order, herby waiter on wheel intimates the restaurant and to the driver. The driver is responsible for the delivery. He takes up the order from the restaurant and delivers to the customer address and takes the payment and hand over the bill to the customers and after that he gets back to his waiter on wheels Problems in existing current system Since they are running the business on waiter on a wheel and have a tie up with other restaurant so it is obvious that they will come up with many type of problem. No doubt they will have benefit but at some point of time they will face some problems. The problems that they will face are as follows: 1. Inadequate resources and requirement 2. Inadequate techniques 3. Inadequate designing and tools 4. Absence of CASE support for analysis and design 5. Updating of database management system 6. Low level of involvement of users was due to lack on ownership and assurance of the system. 7. Business requirement have changed between commencement and deliverance. Since there were many problems they might face so to sort out the above mentioned problems there must be a proper solution. So we come up with the following solutions: 1. End of day deposit slips 2. Weekly rep[ort of restaurant 3. Sales report as per their device 4. Able to record order effectively and informing the user effectively 5. Inform drivers and restaurant at the click button Feasibility report Before I lay down the reports for the feasibility, we must be aware of the term feasibility. Feasibility is defined as the viability of project feasibility does not solve any problem but it gives a scope of solving problem. The aim of feasibility report is to find out the problem of the current system and meet the end user requirement. Our feasibility reports consist of the following: 1. Technical feasibility . Operational feasibility 3. Schedule feasibility 4. Economics feasibility Out here I will be reporting on technical feasibility. In this feasibility there are problems or issues which have to be looked at. The issues are as follows: * Is the proposed system technology is practical * Does the organization currently possess the necessary technology * Does the organization possess the necessary technical exp ertise * And if the technology is not present then is it affordable by the organization. Generally, the technology for the any defined solution is available. The question which should be considered is whether that technology is mature enough to be easily applied to the problem. Some firms like to use latest technology, but most of the firms prefer a mature and proven technology . A mature technology has a larger customer base for obtaining advice concerning problems and improvements. Assuming that the solution’s technology is practical, the next step is to determine whether it is available in the organization has the capacity to use it? If the answer to nay of the above questions is no, then the possibility of getting it from outside should be considered. If it is available outside, but is too costly for the organization to purchase it, then the alternative that requires the technology is not practical and is technically infeasible. Selecting the methodology In this we have to select the methodology for our project i. e. Waiter on Wheels customer support system. Basically there are two types of methodology used for the projects Structured System Analysis and Design Methodology and Object Oriented Methodology. We have chosen Structured System Analysis and Design Methodology (SSADM). Physical design Screen 1: In the screen shot 1 we deal about the customer information. Here you can clearly see that in the customer information we see that for every customer we have date, customer id, time, customer name and customer address. When the customer places the order we keep record of all the above information. First we note down the time and date at which the customer places the order and give them a customer id. After that we jot down their address. This is all we have in our screen shot 1 Screen 2: In screen shot we deal with the driver’s information that is responsible for delivery. All the details of the driver are fed in the form. The details which includes in the form are as follows: Driver name/id Order id Delivery time Closing shift time Contact no Reporting time Order time Screen 3: Third screen deals with the invoice bill. In this again date, time ,customer id, customer name, customer address are mentioned. There we also mention all the details of order such as items. Quantity and rate. And the total amount. This is for the customer so that he must be made aware of the orer he has placed and how much he is going to pay for his order. Screen4: Fourth screen deals with the transaction per day form. In this form all the details of the daily transaction are mentioned. Transaction form consists of order detail, total number of order placed in a day and total sale. In order detail all the details including the time at which it was ordered, then the name of drivers and his id is written . the name of restaurant and total bill are also mentioned. This helps them to maintain the record of their daily sales. Screen 5: Fifth form deal with all the information related to weekly report. The weekly report consists of information related to Restaurant Payment

Writing Research Papers

Writing Research Papers Writing Research Papers Writing Research Papers: Steps to Walk Writing research paper is a rather complicated task as it demands a lot of efforts from students. However, it becomes much simpler to cope with the task if you are acquainted with the main steps you have to walk while writing research paper. In this article, we are going to make you acquainted with these steps of successful writing research paper. Step 1. Choose the proper topic for your writing. You see if you like the topic, you are dealing with in your writing research paper, you have enough enthusiasm and desire to complete it and you do not have to torture yourself while writing it, as writing is like an exciting adventure for you. Of course, if you do not like the topic of your writing research paper, you will have to make yourself writing it, and it will be rather boring for you to deal with the task. If a person does something without a proper desire it becomes too difficult for him or her to succeed in completing the task. Step 2 . Searching for information. The majority of professors advise their students to make use of primary sources for gathering information for writing research paper such as libraries and textbooks. Of course, when you have enough time this is the best way to get your information. However, if you have limited time, we recommend you to serf the Internet. You see by clicking different links you may find useful information much faster than reading through hundreds of pages of textbooks. That is why if you have compressed time for completing your writing research paper, we recommend you to gather your information with the help of the Internet. Appeal to some custom writing service in order to make your search of information fast and effective. Step 3. Make an outline for writing research paper. You see in order to structure all the information you have gathered it is recommended to spend your time for writing research paper outline. This outline helps students to concentrate upon th e main points of view in their writing research paper and not to forget any important idea he or she wants to present. That is why we consider writing research paper outline to be necessary step to walk. After you have walked all the steps, it is high time to start writing research paper. We wish you good luck with your work.