Project Synopsis

1. Title Of the Project: Plywood Office Management

2. Objective of the project:

Main aim of developing: Plywood Office Sales and Inventory Management is to provide an easy way not only to automate all functionalities of a Plywood manufacturing companies office, but also to provide full functional reports to top management of company with the finest of details about every aspect of wood inventory and sales.

We are committed to bring the best way of management in the various forms of POSIM. We understand that POSIM in not a product to be sold, it is a tool to manage the inner operation of plywood manufacturing company from inventory of finished products to sales.

3. Project Category: RDBMS

4. Front End: VB.Net

5. Back End: Ms Access

6. Platform : Windows XP,DOT NET Framework 2.0

7. Software Requirements: Microsoft Visual Studio 2008 MS Access 2003

8. Hardware Requirements Processor: Pentium 4 or above RAM :256 MB

9. Modules

Inventory:This module manages the stock keeping and stock entry aspects of the plywood

manufacturing company.

Order Processing:This module deals with processing of the distributors/Client orders

Sales:This module deals with the actual sales of the product to distributor or client

10. Data Structure:

WoodTypeField Name Data Type Constraints DescriptionId Number Primary Key Unique id for WoodtypeWoodtype Text Not Null

CategoryField Name Data Type Constraints DescriptionId Number Primary Key Unique id for CategoryWoodetype Text Not NullCategory Text Not Null

GradeField Name Data Type Constraints DescriptionId Number Primary Key Unique id for GradeWoodetype Text Not NullCategory Text Not NullGrade Text Not Null

ProductField Name Data Type Constraints DescriptionId Number Primary Key Unique id for ProductProduct Text Not Null

Product UnitField Name Data Type Constraints DescriptionId Number Primary Key Unique id for Product

UnitProduct Text Not NullUnit Text Not Null

ProductPriceField Name Data Type Constraints DescriptionId Number Primary Key Unique id GradeId Number Not NullProductUnitId Number Not NullPrice Number Not Null

TaxField Name Data Type Constraints DescriptionTax Number Primary Key Unique id for WoodtypeTaxDesc Text Not NullPerc Number

CompanyInfoField Name Data Type Constraints DescriptionCompanyName TextAddress TextContactVATTIN TextCSTNO TextWebsite TextEmail Text

Product StockField Name Data Type Constraints DescriptionId Number Primary Key Unique id for Product

Stock entry GradeId Number Not NullProductUnitId Number Not NullProductSize Number Not NullStock Number Not Null

Login

Field Name Data Type Constraints DescriptionUId Text Primary Key Unique id Password Text Not Null

SalesMasterField Name Data Type Constraints DescriptionInvoiceNo Text Primary KeyInvDAte DAteTimeBuyerName TextBuyerAdd TextBuyerContact TextDespatchedBy TextDestination TextTerms TextAmount NumberTax NumberDiscount NumberTotalAmount NumberAmountInWords Text

SalesDetailsField Name Data Type Constraints DescriptionInvoiceNo Text Foreign KeyItem TextQuantity NumberRate NumberAmount NUmber

11. Any Other Information

12. Project Scope:

Software

Requirements

Specification

CHAPTER 2

Software Requirements Specification

Plywood Office Sales and Inventory Management 

Table of Contents 

1.0. Purpose 1.1. Introduction 1.2. Scope 1.3. Glossary 1.4. References 1.5. Document overview 2.0. Overall description 2.1. System environment 2.2. Product Functions 2.3 User Characteristics2.4 General Constraints 2.5 Assumption a and Dependencies3.0. Specific Requirements 3.1 External Interface Requirements 3.1.1 User Interface 3.1.2 Hardware Interface 3.1.3 Software Interface 3.1.4 Communication 3.2 Functional Requirements 3.3 Performance Constraints 3.4 Design Constraints

3.5 System Attributes 3.5.1 Reliability 3.5.2 Availability 3.5.3 Security 3.5.4 Maintainability 3.5.5 Portability

3.6 Other Requirements

1.0. Purpose

1.1. Introduction

This Software Requirements Specification provides a complete description of all the functions and specifications of the Plywood Office Sales and Inventory Management. The project will be supposed to implement the storage of products so that a large collection could be maintained with minimum storage space. This project will also be able to provide reports of products sold to the customer and brought to the store.

The expected audience of this document is the faculty of Computer Science, Govinda Dasa First Grade College, including the faculty who will use this system, Examiners of Mangalore University, and the developers. 

1.2. Scope

Main aim of developing: Plywood Office Sales and Inventory Management is to provide an easy way not only to automate all functionalities of Plywood manufacturing company’s office, but also to provide full functional reports to top management of company with the finest of details about every aspect of wood inventory and sales

We are committed to bring the best way of management in the various forms of POSIM. We understand that POSIM in not a product to be sold, it is a tool to manage the inner operation of plywood manufacturing company from inventory of finished products to sales.

 Definitions, Acronyms, Abbreviations

Report Generation:This is a client program which will request for reports.

 1.4. References Programming Visual Basic .NET, Second Edition by Jesse Liberty The needed requirements for this project has been obtained from the

stock by observing manual records and also gathered some of the

information by asking questions.

1.5. Document overview

Plywood Office Sales and Inventory Management is a process for implementing all sales and inventory activities of a plywood factory in a computerized automated way to promote sales by keeping inventory for large final selling products.

The primary purpose of this application is to implement the above stated functionality. The application should be capable enough to store the products and also perform some updating on the products that is stored. It will be having user friendly GUIs that will guide the user to easily achieve the same. The application shall also have some features like reports displaying in the same window.

In addition to this the application also supports feature to generate different kinds of reports. The application is to be fully developed under Dot Net using Visual Basic .Net

2. Overall description

2.1. System environment

POSIMDB

User

2.1 Product PerspectiveThis software is developed specifically to cater the needs of the office of Plywood Manufacturing Company (Apple Ply). It is totally self contained and works efficiently. It provides simple database rather than complex ones for high requirements and it provides good and easy graphical user interface to both new as well as experienced user of the computer.The product will be developed completely independent and standalone. Each user will have to have an individual copy of the product

2.2 Product FunctionsThe application functions are divided as follows.

Masters:This module creates the initial data required so that other functional modules can work open them. It maintains the basic records pertaining to Wood Type, Category, Grade, Product, Price, and Unit.

Inventory:This module accepts and records all the product stocks details of the Company. It also shows the current Stock details.

Order:This module deals with activities of accepting the order from the customers along with customers’ details and it stores order data for functioning of fulfilling Customer order.

Order Processing:This module attempts to make decisions related to Forward, Arrival, Delivering of ordered products based on the available stocks.

Sales:

This module handles activities of selling and delivering products to Customers and also maintains Sales records.

Reports:This module generates meaningful reports based on the data available.

This can be analyzed for betterment of the company.

2.3 User Characteristics The user of this product is supposed to be fairly educated about the usage of the

computers. Should know English Should be able to use and do according to the graphical user interface

2.4 General Constraints System must have windows OS installed on it. This Application must also be installed on the system

2.5 Assumption and DependenciesAssumptions:

The code should be free with compilation errors/syntax errors.

The product must have an interface which is simple enough to understand.

Dependencies:

All necessary hardware and software are available for implementing and use of

the tool.

The proposed system would be designed, developed and implemented based on

the software requirements specifications document.

End users should have basic knowledge of computer and we also assure that the

users will be given software training documentation and reference material.

3. Specific Requirements3.1 External Interface Requirements

3.1.1 User Interface The software provides good graphical interface for the front end which is

self explanatory. The user interface is designed in Visual Basic .NET. The developer will have to study the designing of the product. The use of the controls and the component from the Add items feature of the VB.

3.1.2 Hardware Interface 1)40 GB hard disk 2)256 MB RAM 3 Peripheral devices

3.1.3 Software InterfaceThe software is developed with all the basic controls and class provided in

VB .Windows XP or above installed on the system. Application Package must be installed.

3.1.4 Communication Interface

Windows Forms

3.2 Functional RequirementsLogin:This module is suppose to identify the Login type for the software.Login can be either Admin login or User Login.

Admin Login:

- > Product Masters

This module is displayed only to the admin who is logged in and he will be the super user having rights to define differents typs of products.

Wood typeThis module is used to define the wood type and different wood type can be viewed or deleted.Input:

Category This module is used to define the category for selected Wood type and different categories along with their Wood Type can be viewed or deleted

GradeThis module is used to define the Grade for selected Wood type and Grade.Different Grades along with Wood type and Grade can be viewed or deleted

Products and Units

This module is used to define the Products and their Specifications of different Products and these products units can be viewed or deleted

PriceThis module is used to define the Price for the product with all details about its stuff are selected and different prices along with their Specifications can be viewed or deleted.

CustomerThis master is used to store the customer details.

TaxProvides functions of adding,deleting tax values

- > Inventory Stock In

This module is displyed to both Admin/User who logged in.This modules mainly performs functions of storing stock details that are arrived at the godown.

Stocks This module shows the available stock in the godown with all details.

- > Transactions

Accepting Customer/Dealer orderThis module deals with activities of accepting the order from the customers along with customers’ details and it stores order data for functioning of fulfilling Customer order.

Check for Availability for the productsThis module performes the checking of avilable products that are ordered and if no products available then it will place order for the productions of products from at the factory.

Deliverying ProductsThis module creates the invoice and also make arrangment for deliverying products to customers.

Collecting PaymentsThis module handles activities related to customer dues.

- > Reports

This form will generate reports for transactions and customers who have taken products.

3.3 Performance Constraints1) Good working pc with all requirements stated above.2) Should not be overloaded and should be free from malicious.

3.4 Design ConstraintsSoftware Constraints:

1) Operating system Windows XP

2) VB .NET

3) MS Access 2003 Compatibility mode

Hardware constraints:1) Computer: INTEL compatible and others

2) RAM: 256 MB or higher

3.5 System Attributes1) Computer: INTEL compatible2) RAM: 256 MB or higher3) Operating system Windows XP, 2003 4) Microsoft Visual Basic .Net framework

5) MS Access 2003 Compatible

3.5.1 ReliabilityThis system is designed to have very simple database just to cater the exact need of employee leave management. It is tested for all the constraints at development stage

3.5.2 AvailabilityThis system will only available till the system on which it is installed is running

3.5.3 SecurityThis system is provided with authentication without which no user can pass. So only the legitimate users are allowed to use the application. If the legitimate users share the authentication information then the system is open to outsiders.

3.5.4 Maintainability

There will be no maintenance required for the software. The database is provided by the end-user and therefore is maintained by this user.

3.5.5 PortabilityThe system is not portable as it is a standalone application running on single system with no shared database.

3.6 Other RequirementsNone

CHAPTER 3

SYSTEM DESIGN

IntroductionThe purpose of the Design Phase is to a solution of the problem specified in the requirements document. This is the first step in moving from the problem domain to the solution domain. The design of a system is perhaps the most critical factor affecting the quality of the software; it has a major impact on the later phases is the Design Document. This Document is similar to a blueprint or a plan for the solution and is used later during implementation, testing and maintenance.

The Design activity is often divided into separate phases – System Design and Detailed Design. System Design is sometimes also called Top-Level Design. This system design aims to identify and modules that should be in the system, the specifications of these modules, and how they interact with each other to produce the desired result. At the end of the System Design all the major data structures, file formats, and the major modules in the system and their specifications are decided.

CONTEXT FLOW DIAGRAM (CFD)A Context Flow Diagram is a top level (also known as level 0) data flow diagram. It only contains one process node (process 0) that generalizes the function of the

entire system in relationship to external entities. In context diagram the entire system is treated as a single process and all its inputs, outputs, sinks and sources are Identified and shown.

The notations used in flow diagram are: Bubble The Bubble represents a process or transformation that is applied to

the data which changes in some way. Each bubble is assigned a number. Box The Box is called an entity which represents a producer or a customer of

the Information. Arrow The Arrow represents the data flow. All arrows in the data flow

diagram are labeled. The arrowhead indicates the direction of data flow. Parallel Lines Represents a repository of data that is to be stored for use

by one or more processes

CFD of POSIMS

Data Flow Diagram Notation

.

Administrator User /Clerk

Reports

Login

Plywood Office Sales and Inventory Management System

Accept Order

Delivery Products

Function

Data Flow Diagram

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data

through an Information System. A data flow diagram can also be used for the

visualization of Data Processing. It is common practice for a designer to draw a

context-level DFD first which shows the interaction between the system and

outside entities. This context-level DFD is then "exploded" to show more detail of

the system being modeled.

A DFD represents flow of data through a system. Data flow diagrams are

commonly used during problem analysis. It views a system as a function that

transforms the input into desired output. A DFD shows movement of data

through the different transformations or processes in the system.

Factory

Place Order

Move Ordered Products

POSIMSystem

Data BaseInput

OutputAdmin/User

Dataflow diagrams can be used to provide the end user with a physical idea of

where the data they input ultimately has an effect upon the structure of the

whole system from order to dispatch to restock how any system is developed can

be determined through a dataflow diagram. The appropriate register saved in

database and maintained by appropriate authorities.

Data Flow Diagram Notation

.

Function/Process

File/Database

Input/output

Flow

Level 1

User

LOGIN

AdminAdmin Main Screen

User Main Screen

Valid

Valid

Not valid

Not valid

Level 2

Level 3

Login Admin/User

DB Add/Edit/Delete View Update Delete the Items

Reporting

Sales and others

Pending and Payment Report

Level 4

Logged in Admin/User Admin/User

New customer/products details

DB

Transactions Of products/status

List of transactions/customers

Sell to customer/Collect from factory/godon

DB

Customer details

Inventory Add/Delete stock

Reports Display

Logout

CHAPTER 4

DATABASE DESIGNDOCUMENT

1. Database Description

Database description describes all the databases used in the software to store all the records. The database in turn is further described in detail giving all the fields used with their data type, constraints available to them and description. Constraints include primary key, foreign key, etc. Which allow the entities to be uniquely identified.

2. Introduction

In this database description we describe all ten databases which are used to store the all the records of the products, the customers and billing calculation of store.

NORMALIZED TABLES

Table Name: LoginDescription: This table stores the User Name and the Password as a login Form.

Sl.N. FieldName Data Type Description Constraints

1. UserName Text Name of the User Not Null

2. Password Text Password of User Not Null

Table Name: WoodTypeDescription: This table stores the Wood type along with a random generated ID..

Sl.N. Field Name Data Type Description Constraints

1. ID AutoNumber WoodType ID Not Null

2. Wood Text Name of the Wood Not Null

Table Name: ProductUnit. Description: This table stores the Product type and their specification along with a random generated ID

Sl.N. Field Name DataType Description Constraints

1. ID AutoNumber Category ID Not Null

2. Product Text Name of the Product Not Null

3 Unit Text Specification Not Null

Table Name: CategoryDescription: This table stores the Wood type and Category along with a random generated ID.

Sl.N. Field Name Data Type Description Constraints

1. ID AutoNumber Category ID Not Null

2. WoodType Text Name of the Wood Not Null

3 Category Text Name of the Category Not Null

Table Name: GradeDescription: This table stores the Wood type, Category and Grade along with a random generated ID.

Sl.N. Field Name DataType Description Constraints

1. ID AutoNumber Category ID Not Null

2. WoodType Text Name of the Wood Not Null

3 Category Text Name of the Category Not Null

4 Grade Text Name of the Grade Not Null

Table Name: ProductPriceDescription: This table stores the Wood type, Category and Grade along with a random generated ID.

Sl.N. FieldName DataType Description Constraints

1. ID AutoNumber Category ID Not Null

2. GradeId Number New GradeId Not Null

3 ProductUnitId Number New ProductUnitID Not Null

4 Price Number Price of the Product Not Null

Table Name: ProductStockEntryDescription: This table stores all the details of stock are arrived at the godown along with a random generated ID.

Sl.No

.Field Name DataType Description

Constraints

1. ID AutoNumber Product Stock Entry Id Not Null

2. GradeId Number New GradeId Not Null

3 ProductUnitId Number New ProductUnitID Not Null

4 Productsize Text Price of the Product Not Null

5 ProductQuantity Number Quantity of the product Not Null

6 ReceiptNo Text Receipt Number Not Null

7 ReceiptDate Date/Time Current Date Not Null

8 Remarks RemarksAny additional

information

No constraints

Table Name: ProductStockDescription: This table stores the all the details of a product from particular Wood Type along with a random generated ID.

Sl.N. Field Name Data Type Description Constraints

1. ID AutoNumber Category ID Not Null

2. GradeId Number New GradeId Not Null

3 ProductUnitId Text New ProductUnitID Not Null

4 ProductSize Text Size of the Product Not Null

5 Stock NumberArrived Stock of the

products

Not Null

Table Name: OrderDetailDescription: This table stores the all the particulars of a product from a particular Wood Type required by the customer and also it store the calculated amount.

Sl.No. Field Name Data Type Description Constraints

1. OrderNo Numberr Not Null

2. GradeId Number Not Null

3 ProductUnitId Number Not Null

4 Qty Text Size of the Product Not Null

5 Amount Number Total amount Not Null

Table Name: CompanyInfoDescription: This table stores all the details about the company.

Sl.No. Field Name DataType Description Constraints

1. CompanyName Text Not Null

2. Address Text Not Null

3 Contact Number Not Null

4 VATTIN Text Not Null

5 CSTNO Text Not Null

6 Website Text Not Null

7 Email Text Not Null

Table Name: OrderMasterDescription: This table stores the all the particulars of a product from a particular Wood Type required by the customer and also it store the calculated amount.

Sl.No. Field Name Data Type Description Constraints

1. OrderNo Number ----------- Not Null

2. OrderDate Date/Time ----------- Not Null

3 CustomerType Text ----------- Not Null

4 CustName Text Not Null

5 Address Memo Not Null

6 PhoneNo Number -----------

7 ModeOfPayment Text -----------

8 E-MailId Text -----------

9 Terms Memo -----------

10 Destination Text ----------- Not Null

11 Advance Number -----------

12 Balance Number -----------

13 TotalAmt Number -----------

ER DiagramAn Entity Relation(ER) Diagram is a specialized graphics that illustrates the interrelationship between entities in a database. ER diagrams often use symbols to represent 3 different types of information. Boxes are commonly used to represent entities. Diamonds are normally used to represent relationships and ovals are used to represent attributes.

An Entity Relationship Model (ERM), in software engineering is an abstract and conceptual representation of data. Entity Relationship modeling is a relational schema database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relation database, and its requirements in a top-down fashion

Entity:Entity is the thing which we want to store information. It is an elementary basic building block of storing information about business process. An entity represents an object defined within the information system about which you want to store information. Entities are distinct things in the enterprise.

Relationships:A relationship is a named collection or association between entities or used to

relate two or more entities with some common attributes or meaningful interaction between the objects.

Attributes:Attributes are the properties of the entities and relationship, Descriptor of the entity.

Attributes are elementary pieces of information attached to an entity.

ER Diagram of POSIM

Symbols Used in E-R Diagram

ENTITY

ATTRIBUTE

RELATIONSHIP