Techniques

You might also like

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 20

-Jaydeep Modi

Techniques: Techniques

provide additional information on different ways that task may be performed or different forms the output of the task may take. A task may have none, one, or more related techniques. A technique must be related to at least one task.

Types of Techniques:

Acceptance & Evaluation criteria definition Brainstorming Business rules analysis Data dictionary & Glossary Data flow diagram Data modeling Decision analysis Document analysis Interviews Matrix & key performance indicators Non-Functional requirements analysis Organization modeling Problem tracking Process modeling Requirement workshop Scenarios & use cases

Techniques I used: Data dictionary & Glossary


Data flow diagrams Data modeling

Process modeling

Data dictionary & Glossary: A data dictionary or glossary defines key terms & data

relevant to a business domain. Data dictionary or glossaries are used to formally identify and define all terminology used by the organizational unit. According to my project, tables of the database are the data dictionary of my website.

Example of data dictionary:Database Name:- paint_Master


Table Name:- login_Master Field Name User_Name Password Question Answer Data Type Int Int Varchar(50) Varchar(50) Constraint Description

Primary Key Enter User Name Not Null Not null Not null Enter Password Question Answer

Table Name:- suplier_Master

Field Name
S_ID SName S_Add Sup_City Phone_no E_mail_id

Data Type Constraint


Int Varchar(50) Varchar(300) Varchar(30) Varchar(15) Varchar(255) Not Null Not Null Not Null Not Null Not Null

Description
Enter Supplier Name Enter Supplier Address Supplier City Enter Phone Number Enter E-Mail ID

Primary Key Enter Supplier ID

Data Flow Diagrams: Data flow diagrams use to show how information is input,

processed, stored, & output from a system. The data flow diagram provides a visual representation of how information is moved through a system. It shows: External entities that provide data to system or receive data

from a system. The process of the system that transform data. The data stores in which data is collected for some period of time. The data flows by which data moves between external entities, process & data stores.

Example of DFD:Request CUSTOMER Response

Stock Management System

Request DEALER Response

Context Level Diagram

Purchase Entry
Purchase_Master

1.0 Purchase

Supplier
Give Product & Bill

Customer
Receive payment

2.0 Sales

Sales_Master
Sales Entry

Return Product Return Product

3.0 Sales Return 4.0 Purchase Return

Sales Return Entry

Sales_return

Purchase Return Entry

purchase_return

Zero Level Diagram

Purchase_detail

Stock Detail

1.1 Place Order

Update Stock

1.2 Receive Delivery & Bill

Purchase Product

Purchase_master

Receive Bill Account Department Receive Payment Supplie r

1.3 Pay Payment Pay

payment

First Level Diagram For Purchase

2.1 Receive Order

Order

Sales_master

Sales Detail

2.2 Sales Bill

Receive Product

Customer

3.3 Receive Payment

Payment

First Level Diagram For Sales

purchase_master

3.1 Purchase a product


Return product

Supplier

Return product

3.2 Product return

purchase_return

First Level Diagram For Sales


return

Sales_master

4.1 Sale a product

Customer

Update Stock

4.2 Product return

Return product

Sales_return

First Level Diagram For Purchase return

Data Modeling: The purpose of a data model is to describe the

concepts relevant to domain, the relationship between those concepts and information associated with them. The two most widely used types of data model are uder below: The Entity-Relationship diagram(E-R Diagram) Class diagram

I used the E-R diagram in my project of inventory

management system.

Symbols of E-R Diagram

customer

Category _ master

1
has

M
item 1 1 include d has included M 1 Sales _master 1 has 1 Purchase _master 1 has M M Sales _detail 1 include d 0..1 Sales_ return

supplier 1 mak e

M
Purchase order 1 has M Purchase order detail M 1 Purchase return

has
M Purchase _master detail 1

has

0..1

included

Process modeling: The purpose of process modeling is to understand how

work that involves multiple roles and departments is performed within an organization.

Start

Login Yes No Yes If Purches

No

Yes Purchase Transaction Stock Maintain Update Stock

No

If Sales

Sales Transaction Update Stock Receive Payment

Bill

Receive Bill

Pay payment

End

System Flow Chart

You might also like