8Manage Reliability & Fault Tolerance

8Manage Design for Workflow Safeness & Data Integrity

Automated Workflow with Policy Control

Clearly defining each step of a workflow, including responsibilities, control points, inputs, and outputs, to reduce ambiguity and ensure consistency.

Error Prevention & Validation

Implementing checks and validation rules to prevent incorrect data entry or actions that could lead to errors. Automated workflows often incorporate validation rules and conditional branching to ensure accuracy.

Monitoring & Alerting

Real-time monitoring of workflows to detect anomalies, bottlenecks, or security incidents and trigger alerts for immediate action.

4 Eyes Principle & Maker/Checker Mechanism

8Manage's maker/checker mechanism is a highly effective way to enhance data integrity. Here's why:

• Prevents human errors

It introduces a "four-eyes" principle, meaning that any data entry, modification, or transaction is reviewed and verified by a second, independent person (the checker) after being initiated by the first person (the maker). This significantly reduces the chance of errors, omissions, or discrepancies going unnoticed.

• Deters fraud & unauthorized activity

By requiring two separate individuals to approve a critical action, the maker/checker mechanism creates a robust control against internal fraud and unauthorized changes. No single person has complete control over a sensitive process, making it much harder for malicious activities to occur undetected.

• Enhances accountability & transparency

Each role (maker and checker) has distinct responsibilities, leading to clearer accountability. All actions are typically logged, creating an audit trail that shows who initiated what and who approved it. This transparency improves overall quality control and makes it easier to investigate any issues.

• Improves compliance

Many regulatory frameworks and industry best practices recommend or require segregation of duties and dual controls. Implementing a maker/checker mechanism helps organizations meet these compliance requirements, especially in fields like finance, healthcare, and data management.

• Increases data accuracy

By having a second person meticulously review the data, comparing it against source documents or predefined criteria, the accuracy of the data is greatly improved. This is crucial for maintaining reliable records and making informed decisions.

8Manage Design for Scalability & Fault Tolerance

8Manage supports the following levels of recovery to maximize the availability (uptime) of the system and minimize data loss even if a system crash or site disaster occurs:

Server Clustering

8Manage server clusters provide the raw computational, memory, and storage capacity to handle increased workloads through horizontal scaling.

Load Balancer Clustering

8Manage load balancer clusters intelligently manage and distribute incoming traffic across these server clusters, ensuring optimal performance, high availability, and the ability to scale resources dynamically to meet fluctuating demands.

Data Backup & Restore

Periodical backup of data to secondary storage automatically to minimize data loss if a system crash occurs.

Hot failover

8Manage supports different modes of hot failover such as Active-Standby mode and Active-Active modes to minimize system downtime or unavailability.

• In Active-Standby mode

The active server will be online and synchronize data to the standby server. At the same time, the standby server will monitor the status of the active server and activate itself when the active server crashes.

• In Active-Active mode

Both servers are online and provide the same services, it improves performance of the whole system and provides load balancing function.

Disaster Recovery

8Manage supports replication of data to an off-site location to overcome the need to restore the data (only the systems then need to be restored or synchronized).

8Manage Coding Standards & Practices

8Manage team is using the following coding standards and practices are fundamental to enhancing software reliability.

Consistent Coding Style

Ensure code is readable and maintainable.

Modular, Reusable Code

Promote code reusability and reduce duplication.

Design Patterns

Use established design patterns to solve common problems reliably.

Version Control Systems

Manage code changes effectively.

Code Review Processes

Conduct regular, thorough code reviews to identify defects, improve quality, and ensure adherence to standards. Involve multiple reviewers for diverse perspectives.

Automate Everything Possible

Reduce manual intervention and human error, accelerating responses to incidents. Focus on automating "toil" (repetitive, manual tasks).

8Manage Comprehensive Testing

8Manage Comprehensive Testing is a multifaceted process that evaluates the large-scale 8Manage applications for functionality, security, performance and user satisfaction within complex ecosystems. It's crucial for ensuring business continuity, handling high traffic, supporting various user scenarios, ensuring seamless integrations, and adhering to industry-specific regulations.

• ​​Functional gaps & misinterpretations of requirements
• Usability & User Experience (UX) issues
• Data entry problems, Incorrect data & reporting & Data integrity issues
• Performance & Operations issues
• Training & Documentation gaps

• ​​Missing/Incorrect requirements
• Incorrect workflows & data integrity issues
• Performance/Security/Usability/Compatibility/Reliability errors
• Installation/Configuration errors

• Interface/Communication/Functional errors
• Incompatible parameters/data structures
• Data flow errors
• Configuration errors
• Performance bottleneck at integration point

• Functional​​/Logical errors
• ​​Data conversion errors
• Boundary condition errors
• Exception handing errors

Unit Testing

• Functional​​/Logical errors

• Data conversion errors

• Boundary condition errors

• Exception handing errors

Integration Testing

• Interface/Communication/Functional errors

• Incompatible parameters/data structures

• Data flow errors

• Configuration errors

• Performance bottleneck at integration point

System Testing

• ​​Missing/Incorrect requirements

• ​​Incorrect workflows & data integrity issues

• Performance/Security/Usability/Compatibility/Reliability errors

• Installation/Configuration errors

Acceptance Testing

• Functional gaps & misinterpretations of requirements

• ​Functional gaps & misinterpretations of requirements

• Data entry problems, Incorrect data & reporting & Data integrity issues

• Performance & Operations issues

• Training & Documentation gaps