2. Architecture Constraints
Any requirement that constrains software architects in their freedom of design and implementation decisions or decision about the development process. These constraints sometimes go beyond individual systems and are valid for whole organizations and companies.
2.1. Technical Constraints
| Constraint | Explanation |
|---|---|
C1.1 |
The system must be developed using technologies compatible with the existing infrastructure. |
C1.2 |
Other systems in the organization’s ecosystem are developed using React, and React is the preferred technology for Dastan AdTech platform. |
C1.3 |
Integration with third-party analytics tools must be done using RESTful APIs, and the choice of third-party tools is limited to those with a proven track record of security and reliability. |
C1.4 |
The architecture must support horizontal scalability to accommodate hundreds of thousands of concurrent users during peak usage. |
C1.5 |
The smart contract will be deployed on the Arbitrum blockchain, which constrains it to the Ethereum Virtual Machine (EVM) and Solidity programming language. |
C1.6 |
Web3Sense will be used to provide deep and actionable insights about creators to help advertisers make informed decisions. |
2.2. Organizational and Political Constraints
| Constraint | Explanation |
|---|---|
C2.1 |
Development and maintenance costs will adhere to the allocated budget, influencing technology choices and development processes. |
C2.2 |
The system must comply with regional data privacy regulations, such as GDPR, influencing how user data is collected, stored, and processed. |
2.3. Conventions
| Constraint | Explanation |
|---|---|
C3.1 |
Developers must adhere to the established coding standards, including code formatting, naming conventions, and documentation practices. |
C3.2 |
The system follows semantic versioning (SemVer) for releases, with clear guidelines on how version numbers are incremented. |