Group 36

Trade-off

Software reuse

Number of users

Maintainability vs performance

By using unreliable programming techniques

By designing the system protection as a series of layers

By ignoring user behavior

By reducing system complexity

Making essential compromises

Optimizing everything

Avoiding any compromises

Choosing the most expensive option

By increasing system complexity

By having redundant components

By reducing testing procedures

By ignoring system failures

Creating software with unpredictable behavior

Minimizing the likelihood of system failures

Introducing bugs and vulnerabilities

Increasing system downtime

System availability and time to market

System downtime and cost reduction

User behavior and system complexity

Technologies used and components reused

By using unreliable communication methods

By isolating each component

By ensuring seamless interaction

By avoiding communication altogether

Each component being redundant

Each component being completely independent

Each component providing a subset of the overall system functionality

Each component providing the same functionality

Number of users

Software compatibility

Trade-off

Maintainability vs performance

Security vs usability

Maintainability vs performance

Availability vs time to market and cost

Software reuse