Illuminasia inventory system - VB.Net System Documentation

Page 1

A Project Presented to the Faculty of the Computer Engineering Technology Department Technological University of the Philippines Taguig Campus

In Partial Fulfillment of the Requirements in Computer System Analysis

Presented by: Anos, Angelica D. Galvez, Sergio Jr. M. 3H1 CoET Date: September 23, 2013


ILLUMINSIA INVENTORY SYSTEM

TABLE OF CONTENTS Acknowledgement …………………………………………………………………………………………………………….. I. Introduction 1.1 Overview ………………………………………………………………………………………………. 1.2 Statement of the problem …………………………………………………………………. 1.3 Significance of the study …………………………………………………………………. 1.4 Objectives of the project 1.4.1 General Objectives …………………………………………………………………. 1.4.2 Specific Objectives …………………………………………………………………. 1.5 Scope and Limitations 1.5.1 Scope ……………………………………….………………………………………. 1.5.2 Limitation ……………………………………….………………………………………. II.

Methodologies 2.1 Project Planning Method 2.2 Analysis Method 2.3 Design Method 2.4 Coding Method 2.5 Testing Method

III.

IV.

………………………….………………………………………. ……………………………………….………………………………………. ……………………………………….………………………………………. ……………………………………….………………………………………. ……………………………………….……………………………………….

System phase Analysis 3.1 Data Gathering Procedures ………………………...………………………………………. 3.2 Functional Requirements ………………………...………………………………………. 3.3 Event Table ……………………………………………….…...………………………………………. 3.4 Activity Diagram …………………………………….…...……………………………………............. 3.5 Data Flow Diagram ………………………………….…...………………………...............

í 1 2 3 3 3 3 4

5 5 5 5 6

7 8 9 11 12

System Design Phase 4.1 System Flowchart 4.2 Structure Chart 4.3 Database Design (ERD) 4.4 User Interface Design

V. System Testing VI. System Implementation 6.1 Hardware Requirements 6.2 Software Requirements 6.3 Non-Functional Requirements VII. Discussion of results VIII. Summary and Recommendation

Table Of Contents ii


ILLUMINSIA INVENTORY SYSTEM

ACKNOWLEDGEMENT Foremost, we would like to thank our client Mr. Mark Dumadag and Illuminasia itself for letting us have all the relevant information of Illuminasia in creating our system; for the time he spared for us to interview him and his willingness to help us understand what Illuminasia is. We express our gratitude that he lends us some of their transaction records though confidential for us to understand how their process flows. We also would like to express our sincere gratitude to our advisor Prof. Dalisay for the continuous support of our study and research, for his patience, motivation, enthusiasm, and immense knowledge. His guidance helped us in all the time of research and writing of this system project. We could not have imagined having a better advisor and mentor for our study. This project report provides us the opportunity to put into practice, the theoretical knowledge acquired all through our academic career. An outcome of blessings and contributions of many aspirations. We express our sincere gratitude to the respected faculty members. It is all because the blessing of our parents and well wishes that we have been going ahead in our life. We take this opportunity to convey our deep sense of gratitude and respect to them. We are highly thankful to our respondents and classmates who spared their precious time to extend the right amount of information and to those who have directly or indirectly helped us for completing this report. We are happy to place on record my thanks to all the faculty members of my institution for timely help during this study. Last but not the least, we thank Almighty God for reasons too numerous to mention.

Acknowledgement i


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 1 INTRODUCTION 1.1

OVERVIEW We are living in an age of Information Technology. Computerization is at the very foundation of the Information and Computer Age. The giant strides that we have made in the areas of communications and business automation are possible only because of the great successes that we have achieved in the field of computers. Again, we are astonished, how we are able to talk to our near and dear living several thousands of kilometers away, from wherever we are, at home, office, on the road in a car, or in a classroom – by just clicking a few n umbers on our palm sized cellular phones! Unlike the older days where people sends their message through snail mail which will took a lot of time to be sent. Computers are changing the way we do business and the way we live. Nowadays, computers are not only used to serve as our internet media and communication link to far relatives, but a medium to locally automate business processes to a great extent. A broader or even small scale business composes of systems that can actually fully increase process of transacting with customer in such that almost a second all information regarding an order can be recorded and viewed to a database. System application plays a large role in our businesses providing fast growing information with the use of database. With the role to fulfill one of our requirements in Computer System Analysis, this system has been developed. Developed to provide and meet all the needs that our client requires to their business. A well-developed business always seeks improvement of their status thus it is great responsibility to secure the stability of their company with our system. Illuminasia Lights Incorporated comprises of 4 office branches and one head office which is located on 2130 D Leveriza St., Buendia, Pasay City. This company is a retailer type business that handles lighting fixtures. Illuminasia maintains the records for their transactions, product inventory as well as their sales reports. Illuminasia Inventory System is an implementation which helps financial/Accounting staff to search the availability and prices of various products, along with the updates with the product. This project also covers various features like error controlling etc. In general, this application would be designed to perform like any other Inventory and sales Application (Desktop Based) available as offline.

Introduction

1


ILLUMINSIA INVENTORY SYSTEM

1.2

STATEMENT OF THE PROBLEM Existing system is based on manual work and all the process are done manually, so they maintain registers and files for recording all the details of the system. They maintain several registers for recording the entry of daily transactions such as billing of the products to the clients; also they keep information regarding their regular clients in the master file. They keep the bill book or cash book to maintain the record for each sale of the product or transaction in the company. Similarly they maintain the book for their reservation and delivery so they can pay the money to them after some time. Thus maintaining information, customer information, product transaction and all the things are done manually. As the growing trend in InfoTech world of computers need of accuracy, Perfect ness, speed and high memory data storage is a must. Each and every Problem must be solved with a least amount of time and energy. The problems faced by existing system are described as below:  Difficult in Maintenance of Records. It is very difficult to maintain data record in the system as all the records are entered in the register or the respective record books. There are chances of the record books or files in which all the data is kept may be torn or wearied out or some other damages which results in the destroyed data. Also a problem occurs if the data file or register is misplaced somewhere else and is not getting at the time of actual requirement of the data stored. It is also difficult to maintain old files and registers which have data of past years which the owner has kept for future references. The problem occurs when the sale of fixture is more and when the monthly report or bill is generated then the owner has to go through lots of record and which is very tedious task.  Time Consuming. It is very time consuming process to write each and every entry in the database register. Also it takes a lot of time if all the entries are repeated. In the system processes such as making different type of reports, billing, tedious calculations are examples of time consuming process in the system. It is also time consuming process to know the total number of sale done by the Illuminasia when written manually but through computerized system it takes less time as it is speedy and accurate.  Editing of data becomes a tedious job. Manual written data cannot be changed or edited once written. If there is a mistake and if we try and write it makes the register very dirty and untidy, which creates a bad impression of the business. If data is entered incorrect whole document gets incorrect whole document gets incorrect while errors cannot be easily solved by editing wrongly entered data. If one had done some wrong entry then to edit the one has to go through lots of records and, again and again editing the record makes it difficult to read.  No Security of Data. As the data is stored in files or registers, it is not in a secure place. As the storage media here are files and books or registers there are chances of getting these storage media lost, torn, or it may go in the hand of wrong person which can destroy the database or it can also be destroyed accidentally. Also in the system data should be shown to the person according to his position and post in the office everybody should not be allowed to use all the data. If the data goes in the hand of wrong person then he/she may take advantage of the data and the Illuminasia may go in loss. So security is the major aspects of the Illuminasia.  Proper Generation of Report.  Product Maintenance. Product records in the company cannot be updated easily due to thousands of product stock. Manual work can take a lot of time.

Introduction

2


ILLUMINSIA INVENTORY SYSTEM

1.3

SIGNIFICANCE OF THE STUDY Inventory is a term used to describe a company goods or merchandise being stocked at a warehouse. Every but not all company that provides a large number of goods or merchandise to be sold has been into this type of business process. Allocating stocks for availability purpose of the product can actually decrease the works of daily supplying for their stores. Thus to lessen the work of identifying the stock of a product, this system has been developed. The aim of this software is to develop a systematic analysis of the procedure involved in the Inventory and sales of products for the company. This should be used in an effective way so that various advantages are obtained from the software. Software means establishment of sound and indepth development of a task using high-level language that results in well-equipped, economical software, which is reliable. The “ILLUMINASIA INVENTORY SYSTEM” undertakes as a project based on relevant technologies. The main aim of this project is to develop the software for the process of recording transactions should lead to increased efficiency and reduced drawbacks which were present in the previous procedure of using logbook. The software should be error controlled both logically as well as in syntactic manner.

1.4

OBJECTIVES OF THE PROJECT 1.4.1

General Objectives The main objective of this system is to overcome the existing manual system and the problems existing of Illuminasia Lights Incorporated with the help of some platforms such as VB.NET serving as the programming language and Microsoft Access as the database in order to give ease at work up to a great extent.

1.4.2

Specific Objectives  Provide a User-friendly application for Illuminasia and give ease of recording, updating and deletion of transaction records.

    1.5

To develop a module that will compute the sales, income, and inventory of the company and provide generated reports for their timely record in a daily, weekly and monthly basis of time. Increase work efficiency of employees in transacting with customers using automation of order records and printing of receipts. Provide a well secured database with back-up and retrieve capabilities to overcome possible data corruption. Secure information in database using login options to designate user access in the system.

SCOPE AND LIMITATIONS 1.5.1

Scope

As a part of the preliminary study, the scope of the system has to be clearly outlined. This is useful for estimating the amount of effort required, the cost involved etc. In any Illuminasia Lights store, Purchase and Finance department plays an important role to produce great image in market. We cannot think about an existence of an individual department only. Here the Purchase department deals with all the procedure regarding the purchase of the

Introduction

3


ILLUMINSIA INVENTORY SYSTEM shoes from the customer’s order, reservation or delivery. While the billing department deals with all the procedure regarding the sale of the light fixtures to the customer. During the purchase or billing procedure, Illumnaisa will interact with the customer or with the client as external entity and with other departments inside the environment of Store.

1.5.2

Limitations

The boundaries of the system store which encloses the different departments including the purchase and sale department which interact with the external entities as customer and Client. Also the system cannot add stock due that the product’s beginning stock is always fixed. The system can’t operate when there’s a power interruptions/failures. Only the authorized personnel can access the system.

Introduction

4


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 2 METHODOLOGIES 2.1

PROJECT PLANNING METHOD This part of methodology acquires a full understanding on how to construct or come up with the exact output of your project. You should know how to give solutions to the dilemmas that your client complaints about. The programmer has to visualize a certain concept or idea that satisfies the requirement of the client and give suggest a possible solution. In order to meet the needed requirements for this project study, we used several techniques and methods to be used in improving our project. The following are the methods we used to plan for our system:  Internet – great vast of knowledge had been provided through internet. Through exploration of website allows us to learn a lot of things more for our system including partial GUI, system codes and even sample related projects for reliable sources of information.  Evaluation – Asking friends, classmates and foremost our client also helps us to understand more clearly what our system must provide.  Interviews – conducting interview most especially to our client brings more accurate and clear outlook of our system.

2.2

ANALYSIS METHOD This phase of method explains the gathering of all the needed and relevant information or data that will later serve as an important basis on to what kind of system you need to come up with. The programmer/developer should dissect each information to help them understand more the current drawback and for the programmers to be able to have a more seamless solution.

2.3

DESIGN METHOD This phase is all about the “visual” part of the system together with the source codes that the programmers apply into the system. The vitality of source codes allows the solution for every client’s requirement. In designing this system we used the following applications:  Microsoft Access 2010 – this will serve as the records database.  Microsoft Visual Studio 2010 – GUI and coding of system  Paint – Simple picture editing  Gimp shop - Simple picture editing  Crystal report – Report generation  Photoshop – advance photo editing  Browser/Internet – built images downloaded through web

2.4

CODING METHOD System coding is the primary key to run and form the system. Without this, the system will be useless. It is the essential part in a system because it allows a simple GUI becomes seamlessly data manipulative.

Methodologies

5


ILLUMINSIA INVENTORY SYSTEM

2.5

TESTING METHOD Errors cannot be regarded so a testing implementation is conducted to avoid and trap crashing of the whole system. In most of the system testing, it is an important thing to determine all errors to be corrected and trapped.

Methodologies

6


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 3 SYSTEM PHASE ANALYSIS 3.1

DATA GATHERING PROCEDURES Information gathering in large and complex organization is not an easy task. It has to be gathered in an organized way so that, • No system details are left out • Right problems are identified • Repetitive work is avoided • Wrong or incomplete details are not collected • To this end, a proper search strategy must be decided first. Search strategy includes selecting information sources and search methods. Here in this project we have used: • INTERVIEWING • OBSERVATONS

INTERVIEWING: Interviewing allows information from individual or existing group who are generally the current users of existing system or potential users of the proposed system. They may be owner or employees of the firm itself who provide the data for the proposed system and who will be affected. . It allows the analyst to analyze and discover areas of misunderstanding, indication of resistance to proposed system The INTERVIEW regarding the project was done with the head of the accountancy in the Bata shoes company. Some of the questions asked were: 1. How do you process an order from the customer? 2. What is the nature of the business? 3. Do you want printing of receipt for the system? 4. How do you compute for the daily, weekly and monthly income? 5. What are the things you asked to the customer during transaction? 6. Do you allow debt for ordering products? 7. Do prices and stock need to be updated? 8. Do you want government and company tax be inputted? 9. How do you compute for the daily, weekly and monthly Sales? 10. How long will it take for the reservation to be cancelled? 11. Do you allow credits for order? 12. Does your company acquire delivery of products? 13. If you accept delivery, how much will it cost? Does it depend upon location or is it fixed in value? 14. Does your company offer discount? 15. Do you have suppliers? 16. If yes, do you pay for importation of products?

System Phase Analysis

7


ILLUMINSIA INVENTORY SYSTEM

OBSERVATION: Observation can bring in missed facts, new ways to improve the existing procedures. It can bring in what other fact-finding methods can’t. It took after operational in efficiencies, alternative routes and procedures, interruptions in normal workflow etc. The use and observation of the current system helped to find out the Operational Inefficiencies in the existing system. These Operational Inefficiencies are: Poor interface with user for input and output giving, no data security, delay in producing reports, lack of programming, inefficient storage and retrieval relates with increase in number of products or items records, etc.

3.2

FUNCTIONAL REQUIREMENTS A. At start of transaction  Can automate the work of recording customer’s information including the customer’s name, address, and contact number.  Can tell which item/s are available, salable and not. B.

During Sales  Inquiry of items.  Calculating price as per quantity.  Collection (payments of customer).  Can generate financial sales reports.  Can provide quick and efficient means for performing billing related activities and to effortlessly generate report of the system.  Can calculate discount

C.

Inventory Tracking  Can tell how many items are left in the store.  Can generate report for the stores (daily, weekly & monthly) of inventory..

D. Data Add, Edit, Search and Delete  User can manipulate data inside the database, such that adding record for every customer, editing items and even deleting them in accordance with the customer will.  Can search any particular records within the database just by selecting the customer’s name, item he/she buys, or date of transaction. E.

Reservation  Customer can reserve order through phone or personal.

F.

Delivery  Company can deliver products upon only the customers will.  Delivery charge will be added when customer requested for a delivery.

G. Financial reports  Can generate supply reports.  Can generate income report.

System Phase Analysis

8


ILLUMINSIA INVENTORY SYSTEM

H. User Accounts ď ś Every employee of the Illuminasia Incorporated has their own accounts with which can access the system. ď ś Can record the logs of employee who uses the system.

3.3 1.

2. 3.

EVENT TABLE Event Employee wants to login Employee wants to logout Employee wants to add customer

Trigger Account number, Username and Password inquiry Logout / Time-out

Source Employee

Activity Account verification

Response Show Log and Time details

Destination Employee

Employee

Record log out details Add customer details Update customer details Delete customer details Search customer details Add product details Update product details Delete product details Search product details Verify Information Update user account Delete User account details Search user account details New order record added Add reservation

Admin log out

Employee

New customer record added

Employee

Customer record updated Customer record deleted

Employee

Customer record

Employee

New product record added Product record updated

Employee

Product record deleted

Employee

Product record

Employee

Account validate Account updated User account deleted

Employee

User account records

Employee

Order or transaction added Reservation added

Customer

Customer details inquiry

Employee

Employee wants to update customer Employee wants to delete customer Employee wants to search customer Employee wants to add product Employee wants to update product

Customer details change request

Employee

Customer selection

Employee

Customer details inquiry

Employee

Product details inquiry Product details change request

Employee

Employee wants to delete product

Product selection

Employee

10. Employee wants to search product

Product details inquiry

Employee

11. Employee creates new account 12. Employee updates a user account 13. Employee deletes a user account

User account details inquiry User account detail change User account selection

Employee

14. Employee search a user account

User account detail inquiry

Employee

15. Customer creates new order

Order information inquiry

Employee

16. Customer creates order reservation

Reservation information

Employee

4.

5.

6.

7. 8.

9.

Employee

Employee Employee

Employee

Employee

Employee Employee

Customer

System Phase Analysis

9


ILLUMINSIA INVENTORY SYSTEM

17. Customer wants delivery of order 18. Employee adds supplier 19. Owner wants to view products that are bestseller 20. Owner wants to view or compute daily sales 21. Owner wants to view or compute weekly sales 22. Owner wants to view or compute monthly sales

inquiry Record delivery order Supplier information inquiry Product request

Employee

Add delivery of order Add supplier information

Delivery selected New supplier detail added

Owner

Look up products

Product details

Owner

Expenses inquiry

Owner

Generate sales report

Owner

Expenses inquiry

Owner

Generate sales report

Owner

Expenses inquiry

Owner

Produce daily sales report Produce weekly sales report Produce monthly sales report

Generate sales report

Owner

Employee

Customer Employee

The table above comprises of six (6) columns namely: Event, Trigger, Source, Activity/Use case, Response and Destination. Each has their specific function in the table. The Event column shows all the events that the causes the system to do something. The Trigger is data entering the system or the point in time that triggers the system processing. The Source is the external agent or actor that triggers the system event. The activity is what the system do or done when the event occurs. The response is the output (if any) that is produced by the system after the activity. And the Destination is the external agent that gets the output produced by the system. These columns show how every event in particular will be activated and how they are triggered in specific time. The events above show the different activities that the user can be done in the system. With the basic event of adding, editing, viewing, deleting and searching, every records are easily manipulated the database. The employee for example adds a supplier; the trigger will be the inquiry of supplier information; since the employee triggers the event, then the source will be the employee itself; the activity will be the adding of supplier record to the database and the response should be a message that the record is added. This flow of events are then activated for every actions of the user in t eh system.

System Phase Analysis

10


ILLUMINSIA INVENTORY SYSTEM

3.4

ACTIVITY DIAGRAM

Activity Diagram – Illuminasia Employee

System

Owner

Y

Compute Sales/ Income?

Admin/Owner? Login Time-In

N

User Account Exist?

Y

View/Generate Sales Report

Create New Account

Y

C Y

C

N

N

View Best Seller Products? N

N Create Transaction?

Add/Update Products?

Y

Add/Update Supplier & Products

N

y

View Products

A

A

A

Add Customer Record

Y New Customer? Add expenses

N Input Transaction Details

B

Delivery?

Y B

Reservation Added

Reserve?

C

Save Transaction

C

A

Phase

Logout

This system activity diagram has been divided into three (3) parts namely the employee, the owner and the system itself. The first column above is the employee that shows the transaction done by the employee with customer. The employee is also valid for adding, updating, deleting and viewing record in database. The owner has the activity to compute and also generate sales, income and inventory reports in a timely basis (daily, weekly and monthly). Last is the system which keeps all the records and processed transaction made by the customers and inputted by the employee.

System Phase Analysis

11


ILLUMINSIA INVENTORY SYSTEM

3.5

DATA FLOW DIAGRAM 1.

Employee or Owner Login Record User log

D2

1.0 Employee or Owner

Account Inquiry

Logs

Employee Access

Employee

Login Owner Access

Owner

Lookup Verify

2.0 Create new user Save New Account

2.

D1

Admin

Add/Edit or Delete Product

Employee

Add/Edit or Delete products

2.0

D2

Product

Add/Update/Delete Product

Product Changes

D3

Supplier

D4

Stock

3. Create new order

Employee

3.

Create new order

3.0

New record added

Add new Order D5

Order

D6

Orderline

Add new customer details Fill up form Employee

New customer record added

4.0 Add new Customer

Save Customer

D7

Customer

System Phase Analysis

12


ILLUMINSIA INVENTORY SYSTEM

4.

Search Existing Customer Search Customer Employee

5.

Customer Details

Employee

Order Recorded

Employee

Reservation Added

Employee

Customer Record

5.0 Add new Order

Save order

D8 D5

Orders

Save reservation

D8 D5 D5

Orders

Save Delivery

D8

Orders

Save Supplier Record

D3

Supplier

6.0 Add new reservation

Delivery Added

7.0 Add new Delivery

Add new Supplier

Employee

9.

Customer

Add Delivery Add Delivery

8.

Search existing Customer

D7

Add New Reservation Add Reservation

7.

Lookup Customer

Add new order Add order

6.

5.0

Add Supplier

8.0

Supplier Details Added

Add new Supplier

View Best-Seller Products

Owner

View Best-Seller Products Product Details

9.0 View Best Seller Products

Record Details

D2

Product

D5

Order

D6

Orderline

System Phase Analysis

13


ILLUMINSIA INVENTORY SYSTEM 10. View and Compute Sales Report View/Compute Sales Owner

Generate Sales Report

10.0

D8

Bill

D5

Order

D6

Orderline

Sales Report Record Details

11. Employee or Owner Logout Logout Employee/Owner

System Exit

11.0 Logout

Record Logout

D2

Logs

A data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual implements and movement of data between people, departments and workstations. A full description of a system actually consists of a set of data flow diagrams. In the table above, the DFD has been divided into fragments showing every data flow in the system. Together with the data storage, the process composes of process flow to indicate flow of data for every fragment.

System Phase Analysis

14


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 4 SYSTEM DESIGN PHASE 4.1

SYSTEM FLOWCHART Illuminasia System

Login

B Employee

Select Transaction

C

Create Order

Select Existimg

Create New Customer

Customer

Fill up Customer Detail

Select Product

Product

Record As Reservation

Fill up Order Form

Orders and OrderLine

Payment

End

Record as Delivey

À

Receipt

Orders, OrderLine and BillInfo Orders, OrderLine and BillInfo À

End À

System Design Phase

15


ILLUMINSIA INVENTORY SYSTEM B

Owner

Sales Report

Income Report

Inventory Report

Select Date

BillInfo, Orders and OrderLine

BillInfo, Expenses

Product

Daily, Weekly and Monthly Report

End

C

Modify Records

Add, Edit or Delete Records

Change Inquiry

Product

Customer

Supplier

End

The flowchart above shows the representation of various computer files, databases and associated manual process that make up our system. Our system flow chart shows the process that occurs upon the execution of the program. The system has been built with two access options: the employee and owner option to secure datum for unauthorized access. The flow shows how the employee will transact with customer and steps for the transaction.

System Design Phase

16


ILLUMINSIA INVENTORY SYSTEM

4.2

STRUCTURED CHART

Illuminasia Inventory System

Login

Account Information Inquiry

Employee Account Validate

Owner Account Validate

Employee Access

Create New Order, Reservation or Delivery

Owner Access

Modify records (Product, Customer or Supplier)

Look Up item availability

OrderLine items Record Customer Information

Order, Reserve or Delivery List

Produce Sales Report

Order Financials

Customer Information

Record Order or Reservation

Produce Inventory Report

Process Order Order ID Order and Payment

Customer Information Add Customer Information

Select Existing Customer

Get order information

Process Order Item

Produce Income Report Write Transaction

Create New Customer Info Product ID, Qty

Product ID, Stock

Get requested item

Select Product

Item Information

Create OrderLine item

System Design Phase

17


ILLUMINSIA INVENTORY SYSTEM

4.3

DATABASE DESIGN (ERD)

System Design Phase

18


ILLUMINSIA INVENTORY SYSTEM

4.4

USER INTERFACE DESIGN (GUI) 1.

Login Options Illuminasia Inventory System consist of two login options; one for the owner of the company and one for its employee’s The two options have different access in the system, thus records will not be accessed thoroughly by unauthorized users

2.

Login

The login form consists of three (3) fields which must be filled up to have access on the system.

3.

Main

The owner’s main form composes of four functional buttons (at the bottom) and 4 non-functional (at the top). One button is disabled which is the transact button for which the access of owner does not include transacting with customers. The Hide button on top allows the system to be seen on the notifications not on the taskbar pane; while the shutdown allows the system to close without logging off. Right clicking the picture of user (at the right side) logs off the account.

System Design Phase

19


ILLUMINSIA INVENTORY SYSTEM

4.

Owner Records

When the records button is clicked, transaction list will be seen. Three (3) buttons (at the top) are disabled which means buttons are not accessible by the owner. Clicking the Order data will show the billing information of the order. Clicking the filter record button allows the owner to filter records into: On-hand, Reserve and delivery List 5.

Database Setting

The database form allows owner to backed up (store a copy of the current database into a folder) and retrieve (get the copy of the database from the back-up to the current database). This form also opens your database directly without looking on folders. 6.

Product Inventory Reports

In the reports from, you will see a navigator showing the reports of the system. Clicking on the nodes of navigator and clicking the show data button will show a data of which the crystal report will also generate. On the screen, you will see a product inventory report selected at “imported - new�.Design Phase System

20


ILLUMINSIA INVENTORY SYSTEM

7.

Product Inventory Crystal Reports

This form will be shown after clicking generate crystal report button from the report form.

8.

Sales Report

The same with product inventory but differs in such that the sales report requires a date to filter records in terms of daily, weekly and monthly basis. 9.

Sales Crystal Report

System Design Phase

21


ILLUMINSIA INVENTORY SYSTEM

10. Invoice Report

When invoice report is clicked, a dialog will show up, showing a combo box consisting of the number of orders, allowing the owner to see a number of receipts given to the customer. 11. NET Income

12. NET Income Crystal Report

System Design Phase

22


ILLUMINSIA INVENTORY SYSTEM

13. System Setting – Employee Records The setting form shows the employee accounts, logs and system appearance for modification. The employee data grid shows all employees and on the side is the preview pane of the employee.

14. System Setting – Employee Modification

15. System Setting – Employee Suspend This dialog is to suspend an employee. Suspending an employee will disable employee from logging in for a while. 16. System Setting – Employee Block This dialog can block an employee to disable an account.

17. System Setting – Block Modification

This dialog will show up when a customer is blocked and the owner wants to modify the account: it has either of modifying or unblocking an account

System Design Phase

23


ILLUMINSIA INVENTORY SYSTEM

18. System Setting – Suspend Modification This dialog will show up when a customer is suspended and the owner wants to modify the account: it has either of modifying or unsuspending an account

19. System Setting – Log History

The log history tab show a list of actions taken by the employee and owner including log, back-up, shutdown and etc. records can be filtered by time in ascending or descending order. 20. System Setting – Appearance

The system appearance tab allows the owner to modify wallpaper, background and palettes of the system for simple appearance modification.

System Design Phase

24


ILLUMINSIA INVENTORY SYSTEM 21. Transact (Order, Reserve and Delivery)

The transact form comprises of three (3) tabs: order, reserve and delivery. All three has the same order design, clicking the select existing will show dialog to select customer from record while adding new customer will add non existing record of customer. the product will be selected through a dialog. 22. Product Dialog Shows record of products to be selected in the order form. Product with stocks of zero(0) will not be selected and a prompt will show up. 23. Customer Dialog

This dialog shows a list of customer to be selected in the order.

System Design Phase

25


ILLUMINSIA INVENTORY SYSTEM 24. Transact 2 (Order, Reserve and Delivery)

The next page for the order consist of billing activities such as adding discount, tax, payment and due. This also includes printing of receipt optional to the customer buying the product. 25. Delivery (additional information)

System Design Phase

26


ILLUMINSIA INVENTORY SYSTEM 26. Order List

27. Reserve List

28. Delivery List

System Design Phase

27


ILLUMINSIA INVENTORY SYSTEM

29. Employee Records (Customer, Product and Supplier)

System Design Phase

28


ILLUMINSIA INVENTORY SYSTEM

30. Tools

This shows all tools available for use; some are for operational purpose and some are to entertain users.

System Design Phase

29


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 5 SYSTEM TESTING INTRODUCTION: Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and coding. In fact, testing is the one step in the software engineering process that could be viewed as destructive rather than constructive. A strategy for software testing integrates software test case design methods into a well-planned series of steps that result in the successful construction of software. Testing is the set of activities that can be planned in advance and conducted systematically. The underlying motivation of program testing is to affirm software quality with methods that can economically and effectively apply to both strategic to both large and small-scale systems.

UNIT TESTiNG: Unit testing focuses verification effort on the smallest unit of software design, the module. The unit testing we have is white box oriented and some modules the steps are conducted in parallel. 1. WHITE BOX TESTING This type of testing ensures that: All independent paths have been exercised at least once All logical decisions have been exercised on their true and false sides All loops are executed at their boundaries and within their operational bounds All internal data structures have been exercised to assure their validity. To follow the concept of white box testing we have tested each form .we have created independently to verify that Data flow is correct, All conditions are exercised to check their validity, All loops are executed on their boundaries. 2. BASIC PATH TESTING Established technique of flow graph with Cyclomatic complexity was used to derive test cases for all the functions. The main steps in deriving test cases were: Use the design of the code and draw correspondent flow graph. 3. CONDITIONAL TESTING In this part of the testing each of the conditions were tested to both true and false aspects. And all the resulting paths were tested. So that each path that may be generate on particular condition is traced to uncover any possible errors. 4. DATA FLOW TESTING This type of testing selects the path of the program according to the location of definition and use of variables. This kind of testing was used only when some local variable were declared. The definition-use chain method was used in this type of testing. These were particularly useful in nested statements. 5. LOOP TESTING In this type of testing all the loops are tested to all the limits possible. The following exercise was adopted for all loops: All the loops were tested at their limits, just above them and just below them. All the loops were skipped at least once. For nested loops test the inner most loop first and then work outwards. For concatenated loops the values of dependent loops were set with the help of connected loop. Unstructured loops were resolved into nested loops or concatenated loops and tested as above. Each unit has been separately tested by the development team itself and all the input have been validated.

System Testing

30


ILLUMINSIA INVENTORY SYSTEM

PROJECT TESTING: COMPILATION TEST: It was a good idea to do our stress testing early on, because it gave us time to fix some of the unexpected deadlocks and stability problems that only occurred when components were exposed to very high transaction volumes. EXECUTION TEST: This program was successfully loaded and executed. Because of good programming there were no execution errors. OUTPUT TEST: The successful output screens are placed in the output screens section

EVALUATION TESTING: This evaluation sheet is used to determine whether your client is satisfied with the requirement she demands. Other people can also give there comment as well about your project so that you may know whether the system that you created is good enough. INSTRUCTIONS: For evaluation of this software material you need to check the box that corresponds to a certain number. On the left side of the numerical rating is the equivalent of your chosen number. NUMERICAL RATINGS

EQUIVALENT

5 4 3

Excellent Very Good Good

2

Fair

1

Poor 5

4

3

2

1

A. FUNCTIONALITY 1.User-friendliness of the system 2.Accessibility of the system 3.Execution of the System Function 4.Provision for the comfort and convenience

B. CONTENT 1.Presentation of the Contents 2.Accuracy of the Contents

C. VISUAL 1.Colors,Fonts and Size 2.Images and System Layout

D. SYSTEM SECURITY 1.Data storage 2.Data reliability

Signature over printed Name

System Testing

31


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 6 SYSTEM IMPLEMENTATION 6.1

HARDWARE REQUIREMENTS This phase of the software development process deals with a brief study of different hardware used in the computerized system. There is a list of hardware materials used during the making and also during the use of the proposed system. As the new system to be made into a computerized functional system, requirement of a computer is must. All the hardware needed here are generally the basic configuration of a typical office computer. A list of the hardware requirement used in the system given below: Minimum Configuration: To run the application software of the system in the computer the minimum configuration required is as below: ● 233 MHz Pentium processor or other compatible. ● Intel Chipset Motherboard. ● 32 MB SD – RAM. ● 2 – 4 GB Hard – Disk. ● 4x Compact Disc drive or faster. ● 1.44 MB Floppy Disk Drive. ● Monitor [640 x 480 Display]. ● Keyboard. ● Mouse. ● Dot Matrix Printer.

6.2

SOFTWARE REQUIREMENTS Hardware requires software to make or run a system with the computer hardware. Collection of different types of hardware into a specific type from computer can perform but it cannot execute process on its own. For efficient and proper working of any system, software must be installed. Software may be in the form of operating system or application software. To make the Inventory and Sales system for Illuminasia, We too have used certain software which is listed below. The software’s used in the proposed system are the latest versions of them and can give up-to-date and perfect result of every process in the system. Their software comprises operating system and application software used in the system.

● ●

6.3

Operating System : Microsoft Windows with .NET 4 Framework Application Software : Microsoft Access 2000 and Above [back -end – tool] Microsoft Visual Studio 2010 [front – end – tool] Crystal Report for VS2010

NON FUNCTIONAL REQUIREMENTS Nonfunctional requirement refers to the capacity of the system beyond the functional requirements that you proposed, but it helps the system’s competence the same way your functional requirement does to the entire system.

System Implementation

32


ILLUMINSIA INVENTORY SYSTEM

Illuminasia Inventory System can change system background itself. This nonfunctional requirement has been modified to establish a user customization of the system itself. Only the Owner has this function. The System has tools embedded to provide ease of work and also entertainment. Tools embedded with system include customized image capture, image editor, notepad, system information provider, calculator, alarm and games. These tools are not included in our functionality but can reduce hassle of computing or saving any notes. The Program has been provided with hot keys. Hot keys provided with the system enable fast performance of transaction as well as efficiency of work. The System can be hid to notification area and not shown in the taskbar pane. One of the great functions of the system is hid to notification where it can be opened at any time without shutting down the whole application. This has been done to provide any other works in the computer without the program on the screen. It doesn’t even allocate much space in the desktop. Also, the System has the system picture for every employee. In order for the owner to orderly identify his/her employees in terms of looks and how their performance has been doing. The System also gives ability for the Owner to block or suspend a employee. This function disables the account of any employee when the owner desired to. Blocking of customer disables the employee from logging unless otherwise unblocked by the owner, while suspension of customer disables the logging of employee limited for a time required by the owner. Exportation of records to excel from data grid. Excel has been a former log book of Illuminasia, thus the ability of some records to be exported to excel can give extra credits to hassle of manually inputting records from the log book. Database can be retrieved and backed up. This function allows your system to back up before any database corruption.

System Implementation

33


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 7 DISCUSSION OF RESULTS

Discussion Of Results

34


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 8 SUMMARY & RECOMMENDATION SUMMARY: It has been a great pleasure for us to work on this exciting and challenging project. This project proved us that it provides practical knowledge of not only programming in VB.NET application and no some extent Windows Application and MS-ACCESS Server, but also about all handling procedure related with “Inventory and Sale System”. It also provides knowledge about the latest technology that will be in great demand for the future. This will provide better opportunities and guidance in future in developing projects independently Our futures plan is to make more features enriched software that can fulfill the users demand ADVANTAGES The project is identified by the merits of the system offered to the user. The merits of this project are as follows:        

The project has been appreciated by many users including my classmates, friends and etc. It is easy to use, since it uses the GUI provided in the user dialog. User friendly screens are provided. The usage of software increases the efficiency, decreases the effort. It has been thoroughly tested and implemented. Eye-catching designs make it more gradually appealing to the user. Error catching statements are applied in such to avoid crashing of the system. Additional features are compromised to accompany and entertain users with tools and games respectively.

RECOMMENDATIONS: Our future plan is to give a new form to our project which is a desktop application .Making more reliable, realistic with many extra features such as:       

Make our System project more informative, attractive and interactive to the user. Analyzing and designing software based on scientific survey rather than ordinary survey. Converting our desktop based project into website based with feature enriched which can support many more features that are not provided by an ordinary website. During project enhancement we will never forget to make software from user’s point of view rather than programming point of view. Providing user more entertainment such that they will not feel bore and can spend more time with enthusiastically and willingly. Try to make a web based application Less use of forms in the system for easy code correction.

Summary and Recommendation

35


ILLUMINSIA INVENTORY SYSTEM

CHAPTER 9 BIBLIOGRAPHY FOR VB.NET INSTALLATION www.support.mircosoft.com FOR MS-ACCESS INSTALLATION www.msdn.microsoft.com FOR CRYSTAL REPORT and TUTORIALS www.msdn.microsoft.com www.youtube.com www.google.com www. Sourcecodester.com FOR CODE REFERENCES www.Sourcecodester.com www.google.com www.youtube.com FOR VISUAL PROJECT INSTALLER ClickTeam Install Creator FOR OUR CLIENT AND INFORMATION Illuminasia Lights Inc. 2130 D Leveriza St., Buendia, Pasay City Mark Dumadag; Accounting Staff +63 09(08)9389219 / 833-3687

Bibliography

36


Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.