Professional Documents
Culture Documents
Project of Database
Project of Database
Project of Database
DATABASE MANAGEMENT
SYSTEM
ON WARID TELECOM
SEMESTER: 6TH
Preface
INTERODUCTION TO BUSINESS
Warid Telecom launched in Pakistan on 23rd May 2005 but its pre
launch operations started working six months before the Launch
this shows the planning masters took enough time studying
Pakistan’s Market and is well equipped to serve in the field of
service based cellular industries in Pakistan.
NATURE OF BUSINESS
MISSION STATEMENT
Company assets
The company’s asset’s information is also recorded in the
database.
Customer’s information
• CEO
• General Managers
• Senior Managers
• Managers
• Assistant Managers
• Executive Managers
• Coordinators
• Supervisors
• Team Members
• Engineers
• Database administrators
• Security guards
• Peons
Packages or the services offered to customers
pre-paid
• Warid Minute Package
• Crazy Hours
• Crazy Nites
• Voice Craze
• Zem ezeeLOAD
• SMS Craze
• Zem Sunday Craze
• infiNite Craze
post-paid
The warid telecom also provides their customers the GPRS, MMS,
WAP service to both pre-paid and post-paid customers.
CUSTOMER ACCOUNT
CUSTOMER NO OF
PACKAGES
SM
S
ALI WA
KHAN P
GPR
S
CUSTOMERS PACKAGES
We can express the overall logical structure of a database
graphically with an E-R diagram.
Its components are:
• Rectangles representing entity sets.
• Ellipses representing attributes.
• Diamonds representing relationship sets.
• Lines linking attribute to entity sets and entity sets to
relationship sets.
In the text, lines may be directed (have an arrow on the end) to
signify mapping cardinalities for relationship sets.
AN EXAMPLE OF ER DIAGRAM.
PACKAGE
ADDRESS
ACCOUNT
ID PHONE NO
CUSTOMER
S CES
E I
US ERV
S BALANCE
NAME INFORMATION
1 Analysis:
Analyzing the user’s requirements.
2 Physical Designs:
Describing what the system should do, as seen from the user.
3 Conceptual Designs:
Describing the system’s interfaces, functionality and structure as
the designers intend to implement them.
4 Implementation:
Producing the programs.
5 Maintenance Design:
As the software is used, errors and new requirements are usually
uncovered. Maintenance is the task of modifying the software so
that the errors are eliminated and the new requirements are taken
care of.
Conceptual Design:
To facilitate rapid and efficient introduction of Warid telecom
new services, we envisage extensive reuse of specifications and
software. In the design phase services are designed by assembling
reusable software components in a controlled manner. Most of the
software components are already designed in detail - the design of
the service concerns the problem of putting various software
components together according to the specification. This should be
a trivial task, supposing there is a well-defined mapping between
the specification constructs and the design objects.
Implementation
The implementation phase concerns the production of complete
programs that satisfy the specification of the WARID Telecom
service. The implementation will ordinarily contain both new
software and reused software. Reused software is taken from a
software library while the new software has to be implemented
now.
Maintenance Design:
Activation means that the service is made available to the user, that
is the service can now be invoked. We refer to the activation of a
service in three different cases:
• The service is freshly installed, and has not been in use.
• The service has been used by other subscribers, and this new
subscription is handled by modifying the new subscriber’s
service profile.
• A subscriber modifies a service’s parameters by operating
directly on his service profile (not all subscribers have the
right to do this). The modification is effectuated by activating
his modified service. This can be viewed as a maintenance
activity. Security requirements must be addressed at this
point.
Creating Tables
Access databases work via numerous tables. The tutorial below
will visually demonstrate different choices you have for building
database tables. It then shows you how to build your first table.
Adding Records
Now you have a database table built, its time to add some records.
Or in other words, add some customers. The tutorial below will
show you how to add a few customer records to your database.
Creating Relationships
In Part VII of the tutorial, we'll create relationships between tables
to complete our implementation of the Patrick's Widgets relational
Queries
Queries are the heart and soul of data retrieval. In Part IX of our
series, you'll learn how to build queries to retrieve information
from an Access database.
Reporting
Once you have information stored in your database, it sure would
be nice to get it back out again! Part X of our series explains how
to use reports to retrieve information from your database
The following tables are
Customer Table
Customer ID Customer Company
Names Name
001 Ali khan Warid telecom
002 Usman Khan Warid telecom
003 Qasim Warid telecom
Rules
Rules further restrict operations based upon specific requirements
and needs. This is accomplished using environmental or
domain-specific decision factors such as database, machine,
IP addresses, and time-of-day and authentication modes. For
example, an organization can prevent an administrator from
making changes to a database system from outside of the
corporate intranet or when working outside of normal
business hours.
Such rules are becoming more crucial as employees
increasingly require remote access to corporate information.
Organizations cannot control the security standards of
external networks, so the best defense is to restrict select
information traffic over pre-approved IP addresses.
Inference channels
A user at a low security class can use his knowledge of the low
security class data and of the constraint (if it is made available to
him) to infer information about high security class data also
affected by the constraint.
Signaling channels
Signaling channels are divided into storage channels and timing
channels. In a storage channel, if satisfaction of an integrity
constraint requires that changes to data at a high security class be
reflected indirectly in the value of data at a lower security class, a
Trojan horse program embedded in a process at a high security
class could encode high data as low data by varying the high data
involved in the integrity constraint so that it produces detectable
changes in the low data. Such a channel could be used to pass on
not only information directly affected by the constraint, but any
other information the Trojan horse has access to.
In a timing channel, if an integrity constraint depends on data at
both high and low security classes, a Trojan horse program could
encode high data by varying the time it takes to make the high data
necessary for verification of the integrity constraint available.
Again, such a channel could be used to pass on any information to
which the Trojan horse has access.
Many of the conflicts between security and integrity in multilevel
secure databases arise out of the fundamental incompatibility of
what we will call the basic security principle for databases with the
database integrity properties of consistency, correctness, and
availability [MEAD88a]. The basic security principle is as follows:
The security class of a data item should dominate the security
classes of all data affecting it. The reason for the basic security
principle is clear: If the value of a datum can be affected by data at
levels not dominated by its own, information can flow into the item
from those other levels. The database integrity properties are
defined as follows:
Integrity
Integrity is usually considered to be at odds with security in
multilevel databases. Integrity constraints enforce conditions on
relations between data, while security constraints enforce
separation between data. If an integrity constraint is defined over
data at different security levels, a direct conflict results. However,
the solution is not to sacrifice the integrity constraint altogether.
Compromise solutions can often be found that guarantee some,
although not all, of the desired results of the constraint. In this
essay we will show that by dividing the desired goals of integrity
into three areas — consistency, correctness, and availability — one
can often find solutions to integrity problems that achieve some, if
not all, of the goals without sacrificing security. The rest of this
essay is structured as follows. After a brief overview of security
issues in multilevel databases, we discuss integrity and describe the
three integrity properties: consistency, correctness, and
availability. Then we discuss integrity in relational databases and
integrity of transactions. We also discuss integrity of object-
oriented databases.
Consistency
A database is consistent if, whenever two different methods exist
for deriving a piece of information, a request for that information
always yields the same response no matter what method is used.
Correctness
A database is correct if all data satisfy all known constraints.
Availability
A database is available if the data in it can be made available to
any authorized user, and any user who is authorized to enter or
update data may do so.
Backup Technique
Backup is very important for any company today. With the many
files stored in a computer, it becomes such a risk to lose any of
these files, primarily because these just may contain information
pertinent to the success of the company itself. Imagine how costly
it would be to lose all classified files from just one computer. Now,
imagine how costly it would be for all computers in your network
to experience massive data loss. This could very well bring your
operations to a sudden end. Thus, backup is a necessity that all
companies have to attend to these days. And it is even more
important to understand the concept of changed files backup.
There are actually several types of backup methods that a company
can choose from. Each backup method comes with its own pros
and cons. The key in choosing a backup method is to find that
particular one that suits your company's needs. But in general,
these are the types of backups that any company should know of:
Full Backup
Mirror Backup
Differential Backup
Incremental Backup
www.waridtel.com
www.scribd.com
www.wikipedia.com
www.freemanagementeassy.com
www.google.com