Water Heating Software Development using Software Engineering Principles

This article discusses the development of water heating software using software engineering principles such as ERD, DFD, and SPECs. It covers the Central Heating System Version 10, Control Flow Diagram, Control Specifications, and more.

INDEX
Central Heating System Version 10...........................................................................................2
Context Diagram......................................................................................................................3
Control Flow Diagram.............................................................................................................4
Control Specifications (CSPECs)..........................................................................................12
Duct Control System Control Flow Diagram........................................................................5
Executive summary..................................................................................................................1
Gas Meter Supply...................................................................................................................10
Heating Duct.............................................................................................................................9
Heating Unit..............................................................................................................................6
Introduction..............................................................................................................................1
Process activation table..........................................................................................................12
References...............................................................................................................................15
SPECs (Process Specification Description)............................................................................6
State machine..........................................................................................................................12
System Clock.............................................................................................................................7
System control..........................................................................................................................8
Temperature Detector System..............................................................................................11
Water Heating Company Data Dictionary..........................................................................13

Executive summary
In summary, use of software engineering principles makes it easy to develop large programs.
In any software development industry, software engineering processes are required to
accommodate difficulty and complex software product since every process is broken down
into a module each module processes represented pictorially.
Introduction
Software engineering denotes to a branch related to development of software product with
well-defined scientific processes, methods, procedures and principles. In this task we will be
using scientific principles such as ERD, DFD and SPECs to develop water heating software.
Kiremire, (2011), ERD diagram in software engineering refers to the process of
diagram representation of relationships, attributes and entities. It offers the relationships for
database in software design system. In the figure below we present a visual concept of
Central Heating System Version 10 (CHCV10). It portraits how the inner parts of the system
interrelates with the outer setting. In the graphic diagram, cardinalities and modalities
together with their relationships are provided
Central Heating System Version 10

Assumptions made
In the diagram above, it is assumed that:

 supplied gas to the room is fanned with one or more pipes
 The heating system has only one control panel board. This control panel coordinates
system activities.
 Gas supply comes from one and only one supply pipe.
 Each subsystem control panel has more than one or zero operators.
Kendall & Kendall, (2014).
Context Diagram
Laplante & Ovaska (2012), context diagram outlines specific boundaries in a certain system
or environment.

Assumptions
 Our system real-time water heating system CHCV10 offers boundaries in the system.
 This real-time system is the introduced system in the task as Heating Water Company
 Physical entities exists in the system. These entities include but are not limited to
gas, clock system, supply pipes
Control Flow Diagram
Assumptions
 Manual control activities system get information from user
 Processes for instance stop, start manipulates the heating CHCV10 system
 Air replacement fetch information from temperature detection system

Duct Control System Control Flow Diagram
SPECs (Process Specification Description)
Pressman, (2010), explains process specification as a scheme deployed to analyse,
document and explain judgement making logic and prescriptions used to produce data from
the input methods’ information. Hatley & Pirbhai(2013), the process essentially flows down
processes specifying engineering needs and techniques. As outlined below, these are design
language for our water heating company system.
Heating Unit
if
<50% of pipe ducts are open

then
heating system turned on
else if
room temperature falls below minimum required
then room heated
until
room temperature measured is above range
else
no heating alert displayed
then
heating system is turned on manually
end
System Clock
if power energy is available
then
clock system always on
else if
power energy backup available
then
clocking system is always on

end
System control
if
time of the day is between 12:00:00 am and 5:59:00 am
then
room temperature range of 5 to 10 degrees Celsius maintained
else
turn on heating system
else if
time of the day is between 7:00:00 am 5:59:00 pm
then
room temperature of 15 to 20 kept constant
else if
time of the day is between 6:00:00 pm and 11:59:00 pm
then
room temperature of 5 and 10 kept constant
else if
manual heating is set to certain temperature
then override automatic heating system
until

heating system is scheduled to turn on
else if
Fan and Heating unit are turned on
then
turn on automatic heating system
else
heating system shows updated room temperature status
end
Heating Duct
if pipe duct closed manually
then
open it manually again
else if
heating duct system closed by CHCSV10
then
open heating duct system by CHCSV10
end if
if central heating system working
then
pipe duct system report status

else if
no status report
end if
if new active status determined
then
display new status alerts
else
display latter status
end
Gas Meter Supply
if
gas supplied is available
then
record of available gas is obtained.
else if
gas supplied in not available
then
no record of gas supplied
end if
else if

gas supply is unavailable
then
gas supply is stopped
end if
end
Temperature Detector System
if power available
then
temperature detector system is on
else if
power backup energy available
then
temperature detector System on
end if
if central system working
then
temperature detector system send temperature status alerts to monitor
display
else

no temperature alerts display
end
Control Specifications (CSPECs)
Jalote, (2012), explains Control Specifications as the constraints of a physical production
method. Control Specifications Controls simulates system activities from different level of
operation to an additional level. Our water heating system has Control Specifications as
outlined below:
State machine
Process activation table
Input Actions
Start or Stop 0 1 0 0 0 0
Screen Monitor event status finished 0 0 0 1 0 0

Gas notification 0 0 1 1 0 0
Timing out 0 0 0 0 0 1
Display action status Incomplete 0 0 1 0 0 0
Sensor activity 0 0 0 0 1 0
Output
Signal of Temperature 0 0 0 0 1 0
Process activation
User Interruption 1 0 0 1 0 1
Invoke/Deactivate heating system 0 1 0 0 0 0
Show statuses and messages 1 0 1 1 1 1
System Control and Screen Monitor 0 1 0 0 1 1
Water Heating Company Data Dictionary.
Krishna, (2011), a data dictionary denotes to a description of informational entities in
a data modelling. It benefits programmers who use the data dictionaries as a point of
reference during their coding activities. The following is our water heating data dictionary.
Data Structure
Gas from
fanning system
Volume: as required
Temperature: as required in degrees Celsius
Flow rate: as adjusted
Normal gas Normal gas = Natural gas
Warm gas heated gas=
-------

Flow rate: as adjusted in m/s
Temperature: as required in degrees Celsius
Volume: as required
Gas supplied in
the room
Volume: as required
Temperature: as needed in degrees Celsius
Flow rate: as adjusted
Supplied gas
Supplied gas =
---------
Volume : as required
Flow rate: as required
Other versions: filtered or unfiltered

References
Hatley, D., & Pirbhai, . (2013). Strategies for Real-Time System Specification. Boston:
Addison-Wesley.
Kendall, K.E. & Kendall, J.E. (2014). Systems Analysis and Design (9th
Ed.). Harlow, England: Pearson Education Inc.
Kopetz, H. (2011). Real-time systems: design principles for distributed
embedded applications. Springer Science & Business Media.
Krishna, C. M. (2011). Real‐Time Systems. Wiley Encyclopedia of Electrical
and Electronics Engineering. Northcutt, J. D. (2014). Mechanisms for
reliable distributed real-time operating systems: The Alpha Kernel (Vol.
16). Academic Press.
Laplante, P. A. & Ovaska, S. J. (2012). Real-Time Systems Design and Analysis: Tools for
the Practitioner
Pressman, R.S. (2010). Software Engineering: A Practitioners Approach (7th
Ed.). McGraw-Hill. ISBN: 978-007-126782-3
Kiremire, A. R. (2011). The application of the Pareto principle in software
engineering. Consulted January, 13, 2016.