REQUIREMENT VALIDATION VS. REQUIREMENT ELICITATION
Current Language EN
English English Türkçe Türkçe Español Español Português Português Pусский Pусский Filipino Filipino Tiếng Việt Tiếng Việt हिन्दी हिन्दी العربية العربية বাংলা বাংলা Deutsch Deutsch 中文 中文

REQUIREMENT VALIDATION VS. REQUIREMENT ELICITATION

PANDEY, DHIRENDRA; KHAN, MOHD. WARIS; PANDEY, VANDANA
International Journal of Computer and Communication Technology 2016 pp. 1-8
2
dhirendra2016requirement

Abstract

To support the evocation and validation of the goals achieved by the existing system and to illustrate problems of the old system, we suggest to capture current system usage using rich media (e.g., video, speech, pictures, etc.) and to interrelate those observations with the goal definitions .Therefore it becomes necessary to relate the parts of the observations which have caused the definition of a goal or against which a goal was validated with the corresponding goal in every phase of software development process. These interrelations provide the base for: 1) explaining and illustrating a goal model to, e.g., untrained stakeholders and/or new team members, and thereby improving a common understanding of the goal model; 2) detecting, analyzing, and resolving a different interpretation of the observations; 3) comparing different observations using computed goal annotations; and 4) refining or detailing a goal model during later process phase. Using the PRIME implementation framework, we have implemented the PRIME-CREWS environment, which supports the interrelation of conceptual models and captured system usage observations. We report on our experiences with PRIME-CREWS gained in a first experimental case study. The successful implementation of proposed requirement evocation and validation process can have a good impact on the production of quality software product.

Access

DOI:
10.47893/ijcct.2016.1324
URL:
https://doi.org/10.47893/ijcct.2016.1324

Citation

ID: 284251
Ref Key: dhirendra2016requirement
Use this key to autocite in SciMatic or Thesis Manager

References

References

No Bibliography

Blockchain Verification

Account:
NFT Contract Address:
0x95644003c57E6F55A65596E3D9Eac6813e3566dA
Article ID:
284251
Unique Identifier:
10.47893/ijcct.2016.1324
Network:
Scimatic Chain (ID: 481)
Blockchain Readiness Checklist
Authors
Abstract
Journal Name
Year
Title
5/5
Creates 1,000,000 NFT tokens for this article
Token Features:
  • ERC-1155 Standard NFT
  • 1 Million Supply per Article
  • Transferable via MetaMask
  • Permanent Blockchain Record
Blockchain QR Code
Scan with Saymatik Web3.0 Wallet
Gas fees required in SCI Coins
Buy SCI

Saymatik Web3.0 Wallet

Google Play
App Store