eztracker (final)
TRANSCRIPT
-
8/3/2019 EzTracker (FINAL)
1/91
-
8/3/2019 EzTracker (FINAL)
2/91
EzTracker an Inventory Control System
ACKNOWLEDGEMENT
The authors would like to thank Mrs. Manesha Peiris for the given encouragement
and support throughout this whole process to make this project a success. Without
her continuous guidance, this project might have been harder to achieve the current
success.
Also, the manager of the New vista Telecommunication, Kandy Mr. Aruna
Andaramana should be given credit for his support in fact gathering and for allowing
the authors to develop the system.
In addition, special thank goes to all the fellow classmates in APIIT who was besideus to keep the spirit of the project alive, loving parents who always support us in
their best possible ways and the Academic and non-academic staffs of Asia Pacific
Institute of Information Technology for helping in countless ways to formulate this
master piece of work.
2Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
3/91
EzTracker an Inventory Control System
TABLE OF CONTENTS
ACKNOWLEDGEMENT............................................................................................1
TABLE OF CONTENTS.............................................................................................2LIST OF TABLES........................................................................................................4
TABLE OF FIGURES..................................................................................................6
1.0 Introduction.............................................................................................................7
1.1 Analysis of the existing system..........................................................................8
1.2 Identified problems in the existing system.........................................................8
1.3 Proposed solution................................................................................................9
1.4 Benefits.............................................................................................................10
1.5 Scope.................................................................................................................10
2.0 Feasibility Study...................................................................................................11
2.1 Schedule Feasibility..........................................................................................12
2.1.1 Work Load Matrix.....................................................................................12
2.1.2 Gantt Chart.................................................................................................14
2.2 Technical Feasibility.........................................................................................15
2.3 Operational Feasibility......................................................................................16
2.4 Economic Feasibility........................................................................................18
2.4.1 Cost Benefit Analysis................................................................................18
3.0 Systems Development Methodology....................................................................22
3.1 System Development Life Cycle......................................................................23
4.0 Requirement Gathering.........................................................................................26
4.1 Observation.......................................................................................................26
4.2 Interview...........................................................................................................27
4.3 Questionnaires..................................................................................................275.0 System Analysis....................................................................................................29
5.1 Data Flow Diagrams.........................................................................................29
5.1.1 Context Diagram........................................................................................29
5.1.2 Level 0 Diagram........................................................................................30
5.1.3 Level 1 Diagrams.......................................................................................31
5.2 Data Dictionary.................................................................................................34
5.2.1 External Entities.........................................................................................34
5.2.2 Data Flows.................................................................................................36
3Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
4/91
EzTracker an Inventory Control System
5.2.3 Data Stores.................................................................................................51
6.0 Implementation.....................................................................................................54
6.1 Implementation Strategy Selection for the System...........................................56
7.0 Testing..................................................................................................................57
7.1 Testing methodology research..........................................................................57
7.1.1 Black box testing.......................................................................................57
7.1.2 White box testing.......................................................................................59
7.1.3 Daily build and smoke test........................................................................61
7.2 Testing plan for the system...............................................................................63
7.3 Sample Testing Report.....................................................................................64
7.4 Future Enhancements........................................................................................65
8.0 Conclusion............................................................................................................66
REFERENCES...........................................................................................................67
APPENDIX.................................................................................................................68
Appendix A: Minutes of Weekly Meetings............................................................68
Appendix B: Interview Report................................................................................83
Appendix C: Sample Questionnaires......................................................................85
Appendix D: Work Breakdown Structure..............................................................87
Appendix E: Testing Reports..................................................................................88Appendix E: Testing Reports
4Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
5/91
-
8/3/2019 EzTracker (FINAL)
6/91
EzTracker an Inventory Control System
Table 48: Data Dictionary for SIM Registration File.................................................52
Table 49: Data Dictionary for Supplier File...............................................................52
Table 50: Data Dictionary for Stock File....................................................................52
Table 51: Data Dictionary for Invoice File.................................................................53
Table 51: Data Dictionary for Invoice File
TABLE OF FIGURES
Figure 1: SDLC Phases...............................................................................................24
Figure 2: Context Diagram of EzTracker...................................................................27
6Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
7/91
EzTracker an Inventory Control System
Figure 3: Level 0 Diagram of EzTracker....................................................................28
Figure 4 : Level 1 Diagram for 1.0 Access Control Process......................................29
Figure 5 : Level 1 Diagram for 2.0 SIM Registration Process...................................29
Figure 6 : Level 1 Diagram for 3.0 Stock Registration Process.................................30
Figure 7 : Level 1 Diagram for 4.0 Sale Process........................................................30
Figure 8 : Level 1 Diagram for 5.0 Report Generating Process.................................31
Figure 9: Work Breakdown Structure.........................................................................72
Figure 9: Work Breakdown Structure
1.0 Introduction
7Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
8/91
EzTracker an Inventory Control System
This is the Project proposal for the System Analysis and Design group
assignment which is required to successfully complete the Systems Analysis and
Design module of Level 1 (Diploma) in B.Sc. (Hons) Computing at Asia Pacific
Institute of Information Technology.
In order to achieve it, EzTracker - an Inventory Control System for a
communication was proposed.
New Vista Telecommunication is located at Kandy, Sri Lanka which performs
several functions as follows;
Provide telecommunication facility
Fax facility
Laminating facility
Selling of items such as
Mobile Phones
SIM Cards
Mobile Accessories
And this project will analyze problems in the current inventory control
system of New Vista Telecommunication and provide better solutions for the
development of the company.
1.1 Analysis of the existing system
8Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
9/91
EzTracker an Inventory Control System
As for now, New Vista Telecommunication uses a manual system for
inventory control.
Once the supplier arrived, required amount of goods will be bought after
going through the current stock. When selling a SIM card, basic details of the
customer will be noted down for activation purpose. And for guaranteed items such
as Mobile phones and mobile phone accessories, a card which includes the guaranty
period and other necessary information.
Other than that, no other paper work or record keeping method is maintained
by the communication.
1.2 Identified problems in the existing system
As for usual, using a manual system for inventory controlling purpose is
taking a considerable time and also could effect on the accuracy of information and
efficiency.
When considering New Vista Telecommunication, their documentation
contains only the basic information about SIM card registrations. They arent
keeping further record of any other transaction. They arent maintaining a proper
inventory control method rather than going through the remaining stock at the
moment of buying new stocks. Even for guaranteed items, only the customer will
receive a guaranty card and there will be no other record to verify the guaranty
details. If a customer claimed for guarantee, there will be no information in the
communication to verify the accuracy of the purchased item.
In conclusion, New Vista Telecommunications existing inventory control
system is in a very poor level and it should be replaced in order to maintain a high
level of accuracy and efficiency.
1.3 Proposed solution
9Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
10/91
EzTracker an Inventory Control System
To enhance the efficiency and accuracy of New Vista
Telecommunications inventory control is through offering proper stock, supplier
and customer details management. For that EzTracker - a customized Inventory
Control System will be developed and implemented.
Characteristics of EzTracker system are as follow;
Components Stock Management, Customer details Management, Supplier
details Management.
Interrelated Components Orders, Sales
Boundary The system will be implemented on a single PC (Personal
Computer) only
Purpose Stock, Supplier and Customer details management of the
communication. Enhance the efficiency and the accuracy of the
communications inventory controlling.
E nvironment Customers, Suppliers and other shops with communication
facilities, mobile phones and accessory for sales.
Input Supplier details, Stock details, Customer details, Sales details
Output Supplier report, Customer detail report, Stock report, Sales report
Constraints System will be offering these functions only: Managing stock
according to a given single method, print monthly stock report, store
submitted supplier details, print supplier detail list, store submitted customer
details and print customer detail list.
Interfaces
Security Access Control to system. System will be only accessed by
authorized personals. Unauthorized access will be blocked using
password protection.
Filtering When taking Customer/Stock/Supplier/Sales details only
necessary data will be gathered and when printing a
Customer/Stock/Suppler/Sales report, only relevant details will be
printed.
Detecting and Correcting Errors System will validate the data
entered into the System at its submitting process and will inform to do
corrections if detected any errors.
Buffering In stock management, when stock reaches its reorderlevel, cashier will get an alert message regarding that.
10Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
11/91
EzTracker an Inventory Control System
Summarizing Supplier detail reports, Customer detail reports and
Stock reports will be available for cashier to view and print in a useful
way.
1.4 Benefits
Benefits of EzTracker system will be as follow;
All necessary information about suppliers and supplied stock will be stored in
the system.
SIM registration details will be recorded in the system,
When a customer bought Guaranteed Items, those will be recorded for further
uses such as in an event of a guarantee claim.
View/Print Customer details, Supplier details, Sales and Stock report
whenever wanted.
Notifications will be appear when stock reaches re-order level.
1.5 Scope
EzTracker will not exceed the scope mentioned below;
System will not focus on any accountancy areas
System will be able to view and modify SIM registration details, Guarantee
details, and stock details and to print those if necessary.
Password protection will be supplied with several User Access ability
System will be built using MS Access
Any other necessary sections could be added during the development if client
requested.
2.0 Feasibility Study
11Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
12/91
EzTracker an Inventory Control System
2.1 Schedule Feasibility
2.1.1 Work Load Matrix
Kasun Ashan Lakshika
12Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
13/91
EzTracker an Inventory Control System
1.0 Project Plan 50% 30% 20%
Project proposal 50% 30% 20%
Gantt chart 100%
Gantt chart verification 50% 50%
Work load matrix 100%
Work load matrix verification 50% 50%
Work breakdown structure 100%
Work breakdown structure verification 50% 50%
2.0 Investigation
Observation 20% 60% 20%
Interviews 100%
Questionnaires 30% 50% 20%
Questionnaire preparation 60% 40%
Questionnaire completion 100%
30 System Development Methodology
- Research on System development
methodologies
34% 33% 33%
- SDLC research 100%
4.0 Analysis of the current System * * *
Study the system 30% 35% 35%
Identify problems of the system 30% 35% 35%
Identify requirements for the system 25% 35% 40%
5.0 Technology Research 50% 30% 20%
Software and devices 50% 50%
Feasibility Study
- Technical feasibility 100%
13Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
14/91
EzTracker an Inventory Control System
- Schedule feasibility 100%
- Operational feasibility 100%
- Economical feasibility 100%
6.0 Designing * * *
Data Flow Diagrams
- Context diagram 60% 20% 30%
- Level 0 diagram 50% 25% 25%
- Level 1 diagram 50% 25% 25%
Data Dictionary 100%
Interfaces
- for Access Control 100%
- for SIM Registration 100%
- for Stock Registration 100%
- for Sales 100%
7.0 Testing 43% 26% 31%
Testing strategy research 40% 60%
Testing strategy selection 40% 30% 30%
Testing plan 100%
Testing the system 33% 33% 34%
8.0 Project Finalization 34% 35% 31%
Finalizing softcopy 70% 20% 10%
Verify softcopy finalization 50% 50%
Finalizing hardcopy 33% 34% 33%
9.0 Presentation
Preparation for the final presentation 34% 33% 33%
14Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
15/91
EzTracker an Inventory Control System
Table 1: Workload Matrix
2.1.2 Gantt Chart
15Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
16/91
EzTracker an Inventory Control System
2.2 Technical Feasibility
To use EzTracker System, New Vista Telecommunication needs a desktop
computer or a laptop device, printer for reports and bill printing and training for the
user of the system.
Currently, the communication doesnt possess above required technology. Therefore,
they will have to acquire technology as mentioned below;
Recommended specifications for the required computer/laptop:
16Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
17/91
EzTracker an Inventory Control System
512MB RAM
Pentium 4 or higher processor
Any version of Windows XP or higher
MS Office software
40GB hard disk space
Keyboard and mouse
Dot-Matrix or Ink-Jet Printer (only if needed to print reports and bills)
A Basic Training for the user of the system
2.3 Operational Feasibility
PIECES framework was conducted on the communication center and the following
problems were identified within the current system the shop uses.
2.3.1 Performance
The through put and the response time of the existing system is very quick as there is
no paper work or anything involved in the operational process for sales items such as
batteries, stationary items. But the details which are taken to SIM activation process
17Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
18/91
EzTracker an Inventory Control System
takes a slow rate of response time since everything has to be noted in papers and if
they are to find an entry, it takes a higher amount of time.
2.3.2 Information
Since the current system doesnt record the transaction details the manager is not
provided with accurate information about the operation of the communication.
2.3.3 Economy
The current system does provide a cost effective systems since the tangible cost is
only paper material. But on the other hand, many loop holes are found in the system
such as if the customer loses the sticker which the company provided with the items
such as battery, they are not repaired. By implementing this information system
intangible benefits such as customer satisfaction can be gained.
2.3.4 Control
The current system doesnt provide any assist with security of the data. For an
example the cashier could fraud since there are no evidences of accounting. This is a
vital failure of the existing system. Thus, correcting this is a necessity.
2.3.5 Efficiency
As observed the current systems such as registering of SIM cards is a burden to the
cashier as it takes time. This can be rectified by implementing a system to deal with
it. Other than that since the response time as discussed is minimized, the efficiency is
maintained. Usually to do a normal transaction such as selling a phone cover takes
about 1-2 minutes in normal hours and 1-5 minutes in rush hours.
2.3.6 Services
18Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
19/91
EzTracker an Inventory Control System
Like discussed the customer satisfaction is not up to the standard. This reduces the
flexibility of the system. The services can be improved by implementing an
information system to record the details of the customers and provide them with
better services, Instead of considering the sticker that is pasted on the item.
Following are the functions that are available in the communication centre.
Provide telecommunication facility
Fax facility
Laminating facility
Selling of items such as
Mobile Phones
SIM Cards
Mobile Accessories
2.4 Economic Feasibility
2.4.1 Cost Benefit Analysis
Costs
Estimated Developmental Costs
Cost Type Cost (Rs.)
Personal Salary
System Analyst 75 000.00
19Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
20/91
EzTracker an Inventory Control System
Programmer & Developer
System Architect & GUI Designer
Training expenses
Initial User Training
Hardware purchase
Personal Computer
Printer
Software Purchase
MS Office
Software License
Total Developmental Costs
60 000.00
50 000.00
10 000.00
25 000.00
5 000.00
11 500.00
6 000.00
242 500.00
Estimated Annual Operational Costs
Cost Type Cost (Rs.)
Personal Salary
Cashier
System Maintenance
Ongoing Training
System Maintenance & Modifications
180 000.00
10 000.00
60 000.00
20Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
21/91
EzTracker an Inventory Control System
Other Expenses
Printing Papers, Cartridges & Stationary
Electricity Bill
Total Operational Costs
50 000.00
36 000.00
336 000.00
Intangible Costs
The time for Billing process is increased which results in dissatisfaction
of the customers who purchase limited number of items.
Benefits
Intangible Benefits
Higher employee morale
Customer satisfaction
Less time consumption in Inventory Control.
Supplier satisfaction.
Tangible Benefits
21Asia Pacific Institute of Information Technology
Benefit Type Cost (Rs.)
Error Reduction & More Accuracy
Improved Inventory Management & Control
Accelerated Speed of Transactions
Opening New Markets
Increasing Sales Opportunities
Total tangible Benefits
24 000.00
50 000.00
100 000.00
70 000.00
180 000.00
42 4 000.00
-
8/3/2019 EzTracker (FINAL)
22/91
EzTracker an Inventory Control System
Payback Analysis
Payback Period = 2 + [ (928 500 874 000) / (495 000 365 000) ] years
= 2.419230 years
= 2 years & 5 months
It will take 2 years and 8 months to accomplish the payback.
Return On Investment Analysis
ROI = ( Total Benefits Total Costs ) / Total Costs * 100
= ( 2 539 000.00 2 086 500.00) / 2 086 500.00 * 100
22Asia Pacific Institute of Information Technology
Year Costs Cumulative
Costs
Benefits Cumulative
Benefits
Year 0 242 500.00 242 500.00 - -
Year 1 336 000.00 578 500.00 424
000.00
424 000.00
Year 2 350 000.00 928 500.00 450
000.00
874 000.00
Year 3 365 000.00 1 293
500.00
495
000.00
1 369 000.00
Year 4 383 000.00 1 676
500.00
555
000.00
1 924 000.00
Year 5 410 000.00 2 086
500.00
615
000.00
2 539 000.00
-
8/3/2019 EzTracker (FINAL)
23/91
EzTracker an Inventory Control System
= 0.216870 * 100
= 21.6870 %
3.0 Systems Development Methodology
Systems Development Methodology is a standard process followed in an
organization to conduct all the steps necessary to analyze, design, implement &
maintain Information Systems.(Hoffer, 2004)
23Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
24/91
EzTracker an Inventory Control System
Importance of System Development Methodology:(Lecture Notes- AAPP007-3-2,
2010)
To ensure consistency in management of projects
To ensure easier estimation of project times & costs
Reduce time & cost
To improve the quality of work & system
Produce complete & accurate design specification & documentation
Meet user requirement
Some of the Systems Development Methodologies used in present are;
(Lecture Notes- AAPP007-3-2, 2010)
Prototyping:
Designing and building a scaled-down but working version of a desired
version.
1. Evolutionary Prototyping
2. Throwaway Prototyping
Joint Application Design (JAD):
A structured process in which users, managers & analysts work together for
several days in a serious of intensive meetings to specify or review system
requirements.
Object-Oriented Analysis & Design (OOAD):
System development methodologies & techniques based on objects rather
than data or processes
Rapid Application Development (RAD):
Team based development method that speeds up systems development
24Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
25/91
EzTracker an Inventory Control System
In this project we have chosen System Development Life Cycle as the Systems
Development Methodology in order to create a complete & an accurate information
system.
3.1 System Development Life Cycle
System Development Life Cycle is a methodology which used to develop, maintain,
and replace information systems.(Hoffer, 2004)
Advantages in Systems Development Life Cycle:
(Lecture Notes- AAPP007-3-2, 2010)
Highly Structured, systematic process
Thorough definition requirements
Clear milestones with management sign-offs
Disadvantages in Systems Development Life Cycle:
(Lecture Notes- AAPP007-3-2, 2010)
May ignore evolving requirements during project
Time-consuming, costly process
Top-down commitment required
3.1.1 Phases in System Development Life Cycle
(Lecture Notes- AAPP007-3-2, 2010)
25Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
26/91
EzTracker an Inventory Control System
Figure 1: SDLC Phases
1. Identifying problems, opportunities & objectives
Identifying problems in the current system
Identifying the opportunities which can be enhanced by the new
computerized system.
Identifying the objectives of the company & see whether these
objectives can be achieved through this system
Estimate the scope of the system
Generating Feasibility reports
This phase is discussed in details in theIntroduction
1. Determining Information Requirements
Through interviews & Questionnaires identifying the current systems
functions, procedures & the people involved in it.
This phase is discussed in details in 3.0 Requirement Gathering
1. Analyzing system needs
Analyzing the systems requirements by creating Data Flow Diagrams
& Data Dictionary
Preparing system proposal
This phase is discussed in details in 4.0 System Analysis
1. Designing the recommended system
26Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
27/91
EzTracker an Inventory Control System
Designing the logical design of the system by designing user friendly
& accurate interfaces & files
This phase is discussed in details thoroughly in *
1. Developing & documenting software
Developing the original system
Developing the documentation for the users such as manuals & user
guides
1. Testing & maintaining the system
Selecting a method & a technique for testing
Maintaining the testing
This phase is discussed thoroughly in 6.0 Testing
1. Implementing & evaluating the system
Transferring smoothly from older system to the new system by conducting
Training programs, installing software etc.
Selecting an Implementation Strategy
This phase is discussed thoroughly in 5.0 Implementation
4.0 Requirement Gathering
Requirement gathering was achieved using following methods:
27Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
28/91
EzTracker an Inventory Control System
Observation
Interviews
Questionnaires
4.1 Observation
Vista communication is a telecommunication where it performs several functions as
follows.
Provide telecommunication facility
Fax facility
Laminating facility
Selling of items such as follows
Mobile phones
SIM cards
Phone covers
Batteries
Chargers
In our context as we are going to make an inventory control system. We look in to
the function of buying and selling items. The process is done according to the
following sequence,
Once the suppliers come in to the shop, the required goods are brought after going
through the stock. When selling SIM cards basic details of the borrower is taken by
the shop for guaranteed items such as phones, batteries and chargers. Once this is
done a card is issued containing the guarantee period and other necessaryinformation.
4.2 Interview
Interviews are attached in Appendix B: Interview Report.
28Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
29/91
EzTracker an Inventory Control System
4.3 Questionnaires
Questionnaires are attached in Appendix C: Sample Questionnaires.
29Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
30/91
EzTracker an Inventory Control System
Above is an abstract idea of how the existing system of the communication centre
performs. After observing this process for a while following problems were
encountered during the process.
Once a customer came up with a battery stating that he purchase it from this
communication center and is not working. The customer had no proof to
support his argument. But still the manager had to give out a new battery to
him to keep up his businesses. Thus from the above scenario identified that
trust plays its role. These are problems which cannot be solved even if the
computer system is implemented.
The response time of the current system varies from 1- 5 minute dependingon the time of the day and the item which is purchased. But sometimes there
is a risk that if the system is implemented, this could take a longer period of
time since factors such as the speed of the cashier to enter data, condition of
the computer equipments add on to the above mentioned criterion.
The current stock could not be checked when the vendors come to sell their
items. The cashier or the manager has to go through the stock to find it out.
This can be easily rectified by having an option to check the current stock in
the automated system which is going to be implemented.
The rates which are given to the items are not fixed when it comes to selling
the goods. The cashier lowers the price so as to meet the satisfactory level of
the customer. This might become a hindrance in implementing the
computerized system since the rates are fixed and thus result in accounting
errors.
30Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
31/91
EzTracker an Inventory Control System
5.0 System Analysis
5.1 Data Flow Diagrams
5.1.1 Context Diagram
Figure 2: Context Diagram of EzTracker
31Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
32/91
EzTracker an Inventory Control System
5.1.2 Level 0 Diagram
Figure 3: Level 0 Diagram of EzTracker
32Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
33/91
EzTracker an Inventory Control System
5.1.3 Level 1 Diagrams
Level 1 Diagram for 1.0 Access Control Process
Figure 4 : Level 1 Diagram for 1.0 Access Control Process
Level 1 Diagram for 2.0 SIM Registration Process
Figure 5 : Level 1 Diagram for 2.0 SIM Registration Process
33Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
34/91
EzTracker an Inventory Control System
Level 1 Diagram for 3.0 Stock Registration Process
Figure 6 : Level 1 Diagram for 3.0 Stock Registration Process
Level 1 Diagram for 4.0 Sale Process
34Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
35/91
EzTracker an Inventory Control System
Figure 7 : Level 1 Diagram for 4.0 Sale Process
Level 1 Diagram for 5.0 Report Generation Process
35Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
36/91
EzTracker an Inventory Control System
Figure 8 : Level 1 Diagram for 5.0 Report Generating Process
36Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
37/91
EzTracker an Inventory Control System
5.2 Data Dictionary
5.2.1 External Entities
Name Owner
Description
Owner gives Login Details to create/edit
user accounts. By giving New Login
Details Owner can login to the system in
order to receive SIM stock details, SIM
registration details, SIM supplier details,
stock details, supplier details & Invoice
details.
Data Inflow
Login Verification, Registered SIM
Stock Details, Registered SIM
Registration Details, Registered SIM
Supplier Details, Registered Stock
Details, Registered Supplier Details,
Registered Invoice Details
Data Outflow Login Details, New Login Details
Table 6: Data Dictionary for the External Entity Owner
Name Supplier
Description
Supplier gives SIM Details & SIM
Supplier Details in order to register SIM
supplier & SIM stocks. Giving SupplierDetails & Stock Details supplier can
register supplier & stocks in the system.
Data Inflow -
Data OutflowSIM Supplier Details, SIM Details,
Supplier Details, Stock Details
37Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
38/91
EzTracker an Inventory Control System
Table 7: Data Dictionary for the External Entity Supplier
Name Customer
Description
Customer gives his details for SIM
registration. In the sales process
Customer gives Purchasing Details in
order to receive a verified Invoice.
Data Inflow Verified Invoice
Data Outflow Customer Details, Purchasing Details
Table 8: Data Dictionary for the External Entity Customer
38Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
39/91
EzTracker an Inventory Control System
5.2.2 Data Flows
Name New Login Details
DescriptionNew Login Details in order to create or
edit user account
Origin / Source Owner
Destination / Sink 1.1 Create/Edit User Account Process
Data Structure New User ID & Password
Table 9: Data Dictionary for Data Flow of New Login Details
Name Registered Login Details
DescriptionVerified Login Details assigned store in
User File
Origin / Source 1.1 Create Edit User Account Process
Destination / Sink D1 User File
Data Structure Verified New User ID & Password
Table 10: Data Dictionary for Data Flow of Registered Login Details
Name Login Details
DescriptionLogin Details in order to login to the
system
Origin / Source Owner
Destination / Sink 1.2 Login Verification Process
Data Structure User Name & ID
Table 11: Data Dictionary for Data Flow of Login Details
39Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
40/91
EzTracker an Inventory Control System
Name Login Details
DescriptionCurrent Login Details in order to verify
User inputted Login Details
Origin / Source D1 User File
Destination / Sink 1.2 Login Verification Process
Data Structure Current User Name & IDTable 12: Data Dictionary for Data Flow of Login Details
Name Login Verification
DescriptionLogin Verification Details which will be
sent to the Owner
Origin / Source 1.2 Login Verification Process
Destination / Sink Owner
Data StructureMessage about Successful login or
Unsuccessful login
Table 13: Data Dictionary for Login Verification
Name SIM Supplier Details
DescriptionSIM Supplier Details for Supplier
Registration
Origin / Source Supplier
Destination / Sink 2.1 SIM Supplier Registration Process
Data StructureSupplier Name, Address, Telephone
Number, Email Address (Optional)
40Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
41/91
EzTracker an Inventory Control System
Table 14: Data Dictionary for Data Flow of SIM Supplier Details
Name Verified SIM Supplier Details
DescriptionVerified SIM Supplier details assigned to
store in SIM Supplier File
Origin / Source 2.1 SIM Supplier Registration Process
Destination / Sink D2 SIM Supplier File
Data Structure
Verified Supplier Name, Supplier ID,
Address, Telephone Number, Email
Address (Optional)
Table 15: Data Dictionary for Data Flow of Verified SIM Supplier Details
Name SIM Details
Description SIM Details for SIM Stock Registration
Origin / Source Supplier
Destination / Sink 2.2 SIM Stock Registration Process
Data Structure Provider Name, SIM Code, SIM Number
Table 16: Data Dictionary for Data Flow of SIM Details
41Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
42/91
EzTracker an Inventory Control System
Name Registered SIM Supplier Details
Description
Details on the related SIM Supplier in
order to prepare verified SIM Supplier
Details
Origin / Source D2 SIM Supplier File
Destination / Sink 2.2 SIM Stock Registration Process
Data Structure
Registered Supplier Name, Supplier ID,
Address, Telephone Number, Email
(Optional)
Table 17: Data Dictionary for Data Flow of Registered SIM Supplier Details
Name Verified SIM Stock Details
DescriptionVerified SIM Stock Details assigned to
store in SIM Stock File
Origin / Source 2.2 SIM Stock Registration Process
Destination / Sink D3 SIM Stock File
Data StructureVerified Provider Name, SIM ID, SIM
Code, SIM Number
Table 18: Data Flow of Verified SIM Stock Details
Name Customer Details
Description Customer Details for SIM Registration
Origin / Source Customer
Destination / Sink 2.3 SIM Registration Process
42Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
43/91
EzTracker an Inventory Control System
Data StructureCustomer Name, Address, Contact
Number, Comments (Optional)
Table 19: Data Dictionary for Data Flow of Customer Details
Name Registered SIM Stock Details
DescriptionRegistered SIM Stock Details for SIM
Registration
Origin / Source D3 SIM Stock File
Destination / Sink 2.3 SIM Registration Process
Data StructureRegistered Provider Name, SIM ID, SIM
Code, SIM Number
Table 20: Data Dictionary for Data Flow of Registered SIM Stock Details
Name Verified SIM Registration Details
Description
Verified SIM Registration Details
assigned to store in SIM Registration
Process
Origin / Source 2.3 SIM Registration Process
Destination / Sink D4 SIM Registration File
Data Structure
Verified Customer Name, Customer ID,
Address, Contact Number, Comments
(Optional), Registered Provider Name,
SIM ID, SIM Code, SIM Number
Table 21: Data Dictionary for Data Flow of Verified SIM Registration Details
Name Supplier Details
Description Supplier Details for Supplier Registration
43Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
44/91
EzTracker an Inventory Control System
Origin / Source Supplier
Destination / Sink 3.1 Supplier Registration Process
Data Structure
Supplier Group, Name, Product Details,
Address, Telephone Number, Email(Optional)
Table 22: Data Dictionary for Data Flow of Supplier Details
Name Verified Supplier Details
DescriptionSupplier Details which are verified and
assigned to store in Supplier File
Origin / Source 3.1 Supplier Registration Process
Destination / Sink D5 Supplier File
Data Structure
Verified Supplier Group, Name, Supplier
ID, Product Details, Address, Telephone
Number, Email (Optional)
Table 23: Data Dictionary for Data flow of Verified Supplier Details
Name Stock Details
Description Stock Details for Stock Registration
Origin / Source Supplier
Destination / Sink 3.2 Stock Registration Process
Data StructureStock Group, Stock Name, Quantity,
Unit Price, Guarantee Details (Optional)
Table 24: Data Dictionary for Data Flow of Stock Details
Name Registered Supplier Detail
DescriptionRegistered Supplier Details in order to
prepare Verified Stock Details
44Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
45/91
EzTracker an Inventory Control System
Origin / Source D5 Supplier File
Destination / Sink 3.2 Stock Registration Process
Data Structure
Registered Supplier Group, Name,
Supplier ID, Product Details, Address,Telephone Number, Email (Optional)
Table 25: Data Dictionary for Data Flow of Registered Supplier Details
Name Verified Stock Details
DescriptionStock Details which are verified &
assigned to store in the Stock File
Origin / Source 3.2 Stock Registration Process
Destination / Sink D6 Stock File
Data Structure
Verified Stock Group, Stock Name,
Stock ID, Quantity, Unit Price,
Guarantee Details (Optional)
Table 26: Data Dictionary for Data Flow of Stock Details
Name Purchasing Details
DescriptionPurchasing Details in order to gather
Sales Data
Origin / Source Customer
Destination / Sink 4.1 Gather Sales Data Process
Data StructureItem Group, Item Name, Supplier Name,
Quantity, Customer Details (Optional)
Table 27: Data Dictionary for Data Flow of Purchasing Details
45Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
46/91
EzTracker an Inventory Control System
Name Registered Stock Details
DescriptionRegistered Stock Details in order to
gather Sales Data
Origin / Source D6 Stock File
Destination / Sink 4.1 Gather Sales Data process
Data Structure
Registered Stock Group, Stock Name,
Stock ID, Unit Price, Guarantee Details
(Optional)
Table 28: Data Dictionary for Data Flow of Registered Stock Details
Name Sales Details
Description
Sales Details in order to identify
guarantee details if needed & create
Invoice Details.
Origin / Source 4.1 Gather Sales Data Process
Destination / Sink 4.2 Guarantee Process
Data Structure
Item Name, Supplier Name, Quantity,
Customer Details (Optional), Customer
ID(Optional), Registered Stock Group,
Stock Name, Stock ID, Unit Price,
Guarantee Details (Optional)
Table 29: Data Dictionary for Data Flow for Sales Details
Name Invoice Details
DescriptionInvoice Details which are used to create
Invoice
Origin / Source 4.2 Guarantee Process
46Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
47/91
EzTracker an Inventory Control System
Destination / Sink 4.3 Create an Invoice Process
Data Structure
Item Name, Unit Price, Quantity, Total
Price, Stock ID, Supplier Name,
Guarantee Details (Optional), Customer
Details (Optional)
Table 30: Data Dictionary for Data Flow of Invoice Details
Name Verified Invoice
DescriptionVerified Invoice which should be send to
Customer
Origin / Source 4.3 Create an Invoice Process
Destination / Sink Customer
Data Structure
Verified Item Name, Unit Price,
Quantity, Total Price, Stock ID, Supplier
Name, Guarantee Details (Optional),
Customer Details (Optional)
Table 31: Data Dictionary for Data Flow of Verified Invoice
Name Verified Invoice Details
DescriptionVerified details on Invoices which are
assigned to store in Invoice File
Origin / Source 4.3 Create an Invoice Process
47Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
48/91
EzTracker an Inventory Control System
Destination / Sink D7 Invoice File
Data Structure
Verified Item Name, Unit Price,
Quantity, Total Price, Stock ID, Supplier
Name, Guarantee Details (Optional),Customer Details (Optional)
Table 32: Data Dictionary for Data Flow of Verified Invoice Details
Name Registered SIM Supplier Details
DescriptionRegistered SIM Supplier Details to
generate SIM Supplier Details Report
Origin / Source D2 SIM Supplier File
Destination / Sink5.1 SIM Supplier Details Report
Generating Process
Data Structure
Verified Supplier Name, Supplier ID,Address, Telephone Number, Email
Address (Optional)
Table 33: Data Dictionary for Data Flow of Registered SIM Supplier Details
Name SIM Supplier Details Report
Description
SIM Supplier Details Report for the
Owner
48Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
49/91
EzTracker an Inventory Control System
Origin / Source5.1 SIM Supplier Details Report
Generating Process
Destination / Sink Owner
Data Structure
Verified Supplier Name, Supplier ID,
Address, Telephone Number, Email
Address (Optional)
Table 34: Data Dictionary for Data Flow of SIM Supplier Details Report
Name Registered SIM Stock Details
DescriptionRegistered SIM Stock Details to generate
SIM Stock Details Report
Origin / Source D3 SIM Stock File
Destination / Sink5.2 SIM Stock Details Report Generating
Process
Data Structure
Verified Provider Name, SIM ID, SIM
Code, SIM Number, Registered Supplier
Name, Supplier ID, Address, Telephone
Number, Email (Optional)
Table 35: Data Dictionary for Data Flow of SIM Supplier Details Report
Name SIM Stock Details Report
49Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
50/91
EzTracker an Inventory Control System
Description SIM Stock Details Report for the Owner
Origin / Source5.2 SIM Stock Details Report Generating
Process
Destination / Sink Owner
Data Structure
Verified Provider Name, SIM ID, SIM
Code, SIM Number, Registered Supplier
Name, Supplier ID, Address, Telephone
Number, Email (Optional)
Table 36: Data Dictionary for Data Flow SIM Stock Details Report
Name Registered SIM Registration Details
Description
Registered SIM Registration Details in
order to generate SIM Registration
Details Report
Origin / Source D4 SIM Registration File
Destination / Sink5.3 SIM Registration Details Report
Generating Process
Data Structure
Registered Customer Name, Customer
ID, Address, Contact Number,
Comments (Optional), Provider Name,
SIM ID, SIM Code, SIM Number
Table 37: Data Dictionary for Data Flow of Registered SIM Registration Details
50Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
51/91
EzTracker an Inventory Control System
Name SIM Registration Details Report
DescriptionSIM Registration Details Report for the
Owner
Origin / Source5.3 SIM Registration Details Report
Generating Process
Destination / Sink Owner
Data Structure
Registered Customer Name, Customer
ID, Address, Contact Number,
Comments (Optional), Provider Name,
SIM ID, SIM Code, SIM Number
Table 38: Data Dictionary for Data Flow of SIM Registration Details Report
Name Registered Supplier Details
DescriptionRegistered Supplier Details to generate
Supplier Details Report
Origin / Source D5 Supplier File
Destination / Sink5.4 Supplier Details Report Generating
Process
Data Structure
Registered Supplier Group, Name,
Supplier ID, Product Details, Address,
Telephone Number, Email (Optional)
Table 39: Data Dictionary for Data Flow of Registered Supplier Details
51Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
52/91
EzTracker an Inventory Control System
Name Supplier Details Report
Description Supplier Details Report for the Owner
Origin / Source5.4 Supplier Details Report Generating
Process
Destination / Sink Owner
Data Structure
Registered Supplier Group, Name,
Supplier ID, Product Details, Address,
Telephone Number, Email (Optional)
Table 40: Data Dictionary for Data Flow of Supplier Details Report
Name Registered Stock Details
DescriptionRegistered Stock Details to generate
Stock Details Report
Origin / Source D6 Stock File
Destination / Sink5.5 Stock Details Report Generating
Process
Data Structure
Registered Stock Group, Stock Name,
Stock ID, Quantity, Unit Price,Guarantee Details (Optional), Supplier
Group, Name, Supplier ID, Product
Details, Address, Telephone Number,
Email (Optional)
Table 41: Data Dictionary for Data Flow of Supplier Details Report
Name Stock Details Report
Description Stock Details Report for the Owner
Origin / Source5.5 Stock Details Report Generating
Process
Destination / Sink Owner
52Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
53/91
EzTracker an Inventory Control System
Data Structure
Registered Stock Group, Stock Name,
Stock ID, Quantity, Unit Price,
Guarantee Details (Optional), Supplier
Group, Name, Supplier ID, Product
Details, Address, Telephone Number,
Email (Optional)
Table 42: Data Dictionary for Data Flow of Stock Details Report
Name Registered Invoice Details
DescriptionRegistered Invoice details to generate
Invoice Details Report
Origin / Source D7 Invoice File
Destination / Sink5.6 Invoice Details Report Generating
Process
Data Structure
Registered Item Name, Unit Price,
Quantity, Total Price, Stock ID, Supplier
Name, Guarantee Details (Optional),
Customer Details (Optional)
Table 43: Data Dictionary for Data Flow of Registered Invoice Details Report
Name Invoice Details Report
Description Invoice Details Report for the Owner
Origin / Source
5.6 Invoice Details Report Generating
Process
53Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
54/91
EzTracker an Inventory Control System
Destination / Sink Owner
Data Structure
Registered Item Name, Unit Price,
Quantity, Total Price, Stock ID, Supplier
Name, Guarantee Details (Optional),Customer Details (Optional)
Table 44: Data Dictionary for Data Flow of Invoice Details Report
5.2.3 Data Stores
Name D1 User File
Description Stores Login Details of the User
54Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
55/91
EzTracker an Inventory Control System
Accounts
Data Inflow Registered Login Details
Data Outflow Login Details
Data Structure User ID, Password
Table 45: Data Dictionary for User File
Name D2 SIM Supplier File
Description Stores SIM Supplier Details
Data Inflow Verified SIM Supplier Details
Data Outflow Registered SIM Supplier Details
Data StructureSupplier Name, Address, Telephone
Number, Email Address (Optional)
Table 46: Data Dictionary for SIM Supplier File
Name D3 SIM Stock File
Description Stores SIM Stock Details
Data Inflow Verified SIM Stock Details
Data Outflow Registered SIM Stock Details
Data StructureProvider Name, SIM ID, SIM Code, SIM
Number, Supplier Name
Table 47: Data Dictionary for SIM Stock File
Name D4 SIM Registration File
Description Stores SIM Registration Details
Data Inflow Verified SIM Registration Details
55Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
56/91
EzTracker an Inventory Control System
Data Outflow Registered SIM Registration Details
Data Structure
Customer Name, Customer ID, Address,
Contact Number, Comments (Optional),
Registered Provider Name, SIM ID, SIMCode, SIM Number
Table 48: Data Dictionary for SIM Registration File
Name D5 Supplier File
Description Stores Supplier Details
Data Inflow Verified Supplier Details
Data Outflow Registered Supplier Details
Data Structure
Verified Supplier Group, Name, Supplier
ID, Product Details, Address, Telephone
Number, Email (Optional)
Table 49: Data Dictionary for Supplier File
Name D6 Stock File
Description Stores Stock Details
Data Inflow Verified Stock Details
Data Outflow Registered Stock Details
Data Structure
Stock Group, Stock Name, Stock ID,
Quantity, Unit Price, Guarantee Details
(Optional)
Table 50: Data Dictionary for Stock File
Name D7 Invoice File
Description Stores Invoice Details
Data Inflow Verified Invoice Details
56Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
57/91
EzTracker an Inventory Control System
Data Outflow Registered Invoice Details
Data Structure
Item Name, Unit Price, Quantity, Total
Price, Stock ID, Supplier Name,Guarantee Details (Optional), Customer
Details (Optional)
Table 51: Data Dictionary for Invoice File
57Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
58/91
EzTracker an Inventory Control System
6.0 Implementation
Implementing & evaluating the System is an important phase of the Systems
Development Life Cycle as now the company transfers from the older system to thedeveloped new system. Certain set of steps are taken in order to make this transition
more safe & smooth.
Training the users
As the users in the inventory control system are used to work in a manual
system they are not familiar working in a computerized system. Therefore
giving them an initial training is very important in order to make them feel
comfortable with the new system & to enhance the accuracy of the activities
in the new system.
Installing the developed system
As this system introduce Information Systems to the company it is necessary
to fulfill the hardware requirements to the system. After installing the
necessary software the newly developed system can be installed.
Using the developed system
The installed inventory control system is now used by the company & now
the real performance of the system can be observed.
There are four main Implementation Strategies to transmit from older system to the
new system.
(Mark Kelly, 2010)
58Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
59/91
EzTracker an Inventory Control System
1. Cutover Strategy
The old system is stopped and the new system replaces it immediately. It is a
quick transition, which may be unnerving if the changes are large.
2. Phased Strategy
If the new system has several components, they can be introduced one at a
time. This takes more time, but each small step is less traumatic than one
huge one, and staff can become accustomed to one change before facing the
next. Also, problems with any step can be detected and fixed before the next
step is taken.
3. Pilot Strategy
If the organization has several branches or departments where the new
system will be implemented, it may decide to trial the new system in one
location first and see how it goes. Any faults and problems will be limited to
that one location and will not cripple the whole organization.
4. Parallel Strategy
If it is possible to keep the old system in place and running while the new
system is installed, you gain certain benefits.
You can directly compare the effectiveness and efficiency of the new
and old systems
If the new system fails, the old system is still there chugging away as
normal so no harm is done.
Parallel conversion is only possible if the old and new systems are completely
independent. It is impossible to achieve if the new system is built on the old
system.
59Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
60/91
EzTracker an Inventory Control System
6.1 Implementation Strategy Selection for the System
Cutover strategy is too risky for implementation as the users in the inventory control
system has never used an information system earlier. Therefore the probability to
have failures is fairly high.
Conducting Pilot & Phased Implementation Strategies for implementation will
provide fewer benefits as New Vista Telecommunication is fairly a small
organization with a limited number of functions.
Therefore Parallel Implementation Strategy is chosen for EzTracker Inventory
Control System to acquire more benefits as well as to ensure safety. As the oldsystem is manually controlled, the old system & new system is totally independent
which make it possible to run both systems at the same time. Parallel Implementation
ensures continuous pursuit in the organization though errors are encountered with the
new system.
60Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
61/91
EzTracker an Inventory Control System
7.0 Testing
7.1 Testing methodology research
7.1.1 Black box testing
Introduction
Black box testing is possible combinations of end-user actions. Black box testing
assumes no knowledge of code and is intended to simulate the end-user experience.
You can use sample applications to integrate and test the application block for black
box testing. You can begin planning for black box testing immediately after the
requirements and the functional specifications are available. ()
Therefore black box testing is a method of testing the system, which can be
performed by anybody who may not have a vast knowledge in program code. It
basically tests whether the system reacts the way it suppose to base on the inputs
given to it. Black box testing is done to make sure the system provides the desired
outputs for the given inputs.
The steps of the testing
1. Create test plans. Create prioritized test plans for black box testing.
2. Test the external interfaces. Test the external interfaces for various
types of inputs using automated test suites, such as NUnit suites and custom
prototype applications.
3. Perform load testing. Load test the application block to analyze the
behavior at various load levels. This ensures that it meets all performance
objectives that are stated as requirements.
4. Perform stress testing. Stress test the application block to analyze
various bottlenecks and to identify any issues visible only under extreme load
conditions, such as race conditions and contentions.
61Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
62/91
EzTracker an Inventory Control System
5. Perform security testing. Test for possible threats in deployment
scenarios. Deploy the application block in a simulated target environment and
try to hack the application by exploiting any possible weakness of the
application block.
6. Perform globalization testing. Execute test cases to ensure that the
application block can be integrated with applications targeted toward locales
other than the default locale used for development. ()
The planning for black box testing immediately after the requirements and the
functional specifications are available. ()
Though we can carry on black testing on many sections of the system, usually
the black testing is done to the areas of the system which are used by the user
frequently as it saves time as well as money.
Advantages & Disadvantages
The main advantage of this testing method is, the testing can be done soon after
the requirements & the fundamental specifications are obtained which allows the
testing to be done constantly. Reproducibility & the ability to test the
environment of the system are some of the benefits of the black box testing.
Another advantage of this testing method is the testers in black box testing
should not need to have a high programming knowledge which means the
company needs not to spend money to employ people with programming
knowledge to do the black box testing.
However there are some disadvantages in black box testing such as the difficulty
to identify the inputs & the inability to recognize the reasons for the failures
identified through testing as it only provides a symptom of the problem. This
results in both time & cost consumption. Another disadvantage identified in
black box testing is the inability to test all the features of the system.
62Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
63/91
EzTracker an Inventory Control System
7.1.2 White box testing
Introduction
White box testing is creating test cases by looking at the code to detect any
potential failure scenarios. You determine the suitable input data for testing various
APIs and the special code paths that need to be tested by analyzing the source code
for the application block. ()
Unlike in black box testing, white box testing cannot be conducted by a person with
a less knowledge in programming. As white box testing is a technique that verifies
the codes in the system, the tester should have a competing knowledge on
programming in order to do the testing.
The steps of the testing
1. Create test plans. Identify all white box test scenarios and prioritize them.
2. Profile the application block. This step involves studying the code at run
time to understand the resource utilization, time spent by various methodsand operations, areas in code that are not accessed, and so on.
3. Test the internal subroutines. This step ensures that the subroutines or the
nonpublic interfaces can handle all types of data appropriately.
4. Test loops and conditional statements. This step focuses on testing the
loops and conditional statements for accuracy and efficiency for different
data inputs.
5. Perform security testing. White box security testing helps you understand
possible security loopholes by looking at the way the code handles security.
()
White box testing requires access to the source code. Though white box testing can
be performed any time in the life cycle after the code is developed, it is a good
63Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
64/91
EzTracker an Inventory Control System
practice to perform white box testing during the unit testing phase.((Janardhanudu,
2005)
Accordingly any phase of the testing cannot be completed until the codes are
implemented which means until then the system should be implemented without
undergoing any testing which can be considered as a high risk.
Advantages & Disadvantages
The main advantage of the white box testing is unlike in black box testing if a
failure occurs the tester identifies the problem of the system during the testing
progress itself as he tests the codes of the system. This method of testing
provides a good view about the problem other than providing only a symptom.
This results in saving money & time that can be allocated to some other
process.
The disadvantage that can be identified in white box test is it consumes a lot
of time as the tester has to recheck all the codes thoroughly. Most of the effort
put in to testing is in vain as the percentage of inaccurate codes in the system
is very low comparing to the accurate codes in it. The company must employ
people with a good knowledge on programming for the white box testing
which ultimately results in low cost efficiency.
7.1.3 Daily build and smoke test
Introduction
64Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
65/91
EzTracker an Inventory Control System
In construction of extensive systems and programs, the key program is divided in to
various components and thus the development takes place accordingly. In daily build
and smoke test, the program is complied, linked and combined into an executable
program everyday and the testing is carried on a daily basis to bug the errors in the
code which was done on that specific day.(McConnell, 1996)
Procedure to do a daily build smoke test
Merge code changes upgrade the private copy of a developers source
file with the original and hence the code is added to the source file by an
automated code control tool.
Build and test the private build the added code is checked to see the
program runs smoothly.
Execute the smoke test- the smoke test is run in the developers source
file.
Check in- the source code of the private copies is checked in to the
master source file.
Generate the daily build- the build team upgrades the master source file
with the new changes made.
Run the smoke test- smoke test is done to the master file.
Fix any problems- if any errors are found the code is revised to be
corrected.(constux, 2010)
Why using the method and its benefits.
Reduces integration risk
As mentioned earlier a huge program would consist of hundreds of files which
should be combined to complete the full program. If the programmers try to
debug it at the end of the designing of the whole program and find errors this
leads to major downfalls since it is hard to integrate these components together.
But if the code is checked before the risk to integrate the system is very less
which is a major benefit of daily build and smoke test.
Perfects your Build Process
65Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
66/91
EzTracker an Inventory Control System
By testing the code daily a solid code is ensured by the programmers as the
program continues. Hence this reduces the time spent from development to
quality assurance.
Easier to diagnose errors of the program
For an example if the program is running smoothly on day 10 and the next day
the developers found a bug once the daily written code is added to the source
code, they come to know the exact area where the bug is.
Reduces rework
As the quality assurance is easier it is also to identify any derivations from user
specification in the program and the relevant measures can be immediately.
Improve the moral of the developers
Since the developers could see their program coming up with a strong build
process, and how accurate it is the moral of the developers also goes high.
Source: (McConnell, 1996)(Miller, 2010)
7.2 Testing plan for the system
Considering above research details, following steps will be used for testing the
System:
66Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
67/91
EzTracker an Inventory Control System
Testing team is consists of all the members of the project.
Each of them will go through Black Box testing for the verification of the outputs
of separated parts of the system.
White box testing will be used in the parts where manual coding was used. And it
would be assigned to Kasun Fernando.
After completion of the system Black box testing will be take place by group
members.
For final Black box test, a test report will be completed during the testing
process.
Test report will contain following:
Test items
Features to be tested
Features not to be tested
Approach
Item pass/fail criteria
Suspension criteria and resumption requirements
Test deliverables
Testing tasks
7.3 Sample Testing Report
67Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
68/91
EzTracker an Inventory Control System
Test
items
Feat
ures
to beteste
d
Featu
res
not to
be
tested
Appr
oach
p
a
s
s
/f
a
i
l
Suspensio
n criteria
and
resumptio
n
requirem
ents
Test
deliverable
Test
ing
task
s
Testing reports by each member in the testing group are attached in Appendix
E: Testing Reports.
68Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
69/91
EzTracker an Inventory Control System
69Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
70/91
EzTracker an Inventory Control System
7.4 Future Enhancements
70Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
71/91
EzTracker an Inventory Control System
8.0 Conclusion
71Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
72/91
EzTracker an Inventory Control System
REFERENCES
Anon., n.d. Microsoft corporation, MSDN library. [Online] Available at:
http://msdn.microsoft.com/en-us/library/ff649503.aspx [Accessed 22 July 2010].
constux, 2010. [Online] Available at: http://www.construx.com/Page.aspx?hid=1213
[Accessed 21 July 2010].
Hoffer, J.A..G.J.F..V.J.S., 2004. Modern Systems Analysis and Design. 4th ed.
Pearson Education, India.
Janardhanudu, G., 2005. The Build Security In (BSI) portal. [Online] Available at:
https://buildsecurityin.us-cert.gov/bsi/articles/best-practices/white-box/259-BSI.html
[Accessed 22 July 2010].
Lecture Notes- AAPP007-3-2, S.A.&.D., 2010. "Overview of SDLC-Part 1".
Lecture Notes- AAPP007-3-2,".A.&.D., 2010. Overview of SDLC-Part 2.
Mark Kelly, M.S.C., 2010. SDLC-Impement the Solution. [Online] Mark Kelly
Available at: http://vceit.com/SDLC/06-implementation/index.htm [Accessed 01
September 2010].
McConnell, S., 1996. [Online] Available at:
http://www.stevemcconnell.com/ieeesoftware/bp04.htm[Accessed 21 July 2010].
Miller, S., 2010. [Online] Available at:http://www.softwareplanner.com/newsletters/Newsletter_2010_05_SP.htm
[Accessed 21 July 2010].
72Asia Pacific Institute of Information Technology
http://msdn.microsoft.com/en-us/library/ff649503.aspxhttp://www.construx.com/Page.aspx?hid=1213https://buildsecurityin.us-cert.gov/bsi/articles/best-practices/white-box/259-BSI.htmlhttp://vceit.com/SDLC/06-implementation/index.htmhttp://www.stevemcconnell.com/ieeesoftware/bp04.htmhttp://www.stevemcconnell.com/ieeesoftware/bp04.htmhttp://www.softwareplanner.com/newsletters/Newsletter_2010_05_SP.htmhttp://msdn.microsoft.com/en-us/library/ff649503.aspxhttp://www.construx.com/Page.aspx?hid=1213https://buildsecurityin.us-cert.gov/bsi/articles/best-practices/white-box/259-BSI.htmlhttp://vceit.com/SDLC/06-implementation/index.htmhttp://www.stevemcconnell.com/ieeesoftware/bp04.htmhttp://www.softwareplanner.com/newsletters/Newsletter_2010_05_SP.htm -
8/3/2019 EzTracker (FINAL)
73/91
EzTracker an Inventory Control System
APPENDIX
Appendix A: Minutes of Weekly Meetings
73Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
74/91
EzTracker an Inventory Control System
74Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
75/91
EzTracker an Inventory Control System
75Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
76/91
EzTracker an Inventory Control System
76Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
77/91
EzTracker an Inventory Control System
77Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
78/91
EzTracker an Inventory Control System
78Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
79/91
-
8/3/2019 EzTracker (FINAL)
80/91
EzTracker an Inventory Control System
80Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
81/91
EzTracker an Inventory Control System
81Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
82/91
EzTracker an Inventory Control System
82Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
83/91
EzTracker an Inventory Control System
83Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
84/91
EzTracker an Inventory Control System
84Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
85/91
EzTracker an Inventory Control System
85Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
86/91
EzTracker an Inventory Control System
86Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
87/91
EzTracker an Inventory Control System
Appendix B: Interview Report
Following includes the interview which was conducted with the manager and the
cashier on the existing system that they used.
Q: Who are the people involved in the system and how do they interact with the
current system?
There is me (manager) and a cashier to perform operational functions and I
handle the financial sides of the communication center by checking in items
and issuing cheques when needed.
Q: Can you name some of the items that you take in with the vendors?
We take mobile accessories such as batteries, chargers from Mr.Avishka
Gunawardena and referees from different mobile service providers come in.
Q: How many times a week do they visit the communication centre?
87Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
88/91
EzTracker an Inventory Control System
Mr.Avishka comes ones a month and the others usually visit three times a
week.
Q: How are the payments made and how do you check the items for quality
assurance?
The payments are made mostly by cheques and for service providers we pay
by cash. When it comes to the quality assurance, it only matters in guaranteed
items. Suppose the item is a battery charger, we check it when the item is
purchased. Mostly the case is based on trust that both put on each other
Q: As you know we do a system to control your inventory. This may change the
action in which the system operates. For an example you may want to give a
code to each item, all the transactions are stored in the database etc. What do
you feel about this change?
I feel confident about the system that you are going to make for us. Of course
there are a bitt of work in our side, like you said counting and naming the
items. But I am sure that we are ready to accept the change in a positive
manner.
Mr. Aruna suggested us to talk with the cashier in order to get details on the
operational level activities. Following is the interview that was conducted with him
Q: What exactly are your responsibilities in this communication center?
I handle all the transactions that happen with the customers such as selling a
battery to take photocopies. Suppose the sale item was a SIM card, I write
down the details of the customer on a book with relevant details. Sometimes
the manager also helps me out in these things. I am the one who interact with the customers a lot and sometimes I have to
interact with the vendors such as making cash payments which were assigned
to them by the manager. Also if we are out of stock I have to call the manager
to get the vendors to visit the communication center.
Q: What are some of the problems that you face while working (related to the
manual system that is used)?
88Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
89/91
EzTracker an Inventory Control System
Well, mostly the SIM registration process is a irritating activity since I got to
enter all the details of a customer to a book twice, one for the vendors and
other for our record.
Sometimes we face difficulties when we are to return an item that was
purchased since we dont have any records from which vendor the items were
taken from.
Q: Do you want any features to be included in the computerized system that you
think would ease your workload?
I would be pleased if the above mentioned problems are rectified. In addition
it would be helpful to generate the bill via the computer other than me issuing
a handwritten bill.
Appendix C: Sample Questionnaires
Questionnaires
(For the development of EzTracker system)
a) What are the services available at the communication?
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
b) What kind of system is using when supplying those services?
Automated System (Software) Manual System None
Describe it in brief.
89Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
90/91
EzTracker an Inventory Control System
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
c) What are the problems that you have to face by using current system?
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
d) Do you think using an automated system (software) will help to overcome
those problems?
Yes No other (describe in brief)
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
e) If you need an automated system, what kind of features would you expect to
be included?
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
90Asia Pacific Institute of Information Technology
-
8/3/2019 EzTracker (FINAL)
91/91
EzTracker an Inventory Control System
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
.............................................................................................................................
f) Will it be useful for your shop, if an automated system was implemented to
tracker all stock and registration details?
Yes No
.Signature Date
Appendix D: Work Breakdown Structure
Figure 9: Work Breakdown Structure
Appendix E: Testing Reports