Julian.Kellett

Employee.Details_Plus

by

Purpose The Employee.Details_Plus view extends the foundational Employee.Details dataset, offering enriched employee data for segmentation, reporting, and integration across organisational systems. It consolidates employment, organisational, and job-related details into a comprehensive, consistent format to support analytical and operational needs. Use Case Owner: Sam Jopson-WhiteTypical Use Case: Integration with fact tables for enhanced reporting and analysis, such as … Read more

Project.Revenue_History

by

Purpose For the calculation of Project Baseline Costs/Revenue Use Case Owner: Martyn ColeTypical Use Case: Project Reporting PortalStyle: Fact Code & Source related to Project.Cost(History) Source WHERE [ELEMENT_TYPE_DB_KEY] = ‘REVE’ Key Parameters CompanyProjectCustomer Sample Exec Response SEQ Dates Entity Measures Codes Project Other Codes

Project.Cost_History

by

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

by

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

by

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

by

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

by

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