In this project based research an effort has been made to explore the different aspects of Sales management along with Management Information System. Various dimensions of the scope of sales related Management System have been studied in this project. Initiative has been taken to explore the field where competent management can comply properly. The key task of this project is to be sensitized and familiarized with Management concepts and its effect on Sales Management System of relevant Company. In this project it has been tried to build a uncomplicated multidimensional Database Management System. It has also been tried to make an analytical Processing Cube with a view to illustrate how to utilize Sales Management System software. The final component the of this project’s goal is to make certain that in which way the relevant company can get benefitted by utilizing Sales Management.

1. 3/28/2017
SALES MANAGEMENT
SYSTEM
ABC COMPANY

2. Sales Management System for ABC Company
Post Graduation Diploma in Information & Communication Technology
Batch-25
Group:1
Submitted Date: 27.03.2017
Bangladesh Computer Council
Anisur Rahman
Post Graduate Diploma in ICT
System Analysis and Design

3. Abstract
In this project based research an effort has been made to explore the different aspects of
Sales management along with Management Information System. Various dimensions of the
scope of sales related Management System have been studied in this project. Initiative has
been taken to explore the field where competent management can comply properly.
The key task of this project is to be sensitized and familiarized with Management concepts
and its effect on Sales Management System of relevant Company. In this project it has been
tried to build a uncomplicated multidimensional Database Management System. It has also
been tried to make an analytical Processing Cube with a view to illustrate how to utilize
Sales Management System software.
The final component the of this project’s goal is to make certain that in which way the
relevant company can get benefitted by utilizing Sales Management.

4. Acknowledgement
First of all the members of this group would like to express gratitude to Allah the most
Merciful & Beneficent as the holy entity made it possible for the group members to complete
the project successfully.
The group members acknowledge the guidance and immense support of the supervisor Md.
Zafurul Alam Khan Senior Programmer, Bangladesh Computer Council. His continuous
cordial support, advice and inspiration helped the group members in completing the research
work and in writing it. He went through every necessary point to the study to give the right
direction. It was a great learning session for the group members to know how to conduct a
research and to write it from the supervisor. Without his sincere encouragement it would not
have been possible to carry out this project properly.
Next the group members immensely indebted to the honorable Course Coordinator &
teachers of the Bangladesh Computer Council whose support and keen advises paved the
way to write the project report in its perfect manner.

5. Declaration
It is hereby declared that this project report has been submitted by the under-mentioned
group members to Md. Zafurul Alam Khan, Senior Programmer of Bangladesh Computer
Council as partial fulfillment of the module System Analysis and Design (PGDICT-201). It is
also declared that neither this project report nor any part of this project report has been
submitted elsewhere for award of any degree or diploma.
Group Members-
1. Kazi Shamsur Rahman, P-2016025202
2. Mohammad Hossain Ali, P-2016025203
3. Mohammad Ahsanul Haq, P-2016025204
4. Anisur Rahman, P-201602505
5. A H M Anwar Parvez, P-2016025210
PGDICT, Batch-25, Bangladesh Computer Council

6. Contents
Abstract
Acknowledgement
Declaration
Case Study & Objective --------------------------------------------------------------------------- 1-2
1.Project Planning----------------------------------------------------------------------------------- 3-14
• Define Problem
• Context Diagram
• Work Schedule
• Gantt Chart
• Project Feasibility
• Staffing and Launching the Project
• Launching the Project
• Resource List
• Who Does What Type of Work
• Task Usage
• Network Diagram
• Budget Report
• Cash Flow
2.Project Analysis---------------------------------------------------------------------------------- 14-21
• Gather Information
• System Requirements
• Build Prototypes
• Prioritize Requirements
• Approve Recommendation with Management
• Diagrams Of Sales Management System
o Use Case Diagram
o Activity Diagram
o Sequence Diagram
o Data Flow Diagram
3.Project Design ---------------------------------------------------------------------------------- 22-30
• Table Information and Description
• Table Design
• Input Layout
• Output Layout
• Entity Relationship Diagram
4.Implementation --------------------------------------------------------------------------------- 31-52
• User creation and privileges
• Table creation Code
• Input Layout with Code
• Output Layout

7. • System Installation
o Direct Installation
o Parallel Installation
o Single Location Installation
o Phased Installation
• Verify and Testing
• Training
5.Support --------------------------------------------------------------------------------------------- 53-54
• Maintenance and System Enhancement
• Support User

8. Page | 1
Case Study
Objective: To analyze, design and develop a Sales Management Information System for
ABC Company Ltd by analyzing the following information.
Introduction: ABC Company Ltd has been marketing some products through their
authorized dealers (Clients) since 1980. The Company used to receive orders and delivers
products by using some pre-designed form by their sales department. The sales department
or any sales representative receives order from their clients after checking availability of
related items. The sales department also ensures a delivery schedule/shipment to the client
after checking their previous dealing, outstanding bills etc. The other information of the
company is briefly presented in the following sections:
Product Information: The Company is marketing number of products. Each product/item
has a unique id number and also have catalog , some of the items are considered as a set
(e.g. 01 set PC means 01 system unit,01 monitor,01 mouse,01 keyboard etc. ) . The
company has a pre-calculated costing for each item/set and also has a selling price for each
of the item/set which can’t be modified at any level except the top level management. But
there is a provision of discount on sells for the clients against a single order , if the total
amount of sells is more than 20 lac then rate of discount is 2%, if it is within tk.10-20 lac the
rate of discount is 1% and if it is less then 10 lac no discount will provide. A certain amount
of quantity of each item/set should always be reserved in their super store. If any order
places against specific item, the quantity of which is not available in the super store, in that
case the company is capable to produce and make it available in the super store within 15
days after confirmation of the order. Therefore, all sales personnel are aware about the
situation/circumstances and accordingly will provide delivery schedule to the client. The
company also provides commission to sales person @2% on their individual sales amount is
more than 10 lac per month.
Client Information: The Company has its enlisted client list. Only enlisted clients are
capable to place the order to the company directly or through email/telephone. If any new
client is interested to purchase any items from ABC company, the client will have to fulfill
the criterion for enlisted as an authorized dealer of that Company. The Company maintains
all possible information about their clients.
Order/Delivery Information: Sales personnel used to maintain a pre-design order form/slip,
which includes order number, order date, items information, quantity, client information, and
delivery date etc. During delivery, the sales department also maintains a record and will
issue a delivery chalan for the shipment of items.
Employee Information: The management of the company maintains all the information
relating to an employee i.e. Personal information, Salary & Commission Information etc.
according to the existing rules of the company.
All the activities of the company maintain manually. In consequence, the company is
suffering from many problems. Therefore, the company management decided to
automate/computerized the Sales Management Information System where the product
information, client information, order information, delivery information etc are to be
computerized to improve the performance of the company for better access to information,
prompt efficient service for the clients which will lead the company to earn more revenue.
The company desired to automate the following information services:

9. Page | 2
01. Product/Item Stock reserved information
02. Daily/Weekly/Monthly delivery information
03. Order backlog information
04. Sales Order Information based on order number and date
05. Monthly product wise sales information (Matrix)
06. Monthly sales information based on sales personnel.
07. Employees monthly pay slips with commission.
Following the above information you will have to analyze, design and develop a cost
effective Sales Managements Information System for the ABC Company Ltd with
documentation, so that the Company can operate its sales activities very user friendly,
effectively and efficiently.

10. Page | 3
1.Project Planning
Problem Definition
ABC Company Ltd is marketing some products through their authorized dealers (Clients).
The activities of the company maintain manually. In consequence the company is suffering
from many problems. Therefore, the company management decided to
automate/computerized the Sales Management Information System where the product
information, client information, order information on, delivery information etc. are to be
computerized to improve the performance of the company from better access to information,
prompt efficient service for the clients which will lead the company to earn more revenue.
The company desired to automate the following information services:
01. Product/Item Stock reserved information
02. Daily/Weekly/Monthly delivery information
04. Order backlog information
05. Sales Order Information based on order number and date
06. Monthly product wise sales information (Matrix)
07. Monthly sales information based on sales personnel.
08. Employees monthly pay slips with commission.
Business Rule:
Products:
(i) Each Unit/Item has a unique id number and also have catalog , some of the
items are considered as a set (e.g. 01 set PC means 01 system unit,01
monitor,01 mouse,01 keyboard etc. ). List of Product Appendix (i).
(ii) Each Unit/Item has a pre-calculated costing and selling price which can’t be
modified at any level except the top level management.
(iii) The top level management may be changed the price. Sales personnel receives
information at the same time if any price changed by the management.
Clients:
(i) Enlisted clients are capable to place the order. List of Clients Appendix (ii).
(ii) If any new client is interested to purchase any items from the Company, the client
will haveTk.100 lacs bank balance and well reputation.
(iii) The Company didn’t provide more than one dealer in a city.
Sales Order/Delivery:
(i) Sales personnel receives order from clients using a form/slip, which includes
order number, order date, items information, quantity, client information, and
delivery date. Sample of Form in Appendix (iii).
(ii) Sales personnel receive order if any client sends email or call a telephone. In that
Case they will use their order form.

11. Page | 4
(iii) The Company provides discount on sells against a single order if
(a) Sells amount is more than 20 lacs then rate of discount is 2%,
(b) Sells amount is more than 10-20 lacs then rate of discount is 1%,
(c) Sells is less then 10 lacs no discount will provide.
(iv) .Order places against specific item, the quantity of which is not available in the
super store, in that case the Company is capable to produce and make it
available in the super store within 15 days after confirmation of the order.
Therefore sales personnel will provide delivery schedule to the client accordingly
consider the situation/circumstances.
(v) During delivery, the sales department/personnel also maintain a record and will
issue a delivery chalan for the shipment of items. Sample of Form in Appendix
(iv).
Employees:
(i) The management of the company maintains all the information relating to an
employee i.e. Personal information. The list of employee (v).
(ii) The sales personnel receive commission with their monthly salary @2% on their
individual sales amount is more than 10 lacs/per month.
(iii) All employees receive medical allowance, house rent and transport allowance.
Those employees didn’t get transport facilities from the Company only those are
authorized for transport allowance. Provident fund is 10% of basic salary deducts
from their total salary. The allowances are :
(a) Medical allowance 30% of basic salary.
(b) House rent 60% of basic salary.
(c) Transport allowance 20% of basic salary.
Context Diagram of Sales Management System

12. Page | 5
Sales Management System of ABC Company Ltd.
Work Schedule

13. Page | 6

14. Page | 7
Gant
t
Char
t

15. Page | 8
Project Feasibility
Project feasibility analysis is an activity that verifies whether a project can be started and
successfully completed. Because, by definition, a project is a unique endeavor, every project
has unique challenges that affect its feasibility.
1.Economic Feasibility:
Cost/benefit analysis (CBA)
❖ Estimate project development costs
❖ Estimate operational costs after project
❖ Estimate financial benefits based on annual savings and increased revenues
❖ Calculate CBA using complete list of costs and benefits
2.Organizational and Cultural Feasibility:
➢ Each company has own culture
❖ New system must fit into culture
➢ Evaluate related issues for potential risks
❖ Low level of computer competency
❖ Computer phobia
❖ Perceived loss of control
❖ Shift in power
❖ Fear of job change or employment loss
❖ Reversal of established work procedures
3.Technological Feasibility:
➢ Does system stretch state-of-the-art technology?
➢ Does in-house expertise presently exist for development?
➢ Does an outside vendor need to be involved?
➢ Solutions include:
❖ Training or hiring more experienced employees
❖ Hiring consultants
❖ Changing scope and project approach
4.Schedule Feasibility:
➢ Estimates needed without complete information
➢ Management deadlines may not be realistic
➢ Project managers:
❖ Drive to realistic assumptions and estimates
❖ Recommend completion date flexibility
❖ Assign interim milestones to periodically reassess completion dates
❖ Involve experienced personnel
❖ Manage proper allocation of resources
5.Resource Feasibility:
➢ Team member availability
➢ Team skill levels
➢ Computers, equipment, and supplies
➢ Support staff time and availability
➢ Physical facilities

16. Page | 9
Staffing and Launching the Project
➢ Develop resource plan for the project
➢ Identify and request specific technical staff
➢ Identify and request specific user staff
➢ Organize the project team into workgroups
➢ Conduct preliminary training and team building exercises
➢ Key staffing question: “Are the resources available, trained, and ready to start?”
Launching the Project
➢ Scope defined, risks identified, project is feasible, schedule developed, team
members identified and ready
➢ Oversight committee finalized, meet to give go-ahead, and release funds
➢ Formal announcement made to all involved parties within organization
➢ Key launch question: “Are we ready to start?”

17. Page | 10
Resource List

18. Page | 11
Who Does What Type of Work

19. Page | 12
Task Usage View

20. Page | 13
Net
wor
k
Dia
gra
m

21. Page | 14
Budg
et
Repor
t

22. Page | 15
Cas
h
Flo
w

23. Page | 16
2.Project Analysis
1.Gather Information:
➢ Analysis phase done to understand business functions and develop system
requirements
➢ Original structured approach
❖ Create model of existing system
❖ Derive requirements from existing system model
➢ Current approach
❖ Identify logical requirements for new system
❖ Balance the review of current business functions with new system
requirements
Figure: Information gathering and model building.

24. Page | 17
Review Existing Reports, Forms and Procedure Descriptions:
➢ Source: External industry wide professional organizations and trade publications
➢ Source: Existing business documents and procedure descriptions within organization
❖ Identify business rules, discrepancies, and redundancies
❖ Be cautious of outdated material
❖ Obtain preliminary understanding of processes
❖ Use as guidelines / visual cues to guide interviews
Sample Order Form of ABC Ltd
Conduct Interviews and Discussions with Users:
➢ Effective way to understand business functions and rules
➢ Time-consuming and resource-expensive
➢ May require multiple sessions to:
❖ Meet all users
❖ Understand all processing requirements
➢ Can meet with individuals or groups of users
➢ List of detailed questions prepared
2.System Requirements:
Generally we divide system requirements into two categories:
1.Functional requirements.
2.Non-Functional requirements.
The functional requirements are those that explain the basic business functions that the
new system must support.
• Activities system must be performed(Use case)
• Based On Procedures and business functions

25. Page | 18
• Documented in analysis models
Non-Functional requirements involve the objectives of the system for technology,
performance, usability, reliability, and security.
• Performance – for example Response Time, Throughput, Utilization, Static
Volumetric
• Scalability
• Availability
• Reliability
• Recoverability
• Maintainability
• Security
• Manageability
• Usability
3.Build Prototypes:
➢ Preliminary working model of a larger, more complex system
❖ Discovery, design, evolving prototypes
➢ Operative
❖ Working model to provide “look and feel”
➢ Focused to accomplish single objective
➢ Quick
❖ Built and modified rapidly with CASE tools
4.Prioritize Requirements:
➢ Make sure gathered information is correct.
➢ Structured walkthrough
• Effective means of implementing quality control early in project
• Verify and validate system requirements.
• Review of findings from investigation and of models based on findings
➢ Project Manager responsible for the system quality
5.Approve Recommendation with Management:
➢ Correct?
➢ Consistent?
➢ Complete?
• Externally-all desired properties are present
• Internally-no undefined references
➢ Each requirement describes something actually needed by the customer
➢ Requirements are verified(testable)
➢ Requirements are traceable

26. Page | 19
Diagrams Of Sales Management System
Use Case Diagram of Sales Management system

27. Page | 20
Activity Diagram of Sales Management system

28. Page | 21
Sequence Diagram of Sales Management system

29. Page | 22
Data Flow Dagram 1 for SALES MANAGEMENT

30. Page | 23
3.Project Design

31. Page | 24
Table Information and Description
Table Name : DEPARTMENT_INFO
Description : Used to store information about Department of the company.
Column Name DataType Size Column Description
DEPT_ID Number 5 Department id used as Primary Key
DEPT_NAME Varchar2 30 Department Name
Integrity Constraints:
➢ PK_DEPT_ID Primary Key constraint applied based on DEPT_ID column of
DEPARTMENT_INFO table
Table Name : EMPLOYEE_INFO
Description : Used to store information about employees of the company.
Column Name Data Type Size Column Description
EMP_ID Varchar2 10 Employee id used as Primary Key
EMP_NAME Varchar2 50 Name of the employee
D_BIRTH Date - Date of birth of the employee
DESIGNATION Varchar2 50 Designation of the employee
DEPT_ID Number 5 Employee department number
JOIN_DATE Date - Joining Date
BAS_SALARY Number 10,2 Basic Salary
ADDRESS Varchar2 150 Address of the employee
CONTACT Varchar2 40 Cell Phone number/Email etc
Integrity Constraints:
➢ PK_EMP_ID Primary Key constraint applied based on EMP_ID column of EMPLOYEE_INFO
table.
➢ FK_DEPT_ID Foreign Key applied based on DEPT_ID column that References DEPT_ID
from the DEPARTMENT_INFO table.
➢ First letter of EMP_ID must start with E
Table Name : FACTORY_PRODUCTION

32. Page | 25
Description : Used to store information about factory production.
Column Name Data Type Size Column Description
PRODUCT_ID Varchar2 10 Product identity
PRODUCT_DATE Date - Date of production
QUANTITY Number 10 Quantity of material to be delivered.
Integrity Constraints :
➢ PK_PRODUCT_ID_01 Composite Primary Key that is based on the PRODUCT_ID and
PRODUCT_DATE and column of FACTORY_PRODUCTION table.
➢ FK_PRODUCT_ID_O1 Foreign Key based on the column PRODUCT_ID that References
PRODUCT_ID from the PRODUCT_INFO table
Table Name : PRODUCT_INFO
Description : Used to store information about products supplied by the company.
Column Name Data Type Size Column Description
PRODUCT_ID Varchar2 10 Product id used as Primary Key
DESCRIPTION Varchar2 50 Description of a product
UNIT_MEASURE Varchar2 10 Unit in which a product is measured.
QTY_ON_HAND Number 10 Quantity which is available in stock
REORDER_LVL Number 10 Quantity when stock should be re-
ordered.
COST_PRICE Number 10,2 Cost price of the product.
SELLING_PRICE Number 10,2 Selling price of the product.
Integrity Constraints :
➢ PK_PRODUCT_ID Primary Key constraint applied based on PRODUCT_ID column
of PRODUCT_INFO table.
➢ First letter of product_id must start with P.
➢ Qty_On_Hand should have a default value of 0.
➢ Selling_Price cannot be less than cost_price.
Table Name : CLIENT_INFO
Description : Used to store information about clients.

33. Page | 26
Column Name Data Type Size Column Description
CLIENT_ID Varchar2 10 Client id used as primary key for each client
CLIENT_NAME Varchar2 50 Name of Company ( client )
ADDRESS Varchar2 50 Client’s address.
CITY Varchar2 15 City in which client’s is located.
STATE Varchar2 15 State in which client’s is located.
BAL_DEBIT Number 10,2 Debit of the Client’s
BAL_CREDIT Number 10,2 Credit of the Client’s
CONTACT Varchar2 50 Contact number/Email address etc
REMARKS Varchar2 100 Client history / Remarks
Integrity_Constraints:
➢ PK_CLIENT_ID Primary Key constraint applied based on CLIENT_ID column of
CLIENT_INFO table .
➢The first letter of CLIENT_ID must start with C.
Table Name : SALES_ORDER
Description : Used to store order header information.
Column Name Data Type Size Column Description
S_ORDER_ID Varchar2 10 Sales order id used as primary key allotted to each order.
ORDER_DATE Date Date on which order is generated.
CLIENT_ID Varchar2 10 Client for whom the sales order is created.
ORDER_STATUS Varchar2 1 The delivery status of the Order.
EMP_ID Varchar2 10 Employee ID is responsible for sales
Integrity Constraints :
➢ PK_ORDER_ID primary key constraint applied based on S_ORDER_ID column
of the SALES_ORDER table.
➢ FK_CLIENT_ID Foreign Key based on the column CLIENT_ID that References
CLIENT_ID from the CLIENT_INFO table.
➢ FK_EMP_ID Foreign Key based on the column EMP_ID that References
EMP_ID from the EMPLOYEE_INFO table.
Table Name : SALES_ORDER_DETAILS
Description : Used to store information about order details.

34. Page | 27
Column Name Data Type Size Column Description
S_ORDER_ID Varchar2 10 Order number against which Order details are
stored.
PRODUCT_ID Varchar2 10 Product identity of the material being Ordered.
PRODUCT_RATE Number 10,2 Rate at which the Material is sold.
QTY_ORDERED Number 8 Quantity of material Ordered.
Integrity Constraints :
➢ PK_SALES_DETAILS Composite Primary Key that is based on the S_ORDER_ID and
PRODUCT_ID column of the ORDER_DETAILS table.
➢ FK_ORDER_ID Foreign Key based on the column S_ORDER_ID that References
S_ORDER_ID from the SALES_ORDER table.
➢ FK_PRODUCT_ID Foreign Key based on the column PRODUCT_ID that References
PRODUCT_ID from the PRODUCT_INFO table.
Table Name : DELIVERY_HEADER
Description : Used to store delivery header Information.
Column Name Data Type Size Column Description
S_ORDER_ID Varchar2 10 Order number against which Order to be
delivered.
DEL_DATE Date - Delivery Date when material must be delivered
➢ PK_S_ORDER_ID_01 Composite Primary Key that is based on the S_ORDER_ID and
DEL_DATE and column of the DELIVERY_HEADER table.
➢ FK_S_ORDER_ID_O1 Foreign Key based on the column S_ORDER_ID that References
S_ORDER_ID from the SALES_ORDER table.
Table Name : DELIVERY_SCHEDULE
Description : Used to store information about order delivery schedule.
Column Name Data Type Size Column Description

35. Page | 28
S_ORDER_ID Varchar2 10 Order number against which Order details are
stored.
PRODUCT_ID Varchar2 10 Product identity of the material being Ordered.
DEL_DATE Date - Delivery Date when material must be delivered
QUANTITY Number 10 Quantity of material to be delivered.
Integrity Constraints :
➢ PK_DELIVERY_ID Composite Primary Key that is based on the S_ORDER_ID
,PRODUCT_ID and DEL_DATE and column of the DELIVERY_SCHEDULE table.
➢ FK_ORDER_ID_O1 Foreign Key based on the column S_ORDER_ID that References
S_ORDER_ID from the SALES_ORDER table.
➢ FK_PRODUCT_ID_O1 Foreign Key based on the column PRODUCT_ID that References
PRODUCT_ID from the PRODUCT_INFO table
Table Design

36. Page | 29
Table Name : DEPARTMENT_INFO
Table Name : EMPLOYEE_INFO
Table Name : FACTORY_PRODUCTION
Table Name : PRODUCT_INFO
Table Name : CLIENT_INFO

37. Page | 30
Table Name : SALES_ORDER
Table Name : SALES_ORDER_DETAILS
Table Name : DELIVERY_HEADER

38. Page | 31
Table Name : DELIVERY_SCHEDULE

39. Page | 32
4.Implementation
y Relationship Diagram(ERD)

40. Page | 33
User & Table creation script for the project Sales Management System
User creation and privileges
### User creation with location of user object placement
CREATE USER sms identified by sms
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA 100 M on users ;
### Provide all privileges
GRANT connect, resource, dba to sms;
(N.B : User creation and privileges to be done by SYS/SYSTEM users who have DBA
privileges)
Table creation Code
### DEPARTMENT_INFO table used to store information about Department of the
company.
CREATE TABLE department_info
(dept_id number(5),
dept_name varchar2(30),
CONSTRAINT pk_dept_id PRIMARY KEY (dept_id));
### EMPLOYEE_INFO table used to store information about employees of the company.
CREATE TABLE employee_info
(emp_id varchar2(10),
emp_name varchar2(50),
d_birth date,
designation varchar2(50),
dept_id number(5) ,
join_date date,
bas_salary number(10,2),
address varchar2(150),
contact varchar2(40),
CONSTRAINT pk_emp_id PRIMARY KEY (emp_id),
CONSTRAINT fk_dept_id FOREIGN KEY (DEPT_ID) REFERENCES
department_info(dept_id)) ;
### FACTORY_PRODUCTION used to store information about daily factory production.

41. Page | 34
CREATE TABLE factory_production
(product_id varchar2(10),
product_date date,
quantity number(10),
CONSTRAINT pk_product_01 PRIMARY KEY (product_id,product_date),
CONSTRAINT fk_product_id_01 FOREIGN KEY (product_id) REFERENCES
product_info(product_id));
### PRODUCT_INFO table used to store information about products supplied by the
company
CREATE TABLE product_info
( product_id varchar2(10),
description varchar2(50),
unit_measure varchar2(10),
qty_on_hand number(10),
reorder_lvl number(10),
cost_price number(10,2) ,
selling_price number(10,2),
CONSTRAINT pk_product_id PRIMARY KEY (product_id));
.
### CLIENT_INFO table used to store information about clients.
CREATE TABLE client_info
( client_id varchar2(10),
client_name varchar2(50),
address varchar2(100),
city varchar2(15) ,
state varchar2(15),
bal_debit number(10,2),
bal_credit number(10,2),
contact varchar2(50),
remarks varchar2(50),
CONSTRAINT pk_client_id PRIMARY KEY (client_id));
### SALES_ORDER table used to store order header information
CREATE TABLE sales_order
(s_order_id varchar2(10),
order_date date,
client_id varchar2(10),
emp_id varchar2(10),
order_status varchar2(1),
CONSTRAINT pk_s_order_id PRIMARY KEY (s_order_id),
CONSTRAINT fk_client_id FOREIGN KEY (client_id) REFERENCES client_info(client_id) ;
CONSTRAINT fk_emp_id FOREIGN KEY (emp_id) REFERENCES
employee_info(emp_id)) ;
###SALES_ORDER_DETAILS table used to store information about order details.

42. Page | 35
CREATE TABLE sales_order_details
(s_order_id varchar2(10),
product_id varchar2(10),
product_rate varchar2(10),
qty_ordered number(8),
CONSTRAINT pk_sales_detail PRIMARY KEY (s_order_id,product_id),
CONSTRAINT fk_order_id FOREIGN KEY (s_order_id) REFERENCES
sales_order(s_order_id),
CONSTRAINT fk_poduct_id FOREIGN KEY (product_id) REFERENCES
product_info(product_id));
### DELIVERY_HEADER used to store information about Delivery header Information.
CREATE TABLE delivery_header
(s_order_id varchar2(10),
del_date date,
CONSTRAINT pk_sales_order_id_01 PRIMARY KEY (s_order_id,del_date),
CONSTRAINT fk_sales_order_id_01 FOREIGN KEY (s_order_id) REFERENCES
sales_order(s_order_id));
### DELIVERY_SCHEDULE table used to store information about order delivery
schedule.
CREATE TABLE delivery_schedule
(s_order_id varchar2(10),
product_id varchar2(10),
del_date date,
quantity number(8),
CONSTRAINT pk_delevery_id PRIMARY KEY (s_order_id,product_id,del_date),
CONSTRAINT fk_order_id_01 FOREIGN KEY (s_order_id) REFERENCES
sales_order(s_order_id),
CONSTRAINT fk_poduct_id_01 FOREIGN KEY (product_id) REFERENCES
product_info(product_id));
Input Forms Layout of Sales Management Information System
(SMIS)

43. Page | 36
Production Information Entry Screen
Activities : This form will be developed using Product_info table to store product
information into the Product_info table.
Code ubder Button_bk block against different button
Trigger when-button-press against Add button under Button_bk block
begin
go_block('product_info');
create_record;
end;
Trigger when-button-press against Search button under Button_bk block
begin
go_block('product_info');
enter_query;
end;
Trigger when-button-press against Delete button under Button_bk block
begin
set_alert_property('Question_Alert',alert_message_text,'Do you want to Delete the record
!!!');
if show_alert('Question_Alert')=Alert_Button1 then
go_block('product_info');
delete_record;
end if;

44. Page | 37
end;
Trigger when-button-press against Save button under Button_bk block
begin
set_alert_property('Question_Alert',alert_message_text,'Do you want to save the record
!!!');
if show_alert('Question_Alert')=Alert_Button1 then
commit_form;
end if;
end;
Trigger when-button-press against Exit button under Button_bk block
begin
exit_form;
end;
Code ubder Product_info block against different item
Trigger when-validate-item against cost_price item under Product_info block
begin
if :product_info.cost_price =0 then
message('Cost price cannot be 0');
raise form_trigger_failure;
elsif :product_info.cost_price>= :product_info.selling_price then
message(' Cost price cannot be greater or equal to selling price');
raise form_trigger_failure ;
end if;
end;
Trigger when-validate-item against selling_price item under Product_info
begin
if :product_info.selling_price =0 then
message('Selling price cannot be 0');
raise form_trigger_failure;
elsif :product_info.selling_price<= :product_info.cost_price then
message(' Selling price cannot be Lower or equal to cost price');
raise form_trigger_failure ;
end if;
end;
Factory Information Entry Screen

45. Page | 38
Activities: This form will be developed using Factory_Production table to store
factory Information into the Factory_Production table and add
quantity with quantity_on_hand of Product_information table. Both
works will be done by posting button.
Code ubder Factory_production against button
Trigger when-button-press against Posting button under Factory_production block
begin
set_alert_property('Question_Alert',alert_message_text,'Do you want to posting the quantity
!!!');
if show_alert('Question_Alert')=Alert_Button1 then
update product_info
set qty_on_hand=:factory_production.quantity+nvl(qty_on_hand,0)
where product_id=:factory_production.product_id;
commit_form;
end if;
end;
Record group belongs to product_id item
SELECT ALL PRODUCT_INFO.PRODUCT_ID, PRODUCT_INFO.DESCRIPTION
FROM PRODUCT_INFO
Department Employee Entry Screen

46. Page | 39
Activities: This master detail form will be developed using Department_info and
Employee_info table to store department information into the
Department_info table employee Information into the
Employee_Information table simultaneously.
Client Information Entry Screen
Activities : This form will be developed using Client_info table to store Client information
into the Client_Info table. Hence client number will be generated
automatically starting with C.
Generate Client number using follow code and client number must start with C (Here
sequence when-mouse-click trigger)
declare

47. Page | 40
primary_key_value varchar2(10);
begin
select lpad(to_char(client_seq.nextval),5,0) into primary_key_value from dual;
:client_info.client_id:='C'||primary_key_value;
end;
Slaes Order Information Entry Screen
Activities: This master detail form will be developed using Sales_Order and
Sales_Order_Detail table to store sales order information into the
Sales_Order table and sales order detail information into the
Sales_Order_Detail table simultaneously. Hence, sales order number in
the master block will be generated automatically starting with S and. the
datas in the Cilent id and Emp_id field will come from respective
primary key field as list box or combo box.
Product ID in the detail block will come from Product_Info table as list
box or combo box. After selection of product_id respective description
and product rate will show which are available in the Product_Info table.
Total and Grant total field will be working as display fields.
Trigger when-button-press against Confirm button underSales_order_details block
declare

48. Page | 41
p_id varchar2(10);
qty number(10);
begin
set_alert_property('Question_Alert',alert_message_text,'Do you want to confirm the Order
!!!');
if show_alert('Question_Alert')=Alert_Button1 then
go_block('sales_order_details');
select p_id,qty_on_hand into p_id, qty from product_info where
product_id=:sales_order_details.product_id;
while p_id=:sales_order_details.product_id loop
update product_info
set qty_on_hand=qty-:sales_order_details.qty_ordered
where product_id=:sales_order_details.product_id;
end loop;
commit_form;
end if;
end;
Record group belongs to client_id item
SELECT ALL CLIENT_INFO.CLIENT_ID FROM CLIENT_INFO
Record group belongs to Product_id item
SELECT ALL PRODUCT_INFO.PRODUCT_ID, PRODUCT_INFO.DESCRIPTION,
PRODUCT_INFO.SELLING_PRICE
FROM PRODUCT_INFO
Record group belongs to Emp_id item
SELECT ALL EMPLOYEE_INFO.EMP_ID, EMPLOYEE_INFO.EMP_NAME
FROM EMPLOYEE_INFO
Delivery Schedule Information Entry Screen

49. Page | 42
Activities: This master detail form will be developed using Delivery_Header and
Delivery_Schedule table to store delivery header information into the
Delivery_Header table and delivery schedule information into the
Delivery_Schedule table simultaneously. Hence, Delivery date is the
system date and sales order number in the master block will come from
sales_order table i,e respective primary key field as list box or combo
box. After selection of sales order id respective product_id , quantity,
rate will show which are available in the Sales_Order and
Sales_Order_Detail table.Total and Grant total field will be working as
display fields
Posting Delivery button will act as save button and will subtract/reduce
quantity form Product_Info table accordingly.
declare
order_yn varchar2(1);
s_id varchar2(10);
p_id varchar2(10);
qty number(10);
cursor sales_cursor is
select s_order_id,product_id,qty_ordered from sales_order_details where
s_order_id=:Delivery_header.s_order_id order by Product_id ASC;
begin
set_alert_property('Question_Alert',alert_message_text,'Do you want to posting the
delivery !!!');
if show_alert('Question_Alert')=Alert_Button1 then
go_block('Delivery_header');
select order_status into order_yn from sales_order

50. Page | 43
where s_order_id=:delivery_header.s_order_id;
if order_yn='N' then
update sales_order
set order_status ='Y'
where s_order_id=:delivery_header.s_order_id;
end if;
open sales_cursor;
loop
fetch sales_cursor into s_id,p_id,qty ;
exit when sales_cursor%notfound;
update product_info
set qty_on_hand=qty_on_hand-nvl(qty,0)
where product_id=p_id ;
end loop;
close sales_cursor;
end if;
commit_form;
end;
Record group sys belongs to Del_date item
select sysdate from dual
Record group Products belongs to Product_id item
SELECT ALL SALES_ORDER_DETAILS.PRODUCT_ID,
SALES_ORDER_DETAILS.PRODUCT_RATE,
SALES_ORDER_DETAILS.QTY_ORDERED
FROM SALES_ORDER_DETAILS
where s_order_id =:delivery_header.s_order_id
Record group sales belongs to sales_order_id item
SELECT ALL SALES_ORDER.S_ORDER_ID, SALES_ORDER.CLIENT_ID
FROM SALES_ORDER WHERE ORDER_STATUS ='N'
Output Layout of Sales Management Information System (SMIS)

51. Page | 44
Product/Item Stock Information of ABC Company
Date :--------- /----------- / -----------------
SN Product id Description Quantity
Activities : This output layout will be developed using Product_info table to show
Product/Item Stock Information of ABC Company .
Daily delivery Information of ABC Company
Date :--------- /----------- / -----------------
SN Sales
order id
Client
Name
Product_id Description Quantity Sales
Person
Weekly delivery Information of ABC Company
Date :--------- /----------- / ----------------- to --------- /----------- / -----------------

52. Page | 45
SN Sales
order id
Client
Name
Product_id Description Quantity Sales
Person
Monthly delivery Information of ABC Company
Month ::-------------------- Year -----------------
SN Sales
order id
Client
Name
Product_id Description Quantity Sales
Person
Activities: Daily/Weekly/Monthly output layout will be developed using
Delivery_Header ,Delivery_Schedule, Sales_Order, Client_info and
Employee_info table to show Daily/Weekly/Monthly delivery
information of ABC Company.
Order backlog Information of ABC Company
Date :--------- /----------- / -----------------

53. Page | 46
SN Sales
order id
Client
Name
Product_id Description Quantity Sales
Person
Activities: Daily/Weekly/Monthly output layout will be developed using,
Sales_Order, Sales_order_Detail,Client_info and Employee_info table
to show backlog order information of ABC Company.
Sales Order Information based on order number and date
Date :--------- /----------- / ----------------
-
SN Sales
order id
Client
Name
Product_id Description Quantity Delivery
Status
Activities: This output layout will be developed using Sales_Order,
Sales_order_Detail and Client_info table to show Sales order
information of ABC Company. Any authorized personnel will use sales
order id and date to show order/Delivery status.
Monthly product wise sales information (Matrix)
Date :--------- /----------- / -----------------

54. Page | 47
Product
Date
P01 P02 P03 P04 - - P0N
Date1
Date2
Date3
-
-
Date N
Total
Activities: This output layout will be developed using Sales_Order and
Sales_order_Detail table to show monthly product wise sales
information (matrix) of ABC Company. Only those products will
consider as sale where order status indicator is Y in the sales_Order
table.
Monthly sales Information based on sales persons
Date :--------- /----------- / -----------------
SN
Employee
ID
Name
Sales
Order ID
Product
ID
Quantity
Amuont in
Taka
Total
Activities: This output layout will be developed using Sales_Order,
Sales_order_Detail and Employee_info table to show monthly product
sales information based on sales persons of ABC Company.

55. Page | 48
Employee s monthly pay slip with commission
Date :--------- /----------- / -----------------
Employee id : --------------------------------------- Employee name :---------------------
Designation : ----------------------------------------- Department:---------------------
SN Item Amount in
Taka
01 Basic salary
02 House Rent
03 Medical
Allowance
04 Education
Allowance
05 Tiffin Allowance
06 Commission
07 Provident fund
(10% -)
Total
Accounts Officer
Activities: This output layout will be developed using Employee_info, Sales_Order,
and Sales_Order_Details table to generate pay slip of each employee
with commission.
System Installation
 Process of moving from old system to new system

56. Page | 49
 Conversion of data must be planned
Four installation strategies:
 Direct Installation.
 Parallel Installation.
 Single-location installation.
 Phased Installation.
Direct Installation
Single Location Installation
Single Location Installation
Phased Installation

57. Page | 50
Verify and Testing

58. Page | 51
• Verification is the process to make sure the product satisfies the conditions
imposed at the start of the development phase.
• In other words, to make sure the product behaves the way we want it to.
• Software testing is the process of evaluation a software item to detect
differences between given input and expected output.
• Software testing is a process that should be done during the development
process. In other words software testing is a verification and validation
process.
There are different types of Testing,
• Static testing: Static testing doesn't need actual execution of program
module. Code Reviews, walkthroughs, or inspections are considered as static
testing.
• Dynamic Testing: Dynamic Testing methods are traditionally divided into
black box testing and white box testing.
White Box Testing:
• White box testing is the detailed investigation of internal
logic and structure of the code. White box testing is also called
glass testing or open box testing.
• In order to perform white box testing on an application,
the tester needs to possess knowledge of the internal working of
the code.
Black Box Testing:
• Testing method without having any knowledge of the
interior workings of the application is Black Box testing.
• A tester will interact with the system's user interface by
providing inputs and examining outputs without knowing how
and where the inputs are worked upon.
Levels of Testing:
• Levels of testing include the different methodologies that can be used while
conducting Software Testing. Following are the main levels of Software
Testing:
• Functional Testing.
• Non-Functional Testing.
Functional Testing:

59. Page | 52
 Unit testing
 Each module is tested alone in an attempt to discover any errors
in its code.
 Integration testing
 Individual software modules are combined and tested as a
group.
 System testing
 Designed to uncover weaknesses that were not found in earlier
tests.
 Stub testing
 Performed on individual events or modules of a program.
Non-Functional Testing:
• ALPHA Testing : Spelling Mistakes , Broken Links,
Cloudy Directions. The Application will be tested on machines with the lowest
specification to test loading times and any latency problems.
• BETA Testing : Users will install, run the application
and send their feedback to the project team. Typographical errors, confusing
application flow, and even crashes.
• Regression Testing :Whenever a change in a software
application is made it is quite possible that other areas within the application
have been affected by this change. To verify that a fixed bug hasn't resulted in
another functionality or business rule violation is Regression testing.
• Performance Testing: It is mostly used to identify any
bottlenecks or performance issues rather than finding the bugs in software.
There are different causes which contribute in lowering the performance of
software:
➢ Network delay.
➢ Client side processing.
➢ Database transaction processing.
➢ Load balancing between servers.
➢ Data rendering.
• Security Testing: Security testing involves the testing
of Software in order to identify any flaws ad gaps from security and
vulnerability point of view. Following are the main aspects which Security
testing should ensure:
➢ SQL insertion attacks.
➢ Injection flaws.
➢ Session management issues.
➢ Cross-site scripting attacks.
➢ Buffer overflows vulnerabilities.
➢ Authorization.
➢ Directory traversal attacks.

60. Page | 53
• Portability Testing: Portability testing includes the
testing of Software with intend that it should be re-useable and can be
moved from another Software as well. Following are the strategies that can
be used for Portability testing.
➢ Transferred installed Software from one computer to another.
➢ Building executable (.exe) to run the Software on different platforms.

61. Page | 54
Training:
 Potential training topics
 Use of the system.
 General computer concepts.
 Information system concepts.
 Organizational concepts.
 System management.
 System installation.
Training and support activities vary with the target audience. Audience
characteristics that affect training include the following:
• Frequency and duration of system use
• Need to understand the system’s business context
• Existing computer skills and general proficiency
• Number of users
Training for end users must emphasize hands-on use and application of the system
for a specific business process or function, such as order entry, inventory control, or
accounting. If the users are not already familiar with those procedures, training must
also include them. Widely varying skill and experience levels call for at least some
hands-on training, including. practice exercises, questions and answers, and one-on-
one tutorials. Self-paced training materials can fill some of this need, but complex
systems usually require some face-to-face training also. The relatively large number
of end users makes group training sessions feasible, and a subset of well-qualified
end users can be trained and then pass on their knowledge to other users.
System operator training can be much less formal when the operators are not end
users. Experienced computer operators and administrators can learn most or all they
need to know by self-study. Thus, formal training sessions might not be required.
Also, the relatively small number of system operators makes one-on-one training
feasible, if it is necessary.
Determining the best time to begin formal training can be difficult. On one hand, early
training provides plenty of time for learning and can ensure that users “hit the ground
running.” On the other hand, starting early can be frustrating to both users and
trainers because the system might not be stable or complete. End users can quickly
become upset when trying to learn on a buggy, crash-prone system with features
and interfaces that are constantly changing.
In an ideal world, training doesn’t begin until the interfaces are finalized and a test
version has been installed and fully debugged. But the typical end-of-project crunch
makes that approach a luxury that is often sacrificed. Instead, training materials are
normally developed as soon as the interfaces are reasonably stable, and end-user
training begins as soon as possible thereafter. It is much easier to provide training if
system interfaces are developed early and if the top-down modular development
approach is employ.

62. Page | 55
5.Support
Maintenance and System Enhancement
Software maintenance:
Modification of a software product after delivery to correct faults, improve
performance or other attributes, or adapt the product to a changed environment.
a software product after delivery to accomplish at least one of the following
objectives:
• Correct faults
• Improve performance or other attributes
• Adapt the product to a changed environment
Maintenance activities include the following:
• Tracking modification requests and error reports
• Implementing changes
• Monitoring system performance and improving performance or increasing capacity
• Upgrading hardware and system software
• Updating documentation to reflect maintenance changes
Support User
• Support User Up to 1 year.
There are two classes of users—end users and system operators—who must be
considered for documentation, training, and support. End users are people who use
the system from day to day to achieve the system’s business purpose. System
operators are people who perform administrative functions and routine maintenance
to keep the system operating.

63. Page | 56
Supporting the End-user
 Information Center / Help desk
 Automating support
 Resident expert
 Other things to consider:
 Providing recovery and backup
 Disaster recovery
 PC maintenance
The End