SE- UOG – Software Verification and Validation SV&V

Project Date: August 08, 2020

Department of Software Engineering

University of Gujrat

Project

Software Verification and

Validation

Semester 6th Spring 2020

Submitted to: Ma’am Uzma Ijaz

Submitted from:

Bilal Iqbal 17221598-116

Suleman Amjad 17221598-127

Dilawar Hussain 17221598-129

Fahad Murad 17221598-152

© Department of Software Engineering

University of Gujrat
1
 SE- UOG – Software Verification and Validation SV&V
Project Date: August 08, 2020

 CHECKLIST TESTING:
CASE STUDY:
Consider the problem statement of a university registration system. Prepare the
software requirement checklist with the details of faults in the given SRS.

# Description Yes/No/NA Remarks

Introduction
Is the purpose of the project clearly defined? No It contains only
information about the
papers not the overall
URS.
Is the scope clearly defined? No It is not stated that the
faculty details will be
maintained.
Is the document format as per standard/guidelines Yes The format of
(Ex. IEEE 830-1993)? document is
conforming with IEEE
830-1993
Is the project formally approved by the customer? NA This is not stated in
document whether it
is formally approved
or not.
Are all requirements, interfaces, constraints, Yes They are distinctly
definitions etc. listed in the appropriate sections? listed into the
appropriate sections.
Not listed in
inappropriate section
Correctness
Is the expected response time from the user’s point Yes It is plainly specified
of view specified for all operations? in performance
requirement of the
document. (within 2
secs).
Are all stated requirements expressing the Yes For example, Login is
functionality? a requirement that
allow the user to use
other functionalities.
Are there areas not addressed in the SRS document Yes The layout of the student
that need to be covered? registration card and
reports that the system
will generate has not
been given.

SE- UOG – Software

© Department Verification
of Software and Validation
Engineering SV&V
Project
University of Gujrat Date: August 08, 2020
2
 Are the non-functional requirements stated? Yes Not all but some like
Portability,
maintainability,
response time, etc are
stated.
Are validity checks properly defined for every input No 1. The range of values of
condition? the school name has not
been defined.
2. It is not mentioned
that a school name
cannot be blank.
3.The range of values of
login id and password
have not been defined
etc.

Ambiguity
Are functional requirements separated from non- Yes Functionalities login,
functional requirements? school details etc. are
separated from non-
functional
requirements that are
maintainability etc.
Does any requirement convey more than one No All the requirements
interpretation? convey the only
functionality they will
perform.
Are all requirements clearly understandable? Yes All requirements are
clearly
understandable.
Does any requirement conflict with or duplicate with Yes Login id and roll no
other requirements? are same thing but
stated in different
sections, duplicates
with each other
Are there ambiguous or implied requirements? No There are no such
ambiguity in
requirements because
they are clearly
defined their
functionality.
Completeness
Are all functional and non-functional requirements No All functional
stated? requirements have not
been stated, the non-
functional requirements
usability and reliability
have not been
mentioned.

© Department of Software Engineering

University of Gujrat
3
SE- UOG – Software Verification and Validation SV&V
Project Date: August 08, 2020

Are forms available with validity checks? No Change Password

form validity checks
are not defined.
Are all reports available in the specified format? No Neither is there any
snapshot of the student
registration card and
output reports nor have
the contents been
mentioned.
Are all references, constraints, assumptions, terms, No 1.The abbreviation of
and units of measures clearly stated? LAN has not been given.
2. The assumption that
the registration process
will be open only for a
specific duration is not
stated.
3.The dependencies that
the list of students will
be obtained from the
academic section and the
list.
Has analysis been performed to identify missing No There is no
requirements? mechanism to identify
the missing
requirements in the
document.
Consistency
Are the requirements specified at a consistent level No They are not specified
of detail? completely. Functions
to perform add edit
del faculty details are
not specified.
Should any requirements be specified in more Yes I think all the
detail? requirements related
to the registration are
in their full details.
Anyone can easily
understand all of
these requirements.
Should any requirements be specified in less detail? Yes Non-functional
requirements are not
specified clearly.
Are the requirements consistent with other N/A We have not been
documents of the project? provided any other
document

© Department of Software Engineering

University of Gujrat
4
SE- UOG – Software Verification and Validation SV&V
Project Date: August 08, 2020

25. Is there any difference in the stated requirements Yes We only entered all
at two places? the requirements at
once.
Verifiability
26. Are all stated requirements verifiable? Yes All requirements are
verifiable.
27. Are requirements written in a language and Yes The requirements are
vocabulary that the stakeholders understand? written in vocabulary
and language that is
understandable by
the stakeholders.
28. Are there any non-verifiable words? Yes In this “user” is a
non-verifiable word.
It doesn’t specify
whether the user is
administrator,
student or faculty.
29. Are all paths of a use case verifiable? No No use cases have
been defined in
document provided.
30. Is each requirement testable? Yes Yes, the requirements
the document are
testable
Modifiability
31. Are all stated requirements modifiable? No Some requirements
cannot modifiable
and some are not
modifiable like
security
requirements.
32. Have redundant requirements been consolidated? No This case study only
focuses on the
compulsory
requirements.
33. Has the document been designed to incorporate Yes It is easy to add
changes? function or delete
some requirements
according to needs.
34. Are the format structure and styles of the Yes The document is
document standard? according to the
standards made by
IEEE.
35. Is there any procedure to document a change? Yes Change control
procedure is to
change
a document.

© Department of Software Engineering

University of Gujrat
5
SE- UOG – Software Verification and Validation SV&V
Project Date: August 08, 2020

Traceability
Can any requirement be traced to its origin or N/A If case tools are used
source? in SRS then we can
trace otherwise not.
Is every requirement uniquely identifiable? Yes Every requirement is
in its respective
section and numbered
id.
Are all requirements clearly understandable for Yes Requirements like
implementation? student nametype and
other input types are
clearly
understandable
and vice versa.
Has each requirement been crossed-referenced to N/A It cannot be answered
requirements in the document of comparable since no previous
previous projects? project requirement
document is given.
Is each requirement identified such that it facilitates Yes These requirements
referencing of each requirement in future like required inputs
development and enhancement efforts? for
the registration form
and categories will
facilitate the future
developments.
Is every stated requirement feasible? Yes Because there is no
time requirement for
implementation, cost
constraints defined in
the document.
Is any requirement non-feasible due to technical No No requirement is non
reasons? feasible because all
necessary technical
errors will be solved.
Is any requirement non-feasible due to lack of No This system is not
resources? affected because all
necessary resources
are available in the
document.
Is any requirement feasible but very difficult to No All requirement has
implement? enough information,
so it is not difficult to
be implemented.
Is any requirement very complex? No This system is not
complex rather it is
easy to implement
that is it don’t contain
complex requirements

© Department of Software Engineering

University of Gujrat
6
SE- UOG – Software Verification and Validation SV&V
Project Date: August 08, 2020

General
Is the document concise and easy to follow? Yes According to this
project, this document
is easy and
concise. Everything is
stated clearly and
concisely.
Are requirements stated clearly and consistently Yes All the requirements
without contradicting themselves or other are
requirements? stated step by step.
And
easy to understand
Are all forms, figures, and tables uniquely No Numbering is not
numbered? given for forms and
figures.
Are hardware and other communication No Hardware
requirements clearly stated? requirements are
stated but the
document don’t
contain any
communication
requirements.
Are all stated requirements necessary? Yes All requirements are
necessary to
implement for better
working and quality of
this system.

© Department of Software Engineering

University of Gujrat
7