No abstract

No abstract

No abstract

No abstract

No abstract

We consider applicability of the e-learning at Hashemite University (HU) from different perspectives based on the academic major of students. The e-learning concept had professionally been applied on some majors offered at the HU and gained a great impact on the learning process, students and staff. The HU has made an excellent progress toward practicing e-learning environment through sequence of actions in real life scenario that overcome the limitations related to the traditional learning system. This paper presents the first study of multi-variate factors that influence the e-learning process at HU by applying the linear-regression, one-way ANOVA and Scheffe tests.

The nonfunctional requirements (NFR) are often captured only generically at a fairly high level, and they do not include the levels of detail necessary at this stage for the system engineers to allocate them as specific functionalities to be handled either by the software or the hardware, or a specific combination of the two. The European Cooperation for Space Standardization (ECSS) series of standards for the aerospace industry includes maintainability requirements as one of 16 types of NFR for embedded and real-time software. A number of maintainability-related concepts are dispersed throughout the ECSS, ISO 9126, and Institute of Electrical and Electronics Engineers standards to describe, at varying levels of detail, the various types of candidate maintainability requirements at the system, software, and hardware levels. This paper organizes these dispersed maintainability concepts into a standards-based reference model of system maintainability requirements. The availability of this reference model can facilitate the early identification of the system maintainability-NFR and their detailed allocation as specific maintainability functions to be handled by the specified allocation to hardware or software, or a specific combination of the two. In the absence of such a reference model, these NFR are typically handled in practice much later on in the software development life cycle, when at system testing time, users and developers find out that a number of maintainability requirements have been overlooked and additional effort has to be expended to implement them. The approach adopted in this research for the structure of this reference NFR model is based on the generic model of software functional requirements proposed in the COSMIC -ISO 19761 model, thereby allowing the functional size of such maintainability requirements allocated to software to be measured. Standardization (ECSS), the Institute of Electrical and Electronics Engineers (IEEE), and the International Organization for Standardization (ISO).In the ECSS standards for the aerospace industry [30][31][32][33], maintainability is identified as one of sixteen types of NFR, and in the ISO 9126 [34] and IEEE 830 [35] standards, a number of concepts are provided to describe various types of candidate maintainability requirements at the system, software, and hardware levels.However, these standards vary in their views, terminology, and coverage of maintainability. Currently, there exists no reference model for the identification and specification of software-FUR for implementing system maintainability requirements (system-NFR) on the basis of the various views documented in these international standards and in the literature. Consequently, it is challenging to measure maintainability-related software-FUR and take them into account quantitatively for estimating software projects.The research reported here, which focuses on a single type of NFR, that is, system maintainability requirements, describes the work carried out to define a reference model for system...

No abstract