Sign In

Graham Berrisford

CEO Avancier Limited

Graham Berrisford is a highly respected figure in the enterprise and solution architecture training industry, with a reputation for providing top-quality training that is continuously refined to meet the evolving needs of IT functions.

With over 25 years of experience, Graham has worked with a diverse range of clients in the public sector, utility companies, consultancies, CASE tool vendors, and global systems integrators, showcasing his expertise as a manager, consultant, analyst, and architect.

He possesses a unique blend of technical prowess and people management skills, enabling him to mentor, manage, and influence individuals effectively. Graham's innovative solutions have set industry standards and have been emulated by others, demonstrating his forward-thinking approach.

His management skills span across various areas such as review and assurance, strategic leadership, change management, quality management, knowledge management, and global liaison, showcasing his versatility and ability to navigate complex organizational landscapes.

In terms of consulting skills, Graham excels in analysis, architecture, process/practice improvement, communication, and training, having successfully mentored numerous professionals to enhance their architectural capabilities.

He is recognized for his exceptional reputation within the field, with testimonials praising his wealth of knowledge and consistent delivery of value across all levels, from juniors to principal consultants.

Graham Berrisford's educational background includes a BSc in Psychology from the University of Leeds and a previous academic stint at the Royal Grammar School in Newcastle-upon-Tyne.

Throughout his career, Graham has held significant roles at various organizations, including serving as the former CEO of Enterprise & Solution Architecture Training & Consulting at Avancier Limited, Manager and Consultant at Atos Origin, and Best Practice Manager at Sema, among others.

For more information about Graham Berrisford, visit his 'About me' page at http://grahamberrisford.com

Highlights

Jul 22 · linkedin

SERVICE ORIENTATION IN BUSINESS ARCHITECTURE

"Service-orientation: viewing an enterprise, system, or building block in terms of services provided and consumed." (TOGAF).

The “Open Agile Architecture“ standard from The Open Group defines "service" has having two meanings. One definition is "An encapsulated component that delivers outcomes through well-defined interfaces.”

This article favors the other definition: “An act performed for the benefit of another." Such a service may deliver information or materials, or make a product or facility available for a period of time.

SERVICE CONTRACTS

The parties who request and/or consume business services include not only customers (who pay for services provided), but also prospects (who make enquries, but may never become customers), suppliers (who invoice us for services we consume), legislators (who request evidence of compliance), and others.

The general principle is to define a service from the outside, in terms of what it requires and delivers, rather than the activities, actors and resources needed to complete it. For example, the services provided by a butler to a gentleman may include: -- Iron shirt - triggered by a request, delivers a creaseless shirt. -- Make breakfast - triggered by a time event (08.00 hours), delivers food. -- Polish shoes - triggered by a state change event (shoes dirty), delivers shiny shoes.

The act of delivering polished shoes is definable in a service contract that includes some or all of the following information: -- trigger (a request, time event or system state change), -- entry conditions (inputs and preconditions), -- exit conditions (outputs and post conditions, results or effects) -- non-functional qualities (speed, throughput, availability, price, etc.). You might add the value delivered by a service - whatever you mean by that.

This service contract makes no reference to the process and resources needed to complete the service. Moreover, it does not mention the service provider or consumer.

Note: a service-level agreement (SLA) document is a different kind of contract (between identified parties) that usually covers several or many discrete services of the kind discussed above, which may be named but not defined in detail.

SERVICE PARTICIPANTS

A service contract may be defined independently of the parties accountable for requesting, providing or consuming the service, and completed in various ways. For example, the delivery of a pizza in response to an order may be distributed between actors, who may each invoke services from other parties.

Service providers may compete to be the fastest, cheapest or best. Business directors can select from alternative business service providers, and govern them against an SLA document that defines services without constraining how service providers work. (Having said that, constraints on how they work can be specified service contracts.)" https://lnkd.in/g-xk2Tcb

Apr 13 · linkedin

Service-oriented EA

"In structured analysis approaches of the 1980s, Business Functions, Applications and Technologies were seen as active or dynamic components in a network of components that interact by sending and receiving data flows (each containing a message, file or other kind of data structure), to produce desired effects (state changes and outputs).

The term interface was used for a data flow exchanged between sender and receiver components.

In object-oriented approaches of the 1990s, Business Functions, Applications and Technologies were seen as interacting in network of objects that provide and require methods or operations - each being an act performed for another.

The term interface was now used for a declaration of operations that an object provides, or requires, here called services.

Not all object-oriented software architecture principles scale up to enterprise architecture, but still, TOGAF v10 takes a service-oriented approach, defining service-orientation as "viewing an enterprise, system, or building block in terms of services provided and consumed."

TOGAF uses the term interface ambiguously, for a data flow, and for a service portfolio, defined as "a collection of services [or] interface definition [used] to define the requirement for a building block or system."

ArchiMate defines a service as the external view of a unit of behavior. The contract for a service encapsulates (hides) the particular activities and resources needed to deliver it. So, a service can be completed in different ways, by different providers, who might compete to be the fastest, cheapest or best in some other way."

https://lnkd.in/g-xk2Tcb

Graham Berrisford
Add to my network

Location

Kingston upon Thames, United Kingdom