Managing non‐functional requirements in agile software development
Abstract Non‐functional requirements define qualities of the software system that ensure effectiveness while embedding any constraints and restrictions on the design. A challenge rises with agile implementation in handling non‐function requirements in regulated environments. Thus, a practitioner...
Saved in:
| Main Authors: | Scarlet Rahy, Julian M. Bass |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
Wiley
2022-02-01
|
| Series: | IET Software |
| Subjects: | |
| Online Access: | https://doi.org/10.1049/sfw2.12037 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Similar Items
-
Requirements‐related fault prevention during the transformation from formal specifications to programs
by: Jiandong Li, et al.
Published: (2023-06-01) -
Social loafing prevention in agile software development teams using team expectations agreements
by: Ilenia Fronza, et al.
Published: (2021-06-01) -
The Formalism and Language Tools for Semantics Specification of Software Libraries
by: V. M. Itsykson
Published: (2016-12-01) -
What have we learnt from the challenges of (semi‐) automated requirements traceability? A discussion on blockchain applicability
by: Selina Demi, et al.
Published: (2021-12-01) -
Prioritization of global software requirements' engineering barriers: An analytical hierarchy process
by: Muhammad Azeem Akbar, et al.
Published: (2021-08-01)