Search results

As systems get complex, requirements elicitation and analysis are becoming increasingly difficult and important in software development. Even though various analysis methods have been proposed, including scenario‐based analysis, goal‐based analysis, combining goal with scenario and use case‐driven analysis – each method has its own strengths and weaknesses and do not support requirements elicitation and analysis efficiently. This paper proposes a multi‐view approach to analyze the requirements of complex software systems. The multi‐view approach comprises four views, which incorporate many factors that are part of existing methods. This paper discusses the need for these four views, the activities that are part of each view and how they are carried out. As a proof of concept, we apply the multi‐view approach to an automatic teller machine system development.

Although requirement elicitation is generally acknowledged to be very important in traditional information systems development (ISD), it does not get enough attention in most Web‐based information systems development (WISD). This paper highlighted the difference between ISD and WISD, and proposed a three‐stage model of user requirements elicitation for Web‐based information systems. This model divides the requirements definition into three stages: initial analysis, key user requirements elicitation and regular user responses. Most current WIS design methodologies consider only initial analysis, and neglect actual users’ requirements. Key user input is emphasized in this model, and social network analysis is proposed as a tool for identifying key users. Requirements analysis for WISD is no longer considered a one‐stop step, but is better regarded as a continuous evolving process. Finally, managerial implications are also provided in this paper.

The purpose of this paper is to elicit tacit knowledge exhibited in expert information system (IS) professionals in a form that can be shared with others; and to develop categorical framework suggesting key content areas of tacit knowledge in the requirements analysis domain.

Requirements analysis is selected as the main focus of this study due to the importance of this phase to the success of IS development and the nature of requirements analysis tasks requiring extensive amount of tacit knowledge. The authors used the “storytelling” approach, a semi-structured interview technique for knowledge elicitation.

The study resulted in 132 knowledge items using a qualitative method and categorized them into 14 categories using cluster analysis. The study found that experienced, successful analysts see systems analysis in behavioral, managerial, and political terms and focus heavily on interpersonal, project management, and organizational issues.

The limitations in the research sample, or in the recollection capability of the research subjects could compromise the comprehensiveness of the tacit knowledge in the requirements analysis domain; however, the elicited knowledge at least represents important dimensions one might reasonably find in this domain.

Very little research has attempted to capture this tacit dimension of system analysts’ knowledge. Thus, capturing and transferring the tacit knowledge from experts should help in the evolution of novice to expert system analysts thereby improving both their effectiveness and the quality of the information systems developed.

This paper aims to analyze high-quality papers on the research of electronic word-of-mouth (eWOM) for product and service quality improvement from 2009 to 2022, in order to fully understand their historical progress, current situation and future development trend.

This paper adopts the bibliometrics method to analyze the relevant literature, including publishing trend and citation status, regional and discipline area distribution, and influential publications. Secondly, the VOSviewer is used for literature co-citation analysis and keyword co-occurrence analysis to obtain the basic literature and research hotspots in this research field.

Firstly, the study finds that the number of publications basically shows an increasing trend, and those publications are mainly published in tourism journals. In addition, among these papers, China has the largest number of publications, followed by the USA and South Korea. Through co-citation analysis of literature and keyword co-occurrence analysis, 22 foundational papers and six main research topics are obtained in this paper. Finally, this paper elaborates on the development trend of the research topic and future research directions in detail.

This is the first paper that uses bibliometrics to analyze and review relevant researches on eWOM for product and service quality improvement, which is helpful for researchers to quickly understand its development status and trend. This review also provides some future research directions and provides a reference for further research.

“The offshore installations and wells (design and construction, etc.) regulations” (DCR) requires that all safety‐critical elements in both the system and software domains be assessed and evaluated. In this paper, following a brief review of offshore system (application) safety analysis, offshore software safety analysis is introduced. It is followed by a study of combining offshore system safety analysis with software safety analysis. The typical standards for the development of safety‐critical systems in several industrial sectors are discussed with particular reference to formal methods. A generic offshore software safety analysis framework is proposed with discussions. Formal methods for producing safety requirements specifications are then discussed. A case study is used to demonstrate safety requirements modelling for safety‐critical software development. Finally recommendations for further development in offshore software safety analysis are given.

This paper aims to explore the requirements of organizational knowledge management initiatives using requirements engineering techniques, identifying the optimal techniques configuration and serving as a management tool for knowledge engineers.

The method is selection attributes. Knowledge management enablers are characterized and mapped with the coverage capabilities of requirements engineering techniques, using the attributes of the elicited object and a box-plot analysis. The information is gathered from 280 references, 32 companies and 16 experts in requirements engineering.

Requirements of organizational knowledge management initiatives are got optimally by combining interviews, use cases, scenarios, laddering and focus group techniques. The requirements of structure and processes are more complex to identify, while culture requirements are the best covered.

Knowledge management enablers are analyzed according to the current studies and comprehension of engineering techniques.

Knowledge engineers need to consider the coverage capabilities of engineering techniques to design an optimal requirement identification and meet the objectives of organizational knowledge acquisition initiatives. Requirement engineers can improve the requirements identification by a staged selection process.

The requirements of knowledge management initiatives that impact the community can be identified and traced to ensure the knowledge objectives. Requirements related to culture and people, like shared values, beliefs, and behaviors, are also considered.

To the best of the authors’ knowledge, this is the first study about formal requirement identification of knowledge management initiatives in the organizational context, providing the optimal configuration. A novel staged process is proposed for requirements engineering techniques selection, analyzing the enablers at component level and identifying the attributes associated with the elicited object.

This study aims to provide a method for classifying travellers’ requirements to help hoteliers understand travellers’ requirements and improve hotel services. Specifically, this study develops a strength-frequency Kano (SF-Kano) model to classify the requirements expressed by travellers in online reviews.

The strength and frequency of travellers’ requirements are determined through sentiment and statistical analyses of the 13,217 crawled online reviews. The proposed method considering the interaction between strength and frequency is proposed to classify the different travellers’ requirements.

This study identifies 13 travellers’ requirements by mining online reviews. According to the results of the improved Kano model, the six travellers’ requirements belong to one-dimensional requirements; two travellers’ requirements belong to must-be requirements; three travellers’ requirements belong to attractive requirements; two travellers’ requirements belong to indifferent requirements.

Results of this research can guide hoteliers to address hotel service improvement strategies according to the types of travellers’ requirements. This study can also expand the analysis scope of hotel online reviews and provide a reference for hoteliers to understand travellers’ requirements.

By mining online reviews, this study proposes an SF-Kano model to classify travellers’ requirements by considering both the strength and frequency of requirements. This study uses the optimisation model to determine the classification thresholds. This process maximises travellers’ satisfaction at the lowest cost. The classification results of travellers’ requirements can help hoteliers gain a deeper understanding of travellers’ requirements and prioritise service improvements.

The purpose of this paper is to describe and analyze the benefits of the application of a requirements engineering framework to assist Enterprise Resource Planning (ERP) development. This framework combines the technology-driven and the process-driven approaches for requirements analysis and implementation. Specific business process modeling methods enhance the framework and assist the formulation of the functional specifications of the ERP system and the management of requirements.

A case study strategy was chosen as the most appropriate method to answer the research question and test the theoretical propositions. The case study’s unit of analysis is a Greek manufacturing company and its ERP implementation project. A requirements engineering framework enhanced with business process modeling methods was applied and the results were evaluated using metrics for ERP implementation success. Data were collected using multiple sources of evidences, including interviews with various stakeholders, structured questionnaires, direct observations, vendors’ functionality papers and company’s documentation.

This study proves that the configuration of ERP’s reference models together with the adjustments of organization’s processes, provided through a structured requirements engineering framework can lead to reliable functional specifications, a smooth transition to an ERP system and, eventually, to successful ERP implementation, concerning its alignment with requirements.

A single case study is conducted in a typical manufacturing company, providing opportunities for further research in other industries, testing in parallel well-defined requirements and other success factors for ERP implementation.

The paper fulfils the identified needs for applied methodologies and frameworks for requirements engineering which can assist successful ERP implementations.

A software product line (SPL) captures commonalities and variations (C&V) within a family of systems. Although, feature‐oriented approaches have been proposed for building product lines, none of them provide a systematic approach for identifying features. This paper proposes a domain analysis method for creating SPL based on scenarios, goals and features. In particular, the paper presents a domain requirements model (DRM) that integrates features with goals and scenarios, and a domain requirements modeling method that uses the DRM. This approach has been applied to the home integration system (HIS) domain to demonstrate its feasibility. This approach makes it possible to systematically identify features and provide the rationale for both features and C&V.

Job analysis is the common basis for designing a training course or programme, preparing performance tests, writing position (job) descriptions, identifying performance appraisal criteria, and job restructuring. Its other applications in human resource development include career counselling and wage and salary administration. Job analysis answers the questions of what tasks, performed in what manner, make up a job. Outputs of this analytical study include: (a) a list of the job tasks; (b) details of how each task is performed; (c) statements describing the responsibility, job knowledge, mental application, and dexterity, as well as accuracy required; and (d) a list of the equipment, materials, and supplies used to perform the job. Various techniques for conducting a job analysis have been used. Each has its advantages and disadvantages. As a result, different techniques or combinations of techniques are appropriate to different situations. The combined on‐site observation and individual interview techniques are recommended for industrial, trade, craft, clerical, and technical jobs because they generate the most thorough and probably the most valid information. A job analysis schedule is used to report the job information obtained through observations and individual interviews. The schedule provides a framework of 12 items in which to arrange and describe important job analysis information. These 12 items are organised into four sections. Section one consists of items one through four. These items identify the job within the establishment in which it occurs. The second section presents item five, the work performed. It provides a thorough and complete description of the tasks of the job. The Work Performed section describes what the job incumbent does, how it is done, and why it is done. Section three presents items six through nine. These are the requirements placed on the job incumbent for successful performance. It is a detailed interpretation of the basic minimum (a) responsibility, (b) job knowledge, (c) mental application, and (d) dexterity and accuracy required of the job incumbent. The fourth section includes three items which provide background information on the job. These items are: (a) equipment, materials and supplies; (b) definitions of terms; and (c) general comments. Appendix A is a glossary of terms associated with job analysis. It is provided to facilitate more exacting communication. A job analysis schedule for a complex and a relatively simple job are included in Appendices B and C. These examples illustrate how important job analysis information is arranged and described. Appendix D provides a list of action verbs which are helpful when describing the manipulative tasks of a job.