0% found this document useful (0 votes)
4 views4 pages

Software Engineering Chapter 10

The document evaluates the dependability of an online betting platform through a sociotechnical lens, focusing on five core dimensions: availability, reliability, safety, security, and resilience. It details the system's structure, including software, human, and policy layers, and proposes strategies for redundancy and diversity to prevent failures. Additionally, it emphasizes the importance of formal methods for verifying critical system components to ensure financial sustainability and user trust.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views4 pages

Software Engineering Chapter 10

The document evaluates the dependability of an online betting platform through a sociotechnical lens, focusing on five core dimensions: availability, reliability, safety, security, and resilience. It details the system's structure, including software, human, and policy layers, and proposes strategies for redundancy and diversity to prevent failures. Additionally, it emphasizes the importance of formal methods for verifying critical system components to ensure financial sustainability and user trust.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Name: Richard Ramashala

Student Number: 202306214

Module: System Dependability (Chapter 10)

System: Online Betting Platform

1. Introduction

Dependability is arguably the most essential attribute of any modern software system,
particularly those handling financial transactions and real-time data. In this context, a
dependable system is one that users can trust to operate correctly, predictably, and
consistently, even when individual components within the system experience failure. As
digital services become more integrated into our daily lives, many of these systems have
evolved into sociotechnical systems. This means they are not merely static pieces of code,
but rather complex, dynamic ecosystems that require the harmonious interaction of
software agents, human participants, administrators, and rigid organizational or legal
policies. This assignment evaluates an online betting platform through this sociotechnical
lens, analyzing its dependability based on five core dimensions: availability, reliability,
safety, security, and resilience.

2. Sociotechnical System Model

An online betting platform functions at the volatile intersection of high-speed technical


infrastructure and strict human regulation. To properly model this, we must recognize that
the system’s effectiveness is defined by the interaction between three distinct but
interdependent layers.

• The Software Layer: Includes the web/mobile interface, the core betting engine
responsible for real-time odds calculation, and the payment gateway that mediates
financial transfers.

• The Human Layer: Comprised of bettors who require 24/7 access to their accounts,
and administrators, including IT technicians, risk managers, and odds-makers—
who monitor for fraudulent activity.

• The Policy Layer: The governance framework that includes gambling commission
regulations, mandatory age-verification protocols, and internal algorithms designed
to detect and flag addictive gambling behaviors.

[DIAGRAM PLACEMENT 1: INSERT YOUR SOCIOTECHNICAL MODEL HERE]


3. Dependability Requirements

For a betting platform to be considered dependable, it must satisfy five rigorous


requirements. Failure in any of these areas typically results in lost revenue, legal liabilities,
or the permanent loss of customer trust.

• Availability: The platform must maintain high uptime, particularly during "Peak
Events" such as major football finals or global tournaments. Because betting is
time-sensitive, even a ten-minute outage during a high-stakes match results in
significant financial loss and user attrition.

• Reliability: This requires that every bet placed is recorded and processed exactly as
the user intended. If a user places a "last-minute" wager, the system must ensure
the bet is logged before the market closes, providing an accurate audit trail for both
the user and the platform.

• Safety: In a betting context, safety involves protecting the financial and


psychological well-being of the user. The system must implement "Bet Limits," "Self-
Exclusion" mechanisms, and data validation checks to prevent users from placing
erratic, accidental, or harmful wagers due to user interface errors or systemic
glitches.

• Security: As a high-value financial target, the system is constantly exposed to cyber


threats. The architecture must prioritize encrypted digital wallets, robust protection
against Distributed Denial of Service (DDoS) attacks, and advanced defenses
against SQL injection to ensure that sensitive user account and payment data
remain unreachable by malicious actors.

• Resilience: The system must be capable of recovering gracefully from failure. If the
primary transaction database fails due to an overwhelming surge in traffic, the
platform should be architected to automatically "failover" to a secondary node
without the user ever noticing a drop in service or a loss in their account balance.

4. Redundancy and Diversity Strategies

To prevent a single point of failure from causing a catastrophic system collapse, we apply
proven engineering principles of redundancy and diversity supported by design
justifications.

Redundancy (Hardware and Data Strategy) We propose the use of Active-Passive


Database Mirroring. In this configuration, every transaction processed by the primary
server is simultaneously written to a "Hot Standby" database located in a geographically
distinct data center.
• Design Justification: This strategy addresses the Resilience requirement. If the
primary data center experiences a power failure or hardware crash, the standby
database takes over operations immediately. For a betting platform, the loss of a
confirmed winning bet record is a legal and financial catastrophe; therefore,
hardware redundancy is a necessary investment for organizational integrity.

Diversity (Software and Process Strategy) We propose the use of Multi-Vendor Payment
Gateways. Rather than relying on a single financial API, the platform integrates three
independent gateways—such as Visa, PayPal, and Mobile Money—developed by entirely
different engineering teams.

• Design Justification: This strategy addresses Reliability and Availability. If a


specific software bug impacts the Visa payment gateway, the platform does not
suffer an outage, as users can simply switch to an alternative payment path.
Because these diverse systems are built on different codebases, they are
statistically unlikely to experience the same software bugs at the same time.

5. Formal Methods and Conclusion

Finally, we apply Formal Methods—mathematical verification techniques—to the most


critical logic gate in the system: the Payout Calculation Engine. By using mathematical
models to verify the system, we ensure that the logic is provably sound before it is
deployed. For example, we verify that a payout () is only triggered if the following logical
condition is met:

The justification for this approach is that manual testing cannot account for every possible
edge case in complex financial calculations. Formal verification mathematically
guarantees that "logic bombs" or rounding errors cannot occur, thus protecting the
platform’s financial sustainability.

In conclusion, by viewing the betting platform as a sociotechnical system, we ensure that


the software is not just technically efficient, but also socially responsible and legally
compliant. Through the strategic application of redundancy, diversity, and mathematical
rigor, we create a platform that users can rely on under even the most extreme operational
pressures.

You might also like