Clarifying Non-functional Requirements to Improve User Acceptance – Experience at Siemens

Marhold, Christoph; Rohleder, Clotilde; Salinesi, Camille; Doerr, Joerg

doi:10.1007/978-3-642-02050-6_12

Cited by 9 publications

(1 citation statement)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Also because there is no consensus about them [8]. Christoph Marhod et al [9] show that there are many problems related to representing NFRs more than FRs. These problems causing the user non satisfaction and can expensive downtime or even complete failure of the system [10].…”

Section: Introductionmentioning

confidence: 99%

NFRs Model for Nuclear Power Plants

Shafei¹,

Sallam²,

Aref³

2017

IJSEA

View full text Add to dashboard Cite

Requirements analysis phase plays a vital role in drawing the performance and characteristics of critical software systems. As the requirements were global, detailed and complementary as the system was successfully functioning, free of errors and flaws, and adapted to environment dynamicity. In critical systems, such as Nuclear Power Plants (NPPs), implementing software functional requirements (FRs) is not enough to ensure system safety. Non-functional requirements NFRs implementation beside FRs becomes crucial for ensuring such function. NFRs performs other functions that are essentials for system availability, reliability, and dependability. NFRs should be supportive, not precluding to FRs, and keep system complexity and cost as low as possible. To this end, this paper proposes a model for NFRs which have importance in nuclear field based on safety system classification, and graded approach which assign the quality attributes and constraints to a given system based on its importance to safety. This model helps in enhancing the system overall safety without increasing the system complexity and implementation cost without need.

show abstract

Section: Introductionmentioning

confidence: 99%