Unit 19 - KLO2

To ensure the software meets user needs and expectations

To reduce the overall project cost

To avoid unnecessary features

To speed up the coding process

Introduction

System Features and Requirements

External Interface Requirements

Source Code Implementation

To write technical code

To clearly define what a software system must do and how it must operate

To design the user interface

To test the software

The system must allow users to reset their password.

The system must load pages within 3 seconds on mobile devices.

The system must support multiple user roles.

The system must be available 99.9% of the time.

Users must be able to log in using national ID

The system must support Arabic as the default language

Users must be able to book, cancel, and reschedule appointments

The system must be available 24/7

Users must be able to log in using national ID

Users must be able to book appointments

The system must support Arabic as the default language

Users must be able to cancel appointments

To write code

To design interfaces

To define system needs clearly

To test the system

The system must be secure

The system must load quickly

The system must be reliable

Users can place orders

To impress developers

To reduce misunderstandings

To increase cost

To speed up coding

How a system works once it is live, including user actions and system responses.

How to design a new system from scratch.

How to market a software product.

How to write code for a system.

Step-by-step processes, user workflows, and simple descriptions of system behaviour.

Marketing plans and user testimonials.

Complex algorithms and code documentation.

Financial reports and business plans.

User selects a restaurant, user chooses items, payment is processed, restaurant confirms order, driver is assigned, order is delivered.

User writes a review, restaurant updates menu, driver refuels vehicle, app updates automatically.

System design

Day-to-day system use

Coding logic

Budget planning

UML diagrams

Error handling

Source code

Algorithms

They reduce development time only

They improve system reliability

They remove risks

They replace testing

To delay development

To increase cost

To select the best option

To confuse stakeholders

After coding

Before testing

Before development

After deployment

User needs

Programmer preference

Colour choice

File size only

Creativity

Realistic possibility

User satisfaction

Code quality

Technical

Economic/Budget

Schedule/Time

None of the answers.

Technical

Budget

Time

Schedule

Development

Design

Maintenance

Planning

It removes all risks

It controls system behaviour

It supports informed decisions

It replaces feasibility analysis

Fully custom software

Bespoke system

Off-the-shelf solution

Tailored platform

To eliminate all problems

To predict and reduce problems

To delay projects

To increase testing time

Late UI update

Minor bug

Slow animation

Data breach

Ignoring risks

Accepting failure

Reducing risk impact or likelihood

Removing requirements