James Martin (author)
James Martin (19 October 1933 – 24 June 2013) was a British Information Technology consultant and author. Martin was nominated for a Pulitzer prize for his book, The Wired Society: A Challenge for Tomorrow (1977).
- A real-time computer system may be defined as one which controls an environment by receiving data, processing them, and taking action or returning results sufficiently quickly to affect the functioning of the environment at that time.
- Martin (1967) Design of real-time computer systems; cited in: John R. Ellis (1998) Objectifying Real-Time Systems. p. 249
- As technology grows in power, its ability either to disrupt or to heal increases. We can destroy the planet more easily than we can heal the harm we have done so far. To heal, we have to move to new technologies, new social patterns, new types of consumer products, new ways of generating and spending wealth. Such changes will inevitably occur, whether they are brought by healing forethought or mindless destruction. The future will not be a repetition of the past.
- James Martin (1978) The wired society. p. 3
- From a very early age, we form concepts. Each concept is a particular idea or understanding we have about our world. These concepts allow us to make sense of and reason about the things in our world. These things to which our concepts apply are called objects.
- James Martin (1993, p. 17) as cited in: "CIS330 Object Oriented Approach Ch2" webcadnet.blogspot.nl. 2011/04/16
Information Engineering (1989)
- Information engineering has been defined with the reference to automated techniques as follows: An interlocking set of automated techniques in which enterprise models, data models and process models are built up in a comprehensive knowledge-base and are used to create and maintain data-processing systems.
- p. viii
- Information Engineering is the application of an interlocking set of formal techniques for the planning, analysis, design, and construction of information systems on the enterprise wide basis or across a major sector of the enterprise.
- p. 1; cited in Karl E. Kurbel (2008) The making of information systems [electronic resource]. p. 176
The great transition (1995)
James Martin (1995) The great transition: using the seven disciplines of enterprise engineering to align people, technology.
- Enterprise Engineering is not a single methodology, but a sophisticated synthesis of the most important and successful of today's change methods. "Enterprise Engineering" first explains in detail all the critical disciplines (including continuous improvement, radical reinvention of business processes, enterprise redesign, and strategic visioning). It then illustrates how to custom-design the right combination of these change methods for your organization's specific needs.
- Book summary
- A new type of professional is emerging – the enterprise engineer
- p. xii, As cited in: Jan Hoogervorst (2009) Enterprise Governance and Enterprise Engineering. p. 9
- Enterprise engineering is an integrated set of disciplines for building an enterprise, its processes, and systems.
- p. 58; As cited in: Jan Hoogervorst (2009, p. 9)
- A horrifying amount of "business engineering" is done with the wrong strategic vision. A horrifying amount of IT development is done with the wrong business design.
- As cited in: "The Great Transition" Jurgens Pieterse April 7, 2006
About James Martin
- Dr James Martin, entrepreneur, visionary, "guru of the information age", "father of Case", ranked fourth in the world by Computerworld among the most influential people in the computer industry, Martin is not only a distinguished technology expert, but also a leading business authority, generally acknowledged as THE specialist on the social and business implications of computers and technology.
- "Interview: Dr James Martin", computerweekly.com Thursday 28 October 2010 17:45
- Systems engineering as an approach and methodology grew in response to the increase size and complexity of systems and projects... This engineering approach to the management of complexity by modularization was re-deployed in the software engineering discipline in the 1960s and 1970s with a proliferation of structured methodologies that enabled the the analysis, design and development of information systems by using techniques for modularized description, design and development of system components. Yourdon and DeMarco's Structured Analysis and Design, SSADM, James Martin's Information Engineering, and Jackson's Structured Design and Programming are examples from this era. They all exploited modularization to enable the parallel development of data, process, functionality and performance components of large software systems. The development of object orientation in the 1990s exploited modularization to develop reusable software. The idea was to develop modules that could be mixed and matched like Lego bricks to deliver to a variety of whole system specifications. The modularization and reusability principles have stood the test of time and are at the heart of modern software development.
- Peter Allen, Steve Maguire, Bill McKelvey (2011) The SAGE Handbook of Complexity and Management. p. 35