5 Level pyramid model diagram - Information systems types

A five level pyramid model of different types of Information Systems based on the information processing requirement of different levels in the organization. The first level represents transaction processing systems to process basic data. The second level represents office support systems to process information in office. The third level represents management information systems to process information by managers. The fourth level represents decision support systems to process explicit knowledge. The fifth level represents executive information systems to process tacit knowledge.
"A Computer(-Based) Information System is essentially an IS using computer technology to carry out some or all of its planned tasks. The basic components of computer based information system are:
(1) Hardware - these are the devices like the monitor, processor, printer and keyboard, all of which work together to accept, process, show data and information.
(2) Software - are the programs that allow the hardware to process the data.
(3) Databases - are the gathering of associated files or tables containing related data.
(4) Networks - are a connecting system that allows diverse computers to distribute resources.
(5) Procedures - are the commands for combining the components above to process information and produce the preferred output.
The first four components (hardware, software, database and network) make up what is known as the information technology platform. Information technology workers could then use these components to create information systems that watch over safety measures, risk and the management of data. These actions are known as information technology services." [Information systems. Wikipedia]
This pyramid diagram was redesigned using the ConceptDraw PRO diagramming and vector drawing software from Wikimedia Commons file Five-Level-Pyramid-model.png. [commons.wikimedia.org/ wiki/ File:Five-Level-Pyramid-model.png]
This file is licensed under the Creative Commons Attribution 3.0 Unported license. [creativecommons.org/ licenses/ by/ 3.0/ deed.en]
The triangle chart example "Information systems types" is included in the Pyramid Diagrams solution from the Marketing area of ConceptDraw Solution Park.

This example of cloud computing system architecture diagram was redesigned from the Wikimedia Commons file: Windows Azure Network and Computes Architecture.png. [commons.wikimedia.org/ wiki/ File:Windows_ Azure_ Network_ and_ Computes_ Architecture.png]
This file is licensed under the Creative Commons Attribution-Share Alike 2.0 license. [creativecommons.org/ licenses/ by-sa/ 2.0/ ]
"Microsoft Azure (formerly Windows Azure before 25 March 2014) is a cloud computing platform and infrastructure, created by Microsoft, for building, deploying and managing applications and services through a global network of Microsoft-managed datacenters. It provides both PaaS and IaaS services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems." [Microsoft Azure. Wikipedia]
The diagram example "Microsoft Azure network and computes architecture" was created using ConceptDraw PRO diagramming and vector drawing software extended with the Azure Architecture solution from the Computer and Networks area of ConceptDraw Solution Park.

A four level pyramid model of different types of Information Systems based on the different levels of hierarchy in an organization. The first level represents transaction processing systems for workers. The second level represents management information systems for middle managers. The third level represents decision support systems for senior menegers. The fourth level represents executive information systems for executives.
"The "classic" view of Information systems found in the textbooks in the 1980s was of a pyramid of systems that reflected the hierarchy of the organization, usually transaction processing systems at the bottom of the pyramid, followed by management information systems, decision support systems, and ending with executive information systems at the top. Although the pyramid model remains useful, since it was first formulated a number of new technologies have been developed and new categories of information systems have emerged, some of which no longer fit easily into the original pyramid model.
Some examples of such systems are:
data warehouses,
enterprise resource planning,
enterprise systems,
expert systems,
search engines,
geographic information system,
global information system,
office automation." [Information systems. Wikipedia]
This diagram was redesigned using the ConceptDraw PRO diagramming and vector drawing software from Wikimedia Commons file Four-Level-Pyramid-model.png. [commons.wikimedia.org/ wiki/ File:Four-Level-Pyramid-model.png]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license. [creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
The triangle chart example "Information systems types" is included in the Pyramid Diagrams solution from the Marketing area of ConceptDraw Solution Park.

"A hydraulic circuit is a system comprising an interconnected set of discrete components that transport liquid. The purpose of this system may be to control where fluid flows (as in a network of tubes of coolant in a thermodynamic system) or to control fluid pressure (as in hydraulic amplifiers).
... hydraulic circuit theory works best when the elements (passive component such as pipes or transmission lines or active components such as power packs or pumps) are discrete and linear. This usually means that hydraulic circuit analysis works best for long, thin tubes with discrete pumps, as found in chemical process flow systems or microscale devices." [Hydraulic circuit. Wikipedia]
The engineering drawing example "Hydraulic circuits" was redrawn using ConceptDraw PRO diagramming and vector drawing software from the Wikimedia Commons file: Hydraulic circuits.png.
[commons.wikimedia.org/ wiki/ File:Hydraulic_ circuits.png]
This file is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported license.
[creativecommons.org/ licenses/ by-sa/ 3.0/ deed.en]
The engineering drawing example "Hydraulic circuits" is included in the Mechanical Engineering solution from the Engineering area of ConceptDraw Solution Park.

This sequence diagram example was redesigned from the Wikimedia Commons file: Builder design pattern sequence1.png.
"The UML sequence diagram which illustrates the Builder design pattern."
[commons.wikimedia.org/ wiki/ File:Builder_ design_ pattern_ sequence1.png]
"The builder pattern is an object creation software design pattern. Unlike the abstract factory pattern and the factory method pattern whose intention is to enable polymorphism, the intention of the builder pattern is to find a solution to the telescoping constructor anti-pattern. ... The intent of the Builder design pattern is to separate the construction of a complex object from its representation. By doing so the same construction process can create different representations." [Builder pattern. Wikipedia]
The SysML sequence diagram example "Builder design pattern sequence" was drawn using the ConceptDraw PRO diagramming and vector drawing software extended with the SysML solution from the Software Development area of ConceptDraw Solution Park.

This example was redesigned from the Wikipedia file: LastResortHotel BookRoom Process.png. [en.wikipedia.org/ wiki/ File:LastResortHotel_ BookRoom_ Process.png]
This file is licensed under the Creative Commons Attribution-ShareAlike 3.0 License. [creativecommons.org/ licenses/ by-sa/ 3.0/ ]
"Event partitioning is an easy-to-apply systems analysis technique that helps the analyst organize requirements for large systems into a collection of smaller, simpler, minimally-connected, easier-to-understand ‘mini systems’ / use cases. ...
Defining requirements.
Single process in a fictitious hotel using data flow diagram notation.
Single use case in a fictitious hotel using use case diagram notation.
This approach helps the analyst to decompose the system into ‘mentally bite-sized’ mini-systems using events that require a planned response. The level of detail of each response is at the level of ‘primary use cases’. Each planned response may be modelled using DFD notation or as a single use case using use case diagram notation.
The basic flow within a process or use case can usually be described in a relatively small number of steps, often fewer than twenty or thirty, possibly using something like ‘structured English’. Ideally, all of the steps would be visible all at once (often a page or less). The intention is to reduce one of the risks associated with short-term memory, namely, forgetting what is not immediately visible (‘out of sight, out of mind’). ...
Single process in a fictitious hotel using data flow diagram notation." [Event partitioning. Wikipedia]
The DFD example "Last resort hotel book room process" was created using the ConceptDraw PRO diagramming and vector drawing software extended with the Data Flow Diagrams solution from the Software Development area of ConceptDraw Solution Park.