Event partitioning, the Glossary

Table of Contents

1. 46 relations: Activity diagram, Actor (UML), Asterisk, Boolean data type, Brainstorming, Business case, Business rule, Communication diagram, Conditional (computer programming), Data element, Decomposition (computer science), Detection theory, Don't repeat yourself, Edward Yourdon, Empathy, Essential systems analysis, Event-driven architecture, For loop, Functional requirement, Hyperlink, Identifier, Infinite loop, ISO 8601, Nassi–Shneiderman diagram, Non-functional requirement, Object Constraint Language, Peter Checkland, Plan, Reductionism, Requirement, Scenario (computing), Semicolon, Sequence diagram, SIPOC, Soft systems methodology, Stephen J. Mellor, Structured English, Switch statement, System context diagram, Systems analysis, Systems thinking, Unified Modeling Language, Use case, Use case diagram, User story, While loop.

2. Decomposition methods
3. Events (computing)

Activity diagram

Activity diagrams are graphical representations of workflows of stepwise activities and actions with support for choice, iteration, and concurrency.

See Event partitioning and Activity diagram

Actor (UML)

An actor in the Unified Modeling Language (UML) "specifies a role played by a user or any other system that interacts with the subject." "An Actor models a type of role played by an entity that interacts with the subject (e.g., by exchanging signals and data), but which is external to the subject." "Actors may represent roles played by human users, external hardware, or other subjects.

See Event partitioning and Actor (UML)

Asterisk

The asterisk, from Late Latin asteriscus, from Ancient Greek ἀστερίσκος,, "little star", is a typographical symbol.

See Event partitioning and Asterisk

Boolean data type

In computer science, the Boolean (sometimes shortened to Bool) is a data type that has one of two possible values (usually denoted true and false) which is intended to represent the two truth values of logic and Boolean algebra.

See Event partitioning and Boolean data type

Brainstorming

Brainstorming is a creativity technique in which a group of people interact to suggest ideas spontaneously in response to a prompt.

See Event partitioning and Brainstorming

Business case

A business case captures the reasoning for initiating a project or task.

See Event partitioning and Business case

Business rule

A business rule defines or constrains some aspect of a business.

See Event partitioning and Business rule

Communication diagram

A communication diagram in Unified Modeling Language (UML) 2.5.1 is a simplified version of the UML 1.x collaboration diagram.

See Event partitioning and Communication diagram

Conditional (computer programming)

In computer science, conditionals (that is, conditional statements, conditional expressions and conditional constructs) are programming language constructs that perform different computations or actions or return different values depending on the value of a Boolean expression, called a condition.

See Event partitioning and Conditional (computer programming)

Data element

In metadata, the term data element is an atomic unit of data that has precise meaning or precise semantics.

See Event partitioning and Data element

Decomposition (computer science)

Decomposition in computer science, also known as factoring, is breaking a complex problem or system into parts that are easier to conceive, understand, program, and maintain. Event partitioning and Decomposition (computer science) are Decomposition methods.

See Event partitioning and Decomposition (computer science)

Detection theory

Detection theory or signal detection theory is a means to measure the ability to differentiate between information-bearing patterns (called stimulus in living organisms, signal in machines) and random patterns that distract from the information (called noise, consisting of background stimuli and random activity of the detection machine and of the nervous system of the operator).

See Event partitioning and Detection theory

Don't repeat yourself

"Don't repeat yourself" (DRY) is a principle of software development aimed at reducing repetition of information which is likely to change, replacing it with abstractions that are less likely to change, or using data normalization which avoids redundancy in the first place.

See Event partitioning and Don't repeat yourself

Edward Yourdon

Edward Nash Yourdon (April 30, 1944 – January 20, 2016) was an American software engineer, computer consultant, author and lecturer, and software engineering methodology pioneer.

See Event partitioning and Edward Yourdon

Empathy

Empathy is generally described as the ability to take on another's perspective, to understand, feel, and possibly share and respond to their experience.

See Event partitioning and Empathy

Essential systems analysis

Essential systems analysis was a new methodology for software specification published in 1984 by Stephen M. McMenamin and John F. Palmer for performing structured systems analysis based on the concept of event partitioning.

See Event partitioning and Essential systems analysis

Event-driven architecture

Event-driven architecture (EDA) is a software architecture paradigm concerning the production and detection of events. Event partitioning and event-driven architecture are events (computing).

See Event partitioning and Event-driven architecture

For loop

In computer science, a for-loop or for loop is a control flow statement for specifying iteration.

See Event partitioning and For loop

Functional requirement

In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a summary (or specification or statement) of behavior between inputs and outputs. Event partitioning and functional requirement are software requirements.

See Event partitioning and Functional requirement

Hyperlink

In computing, a hyperlink, or simply a link, is a digital reference to data that the user can follow or be guided to by clicking or tapping.

See Event partitioning and Hyperlink

Identifier

An identifier is a name that identifies (that is, labels the identity of) either a unique object or a unique class of objects, where the "object" or class may be an idea, physical countable object (or class thereof), or physical noncountable substance (or class thereof).

See Event partitioning and Identifier

Infinite loop

In computer programming, an infinite loop (or endless loop) is a sequence of instructions that, as written, will continue endlessly, unless an external intervention occurs, such as turning off power via a switch or pulling a plug.

See Event partitioning and Infinite loop

ISO 8601

ISO 8601 is an international standard covering the worldwide exchange and communication of date and time-related data.

See Event partitioning and ISO 8601

Nassi–Shneiderman diagram

A Nassi–Shneiderman diagram (NSD) in computer programming is a graphical design representation for structured programming.

See Event partitioning and Nassi–Shneiderman diagram

Non-functional requirement

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. Event partitioning and non-functional requirement are software requirements.

See Event partitioning and Non-functional requirement

Object Constraint Language

The Object Constraint Language (OCL) is a declarative language describing rules applying to Unified Modeling Language (UML) models developed at IBM and is now part of the UML standard.

See Event partitioning and Object Constraint Language

Peter Checkland

Peter Checkland (born 18 December 1930, in Birmingham, UK) is a British management scientist and emeritus professor of systems at Lancaster University.

See Event partitioning and Peter Checkland

Plan

A plan is typically any diagram or list of steps with details of timing and resources, used to achieve an objective to do something.

See Event partitioning and Plan

Reductionism

Reductionism is any of several related philosophical ideas regarding the associations between phenomena which can be described in terms of other simpler or more fundamental phenomena.

See Event partitioning and Reductionism

Requirement

In engineering, a requirement is a condition that must be satisfied for the output of a work effort to be acceptable. Event partitioning and requirement are software requirements.

See Event partitioning and Requirement

Scenario (computing)

In computing, a scenario (loaned) is a narrative of foreseeable interactions of user roles (known in the Unified Modeling Language as 'actors') and the technical system, which usually includes computer hardware and software. Event partitioning and scenario (computing) are software requirements.

See Event partitioning and Scenario (computing)

Semicolon

The semicolon (or semi-colon) is a symbol commonly used as orthographic punctuation.

See Event partitioning and Semicolon

Sequence diagram

In software engineering, a sequence diagram shows process interactions arranged in time sequence.

See Event partitioning and Sequence diagram

SIPOC

In process improvement, SIPOC or suppliers, inputs, process, outputs and customers (sometimes in the reversed order: COPIS) is a tool that summarizes the inputs and outputs of one or more business processes in table form, with each of the words forming a column in the table used in the analysis.

See Event partitioning and SIPOC

Soft systems methodology

Soft systems methodology (SSM) is an organised way of thinking that's applicable to problematic social situations and in the management of change by using action.

See Event partitioning and Soft systems methodology

Stephen J. Mellor

Stephen J. Mellor (born 1952) is an American computer scientist, developer of the Ward–Mellor method for real-time computing, the Shlaer–Mellor method, and Executable UML, and signatory to the Agile Manifesto.

See Event partitioning and Stephen J. Mellor

Structured English

Structured English is the use of the English language with the syntax of structured programming to communicate the design of a computer program to non-technical users by breaking it down into logical steps using straightforward English words.

See Event partitioning and Structured English

Switch statement

In computer programming languages, a switch statement is a type of selection control mechanism used to allow the value of a variable or expression to change the control flow of program execution via search and map.

See Event partitioning and Switch statement

System context diagram

A system context diagram in engineering is a diagram that defines the boundary between the system, or part of a system, and its environment, showing the entities that interact with it. Event partitioning and system context diagram are systems analysis.

See Event partitioning and System context diagram

Systems analysis

Systems analysis is "the process of studying a procedure or business to identify its goal and purposes and create systems and procedures that will efficiently achieve them".

See Event partitioning and Systems analysis

Systems thinking

Systems thinking is a way of making sense of the complexity of the world by looking at it in terms of wholes and relationships rather than by splitting it down into its parts. Event partitioning and Systems thinking are systems analysis.

See Event partitioning and Systems thinking

Unified Modeling Language

The unified modeling language (UML) is a general-purpose visual modeling language that is intended to provide a standard way to visualize the design of a system. Event partitioning and unified Modeling Language are software requirements.

See Event partitioning and Unified Modeling Language

Use case

In software and systems engineering, the phrase use case is a polyseme with two senses. Event partitioning and use case are software requirements.

See Event partitioning and Use case

Use case diagram

A use case diagram is a graphical depiction of a user's possible interactions with a system. Event partitioning and use case diagram are software requirements.

See Event partitioning and Use case diagram

User story

In software development and product management, a user story is an informal, natural language description of features of a software system. Event partitioning and user story are software requirements.

See Event partitioning and User story

While loop

In most computer programming languages, a while loop is a control flow statement that allows code to be executed repeatedly based on a given Boolean condition.

See Event partitioning and While loop

See also

Decomposition methods

• Benders decomposition
• Dantzig–Wolfe decomposition
• Decomposition (computer science)
• Event partitioning
• Modular design
• Network partition
• Theory of two-level planning
• Variable splitting

Events (computing)

• Apama (software)
• Asynchronous I/O
• Business activity monitoring
• Complex event processing
• Concurrent estimation
• DOM event
• Data event
• Database trigger
• Dead letter queue
• Discrete rate simulation
• Discrete-event simulation
• Enterprise Dynamics
• Epoll
• Esper (software)
• Event (computing)
• Event (synchronization primitive)
• Event Processing Technical Society
• Event bubbling
• Event chain diagram
• Event chain methodology
• Event correlation
• Event logging
• Event loop
• Event partitioning
• Event-driven architecture
• Event-driven programming
• Input/output completion port
• Interrupts
• Kqueue
• Libevent
• Libuv
• List of discrete event simulation software
• Message loop in Microsoft Windows
• Message queue
• Overlapped I/O
• Poll (Unix)
• Polling (computer science)
• Proactor pattern
• Reactor pattern
• Reverse computation
• RuleML
• Select (Unix)
• Staged event-driven architecture
• Unix signals
• Vert.x
• Webhook
• WindowProc

References

[1] https://en.wikipedia.org/wiki/Event_partitioning