The NORMAP Methodology: Lightweight Engineering of Non-functional Requirements for Agile Processes

Farid, Weam M.

doi:10.1109/apsec.2012.23

Cited by 22 publications

(26 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The fundamental objective of the NORMAP Methodology [11] was to research and develop a systematic yet simple NFR modeling framework for agile processes. The framework design objectives included integrating both FRs and NFRs in a single framework that visually links NFRs to FRs using a color-coded downscaled version of Chung's NFR Framework [7].…”

Section: A the Normap Methodology: An Overviewmentioning

confidence: 99%

“…The NORMAP Methodology [11] proposed fundamental project management and requirements quality metrics that were deemed essential for developing a riskdriven requirements implementation sequence algorithm. First, the project management metrics include multifaceted types of metrics such as planning metrics, team development and technology metrics, and agile process maturity metrics.…”

Section: B Agile Planning Using Project Management Metricsmentioning

confidence: 99%

“…Because Scrum requires engineering excellence through continuous inspection and adaptation [6], such adaptation should also be reflected in agile yet accurate planning through visual planning tools to support such objectives. Our initial research addressed issues such as the identification and linking of NFRs with FRs through the proposal of the Non-functional Requirements Modeling for Agile Processes (NORMAP) methodology [9][10] [11]. However, one major area that deserves further research is the interdisciplinary approach of combining Agile Project Scheduling with the modeling of Agile NFRs.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Visualization and scheduling of non-functional requirements for agile processes

Farid

Mitropoulos

2013

2013 Proceedings of IEEE Southeastcon

Self Cite

View full text Add to dashboard Cite

Agile software development and project management methodologies, such as Scrum and Extreme Programming, have become very popular in quickly delivering quality Functional Requirements (FRs). However, agile project management methodologies have not adequately captured planning and visualization activities for crosscutting concerns and non-functional requirements in agile practices. This research proposes a planning and visualization framework that would be used to schedule software non-functional requirements implementations while utilizing agile software development and project management agile techniques. The approach is validated through visual simulation and a case study. Results showed that utilizing a risk-driven agile planning approach that involve non-functional requirements resulted in shortening the project schedule by one to two months over a traditional "Highest-Business-Value-First" agile scheduling technique.

show abstract

Section: A the Normap Methodology: An Overviewmentioning

confidence: 99%

Section: B Agile Planning Using Project Management Metricsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Visualization and scheduling of non-functional requirements for agile processes

Farid

Mitropoulos

2013

2013 Proceedings of IEEE Southeastcon

Self Cite

View full text Add to dashboard Cite

show abstract

“…Usually, a manual process is adopted for identification of NFR from FR by the requirement engineers. There are some studies that proposed manual, semi automated and automated solutions for identification of NFR in a document [26]- [29]. The pre-processing techniques have a significant role in improving the performance of machine…”

Section: Automated Approach For Nfr Identificationmentioning

confidence: 99%

“…During the requirement elicitation phase, the primary emphasis is on gathering functional requirements, however, NFRs are overlooked. The nature of agile software methodology is also a reason to ignore NFRs [1]. This ignorance of NFRs becomes a cause to produce significant cost issues in software system [2].…”

Section: Introductionmentioning

confidence: 99%

An Automated Approach for Identification of Non-Functional Requirements using Word2Vec Model

Younas¹,

Wakil²,

Jawawi³

et al. 2019

IJACSA

View full text Add to dashboard Cite

Non-Functional Requirements (NFR) are embedded in functional requirements in requirements specification document. Identification of NFR from the requirement document is a challenging task. Ignorance of NFR identification in early stages of development increase cost and ultimately cause the failure of the system. The aim of this approach is to help the analyst and designers in architect and design of the system by identifying NFR from the requirements document. Several supervised learningbased solutions were reported in the literature. However, for accurate identification of NFR, a significant number of pre-categorized requirements are needed to train supervised text classifiers and system analysts perform the categorization process manually. This study proposed an automated semantic similarity based approach which does not needs pre-categorized requirements for identification of NFR from requirements documents. The approach uses an application of Word2Vec model and popular keywords for identification of NFR. Performance of approach is measured in term of precision-recall and F-measure by applying the approach to PROMISE-NFR dataset. The empirical evidence shows that the automated semi-supervised approach reduces manual human effort in the identification of NFR.

show abstract