Saturday, February 23, 2008

IT Glossary

This previous business and IT glossary comprises some terms often mentioned by the market and literature. Some of them are not yet standardized.

Any comments and insertions are very welcome:

IT Service (ITIL Vision)

A service provided to one or more customers by an IT Service Provider. An IT Service is based on the use of information Technology and supports the customer´s businesses processes. An IT Service is made up from a combination of people, processes and technology and should be defined in a Service Level Agreement (SLA)

Agility

A system is also adaptative to unexpected changes.

F. Becker / Vokurka and Flidner cited in (Schelp & Winter, 2007)

Is the successful exploration of competitive bases (speed, flexibility, innovation proactivity, quality and profitability) through the integration of reconfigurable resources and best practices in a knowledgerich environment to provide customer-driven products and services in a fast changing market environment”

Yusuf Cited in (Schelp & Winter, 2007)

Flexibility

A system is able to adapt to expected changes.

F. Becker / Vokurka and Flidner cited in (Schelp & Winter, 2007)

Architecture

fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution” ANSI/IESS Std 1471-200

Enterprise

collection of organizations that has a common set of goals and/or a single bottom line. In that sense, an enterprise can be a government agency, a whole corporation, a division of a corporation, a single department, or a chain of geographically distant organizations linked together by common ownership.The term "enterprise" in the context of "enterprise architecture" can be used to denote both an entire enterprise, encompassing all of its information systems, and a specific domain within the enterprise. In both cases, the architecture crosses multiple systems, and multiple functional groups within the enterprise.Confusion also arises from the evolving nature of the term "enterprise". An extended enterprise nowadays frequently includes partners, suppliers, and customers. If the goal is to integrate an extended enterprise, then the enterprise comprises the partners, suppliers, and customers, as well as internal business units. (Opengroup, 2003)

Enterprise Architecture

the fundamental organization of a government agency or a corporation, either as a whole, or together with partners, suppliers and / or customers (“extended enterprise”), or in part (e.g. a division,a department, etc.) as well as the principles governing its design and evolution. (Schelp & Winter, 2007)

Business Model

High level definition: the representation of an organization´s business processes. (Kontogiannis et al., 2007)

SOA Governance

Involves defining the organizational issues, the governance processes,metrics and procedures, and the necessary SOA policies (business, security, conformance, performance, technical, organizational) required to manage services and the SOA infrastructure throughout the SOA lifecyle (service design, development, pubslishing, invocation and monitoring). In addition, SOA GOV Model establishes behavioral rules and guidelines of the organization and all SOA community (architect, deirectors, business, developers, users) defined by SOA Policies. (Marks & Bell, 2006)

Service Model

The representation of an organization´s existing services and how they relate to the business processes in the business model. SOA as an IT architectural strategy actually uses services as the “operating system” for the business and its business processes. (Kontogiannis et al., 2007)

Service-Oriented Business

An organization that has progressed with its SOA efforts such that its business really does operate using an SOA. (Marks & Bell, 2006)

Service-Oriented Systems (Business Perspective)

A way of exposing legacy functionality to remote clients, implementing new business processes models by utilizing existing or third-party software assets, reducing the overall IT expenditures while potentially increase the potential for innovation through software investments. (Bieberstein, Bose, Fiammante, Jones, & Shah, 2006)

Service-Oriented Systems (Technical Perspective)

An approach to software development where services provide reusable functionality with well-defined interfaces; A service infrastructure enables discovery, composition and invocation of services; and applications are built using functionality from available services. (Bieberstein, Bose, Fiammante, Jones, & Shah, 2006)

SOA

Conceptual business architecture where business functionality, or application logic, is made available to SOA users, or consumers, as shared, reusable services on an IT network. (Marks & Bell, 2006)


Service Oriented Enterprise (SOE)

From a systems and IT perspective, SOE is a model for architecting software and IT infrastructure. It works in concert with current platform architectures as well as enables business process-driven architectures. From a business perspective, the concept of SOE should also cover the componentization of business functions into services whose re-composition using business processes will result in various business functions. (Huang, 2005)


Services

Modules of business or application functionality with exposed interfaces, and are invoked by messages. (Marks & Bell, 2006)

Service Orchestration

Combination of services at run-time (Schelp & Winter, 2007)

Service Composition

Combination of Services at build-time (Schelp & Winter, 2007)

Referências:

Bieberstein, N., Bose, S., Fiammante, M., Jones, K., & Shah, R. (2006). Service Oriented Architecture Compass - Business Value, Planning and Enterprise Roadmap. Upper Saddle River: Pearson.

Huang, Y., Kumaran, S., & Chung, J.-Y. (2005). A model-driven framework for enterprise service management. Information Systems and E-Business Management, 2(3), 202-217.

Kontogiannis, K., Lewis, G. A., Smith, D. B., Litoiu, M., Müller, H., Schuster, S., et al. (2007). The Landscape of Service-Oriented Systems: A Research Perspective. Paper presented at the International Workshop on Systems Development in SOA Environments (SDSOA'07).

Marks, E., & Bell, M. (2006). Service-Oriented Architecture (SOA): A Planning and Implementation Guide for Business and Technology. New Jersey: John Wiley & Sons, Inc.

Opengroup. (2003). TOGAF Enterprise Edition Version 8.1. Retrieved 20/02/2008, 2008, from http://www.opengroup.org/architecture/togaf8-doc/arch/

Schelp, J., & Winter, R. (2007). Towards a Methodology for Service Construction. Paper presented at the 40th Hawaii International Conference on System Sciences, Hawaii.

Enterprise Architecture 1st View

Provavelmente Enterprise Architecture (EA) seja um dos termos mais mencionados no mundo da TI nos últimos dois anos que apresenta menor nivel de certeza sobre o seu real significado e abrangência. As práticas empresariais e a comunidade científica, no entanto, categoricamente afirmam sua importância como elemento fundamental para alcançar flexibilidade nos sistemas de informação e agilidade para promover mudanças inesperadas em processos de negócios, o que é essencial para dinamizar novos modelos de negócios em organizações. Tema quente, polêmico e de suma importância.

Antes de mencionar nas próximas postagens algumas referências sólidas sobre EA como o tradicional Zachman e os 15 anos que cercam a evolução do TOGAF pelo Open Group , menciono um conceito mais amplo sugerido por (Winter & Fischer, 2006) que trata o assunto numa visão corporativa mais integrada, ao invés de tratar como arquitetura de Sistemas de Informação (ASI) unicamente:

" the fundamental organization of a government agency or a corporation, either as a whole, or together with partners, suppliers and / or customers (“extended enterprise”), or in part (e.g. a division,a department, etc.) as well as the principles governing its design and evolution."

O conceito é amplamento aceito, mas a diferença entre os diversos modelos está no conteúdo e relação entre as suas diversas arquiteturas. Segundo o modelo dos professores da University of St Gallen, EA pode ser mapeado em cinco camadas hierárquicas, mutuamente dependentes com actividades verticais entre elas: Business Architecture, Process Architecture, Integration Architecture, Software Architecture e Technology Architecture.

Só para antecipar, TOGAF por exemplo, considera que EA é composto por 4 camadas arquitecturais: Business, Data, Application e Technology, sendo a Arquitectura de Sistemas de Informação resultado da combinação das camadas de dados e aplicação. (Opengroup, 2003)

Referências:

Winter, R., & Fischer, R. (2006, October 17 2006). Essential Layers, Artifacts, and Dependencies of Enterprise Architecture. Paper presented at the EDOC Workshop on Trends in Enterprise Architecture Research (TEAR 2006), Hong Kong.

Opengroup. (2003). TOGAF Enterprise Edition Version 8.1. Retrieved 20/02/2008, 2008, from http://www.opengroup.org/architecture/togaf8-doc/arch/