Invetory Management System

Inventory Management System for Hodan Co.
Waberi Group 2011
(INVENTORY MANAGEMENT SYSTEM FOR

HODAN CO. WABERI GROUP)
A Research Paper
Submitted for the partial fulfillment of the requirements for the award of the
Degree in
Information Communication Technology (ICT)
Under the Guidance of Ahmed Hassan Haji
By
Hassan Mohamed Abdilahi – ICT 774/08

&
Mohamed Ismail Ibrahim – ICT 804/08
DEPARTMENT OF ICT
Admas University College

Hargeisa Main Campus
July – 2011
ADMAS UNIVERSITY COLLEGE Final Year Project 1

Inventory Management System for Hodan Co. Waberi Group 2011
AdmasUniv
Admas University College
er sit y Col l ege Hargeisa
Har geissaMain
MainCampus
Campus
HMC
d ª “ "U þ e
› É T e ¿’ >y` e+ ¢K?Ï N ` Ñ@
mail :___________________________
Tel :-________ ____________Fax:-____________________P.o .Box:-_____________e:
CERTIfICATE
This is to certify that the project titled “Inventory management System for Hodan Co. Waberi
Group” is a bona-fide work done by
Hassan Mohamed Abdilahi – ICT 774/08

&
Mohamed Ismail Ibrahim – ICT 804/08
In partial fulfillment of the requirements for the award of BBA (Accounting)

During the period 2008-2011
Ahmed Hassan Haji Resfalem R.

Advisor Head of the Department
(Ahmed Hassan Haji)

Academic Vice president

DECLARATION
We, Hassan Mohamed abdilahi and Mohamed Ismail hereby declare that this thesis is our
original work and has not been presented for the award of any degree/diploma in any other
college or university.
Signatures:…………………………………………………………………………………..
Date:…………………………………
This thesis has been submitted with my approval as supervisor:
Ahmed Hassan Haji Professor of CT,
Admas University College, Hargeisa. Somaliland.
Signature………………………………………………..
Date:………………………

Table of Contents
Content ................................................................................................................. Page Number
Acknowledgment .......................................................................................................................
Chapter 1: System Study ......................................................................................................... 4
Organizational Profile .......................................................................................................... 5
Organizational Chart ............................................................................................................ 6
Project Description ............................................................................................................... 6
Statement of the Problem ..................................................................................................... 6
Project Objectives ................................................................................................................ 6
Project Scope ....................................................................................................... 6
Work Break-down ................................................................................................................ 6
Work Break-down Structure................................................................................ 6
Gant Chart ........................................................................................................... 6
Literature Review ................................................................................................ 6
Chapter 2: System Analysis ...................................................................................................... 4
Definition ............................................................................................................. 6
Traditional Methods of Data collection ............................................................... 6
Interview .................................................................................................. 6
Process Modeling ................................................................................................ 6
Data Flow Diagram ............................................................................................. 6
Context Diagram ..................................................................................... 6
Level 0 Diagram ...................................................................................... 6
Purchase Process ..................................................................................... 6
Sales Process ........................................................................................... 6
Entities and Relationship.................................................................................................6
Description about Entities ....................................................................... 6
Chapter 3: System Design ......................................................................................................... 6
introduction.......................................................................................................... 6
Logical Database Design ..................................................................................... 6
Transforming Entities into Small Tables ................................................. 6
Normalization .......................................................................................... 6

Data Distionary ........................................................................................ 6

Physical Design ................................................................................................... 6
Front End Selection ................................................................................. 6
Introductin to VB.NET ................................................................ 6
Back End Selection .................................................................................. 6
Inroduction to Ms Access ............................................................ 6
Windows Forms....................................................................................... 6
Crystal Reports ........................................................................................ 6
Chapter 4: Implementation ...................................................................................................... 6
Chapter 5: Coding .......................................................................................................................
Chapter 6: Testing……………………………………………………………………………

CHAPTER 2: SYSTEM STUDY

1.1 Organizational Profile
Background
Waberi group is a large Group of Companies in Horn of Africa (Djibouti, Somaliland,

Somalia, Ethiopia) Established in 1990's its head quarter is in Djibouti and it has also
other company in each country and they are : -
Djibouti - Waberi group (Head quarter)
Somaliland - Hodan Co.
Mogadishu - Olad Co.
Bossaaso - Tawfiiq Co.
Ethiopia - Al nuur Co.
Hodan Co waberi group imports different products through Waberi, some of well known
products are Coast Milk powder,Foster Clarks,Jumbo Chicken,Tiara Porridge ,Energizer
Batteries.
Hodan Co. has a sub branches in Somaliland Regions such as Hargeisa (head quarter)
Burco, Berbera, Borama and has a large market in Somaliland.
Vision:
To be the best Commercial Company giving its customers a products at affordable price.
And get more number of customers.
Mission:
We exist to provide cost effective, efficient and reliable means of business s at affordable
price at anytime and anywhere across regions in a way that maximizes customer satisfaction at
the same time optimizing returns to our owner and employees”
Goals
 To get good market target strategy
 To get more monopoly competition in this country or horn of Africa
 To minimize cost

HODAN CO. WABERI GROUP

ORGANIZATIONAL CHART
General Manager
Head Office - Hargeisa -
Director of Addmin / Accounts
Regional Sector Manager Stock and Treasury Supervisor General Admin and Supervisor
General Sales & Treasury in

Charge
Officer
Store One Sales Marketing & Sales Store Two Sales

Department
Lascanod Manger Burao Manager Berbera Manager Borama Manager
Sales Man Sales Man Sales Man Sales Man

1.3 Project Description
In this project we will develop an application to reduce the manual workload of administrative
activities in terms of company management. The application will address all necessary main
tasks required to efficiently manage activities of company. Basic management tasks will be the
main points of consideration, these includes: sales, buying, product, order, customer and other
useful information required to keep from company. It will be used to record available of
selling and buying department and other useful events of the department. It will generally help
managers to keep track of goods data which usually includes product, order sales, buying and
customer to easily generate daily, monthly and yearly reports of product attendance, price,
benefits, number of goods and buying etc.
Comprehensive inventory reports help automate key administrative responsibilities, such as

tracking inventory item usage by vendor and physician, maintaining in-stock value of
consignment verses non-consignment items, and providing notification of items with
upcoming expirations.
An application that reduces purchasing and inventory costs connect inventory control,
purchasing, and sales order processing with demand planning and help reduce costs, improve
cash flow, and help ensure that you have the right stock available when you need it. Gain
visibility into inventory processes. Effectively balance availability with demand and track
items and their possible expiration dates throughout the supply chain to help minimize on-
hand inventory, optimize replenishment, and increase warehouse efficiency.

1.4 Problem statement:
There are many problems in this company like report generating it takes more time
and difficult to collect information that company needs, Wasting a plenty of time
when locating and searching records. This could be utilized for other tasks, more
employee errors when calculating; the administration cannot get sufficient
information to keep track of the smooth running of the company
In this company the information is very hard to retrieve and find particular
information and generated by various dealings and it takes time and pains to be
stored at right place.
1.5 Objectives of the project:
After deeply analyzing all problems faced the previous system, the main objective is to solve
and fix all the problems recorded, as well as to make the system easier, faster, cheaper and
more efficient than the previous system and rise with an essential improvement.
The application is going to be build keeping the commercial aspects of the organization. The
application will have different Category of Products, Sub category of Products and items. This
application will also have transaction details and reports. The administrator of this
application will have right to create product, add items delete items etc. The application will
provide information on available stock of the products
Improve customer satisfaction. Make more accurate order promises and intelligent last-minute
exceptions with access to up-to-date inventory information. Respond quickly and
knowledgably to customer queries for improved customer service.
Reduce time to market. With integrated order, inventory, and distribution processes, as well as
item tracking capabilities, your business can reduce manual data entry and get your goods to
market fast.

The application will also help to generate reports to get latest update on
• Available stock
• Stock Less
• Sale
• Purchase
1.5.1 Project Scope:
 To register the a daily sales of the company

 To record purchases.
 To register the new customer` that joints the Company
 Registering physical count.
 Transactions Reporting
 Monthly and yearly Reports about inventory

3.1 Work break down Structure (WBS)
First developed by the US Defense Department in the second half of the 1950s and by NASA
in the early 1960s, a Work Breakdown Structure is a document used by project managers to
define the scope of a project. It describes the end goal, not the means of reaching that goal. For
example, if the project is to build a house, the WBS defines all the aspects of the finished
house, in increasing levels of detail. It does not specify how the elements of the house are to
be constructed, except where the method of construction is an important part of the finished
house.
A Work Breakdown Structure is not a list of tasks, a schedule or an organization chart. Rather
it provides the basis on which a task list and a schedule can be constructed. Tasks and
schedules are better handled in other ways, for example by using Gantt charts.
3.2 Gantt chart

A Gantt chart, commonly used in project management, is one of the most popular and useful
ways of showing activities (tasks or events) displayed against time. On the left of the chart is a
list of the activities and along the top is a suitable time scale. Each activity is represented by a
bar; the position and length of the bar reflects the start date, duration and end date of the
activity. This allows you to see at a glance:
What the various activities are

When each activity begins and ends
How long each activity is scheduled to last
Where activities overlap with other activities, and by how much
The start and end date of the whole project
To summarize, a Gantt chart shows you what has to be done (the activities) and when (the
schedule).

Work Breakdown
1. Pre-Analysis
1.1 initial investigations
1.2 existing system
1.3 proposed system
1.4 traditional method of data collection
2.2 feasibility study
2. Analysis
2.1. System definition
2.2 process modeling
2.3 Conceptual data modeling
3. Database design
3.1 Logical database design
3.1.1 Transforming entities into small table
3.1.2 Normalization
3.2 physical Design
4. Interface designs
4.3.2. Windows form
4.3.3. Crystal report
4.3.4. User interface
4.3.4.1. Report designer
4.3.5.2 Interface design
5. Implementation
5.1. Coding
6. Testing

GANT CHART

LITERATURE REVIEW
There is numerous accounting software such well known software packages are Peachtree
Complete accounting, QuickBooks and Dac easy. One of the famous in these software’s is
Peach tree.
Peach tree is a complex accounting software package that manage accounts receivable,
accounts payable, payroll, inventory, banking, time billing, job costing, general ledger, fixed
assets and more. It’s based on American accounting system.
Maintaining inventory items Sales/invoicing
The reason that we developing this project, rather than taking Peachtree is that complexity
meaning that there is more features’ that you will never use it according to the environment
of this company. Peachtree accounting needs more training and takes years to be
experienced.
Hodan Co. needs only a few of those features to manage their businesses because inventory
has first priority of importance. The new software is based only the company needs, so its less
featured than Peachtree, and produces more Detailed reports like

3. System analysis
3.1 System analysis definition:
System analysis is the process of investigating a system, identifying problems, and using the
information to recommend improvements to the system.
System development can generally be thought of having two major components: systems
analysis and systems design. In System Analysis more emphasis is given to understanding the
details of an existing system or a proposed one and then deciding whether the proposed system
is desirable or not and whether the existing system needs improvements.
Analysts are often familiar with a variety of programming languages, operating systems, and
computer hardware platforms. Because they often write user requests into technical
specifications, the systems analysts are the liaisons between vendors and IT professionals they
may be responsible for developing cost analysis, design considerations, and implementation
time-lines
A systems analyst may:
1. Interact with the customers to learn and document requirements.
2. Interact with designers to understand software limitations.
3. Help programmers during system development.
4. Perform system testing.
5. Deploy the completed system.
6. Document requirements or contribute to user manuals.

3.2 Traditional method of data collection:
1. Interviewing individuals
2. Interviewing groups
3. Observing workers
When we visit Hodan Company office we met several officials but the most important person
we interviewed is a manager of the company, we asked him many questions that list below.
Interview
1. Since how many years is the business operating?
This business operates since 1992
2. What does the business deal with?

Hodan Co. imports products from foreign Countries and sells to Whole sellers
3. What kind of system is the business using?

We use manual system using books to register all transactions and physical files to
keep documents.
4. What are the objectives set by the business?

To get good market target strategy and get more monopoly competition in this country
or horn of Africa and also to minimize cost
5. Is the current system helping in the achievement of the business objectives?

I think it’s difficult to make an achievement of our objectives because some limitations
of this system, like getting information about business transactions take days.
6. How many employees are there in the business?

There are 32 Employee in Our Company
7. Who are the persons who run the present system?

They are manager and Directors of departments like Finance, Marketing, Sales

8. What are their job functions?

o Manager is responsible to ensure general activities of the Company.
o Finance Director has the supreme responsibility to ensure that all financial
reports are accurate and up to date.
o Marketing directors want to know which market segments will buy their
company's products and how best to sell those products to their target market.
o Plans and directs sales force activities to maximize sales volume and profit
from all segments of the market
9. What are the information they require for their work?

Manager needs summarized daily activities
Finance Director needs daily income or expenses
Marketing Director needs information about Market and prices.
Sales Director Needs Daily sales reports
10. What is your opinion about the implementation of a computerized system?

Computerized system will be great, because it’s very fast.
11. Would you like to see a computerized approach to solving your accounts receivable
problems?
Yes, because in this system it’s difficult or takes time to find
- the amount we owe our customers
- information about all customers
- To view in-depth the profits made on sales to each of your
customers with specific time.
12. Do you think that a computerized system will help in the achievement of the objectives as
well as the goals of the business?
Yes I think
13. Why do you think so?

Because computerized system can do things more efficiently, quicker, and with less
fuss than manual labor.
14. in your point of view, will the employees be able to work with a computerized database
system?
After a short training they will be able to work with computerized Database system.
3.2.1 Justifications for choice of technique
What is an interview?
An interview is a face to face interpersonal role situation in which a person called the
interviewer asks a person being interviewed questions designed to gather information about a
problem area.
The reasons for choosing interview method are :-
• It is rather a flexible technique where further questions may be asked to have an in depth
understanding of the subject matter.
• Many people enjoy being interviewed and usually cooperate in a study where they have to
talk.
An interview ensures a higher response rate compared to, like for instance questionnaire.
• This method of data gathering makes it possible to observe not only what interviewees say
but also how they say it. This offers a better opportunity to evaluate validity of information
gathered.
• It allows the people concern about the business to express their own opinions and point of
view about the current system in used and how this can be improved or changed in order to
meet the objectives and goals set by the organization.

3.4 PROCESS MODELING:
Business process modeling is the activity of representing processes of an enterprise, So that

the current process may be analyzed and improved BPM is typically performed by business
analysts and managers who are seeking to improve process efficiency and quality. The process
improvements identified by BPM may or may not require information Technology, although
that is a common driver for the need to model a business process by creating a process master
There are three processes which are:
1. Purchase processing
2. Payment processing
3. Sales processing

3.7 Dataflow diagram
3.7.1 Context diagram
A context diagram is a graphic design that clarifies the interfaces and boundaries of the project
or process at hand. It not only shows the process or project in its context, it also shows the
project’s interactions with other systems and users. According to Wikipedia, a context diagram
is “is the highest level view of a system . . . showing a . . . system as a whole and its inputs and
outputs from/to external factors. Further, a context diagram “shows the interactions between a
system and other actors with which the system is designed to interface. System context
diagrams can be helpful in understanding the context which the system will be part of.

3.7.2 DFD Level 0

3.7.2 Sales process

3.7.3 Purchase Process

3.4.1 Description about entities
Entities are:
1. CUSTOMER
2. SUPPLIER
3. PRODUCT
4. ORDER
CUSTOMER:
A person or organization that buys goods or services from a store or other business.
SUPPLIER:
Someone whose business is to supply a particular service or commodity
PRODUCT:
An article or substance that is manufactured or refined for sale
ORDER:
A written direction to pay money or deliver property

3.8 Entities and Relationships

Entity-relationship diagrams were first proposed as a means of quickly obtaining, with
minimum effort, a good sense of the structure of a database. Consequently, several key terms
are taken from database theory.
An entity is an object (a person, group, place, thing, or an activity) about which data is stored.
An occurrence is a single instance of an entity; An attribute is a property of an entity; for
example, such attributes as stock number, description, and stock on hand might be associated
with Inventory. Generally, the same set of attributes is associated with each occurrence of an
entity, so every part in Inventory can be expected to have a stock number, a description, and a
stock on hand. The set of attributes associated with an entity can be visualized as a table or a
record.
A data element is an attribute that cannot be logically decomposed. A set of related data
elements forms a data structure or a data composite; for example, the set of attributes
associated with each occurrence of an entity is a data structure. The key to an entity is the
attribute or group of attributes that uniquely distinguishes one occurrence from all other
occurrences. A foreign key is a key to some other entity; for example, a Supplier code might
be associated with the Inventory data.
A relationship links two entities and is shown by drawing a line between them as shown in
figure 1.
Logically, the relationship can be stated in the form of a sentence with a verb linking the two
entities; for example, Sales transactions are composed of Products or Products make up Sales
transactions.
The act of creating such sentences is a good test of the relationship’s validity; if you can’t
express the link, it might not exist. In most cases where the relationship is unclear, the
sentence might be written alongside the relationship line as shown below.

A customer can place many orders and one order placed by one Customer
Cardinality: One–to - Many
One Order can contain many products but one product contains
Cardinality: One–to - One
One Vendor can provide many products also a product can received from many Vendors.
Cardinality: Many to Many

3.7.2 Detailed ER Diagram

3.0 System Design
Introduction
The purpose of System Design is to create a technical solution that satisfies the
functional requirements for the system. At this Point in the project lifecycle there should be a
Functional Specification, written primarily in business terminology, containing a complete
description of the operational needs of the various organizational entities that will use the new
system. The Challenge is to translate all of this information into Technical Specifications that
accurately describe the design of the system, and that can be used as input to System
Construction. The Functional Specification produced during System Requirements Analysis is
transformed into a physical architecture. System components are distributed across the
physical architecture, Usable interfaces are designed and prototyped, and Technical
Specifications are created for the Application Developers, enabling them to build and test the
system.
4.2 Logical Database design
Logical database design is the process of transforming the conceptual data model into a
logical model - which is consistent and compatible with a type of database technology. An
experienced database designer often will do logical database design in parallel with conceptual
data modelling if he or she knows the type of database technology that will be used a beginner.
The result of this process is a set of relations in third normal form that can be implemented
using any contemporary relational database management system. Each entity type in the EER
diagram is transformed to a relation that has the same primary key as the entity type. A one-to-
many relationship is represented by adding a foreign key to the relation that represents the
entity on the money side of the relationship. (This foreign key is the primary key of the entity
on the one side of the relationship.) a money-to money relationship is represented by creating
a separate relations. This primary key of these relations is a composite key, consisting of the
primary of each of the entities that participate in the relationship

4.2.1 Transforming entities into small table
NOTE: (_________) _: Primary key, (............): Foriengn Key
CUSTOMER
Customer_id
Customer_Name
Address
Address
CUSTOMER
Customer_id Customer_Name Address Address
ORDER
Order_id
Order_Date
Customer_id
Product_id
Ordered_qty
ORDER
Order_id Order_date Customer_id Product_id Ordered_qty
PRODUCTS
Product_id
Product_Name
Vendor_id
Price
PRODUCTS
Product_id Product_name Vendor_id Price

VENDOR
Vendor_id
Vendor_Name
Address
Tel
Email
VENDOR
Vendor_id Vendor_name Address Tel Email
4.2.2 Normalization
In the field of relational database design, normalization is a systematic way of ensuring

that a database structure is suitable for general purpose querying and free of certain
undesirable characteristics—insertion, update, and deletion anomalies – that could lead to a
loss of data integrity.
In other hand: Normalization is the process of efficiently organizing data in a database.

There are two goals of the normalization process: eliminating redundant data in more than one
table and ensuring data dependencies make sense (only storing related data in a table). Both of
these are worthy goals as they reduce the amount of space a database consumes and insure that
data is logically stored
4.2.2.1 Three types of normalization are:
I. First normal form
II. Second normal form
III. Third normal form

Description:
I. First normal form (1NF) is a relationship has a primary key and in which are no
repeating groups
II. Second normal form (2NF) is a relation in first normal form in which every non key
attributes are functionally dependent on the primary key.
III. Third normal form (3NF) is a relationship second normal transitive dependence exist-
transitive dependence in a relation is a functionally dependency between two or more
non key attributes.
CUSTOMER
Customer_id Customer_Name Address Address
ORDER
Order_id Order_date Customer_id Amount
ORDER_LINE
Orderline_id Order_id Product_id Ordered_qty Unit_Price
PRODUCTS
Product_id Product_name Vendor_id Price
VENDORS
Vendor_id Vendor_name Address Tel Email

4.2.3 Data Dictionary
A data dictionary is a collection of descriptions of the data objects or items in a data

model for the benefit of programmers and others who need to refer to them. A first step in
analyzing a system of objects with which users interact is to identify each object and its
relationship to other objects this process is called data modelling and results in a picture of
object relationships. After each data object or item is given a descriptive name, its relationship
is described (or it becomes part of some structure that implicitly describes relationship), the
type of data (such as text or image or binary value) is described, possible predefined values are
listed. And a brief textual description is provided. This collection can be organized for
reference into a book called a data dictionary.
When developing programs that use tha data model, a data dictionary can be consulted
to understand where a data item fits in the structure, what values it may contain, and basically
what the data item means in real-world terms. For a bank or group of banks could model the
data objects involved in consumer banking. They could then provide a data dictionary for a
bank's programmers. The data dictionary would describe each of the data items in its data
model for consumer banking (for example, "Account holder" and ""Available credit").
CUSTOMER TABLE
FEILD NAME FIELD SIZE DATA TYPE CONSTRAINTS
Customer_ID 30 NUMBER PRIMARY KEY
Customer_Name 40 TEXT NOT NULL
Address 30 Text NOT NULL
Tel 40 Number NOT NULL

PRODUCT TABLE
FEILD_NAME FEILD_ZISE DATATYPE CONSTRAINTS
Product_id 30 NUMBER PRIMARY KEY
Product_name 30 NUMBER NOT NULL
Vendor_id 40 TEXT FORIENG KEY
Cost 30 NUMBER NOT NULL
Sale 30 NUMBER NOT NULL
ORDER TABLE
Order_id 30 NUMBER PRIMARY KEY
Order_date 30 DATE/TIME NOT NULL
Customer_id 40 TEXT FORIEGN KEY
Amount 30 NUMBER NOT NULL
ORDER-LINE TABLE
OrderlLine_id 30 NUMBER PRIMARY KEY
Order_id 30 NUMBER FORIENG KEY
Product_id 40 NUMBER FORIENG KEY
Product_Qty 30 NUMBER NOT NULL
Uprice 30 NUMBER NOT NULL
ENDOR TABLE
Vendor_id 30 NUMBER PRIMARY KEY
Vendor_Name 30 TEXT NOT NULL
Address 40 TEXT NOT NULL
Tel 30 NUMBER NOT NULL
Email 30 TEXT NOT NULL

Physical design
Introduction
During physical database design the designer translate the logical description of data
into the technical specifications for storing and retrieving data. The goal is to create a design
for storing data that will provide adequate performance and ensure database integrity, Security,
and recoverability. In physical database design, you consider normalized relations and data
volume estimates, data definitions, data processing requirements and their frequencies, user
expectations, and database technology characteristics to establish field specifications, record
designs, file organizations, and database architecture.
Front-end and Back-end selection
An important issue for the development of a project is the selection of suitable front-end and
back-end. When we decided to develop the project we went through an extensive study to
determine the most suitable platform that suits the needs of the organization as well as helps in
development of the project.
The aspects of our study included the following factors.
Front-end selection:
1. It must have a graphical user interface that assists employees that are not from IT
background.
2. Scalability and extensibility.
3. Flexibility.
4. Must provide excellent reporting features with good printing support.
5. Platform independent.
6. Easy to debug and maintain.
7. Front end must support some popular back end like Ms Access.
According to the above stated features we selected VB6.0 as the front-end for developing my
project vehicle management system.

Visual Basic.net overview:
Visual Studio is an Integrated Development Environment (IDE) from Microsoft it can be

used to develop console and graphical user interface applications along with windows forms
applications web sites, web applications, and web services in both native code together with
managed code for all platforms supported by Microsoft Windows, Windows mobile, Windows
CE, .Net Framework, .Net Compact Framework and Microsoft Silver light.
Visual Studio supports different programming languages by means of language services,
which allow the code editor and debugger to support (to varying degrees) nearly any
programming language, provided a language-specific service exists. Built in languages include
C/C++ (via Visual C++), VB.NET (via visual basic.NET), C# (via visual C#), and F# (as of
visual studio 2010) supports for other languages such as M, Python, and Ruby among others is
available via language services installed separately. It also supports XML/XSLT,
HTML/XHTML, JavaScript and CSS. Individual language-specific versions of visual studio
also exits which provide more limited language services to the user: Microsoft Visual Basic,
Visual J#, Visual C#, and Visual C++.
Visual Studio 2005 supports four .NET languages:
Visual Basic .NET: Designed for rapid application development.
Visual C# .NET: A language that combines the features of java and C++.
Visual J# .NET: Microsoft‘s version of java that runs in .NET framework.
Visual C++ .NET: Microsoft’s version of C++ that can be used for applications that need high
performance.
Back end Selection
1. Multiple user support.

2. Efficient data handling.
3. Provide inherent features for security.
4. Efficient data retrieval and maintenance.
5. Popularity.
6. Operating System compatible.
7. Easy to install.
8. Easy to implant with the Front-end.

According to above stated features we selected Ms-Access as the backend.
The technical feasibility is frequently the most difficult area encountered at this stage. It is
essential that the process of analysis and definition be conducted in parallel with an
assessment to technical feasibility. It centers on the existing computer system (hardware,
software etc.) and to what extent it can support the proposed system.
Introduction of Microsoft Access

Microsoft Office Access, previously known as Microsoft Access, is a pseudo-relational
database management system from Microsoft that combines the relational Microsoft Jet
Database Engine with a graphical user interface and software-development tools. It is a
member of the Microsoft Office suite of applications, included in the Professional and higher
editions or sold separately
Microsoft Access is used to create simple database solutions. Access tables support a variety
of standard field types, indices, and referential integrity. Access also includes a query
interface, forms to display and enter data, and reports for printing. The underlying Jet
database, which contains these objects, is multiuser-aware and handles record-locking and
referential integrity including cascading, updates and deletes.




4.3.4 Crystal reports
Crystal Reports is a business intelligence application used to design and generate reports
from a wide range of data sources. Several other applications, such as Microsoft Visual Studio,
bundle an OEM version of Crystal Reports as a general purpose reporting tool.[1] Crystal
Reports became the de facto standard report writer when Microsoft released it with Visual
Studio
Features
 A common standard file format allows for feature-rich reports that contain data
retrieval criteria, grouping, summary, parameter, drill down, and subreport linking
information.
 An embedded Crystal Reports designer, assisted by wizards and experts, builds

complex report files easily.
 Data and .NET Dataset connections use the Database Expert to easily interact with a
wide variety of database protocols, as well as proxy data in the form of ADO.NET
Datasets.
 Dataset processing speed has been significantly improved in Crystal Reports 10 and
Crystal Reports for Visual Studio 2005.



4. Implementation
Introduction
Implementation is the realization of an application, or execution of a plan,

idea, model, design, specification, standard, algorithm, or policy.
In computer science, an implementation is a realization of a technical specification or

algorithm as a program, software component, or other computer system. Many
implementations may exist for a given specification or standard
In the IT Industry, implementation refers to post-sales process of guiding a client from

purchase to use of the software or hardware that was purchased. This includes Requirements
Analysis, Scope Analysis, Customizations, Systems Integrations, User Policies, User Training
and Delivery. These steps are often overseen by a Project Manager using Project Management
Methodologies set forth in the Project Management Body of Knowledge. Software
Implementations involve several professionals that are relatively new to the knowledge based
economy such as Business, Technical Analysts, Solutions Architect, and Project Managers.



Chapter 5 Coding
Login Code:
Imports System.Data.OleDb
Public Class FrnLogin
Dim cn As New
OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=D:\HodanDB.mdb")
Dim ds As New DataSet
Dim username As String
Dim password As String
Private Sub FrmUser_Load(….) Handles MyBase.Load

Dim da1 As New OleDbDataAdapter("select * from Users",
cn)
da1.Fill(ds, "User")
username = ds.Tables("User").Rows(0)(0)
password = ds.Tables("User").Rows(0)(1)
MDIForm.Show()
End Sub
Private Sub TxtUsername_KeyPress(……….) Handles

TxtUsername.KeyPress
If (Char.IsControl(e.KeyChar) = False) Then
If (Char.IsLetter(e.KeyChar)) Or
(Char.IsWhiteSpace(e.KeyChar)) Then
Else
e.Handled = True
End If
End If
If e.KeyChar = vbCr Then
login()
End If
End Sub
Private Sub txtPassword_KeyPress(…….) Handles

txtPassword.KeyPress
If e.KeyChar = vbCr Then
login()
End If
End Sub
Private Sub BtnLogin_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles BtnLogin.Click
If TxtUsername.TextLength < 3 Then

MsgBox("Please Username should be Minimum 6

Characters")
ElseIf txtPassword.TextLength < 5 Then
MsgBox("Please Password Should be Mimimum 6
Characters")
Else
login()
End If
End Sub
Save Code
Private Sub Save()

Try
If ComVendorName.Text = "" Then
MsgBox("---::: Please Select Customer Name :::-
--")
ComVendorName.Select()
ElseIf TxtProName.Text = "" Then
MsgBox("---::: Please Select Product Name :::-
--")
TxtProName.Select()
Else
cn.Open()
Dim cmd As New OleDbCommand("insert into
products values(" & TxtProID.Text & ",'" & TxtProName.Text &
"'," & TxtVendorID.Text & "," & TxtCost.Text & "," &
Txtprice.Text & ")", cn)
cmd.ExecuteNonQuery()
MsgBox(" Successfully Saved")
End If
cn.Close()
Clear()
Catch ex As Exception
MsgBox(ex.Message)
End Try
cn.Close()
End Sub
Update Code:
Sub updateData()
Try
If MsgBox("Are You Sure This Record?", vbYesNo +
vbQuestion, "Update This Record?") = vbYes Then
cn.Open()

Dim strsql As String = "update Products set

product_id=" & TxtProID.Text & ", product_name='" &
TxtProName.Text & "',vendor_id=" & TxtVendorID.Text & ", cost
=" & TxtCost.Text & ", price=" & Txtprice.Text & " Where
product_id=" & TxtProID.Text & " "
Dim mycmd As New OleDbCommand(strsql, cn)
mycmd.ExecuteNonQuery()
MsgBox("The Record Was Updated Successfully!",
vbInformation, "Succesful Update Procedure")
Else
MsgBox("No Modifications Have Taken Place!",
vbInformation, "No Modifications!")
End If
MessageBox.Show(ex.Message)
End Try
cn.Close()
End Sub
Delete Code:
Sub deletedata()
Try
If ComVendorName.Text = "" Then
MsgBox("---::: Please Select Customer Name :::-
--")
ComVendorName.Select()
ElseIf TxtProName.Text = "" Then
MsgBox("---::: Please Select Product Name :::-
--")
TxtProName.Select()
Else
cn.Open()
Dim cmd As New OleDbCommand("delete from
products where product_id=" & TxtProID.Text & "", cn)
cmd.ExecuteNonQuery()
MsgBox(" Successfully Deleted")
End If
cn.Close()
Clear()

MsgBox(ex.Message)
End Try
cn.Close()
End Sub
Validations code:
Private Sub TxtCost_KeyPress(……….) Handles TxtCost.KeyPress

If (Char.IsDigit(e.KeyChar)) Then
Else
e.Handled = True
End If
End If
End Sub
Private Sub TxtProName_KeyPress(…….) Handles

TxtProName.KeyPress

If (Char.IsLetter(e.KeyChar)) Or
(Char.IsWhiteSpace(e.KeyChar)) Then
Else
e.Handled = True
MsgBox("Sorry Only Character & Spaces
Allowed!!", _
MsgBoxStyle.Information, "Verify")
End If
End If
End Sub
Automatic ID Generation:
Sub generateid()
ds.Clear()
Dim daid As New OleDbDataAdapter("select
max(product_id) from Products", cn)
daid.Fill(ds, "Id")
If (ds.Tables("Id").Rows(0)(0) Is DBNull.Value) Then
TxtProID.Text = 1
Else
TxtProID.Text = ds.Tables("Id").Rows(0)(0) + 1
End If
End Sub

6.0 System Testing:
Introduction
System testing of software is testing conducted on a complete, integrated system to evaluate

the system's compliance with its specified requirements. System testing falls within the scope
of black box testing, and as such, should require no knowledge of the inner design of the code
or logic. [1]
As a rule, system testing takes, as its input, all of the "integrated" software components that
have successfully passed integration testing and also the software system itself integrated with
any applicable hardware system(s). The purpose of integration testing is to detect any
inconsistencies between the software units that are integrated together (called assemblages) or
between any of the assemblages and the hardware. System testing is a more limiting type of
testing; it seeks to detect defects both within the "inter-assemblages" and also within the
system as a whole.
5.1 Unit Testing
Unit testing is a method by which individual units of source code are tested to determine if
they are fit for use. A unit is the smallest testable part of an application. In procedural
programming a unit may be an individual function or procedure. Unit tests are created by
programmers or occasionally by white box testers.
Ideally, each test case is independent from the others: substitutes like method stubs, mock
objects,[1] fakes and test harnesses can be used to assist testing a module in isolation. Unit tests
are typically written and run by software developers to ensure that code meets its design and
behaves as intended. Its implementation can vary from being very manual (pencil and paper)
to being formalized as part of build automation.

Customer ID:
Test Case Input Expected Out put

1 123 Valid Id number
2 ABC Invalid (ID Number cannot be a text)
3 2312121321312323 Invalid (out of range)
4 -234 Invalid (id cannot be minus)
Customer_Name:

1 123 Invalid (numbers are not allowed)
2 ABC Valid Customer Name
3 Sdfasdfasdfsdfsadfasddf Invalid (out of range)
asdfasdfas
4 -234 Invalid (Negative value is not allowed)
Telephone:

1 123 Valid
2 ABC Invalid (Tel cannot contain a letter)

Address:

1 123 Invalid (not allowed numbers only)
2 ABC Valid Address
3 231212132dsfasdfasdfasf Invalid (out of range)
Dfasdfsdfsadfsdf3534esfa
4 Street 150 Valid Address
Email:

1 123 Invalid (not allowed numbers only)
2 ABC Invalid Email Address
3 231212132dsfasdfasdfasf Invalid (out of range)
Dfasdfsdfsadfsdf3534esfa@mail.com
4 Abc123@mail.com Valid Email Address
5 /()!#$%^&* Invalid (Not allowed Characters)
Quantity:

1 123 Valid
2 ABC Invalid (Characters Not allowed)
Unit Price:

1 123 Valid
2 ABC Invalid (Characters Not allowed)


Invetory Management System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Invetory Management System

Uploaded by

Copyright:

Available Formats

Inventory Management System for Hodan Co.

Waberi Group 2011

(INVENTORY MANAGEMENT SYSTEM FOR

Information Communication Technology (ICT)

Under the Guidance of Ahmed Hassan Haji

Hassan Mohamed Abdilahi – ICT 774/08

Admas University College

ADMAS UNIVERSITY COLLEGE Final Year Project 1

Hassan Mohamed Abdilahi – ICT 774/08

In partial fulfillment of the requirements for the award of BBA (Accounting)

Ahmed Hassan Haji Resfalem R.

(Ahmed Hassan Haji)

ADMAS UNIVERSITY COLLEGE Final Year Project 2

This thesis has been submitted with my approval as supervisor:

Ahmed Hassan Haji Professor of CT,

Admas University College, Hargeisa. Somaliland.

ADMAS UNIVERSITY COLLEGE Final Year Project 3

ADMAS UNIVERSITY COLLEGE Final Year Project 4

Data Distionary ........................................................................................ 6

ADMAS UNIVERSITY COLLEGE Final Year Project 5

CHAPTER 2: SYSTEM STUDY

Waberi group is a large Group of Companies in Horn of Africa (Djibouti, Somaliland,

ADMAS UNIVERSITY COLLEGE Final Year Project 6

HODAN CO. WABERI GROUP

Director of Addmin / Accounts

General Sales & Treasury in

Store One Sales Marketing & Sales Store Two Sales

Lascanod Manger Burao Manager Berbera Manager Borama Manager

Sales Man Sales Man Sales Man Sales Man

ADMAS UNIVERSITY COLLEGE Final Year Project 7

1.3 Project Description

Comprehensive inventory reports help automate key administrative responsibilities, such as

ADMAS UNIVERSITY COLLEGE Final Year Project 8

1.4 Problem statement:

1.5 Objectives of the project:

ADMAS UNIVERSITY COLLEGE Final Year Project 9

1.5.1 Project Scope:

 To register the a daily sales of the company

ADMAS UNIVERSITY COLLEGE Final Year Project 10

3.1 Work break down Structure (WBS)

3.2 Gantt chart

What the various activities are

ADMAS UNIVERSITY COLLEGE Final Year Project 11

ADMAS UNIVERSITY COLLEGE Final Year Project 12

ADMAS UNIVERSITY COLLEGE Final Year Project 13

Maintaining inventory items Sales/invoicing

ADMAS UNIVERSITY COLLEGE Final Year Project 14

3.1 System analysis definition:

A systems analyst may:

1. Interact with the customers to learn and document requirements.

2. Interact with designers to understand software limitations.

3. Help programmers during system development.

4. Perform system testing.

5. Deploy the completed system.

6. Document requirements or contribute to user manuals.

ADMAS UNIVERSITY COLLEGE Final Year Project 15

3.2 Traditional method of data collection:

2. What does the business deal with?

3. What kind of system is the business using?

4. What are the objectives set by the business?

5. Is the current system helping in the achievement of the business objectives?

6. How many employees are there in the business?

7. Who are the persons who run the present system?

ADMAS UNIVERSITY COLLEGE Final Year Project 16