Search results

Nowadays, most of the software development processes still does not provide appropriate support for the development of secure systems. Rational Unified Process (RUP) is a well‐known software engineering process that provides a disciplined approach to assigning tasks and responsibilities; however, it has little support for development of secure systems. This work aims to present a proposal of RUP for the development of secure systems.

In order to obtain the proposed RUP, the authors consider security as a knowledge area (discipline) and they define workflow, activities and roles according to the architecture of process engineering Unified Method Architecture (UMA). A software development was used to assess qualitatively the extended RUP.

Based on the development, the authors find that the proposed process produces security requirements in a more systematic way and results in the definition of better system architecture.

The proposed extension requires specific adaptation if other development processes such as agile process and waterfall are employed.

The extension facilitates, the management of execution, and control of the activities and tasks related to security and the development teams can benefit by constructing better quality software.

The originality of the paper is the proposal of extension to RUP in order to consider security in a disciplined and organized way.

With the customers’ increasing expectation on the product value, manufacturing enterprises around the world have made significant efforts to provide high value-added services in addition to their traditional product development and manufacturing business. For this reason, it is of great importance to research product service system. The purpose of this paper is to research on the key problem of integrated product service system (IPSS) design.

A value-oriented IPSS is developed, which is set up based on “requirements-functions-processes-structures” mapping model to give full consideration to customer value and service functions. An extended product-service blueprint, which stems from the service blueprint, is developed to describe product behaviors, service deliver processes, stakeholders’ activities and supporting activities. An ontology-based design support system is proposed to improve design efficiency and help designers making better-informed decisions. A computer-aided prototype system has been developed, and an initial attempt has been made to demonstrate the role of IPSS in the aerospace industry.

Many traditional design methods cannot effectively address the objects and processes integration problem of products and services. Moreover, both product and service should be considered in IPSS design, and both of them extremely depend on designers’ own experience and knowledge. Thus, a broader range of knowledge is required to understand product-service system (PSS) design.

This research provides a solid foundation for PSS C and promotes an effective means for PSS design.

A customer value-oriented IPSS is presented. Customer requirements are considered during the design phase of PSS as well as both product and service knowledge.

Digital content management system is a software system that provides preservation, organization and dissemination services for digital collections. By adapting the systems analysis process, the University of Arizona Library analyzed its needs and developed content management system requirements for finding a suitable information system that addresses the increasing needs of digital content management. Dozens of commercial and open source candidates were examined to match against the requirements. This article provides detailed analysis of three major players (Greenstone, Fedora, and DSpace) in key areas of digital content management: preservation, metadata, access, and system features based on the needs of the University of Arizona Library. This paper describes the process used to analyze and evaluate potential candidates and includes results of analysis to illuminate the process.

This paper presents a recommendation on how one requirement elicitation technique supports the other techniques in defining system requirement for a case-based system. A case-based lesson planning system aims to assist teachers in constructing quality lesson plans through its cycle which begins with case retrieval. To retrieve relevant lesson plans, appropriate inputs should be used and the intended output needs to be identified via suitable requirement elicitation techniques. The use of a single technique might result in inadequate requirement specification, thus affecting the quality of the output requirements as well as quality of the final information system.

Requirement elicitation was carried out in three phases: phase I involved document review, phase II was an interview and phase III used a survey. Respondents of the study comprised experienced teachers as well as new teachers. This research used both qualitative and quantitative approaches to answer the research questions, which involved semi-structured interviews, document review and survey to collect the relevant data. Documents were reviewed by analysing lesson plans from three different countries. In addition, a review of lesson plans prepared by teachers and the standard syllabus were carried out. Findings from the document review were used in structured interviews using a teach-back technique, sorting and matrix of attribute-values. A questionnaire was then constructed based on the interviews and document review.

The findings of this initial study, as part of a larger research investigation, would help in knowledge modelling and representation. This will contribute to effective case retrieval via good design of the system input and output. The study identifies important elements of a lesson plan according to their ranking. Keywords that were used by teachers as input for retrieval were identified together with the expected output.

The main goal of requirement elicitation is to specify complete and detailed requirements of the proposed system. There are two main types of requirement: functional and non-functional requirements. This paper only focuses on functional requirements – specifically case retrieval with appropriate input and output.

Various requirement engineering (RE) techniques can be applied in different phases of requirement elicitation. Suitable technique should be chosen at different phases of RE, as it is important for triangulation purposes. Incomplete RE will affect the modelling part of system development, and, thus, affect the design and implementation of an information system.

Software engineer or anybody involved in system development should plan accordingly for the RE process. They should be creative and reasonable in selecting suitable RE techniques to be applied.

This study aims to gain understanding of the various aspects of lesson planning. Crucial knowledge in lesson planning that was gathered from the elicitation phase is modelled to have a good understanding of the problems and constraints among teachers. The findings of this initial study, as part of a larger research investigation, would help in knowledge modelling and representation. This will contribute to effective case retrieval via a good design of the system input and output.

Most Higher Education Institutions (HEIs) have silos of distributed processes, which adds to the confusion and conflict concerning the Customer Relationship Management (CRM), desires, expectation and needs (DEN). Where possible, in order to maximise resource impact and minimise organisational disruption, HEIs should practically map these DEN to processes, roles, events, activities, channels, and technologies (PRE-ACTs) that already exist within the organisation. The paper iteratively considers use of additional practical approaches that need be considered in order to ensure that strategic HEI CRM DEN are effectively captured, and that the requirements are appropriately mapped to existing HEI activities.

Content from 27 JISC cases, 10 semi-structured interviews and three focus group sessions have been collected and analysed using thematic analysis to understand how to develop preliminary stage 2 steps and assess the applicability of the final CRM strategy orientation support (CRM-SOS) framework stage 2 methods.

The authors believe that this study provides substantial practical support to CRM implementation practitioners when analysing customer CRM desires, expectation, and needs requirements. The developing practical tools aim to 1) support practitioners better comprehend the multifaceted life cycles, needs, and requirements of HEI customers, and 2) aid in the planning and management of CRM change more effectively.

The paper is extending the recent research around CRM strategy in HEIs by proposing additional practical approaches that need be considered to ensure that strategic CRM are effectively captured. The paper also offers considerable practical support to CRM implementation practitioners when analysing customer CRM desires, expectation, and needs' requirements.

Very few high technology acquisition projects are successful. Problems occur far too often, regardless of whether one is acquiring clinical or business information systems, patient monitoring systems, or therapeutic and diagnostic systems. The odds are good that the project will be delivered late, cost far more than predicted, and not provide all of the features promised. Only 9 percent of projects are on time and under budget, and only about 16 percent deliver what was promised. The principal reason for project failure is improper management of the requirements of the system. Requirements engineering and management (REAM) is a skill from the systems engineering profession that can be learned by nearly any professional who is managing a technology acquisition project. This paper will tell you what REAM is and how it is done.

The purpose of this paper is to examine the concept of quality related to the context of software development using the ISO, TickIT and CMM frameworks. The paper also seeks to stress the fact that the different perspectives of those involved in software development will influence how quality is seen and measured. In the context of software engineering projects, quality takes on a broad meaning that refers not only to the way in which companies manage software engineering projects, but also to the software development process itself.

The approach and methodology adopted for this paper were a review of the literature and best practice in software engineering. It is argued that users of software systems are more interested in how easy the software is to use than in the underlying application code that is used to generate the system. Using the body of knowledge that is software quality the basic characteristics of software quality are described and compared in terms of quality standards such as ISO, TickIT and CMM. Each of these standards is decomposed further in order to clarify its usefulness.

The findings in the paper suggest that, whilst there are many differences in the quality standards used, there are a number of similar characteristics. In essence the underlying philosophies of ISO and CMM have at the core the same goals. Some academics see CMM as being technically over‐engineered; a CMM‐compliant quality system is in many respects far in advance of ISO.

This paper helps define the strengths and weaknesses within ISO, TickIT and CMM from a software engineering practitioner perspective.

The paper shows that software engineers need to pay more attention to the performance and conformance issues in software projects and to be proactive rather than reactive to quality issues.

It may be argued that the importance of this paper lies in the assertion that those engaged in the software engineering are in need of a multi‐perspective view on quality and, with that in mind, this paper should appeal to practitioners and members of the academic community with an interest in software quality.

The purpose of this paper is to present the proposal of a Product Line (PL)-based approach for Business Process Management (BPM) projects that cover the entire BPM lifecycle and proposes integrating it with dynamic techniques still not used together.

The authors carried out this work using the design science research methodology. The authors assessed the proposed approach using a classification procedure created through a series of specific attributes, which enables a comparison of the proposed integrated approach with related works selected from a systematic literature review.

The comparative assessment has shown that the proposed approach presents the most comprehensive solution than any other similar one suggested for the same purpose, mainly in terms of the coverage of the entire BPM lifecycle and dynamic techniques.

Due to the high-level conceptual nature of the proposed approach, the authors could not evaluate it also in terms of some controlled experiment or a case study.

The proposed approach aims at improving the management of business processes in organizations in a systematic way using concepts and techniques that exist in other areas, but not widely used together yet, such as BPM, service-oriented computing, and Software PL.

The purpose of this paper is to analyze cloud reviews according to the end-user context and requirements.

propose a comprehensive knowledge base composed of interconnected Web Ontology Language, namely, modular ontology for cloud service opinion analysis (SOPA). The SOPA knowledge base will be the basis of context-aware cloud service analysis using consumers' reviews. Moreover, the authors provide a framework to evaluate cloud services based on consumers' reviews opinions.

The findings show that there is a positive impact of personalizing the cloud service analysis by considering the reviewers' contexts in the performance of the framework. The authors also proved that the SOPA-based framework outperforms the available cloud review sites in term of precision, recall and F-measure.

Limited information has been provided in the semantic web literature about the relationships between the different domains and the details on how that can be used to evaluate cloud service through consumer reviews and latent opinions. Furthermore, existing approaches are lacking lightweight and modular mechanisms which can be utilized to effectively exploit information existing in social media.

The SOPA-based framework facilitates the opinion based service evaluation through a large number of consumer's reviews and assists the end-users in analyzing services as per their requirements and their own context.

The SOPA ontology is capable of representing the content of a product/service as well as its related opinions, which are extracted from the customer's reviews written in a specific context. Furthermore, the SOPA-based framework facilitates the opinion based service evaluation through a large number of consumer's reviews and assists the end-users in analyzing services as per their requirements and their own context.

This paper aims to explore the use of the knowledge management (KM) perspective for configuration projects. Configuration projects implement configurators as information technology systems that help companies manage the specification process of customised products. An effective method of retrieving and formalising knowledge for configurators is essential, because it can reduce the risk of unsuccessful implementation and the time and effort required for development. Unfortunately, no standard KM frameworks are available specifically for configuration projects. This study identifies the knowledge necessary for different phases of a configuration project (which knowledge, for what purpose and from what sources), examines how it is transformed during a configuration project (what KM activities and tools are used) and establishes how the knowledge can be documented for future maintenance and updates.

This paper proposes a four-step framework for making the KM process more efficient in configuration projects. The framework is based on the literature, developed in collaboration with industrial partners and tested on four configuration projects in two engineering companies. The framework is a structured KM approach designed to save time for both domain experts and the configuration team. The authors have used a qualitative exploratory design based on multiple data sources: documentation, workshops and participant observation.

The proposed framework comprises four steps: determination of the system’s scope, to establish the project’s goal based on stakeholders’ requirements and prioritise the required products and processes; knowledge acquisition, to classify the knowledge according to the desired output and identify different knowledge sources; modelling and knowledge validation; and documentation and maintenance, to ensure that the KM system can be maintained and updated in the future.

Because the framework is tested on a limited number of cases, its generalisability may be limited. However, focusing on a few case applications allows us to assess the effectiveness of the framework in detail and in depth to identify the practical challenges of applying it. The results of the tests support the framework’s validity. Although the framework is designed mainly for engineering companies, other industries could benefit from using it as well.

The individual steps of the framework create a structured approach for the KM process. Thus, the approach can save both time and resources for companies, without the need for additional investment.

A standard framework is lacking in the literature on KM for configuration projects. This study fills that gap by developing a KM framework for configuration projects, based on KM frameworks developed for IT projects, and KM tools.