Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software System
Operability Best Practices
What are Operability Best…
Software System
Operability Best Practices
What are Operability Best Practices?
Good operability means making routine tasks easy, allowing the operations team to focus their efforts on high-value activities
Why should we care?
Getting this right at the design stage (by feeding in as requirements) means better chance of success from the outset
Monitoring and Alerting
-
-
-
-
Usage - this shouldn't be underestomated - knowing who, what, when and why things are being used drives decsions - but also helps undersatnd what is happening and potentially why
-
-
-
-
-
-
-
-
-
-
-
Fitness? How do we know that a software system is still fit for purpose? How can we test a software system to ensure it is still fit for purpose.
With the appropriate tests we can demonstrate that work needs to be done, or it needs to be decom'd
Having Fitness Tests could avoid the long tail
-
-
-
-
-
Knowledge - you could say that having answers to all of these means we have full knowledge of the whole software system
Brain dump of areas that should have a minimum set of requirements that I&C can provide to the rest of the business to ensure services are 'production ready'
Concept being that if the software system is designed with this in mind then we would need to employ less blue tack and sticky tape and ineffective process after the fact
These could also be gates for any acceptance of new software systems into production
This would mean move to production and therefore service to customers is much improved
Where should this reside, LeanIX? ServiceNow? Federated across multople systems? Ideally somewhere that Ops can get to easily and that can be used programmatically to add context to dashboards, alarms etc :question: