Skip to content

Product Vision

Jump to bottom
Keito404 edited this page Sep 18, 2018 · 4 revisions

  1. Executive Summary

    SwinGardenPlanner is a sophisticated garden planner for people who have gardens who want to keep track of the plants in their garden. Unlike Garden planning books our Planner gives you personal suggestions according to users own atmosphere.

  2. Problem:

    People having trouble managing their garden due to the busy lifestyle and having no knowledge in garden decoration & design.

  3. Initial architecture:

    Initial Architecture

  4. Scope/initial requirements:

    • GARDEN AREA INPUT (WIDTH x HEIGHT)
    • BUDGET INPUT
    • NAME OF GARDEN INPUT
    • A LIST OF EXISTING PLANTS + PRICE + SEASON.
      • ADD PLANTS TO THE LIST (NAME + PRICE + SEASON).
      • REMOVE PLANTS OUT OF THE LIST.
      • MOVE PLANTS AND AVOID THE CONFLICT (2 PLANTS IN THE SAME LOCATION). *A LIST OF EXISTING TOOLS (OR GEARS)
      • ADD TOOLS TO THE LIST (NAME + PRICE).
      • TOOLS WILL HAVE A WEAR FACTOR (OPTIONAL)
    • SORTING PLANTS BY GROUPS, CURRENT BUDGET, SIZE, SEASONS.
    • PLANT RECOMMENDATION DEPENDS ON AREA SIZE.
    • DISPLAY CURRENT PLANTS IN THE AREA.

  5. Release plan:

    The project will be divided into 3 iterations (2 weeks each). Iteration 1 is going to start at 20/09/2018 Release Plan

  6. Risks:

    • Lack of time management can lead to exceeding the due date.
    • Over-stating requirements may cause unnecessary workload commitments
      • Building on that, construction of a GUI for the program may be particularly time-consuming, despite its effectiveness.
      • Under-stating requirements may also lead to an unfinished or unpolished product.
    • Lack of task management can delay and prolong group work.
    • Unclear objectives can result in unwanted outcomes.
    • It can be difficult to split tasks evenly for a large group.
      • This can force team members to take on roles or tasks they do not want to undertake, going against DAD.

  7. Assumptions:

    • The system can provide information to the user on the types of plants that are known.
    • The system will have a menu to navigate through different functions.
    • The system assumes the user knows what the current season is.

  8. Software development process:

    The process for development will use the Disciplined Agile Delivery (DAD) process.

  9. Other project details (where applicable):

    • Communication between the team will occur over Slack
    • The team meetings will be held over Discord
    • Toggl can be utilised for team meetings
    • Trello will be utilised for task management
    • GitHub will be used for version control
Clone this wiki locally