Design as Intercultural Dialogue: Coupling Human-Centered Design with Requirement Engineering Methods

The use of information systems in an organization has become an obligation to support the organization’s business process. However, the development of an Information System still often faces problems, the most important problem occurs in the requirements engineering phase where developers try to meet user needs, these problems can also increase when user needs are not following the standards in general. The objective of this research is to design a digital library information system based on the organization goal-oriented requirements engineering (OGORE) method. OGORE is a Requirements Engineering method that focuses on organizational needs and is expected to eliminate the (noise) needs of users. The OGORE method has been used since its goal is to reduce the risks that arise because of user needs based on personal desires. The Development Method used is the Extreme Programming (XP) method. Data collection methods used were observation, interview, and literature study. With OGORE method, the results of a Library Information System can fulfil all the vision and mission of the library.

The importance of the role that knowledge management (KM) plays in the success of knowledge-intensive organizations has long been acknowledged. However, requirements engineering (RE) methods for KM solutions still lack maturity, as do the educational programs in this domain. In this paper, an agile-based educational method for teaching RE for KM solutions, specifically an agile KM RE methodology (AKM-REM), is proposed. The paper reports a teaching experience, in which 17 teams of graduate students learned and implemented AKM-REM, each in a different real-life case study. Data were collected via class observations and from the students’ submitted projects and underwent qualitative content analysis. The findings demonstrate the manner in which AKM-REM creates a culture of collaboration, trust, and reflection, fostering the dynamic and flexible organization that is required in today’s competitive business environment. The contribution of this paper is fourfold. First, it presents an extension of the research on agile-based RE for KM solutions as a specialized area. Second, it presents an extension of an existing method KM-REM along the agile principles. Third, it provides means for agile-based education for analyzing and addressing KM challenges effectively. Finally, it describes the importance of agile KM RE in the context of sustainability.

An effective network security requirement engineering is needed to help organizations in capturing cost-effective security solutions that protect networks against malicious attacks while meeting the business requirements. The diversity of currently available security requirement engineering methodologies leads security requirements engineers to an open question: How to choose one? We present a global evaluation methodology that we applied during the IREHDO2 project to find a requirement engineering method that could improve network security. Our evaluation methodology includes a process to determine pertinent evaluation criteria and a process to evaluate the requirement engineering methodologies. Our main contribution is to involve stakeholders (i.e., security requirements engineers) in the evaluation process by following a requirement engineering approach. We describe our experiments conducted during the project with security experts and the feedback we obtained. Although we applied it to evaluate three requirements engineering methods (KAOS, STS and SEPP) in the context of network security, our evaluation methodology can be instantiated in other contexts and other methods.

Requirements engineering is an important component of Enterprise Resource Planning (ERP) projects. We propose: (1) An ERP maturity model (EMM) for assessing the ERP maturity within the organization and (2) A Requirements Engineering (RE) method to capture the requirements from the different types of users of an ERP system, verifying and validating them. The EMM consists of three levels and each level has a focus and a key process area. Key indicators of ERP functionality identified by a major ERP vendor have been used to apply the EMM to an enterprise. This identifies the level of the EMM to which an enterprise belongs. Then the RE is used to enable the enterprise to assess its ERP system requirements and refine it using a process database to reach a higher level in the EMM. We deem that the EMM and the RE can benefit users across all the ERP projects.

Summary Objectives : Despite national mandates, incentives, and other programs, the design of health information technology (IT) remains problematic and usability problems continue to be reported. This paper reviews recent literature on human factors and usability of health IT, with a specific focus on research aimed at applying human factors methods and principles to improve the actual design of health IT, its use, and associated patient and clinician outcomes. Methods : We reviewed recent literature on human factors and usability problems of health IT and research on human-centered design of health IT for clinicians and patients. Results : Studies continue to show usability problems of health IT experienced by multiple groups of health care professionals (e.g., physicians and nurses) as well as patients. Recent research shows that usability is influenced by both designers (e.g., IT vendors) and implementers in health care organizations, and that the application of human-centered design practices needs to be further improved and extended. We welcome emerging research on the design of health IT for teams as team-based care is increasingly implemented throughout health care. Conclusions : Progress in the application of human factors methods and principles to the design of health IT is occurring, with important information provided on their actual impact on care processes and patient outcomes. Future research should examine the work of health IT designers and implementers, which would help to develop strategies for further embedding human factors engineering in IT design processes.

In this paper we examine a method for identifying privacy requirements within the context of a security requirements engineering method. We briefly describe the security quality requirements engineering (SQUARE) methodology. Next we discuss our definition of privacy and the associated privacy concerns. We discuss the challenges of privacy requirements engineering and the need for incorporating privacy considerations into security requirements engineering approaches. We describe a novel modification to the SQUARE method and tool to incorporate privacy considerations, and identify future work that will lead to a more integrated method for security and privacy requirements engineering.

The implementation of an information system that supports company goals is the main strategy of an organization. But aligning business strategies with information system(IS) and information technology(IT) is not as easy as it seems, because there are several gaps of strategies between upper level and practical level. Often the focus in system development is only on the architecture of the future system, even though the study says that the engineering model of needs is the most important thing in the process of developing the company’s system. PT. SBS is a distributor and supplier company. Along with the development of its business, business processes also become more complex. The information system that was originally felt to be sufficient is considered to be no longer optimal so that it often results in delays in delivery with a fairly large percentage. Therefore, an Enterprise Resources Planning(ERP) system will be developed but it must be ensured that the business processes used are oriented towards organizational goals. The purpose of this study is to introduce and explain the stages of the Organization Goal-Oriented Requirement Engineering (OGORE) method as a requirement engineering method in a company’s business processes that focuses on organizational goals. The research method was done by collecting business process data and defining key performance indicators(KPIs) in a small discussion group with stakeholders in the company. The results of this method were Goal Tree Model (GTM) diagrams which was then used as a reference in describing new business processes and in preparing the requirements specification documents. The conclusion obtained that the stages of the OGORE method are able to eliminate needs according to the organization’s goals. It is also recommended to use the OGORE method as one of the requirements management steps in the Enterprise Architecture method to create new method as an agenda for the future.

The security requirements are one of the non-functional requirements (NFR) which acts as a constraint on the functions of the system to be built. Security requirements are important and may affect the entire quality of the system. Unfortunately, many organizations do not pay much attention to it. The security problems should be focused on the early phases of the development process i.e. in the requirements phase to stop the problems spreading down in the later phases and in turn to avoid the rework. Subsequently, when security requirements are to be focused, proper guidance should be provided which should assist requirements engineers. Many security requirements engineering methods were developed in the past which require different level of expertise such as SQUARE process which requires requirements engineer to have a certain level of security expertise. Moreover, it lacks proper guidance especially for novice developers in applying the existing security requirements engineering (SecRE) methods to identify security requirements. Hence, this study intends to address the gap by developing a guided template to assist novice developers in the security requirements identification and documentation. The main objectives of the research are: 1) to study and investigate the existing security requirements engineering (SecRE) methods. 2) To develop a template to aid novice developers in identifying and documenting security requirements. The developed template is applied to two case studies of software projects to determine its usability and applicability. The results of the case studies evaluation show that both the usability and applicability of the template is good. The template is also evaluated by several experts and software practitioners. The evaluation results show that the SecRS template is found to be satisfying the usability and applicability factors; thereby confirming that the proposed template achieves its desired objective of aiding the novice developers to identify and document security requirements correctly.

The use of intentional concepts, the notion of "goal" in particular, has been prominent in recent approaches to requirement engineering (RE). Goal-oriented frameworks and methods for requirements engineering (GORE) have been keynote topics in requirements engineering, conceptual modelling, and more generally in software engineering. What are the conceptual modelling foundations in these approaches? RIGiM (Requirements Intentions and Goals in Conceptual Modelling) aims to provide a forum for discussing the interplay between requirements engineering and conceptual modelling, and in particular, to investigate how goal- and intention-driven approaches help in conceptualising purposeful systems. What are the fundamental objectives and premises of requirements engineering and conceptual modelling respectively, and how can they complement each other? What are the demands on conceptual modelling from the standpoint of requirements engineering? What conceptual modelling techniques can be further taken advantage of in requirements engineering? What are the upcoming modelling challenges and issues in GORE? What are the unresolved open questions? What lessons are there to be learnt from industrial experiences? What empirical data are there to support the cost-benefit analysis when adopting GORE methods? Are there applications domains or types of project settings for which goals and intentional approaches are particularly suitable or not suitable? What degree of formalization and automation or interactivity are feasible and appropriate for what types of participants during requirements engineering? e.g., business domain stakeholders, requirements modellers, ontology engineers, etc.KeywordsConceptual ModellingRequirement EngineeringApplication DomainHuman Computer InteractionRecent ApproachThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

"This book provides a detailed account concerning information society and the challenges and application posed by its elicitation, specification, validation and management: from embedded software in cars to internet-based applications, COTS packages, health-care, and others"--Provided by publisher

This paper presents an evaluation of the security quality requirements engineering (SQUARE) method. The evaluation of SQUARE was conducted by its application on the advanced metering infrastructure of smart grid as a case study. We evaluated the effectiveness of SQUARE with respect to its ability to elicit a set of artifacts, threats, and vulnerabilities; to perform likelihood, impact analysis, and risk level determination; and to elicit, categorize, and prioritize the security requirements. The main contribution of this work is the evaluation of the effectiveness of SQUARE using qualitative security requirements engineering method evaluation criteria.

The use of intentional concepts, the notion of "goal" in particular, has been prominent in recent approaches to requirement engineering (RE). Goal-oriented frameworks and methods for requirements engineering (GORE) have been keynote topics in requirements engineering, conceptual modelling, and more generally in software engineering. What are the conceptual modelling foundations in these approaches? RIGiM (Requirements Intentions and Goals in Conceptual Modelling) aims to provide a forum for discussing the interplay between requirements engineering and conceptual modelling, and in particular, to investigate how goal- and intention-driven approaches help in conceptualising purposeful systems. What are the fundamental objectives and premises of requirements engineering and conceptual modelling respectively, and how can they complement each other? What are the demands on conceptual modelling from the standpoint of requirements engineering? What conceptual modelling techniques can be further taken advantage of in requirements engineering? What are the upcoming modelling challenges and issues in GORE? What are the unresolved open questions? What lessons are there to be learnt from industrial experiences? What empirical data are there to support the cost-benefit analysis when adopting GORE methods? Are there application domains or types of project settings for which goals and intentional approaches are particularly suitable or not suitable? What degree of formalization and automation, or interactivity is feasible and appropriate for what types of participants during requirements engineering?KeywordsConceptual ModellingRequirement EngineeringService DiscoverySoftware Product LineFundamental ObjectiveThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Faster development cycles of innovative products in business networks of mechanical engineering or smart home robotics companies challenge systems engineers responsible for Requirements Management and Engineering. Applying System of Systems aspects in organizing the R&D processes in a business network is the first step, to deal with these challenges. However, in order to link different Requirements Engineering methods, handle diverse product conformity documents and provide up to date product models for all network partners, a basic, common concept for Requirements Engineering and Requirements Management is needed. This concept should be flexible and adaptable for the specific needs of one partner, but also include some level of standardization. The following paper presents an innovative concept that can help to implement a structured procedure in business networks regarding Requirements Engineering and Requirements Management. Based on international literature analysis and an industry survey in Germany, the resulting, innovative concept - the ReMaiN-concept - is in the process of evaluation in German mechanical engineering and smart home robotics business networks right now.

The present paper discusses possible ways of how ontologies could be used to drive requirements and the requirements engineering (RE) process itself in an attempt to overcome many of the problems that large engineering‐focused companies encounter in trans‐national and multi‐disciplinary business contexts.The current use of ontologies in the context of systems engineering (SE) is explored with an emphasis on applications in the RE domain, followed by concurrent approaches to RE. Then, the scope of RE is discussed and how it should be widened horizontally and vertically in order to more fully benefit from the positive impact of this discipline in relation to cost, schedule and quality, leading to knowledge‐driven RE rather than only process‐driven RE.An example of a knowledge‐driven approach to RE in the form of OntoREM – a comprehensive, ontology‐driven RE methodology – is introduced, which is currently being developed at the University of the West of England in close cooperation with Airbus. Although this methodology is not yet mature enough and tested to be deployed operationally, some promising results can be expected from a series of applications of aspects of the methodology that are scheduled to be conducted in the context of the Integrated Wing Aerospace Technology Validation Programme, a GBP 34 million, multidisciplinary UK research undertaking, in the first two quarters of 2008.

The rise of social media has fostered increasing instances of deviant behavior. Arguably, the most notable of these is cyberbullying (CB), which is an increasing global concern because of the social and financial ramifications. This has necessitated a new line of research aimed at understanding and preventing CB. Although much progress has been made in understanding CB, little is known about how to prevent it, especially through the information technology (IT) design. Based on the need for a better causal theory and more effective empirical methods to investigate and mitigate this phenomenon, we leverage the control balance theory (CBT) for system design. Our model examines the causes of CB from several novel angles, including (1) the strong nonlinear influence of control imbalances on CB, and (2) using the concept of fit to understand how different design features of information technology artifacts influence factors such as deindividuation and accountability, thus affecting control imbalance. Using an innovative factorial survey method that enabled us to manipulate IT design features to obtain a nuanced view, we tested our model with 507 adults and found strong support for our model. The results show that IT design features create a strong CB opportunity for individuals who perceive that they are controlled by others. Whether this perception is real or imagined, it creates a sense of vulnerability, prompting them to engage in CB. We can thus propose specific IT design feature manipulations that can be used to discourage CB. These results should have salient implications for researchers and social media designers, especially in developing social media networks that are safe, supportive, responsible, and constructive.