Skip to ContentGo to accessibility pageKeyboard shortcuts menu
OpenStax Logo

Summary

2.1 Computational Thinking

  • Complex problems are situations that are difficult because they involve many different parts or factors.
  • Computational thinking means breaking these problems into smaller parts, understanding how these parts relate to each other, and then coming up with effective strategies or steps to solve each part.
  • Computational thinking is a set of tools or strategies for solving (and learning how to solve) complex problems that relate to mathematical thinking in its use of abstraction, decomposition, measurement, and modeling.
  • Characterization of computational thinking is the three As: abstraction, automation, and analysis.
  • Decomposition is a fundamental concept in computational thinking, representing the process of systematically breaking down a complex problem or system into smaller, more manageable parts or subproblems.
  • Logical thinking and pattern recognition are computational thinking techniques that involve the process of identifying similarities among and within problems.
  • Abstraction is a computational thinking technique that centers on focusing on important information while ignoring irrelevant details.
  • Algorithms are detailed sets of instructions to solve a problem step-by-step.
  • Testing and debugging is about finding and fixing mistakes in the step-by-step instructions or algorithms used to solve a problem.

2.2 Architecting Solutions with Adaptive Design Reuse in Mind

  • Computational thinking commonly employs a bottom-up strategy for crafting well-structured components.
  • A business solution architecture is a structural design that is meant to address the needs of prospective solution users.
  • Business solutions are strategies/systems created to solve specific challenges in a business. Designing business solutions can be described as a complex systemic process that requires expertise in various spheres of technology as well as the concerned business. A blueprint is a detailed plan or design that outlines the structure, components, and specifications of a building, product, system, or process.
  • Two heuristics are inherent to the design of business solutions and the creation of business solution architectures. Layering in business solution architecture involves creating distinct layers that abstract specific aspects of the overall architecture. The layering approach relies on the principle of separation of concerns. The presentation layer holds the user interface (UI) that interacts with the outside world.
  • User experience (UX) refers to the overall experience that a person has when interacting with a product, service, or system.
  • A monolithic structure is a system or application architecture where all the components are tightly integrated into a single unit.
  • Enterprise-level architecture encompasses various domains that define the structure, components, and operations of an entire organization. Enterprise architecture (EA) views the enterprise as a system or a system of systems.
  • The enterprise business architecture (EBA) is a comprehensive framework that defines the structure and operation of an entire organization. A business model is a framework that outlines how a business creates, delivers, and captures value. The organizational model is the structure and design of an organization, outlining how roles, responsibilities, and relationships are defined.
  • The business process is a series of interrelated tasks, activities, or steps performed in a coordinated manner within an organization to achieve a specific business goal.
  • Location model refers to a set of rules used to analyze and make decisions related to the positioning of entities, activities, or resources.
  • The enterprise technology architecture (ETA) is a comprehensive framework that defines the structure, components, and interrelationships of an organization’s technology systems to support its business processes and objectives.
  • The application architecture is a subset of the enterprise solution architecture.
  • A data architecture model is a conceptual framework that outlines how an organization structures, organizes, and manages its data assets.
  • Data modeling is the collaborative process wherein IT and business stakeholders establish a shared understanding of essential business terms, known as entities.
  • Architecture views are representations of the overall system design that matter to different stakeholders.

2.3 Evolving Architectures into Useable Products

  • The combination of top-down, adaptive design reuse and bottom-up, computational thinking optimizes modern software development.
  • Model-View-Controller (MVC) is a software architectural pattern commonly used in the design of interactive applications, providing a systematic way to organize and structure code.
  • The adaptive design reuse approach is a strategy in software development that emphasizes the efficient reuse of existing design solutions to create new systems or applications.
  • World Wide Web Consortium (W3C) is an international community that develops guidelines to ensure the long-term growth and accessibility of the World Wide Web.
  • Web 2.0 is the second generation of the World Wide Web when we shift from static web pages to dynamic content.
  • Web 3.0 is the third generation of the World Wide Web and represents a vision for the future of the Internet characterized by advanced technologies.
  • A web application (web app) refers to a software application that is accessed and interacted through a web browser over the Internet.
  • Blockchain is a secure and transparent way of recording transactions. It uses a chain of blocks, each storing a list of transactions.
  • Microservices is a way of building software by breaking it into small, independent pieces. Each piece, or service, does a specific job and works on its own.
  • Migrating legacy business solutions means upgrading or replacing old systems with newer, more efficient ones.
  • Innovative cloud mashups refer to creative combinations of different innovative business solutions that leverage disruptive technologies.
Citation/Attribution

This book may not be used in the training of large language models or otherwise be ingested into large language models or generative AI offerings without OpenStax's permission.

Want to cite, share, or modify this book? This book uses the Creative Commons Attribution License and you must attribute OpenStax.

Attribution information
  • If you are redistributing all or part of this book in a print format, then you must include on every physical page the following attribution:
    Access for free at https://openstax.org/books/introduction-computer-science/pages/1-introduction
  • If you are redistributing all or part of this book in a digital format, then you must include on every digital page view the following attribution:
    Access for free at https://openstax.org/books/introduction-computer-science/pages/1-introduction
Citation information

© Oct 29, 2024 OpenStax. Textbook content produced by OpenStax is licensed under a Creative Commons Attribution License . The OpenStax name, OpenStax logo, OpenStax book covers, OpenStax CNX name, and OpenStax CNX logo are not subject to the Creative Commons license and may not be reproduced without the prior and express written consent of Rice University.