Visualization and scheduling of non-functional requirements for agile processes

Abstract

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.

Improving agile requirements: the Quality User Story framework and tool

“…One exception is the rigorous set of validation checks by Zowghi and Gervasi [58] to detect errors in requirements specifications. As part of their NORPLAN framework, Farid and Mitropoulos [15] propose requirements quality metrics for non-functional requirements. Aside from ambiguity, however, these metrics are based on the processes related to requirements instead of the actual requirements themselves.…”

Investigating the Link between User Stories and Documentation Debt on Software Projects

“…To Predict Impacts of Changes: It is hard to assess the impacts and risks of adding new requirements [24].…”

Requirement Engineering Challenges in Agile Software Development

“…Tacit knowledge [73] Direct communication, observation, surveys, interviews, and the three factors: domain expert, communication process, and audience will help [40] Changing requirements [6,16,40,71,75] Use agile requirement change management readiness model (ARCMRM) [91], adopt 21 progress and success factors of ARCM [92], automated techniques, and tools to manage the requirement issues, i.e., JIRA and RE-KOMBINE [40,71,87] Requirement prioritization [74,77] Four stages based frame has been proposed [93] Negligence of nonfunctional requirements [40] Simulation tool NORMATIC for NFRs modeling [67], planning and visualization procedure, [94], NFR elicitation process [95] Complex software development projects such as supply chain management having unstable and uncertain requirement Long duration of RE due to complex decision making process, difficulty in creating and maintaining requirement priority list…”

“…Farid and Mitropoulos [67] proposed the javabased simulation tool NORMATIC for nonfunctional requirement modeling in agile development process. Planning and visualization procedure is presented to implement the NFRs in agile projects [94]. Younas et al [95] discussed about the user story cards, their attributes, and agile NFR elicitation process.…”