A generic model for the specification of software reliability requirements and measurement of their functional size

Meridji, Kenza; Al-Sarayreh, Khalid T.; Al-Khasawneh, Ahmad

doi:10.1504/ijiq.2013.054279

Cited by 3 publications

(6 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…A few research is found in the literature on the identification and measurement of software requirements based on international standards (Abran et al, 2013;Al-Sarayreh et al, 2013a;Meridji et al, 2013;Al-Sarayreh et al, 2013b;2014;Al-Sarayreh and Abran, 2010). Most of research studies target the identification and measurement of software requirements at late phase of the software development life cycle (Khatter and Kalia, 2013).…”

Section: Introductionmentioning

confidence: 99%

Towards a Reference Model of Software Resources Quality

Almakadmeh¹,

Meridji²,

Al-Sarayreh³

2018

Journal of Computer Science

Self Cite

View full text Add to dashboard Cite

International standards for software product quality classify software resources as a non-functional requirement for software product. Resources requirements based-standards describe required resources requirements related to software and hardware requirements, in which hardware resources requirements specify requirements relevant to hardware environment in which the software will operate. Whereas, software resources requirements specify sizing and timing requirements required by software product. This paper propose a reference model to identify and measure resources requirements of software product quality based on ISO international standards. The proposed reference model is experimented to present its applicability using the software specifications of an ATM machine to identify and measure the functional size of resources requirements independently from development technology. This measure take place at an early phase of the software development life cycle and used by software project managers as one of the primary inputs for the effort estimation process of software products.

show abstract

Section: Introductionmentioning

confidence: 99%

Towards a Reference Model of Software Resources Quality

Almakadmeh¹,

Meridji²,

Al-Sarayreh³

2018

Journal of Computer Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…They may have a considerable impact on project effort, and should be taken into account for estimation purposes and in comparing project productivity. In the system analysis phase, the NFRs are typically described at the system level (Abran et al, 2013;Al-Sarayreh et al, 2012a, 2012bMeridji et al, 2013;Al-Khasawneh et al, 2013) and not at the software level. As yet, there is no consensus on how to describe and measure system NFR.…”

Section: Introductionmentioning

confidence: 99%

“…As yet, there is no consensus on how to describe and measure system NFR. In current practice, they may be viewed, defined, interpreted and evaluated differently by different people in the later project phases, particularly when they are stated vaguely and only briefly in the system requirements phase (Abran et al, 2013;Al-Sarayreh et al, 2012a, 2012bMeridji et al, 2013). It is challenging, therefore, to take them into account in software estimation and software productivity benchmarking, particularly as they have received less attention in the software engineering literature and are definitely less well understood than other cost factors (Chung and Leite, 2009).…”

Section: Introductionmentioning

confidence: 99%

“…In practice, requirements are initially typically addressed at the system level (Abran et al, 2013;Al-Sarayreh et al, 2012a, 2012bMeridji et al, 2013), either as high-level system Functional User Requirements (system FURs) or as high-level system NFRs. The latter must usually be detailed, allocated and implemented in either hardware or software, or both, as software FUR.…”

Section: Introductionmentioning

confidence: 99%

“…This paper proposes a generic model for the identification and specification of software FUR for implementing system operations requirements (system NFR) based on the various views documented in international standards and in the literature (Abran et al, 2013;Al-Sarayreh et al, 2012a, 2012bMeridji et al, 2013).…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A standard-based reference framework for system operations requirements

Al-Sarayreh

Al‐Oqily

Meridji

2013

IJCAT

Self Cite

View full text Add to dashboard Cite

European series of standards for the aerospace industry, includes system operations requirements as one of 16 types of NFRs for embedded and real-time systems. A number of concepts are provided in the ECSS and Institute of Electrical and Electronics Engineers (IEEE) standards to describe the various types of candidate operations requirements at the system, software and hardware levels. In the absence of such a generic and detailed model, these NFRs are typically handled much later on in the software development life cycle, when, at system testing time, users and developers may discover that a number of system operations requirements have been overlooked and additional work is required to implement them. This paper organises these dispersed operations concepts into a standards-based reference framework of system operations requirements.

show abstract