Software engineering

Software process

a structured set of activities involved in developing a software system

Waterfall model

a plan driven process with separate and sequential phases

Incremental development

development where specification, implementation and validation are interleaved

Integration and configuration

building systems by assembling existing configurable components

Software engineering

the systematic application of engineering approaches to the development, operation and maintenance of software

Software architecture

the high-level structure of a system including components and their interactions

Problem definition

define what problem the AI system should solve and what success means

Data collection

gather relevant data from sources such as logs, sensors, databases or users

Data labeling (ML)

assign correct labels or annotations to data

Data cleaning

remove noise, errors, inconsistencies, duplicates and missing values

Feature engineering (ML)

select, transform or create features that help the model learn patterns

Model selection

choose an appropriate machine learning algorithm or model

Model training

train the model using the prepared data to learn patterns

Model evaluation

access model performance using metrics and test data

Deployment and monitoring (ML)

deploy the model in real use and continuously monitor performance and behavior

State of the asset

processing, transmission, storage

Vulnerability types

confidentiality, integrity and availability

Assurance types

weak encryption, poor authentication, malware, bugs

Software construction

implementation of the system through coding

Software design

high-level planning of system structure and behavior

Why MVC

to improve separation of concerns

Publish-Subscribe

components publish events without knowing subscribers and subscribers receive events asynchronously, enabling loose coupling

Request-Reply

A client sends a request to a server and waits for a corresponding response

N-versioning

multiple independent versions of the same component are executed in parallel to improve fault tolerance

Elicitation

discovering and gathering requirements from stakeholders and other sources

Documentation / specification (RE)

the activity of clearly writing and structuring requirements

Validation (RE step)

checking that the documented requirements are correct, complete, consistent and reflect stakeholder needs

Change and management (RE)

handling requirement changes over time while maintaining consistency and traceability