A standards-based reference framework for system portability requirements

Abran, Alain; Al-Sarayreh, Khalid T.; Cuadrado-Gallego, Juan J.

doi:10.1016/j.csi.2012.11.003

Cited by 23 publications

(10 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [19], Bartholdt et aI., present IQSPLE (Integrated QualJty Software Product Line Engineering), an integrated tool-supported modeling approach that evaluates both q � alitati � e and quantitative quality attributes without imposing hierarchical structural constraints. In [20] [21] the authors propose a standards-based reference framework for the identification of system portability requirements. The � vail � bili� of this framework can facilitate the early IdentificatIOn and specification of the system portability NFR and their detailed allocation as specific portability functions to be handled by the specified allocation to hardware or software or a specific combination of the two.…”

Section: Related Workmentioning

confidence: 99%

Towards a variable non-functional requirements integration for Component-Based Product Line a generic approach

Hammani

Rhanoui

Asri

2014

2014 Second World Conference on Complex Systems (WCCS)

View full text Add to dashboard Cite

Software Product Line and Component-Based Software Engineering are two expanding paradigms for developing critical and complex systems. Therefore, these two paradigms seem have complementary strengths. So, significant benefits can be gained from their integration. Despite the fact that Non-Functional Requirements (such as security, performance and reliability) are critical to software systems, and they must be taken into account at early stage of software development life cycle and should be explicitly specified as well as functional requirements; these NFR are overlooked in Software Product line and Component-Based Software Development Processes. So, our main objective is to discuss some recent approaches in the field and to propose a new extension to Software Product Line processes that supports Component Based Approaches, and integrates Non-Functional Requirement in domain requirements stage.

show abstract

Section: Related Workmentioning

confidence: 99%

Towards a variable non-functional requirements integration for Component-Based Product Line a generic approach

Hammani

Rhanoui

Asri

2014

2014 Second World Conference on Complex Systems (WCCS)

View full text Add to dashboard Cite

show abstract

“…For the former, there are a few international functional sizing standards, such as ISO 19761. For the latter, there is recent work linking measurement with ISO 19761 to the non functional requirements described in the European ECSS set of standards [10].…”

Section: Standards and The Economy Information Asymmetrymentioning

confidence: 99%

Using the ISO 19761 COSMIC Measurement Standard to Reduce “Information Asymmetry” in Software Development Contracts and Enable Greater Competitiveness

Souto¹,

Abran²

2013

Self Cite

View full text Add to dashboard Cite

In most economic transactions involving software development projects, differences in the amount and quality of information possessed by economic agents (i.e. producers and customers) can lead to significant market inefficiencies. This paper describes the way the information derived from the functional size of software measured using the ISO 19761 COSMIC measurement standard that can help reduce information asymmetry in software development transactions, and lead to increased competitiveness in the software industry.

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%

See 1 more Smart Citation

A standard-based reference framework for system operations requirements

Al-Sarayreh

Al‐Oqily

Meridji

2013

IJCAT

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

A standards-based reference framework for system portability requirements

Cited by 23 publications

References 4 publications

Towards a variable non-functional requirements integration for Component-Based Product Line a generic approach

Towards a variable non-functional requirements integration for Component-Based Product Line a generic approach

Using the ISO 19761 COSMIC Measurement Standard to Reduce “Information Asymmetry” in Software Development Contracts and Enable Greater Competitiveness

A standard-based reference framework for system operations requirements

Contact Info

Product

Resources

About