ABSTRACT

A stock inventory management system is web-based computerized system that the user shall use to keep
track of the business stock movement in and out of the system. In this current day and age, many of the
businesses in Zambia operate in a traditional way in processing of data and Kalimandema Enterprise is one
of them. This business uses a traditional way of monitoring day to day transactions and stores record on
pieces of paper and then locked in a room. They use many ways of transactions such as receipts, cash
books, invoices etc. Monitoring of these day to day transactions happens every day just after close of
business. I have observed and seen their need for a computerized stock inventory system as it will provide
efficiency and secure the data. The consequence of having this system is an increased level of
professionalism and reduction in human errors with enhanced accessibility to the other sales people. The
core concept of this system is to keep track of stock movement coming in and going out of the business
and help staff on accounting for every transaction. This system will use a web-based interface with a
database that allows multiple storage of stock in the system.
 Page |2

Table of Contents

Statment of Confirmation..........................................................................................................................I

Title Page.................................................................................................................................................II

Abstract....................................................................................................................................................1

Contents Page.........................................................................................................................................2

Introduction..............................................................................................................................................4

Analysis.................................................................................................................................................10

Design....................................................................................................................................................18

Implementation......................................................................................................................................21

Conclusion.............................................................................................................................................25

Done by Wongani Msiska Computing Project December 2018

 Page |3

Acknowledgments

I would like to thank Ms. Angela Mateyo for the emotional, spiritual and financial support given to me during
the course of this project. Furthermore, I would like to thank Shadreck Mutinta for opening my eyes to see
the need for systems in each business. I would buy a lot of stocks and any kind of business, but I didn’t
know the amount of work that is put to account for every transaction.

Lastly many thanks to Mr. Moses Belemu for believing in the solution of my project to the business and Mr.
Jonathan Zulu my supervisor for the guidance during this project.

Done by Wongani Msiska Computing Project December 2018

 Page |4

INTRODUCTION

“One of the greatest responsibilities that I have is to manage my assets wisely, so that

They create value.” – Alice Walton

This project report describes the Stock Management System sufficiently to determine the
feasibility and usability of a finished system. The core concept is to track the sale of items from
the cash registers with additional features for interpreting the data. It uses a client-server model
with a connected database to allow multiple stores and warehouses to be connected. This allows
for later expansion while still supporting the targeted small businesses. The core features and
final framework should be completed within 2 weeks, leaving 5 weeks to implement additional
features and testing.

The circumstances of having a business in this world using a computerized inventory management
system are little. Focusing on Zambia, the business itself did not see the need and the advantage
that comes with having a computerized system but currently just rely on a manual way of
transacting. Most businesses run on stock products or inventory such as assets and if you do not
keep track of the business stock that is going in and out of the business, then you could be letting
money slip through your fingers because of failure to account most transactions.

THE DEVELOPED SYSTEM

The system to be developed is a stock inventory management system for Kalimandema Enterprise
which is a PHP web-based system. What is a stock inventory management system? This is the
process of carefully and efficiently overseeing the flow of stock in and out a warehouse where
goods are stored. This process is used to show how much stock you may have at any given point
in time and you can keep track of it. As compared to this system, the manual does not make it
easy to keep track of records of transactions because much time was spent on organizing data for
any given period. Furthermore, a computerized stock inventory management system operates in a
similar was as a manual but is more flexible and its information is easier to obtain. The system can
show a stock valuation and provide information of what stock is moving. This computerized stock
inventory management system is a good option to this business because it deals with different
types of stock products.
Now that we know management of inventory is an important part to the business success, below
are the benefits of having good management system;

1. Planning accurately:

With the current demand of stocks, the system helps you stay ahead of the demand curve by
pulling out reports that show how much stock available, what stock is on demand and what stock
is needed.

2. Building efficient employees:

Done by Wongani Msiska Computing Project December 2018

 Page |5

When you train your employees, they can help you manage stock and in the long run the results
help the business use its resources both human and technological.

3. Saving on Time Spent:

Knowing the time spent on accounting for all transactions after close of business is exhausting, the
developed system helps you through generating of reports which show day to day transactions.

4. Reduced Human Error:

The previous system (manual) relied on human actions and inputs, it was hard to trace the
movement of stock due to many reasons. Sometimes the sales staff would forget to enter the
transaction of the stock that has been sold or they could write down wrong data due to
miscounting of stock. This would result into you ordering more stock for the one that was
miscounted. On a good note the system maintains integrity and shows accurately how much stock
is in and reduces on human error when the staff decide to know how much stock is available.

SYSTEM LIMITATIONS

In system development, communication was an essential part and with the discussions we had
with the Manager, we concluded only having one account (Admin) as requested. Therefore, the
system is only limited to having one account although in future if need be we shall improvise.
Below are some other limitations;

- The systems rely on the strength of the Anti-virus for security.

- The system is as accurate as you update it. What this means is that, when the manager
does not take to account what stock has been received, the system will always give false
readings as compared to what you have at hand.

JUSTIFICATION FOR METHOD OF FRAMEWORK USED

A. Agile Development
This is the approach taken to the development of software involving an Iterative approach to the
delivery and building of software as opposed to developers trying to deliver a working project at
one go. Iterative approach means the ability to go back to a process that may have passed to
guarantee satisfaction. Agile development is different from other software developments because
it is aimed at delivering projects on time within its required budget while focusing on the Business
value. This includes the aspect that projects can be completed on time by prioritising its
requirements. Throughout the development, agile will emphasize on end-user involvement. This is
the most appropriate approach for Kalimandema because of its guaranteed their satisfaction
through participation. Agile development is distinct from other development methodologies
because;

- It guarantees the manager satisfaction by the rapid and continuous delivery of useful
software which will be useful for the business

- Has the best form of communication which is face-to-face and makes the client a vital part
of the development process by constantly referring to the client for at whatever stage

- Allows changes to be made even at a late stage

Done by Wongani Msiska Computing Project December 2018
 Page |6

- It aims at involving the user of the proposed stock inventory management system.

- It is flexible to change

- At the end of the project, the Sales Manager shall not have a working solution, but the
knowledge and experience gained from the project on the inventory stock management
system and its benefits this development brings to the business as opposed to the
traditional way of accounting for stock.

Conclusion

The best time would be NOW when this business wants to engage a new system to improve the
business processes. Why? Because of the freedom agile gives to change which is very important.
Latest changes can be implemented at very little cost because of the frequency of new increments
that are produced. Not only that but both the developers of the system and the stakeholders alike,
find the freedom of time and options than if the software was developed in a more rigid sequential
way. Having options gives both of us the ability to leave important decisions until more or better
data or even the entire hosting programs are available; meaning the project can continue to move
forward without fear of reaching a sudden standstill.

B. Object Oriented Analysis and Design (OOAD)

This is the technical approach that an application developer uses in order to analyze, design an
application system by applying object-oriented diagrams throughout the development life cycles.
The sole purpose is to develop solution models that satisfy the customer requirements.

C. PHP (Hypertext Processor)

PHP is currently the most popular scripting language that fits properly into HTML and leaves the
responsibility of creating dynamic websites to people. PHP original stood for “personal home
page” but now stands for Hypertext processor. PHP is server-side programming language
because its code runs on the server. Since Web development is all about communication. In our
case, communication will be between two (2) parties, over the HTTP protocol:

 The Server - This is the one responsible for hosting the web-based management system.

 The Client - This is the one that requests pages from the Server and displays them to the
user. In most cases, the client is a web browser.

 The User - The user such as the sales manager uses the Client to surf the web
such as enter details in the stock management system and also requests for reports.

Below are some of its benefits;

- Easy to Read: This programming is easy to read and understand and is well organized
- Easy to Edit
- Better performance
- PHP is widely available
D. APACHE

Done by Wongani Msiska Computing Project December 2018

 Page |7

This is a web-server software developed by Apache software foundation. A web-server checks all
the web pages a user requests and retrieves it for the user to view.

E. MySQL

This is a database management system that is used to store and retrieve all web information. It
runs on a server and does allow for multiple users to manage the data it stores.

F. Wamp Server

This is a windows environment that helps you run web applications with the use of Apache, PHP
and MySQL database.

AIMS AND OBJECTIVES OF THIS SYSTEM

AIM

To develop a stock inventory system that will allow the input of stock details, querying of data from
the database for daily transactions, efficient capturing of data, improved security of data and
inventory that reduces human error with the aid of a user-friendly interface.

OBJECTIVES

The main objective is to introduce the stake holder (Sales Manager of Kalimandema Ent.) to the
system with its benefits and get rid of the old manual way of processing transactions. This
provides a better solution because it reduces on human error and the time spent on accounting for
transactions.

Other Objectives;

- To Reduce on costs
- To become faster to responding to customer and stakeholder requests
- To improve customer service
- To improve marketing for the business
- To improve control of money for the business
- To increase information reporting accuracy
- To deliver a system that is easy to use and maintain

SHORT OVERVIEW OF THE REMAINING CHAPTERS

CHAPTER NAME DESCRIPTION STRUCTURE

ANALYSIS Understanding what the - Requirements: this is

system to be built should be where we define the
functional and non-
functional requirements

Done by Wongani Msiska Computing Project December 2018


DESIGN After understanding what the
system should be this stage
turn it into a working system
that can be implemented,
IMPLEMENTATION This stage takes the design
and turns it into a working
system.
OTHER PROJECT ISSUES This chapter accounts for the
approach to project
management, risk
management, configuration
management and testing
Done by Wongani Msiska
Page |8
of the system.
- Use Cases: This
technique identifies the
objectives to
accomplished by the
software system
- Architecture: the
architecture shows a
depiction of how the
system to be developed
should behave. It
serves as a blue-print
for both system and the
project.
- Structural Model: this
model gives a detailed
class diagram
- Behavioral Model:
Describes the behaviors
of the actors and
classes of this system
- Choice of the
programming language
used
- System transition from
development
architecture to
implementation
architecture
- Data migration from
development
architecture to
implementation
architecture
- Training
- Describing particular
techniques used , why
they were used rather
than others
- Providing a main
summary of main
results
Computing Project December 2018
 Page |9

CONCLUSION Having to evaluate the firm

aspects of my work within
context

REFERENCE This chapter shows all

citations using the Harvard
referencing system

APPENDIXES Any supported materials at

the end of the book

ANALYSIS

What is Analysis? This is the process of understanding what the system should be. This stage
usually begins with a problem domain. In this case, it is to create a system that will help the Sales
Manager to make a more efficient job in managing the business.

System Requirements

Done by Wongani Msiska Computing Project December 2018

 P a g e | 10

A system requirement is a description of the services that the system to be developed will provide
and its limitations under which it will operate.

Functional Requirements:

These are services that the system should provide, what results certain inputs shall provide and
how the system to be developed should behave. Functional requirements mainly describe
functionality and sometimes may be high-level statements of what the system should do.

Examples of Functional Requirements:

- Obtain name and price of stock

- The system shall prompt for username and password on every login to improve security
- The user shall be able to Add details of the stocks or products e.g. the manager can add
products received with the system producing an automated unique identifier.
- The Manager who is admin can generate reports from a specified date
- The user can update store details
- Every stock added into the system shall have a unique identifier (Stock_ID)
- The Admin will be able to view clients with outstanding payments
- The Admin will be able to add suppliers to the system
- The system will be able to show the number of stock in the system on the dashboard
- The web application shall be able to cash a sale
- The Web application shall be able to input customer orders

Inputs:

These inputs give a certain result in the system.

- Ctrl+0 (This takes you to the Home page)

- Ctrl+2 (This input makes you add stock to the system)
- Ctrl+8 (This input displays a list of sales in the system)

Non-Functional Requirements

These are requirements that are generally not concerned with the functions of the system but look
at the criteria to which the stock inventory system is supposed to conform to. To an extent, non-
functional requirements can be linked with user satisfaction and how the system plays a key role in
the process.

Done by Wongani Msiska Computing Project December 2018

 P a g e | 11

Below are the non-functional requirements;

1) Usability:
- The system must be easy to use by the Manager (Admin)
- The system must be quickly accessible by the Manager
-The system will be intuitive and simple in the way it displays all relevant data
-the system interface should be easy for the stakeholders or users of the system and
provide a positive user experience on what the user expects it to do
-The menus on the system must be easy for the manager to navigate and easy to
understand
2) Reliability:
-The system will provide an accurate inventory status to the manager.
-The system must successfully add stock
-To system must provide security through user authentication
3) Performance:
- The system should work smoothly and not lag
-All functions of the system should function as soon as it comes on
4) Supportability:
-The wed-based inventory should work in environments such as any Operating
Systems
-The system is easy to adapt even if additional plugins and modules are added
5) Security: the system should have authentication so that unauthorized users do not have
access to the system
6) Availability: the expected availability of the interface
7) Maintainability: having source code that adheres to coding standards for the developed
language used

Requirement Prioritization

This technique helps the developer see what is essential from the customer’s point of view. This
technique sorts out priorities in order. The Technique is known as MOSCOW. It stands for “Must
Have”, “Should Have”, “Could Have” and “Won’t Have”. From this it is important to have a healthy
number of “should have” and could have”.

MUST HAVE

Done by Wongani Msiska Computing Project December 2018

 P a g e | 12

This prioritization defines a requirement that must be satisfied for the final solution to be
acceptable to the user and carry a critical impact on the business if not followed properly.

E.g. in the Stock inventory system, its mostly about purchases and sales of stock. Must
requirements of the system will include putting an “Add” button to the system which will enable the
system to add every stock item in the system.

SHOULD HAVE

This part of prioritization shows the high priority requirements that should be involved in business
solution if it we are able to do so. Most of these requirements are highly desirable. These
requirements have a less priority than “must have” requirements. 

E.g.  Should requirements for the stock inventory management system include change of delivery
date of stock and ability to change varieties stock in the system. These requirements are high
priority requirements for the stock inventory system which is helpful for boosting quality of
information in the stock inventory system.

COULD HAVE

This prioritization includes requirements which could be desirable but not necessary to implement
that very requirement. The Sales Manager thinks over these requirements if they have enough
time and resources of which is not the case in this scenario. These requirements have a high
priority than “Won’t have” requirements which shall soon be talked about.

E.g. could the requirements for the stock inventory management system include stock items
according to order?

WON’T HAVE

This involves requirements which are necessary but for the future. The sales manager can
analyze and consider this requirement for future use. Below are some of the reasons as to why
some of these requirements have been placed in this category.

 If a requirement is not as important on observation

 If a requirement is too difficult for the user to comprehend

 If the requirement implementation is costly

 If the risk of having that requirement is too high

E.g. buying stock from third party vendor to resell. This is a “won’t have” requirement because on
observation this requirement is not that much important.

USE CASE

One of the major features that come with the “use cases” is having the ability to present your data
in context with the requirements of the system. For example, the system should be able to log
payments to the accounts stock inventory system. When the developer makes use of the “use
Done by Wongani Msiska Computing Project December 2018
 P a g e | 13

cases” he primarily focuses on the users of the system rather than the system itself. Use cases
are easy to understand and understandable to stakeholders because it consists mainly of narrative
text. When you bring stakeholders during the planning stages of a project through the use of “use
case diagrams”, we bring people who best understand the problem faced by the future users of a
proposed system. How the system is used is described by the use of a “use case diagram” but on
the other hand, the use case diagram can also describe all the things that may go wrong. So when
a use case diagram has been modeled, it can be used to drive many other aspects of
development of software such as planning and user documentation.

Actor: the actor in this case is the user of the system (Manager)

User: this only consist of the sales manager as wants to be the only one to manipulate the system.

Sales Manager: logs on to the system as ADMIN and can add customer with their details and do
other administrative work.

The next page has a diagram of the use case diagram.

USECASE DIAGRAM

Done by Wongani Msiska Computing Project December 2018

 P a g e | 14

ARCHITECTURE

Done by Wongani Msiska Computing Project December 2018

 P a g e | 15

The system architecture is the design of a structure and how its components will connect,
including its principle guiding its design and if the system shall have any constraints. We shall look
at two parts in this section which N-Tier Architecture and Class Diagram. N-Tier architecture is a
vital part of software development and for this project because we must see how the processing,
data management and presentation function separately. The class diagram will show the view of
an application.

N-Tier architecture

This is called the multi-tier architecture because it is a client-server architecture where its
application processing and functions of data are separate. The Stock inventory management
system is based on a 3-Tier architecture system.

1) Data Tier:

The data layer does consist of database server that stores information for the business be it
customer details, stock details and payment details to name a few. This data layer handles all data
synchronization in the system.

2) Business Logic Tier:

The business layer logic contains the rules and functions of the business. This layer handles all
the transactions been processed and the system communication with other devices for example
client machine and server.

3) Presentation Layer:

This is the layer that makes use of a user interface and interacts with the business logic tier. This
system to be developed has a web interface that is user friendly and can be modified to suit the
user’s needs.

This section shows how a user of the system would send a request such as to display a list of
stock items in the system. The database in the system would bundle up the query to that very
location in the database. The data layer will receive the data and then return the request to the
system which then later converts it into a format that the user can understand.

Done by Wongani Msiska Computing Project December 2018

 P a g e | 16

Analysis Diagram of the System

Class Diagram

This diagram shows the different entities (people, things and data) relate to each other, hence
showing the static structure of the system. Class diagrams can be used to show what
programmers deal with, like implementation of classes. Furthermore, the class diagram is not only
used for visualization, describing and documenting but also for constructing code that is
executable for the software or web application. Below are some of the reasons why it’s important
to have a class diagram;

- Reverse and Forward Engineering

- Describe the responsibilities of a system
- Analysis and Design of the static view of an application

The next page has the class diagram of the system.

Class Diagram

Done by Wongani Msiska Computing Project December 2018

 P a g e | 17

DESIGN

INTRODUCTION
Done by Wongani Msiska Computing Project December 2018
 P a g e | 18

Design is the stage that follows Analysis. This is the process where we take what we
understand about the system and convert it into a system that can be implemented. Design is
about producing a solution that meets the requirements that have been analyzed. This project
illustrates the detail of the design specification of the proposed system by splitting the design
structure into Structural and Behavioral models that are designed using starUML.

STRUCTURAL MODEL

The Structural model addresses issues concerned with the way classes and objects are
organized.it is an important aspect of the development life cycle. The structural model will capture
the static features of the system. They consist of the following;

- Class Diagrams
- Object diagrams
- Deployment Diagrams
- Package diagrams
- Component diagram

The structural model represents the framework for the system and this framework is where all
components exist. Kindly note that this model will not describe the dynamic behavior of the
system.

BEHAVIOURAL MODEL

Behavioral models describe the interaction in the system. This are the interactions between
structural diagrams and will also show the dynamic nature of the system. Example of diagrams
under this model are:

- Sequence Diagrams
- Activity Diagrams
- Interaction Diagrams
- Use Case Diagrams

Earlier in this report, we looked at how that the class diagram describes the static view of the
system, under the behavioral model the activity diagram describes the dynamic aspect of the
system.

Sequence Diagram

A sequence diagram describes an interaction among a set of objects participated in a

collaboration (or scenario), arranged in a chronological order; it shows the objects participating in
the interaction by their "lifelines" and the messages that they send to each other

Done by Wongani Msiska Computing Project December 2018

 P a g e | 19

UML Sequence diagrams are interaction diagrams that detail how operations are carried out. As
sequence diagrams can be used to capture the interaction between objects in the context of a
collaboration, one of the primary uses of sequence diagrams is in the transition from requirements
expressed as use cases to the next and more formal level of refinement. Use cases are often
refined into one or more sequence diagrams.

Sequence diagrams are time focus and they show the order of the interaction visually by using the
vertical axis of the diagram to represent time what messages are sent and when.

Sequence Diagrams captures interaction in different level of granularity:

high-level interactions between user of the system and the system, between the system and other
systems, or between subsystems (sometimes known as system sequence diagrams)

the interaction that takes place in a collaboration that either realizes a use case or an operation
(instance diagrams or generic diagrams)

Represent objects interact in (Model, View / Controller) MVC pattern of software framework

Activity Diagram

Activity diagrams are used the same way as a flow chart but with some added capabilities which
include branching, parallel flow and swimlane to mention a few. We need to have a clear
understanding of the elements used in the activity diagram. The purpose of the activity diagram
are as follows;

Done by Wongani Msiska Computing Project December 2018

 P a g e | 20

- Having a picture of the activity flow of the system

- Knowing the sequence from activity to another

Below is the activity diagram showing the process of when the admin logs into the system, views
the dashboard and its functionality, generates a desired report and prints it.

CONCLUSION

Having looked at this stage we have a picture of how the system should behave including its
dynamic behavior. During this design stage, we showed a high-level sequence diagram of static
side of the web-application.

IMPLEMENTATION

Implementation refers to taking the design and turning it into an actual working system. This
chapter gives details of the programming language used, algorithms used, and design patterns
applied It also gives details of system cutover from development to the implementation
architecture, data migration from development architecture to implementation architecture and
training of users.

CHOICE OF PROGRAMMING LANGUAGE

Done by Wongani Msiska Computing Project December 2018
 P a g e | 21

The developer of the system opted to go for five (5) programming languages.

Below are the following;

1 HTML: HTML is the markup language used to create the frontend of the
website that will be presented to the user when they access the page. It
placed the outline and structure of the webpages. It uses tags that specify
headings, paragraphs, list items and other structural components. HTML
version 5 was used with a combination of PHP (to be discussed later) as it is
now the standard version of HTML that works cross-browser norm accepted
by most modern web browsers. HTML 5 has a better and more efficient way
of defining web structure.
2. PHP: This language has been largely combined with HTML5 in this project to
create a webpage that allows front end element to interact with the back end.
PHP is a server-side scripting language that handles interactions between the
Admin and the server. PHP is open source meaning one can have access to
PHP code for free and it is very easy to learn. The version that was used for
the project was PHP storm. The net framework helps to make system more
like an application
3. SQL: Structured query language in this project was used to create database
tables, define and manipulate database structures on the server side of the
database using the Data Defining Language(DDL) and the Data Manipulation
Language (DML) key words. It was used to create the database for all orders
and products to be stored. The SQL was embedded inside HTML and PHP
code and it is this this code that was used to query the database.
4. JavaScript: JavaScript is a programming language commonly used in
dynamic web development that helps add the additional functionality needed
to allow users to interact with the website without having to communicate with
the server side of the application. It is a Admin-side scripting language, which
means the source code is processed by the Admin web browser rather. This
means JavaScript functions are able to run without the Admin having to
refresh the web browser. A JavaScript function may be used to validate data
entry on a web form before it is submitted to ensure valid entries without
reloading the page or to specifically target a certain element. This makes the
website more efficient.

SYSTEM CUTOVER

Below are the cutover approaches we had considered;

CUTOVER NAME DESCRIPTION

Pilot -Involves implementing a complete new system at a
selected location of Kalimandema Enterprises.
-It reduces risks by restricting implementation of the system
at a isolated location, and is less expensive compared to
the parallel changeover.

Done by Wongani Msiska Computing Project December 2018

 P a g e | 22

-This involves switching over from the old system to the

new system. It is the least expensive approach compared
Direct Approach
to other changeover methods.
-Both the old and the new system operate fully side by side
for a specified period. The old system is closed when users,
management and IT Staff are satisfied that the new system
Parallel Approach operates correctly as expected.
-It is the most costly method and involves lower risks.
Phased Approach -This involves implementing the new system in stages or
modules.
-It has fewer risks and errors and it is also less expensive.

After considering all approaches, the pilot approach seemed to me more appropriate looking at the
circumstance we have of moving from a traditional approach to dynamic approach.

TRAINING

Training involves teaching the manager on how to use the system effectively. The following will be
considered before the actual training of the manager.

 Selecting which date will be appropriate for us to train the manager.

 Provide the manager with effective learning materials and interactive tutorials.

Training Plan

Training plays a key role as it ensures that the user has attained the knowledge required to use
the system. The plan below gives details of when the Manager for Kalimandema will be trained
and what contents will be covered.

Trainee Topic Summary

Manager - The Importance of training The admin will need to know

the importance of this part of
the development cycle

- Setting up of the Stock Inventory How to setup the web-based

Done by Wongani Msiska Computing Project December 2018

 P a g e | 23

Management System system and it will function

Training Deliver Methods

This section presents the types of methods that are involved in training of user for the new system.
We shall look at two type of delivery methods; Instruct-led training and Hands-on training. The
method which would be favorable is the instruct-led training is it center’s communication between
the developer and the client hence making it part of the development process.

Technical Documentation

This type of documentation contains descriptive texts, code dumps and its narrative, flowcharts,
etc., that guide users of the system who want to modify or update the functionality of system.

The username and password to get into the application are;

Username: admin

Password: admin

A technical documentation can among others, contain the following components:

 The step-by-step for running the installation program.

 How to open the stock inventory management system after setup.

Conclusion

The implementation of the stock management system will use a parallel system cutover method
through the process when converting data that is stored on hard copy to electronic copy.

Other Project Issues

TESTING

Testing is the technique of analyzing software to detect the differences between existing and the required
conditions so that features of a software item can be evaluated. There are two types of tests, namely; White
Box testing and Black box testing. The type of testing recommended in this project is Black Box testing.

WHITE BOX TESTING

This type of test investigates the logic and structure of the code. The tester looks inside the source code
and analyze which unit of code is not functioning as expected.

BLACK BOX TESTING

Done by Wongani Msiska Computing Project December 2018

 P a g e | 24

This is the testing technique which is performed without having any knowledge of the internal workings on
an application software system. It tests for the functionality of the system whose test data is derived from
the analysis and design specification.

The tester ensures that correct outputs are defined for both valid and invalid inputs. A tester interacts with
the system's user interface which provides inputs and examines the outputs without knowing how and
where the inputs are worked upon.

TEST DELIVERABLES

Test inputs and outputs are identified as deliverables. These include; Test plan, Test scripts, Metrics
reports and Test procedure.

UNIT TESTING

Individual components of the system are tested as units to ensure that they are fit for purpose. The purpose
of unit testing is to ensure that the program logic is correct and complete, to ensure that the component
works as designed. This approach will be carried out at class level as required by the object-oriented
approach used.

INTEGRATION TESTING

Integration testing is a combination of the unit tests. Individual ‘units’ of a system are combined and tested
to ensure they are fit for purpose. This test ensures that design objectives are met and that the software
compiles with operational requirements as a complete entity.

CONCLUSION ON OTHER PROJECT ISSUES

The contents of ‘Other projects Issues’ were well elaborated and presented best practices in project
management. The developer understood the concept testing and of configuration management and what
should be identified as a configuration item.

Conclusion

In any business, make it big or small, we must understand that taking diligent care of our inventory
is very important. If we as stake holders do not understand the concept of good inventory
management, we must learn to be familiar with it and its applications. One of the reasons for the
failure of a business is its inventory management. There are many ways to fight failure, and we
can start from here. There is new technology that can help us maintain and supervise our
inventory. What we can do is learn, implement and evaluate our business. And you can start with
your inventory. The aims and objectives of the project have been met as evidenced from the
functionality offered by the system. The MOSCOW prioritization technique further expanded the
analysis of requirements.

Done by Wongani Msiska Computing Project December 2018

 P a g e | 25

REFERENCES

1. The Bangalow Bar and Restaurant, (Monday, December 6, 2010), Functional and non-functional
requirements, ‘Definitions’, Available at:
http://thebungalowbarandrestauraunt.blogspot.com/2010/12/functional-and-non-
functional_06.html, Date Accessed [21/10/2018].
2. UML Use Case Diagram, Available at: www.
https://www.tutorialspoint.com/uml/uml_modeling_types.htm , Date Accessed [ 22/10/2018]
].
3. Bennet, S., McRobb, S., Farmer, R., Object_oriented Systems Analysis and design Using UML,
Chapter 12, System Architecture, ‘What Do We Mean by Architecture?’, Third Edition, McGraw-
Hill Education.
4. Techopedia.com. (2017). What is Three-Tier Architecture? - Definition from Techopedia. [online]
Available at: https://www.techopedia.com/definition/24649/three-tier-architecture
[Accessed 22/10/2018].

Done by Wongani Msiska Computing Project December 2018

 P a g e | 26

5. NCC Education (National Computing Cooperation) 2011, Analysis, Design and Implementation
Student Notes and Student Guides [Accessed 22/10/2018].
6. Agilemodeling.com. (2017). UML 2 Sequence Diagrams: An Agile Introduction. [online] Available
at: http://www.agilemodeling.com/artifacts/sequenceDiagram.htm [Accessed 23/10/2018].
7. Smartdraw.com. (2017). Activity Diagram - Activity Diagram Symbols, Examples, and More.
[online] Available at: https://www.smartdraw.com/activity-diagram/ [Accessed 23/10/2018].
8. S Coplan, and D. Masuda (2011), Cutover Management , Apm, (2017) what is project
management? , Chartered Body For the Project Professional. Available at:
https://www.apm.org.uk/ [Accessed 23/10/2018].
9. ccm.net(2017). Networking - 3-Tier Client/Server Architecture. [online] Available at:
http://ccm.net/contents/151-networking-3-tier-client-server-architecture/ Accessed 23/10/2018].
10. Inflectra.com. (2017). Software Testing Methodologies - Learn The Methods & Tools. [online]
Available at: https://www.inflectra.com/ideas/topic/testing-methodologies.aspx [Accessed
23/10/2018].

Appendices

USECASE DESCRIPTIONS

Use Case Name Login Username and Password

Actor Manager / Admin

Pre-condition The Manager should have a username and password

Post-condition Log into the system

TEST SCRIPTS

The user must first download Wamp server in install on their desktop.
Unit Test Test Class: Products Designed By: Nalisa
Done by Wongani Msiska Computing Project December 2018
 P a g e | 27

Wamunyima
Data Source: Log-in Screen Objective: Test for basic Tester: admin
functionality
Test Case Description Tasks Expected Actual Result
Result
1.1 Test for basic Enter stock details: Record is Confirmed
functionality Stock Name: Tanji added to
Supplier: Trade Kings the
Address: Lusaka database
Contact:
Date:

Done by Wongani Msiska Computing Project December 2018