Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
(SRS)
On
INVENTORY MANAGEMENT SYSTEM
BACHELOR OF TECHNOLOGY IN
COMPUTER SCIENCE AND ENGINEERING
By
ERAMALLA ARAVIND
11709190
Roll No: B-35
Section: K17DM
E.ARAVIND
ROLLNO:B-35
Table of Contents
1. Introduction
1.1 Overview
1.2 Purpose
1.3 Scope
1.4 Glossary
1.5 Overview
2. Overall description
3. Specific Requirements
3.1 Functional Requirements
3.1.1 General functional requirements:
3.1.2 Functional Requirements for Production Controller
3.1.3 Functional Requirements for Production Supervisor
3.1.4 Functional Requirements for Administrator
3.1.5 Quality Function Depolyment
3.1.5.1 Normal Requirements
3.1.5.2 Excepted Requirements
3.1.5.3 Exciting Requirements
6. Constraints
6.1 Design constraints
This paper will be more easeful after communicating with our client with their more specific
requirements. At the same time, in this paper we will focus on Inventory management
module. Again this paper is a partial submission; more detail will be included as per
communicating with the entire stakeholder’s.
1.1 Purpose
The purpose of this document is to present a detailed description of the Online Inventory
Management System. It will explain the purpose and features of the system, the interfaces of
the system, what the system will do, the constraints under which it must operate and how the
system will react to external stimuli.
In this document we will try introduce our stakeholders along with their respective
viewpoints, describe the existing problem, combining those various view points, balancing
those to reach an ultimate “theoretical” solution of the identified problems, generating
graphical reviews through unified modeling language (UML) to formulate the problems and
the proposed solution, the project scope and the project schedule. Next we present the
solution including system analysis, the deviation between final and initial design, the function
of our Inventory management system and testing plan. Finally we evaluate our work on
different aspects, present areas of improvement and conclusion.
1.2 Scope
The outcome of the project would be automated inventory management service .The software
will have all common features and functionalities along with some other special facilities.
1.3 Glossary
QC Quality Control
PQ Production Controller
1.4 Overview
The next chapter is identifying stakeholders. In this chapter gives an over view who are
directly or indirectly depend on the developing system and what is their point of view.
The next chapter, the General Description section, of this document gives an overview of the
functionality of the product. It describes the informal requirements and is used to establish a
context for the technical requirements specification in the next chapter.
The Forth chapter, Requirements Specification section, of this document is written primarily
for the developers and describes in technical terms the details of the functionality of the
product.
All the sections of the document describe the same software product in its entirety,
.
2. Over Description
2.1 Product Perspective
In this modern world of commercialization, garments business has been established as one of
the flourishing in Bangladesh. It has been one of the most flourishing export sectors for our
country, as we have told in background. Now, our project is concerned with this sector. This
is a huge field to cover, as hundreds of manageable aspects can be found to maintain the
highest productivity of textile manufacturing. We choose the inventory management as our
preferred field to work.
To instantiate, this can be specified as a b2b system, from producers to abroad or home
dealers through some intermediate business nodes. The important deals that our RMG sector
are mostly from abroad interests, as stated above. And our goal would be facilitate this whole
process, from collecting raw materials to the finished product shipment.
Unlike the old days, RMG sector of Bangladesh has been implementing a variety of
management software, in order to enhance the productivity, and to satisfy the customers’
needs. As these deals are very sensitive to handle, and there are a lot of variables that must be
maintained, the need of online interaction between the buyer and the seller, or even seller to
seller, is a must, and can play a dramatic influence on these deals.
As the whole process has multiple steps to the way to finished goods, a single delay in a
single step can cause delay in the shipment schedule, suppose our delay in cutting can
demolish the required time structure, which can also cause financial damage and bad business
reputation.
The existing systems have been using not for so long, and the maturity level of software
industry in our country is still very low. So, the systems which are being used in recent days
in the garments industry do have a lot of bugs, functional dependencies and design
constraints. Besides, there is still a lacking of a complete solution for managing garments
which is yet to be made. And we have to say, after studying, we find that majority of the
garment industry doesn’t use any automated management system, where a large amount of
problems in manual management can be solved in automated system.
The thing is missing all through and which we have been planning to introduce in these kind
of usual management system, is online interface to control the system. Internet has been a
pivotal determiner in every aspects life. We are proposing to introduce internet controlling
module of this system, so that the authority of our client can monitor and manipulate the
system, as well as the database through the internet.
At the same time, there are technologies being used to manage payroll, appointments,
inventory, and in many other purposes. But as our major concerns will be inventory oriented,
we will focus the most on that.
2.2 Product Functions
Inventory Management System must be designed to meet the dictates of the marketplace and
support the company's strategic plan. Along with the inventory system Garment industries
need some more special attributes. The Software’s for Garment are specially made for
managing the various steps in order processing of garments manufacturing process. This
software is modular in design and is web enabled for remote access as well as intranet usage
without the need to install in every machine.
Inventory Management System has some features which are badly needed for a complete
Inventory system of Garment industries. So the features are,
These features are primary requirement of our client for this inventory management system.
This feature list will change in terms of client demand
Both users will be able to visit the homepage of the website but only the registered user is
allowed to give input in the system. To work through the system one user should go through
some fixed steps-
The administrator of this inventory system will have right to create product, add items delete
items etc. The application will provide all information of the products. The category will be
tagged with subcategory. Again the subcategories are tagged with different items in the
respective category and rate of the item. Each item will have a specific bar code. The rates
will be tagged to the bar code.
The application will also help to generate reports to get latest update on
Master Entry
Purchase order entry
Receive entry
Delivery entry
Report
3. Requirement Analysis
Requirement Analysis presents the requirement specification, software and hardware
requirements for both system developers and system users, process model and data model. In
this section we specify the External Interface Requirements, functional and nonfunctional
requirements of the system.
Login.
Browse desired modules.
Browse desired supervisor portfolio.
Notify the system about the module requirements.
Input product quantity after compiled.
Distribute requirements between the production supervisors.
Supervise inter-work station combination.
View production details with delivery date.
Browse through different production areas.
Balancing the check sheet.
Login.
Accessibility to the whole system.
Monitoring the total system as well as the database.
Giving the total goal of a deal as the input.
Clarifying the resources.
Distributing the job segments to the controllers.
Getting update information about the production.
Getting update information about production delay.
Getting update information about operation.
Invoice information collection.
Change settings
Quality function deployment is a method to transform user demands into design quality, to
deploy the functions forming quality, and to deploy methods for achieving the design quality
into subsystems and component parts, and ultimately to specific elements of the
manufacturing process.
QFD helps transform customer needs into engineering characteristics for a product or service,
prioritizing each product or service characteristic while simultaneously setting development
targets for product or service.
Quality Function Deployment (QFD) can be categorized by-
Normal Requirements,
Expected Requirements, and
Exciting Requirements.
Normal requirements are those requirements which stakeholders want to be available in the
System. The normal requirements of this proposed application are given below-
The system will perform authorization of users for security purposes. All
the users as well as the administrator must have to perform this part.
If any kind of change will occur, there will be an update option in the
system, using that administrator can change the existing information.
The system must ensure database backups, which are as recent and
complete as possible
Check sheet, production planning, and backup files should be in readable
file format or in crystal reports format.
Order will be issued according to buyer name. This will help authority to
deal with their respected buyer.
Exciting requirements are those requirements which stakeholders not actually want but these
requirements have to fulfill to make the system interesting. The exciting requirements for our
proposed system are given below-
Production planning with investment and estimated profit will be
calculated through the system.
Normal users and administrators have to login through different login
page which will ensure that, without administrator no one can change
any information of a production as well as the system.
System has the notifying system for any kind of delay occurs in the
given period. But the system can notify the dependent working group
supervisors if the administrators need them.
Administrators can distribute the job segments to the controllers.
4. Requirement Analysis
Requirement Analysis presents the requirement specification, software and hardware
requirements for both system developers and system users, process model and data model. In
this section we specify the External Interface Requirements, functional and nonfunctional
requirements of the system.
Server:
Internet Information system
MsSQL server 2008.
MVC 3.
Client:
JavaScript.
OpenSSL.
JavaScript (synchronous/asynchronous) Enable Browser.
4..4 Communications Interfaces
All sorts of communications between server and client programs will be using ADO.NET
(ActiveX Data Objects for .NET) is a set of computer software components that programmers
can use to access data and data services. It is a part of the base class library that is included
with the Microsoft .NET Framework. It is commonly used by programmers to access and
modify data stored in relational database systems, though it can also access data in non-
relational sources and the messaging will be done by XML format.
5.1 Performance
Our proposed inventory management system will be used in Garment industry. There are lot
of internal and external operation which are inter-related with each other for fruit full
production. So the communication among each end system should be tightly scheduled and
the notification should be sent in timely manner.
5.2 Reliability
The production process in the garment industries is a combination of different operations,
which generate lots of data. These data lose can cause high damage to a specific module as
well as to the total process. So if the reliability is not confirmed, this lacking will affect the
production performance.
5.3 Availability
This system will be dedicated to a particular client. So the availability will be restricted of
this system.
5.4 Security
This system will deal with huge amount of data. So security is a prime issue of our system.
So the system should be secured from external interfere by providing efficient security to the
entire system.
5.5 Maintainability
Software maintenance in software engineering is the modification of a software product after
delivery to correct faults, to improve performance or other attributes. Maintainability of
software is categorized in four classes:
Adaptive – dealing with changes and adapting in the software environment.
Perfective – accommodating with new or changed user requirements which concern
functional enhancements to the software.
Corrective – dealing with errors found and fixing it.
Preventive – concerns activities aiming on increasing software maintainability and
prevent problems in the future.
So to maintain our system we will try to concentrate on this four classes.
5.6 Portability
Portability is the degree to which software running on one platform can easily be converted
to run on another. Portability is hard to quantify, because it is hard to predict on what other
platforms the software will be required to run. So to make our system portable we have to
use languages, operating systems and tools that are universally available and standardized.
5.7 Operational Requirement
The team used MsSQL database to develop and maintain the database
management systems.
6 Constraints
6.1 Design constraints
When the project team is started to design the system, at that time the team always tries to
meet all the requirements of their client properly. But some time client’s make the job
difficult for the team to design the system by raising some last moment requirements. This is
considered as main constraints of designing a system.
7. Scenario Based Model
In software and systems engineering, a use case is a list of steps, typically defining
interactions between a role or actor and a system, to achieve a goal. The actor can be a human
or an external system.
Initially after analyzing the requirements of our client we notify two potential actors in our
proposed system. But this can change any time when their requirements are modified.
So in this system normal users are production controllers. They can browse through their
production related modules. They can view all the production details, all the partial
production areas related to their production, can create check sheet according to order
quantity.
Figure : Use Case Diagram
On the other hand admin can change system settings, update operation information, Update
production information etc
7.2 Activity Diagram
If we consider the given activity diagram, it will easier for us to find out step-by step
operational workflows of total system. When the process starts it will allow a user to select
his/her own authentication. If the user logged in as an Administrator, the user has the
authority to select operation between change settings of the working module and update
information of the production.
8. Flow model
Data flow diagram
A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system, modeling its process aspects. Often they are a preliminary step used to
create an overview of the system which can later be elaborated. DFDs can also be used for
the visualization of data processing .
A DFD shows what kinds of data will be input to and output from the system, where the data
will come from and go to, and where the data will be stored. It does not show information
about the timing of processes, or information about whether processes will operate in
sequence or in parallel
DFD level 0 , is the representation of the system which can only shows the inputs and outputs
of the system without dealing with any function and file or database issue. In the given figure
this is the data flow diagram (Level 0) for our proposed inventory management system.
Control panel and the planning is two input entity which can give data command to the
system, all the inputs will process in the system and the outputs will view in the display panel
or as notification. And the system also can produce check sheet according to given planning.
Figure : Data Flow Diagram (Level 1)
DFD level 1, is the representation of the system which can visualize the relation among the
functions and the file or database with the inputs and outputs. Control panel and planning
entity can give input command to the system, which can process by some functions in this
system like interact with user, configure, and update input, display status. There is a database
related with configure function which one can modify production information. And display
status, notification, check sheet can produce output depend on all the functions which
configure inputs.
9. Class Model
Class Diagram
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type
of static structure diagram that describes the structure of a system by showing the system's
classes, their attributes, operations or methods, and the relationships among the classes.
In the above exposed diagram ‘Module’ is the parent class which has two child classes
‘Administrator’ and ‘Production Controller’. Order Class deals with all the steps related to
order and maintained by administrator. ‘Store ‘and ‘Shipment’ class maintained by
production controller.
10.Sequence Diagram