2.1 Computational Artifacts

What is a Computational Artifact?

A computational artifact is anything created by a human using a computer. It is a product of computational thinking and problem-solving. Computational artifacts can be:

• Programs / Software — desktop apps, mobile apps, games
• Digital Media — images, audio files, videos, animations
• Documents & Presentations — spreadsheets, slide decks, web pages
• Databases — structured collections of data
• Algorithms — step-by-step procedures encoded in software (e.g., AI models)

---

Why Create Computational Artifacts?

Creating artifacts allows individuals to:

1. Solve real-world problems — e.g., a budgeting app that automates calculations.
2. Express creativity — e.g., digital art, music production software.
3. Communicate ideas — e.g., a website or social media platform.
4. Collaborate — e.g., shared documents, version-controlled codebases.

---

The Development Process

Creating a quality computational artifact is rarely a one-step process. It follows a structured cycle:

1. Analysis

Identify the problem or need. Define requirements: What should the artifact do? Who will use it?

2. Design

Plan the solution using tools such as:

• Pseudocode — plain-language description of the algorithm
• Flowcharts — visual representation of logic and flow
• Wireframes — layout sketches for user interfaces

3. Development (Coding)

Translate the design into a working artifact using a programming language or digital tool.

4. Testing

Verify that the artifact works correctly. Types of testing include:

• Unit testing — testing individual components
• Integration testing — testing how components work together
• User testing — real users interact with the artifact

5. Iteration

Iteration is the process of repeatedly refining and improving the artifact based on testing results and user feedback. Each cycle produces a better version until the artifact meets its goals.

Analyse → Design → Develop → Test → Refine → (repeat)

---

Complexity of Artifacts

Complex artifacts are typically built by teams, use modular design (breaking the problem into sub-problems), and go through many iterations.

---

Computational Thinking Connection

Creating artifacts requires the four pillars of computational thinking:

• Decomposition — break the artifact into smaller, manageable parts
• Pattern Recognition — identify reusable solutions
• Abstraction — focus on essential features, hide unnecessary detail
• Algorithm Design — define the step-by-step logic the artifact will follow