ITECH7410 - Real-Time System: Requirements Analysis of Heat Exchange

This report provides a requirements analysis specification for a real-time heat exchange system, in line with the ITECH7410 Software Engineering Methodologies course. It explores the concepts of real-time operating systems (RTOS) and their characteristics, emphasizing memory allocation and the importance of avoiding memory leaks. The report delves into requirements modeling, covering content models, interaction design, functional design, and navigation modeling for WebApps. It also summarizes the DeMarco and Hatley-Pirbhai models, highlighting their features and extensions for structured analysis. Finally, the document includes a discussion on data dictionaries and their role in database management systems, providing a comprehensive overview of the components required for a real-time system analysis.

1
HEAT EXCHANGE PROCESS
HEAT EXCHANGE PROCEDURE
NAME -
UNIVERISTY NAME-

2
HEAT EXCHANGE PROCESS
TABLE OF CONTENT
Serial
Number
Topic Page
Number
1 CONCEPT OF REAL-TIME SYSTEMS 3-4
2 REQUIREMENTS MODELING: FLOW, BEHAVIOR,
PATTERNS, AND WEBAPPS
4 -11
3 REQUIREMENTS ENGINEERING METHODOLOGY 12
4 A SUMMARY OF THE DEMARCO MODEL 13-14
5 A SUMMARY OF THE HATLEY AND PIRBHAI 14
6 HATLEY AND PIRBHAI EXTENSIONS 14-15
7 DATA DICTIONARY 15-16
8 REFERENCE 17

3
HEAT EXCHANGE PROCESS
CONCEPT OF RT OPERATING SYSTEMS
A RT operating system (RTOS) is undoubtedly an operating system designed to provide actual
time software that procedure information as it is supplied, usually without stream slowdowns.
Processing time period specifications are assessed in tenths of sec. A real-time system is really a
time chained program that has well described fixed time frame constraints. Handling must be
carried out within the described limitations or the program may fail. They possibly are occasion
driven or period sharing.
A key feature of an RTOS is the level of its regularity regarding the volume of time it takes to
acknowledge and finish the process of its application; the variation is aflutter. A difficult RT
operating system offers less aflutter compared to a soft RT operating system. The fundamental
aim is not large output but instead,assured of a hard or soft efficiency group. An RTOS has a best
algorithmic rule for arranging. Hardware skillfulness enables a broader, system of computer
arrangement for method points, but a RT operating system is more often committed to a small
format of programs. (Frank, 2015)
RTOSs applying the unified structures solve the trouble by simply turning off interrupts
although the inner list is up-to-date. The drawback of this is that disrupt latency raises,
potentially shedding interrupts. The segmented architecture will not make immediate OS calls
but delegates the OS associated work to a distinct handler. This handler operates at a higher
concern than any thread but reduced than the disturb handlers As a result, OSes which apply the
segmented architecture are much more foreseeable and can cope with higher disrupt rates in
comparison to the unified architecture.

4
HEAT EXCHANGE PROCESS
Memory allowance is more crucial in a real-time OS compared to in other OS. First, for
steadiness, there are not able to be memory leaks. The gadget must work consistently, without
having ever required a reboot. That is why dynamic memory allocation is frowned on. Anytime
achievable, all necessary memory allowance is specific statically at make time. Another cause to
avoid dynamic memory allowance is memory space division. With prevalent stake and release of
small pieces of storage, a circumstance might be able to occur while the storage is distributed
into a number of segments; in that case the RTOS are unable to spend a vast constant wedge of
memory, even though there is enough free memory space. Second part is, the velocity of
allocation is significant. A regular memory share scheme scans an associated list of
indeterminate size to find an appropriate free memory block that is unwanted in an RTOS
because memory allowance must occur inside a specific sum of the moment.
REQUIREMENTS MODELING: FLOW, BEHAVIOR, PATTERNS, AND WEBAPPS
Necessity Creating Regarding WebApps (Demir, et. al2009)
 Necessity Analysis will take time, but resolving the incorrect difficulty requires even far
more time.
 The issue for every single WebApp programmer is basic – currently confident you realize
the specifications of the issue?
 If the solution is a “yes” then it might be feasible to skip specifications modeling.
 However, the solution is “no”, then the specifications building should be carried out.
What amount of analysis is sufficient?
 The amount to that requirement creating for WebApps is highlighted on the subsequent
aspects:

5
HEAT EXCHANGE PROCESS
 Size and complexness of WebApp
 The layout of a particular component of the WebApp only needs an evaluation of those
specifications that impact only that component of the WebApp.
Necessity Creating Input
 Portable edition of the general software procedure can be utilized when WebApps are
designed.
 The procedure contains a communication activity that recognizes stakeholders
 The evaluation takes this details, clusters it using an officially defined counsel plan and
then generates more strenuous versions as a result.
Necessity Creating End result
 Necessity analysis supplies a regimented system for addressing and analysing WebApp
articles and functionality, the settings of discussion that users will experience, and the
atmosphere and facilities in which the WebApp resides.
 All these features can be displayed as a set of versions that allow the WebApp
specifications to be assessed in an organized manner.
Content Model for WebApps
 Recognizes the full range of information to be supplied
 These structural components include content objects
A content object is any kind of item of natural details which is to be shown to an end user.
 The content design must be competent of explaining the content item.
 A data tree is developed for any information that is made up of multiple content items
and data items.

6
HEAT EXCHANGE PROCESS
Discussion Design for WebApps
 The huge bulk of WebApp a “conversion” among a user and program performance,
information, and conduct.
 This discussion can be explained using a discussion model that can be constructed of a
number of elements: (1) utilize case, (2) series diagram, (3) state diagrams, and (4) user interface
prototype.
Useful Design for WebApps
The useful model tackles two running elements addressing various level of procedural abstract:
(1) User visible performance encompasses any running features. (2) The procedures contained
within analysis
Setup Design for WebApps
 The setup model is nothing over a list of server-side and client-side characteristics.
Navigation Modelling
 Navigation modelling issues how each user group will get around
 At this phase, you must concentrate on total navigation

7
HEAT EXCHANGE PROCESS

8
HEAT EXCHANGE PROCESS

9
HEAT EXCHANGE PROCESS

10
HEAT EXCHANGE PROCESS

11
HEAT EXCHANGE PROCESS
REQUIREMENTS ENGINEERING METHODOLOGY
Requirements engineering relates to the process of identifying, documenting and supporting
specifications in the engineering format treatment. This really is a regular functionality in
techniques and software engineering. (Abu-Khader, 2012)
The initial utilize of the phrase specifications of practical application was possibly in the year
1979 in the technical report of TRW but failed to came into public use till the year of 1990 with
the distribution of the Computer Society of an IEEE tutorial and the start of a seminar chain on
specifications engineering that has formulated into the current International Requirements
Engineering Conference.
These actions involved in specifications engineering vary broadly, based on the type of program
being formulated and the particular procedures of the organization(s) included. These might
include:
Requirements creation or specifications elicitation Requirements evaluation and negotiation –

12
HEAT EXCHANGE PROCESS
 Program modelling
 Requirements standards
 Requirements affirmation
 Requirements administration
There is certainly no proof that specifications engineering adds to the achievement of software
program or systems. Problem building, a key element of requirements engineering, reduces
design efficiency.
A SUMMARY OF THE DEMARCO MODEL
THE DEMARCO MODEL
Fundamental Features:-
• Semi-formal structure in that to create a set of Requirements Specifications explaining what
efficient handling a System should do.
• A rational design that neglects implementation problems.
• Thinks excellent technological innovation
• Could be seen as a large network of simple functions interacting via data flows, but is a lot
more easily displayed as a distrait structure of functional processes.
DFD ELEMENTS