According To Criminal Justice Today Essay Example for Free

According To Criminal Justice Today Essay â€Å"Modern sentencing practices are influenced by five goals, which weave their way through widely disseminated professional and legal models, continuing public calls for sentencing reform.† The five goals of contemporary sentencing are Retribution, Incapacitation, Deterrence, Rehabilitation and Restoration. We are going to discuss what each goal means for sentencing criminals. Retribution a demand for punishment based on a need for vengeance. This is the earliest known rationale for punishment. Early cultures would punish almost every offender almost immediately and without a hearing. Severe penalties like death and exile where common forms of punishment even for minor offenses in early societies. The term just deserts means the offenders sentencing holds that the offenders deserve the punishment they receive at the hands of the law and the punishment should be appropriate with the type of crime. Incapacitation is the second goal of criminal sentencing and seeks to protect the innocent members of society from offenders who might harm them. Unlike retribution, incapacitation requires only restraint and not punishment like sending the offender to a correctional institution without imprisonment. The third example is deterrence. When you think of deterrence, it uses the example or threat of punishment that will convince people that committing crimes is not worth the penalty. Rehabilitation is the fourth example and brings about fundamental changes in offenders and their overall behavior. The ultimate goal of rehabilitation is to reduce the overall number of criminal offenses. Rehabilitation means to return a person to their previous condition. The final example is restoration. Restoration is a sentencing goal that seeks to address what damage was called by the offender that will make those who suffered whole again. This can range from victim’s assistance and/or supporting the victims with some form of compensations.

The Times They Are A-Changin by Bob Dylan Essay -- essays research pa

Bob Dylan's, ';The Times They Are A-Changin'; is an anthem for the oppressed, down-trodden young people, while warning that oppressors and abusers will be victims of their own actions. In the beginning of the poem, Dylan speaks to everyone and talks of the change coming from young people who feel that laws from the government and mom and dad's rules are smothering. He emphasizes 'everyone'; by using water to help the reader visualize how complete the wave of change will surround people. He then uses the water in a sink or swim analogy illustrating the direness of the situation. Throughout the poem, he shows the extent and gives examples of who will be affected. Although he draws class lines and social standings, the opportunity to change along with the times is always present. Dylan points specifically to 'senators, congressmen,'; ';mothers and fathers,'; because they have the most influence on America's youth. Dylan calls on the American government to 'Please heed the call' which shows that in the beginning, respect and persuasion will be used. The next two lines begin 'Don't'; which indicates a stronger will and mind set. 'For he that gets hurt/Will be he who is stalled,'; illustrates that if there is resistance to young people's ideas against the war in Vietnam, the idea of free love and the distaste for accepted social structures, that peace may not be an option. Dylan goes as far as to say 'There's a battle outside/And its ragin/it'll soon shake your windows/and ra...

Methodology is about the creation of knowledge Essay

Methodology is about the creation of knowledge, and methods are the guiding principles for the creation of knowledge (Arbnor & Bjerke, 1997). A methodology is chosen based upon philosophical presumptions, such as background hypotheses, normative theories, conceptions, and paradigms. A methodology is chosen based upon how an interaction between presumptions and technical possibilities define and shape the problem. To choose a methodology there should be an identifiable relationship between the methodological approach and the area to be studied, bridged by an operative paradigm. Methodology is an understanding of how methods are constructed and how an operative paradigm is developed. The operative paradigm consists of the methodical procedure and methodics. A methodical procedure is the specific use of a given technique for research in a methodological approach. As such, a technique becomes a method through the application of an explicit methodical procedure. Methodics is the way researchers relate techniques and methods into a study plan and the conduct of the study. While there are a variety of methodological approaches and procedures, there are three common research methodologies to guide primary researchers in the creation of knowledge. Quantitative research is the traditional research design, and it is considered to be scientific research due to its use of numbers as quantitative data (Robson, 2002). This method relies heavily on experiments and surveys which give it the label of a fixed research design. There is no variation from the administration of data gathering instruments. It may be easier to establish validity, reliability, objectivity, generalizability, and trustworthiness with quantitative research designs. Quantitative research may be characterized by experiments and measures. Comprehensive Examination for Aric W Hall Quantitative research attempts to precisely measure something, such as consumer behavior, attitudes, or knowledge (Cooper & Schindler, 2006). Quantitative research attempts to design, explain, and predict. The methodology may answer questions such as how much, how many, how often, when, and who. The survey is the dominant instrument of quantitative research. There is low researcher involvement, thus reducing the likelihood of researcher bias. Qualitative Early interest in qualitative research stemmed from the inadequacies of quantitative research to solve problems in the social sciences (Morgan & Smircich, 1980). Quantitative research is appropriate for the natural sciences, where reality is concrete, mathematical, and objective. However, it fails to address the often subjective, imaginative, values-based, and unpredictable human elements that social scientists study. Humans are social actors, made by their environmental and social context. Human reality is found within a context that is anything but natural science. Qualitative research is a more contemporary research design, and it has historically been considered unscientific

The Consumer Complaint Behavior

The consumer complaint behavior, CCB in short, is an area of research which deals with the identification and analysis of all the aspects involved in the consumer reaction to a product or a service failure and the consequent perceived dissatisfaction. A growing interest for CCB starts appearing toward the middle of the '60s as a particular aspect of a general attention for consumer behaviors and attitudes. Consumer satisfaction, dissatisfaction and consumer complaint behavior, in particular, are three distinct, but highly correlated subjects investigated by marketing and consumer studies.Real marketing problems can be considered at the origin of these studies. The growing competition in the market, the developing consumerism, the importance given to quality, performance and satisfaction, the emphasis given to customers, considered at the Centre of a product or of a service, bring researchers to inquiry about the complex mechanisms which determine customer satisfactions or dissatisfac tion and what are the consequent consumer behaviors.At the same time, as the research is deeply rooted in real life, the findings of the studies are aimed at identifying and suggesting managerial and practical solutions directly applicable to markets or services. As far as CCB research is concerned, the main aspects investigated can be summarized according to the some questions. The proposed list is anything but exhaustive: 1. Why do people complain? 2. Why do people not complain? 3. To whom do people complain? 4. Facing an unsatisfactory product or service, what are the possible reactions available for a customer? . Are there any differences in CCB according to the product or the service investigated? Being a Customer Relationship Manager of a luxurious hotel in Penang I received a mail from Mr. Stanley. He and his family stayed at my hotel last week. He has complained that the quality of food served was not satisfactory, hotel staff very impolite and not helpful and his computer n otebook and some cash was missing from his hotel room. Also he has criticized the hotel staff members that they do not listen to his complaint patiently. Firstly, I will send Mr.Stanley a letter of apologize and tell him about we will take further step even when full resolution is likely to take longer because fast acknowledgment remains very important and this action helps to build rapport with customer, the ? rst step in rebuilding a bruised relationship. In this letter I would not argue with Mr. Stanley and the goal should be to gather facts to reach a mutually acceptable solution, not to win a debate. Arguing gets in the way of listening and seldom diffuses anger. Next, I will show that I understand the problem from his point of view.Seeing situations through his eyes is the only way to understand what he thinks has gone wrong and why he is upset. Service personnel should avoid jumping to conclusions with his interpretations. Besides that, I have to clarify the truth and sort ou t the cause. Mr. Stanley says my hotel staffs are impolite, the food served is not satisfied and hotel members didn’t listen to his complaint, it may result from inefficiency of service, misunderstanding by Mr. Stanley, or the misbehavior of a hotel staff or third party. If I’ve done something wrong, I will apologize immediately. The more Mr.Stanley can forgive me, the less he will expect to be compensated. I would not be defensive because acting defensively may suggest that my hotel has something to hide or is reluctant to explore the situation fully. Furthermore, I will provide Mr. Stanley the bene? t of the doubt because not all customers are truthful and not all complaints are justi? ed. However, he should be treated as though they have a valid complaint until clear evidence to the contrary emerges. Because Mr. Stanley miss some cash money and computer notebook from his hotel room so careful investigation is warranted.Because the amount involved is not small, it ma y be worth haggling over a refund or other compensation. However, it’s still a good idea to check records to see if there is a past history of dubious complaints by the same customer. Propose the steps needed to solve the problem. When instant solutions aren’t possible, I will tell Mr. Stanley how my hotel plans to precede shows that corrective action is being taken. It also sets expectations about the time involved and I should be careful not to overpromise. I have to keep Mr.Stanley informed of progress because nobody likes being left in the dark and it may cause uncertainty breeds anxiety and stress. People tend to be more accepting of disruptions if they know what’s going on and receive periodic progress reports. Moreover, I have to consider compensation. When Mr. Stanley do not receive the service outcomes he believes he has paid for or have suffered serious inconvenience and loss of time and money because the service that hotel provide are failed to delive r to him, I might offer an unconditional money back guarantee and tell Mr.Stanley if at any point during the search process he is unhappy with progress, simply address the fact with us and if we are still not 100 percent satis? ed after that discussion, I will cheerfully and unconditionally refund every cent he has paid as a retainer. No quibble, no hassle, guaranteed period. This type of recovery strategy may also reduce the risk of legal action by an angry customer. Service guarantees often lay out in advance what such compensation will be, and hotel should ensure that all guarantees are met.Whatever is promised in the guarantee must be totally unconditional, and there should not be any element of surprise for the customer. The guarantee has to easy to understand and communicate to Mr. Stanley so that he is clearly aware of the bene? ts that can be gained from the guarantee. Meaningful to Mr. Stanley in that the guarantee is for something important to him and the compensation shou ld be more than adequate to cover the service failure.Guarantee has made must easy to invoke It should be easy for the customer to invoke the guarantee and it also have to easy to collect on because If a service failure occurs, the customer should be able to easily collect on the guarantee without any problems. Lastly, guarantee has to be credible and be believable. Persevere to regain Mr. Stanley goodwill. When Mr. Stanley has been disappointed, one of the biggest challenges is to restore his confidence and preserve the relationship for the future. Perseverance may be required to defuse is anger and to convince him that actions are being taken to avoid a recurrence of the problem.Truly exceptional recovery efforts can be extremely effective in building loyalty and referrals. Also I will check the service delivery system and pursue eminence. Because Mr. Stanley has left, I should check to determine whether the service failure was caused by accidental mistakes or system defects. I ne ed to take advantage of every complaint from Mr. Stanley to perfect the whole service system. Even if the complaint is found to be a result of a misunderstanding by Mr. Stanley, this implies that some part of my communication system is ineffective.But while we discussed the importance of professional complaint handling and service recovery, we have to acknowledge that not all complaints are honest. When ? rms have generous service recovery policies or offer guarantees, there is always the fear that some customers may take advantage. Also, not all complaining customers are right or reasonable in their behavior, and some may actually be the cause of complaints by other customers. We refer to such people as jaycustomers. Every service has its share of jaycustomers. Jaycustomers are undesirable. At best, a ? rm should avoid attracting them in the ? st place, and at worst, a ? rm needs to control or prevent their abusive behavior. Let us ? rst describe the main types of jaycustomers befo re we discuss how to deal with them. De? ning a problem is the ? rst step in resolving it, so let’s start by considering the different types of jaycustomers. I’ve identi? ed seven broad categories. The Cheat – There are many ways in which customers can cheat service ? rms. Cheating ranges from writing compensation letters with the sole purpose of exploiting service recovery policies and cheating on service guarantees, to in? ating or faking insurance claims and â€Å"ward robing†.The Thief – Those customers who always wishes to payless or not to pay, these may be like travelling in public transport freely, or not paying restaurant bills and others – firms to be prevented from such customers use many tips because if company is not taking actions against such people; other customers would also have intentions to behave in such manners. The Rulebreaker – Those customers who don’t obey rules of company or country like breaking traf fic rules – even though it costs them sometimes a lot but they do because they feel pleasure in behaving such manners†¦.Company should ensure that rules are to be followed. The Belligerent – Expresses resentment, use to abuse employees verbally or even physically. It causes demotivation of employees if company doesn't react upon such customers because for everyone in this world SELF RESPECT is most important thing, Guards/Security are their best solutions, Company should also guide their Front line staff to deal with such uncertain circumstances†¦ The Family Feuders – Customers who gets in detailed arguments with other customers about company of any kind.The Vandal – Those customers who always makes hurdle for company like pouring water in ATM, writing on walls, in cybercafes deleting windows files or other software. The Deadbeat – These are not like thief but close to them, these are those who pays the amount but after creating such prob lems for company, like I’ll pay tomorrow, they know that they have to pay but they try to delay as much as they can. Encouraging customer feedback provides an important means of increasing customer satisfaction and retention.It is an opportunity to get into the hearts and minds of the customer. In all but the worst instances, complaining customers are indicating that they want to continue their relationship with the firm, but they are also indicating that all is not well and that they expect the company to make things right. Here, service firms need to develop effective strategies to recover from service failures so they can maintain customer goodwill. That is vital for the long-term success of the company.Having professional and generous service recovery systems does not mean â€Å"the customer is always right† and that the ? rm is open to customer abuse. Rather, it is important for the bene? t of all too effectively deal with jaycustomers. (1782 words) References www . google. com www. wikipidea. org http://deni9ek. blogstudent. mb. ipb. ac. id/files/2011/12/CHAPTER-13-CASE-3. pdf http://www. scribd. com/doc/51888732/Services-Marketing-Lovelock-Wirtz-Chaterjee-Ch-13

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

Biography of Georges Braque, Pioneer Cubist Painter

Biography of Georges Braque, Pioneer Cubist Painter Georges Braque (May 13, 1882 - August 31, 1963) was a French artist best known for his cubist paintings and the development of collage techniques. He worked closely with Pablo Picasso as they broke down traditional rules of the use of perspective in painting. Fast Facts: Georges Braque Occupation: Painter and collage artistBorn: May 13, 1882 in Argenteuil, FranceDied: August 31, 1963 in Paris, FranceSelected Works: Houses at lEstaque (1908), Bottle and Fishes (1912), Violin and Pipe (1913)Notable Quote: Truth exists; only lies are invented. Early Life and Training Growing up in the port city of Le Havre, France, young Georges Braque trained to be a house painter and decorator like his father and grandfather. In addition to working on his vocation, Braque studied in the evenings at Le Havres Ecole des Beaux-Arts as a teenager. After apprenticing with a decorator, he earned a certificate to practice the craft in 1902. In 1903, Braque enrolled in the Academie Humbert in Paris. He painted there for two years and met avant-garde painters Marie Laurencin and Francis Picabia. The earliest Braque paintings are in the classic impressionist style. That changed in 1905 when he began to associate with Henri Matisse. Public domain Fauvist Matisse was at the forefront of the group of painters known as the Fauves (beasts in English). They are noted for the use of vibrant colors and simpler lines designed to make a bold, emotional statement to the viewer. Georges Braques first exhibit of his Fauvist paintings took place at the Salon des Independants show Paris in 1907. Braques Fauvist works are slightly more subdued in color than those of some of the other leaders of the style. He worked closely with Raoul Dufy and fellow Le Havre artist Othon Friesz. After viewing a massive retrospective show of the work of Paul Cezanne in Paris in late 1907, Braques work began to shift again. He also visited Pablo Picassos studio for the first time in 1907 to view the legendary painting Les Demoiselles dAvignon. The association with Picasso had a powerful impact on Braques evolving technique. The Olive Tree Near lEstaque (1906). Public domain Work With Pablo Picasso Georges Braque began to work closely with Picasso as they both developed a new style that was soon dubbed cubism. Many researchers dispute the specific origins of the term, but while organizing a salon show in 1908, Matisse reportedly said Braque has just sent in a painting made of little cubes. Picasso and Braque were not the only artists developing the new approach to painting, but they were the most prominent. Both artists exhibited influences of Paul Cezannes experiments with painting objects from multiple perspectives. While some believed that Picasso led the way and Braque merely followed in his wake, a close examination by art historians has revealed that Picasso focused on the animation of objects while Braque explored a more contemplative approach. In 1911, Braque and Picasso spent the summer together in the French Pyrenees mountains painting side by side. They produced works that are virtually impossible to distinguish from each other in terms of style. In 1912, they expanded their approach to include collage techniques. Braque invented what came to be known as papier colle, or paper cutouts, a method of incorporating paper with paint to create the collage. Braques piece Violin and Pipe (1913) illustrates how the pieces of paper allowed him to literally take the shapes present in the objects apart and rearrange them to create art. Man with a Guitar (1911). Corbis Historical / Getty Images The extended collaboration came to an end in 1914 when Georges Braque enlisted in the French Army to fight in World War I. He suffered a severe head injury in May 1915 in the battle at Carency. Braque experienced temporary blindness and required a long period of recuperating. He did not begin painting again until late 1916. Cubist Style The style of cubism is an expansion of the experiments by painter Paul Cezanne in depicting three-dimensional form on a two-dimensional canvas. Cezanne died in 1906, and, following significant retrospectives of his work in 1907, Pablo Picasso painted Les Demoiselles dAvignon, a piece that many believe is an example of proto-Cubism. At the same time as Picasso exhibited his new style through abstracted images of people, Braque was at work on extending Cezannes vision of landscapes with reductive, geometric forms. Soon, the pair became leaders of a new style of painting that attempted to represent multiple viewpoints on an object or person simultaneously. Some observers likened the works to a diagram of how the objects worked and moved in real life. Gjon Mili / Getty Images In the period between 1909 and 1912, Braque and Picasso focused on a style now known as analytic cubism. They painted mostly in neutral colors like brown and beige while taking apart objects and analyzing their shapes on the canvas. It is difficult to tell the work of the two artists apart in this period. One of Braques key works during this time is Bottle and Fishes (1912). He broke the object into so many discreet shapes that the whole became nearly unrecognizable. Cubists challenged the conventional view of perspective in painting that ruled the establishment since the Renaissance. It was perhaps the most important legacy of Braques art. Breaking down the rigid notion of perspective paved the way for multiple developments in the painting of the 20th century that ultimately led to pure abstraction. Later Work After he began painting again in 1916, Georges Braque worked alone. He began to develop a more idiosyncratic style that included brighter colors while relaxing the harsh nature of his earlier cubist work. He became close friends with Spanish artist Juan Gris. New subject matter entered Braques work in the 1930s. He began to focus on Greek heroes and gods. He explained that he wanted to show them in a pure form stripped of symbolic gestures. The bright colors and emotional intensity of these paintings depict the emotional anxiety felt by Europeans as a second world war approached. Painter and Model (1939). Corbis Historical / Getty Images After World War II, Braque painted ordinary objects like flowers and garden chairs. He created his final series of eight works between 1948 and 1955. They were all titled Atelier, the French word for the studio. At the time Georges Braque died in 1963, many considered him one of the fathers of modern art. Legacy While his painting ranged across multiple styles during his lifetime, Georges Braque is primarily remembered for his cubist work. His focus on still life and landscapes influenced later artists who returned to the traditional subject matter. Braques most distinctive legacy is his development of collage techniques involving cut paper that he focused on for only a few short years of his career. Source Danchev, Alex. Georges Braque: A Life. Arcade, 2012.

Critique Essay Example | Topics and Well Written Essays - 2500 words

Critique - Essay Example In this qualitative study, titled - Using a strategy of â€Å"structured conversation† to enhance quality of tutorial time the author Stephanie Robinson has proposed a specific approach referred to as â€Å"structured conversation† as an effective tool for improving the quality of tutorial time with regard to students with ASD. The article was published in the Journal of Further and Higher Education (Vol. 32, No.1 February 2008). It is an international peer-reviewed academic journal involved in publishing articles and book reviews concerning global issues related to the field of learning and education, especially those with learning disabilities (2009 [online]). The author is a lecturer and module leader for the PGCert.LTHE since 2003 and for the Brunel Associate Practitioner Pathway since. She is involved in various projects including providing further education particularly to students with learning difficulties and is focused on working with both the adolescents as well as adults with ASD. She has also been a part of a program dedicated to development and implementation of training for staff teaching children or adults with autism or Aspergers Syndrome (2009 [online]). Her credentials and extensive knowledge in the field of education (and particularly with regard to students with learning disabilities) establishes her as a worthy and suitable authority within the sphere of research concerning special education. In this article the author Stephanie Robinson, attempts to examine the â€Å"The impact of a technique of structured conversation to enhance a student-centered approach to tutorial time for students with autistic spectrum disorder† (2008., Pp.59) and suggests that the development of such an approach can offer enhanced learning support in the current challenge of widening diversity in the learner population. The purpose of the article was aptly