Organization Overview: Name of The Organization

Mobile Store Management
ORGANIZATION OVERVIEW
Name of the Organization: - “MAHALAKSHMI COMMUNICATION”
Address of the Organization: -Shop No. 6, Opp. Sant Punjab Hotel, Chembur
Camp, Chembur (E), Mumbai-400 074.
About the Organization:-

MAHALAKSHMICOMMUNICATION is a one stop mobile solution shop that
provides, multi brand handsets, accessories, all under one roof.
Mahalakshmi Communicationcurrently has over 2 outlets and the vision is to have a
network all across City, thus covering virtually every major town in every state across
India.
Mahalakshmi Communicationhas categorized its mobile device offerings into
consumer segments keeping in mind the profiles and needs of different consumers.
The unique segments available in Shop:
Business - PDA & Smartphones, Emails, data transfer etc.
Lifestyle - Fashion phones, Look and elegance
Value for Money - Special offers, discounts and budget phones.
T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

PROJECT DESCRIPTION
NAME OF THE PROJECT: MOBILE STORE MANAGMENT
Following are few characteristics of the Mobile Management System
 Referential Integrity of relational Database is followed

 Use of shortcuts t access different processes is provided for the user having
computer knowledge
 User-Friendly prompts are provided for user.
 Attractive and catch Graphical & Photographic Interfaces are used for user
interaction
 Data reports allow generation of reports dynamically with desired query.
 Strong management system controls are used easy Navigation is provided for
maintaining proper flow of system.

LIMITATIONS OF THE PRESENT SYSTEM
The current system has several shortcomings that are as follows:-
 The existing system was not very effective & was highly time consuming.
 The current system works manually.
 The existing system was somewhat paper-based (paper-work).
 Which takes time?
 The rate at which the work done is very slow due to non-utilization of
computerized system.
 It does not provide better data facilities as well as data availability on
fingertip.
 Inconsistency was the major problem in the existing system as there is no
proper facility was provided to update the data.
 In case user wants to find out details of particular Mobiles whole database
records are displayed.
 It is difficult to remember all data
 Consumes large volume of paper work
 Large storage space is required to keep to the files and register in proper
coordination’s
 In the present system the report generation becomes very difficult.

PROPOSED SYSTEM
 This system computerizes all data is storing all data of the Mobiles Sales,
Customer Details, Employee Details along with Salary.
 Validation at the time of entering data, so no chance of duplication of data.
 Extensive Validation on input record so that no changeable record are Prone to

error.
 Response time for the query should be minimized.
 To keep data base up to date by regular updating.
 Reduce the cost of maintaining system.
 To provide various report facility.
 Cost effective and less manpower required.
ADVANTAGES OF PROPOSED SYSTEM
 The new system would easily overcome most of the short coming of the
current system.
 Owner can see the fine report.
 Not much manual work is involved.
 Ensure data accuracy
 Security of data is done
 Save a lot of time and effort
 Optimize processing time.
 User friendly system.

LIMITATION OF PROPOSED SYSTEM
 Only one person can use the system.

 The system prepared is competent but we cannot say that it is a perfect system.
This system like any other system has some flaws & shortcomings in it. They
are as follows:
o This system is semi-functional. This means that the system covers the
manipulation related to the record only.
o There would be high rate & better quality of performance.

PROCESSING ENVIRONMENT
Processing environment includes hardware and software requirements.
Software Requirement
Operating system: - Windows XP, Windows7

Front-end Tool: - Visual studio 2008
Back-end Tool: - MS SQL2005
Hardware Requirement
Operating system: Windows XP and above.

Minimum 5 GB HDD space
3.00 Megahertz Intel Pentium IV Processor
1 GB RAM

FEASIBILITY STUDY
The feasibility study plays a major role in the analysis of the system. The very
decision of the system analysis whether he should design a particular system or not
and till what extend or limits the very project should be stretched can be inferred from
the system feasibility study. Hence the feasibility study forms the basis of the system.
The feasibility system can be categorized into:
 Technical Feasibility:-
It determines the technology needed for the proposed system is available and
how this technology can be integrated into the organization. Technical evaluation
must also access whether the existing system can be upgraded to use the new
technology and whether the organization has the expertise to use it. Genuine
Computer is equipped with the necessary hardware and software.
 Software Available
Microsoft Windows 98, XP.
Microsoft Office.
 Hardware Available
Intel Pentium IV Processor.
256 MB RAM.
3.5” Floppy Disk Drive.
HP Printer.
DVD Rom
 Organizational and Culture Feasibility:-

The organizational and culture feasibility analysis is done to scrutinize whether the
system sits up with the working environment and the organizational discipline and
rules.
Following issues are considered:
The current level of computer competency.
Re-engineering the old working procedures.
Substantial tech phobia.
Expectation of the users.

 Operational Feasibility:-
The proposed system will automated the existing manual system and make it
user friendly. With the required training the users will find the system easier to
operate. The systems cuts down the time delay of the existing manual system.
 Economic Feasibility:-
The economic feasibility of the system looks upon the financial aspects of the
system. It determines whether the project is economically feasible. In other words, It
determines whether the investment that goes into the implementation of the project is
recoverable. The cost benefit analysis is a commonly used method in evaluating the
effectiveness of the system. As the hardware is already available and no investment is
to be made in that direction, the only cost involved is that of implementing the system
and software.
 Resource Feasibility: -
A resource feasibility test was conducted to check the following things
Availability of manpower
The necessary skills and support on behalf of the staff.
Availability of necessary infrastructure
This test produced the following results:-
First & foremost, each & every functions of each type of user is well defined.
System has a very user friendly environment.
Roles of each user are very well defined.

STAKE HOLDERS
Stake holder is a party that can affect or be affected by the actions of the
business as a whole.
 TYPES OF STAKE HOLDERS:
INTERNAL STAKE HOLDER -

Internal stake holders-Market (or primary)Stake holders are those that are
engaged in economic transactions with the business.
EXTERNAL STAKE HOLDERS-

Non market(or secondary) stake holders are those who although they do
not engaged in direct economic exchange with the business are affected by or
can affect its actions.
 STAKEHOLDERS IN THIS SYSTEM ARE AS FOLLOWS:-
EMPLOYEES
He actually works 24/7 to grow business. Honest, open communication with
them will Impress the rest of stake holders and
Result in sales and profit. Company will be affected if employees are not honest,
loyal. Employees are affected if wrong data is inserted.
CUSTOMER
Customer will be affected if he does not get delivery of Mobiles on time. He
may cancel next order or do not give order at all. This will adversely affect the
company. Company should satisfy clients demand on time.
ADMINISTRATOR
The owner of the admission system needs to keep a check on everything
which is visiting admission system about each and every registration and
viewing and making changes i.e. update, delete etc. this is one of the important
issue to be handled . Industry should be kept on changing according to the
staffs and liking of the Customer/Owner

FACT FINDING TECHNIQUES

Informationandthorough knowledge as well as on job training plays a very important
role in any organization. Acquiring valuable information is essential for developing a
new system in an organization. There are many ways of gathering information. But
the following things need to be kept in mind while gathering information.
No system details are left out.

Problems are correctly identified.
Repetitive work is avoided.
Following are the fact finding techniques:-
o Structured interview
o Mechanical knowledge skills
o Questionnaires
o Record inspection
o Observation
Structured Interview
This method is used to collect the information from groups or individuals.
Analyst selects the people who are responsible and related with the system for
the interviewer. In this method the analyst had dialog and discussion in person
or telephonic conversation.
Record Inspection
The information related to the system is published in the sources like
newspapers, magazines, journals, documents etc. This record review helps the
analyst to get valuable information about the system and the organization.
Observation
Unlike the other fact finding techniques, in this method the analyst himself
visits the organization and observes and understand the flow of documents,
working of the existing system, the users of the system etc. For this method to
be adopted it takes an analyst to perform this job as he knows which points
should be noticed and highlighted. In analyst may observe the unwanted things
as well and simply cause delay in the development of the new system

EVENT TABLE
TRIGGER:
Trigger an occurrence that tells the system that has occurred, either the arrival of data
needing or of a point in time
SOURCE:
An external agent or actor that supplies data to the system.
ACTIVITY:
Behavior that the system performs when an event occurs
RESPONSE:
An output produced by the system that goes to a destination.
DESTINATION:
An external agent or actor that receives data from the system

EVENT TRIGGER SOURCE ACTIVITY RESPONSE DESTINATION
Create an Employee Employee Add Information Employee

Employee Details employee saved
details
Update Update Employee Update Update Employee

Employee employee employee Information
Add Mobile Mobile Mobile Add Mobile Information Mobile

details and and saved
add in in inventory
inventory
Update Update Mobile Update quantity Information Inventory Master
Inventory Mobile updated
Generate Create bill Bill Calculate Bill Bill Master

bill bill amount generated
Save Bill Save Bill Bill Save Bill Information Bill Master
saved
Print Bill Generate and Bill Print bill Take print of Bill master
print Bill
Get Inventory Inventory Produce Report Inventory master

Inventory report master inventory generated
report report

USE CASE
A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its purpose is
to present a graphical overview of the functionality provided by a system in terms
of actors, their goals (represented as use cases), and any dependencies between
those use cases.

ER-DIAGRAM
Symbols used in Entity-Relationship Diagram are as follows:
• Represent Data Entity.
Represent connection Administrator
Connect two Entities or One to One

relation.
• Represent the relationship.

An entity-relationship (ER) diagram is a specialized graphic that illustrates the

interrelationships between entities in a database. ER diagrams often use symbols to
represent three 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.

ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control.
Activity Diagram for system

Activity Diagram for Customer

Activity Diagram for Mobile Phone

Activity Diagram for sales report

CLASS DIAGRAM
In software engineering, a class diagram in the Unified Modeling Language (UML) is

a type of static structure diagram that describes the structure of a system by showing
the system's classes, their attributes, operations (or methods), and the relationships
among the classes.

SEQUENCE DIAGRAM
Sequence diagrams are used to show how objects interact in a given situation. An
important characteristic of a sequence diagram is that time passes from top to bottom:
the interaction starts near the top of the diagram and ends at the bottom (i.e. Lower
equals later).A popular use for them is to document the dynamics in an object-
oriented system.

DFD - LEVEL 1(Top Level DFD)
A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. Often they are a preliminary step
used to create an overview of the system which can later be elaborated. DFDs can also
be used for the visualization of data processing (structured design).

Second level DFD Item master
SECOND LEVEL DFD SALE

Second level DFD Purchase
Second level DFD Employee Detail
Second level DFD Report

CONVERTING ERD TO TABLES
Customer
Employee Product
Bill Receipt Employee salary

STRUCTURE CHART
A Structure Chart (SC) in software engineering and organizational theory is

a chart which shows the breakdown of a system to its lowest manageable levels. They
are used in structured programming to arrange program modules into a tree.

MENU TREE

LIST OFTABLESWITHATTRIBUTES AND

CONSTRAINTS
Table Name: UserMaster

FieldName DateType Key Description
UserName Varchar(100) Primary Key To store username and
Password Varchar(150) ---- password
Table Name: Mobile

MobileID Numeric(18,0) Primary Key To store the Mobile
MobileName Varchar(50) ---- details
batchNo Varchar(50) ----
ExpiryDate datetime ----
ManufacturingDate datetime ----
Price Numeric(18,0) ----
Table Name: Inventory

InventoryID Numeric(18,0) Primary Key To store
MobileID Numeric(18,0) foreign Key Inventorydetailsof the
Quantity Varchar(50) ---- Mobile
Table Name: Employee

employeeID Numeric(18,0) Primary Key To store the Employee
employeeName Varchar(50) ---- details
desigantionID Numeric(18,0) foreign key
salary numeric(18,2) ----
address varchar(50) ----

Table Name: Customer

customerID Numeric(18,0) Primary Key To store Customer
customerName varchar(50) ---- adoption details
address varchar(50) ----
contactNo varchar(50) ----
emailed varchar(50) ----
Table Name:EmployeeDesignation
desiganationID Numeric(18,0) Primary Key To store
Type Varchar(50) ---- EmployeeDesignation
details
Table Name: Attendance

AttendanceID Numeric(18,0) Primary Key To store
employeeID Numeric(18,0) foreign key EmployeeAttendance
attendancevalue Varchar(100) ---- details
attendanceDate Datetime ----
Table Name: Punches

purchesID Numeric(18,0) Primary Key To store the purchased
purchesItem Varchar(50) ---- Item details
purchesDate datetime ----
Quantity Numeric(18,0) ----
Price Numeric(18,0) ----
Total Numeric(18,0) ----

Table Name:Sale

saleID Numeric(18,0) Primary Key To store the details of
MobileID Numeric(18,0) ---- sales of the Mobile
Quantity Numeric(18,0) ----
totalamount Numeric(18,0) ----
Date of sale Datetime ----
customerId Numeric(18,0) ----
tax Numeric(18,0) -----

VALIDATION
The forms were tested for their functionality and error messages are displayed
wherever the input does not meet the required requirements
 Loginform giving error message.

If any invalid user want to take entry into the system then this form restrict him from
entering into the system. By entering invalid username or password it gives an error
message
 CustomerInfoform gives an error message.

CustomerInfoform gives an error message if valid data entry is not done. For
example, phone number should be numeric & length should be greater than 9 and less
than12 digit. CustomerName should be in alphabet. All Information should be filled
up properly
 Customer InfoForm error for invalid data

Customer Info form gives an error message if valid data entry is not done.
Email ID should be proper format.
 SaleForm gives error message

Sale Form gives an error message if we are not Selected the Mobile, Or the Customer
in given filed, required information then error message is shown.
Example: Please select a Mobile.

VALIDATION TABLE
Customer
Field Name Valid values Invalid values
ID admin 1,2
Name admin r@jesh,v@ish,s@rekha
Contact number 985421654 178$%&^
address Nerul,Andheri Ne@rul,And@heri
Mobile
Field name Valid values Invalid values
Id 1 ,2 One, two
name Wall counter wal@lmo@unt_r
date 28/1/2011 28jan-2011
price 4000 Four thousand
Employee
Field name Valid values Invalid values
ID 1,2 One, two
name Rajesh Ra%je@sh
salary 4000 Five thousand

address - -

SCREEN LAYOUT & REPORT LAYOUT
 Splash screen

 Login screen

 MDI FORM

 Add Customer form

 Add Employee form

 Employee update Form

 Add Mobile Form

 Mobile Update Form

 Invoice Generation form

 Employee Salary Form

 Invoice Generation

 Mobile inventory report

 Employee Report

 Customer Form

 Customer Information Report

 Mobile Status Report

 Mobile Available Form

 About us Form

SYSTEM IMPLEMENTATION
 Computer will be used to maintain the records of the Mobile, Customer, sales
and purchase, in the computer database.
 A Computerized report in a particular format can be generated.
 Availability of Mobile can be checked.
 Finding employee,customer,Mobile details is easier.
 The details of the sales and purchasing of Mobiles will be recorded in the
system.

FUTURE ENHANCEMENTS
 The system could be modified suitably to work on a network. This involves,

among other, resolving used conflicts, protecting database integrity and
ensuring consistency of data if it is distributed across multiple locations.
 Maintain attendance details of employee.

 Maintain Mobile details.
 Other possibilities

CONCLUSION
 An attempt is made in all its earnest towards the successful completion of the
project. This system was verified with valid as well as with invalid data.
 This system is user friendly since it has been developed in visual studio 8 a
successful GUI environment. Since the connection can be extended to any
database. The control will be more powerful.
 Connecting it to any type of database extends the development control. Any

suggestions for future development of the system are welcome
 Upgrading the system if may can be done without affecting the proper
functioning of system.

BIBLIOGRAPHY
BOOK REFERENCE
1.) Book name:Murach visual basic 2008

Author: Anne Boehm, Murach
2.) Book name:Database programming with Visual Basic in 21 days

Author:Curtis Smith & Michael Amundsen
WEBSITE REFERENCE
www.google.com
www.webmonkey.com
www.w3schools.com
Thank you.

Organization Overview: Name of The Organization

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Organization Overview: Name of The Organization

Uploaded by

Copyright:

Available Formats

Mobile Store Management

Name of the Organization: - “MAHALAKSHMI COMMUNICATION”

About the Organization:-

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

NAME OF THE PROJECT: MOBILE STORE MANAGMENT

Following are few characteristics of the Mobile Management System

 Referential Integrity of relational Database is followed

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

LIMITATIONS OF THE PRESENT SYSTEM

The current system has several shortcomings that are as follows:-

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

 Validation at the time of entering data, so no chance of duplication of data.

 Extensive Validation on input record so that no changeable record are Prone to

 Response time for the query should be minimized.

 To keep data base up to date by regular updating.

 Reduce the cost of maintaining system.

 To provide various report facility.

 Cost effective and less manpower required.

ADVANTAGES OF PROPOSED SYSTEM

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

LIMITATION OF PROPOSED SYSTEM

 Only one person can use the system.

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

Operating system: - Windows XP, Windows7

Operating system: Windows XP and above.

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

 Organizational and Culture Feasibility:-

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

This test produced the following results:-

System has a very user friendly environment.

Roles of each user are very well defined.

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

 TYPES OF STAKE HOLDERS:

INTERNAL STAKE HOLDER -

EXTERNAL STAKE HOLDERS-

 STAKEHOLDERS IN THIS SYSTEM ARE AS FOLLOWS:-

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

FACT FINDING TECHNIQUES

No system details are left out.

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

EVENT TRIGGER SOURCE ACTIVITY RESPONSE DESTINATION

Create an Employee Employee Add Information Employee

Update Update Employee Update Update Employee

Add Mobile Mobile Mobile Add Mobile Information Mobile

Generate Create bill Bill Calculate Bill Bill Master

Get Inventory Inventory Produce Report Inventory master

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

A use case diagram in the Unified Modeling Language (UML) is a type of

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

Symbols used in Entity-Relationship Diagram are as follows:

• Represent Data Entity.

Represent connection Administrator

Connect two Entities or One to One

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

An entity-relationship (ER) diagram is a specialized graphic that illustrates the

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

Activity diagrams are graphical representations of workflows of stepwise activities

Activity Diagram for system

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012

Activity Diagram for Customer

T.Y. B.Sc. (COMPUTER SCIENCE) 2011– 2012