RiVidium -- The Missing Element in Technology


Enterprise Architecture Development


RiVidium is a thought leader in Service-Oriented architecture (SOA). SOA is an architectural style that formally separates services, which are the functionality that a system can provide, from service consumers, which are systems that need that functionality. This separation is accomplished by a mechanism known as a service contract, coupled with a mechanism for providers to publish contracts and consumers to locate the contracts that provide the service that they desire. Rather than coupling the consumer with the service in terms of technical aspects of invoking the service, SOA separates the contract from the component or implementation of that contract. This separation produces an architecture in which the coupling between the consumer of the service and the modules that produce the work is extremely loose and easily reconfigured.	Benefits • Decreased application development costs • Decreased maintenance costs • Increased corporate agility • Increasing overall reliability by producing systems that are more resistant to application and equipment failure and disruption. • Providing an application upgrade path that is considerably cheaper and less disruptive than the total application replacement that is the norm using monolithic applications.
RiVidium is a master in transitioning legacy systems to SOA through our three engines: GovernanceEngine, ArchitectureEngine and SOA Engine. We can decouple functionalities from legacy and client/server applications by encapsulating their functionality in objects and publishing those objects to a baseline or to-be architecture. These are just some of the steps in the RiVidium process. SOA can be of enormous benefit to an organization's To-Be-Enterprise. It provides an important new avenue for integration of applications. Creating new applications under an SOA offers a significant increase in the qualities of availability, interoperability, maintainability, and reliability for those applications. For the enterprise as a whole, the SOA translates into lower operating costs, lower development costs, higher quality, and greater corporate agility. SOA benefits flow primarily from breaking applications into modules with a well-defined interface contract that leads to very loose coupling between services and applications. Loose coupling between consumer and provider benefits the consumer because consumer applications are effectively protected from changes in service provider implementations and the consumer has a greater choice of providers. It benefits the provider because from an implementation of loosely coupled systems come applications that map much more closely to the business processes that represent a company's value proposition. In addition, these applications increase the enterprises' competitiveness because they are easier to modify to satisfy changing business conditions. In addition, applications and work processes assembled using an SOA are cheaper to maintain. Organizations that adopt a service-oriented philosophy of development will be able to handle change more quickly and cheaply. SOA can provide a major increase in the value of the data and application resources of a company by enabling a major new mode of integration of these assets. RiVidium's approach to architecture development is also based on the result of a set of business and technical decisions. We believe there are many influences at work in architectures design, and the realization of these influences will change depending on the environment in which the architecture is required to perform. In any architecture development effort, the requirements make explicit some—but only some—of the desired properties of the final system. Not all requirements are concerned directly with those properties; a development process or the use of a particular tool may be mandated by them. But the requirements specification only begins to tell the story. Failure to satisfy other constraints may render the system just as problematic as if it functioned poorly. Understanding these key issues is just as important as creating the artifacts to get the architecture to a functional state. RiVidium understands these issues and more when building enterprise architecture.
RiVidium's approach to successful enterprise architecture development focuses on the stakeholder. These stakeholders can be: the customer, the end users, the developers, the project manager, the maintainers, and even those who market the system. In our approach we understand the stakeholders has different concerns that they wish the system to guarantee or optimize, including things as diverse as providing a certain behavior at runtime, performing well on a particular piece of hardware, being easy to customize, achieving short time to market or low cost of development. In our approach we can help stakeholders with: How organizational goals influence requirements and development strategy How requirements lead to an architecture How architectures are analyzed How architectures yield systems that suggest new organizational capabilities and requirements


	Company		Services		Solutions
	About RiVidium		Enterprise Architecture Development		RiVidium Framework
	Corporate Governance		Enterprise Data Strategy		GovernanceEngine™
	Careers		Portfolio Management (Governance)		ArchitectureEngine™
	Partners		Software Engineering		SOAEngine™
	WhitePapers		Systems Engineering		DataStrategyEngine™
	Contact Us		Systems Integration		BiometricsEngine™
					IdentityManagementEngine™
					Bricks & Patterns

RiVidium, Inc. Copyright 2009 | Privacy Policy