An intentional scenario-based approach for testing software requirements specifications

Z. Al-Khanjari, Y. Jamoussi, N. Kraiem, A. Al-Kindi, X. F. Al-Salti

Research output: Contribution to journalArticle

1 Citation (Scopus)

Abstract

Software Requirement Specifications (SRS) provide a complete description of the software functionality, behavior and its constraints. Most bugs in software are due to incomplete or inaccurate software requirements. Testing SRS can identify the requirement conflictions and ambiguities and ensure the delivery of software which meets and satisfies the user requirements. The aim of the present study is to propose and implement an approach for testing SRS. The approach validates user requirement specifications against requirements specifications extracted from the corresponding ready software and produce a testing report. This study reports the development of the semi-automated SRS toolset that implements the proposed approach. This approach was formalized using MAP formalism which is a process model based on a non-deterministic ordering of goals and strategies. The SRS testing toolset extracts requirement specifications from the implemented software chosen to be an XML schema and compares them with SRSs from the user's perspective that are collected through a set of forms. Such toolset is expected to produce an informative validation report that indicates the degree of matching between the specifications and user requirements. To test the implemented tool, an input test case can be put which is an XML Schema sample and the corresponding user requirements specifications. The specifications for each test case are extracted manually and written out. Depending on the limitation of time, the number of test cases to be run will be three test cases; with complete entities, attributes and relationships, with some mismatches, with some mismatches but relationships.

Original languageEnglish
Pages (from-to)42-57
Number of pages16
JournalResearch Journal of Information Technology
Volume7
Issue number1
DOIs
Publication statusPublished - 2015

Fingerprint

Software testing
Specifications
XML
Testing

Keywords

  • Design and development
  • Formal verification
  • SRS
  • Testing database
  • Validation

ASJC Scopus subject areas

  • Computer Science(all)

Cite this

An intentional scenario-based approach for testing software requirements specifications. / Al-Khanjari, Z.; Jamoussi, Y.; Kraiem, N.; Al-Kindi, A.; Al-Salti, X. F.

In: Research Journal of Information Technology, Vol. 7, No. 1, 2015, p. 42-57.

Research output: Contribution to journalArticle

@article{4319e29844f2467aac271382fac00e8b,
title = "An intentional scenario-based approach for testing software requirements specifications",
abstract = "Software Requirement Specifications (SRS) provide a complete description of the software functionality, behavior and its constraints. Most bugs in software are due to incomplete or inaccurate software requirements. Testing SRS can identify the requirement conflictions and ambiguities and ensure the delivery of software which meets and satisfies the user requirements. The aim of the present study is to propose and implement an approach for testing SRS. The approach validates user requirement specifications against requirements specifications extracted from the corresponding ready software and produce a testing report. This study reports the development of the semi-automated SRS toolset that implements the proposed approach. This approach was formalized using MAP formalism which is a process model based on a non-deterministic ordering of goals and strategies. The SRS testing toolset extracts requirement specifications from the implemented software chosen to be an XML schema and compares them with SRSs from the user's perspective that are collected through a set of forms. Such toolset is expected to produce an informative validation report that indicates the degree of matching between the specifications and user requirements. To test the implemented tool, an input test case can be put which is an XML Schema sample and the corresponding user requirements specifications. The specifications for each test case are extracted manually and written out. Depending on the limitation of time, the number of test cases to be run will be three test cases; with complete entities, attributes and relationships, with some mismatches, with some mismatches but relationships.",
keywords = "Design and development, Formal verification, SRS, Testing database, Validation",
author = "Z. Al-Khanjari and Y. Jamoussi and N. Kraiem and A. Al-Kindi and Al-Salti, {X. F.}",
year = "2015",
doi = "10.3923/rjit.2015.42.57",
language = "English",
volume = "7",
pages = "42--57",
journal = "Research Journal of Information Technology",
issn = "1815-7432",
publisher = "Academic Journals Inc.",
number = "1",

}

TY - JOUR

T1 - An intentional scenario-based approach for testing software requirements specifications

AU - Al-Khanjari, Z.

AU - Jamoussi, Y.

AU - Kraiem, N.

AU - Al-Kindi, A.

AU - Al-Salti, X. F.

PY - 2015

Y1 - 2015

N2 - Software Requirement Specifications (SRS) provide a complete description of the software functionality, behavior and its constraints. Most bugs in software are due to incomplete or inaccurate software requirements. Testing SRS can identify the requirement conflictions and ambiguities and ensure the delivery of software which meets and satisfies the user requirements. The aim of the present study is to propose and implement an approach for testing SRS. The approach validates user requirement specifications against requirements specifications extracted from the corresponding ready software and produce a testing report. This study reports the development of the semi-automated SRS toolset that implements the proposed approach. This approach was formalized using MAP formalism which is a process model based on a non-deterministic ordering of goals and strategies. The SRS testing toolset extracts requirement specifications from the implemented software chosen to be an XML schema and compares them with SRSs from the user's perspective that are collected through a set of forms. Such toolset is expected to produce an informative validation report that indicates the degree of matching between the specifications and user requirements. To test the implemented tool, an input test case can be put which is an XML Schema sample and the corresponding user requirements specifications. The specifications for each test case are extracted manually and written out. Depending on the limitation of time, the number of test cases to be run will be three test cases; with complete entities, attributes and relationships, with some mismatches, with some mismatches but relationships.

AB - Software Requirement Specifications (SRS) provide a complete description of the software functionality, behavior and its constraints. Most bugs in software are due to incomplete or inaccurate software requirements. Testing SRS can identify the requirement conflictions and ambiguities and ensure the delivery of software which meets and satisfies the user requirements. The aim of the present study is to propose and implement an approach for testing SRS. The approach validates user requirement specifications against requirements specifications extracted from the corresponding ready software and produce a testing report. This study reports the development of the semi-automated SRS toolset that implements the proposed approach. This approach was formalized using MAP formalism which is a process model based on a non-deterministic ordering of goals and strategies. The SRS testing toolset extracts requirement specifications from the implemented software chosen to be an XML schema and compares them with SRSs from the user's perspective that are collected through a set of forms. Such toolset is expected to produce an informative validation report that indicates the degree of matching between the specifications and user requirements. To test the implemented tool, an input test case can be put which is an XML Schema sample and the corresponding user requirements specifications. The specifications for each test case are extracted manually and written out. Depending on the limitation of time, the number of test cases to be run will be three test cases; with complete entities, attributes and relationships, with some mismatches, with some mismatches but relationships.

KW - Design and development

KW - Formal verification

KW - SRS

KW - Testing database

KW - Validation

UR - http://www.scopus.com/inward/record.url?scp=84921469273&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84921469273&partnerID=8YFLogxK

U2 - 10.3923/rjit.2015.42.57

DO - 10.3923/rjit.2015.42.57

M3 - Article

VL - 7

SP - 42

EP - 57

JO - Research Journal of Information Technology

JF - Research Journal of Information Technology

SN - 1815-7432

IS - 1

ER -