Web Based POS Development

Transcription

1 Web Based POS Development REPORT OF MAJOR PROJECT SUBMITTED FOR PARTIAL FULFILLMENT OF THE REQUIREMENT FOR THE DEGREE OF MASTER OF COMPUTER APPLICATION (MCA) Of JADAVPUR UNIVERSITY By Kalyan Layek Registration No: of Exam Roll No: MCA Under the supervision of Prof. Anupam Sinha Dept. of Computer Science and Engineering Jadavpur University Department of Computer Science and Engineering Faculty of Engineering and Technology Jadavpur University Kolkata

2 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING FACULTY OF ENGINEERING AND TECHNOLOGY JADAVPUR UNIVERSITY TO WHOM IT MAY CONCERN This is to certify that the work titled XENOS-DEVELOPMENT reported in this dissertation has been satisfactorily completed by Kalyan Layek(Reg. No of ). It is a bona-fide piece of work carried out under my supervision and may be accepted in partial fulfillment of the requirements for the awarding of the Master of Computer Application degree of the Department of Computer Science and Engineering, Faculty of Engineering & Technology, Jadavpur University, during the academic year I wish him every success in life. (Prof. Anupam Sinha) Department of Computer Science and Engineering Jadavpur University Kolkata Countersigned By:. Prof. Sivaji Bandyopadhyay Head of the Department, Computer Science & Engineering, Jadavpur University, Kolkata

3 JADAVPUR UNIVERSITY FACULTY OF ENGINEERING AND TECHNOLOGY DECLARATION OF ORIGINALITY AND COMPLIANCE OF ACADEMIC ETHICS I hereby declare that this project contains requirement analysis gathered from client and original research work by the undersigned candidate, as part of requirements of the degree of MASTER OF COMPUTER APPLICATION of Jadavpur University. All information in this document have been obtained and presented in accordance with academic rules and ethical conduct. NAME : Kalyan Layek REGISTRATION NO : of ROLL NUMBER : MCA PROJECT TITLE : WEB BASED POS DEVELOPMENT. (Signature of the candidate with date)

4 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING FACULTY OF ENGINEERING AND TECHNOLOGY JADAVPUR UNIVERSITY CERTIFICATE OF APPROVAL This is to certify that the project titled WEB BASED POS DEVELOPMENT is a bonafide record of work carried out by Kalyan Layek for the award of the degree of Master of Computer Application in the Department of Computer Science & Engineering, Jadavpur University, during the period January 2013 to May It is understood that by this approval the undersigned do not necessarily endorse or approve any statement made, opinion expressed or conclusion drawn therein, but approve the project only for the purpose for which it is submitted (Signature of Examiners)

5 Acknowledgement The work of the project named WEB BASED POINT OF SALE DEVELOPMENT is successfully completed. We are most indebted to our We are extremely thankful to our respected teacher Mr. Palash Chanda for providing excellent guidance, encouragement and inspiration throughout the project work. Their wide knowledge and understanding have provided a good basis for work. In the process of making this project come to success we gathered many information from websites, books etc. and we also get a very good amount of help from our project guide Prof. Anupam Sinha. An enormous debt is also owed to our HOD of Dept. of Computer science and Engineering, and our respected teachers for their kind support and guidance during the entire course of MCA in Jadavpur University. I would like to convey special thanks to Finally the team expresses their gratitude to NIVT for the guidance to complete the project successfully. Date:.... (Kalyan Layek) M.C.A. 3rd Year Exam Roll No : MCA Jadavpur University

6 Metamorphosis 1. Scope of the project 2. Problem statement 3. Objectives 4. Benefits of the new system 5. Development platforms Requirement Analysis 1. Introduction 2. Information requirements 3. Software Requirement Specification 4. Feasibility Analysis a. Introduction b. Economic feasibility c. Technical feasibility d. Behavioral Feasibility Structural Analysis a. Context Analysis Diagram b. Data Flow Diagram c. Data Dictionary d. Process Description Planning of Project 1. Software Development Paradigm 2. Team Structure 3. Cost Estimation 4. Software Size Estimation 5. Estimated Time Scheduling 6. Software Configuration Management Design Analysis 1. Logical Design 2. Physical Design a. Input Design b. Output Design c. E-R Diagram

7 Database Ananlysis 1. Normalisation 2. Database Design a. Table Structure b. Database Implementation (Model Data) Testing and Debugging 1. Testing Process 2. Definitions of Testing 3. Testing Objectives 4. Testing Principles 5. Theory of Testing 6. System Testing a. Unit Testing b. Integration Testing c. Validation Testing d. Functional Testing 7. Debugging 8. Testing Modules 9. Testing Strategies for the Project 10. User Training 11. System Implementation Security of the System 1. Physical Security 2. Database Security 3. Application Security Conclusion 1. Overview of the whole project 2. Project Scheduling 3. Limitations 4. Scope for Future Amendments

8 Appendix A: CODE SNIPPETS Appendix B: SNAPSHOTS Appendix C: BIBLIOGRAPHY

9 ABSTRACT Point of Sale (POS) The Physical location of a transaction, but usually refers to any device or system that is used to record the transaction for the retailer.a POS (Point-Of-Sale) system is a computer system typically used to manage the sales in retail stores. The most basic function of a POS system is to handle sales. When a customer arrives at a POS counter with goods to purchase, the cashier will start a new sale transaction. When the barcode of a good is read by the POS system, it will retrieve the name and price of this good from the backend catalog system and interact with inventory system to deduce the stock amount of this good. When the sale transaction is over, the customer can pay in cash, credit card or even check. After the payment is successful, a receipt will be printed. The prime activities figured out in this application are to sell products, prepare invoice, edit& delete products by admin, edit and remove customers, report generation etc. This Web Application reduces the paper work of shopkeepers& there are other many features to purely help them to work easily in their fields.

10 SCOPE OF THE PROJECT A POS (Point-Of-Sale) system is a computer system typically used to manage the sales in retail stores. It includes hardware components such as a computer, a bar code scanner, a printer and also software to manage the operation of the store. Basically we know that most of the points of sale software s are desktop application but this point of sale is a web based application so that it has a special feature that we can create a centralized database for this point of sale that is it is possible to used multiple application from different location using only one database. PROBLEM STATEMENT A POS (Point-Of-Sale) system is a very user input software and is less available in market. And as we know it is a web based and it maintains centralized database that s why there is huge probability of creating rush.

11 OBJECTIVE OF THE PROJECT A POS (Point-Of-Sale) system is a computer system typically used to manage the sales in retail stores. It includes hardware components such as a computer, a bar code scanner, a printer and also software to manage the operation of the store. Point of sale (POS) or checkout is the place where a retail transaction is completed. It is the point at which a customer makes a payment to a merchant in exchange for goods or services. At the point of sale the merchant would use any of a range of possible methods to calculate the amount owing, such as a manual system, weighing machines, scanners or an electronic cash register. The merchant will usually provide hardware and options for use by the customer to make payment, such as an EFTPOS terminal. The merchant will also normally issue a receipt for the transaction. For small and medium-sized retailers, the POS will be customized by retail industry as different industries have different needs. Currently in market there are many POS software available. Most of the POS Systems are Desktop Based Application. So for different operating system (platform) different POS System is required. Another drawback is if the POS application or the computer on which the POS is installed crashed, then all the data will be lost. So the web based POS will provide an ultimate solution to this problem which enables user to perform his operations efficiently and easily,

12 Benefits of the new system There are number of software available in the market. But our objective is to Introduce Point Of Sale System to provide a much more scientific & disciplined software for the customers & administrators. Computer based POS systems consists of a computer platform, a variety of special peripheral devices and a POS software application which ties it all together. Currently in market there are many POS software available. Most of the POS Systems are Desktop Based Application. So for different operating system (platform) different POS System is required. Another drawback is if the POS application or the computer on which the POS is installed crashed, then all the data will be lost Basically we know that most of the points of sale software s are desktop application but this point of sale is a web based application so that it has a special feature that we can create a centralized database for this point of sale that is it is possible to used multiple application from different location using only one database.

13 DEVELOPMENT PLATFORMS HARDWARE REQUIREMENTS Processor : Pentium Dual-core CPU 2.00GHz RAM : 1.00 GB HDD : 5 GB free-space Input device : Standard Keyboard and Mouse Output device : VGA and High Resolution Monitor SOFTWARE REQUIREMENTS Operating System : Windows 7 Home Basic 32-bit or higher Front End : NETBEANS IDE Back End : MICROSOFT SQL SERVER 2008 Language : JAVA Webserver : APACHE TOMCAT

14 JAVA CLIENT SERVER ARCHITECTURE Figure : Client-Server Model MODEL VIEW CONTROLLER ARCHITECTURE Figure : MVC Architecture

15 SERVLET&JSP ARCHITECTURE Servlet Architecture JSP Architecture

16 SQL SERVER 2008 SQL server is a high performance relational database server based on SQL. It is built on CLIENT-SERVER architecture, which means a front-end or client component, and a back end, or server component. SQL server forms the back-end component in this architecture and is responsible for providing all the standard DBMS functions. The client component, for which there are many different possibilities, is responsible for providing all of the user interface and application processing function. The language used to communicate between clients and SQL server is called Transact SQL is a superset of ANSI SQL. Transact SQL is an enhanced version provided by SQL SERVER. SQL SERVER 2008 is a scalable, high performance database management system designed to meet the requirements of distributed client-server computing. SQL SERVER 2008 is tightly integrated with almost all the languages available in the market. SQL Server 2008 Internal Structure

17 REQUIREMENT ANALYSIS Introduction Requirements analysis in systems engineering and software engineering encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various stakeholdersanalyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success of a systems or software project. The requirements should be documented, actionable, measurable, testable, traceable, related to identified business needs or opportunities, and defined to a level of detail sufficient for system design. Information requirements Before we starting a project we must have a specific knowledge about the the project that we want to develop that s why we must gather all the important informations about the project. Software Requirement & Specification A Software requirements specification (SRS), a requirements specification for a software system, is a complete description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints). The software requirements specification document enlists all necessary requirements that are required for the project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with the project team and customer.

18 Feasibility Analysis: Introduction The aim of the feasibility study activity is to determine whether it would be financially and technically feasible to develop the system or not. A feasibility study is carried out from following different aspects: Economical feasibility Economic justification is generally the Bottom Line consideration for most systems. Economic justification includes a broad range of concerns that includes cost benefit analysis. In this we weight the cost and the benefits associated with the candidate system and if it suits the basic purpose of the organization i.e. profit making, the project is making to the analysis and design phase. The financial and the economic questions during the preliminary investigation are verified to estimate the following: The cost to conduct a full system investigation. The cost of hardware and software for the class of application being considered. The benefits in the form of reduced cost. The proposed system will give the minute information, as a result the performance is improved which in turn may be expected to provide increased profits. This feasibility checks whether the system can be developed with the available funds. The Point Of Sale System does not require enormous amount of money to be developed. This can be done economically if planned judicially, so it is economically feasible. The cost of project depends upon the number of manhours required. Operational Feasibility It is mainly related to human organizations and political aspects. The points to be considered are:

19 What changes will be brought with the system? What organization structures are disturbed? What new skills will be required? Do the existing staff members have these skills? If not, can they be trained in due course of time? The system is operationally feasible as it very easy for the End users to operate it. It only needs basic information about Windows platform. Technical feasibility: A study of resource availability that may affect the ability to achieve an acceptable system. This evaluation determines whether the technology needed for the proposed system is available or not. Can the work for the project be done with current equipment existing software technology & available personal? Can the system be upgraded if developed? If new technology is needed then what can be developed? This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may include: Implementation Feasibility: This project can easily be made available online without much consideration of the hardware and software. The only required thing at the applicant s side is the Internet connection and a web browser, which are a no difficult issue these days. A database server and application server are required to set up at the admin side. After setting up the project online, even the administrator can access the system from anywhere.

20 STRUCTURAL ANALYSIS Data Flow Diagram A DFD is a graphic tool used to describe and analyzes the movement of the data through a system depicting the flow of data, store of data, source or destination of data and the processes that respond to changes in data. When the processes is described logically and independently of the physically components associated with the system. In contrast, physically data flow diagrams show the actual implementations and the movement of data between people, department and workstations. The DFD is one of the most important tool sets by the system analyst to model system components namely: System processes Any external entities that interact with the system (source or destination of the data) Data store The information flows in the system The following symbols are used is a Data flow diagram: Process: It is piece if work performed on data i.e. it shows what a system does. Data store: Data store is a place where data is held between processes, known as a file. Data Store External entities: Represent the people, programs organizations or other entities. Interact with the system by supply input or using outputs. Data flow: Shows the flow of data in the data flow diagram.

21 Data Dictionary: A data dictionary, or metadatarepository, as defined in the IBM Dictionary of Computing, is a "centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format. The term may have one of several closely related meanings pertaining to databases and database management systems (DBMS): a document describing a database or collection of databases an integral component of a DBMS that is required to determine its structure a piece of middleware that extends or supplants the native data dictionary of a DBMS Process Description: At first company adimin enter the company ID and password and logged in then make a new sale to the existing or non existing customer by registering the customer and at last after the completation of the total transaction generate a invoice and PLANNING OF THE PROJECT 1. SOFTWARE DEVELOPMENT PARADIGM: During the software development process the main focus sticks on the production related activities i.e. design, coding and testing. A process model that has been followed in order to meet the goal is process step specification, which is just a sequence of steps. Each step performs a well-defined activity, which leads to the output of one step forming the input of the next one. The information flow from a step is in the form of summary reports describing the amount of resources spent in the phase, scheduling information, errors found in the verification & validation activities etc. This type of information flow in the development process makes it possible for the project management to get precise information about the development process without being directly involved in the development process.

22

23 The waterfall model with feedback has been followed by the project development. In this model the project begins with the requirements. On successful demonstration of the requirements of the project, the specification begins. The planning starts only after the completion of specification phase and design after the planning phase. Once the design completed implementation phase begins. After this phase the integration phase starts and assures all the integration measures. The classical waterfall model is an idealistic one since it assumes that no development error is ever committed by the engineers during any of the life cycle phase. However in practical development environments the engineers do commit a large number of errors in almost every phase of the life cycle. The source of the defect can be many: oversights, wrong assumptions, use of inappropriate technology, communication gap among the project engineer etc. these defects usually detected much later in the life cycle. For example a design defect might go unnoticed till we reached the coding or testing phase. Once a defect is detected the engineer need to go back to the phase where the defect has occurred and need some of the work done during that phase and the subsequence phases to correct the defect and its effect on the later phases. Therefore in any practical; software development work it is not possible to strictly follow the classical waterfall model. Feedback paths are needed in classical waterfall model from every phase to its preceding phase as shown in figure to allow the correction of the errors committed during the phase that is detected in later phases.

24 Iterative Waterfall Model Though errors are inevitable in almost every phase of development, it is desirable to detect these errors in the same phase in which they occur. However it may not always be possible to detect all errors in the same phase in which they occur. Nevertheless the errors should be detected as early as possible. Even though a basic understanding of the waterfall model is necessary to be able to appreciate the other development processes the waterfall model suffers from many shortfalls. Some of the glaring shortcomings of the waterfall model are the following: 1. The waterfall model cannot satisfactorily handle the different types of risks that a real life software project is subjected to. E.g. the waterfall model assumes that the requirements be completely specified before the rest of the development activity can start. Therefore it cannot

25 be accommodated the uncertainties that exist at the beginning of most of the project. As a result it cannot be satisfactorily used in projects where only rough requirements are available. 2. To achieve better efficiency and higher productivity most real life projects cannot follow the rigid phase sequence imposed by the waterfall model. A rigid adherence to the waterfall model creates blocking states in the system. That is some team members would have to wait for a phase to be complete before they can start their next activity. This is clearly wastage of resources and such wastages are rarely tolerated in real projects. 2. TEAM STRUCTURE: Efficient software project management focuses on people, problem, and process. The manager who forgets the software engineering work is immensely goal oriented and human endeavor will never have excess in project management. Before software can be planed its objectives and scope should be established, alternative solution should be considered, technical and managerial constrains should be identified. The persons who are the five constrain-populate of the software process are: Senior Manger:-Who defines the business issues that often have significant Influence on the project. Project/Technical Manager:-Who plans, motivates, organizes and controls the practitioners who does the software work. Practitioners: -Who deliver the technical skill that is necessary to engineer a project or application. Customer:-Who specify the requirements for the software to be organized. End User:-Who uses the software as an application.

26 3. COST ESTIMATION: Software cost and effect estimation will never be exact to every variable, technical environment can affect the cost of software and affect the development. However, software project estimation can be transformed from a mysterious act to a series of systematic steps that provides estimates with acceptable risk. To activate reliable cost and effect estimate, a number of step arise. They are: 1. Delay estimation until late in the project (obviously, we can achieve 100% accurate estimates after the project is completed). 2. Base estimates on similar projects that have already been completed. 3 Use relatively simple decomposition techniques to generate project cost and effort estimates. 4 Use one or more empirical models for software cost and effort estimations. Here, the exact cost of the software cannot be disclosed because of our legal agreement with the organization. 4. SOFTWARE SIZE ESTIMATION: The exact size of the software was not known at the beginning because the requirements of the clients could not freeze at beginning. At an approximate the total size of the software was almost 6 MB. 5. ESTIMATED TIME SCHEDULING: Like all other areas of software engineering a number of basic principles guide software project scheduling. 1. Compartmentalization: The project must be Compartmentalized into a number of manageable activities and tasks to accomplish Compartmentalization, both products and the process are decomposed.

27 2. Interdependency: The Interdependency of each compartmentalized activity or task must be determined. Some task must occur in sequence other occur in parallel. Some activities cannot commence until the work product produced by another is available. 3. Time allocation: Each time to be scheduled must be allocated some number of work units. In addition, each task must be assigned a start date and a completion date that are function of interdependencies and whether work will be conducted on a full time basis. 4. Effort Validation: Every project has a defined number of staff members. As time allocation occurs, the project manager must ensure that not more than allocated number of people has been allocated at a given time. 5. Defined Responsibility: Every task that is scheduled is assigned to a specific team member. 6. Defined outcome: Every task that is scheduled should have a defined outcome, for software projects the outcome is normally a work product or a part of a work product. 7. Defined milestones: Every task or a group of tasks should be associated with a project milestone. A milestone is accomplished when one or more work product have been reviewed for quality or approved. 6. SOFTWARE CONFIGURATION MANAGEMENT: Software configuration management (SCM) is an umbrella activity and is applied through the software process, because change can occur at any time and for any reason. In fact the first law of software engineering state, No matter where you are in the system lifecycle, the system will change andthe desire to change will persist through the life cycle SCM activities are develop to:

28 Identify Change Control Change Ensure that change is properly implemented Report change to other who may have an interest SCM is based of tracking and control activities that begin when a software project begins and terminates only when the software is taken out of operation the output of the software process is information that may be divided into three formal categories. 1. Computer programs (both source level and executable forms) 2. Document that describe the computer program (both technical practitioners and users) 3. Data (contained within the program or external) The items that comprise all information produced as part of the software process are collectively called a software configuration. In our software we have assured the clients that whatever changes are required will be done but in the case of any major changes after implementation, these changes will require changing the backend or font-end to quite a large extent. DESIGN ANALYSIS System design is the process of planning a new system to complement or altogether replace the old system. The purpose of the design phase is to move from the problem domain to solution domain. The design of the system is the critical aspect that affects the quality of the software. System design is also called the top level design. The design phase translates the logical aspects of the system into physical aspects of the system.

29 1. LOGICAL DESIGN: We know that a data flow diagram shows the logical flow of system development boundaries of the system. Logical design specifies the user needs in detail and usually terminates the information flow into and out of the system and the required process. Logical design describes the input, outputs and databases and procedural format that meet the user requirements. Input and output specifications are nothing but the composition of the system. The input screen has logically designed so that the user feels confident of the data entry. When tables are designed this method has been considered keeping the easy retrieval in view of faster query processing and quick decision taking process. 2. PHYSICAL DESIGN: It maps out details of the logical system, plans the system implementation and specifies any new hardware and software. System design is a highly creative process that can be greatly vacillated by the following: Strong problem definition Set of requirement for the new system It produces the working system by defining the specific design that tells programmers exactly what the software must do. In short it can state the physical design in the implementation of the logical design. Physical system design consist of the following steps 1. Design the physical system Specify input/output media Design the database and specify the back up procedure Design the physical information flow through the system and a physical design walk through.

30 2. Plan system implementation Prepare a conversion schedule and target date Determine the training procedure 3. Device a test and implementation plan and specify any new hardware or software. 4. Update the benefit cost, convert data and system constraints. System design involves the following steps: Input design Output design Database design INPUT DESIGN Input design is one of the most important phases of the system design. Input Design is the process where the input received in the system are planned and designed, so as to get necessary information from the user, eliminating the information which is not required. The aim of the input design is to ensure the maximum possible levels of accuracy and also ensures that the input is accessible that understood by the user. The objectives considered during input design are: Nature of input processing Flexibility and thoroughness of validation rules Handling of properties within the input documents. Careful design of the input also involves attention to error handling, controls, batching and validation procedures Output Design: Output design generally refers to the results and information that are generated by the system for many end-users. Output is the main reason for developing the system and the basis on

31 which they evaluate the usefulness of the application. Output design is a process that involves designing necessary outputs that have to be used by various according to requirements. When designing the output, system analyst must accomplish the following Determine the information to present. Decide whether to display, print, speak the information and select the output medium. Arrange the information in acceptable format. The output should be simple to read and interpret. We have emphasis the following thing in project: Information will never have to be manually edited. Provided easy navigation across information The timing of output is important The distribution of outputs must be sufficient to all relevant users. E-R Diagram: In software engineering, an Entity Relationship model (ER model for short) is an abstract way to describe a database. It usually starts with a relational database, which stores data in tables. Some of the data in these tables point to data in other tables for instance, your entry in the database could point to several entries for each of the phone numbers that are yours. The ER model would say that you are an entity, and each phone number is an entity, and the relationship between you and the phone numbers is has a phone number. Diagrams created to design these entities and relationships are called entity relationship diagrams or ER diagrams. The steps involved in creating an ERD are: Identify the entities. Determine all significant interactions. Analyze the nature of the interactions. Draw the ERD.

32 ERD symbols: Entity: An entity is an object or concept about which you want to store information. Key attribute: A key attribute is the unique, distinguishing characteristic of the entity. For example, an employee s social security number might be the employee s key attribute. Relationships: Relationships illustrate how two entities share information in the database structure. Pipeline: It indicates data flow-data in motion. It is a pipeline through which information flows. DATABASE ANALYSIS Normalization: Database normalization is the process of organizing the fields and tables of a relational database to minimize redundancy and dependency. Normalization usually involves dividing large tables into smaller (and less redundant) tables. This Point of Sale project is normalized upto second normal form because here every non key attribute totale dependent on the primary key.

33 Database Design: Table Structure

34 TESTING & DEBUGGING SYSTEM TESTING Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. Software testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs. TESTING OBJECTIVE Testing is a process of executing a program with the intend of finding an error A good test case is one that has high probability of finding an undiscovered error. A successful test is one that uncovers an as-yet undiscovered error TESTING PRINCIPLES All tests should be traceable to customer requirements Test should be planned long before testing begins The Pareto principle can be applied to software testing is 80% of all errors uncovered during testing will likely be traceable to 20% of all program modules Testing should begin in the small and progress toward testing in the large Exhaustive testing is not possible To be most effective, testing should be conducted by an independent third party TYPES OF TESTING Unit Testing Integration Testing Validation Testing Output Testing User Acceptance Testing

35 Unit Testing The individual components are tested independently to ensure their quality. Focus to uncover the errors in design and implementation. The various tests that are conducted during the unit test are described as below Module interface are tested for proper information flow in and out the program Local data are examined to ensure that integrity is maintained Boundary conditions are tested to ensure that the module operates properly at boundaries established to limit or restrict processing All the basis paths are tested for ensuring that all statements in the module have been executed only once All error handling paths should be tested. Integration Testing A group of dependent components are tested together to ensure their quality of their integration unit.the objective is to take unit tested components and build a program structure that has been dictated by software design The focus of integration testing is to uncover errors in: Design and construction of software architecture Integrated functions or operation at sub system level Interfaces and interactions between them Resource integration and / or environment integration Validation Testing The test is tested based on requirements to ensure that the desired product is obtained In validation testing the main function focus to uncover errors in System input / output System functions and information data System interfaces with external parts User interfaces

36 System behaviour and performance Software validation can be performed through a series of black box tests After performing the validation tests exists two conditions The function or performance characteristics are according to the specification and are accepted The requirement specifications are derived and the deficiency list is created. The deficiencies then can be resolved by establishing the proper communication with the customer Finally it ensures all the elements of software configuration are developed as per requirements. This is called configuration review or audit. Output Testing After performing validation testing, nest step is output testing of the proposed system, since no system could be usefulif it does not provide the required output in the specified format. Here the output format is considered in two ways. One is on the screen and another is printed format. The output format is corrected according to the user needs. Hence output testing does not result in any correction to the system. For example, we checked whether the particulars, date, logos, and addresses are printed in correct location or not by taking the hard copy. User Acceptance Testing This is a kind of testing conducted to ensure that the software works correctly in the user work environment. Test is conducted over a period of weeks or months Two types of acceptance testing are: 1. Alpha Test This test version of complete software is tested by the customer under the supervision of developer. This testing is performed at developer s site 2. Beta Test Testing in which version of software is tested by the customer without the developer being present and performed at customer s site.

37 SECURITY OF THE SYSTEM Physical Security The Point of Sale project is physical security is high as it is a web based application so there is a little chance of software crashing and data losing. Database Security A POS (Point-Of-Sale) system is a computer system typically used to manage the sales in retail stores. It includes hardware components such as a computer, a bar code scanner, a printer and also software to manage the operation of the store. Basically we know that most of the points of sale software s are desktop application but this point of sale is a web based application so that it has a special feature that we can create a centralized database for this point of sale that is it is possible to used multiple application from different location using only one database. Application Security This point of sale is a web based application so that it has a special feature that we can create a centralized database for this point of sale that is it is possible to used multiple application from different location using only one database without any damage of data.

38 CONCLUSION We have tried to create a user friendly, useful, easy to handle and most importantly platform independent application. The developed system is flexible, robust.this software provides the clarity in all its operation in terms of what, why, who, when, where, how and also reduces the cost of operations. The newly produced system provides facility which existing system were unable to provide such as remote access from anywhere, platform independence, easier maintenance etc. I am concluding that this project work has been completed successfully. This project proved good for me as it provided practical knowledge of not only J2EE and MS-SQL and some other technologies, but it also gave me a chance to get real time experience of developing project. OVERVIEW OF THE PROJECT The project WEB BASED POINT of SALE is developed in NETBEANS IDE with full JAVA support. So, It is a JAVA based application. Java coding has been done to build back end methods to execute the process of receiving and controlling data from web forms. This is needed to describe all the error handling code to help user, during execution time. This will be a new lucrative product in the software market which includes all the parameters of purchasing and selling starting form entry of customer details, contact with the admin. It also encompasses advanced search of with the product id(model name). Nowadays Java is a very popular and powerful language with tremendous capabilities. JSP is a server side scripting language which is gaining popularity day by day. We have taken it as a challenge and put them into proper perspective. A very large amount of commercial application and websites are developed using Java, JSP. Several key areas in commercial applications have been tried to address a set of issues that most commercial application developers require. Java and JSP are enjoyable language due to its visual environment with web enabled capability. It is much more than just a programming language. Nevertheless, the

39 language is a secondary consideration to the user interface. It offers a high degree of user interaction using the graphical elements that form the objects on the window the user sees. There is main drawback of existing software, they are not Platform Independent. But our software is platform Independent as this is a JAVA based online software. We have tried to create a user friendly, use full, easy to handle and most importantly platform independent software. The Project provides all types of information related to the sale of product, customer management, inventory management report generation etc.. The information are quickly available through an user friendly interface. An user can understand all booking option before going for any registration and booking option. MODULES DESCRIPTION This project consists of following modules: Admin Module Sale Module Report Generation Module Customers Module Inventory Module Edit Information Module Admin Module : This module consists of following sub-module Edit Company Info => Admin can Edit Company Information Change Password => Admin can change Login Password Manage Cart => Admin can manage unused cart

40 Sale Module : This module consists of following sub-modules New Sale => Make a new sale to customer Sale History => Get History of sale transaction for a period of time Best Seller/Worst Seller => Get Information about the customer who bought the most /least product for a period of time Report Generation Module In this module report can be generated about sales or any other information in PDF or Excel sheet Customers Module :This module consists of following sub-module New Customer => To add a new Customer Edit Customer => To edit existing customer s Information Customer List => To obtain existing customer s list Remove Customer => Remove customer from database Inventory Module :This module consists of following sub-module New Item/Category/Vendor=> To add new item/category/vendor Quantity/Price Adjustment => To adjust the quantity or price of a product Item/Category/Vendor list => To obtain the existing item/category/vendor list Qty./Cost Adjustment history=> To obtain the quantity/price adjustment history Edit Information Module :This module consists of following sub modules Edit customer Information

41 Edit Item details Edit Category/Vendor details Remove Item from data base Remove Category from data base Remove Vendor from data base LIMITATIONS: Modules and sub-modules are less integrated. Web pages and web services are inefficient and slow. Used database technologies are inefficient and slow. Have to be installed separately on each computer in the shop. If the application or the computer crashed, then the data will be lost POS System can be accessed only through the computer on which it is installed. Most of the POS system are not Platform Independent SCOPE FOR FUTURE ENHANCEMENT Every application has its own merits and demerits. This project has covered almost all the requirements. Further improvements can easily be done since it is based on Object Oriented Programming This system can be upgraded in the following ways: Databases and interfaces should be made for extra facilities (ex: purchase multiple products, products discounts, Due Balance, Accounts etc.). Reports on some other activities can be included using different time interval. Page design can be further improved using different functions of flash and Adobe Photoshop.

42 Project DFD:- Admin Part: ADMIN LOGIN Valid Login Invalid Login COMPANY DATABASE INVENTORY DATABASE CART MAKE NEW SALE ADD EDIT REMOVE VIEW VENDOR DATABASE CATEGORY DATABASE CUSTOMER DATABASE ADMIN ID Pswd LOGIN Valid Login Invalid Login COMPANY DATABASE MANAGE CART ALL CART DATABASE Make New Sale CART DATABASE Cart _Details Sales MAKE PAYMENT TRANSACTION CUSTOMER DELETION CUSTOMER DATABASE SALES DATABASE Details Customer_ Details

43 Company Part: ADMIN Company_ID Password LOGI N Valid Login Invalid Login COMPANY DATABASE GENERAT E INVOICE GENERAT E REPORT SALES DATABASE VIEW DATA HISTOR Y Company Part:- CUSTOMER PURCHASE ITEM CART Cart _Details MAKE PAYMENT Payment _Details SALES DATABASE

44 10.1 SOURCE CODE:- <%-- Document : index Created on : 15-May-2013, 11:57:17 Author : kalyanlayek --%> <%@page contenttype="text/html" pageencoding="utf-8"%> <!DOCTYPE html> <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <title>pos home</title> <link rel="stylesheet" type="text/css" href="css/style.css" /> <script type="text/javascript" src="js/pos.js"></script> <style type="text/css"> a{ color: #666; text-decoration:underline; } #login_box { background: url('images1/loginbox/login.png') no-repeat; font-family: Tahoma,Verdana,arial,sans-serif; font-size: 10pt; color: #666; width:210px; height:200px; padding:20px 0px 0px 20px; visibility: hidden; } </style>

45 </head> <% String n=request.getparameter("n"); if(n!=null) out.println("<font color='blue' size='10'>"+n+"</font>"); %> <body> <div id="top_menu"> <br /> </div> <td></td> </tr> <div id="main_content"> <table> <tr> <td><img src="images1/pos-logo.gif" width="289" height="130" border="0" /></td> <td> </td> <td> </td> </table> <img src="images1/gb.gif" width="980" height="5" border="0" /> <p><br> <tr> <table width=""> <td> <img src="images1/pp.jpg" width="350" height="310" border="0" /></td> <td> </td> <td> multi-user access. This is totally web-based, retail-management Point of Sale application.<br>it supports It is absolutely for you. Are you ready<br>to grow your business to hundreds of stores? With the help of POS<br>Anyware, we are confident that you can. <a href="" style="text-decoration: none; color: blue;">read more...</a>

46 <p><br> <img src="images1/yc1.jpg" width="100" height="80" onclick="make_visible_country();" /><p><br> <div id="h" style="visibility: hidden;"> <form action="registration.jsp" method="post"> <table> <tr> <td>select Country :</td> <td id="cmg"><img src="images1/country/india3.png" height="30"/></td> <td> <select name="c" id="c" onchange="return flag_chng();"> <option>india</option> <option>guyana</option> <option>sri Lanka</option> </select> </td> <td> </td> <td><input type="submit" value="next" /></td> </tr> </table> </form> </div> <p><br><br> </td> <td> </td> <td> <a style="text-decoration: none;" onclick="return make_visible_loginbox();"><img src="images1/ml.jpg" width="170" height="60"></a> <div id="login_box"> <small><img src="images1/loginbox/secure.gif" alt="secure login"><b> Member Login</b></small> <img src="images1/loginbox/close.gif" style="padding-left:25px;margin-top:-20px;" onclick="return close_loginbox();">

47 <div style="padding-left:10px;"> <form action="login_controller" method="post" style="margin-top:5px;" onsubmit="return login_check();"> <small>account id</small><br/> <input id="aid" name="account" size="16" style="width:150px;"><br/> <small>password</small><br/> <input id="p" type="password" size="16" name="password" style="width:150px;"><br/> <input type="submit" value="login"><br/><br> <small><ahref="public/trouble_logging_in.html">having trouble?</a></small> </form> </div> </div> <p><br></td> </tr> </table> <p><br <% String crmsg = request.getparameter("crmsg"); if (crmsg!= null) { out.println("<font color='green'><b>" + crmsg + "</b></font>"); } %> </div> </body> </html>

48 Registration Page:- <%-- Document : registration Created on : 15-May-2013, 12:02:05 Author : kalyanlayek --%> <%@page contenttype="text/html" pageencoding="utf-8"%> <!DOCTYPE html> <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <link rel="stylesheet" type="text/css" href="css/style.css" /> <script type="text/javascript" src="js/pos.js"></script> <style type="text/css"> a{ color: #666; text-decoration:underline; } #login_box { background: url('images1/loginbox/login.png') no-repeat; font-family: Tahoma,Verdana,arial,sans-serif; font-size: 10pt; color: #666; width:210px; height:200px; padding:20px 0px 0px 20px; visibility: hidden; }

49 </style> <link rel="stylesheet" type="text/css" href="css/style.css" /> <title>registration Page</title> <script type="text/javascript" src="js/registration.js"></script> <style type="text/css"> a{ color: #666; text-decoration:underline; } </style> <style type="text/css"> #overlay { width:100%; height:100%; float:left; background-color:#333333; position:absolute; left:0px; top:0px; z-index:201; } #popup { width:auto; height:auto; /*float:none;*/ background-color:#ffffff; position:absolute; left:15%; top:17%;

50 z-index:202; box-shadow: 15px 15px 25px black; } #regn{ padding-top: 20px; padding-bottom: 17px; padding-left: 20px; padding-right: 20px; } #regcomp{ font-size: 1.0em; font-weight: bold; color: blue; } #tn,#te,#ta,#tp,#trp{ font-family: Tahoma; font-size: 0.86em; font-weight: bold; color: grey; } #ne,#ee,#ae,#pe,#rep{ font-family: Tahoma; font-size: 0.84em; } #cross{

51 position: absolute; left: 98%; top: -5%; width: 35px; height: 35px; } </style> <script type="text/javascript" src="js/jquery.min.js"></script> <script type="text/javascript"> $(document).ready(function() { var wait; $('#overlay').hide(); $('#popup').hide(); $('#trigger1').click(function() { $('#overlay').show(); $('#overlay').fadeto(0, 0); $('#overlay').fadeto(1000, 0.50); $('#popup').show(); $('#popup').fadeto(0, 0); $('#popup').fadeto(1000, 1); }); $('#cross').click(function() { $('#overlay').hide(); $('#overlay').fadeto(0, 0); $('#overlay').fadeto(1000, 0.50);

52 $('#popup').hide(); $('#popup').fadeto(0, 0); $('#popup').fadeto(1000, 1); }); }); </script> </head> <body> <div id="top_menu"> <br /> </div> <table><tr> <div id="main_content"> <td><img src="images1/pos-logo.gif" width="289" height="130" border="0" /></td> <td> </td> </tr> </table> <img src="images1/gb.gif" width="980" height="5" border="0" /> <p><br> <table width=""> <tr> <td> <img src="images1/pp.jpg" width="350" height="310" border="0" /></td> <td> </td> <td> <div id="overlay"></div> This is totally web-based, retail-management Point of Sale application.<br>it supports multi-user access. It is absolutely for you. Are you ready<br>to grow your business to hundreds of stores? With the help of POS<br>Anyware, we are confident that you can. <a href="" style="text-decoration: none; color: blue;">read more...</a> <p><br>