Proposing a Systematic Approach to Verify Software Requirements

Al-Khanjari, Zuhoor

doi:10.4236/jsea.2014.74023

Cited by 6 publications

(3 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…1. Articles, in which questions of assessment at the level of separate requirements are reviewed, that are not connected to a single software requirements profile [6][7][8][9]. Approach for assessment of single software requirement and software requirements profile has some differences.…”

Section: Related Work Analysismentioning

confidence: 99%

Profile-Oriented Assessment of Software Requirements Quality: Models, Metrics, Case Study

Gordieiev¹,

Kharchenko²

2020

IJC

View full text Add to dashboard Cite

The article is devoted to profile-oriented approach to assessing the software requirements profile quality. The process of assessment is implemented in accordance with software requirements profile quality model for external quality of software requirements profile and internal quality of software requirements profile. For assessment of quality of each element of such model (characteristics and attributes of software requirements and their classification features; characteristics and attributes of software requirements profile and their classification features; structure of software requirements profile; semantics and syntax of software requirements) taxonomy of metrics and indicators are introduced, which is a part of software requirements profile quality assessment model. All metrics are divided into qualitative and quantitative groups. Additive convolution method is used to go from the multi-vector values of set of connected indicators or metrics to the single scalar value. Received values of metrics and indicators are visualized by radial-metrics diagrams. An example is discussed, which represents the assessment of external quality of software requirements profile for requirements profile from new standard “Requirements to computer security of NPP Instrumentation and Control Systems (NPP I&C)” developed by Ukrainian state regulatory body.

show abstract

Section: Related Work Analysismentioning

confidence: 99%

Profile-Oriented Assessment of Software Requirements Quality: Models, Metrics, Case Study

Gordieiev¹,

Kharchenko²

2020

IJC

View full text Add to dashboard Cite

show abstract

“…Stakeholders can be defined as anyone who is directly or indirectly affected by the system being developed or deployed [16]. M-learning stakeholders includes: learners, instructors, administrators and technician staff.…”

Section: Stakeholdersmentioning

confidence: 99%

Proposing A new Design Approach for M-learning Applications

Al-Harrasi

Al-Khanjari²,

Sarrab³

2015

IJSEIA

View full text Add to dashboard Cite

As Information and Communication Technologies (ICT) are developing frequently, new learning approaches have been introduced to facilitate teaching and learning processes. Mobile devices are growing in popularity and there has been an increasing interest in their potential as innovative tools for learning. Mobile learning or shortly (M-learning) is a new learning approach intending to use mobile devices such as laptops, smart phones and personal digital assistant (PDA) in learning process in any place and at any time. M-learning application needs to be designed in a way that considers the special features and constraints of mobile devices such as screen size, available storage, processor speed and battery life. This paper explores the existing design approaches for M-learning and highlights their main limitations. As a step forward in this direction, this paper also proposes a new design approach for M-learning applications focusing mainly on three main aspects: learner, learning content and technology. The approach consists of three phases: starting dimensions (SD) phase, M-learning Development (MLD) phase and Learning Content Design (LCD) phase. Finally, this paper provides a case study scenario to demonstrate the feasibility of the proposed approach.

show abstract

“…The need analysis or requirement analysis is a very important aspect to be clarified when developing any new software. Al-Khanjari (2014) [6] proposed a tool as a cross check technique to help in reducing the conflicts between software developers and system stakeholders. In order to compromise requirements stated on the basis of different viewpoints, Quality Models have been introduced as the engineering artifact to define the quality factors that apply to web service usage.…”

Section: Introductionmentioning

confidence: 99%

Towards a Comprehensive View of Web Services QoS Models

Al-Kalbani

Kraïem

Al-Khanjari

et al. 2015

IJMUE

View full text Add to dashboard Cite

In a growing web services environment, the usage, design and composition methods of web services require proper and reliable information about web services quality. Qualityof-Service (QoS) is usually referred to the non-functional characteristics of web services which can be used as an important role to differentiate between different web services. In order to select the best web services among those with similar functionality, it is important for the web requester to have a mechanism to rank them and also from the service providers side to ensure that their web services are according to the agreed QoS. Currently there is no standard manner to define the QoS characteristics of web services. Many studies have shown different categorization of QoS which led to the issue of semantic interoperability of QoS. One way to understand the QoS, is to identify all its possible requirements for web services. This paper is an attempt to explore some of the QoS issues which are essential for web services. It first proposes a QoS framework which suggests considering QoS for web services along four different views. Each view is representing a particular relevant facet of QoS models. The main contribution of this paper is to show that there is a big quantity and variety of interpretations of various service quality concepts and models and gives the reasons why there is no holistic QoS modeling approach.

show abstract

Proposing a Systematic Approach to Verify Software Requirements

Cited by 6 publications

References 17 publications

Profile-Oriented Assessment of Software Requirements Quality: Models, Metrics, Case Study

Profile-Oriented Assessment of Software Requirements Quality: Models, Metrics, Case Study

Proposing A new Design Approach for M-learning Applications

Towards a Comprehensive View of Web Services QoS Models

Contact Info

Product

Resources

About