House Resource Management Software

Introduction

Software to manage the resources of a house in a cyclical closed-loop system.

Sub-component of the Village Resource Management Software.

House resources are defined as:

• Water
• Food
• Energy

Thus, a House, in the software can be thought of as a generic interface with the following methods:

• getWater()
• getFood()
• getEnergy()

Plant UML Source

@startuml
interface House {
  getWater()
  getFood()
  getEnergy()
}
@enduml

You may have several implementations of this generic House interface for different bio-regions.

For example, a mid-western house.

Plant UML Source

@startuml
interface House {
  getWater()
  getFood()
  getEnergy()
}

class MidWesternHouse implements House {
  getWater()
  getFood()
  getEnergy()
}

class RainWaterHarvester << (M,#FF7700) >> {
  getWater()
}


class AquaponicGreenHouse << (M,#FF7700) >> {
  getFood()
}


class SolarPanelArray << (M,#FF7700) >> {
  getEnery()
}

MidWesternHouse ..> RainWaterHarvester
MidWesternHouse ..-> AquaponicGreenHouse
MidWesternHouse ..> SolarPanelArray
@enduml

I/O

A house can be defined in terms of I/O, or inputs and outputs.

Inputs

Inputs are unique to a geographic location or bio-region, and result in resource generation.

For example, in the mid-west of the United States, an input to a house may be rain-water.

The house would have a rain-water harvesting sub-component that adapts the input of rain-water to the resource of water.

Other geographic locations may have different inputs that lead to water resource generation such as ground-water, salt-water, river-water, glacier-water, or spring-water -- and each water input would need a different sub-component to adapt it to a water resource ready for human consumption.

Outputs

TODO: Define outputs.

• Human waste
• are there others?

Principles

See Village Resource Management Software#Principles.