Assumptions and Constraints
Constraints
- Available human resources for the project
Title | Person | Role |
---|---|---|
Engineering Manager | Christiaan Nagel | Responsible for software development lifecycle, agile/scrum implementation, resource management, project management, team management, best practices, technical guidance, and oversight as well as cross-functional collaboration between team leads, communication internally and externally. Responsible for product requirement document. Administrator of Azure cloud resources. |
Back-end Team Lead | Lukas Kok | Responsible for APIs for integrations, middleware, models, views, and controllers. |
Database administrator | Wayne Swanepoel | Responsible for data compliance, normalization of tables, data integrity. |
Azure Cloud Architect | Christiaan Nagel, Lukas Kok | Responsible for resource groups security groups, virtual networks, resources and peering. |
System Architect | Christiaan Nagel, Lukas Kok | Responsible for technical requirement documentation (Solution strategy, tech stack, deployment diagrams, build views, runtime views, use cases, user story flow, context/container/component, and code breakdowns) |
Front-end Team Lead | Christiaan Nagel | Responsible for user interface build and integration with the backend. |
Product Owner | Malik Stuurman | Relay product vision, establish backlog, and prioritize tickets. |
Scrum Master | Christiaan Nagel | Scrum principles and practices, removing impediments, timelines, epics. |
Designer | Janico Steyn | Responsible for Figma user interface design and UI/UX experience/flow. |
Must integrate with Azure Cloud Provider.
Embedding Models constrain us with the number of tokens that can be used, and the models have certain limitations to what is possible.
Must use Azure Active Directory for SSO (Need to be made principle of the cloud resource to register app to assign Azure Active Directory to it. This might be a bottleneck at IT and security policy. As a contingency, implement just normal email and password at first.)
Must comply with GDPR (UK) and POPIA (South Africa) regulations for data protection and privacy.
Project budget is fixed and must cover all aspects of development, deployment, and initial maintenance.
Project must be completed within a specific time-frame, limiting the scope of features and the extent of testing and fine-tuning.
System must be compatible with existing IT systems and workflows within the law firm.
Must adhere to data retention and purging policies, specifically Azure's 48-hour retention policy for anonymised data.
System must meet performance benchmarks for response time and throughput.
Availability of key personnel may be limited by their involvement in other projects or responsibilities.