Design a heating, ventilation and air conditioning (HVAC) system for a typical office building.

D1.2. O diagrama de use-case-uri, alaturi de explicatii textuale cu privire la fiecare caz de utilizare.

D1.3. O schita a interfeti utilizator si a modelului de interactionare cu utilizatorul.

modelul arhitectural al aplicatiei. Va trebui sa fie specifcat: partea care va fi implementata in Java si de asemenea partea care va fi implementata in JESS, precum si modul de interactiune dintre aceste module ale aplicatiei. (D2.1)

modelul orientat - obiect al aplicatiei (diagrama de clasa pentru partea de Java a aplicatiei, insotita de 1-2 diagrame de secventa, 1-2 diagrame de activitate si explicatii). (D2.2)

04/19/23 1

Name:* HVAC controllerIteration: 1.0Brief description: Our team creates a

software for Heating, Ventilation and Air Conditioning (HVAC) which can be use in a offices building.

Added value: The offices are comfortable, therefore companies employees are more productive.

Scope: An HVAC controller for offices building.

Primary actor:* Offices building OwnersSupporting actors: HVAC team-5Precondition: To have a company in an

offices building.

04/19/23 2

Main Success Scenario: 1. Offices building Owners buys

an air conditioning system on average every ten years.

2. Offices building Owners buys a heating system on average every 15 years.

3. Offices building Owners performs maintenance on the air conditioner in May.

4. Offices building Owners performs maintenance on the heater in November.

04/19/23 3

Unanchored Alternate Flow: Offices building Owners performs repairs

on the HVAC system whenever a component fails.

Specific RequirementsFunctional Requirement:Offices building Owners shall buy,

maintain and repair an HVAC system [from HVAC use case].*

Nonfunctional Requirement:Offices building Owners desires

maintenance services when scheduled and repair services within 48 hours [from customer interviews].

04/19/23 4

Iteration: 2.0Brief description: Maintain the room temperature

(roomTemp) between lowerThreshold (see Rule1) and upperThreshold (see Rule2) degrees Fahrenheit using a Heater and an Air Conditioner (AC).

Added value: The office building are comfortable, therefore companies employees are more productive.

Scope: An HVAC controller for offices building.Primary actor: Offices building Owners Supporting actors: Heater and Air ConditionerPrecondition: The system is turned on

and the roomTemp is between lowerThreshold and upperThreshold.

04/19/23 5

Main Success Scenario: 1. The system senses roomTemp.2a. The roomTemp exceeds upperThreshold.3. The system turns on the Air Conditioner.4. The roomTemp drops below upperThreshold.5. The system turns off the AC [repeat at step 1].Anchored Alternate Flow: 2b. The roomTemp drops below lowerThreshold.2b1. The system turns on the Heater.2b2. The roomTemp exceeds lowerThreshold.2b3. The system turns off the Heater [repeat at

step 1].

04/19/23 6

Specific RequirementsFunctional Requirements:1. The system shall be capable of turning the AC on

and off [from Regulate Temperature use case, steps 3 and 5].

2. The system shall be capable of turning the Heater on and off [from Regulate Temperature use case, steps 2b1 and 2b3].

3. The system shall be capable of sensing room temperature [from Regulate Temperature use case, step 1].

Rules:Rule1: lowerThreshold default value is 70 degrees F.Rule2: upperThreshold default value is 73 degrees F.

04/19/23 7

Name: Display System StatusBrief description: Indicate the health of the

systemAdded value: Offices building Owners knows if

the system is working properly.Scope: An HVAC controller for offices buildingsPrimary actor: Offices building Owners Frequency: Typically once a dayMain Success Scenario: 1. Offices building Owners asks the system for

its status.2. Each component in the system reports its

status to the Controller.3. The system accepts this information and

updates the System Status display.4. Offices building Owners observes the

System Status [exit use case].04/19/23 8

Alternate flows go here.Specific RequirementsFunctional Requirements:1. Each component shall have the capability to

report its status to the Controller [from Display System Status use case, step 2].

2. The system shall be capable of displaying System Status [from Display System Status use case, step 3].

04/19/23 9

04/19/23 10

Heater

heatAir()

Air Conditioner

coolAir()

Regulate Temperature

Display System Status

Offices building Owners

Iteration: 2.0Brief description: When it is hot outside, use an Air

Conditioner (AC) to maintain the room temperature (roomTemp) between ACLowerLimit and ACUpperLimit degrees Fahrenheit.

Added value: The Offices are comfortable, therefore companies employees are more productive.

Scope: An HVAC controller for a offices building.Primary actor: Offices building OwnersSupporting actor: Air ConditionerFrequency: The system operates continuously.Precondition: Offices Owners has turned on the

cooling system and the roomTemp is between ACLowerLimit and ACUpperLimit.

04/19/23 11

Brief description: When it is cold outside maintain the roomTemp between heaterLowerLimit (see Rule2) and heaterUpperLimit (see Rule3) degrees Fahrenheit using a Heater.

Added value:* The Offices are comfortable, therefore companies employees are more productive.

Goal:* Maintain offices at a comfortable temperatureScope: : An HVAC controller for a offices building.Primary actor: Offices building OwnersSupporting actor: HeaterFrequency: The system operates continuously. Precondition: The heating system is on and the

roomTemp is between heaterLowerLimit and heaterUpperLimit.

04/19/23 12

Main Success Scenario: 1. The system is sensing roomTemp.2. The roomTemp falls below heaterLowerLimit.3. The system turns on the Heater [in accordance with

Rule1].4. The roomTemp rises to heaterUpperLimit.5. The system turns off the Heater [Rule1] [go to step

1].Unanchored Alternate Flow:1. Companies employees turns off Heater [exit use

case].Specific RequirementsFunctional Requirements:1. The system shall turn the Heater on and off [from

steps 3 and 5 of the Heat Offices use case].2. The system shall sense room temperature [from step

1 of the Heat Offices use case].

04/19/23 13

Nonfunctional performance requirement: On-off cycles should last at least 15 minutes [from

interview with Chief Systems Engineer].Rules:Rule1: When the Heater is on, turn the Fan on.

When the Heater is off, turn the Fan off.Rule2: heaterLowerLimit default value is 70 degrees

F.Rule3: heaterUpperLimit default value is 71 degrees

F.

04/19/23 14

Iteration: 2.0Brief description: The system shall monitor the

health of each object in the system and display the status of the complete system. The display could be a simple go/no-go or it might be more sophisticated.

Added value: Offices building Owners knows if the system is working properly.

Scope: An HVAC controller for a offices building.Primary actor: Offices building OwnersFrequency: The system shall display system status

continuously.Main Success Scenario: 1. The Fan reports status to the Controller.2. The Air Conditioner reports status to the

Controller.3. The Heater reports status to the Controller.

04/19/23 15

4. The Thermostat reports status to the Controller.5. The Controller computes the System Status and

sends results to the Display.6. The Displays shows the System Status.7. Home Owner observes the System Status

periodically [repeat at step 1].Specific RequirementsFunctional Requirements:1. Each component shall report its status to the

Controller [from steps 1 to 5 of the Display System Status use case].

2. The system shall display System Status.Nonfunctional requirement: System Status shall be

displayed within 2 seconds of request.

04/19/23 16

04/19/23 17

Heater

heatAir()

Display System Status

Heat offices

Air Conditioner

coolAir()

Cool OfficesOffices building Owners

04/19/23 18

: Thermostat

: AC Interface

: Air Conditioner

: Controller

1: set(tooHot)4: reset(tooHot)

3: turnOn6: turnOff

2: turnOnAC5: turnOffAC

04/19/23 19

Heater

heatAir()

Air Conditioner

coolAir()Fan

turnOn()turnOff()

The Heater and AC Interfaces should also have functions that turn the Fan on and off.

Home Owner Heater Interface

turnOnHeater()turnOffHeater()

AC Interface

turnOnAC()turnOffAC()

Controller

tooHot : Boolean = NotooCold : Boolean = No

set()reset()

Thermostat

ACupperThreshold : Integer = 73AClowerThreshold : Integer = 72roomTemperature : IntegerheaterUpperThreshold = 71heaterLowerThreshold = 70

Brief description: When it is hot outside maintain the room temperature (roomTemp) between coolerLowerLimit and coolerUpperLimit degrees Fahrenheit using a Cooler (either an Evaporative Cooler or an Air Conditioner).

Scope: An HVAC controller for a offices building.Level: LowPrimary actor: Offices building OwnersSupporting actor: CoolerFrequency: The system operates continuously.Precondition: Offices building Owners has selected

the Cooler, systemStatus is ready, systemState is Cooler Off, and the roomTemp is below coolerUpperLimit.

Trigger: The roomTemp exceeds coolerUpperLimit.04/19/23 20

Brief description: When it is cold outside maintain the roomTemp between heaterLowerLimit and heaterUpperLimit degrees Fahrenheit using a Heater.

Scope: An HVAC controller for a offices building.Level: LowPrimary actor: Offices building OwnersSupporting actor: HeaterFrequency: The system operates continuously. Precondition: Offices building Owners has selected the

Heater, systemStatus is ready, system state is Heater Off, and roomTemp is above heaterLowerLimit.

Trigger: The roomTemp falls below heaterLowerLimit.Main Success Scenario: 1. The system turns on the Heater [in accordance with

Rule1].04/19/23 21

2. The roomTemp rises to heaterUpperLimit.3. The system turns off the Heater [Rule1] [exit use

case].Unanchored Alternate Flow:2. Offices building Owners turns off Heater [exit use

case].Postcondition: Heater is offFunctional requirements…Nonfunctional performance requirement: On-off

cycles should last at least 15 minutes.Rules:Rule1: When the Heater is on, turn the Fan on.

When the Heater is off, turn the Fan off.Rule2: heaterLowerLimit default value is 70 degrees

F.Rule3: heaterUpperLimit default value is 71 degrees

F.04/19/23 22

Brief description: The system shall monitor the health of each object in the system and display the status of the complete system. This display should indicate ready or fault.

Scope: An HVAC controller for a offices building.Level: MediumPrimary actor: Offices building OwnersFrequency: The systemStatus shall be computed

periodically (e.g. every minute) or it may be event driven (e.g. on each state transition). The system shall display the systemStatus continuously.

Main Success Scenario: 1. The Fan Interface executes its Built-in Self-Test (BiST)

for the Fan and the Fan Interface and reports the results to the Controller.

2. The Air Conditioner Interface executes its BiST and reports the results to the Controller.

04/19/23 23

3. The Evaporative Cooler Interface executes its BiST and reports the results to the Controller.

4. The Heater Interface executes its BiST and reports the results to the Controller.

5. The Thermostat executes its BiST and reports the results to the Controller.

6. The Controller executes its BiST and computes the systemStatus.

7. The Controller sends the systemStatus to the Thermostat.

8. The Thermostat displays the systemStatus.9. Offices building Owners observes the systemStatus

periodically [repeat at step 1].

04/19/23 24

Brief description: Offices building Owners changes the HVAC temperature limits

Scope: An HVAC controller for a offices building.Level: MediumPrimary actor: Offices building OwnersFrequency: DailyPrecondition: Offices building Owners has selected

the equipment and systemStatus is ready.Main Success Scenario: 1. Offices building Owners sets coolerUpperLimit.2. Offices building Owners sets coolerLowerLimit.3. Offices building Owners sets heaterUpperLimit.4. Offices building Owners sets heaterLowerLimit.5. Exit Set Temperature Limits use case.Postcondition: All four limits are set.

04/19/23 25

04/19/23 26

HeatHouse

SetTemperature

Limits

CoolHouse

Select Equipment

DisplaySystemStatus

HVAC Control System

Heater

EvaporativeCooler

AirConditioner

OfficesbuildingOwners

04/19/23 27

: Thermostat : Heater Interface

: Heater: Controller

roomTemp=<heaterLowerLimit

turnOnHeater

turnOn

roomTemp>=heaterUpperLimit

turnOffHeater

turnOff

Time runs from top to bottom.

04/19/23 28

: Thermostat : Controller :Heater Interface : Heater: Home Owner

Time runs from top to bottom

roomTemp=<heaterLowerLimit

turnOnHeater

turnOn

turnOffHeater

turnOffHeaterturnOff

Home Owner smells gas.

04/19/23 29

Home Owner

(from Use Case View)

Thermostat

coolerUpperLimit : Integer = 73coolerLowerLimit : Integer = 72heaterUpperLimit : Integer = 71heaterLowerLimit : Integer = 70roomTemp : Integer

compareRoomTempToLimits()BiT()displaySystemStatus()

Air Conditioner

coolAir()

(from Use Case View)

AC Interface

turnOnAC()turnOffAC()BiT()

Evaporative Cooler

coolAir()

(from Use Case View)

Evaporative Cooler Interface

turnOnEvapCooler()turnOffEvapCooler()BiT()

Heater

heatAir()

(from Use Case View)

Heater Interface

turnOnHeater()turnOffHeater()BiT()

Controller

systemStatus : Boolean = fault

BiT()setSystemStatus()

<<active>>

Fan

blowAir()

(from Use Case View)

Fan Interface

turnOnFan()turnOffFan()BiT()

Notes: The bottom third of each class box lists the functions, which are also called operations or responsibilities.BiT stands for Built in Test.

Function(class) in Jess: - Bind - Ntimes - UserFunction

Function(class) in Java: - all java files from “control” package.

04/19/23 2009 30