1. WHAT ARE DATABASE OBJECTS? EXPLAIN THE PURPOSE OF EACH BRIEFLY.

A database object in a relational database is a data structure used to either store or reference data. The
most common object that people interact with is the table. Other objects are indexes, stored
procedures, sequences, views and many more.

When a database object is created, a new object type cannot be created because all the various object
types created are restricted by the very nature, or source code, of the relational database model being
used, such as Oracle, SQL Server or Access. What is being created is instances of the objects, such as a
new table, an index on that table or a view on the same table.

Most of the major database engines offer the same set of major database object types:

 Tables
 Indexes
 Sequences
 Views
 Synonyms

1. Tables
Oracle stores information in the form of tables. For eg you can have a table named as climate in which
you can store information about the climate of a place in the form of columns which could be the
temperature, name of the place, date, humidity, etc. In the terms of a relational database, one can call a
table as an entity and the columns as it attributes.
2. Indexes
Indexing is a concept of listing of keywords accompanied by the location of information of the subject.
Indexes are used to speed up the processing, especially searching.
3. Views
A view is a way of hiding the logic that created the joined table just displayed. For example: create view
AB
Select A.x, B.y from A, B where A.x = B.y;
You can query it as select x, y from AB.
Note: AB is the view name, A, B are the Table names with x and y as their column names respectively.
For views, you don’t need to specify the tables as the logic is hidden inside the views.
4. Synonyms
A synonym is a name assigned to a table or view that may be used refer to it thereafter. If you have an
access to another users table, you may create a synonym for it and refer to it by the synonym alone,
without entering the users name as a qualifier. Using synonyms is a good way to implement location
transparency.
5. Sequences
Tables usually have a primary key which uniquely identifies a row in a table. A sequence is a unique
number generator which can be assigned to the primary keys of the tables.
Eg create sequence xyz
increment by 1
start with 1;
2. EXPLAIN THE THREE-TIER APPLICATIONS ARCHITECTURE WITH IMPORTANCE OF EACH

A three-tier architecture is a client-server architecture in which the functional process logic, data
access, computer data storage and user interface are developed and maintained as independent
modules on separate platforms. Three-tier architecture is a software design pattern and a well-
established software architecture.

Three-tier architecture allows any one of the three tiers to be upgraded or replaced independently.
The user interface is implemented on a desktop PC and uses a standard graphical user interface
with different modules running on the application server. The relational database management
system on the database server contains the computer data storage logic. The middle tiers are
usually multitiered.

The three tiers in a three-tier architecture are:

1. Presentation Tier: Occupies the top level and displays information related to services
available on a website. This tier communicates with other tiers by sending results to the
browser and other tiers in the network.

2. Application Tier: Also called the middle tier, logic tier, business logic or logic tier, this tier is
pulled from the presentation tier. It controls application functionality by performing detailed
processing.

3. Data Tier: Houses database servers where information is stored and retrieved. Data in this
tier is kept independent of application servers or business logic.
3. EXPLAIN Etom LEVEL ZERO WITH A SUITABLE DIAGRAM. (ROWS & COLUMNS TITLES
ONLY)

The Business Process Framework (eTOM) describes and analyzes different levels of enterprise processes according
to their significance and priority for the business. The framework is defined as generically as possible so that it
remains organization-, technology-, and service-independent.
For service providers, the Business Process Framework serves as the blueprint for process direction. It also provides
a neutral reference point for internal process reengineering needs, partnerships, alliances, and general working
agreements with other companies.
For suppliers, the Business Process Framework outlines potential boundaries of software components that should
align with their customers' needs, as well as highlighting the required functions, inputs, and outputs that must be
supported by their products. At the overall conceptual level (Figure 3), the Business Process Framework can be
viewed as having the following three major process areas:
• Strategy, Infrastructure, and Product (SIP) covering planning and lifecycle management
• Operations covering the core of day-to-day operational management
• Enterprise Management covering corporate or business support management
Figure 3. eTOM Level 0 Model (Copyright TM Forum)

The Level 0 Framework also includes views of functionality as they span horizontally across an enterprise's internal
organizations:
• Market, Product, and Customer: High-level view of the market and the enterprise's offerings
• Service: Product components developed by the enterprise
• Resource (Application, Computing, and Network): Consumed in the production of the Service
• Supplier/Partner: Providing products and services to the enterprise for the production of the Service
The eTOM layers can generally be described as following:
• Level 0: Business Activities that distinguish operational customer-oriented processes from management and
strategic processes
• Level 1: Process Groupings including business functions and standard end-to-end processes
• Level 2: Core Processes that combine together to deliver service streams and other end-to-end processes
• Level 3: Tasks and associated detailed "success model" business process flows
• Level 4: Steps and associated detailed operational process flows with error conditions and product and
geographical variants (where required)
• Level 5: Further decomposition into operations and associated operational process flows where required
4. STATE THE AREAS ADDRESSED IN ENTERPRISE MANAGEMENT AND EXPLAIN ANY ONE IN
DETAIL.
5. STATE THE SIMILARITIES/DIFFERENCE BETWEEN ETOM AND ITIL WITH REFERENCE TO
SCOPE, IMPLEMENTATION AND COMPLIANCE.

eTOM ITIL®

Context • eTOM is a prescriptive catalogue of Process • ITIL ® is a set of nonprescriptive guidelines for IT/ICT
Element categories and a total enterprise Service Management.
process framework for the ICT industry.

Objectives • Provides a business process blueprint for • Aligns IT services with the current and future needs of
service providers to streamline their end-to- the business and its customers.
end processes. • Enables standard terminology across business and IT.
• Enables effective communication and common • Improves the quality of the IT services delivered.
vocabularies within the enterprise as well as
with customers and suppliers. • Reduces the long-term cost of service provision.

Scope • Provides a top-down hierarchical view of • The ITIL ® processes represent flows in a number of key
business processes across the whole operational areas, with a strong orientation towards how
enterprise and does not itself address how these processes will map onto IT support environments.
these processes are supported by automated • Processes are developed through flows.
or human action (this is, however, addressed
in the wider NGOSS program of the TMF). • It is primarily nonprescriptive, offers advice and guidance
on the implementation and continued delivery of service
• Processes are developed through iterative management, including planning common processes,
decomposition. roles, and activities with appropriate reference to each
• It focuses on identifying the commonality of other and how the communication lines should exist
enterprise processes required among similar between them.
services, such as telephony, data, Internet, • ITIL ® is primarily focusing on serving internal IT
mobiles, etc., for delivering high-quality, end- customers.
to-end service management.
• eTOM focuses on service delivery to external
customers.

Adoption • eTOM has been adopted as ITU International • ITIL ® is a set of best practices that is used by tens of
Standards for the Telecom Sector, and thousands of companies worldwide and continues to be
primarily used by Service Providers in the ICT advanced by itSMF local chapters:http://www.itsmf.com/
industry. eTOM is advanced by TM
Forum: http://www.tmforum.org/

Implementati • eTOM is a framework; therefore, the • ITIL ® is a framework; therefore, the implementation will
on implementation will be different from company be different from company to company.
to company. • Until recently, ITIL ® did not provide guidelines on the
• The implementation of eTOM is supported by implementation order or means to assess the maturity of
other TMF/NGOSS specifications, including the service organization. In Version 3, more attention is
the Shared Information/Data Model (SID), being paid to implementation guidelines.
NGOSS Lifecycle and Methodology, and other
related specifications.

Compliance • eTOM compliance is achieved through the • ITIL ® is not a standard, nor is it a set of regulations, and,
TMF/NGOSS Compliance Program; its therefore, neither tools, processes, or people can be
certification is on tools not on organizations or deemed "ITIL ® compliant." Processes and organizations
processes. NGOSS compliance program can be assessed against ISO 20000, the IT Service
encompass the conformance tests of other Management standard based on ITIL ®. However, neither
NGOSS specifications that further define the tools nor individuals can be certified against ISO 20000.
business objects and operations framework
required for effective eTOM implementation.
6. MAPPING THE CARDINALITIES
A mapping cardinality is a data constraint that specifies how many entities an entity can be
related to in a relationship set. Example: A student can only work on two projects, the number of
students that work on one project is not limited.
A binary relationship set is a relationship set on two entity sets. Mapping cardinalities on
binary relationship sets are simplest. Consider a binary relationship set R on entity sets A and B.
There are four possible mapping cardinalities in this case:
1. one-to-one - an entity in A is related to at most one entity in B, and an entity in B is
related to at most one entity in A.

2. one-to-many - an entity in A is related to any number of entities in B, but an entity in B

is related to at most one entity in A.

3. many-to-one - an entity in A is related to at most one entity in B, but an entity in B is

related to any number of entities in A.

4. many-to-many - an entity in A is related to any number of entities in B, but an

entity in B is related to any number of entities in A.
7. JOINS

In a relational database system like Access, you often need to extract information from more than
one table at a time. This can be accomplished by using an SQL JOIN statement, which enables
you to retrieve records from tables that have defined relationships, whether they are one-to-one,
one-to-many, or many-to-many.

INNER JOINs

The INNER JOIN, also known as an equi-join, is the most commonly used type of join. This join
is used to retrieve rows from two or more tables by matching a field value that is common
between the tables. The fields you join on must have similar data types, and you cannot join on
MEMO or OLEOBJECT data types. To build an INNER JOIN statement, use the INNER JOIN
keywords in the FROM clause of a SELECT statement. This example uses the INNER JOIN to
build a result set of all customers who have invoices, in addition to the dates and amounts of
those invoices.

OUTER JOINs

An OUTER JOIN is used to retrieve records from multiple tables while preserving records from
one of the tables, even if there is no matching record in the other table. There are two types of
OUTER JOINs that the Access database engine supports: LEFT OUTER JOINs and RIGHT
OUTER JOINs. Think of two tables that are beside each other, a table on the left and a table on
the right. The LEFT OUTER JOIN selects all rows in the right table that match the relational
comparison criteria, and also selects all rows from the left table, even if no match exists in the
right table. The RIGHT OUTER JOIN is simply the reverse of the LEFT OUTER JOIN; all rows
in the right table are preserved instead.

The Cartesian product

A term that often comes up when discussing joins is the Cartesian product. A Cartesian product is defined
as "all possible combinations of all rows in all tables." For example, if you were to join two tables without
any kind of qualification or join type, you would get a Cartesian product.

This is not a good thing, especially with tables that contain hundreds or thousands of rows. You should
avoid creating Cartesian products by always qualifying your joins.

8. MIDDLEWARE

3-tier architecture pdf file- 13/19 ( sent by aaquib) – istb collection

9. THIN CLIENT

A thin client (sometimes also called a lean, zero or slim client) is a computer or a computer program that
depends heavily on another computer (its server) to fulfill its computational roles. This is different from
the traditional fat client, which is a computer designed to take on these roles by itself. Thin-client
computing is also a way of easily maintaining computational services at a reduced total cost of
ownership. The most common type of modern thin client is a low-end computer terminal which only
provides a graphical user interface – or more recently, in some cases, a web browser – to the end user.

CHARATERISTICS OF THIN CLIENTS:

 Single Point of failure

 Cheap client hardware
 Client Simplicity
 Slow Bitmapped/animated graphics

Thin clients occur as components of a broader computer infrastructure, where many clients share their
computations with the same server. As such, thin client infrastructures can be viewed as providing some
computing service via several user interfaces. This is desirable in contexts where individual fat clients
have much more functionality or power than the infrastructure requires.

10. CLIENT SERVER TECHNOLOGY

Client/ Server technology is a means for separating the functions of an application into two or more distinct
parts. Client/ server describes the relationship between two computer programs in which one program, the
client, makes a service request from another program, the server, which fulfills the request. The client presents
and manipulates data on the desktop computer. The server acts like a mainframe to store and retrieve
protected data. It is network architecture in which each computer or process on the network is either a client or
a server. Servers are powerful computers or processes dedicated to managing disk drives (file servers),
printers (print servers), or network traffic (network servers). Clients are PCs or workstations on which users run
applications. Clients rely on servers for resources, such as files, devices, and even processing power.

Objective
Client - Server Technology

A client/ server model has following three distinct components, each focusing on a specific job:

 Database server
 Client application
 Network.
Database Server
A server (or "back end") manages the resources such as database, efficiently and optimally among various
clients that simultaneously request the server for the same resources. Database server mainly concentrates on
the following tasks.
 Managing a single database of information among many concurrent users.
 Controlling database access and other security requirements.
 Protecting database of information with backup and recovery features.
 Centrally enforcing global data integrity rules across all client applications.
Client Application
A client application (the "front end") is the part of the system that users apply to interact with data. The client
application in a client/ server model focus on the following job:

Presenting an interface between the user and the resource to complete the job Managing presentation logic,
Performing application logic and Validating data entry Managing the request traffic of receiving and sending
information from database server

Network
The third component of a client/ server system is network. The communication software is the vehicles that
transmit data between the clients and the server in client server system. Both the client and the server run
communication software that allows them to talk across the network.

11 & 12. FRONTEND & BACKEND TOOLS

Front-end and back-end are terms used to characterize program interfaces and services relative
to the initial user of these interfaces and services. (The "user" may be a human being or a
program.) A "front-end" application is one that application users interact with directly. A "back-
end" application or program serves indirectly in support of the front-end services, usually by
being closer to the required resource or having the capability to communicate with the
required resource. The back-end application may interact directly with the front-end or,
perhaps more typically, is a program called from an intermediate program that mediates front-
end and back-end activities.
The front end typically includes the HTML, CSS and JavaScript that creates pages, menus,
buttons and everything else that forms the basis of what the user sees in his or her Web
browser. So someone working as a front-end developer would be familiar with code that
focuses on display, and may also have Web design skills with tools like Photoshop.

The back end generally includes a Web server that hosts an application (built with code like
PHP, Python, Ruby on Rails, C/C#/C++ , .NET, or Java), which communicates with a database
(using something like MySQL or Microsoft Access) to serve up the information that the front-
end presents. Back-end developers have expertise in building applications that can efficiently
locate and deliver data. Increasingly, companies are turning to Backend-as-a-Service vendors
who can make this processing faster, particularly for mobile application development.

As an example of how front-end and back-end systems work together, consider a website that
has different content that is accessible to users with different permissions. When a user visits
the website and attempts to access a certain page, he or she will be asked to log in; that login
information will be authenticated via a database lookup, and then the back-end application
communicates with the front end (sometimes via an intermediary program) to display the
proper page to the user.

13. SAN

SAN (storage area network) is a high-speed network of storage devices that also connects those
storage devices with servers. It provides block-level storage that can be accessed by the
applications running on any networked servers. SAN storage devices can include tape libraries
and disk-based devices, like RAID hardware.

SANs are particularly helpful in backup and disaster recovery settings. Within a SAN, data can
be transferred from one storage device to another without interacting with a server. This
speeds up the backup process and eliminates the need to use server CPU cycles for backup.
Also, many SANs utilize Fibre Channel technology or other networking protocols that allow the
networks to span longer distances geographically. That makes it more feasible for companies to
keep their backup data in remote locations.

Utilizing a SAN can also simplify some management tasks, potentially allowing organizations to
hire fewer IT workers or to free up some IT workers for other tasks. It's also possible to boot
servers from a SAN, which can reduce the time and hassles involved in replacing a server.

14. NGOSS

NGOSS (Figure 1) is a comprehensive, integrated framework for developing, procuring, and

deploying operations and business support systems (OSSs/BSSs) and software. It is available as
a toolkit of industry-agreed specifications and guidelines that cover key business and technical
areas including:
• eTOM Business Process Map: An industry-agreed set of integrated business process
descriptions, created with today's customer-centric market in mind, used for mapping and
analyzing operational processes.
• Shared Information/Data (SID) Model: Comprehensive, standardized information definitions
acting as the common language for all data to be used in NGOSS-based applications. A common
information language is the linchpin in creating easy-to-integrate software solutions.
• Technology Neutral Architecture: Key architectural guidelines and specifications to ensure
high levels of flow-through amongst diverse systems and components.
• Compliance and Conformance Criteria: Guidelines and tests to ensure that systems defined
and developed utilizing NGOSS specifications will interoperate.
• Lifecycle and Methodology: Processes and artifacts that allow developers and integrators to
use the toolset to develop NGOSS-based solutions employing a standard approach.

NGOSS presents a number of benefits to the various industry players, such as:
• For service providers
– Facilitate the implementation of cost-effective OSS/BSS solutions through standard
specifications and interfaces
– Provide long-term direction for IT strategy by specifying a business process framework
– Enable IT systems to support rapidly evolving integrated service offerings by offering a logical
system view independent of the particular service or software provider
– Reduce operational costs through tighter coupling of business processes and more
automation
• For OSS software vendors
– Reduce development costs by using a standard framework specification
– Simplify interoperability with other components based on a standard set of interfaces and use
cases
• For systems integrators
– Facilitate predictable, repeatable, and scalable implementation projects by using standard
components
– Enable a broader, multivendor portfolio without a steep learning curve through the use of a
common set of specifications

15. ITIL & ITS BENEFITS

ITIL is a best practice framework that has been drawn from both the public and private sectors
internationally. It describes how IT resources should be organised to deliver business value,
documenting the processes, functions and roles of IT Service Management (ITSM).

ITIL BENEFITS

The top 5 benefits are:

1. ITIL is proven and used worldwide
ITIL defines common concepts and terms within an integrated set of best practices that evolves
to meet market needs in a cycle of continual improvement.
Organizations across the world have demonstrated that they can adapt and adapt ITIL to their
business needs. As ITIL is flexible and scalable, organizations of all shapes and sizes can
implement parts of ITIL to deliver business benefits in stages.
Using ITIL works in practice as its adoption provides individuals and organizations the
confidence for action. A key contributor to ITIL’s success is the associated education, training
and qualification schemes. Delivering service successfully depends on personnel involved in
service management having the appropriate education, training, skills and experience.

2. Improved customer satisfaction and relationships

ITIL is designed to help everyone to focus their attention on the needs of the customers and
user experience rather than focussing too much on the technology issues. Increasing customer
satisfaction leads to a better and trusted relationship.

3. Better reliability and quality of service

By adopting standards that are proven to work, service providers can more easily deliver
services consistently to the agreed service levels, efficiently and effectively. Support teams can
restore service faster, reducing downtime and disruption. Service providers are also more
capable of meeting their service levels, contractual, regulatory and legal compliance
requirements.

4. Optimisation of service delivery across the supply chain

ITIL offers significant opportunities for simplification and standardisation across trading
partners. ITIL provides processes and models to help service providers to work with their
business, customers, users and suppliers to make sound business decisions on investment
opportunities, cost optimisation, management of risks and priorities for improvement. Typical
benefits from implementing ITIL best practices are:
 Reduce support costs by 30%
 Increase incidents fixed at first call by 20%
 Increased value from service portfolio, with reduced cost and risk

5. Competitive advantage through value creation and agile change

By adopting ITIL service lifecycle practices, organizations can focus on delivering value to the
customer and quickly adopt change for the business and IT. Defining and managing the
customer and service portfolios enables successful business transformation and growth with an
increased competitive advantage. Typical benefits include:
 Reduction in cycle time for projects and changes by 30% to 50%
 Increased success rate of change
 Reduction in risk from unplanned and late changes
16. Etom vs. TMN
In 1996, the International Telecommunication Union (ITU) Telecommunication Standardization
Sector (ITU-T) released recommendation M.3010 (further expanded to M.3013), which
introduced the concept of the Telecommunication Management Network (TMN).
Recommendation M.3010 was developed as a framework for service providers to manage their
service delivery networks. It consisted of four management layers at different levels of
abstraction: functional, physical, informational, and logical. The logical level was further
abstracted into four layers: Business Management Layer (BML), Service Management Layer
(SML), Network Management Layer (NML), and Element Management Layer (EML).
In 1997 ITU-T published recommendation M.3400 (Figure 2) extending the TMN framework,
which introduced the concept of fault, configuration, accounting, performance, and security
(FCAPS).
Between 1995 and 1999, the TM Forum developed TOM, which evolved into eTOM. eTOM was
developed between 2000 and 2002 and was also released as ITU-T Recommendation M.3050.
The main differentiator between eTOM and TMN is that the TMN approach was built on the
requirements to manage network equipment and networks (bottom up) while eTOM was built
on the need to support processes of the entire service provider enterprise (top down).
Other related standards and management frameworks have been developed, including IT
Information Library (ITIL ®), Service-Oriented Architecture (SOA), and various enterprise
architecture frameworks (such as Zachman).

17. FOUR RELATED STANDARDS/FRAMEWORKS USED WHILE DEVELOPING OSS/BSS AND

THEIR UTILITY.
1. What is the Business Process Framework? - eTOM

It is a hierarchical catalog of the key business processes required to run a service-focused

business. At the conceptual level, the framework has three major areas, reflecting major
focuses within typical enterprises:

 Strategy, Infrastructure and Product

 Operations
 Enterprise Management

2. What is the Information Framework? - SID

The Information Framework (SID) provides a reference model and common vocabulary for all
the information required to implement Business Process Framework (eTOM) processes. It
reduces complexity in service and system integration, development and design by providing an
off the shelf information model that can be quickly adopted by all parties.
 3. What is the Application Framework?

The Application Framework (TAM) provides a systems map which captures how business
capabilities are implemented in deployable, recognizable applications. The Application
Framework provides a common language for communities who specify, procure, design, and
sell systems, so that they can understand each other’s viewpoints. It provides logical groupings
of applications, then describes each application’s functionality. As a result, it is a practical,
everyday working guide to define and navigate the elements of the complex management
systems landscape.

4. What is the Integration Framework?

The Integration Framework is a set of standards that supports the interoperability between
applications defined in the Application Framework via TM Forum interfaces. The interfaces are
defined in terms of the Information Framework’s entities/attributes, and the requirements for
the interfaces from a business process perspective come from the Business Process Framework.
The interface patterns are standardized ensuring optimal interoperability on implementation.
The Integration Framework acts as the glue that holds together the other Frameworks in an
implementation: This is why the Integration Framework is shown in the middle of the
Frameworx graphic.

18. RENAME OPERATION

In the context of databases, a tuple is one record (one row).

The RENAME operator returns an existing relation under a new name. This is a
Mechanism used for renaming both relations and attributes, this renaming is highly
useful when one has to compare a set of tuples of the same relation with other
tuples of that relation. It has the following general format :

old_name as new-name

19. GROUP BY CLAUSE

 A query command used to combine data based on the value(s) in the field(s) of a table(s).
 Most often used in combination with one or more aggregate functions.
SYNTAX

SELECT expression1, expression2, ... expression_n,

aggregate_function (aggregate_expression)
FROM tables
WHERE conditions
GROUP BY expression1, expression2, ... expression_n;

Parameters or Arguments
expression1, expression2, ... expression_n
Expressions that are not encapsulated within an aggregate function and must be
included in the GROUP BY Clause at the end of the SQL statement.
aggregate_function
This is an aggregate function such as the SUM, COUNT, MIN, MAX,
or AVG functions.
aggregate_expression
This is the column or expression that the aggregate_function will be used on.
tables
The tables that you wish to retrieve records from. There must be at least one table
listed in the FROM clause.
conditions
These are conditions that must be met for the records to be selected.

EXAMPLE - USING SUM FUNCTION

This GROUP BY example uses the SUM function to return the name of the department and
the total sales (for the department).

SELECT department, SUM(sales) AS "Total sales"

FROM order_details
GROUP BY department;

20. SOA APPLICATIONS

Service-Oriented Architecture (SOA) Definition

A service-oriented architecture is essentially a collection of services. These services communicate with

each other. The communication can involve either simple data passing or it could involve two or more
services coordinating some activity. Some means of connecting services to each other is needed.
SOA can be used to solve difficult integration problems among large systems, where you need to define
interfaces, particularly in those going between different organizations or different departments within
an organization, where you need to define the responsibilities and contracts between those parts of the
organizations.

SOA is viable today because there still are so many different ways of doing things within it. The
technologies that fall under the SOA umbrella and the enterprise-service-bus umbrella are so diverse.

21. SID
SID (Shared Information and Data model) is one of the frameworks of the TMForum NGOSS Frameworx
suite. It is also called the Information Framework. SID can be considered as the language of the NGOSS.
It helps us to identify the business entities that play role in the business processes of a
telecommunications service provider.

SID and eTOM goes hand-in-hand and TMForum provides mappings between them. SID Domains are
consistent with the eTOM domains. The Domains include the Level 1 ABEs which are also mapped to
eTOM Level 2 business processes. What an ABE is? Well, it is the abbreviation for Aggregate Business
Entity, which means an entity that can further be decomposed to other sub-entities. (Just like the
decomposition we see in the eTOM hierarchy).

SID Business Entities are modeled in UML diagrams and can be imported to UML tools. (TMForum
publishes them in different importable formats). The framework also comes with an extensive
documentation that explains the structure and the behaviors of the business entities. Typically, you will
find an abbreviation document for each ABE.

Today, OSS application vendors are more NGOSS aware and they try to design/re-design their products
based on NGOSS. In order for two different OSS systems to communicate effectively, their data
structures should be consistent with each other. This way, it will require minimum conversion during the
conversation. OSS/J enables this on the API level but the data structure of the application is also
important. Using SID in designing applications eases the integrations between the different applications.
Explaining your OSS product in SID terms will also be appreciated by your customers and
supplier/partners.

22. THETA JOIN

Join is a special form of cross product of two tables. It is a binary operation thatallows
combining certain selections and a Cartesian product into one operation.
Theta Join: In theta join we apply the condition on input relation(s) and then only those
selected rows are used in the cross product to be merged and included in the output. It means
that in normal cross product all the rows of one relation are mapped/merged with allthe rows
of second relation, but here only selected rows of a relation are made crossproduct with second
relation.

23. DISK DUPLEXING

Disk duplexing is a variation of disk mirroring in which each of multiple storage disks has its own SCSI
controller. Disk mirroring (also known as RAID-1) is the practice of duplicating data in separate volumes
on two hard disks to make storage more fault-tolerant. Mirroring provides data protection in the case of
disk failure, because data is constantly updated to both disks. However, since the separate disks rely
upon a common controller, access to both copies of data is threatened if the controller fails. Disk
duplexing overcomes this problem; the use of redundant controllers enables continued data access as
long as one of the controllers continues to function.

This failover method helps to ensure that data access will continue transparently to the user and allows
technicians to take the server down to replace the defective controller at a more opportune time,
instead of at the moment of failure. The ability to choose when the server comes down can be very
advantageous, because -- in accordance with Murphy's Laws of Information Technology (Law of
Inconvenient Malfunction) -- a device is likely to fail at the least opportune possible moment.
Nevertheless, some experts advocate other systems (such as higher level RAID configurations) that don't
require taking the server down to replace defective hardware.

Another benefit of disk duplexing is increased throughput. Using a technique known as a split seek,
whichever disk can deliver the requested data more quickly responds. Multiple requests may also be
split between the disks for simultaneous processing.

24.
25.

26. KEYS IN DATBASE

Keys are, as their name suggests, a key part of a relational database and a vital part of the structure
of a table. They ensure each record within a table can be uniquely identified by one or a combination
of fields within the table. They help enforce integrity and help identify the relationship between
tables. There are three main types of keys, candidate keys, primary keys and foreign keys. There is
also an alternative key or secondary key that can be used, as the name suggests, as a secondary or
alternative key to the primary key.
Super Key
A Super key is any combination of fields within a table that uniquely identifies each record within
that table.
Candidate Key
A candidate is a subset of a super key. A candidate key is a single field or the least combination of
fields that uniquely identifies each record in the table. The least combination of fields distinguishes a
candidate key from a super key. Every table must have at least one candidate key but at the same
time can have several.
Once your candidate keys have been identified you can now select one to be your primary key
Primary Key
A primary key is a candidate key that is most appropriate to be the main reference key for the table.
As its name suggests, it is the primary key of reference for the table and is used throughout the
database to help establish relationships with other tables. As with any candidate key the primary key
must contain unique values, must never be null and uniquely identify each record in the table.
Foreign Key
A foreign key is generally a primary key from one table that appears as a field in another where the
first table has a relationship to the second. In other words, if we had a table A with a primary key X
that linked to a table B where X was a field in B, then X would be a foreign key in B.
Secondary Key or Alternative Key
A table may have one or more choices for the primary key. Collectively these are known as
candidate keys as discuss earlier. One is selected as the primary key. Those not selected are known
as secondary keys or alternative keys.
Simple Key
Any of the keys described before (ie primary, secondary or foreign) may comprise one or more
fields, for example if firstName and lastName was our key this would be a key of two fields where as
studentId is only one. A simple key consists of a single field to uniquely identify a record.
Compound Key
A compound key consists of more than one field to uniquely identify a record. A compound key is
distinguished from a composite key because each field, which makes up the primary key, is also a
simple key in its own right.
Composite Key
A composite key consists of more than one field to uniquely identify a record. This differs from a
compound key in that one or more of the attributes, which make up the key, are not simple keys in
their own right.

27. DSS

A decision support system (DSS) is a computer-based information system that supports business
or organizational decision-making activities. DSSs serve the management, operations, and
planning levels of an organization (usually mid and higher management) and help people make
decisions about problems that may be rapidly changing and not easily specified in advance—i.e.
Unstructured and Semi-Structured decision problems. Decision support systems can be either
fully computerized, human-powered or a combination of both.

1. DSS tends to be aimed at the less well structured, underspecified problem that upper
level managerstypically face;
2. DSS attempts to combine the use of models or analytic techniques with traditional data
access and retrieval functions;
3. DSS specifically focuses on features which make them easy to use by noncomputer
people in an interactive mode; and

4. DSS emphasizes flexibility and adaptability to accommodate changes in

the environment and the decision making approach of the user.

Three fundamental components of a DSS architecture are:[7][8][12][13][14]

1. the database (or knowledge base),

2. the model (i.e., the decision context and user criteria), and ㄹ자ㅐ
3. the user interface.

ㅇ The users themselves are also important components of the architecture.

28. MIS IN TELECOM
The term of management information systems consists of three parts, to understand the
meaning of this term must understand what the meaning of management, information, and
systems. It is better to understand each part of the term.
Management is to achieve organizational goals efficiently and effectively through planning,
organizing, directing and controlling organizational resources, it's ability to achieve the goals by
others
Data is raw unprocessed facts and figures that have no context or purposeful meaning and
information is processed data that has meaning and is presented in a context.
A system is a set of interrelated components, with a clearly defined boundary, working together
to achieve a common set of objectives by accepting inputs and producing outputs in an
organized transformation process.
In the telecommunication companies in Yemen, management information systems enable to
compilation, processing and storage of the information; with overall purpose to make that
information available on demand in the required format. Communications companies used
modern computers and advanced servers connected to an advanced network, this network
connects all network communications centers to each other. The system is connected to the
main server so that the data is stored and files on a central server. So it is easy to retrieve data
when needed. The telecommunication companies develop the systems and network and
provide technical support by specialists and experienced in this field. In addition provide
specialized training programs for their employees to help them to use the management
information systems. Telecom Companies can’t work without management information
systems as the number of participants in these companies more than million subscribers, so it’s
hard to save their data using the manual method (using files).As we know that telecom
companies are saving the subscriber data (name, card number, etc.) in a database where the
subscriber can go to any branch in any city to inquire. Management information systems
assisted in automating tasks. Automation can save time, money, resources, reduce employee’s
staff, and enhance organizational workflow. In addition assist in increased organization
productivity, effectiveness, increase customer satisfaction, and efficiency of the work.
Management information systems play a key role in the life of organizations; it provides the
appropriate information in right time as needed to support the management activities.