If the expected system's life is short, it may be not worthwhile to focus on:

• Optimisation for maintainability: too much documentation, focus on understandability of the internal design
• Extensibility: when the system requirements will change, the time may come to replace the system entirely, not just to modify it

On the other hand, it may be worth to pay extra attention to the flexibility of integration of the system with other systems: see ‣.

When considering improving a system (e. g. reduce an alert rate, improving metrics), consider the ROI with the expected system's life in mind.

One of the ‣.

Related:

• Design for change: consider requirement's half-life
• ‣
• Keep design simple

Contra:

• ‣
• ‣

References

‣ Requirements have a half-life time.