Skip to content
Gallery
Software Design and Development
Share
Explore
Week 4

Evidence of Learning

Screen Designs

Factors Affecting Language and Technology Selection

Hardware and Software Selection

Q1. The benchmark system used was PugetBench, a benchmarking utility that displays performance in Adobe Premiere Pro.
The benchmark results displayed that the M1 Ultra Mac Studio is usually beaten by more affordable home-built desktop PCs, except when given more specific and highly CPU intensive tasks, like dealing with RED footage or using CPU-heavy VFX. The M1 Max Mac Studio is more of a value offering, and beats similarly priced PCs. However, this article doesn’t test energy consumption, noise, and heat of the systems. These aspects are generally always in favour of the Apple Silicon desktop systems (and windows laptops are entirely out of the question here for being on par with Apple Silicon MacBooks as video editing machines). (definitely no bias here promise)
Q2. Software benchmarking is the act of running intensive workloads to determine the performance of a system in a particular piece of software or in a general range of tasks. For example, Geekbench tests CPU performance, 3DMark tests graphical performance, and the PugetBench line of benchmarks tests general performance in specific software, like Premiere Pro or DaVinci Resolve.
Q3. The table benchmarks a search program, and displays the time difference between a binary and linear search. The benchmark results display that linear searches are better for smaller databases, benchmarking 3 seconds faster than a binary search. The benchmark also displays that binary searches are much better than linear searches for large databases, with the binary search being 73 seconds faster than a linear search.

Language Selection

Q1. Operating system/hardware support (eg. Swift for iOS, Kotlin for Android), feature set, ease of use, control over hardware (eg. Assembly for low-level programming).
Q2. Requires an event to occur during execution. Usually involves the mouse, buttons, and menus.
Q3. All instructions are executed in a linear order. This takes places from the top and moves through translating and executing each instruction.
Q4. A program might not require a GUI if it is designed for experienced/professional users (eg. Docker for sysadmins, Git for developers both primarily use a CLI), or if it needs to be automated (eg. bash scripts or Ansible playbooks).

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.