Page 451 - Handbook of Modern Telecommunications

3-242 CRC Handbook of Modern Telecommunications, Second Edition

TABl E 3.10.1 HP Global Methodology for IT Systems Architecture: Four Fundamental Views
View Primary stakeholders Content
Business Business manager Why are we doing this?
System acquirer What are the internal and external drivers?
Business analyst What are the business models and processes?
Who participates in the business processes?
What are the project goals?
How will the success of the solution be measured?
Functional System users What should the solution do?
Business process designers What will the completed solution do?
Information modelers How will it be used and what services will it provide?
What information will it provide? To whom?
What qualities must the solution have?
Technical System developers How should the solution work?
Technical consultants How will the system be structured and constructed?
Subsystem suppliers What are the interfaces and other constraints?
What applications and data are needed?
What does the infrastructure look like?
What standards will apply?
How will the system qualities be achieved?
Implementation Project managers With what will the solution be built?
System developers What specific products and components, from which vendors, are needed
System testers to build the system?
System deployers How will the system be developed and deployed?
Operators/Managers What validation methods will be used?
How will it be managed?
What is the source of funding?

We will use these concepts and views to describe the HP view of an OSS. First, we take a brief look
at the business drivers for a new approach to OSS—answering the why questions about the system. We
then look at the job of the OSS—what it needs to do, both from the business processes it needs to sup-
port and the functionality it needs to deliver. The section on how to build an OSS describes the technical
approaches that are needed to support the required functionality. Finally, since the details of a technol-
ogy change quickly, rather than looking at the components needed to build an OSS, we look at some of
the considerations that should be taken into account when specifying the implementation view.

3.10.3 Business Drivers Require a New Approach to OSS
The first thing we want to understand is the business view: why do we need an OSS, and more impor-
tantly, why can’t we just keep the OSS approaches and implementations that have served us so well for
so many years?

3.10.3.1 Convergence
The industry is undergoing massive changes that can best be categorized as a multifaceted convergence.
Convergence is happening across business, customer, service, infrastructure, and other dimensions,
each of which has implications for the service provider business and the how the OSS needs to support
these changes.

• Traditional telecommunications network architectures consisted of multiple networks, some-
times interconnected or dependent on each other, but mostly autonomous. Through network
convergence, these multiple separate networks are converging on a single IP/MPLS network that
supports multiple access methods. Interestingly, this sometimes results in customer circuits being
provisioned through nondeterministic packed-switched networks. Not only does the OSS need to