Service Portfolio Management in .NET Maker GS1-13 in .NET Service Portfolio Management

How to generate, print barcode using .NET, Java sdk library control with example project source code free download:
3. use visual .net ean/ucc-13 printing toproduce ean/ucc-13 with .net Web app Have operational reports b EAN13 for .NET een defined for all service consumers and service providers Have all records in the service repository and other metadata repositories (for example, configuration management database) been updated for the service consumers and service providers Have all service contracts been finalized . Service Portfolio Management A consistent theme through .NET European Article Number 13 out this chapter has been raising the awareness of project teams to other services and consumers in the enterprise. While there"s a certain amount of improvement that can happen simply through word of mouth, in general, that approach is not sustainable.

For example, in the past, there were efforts to raise awareness of applications and their database dependencies. One or two select people may have had knowledge of 80% of the applications associated with one database based upon their experiences, when we expand this out to all applications and all databases the problem quickly becomes unmanageable, with no single person having the complete view. As a result, many organizations are now undertaking application portfolio management efforts simply to get their arms around the problem.

In contrast, we are in the early stages of SOA adoption and can prevent the same situation from occurring in the context of services. To do this, an organization should practice service portfolio management. The portfolio is always changing, with new services and their consumers being generated, while older services or consumers may be decommissioned.

While it is certainly possible that a small organization can manage this effectively through the use of nothing more than an Excel spreadsheet, larger organizations can optimize their efforts through the use of a Service Registry/Repository.. The Service Registry/Repository The Service Registry/Repos visual .net EAN-13 Supplement 2 itory is one of two tools most frequently associated with SOA governance. Keep in mind that governance, first and foremost, is about people, policies, and processes.

You cannot buy governance. You can, however, buy tools that can make your governance efforts more efficient, and the Service Registry/ Repository definitely falls into that area..

[ 67 ]. Avoiding a Bunch of Services Most companies that are ad opting SOA include reuse as part of their desired behaviors. In order to be reused, consumers of those services must be aware of their existence. If they don"t know that a service is available, they"re going to build or buy their own, creating redundant solutions.

While the processes that have been described in this chapter are intended to raise awareness of what services exist, individual members of the governance teams, whether a Center of Excellence or existing organizations, cannot be expected to know about every single service that exists, especially as the portfolio of services grows over time. Imagine going to a library where there is no card catalog (or these days, a computer-based directory), only librarians. While the librarians will probably have a better knowledge of the books in the library in comparison to anyone else, any individual librarian will only be aware of a fraction of the books available.

Now, while the typical enterprise won"t have as many services as a library has books, the amount of tribal knowledge is rampant. Most project documentation is exactly that project documentation. When the project ends, the value of the documentation does as well.

The only information that is retained is what is in the minds of the project staff. With SOA, the opportunity now exists to do this right from the beginning, and that starts with creating and preserving information about the service as early as possible. Recall that at the analysis checkpoint, the project team should be forming an idea of the services needed for the solution, and at the architectural checkpoint, the project team should have a clear idea of the services necessary.

Additionally, the project team should know which of those services already exist. They can identify so by querying the registry/repository. At the same time, all of the services that aren"t in the registry/repository need to be entered.

The time to enter new services is when they are first identified. The reason for this is that there are always multiple projects occurring simultaneously. This creates a risk that there are two (or more) projects that will need the same service.

If projects wait to enter a service in the registry/ repository until it has been built and deployed into production, another project may be well into their own implementation of the exact same service before there"s ever any record of its existence. Initially, it may seem that the only role for the registry/repository in the space of design-time governance is as a human facing catalog to allow project teams to identify services that already exist, and publish the services that they create. However, it does go beyond this.

First, awareness is only part of the equation. As shown in the example in this chapter, if there is no one responsible for the service after it goes into production, not just for making sure it continues to run properly, but to manage the interest that other consumers may have, the organization will have problems. The registry/repository plays a key role in managing the aspects of the consumer/provider relationship, from allowing a consumer to find the proper person to talk to, to allowing a provider to notify all consumers of a service of upcoming changes.

. [ 68 ].
Copyright © . All rights reserved.