Revenue Critical Software
Revenue critical software requires a detailed and rigorous process to best assure that the final product is correct and as reliable as possible. Omnicon’s process is based on stringent guidelines of widely accepted software development documents which address the entire life cycle process for software intended for the most critical or vital applications.
Safety-Critical Systems are essential for detecting and mitigating abnormal hazards. Examples include x-ray control software, fire detection systems, and train signaling systems.
Mission-Critical Systems are essential to executing and completing a major objective. Examples include propulsion systems, defibrillators, and power grid control systems.
Revenue-Critical Systems are essential for maintaining a normal flow of money. Examples include transaction processing software, production line test equipment, and satellite communication systems.
Omnicon Software Engineers Apply Skills to Every Part of the Software Life Cycle
- Requirements Analysis
- System Design (Architecture, Hardware/Software Partitioning, Timing and Sizing)
- Top Level Design (Systems, Units, Components)
- Detailed Design (Object Oriented Design Capture, Algorithms)
- Code (Real Time, Multi-Tasking, Input Data Driven, Event Driven)
- Independent Audits and Reviews
- Integration, Test, and Debug
- Verification and Validation
Omnicon Analyzes Critical Software to Improve Products
A critical system performs essential operations and must therefore be designed and built to provide highly reliable service. Even if a failure occurs, a critical system must still operate in some fashion so that essential operations can continue until repairs can be completed. To minimize occurrence of failures and their effects on system operations, Omnicon performs several kinds of analyses on critical system software, to determine:
- System-level consequences of each possible kind of failure (Functional Hazard Analysis)
- Potential underlying causes and likelihoods of such failures (Fault Tree Analysis)
- System-level effects and consequences of software failures (Software Failure Modes, Effects, and Criticality Analysis)
- Methods and effectiveness for ensuring continued operations in the event of critical system failures. Examples include design for operation in degraded modes, design to allow human takeover, and use of backup systems
admin January 5, 2016