📈Graphical Representation: Tree (Definitions)

"A complex data structure built from nodes, each of which points to two or more other nodes." (Jesse Liberty, "Sams Teach Yourself C++ in 24 Hours" 3rd Ed., 2001)

"In the hierarchical data mode, a single entity hierarchy." (Jan L Harrington, "Relational Database Design and Implementation" 3rd Ed., 2009)

"A structure for data relationships where all relationships are one-to-many and no child entity may have more than one parent entity." (Jan L Harrington, "SQL Clearly Explained" 3rd Ed., 2010)

"A graph in which child nodes do not have more than one parent. SEE ALSO chart; graph; structure, tree." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A hierarchy of things from the same population. The things could be a) instances from a population represented by a single type icon representing the population of instances, and a reflexive relationship on that type, or b) types from the set of types defined in a database represented by a tree structure where each node of the tree is a population of instances of the same type. In the first case, it is the instances that form a tree structure, and in the second, it is the types that form a tree structure. The latter is called a hierarchical data structure." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A linked data structure that forms a hierarchy where nodes at higher levels know about a subset of the nodes in the level below them. Each node in a tree can only be reached from a single node in the level above it." (Mark C Lewis, "Introduction to the Art of Programming Using Scala", 2012)

"A structure with a unique starting node (the root), in which each node is capable of having multiple child nodes, and in which a unique path exists from the root to every other node" (Nell Dale et al, "Object-Oriented Data Structures Using Java" 4th Ed., 2016)

"A tree is a constrained graph. Trees are directed graphs because the 'parent of' relationship between nodes is asymmetric: the edges are arrows that point in a certain direction. Trees are acyclic graphs, because if you follow the directed edges from one node to another, you can never encounter the same node twice. Finally, trees have the constraint that every node (except the root) must have exactly one parent." (Robert J Glushko, "The Discipline of Organizing: Professional Edition, 4th Ed", 2016)

"Trees consist of nodes joined by edges, recursively nested. When a single, root dictionary is connected to child nodes that are themselves dictionaries, we say that the dictionaries are nested into a kind of tree structure." (Robert J Glushko, "The Discipline of Organizing: Professional Edition" 4th Ed., 2016)

"Hierarchical data structure where each node may have any number of child nodes, but only one parent node (with the exception of the root node, which has no parent)." (Karl Beecher, "Computational Thinking - A beginner's guide to problem-solving and programming", 2017)

📈Graphical Representation: PERT Chart (Definitions)

"A type of network planning chart." (Michael S Dobson, "The Juggler's Guide to Managing Multiple Projects", 2003)

"Diagram that displays the dependency relationships between tasks." (Clyde M Creveling, "Six Sigma for Technical Processes", 2006)

"Diagram that displays the dependency relationships that exist between tasks and helps to discern the variation in expected task time." (Lynne Hambleton, "Treasure Chest of Six Sigma Growth Methods, Tools, and Best Practices", 2007)

"Project Evaluation and Review Technique; a graphical representation of work tasks and their predecessor and successor relations." (Bruce P Douglass, "Real-Time Agility", 2009)

"a type of chart used in project management, where tasks are represented as circles, and arrows between tasks are used to show the sequence and task dependencies." (Bill Holtsnider & Brian D Jaffe, "IT Manager's Handbook" 3rd Ed., 2012)

"A graph that uses nodes (circles or boxes) and links (arrows) to show the precedence relationships among the tasks in a project." (Rod Stephens, "Beginning Software Engineering", 2015)

🚧Project Management: Program (Definitions)

"(1) A project. (2) A collection of related projects and the infrastructure that supports them, including objectives, methods, activities, plans, and success measures." (Sandy Shrum et al, "CMMI®: Guidelines for Process Integration and Product Improvement", 2003)

"A set of projects pointed toward the same objective." (Steve Williams & Nancy Williams, "The Profit Impact of Business Intelligence", 2007)

"A group of related projects managed in a coordinated way to obtain benefits and control not available from managing them individually. Programs may include elements of related work outside of the scope of the discrete projects in the program." (Cynthia Stackpole, "PMP® Certification All-in-One For Dummies®", 2011)

"A collection of projects with a common success criteria under integrated management. These projects consist of people, technology, and processes aimed at implementing significant business and technology change. A program is a major enterprise initiative, an element in the overall business strategy and direction." (Paul C Dinsmore et al, "Enterprise Project Governance", 2012)

"A portfolio of projects and initiatives managed together - sharing something critical like joint objectives or a common resource pool." (Mike Clayton, "Brilliant Project Leader", 2012)

"A group of related projects, subprograms, and program activities that are managed in a coordinated way to obtain benefits not available from managing them individually." (PMI, "Implementing Organizational Project Management: A Practice Guide", 2014)

"An endeavor that seeks to deliver benefits via activities that by their nature have uncertain outcomes. The uncertainty associated with programs dictates that they need to be managed adaptively, so that their strategies and plans can be modified in response to emergent outcomes. As a result, programs may be highly complex. The outcomes required by programs are pursued via projects, subprograms, and other program-related activities." (Richard J Heaslip, "Managing Complex Projects and Programs", 2014)

"Coordinated set of change projects that provide business benefits to the organization." (Gilbert Raymond & Philippe Desfray, "Modeling Enterprise Architecture with TOGAF", 2014)

"Related projects, subsidiary programs, and program activities that are managed in a coordinated manner to obtain benefits not available from managing them individually." (Project Management Institute, "A Guide to the Project Management Body of Knowledge (PMBOK® Guide)" 6th Ed., 2017)

"A group of related projects, subsidiary programs, and program activities managed in a coordinated way to obtain benefits not available from managing them individually. May include work outside the scope of projects but will always have two or more projects within its scope." (H James Harrington & William S Ruggles, "Project Management for Performance Improvement Teams", 2018)

"Projects/activities planned and managed together to achieve an overall set of related objectives and outcomes" (ITIL)

📈Graphical Representation: Flow Chart (Definitions)

"A flow chart is a graphic method to show pictorially how a series of activities, procedures. operations. events. ideas, or other factors are related to each other. It shows the sequence, cycle. or flow of these factors and how they are connected in a series of steps from beginning to end." (Robert Lefferts, "Elements of Graphics: How to prepare charts and graphs for effective reports", 1981)

"A flow chart is a diagram that visually displays interrelated information such as events, steps in a process, functions, etc., in an organized fashion, such as sequentially or chronologically. The things being represented can be tangible or intangible." (Robert L Harris, "Information Graphics: A Comprehensive Illustrated Reference", 1996)

"A pictorial representation of the flow of logic." (Greg Perry, "Sams Teach Yourself Beginning Programming in 24 Hours" 2nd Ed., 2001)

"An activity that defines the flow chart modeling style. Child activities can be added to this activity, and direct connections can be defined between the activities to control the flow of execution." (Bruce Bukovics, "Pro WF: Windows Workflow in .NET 4", 2010)

[flowcharting:] "The depiction in a diagram format of the inputs, process actions, and outputs of one or more processes within a system." (Cynthia Stackpole, "PMP® Certification All-in-One For Dummies®", 2011)

"A means of depicting a process from beginning to end, using flowcharting symbols to indicate the type of tasks in the process." (Charles Cooper & Ann Rockley, "Managing Enterprise Content: A Unified Content Strategy" 2nd Ed., 2012)

[flowcharting:] "A graphical method for depicting the movement of items, customers, or information though a system. Although many of the symbols were originally developed with information processing in mind, they have been adapted in various forms to map other process flows." (Kenneth A Shaw, "Integrated Management of Processes and Information", 2013)

"The depiction in a diagram format of the inputs, process actions, and outputs of one or more processes within a system." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

"A diagram that represents an algorithm or process. Some organizations use flow charts in troubleshooting guides to help technicians diagnose problems. They are also useful when developing expert systems." (Darril Gibson, "Effective Help Desk Specialist Skills", 2014)

📈Graphical Representation: Heatmaps (Definitions)

"A chart where one set of values is represented by areas of rectangles, and other sets of values are represented by colors. [...] the size of a rectangle reflects its importance, and color conveys the speed of change." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A type of map presentation where the intensity of color for each polygon corresponds to the related analytical data. For example, low values in a range appear as blue (cold) and high values as red (hot)." (Microsoft, "SQL Server 2012 Glossary", 2012)

"A heat map is a graphical representation where the data values are mapped to color intensities. The name heat map refers to the popular color-encoding where high values are encoded to hotter colors such as reds and yellows and smaller values are encoded to greens and blues. However, a heat map can have any color encoding that is convenient." (Ira Greenberg et al, "Processing: Creative Coding and Generative Art in Processing 2", 2013)

"A color-coded matrix generated by stakeholders voting on risk level by color (e.g., red being highest)." (Robert F Smallwood, "Information Governance: Concepts, Strategies, and Best Practices", 2014)

"Heatmap is a visualization that displays the expression values of the features (genes, exons, etc.) using a color scale. Features are typically arranged in columns (samples) and rows (features) as in the original data matrix. Each feature-sample pair is represented with a small rectangle that is colored according to its expression. Often both samples and features are hierarchically clustered before constructing the heatmap, and clustering is represented with a tree on the left and top from the colored data matrix." (Eija Korpelainen et al, "RNA-seq Data Analysis: A Practical Approach", 2014)

"[Heatmap is] a special kind of tile map, which is a two-dimensional graphical representation of data having values displayed using colors instead of numbers, text, or markers (data  points). It provides an easy way to understand and analyze complex/huge data sets. It applies blurring of markers and shading (dark or light) on the basis of the total amount of overlap."  (Yuvraj Gupta, "Kibana Essentials", 2015)

"Heatmaps are two-dimensional graphical representations of data where the values of a variable are shown as colors." (Agnieszka Bojkon, "Informative or Misleading? Heatmaps Deconstructed", [in "Human-Computer Interaction: New Trends, 13th International Conference"] 2009) 

"A heat map is a graphical representation of a table of data. The individual values are arranged in a table/matrix and represented by colors. Use grayscale or gradient for coloring. Sorting of the variables changes the color pattern." (Kristen Sosulski, "Data Visualization Made Simple: Insights into Becoming Visual", 2019)

"A heat map is a thematic map in which areas are shaded or patterned in proportion to the measurement of the statistical variable being displayed on the map, such as population density or per capita income. Heat maps provide an easy way to visualize how a measurement varies across a geographic area or show the level of variability within a region." (Sankar N. Nair & E S Gopi,  "Deep Learning Techniques for Crime Hotspot Detection", 2020)

"A heatmap is a visualization where values contained in a matrix are represented as colors or color saturation. Heatmaps are great for visualizing multivariate data (data in which analysis is based on more than two variables per observation), where categorical variables are placed in the rows and columns and a numerical or categorical variable is represented as colors or color saturation." (Mario Döbler & Tim Großmann, "The Data Visualization Workshop", 2nd Ed., 2020)

"Heatmap is another representational way in which the frequencies of the various parameters of the data set is represented in different colors, much like an image captured by a thermal imaging camera in which the graph consists of varying temperatures and the temperatures are differentiated according to the colors." (Shreyans Pathak & Shashwat Pathak, "Data Visualization Techniques, Model and Taxonomy", 2020)

"A heatmap is a plot that shows the magnitude of a phenomenon as color in two dimensions. The color variation may be by hue or intensity." (Swapnil Saurav, "Python Apps on Visual Studio Code", 2024)

📈Graphical Representation: Bar Chart (Definitions)

"A graphic that uses rectangular bars in varying lengths to represent comparisons of amounts." (Jennifer George-Palilonis, "A Practical Guide to Graphics Reporting", 2006)

"A chart that shows bars to illustrate frequencies or values for individual categories." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A horizontal bar chart used in project management; a graphical illustration of a schedule that helps to plan, coordinate, and track specific tasks in a project." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A graphic display of schedule-related information. In the typical bar chart, schedule activities or work breakdown structure components are listed down the left side of the chart, dates are shown across the top, and activity durations are shown as date-placed horizontal bars." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

"A graphical representation of project activities shown in a time-scaled bar line with no links shown between activities." (Peter Oakander et al, "CPM Scheduling for Construction: Best Practices and Guidelines", 2014)

"A chart that uses horizontal bars to represent values." (Faithe Wempen, "Computing Fundamentals: Introduction to Computers", 2015)

"It is a statistical presentation technique that represents frequency data as horizontal or vertical bars. Bar charts are used to represent time series and quantitative data." (K  N Krishnaswamy et al, "Management Research Methodology: Integration of Principles, Methods and Techniques", 2016)

📈Graphical Representation: Gantt Chart (Definitions)

"A chart that represents project activities as horizontal lines whose length shows the time span of each activity. The ends of each line correspond to the start and finish milestones, indicated by triangles. Progress is indicated by filling in the triangles when milestones are completed. Gantt charts are useful for simple schedules, but do not show task dependencies. Resource loaded networks (RLNs) should be used for projects with many interdependent tasks." (Richard D Stutzke, "Estimating Software-Intensive Systems: Projects, Products, and Processes", 2005)

"A bar chart (named after Henry Gantt) that shows when tasks start and finish as well as the relationships between tasks." (Bonnie Biafore, "Successful Project Management: Applying Best Practices and Real-World Techniques with Microsoft Project", 2011)

"A horizontal bar chart used in project management; a graphical illustration of a schedule that helps to plan, coordinate, and track specific tasks in a project. Named for Henry Gantt." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A tool developed by Henry Gantt that helps a project manager to plan, communicate and manage a project. Shows project activities as horizontal bars, with a length that represents the duration of the task, and places them against a fixed timeline." (Mike Clayton, "Brilliant Project Leader", 2012)

📈Graphical Representation: Infographic (Definitions)

"an infographic is defined as a visualization of data or ideas that tries to convey complex information to an audience in a manner that can be quickly consumed and easily understood." (Mark Smiciklas, "The Power of Infographics: Using Pictures to Communicate and Connect with Your Audiences", 2012)

"Tools and techniques involved in graphical representation of data, mostly in journalism, art, and storytelling." (Anna Ursyn, "Visualization as Communication with Graphic Representation", 2015)

"Use of visual images such as charts, graphic organizers, diagrams, photos, etc. in teaching and learning." (Esther Ntuli, "Active Learning Strategies in Technology Integrated K-12 Classrooms", 2015)

"Information graphics that are visual representations of data or information." (Julie A Delello & Rochell R McWhorter, "New Visual Literacies and Competencies for Education and the Workplace", 2016)

 "Information or data represented as a visual image in a chart or diagram. An infographic can be an excellent way to conceptualize dense text or numbers in ways that appeal to the eye and engage the reader." (Kindra Cotton et al, "Leveraging New Media as Social Capital for Diversity Officers", 2016)

"A short-form, visual representation of information, data, or knowledge presented through simple images that highlight patterns, trends, or insights. Simplified from the term information graphic." (Jonathan Ferrar et al, "The Power of People: Learn How Successful Organizations Use Workforce Analytics To Improve Business Performance", 2017)

[Infographic Map:] "Diagrammatic 'visualizations' of the space of knowledge and its associative logics that allows to use its own 'form' as a tool to 'act' on complex systems of knowledge." (Alessandra Cirafici & Alessandra Avella, "A Virtual Museum of Pompeii 'ex Votos': Design Strategies", 2020)

"Graphic visual representations of information, data or knowledge intended to present complex information quickly and clearly." (Jing Zhou, "Connecting Art, Culture, Science, and Technology", 2021)

"a form of communication that uses visual language and text. Both languages are complementary, part of a whole, and therefore can’t be understood when separate" (Jaime Serra)

"An infographic is a visual form of content used as a medium to represent and share information, knowledge, and data." (Infographic World)

"An infographic is an edited, summarized presentation of data selected by a designer to tell a story. A visualization is a display designed to explore data so every reader will be able to extract his or her own stories" (Alberto Cairo)

📈Graphical Representation: Causal Loop Diagrams (Definition)

"One of the tools of systems thinking. Causal loop diagrams capture how variables in a system are interrelated. A CLD takes the form of a closed loop that depicts cause-and-effect linkages." (Virginia Anderson & Lauren Johnson, "Systems Thinking Basics: From Concepts to Casual Loops", 1997)

"A CLD is a graphic model of some of the key system variables connected by arrows that denote the causal influences among the variables. Each arrowhead is identified as either positive (+) or negative (-) to indicate how the dependent variable changes when the independent variable changes." (Daniel D Burke, System Dynamics-based Computer Simulations and Evaluation, 2006)

"A CLD is diagrammatic tool used to describe the causal relationship between key quantities and to identify feedback mechanisms." (Dina Neiger & Leonid Churilov, "Integration of Diagrammatic Business Modeling Tools", 2008)

"A network of actuators connected together is called a causal loop diagram. A causal loop diagram shows how potential business actions lead to complex dynamic effects." (David M Bridgeland & Ron Zahavi, "Business Modeling: A Practical Guide to Realizing Business Value", 2009)

"A tool that captures the causal interrelationships amongst a set of variables. CLDs reveal systemic patterns underlying complex relationships and highlight hidden causes and unintended consequences." (Kambiz E Maani, "Systems Thinking and the Internet from Independence to Interdependence", 2009)

"Causal loop diagramming is a form of cause-and-effect modeling. The diagrams represent systems and their behaviors as a collection of nodes and links. Nodes represent the things in a system, and links illustrate interactions and influences." (Olivia Parr Rudd, "Business Intelligence Success Factors: Tools for Aligning Your Business in the Global Economy", 2009)

"Causal loop diagrams (CLDs) are a kind of systems thinking tool. These diagrams consist of arrows connecting variables (things that change over time) in a way that shows how one variable affects another." (Raed M Al-Qirem & Saad G Yaseen, "Modelling a Small Firm in Jordan Using System Dynamics", 2010)

"A visual representation of a system's feedback loops, where positive loops cycle clockwise, and negative loops cycle counter-clockwise." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"In systems thinking terms, causal loop diagrams are simplified ways to describe essential elements and relationships in a system. These diagrams include curved causal-link arrows (depicting influence from cause to effect) and the polarity of that linkage. An 's' indicates that cause and effect move in the same direction and an  'o' shows that they move in opposite directions (e.g., when cause increases, effect decreases below what it would have been). Causal-link arrows combine into balancing (B) and reinforcing (R) feedback loops. Significant lags between an action and the effects of that action appear as 'delay' on the causal-link arrows." (Karen L Higgins, "Economic Growth and Sustainability: Systems Thinking for a Complex World", 2015)

"A causal loop diagram (CLD) is a causal diagram that aids in visualizing how a number of variables in a system are interrelated and drive cause-and-effect processes. The diagram consists of a set of nodes and edges. Nodes represent the variables, and edges are the links that represent a connection or a relation between the two variables." (Andreas F Vermeulen, "Practical Data Science: A Guide to Building the Technology Stack for Turning Data Lakes into Business Assets", 2018)

"Methodology to build conceptual or simulation models depicting the causal structure of a complex system." (Francesca Costanza & Pietro Fontana, "Distributing Mutual Advantages in Italian Cooperatives: An Analysis of Patronage Refunds", 2019)

"In system dynamics modelling, they are closed causal chains involving relevant variables, whose interactions are responsible for the patterns of behavior taking place within a certain system." (Francesca Costanza, "Managing Patients' Organizations to Improve Healthcare: Emerging Research and Opportunities", 2020)

📈Graphical Representation: Pareto Chart/Diagram (Definitions)

"Fundamental tool for determining which characteristic is causing problems in a given process. Constructed by categorizing data, ranking, and plotting frequency of occurrence in bar-chart form in descending order along the x axis. Sometimes dollars are plotted on the y axis to emphasize the cost factor." (Alan Wa Steiss, "Strategic Management for Public and Nonprofit Organizations", 2003)

"A graphical tool for ranking causes from most significant to least significant." (Sohail Anwar, "Quality Management and Control", 2009)

"A chart showing both bars and a line, where the line shows the cumulative total of the individual bars going left to right." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A histogram, ordered by frequency of occurrence, that shows how many results were generated by each identified cause." (Cynthia Stackpole, "PMP® Certification All-in-One For Dummies", 2011)

"A method of displaying data values over time and classification" (Daniel Linstedt & W H Inmon, "Data Architecture: A Primer for the Data Scientist", 2014)

"A basic Pareto chart analyzes the unique values of a process variable, which are referred to as Pareto categories or levels. These values typically represent problems encountered during some phase of a manufacturing or service activity." (SAS)

"A Pareto chart is a bar graph. The lengths of the bars represent frequency or cost (time or money), and are arranged with longest bars on the left and the shortest to the right. In this way the chart visually depicts which situations are more significant." (ASQ) [source]

[Pareto analysis] "A statistical technique in decision making that is used for selection of a limited number of factors that produce significant overall effect. In terms of quality improvement, a large majority of problems (80%) are produced by a few key causes (20%)." (IQBBA)

📈Graphical Representation: Data Flow Diagram (Definitions)

"A diagram that shows the data flows in an organization, including sources of data, where data are stored, and processes that transform data." (Jan L Harrington, "Relational Database Dessign: Clearly Explained" 2nd Ed., 2002)

"A diagram of the data flow from sources through processes and files to users. A source or user is represented by a square; a data file is represented by rectangles with missing righthand edges; a process is represented by a circle or rounded rectangle; and a data flow is represented by an arrow." (Jens Mende, "Data Flow Diagram Use to Plan Empirical Research Projects", 2009)

"A diagram used in functional analysis which specifies the functions of the system, the inputs/outputs from/to external (user) entities, and the data being retrieved from or updating data stores. There are well-defined rules for specifying correct DFDs, as well as for creating hierarchies of interrelated DFDs." (Peretz Shoval & Judith Kabeli, "Functional and Object-Oriented Methodology for Analysis and Design", 2009)

[Control Data Flow Graph (CDFG):] " Represents the control flow and the data dependencies in a program." (Alexander Dreweke et al, "Text Mining in Program Code", 2009)

"A graphic method for documenting the flow of data within an organization." (Jan L Harrington, "Relational Database Design and Implementation: Clearly explained" 3rd Ed., 2009)

"A graphic representation of the interactions between different processes in an organization in terms of data flow communications among them. This may be a physical data flow diagram that describes processes and flows in terms of the mechanisms involved, a logical data flow diagram that is without any representation of the mechansm, or an essential data flow diagram that is a logical data flow diagram organized in terms of the processes that respond to each external event." (David C Hay, "Data Model Patterns: A Metadata Map", 2010)

"Data-flow diagrams (DFDs) are system models that show a functional perspective where each transformation represents a single function or process. DFDs are used to show how data flows through a sequence of processing steps." (Ian Sommerville, "Software Engineering" 9th Ed., 2011)

"A model of the system that shows the system’s processes, the data that flow between them (hence the name), and the data stores used by the processes. The data flow diagram shows the system as a network of processes, and is thought to be the most easily recognized of all the analysis models." (James Robertson et al, "Complete Systems Analysis: The Workbook, the Textbook, the Answers", 2013)

"A picture of the movement of data between external entities and the processes and data stores within a system." (Jeffrey A Hoffer et al, "Modern Systems Analysis and Design" 7th Ed., 2014)

"A schematic indicating the direction of the movement of data" (Daniel Linstedt & W H Inmon, "Data Architecture: A Primer for the Data Scientist", 2014)

"A Data Flow Diagram (DFD) is a graphical representation of the 'flow' of data through an information system, modeling its process aspects. Often it is a preliminary step used to create an overview of the system that can later be elaborated." (Henrikvon Scheel et al, "Process Concept Evolution", 2015)

"Data flow maps are tools that graphically represent the results of a comprehensive data assessment to illustrate what information comes into an organization, for what purposes that information is used, and who has access to that information." (James R Kalyvas & Michael R Overly, "Big Data: A Business and Legal Guide", 2015)

"A graphical representation of the logical or conceptual movement of data within an existing or planned system." (George Tillmann, "Usage-Driven Database Design: From Logical Data Modeling through Physical Schmea Definition", 2017)

"a visual depiction using standard symbols and conventions of the sources of, movement of, operations on, and storage of data." (Meredith Zozus, "The Data Book: Collection and Management of Research Data", 2017)

"A data-flow diagram is a way of representing a flow of data through a process or a system (usually an information system). The DFD also provides information about the outputs and inputs of each entity and the process itself." (Wikipedia) [source]

"A graphical representation of the sequence and possible changes of the state of data objects, where the state of an object is any of: creation, usage, or destruction." (IQBBA)

📈Graphical Representation: Cause-Effect Diagram (Definitions)

"A chart that can be used to systematically gather the problem causes of quality defects. Sometimes referred to as the 5M- or 6M-chart because most causes can be related to man (e.g., human factors), machine, method, material, milieu (i.e., the work environment), or the medium (the IT-platform)." (Martin J Eppler, "Managing Information Quality" 2nd Ed., 2006)

"A root cause approach to identifying, exploring, and graphically displaying all possible causes of an issue using a standard quality technique." (Danette McGilvray, "Executing Data Quality Projects", 2008)

"A chart that links an outcome to chains of possible contributing factors as tree structure working backwards from an event to determine possible root causes, drawn sideways so that it resembles the skeleton of a fish. Because the chart resembles the skeleton of a fish, it is often called a fishbone diagram." (DAMA International, "The DAMA Dictionary of Data Management", 2011)

"A chart associated with a technique for identifying factors linked to potential problems, risks, or effects. Factors can include time, machinery, methods, material, energy, measurements, personnel, and environment. Also known as the Ishikawa diagram or fishbone diagram." (Bonnie Biafore & Teresa Stover, "Your Project Management Coach: Best Practices for Managing Projects in the Real World", 2012)

"A decomposition technique that helps trace an undesirable effect back to its root cause." (For Dummies, "PMP Certification All-in-One For Dummies" 2nd Ed., 2013)

"A model used for identifying cause and effect. Also known as a fishbone diagram and named after its creator, Kaoru Ishikawa." (Sally-Anne Pitt, "Internal Audit Quality", 2014)

"Named after Kaoru Ishikawa, a diagram that shows possible causes of effects that you want to study such as excessive bugs, delays, and other failures in the development process." (Rod Stephens, "Beginning Software Engineering", 2015)

"A diagramming technique, also called the Ishikawa diagramming, which teams can use to identify root causes to a problem, the effects of an action, or the action items they could take to meet a goal." (David K Pham, "From Business Strategy to Information Technology Roadmap", 2016)

"A decomposition technique that helps trace an undesirable effect back to its root cause." (Project Management Institute, "The Standard for Organizational Project Management (OPM)", 2018)

📈Graphical Representation: Sparklines (Definitions)

"A sparkline is a small, intense, simple, word-sized graphic with typographic resolution." (Edward R Tufte, "Beautiful Evidence", 2006)

"A sparkline is a mini-image (thumbnail) of graphical data that enables you to put numbers in a temporal context without the need to display full charts." (Brian Clifton, "Advanced Web Metrics with Google Analytics", 2010)

"A sparkline is a very small chart, typically a line chart, that is drawn without labels on either axis. Its purpose is to show the variation in data, typically over time." (Bruce Johnson, "Professional Visual Studio", 2012)

"Sparklines are condensed graphs or charts that can be used in-line with text or grouped to show trends across several different measures." (Ryan Sleeper, "Practical Tableau: 100 Tips, Tutorials, and Strategies from a Tableau Zen Master", 2018)

"A sparkline is a small line chart with the purpose of showing a general trend, without the full details. A sparkline is very efficient in the amount of screen space it uses." (Andrew Berridge &, Michael Phillips, "TIBCO Spotfire: A Comprehensive Primer", 2019)

"A Sparkline is a tiny chart that appears in a cell and does not include any text data. So, a Sparkline is a great way to give a quick glance of a trend." (Eric Butow, "MCA Microsoft Office Specialist: Office 365 and Office 2019", 2021)

"A sparkline chart is a small, simple, and condensed data visualization tool that presents trends and variations in data over a concise space, typically in the form of a tiny line chart." (Phocas)

"A sparkline is a line chart that displays the variation in a null value, unique value, or non-unique value across the latest five consecutive profile runs." (Informatica)

"A sparkline is a tiny chart in a worksheet cell that provides a visual representation of data. Use sparklines to show trends in a series of values, such as seasonal increases or decreases, economic cycles, or to highlight maximum and minimum values. Position a sparkline near its data for greatest impact." (Microsoft)

"A sparkline is a very small line chart, typically drawn without axes or coordinates. It presents the general shape of a variation (typically over time) in some measurement, such as temperature or stock market price, in a simple and highly condensed way." (Wikipedia)

"Sparklines are small, simple line graphs traditionally used for displaying trends or variations of some variable" (TIBCO)

📈Graphical Representation: Mind Map (Definitions)

"A visual note-taking process that pares thoughts to key words and pictures illustrating the relationships among concepts." (Ruth C Clark & Chopeta Lyons, "Graphics for Learning", 2004)

"A mind map consists of a central concept which acts as a headline for the map and the branches that represent the aspects of the main concept. A mind map allows summarizing and decomposition of the key aspects of a complex problem or issue." (Hannu Kivijärvi et al, "A Support System for the Strategic Scenario Process", 2008) 

"A mind map is a diagram uses intuition to depict words, ideas or other items in branches around a central key word or idea." (Wan Ng & Ria Hanewald, "Concept Maps as a Tool for Promoting Online Collaborative Learning in Virtual Teams with Pre-Service Teachers", 2010)

[mind mapping:] "A process that brainstorms ideas, words, tasks or other elements and arranges them in groups around a central notion."  (Wan Ng & Ria Hanewald, "Concept Maps as a Tool for Promoting Online Collaborative Learning in Virtual Teams with Pre-Service Teachers", 2010)

[mind-mapping:] "A technique that uses multiple levels of detail for a texture. This technique selects from among the different sizes of an image available, or possibly combines the two nearest sized matches to produce the final fragments used for texturing." (Graham Sellers et al, "OpenGL SuperBible: Comprehensive Tutorial and Reference" 5th Ed., 2010)

"Refers to a technique for the graphical representation of information items, enabling visualization. A mindmap has a radial structure: it is constructed by starting from a central information item, around which other information items are organized like rays from a star, except that each ray can in turn be subdivided in a plurality of finer rays, and so on. The 'rays' are linear, going from an upstream point to downstream, more secondary points, and so on." (Humbert Lesca & Nicolas Lesca, "Weak Signals for Strategic Intelligence: Anticipation Tool for Managers", 2011)

"Powerful techniques you can utilize to increase your comprehension of written materials." (Jeffrey Magee, "The Managerial Leadership Bible", 2015)

[mind-mapping:] "A technique used to consolidate ideas created through individual brainstorming sessions into a single map to reflect commonality and differences in understanding and to generate new ideas." (Project Management Institute, "A Guide to the Project Management Body of Knowledge (PMBOK Guide)", 2017)

[mind mapping:] "A method to brainstorm thoughts while showing relationships of the parts to the whole." (Errick D Farmer et al, "Digital Course Redesign to Increase Student Engagement and Success", 2019)

"A diagram used to represent words, ideas, tasks, or other items linked to and arranged around a central keyword or idea. Mind maps are  used to generate, visualize, structure, and classify ideas, and as an aid in study, organization, problem solving, decision making, and writing." (Software Quality Assurance)

MS Office: Access vs. LightSwitch - About Starts and Ends of Software Products

Introduction

    When an important software product or technology is released on the market, it brings with it dooming prophecies about the end/death of a competing or related product or technology. Even if maybe it catches the attention, the approach became a stereotype leading to other futile fights between adepts, some food for thought and a pile of words for search engines. As LightSwitch was released recently, people started already sketching dooming plans for competing tools like MS Access, Silverlight, WebMatrix, Visual Studio, etc. It’s actually interesting to study and understand how the entry on the software market impacts the overall landscape, the publishing of more or less pertinent thoughts on the future of a product are more than welcome, though from this to forecasting the end of a software product or technology, at least not without well-grounded reasons, it’s a long way.
    In many cases it’s not even needed to go too deep into the features of the compared software products in order to dismiss such statements, this because there are a few common sense reasons for which the respective products will coexist, at least for the near future. Here are a few of them grouped into technology, products, people, partners and processes. Please note that by the terms old and new (software) products I’m referring here to a product existing on the market for a longer time, respectively a newly entered product.

Technology

    In theory a new software product attempts to take advantage of the latest technological advances in the field, following the trends. Also an old product can take advantage of the latest technological developments, though a certain backward compatibility needs to be maintained, fact that could come with advantages and disadvantages altogether. Considering that nowadays such a product doesn’t exist “per se” but in a complex infrastructure with multiple layers of interconnectivity, a new product has to fit also in the overall picture.
    A product in particular and a technology in general is doomed to extinction when it’s not more able to cope with the trends, when its characteristics don’t satisfy anymore users’ demands or the overhead of using it is greater than its benefits. As long two competing software products are trying to keep up with the trends and consolidate their market, the chances that they will parish are quite small. On the other side, each technology has sooner or later its own end.

Products

    Software products having a few years on the market have reached in theory a certain maturity and stability. New software products typically go through an adoption phase that may last from months to years, and it will take time until they reach a certain maturity and stability, until their market develops, until vendors include them in their portfolio, until other products will develop interfaces to them, etc. First of all it will take some time until the two will come to have the same market share, and secondly it will take even more time until the market share of one of the products will deprecate. In addition, markets embrace diversity and the demands are so various that each product arrives to find his place.
   When the products are coming from the same vendor and they are a part of greater packages and strategies, it’s hard to believe that a vendor would want to blow in the air his own business. Usually the two solutions target different markets, even if their markets intersect. Sure, there are also cases when a vendor might want to strengthen the position of a product in the detriment of another, especially when the benefits are higher.

People

    Often different products demand different skill sets or an upgrade of skill set. For sure not all developers will move from one platform to the other, some will be reticent, while others are declared fans so there is no way to move to something new. Sure, in IT there are frequent the cases when developers have knowledge about 2-3 competing products, though this aspect doesn’t necessarily have a huge impact on the short term. Considering that software products are becoming more and more complex, it’s sometimes even needed a specialization covering only a part of a product.

Partners

    Vendors and Customers, especially existing partners, will most probably approach and evaluate the new product, find a place in their portfolio/solution, conduct some pilot projects and eventually consider the product for further use. We can talk here about an adoption period, corroborated with the appearance of training material, best practices, books or any other material that facilitate the use of such a product. All this time requires time and effort, successful and unsuccessful projects, some years of experience.

Processes

    Organizations have already in place solutions based on a product and integrated with other products. Some of them could be personal solutions, and maybe quite easy to replace, though the replacement of business/enterprise solutions come maybe with important expenses, changes in the infrastructure, and maybe the most important, process changes. And why change something that’s working just for the sake of change?! Sure, if there is the need for a second or third product, this doesn’t (always) mean that all the previous similar products will be replaced. For sure the two or more products can coexist, even if provide similar functionality, and the can maybe complete each other.

Conclusion

    If one product or another will come to its end, for sure only time will tell. Usually when this happens, there are multiple factors that influenced the decay, factors that could be used maybe to foresee such an event. Though, without a detailed analysis or at least some well-supported ideas, dooming declarations about the rise or fall of software products are kind of futile, even if intended to catch readers’ attention. Enthusiastic or contradictory feelings about old or new products are natural, expressing opinions is free and welcomed when there is something to say, though are such declarations really necessary?!