This action might not be possible to undo. Are you sure you want to continue?
the various types of Records pertaining to his/her customer. The product will help the user to work in a highly effective and efficient environment. The salespersons have been recording the customer information in the past and even in the present through their personal manual efforts. And indeed, it consumes their considerable time and energy that could be utilized in the better productive activities. Apart from that, with increasing customer Strength, the task of managing information of each individual customer is indeed a cumbersome task. There is a lot of reason for the introduction of this project. In the manual System, there are number of inefficiencies that a salesperson faces. The information retrieval is one of the foremost problems. It is very difficult to gather the overall performance reports of the customer. Large records-books have to be maintained where relevant and irrelevant information has to be stored which is very untidy and clumsy process. On the other hand, there are many inherent problems that exist in any manual system. Usually, they lack efficiency. Less efficiency has a great impact on the productivity of any human being keeping the data up-to-date. The4 automation deals with all such problems and tries to remove them in the best suitable fashion. The new system will cater to the need of the salespersons of any supermarket so that they can manage the system efficiently. The project “supermarket” is developed with the objective of making the system reliable, easier, fast, and more informative.
HOW IT IS IMPLEMENTED: “Supermarket caters to the needs of the salespersons. It’s easy for the user to meet the challenges of managing their records and retrieval of useful information. The application covers the area of client information, invoice, vendor, product etc and product in hand and delivered information. The system revolves around the menu of the items available. The user can browse through the menu to get the desired information. The project is very flexible because it allows the user to get information in Various possible categories. Everything is done dynamically. All the details are stored into appropriate database. The functionality of the proposed system includes the following: Customer information Vendor information Product information Quantity in hand Delivered stock The user can find relevant data in each module itself. He/she can modify, delete, update, view, or inset new data as when required. Performing these tasks is a very simple task in the product and the user can do it quite easily. The database is connected dynamically to front-end so that any changes made to database are immediately reflected to the user. SOFTWARE METHODOLOGY ADOPTED
Methodology is step-by-step plan for achieving a desire result. Software methodology uses a identified by major activities like analysis, design, coding, and testing to carried out and indicates which people (users, managers, technicians) should be involved in each activity and what role they play. Methodology often describes entry criteria, exit criteria and checkpoints for each of activities/stages. The term life cycle can be used sinuously with the term methodology. The most popular methodology is used today are based on the structured techniques or information engineering techniques. Object oriented techniques have of late attracted a great deal of attention and are becoming dominant methodology. Where as method is a step-by-step technical approach for performing one or more activities identified in an over all methodology. Thus, structured analysis is a method for carrying out the analysis phase of a project while object oriented design is a method for performing the design face.
The waterfall life cycle, which was developed in the late 1960’s is one of the commonly practiced approaches to software development. The waterfall life cycle is illustrated below: Analysis
STRUCTURED METHDOLOGY Structured techniques made their first appearance in the late 1960’s with the introduction of the structured programming. Structured design and structured analysis techniques were proposed later in 1970’s. These techniques are best suited for process-oriented systems i.e. they are driven by the functionality of the system rather than by the data used by the system. It is more function-oriented methodology then the data oriented. Structured analysis and design tools were originally characterized by two graphical modeling tools (data flow diagram and structure charts) that emphasized the functions performed by a system. Additional components included data dictionaries, process specification and later on incorporated entity relationship diagrams and time dependent behavior of the system. Information engineering methodology Information engineering methodology reverses the emphasis: data plays the dominant role and faction plays subordinate role. This Information engineering methodology includes business function/entity type matrices to show relationship with in the enterprise and entity they used or modify and include diagrams life ER diagrams, hierarchy diagrams etc. the more important than the emphasis on the data is emphasis on the level of the models in Information engineering methodology. While structured methodology can be used to model entire enterprises, majority of cases they are used to models individual programs or system. Information engineering is perceived as the higher-level methodologies that is intended to the first model the enterprise/organization and then model the individual system that constitutes the organization. The idea is not to study the only particular system but the whole organization as a whole. Which constitutes number of sub-system. Information is the thread binding all the different function/subsystem and hence it forms the basis for analysis the business needs, objectives and a strategies. And organizational view taken and a model built which shows the relationship of these various elements. This model when further decompose will give details of the individual system and the processes with them. Thus Information engineering methodology is becoming gradually more popular as organization is looking at enterprise wide solution and total methodology OBJECT ORIENTED METHODOLOGY: Object oriented programming technology existed in 1960’s. The underlining concept of an object oriented methodology matured from issues of coding to issues of analysis and design. The underlining technology for building system has become much more powerful like it was difficult to think about coding in an object oriented fusion when language of choice was Cobol, Fortran or C, it has become easier with C++, Objective C, Smalltalk and ADA. The system we build today is different than they were ten or twenty years ago. In every respect they are large and more complex. They are also more volatile and subject to constant change. We find that today online, interactive systems devote much more attention to the user interface than the text oriented batch-processing systems. Almost 75% of the code in modern system is concerned with user interface and this particular evident with the GUIs available today. With systems beige subject to constant change, reusing components of exiting system and building newer systems has become a necessity. An object oriented to such systems is a more nature way of
dealing with such use oriented systems. Systems built today are more “Data Oriented “ than systems built earlier. Hence, modeling the data has become a higher priority. Suitable Methodology: Software Engineers are constantly facing with the dilemma of which methodology to use for which system. The solution is to use the methodology depending on the application/system in question. The type and requirements of the application will dictate which method so best suited for that system. Software Methodology Used For The Proposed System Since the proposed system is more process Oriented than Data Oriented therefore, I adopted the Structured Methodology. It is more Function-oriented methodology than data oriented. Under this methodology I went through the following steps of systems development: A) System Analysis: System Analysis is the first and foremost phase in the methodology of system development because the development of and success of all the phases ahead are entirely dependent on the successful development of this phase hence, system analysis in this organization is taken as most crucial and done very carefully. I went through the following steps in this phase: 1. Problem identification: The problem has to identify before it can be solved. The basis for an alternative system is the recognition of the need for improving an information system or all a procedure. The objective of this phase is to answer the following question: a) What is the problem perceived? b) What is the goal to be achieved by the solution? c) What are the benefits, which will result for achieving the solution? 2. Preliminary Investigation: After identifying the problem the Preliminary Investigation was done for the feasibility study and technical, economic and operation feasibility was determined along with cost benefit analysis. After determining the feasibility of the proposed system I started understanding the situation, gathering and interpreting facts, and diagnosing the problems. Basically in this process the system requirements were determined and the activities in requirement analysis & determination were: a) Requirement anticipation b) Requirement investigation c) Requirement specification
System Design: System Design is the most creative part of the Programming. In this phase of Project design, flowcharts and pseudopodia are of great importance. System design is a transition from a useroriented document to a document oriented to programmers or database personnel. I went trough logical and physical design with emphasis on the following: a. Preparing input/Output specification. b. Specifying the implementation plan. c. Preparing a logical design walkthrough before implementation. The various activities involved in the design process were: 1. Database design 2. Project design 3. System and program test preparation etc. Diagrammatic Presentation how this phase went through is as below:
Database Design Design Specification Allocation Of Function Program Design Design Phase Walkthrough
System test Requirements def.
Program test requirement
Development of Software: On the basis of analysis and design specification. I started the development of the software. In this phase actual coding of the program was done. System testing: Once the program are tested individually, then the system as a whole need to be tested. During testing, the system was used experimentally to ensure that the software does not fail i.e. that it will run according to its specification and in the way the user expect it to. Special test data was prepared as input for processing and the result were examined to locate unexpected result. System Implementation: In this stage I finally planned to implement the developed software before I collect the following required information by using the following facts finding techniques: 1. Interviews: Under the guidelines of my training officer and supervisor I interviewed the persons directly dealing with the manual system i.e. with salespersons and the manager of supermarket. I asked about how they perform their duties and what steps do they take. 2. Record Review: I also reviewed the complete record so as to come to know about the detailed procedure of the supermarket that how they manually handle the complete process form the in coming of the client till the delivery of their products. 3. Observation: Observation helps analysts to gain information one can’t obtain by any fact-finding method. I observed the functioning of supermarket and got first hand information about how the activities are carried out in supermarket. I came to know how the documents are handle, how processed are carried. 4. Discussion: Another way to finding the facts and data for the design of the system is discussion. Discussion is the best method to solve sort of critical and abstract problems that cant be solved concretely by just observing and record reviewing etc.
5. LITERATURE SURVEY The major part of the information about the project was obtained from the client’s specification. Other information was gained by indulging into hectic and detailed discussion with the salespersons involved in the project. In order to get the realistic picture of the system requirement, the manual system of supermarket was supervised with the permission and full cooperation of the salespersons. Several type of question was asked from the salespersons to make picture clearer. The exiting manual system was also analyzed deeply to know the requirements of the client. The client was consulted many times for the betterment of the project. A large number of queries were asked from the End user in this regard.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.