Project.Cost_History

Purpose For the calculation of Project Baseline Costs/Revenue Use Case Owner: Martyn ColeTypical Use Case: Project Reporting PortalStyle: Fact Data Marts CompanyProjectCustomer Code & Source related to Project.Revenue(History) Source FACT_PROJECT_HISTORY_LOG_OL Where Sample Exec Response SEQ Dates Measures Transaction Hours Cost Codes SQL

Employee.Hours

Purpose The Employee Hours fact table is designed to display quantitative data related to employees. This table integrates with dimension tables, such as Employee_Details, to provide detailed insights into various aspects of employee performance, compensation, and other metrics. The primary purpose is to support data-driven decision-making across the organisation. Use Case Owner: Sarah MartinoTypical Use Case: Calculation … Read more

Avoiding Architectural Debt

In Agile design, teams work in short sprints and prioritise the most important features to be developed first. Value-based prioritisation allows startups to get a Minimal Viable Product (MVP) to market quickly and start gathering feedback from customers. Additionally, and by definition, Agile design encourages safe-to-fail experimentation early on in the product’s lifecycle, giving the designer quick … Read more

How Unarticulated Needs Direct the Evolutionary Path of Agile Designs

The traditional design methods, which assume that developers fully understand the user’s requirements and that the user knows what they want before seeing the product, are often flawed in the real world. Complex systems, such as software products and their users, constantly evolve and adapt to users’ changing needs and preferences. As users interact with a software product, … Read more

A Measure of Good Design

A measure of good design is how dependent higher structures are on lower ones, and this is closely related to the principle of separation of concerns and cohesion. Cohesion is a measure of how closely the elements of a module or component work together to achieve a single, well-defined purpose. When a system is well-designed, the higher structures … Read more

Small Cross-Functional Teams Drive Agile Design

Distributed large teams can face several challenges when producing Agile architecture. One of the main challenges is communication and coordination. Team members may be located in different locations and time zones and have different cultural backgrounds. These factors make having regular meetings, sharing information, and collaborating on design decisions difficult. Additionally, distributed teams may have difficulty building trust and developing a … Read more

Hierarchical Structures and Constant Regeneration

A hierarchical system facilitates evolution and constant regeneration by allowing for modularity and flexibility in its design. The system is divided into several layers, each building upon the one below it. This structure allows individual components within each layer to be modified or replaced without affecting the overall system’s functionality. In software design, this concept … Read more

Antifragility, Evolution, Innovation and Agile Design

Agile design, evolution in living organisms, and antifragility share similarities in how they approach problem-solving and adapting to change. Evolution is a process by which organisms adapt to changing environments through: The ability of an organism to adapt and evolve is critical to its survival and success. Similarly, Agile design is based on the principle of … Read more