Computing Tech
These are things your app must do — its core functions or features.
They answer: What should the app be able to do?
Examples:
Users can log in and sign up
Users can add tasks
Users can view study methods
A timer works when clicked
Think of it like: what the system MUST do?
These are things about how well your app performs or looks — not what it does.
They answer: How should the app behave or feel?
Examples:
The app is easy to use (user-friendly)
It looks clean and not cluttered
It loads quickly
It works on phones and tablets
Think of it like: “Is it smooth, fast, and easy to use?”
—---------------------------------------------------------------------------------------------------------------------
Functional criteria: What the system must do (e.g. login, search, send messages).
Non-functional criteria: How the system should be (e.g. fast, secure, easy to use).
_________________________________________________________________________
Focus: How a user feels when interacting with a product.
Goal: To create a smooth, intuitive, and satisfying experience.
Includes:
Usability
Accessibility
Information architecture
User research & testing
Journey mapping
Example: A food delivery app that makes it easy to find meals, place orders quickly, and receive timely updates.
Focus: The visual layout and interactive elements of a product.
Goal: To design an aesthetically pleasing and functional interface.
Includes:
Buttons, icons, menus
Typography, color schemes
Spacing and layout
Animations and transitions
Example: The color of a "Buy Now" button, the font used in menus, and how screens transition.
UX is how it works.
UI is how it looks.
Databases?
Databases are organised collections of structured data stored electronically. Designed to be easily accessed, updated, and managed.
Row ID, purpose, and what?
A value that uniquely identifies a row in a table.
What does WCAG stand for?
Web content accessibility guidelines
Bandwith meaning?
Is the maximum amount of data that can be sent over the internet in a certain amount of time.
Whats the importance of using small files?
Reduces download time, and saves bandwidth. Leads to better performance and better UX.
Faster loading times
Less storage use
Lower date costs
Better performance
Lossless and lossy compression?
Lossless compression keeps all the original data, so when you open the file again, it's exactly the same as before.
Lossy compression removes some data to make the file smaller, but this can cause a slight drop in quality (like blurrier images or lower sound quality).
Test case and use case?
Use Case: how a user interacts with a system. What the user wants to do.
- e.g., user logs in to check messages
Test case:how to test if the system works correctly
- Enter login info, click login, check if inbox shows
Test 2: 14/20 = 70%