Richard Veryard

Richard Veryard (born 1955) is a British computer scientist, author and business consultant, known for his work on service-oriented architecture and the service-based business.[1]

Biography

Veryard attended Sevenoaks School from 1966 to 1972, where he attended classes by Gerd Sommerhoff. He received his MA Mathematics and Philosophy from Merton College, Oxford, in 1976, and his MSc Computing Science at the Imperial College London in 1977. Later he also received his MBA from the Open University in 1992.[2]

Veryard started his career in industry working for Data Logic Limited, Middlesex, UK, where he first developed and taught public data analysis courses. After years of practical experience in this field, he wrote his first book about this topic in 1984. In 1987 he became an IT consultant with James Martin Associates (JMA), specializing in the practical problems of planning and implementing information systems. After the European operation of JMA were acquired by the Texas Instruments, he became a Principal Consultant in the Software Business and a member of Group Technical Staff. At Texas Instruments he was one of the developers of IE\Q, a proprietary methodology for software quality management.[3] Since 1997 he is freelance consultant under the flag of Veryard Projects Ltd. Since 2006 he is a principal consultant at CBDi, a research forum for service-oriented architecture and engineering.[2]

Veryard has taught courses at City University, Brunel University and the Copenhagen Business School, and is a Fellow of the Royal Society of Arts in London.[2]

Work

Pragmatic data analysis, 1984

In "Pragmatic data analysis" (1984) Veryard presented data analysis as a branch of systems analysis, which shared the same principles. His position on data modelling would appear to be implicit in the term data analysis.[4] He presented two philosophical attitudes towards data modeling, which he called "semantic relativism and semantic absolutism. According to the absolutist way of thinking, there is only one correct or ideal way of modeling anything: each object in the real world must be represented by a particular construct. Semantic relativism, on the other hand, believe that most things in the real world can be modeled in many different ways, using basic constructs".[5][6]

Veryard further examined the problem of the discovery of classes and objects. This may proceed from a number of different models, that capture the requirements of the problem domain. Abbott (1983) proposed that each search starts from a textual description of the problem. Ward (1989) and Seidewitz and Stark (1986) suggested starting from the products of structured analysis, namely data flow diagrams. Veryard examined the same problem from the perspective of data modeling.[7]

Veryard made the point, that the modeler has some choice in whether to use an entity, relationship or attribute to represent a given universe of discourse (UoD) concept.[8] This justifies a common position, that "data models of the same UoD may differ, but the differences are the result of shortcomings in the data modeling language. The argument is that data modeling is essentially descriptive, but that current data modeling languages allow some choice in how the description is documented."[8]

Economics of Information Systems and Software, 1991

In the 1991 book "The Economics of Information Systems and Software", edited by Veryard, experts from various areas, including business administration, project management, software engineering and economics, contribute their expertise concerning the economics of systems software, including evaluation of benefits, types of information and project costs and management.[9]

Information Coordination, 1993

In the 1993 book "Information Coordination: The Management of Information Models, Systems, and Organizations" Veryard gives a snapshot of the state of the art around these subjects. "Maximizing the value of corporate data depends upon being able to manage information models both within and between businesses. A centralized information model is not appropriate for many organizations," Veryard explains.[10]

His book "takes the approach that multiple information models exist and the differences and links between them have to be managed. Coordination is currently an area of both intensive theoretical speculation and of practical research and development. Information Coordination explains practical guidelines for information management, both from on-going research and from recent field experience with CASE tools and methods".[10][11]

Enterprise Modelling Methodology

In the 1990s Veryard worked together in an Enterprise Computing Project and developed a version of Business Relationship Modelling specifically for Open Distributed Processing, under the name Enterprise Modelling Methodology/Open Distributed Processing (EMM/ODP).[12][13] EMM/ODP proposed some new techniques and method extensions for enterprise modelling for distributed systems.

Component-based business

In 2001 Veryard introduced the concept of "component-based business". Component-based business relates to new business architectures, in which "an enterprise is configured as a dynamic network of components providing business services to one another".[14] In the new millennium there has been "a phenomenal growth in this kind of new autonomous business services, fuelled largely by the internet and e-business".[14]

The concept of "component-Based Business constitutes a radical challenge to traditional notions of strategy, planning, requirements, quality and change, and tries to help you improve how you think through the practical difficulties and opportunities of the component-based business". This applied to both hardware and software, and to business relationships.[14]

Veryard's subsequent work on organic planning for SOA has been referenced by a number of authors.[15]

Six Viewpoints of Business Architecture, 2013

In "Six Viewpoints of Business Architecture" Veryard describes business architecture as "a practice (or collection of practices) associated with business performance, strategy and structure."[16]

And furthermore about the main task of the business architect:

The business architect is expected to take responsibility for some set of stakeholder concerns, in collaboration with a number of related business and architectural roles, including
• business strategy planning, business change management, business analysis, etc.
• business operations, business excellence, etc.
• enterprise architecture, solution architecture, data/process architecture, systems architecture, etc.
Conventional accounts of business architecture are often framed within a particular agenda - especially an IT-driven agenda. Many enterprise architecture frameworks follow this agenda, and this affects how they describe business architecture and its relationship with other architectures (such as IT systems architecture). Indeed, business architecture is often seen as little more than a precursor to system architecture - an attempt to derive systems requirements.[16]

Publications

Articles, papers, book chapters, etc., a selection:[17]

References

  1. ↑ Richard Veryard Accessed 17 Dec 2008.
  2. 1 2 3 Richard Veryard Principal Consultant at CBDI. Accessed 17 Dec 2008.
  3. ↑ Sandro Bologna, Giacomo Bucci (ed.) (1996) Achieving Quality in Software: Proceedings of the Third International Conference on Achieving Quality in Software. Chapman & Hall. p.425.
  4. ↑ Graeme Simsion (2001). Data Modeling. p.26.
  5. ↑ Richard Veryard (1984). Pragmatic data analysis. Oxford : Blackwell Scientific Publications. p.7
  6. ↑ Mehdi Khosrowpour (1999) (ed.). Managing Information Technology Resources in Organizations in the Next Millennium. Page 30.
  7. ↑ Grady Booch (1991). Object Oriented Design with Applications: with applications. Benjamin/Cummings Pub. Co., 1991. p.151.
  8. 1 2 Graeme Simsion (2007) Data Modeling: Theory and Practice. p. 78.
  9. ↑ Richard Veryard (1991). The Economics of Information Systems and Software. Butterworth-Heinemann.
  10. 1 2 Richard Veryard (1993). Information Coordination: The Management of Information Models, Systems, and Organizations. Prentice Hall.
  11. ↑ Ayers, Michael (January 1996). "Critical review of Information Coordination". ACM SIGSOFT Software Engineering Notes 21 (1). Retrieved 11 June 2010.
  12. ↑ Richard Veryard and Ian G. MacDonald (1994). "EMM/ODP: A methodology for federated and distributed systems". In: Methods and Associated Tools for the Information Systems Life Cycle, Proceedings of the IFIP WG8.1 Working Conference on Methods and Associated Tools for the Information Systems Life Cycle, Maastricht, The Netherlands, 26–28 September 1994. Alex A. Verrijn-Stuart and T. William Olle (ed.) Elsevier IFIP Transactions. pp.241-273.
  13. ↑ Business relationship modelling Veryard Projects. Accessed 16 dec 2008.
  14. 1 2 3 Richard Veryard (2001). Component-based Business: Plug and Play. Springer.
  15. ↑ Michael Bell, SOA Modeling Patterns for Service-Oriented Discovery and Analysis (Wiley 2010); Tony Bidgood, ArchiMate: A Standard for Enterprise System Modelling (CBDI Journal, August 2008); Marc Lankhorst et al, Enterprise Architecture at Work (Springer, 2005)
  16. 1 2 Veryard (2013, p. i)
  17. ↑ Richard Veryard List of publications from the DBLP Bibliography Server.

External links

This article is issued from Wikipedia - version of the Wednesday, January 13, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.