Kavca / dementia-akm-models

Repository for Models for the Dementia treatment project
Apache License 2.0
0 stars 0 forks source link
akm consept dementia modelling

| Readme | Project | Upload models | About |

Kavca Dementia Models

Click on the links below to open the models in AKM Modeller:

Introduction

Why (Reasons for Treating Dementia)

Who (Involved in Dementia Treatment)

What (Aspects of Dementia Treatment)

How (Approaches to Dementia Treatment)

Where (Settings for Dementia Treatment)

When (Timing for Dementia Treatment)



Project Methodology

Desing Thinking The Design Thinking process is a user-centric approach to problem-solving that typically involves five phases. It's widely used in various fields, including software development, product design, and business innovation. Here's an overview of each phase: - Empathize: This initial stage involves understanding the users' needs, experiences, and motivations. It often includes observing and engaging with users to gain insights into their behaviors and attitudes. This phase is crucial for establishing empathy with the users, which is a key aspect of Design Thinking. - Define: In this phase, the insights gathered during the Empathize stage are synthesized into a clear problem statement. This is where you define the core problem you are trying to solve, often in the form of a user-centered problem statement. It sets a clear direction for the project. - Ideate: Once the problem is defined, the Ideate phase involves generating a wide range of creative ideas to address the problem. This is often done through brainstorming sessions and other ideation techniques. The goal is to explore a broad solution space and think outside the box. - Prototype: The ideas generated during the Ideate phase are turned into tangible prototypes. These prototypes can range from simple paper models to more sophisticated digital or physical creations. The purpose of this phase is to create a physical or digital representation of the solutions to explore their potential. - Test: In the final phase, the prototypes are tested with real users. This involves observing how users interact with the prototype and gathering feedback. The testing phase is crucial for understanding the viability of the proposed solutions and for making iterative improvements based on user feedback. Throughout the Design Thinking process, iteration is key. Based on feedback and insights gained, teams often cycle back to earlier stages to refine their understanding of the problem or to explore new solution ideas. This iterative approach ensures that the final solution is deeply aligned with user needs and has gone through rigorous refinement and testing.

Lean Startup

Build the right Thing!

This is where we build Typedefinition_TD models based on the suggestions in the Concept model in previous step.

Lean Startup (Generated by ChatGPT) Lean Startup process emphasizes the importance of flexibility, quick iterations, and customer feedback in the development of products or services. The process consists of several key components: - Build-Measure-Learn Loop: This is the fundamental cycle at the heart of the Lean Startup method. The idea is to turn ideas into products (Build), measure how customers respond (Measure), and then learn whether to pivot or persevere (Learn). This cycle helps startups to quickly test their hypotheses and make adjustments based on real-world feedback. - Minimum Viable Product (MVP): An MVP is a version of a new product that allows a team to collect the maximum amount of validated learning about customers with the least effort. It's not necessarily the smallest or simplest version of the product, but the one that enables a full turn of the Build-Measure-Learn loop with a minimum amount of effort and time. - Validated Learning: This concept emphasizes the importance of learning about what customers actually want and will pay for, rather than what you assume they will want. This is achieved by testing a series of MVPs, each designed to test specific hypotheses about the product and the business model. - Pivot or Persevere: Based on the feedback and data gathered from the MVPs, startups decide whether to pivot (make a fundamental change to the product) or persevere (continue with the current strategy). Pivoting is not seen as a failure but as a necessary part of finding the right product-market fit. - Continuous Deployment and Innovation Accounting: Lean Startup encourages rapid and continuous deployment of products to accelerate learning and innovation. Alongside this, innovation accounting is used to track progress, set up milestones, and prioritize work. This helps startups to make more informed decisions about when to pivot and when to persevere. Overall, the Lean Startup methodology is about being more adaptive, customer-focused, and iterative in developing products and services. It's particularly well-suited to the uncertain and fast-changing environments that startups often operate in.

Agile development

Build the Thing Right!

Here is where we build the Solution model and generate/configure Solutions (GraphQL/Database schemas etc.)

Agile development (Generated by ChatGPT) Agile development is a methodology that prioritizes flexibility, collaboration, customer feedback, and rapid iteration in the development of software products. Originating from the Agile Manifesto, it contrasts with traditional waterfall methods by being more adaptive and responsive to changes. Here’s an overview of its key components: - Iterative Development: Agile development is characterized by short, iterative cycles called sprints, typically lasting from one to four weeks. Each sprint aims to produce a working increment of the product, allowing for frequent reassessment and adaptation of plans. - Collaboration and Cross-Functional Teams: Agile emphasizes close collaboration between cross-functional teams, which often include developers, designers, and business stakeholders. Daily stand-up meetings (or scrums) are common, where team members discuss progress, plans, and obstacles. - Customer Involvement and Feedback: Agile methods strongly advocate for regular customer involvement and feedback. This can take the form of user stories to define requirements, reviews at the end of each sprint, and frequent releases to gather real-world user feedback. - Adaptive Planning: Agile teams plan iteratively and adaptively. While there's an overarching vision or roadmap, detailed planning is only done for the current and next sprint. This flexibility allows teams to respond to changes and new information quickly. - Continuous Improvement: Regular retrospectives are a key part of Agile. After each sprint, the team reflects on what went well and what could be improved. This continual reassessment aims to enhance efficiency and effectiveness over time. - Working Software as a Primary Measure of Progress: In Agile, the primary measure of progress is the delivery of working software. The focus is on creating software that is functional and adds value to the customer, rather than strictly adhering to a predefined plan. - Sustainable Development: Agile promotes sustainable development practices. The goal is to maintain a consistent pace and avoid burnout, ensuring that the team can continue to deliver high-quality work indefinitely. Agile methodologies include various frameworks like Scrum, Kanban, and Extreme Programming (XP), each with its own specific practices and tools but sharing the core principles of the Agile Manifesto. Agile is widely adopted in the software development industry due to its flexibility, efficiency, and focus on delivering tangible, customer-centric results.