OBJECT ORIENTED ANALYS DESIGN

PROJECT NO:1

STOCK MANAGEMENT SYSTEM

PROJECT MEMBERS:

B.Vignesh Kumar

G.Dhamodharan

B.Balaji

STOCK MANAGEMENT SYSTEM

The main purpose of the stock management system is to maintain an automated system for maintaining details of the stock system. The system provides facilities for adding new item, adding new stock, maintaining details of sold stock. It also allows us to view details of the and edit details of items.

A.1 SCOPE

The software developed is used for the management of stock and is named as Stock management system. The two main features of the system are:

Maintaining details regarding items.

Maintaining details of new stock to be added and stock to be sold.

A.1.1 Audience

The intended users are people responsible for implementing stock management system.

A.1.2 Organisation

The document describes the stock management system requirements in terms of system requirements, executive summary, analysis, and design diagrams.

A.1.3 Scope of the project:

The software developed is used to manage bulk stock in various domains of industry where stock management is a key factor.

A.1.4 Glossary:

In its simplest form, the Glossary is a list of noteworthy terms and their definitions. It is surprisingly common that a term, often technical or particular to the domain, will be used in slightly different ways by different stakeholders; this needs to be resolved to reduce problems in communication and ambiguous requirements

A.1.4 Glossary:

TERM DEFINITION AND INFORMATION

FORMAT ALIASES

UML

Threshold

Qty

Item

Admin

Pwd

Product Id

BLL

Unified Modeling Language

Minimum stock quantity

Quantity available

A product or service for sale

Administrator

Password

Numeric code that identifies a product

Business Logic Layer

STOCK

5 Digitcode Universal product code

A.2 SYSTEM REQUIREMENT SPECIFICATION

The following subsection describes the stock management system requirements specification in terms of problem statement and feasibility studies.

A.2.1 PROBLEM STATEMENT

The stock management system is a project for managing the day-to-day operations of a electronic shop. It comes with very user friendly, easily navigable interface and scalable framework. It can be easily implemented in a regular shops and supermarket.The System should have the following functionalities: . The stock management system can be used to add items, delete unwanted items, place an

order and purchase new items. The shopkeeper can place the order to the dealer if the stock levels are lesser than the

minimum levels

The Stock management system is used to maintain details about the stock items and for updating ,deleting the stock and also displays the details of purchased and sold stock. Stock manager who has the authority to update the stock items into the system and also to view the stock details for reference

Depending upon the minimum stock, the purchased and sold stocks can be altered and viewed from the data base. Details such as product_id, product name,price,existing stock and minimum stock levels are maintained in the database

ASSUMPTIONSThe assumptions for the stock management are as follows:

Access to stock management system is provided only to authorize persons like manager.

The application operates for a single stock management system only. The user has basic knowledge about working of computers and gives appropriate data

for the required fields.

A.2.2 GANTT CHART

A.3UML USE CASE MODEL

A use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary, communication associations between actors and the use cases and generalization among use cases.

Use cases are text documents, not diagrams, and use-case modeling is primarily an act of writing text, not drawing diagrams.

The credit card processing system is used by the customers to do crediting and payback.

SCENARIO:The scenario records the steps of which there are three kinds:

An interaction between actors and the system: The stock administrator is an actor who interacts with the stock system.

A validation: The System usually checks whether the password given by the user is valid or not.

A state change by the system: If the stock administrator wants to make any modifications in their stock details, the

system updates it in the database.

view

Update

Stock management sysstem

search

invalid loginLogin

add new

edit and delete

purchase

sold out

purchase order

check existing shade

pay id pay name

<<extend>>

<<include>>

<<extend>>

<<include>>

<<extend>><<extend>>

<<include>>

<<include>>

<<include>>

The Stock Management System is used to view, update and search the stock data

ACTORS: An actor is a person, organization, or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures. There are three types of actors. They are:Primary Actor: stock administrator

Description: The actor must be able to perform log in and do updation of the stockSupporting Actor: manager

Description: It is the supporting actor who provides service to system and validates any transactionOff-stage Actor: tax

Description: It is the offstage actor who does not interacts with system directly but is involved in all transactions.

USE CASE: USE CASE SPECIFICATION: DELIVER STOCK:

BRIEF DESCRIPTION:This use case is used to deliver the stocks required by the customer. Here before delivering the stock we check for the availability of stock and then deliver the stock to the customer. The use case allows the user to subtract the sold quantity from the available quantity.

FLOW OF EVENTSBasic Flow:1. Read the particular product ID of an item that the customer requires.2. Retrieve the stock value for the selected item from the appropriate table.3. Check for sufficiency of the stock requested.4. On delivery subtract the available stock value from the database.

Alternate flow:1.if the current stock value is below a threshold limit, display an insufficient message and prompt user to add stock.Precondition:There must be sufficient stock in the showroom database.

USE CASE SPECIFICATION: VIEW STOCK:

BRIEF DESCRIPTION:This use case is used to just view the amount of current stock available in the company and to decide on marketing.

FLOW OF EVENTS

Basic Flow:1. Read the particular product ID of an item of which the stock is to ne viewed.2. Retrieve the stock value for the selected item from the appropriate table.

USE CASE SPECIFICATION: STOCK INTAKE:

The use case allows the user to request and add the quantity to available quantity in database. This use case is used for intake of stock items that are insufficient and buy the required stock and update the stock database as per the current stock value.

FLOW OF EVENTSBasic Flow:1.read the particular product ID of an item that has to purchased2. get the number of items that are being purchased.3.display a message that stocks have been updated.4.update the database with increased value of the stock.

Use Case Name: UpdateDescription: The user inputs or edits a given field of data that gets updated to the

databaseUse Case Name: Add New

Description: The use case allows the user to add a new item to the database.Use Case Name: Edit

Description: The use case allows the actor to edit necessary details of existing stocks in the database.

Use Case Name: Delete Description: The use case allows the actor to delete a stock in case such a need arises.

List of Noun Phrases:The initial study of use case of the stock management system produces the following noun phrases:Stock, Addnew, stockDelete, stockUpdateEdit stockPurchase stockView, SearchExisting, Stock checking

RELEVANT CLASSES FUZZY CLASSES IRRELEVANT CLASSESstock Transaction history checkingStock manager dealer Add new stock

customer record Delete stockdealer

A.4 ACTIVITY DIAGRAM FOR A BUSINESS PROCESS

An activity diagram is a variation or special case of state machine, in which the states are activities representing the performance of operations and transitions are triggered by the completion of the operations. It models the entire business process.

Stock Management

View Update

Enter the product id

Display details

Addnew Edit & delete Stock transaction

Enter the item details

Enter the id and reqd quantity

Enter the details to be modified

Purchase Soldstock

Add with available quantity

Subtract with available quantity

update details

Continue

A.5 UML CLASS DIAGRAMS

A.5.1 Conceptual Super class:

A Conceptual super class definition is more general or encompassing than a subclass definition.

Here the conceptual super class is stock class

A.5.2 Conceptual Sub class:

All members of a conceptual subclass set are members of their super class set.

The following classes are subclasses of Stock management system:

Stock manager:

Stock manager is responsible for developing, monitoring and maintaining the system. He updates the stock and carries out transactions based on the quantity. supplier:

Supplier is the dealer who provides Stock Customer:

Based on the available quantity the stock is delivered..

A.5.3 Domain model:

Generalization:

Abstract Conceptual Class:

Association:

Composition :

A.5.4 CLASS DIAGRAM:

A.6 UML INTERACTION DIAGRAMS

A.6.1 SEQUENCE DIAGRAM Sequence diagrams are an easy and intuitive way of describing the behavior of the system by viewing the interaction between the system and its environment. A sequence diagram shows the objects participating in a time sequence. It shows the objects participating in an interaction by their lifelines and the messages they exchange, arranged in a time sequence. We can also use terminologies like Opt, Alt, Loop .

A.6.2 COLLABORATION DIAGRAM

A collaboration diagram represents a collaboration, which is a set of objects related in a particular context, and interaction, which is a set of objects within the collaboration, to achieve a desired outcome.

Manager System

Database

12: add with available qty18: subtract with available qty

1: enter the item details3: view

6: enter the details8: enter the productid to be added

11: enter the reqd quantity14: enter the productid to be sold

17: enter the required quantity

5: display details10: display details16: display details

2: update7: update13: update19: update

4: pass details9: pass details15: pass details

A.7 State chart diagram:

A state diagram is a type of diagram used in computer science and related fields to describe the behavior of systems. State diagrams require that the system described is composed of a finite number of states.

A.8 LOGICAL VIEW OF LAYERED ARCHITECTURE DIAGRAM:

A.8.1 LOGICAL ARCHITECTURE DIAGRAM:

A.8.2PACKAGE DIAGRAM

A package is a group of modeling elements. It may contain both subordinate packages and ordinary model elements. The entire system can be thought of as a single high-level package , with all the uml diagrams organized within it

A.9 USER INTERFACE LAYER:

This layer provides the user interface (UI) within a composite application. To increase user productivity, user interfaces should support easy adoption. The limitations on the UI design resulting from the capabilities of the underlying components should not be seen as constraints, but rather as some help to provide consistent UIs.

User interfaces consume Web services either from the business logic layer or the back-end layer to retrieve and update data. They do not contain any business logic. UI and business logic decoupling is implemented by using services of the business logic layer only.

A.10 DOMAIN LAYER:

A domain layer also known as the business logic layer (BLL) is a software engineering practice of compartmentalizing. The business logic layer is usually one of the tiers in a multitier architecture. It separates the business logic from other modules, such as the data access layer and user interface. By doing this, the business logic of an application can often withstand modifications or replacements of other tiers

A.11 TECHNICAL SERVICES LAYER:

The Infrastructure Layer may be partitioned into different levels (high-level or low-level technical services). Though, it is not unusual that developers only consider the persistence (data access) and therefore only talk about the Persistence Layer or the Data Access Layer (instead of an Infrastructure Layer or Technical services Layer). In other words, the other kind of technical services are not always being explicitly thought of as being part of any particular layer.

A.12 IMPLEMENTATION DIAGRAM

A.12.1 COMPONENT DIAGRAM:

A component diagram depicts how components are wired together to form larger components and or software systems. They are used to illustrate the structure of arbitrarily complex systems. Components are wired together by using an assembly connector to connect the required interface of one component with the provided interface of another component. This illustrates the service consumer - service provider relationship between the two components.

A.12.2 DEPLOYMENT DIAGRAM:

A deployment diagram in the Unified Modeling Language models the physical deployment of artifacts on nodes. The nodes appear as boxes, and the artifacts allocated to each node appear as rectangles within the boxes. Nodes may have sub nodes, which appear as nested boxes. A single node in a deployment diagram may conceptually represent multiple physical nodes, such as a cluster of database servers.

A.13 TESTINGA.13.1 TEST CASES1. The system when entered into by the user ie. the stock manager , displays a list of options from which the user can choose from.2. The add new option indicates the addition of a new item into the stock and updates it to the database.3.The entire stocks present can be viewed , with the quantities and prices.4. If details are edited then the dependent record if any should also be altered automatically.5. The record deleted in the front end must be reflected in the database also.6.When the minimum quantity level is reached , the needed item had to be purchased new.7.The details on the sold stock can be retrieved through the sold stock information.8. The system does not accept null or multiple values for any of the fields except in case of some exceptions.

A.13.1.1 USABILITY TEST CASE SCENARIOS

Scenario 1: Add a new item to the stock database.Scenario 2: View the quantity and price list of all the items.Scenario 3: Update any changes in the price of the items.Scenario 4: Delete an item if it is no more to be present in the stock.Scenario 5: Purchase the items that have reached the minimum quantity level.Scenario 6: Get details of the sold items in the stock.

PROJECT CODING:Form1:Private Sub Command1_Click()If (Text1.Text = "STOCK" And Text2.Text = "STOCK") ThenText1.Text = " "

Text2.Text = " "MsgBox ("Login success")Form2.ShowUnload MeElseMsgBox ("Login failed")End IfEnd SubPrivate Sub Command2_Click()Me.HideEnd SubPrivate Sub Command3_Click()Text1.Text = " "Text2.Text = " "End SubForm2:

Private Sub Command1_Click()Form3.ShowEnd SubPrivate Sub Command2_Click()Form4.ShowEnd SubPrivate Sub Command3_Click()Form5.ShowEnd SubPrivate Sub Command4_Click()EndEnd Sub

Form3:Private Sub Command1_Click()Dim a As Integera = InputBox("HOW MANY ITEMS DO YOU WANT TO BUY?")If Val(a) <= Val(Adodc1.Recordset("PRODUCTCOUNT")) ThenText3.Text = Text3.Text - aAdodc1.Recordset.UpdateAdodc1.Recordset.SaveElseMsgBox "THERE IS A SHORTAGE OF GOODS. PLEASE COME BACK LATER"End IfEnd SubPrivate Sub Command2_Click()Text1.Text = ""Text2.Text = ""Text3.Text = ""End SubPrivate Sub Command3_Click()Form2.ShowUnload Me

End Sub

Form4:

Private Sub Command1_Click()Adodc1.Recordset.AddNewMsgBox ("Enter the field required and click save")Text1.SetFocusEnd SubPrivate Sub Command2_Click()MsgBox ("Record inserted")Adodc1.Recordset.UpdateEnd SubPrivate Sub Command3_Click()Dim a, f As Integera = InputBox("ENTER PRODUCTID TO DELETE")f = 0Adodc1.Recordset.MoveFirstDoIf (Adodc1.Recordset("PRODUCTID") = Val(a)) Thenf = 1Adodc1.Recordset.DeleteMsgBox ("PRODUCT DELTED")Exit DoEnd IfAdodc1.Recordset.MoveNextLoop Until (Adodc1.Recordset.EOF)If (f = 0) ThenMsgBox ("PRODUCT NOT FOUND")End IfEnd SubPrivate Sub Command4_Click()Unload MeEnd SubPrivate Sub Command5_Click()Dim a, f As Integera = InputBox("Enter product id to search")f = 0Adodc1.Recordset.MoveFirstDoIf (Val(a) = Adodc1.Recordset("PRODUCTID")) Thenf = 1Exit DoEnd IfAdodc1.Recordset.MoveNextLoop Until (Adodc1.Recordset.EOF)If (f = 0) ThenMsgBox ("PRODUCT NOT FOUND")End IfEnd Sub

Form5:Private Sub Command1_Click()Adodc1.Recordset.AddNewMsgBox ("Enter the field required and click save")End SubPrivate Sub Command2_Click()MsgBox ("Record inserted")Adodc1.Recordset.UpdateEnd SubPrivate Sub Command3_Click()Dim a, f As Integera = InputBox("Enter product id to search")f = 0Adodc1.Recordset.MoveFirstDoIf (Val(a) = Adodc1.Recordset("PRODUCTID")) Thenf = 1Exit DoEnd IfAdodc1.Recordset.MoveNextLoop Until (Adodc1.Recordset.EOF)If (f = 0) ThenMsgBox ("PRODUCT NOT FOUND")End IfEnd SubPrivate Sub Command4_Click()EndEnd SubPrivate Sub Command5_Click()Form2.ShowUnload MeEnd SubScreen Shot: