Edwin E. Tozer

Last updated

Edwin Ellis (Ed) Tozer (born 1943) is a British retired management and IT consultant and SF author, [1] particularly known for his early work on business information systems in the 1970s and 1980s. [2] [3]

Contents

Life and work

Tozer started his career in the manufacturing and mining industry. [4] In 1969 he became junior systems analyst at the management consultancy firm Scicon in London; a subsidiary of British Petroleum, originally known as Scientific Control Systems, chaired by Sir Maurice Kendall. After spells with other consulting firms, he worked with James Martin's European operation from 1982 to 1984.

In 1984 he founded Edwin E. Tozer Limited, specialized in data management study, which he dissolved after his retirement in 2008. [5] In 1984 he published his first book, entitled "Application Development Tools." in 1988 his second book, "Planning for effective business Information systems," and in 1996 his third book, entitled "Strategic Is/It Planning."

Since his retirement in the new millennium he has been writing SF literature. [1]

Work

In the 1970s Tozer became involved in the CODASYL development of database languages, and wrote his first articles on databases and systems analysis and design [6] He specialized in "effective application of Information Technology to business and administrative problems." [4] [7]

Database Systems Analysis and Design, 1976

In the 1976 article "Database Systems Analysis and Design," Tozer made a comparison between the database field and the evolving field of the Programming technology. He argued:

Developments in the database field have tended to emphasise programming technology, with a dearth of accompanying progress in systems analysis and design methods. This paper puts forward an overall view of system design which is intended to act as a constraining framework. It is based upon a pragmatic approach and is presented in a form which could be (and is being) used on large scale implementation projects. [8]

And furthermore:

Orderly analysis and design procedures are encouraged. The taking of premature design decisions is discouraged, especially through the recognition of three distinct views of data: conceptual, implementation and storage, and through recognition of distinctions between design of each of these, specification of mappings between them, and design of programs and run sequences. It is envisaged that specific procedures developed elsewhere (see references) could be incorporated into the methodology described here. [8]

Developing strategies for management information systems, 1986

In the 1989 article "Developing strategies for management information systems," Tozer presented a model for developing information systems. Tozer's approach was based on his experience of "planning projects in a variety of industries, including wholesale and retail banking, consumer credit, chemicals, Multinational manufacturing and distribution and the oil industry." [9] Tozer presented a model, which consisted of the following four phases:

  • Phase 1: Determine business information needs: This results from the analysis of a series of senior management interviews which are conducted according to a predefined format. The analysis goes through the stages of functional objectives, critical success factors, control information and other quantitative means for determining the successful achievement of critical success factors, leading to a definition of specific information needs.
  • Phase 2: Development of conceptual architecture for systems and data: This phase produces clear architecture statements for application systems and associated conceptual database...
  • Phase 3: Determine key priorities and system groupings...
  • Phase 4: Migration plane. The final sets of deliverables are the plans for achieving the business and technical systems as outlined in these architectures... [10]

The key features of this model, according to Azad (1990) were:

  1. [ït] starts with business planning process dealing with logical links and dependencies on corporate and divisional plans.
  2. Is pragmatic and hence practical.
  3. Combines formality and business expediency.
  4. Takes account of trends in business and information planning.
  5. Encourages the active use of up to date approach in the development if information systems utilising the fourth generation language by the user.
  6. Follows through into the development of a complete, practical, business orientated information system dealing with what must be done, how long it takes, and how much it is going to cost.
  7. Is open with regard to extension and enhancement.
  8. Has been used successfully in major corporations, continues to be used and hence is continuing to develop further. [10]

In this 1986 paper Tozer was one of the first to propose the concept of business architecture in the field of business information systems planning.

Planning for effective business Information systems, 1988

In his 1988 Planning for effective business Information systems, Tozer developed a particular view on Enterprise Data Planning, that dealt with the complexities of extracting key business needs from senior management and then defining relevant architectural visions for the specific enterprise.

In the early 1980s James Martin had been one of the pathfinders in data planning methodologies. He was one of the first to identify data as being an enterprise wide asset that required management, and had developed a series of tools and methods to support that process. [11]

Most of the large consulting firms developed their own methods to address the same basic issue. Frequently, their approaches were incorporated into their own branded system development methodologies that encompassed the complete systems development life-cycle.

Strategic IS/IT Planning, 1996

Tozer's "Strategic IS/IT Planning", was published in 1996 by Butterworth Heinemann as part of the Datamation Professional Series. The book mentioned to offer:

  • Supports a range of business planning techniques such as Portfolio Management and Value Chain Analysis.
  • Helps to ensure accurate and continuing aligning of IS/IT strategy with business goals and intentions.
  • Delivers a complete IS/IT plan, integrated with the business planning process, with effective provision for implementation and continuing maintenance.
  • Incorporates the latest advances in information technology, including Open Systems and Client/Server. [12]

The book was the most comprehensive outline of Tozer's approaches, though it now appears very dated; for example because it didn't even mention the Internet. [12]

Morphosis, 2010

In his 2010 science fiction novel "Morphosis," Tozer has been "speculating that mankind as an evolving species may still be in an early, vulnerable, fledgling state, as much at risk from itself as from environmental factors and competition from other species... [and] sometimes wonders whether it may be necessary - albeit difficult - for us as a species to shed some of the attributes and ingrained reflexes such as our tendency to violent conflict which we developed during our evolutionary struggle for survival so far before we can hope to reach our destiny as a mature species on the wider stage." [1]

Selected publications

Articles, a selection:

Related Research Articles

Software development is the process of conceiving, specifying, designing, programming, documenting, testing, and bug fixing involved in creating and maintaining applications, frameworks, or other software components. Software development involves writing and maintaining the source code, but in a broader sense, it includes all processes from the conception of the desired software through to the final manifestation of the software, typically in a planned and structured process. Software development also includes research, new development, prototyping, modification, reuse, re-engineering, maintenance, or any other activities that result in software products.

<span class="mw-page-title-main">SWOT analysis</span> Business planning and analysis technique

SWOT analysis is a strategic planning and strategic management technique used to help a person or organization identify Strengths, Weaknesses, Opportunities, and Threats related to business competition or project planning. It is sometimes called situational assessment or situational analysis. Additional acronyms using the same components include TOWS and WOTS-UP.

<span class="mw-page-title-main">IDEF</span> Family of modeling languages

IDEF, initially an abbreviation of ICAM Definition and renamed in 1999 as Integration Definition, is a family of modeling languages in the field of systems and software engineering. They cover a wide range of uses from functional modeling to data, simulation, object-oriented analysis and design, and knowledge acquisition. These definition languages were developed under funding from U.S. Air Force and, although still most commonly used by them and other military and United States Department of Defense (DoD) agencies, are in the public domain.

<span class="mw-page-title-main">Systems development life cycle</span> Systems engineering terms

In systems engineering, information systems and software engineering, the systems development life cycle (SDLC), also referred to as the application development life cycle, is a process for planning, creating, testing, and deploying an information system. The SDLC concept applies to a range of hardware and software configurations, as a system can be composed of hardware only, software only, or a combination of both. There are usually six stages in this cycle: requirement analysis, design, development and testing, implementation, documentation, and evaluation.

<span class="mw-page-title-main">Business analyst</span> Person who analyses and documents a business

A business analyst (BA) is a person who processes, interprets and documents business processes, products, services and software through analysis of data. The role of a business analyst is to ensure business efficiency increases through their knowledge of both IT and business function.

<span class="mw-page-title-main">The Open Group Architecture Framework</span> Reference model for enterprise architecture

The Open Group Architecture Framework (TOGAF) is the most used framework for enterprise architecture as of 2020 that provides an approach for designing, planning, implementing, and governing an enterprise information technology architecture. TOGAF is a high-level approach to design. It is typically modeled at four levels: Business, Application, Data, and Technology. It relies heavily on modularization, standardization, and already existing, proven technologies and products.

Technology strategy is the overall plan which consists of objectives, principles and tactics relating to use of technologies within a particular organization. Such strategies primarily focus on the technologies themselves and in some cases the people who directly manage those technologies. The strategy can be implied from the organization's behaviors towards technology decisions, and may be written down in a document. The strategy includes the formal vision that guide the acquisition, allocation, and management of IT resources so it can help fulfill the organizational objectives.

Data architecture consist of models, policies, rules, and standards that govern which data is collected and how it is stored, arranged, integrated, and put to use in data systems and in organizations. Data is usually one of several architecture domains that form the pillars of an enterprise architecture or solution architecture.

<span class="mw-page-title-main">Enterprise architecture framework</span> Frame in which the architecture of a company is defined

An enterprise architecture framework defines how to create and use an enterprise architecture. An architecture framework provides principles and practices for creating and using the architecture description of a system. It structures architects' thinking by dividing the architecture description into domains, layers, or views, and offers models - typically matrices and diagrams - for documenting each view. This allows for making systemic design decisions on all the components of the system and making long-term decisions around new design requirements, sustainability, and support.

<span class="mw-page-title-main">Enterprise modelling</span>

Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.

Service-oriented modeling is the discipline of modeling business and software systems, for the purpose of designing and specifying service-oriented business systems within a variety of architectural styles and paradigms, such as application architecture, service-oriented architecture, microservices, and cloud computing.

Facility condition assessment is an analysis of the condition of a facility in terms of age, design, construction methods, and materials. The individuals who perform the assessment are typically architects and engineers, and skilled-trade technicians. Engineering and architectural professional opinions as to the conditions observed are part of the assessment. Building diagnostics go beyond facility condition assessments to determine solutions to the problems found and predict outcomes of the solutions.

Gerardus Maria "Sjir" Nijssen is a Dutch computer scientist, former professor of computer science at the University of Queensland, consultant, and author. Nijssen is considered the founder of verbalization in computer science, and one of the founders of business modeling and information analysis based on natural language.

<span class="mw-page-title-main">Enterprise life cycle</span> Process of changing an enterprise over time

Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.

Steven Howard Spewak was an American management consultant, author, and lecturer on enterprise architectures, known for the development of Enterprise Architecture Planning (EAP).

In software engineering, a software development process is a process of dividing software development work into smaller, parallel, or sequential steps or sub-processes to improve design and/or product management. It is also known as a software development life cycle (SDLC). The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.

Macroscope is an integrated set of methods aimed at enterprise IT activities. Macroscope was developed and is maintained by Fujitsu in Canada. It is primarily used as their core body of knowledge to support the consulting services that they provide to their clients and is also licensed as a commercial product to a number of their clients

Enterprise data planning is the starting point for enterprise wide change. It states the destination and describes how you will get there. It defines benefits, costs and potential risks. It provides measures to be used along the way to judge progress and adjust the journey according to changing circumstances.

The history of business architecture has its origins in the 1980s. In the next decades business architecture has developed into a discipline of "cross-organizational design of the business as a whole" closely related to enterprise architecture. The concept of business architecture has been proposed as a blueprint of the enterprise, as a business strategy, and also as the representation of a business design.

The Integrated Management Concept, or IMC is an approach to structure management challenges by applying a "system-theoretical perspective that sees organisations as complex systems consisting of sub-systems, interrelations, and functions". The most characteristic aspect of the IMC is its distinction between three particular management dimensions: normative, strategic, and operational management, which are held together by different integration mechanisms. The normative management dimension determines the general aim of the organization, the strategic dimension directs the plans, basic structures, systems, and the problem-solving behaviour of the staff for achieving it, and the operative level translates the normative missions and strategic programs into day-to-day organizational processes.

References

  1. 1 2 3 Ed Tozer at amazon.com. Accessed 9 May 2015.
  2. ↑ Andriole, Stephen J. "The collaborate/integrate business technology strategy." Communications of the ACM 49.5 (2006): 85-90.
  3. ↑ Peña-Mora, Feniosky; Tanaka, Shunsuke (2002). "Information technology planning framework for Japanese general contractors" (PDF). Journal of Management in Engineering. 18 (3): 138–149. doi:10.1061/(asce)0742-597x(2002)18:3(138). hdl: 1721.1/9012 .
  4. 1 2 Tozer (1986); Tozer, Edwin E. (1986). "Developing strategies for management information systems". Long Range Planning. 19 (4): 31–40. doi:10.1016/0024-6301(86)90267-0.
  5. ↑ "Edwin E. Tozer Limited," at duedil.com. Accessed 23-03-2015.
  6. ↑ E. E. Tozer at DBLP Bibliography Server OOjs UI icon edit-ltr-progressive.svg
  7. ↑ Tozer (1975)
  8. 1 2 Tozer (1976)
  9. ↑ Tozer (1986)
  10. 1 2 Farsheed Azad. "MSc. Information Engineering: An investigation on models and methodologies for developing an I.S. Strategy," June 1990. at pchelpline.com, uploaded 2012/07. Accessed 23-03-2015
  11. ↑ James Martin. Viewdata and the information society. 1982
  12. 1 2 Tozer (1998)
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.