Jordan University

POINT TECH
Your business your life

2007
1

Done by: (Mohamed aiham) Akram AlZubi

KING ABDALLAH || SCHOOL FOR INFORMATION TECHNOLOGY COMPUTER INFORMATION SYSTEM DEPARTMENT

ACKNOWLEGMENT 3

The work on this project has been an inspiring, often exciting, sometimes challenging, but always interesting experience. It has been made possible by many other people, who have supported us. We are very grateful to all our teachers in king Abdullah the second school for information technology who taught us, especially for our supervisor Dr. Bassam Hammou who accompanied us from the first years in the university and supported us with his encouragement and many fruitful discussions. We'd like to present our project and all of these years of hard work to our precious dear parents for their continuous support and encouragement through these years. Thank you all. Table of contents
4

Table of Contents
Chapter One: introduction................................................................................7 introduction...................................................................................................8

Chapter Two: Planning Phase.........................................................................14

Objectives.........................................................................................................................9 Contact Pearson .............................................................................................................10 Business Profile .............................................................................................................10 Current System Discretion ............................................................................................11 System history ...............................................................................................................11 Current system used.......................................................................................................12 Problem Definition ........................................................................................................13 System Requirements.....................................................................................................15 New system Proposal.....................................................................................................17 System stakeholder........................................................................................................19 Strategic Planning..........................................................................................................20 SWOT analysis .........................................................................................................20 Feasibility study ............................................................................................................20 Implementation Plane....................................................................................................33

Chapter Three: System Analysis Phase..........................................................34

Chapter four: Design Phase............................................................................47

Information Gathering...................................................................................................35 Requirements Explanation............................................................................................. 36 Process Modeling...........................................................................................................37 Component Analysis......................................................................................................42 Component description..................................................................................................45 User Analysis.................................................................................................................46 Database Design.............................................................................................................48 Structural Design ..........................................................................................................50 System Design................................................................................................................52 User Interface Design....................................................................................................53 Software and Development Tools..................................................................................56
Chapter five: Implementation Phase..............................................................70 Implementation Methodology.......................................................................71 User Manual...................................................................................................74

Conclusion .......................................................................................................................75 References.........................................................................................................................75

ABSTRACT
5

The supermarket point-of-sale system project transforms a Pc into cash Register, which ensures that selling process will be easier than before by getting advantages of computer's capabilities in fast processing, reliability, maintainability and efficiency, and by using our integrated, user-friendly GUI and reliable POS software package, Also our system makes it easier to track the daily inventory transactions in addition to the special provided services for the management to react and make decisions more efficiently in different situations. Mainly, the system is responsible for three functional parts; each part has its own role in the system and provides different services. All these parts are integrated with the system database, which ensures the feasibility of the system

CHAPTER ONE: INTRODUCTION

CONTENTS: -INTRODUCTION -OBJECTIVES -ACADEMIC OBJECTIVES -SYSTEM OBJECTIVES -CONTACT PERSON -BUSINESS PROFILE -over view -VISION -MISSION STATEMENT -VALUES -CURRENT SYSTEM DESCRIPTION -SYSTEM HISTORY -CURRENT USED SYSTEM -PROBLEM DIFINITION

1.1 INTRODUCTION
7

In the current time, the success of any company depends on how much the customer is satisfied by their services, for example, a customer that has to wait 1 hour every time he wants to withdraw an amount of money from his banking account will not tolerate with this service and he will change the bank he deals with, losing customers will eventually kill the business process in that bank and it will be closed. Competition in the current world is a widely used term, there are many Companies that provide the same services or products that are competing for customers, the best company from the customer perspective is the company that best satisfies his needs, and here is the place where Computerized Systems role appear. Being in an Information Technology age, all our work depends on computer and its programs, so companies and people in different majors interact with the computer and software directly and indirectly in their life. Services provided by computer have not only impact on the speed, effort and efficiency of the business process but also have impact on the success of this business, customer confidence and reputation of that company. In order to develop a system that is capable of satisfying the point of sale process needs and improve the current process, we had to analyze the work process by interviews (1) and old system observing, then after collecting enough information we tried to develop (2) a computerized system that can satisfy the functional and non functional requirements of the POS business process. 1.2 OBJECTIVES In this new system we are going to enhance previous systems that dont provide sufficient information for customer nor managers plus adding additional applications to complete what has been missed from previous versions. 1.2.1 ACADEMIC OBJECTIVES:

1. 2.

3. 4.

To complete the graduation project course with the best marks. To live at the real systems life from A-Z the thing that will make from us real Information Technology graduates that could success at all the job market fields. To plan, analyze, design, and implement a full creative system. To implement a new of kind system, that will be creative, useful, and impressive system.

1.2.2 SYSTEM OBJECTIVES: 1. To handle the sales at point-of-sales efficiently and with less probability of errors occurrence. 2. To ensure that customer service will be quicker than before. 3. To ensure the ease of use of the system by the employees and fast adaptation Of the system. 4. To have a complete and consistent recording of all inventory transactions and keeping the inventory status up-to-date. 5. To provide the management with a better administrating tool. 6. To avoid the problems found in the previous installed system. Some of these difficulties: a. The inability to handle wrong input if any. b. The inability to handle long item description. If such description had been found, the system was stuck and could not complete its operation. c. Wrong calculation of totals in some cases. 7. Merging Varity of subsystems to create powerful and multipurpose system such as: A. monitoring system. B. privilege system C. sound box

1.3 CONTACT PERSON

During the analysis phase, we contacted Mr.Imad Mustafa (Sales Development Manager) in AL-Alameyyah Rosters, and upon that we were provided with all the information needed about the mechanism they use in their company. Mr.Imad and we discussed the mechanism in the roster, and what are the requirements for creating good working criteria in order of reaching their goal. Mr.Imad clarified the mechanism of the service provided for the customer, manual selling procedures...etc. For further information, please dont hesitate to contact Mr.Imad Mustafa E-Mail: (imad3@hotmail.com) Tel: (0795820828) 1.4 BUSSINESS PROFILE 1. Over view Since the 60s, AL-Alameyyah Rosters started originally from Kuwait; and started to get a bigger chain in other countries. An important mobilization period for AL-Alameyyeh was opening a branch here in Jordan, although there were a lot of competitive companies, AlAlameyyeh Rosters were in the front always; there were always something makes AL-ALameyyeh Rosters more unique than the others. 2. Vision of AL-Alameyyah Rosters Despite of all the others competitive in the Rosters Market, Al-Alameyyah rosters is looking forward to be one of the best Rosters in the area. To reach this goal, you need to be efficient and effective, and your products must be qualified to get the ultimate satisfaction from the customers. As known, customers service is a very important factor to reach that goal, also; dealing with suppliers must be flexible and reliable. As Mr.Imad believe; these are the most important factors must be taken care of in this work environment.

10

3. Mission Statement In order to reach our goal, we need to push our efforts through the overall contribution by the management, staff and customers. Our mission is to keep our products always in the front with the best quality, best customer service, maintain the quality and keep on developing the quality of our products and not to limit our development ways for our products, but keep on trying to be on the front always.

1.5 Current system description While using the current system, we faced a lot of problems showed up because some bad data processing factors in the system. The current system was dependent on human mathematically concepts and using traditional ways to make transactions, it was not flexible or reliable because it couldnt interact with the customer needs and the management needs. Each simple detail was done manually (Using pen and paper). We needed to computerize the system to make our work easier and more accurate and more efficient. Computerizing the system will solve a lot of problems we are facing in the mean time, for example; if we need to make any kind of simple report, it must be done manually, so our time will be wasted on doing some simple things that can be done in seconds using a computerized system.

1.5.1 System History Back in the 60's the technology were not here to help us managing our work easier, every transaction were being done manually, we used to use a traditional register and also using a calculator, and also we used to keep a hand written record of the sold products. The defective part of this system was the time we used to spent on making a report, and the hand written records that might be lost for any reason,
11

and there were no receipt copy for the customer to review. Now, with the technology available in our hands, we can make things easier for ourselves, a computerized system will do all the calculations and reports in seconds. The new system we invented as we see, solved a lot of problems we complained from, of course we cannot develop a perfect system for the Roster but we tried as hard as we can to make it out of bugs and serve the roster in the best way. 1.5.2 Current use system In any big corporation in these days you will find a point of sale system, but when you let a General designed system take care of your job, it may not fulfill your requirements or needs, so we looked forward to develop a customized system depending on our exact requirements in order to meet our needs. 1.6 Problem definition To improve our work, we cannot keep on using the old system. The way of processing data should be faster and more efficient in order to reach our goal. Dealing with transactions manually is an old fashion way, it must be more moderate using the technology in the 21 century. Dealing with things manually will make our progress slower and less efficient, Using a new technique is the most effective way to develop our system. The old system were static and dealing only with inventory. We need the system to be more interactive with the customers by adding new features that will optimize the customer to be more satisfied and happy about the services provided. We will summarize the problems throw this points: 1. System has some difficulties in ordering some discounts for customers. 2. The POS system is suppurated from monitoring system which has difficulties to manage in both. 3. In current systems doesnt support perfect performance 4. In older systems the mechanism is not flexible so only static applications can be used.
12

5. Old systems provide management level with hard copy of statistical sold items 6. Old systems doesnt provide privileges for managers to choose whom to work on specific level 7. Current systems dont provide motion detectors for thieves. And here is a graphical representation for the main problems using the fishbone diagram, figure (2) shows the non efficient system problem.
inventory priviliges

Non connected

Low limits

Non efficient system

static

low

usablity

monitoring

Figure1: for the non- efficient system problem.

CHAPTER TWO: PLANNING PHASE

CONTENTS: -SYSTEM REQUIRMENTS. -FUNCTIONAL REQUIRMENTS. -NON FUNCTIONAL REQUIRMENTS. -NEW SYSTEM PROPOSAL 1. SYSTEM DESCRIPTION.
13

2. SCOPE OF THE SYSTEM. 3. PREPLANNING AND WORKING TEAM. -SYSTEM STOCK HOLDERS. -STRATIGIC PLANNING. -SWOT ANALYSIS 1. STRENGTHS. 2. WEAKNESSES. 3. OPPORTUNITIES. 4. THREATS -FEASIBILITY STUDY 1- ECONOMIC. 2- OPERATIONAL. 3- TECHNICAL. 4- SCHEDULE. -EVALUATE FESIBILITY. -ESTIMATE PROJECT TIME. -IMPLEMENTATION TIME.

2.1System requirements At this section and after the full understanding for the problems that is being faced by the employees, and after collecting the some additional information about some functions that is liked to be added to the system, we will now list the system requirements, divided as usual to functional and non-functional requirements, to then make it easier in the planning, analysis and design to mach well between the target system and the really implemented system, that will help us to know the percentage of success, and as usual system requirements are divided into two parts, the functional and the nonfunctional requirements.

14

2.1.1 Functional requirements: R1. Show detailed information about each item such as: item name, price, taxes and quantity purchased. R2. Enables the cashier to search for any item that the customer asks for and show its availability and storage place. R3. Allow the cashier to cancel the order in case the customer cancelled the hole buying process. R4. It stores the date and time of each sale on the printed invoice along with the name of the cashier who sold the items. R5. It enables the cashier to open an account for the customer upon request. R6.It handles every payment method in different way.

R7. Record new items which enter the inventory and

stores all its available information and storage conditions. R8. Generates a list of needed item(s) purchases when a defined threshold for that item is reached. R9. Record suppliers' information such as name, phone, address etc. R10.Request daily sales and purchases reports. R11. Request daily report that shows the total amount of cash sales, total amount of credit card sales and the total amount of sales made on account. R12.Gives the manager the ability to print hard copy of any information needed. R13.Search for any invoices and retrieves it. R14.Classify items classes. R15.providing monitoring system that monitors the hall store and cameras for cashiers R16. Adding a waiting list in cashier system for customer that doesnt have current payment. R17. Offering a discount system for customers that buys from store more than a limit or specified limit. R18. Offering a report system that alarm for manager if a products is close to expiring date.

15

R19. Providing a report that shows all the transactions that has been sold or the transaction that has been bought. R20.showing all the sold items for a same cashier in specific time R21. Representing what items have been sold within date. R22. How many cash has been sold by cashier within date. R23. Providing customer an ability to retrain Items which he had sold. R24. Providing manger and report which describe the time of clock in and out of employee. R25. manger has ability to control ways that employees use to access system either by user name and password or his magnetic card. R26. manger can block any access on system. R27. System has a mechanism to print reports. R28. system can print computerized formal invoices. R29. storing process in inventory can be cabinets and shelf. 2.1.2 Nonfunctional Usability: An easy to learn and implement with an easy to use and learn interface. and using the system thro the hardware made it easier such as: 1. touch screens. 2. bar code reader. 3. magnetic card reader. Error handling for any wrong inputs and inconsistency. High performance software and fast response. Security: only authorized employees have access on the system. Reliability: saves data in case of unexpected shutdown. Robustness: simple and fast restart incase of unexpected shutdown. Maintainability: ability to be updated when needed.

2.2 New system proposal

16

After understanding the problems at the current system, and seeing the ultimate need for a new system, and after knowing the requirements needed at this new system, we are now ready to propose a system that solves these problems and satisfies all the requirements. This section contains three sections, the new system description and the scope we will be working at, also it contains an essential draft for how we can implement such a system.
2.2.1 System description:

As mentioned before, our system will add many new interactive features for the customers. Our system is clustered into three subsystems, filing, editing and reporting. First of all we will talk about the filing cluster. The filing system takes care of organizing the content provided to the system like, adding a new customer record, employee recordetc. Also the filing system takes care of inventory, new items and suppliers, so its not just a sale system which take care of only selling stuff, Second of all, the Editing system , its deals with an overall transactions and processing stages in order to create and organize content like editing an invoice or editing an item in some procedures, also when the supplier wants to update the inventory records, the editing system handles it etc. Third of all, Reports system; a collection of information that is provided by processing the data provided to the filing system and the editing system which can serve the management issues in order to keep track of every simple detail in the company. As a plug-in, we provided also some control features for the management and the staff for technical procedures decision support. The last thing in this part is the Point Of Sale system (POS), this feature helps us dealing with the sales invoices. In figure 2 shows the block diagram and the relationship followed by small data dictionary for the block diagram.

17

Figure 2:block diagram

Table 1:data dictionary

2.2.2 Scope of the system This system is designed for a targeted sector of people, like Rosters, Supermarketsetc. Before making a decision of whether this system is applicable or not, we must consider the target that the system serves, as an example; we cannot use this system in any drug store. Generally this system is designed for a medium volume of organizations.

18

2.2.3 Preplanning and Working team Our system is consisted of a System Analyst, Designer and Developer. The system analyst takes care of the mechanism of our invented system. Generally the system analyst gathers information about the procedures considered in the system, and the requirements to invent a new system. The Designer uses some techniques for producing a well visualized interface, he used Adobe Photoshop and some illustrators and Macromedia Flash for producing animations. The Developer part is to produce the code for doing these procedures as well , he used some high techniques and algorithms and some definitions to produce a professional system without bugs or errors.

2.3 System Stakeholders:

The point of sale system interacts mainly with two categories of Stakeholders: A. Inside the system stakeholders. 1. Employees: Cashiers, inventory manager. 2. Manager. B. Outside the system stakeholders. 1. Customers. 2. Suppliers. Here in figure 3 shows the system stock holder.

19

Figure 3 : system stock holder

2.4 Strategic planning The main strategic purpose for producing this system is to produce a simple reliable system and reach the goals of POS and inventory stuff. And as much as we can we tried to gather all the information needed for the organization to improve the efficiency of our work and help the management reach the ultimate control provided to manage their efforts. And this system is a dynamic system by providing some side tools like security cameras and integrating all the features in the system to work together in an effective and efficient way.

20

2.5 SWOT Analysis Here at this section we will discuss the main system evaluation aspects, we will see the points of strength, the points of weaknesses, the opportunities, and the threats we have and we might face while building and after we finish our system, we will discuss each aspect apart and with details. 2.5.1 Strengths: 1. Variety of products. 2. Good quality of products. 3. Good reputation 2.5.2 Weaknesses: 1. Time and efforts consuming. 2. Limited use of system advantages. 3. A lot of papers used. 4. there is no specified design for the reports, its Generalized and in a formal way. 5. Inability to reach every customer needs 2.5.3 Opportunities: 1. Increase the use of different technologies in the work process. 2. To add a special taste that is specialized in simple use. 2.5.4 Threats: 1. Strong competition. 2. Competitors using better technology out side better than ours. 3. Inability to produce products with quality that meets customers' standards.

2.6 Feasibility study

Feasibility study is used to gather a broad data for the members of management that in turn enables them to make a decision whether to proceed with the system development or installing process.

21

A project must be feasible in all three ways to merit further development as shown in the following:

1.Feasibility elements

Economical. Operational Technical. Schedule.

2.6.1 Economic Feasibility

System analysis time: POS business process is not so complicated, so it will not take more than 25 working days (at most) to finish system analysis process. Cost of system study: As we mentioned before POS system is not complicated, and does not need many analyst to perform this job, one analyst can finish the entire job. Cost of employees time: The analyst will need few interviews with workers, he may need to make a questionnaire and observe the system these activities will not take much time from the employees. Cost of software development: The development of system software is not complicated and does not need more than one developer, so it is somehow not expensive. 1. 2. 3. One-Time Costs: Hardware and software. Employee training. System development. Recurring Costs: 1. Technical support and maintenance.
22

2. Software updates. Cost of hardware: The following table summarizes the hardware needed to operate the system:
HARDWARE NAME Cameras Magnetic card reader Bar code reader Wireless network Printer Touch screen 2 Pentium 4 computer Computer terminal TOTAL COST 70 JD 150 JD 200 JD 60 JD 40 JD 300 JD 400 JD 200 JD 1420 JD Table 2: hardware cost.

2.6.2 Operational Feasibility

In the manual system selling process takes a lot of time while the customer picks out his order and letting the sales man proceed, in the new system GUI system will help the salesman to identify the customer and deal with him/her in amore professional way .

The manager needs to know some information about the work (profit, highest product soldetc). In the current system he makes every effort and spends a lot of time to collect information he needs to make a decision. The new system will collect the needed information and make reports automatically in order to facilitate the decision making process on the manager. The system will enable the company to serve customers quickly, efficiently and give them reasons to return. Using the system will be familiar to the old system but more efficient and more usable and user friendly.

23

2.6.3 Technical feasibility:

This involves questions such as whether the technology needed for the system exists, how difficult it will be to build the system, and whether the firm has enough experience using that technology. Technical Resources Needed: 1. Software, involving application software and databases. 2. Hardware, involving some special equipment.
3. Training for employees how to deal with system and

inviting customers to use our system throw getting magnetic cards.

4. Maintenance.

Risk Factors: Project size: 1. Number of members in the project team (3). 2. Project duration time (3 months). 3. Size of programming effort. Development group: 1. Familiarity with hardware, software development, environment and operating system. 2. Familiarity with proposed application area.

2.6.4 Schedule

24

As a graduation project, there are stretch times table we must commit with, the main date we must commit with is the dead line, which will be at the end of December 2007, and it is not exactly assigned yet, other milestones will be requested during the semester as usual, like the analysis and the design of the project. To avoid any latency at the project, since the project is a bit large, we decided to start our work early, to be able to handle any milestone at the needed time, and to be able to organize our time as we need not as requested, so we started our work from march 2007 the thing that gave us very long time to self study and organizing our lines to be able to start working. From the beginning of September 2007 we started to work real in the system at all the fields, from analysis and planning and implementation. The time table and the tasks will be discussed in details at the next section.

2.7 Evaluate feasibility After this analysis, we can see that it is feasible to work and go ahead in this project, and we recommend other countries to go ahead in doing such creative and new IT ideas to improve the economy of their status as done always here in Jordan.

2.8 Estimate project development time This project is scattered to tasks which will be shown bellow, here in this section we will draw the pert , Gantt chart and tables that shows the work overall.

25

Figure 4: table of planning phase

Figure 5:table of designing phase

26

Figure 6: table of analysis phase

27

Figure 7: Gantt of planning phase

Figure 8: Gantt of design phase

Figure 9 : Gantt of analysis phase

28

Figure 10: Pert of planning phase part 1

29

Figure 11 :Pert of planning phase part 2

30

Figure 12 :Pert of planning phase part 3

Figure 13: pert design phase

31

Figure 14: Pert of analysis phase part 1

32

Figure 15: Pert of analysis phase part 2

2.9 Implementation plan

After we knew the system requirements, planned our project we now can organize our job by planning the next levels, as a graduation project, we have a short time, so the next level will be the parallel work level, the design will run first, and as soon as the first functions being designed we will start implementing these functions, after all we will be investing the time of design two times. Our implementation will start in tiring to write a small function that can calculate the amount of money and return a value. At the time we start empower our project we will add some monitoring cameras to the system to make it powerful and efficient so it start with only to three functions so we can manipulate the project and enhance on it The idea of the project is how to make it powerful and more flexible so any addition on the project it will take it in more professional way. So in the implementation phase its not that hard if any company took the project to maintain on it because theres
33

comments between the lines so the programmer can know were to look . In the mean while the other members are working on another function such as the main menu that requires knowledge of adobe photo shop and flash. After that we team up to meet on the real deal which is the POS system that holds all the sales, the idea is that how not to let any employee to work on the POS system, so we added a privileges to the system that only the manager can give or take privileges to the employee. In the POS system we added the camera till know and magnetic card reader bar code reader printer for reports that we will talk about it later. Now about the devices we added the magnetic card reader was added to the system to help customers in more professional way such as if the customer want some discount, the system will not provide him/her until if he/she is a member to the shop itself, or in some cases a manual discount will happen by an order thro the manager himself. Also the magnetic card reader can help the employee to serve the customer thro knowing what the customer had bought last time or before thro viewing reports of desired customer. About the bar code reader was added to the system that is used to encode every item in the store so when a buy process happen only the employee pass the item thro the bar code reader and the price is taken in to the report in the POS system. Also the printer is important in this stage but how to use the printer in a useful way that was a perfect question but first Ill talk about the reports. reports is a good idea is added to the system that is used in many different ways such as manager can get reports about each employee and employee can get reports about customers to help them or manager can get reports about the sum of all employees process. Also the printer was used so it can print the envoy to the bought item for customer so if the customer want to return any items in any specific day it will be done in short amount of time. Because of the short time we will have, we will not be able to discuss all the features we have in the system. Only a description will be said.

CHAPTER Three: ANALYSIS PHASE

34

CONTENTS: -INFORMATION GATHERING. -REQUIREMENTS EXPLANATION. -PROCESS MODEL. DATA FLOW DIAGRAM. DATA DICTIONARY. i. PROCESS DICTIONARY. ii. DATABASE DICTIONARY. -COMPONENT ANALYSIS SYSTEM & SUBSYSTEM. SUBSYSTEM & COMPONENTS. DEPENDING MATRIX -USER ANALYSIS USECASE DIAGRAM.

35

3.1 Information gathering

At the time the idea of the system was born, we have started to collect information about all the systems aspects, not only about the system requirements, but also about the technical details of the systems functions. We have used the interviews methodology to investigate what will be needed from us to implement at the system, and as we mentioned at the beginning; we met the CEO Mr. Imad Mustafa who helped us a lot thro all the process of gathering the data and meeting the employees. The process of gathering data went throw stages : i. first stage : we set with Mr.Imad to see how the overall organization works, he showed us the firm and the system they deal with.the discussion started to cycle around the system and how we can improve it and the strengths and weaknesses. ii. Second stage: in the second time we had with Mr.Imad he showed us some records for the employees and how they sell and the process how they sell in the roasters shop. The problem was that the system doesnt support any soft copy of the transactions in the system. iii. Third stage: we checked on bells that they pay for the government and we conclude that there might be some missed files over years. And the idea how to make bells for government legal, which helped us to maintain that in older system didnt have any dynamic changed to the tax if any change has been done. iv. Fourth stage: we checked on the system that has been running in the roasters shop and we checked it all but the problem is that managers and
36

v.

employees have the same privileges which is totally wrong for an example the employee can make an illegal sale but in our system a new idea we came up with, to have a privileges to managers and employees so not any person who uses the system have fully controlled on the system. Fifth stage: we searched and looked thro books and internet to find if theres any additional staff we have to add and idea we found is to add monitoring system, the monitoring system idea we found is not to have it only for customers over the shop but also to have it on employees that uses the cashier, the idea is to insert a camera pointed on the cashier so if the employee signed in, a camera takes a snapshot of the employee with time and date. Also if the point of sale system is not used for a period of time the camera system is switched on, recording for approximately 3 hours.

3.2 Requirements explanation

After the interviews with the CEO and employees we are able to make our documentation and discuss the requirements in detail. As understood, our main objective is to improve on the old system and enhance the way the firm deals with the system, and use the best technique we can. The first step is to make the requirements in best shape and better appearance for the user. Also make the buttons bigger and easy to click on them, to provide level of managers good reports. we first how the user ability to use the system which is to make some privileges for employees before anything. After that is to use the magnetic card reader to let the user just by check in either by
37

the card reader or by choosing username and then enter the password. Then after that in the main menu that contains other menus and every menu contain submenu such as the filing menu that contain customer, inventory, employee, supplier, item. These submenus are designed to manager/s that to create new record either for customers or employees or to add items to the inventory. Menu is editing that contain create invoices either for sales or buying, also it has vouchers for the process of buying or selling. The idea in here is to record any transaction that the firm does and it must accessed only by the CEO. This menu is important in the firm because once the voucher has been created it will be saved in the data base but in other way it can be edited if there has been any mistake. About the report menu it has daily sales, this submenu is important so the manage can check on the daily sales within single click that shows over all the employee what they has been selling in desired day. Other submenu is expiry date that shows all the items in the inventory and if its close to be expired so the firm can make any offers on them before they throw them away. Also theres employee sales, employee sales items, and inventory items. These submenus are important and the reason because the manager can check not only on the daily sales but also to check on the employee what they have been selling on any specific day and also to check on the most selling items in the store if they are important also what the inventory what it has items. Other menu is the control menu that it has the scanner to enable it or disable, the magnetic card reader which is a good idea to add so in case the card reader is broken it can be replaced by click on this submenu to make it manual also the sound or lets call it the media player. Its a facility If the shop want to put kind of music for the shop so customers can satisfy while buy, its a good idea because while our researches we discovered that soft music put the mind in a good mood and customers will buy more to satisfy themselves. Also the printer and barcode reader. They are also good ideas incase if any of them is not working well they can be disabled so the employee can enter the item manually. Another menu is the POS menu that can be entered by any employee in the system, this menu contains the selling components and it will be discussed later in this chapter.
38

3.3 Process modeling

After the deep understanding for all the stats at the system with al the features and functions, we can now start putting models that will be the infrastructure for building the design then the implementation, we will start here with the process modeling using the well known UML written data flow diagrams, these data flow diagrams will illustrate our system and view every process at it with all the communications and relationships between this process and all other processes , based on these diagrams, we can have a top look at the system to see how the system will work, and it will be the gateway for the design, because every process will be taken apart and designed, to get the full system design. As all the data flow diagrams, we will start from the context diagram and zoom in for the so called zero level and the first level, we will stop at the zero level and leave the rest to the design. 3.3.1 The context diagram From figure (16) that illustrates the context diagram we can notice the main five external entities that deal with the system, supplier, employee, customer, inventory, management figure (16) shows the context diagram for the point of sale system
customer

Customer order payment invoice

0
Check customer request
Point of sale employee

Enter user /pass

Su

Produce reports

inventory manager

It e m

pp ly p ro d uc ts

ch ec ki ng

supplier

39

Figure 16:context diagram for the system

3.3.2 Level zero data flow diagram After building the context diagram, we must now zoom in with our thinking, to see how can we divide the big process "POS" into small more specific functions, figure (17) that shows the zero level data flow diagram will divide this process into around six processes, that can show the main headlines of how the program could be written, these processes will be explained and discussed later.

40

employee employee

Invalid input

1
Enter username password Check employee username

Check employee

Valid input

D1
password

Employee record Employee record

Order not available Customer order

2
Check customers request

Item Checking

inventory Customer order Item info

customer

invoice

Order available

3
Create Invoice Invoice information payment

Employee information Item info

6
Check item information

Item number

Item info

4
Produce reports Item informaiton

D2

Item record

Purchase information Report produce Supplier info managment Supply products

5
Supply products

D3

Supplier record supplier

Figure (17) : zero level data flow diagram.

41

3.4 Data dictionary

After all the diagrams and charts a programmer must have data dictionary to describe all the processes like for an example if the user want to trace the processes he will be lost, he need a description to follow. , here comes the role of the data dictionaries, these dictionaries will explain each part in the level one diagram alone, so the reader will be able to understand the real flow to the data at the system, the dictionaries will be divided into processes dictionaries, data stores dictionaries, and entities dictionaries. 3.4.1 Processes dictionary

At table (3) each process at the zero level data flow diagram toke a row, to be described from all the aspects, the respected value, the return value, and the process itself.

Nu m 1

Process name Check employee

In value Value From Password Employe e record

Return value Value To Invalid employ input ee

Description For checking employee password and user name and return the result

Username Employe password e 2 Check customer request Valid input Check employe e

Valid input Item checki ng

Check custom er request Invento ry

It takes the request from customer and return if valid or invalid for desired item/s

Customer

Custome

Order

Create

42

order

Create invoice

Order available

Check customer request

availab le Order not availab le Invoice

invento ry Create invento ry Custom er To make invoice to customers or suppliers for items that has been bought to sold and record it in the data base

Payment

Custome r

Invoice inform ation

Produce report

Produce reports

Item informati on Item informati on

Check item info Item record Report produc e Manage ment To create reports for manager and save it in the data base. Accessed by manager and to check on each employee individually

Employee Invoice informati on Supply products

Employe e record Create invoice Supplier Purcha se inform ation Item record To provide the system with products thro supplier and insert them to inventory and save records To check on each item in the inventory and make record and

Supply products

Check item information

Item informati on

Item record

Custo mer order

Invento ry

43

provide alert for old items Item informati on Inventor y Item numbe r Item record

Table 3: data dictionary 3.4.2 Data stores dictionary

Finally at the dictionaries that describes the data flow diagrams are the data stores dictionaries, as seen form the DFD, we have two data stores, actually the are one, but they have been divided to two for simplification, we have a database to store the information about the customers and employees, the entities and attributes will be discussed later at the database analysis and design.

3.5 Component analysis

At these levels of analysis, we must divide the system into subsystem and then to small components so we can read the small peaces of the system, which will be understood much better and easier, also the component dividing will help us to implement and design each function in much better way, so at this section we will talk about the small components at our subsystem, how are they connected to the other components and other information about it. As follows a specific description of each system, subsystem and its components 3.5.1 system & subsystem As mentioned before each system is connected to its subsystem. Heres a table that describes The relationship between each of them.

44

System

Subsystem

Filing Filing Filing Filing Filing Editing Editing Editing Editing Report Report Report Report Report Control Control Control Control Control Control Control

Customer Inventory Employee Supplier Item Create invoice of sale Create invoice of buying Voucher of selling Voucher of buying Daily sales Expire date Employee sales Employee sales item Inventory item Scanner Magnetic Sound Camera Printer Barcode reader Touch screen Table 4: Relationship between system& subsystem
3.5.2 subsystem and components

because every subsystem has many components, a perfect idea is to minimize the number of redundancy of every component that is connected to its subsystem. Heres table 5 and table 6 shows the relation between components and subsystem thro numbers.

45

Components New record Save for new record Edit Search Print Delete Done edit Employee picture First Last Previous Next New item Show item Save item Delete item Print report Select date from Select date to Employee name Inventory content Mark item Report Table component number

Component Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 5:relation between component

&

Subsystem customer Inventory Supplier Editing Item Sale invoice Payment invoice

Component Number 1,2,3,4,5,6,7,8,9,10,11,12 1,2,3,4,5,6,7,8,9,10,11,12 1,2,3,4,5,6,7,8,9,10,11,12 1,2,3,4,5,6,7,8,9,10,11,12 1,2,3,4,5,6,7,8,9,10,11,12 1,2,3,4,5,6,7,8,9,10,11,12,13,1 4,15,16 1,2,3,4,5,6,7,8,9,10,11,12,13,1

46

4,15,16 Voucher selling 1,2,3,4,5,6,7,8,9,10,11,12,13,1 4,15,16 Voucher buying 1,2,3,4,5,6,7,8,9,10,11,12,13,1 4,15,16 Daily reports 17,18,19,23 Employee sales 17,18,19,23,20 Employee cash report 17,18,19,23,20 Employee item report 17,18,19,23,20 Inventory content 17,18,19,23 Expiry date 17,22,23 Table 6: relation between subsystem & number

3.6 Component description

After showing relation between the components and its subsystem its easy to describe the components, table 7 is showing each component and its description

Component New record

Description To make new record for employee, customer or supplier Save record Is to save the record for each of the three Edit To manipulate the record Print Is used in many components and its valid Delete Is to wipe any unwanted record Done edit To save in the DB after editing Employee picture To take snapshot for employee First, last, prev, Are features used for DB purposes next New item Is used in DB to insert new item or product Show item To display from the DB any desired item
47

Delete item Print report Choose date from Choose date to Employee name

Is used to delete old item/s Is used to print only reports Is to select desired date from Is to select date to To select from drop down menu the name of each employee Inventory content To select from the inventory the content wanted Mark item To mark on items wanted Table 7: description of contents

3.7 User analysis

Finally at the analysis phase, we must analyze how would the user use the system, in other words, what will he see at the time he opens the system, what will he fill, and how will he interact with the windows, figure (17) shows the use case diagram that will answer all these questions.

48

Figure (17): use case diagram.

With a fast look to this diagram, we can see the user (cashier, manager or data entry) can interact with the systems they can get in front . here the use case diagram shows the manager is connected with the cashier in customer account services and the data entry is separated from the res.

CHAPTER FOUR: DESIGN PHASE

49

CONTENTS: - DATABASE DESIGN. - STRUCTURAL DESIGN. - SYSTEM DESIGN. - USER INTERFACE DESIGN. Collaboration design. Sequence design. - SOFTWARE & DEVELOPING TOOLS

4.1 Database design

To store all the data we need, for sure we need a database, which will satisfy all the databases specification, and normalization properties, and our project is a database project.
50

And it depends on other attributes which they are connected to outsider from the system. At the functional requirements, we have listed some of the data we need to store at our database, not of course; the system itself will request some variables and values to be saved permanently and non-permanently to insure the correctness of our systems run. As all the databases at the design phase, they will finally be represented in an entity relationship diagram; that will allow us to read the entities, and understand the relationships between them, figure (18) will show the Entity Relationship Diagram (ERD) of our system. And figure (19) will show the attributes of each entity.

51

Inventory fragm antation

M
Contain

1
D raw back

1 M

1
check

em ployee

Deal with Inventory

M 1
make Selling voucher edit contain

Payment invoice

M 1
Buying voucher

Selling invoice

contain

item

contain

M M 1 M
Selling content Draw back

Belong to

Paym ent content

1 1
contain customer

class

1 1 1 1

edit

supplier

m ake

Figure 18: Entity relationship diagram

52

Figure 19: attributes of each entity

4.2 Structural design

At this point that we must create the main points about where the components must be implemented at our system, to know the structure of the functions, and the hardware or the type of internal structure it is built of. Mainly our system will be built over a Microsoft platform, this plate form is used mainly around the local area like Jordan for example and its easy to maintain and to use. Other plate form is hard to work on plus is not well known for users. About the database used is the access database and the reason is the cost, and the number of people to access. But in the other had is to use better technology but to maintain the cost low. About the camera is that they are
53

connected to the system and maintain by the manager and record view also. The customer is connected to the employee and the employee connected to the computer as shown in the figure below. Figure (20) will show a representation of the structure that will system work on with the graphical representation.

Figure 20: structural design

54

4.3 System design

At the system design here at this section, we will make an over view for the system as one unit, to have a vision that will allow us to know the places of the functions, and the procedures at the programming classes, so we will show the class diagram, figure (21) will show the class diagram and its description will be below it.

Figure (21) class diagram.

We can see here that the program mainly will be created from eight classes; sure these are the cashier, cart, payment, customer info, inventory, debt, cash, cash, credit card functions and modules are not included. About cashier it contains the name, new sale, identify item, enter customer id. Cart include item id, total with tax, get discount, calculate and update on the data base, payment
55

include payment id, amount, and insert payment. Customer information includes account id, customer name, customer phone, amount, and discount. The inventory includes the item id, item name, quantity and class. Debit includes the account id. Cash include amount paid and change amount, the credit card include card number and card type string.

4.4 User interfaces design

It is now the time to think of how would the user interfaces will be designed, and how will the application will give and show the functionalities that is implemented in the internal modules, the main objective at the design of the interfaces is to make them user friendly and all the functionalities are accessible easily from the main menu and other common places. At this section we will stand in designing the interfaces at the aspects of sequence diagrams collaboration diagram, that will allow the programmer to know the sequence needed to create any interface to any process he have. 4.4.1 collaboration diagram:

The collaboration diagram shows the how it deals with the cashier thro processes or sequences and the cashier deals with cart thro payments or other processes and the cart deals with the inventory and the customer info. Figure (22) contain the collaboration diagram

56

Figure 22: collaboration diagram 4.4.2 sequence diagram: the sequence diagram is more operational than collaboration diagram if and only if the user could not understand the process in the collaboration diagram, sequence diagram shows the processes in order so any step between for example the customer and the cashier is set thro sequences so the reader wont miss it.

57

Figure (23) shows the sequence diagram and the processes in order

Figure 23: sequence diagram

58

4.5 Software and development tools

Basically, and as we have mentioned before, this project will have the structure of a windows application, and while we have to do this project as a graduation project, but if this project has been taken into series way, it can be developed in other platform and improved in many ways, but to say our project in this situation can be used as it happened before it was used for a period of time in the Alalamiyah roasters, and we got the approval from the company. About the software and development tools we used the following applications: VB6 studio (programming language). Adobe photo shop CS2. Microsoft Access. Macromedia flash. Microsoft windows XP(platform).

CHAPTER FIVE: IMLEMENTATION PLAN

59

CONTENTS: - IMPLEMENTATION METHODOLOGY. - USER MANUAL. LOGIN SCREEN. UNIVERSAL WINDOW. DEALER SCREEN. ADD NEW ITEM. EMPLOYEE SCREEN. INVENTORY SCREEN. SUPPLIER SCREEN. PAYMENT INVOICE. SELLING INVOICE. DAILY REPORT SCREEN. EXPPIRED DATE FOR ITEMS SCREEN. - SUMMARY. -CONCLUSION. - REFERENCES.

60

5.1 Implementation methodology

In the implementation plan here we will talk about the program how it was built and the user manual will follow to help the user how to interact with the system and make it easier. At earlier stage we showed how the system was built in sequences and in specific dates. After all building the subsystem requirements helped the program to be efficient to be used by its users. about the user manual we added some screens to show the system for the users. As the following will show the user manual:

5.2 User manual

1. Log in screen: In this screen the user will have to input user name and password, so that he/she can use the system

61

2. Universal window: After logging to the system, the employee will have to enter his user name and password. Each employee has a unique user name and a password.

3. Dealer screen: In this screen the user will be able to make transactions with the customer; he will first process the customer request by searching for the requested items, then making an invoice by calculating the total of the sold item.

62

4. Add new item screen: In this screen the employee will be able to add new item, first he will have to specify the category of the item, and then he will enter the information attached to this item like item name, item number, etc

63

5. Employee screen: In this screen you will be able to view existing employee, also we can add new employee using this screen (of course if you have the privilege to do that).

64

6. Inventory screen: In this screen, you will be able to view inventory information, like inventory number, its location, and the number of retails in each inventory, etc

65

7. Supplier screen: In this screen you will be able to view supplier information, also see the information for each current supplier, also you may want to add new supplier.

66

8. Payment invoice screen: In this screen you will be able to make payment invoices that are when the store purchase items from suppliers, he will then make an invoice explaining the information attached with the purchase process.

67

9. Selling invoice screen: In this screen the employee will be able to make invoices when he/ she sell items to customers.

68

10. Daily report screen: In this screen the employee will be able to view report that contains information for daily transactions, so that he can keep track of the selling items, and according to these reports, he can make future plans for his store.

11. Expiry date for item screen: In this screen the employee will able to view items that their date has reached the expiry date, so that he can have enough information about the product exist in the store.

69

5.3 Summary:
In order to have a successful business in the currents days, you need to provide better customer services than your competitors, neglecting the quality of the service provided to The customer will make the customer neglect you. Stores are widely spread all around the country, so in order to have a successful business in this highly competitive environment you must try to develop a system that can help you managing your own resources then providing better services for Customers. Building a successful system needs good business process understanding, we tried to Understand the system by interviews, questionnaires and observing the old business Process. We tried to develop a system that meets the POS process needs and help the managers to make right decisions in the right time. The system did not only met the functional requirements but also important non functional requirements like usability, reliability and maintainability.

70

5.4 Conclusion:
After performing the feasibility study for the system and understanding the business process we recommend using the computerized system we developed instead of the old system because the new system integrates all the subsystems together and it will help in increasing the services speed.

5.5 References:
1. System analysis and design, KENDALL & KENDALL, 6th edition. 2. Software engineering, Somerville, 7th edition. 3. Visual basic 6, how to program, DEITEL & DEITEL. 4. www.Microsoft.com/vbasic. 5. www.arabteam2000.com 6. www.google.com 7. www.freevb.com 8. www.planetsourcecode.com 9.www.projectcode.com

71