2  PSM

flowchart TD
    A[Problem-solving methodology]
    
    A --> B[Analysis]
    A --> C[Design]
    A --> D[Development]
    A --> E[Evaluation]

    subgraph Analysis_Activities
        direction LR
        F[Solution requirements]
        G[Solution constraints]
        H[Solution scope]
    end
    B --> Analysis_Activities

    subgraph Design_Activities
        direction LR
        I[Solution design]
        J[Evaluation criteria]
    end
    C --> Design_Activities

    subgraph Development_Activities
        direction LR
        K[Manipulation]
        L[Validation]
        M[Testing]
        N[Documentation]
    end
    D --> Development_Activities

    subgraph Evaluation_Activities
        direction LR
        O[Evaluation Strategy]
        P[Solution evaluation]
    end
    E --> Evaluation_Activities

    classDef default fill:#fff,stroke:#00bfff,stroke-width:2px;

2.1 PSM with Godot

2.1.1 Statement of Intention

2.1.1.1 Name of Project:

Provide the title of your project.

2.1.1.2 Who is your client or organisation?

Identify the individual or organisation for whom you are developing this project.

2.1.1.3 How are you going to make ongoing contact with this person or organisation?

Explain how you will maintain communication with your client throughout the project. This could include regular meetings, emails, or feedback sessions.

2.1.1.4 Give an overview of the need or opportunity you have identified.

Describe the problem or opportunity that your project will address. Why is this project necessary?

2.1.1.5 What data do you need to collect?

List the types of data you will need to gather to develop your project. This might include user requirements, preferences, gameplay data, or other relevant information.

2.1.1.6 What information do you hope to produce?

Explain what kind of information or output your project will generate. This could be game statistics, user progress, or other forms of data processing.

2.1.1.7 How do you anticipate you will solve this problem?

Outline your initial thoughts on how you will approach solving the problem using Godot. Consider the key features or mechanics you plan to implement.

2.1.1.8 List the programming you intend to do along with the data files you think you will need.

Detail the specific programming tasks you expect to complete. Include the types of data files you might use, such as images, sound files, scripts, or configuration files.

2.2 Analysis of PSM

In the analysis phase of the Problem-Solving Methodology (PSM), it is essential to thoroughly understand and define the project’s requirements, constraints, and scope. This ensures that the project remains focused and achievable within the given timeframe. In this section, we will explore these three critical elements in the context of a five-week Godot project.

2.2.1 Requirements

Requirements are the specific functionalities and features that the final Godot project must include. Clearly defining these at the outset ensures that the project meets its intended purpose and satisfies user needs. For a five-week Godot project, consider the following:

  • Core Features: Identify the essential gameplay mechanics or functionalities that must be present. For example, if you are creating a platformer game, the requirements might include player movement, level design, and basic enemy AI.

  • User Interface (UI): Determine the basic UI elements that the game needs, such as menus, score displays, or health bars.

  • Platform: Specify the target platform(s) (e.g., PC, mobile) to ensure compatibility.

  • Documentation: Identify any documentation requirements, such as a user guide or developer notes.

2.2.2 Constraints

Constraints are the limitations or restrictions that may affect the development process. Acknowledging these early can help in making realistic plans and setting achievable goals. For a five-week project, consider these common constraints:

  • Time: With only five weeks, time is the most significant constraint. Prioritise tasks to focus on the most critical aspects of the project first.

  • Resources: Assess the available resources, including team members, software (Godot), and hardware. Limited resources may require simplifying certain features or reusing existing assets.

  • Skill Level: Consider the skill level of the team members. If the team is less experienced, it may be necessary to scale down the complexity of the project.

  • Scope Creep: Beware of scope creep—adding new features or changes that were not initially planned. Stick to the original plan to avoid delays.

2.2.3 Scope

Scope defines the boundaries of the project—what will and will not be included. Clearly defining the scope helps manage expectations and ensures that the project is completed on time. For a five-week Godot project, the scope should be:

  • Focused: Limit the project to essential features that can be realistically completed within five weeks. Avoid trying to create a complex or large-scale game.

  • Achievable: Set goals that match the time available. For example, instead of creating a full multi-level game, you might focus on developing one well-designed level with polished mechanics.

  • Prioritised: Rank features by importance, ensuring that the most critical elements are developed first. Less critical features can be added if time permits.

  • Flexible: While the scope should be well-defined, allow some flexibility for adjustments based on feedback or unforeseen challenges during development.

2.2.4 Actions

Now that you have a clear understanding of the requirements, constraints, and scope for your Godot project, it’s time to put your analysis into action. Follow these steps to ensure your project stays on track:

  1. Create the Word Document: Begin by creating a Word document where you will record your analysis of the three areas. Use headings and subheadings to organise your thoughts clearly.

  2. Document Requirements: List out the specific features, functionalities, and any necessary documentation your project needs. Be as detailed as possible to avoid ambiguity later in the development process.

  3. Identify Constraints: Clearly outline the limitations you face, including time, resources, and skill levels. Understanding these constraints will help you make informed decisions throughout the project.

  4. Define the Scope: Set the boundaries of your project by defining what will and will not be included. Prioritise the essential elements to ensure you can deliver a completed project within the five-week timeline.

  5. Review and Refine: Once your document is complete, review it to ensure that your analysis is thorough and realistic. Make any necessary adjustments to your plan based on this review.

  6. Share with Your Team: If you are working in a group, share the document with your team members to ensure everyone is on the same page. Use this document as a reference throughout the project to keep everyone aligned.

By following these actions, you will have a solid foundation to guide your project from start to finish.