Professional Documents
Culture Documents
Full
Full
INTRODUCTION
1.1ABOUT THE PROJECT
The project entitled Departmental Store Management System. The project system is a systematic approach maintaining the following about the customer details, product details, supplier details, sales and purchase transactions, sales and purchase transactions and billing details and it operates. In the computerized Departmental Store Management System, the transactions are handled daily. As the transaction increase, the slaws also increase. The organization was not able to take immediate actions or steps to reduce the slaws. The main objective of this system is to provide an excellent management of all types to sales and stock. This system is used to manage the company information. Also, this system is used to know the current status of the sales, stock and purchase details. All Data Pertaining to customers and products are to be stored and maintained. Generally most of the information in master files remains constant over a period of time. The maintenance module should provide for addition, modification, viewing and deletion of customer, Buyer, employee and product information In order to provide better service to the customers and to improve the sales performance they classify the customers into three categories. Any stranger who step into the Computer shop are ordinary customer and the customer who buys regularly and the customer who buy and sell are coming under the reseller category they do not maintain any details about the ordinary customers, but maintain details about the resellers and regular customers Sales Information: When products are sold to the customers and resellers, cash bill, invoice has to be made to record the transaction. The details about the invoices are stored in the invoice book. When a sale is made, the quantity in the stock has to be updated for the corresponding item in the invoice. Report Generation is an integral part of any information systems reports provide the processed information and highlight areas where controls need to be applied. The successful implementation of any computerized information processing system depends on the effectiveness. In the computerized Departmental Store Management System , the transactions are handled daily. As the transaction increase, the slaws also increase. The organization was not able to take immediate actions or steps to reduce the slaws.
1
1.2
HARDWARE SPCIFICATION
The configuration given below is the hardware for the system development. Processor RAM Hard Disk Floppy Drive Cache Memory Monitor Mouse Keyboard : : : : : : : : PENTIUM IV 2.66 GHz 256 MB RAM 80 GB 1.44 MB 512 MB Zenith 15 COLOR MONITOR Zenith 3 button optical mouse 110 Keys (Zenith)
1.3
SOFTWARE SPECIFICATION The configuration given below is the software handled for the system development. Operating system Front- End Back-End : : : Windows XP Visual Basic 6.0 MS Access
Visual Basic Edition Visual Basic software comes in three editions: Learning Editions: which includes the Visual Basic development environment and use of standard tools to develop applications Professional Edition: is used by computer professionals as it supports the tools to develop ActiveX and Internet controls Enterprise Edition: which includes all the features of professional edition well as Microsoft Visual Source safe for source code control and Automation and Component manager Visual Basic 6.0 Version 6.0 of Visual Basic is specially designed to utilize the internet. It comes with several controls that allow user to create web-based application called ActiveX executables. Additional features 1. OLE Automation is an industrial standard technology that application uses to expose their OLE objects to development tools, macro language, and other application that support OLE Automation. 2. To distinguish Visual Basic project files from source files used by other development tools, the file extension. VBP used. 3. Object Browser is used for hierarchal display of classes, properties, and methods available to the application. 4. The 32-bit version of Visual Basic supports long files names. 5. programmers can define classes, which are contained in Visual Basic class module. Class module is the one, which contains the definition of class; its properties and definition. 6. Enhanced Object Browser, Auto list numbers features and auto quick information feature is also provided. 7. ActiveX is a new buzzword that refers to technologies that previously may have been associated with the term OLE. ActiveX is Microsofts name for technologies that are based on the Component Object Model (COM). 8. Visual Basics internet capability allows one to create powerful applications hosted by standard browser.
3
Visual Basic as a front-end tool Visual Basic is Windows application development platform with a strong combination of a front-end tool and programming language .The ease of the visual approach coupled with the power of programming and the straightforward BASIC language syntax makes programming easy. By using visual Basic, the programmer can create powerful, full feature application that exploit the key feature of MS Windows, including Multiple Document Interface (MDI) , Object Linking and Embedding (OLE), Dynamic Data Exchange (DDE), graphics and many more. Visual Basic can be extended by adding custom controls and by calling procedure in Dynamic Link Libraries (DLLs). Using MDI in Visual Basic: MDI stands for Multiple Document Interface. Visual Basic application can have only one MDI form. A child form is an ordinary form that has its MDI-Child property set to true. The application can include MDI-Child forms. At run time, child forms are displayed within the internal areas of MDI form. When a child form is minimized, its icon appears on the MDI form instead of appearing on the desktop. Element of Visual Basic Visual Basic interface consists of the following elements. Toolbar Provides quick access to commonly used commands in the programming environment. An icon in the toolbar can be clicked to carry out the action represented by that icon. Toolbox Provides as set of tools that can be used at design time to place controls on a form. Menu bar Displays the commands that can be used to build an application. Form Serves as a window that can be used to customize the interface of an application. Controls, graphics and pictures can be added to a from to create the Visual effect required by the user. Project Window Lists the dow form, code, modules and custom control files that make up the current project. A project is the collection of files that a programmer uses to build up his application.
4
Total number of controls The maximum number of controls allowed on a single form up to 254. The limit control array index is 0 to 32,767 on all versions. MS-ACCESS (Back-End Tool) Ms-access is a powerful multi user relational database managements system developed by Microsoft used to implement large amount of information with minimum memory allocation and auto make repetitive task, such as maintaining and generating invoice. Data in ms-access is organized in the form of tables within a table records are arranged to a common reference value known as primary key. FEATURE OF MS-ACCESS Access is window based application and therefore it has an interface similar to windows. Access maintains a single disk file for a database and all its associated objects. Access lets you import from or export to foxpro, oracle and other data form. Access wizard is a vitality that helps to perform complex task by guiding through out the access. Access contains nearly hundred. Wizards to design database application, tables, forms, reports, graphs, mailing labels, control and properties. ADVANTAGES OF MS ACCESS: Less time consumption and quick response. Access has a friendly environment. Microsoft access is not needed for keeping register for recording.
DISADVANTAGES OF MS ACCESS: The data security is very less. The database would not be opened. No availability of temporary tables.
2. SYSTEM ANALYSIS
System analysis is the process of gathering and interpreting facts, diagnosing problems, and using the information or recommend improvements to the system. This is the job of the system analyst. In the case of systems analysis, the substance is the business system under investigation and the parts are the various sub-systems, which work together to support the business. Before designing a computer system, which will satisfy the information requirements of a company, it is important that the nature of the business and the way it currently operates are clearly understood. The detailed examination will then provide the design teams with the specific data they require in order to ensure that all the clients requirements are fully met. The investigation or study conducted during the analysis phase may Build on the results of an initial feasibility study and will result in the Production of a document, which specifies the requirements for a new system. This document is usually called the requirements specification or functional specification, and it is also described as a target document because it establishes goals for the rest of the project.
System is not independent entities but exists in an environment. There are many relationships between a system and its environment and some of these are indirect rather than the direct relationships. The functioning of a system can be affected by changes in the system environment in ways that can be very difficult to predict. As in the physical environment systems are also situated in an organizational environment. In this organizational is not properly understood. Systems may be inappropriate and rejected by users and organizational managers. System analysis aims in providing a scientific approach for solving the problems created by complex situations. The system analysis helps in finding out the various ways in which the system can be developed and also helps mainly in making beneficial decisions in an organization. So, System analysis is mainly needed for decision making and planning in an organization.
Large volumes of data can be stored easily. Maintenance of file is flexible. Records stored are updated easily. Reports can be generated with ease. Accurate calculations are made. Less manpower required. Accuracy and error free transaction process. Neat and clear representation of report. User satisfaction at high level. Efficient service. Reduce data redundancy. Any form of reports can be produced instantaneously. Updating is very easy. Accurate information will be provided when the information is needed. 2.3.2 OBJECTIVE OF THE PROPOSED SYSTEM . The Data redundancy is eliminated Validation checks are performed at instances. Data Integrity is maintained. Hundred percent Client Server techniques can be achieved. Providing table level locking, Row level locking. Providing user friendly entry screens to the end users as GUI based. Reliability, Portability and Flexibility are the main advantages. Even a non Computer professional can also handle.
3. SYSTEM DESIGN
3.1 FILE SPECIFICATION
A database is defined as a collection of data items organized in such a way that the specific data or record can be retrieved and processed when required. The proposed system has following tables. Table Name Purpose Primary key NAME Suppliercode Suppliername Supplieradd Email_id Urladd Latpurdate OpenningBal Table Name Purpose Primary Key NAME Cust_Code Cust_Name Cust_Add CEmail_id CLatpurdate COpenningBal : : : Supplier To store details of suppliers. Suppliercode SIZE FIELD DESCRIPTION 5 Supplier Code 20 Supplier Name 50 Supplier Address 20 Supplier Email ID 20 URL address 8 Latest Purchase Date 8,2 Openning Balance CONSTRAINTS Primary Key Not Null Not Null Not Null Not Null Not Null Not Null
Customers To store the details of customers Cust_code SIZE 5 20 50 20 8 8,2 DESCRIPTION Customer Code Customer Name Customer Address Customer Email ID Latest Purchase Date Openning Balance CONSTRAINTS Primary Key Not Null Not Null Not Null Not Null Not Null
: : : :
CustomerOrders To store the details about the customer orders Order_Code Cust_Code
9
NAME Order_Code Order_Date Cust_Code Goods_code Req_Qty Want_Date Table Name Purpose Primary Key NAME Sal_Code Bill_No Bill_Date Order_Code Goods_Price SQty Free Service_Charge Del_Charge Tax Total CusPaid Sal_Bal
SIZE 5 8 5 5 4 8
DESCRIPTION Order Code Order Date Customer Code Goods Code Required Quantity Wanted Date
CONSTRAINTS Primary Key Not Null Freign Key Foreign Key Not Null Not Null
SalesDetails To store the details about sales details Sal_Code TYPE Text Number Date Text Number Number Text Number Number Number Number Number Number SIZE 5 5 8 5 10,2 5 20 6,2 6,2 8,2 10,2 10,2 10,2 DESCRIPTION Sales Code Bill Number Bill Date Order Code Goods Price Sales Quantity Free Product Service Charges Delivery Charges Sales Tax Total Value Customer Paid Amount Customer Balance CONSTRAINTS Primary Key Not Null Not Null Foreign Key Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null
Table Name Purpose Primary Key NAME SRet_Code SRet_Date Sal_Code R_Qty Remark Value
: : :
SalesReturn To store the details about the details of sales return SRet_Code TYPE Text Date Text Number Text Number SIZE 5 8 5 4 20 10,2 DESCRIPTION Return Code Return Date Sales Code Return Quantity Goods Remarks Total value of goods CONSTRAINTS Primary Key Not Null Foreign Key Not Null Not Null Not Null
10
Table Name Purpose Primary Key Foreign Key NAME Stock_id Pur_Code Current_Stock Total_Price
: : : :
Stock_Details To store the information about the stock details Stock_id. Pur_Code TYPE Text Text Number Number SIZE 5 5 4 10,2 DESCRIPTION Stock Code Purchase Code Available Stock Total Price of Stock CONSTRAINTS Primary Key Foreign Key Not Null Not Null
Supplier master files, store the details of the supplier like address, phone no and email by givings separate code for each member. ITEM DETAILS Item master list is used to provide some details like code number for all item, item name, and type of the item and unit price. Each item should be ordered when the stock in hand is below the unit price level. PURCHASE REQUISITIONS This form is used to enter the requisition details like refno, date, item code, item name, unit type, rate, required quantity, total value and remarks. The validations are made in the form, so that negative values are not accepted. TRANSACTION DETAILS It includes a) Purchase Details b) Store Details. PURCHASE DETAILS In purchase entry we maintain the order no, supplier name and items with quality and rate.
STORE DETAILS Materials are important part of finished production. So it is desirable to have efficient and well-equipped stores department to exercise an effective material control. In stores we maintain the issue no, data, item name, etc., REPORTS The last module is report generation. This module produces the daily transaction report and prints the up to date stores details. Depending on the input give, various reports are generated like: supplier product purchase requisition
12
tested using those test data. Errors are found and corrected by using the following testing steps and corrections are recorded for future reference. Thus a series of testing is performed on the system before it is ready for implementation. Testing is applied at different levels in the development lifecycle. Each level of testing done is different in nature and has different objectives at each level. The focus of all levels of testing is to find errors, but different types of errors are looked for at each level. The quality of system is confirmed by the thoroughness of its testing. Duration and cost of testing and debugging is a significant fraction of the system development cycle and hence influences overall productivity during the development. In this phase, the errors in the programs or modules are localized and modifications are done to eliminate them. The testing makes a logical assumption that all parts of the system work efficiently and the goal is achieved. VERIFICATION TESTING The purpose of the requirement phase is to ensure the users needs are properly understood before translating into design. Requirements are difficult to develop because it is hard to distinguish needs from wants.
VALIDATION TESTING Validation is achieved through a series of testing that demonstrate conformity with requirements. Both the plan and the procedures are designed to ensure that all the functional requirements are satisfied. All behavioral characteristics are achieved. All performance requirements are attained.
BLACK-BOX TESTING Black-box testing is an approach to testing where the tests are derived from the program or component specification. The system is a block box whose behavior can only be determined by studying its inputs and the related outputs. Another name for this is
14
functional testing because the tester is only concerned with the functionality and not the implementation of the software. The following methods are commonly used: The following methods are commonly used: Equivalence partitioning Boundary-value analysis Error guessing.
Equivalence partitioning Equivalence partitioning is a systematic process that identifies, on the basis of whatever information is available, a set of interesting classes of input conditions to be tested, where each class is representative of a large, set of other possible tests. Error guessing Error guessing is an ad hoc approach, based on intuition and experience, to identify tests that are considered likely to expose errors. The basic idea is to make a list of possible errors or error-prone situations and then develop tests based on the list. Some items to try are Empty or null lists/ strings Zero instances/ occurrences Blanks or null characters in strings Negative numbers. Testing for pixel value is zero or not.
WHITE-BOX TESTING When testing is done knowing the internal workings of a product, tests can be conducted to ensure that internal operations are performed according to specifications and all internal components are adequately exercised. This type of testing is called as white-box testing or glass-box testing. White-box testing of software is predicated on close examination of procedural detail. Providing test cases that exercise specific sets of conditions and/or loops tests logical paths
15
through the software. The status of the program may be examined at various points to determine if the expected or asserted status corresponds to the actual status. White box test is done to Guarantee that all independent paths within a module have been exercised at least once Exercise all logical decisions on their true or false sides Execute all loops at their boundaries and within their operational bounds. Exercise internal data structure to assure their validity. Testing was done for the grouping row and column pixels.
There are some basic forms of logic coverage Statement coverage: Each statement is executed at least once. Decision coverage: Each statement is executed at least once; each decision takes on all possible outcomes at least once. Condition coverage: Each statement is executed at least once; each condition in a decision takes on all possible outcomes at least once. Decision/condition coverage: Each statement is executed at least once; each decision takes on all possible outcomes at least once; each condition in a decision takes on all possible outcomes at least once; Multiple/condition coverage: Each statement is executed at least once; all possible combinations of condition outcomes in each decision occur at least once. Whether correct statistical values are getting from the given grouped rows, grouped pixels. UNIT TESTING Unit testing focuses on the verification effort of the smallest unit of design module. Attention is diverted to individual modules, independently to locate errors. This has enabled the detection of errors in coding and logic. The various modules of the system are tested in unit testing method. Using the detailed description as a guide, important control parts are tested to uncover errors within the boundary of the module. The relative complexity of tests and the error detected as a result is limited by the constrained scope established for unit
16
testing. This test focuses on each module individually, ensuring that it functions properly as a unit, and hence the name Unit Testing. INTEGRATION TESTING The program as a whole is integrated into a single component and checked with test data. This is to check that the whole program works together correctly. The various modules are integrated first. Then the system is tested as a whole. The behavior of each module with another is identified in this testing. Any misbehavior will lead to dangerous problems or errors in the system. All these problems can be filtered off using this testing. We combined all the modules into a single component and tested for integrity. We found the crude form of our project is meeting the basic requirements like policy-setting according to user, host and time constraints. We integrated the different components we developed like the Server-Client Chat, Policy setting algorithm on the Gateway (Bluetooth Adaptors), System-System File Sharing Process as of Server-Client File Sharing System. We found our primary version worked without any bug .We also checked our software functioning under different environments. We found it working without any problems. i. ii. Bottom-up Integration: low-level components are integrated and tested before the higher-level components have been developed. Top-down Integration: The high-level components of a system are integrated and tested before their design and implementing has been completed. The steps in top-down integration are: Begin with the top module in the execution hierarchy. Stub modules are produced, and some may require multiple versions. Stubs are often more complicated than they first appear. The next module to be tested is any module with at least one previously tested super ordinate module. After a module has been tested, an actual module and its required stubs replace one of its stubs. Here grouping row and column module was integrated with the statistical representation module A classic system-testing problem is finger pointing.
17
This occurs when a defeat is uncovered, and one system element developer blames another for the problem.
Rather than indulging in such nonsense, the software engineer should anticipate potential interfacing problems along with the below specified points. 1. Design error-handling paths that test all information coming from other elements of the system. 2. Conduct a series of tests that simulate bad data or other potential errors at the software interface. 3. Record the results of tests to use evidence if finger pointing occurs. 4. Participate in the planning and design of system testes to ensure that software is adequately tested.
18
19
5.2 SUGGESTIONS The system makes the possibilities smoothen to the manual system and this software with volumes of input/output data of all possible validations and results have been found to be excellent. The design of this Package can be extended to any extent in the case of inclusion or number of facilities with the system.
20
BIBLIOGRAPHY BOOKS:
1. Stephen Walther, VB Programming, Weily Publications, First Edition, 2003. 2. Dan Hurkwitz, Jesse Liberty, Programming in Visual Basic,second Edition, 2008. 3. Robert Hottmalk MS Access, Galgotia Publications, First Edition 2001. 4. Roger S.Pressman, Software Engineering, Tata McGraw Hill Publications, first Edition 1998. 6. Ragu Ramakrishnan , Johannes Gehrke, Database Management System third Edition. 7. Elias M.Awad, System Analysis And Design Tata Mc Graw Hill, third Edition 1997. URL REFERENCE http://www.google.co.in http://www.vbtutor.net/ http://msdn.microsoft.com/en-us/vbasic/ms789056 http://office.microsoft.com/en-us/access/ http://www.softwaretestinghelp.com/
21