dbms report for mobile handset
Post on 11-May-2017
224 Views
Preview:
TRANSCRIPT
Mobile store and SIM card management system
Chapter 1
IntroductionThe Mobile Store and SIM card Management System is developed for
desktop systems to facilitate mobile shop owners’ management of customer details and
inventory data, which will include mobile phones, SIM card and accessories. It can be
used efficiently for physically separated shops in different locations. This software will
provide in a simple and easy to operate user interface, which can be managed by any user
without having prior in-depth knowledge of the computer system. One can use this
software to get a sales report. Administrators can pull data, from any location from the
server.
1.1 PurposeThis software is a complete package for those organizations which will allow
them to keep track of their sales and inventory, and provide a computerized billing
system. There are various applications with more complex implementation and features
available in the market, but they are generally very expensive. Therefore, creating an
application with the basic requirement of low cost is essential for small organizations.
This application will allow stores to manage customer details, keep inventory of all
products and purchase information, in a very simple way, using a state-of the-art software
application. It will automatically generate invoices and update inventory.
This project helps to overcome the problems produced during the manual
update(such as loosing data or incapability of data manipulation etc.,) and is used to
maintain database records of different types of mobile handsets, handset within different
budgets, with different configurations, with different OSs and SIM card with different
operators, with different numbers.
1.2 ScopeMobile Store Management System is application software designed to take
advantage of today’s technology and reduce or avoid the burden of storing data on paper
and in files. This facilitates moving purchase, sales, and customer information, SIM card
Dept. of CSE, RVCE Jan – May 2014 Page 1
Mobile store and SIM card management system
management, as well as information of supplier and company data, from paper to digital
media on a secured server. The scope of the project is to illustrate the extensive user
database in developing large applications and to show how front end
(HTML-PHP/VB/JAVA) and backend application (SQL) interact with each other.
1.3 ObjectiveThe main objective of the system is to automate the system which manually
maintains the records of the counter sales, purchases for mobiles and SIM cards, and
other related transactions on the counter. The Mobile Store and SIM card Management
System is designed to reduce paper- based data storage system and provide digital touch
to billing and inventory system. This application is designed in a way that it will only
require a minimum amount of information from the user. This system keeps track of all
the users who have registered for some particular products and that information can be
easily retrieved by anyone who has the access permission.
1.4 Methodology A DBMS software MySQL is used for developing the database to store the
information of the customers of the mobiles and SIM cards.
The SQL commands will be used to create the tables of applicants containing the
various fields of information. After the creation of the database a front end tool
will be used where the customer can interact with the database. Then the customer
will be given with a form to enter his/her credentials.
Then the corresponding details are retrieved from the database and presented to
the customer itself or the authority requesting the information. The customers or
the organization can verify the details regarding the particular mobile handset and
SIM card.
1.5 Organization Of report
Dept. of CSE, RVCE Jan – May 2014 Page 2
Mobile store and SIM card management system
Chapter 2: Background: This chapter discusses the background of mobile store and
SIM card management system and targeted market. This chapter also discusses the
history of mobile store management system. It also discusses different approaches for
mobile Store and SIM card management. At the end of chapter Survey results are
included for the possible use of the application by different businesses.
Chapter 3: Requirements: This chapter describes different requirements for this
application.
Chapter 4: Detailed Design: This chapter discusses the design approach for the database
and application like data flow diagram.
Chapter 5: ER diagram: This chapter discuss about the entity relationship diagram for
the project mobile store and SIM card management system.
Chapter 6: Relational Schema and Normalization: This chapter talks about the
mapping of ER diagram into relational schema where the tables are created and also
about the normalization to remove the redundancy.
Chapter 7: Reports: This Chapter talks about the report generated by the project Mobile
and SIM card management system.
Chapter 8: Conclusion: This chapter discusses the limitations of the implemented
project and the future work that can be done.
Dept. of CSE, RVCE Jan – May 2014 Page 3
Mobile store and SIM card management system
Chapter 2
Background, history, relevant literature survey
2.1 Need for a mobile store management systemIn today’s market, retailers and wholesale outlets should quickly adapt to the ever
changing technology to minimize overhead, lower cost of operation, and help to stay
competitive. Everybody needs software, which can facilitate store operations and make
their day-to-day lives much easier. Mobile Store and SIM card Management System is
application software designed to take advantage of today’s technology and reduce or
avoid the burden of storing data on paper and in files.
This facilitates moving purchase, sales, and customer information, as well as
supplier and company data, from paper to digital media on a secured server. Sales and
purchase bills can be generated as needed. Each store has an option to store their data on
one remote central database server. This will also allow stores to access information from
other partner stores. This would in turn lead to information sharing, so that all the stores
are aware of each other’s current inventory. It will be useful when ordering new
purchases to avoid overstocking.
2.2 Background and motivationThe concept of the Mobile Store and SIM card Management system has been
around for a long time, but it is still in the phase of discussion and design. Initially, all
inventory and billing reports were managed manually by shop owners/employers using
ledger- based systems. This requires a significant amount of time due to repeated access
of the data. There is a high risk of lost or stolen data in that system. Storing old data is
also one big factor. Stores have to spare one separate room to store this information.
Paper- based documents might lose their information with time, and after some years we
can’t really read them at all. So the Mobile Store and SIM card Management System is
designed to reduce paper- based data storage system and provide digital touch to billing
and inventory system.
Dept. of CSE, RVCE Jan – May 2014 Page 4
Mobile store and SIM card management system
2.3 Transformation from paper to computer based systemA modern digital inventory management system must have the ability to keep
track of sales and inventory. It should also provide communication means to contact
suppliers as needed. It should also allow the incorporating shop owner’s ideas to be
implemented into the system. Implementing the idea of the previous section is practical
for an inventory system, and requires combining many technologies into one common
approach. The time taken by a customer care representative of any mobile and SIM card
store to enter information in the computer represents a base of the modern Mobile Store
and SIM card Management System.
Merchants used to write down inventory and sales details. They had to search
their paper records to estimate future needs and retrieve old sales information. They had
to spend significant amount of time every day for such work.
After the Industrial Revolution, efficiency and accuracy became the major factors
of business, along with significant change in positive customer care to increase sales. A
team at Harvard University designed the first modern check-out system in the early
1930s. That system needed punch cards associated with items details. A system would
gather information from the punch card and send it to stored data. As the system that was
used by that time was too expensive for general merchants, this was the first time a store
management system was transformed to a computerized system. Although it was very
expensive, as computer systems during that time were relatively new and too expensive,
this new innovation opened new dimensions to a store management system. Yet, the shop
owners knew that they would need a better management system, and then different ideas
for management systems were introduced, such as bar code scanner, RFID- based
scanning systems.
Merchants knew they needed a better system, and researchers created the
forerunner of the modern bar-coding system in the late 1940s and early 1950s. Bar code
Scanners used ultraviolet ink and a reader to detect items at the time of sale. But this
system also required a significant computer contribution, which was also expensive. The
development of affordable laser technology in the 1960s revived the concept, and lasers
Dept. of CSE, RVCE Jan – May 2014 Page 5
Mobile store and SIM card management system
allowed smaller, faster and cheaper readers, or scanners. The modern bar code, or the
Universal Product Code (UPC), was born and caught on just before the 1970s. The
computers became cheaper and more affordable to support UPC codes and manage
inventory systems with a significant improvement. During the mid to late 1990s, retailers
began implementing modern inventory management systems, made possible in large part
by advances in computer and software technology. The proper inventory management
system ensures that customers would get all their needs met, and merchants would get
their profit at same time.
2.4 Point-of-sale system (an innovative proposal)During evolution from traditional management system, mechanical registers were
also replaced by point-of-sale (POS) systems. POS systems helped to build capabilities
and provide more important advantages. Historically, vendors of POS systems have
focused their marketing efforts on large chain stores, but now they have turned their
attention to small businesses because of their significant potential to grow and expand.
Therefore, small organizations are also encouraged to use more powerful computer
systems and software with a more attractive user interface that uses POS system instead
of an old fashioned mechanical register system. For small organizations, such as mobile
shops, product suppliers, and restaurant owners keeping transactions and inventory
records is very hard and takes a lot of effort. POS system can be very beneficial for small
organizations by providing smooth processes and functions.
As the local data cache is stored in a local drive and transfers to a remote sever,
this POS system can provide significant benefits to the small organizations. This study
proved that checkout processing time, which represents operational performance, was
improved significantly both in the local and the remote server-client models, when an
ADO data cache was embedded in the POS system. The more clients the proposed
system served simultaneously, the greater savings it delivered, especially when large
numbers of items were purchased in a sales transaction.
Dept. of CSE, RVCE Jan – May 2014 Page 6
Mobile store and SIM card management system
Figure 2.1 Remote server- Client POS system
Currently the Mobile Store Management System application is not supporting a
full POS system. It only supports remote server-client environment, so the proposed POS
system can be implemented in future.
2.5 Why computerization is required?Accuracy and efficiency are very important to be competitive in this ever-
changing market, given the advantages of technology. Computerization of any system
will improve efficiency and reduce the cost of operation. For every business, effective
management of inventory is one of the most important factors for success. Inventory
management has significance for any enterprise in an industry because effective practices
in inventory management will allow an enterprise to minimize inventory costs, and
therefore avoid the dire consequences that come with a shortage of resources.
Mantho (1994) classified inventory management into three broad areas:
1. Inventory record keeping: due to the availability of computers at a reasonable price,
it is appropriate to automate inventory records through computerization.
2. Inventory decision-making: many models can be integrated into computer-base
inventory systems.
Dept. of CSE, RVCE Jan – May 2014 Page 7
Mobile store and SIM card management system
3. Material requirement planning (MRP) system: MRP is an IM information system
concerned with getting the right materials to the right place at the right time. (This factor
is not applicable for Mobile Store Management System).
The use of formal practices for managing inventories was also inadequate. Poor
inventory management practices are characterized by the lack of an integrated approach
in the form of the absence of links between physical stock and accounting system. Lack
of appreciation for inventory management among the entrepreneurs and lack of qualified
staff are the two major factors contributing to low inventory management practices.
Considering the above factors, we can conclude that formal practices for inventory
management are not efficient and accurate. At same time, they consume a lot of time,
which lowers the performance of store keepers. Use of a computerized inventory system
will help small businesses to grow and make good benefits from their efforts.
2.6 Survey of current inventory systems in storesA survey was undertaken to find out the existing inventory systems used in the
stores by the different merchants. Each of these stores is using different software based
on their requirements. Although there are several benefits, many small businesses don't
track their inventory using software. Some of the small businesses don't track their
inventory manually at all. In a survey conducted by "WAPS Barcode" company 23% of
the customers had not used any kind of inventory tracking system. 30% turned to pen and
paper based inventory tracking system and 32% are using excel or other general purpose
database to track their inventory. The above survey states that there are still around 53%
of small businesses can be transformed to the digital inventory system.
Dept. of CSE, RVCE Jan – May 2014 Page 8
Mobile store and SIM card management system
Figure 2.2 Survey of types of inventory system used by small businesses
Another survey conducted for different inventory management methods and
software used by local stores in San Diego. Many advanced stores use the software,
which are modified as per their requirements, but they still have not fully functional
software as per their needs. Some of the stores are not using any kind of software and
used to keep inventory manually, while some of the stores do not even track their
inventory.
Dept. of CSE, RVCE Jan – May 2014 Page 9
Mobile store and SIM card management system
Chapter 3Software requirement Specification
3.1 Overall DescriptionThis project is to help mobile and SIM card companies to organize their inventory
and billing system in digital form. The requirement Specification is a document that
describes the external and internal requirements for any system. The Requirement analyst
has to identify the requirements by taking to the clients and understanding their needs.
The inputs are to be gathered from different resources to build the syetem based on the
different requirements. The Requirement phase translates the ideas of the clients into a
formal document. The project mobile store and SIM card management system is software
part of the Mobile Billing and simcard management system. This software helps in
tracking all the customer detail, sales item detail and purchase detail, stock detail, bill
detail and also we can be able to generate report. The main goal of the software is to
build a good management tool.
3.2 Functional RequirementsIt defines the function of a system or its components. This system should have
certain components which are given as follows.
1. Customer: Customer is given with a form in which the user has to fill in his details
required for the purchase of certain products. The details might include the name; address
(permanent/residential), age etc., customer is only allowed to view/alter his own data. He
cannot access others’ data without the authentication.
2. Retailer/manager: they are the parts of supply chain. Selling or renting the products
and services of the company. They handle financial transactions.
3. Salesman: sales person has a major responsibility of associating with the retail store.
He/she is in charge of the entire customer experience in the store.
4. Distributors/supplier: a distributor organizes the storage and distribution of products.
He/she also plans and manages the delivery of products to suppliers, retailers or to
customers. They should be aware of essential components such as legislation, fuel cost
etc.,
Dept. of CSE, RVCE Jan – May 2014 Page 10
Mobile store and SIM card management system
5. Network providers/mobile network operators: these are an independent
communication service provider that manages mobile communication between the
subscribed mobile users with users in the same and external wired or wireless telecom
networks.
3.3 User Interface RequirementsThe application should be very simple and easy to use by any user. Below are the
basic requirements of general user interface:
The application shall be easy to use.
The application shall take few inputs from user.
The understanding time of the application shall be very small.
3.4 Non Functional RequirementsUsability: The system should be very easy to use and The managing system has to take
less time to manipulate, update or manage data. The system shall allow the users to
access the system from the Internet using HTML or it’s derivative technologies. The
system uses a web browser as an interface. The system should be user friendly and m has
to be used easily.
Reliability: The system developed has to be very efficient and reliable. System should be
used at any time. The system should hide one users’ data from other. The principle
method of building a reliable system is to provide redundancy in system components.
Availability: This system should be available at very low price and recovery should be
easy in case of severe system failures. the system should take less time for recovery or to
reduce/eliminate the failure. The system should take less time to access the required data
(reachable data).
Safety and Security: The data submitted by the user should be present in a secure
database that can be accessed only by the administrator. Only after necessary
authentication, users can access their profile. There should be a limit for a user to access
the data i.e., the user should be capable of getting what he can reach upto, user should not
be allowed to access the information of the others.
Dept. of CSE, RVCE Jan – May 2014 Page 11
Mobile store and SIM card management system
Chapter 4
Detailed Design4.1 High level designFigure 4.1 explains the communication process between multiple stores using a central
server. Each store stores their information on central server and fetches needed
information from same server. If any store needs to access a different store’s information,
they can access this information easily. Currently there is no separate security system
implemented to access different stores. The central server is managing all the information
for different stores. The central server has different partitions for each store.
Figure 4.1 High level designs
4.2 System architectureThis diagram describes architecture of the system, which represents information sharing
within the system. Figure 4.2 shows the system architecture. It shows a three-tier
architecture between users, server, and database.
Dept. of CSE, RVCE Jan – May 2014 Page 12
Mobile store and SIM card management system
Figure 4.2. Three tier system architecture.
4.2.1 Presentation TierThis part of architecture is responsible for communication between the end user
and the application system. A user interacts with the application using this module of
system. This is the topmost level of the application. The presentation tier displays
information related to such services as browsing merchandise, purchasing, and shopping
cart contents. It communicates with other tiers by outputting results to the browser/client
tier and all other tiers in the network. The application like Mobile Store Management
System uses Visual Studio or Java for user interface development. The Mobile Store
Management System uses Visual Basic.
4.2.2 Logic TierThis is a very important tier for any architecture. It is very essential at same time.
This tier is responsible for the logical processes. This tier communicates with the
database and application and at the same time provides other significant services such as
calculations and logical decisions. This tier is independent from the database and
presentation tier. The logical part never changes with the change of the other tiers. This
Dept. of CSE, RVCE Jan – May 2014 Page 13
Mobile store and SIM card management system
tier is responsible for creating and managing database. At same time it is also responsible
for sending required data to the presentation tier.
4.2.3 Data TierThis database tier is responsible for communicating with the database and the
logical tier. This layer provides access to the database and manages a connection with the
database. The Mobile Store and SIM card Management System is using SQL server.
MySQL, Access, and SQL Server are major database programs used for this tier.
4.3 Data Flow diagramData flow diagram represents the flow data during the operation of any process. In
Mobile Store and SIM card management system data flow diagram indicates the flow of
data during the different phases of transaction.
4.3.1 DFD level 0
Dept. of CSE, RVCE Jan – May 2014 Page 14
Mobile store and SIM card management system
DFD level 0 indicates the users who are connected to the database directly. That is it
indicates that data can flow from database to indicated users during the operation.
4.3.2 DFD level 1
DFD level 1 indicates the data flow between the database and the customer, mobile parts
assembling company.
4.3.3 DFD level 2
Dept. of CSE, RVCE Jan – May 2014 Page 15
Mobile store and SIM card management system
DFD level 2 Indicates the data flow between data base and showroom as well as
salesman.
4.3.4 DFD level 3
DFD – level 3
Dept. of CSE, RVCE Jan – May 2014 Page 16
Mobile store and SIM card management system
DFD – level 3 (contd..)
DFD – level 3 (contd..)
Dept. of CSE, RVCE Jan – May 2014 Page 17
Mobile store and SIM card management system
DFD – level 3 (contd..)
The data flow can be easily identified with the help of data flow diagrams.
Dept. of CSE, RVCE Jan – May 2014 Page 18
Mobile store and SIM card management system
Chapter 5ER Diagram
An Entity-Relationship Diagram (ER Diagram) classically serves as the main deliverable for an intangible data model. An ER Diagram is logical exemplification data, and consists of three chief components:
Entity: It is a piece in the real world that is distinct from other objects. Attributes: It is an asset of an entity. Relationships: It is a linkage between two entities or attributes.
An E-R Diagram is important to demonstrate design of a database and used to plan database as well. The following is an ER diagram for Mobile store and SIM card management
Figure 5.1 ER diagram
The ER diagram of Mobile Store and SIM card Management system consists of Part Manufacturing Company, Part, Part supplier, Mobile parts assembling company, part of mobile, showroom, simcard, manager, purchaser, item, mobile handset and salesman as the real world objects called as entities. It also consists of those relations which connects all these entities. Every entity contains a primary key so all the designed entities are strong entities.
Dept. of CSE, RVCE Jan – May 2014 Page 19
Mobile store and SIM card management system
Chapter 6 Relational Mapping Relational mapping in data management, is the process of creating data
element mappings between two distinct data models.
6.1 Algorithm for ER mappingStep 1: Mapping of Regular Entity Types.
For each regular (strong) entity type E in the ER schema, create a relation R that
includes all the simple attributes of E.
Choose one of the key attributes of E as the primary key for R.
If the chosen key of E is composite, the set of simple attributes that form it will
together form the primary key of R.
Step 2: Mapping of Weak Entity Types
For each weak entity type W in the ER schema with owner entity type E, create a
relation R & include all simple attributes (or simple components of composite
attributes) of W as attributes of R.
Also, include as foreign key attributes of R the primary key attribute(s) of the
relation(s) that correspond to the owner entity type(s).
The primary key of R is the combination of the primary key(s) of the owner(s)
and the partial key of the weak entity type W, if any.
Step 3: Mapping of Binary 1:1 Relation Types
For each binary 1:1 relationship type R in the ER schema, identify the relations S
and T that correspond to the entity types participating in R.
There are three possible approaches:
Dept. of CSE, RVCE Jan – May 2014 Page 20
Mobile store and SIM card management system
1. Foreign Key approach: Choose one of the relations-say S-and include a foreign
key in S the primary key of T. It is better to choose an entity type with total
participation in R in the role of S.
2. Merged relation option: An alternate mapping of a 1:1 relationship type is
possible by merging the two entity types and the relationship into a single
relation. This may be appropriate when both participations are total.
3. Cross-reference or relationship relation option: The third alternative is to set
up a third relation R for the purpose of cross-referencing the primary keys of the
two relations S and T representing the entity types.
Step 4: Mapping of Binary 1:N Relationship Types.
For each regular binary 1:N relationship type R, identify the relation S that
represent the participating entity type at the N-side of the relationship type.
Include as foreign key in S the primary key of the relation T that represents the
other entity type participating in R.
Include any simple attributes of the 1:N relation type as attributes of S.
Step 5: Mapping of Binary M:N Relationship Types.
For each regular binary M:N relationship type R, create a new relation S to
represent R.
Include as foreign key attributes in S the primary keys of the relations that
represent the participating entity types; their combination will form the primary
key of S.
Also include any simple attributes of the M:N relationship type (or simple
components of composite attributes) as attributes of S.
Step 6: Mapping of Multivalued attributes.
For each multivalued attribute A, create a new relation R.
Dept. of CSE, RVCE Jan – May 2014 Page 21
Mobile store and SIM card management system
This relation R will include an attribute corresponding to A, plus the primary key
attribute K-as a foreign key in R-of the relation that represents the entity type of
relationship type that has A as an attribute.
The primary key of R is the combination of A and K. If the multivalued attribute
is composite, we include its simple components.
Step 7: Mapping of N-ary Relationship Types.
For each n-ary relationship type R, where n>2, create a new relationship S to
represent R.
Include as foreign key attributes in S the primary keys of the relations that
represent the participating entity types.
Also include any simple attributes of the n-ary relationship type (or simple
components of composite attributes) as attributes of S.
Step8: Options for Mapping Specialization or Generalization.
Convert each specialization with m subclasses {S1, S2,…., Sm} and generalized
superclass C, where the attributes of C are {k,a1,…an} and k is the (primary) key,
into relational schemas using one of the four following options:
1. Option 8A: Multiple relations-Superclass and subclasses
2. Option 8B: Multiple relations-Subclass relations only
3. Option 8C: Single relation with one type attribute
4. Option 8D: Single relation with multiple type attributes
Option 8A: Multiple relations-Superclass and subclasses
Create a relation L for C with attributes Attrs(L) = {k,a1,…an} and PK(L) = k.
Create a relation Li for each subclass Si, 1 < i < m, with the attributes Attrs(Li) =
{k} U {attributes of Si} and PK(Li)=k. This option works for any specialization
(total or partial, disjoint of over-lapping).
Dept. of CSE, RVCE Jan – May 2014 Page 22
Mobile store and SIM card management system
Option 8B: Multiple relations-Subclass relations only
Create a relation Li for each subclass Si, 1 < i < m, with the attributes Attr(Li) =
{attributes of Si} U {k,a1…,an} and PK(Li) = k. This option only works for a
specialization whose subclasses are total (every entity in the superclass must
belong to (at least) one of the subclasses).
Option 8C: Single relation with one type attribute
Create a single relation L with attributes Attrs(L) = {k,a1,…an} U {attributes of
S1} U…U {attributes of Sm} U {t} and PK(L) = k. The attribute t is called a type
(or discriminating) attribute that indicates the subclass to which each tuple
belongs
Option 8D: Single relation with multiple type attributes
Create a single relation schema L with attributes Attrs(L) = {k,a1,…an} U
{attributes of S1} U…U {attributes of Sm} U {t1, t2,…,tm} and PK(L) = k. Each
ti, 1 < I < m, is a Boolean type attribute indicating whether a tuple belongs to the
subclass Si
Step 9: Mapping of Union Types (Categories).
For mapping a category whose defining superclass will have different keys, it is
customary to specify a new key attribute, called a surrogate key, when creating a
relation to correspond to the category.
Dept. of CSE, RVCE Jan – May 2014 Page 23
Mobile store and SIM card management system
Figure 6.1 Relational mapping
Dept. of CSE, RVCE Jan – May 2014 Page 24
Mobile store and SIM card management system
Chapter 7
Normalization
Database normalization is the process of organizing the fields and tables of a relational
database to minimize redundancy. Normalization usually involves dividing large tables
into smaller (and less redundant) tables and defining relationships between them. The
objective is to isolate data so that additions, deletions, and modifications of a field can be
made in just one table and then propagated through the rest of the database using the
defined relationships.
Edgar F. Codd, the inventor of the relational model, introduced the concept of
normalization and what we now know as the First Normal Form (1NF) in 1970. Codd
went on to define the Second Normal Form (2NF) and Third Normal Form (3NF) in
1971, and Codd and Raymond F. Boyce defined the Boyce-Codd Normal Form (BCNF)
in 1974. Informally, a relational database table is often described as "normalized" if it is
in the Third Normal Form. Most 3NF tables are free of insertion, update, and deletion
anomalies.
A standard piece of database design guidance is that the designer should first
create a fully normalized design; then selective renormalization can be performed
for performance reasons.
7.1 First normal form (1NF): It is a property of a relation in a relational database. A relation is in first normal form if
the domain of each attribute contains only atomic values, and the value of each attribute
contains only a single value from that domain.
It can be used when we come across composite attribute or any multivalued
attributes. In the given example it is done using a composite attribute.
Dept. of CSE, RVCE Jan – May 2014 Page 25
Mobile store and SIM card management system
Example.,
In the above relation, pname is a composite attribute. Hence the relation is not in 1NF. To
make it 1NF, the composite attributes are decomposed into simple attributes as follows.
It is now in 1NF
7.2 Second normal form (2NF):
It is a normal form used in database normalization. 2NF was originally defined by E.F.
Codd in 1971. A table that is in first normal form (1NF) must meet additional criteria if it
is to qualify for second normal form. Specifically: a table is in 2NF if and only if it is in
1NF and no non-prime attribute is dependent on any proper subset of any candidate
key of the table.
A non-prime attribute of a table is an attribute that is not a part of any candidate key of
the table. Put simply, a table is in 2NF if and only if it is in 1NF and every non-prime
attribute of the table is dependent on the whole of a candidate key.
Dept. of CSE, RVCE Jan – May 2014 Page 26
Mobile store and SIM card management system
Example.,
Both maid and pid derives maaddress and panumber. But if maid is alone considered, it
can derive maaddress. Hence becomes partial. Similarly only pmid can derive panumber.
Hence the relation is not in 2NF. To make it in 2NF, the relation is decomposed as
follows.
It is in 2NF
7.3 Third normal form (3NF): is a normal form used in database normalization.
3NF was originally defined by E.F. Codd in 1971. Codd's definition states that a table is
in 3NF if and only if both of the following conditions hold:
The relation R (table) is in second normal form (2NF)
Every non-prime attribute of R is non-transitively dependent on every super
key of R.
A non-prime attribute of R is an attribute that does not belong to any candidate key of
R. A transitive dependency is a functional dependency in which X → Z (X determines Z)
indirectly, by virtue of X → Y and Y → Z (where it is not the case that Y → X).
Dept. of CSE, RVCE Jan – May 2014 Page 27
Mobile store and SIM card management system
A 3NF definition that is equivalent to Codd's, but expressed differently was given by
Carlo Zaniolo in 1982. This definition states that a table is in 3NF if and only if, for each
of its functional dependencies X → A, at least one of the following conditions holds:
X contains A (that is, X → A is trivial functional dependency), or
X is a super key, or
Every element of A-X, the set difference between A and X, is a prime
attribute (i.e., each attribute in A-X is contained in some candidate key)
Zaniolo's definition gives a clear sense of the difference between 3NF and the more
stringent Boyce–Codd normal form (BCNF). BCNF simply eliminates the third
alternative ("Every element of A-X, the set difference between A and X, is a prime
attribute").
Example.,
In the above relation srid - >manid and manid - >mname, start_date. Hence there exists
transitive dependency. Hence it is not in 3NF. To bring it down to 3NF, it is decomposed
as given here.
Dept. of CSE, RVCE Jan – May 2014 Page 28
Mobile store and SIM card management system
It is in 3NF.
Chapter 8
TechnologySelecting technologies to develop any application is the very first step in order to
complete an application successfully. After considering various factors, I have decided to
use Visual Basic and SQL Server to develop Mobile Store Management System. Many
low cost projects employ Visual Basic to develop application and access database.
However, SQL Server is chosen as the technology for this project because of the needs to
centralize data storage when used by multiple stores. SQL Server Express is freely
available from the Microsoft website.
8.1 VISUAL BASIC
VISUAL BASIC is a high level programming language evolved from the earlier DOS
version called BASIC. BASIC stands for Beginners' All-purpose Symbolic Instruction
Code. The program codes in Visual Basic resemble English language. VISUAL BASIC is
a visual and events driven Programming Language.
These are the main divergences from the old BASIC. In BASIC, programming is
done in a text-based environment, and the Program is executed sequentially. In VISUAL
BASIC, programming is done in a graphical Environment. Visual Basic is sometimes
called Rapid Application Development (RAD) system because it enables programmers to
quickly build prototype applications.
Advantages of Visual Basic: The graphical user interface of the VB-IDE provides
intuitively appealing views for the management of the program structure in the large
scale and the various types of entities (classes, modules, procedures, forms).
Powerful Front-End Tool: Event driven concept equipped with advanced features of
object oriented programming along with user friendly IDE makes Visual Basic a
powerful programming and front-end tool. Visual Basic can accomplish simple to
complex business requirements in a very productive and efficient manner. It has
wonderful chemistry with multiple databases, including DBMS (Database Management
Dept. of CSE, RVCE Jan – May 2014 Page 29
Mobile store and SIM card management system
System), like Microsoft Access, RDBMS (Relational Database Management System),
like Microsoft SQL Server and Sybase, and ORDBMS (Object Relational Database
Management System) like Oracle. It can also work with Flat Text file and Microsoft
Excel data files.
Standalone and Distributed Applications: User can create standalone as well as
distributed application with Visual Basic. Standalone refers to a program, which runs on
user’s single desktop, and users’ machine acts as both server and client. In distributed
types, user can install multiple copies of your program or work with single installation in
COM+ environment on corporate network.
8.2 SQL serverSQL Server provides database to store information on remote location. We will see
introduction of SQL server before we start detail functionality of the SQL Server.
8.2.1 What is SQL?SQL Server is a database management system. SQL is an acronym for “Structured Query
Language” and, as mentioned previously, SQL is a standard computer language for
maintaining and utilizing data in relational databases. SQL is a language that allows users
to communicate with relational databases. The American National Standard Institute
(ANSI) introduced its very first version of standards for the language in 1986. After that
first release we have seen several revisions of the language.
It is also described that the SQL language has three major components. The first
component is DML (Data Manipulation Language), which allows you to add, delete,
update, or retrieve data within a database. The second component is DDL (Data
Definition Language), which allows you to create, delete, or modify the database. It also
allows providing update statement, which allows you to modify the tables in the database.
The third component is DCL (Data Control Language), which maintains proper security
for the database. It means it provides security feature to the database, which makes SQL
so important.
Dept. of CSE, RVCE Jan – May 2014 Page 30
Mobile store and SIM card management system
8.2.2 How is it Different from Other Languages?It has been seen discussion of this question, which gives a good overview of the
differences between SQL and other languages. Let’s see a comparison with Visual Basic
or C++, which are much more familiar languages.
These languages are procedural in nature. Procedural nature means that those
languages allow users to specify particular procedures to achieve a desired goal. On the
other hand, SQL is declarative in nature. SQL needs declaration with a single statement
to achieve the desired goal. SQL has simple structure, as it is only concerned with
relational databases rather than the entirety of computer systems.
8.2.3 SQL ServerMicrosoft SQL Server is available in several versions and editions. Available editions run
from a basic Express edition to a fully featured Enterprise edition. The Express edition is
free but still has an abundance of features that allow you to get started with full-fledged
database development.
The Enterprise edition includes many sophisticated database management
features, plus complex business intelligence components. SQL Server is a more robust
database management system. SQL Server was designed to have many hundreds, or even
thousands of users accessing it at any point in time. Microsoft Access, on the other hand,
doesn't handle this type of load very well. SQL Server is a database application to look
after the backend of a system (storing the data, controlling transactions, etc.).
There are many options available, ranging from SQL Server Express Edition
(formally MSDE) which supports 5-10 simultaneous users, to SQL Server Enterprise
Edition. Having a centralized place to store data is a great benefit to SQL Server users.
Centralization is the primary SQL Server benefit that means that everyone is using the
same data source. As a result, there is no need to merge information together in order to
receive an accurate version of a record. With centralized data, every time that one
retrieves a record, one will be confident that they have the latest information.
Dept. of CSE, RVCE Jan – May 2014 Page 31
Mobile store and SIM card management system
Chapter 9
Report generations
Dept. of CSE, RVCE Jan – May 2014 Page 32
Mobile store and SIM card management system
Dept. of CSE, RVCE Jan – May 2014 Page 33
Mobile store and SIM card management system
Chapter 10
Conclusion10.1 SummaryIn this dissertation we have studied different management systems used during evaluation
and presented a low cost store management system application with the help of that
study. A survey was also conducted to get current needs of small businesses which could
be willing to migrate to the Mobile Store and SIM card Management System application.
The implementation of this system as a single solution for different businesses was
challenging. We have learnt a lot about document writing during this progression. The
process of writing thesis document, which is a research paper, was not familiar for us, but
is of great benefit. The application Mobile Store and SIM card Management System is
Dept. of CSE, RVCE Jan – May 2014 Page 34
Mobile store and SIM card management system
created to help small businesses to transfer their records from paper-based system to
computerized system, even with a low budget.
At the same time, the requirements of a basic store have been taken care of, and a
few features that can make the application easier to use and easy to understand to the user
with beginner level knowledge of computers have been added. We hope that Mobile
Store and SIM card Management System fulfills all basic requirements for stores with
intention of transferring to computerized billing and inventory system. The survey of real
world small businesses helped us to understand current practice, and possible needs.
10.2 Limitation
The Mobile Store and SIM card Management System has some flows and limitation due
to different requirements and time constrain. As this application will be used on the
computers so the end user must have the basic knowledge of the computers. Currently
only one item’ information can be entered in the system at a time.
The user has to enter information for different items. The system currently has
only one combination of username and password credentials, every user has to share
same credentials. The search function only supports search using ID number. The user
has to get ID number of customer, sales, purchase, product, or supplier to search within
the system.
10.3 Future enhancementThis system can add multiple usernames and passwords with user- wise separate access
and authorities. This can implement search function using different information also. It is
also possible to integrate an employee’s time card and a payroll management system in
this application. There is another idea to implement SIM card management system. Using
bar code scanner and smart card reader, user can minimize manual data entry, which will
potentially decrease the amount of time to enter data. But at the same time it will increase
the cost of this application.
Dept. of CSE, RVCE Jan – May 2014 Page 35
Mobile store and SIM card management system
Chapter 11
Snapshots
Dept. of CSE, RVCE Jan – May 2014 Page 36
Mobile store and SIM card management system
Snapshot 1: Front page
Snapshot 2: Validation
Dept. of CSE, RVCE Jan – May 2014 Page 37
Mobile store and SIM card management system
Snapshot 3: Validation
Snapshot 4: Security
Dept. of CSE, RVCE Jan – May 2014 Page 38
Mobile store and SIM card management system
Chapter 12
References 1. WIKIPEDIA, Microsoft SQL server. Wikipedia,
http://en.wikipedia.org/wiki/MicrosoftSQLServer , accessed February 26th 2014
at 8.56 pm.
2. SQL SERVER PROGRAMMERS, Benefits of SQL server. SQL Server
Programmers, http://www.sql-programmers.com/Benefits-of-sql.aspx, accessed
march 5th 2014 at 6.34 pm.
3. WIKIPEDIA, Multi-tier architecture. Wikipedia,
http://en.wikipedia.org/wiki/Multitier_architecture.
4. SQL SERVER PROGRAMMERS, Benefits of SQL server. SQL Server
Programmers, http://www.sql-programmers.com/benefits-of-sql.aspx
5. WEBOPEDIA, VisualBasic. Webopedia, http://www.webopedia.com/TERM/V/V
isualBasic.html
Dept. of CSE, RVCE Jan – May 2014 Page 39
top related