IEEE Style Citation: Saurabh Dhupkar, “Tree Structure of Requirements and HKEH Prioritization,” International Journal of Computer Sciences and Engineering, Vol.7, Issue.5, pp.1243-1247, 2019.
MLA Style Citation: Saurabh Dhupkar "Tree Structure of Requirements and HKEH Prioritization." International Journal of Computer Sciences and Engineering 7.5 (2019): 1243-1247.
APA Style Citation: Saurabh Dhupkar, (2019). Tree Structure of Requirements and HKEH Prioritization. International Journal of Computer Sciences and Engineering, 7(5), 1243-1247.
BibTex Style Citation:
@article{Dhupkar_2019,
author = {Saurabh Dhupkar},
title = {Tree Structure of Requirements and HKEH Prioritization},
journal = {International Journal of Computer Sciences and Engineering},
issue_date = {5 2019},
volume = {7},
Issue = {5},
month = {5},
year = {2019},
issn = {2347-2693},
pages = {1243-1247},
url = {https://www.ijcseonline.org/full_paper_view.php?paper_id=4395},
doi = {https://doi.org/10.26438/ijcse/v7i5.12431247}
publisher = {IJCSE, Indore, INDIA},
}
RIS Style Citation:
TY - JOUR
DO = {https://doi.org/10.26438/ijcse/v7i5.12431247}
UR - https://www.ijcseonline.org/full_paper_view.php?paper_id=4395
TI - Tree Structure of Requirements and HKEH Prioritization
T2 - International Journal of Computer Sciences and Engineering
AU - Saurabh Dhupkar
PY - 2019
DA - 2019/05/31
PB - IJCSE, Indore, INDIA
SP - 1243-1247
IS - 5
VL - 7
SN - 2347-2693
ER -
VIEWS
PDF
XML
293
244 downloads
121 downloads
Abstract
Requirement gathering is one of the most crucial phases in the software development life cycle and the change life cycle. Any discrepancy in requirements leads to Technical Debt , has comparatively more impact than other phases of the software development life cycle and has an adverse impact on the software life expectancy. Most of the times, requirements discussed are very superficial that leads to architects and developers assuming so many details. These assumptions mostly end up being discrepancies. Therefore, having precise complete and unambiguous requirements in the initial phase makes the design and development less error prone due to reduced or minimized surprises. Thus, adequate and unambiguous requirements are the key elements of software success.
Along with un-ambiguity and completeness, correct prioritization is vital. Incorrect or misleading prioritization results into inaccurate estimation and unmanageable scope. Therefore having a common vocabulary for prioritization along with precise and detailed requirements can help keeping Technical Debt minimized and longer life expectancy of the software.
There are many techniques of the requirement gathering. In this paper, this author proposes a method for requirement structuring and prioritization.
[1] Microsoft Corporation, Canada, “Microsoft Attention Spans Research Report”, www.scribd.com. [Online] Spring 2015
[2] S. S. Dhupkar, “Measuring Software Life Expectancy”, International Journal of modern Trends in Engineering and Research, Vol. 3, Issue 10, pp. 178-184, 2016
[3] S. S. Dhupkar, “Technical Debts, Impact and Settlement”, International Journal for Research in Applied Science and Engineering Technology, Vol. 5, Issue 11, 2017
VIEWS
PDF 
XML 
