Three- Reflective Journal

profilemoyd.azhaiuddxn2
Module4.2MIS604.pdf

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975602_1&mode=reset 1/5

MODULE 4.2MODULE 4.2

Requirement Validation

Source: Gutiérrez Rivas, José & Berthing, Jesper & Fernández García-

Valdecasas, David & Díaz, Javier. (2012). Safety-Critical Platform Model Based

on Certi�cation Standards.

Introduction:

Following Requirement Elicitation, Requirement Analysis and Requirement

Speci�cation processes, Requirement Validation is another key process in

requirement engineering. Requirement validation is concerned with

whether the written requirements have the characteristics of a good

requirement and whether it conforms to the organisations’ standards. You

should not confuse it with requirement veri�cation, which is concerned with

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975602_1&mode=reset 2/5

whether an end product (the key deliverables) satisfy users requirements,

i.e. whether the “right” thing has been developed.

Requirement validation

Early detection of errors in requirement before they are implemented is

critical. Any requirement errors detected in the delivery phase that were not

caught before the implementation phase are typically very expensive to �x.

As a requirement engineer, you will summon a requirement validation team

that consists of people from various background to ensure the team covers

all the domains of knowledge required for validating requirement. A

validation checklist may be used in the requirement validation process to

ensure the requirements are understandable, free of redundancy and is

complete.

Requirement veri�cation

The introduction image shows the V model of software development – it

connects the various levels of testing with di�erent levels of requirements

and design. Unit testing veri�es low level design; integration testing veri�es

architectural design; System testing veri�es functional requirements; and on

the highest level, acceptance testing veri�es user requirements.

Requirement veri�cation involves the inspection process. Who are the

participants in the inspection process? What’s their roles and

responsibilities? The inspection process has a number of key activities and

stages, from planning to preparation to conducting inspection meetings to

rework and follow-up. Defect checklist is a simple yet e�ective tool to assist

reviews to look for common types of errors in the products.

Acceptance criteria refer to the minimum conditions the �nal product must

pass for the customers to accept it. Acceptance criteria inform the design of

acceptance tests.

Reference:

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975602_1&mode=reset 3/5

Alain. A. , Moore W. J., Bourque P., & Dupuis R., (2004). Guide to the Software Engineering Body of Knowledge, 2004 Version. Los Alamitos, CA: IEEE Computer Society Press.

Stephens, R. (2015). Beginning software engineering (Wrox : programmer to programmer). Indianapolis, IN: John Wiley & Sons. (2015).

Essential Resources:

Stephens, R. (2015). Beginning software engineering (Wrox:

programmer to programmer). Indianapolis, IN: John Wiley &

Sons. (2015).

Read the Validation and Veri�cation Section on page 80 in Beginning

software engineering (Wrox: programmer to programmer). This half-

page section de�nes requirement validation and veri�cation.

This resource is available through Torrens Library:

https://ebookcentral-proquest-

com.ezproxy.laureate.net.au/lib/think/detail.action?docID=1895174

The Guide to the Software Engineering Body of Knowledge

(SWEBOK Guide)

Read Section 6 Requirements Validation in Chapter 1

Software Requirements in Guide to the Software Engineering Body of

Knowledge. In section discusses the meaning of requirement

validation and some commonly used tools and techniques for

requirement validation, for example requirement reviews,

prototyping, and model validation.

You can download SWEBOK Guild for free at:

https://www.computer.org/education/bodies-of-knowledge/software-

engineering

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975602_1&mode=reset 4/5

Requirement Validation – Software Engineering:

https://youtu.be/hFaP8MqytHE

This 9-minute video provides a clear introduction to

requirement validation, including the input and output of the

requirement validation process. The importance of detecting

requirement errors at an early stage. The personnel involved in the

requirement validation process.

Rakitin, S. R. (2001). Software Veri�cation and Validation for

Practitioners and Managers (Vol. 2nd ed). Boston: Artech

House, Inc.

Read page 57 – 58 in Software Veri�cation and Validation for

Practitioners and Managers. Note that the de�nition of software

veri�cation and validation are just the other way around. In this text,

validation is “[t]he process of evaluating a system or component

during or at the end of the development process to determine

whether it satis�es speci�ed requirements” (Rakitin, 2001). You should

be aware of that di�erent authors use di�erent de�nitions for these

two words “veri�cation” and “validation”.

This resource is available through Torrens Library:

http://search.ebscohost.com.ezproxy.laureate.net.au/login.aspx?

direct=true&db=nlebk&AN=67447&site=ehost-live

Learning Activity:

Learning Activity 4.4: Discussion forum post

Use Torrens library and research for an academic reference

that is related to requirement validation. Write a 150-word

annotated bibliography for that reference and post it, together with

the link to the article, to Module 4 discussion forum.

8/6/2020 Laureate International Universities

https://laureate-au.blackboard.com/webapps/blackboard/content/listContent.jsp?course_id=_89880_1&content_id=_8975602_1&mode=reset 5/5

Read other students’ post and provide constructive feedback to at

least two students' posts.

To participate in the Discussion Forum, click here to scroll to the

bottom of this page then click on the "Module 4 - Discussion

Forum" link.

Note: The Learning activities above are not part of summative/graded

assessment; however they are designed to prepare you for incremental

graded assessment and expand your learning.

These activities encourage a community learning experience between peers,

and provide opportunities for facilitators to o�er formative feedback,

throughout a module, to the student cohort.