Presented by:
K.Sravani
S.Harika
P.Shobha
V.D.G.Prakash

---

[attachment=10413]
Introduction….
 About Branch Sales Office Marking System(BSO-MS)
 The term BSO is commonly used to refer to the group of information management methods tied to the automation or support of human decision making.
 Provides information to manage the flow of materials, effectively utilize people and equipment, coordinate internal activities, and communicate with customers.
 It has a user friendly Interface for reporting of data to server.
 System maintains product details ,customer details, purchase indent details, purchase proposal details and material receipt details and generate the delivery order, offer letter, money receipt according to user need.
Problem Specification
Existing System:
 Manually Written.
 Purchasing and Updating Orders are written.
 Require more man power to retrieve the details of requesting the materials and the purchase details.
Disadvantages of existing system
 Data may be lost
 Long process to collecting data
 Employee are enable to communicate with different branches
Advantages of Proposed system
 User friendliness
 User Satisfaction
 Response time
 Error Handling
 Safety
 Robustness
 Reliability
 Less Complexity
 Flexibility
Modules of BSO Marketing system
 Marketing Functions
 Finance Functions
Stockyard Functions
 Management Information System(MIS)
Stockyard Functions
Inputs
 Customer Master details
 Product Master details
 Offer Letter details
 Delivery order details
 DC cum Invoice device
 Money receipt detail
 Outputs
 Customer report
 Product report
 Offer letter generation
 Delivery order preparation
 Money receipt
Requirements
 Hardware Requirements
 CPU Type : P IV (1.2 GH) processor
 RAM : 512 MB.
 Hard Disk : 40 GB
 Mother Board : 100 MHZ
 DESIGN…..
 Use case Diagram
 Class Diagram
Sequence diagram
 SIGNIFICANCE: The sequence diagram in our case specifies how the user and the system interact with each other.
 State chart diagram
 State diagrams typically model the transitions within a single class.
Activity diagram
 The activity diagram in our case focuses on the functionality of the system. It shows in detail how the flow of control takes place in each component. It shows the process in each step.
Component diagram
SIGNIFICANCE:
 A Component Diagram, in particular, is used to describe the dependencies between various software components such as the dependency between executable files and source files. This information is similar to that within make files, which describe source code dependencies and can be used to properly compile an application.
 Deployment diagram
 The deployment diagram in our case focuses on the configuration of components in our system. Deployment diagrams can also be used early on in the design phase to document the physical architecture of a system.
 Screen shots….
BSO MARKETING SYSTEM –Main form
 Login Form
 Stock yard form
 Master menu form
 Customer master form
 Product master form
 Offer letter form
 Delivery order form
 DC cum Invoice form
 Money Receipt Letter form
Reports:
 Customer Report
 Product Report
 Offer letter report
 Delivery order report
 Money receipt report
TESTING….
 Form for Forget password
Conclusion
 The goals of the system has been achieved and bugs are solved. The project is able to successfully incorporate all the requirements.
 The user is provided with a very friendly interface.
 The project is designed and coded in such a way that any further modifications that are needed in the further can be easily implements without affecting the functionality of the system.