Çankaya university

ÇANKAYA UNIVERSITY

Faculty of Engineering

Department of Computer Engineering

CENG408

Innovative System Design & Development I

P201616

Metrajlı Stok Kontrol

Project Report

Version 2

Tuğçe Hilal Şen 201211048

Ahmet Gündoğdu 201211025

Barış Işıkpunar 201211028

CONTENT

1. IntroductIon ................................................................................................................................ 2

1.1 Company Background .......................................................................................................... 2

1.2 Problem Statement ................................................................................................................ 2

1.3 Background or Related Work ............................................................................................... 2

2. Literature Search......................................................................................................................... 3

2.1 Internet Research .................................................................................................................. 3

2.1.2 Manufacturing Inventory Management Systems ...................................................... 4

2.1.3 Enterprise Resource Planning (ERP) ........................................................................ 5

3. Summary ..................................................................................................................................... 7

3.1 Technology Used .................................................................................................................. 7

4. Software RequIrements SpecIfIcatIon ........................................................................................ 7

4.1 Introduction ........................................................................................................................... 7

4.1.1 Purpose ........................................................................................................................... 7

4.1.2 Scope of Project ............................................................................................................. 7

4.2 Overall Description ............................................................................................................... 9

5. Software Design Description .................................................................................................... 19

5.1 Introduction ......................................................................................................................... 19

5.1.1 Purpose ......................................................................................................................... 19

5.1.2 Scope of Project ........................................................................................................... 19

5.1.3 Glossary ....................................................................................................................... 19

5.1.4 Overview of The Document ......................................................................................... 20

5.2 Deployment Diagram .......................................................................................................... 20

5.3 Architecture Design ............................................................................................................ 20

5.3.1 Desktop Application .................................................................................................... 20

5.3.2 Database Diagram ........................................................................................................ 32

5.3.3 Block Diagram ............................................................................................................. 35

5.3.4 Interface Design ........................................................................................................... 37

6. INTRODUCTION .................................................................................................................... 41

6.1 Version Control ................................................................................................................... 41

6.2 Overview ............................................................................................................................. 41

6.3 Scope ................................................................................................................................... 41

6.4 Terminology ........................................................................................................................ 41

7. FEATURES TO BE TESTED .................................................................................................. 42

7.1 Login (LG) .......................................................................................................................... 42

7.2 List Operations(LO) ............................................................................................................ 42

7.3 Send Operations(SO) .......................................................................................................... 42

7.4 Adding Operations(AO)...................................................................................................... 42

7.5 Stock Operations(STO) ....................................................................................................... 42

7.6 Create Operations(CO) ....................................................................................................... 42

8. ITEM PASS/FAIL CRITERIA ................................................................................................ 43

8.1 Exit Criteria ......................................................................................................................... 43

9. Test DesIgn SpecIfIcatIons ...................................................................................................... 43

9.1 Login (LG) .......................................................................................................................... 43

9.1.1 Subfeatures to be tested. .............................................................................................. 43

9.1.2 Test Cases .................................................................................................................... 43

9.2 List Operations (LO) ........................................................................................................... 44


9.2.2 Test Cases .................................................................................................................... 44

9.3 Send Operations (SO) ......................................................................................................... 44


9.3.2 Test Cases .................................................................................................................... 45

9.4 Adding Operations (AO)..................................................................................................... 45

9.4.1 Subfeatures to be tested ............................................................................................... 45

9.4.2 Test Cases .................................................................................................................... 46

9.5 Stock Operations (STO) ...................................................................................................... 46

9.5.1 Subfeatures to be tested ............................................................................................... 46

9.5.2 Test Cases .................................................................................................................... 47

9.6 Create Operations (CO) ...................................................................................................... 47


9.6.2 Test Cases .................................................................................................................... 47

10. DETAILED TEST CASES .................................................................................................... 48

10.1 Login(LG) ......................................................................................................................... 48

10.1.1 LG.AD.01, LG.US.01, LG.DC.01 ............................................................................. 48

10.2 List Operations(LO) .......................................................................................................... 49

10.2.1 LO.GO.01 .................................................................................................................. 49

10.2.2 LO.GO.02 .................................................................................................................. 49

10.2.3 LO.OC.01 ................................................................................................................... 50

10.2.4 LO.OC.02 ................................................................................................................... 50

10.3 Send Operations(SO) ........................................................................................................ 51

10.3.1 SO.GO.01, SO.OC.01, SO.OF.01, SO.DOF.01 ......................................................... 51

10.3.2 SO.GO.02, SO.OC.02, SO.OF.02, SO.DOF.02 ......................................................... 51

10.4 Adding Operations (AO)................................................................................................... 52

10.4.1 AO.US.01 ................................................................................................................... 52

10.4.2 AO.US.02 ................................................................................................................... 52

10.4.3 AO.COM.01 ............................................................................................................... 52

10.5 Stock Operations (STO) .................................................................................................... 53

10.5.1 STO.IN.UP.01, STO.IN.CH.01 ................................................................................. 53

10.5.2 STO.BCK.01 .............................................................................................................. 53

10.5.3 STO.IMP.01 ............................................................................................................... 54

10.6 Create Operations (CO) .................................................................................................... 54

10.6.1 CO.GO.01 .................................................................................................................. 54

10.6.2 CO.GO.02 .................................................................................................................. 55

10.6.3 CO.DO.01 .................................................................................................................. 55

10.6.4 CO.DO.02 .................................................................................................................. 56

11. Test Results ............................................................................................................................ 56

11.1 Individual Test Results ..................................................................................................... 56

11.2 Summary of Test Results .................................................................................................. 58

11.3 Exit Criteria ....................................................................................................................... 58

11.4 Known Problems ............................................................................................................... 58

11.5 Conclusion ........................................................................................................................ 59

12. Conclusions ............................................................................................................................ 59

References ..................................................................................................................................... 60

Table of Figures

Figure 1: EasyStock User Interface ............................................................................................ 3

Figure 2: Type Level Model of Database for Index Arbitrage ................................................... 5

Figure 3: Worldwide ERP Software Market Share, 2012 (Market Size: $24.5B) ...................... 7

Figure 4: Global ERP Software Market ...................................................................................... 7

Figure 5: Application Environment .......................................................................................... 11

Figure 6: List Functions ............................................................................................................ 12

Figure 7: Create Functions ........................................................................................................ 13

Figure 8: Send Functions ......................................................................................................... 14

Figure 9: Check Function.......................................................................................................... 15

Figure 10: Admin Use Case ...................................................................................................... 15

Figure 11: Import Function ....................................................................................................... 17

Figure 12: Login Use Case ....................................................................................................... 18

Figure 13: Deployment Diagram .............................................................................................. 21

Figure 14: Database Diagram ................................................................................................... 34

Figure 15: Block Diagram of The Application ......................................................................... 36

Figure 16: Login Page Design .................................................................................................. 38

Figure 17: Admin Page Design ................................................................................................. 38

Figure 18: Add New Company Page Design ............................................................................ 39

Figure 19: Add New User Page Design .................................................................................... 39

Figure 20: Update Stock Page Design ...................................................................................... 40

Figure 21:User Page Design ..................................................................................................... 40

Figure 22: Order List Page Design ........................................................................................... 41

Figure 23: Company Orders List Page Design ......................................................................... 41

Figure 24: Create Invoice Page Design .................................................................................... 42

1

ABSTRACT

For many years, companies want to hold the materials, the number of this materials, expiration

date and more of the same. As is known, computers or electronic devices didn’t improve well in the past

years so people had tried to hold the information with handwriting on the papers. If we consider that

companies keep this information in papers for many years, this papers had started to get lost, wear off and

at the same time, this take up space very much in the firm so they had caused confusion. Whereafter

computers become widespread in the last years, inventors/software developers had tried to solve this

confusion so they invented inventory management systems. These systems had reduced firm’s work load

and had provided to saving on time. Thus, inventory management systems had started to use lots of areas.

Also, inventory management systems contributed for accounting program. Although development of

technology, the software/systems being developed are associated under the new systems and customer’s

satisfaction is increased. In this report, database systems, purpose and importance of inventory

management systems, usage area, how to use it of these systems, the relation between the Enterprise

Resource Planning(ERP) and sample inventory management system will be analyzed.

Key words: Database Management System, Inventory Management, Enterprise Resource Planning

(ERP).

ÖZET

Çeşitli firmaların ellerindeki malzemeleri, bunların sayısını, son kullanma tarihlerini gibi benzeri

bilgileri tutmak uzun yıllardan beri bir ihtiyaç haline gelmiştir. Bilindiği üzere bilgisayar gibi elektronik

aletler eskiden çok gelişmediği için bu bilgiler kâğıt üzerinde kişilerin el ile yazılmasıyla tutulmaya

çalışılmıştır. Firmaların bu bilgilerin tutulduğu belgeleri uzun yıllar sakladığını düşünürsek, bir süre sonra

bunlar kaybolmaya, yıpranmaya başlamışlar ve aynı zamanda çok fazla yer kapladıkları için karmaşaya

neden olmuşlardır. Bilgisayarların yaygınlaşması ile beraber geliştiriciler/yazılımcılar bir çözüm bulmaya

çalışmışlardır ve bunun sonucunda stok yönetim programlarını geliştirmişlerdir. Bu stok programları

firmaların iş yükünü azaltmıştır ve zamandan tasarruf etmelerini sağlamıştır. Böylece stok programları

birçok alanda kullanılmaya başlanmıştır. Stok programları aynı zamanda muhasebe programlarına da

büyük katkı sağlamıştır. Teknolojinin gelişmesi ile beraber geliştirilen bütün yazılımlar/sistemler başka

yeni bir sistem altında birleştirilmiştir ve müşterilerin memnuniyeti artırılmıştır. Bu raporda, veri tabanı

sistemleri, stok programlarının amacı, önemi, kullanım alanları ve nasıl kullanıldığı, kurumsal kaynak

planlama ile ilişkisi ve örnek bir stok programı incelenecektir.

Anahtar Kelimeler: Veritabanı, Stok Yönetimi, Kurumsal Kaynak Planlaması

2

1. INTRODUCTION

1.1 Company Background

Sufle Mobilya is our supported institution which was established in 1986 to making furniture, in the

project. Generally, it creates kitchen, bathroom cupboard and wardrobe for private customers. Sufle

Mobilya cares about making design by using the computer environment. Moreover, it uses some software

such as inventory and accounting management applications. With this approach, they want us to develop

a program like inventory management system.

1.2 Problem Statement

There are many inventory management applications in the industry. All applications doing some

operations like invoice tracking, stock control, reporting the orders, electronic invoice. However, these

applications do not provide the company of Sufle Mobilya needs. The problem is in the invoicing because

these applications do not make detailed order invoice. Thus, we will make an application to solve this

problem.

1.3 Background or Related Work

1.3.1 EazyStock

EazyStock is inventory optimization solution for salesman and deliveryman. It is strong, is used to

easily and is performed “cloud-based solution of inventory optimization” from users. Planning of stock

and refilling operations for maximizing are automatized recipes for businesses. Its goal is that developing

of competition and productivity of financial for client. Per six months’ utilization, eazystock software is

reported from customers:

Inventory rating reduces above 30%.

Materials which are not in the warehouse reduces between 10-15%.

Finding of redundancy and unused stock materials gets easy.

Vendor time of delivery reduces between 30-50%.

Designer performance grows between 10-20% [8].

3

Figure 1: EazyStock User Interface

As is seen from in Figure 3, deliveryman and salesman can be connected kind of all inventory

management systems with using of eazystock interface to reduce apparency and expensive supply-chain.

They can use all type of graphs, can control order line, can see non-stocked or stocked items and can

select supplier and owner.

2. LİTERATURE SEARCH

2.1 Internet Research

2.1.1 Database in Inventory Management Systems

In contemporary technologies, database systems fall into basic parts of projects [1]. Database is a

system which holds the information which is relational. Information in these databases is ordinate, so

accessing, managing, updating of this information is easy and fast. Database systems fall into our every

area. DBMS have been used upwards of other years for storing data. It holds the data which is kept in the

computer. It is accountable to store data of consumer and transaction of request. With DBMS, consumer

information such as elaboration and qualities be kept on safely [2]. Moreover, daily operations are done

in databases. You can summarize your stock transactions. These summarizations are listed according to

low or high values [3]. According to Wolfe, Lau and Westin [4], there are 3 main properties such as

4

objects, relationships and transactions. In Figure 1, object types represent as double rectangles and

relation types as double diamonds. Maximum success is attained that DBMS must be integrated and vital

items. DBMS are utilized for inventory, manage and regain all of data by database systems. Creating of

three-dimensional core of element is using several techniques of databases. According to Martin, DBMS

has some of basic characteristics [5]:

Designers should show regard to entry of data with separately for data retention.

Designers should perform to restrained and normalized approximation data with proper

verification control to provide with wholeness and compatibility to files of data.

Designers should implement security limitations with data inputs.

Figure 2: Type Level Model of Database for Index Arbitrage [4]

2.1.2 Manufacturing Inventory Management Systems

Industry companies need new software programs to handling their workload, competing with

other companies and meeting customer expectations with developing technology in the world [6]. In the

past, software which used by companies were related about just inventory control according to the

customer needs, but these software systems are became to making better business by the developers [7].

In addition, these requirements lead to create system which name is manufacturing inventory

management systems. Inventory management systems is a software with related to stock which provides

5

to control and follow the stocking of materials. Users can check stock equalities, indents, demands and

submittals. This system can be used for production industry for making work, item receipt and documents

[8]. A preferable inventory management software can raise the financial performance of firms [9].

Therefore, inventory management systems have some benefits of companies. Firms use this system for

abstaining from purchasing more goods and realizing the goods which are not in the warehouse. Vendors,

salesman and deliveryman use it very effectively for items control for reducing income and high “supply

chain costs” [8].

According to researches made by CSCO insights, companies which can control their inventory

management systems have bigger profits than opponents which have same rate of growth [10]. In last

decades, for inventory management companies used Just-In-Time (JIT) inventory systems which is

prevent waste of time and increase quality of business but nowadays they use Enterprise Resource

Planning (ERP) systems [9].

2.1.3 Enterprise Resource Planning (ERP)

Enterprise Resource Planning (ERP) is an integrated software system which supply all business

functions such as inventory management, human resources, production planning and accounting

management in the central database [7]. The purpose of the ERP is split out the all business information

of companies to the firm units and stakeholders. Both firm units and stakeholders can visualize

information flows of company and with this approach they can share and transfer the information to the

other units and shareholders [11,12]. Spathis and Constantinides [13] claims that, most beneficial part of

ERP packages is accounting management, financial data can easily coordinate quickly and quality of

financial data is increased with using ERP packages. In addition to this, ERP systems decrease the time

spent for the accounting operations, material controlling, receiving an order and giving an order can easily

accomplish by using ERP packages and costs of these operations are decreased remarkably [14]. On the

other hand, ERP has some disadvantages to the user, the cost of ERP system can be expensive depending

on the size of company and wide ERP systems require crowded IT units for controlling the system,

maintaining and upgrading ERP packages can reveal extra charge for the companies. Also,

implementation of the ERP system requires software and hardware infrastructures. Companies should

supply this infrastructure to create ERP system and they must be careful while adapt the ERP according to

their system. Indeed, in figure 1, the market size of the ERP industry continues to grow rapidly since the

2012, and in figure 2, the market size of the ERP industry is expected to be $41.69 billion in 2020.

6

Figure 3: Worldwide ERP Software Market Share, 2012 (Market Size: $24.5B)

Figure 4: Global ERP Software Market

7

3. SUMMARY

3.1 Technology Used

Microsoft Visual Studio 2015

Microsoft Visual Studio has developed by Microsoft which is IDE (Integrated

Development Environment). It involves so many software programming languages such as

C, C++, C# etc. It also provides visual programming applications like .NET, Visual Basic

and form applications.

C#

C# is an innovative programming language which has developed by Microsoft. It is

used for creating form applications.

MS SQL (Microsoft Structured Query Language)

MS SQL is a relational database management system which has developed by

Microsoft. It allows holding and retrieving data with queries. Applications connect to the

database and use these data.

4. SOFTWARE REQUIREMENTS SPECIFICATION

4.1 Introduction

4.1.1 Purpose

The purpose of this document is to represent a detailed description of the “Metrajlı Stok Kontrol”

application. There are use case forms that explain actors and their functions in this document, also

functions will be explained one by one according to their requirements. Therefore, external interface

requirements will be explained briefly in this document.

4.1.2 Scope of Project

This project will be an inventory control and accounting management system as a standalone

software. The aim of the project is that create a new program due to the customer’s needs. The

stakeholder is Sufle Mobilya Ltd. Şti. . This program will have superior qualities than programs which

exist on the market. In the application, there are four forms named as “General Order List Form”, “Order

List Form of Company”, “Order Form” and “Detailed Order Form”. “General Order List Form” is a form

which is listed of all companies’ total price of orders. “Order List Form of Company” represents orders

8

and their price, date of a company which is selected by the user. In a “Order Form” user can make an

order which is missing or needed stocks. “Detailed Order Form” is a next step of “Order Form” that

includes order’s properties like measure, number and color. Moreover, project has an interface named

“Import” which is used by user. Companies give list of their order’s prices. This interface helps user to

join the code and the price of the orders because codes are different in the companies. Then, the manager

chooses the company which gives the less price of orders.

4.1.3 Glossary

Term Definition

User Experienced person who has a technical

ability about the application.

Admin A person who manages the application.

Data Converter A person who imports data in the interface.

Stakeholder Person who is the owner of this project.

Import Interface It provides to import data.

Database Location of all data on this system.

Company It is supplier of the order.

Inventory Management System It is a system that helps to user to manages the

stocks. Moreover, user can make an

accounting operations.

4.1.4 Overview of The Document

In this part, details of the project are explained with use case diagrams on Overall Descriptions.

Use case diagrams will supply clear explanation for “Metrajlı Stok Kontrol” system. Actors and their

applications will be defined in the use case diagrams. We divide the use case diagrams depends on the

functionalities to explain clearly. Therefore, requirements will be simplified in the Requirement

Specification part. In the last part, we give ER diagram of the system’s database. This application

provides to user can easily control inventory and performing accounting functions of the company.

9

4.2 Overall Description

4.2.1 Application Environment

Figure 1 is the diagram of overall system. There are three actors, which are admin, user and data

converter, and one system in the “Metrajlı Stok Kontrol” standalone application. Admin, user and data

converter login to the system, admin can add new user and company to system, there may be more than

one user in the system. Also, admin can update the inventory depending on the materials and make back-

up to the system. Data converter imports the data which sending by the companies. Moreover, all orders

are kept on the system, user can list general orders and order that belongs the one company, besides user

can send these orders as an e-mail and fax. User checks inventory and create an order form depending on

the missing materials, order form includes information about the material and user sends order form to the

companies as an e-mail and fax. Likewise, user can create detailed order form that includes more

particular information of the materials and he/she can send detailed order form to the companies.

10

Figure 5: Application Environment

11

4.2.2 Functions

4.2.2.1 User Use Case

4.2.2.1.1 List Functions

Diagram:

Figure 6: List Functions

Brief Description: User can list orders in two different forms: “General Order List Form” and “Order List

Form of Company”.

Initial Step by Step Description:

In “General Order List Form”:

1. User choose the form.

2. Program list the total price of the orders by the companies.

In “Order List Form of Company”:


2. User choose a company.

3. Program list the orders and its prices of the selected company.

Exception: If the user chooses a company in “Order List Form of Company” and there is no order of the

selected company, system gives an error message.

12

4.2.2.1.2 Create Functions

Diagram:

Figure 7: Create Functions

Brief Description: User can create orders in two different forms:” Order Form” and “Detailed Order

Form”.


In “Detailed Order Form”:

1. User check the stocks.


3. User enters the codes of the stocks. Program automatically bring the unit price in the stock

list. Then user enter the sizes.

4. Program automatically calculates the total prices due to sizes and unit prices.

In “Order Form”:

1. User clicks the button named Create Order Form in “Detailed Order Form”.

2. Program automatically join the stocks by the same code in the order.

3. Program automatically sum the prices due to join operation.

4. Program automatically list the stocks in the order.

13

Exception: If the user forgets to enter the size and amount of the stock in “Detailed Order Form”, program

can’t calculate the prices.

4.2.2.1.3 Send Functions

Diagram:

Figure 8: Send Functions

Brief Description: User can send e-mail or print in all the forms.


1. User clicks the send e-mail or print button.

2. User selects the e-mail address or printer which is wanted to send e-mail or print.

3. User clicks the send button.

Exception: If e-mail address or printer is no occur anymore, error mail comes to user’s e-mail address.

14

4.2.2.1.4 Check Function

Diagram:

Figure 9: Check Function

Brief Description: User can check the company inventory.


1. User clicks the stock button.

2. User enters the code of the stock.

3. Program automatically lists the amounts, sizes, price, colors of the selected stock.

Exception: If entered code is wrong or missing, error message will occur.

4.2.2.2 Admin Use Case

Diagram:

15

Figure 10: Admin Use Case

Brief Description: Admin has four options: Add new company/user, update the inventory and make back-

up in the application.


In add new company function:

1. Admin clicks the add new company button.

2. Admin enter the information like company name, address, phone number.

3. Admin clicks the add button.

Exception: If entered company is already exists, program gives an error message.

In add new user function for login:

1. Admin clicks the add new user button for login to the system.

2. Admin enters the information like username, password.

3. Admin clicks the save button.

Exception: If the username is already existing, error message will occur.

In update function:

1. Admin clicks the update inventory button.

2. Admin enters the code of the stock.

3. Admin can change the stock information like code, amount, size, price.

4. Admin can add or delete a stock.

5. After the updating operations, admin clicks the save button.

Exception: If the updated code of the stock is already existing, error message will occur.

In make function:

1. Admin clicks the make back-up button.

2. Admin selects the destination folder for back-up.

3. Admin clicks the save button.

16

Exception: If there is no access to the destination folder, admin must select a different folder.

4.2.2.3 Data Converter Use Case

4.2.2.3.1 Import Function

Diagram:

Figure 11: Import Function

Brief Description: Data converter can import data.


1. Other companies give a price list of their stocks.

2. Data converter selects the price list file.

3. The import interface of the application automatically analyzes the price list to import the data.

4. Codes are listed in the interface.

5. Data converter matches the other company codes and own company codes.

6. Data converter clicks the save button.

Exception:

1. If the given price list formats are not compatible, interface gives an error message.

2. If there is a new stock in the given price list, data converter cannot match the new stock’s codes

and must report to admin to add this new stock.

17

4.2.2.4 Login Use Case

Diagram:

Figure 12: Login Use Case

Brief Description: Admin, User and Data Converter can login the system for access.


1. Admin, user and data converter write their usernames into the username textbox.

2. Admin, user and data converter write their passwords into the password textbox.

3. Admin, user and data converter click login button to connect to system.

Exception:

1. If user and data converter don’t have account, they cannot login the system, in the

circumstances admin should create accounts for the user and data converter.

2. The system will give an error, if the password or username is incorrect.

4.2.3 Constraints

4.2.3.1 Performance

The forms should create less than 5 sec.

User, admin, and data converter should connect less than 2 sec.

18

Order lists should appear less than 2 sec.

4.2.3.2 Usability

System can be used by a lot of companies which have different quality and peoples

thanks to easy to access all forms and usage.

4.2.3.3 Adaptability

System should send information if any error occurs.

Daily or monthly back-up should be taken.

4.2.3.4 Scalability

System can be used by multiple users and admin can add user to the system.

4.2.3.5 Portability

The program can usable in both pc and mobile devices.

4.2.3.6 Security

User, admin, and data converter usernames should not be the same.

User, admin, and data converter passwords should contain numbers and characters

with at least 6 characters long.

4.2.3.7 Safety

Database updating times are recorded by defined time periods.

Accessing of system are recorded by all users and admin.

Database connection are always controlled.

19

5. SOFTWARE DESİGN DESCRİPTİON

5.1 Introduction

5.1.1 Purpose

This Software Design Description (SDD) provides the design details of “Metrajlı Stok Kontrol”

program. The expected audience is owner of the company or accountant. This document describes the

detailed structure of the components of desktop application. It also shows how the use cases detailed in

the SRS will be implemented in the system using this design.

5.1.2 Scope of Project

The “Metrajlı Stok Kontrol” application will be an inventory control system as a desktop software.

This software uses database information about materials and inventory. Client can establish a connection

with database on the application interface and he/she can see inventory of company to give an order. In

the application, there are four forms named as “General Order List Form”, “Order List Form of

Company”, “Order Form” and “Detailed Order Form”. This Software Design Document have sections

such as; Deployment Diagram, Architecture Design and Interface Design.

5.1.3 Glossary

Term Definition

User Experienced person who has a technical

ability about the application.

Admin A person who manages the application.

Data Converter A person who imports data in the interface.

Stakeholder Person who is the owner of this project.

Import Interface It provides to import data.

Database Location of all data on this system.

Company It is supplier of the order.

Inventory Management System It is a system that helps to user to manages the

stocks. Moreover, user can make an

accounting operations.

SRS

Software Requirement Specification

20

SDD

Software Design Document

5.1.4 Overview of The Document

This section includes document contents of the rest. Section 2 is a Deployment Diagram that

represents relationship among the form pages and database. Section 3 has an Architecture Design of

System. It includes form page classes and their variables, also have a design of the database which

includes tables, their attributes and relations. Section 4 is an Interface Design. It shows visual design of

the form pages. Page interfaces have been created user-friendly and client can use these designs easily.

5.2 Deployment Diagram

Figure 13: Deployment Diagram

5.3 Architecture Design

5.3.1 Desktop Application

5.3.1.1 Login Page

Name: Login Page

Type: Form Page

21

Description: When user/data converter/admin enter their usernames and passwords and click the login

button, system directs the form pages according to the type of client. These pages are Admin Page, Data

Converter Page and User Page.

Attributes: username: String

password: String

Resources: Database

Operations: If valid username and password is entered user/data converter/admin can login.

Arguments: None

Returns: None

Pre-condition: Click the login button.

Post-condition: Login is successful.

Exceptions: If username or password is wrong, user/data converter/admin cannot login and

application gives an error message.

Flow of Events:

1. Entering the username and password.

2. Click the login button.

3. System directs the form pages according to the type of client.

5.3.1.2 Admin Page

Name: Admin Page

Type: Form Page

Description: There are some buttons named as update the inventory, add new company, add new user and

make back-up. By clicking these buttons, system directs the admin to form pages.

Attributes: None

Resources: None

Operations: Admin can reach other form pages with clicking buttons.

Arguments: None

22

Returns: None

Pre-condition: Click the buttons.

Post-condition: None

Exceptions: If clicked form page does not exist, admin cannot reach that form pages, and


Flow of Events:

1. Admin click the buttons.

2. System directs the form pages according to the clicked button.

5.3.1.3 User Page

Name: User Page

Type: Form Page

Description: There are some buttons named as Create Detailed Order Form, Create Order Form, List

Orders, List Company Orders, Check Inventory. By clicking these buttons, system directs the user to form

pages.

Attributes: None

Resources: None

Operations: User can reach other form pages with clicking buttons.

Arguments: None

Returns: None

Pre-condition: Click the buttons.


Exceptions: If clicked form page does not exist, user cannot reach that form pages, and


Flow of Events:

1. User click the buttons.

23

2. System directs the form pages according to the clicked button.

5.3.1.4 Data Converter Page

Name: Data Converter Page

Type: Form Page

Description: There is one button named as Import Data. By clicking this button, system directs the user to

form page.

Attributes: None

Resources: None

Operations: Data Converter can reach Import Data form page with clicking button.

Arguments: None

Returns: None

Pre-condition: Click the button.


Exceptions: If clicked form page does not exist, data converter cannot reach that form

page, and application gives an error message.

Flow of Events:

1. Data converter click the button.

2. System directs the form page according to the clicked button.

5.3.1.5 Add New User Page

Name: Add New User Page

Type: Form Page

24

Description: There is one button and some text boxes. Admin enters the fields like name, surname,

username, password. After finishing this, admin clicks the add button.

Attributes: username: String

password: String

name: String

surname: String

Resources: Database

Operations: Admin enter the fields then click the add button.

Arguments: None

Returns: None


Post-condition: New user is added successfully.

Exceptions: If username is already existing or the fields is empty, application gives an

error message.

Flow of Events:

1. Admin enters the fields.


5.3.1.6 Add New Company Page

Name: Add New Company Page

Type: Form Page

Description: There is one button and some text boxes. Admin enters the fields like company name,

address, telephone, mail. After finishing this, admin clicks the add button.

Attributes: company name: String

address: String

telephone: Int

Mail: String

25

Resources: Database

Operations: Admin enter the fields then click the add button.

Arguments: None

Returns: None


Post-condition: New company is added successfully.

Exceptions: If company is already existing or the fields is empty, application gives an error

message.

Flow of Events:

1. Admin enters the fields.


5.3.1.7 Update Inventory Page

Name: Update Inventory Page

Type: Form Page

Description: There is one grid view. In the grid view, the stock fields are automatically get to text boxes.

At the end of the fields, there are one button named update. Admin can update the stock with the update

button in the grid view.

Attributes: stock_name: String

price: Double

quantity: Int

color: String

length: Double

width: Double

Resources: Database

Operations: Admin update the stock fields then click the update button.

26

Arguments: None

Returns: None

Pre-condition: Click the update button.

Post-condition: Stocks are updated successfully.

Exceptions: If database connection is failed, application gives an error message.

Flow of Events:

1. Admin update the stocks fields.

2. Admin clicks the update button.

5.3.1.8 Import Data Page

Name: Import Data Page

Type: Form Page

Description: There are two grid views. In the first grid view, our stock fields are automatically get to

labels. In the second grid view, other company stock fields are automatically get to labels. Data converter

sees the two grid views and decide to which stocks are import. At the end of the fields, there are one

button named import. Data converter can import the two stocks with the import button in the grid views.

Attributes: stock_name_ourcompany: String

price_ourcompany: Double

quantity_ourcompany: Int

color_ourcompany: String

length_ourcompany: Double

width_ourcompany: Double

stock_name_othercompany: String

price_othercompany: Double

quantity_othercompany: Int

color_othercompany: String

length_othercompany: Double

width_othercompany: Double

27

Resources: Database

Operations: Data converter import the two stock fields then click the import button.

Arguments: None

Returns: None

Pre-condition: Click the import button.

Post-condition: Two stocks are imported successfully.

Exceptions: If the stock in the price list is missing in our company, stock can’t be

imported.

Flow of Events:

1. Data converter selects the two stocks.

2. Data converter clicks the import button.

5.3.1.9 List Orders Page

Name: List Orders Page

Type: Form Page

Description: There is one grid view. All companies total amount of the orders is listed in the grid view.

There are two buttons which names are print and send mail. User can click the buttons if he/she want to

print the order list or send email.

Attributes: company_name: String

total_amount(kdv+amount): Double

vat: Double

amount: Double

Resources: Database

28

Operations: User can display the companies and their total amount of orders. He/she can click the print or

send email buttons.

Arguments: None

Returns: None

Pre-condition: None

Post-condition: Orders are listed successfully.


Flow of Events:

1. User clicks the list order button in the user form page and program automatically list the orders.

5.3.1.10 List Company Orders Page

Name: List Company Orders Page

Type: Form Page

Description: There is one grid view and drop down list. All companies are listed in the drop down list.

User choose the one of them and orders of the chosen company will be shown in the grid view. There are

two buttons which names are print and send mail. User can click the buttons if he/she want to print the

order list or send email.

Attributes: company_name: String

total_amount(kdv+amount): Double

vat_percent: Int

amount: Double

date: Date

order_name: String

order_number: Int

Resources: Database

29

Operations: User selects the company in the drop-down list. Program automatically lists the orders and

their attributes. He/she can click the print or send email buttons.

Arguments: None

Returns: None

Pre-condition: User selects the company in the drop-down list.

Post-condition: The selected company orders are listed successfully.


Flow of Events:

1. User selects the company in the drop-down list and program automatically list the selected

company orders.

5.3.1.11 Create Detailed Order Form Page

Name: Create Detailed Order Form Page

Type: Form Page

Description: There is one grid view and the create button. There are also create order form button. This

button make transition to create order form page. In the grid view, there are text boxes in the columns.

User enter the fields in the text boxes and clicks the create button. There are two buttons which names are

print and send mail. User can click the buttons if he/she want to print the order list or send email.

Attributes: stock_code_ourcompany: String

stock_code_othercompany: String

stock_type: String

length: Int

width: Int

color: String

amount: Double

exchange_value: String

exchange_amount: Double

30

exchange_rate: Double

discount_percent: Int

vat_percent: Int

discount_amount: Double

vat_amount: Double

total_amount: Double

quantity: Double

Resources: Database

Operations: User enters the order fields and clicks the create button. After the necessary operations,

program automatically create detailed order form. He/she can click the print or send email buttons.

Arguments: None

Returns: None

Pre-condition: User enters the order fields and clicks the create button.

Post-condition: Detailed order form is created successfully.

Exceptions: If user does not enter the necessary fields, application gives an error message

and form can’t be created.

Flow of Events:

1. User enters the necessary fields.

2. User clicks the create button.

5.3.1.12 Create Order Form Page

Name: Create Order Form Page

Type: Form Page

Description: There is one grid view. In the grid view, there are text boxes in the columns. Previously, user

create a detailed order form and then he/she clicks the create order form button. Program automatically

31

combine the same stock codes in the detailed order form and list these combinations in this form. User

can click the buttons if he/she want to print the order list or send email.

Attributes: stock_code_ourcompany: String

stock_code_othercompany: String

stock_type: String

amount: Double

exchange_value: String

exchange_amount: Double

exchange_rate: Double

discount_percent: Int

vat_percent: Int

discount_amount: Double

vat_amount: Double

total_amount: Double

quantity: Double

Resources: Database

Operations: User clicks the create order form button in the create detailed order form page. After the

necessary operations, program automatically create order form. He/she can click the print or send email

buttons.

Arguments: None

Returns: None

Pre-condition: User clicks the create order form button in the create detailed order form

page.

Post-condition: Order form is created successfully.

Exceptions: None

Flow of Events:

1. User clicks the create order form button in the create detailed order form page.

32

2. Program automatically create the order form.

5.3.1.13 Check Stock Page

Name: Check Stock Page

Type: Form Page

Description: There is one grid view. In the grid view, there are stock fields in the columns. User can see

the stock’s name, code, type, amount, price, length, width and color.

Attributes: name: String

code: String

type: String

amount: Int

price: Double

length: Int

width: Int

color: String

Resources: Database

Operations: User clicks the list stocks button. Program automatically list the stock’s fields.

Arguments: None

Returns: None

Pre-condition: User clicks the list stocks button.

Post-condition: Stocks and their fields are listed in the grid view successfully.


Flow of Events:

1. User clicks the list stocks button.

2. Program automatically list the stock’s fields.

5.3.2 Database Diagram

33

Figure 14: Database Diagram

5.3.2.1 Users Table

Users table holds the user’s information. Users has attributes such as; id, name, surname, username, user

email, isActive, usertypeid and user password. User id is primary key of table.

5.3.2.2 Users Type Table

Users type table keeps the information of user type fields. User type fields has attributes such as;

userTypeid and UserType. UserTypeid is primary key of table.

5.3.2.3 Sırket Table

Sırket table stores the information of companies. Sırket table has attributes such as; companyid,

companyname, companyaddress, companyphone, isActive and companyemail. Company id is primary

key of table.

34

5.3.2.4 Sırket_Malzeme Table

Sırket_Malzeme table includes information of materials of companies. Sırket_Malzeme table has

attributes such as; SirketMalzemeid, birim, yeri, fiyat, doviz, tenzilat, malzemesayisi, kdvOrani,

kdvHariçFiyat, kdvDahilFiyat and isActive and Sirketid and Malzemeid as a foreign key references from

Sirket table and Malzeme table. SirketMalzemeid is primary key of table.

5.3.2.5 Malzeme Table

Malzeme table keeps type of materials forms. This table has attributes like; Malzemeid, MalzemeTuru

and BizimKodid. Also, BizimKodid is foreign keys of BizimKod table. Malzemeid is a primary key of

table.

5.3.2.6 BizimKod Table

BizimKod table holds more information of our company. This table has attributes like; BizimKodID,

BizimKod. Foreign keys of table are SFKodID and SirketID.

5.3.2.7 SFKod Table

SFKod table holds more information of our company. This table has attributes like; SFKodID, SFKod.

Primary key of the table is SFKodID.

5.3.2.6 Siparis Table

Siparis table holds more information of our company. This table has attributes like; ID, SiparisID,

SiparisName, SirketID, SirketMalzemeID, Tarih, En, Boy, Adet, Yeri, DovizKuru, DovizCinsi, Fiyat,

Tenzilat, KdvOrani, TenzilatTutari, KdvTutari, Tutar, Miktar and Aciklama. Foreign keys of table are

SirketID and SirketMalzemeID.

35

5.3.3 Block Diagram

Figure 15: Block Diagram of the Application

5.3.3.1 Brief Description of Figure 15

In the application block diagram, there are six main components and their sub-components. Components

and sub-components have been visualized as rectangular shapes on the block diagram. The main

components are listed below:

5.3.3.2 Login Design

Login design provides to clients to enter the application as user/admin/data converter. According to the

client type, it allows to reach the related form pages.

36

5.3.3.3 List Operations Design

List operations design allows to the user to list previous orders. This design includes database queries of

previous orders, also client can see orders of the chosen company.

5.3.3.4 Send Operations Design

In the all form pages, have send and print button. This design includes mail protocols and connections to

send e-mail. Also, code of print button has printer connection to print the data.

5.3.3.5 Stock Operations Design

Stock operations design totally works with database connection. All operations related about the stock,

has been accomplished in the database. Moreover, this design allows to the admin to make backup of the

database. Also, in this design, data converter can import the data which is sending by the other companies

to the system.

5.3.3.6 Create Operations Design

Purpose of our application helps to the client to create detailed order form. This design includes some

calculation codes according to stock price and amounts, as a result of these calculations detailed bill has

been created.

5.3.3.7 Adding Operations Design

Adding Operations Design is similar like register operation, but in this design, only admin can add

company or user into the system. Information of companies and users directly send to the database in this

design.

37

5.3.4 Interface Design

Figure 16: Login Page Design

Figure 17: Admin Page Design

38

Figure 18: Add New Company Page Design

Figure 19: Add New User Page Design

39

Figure 20: Update Stock Page Design

Figure 21: User Page Design

40

Figure 22: Order List Page Design

Figure 23: Company Orders List Page Design

41

Figure 24: Create Invoice Page Design

6. INTRODUCTION

6.1 Version Control

Version No Description of Changes Date

1.0 First Version April 14, 2017

6.2 Overview

Functions of software will be tested in this document.

6.3 Scope

This document includes test cases of software.

6.4 Terminology

Acronym Definition

LG Login

42

Acronym Definition

LO List Operations

SO Send Operations

AO Adding Operations

STO Stock Operations

CO Create Operations

7. FEATURES TO BE TESTED

7.1 Login (LG)

Login feature provides to enter the system for Admin, User and Data Converter.

7.2 List Operations(LO)

List operations provide to list general orders and orders of company.

7.3 Send Operations(SO)

Send operations provide to send e-mail for the order forms, general order forms, orders of company and

detailed order forms.

7.4 Adding Operations(AO)

Adding operations provide to add user and company into the system by admin.

7.5 Stock Operations(STO)

Stock operations provide some functions which are inventory operations (update inventory, check

inventory), make back-up, import data.

7.6 Create Operations(CO)

Create operations provide to create general order form and detailed order form by user.

43

8. ITEM PASS/FAIL CRITERIA

8.1 Exit Criteria

Application is successful under this condition:

All High and Medium Priority test cases passed

9. TEST DESIGN SPECIFICATIONS

9.1 Login (LG)

9.1.1 Subfeatures to be tested

9.1.1.1 Admin (LG.AD)

Admin can enter to the system.

9.1.1.2 User (LG.US)

User can enter to the system.

9.1.1.3 Data Converter (LG.DC)

Data converter can enter to the system.

9.1.2 Test Cases

Here list all the related test cases for this feature

TC ID Requirements Priorit

y Scenario Description

LG.AD.01

LG.US.01

LG.DC.01

2.2.4 H Enter a valid user name and password

LG.AD.02

LG.US.02

LG.DC.02

2.2.4 H Enter a false user name or password

9.2 List Operations (LO)


9.2.1.1 General Order (LO.GO)

General Order can be listed by user.

9.2.1.2 Order of Company (LO.OC)

Order of company can be listed by user according to choosen company.

9.2.2 Test Cases


9.3 Send Operations (SO)


9.3.1.1 General Order (SO.GO)

General Order can be printed by user.

9.3.1.2 Order of Company (SO.OC)

Order of company can be printed by user according to chosen company.

9.3.1.3 Order Form (SO.OF)

Order Form can be e-mailed or printed by user.

TC ID Requirement

s

Priori

ty Scenario Description

LO.GO.01 2.2.1.1 M List a valid general order form

LO.GO.02 2.2.1.1 M General order form does not exist.

LO.OC.01 2.2.1.1 M List a selected company’s orders.

LO.OC.02 2.2.1.1 M Order form of company does not exist.

45

9.3.1.4 Detailed Order Form (SO.DOF)

Detailed Order Form can be e-mailed or printed by user.

9.3.2 Test Cases


9.4 Adding Operations (AO)


9.4.1.1 User (AO.US)

User can be added by admin.

9.4.1.2 Company (AO.COM)

Company can be added by admin.

TC ID Require

ments

Priori


SO.GO.01

SO.OC.01

SO.OF.01

SO.DOF.01

2.2.1.3 L Print a valid form.

SO.GO.02

SO.OC.02

SO.OF.02

SO.DOF.02

2.2.1.3 L E-mail a valid form.

46

9.4.2 Test Cases


9.5 Stock Operations (STO)


9.5.1.1 Inventory (STO.IN)

Inventory can be updated and checked by admin.

9.5.1.2 Update (STO.IN.UP)

Inventory can be updated by admin.

9.5.1.3 Check (STO.IN.CH)

Inventory can be checked by admin.

9.5.1.4 Make Back-Up (STO.BCK)

Admin can make back-up the system.

9.5.1.5 Import Data (STO.IMP)

Data Converter can import data to the database.

TC ID Requiremen

ts

Priori


AO.US.01

2.2.2 M Enter the fields correctly.

AO.US.02

2.2.2 M Enter the same username.

AO.COM.0

1 2.2.2 M Enter the field correctly.

47

9.5.2 Test Cases


9.6 Create Operations (CO)


9.6.1.1 General Order (CO.GO)

General order can be created by user.

9.6.1.2 Detailed Order (CO.DO)

Detailed order can be created by user.

9.6.2 Test Cases


TC ID

Requir

ement

s

Priori


STO.IN.UP.01

STO.IN.CH.01

2.2.1.4 M A valid stock is updated and checked.

STO.BCK.01

2.2.2 M Back-Up is completed.

STO.IMP.01 2.2.2 M Data is imported.

TC ID Requirements Priorit

y Scenario Description

CO.GO.01

2.2.1.2 H General order form created successfully.

CO.GO.02 2.2.1.2 H General order form could not be created.

48

10. DETAILED TEST CASES

10.1 Login(LG)

10.1.1 LG.AD.01, LG.US.01, LG.DC.01

TC_ID LG.AD.01, LG.US.01 , LG.DC.01

Purpose The client enter the system successfully.

Requirements 2.2.4

Priority High.

Estimated Time

Needed

2 Minutes

Dependency Add User test cases should pass

Setup An admin, user and data converter should be logged.

Procedure [A01] Go to login page.

[A02] Enter a valid user name.

[A03] Enter the valid password for this user

[A04] Click on the “Login” button.

[V01] Observe that the login is successful and the

admin, user, data converter pages appears

Cleanup Logout

10.1.1.1 LG.AD.02, LG.US.02, LG.DC.02

TC_ID LG.AD.02, LG.US.02, LG.DC.02

Purpose The client can not enter the system.

Requirements 2.2.4

Priority High.

Estimated Time

Needed

2 Minutes

CO.DO.01 2.2.1.2 H Detailed order form created successfully.

CO.DO.02 2.2.1.2 H Detailed order form could not be created.

49

Dependency Add User test cases should pass

Setup An admin, user and data converter should be logged.

Procedure [A01] Go to login page.

[A02] Enter a wrong user name.

[A03] Enter the wrong password for this user

[A04] Click on the “Login” button.

[V01] Observe that the login is not accomplished, give

error “wrong user name or password”.

Cleanup Logout

10.2 List Operations(LO)

10.2.1 LO.GO.01

TC_ID LO.GO.01

Purpose Client can list general orders successfully.

Requirements 2.2.1.1

Priority Medium.

Estimated Time

Needed

1 Minutes

Dependency Login test cases should pass

Setup General orders should be displayed.

Procedure [A01] Go to user page

[A02] Click the list general order button

[V01] Observe that the general orders are displayed.

Cleanup Back - Logout

10.2.2 LO.GO.02

TC_ID LO.GO.02

Purpose General orders could not be listed.


Priority Medium.

Estimated Time

Needed

1 Minutes

Dependency Login test cases should pass

Setup General orders should not be displayed.


[A02] Click the list general order button

50

[V01] System gives an error “There is no order to

display”.


10.2.3 LO.OC.01

TC_ID LO.CO.01

Purpose Client can list orders of company successfully.


Priority Medium.

Estimated Time

Needed

1 Minutes

Dependency Login test cases should pass and company should be select.

Setup Orders of company should be displayed.


[A02] Click the list order of company button

[A03] Choose the company.

[V01] Observe that order of copmanies are displayed.

Cleanup Back – Logout

10.2.4 LO.OC.02

TC_ID LO.CO.02

Purpose Orders of company could not be listed.


Priority Medium.

Estimated Time

Needed

1 Minutes

Dependency Login test cases should pass and company should be select

Setup Orders of company should be displayed.


[A02] Click the list order of company button

[A03] Choose the company.

[V01] System gives an error “There is no order to

display”.


51

10.3 Send Operations(SO)

10.3.1 SO.GO.01, SO.OC.01, SO.OF.01, SO.DOF.01

TC_ID SO.GO.01, SO.OC.01, SO.OF.01, SO.DOF.01

Purpose Printing recent forms.


Priority Low.

Estimated Time

Needed

5 Minutes

Dependency Add related test cases should pass.

Setup Forms should be printed.


[A02] Select a form.

[A03] Click the print button.

[V01] Observe that form is printed.


10.3.2 SO.GO.02, SO.OC.02, SO.OF.02, SO.DOF.02

TC_ID SO.GO.02, SO.OC.02, SO.OF.02, SO.DOF.02

Purpose E-mail recent forms


Priority Low.

Estimated Time

Needed

5 Minutes

Dependency Add related test cases should pass.

Setup E-mail should be send.

Procedure [A01] Go to user page.

[A02] Select a form.

[A03] Click the e-mail button.

[V01] Observe that form is sended.


52

10.4 Adding Operations (AO)

10.4.1 AO.US.01

TC_ID AO.US.01

Purpose Adding new user.

Requirements 2.2.2

Priority Medium.

Estimated Time

Needed

5 Minutes

Dependency Login test cases should pass.

Setup New user should be added.

Procedure [A01] Go to admin page.

[A02] Click add user button.

[A03] Enter the fields.

[V01] Observe that new user is added.


10.4.2 AO.US.02

TC_ID AO.US.02

Purpose Adding new user is not created

Requirements 2.2.2

Priority Medium.

Estimated Time

Needed

5 Minutes


Setup New user should not be added.


[A02] Click add user button.

[A03] Enter the same username.

[V01] Observe that new user cannot be added.


10.4.3 AO.COM.01

TC_ID AO.COM.01

Purpose Adding new company is added

Requirements 2.2.2

Priority Medium.

Estimated Time

Needed

5 Minutes

53


Setup New company should be added.


[A02] Click add company button.

[A03] Enter the fields.

[V01] Observe that new company is added.


10.5 Stock Operations (STO)

10.5.1 STO.IN.UP.01, STO.IN.CH.01

TC_ID STO.IN.UP.01, STO.IN.CH.01

Purpose Stock is updated or checked by admin


Priority Medium.

Estimated Time

Needed

4 Minutes


Setup Stock should be updated and checked.


[A02] Click update button.

[A03] Select stock name.

[A04] User check or update the selected stock.

[V01] Observe that stock fields are updated or checked.


10.5.2 STO.BCK.01

TC_ID STO.BCK.01

Purpose System is made back-up by user.

Requirements 2.2.2

Priority Medium.

Estimated Time

Needed

5 Minutes


Setup System back-up should be made.

54


[A02] Click make back-up button.

[V01] Observe that back-up is taken.


10.5.3 STO.IMP.01

TC_ID STO.IMP.01

Purpose Data is imported by data converter.

Requirements 2.2.2

Priority Medium.

Estimated Time

Needed

5 Minutes


Setup Data should be imported.

Procedure [A01] Go to data converter page.

[A02] Select another company price list.

[A03] System automatically parse the price list and ask

the data converter to match the stock.

[A04] Data converter choose a stock name which he/she

want to match.

[V01] Observe that importing data is successful.


10.6 Create Operations (CO)

10.6.1 CO.GO.01

TC_ID CO.GO.01

Purpose General order form is created by user.


Priority Medium.

Estimated Time

Needed

10 Minutes


Setup General order form should be created.


[A02] Click general order form button.

[A03] Select company and fill in the blanks.

[A04] Click the create button.

[V01] Observe that general order form is created

successfully.


55

10.6.2 CO.GO.02

TC_ID CO.GO.02

Purpose General order form could not be created by user.


Priority Medium.

Estimated Time

Needed

10 Minutes


Setup General order form should not be created.


[A02] Click general order form button.



[V01] Observe that general order form could not be

created.


10.6.3 CO.DO.01

TC_ID CO.DO.01

Purpose Detailed order form is created by user.


Priority Medium.

Estimated Time

Needed

10 Minutes


Setup Detailed order form should be created.

Procedure [A01] Go to general order form page.

[A02] Click detailed order form button.



[V01] Observe that detailed order form is created.


56

10.6.4 CO.DO.02

TC_ID CO.DO.02

Purpose Detailed order form could not be created by user.


Priority Medium.

Estimated Time

Needed

10 Minutes


Setup Detailed order form should not be created.

Procedure [A01] Go to general order form page.

[A02] Click detailed order form button.



[V01] Observe that detailed order form could not be

created.


11. TEST RESULTS

11.1 Individual Test Results

TC ID Priority Date Run Run By Result Explanation

LG.AD.01

LG.US.01

LG.DC.01

H 16.05.2017 Tuğçe Hilal

Şen

Pass Clients login

to the system

successfully.

LG.AD.02

LG.US.02

LG.DC.02

H 16.05.2017 Tuğçe Hilal

Şen

Pass Clients

couldn’t login

to the system.

LO.GO.01 M 16.05.2017 Tuğçe Hilal

Şen

Pass Order form

has been

listed.

LO.GO.02 M 16.05.2017 Tuğçe Hilal

Şen

Pass Order form

hasn’t been

listed.

LO.OC.01 M 16.05.2017 Tuğçe Hilal

Şen

Pass Selected

company’s

orders have

been listed.

LO.OC.02 M 16.05.2017 Tuğçe Hilal

Şen

Pass Selected

company’s

orders

haven’t been

listed.

57

SO.GO.01

SO.OC.01

SO.OF.01

SO.DOF.01

L 16.05.2017 Barış

Işıkpunar

Pass Forms have

been printed

successfully.

SO.GO.02

SO.OC.02

SO.OF.02

SO.DOF.02

L 16.05.2017 Barış

Işıkpunar

Pass Forms have

been e-mailed

successfully.

AO.US.01 M 16.05.2017 Barış

Işıkpunar

Pass User has been

added

correctly.

AO.US.02 M 16.05.2017 Barış

Işıkpunar

Pass User hasn’t

been added.

AO.COM.01 M 16.05.2017 Barış

Işıkpunar

Pass Company has

been added

correctly.

STO.IN.UP.01

STO.IN.CH.01 M 16.05.2017 Barış

Işıkpunar

Pass Stock has

been updated

and checked.

STO.BCK.01 M 16.05.2017 Ahmet

Gündoğdu

Not

Executed

This part

hasn’t been

implemented

yet.

STO.IMP.01 M 16.05.2017 Ahmet

Gündoğdu

Not

Executed

This part

hasn’t been

implemented

yet.

CO.GO.01 M 16.05.2017 Ahmet

Gündoğdu

Pass General order

form has been

created.

CO.GO.02 M 16.05.2017 Ahmet

Gündoğdu

Pass General order

form hasn’t

been created.

CO.DO.01 M 16.05.2017 Ahmet

Gündoğdu

Pass Detailed

order form

has been

created.

CO.DO.02 M 16.05.2017 Ahmet

Gündoğdu

Pass Detailed

order form

hasn’t been

created.

58

11.2 Summary of Test Results

Priority Number of TCs Executed Passed

H 2 2 2

M 14 12 12

L 2 2 2

Total 18 16 16

We execute 18 test cases and 16 test cases passed. Also, 2 of high, 12 of medium and 2 of low

priority test cases passed. Exit criteria were met.

11.3 Exit Criteria

We execute all test cases and 89% of test cases passed. Also, 11% of high, 67% of medium

and 11% of low priority test cases passed. However, 11% of medium priority test cases have

not executed. Software development activities are completed within the projected cost.

Software development activities is completed within the projected timelines. Exit criteria

were met.

Criteria Met or Not

100% of the test cases are executed N

89% of test cases passed Y

11% of high priority test cases passed Y

67% of medium priority test cases passed Y

11% of low priority test cases passed Y

Verify if software development activities

are completed within the projected cost

Y

Verify if software development activities

are completed within the projected

timelines.

Y

11.4 Known Problems

There are two medium priority test cases that are not executed. We have not implemented

these parts of the system yet.

59

11.5 Conclusion

This part of the project represents the test result of the project that “Metrajlı Stok Kontrol

Programı”. We have created our test plan and exit criteria to the project. Our project was met

most exit criteria and we will try to implement rest of the project.

12. CONCLUSİONS

As a conclusion, companies who want to grow their business, need enterprise resource

planning(ERP). ERP supplies to use resources efficiently in the firms. It includes some

software like inventory management systems, accounting management systems and workforce

planning. Therefore, in this project, we aimed to develop inventory management system that

is a part of enterprise resource planning.

Purpose of the project is adding the detailed order form in addition to existed

inventory management systems. This form provides the user to enter the size of the stocks and

makes invoice. Moreover, one of the property of the program is importing data. It helps the

company to import the prices of the other companies’ stocks and combines the stock codes.

Use case diagrams which include stakeholders, actors and their functions explained in

the SRS (Software Requirements Specification) part for create clear explanation. Deployment,

database and block diagram, architecture design and interface design is explained in the SDD

(Software Design Document) part.

In the future, we will try to make this project closer to ERP (Enterprise Resource

Planning) by adding accounting and customer relationship management software because the

need of these software is increasing day by day.

Acknowledgement

We would like to thank our advisor: Assoc. Prof. Dr. Hadi Hakan MARAŞ for his worthful

suggestions and supports. Also, thanks should be also given to our supervisor: Abdülbaki

GÖKTÜRK from Sufle Mobilya for his professional guidance.

60

References

[1] Ş. Çiğdem, “Development of A Database Management System For Small and Medium

Sized Enterprises,” April 2005.

[2] W. D. Clifford, “Is the SAS® System a Database Management System?,” Austin.

[3] L. Soriano, “Analyze The Stock Market Using the SAS System”.

[4] V. F. Wolfe, K. F. Lau and S. Westin, “Real-Time Object-Oriented Database Support For

Program Stock Trading”.

[5] R. G. Healey, Database Management Systems, 2016, pp. 251-263.

[6] E. J. Umble, R. R. Haft and M. M. Umble, "Enterprise resource planning:

Implementation procedures," European Journal of Operational Research , no. 146, pp.

241-242, 2003.

[7] A. Karaman Akgül and S. Gözlü, "Enterprise Resource

Planning Implementation: A Survey of Turkish Manufacturing

Organizations," Marmara Üniversitesi Öneri Dergisi, vol. 11,

no. 41, pp. 42-43, January 2014.

[8] EazyStock, "6 Ways to Boost Your Inventory Management System Performance".

61

[9] S. Shin, k. L. Ennis and W. P. Spurlin, "Effect Of Inventory Management Efficiency On

Profitability: Current Evidence from The U.S. Manufacturing Industry," Journal of

Economics and Economic Education Research, vol. 16, no. 1, p. 98, 2015.

[10] CSCO insights, "Five Strategies for Improving Inventory Management Across Complex

Supply Chain Networks," 2011.

[11] C. Circa, A. Almasan, R. Margea and C. Margea, "ERP Systems and Management

Accounting - Evolutions and Challenges," Young Economists Journal, p. 156.

[12] L. Motiwalla and J. Thompson, Enterprise Systems for Management, New Jersey,

Upper Saddle River: Person Education Inc., 2009.

[13] C. Spathis and S. Constantinides, "Enterprise Resource Planning systems' impact on

accounting processes," Business Process Management Journal, vol. 10, no. 2, 2004.

[14] L. E. Scurtu and V. Lupu, "Enterprise Resource Planning - ERP for business and

knowledge management," The USV Annals of Economics and Public Administration, vol.

1, no. 16, pp. 145-146, 2016.

Çankaya university

Documents