500067197

A.P DEEPAK KAMATCHI

R120218006

ASSIGNMENT

1)In this testing, the development team members are included in the testing team to
execute the software's internal design. The working of structural testing is opposite
to Behavioural testing.

In other words, we can say that structural testing tests the different features of an
application based on its types.

Structural testing is also known as white-box testing, glass box testing, and clear-box

testing. Developers mostly implement it to identify the issue and fix them quickly.

The structural testing process requires an in-depth knowledge of the programming

language and is opposite to Functional Testing.

The knowledge of the code's internal executions and how the software is
implemented is a necessity for the test engineer to implement the structural testing.

Throughout the structural testing, the test engineer intends on how the software
performs, and it can be used at all levels of testing

Control flow testing

o The control flow testing is the basic model of Structural testing.

o It is to check the implementation order of commands or statements of the
code over a control structure.
o In the control flow testing, a specific part of an extensive program is selected
by the test engineer to set the testing path.
o Generally, the control flow testing technique is used in unit testing.
o In this testing, the entire test is based on how the control is executed during
the code.
o The complete information of all the software's features and logic is necessary
to execute the control flow testing.

Functional Testing:
It is a type of software testing which is used to verify the functionality of the software
application, whether the function is working according to the requirement
specification. In functional testing, each function tested by giving the value,
determining the output, and verifying the actual output with the expected value.
Functional testing performed as black-box testing which is presented to confirm that
the functionality of an application or system behaves as we are expecting. It is done
to verify the functionality of the application.

Functional testing also called as black-box testing, because it focuses on application

specification rather than actual code. Tester has to test only the program rather than
the system.

Goal of functional testing

The purpose of the functional testing is to check the primary entry function,
necessarily usable function, the flow of screen GUI. Functional testing displays the
error message so that the user can easily navigate throughout the application.

Q2

Risk workshops and interviews Risk workshops and interviews are useful for
identifying, filtering and screening risks but it is important that these judgment
based techniques be supplemented by more robust and sophisticated methods where
possible, including quantitative techniques. Risk identification should be
strengthened by supplementing Management’s perceptions of risks, inter alia, with:
review of external and internal audit reports; review of the reports of the Standing
Committee on Public Accounts and the relevant Parliamentary Committee(s);
financial analyses; historic data analyses; actual loss data; interrogation of trends in
key performance indicators; benchmarking against peer group or quasi peer
group;market and sector information; scenario analyses; Focus points of risk
identification To ensure comprehensiveness of risk identification the Institution
should identify risk factors through considering both internal and external factors,
through appropriate processes of: Strategic risk identification Strategic risk
identification to identify risks emanating from the strategic choices made by the
Institution, specifically with regard to whether such choices weaken or strengthen
the Institution's ability to execute its Constitutional mandate: strategic risk
identification should precede the finalization of strategic choices to ensure that
potential risk issues are factored into the decision making process for selecting the
strategic options; risks inherent to the selected strategic choices should be
documented, assessed and managed through the normal functioning of the system of
risk management; and strategic risks should be formally reviewed concurrently with
changes in strategy, or at least once a year to consider new and emerging risks.
Operational risk identification Operational risk identification to identify risks
concerned with the Institution’s operations: operational risk identification should
seek to establish vulnerabilities introduced by employees, internal processes and
systems, contractors, regulatory authorities and external events; operational risk
identification should be an embedded continuous process to identify new and
emerging risks and consider shifts in known risks through mechanisms such as
management and committee meetings, environmental scanning, process reviews and
the like; and operational risk identification should be repeated when changes occur,
or at least once a year, to identify new and emerging risks. Project risk identification
Project risk identification to identify risks inherent to particular projects: project
risks should be identified for all major projects, covering the whole lifecycle; and for
long term projects, the project risk register should be reviewed at least once a year to
identify new and emerging risks