Preliminary Software Engineering
Unit 1 - Programming Fundamentals
Unit 1 - Programming Fundamentals
  • 1 - Programming Fundamentals
    • Programming Fundamentals Content
  • 2 - Python
    • Expected Python Knowledge
    • GitHub
    • Learning Python
    • Data Structures and File Management
      • Data Structures
        • Lists
        • Arrays
          • Single and Multi-Dimensional Arrays
        • Lists vs Arrays
          • Activities
        • Tuples
        • Sets
        • Dictionaries
          • Activities
      • File Handling
        • Loops, Lists, Dictionaries
        • Activities
  • 3 - Theory Content
    • Theory Content Explained
      • NESA Directional Verbs
      • Responding to Directional Verbs
  • 4 - Software Development and Management
    • Approaches to Software Development
      • Waterfall Model
      • Agile Model
      • Summary: Waterfall vs Agile
      • Activities
    • Software Development Steps
      • Sample Exam Question
      • Requirements Definition
        • Understanding the Need
        • Key Questions to Ask
        • Examples
        • Activities
        • Sample Exam Question
      • Determining Specifications
        • Functional Specifications
        • Non-Functional Specifications
        • Activities
      • Design
        • Top-Down Design Approach
        • Bottom-Up Design Approach
      • Development
        • Optimising Code
      • Integration
        • Example: Payment Program
        • Activity
        • Application Programming Interface (API)
          • Example: OpenWeather API
          • Example: WeatherAPI
          • Activity: Prepare Spells
      • Testing and Debugging
        • Test Data
          • Activities
        • Testing the System
          • Activities
        • Debugging
          • Types of Errors
            • Activities
          • Python Debugger
            • Activities
          • VS Code Debugger
            • Activities
      • Installation
        • Activities
        • Sample Exam Question
      • Maintenance
  • Charts and Algorithms
    • Example: IPO Charts and Pseudocode
      • Activities
    • Algorithms, Flowcharts, Pseudocode
      • Pseudocode Activities
      • Flowchart Activities
      • Sample Exam Questions
    • Structure Charts
      • Activities
      • Sample Exam Questions
    • Data Flow Diagrams
      • Activities
    • Data Dictionaries
      • Activities
    • Decision Trees
      • Activities
      • Sample Exam Questions
    • Gantt Chart
    • Class Diagrams
      • Sample Exam Question
    • Storyboards
      • Sample Exam Question
  • Testing and Debugging
    • Test Data
      • Activities
    • Testing the System
      • Activities
    • Debugging
      • Types of Errors
        • Activities
      • Python Debugger
        • Activities
      • VS Code Debugger
        • Activities
  • Computational Thinking
    • Decomposition
    • Abstraction
    • Activities
  • Version Control
    • Git
    • GitHub
    • Activities
  • Number Systems
    • Binary Systems
    • Hexadecimal Numbers
    • Using Two's Complement
    • Activities
  • 5 - Assessment Task 1
    • Data Science Project
      • Before we Start
        • Setting up GitHub Repository
        • Setting Up Markdown Documentation
      • Examples of API Usage
        • Starter Code: NASA Scenario
        • Starter Code: Spell Book
        • Starter: Pokédex Explorer
        • Starter Code: Weather App
        • Example: OpenWeather API
        • Example: WeatherAPI
        • Example: Prepare Spells
    • Task Guide
      • Requirements Definition
      • Determining Specifications
        • Use Cases
      • Design
        • Gantt Chart
        • Structure Chart
        • Algorithms
        • Data Dictionary
      • Development
        • Comments vs DocStrings
        • UI - main.py
        • Create Python Module
          • Example: NASA Module
          • Example: WeatherFetch Module
          • Example: SpellBook Module
      • Integration
        • Example: Pokedex
      • Testing and Debugging
        • Commit Changes
      • Installation
      • Maintenance
    • Submitting Your Task
Powered by GitBook
On this page
  1. Charts and Algorithms

Storyboards

PreviousSample Exam QuestionNextSample Exam Question

Last updated 3 months ago

PLEASE NOTE: There are NO ACTIVITIES for this as we will get to them a bit later, but feel free to look at the sample examination question if you are curious about what they might look like in an examination.

A storyboard shows the various interfaces (screens) as well as the links between them. In software engineering, particularly in the context of user interface (UI) and user experience (UX) design, a storyboard is a visual tool used to outline the flow of an application or website. It provides a clear, step-by-step representation of how users will interact with the system, highlighting the different screens they will see and the transitions between these screens based on user actions.

Each "frame" in a storyboard represents a specific interface, such as a login screen, a home page, or a settings menu, and shows how these screens connect through buttons, links, or other navigation elements. By mapping out the user journey in this way, storyboards help developers and designers visualise the structure of the application, ensuring a logical and intuitive flow.

Storyboards are essential in the early stages of software development as they provide a blueprint for the design and layout of the application's user interfaces. They help teams identify potential usability issues before any actual coding begins, allowing for early adjustments that can save time and resources later in the development process. For example, a storyboard might reveal that a certain task requires too many steps or that the navigation between screens is confusing or inefficient. By catching these issues early, developers can refine the user experience, making the application more user-friendly and accessible.

Additionally, storyboards facilitate effective communication among team members, stakeholders, and clients. They provide a simple, visual way to convey the design vision and user flow of the application, making it easier for everyone involved to understand and provide feedback. This collaborative approach ensures that the final product aligns with the intended user experience and meets the needs of the target audience. Moreover, storyboards can be used as a reference throughout the development process, serving as a guide for developers, designers, and testers to ensure consistency and coherence in the application's design and functionality.

Storyboards also play a crucial role in iterative design processes. As the development of an application progresses, storyboards can be updated to reflect changes and new ideas, allowing for a flexible and adaptive design approach. This iterative process helps teams continuously improve the user interface, incorporating user feedback and testing results to refine the application. By visualising each step of the user journey and the connections between screens, storyboards provide a comprehensive overview that helps developers and designers create cohesive and engaging user experiences.

Software Design Storyboard for School Canteen (From NESA Course Specifications)
UX Design Storyboard