Joint Application Design Research Articles

Application of the Joint Application Design (JAD) Method in Developing a Women's Clothing Sales Information System Website Based at Aldisa Boutique

A website-based women's clothing sales information system is a significant solution in optimizing sales business processes and increasing market affordability for business owners. In this context, this research aims to apply the Joint Application Design (JAD) Method as an approach in developing the sales information system. The JAD method was used to actively involve stakeholders from the start of the development process, enabling a better understanding of Aldisa Boutique's business needs and user desires. Through this study, design and implement a Website-Based Women's Clothing Sales Information System by integrating the JAD method in every stage of development, including needs analysis, design and implementation. The test results show that the application of the JAD method can improve system quality by producing solutions that are more in line with user expectations and business needs. The system is expected to provide solutions for Aldisa Boutique in increasing sales efficiency and making purchases easier for consumers.

Application electronic marketing to help marketing leading products village

The research we will do is follow-up research from previous research in 2019, namely: "Application of E-Business in Village Government (Study on Marketing of Village Leading Products)", in previous studies it has been stated that applying the concept of E-Business to help market superior products village. In the current research, we will try to make a model or design of an application that can help in marketing the village's superior products. This type of research we use is applied research (Applied Research) because the results of the research can be directly used/applied to solve the problems faced and the implementation of e-business design using the information systems development (ISD) method. The traditional systems development life cycle (SDLC) method provides structured and formal steps. However, this method needs to be changed to adapt to the conditions of information technology and the increasingly complex needs and requires great flexibility and responsiveness. Various modern methods are available for the development of complex systems or those that are desired to be quickly realized, for example, prototyping, joint application design, object-oriented development, and component-based development. This E-Marketing application was created to be able to help promote and market products that are superior to the village. The design of this application is made to make it easier for village communities to promote and market their village's superior products. With this E-Marketing application, information on superior village products can be seen by the wider community. The result of this research is a prototype of the E-Marketing application that can be applied as a solution to promote and market the village's superior products.

Knowledge Management Systems Development and Implementation: A systematic Literature Review

Knowledge management systems can help to automate KM processes that exist in organizations. These systems facilitate knowledge discovery, knowledge capture, knowledge sharing, and applying knowledge in an organization. Using appropriate methods to develop and implementing knowledge management systems help organizations realizing these systems more effectively to enhance an organization’s competitive advantage and facilitate KM processes. This study investigates the approach for developing knowledge management systems in organizations with a systematic literature review in the past ten years. The findings in the literature study show that seventeen methods are used in the development of KMS, where the SECI knowledge spiral is the most often method used for developing KMS by combining it with traditional IS development techniques. In this study, we also compare five methods as candidates for KMS development methods that can support the acceleration of the innovation process in organizations and evaluate them based on KM criteria that support innovation using the analytic hierarchy process technique. It is found that Fernandez’s methodology combines with Joint Application Design (JAD) adoption is the most prominent method used in building a knowledge management system to support the innovation process in an organization and web 2.0 as the most technology applied to support organizational KM implementation.

The development of an epilepsy electronic patient portal: Facilitating both patient empowerment and remote clinician-patient interaction in a post-COVID-19 world.

ObjectivesThe current coronavirus disease 2019 (COVID‐19) pandemic stresses an urgency to accelerate much‐needed health service reform. Rapid and courageous changes being made to address the immediate impact of the pandemic are demonstrating that the means and technology to enable new models of health care exist. For example, innovations such as electronic patient portals (ePortal) can facilitate (a) radical reform of outpatient care; (b) cost containment in the economically constrained aftermath of the pandemic; (c) environmental sustainability by reduction of unnecessary journeys/transport. Herein, the development of Providing Individualised Services and Care in Epilepsy (PiSCES), an ePortal to the Irish National Epilepsy Electronic Patient Record, is demonstrated. This project, which pre‐dates the COVID‐19 crisis, aims to facilitate better patient‐ and family‐centered epilepsy care.MethodsA combination of ethnographic research, document analysis, and joint application design sessions was used to elicit PiSCES requirements. From these, a specification of desired modules of functionality was established and guided the software development.ResultsPiSCES functional features include “My Epilepsy Care Summary,” “My Epilepsy Care Goals,” “My Epilepsy Clinic Letters,” “Help Us Measure Your Progress,” “Prepare For Your Clinic Visit,” “Information for Your Healthcare Provider.” The system provides people with epilepsy access to, and engages them as co‐authors of, their own medical record. It can promote improved patient‐clinician partnerships and facilitate patient self‐management.SignificanceIn the aftermath of COVID‐19, it is highly unlikely that the healthcare sector will return to a “business as usual” way of delivering services. The pandemic is expected to accelerate adoption of innovations like PiSCES. It is therefore a catalyst for change that will deliver care that is more responsive to individual patient needs and preferences.

Requirements elicitation methods based on interviews in comparison: A family of experiments

Abstract Context There are several methods to elicit requirements through interviews between an end-user and a team of software developers. The choice of the best method in this context is usually on subjective developers’ preferences instead of objective reasons. There is a lack of empirical evaluations of methods to elicit requirements that help developers to choose the most suitable one. Objective This paper designs and conducts a family of experiments to compare three methods to elicit requirements: Unstructured Interviews, where there is no specific protocol or artifacts; Joint Application Design (JAD), where each member of the development team has a specific role; Paper Prototyping, where developers contrast the requirements with the end-user through prototypes. Method The experiment is a between-subjects design with next response variables: number of requirements, time, diversity, completeness, quality and performance. The experiment consists of a maximum of 4 rounds of interviews between students that play the role of developers and an instructor that plays the role of client. Subjects had to elaborate a requirements specification document as results of the interviews. We recruited 167 subjects in 4 replications in 3 years. Subjects were gathered in development teams of 6 developers at most, and each team was an experimental unit. Results We found some significant differences. Paper Prototyping yields the best results to elicit as many requirements as possible, JAD requires the highest time to report the requirements and the least overlapping, and Unstructured Interviews yields the highest overlapping and the lowest time to report the requirements. Conclusions Paper Prototyping is the most suitable for eliciting functional requirements, JAD is the most suitable for non-functional requirements and to avoid overlapping, Unstructured Interviews is the fastest but with poor quality in the results.

Knowledge management system design method with joint application design (JAD) adoption

PurposeThis study proposes to adopt joint application design (JAD) in the requirement gathering process on developing a knowledge management system (KMS) using Fernandez methodology. It is proposed that Fernandez methodology produces only a list of KMS features and the requirement of the feature is still unclear. This study aims to produce KMS that meets the needs and expectations of users based on features of Fernandez's methodology.Design/methodology/approachThis study was conducted using a combination methodology that combines Fernandez methodology to identify the feature needs of the organization and JAD to identify user requirements of KMS. The system prototype is evaluated by measuring user satisfaction using the Post Study System Usability Questionnaire.FindingsThe results of this study indicate that with the adoption of JAD it is possible to get the requirement in accordance with the expectations of the user. In addition, this study also shows that the level of user satisfaction with the prototype developed with the requirement is high at 84% of the maximum score.Research limitations/implicationsThis study was used only in the education context, especially teaching assistant problems at the Faculty of Computer Science, University of Indonesia. For this reason, further research is needed for different contexts so that the implementation of this combination of methods can be generalized more broadly.Practical implicationsThis paper provides practical implications for the development of KMS by identifying user requirements using JAD.Originality/valueThis paper provides a combination method to generate KMS that meets user requirements.

CABS: a conceptual model for context-aware B2B sales applications

Purpose – This paper aims to propose a conceptual model that will guide development of mobile applications to support value-added business-to-business (B2B) sales activities. Design/methodology/approach – The paper reviews the concepts of context-aware applications and context-marketing, then examines B2B selling and the creation of value, utilizing Terho’s model of value-based selling, and presenting the potential role of context-aware B2B selling in creating value. Terho’s model is then combined with a taxonomy of context modeling to produce step-by-step a conceptual model for developing context-aware B2B sales applications (CABS). Findings – By mapping the context-aware application development taxonomy against each stage of Terho’s “value-based selling” model, the CABS model is proposed. This model provides a platform for the B2B salesforce, their customers and information technology (IT) staff to work together in developing requirements and prototypes for mobile B2B context-aware applications. Research limitations/implications – The CABS model would require empirical testing to assess its viability and suitability. This would initially be done via focus groups in targeted sales organizations. Practical implications – The CABS model could utilized by sales staff and their customers to develop requirements for mobile context-aware applications to support B2B activity. In addition, the CABS model could be utilized in joint application design processes to enable sales and IT staff to work together in developing prototype mobile applications. Originality/value – While context-aware applications are beginning to transform business-to-sale (B2C) sales activities, it is clear that B2B sales could also benefit from these types of applications, but little progress has been made in understanding or developing their potential. The CABS model enables B2B sales staff and their customers to recognize these benefits and facilitate working with IT staff in defining requirements and developing prototypes.

The development and evaluation of a nursing information system for caring clinical in-patient.

The research aimed to develop a nursing information system in order to simplify the admission procedure for caring clinical in-patient, enhance the efficiency of medical information documentation. Therefore, by correctly delivering patients’ health records, and providing continues care, patient safety and care quality would be effectively improved. The study method was to apply Spiral Model development system to compose a nursing information team. By using strategies of data collection, working environment observation, applying use-case modeling, and conferences of Joint Application Design (JAD) to complete the system requirement analysis and design. The Admission Care Management Information System (ACMIS) mainly included: (1) Admission nursing management information system. (2) Inter-shift meeting information management system. (3) The linkage of drug management system and physical examination record system. The framework contained qualitative and quantitative components that provided both formative and summative elements of the evaluation. System evaluation was to apply information success model, and developed questionnaire of consisting nurses’ acceptance and satisfaction. The results of questionnaires were users’ satisfaction, the perceived self-involvement, age and information quality were positively to personal and organizational effectiveness. According to the results of this study, the Admission Care Management Information System was practical to simplifying clinic working procedure and effective in communicating and documenting admission medical information.

Indonesia Coal Trade System: A Knowledge-based Application Software

Performing coal trading in Indonesia is not simple. Many new comers in coal industry have been fallen down for many reasons. Some coal player collapse by fraudulent and some other fallen down by lack of knowledge in coal trading. To overcome this situation, a solution has proposed. The solution is by developing a web based application software for coal trading named Indonesia Coal Trade System (ICTS).The method in Software Development Life Cycle of ICTS is Joint Application Design by using prototyping. The software designed using UML and its CASE tools. It is smartphone friendly to support field engineers while in duty, and it will utilize phone's GPS and camera to collect important data.ICTS is an application that is not only data recording and processing of coal trading, but it also a workflow application developed by experts in coal trading. They transfer their tacit knowledge into software to guide users in coal trading in Indonesia. ICTS will reduce the chance of coal traders from fraudulent and it can lead companies to legal transactions.

Shortening Requirements Engineering: Dual Imperative Action Research Study

A computer parts company was losing market share because the systems development life cycle (SDLC) took too long. We reduce the requirements engineering (RE) phase of the SDLC while maintaining current levels of product quality and increasing the company competitiveness by reducing the product time-to-market. Action research, a practical and widely used method of inquiry, was used to solve the problem. There are five types of action research (canonical, dialogical, collaborative, dual imperative, and participatory), but dual imperative action research seemed most appropriate for our study. The problem solving approach used in the study combined joint application design (JAD), unified modeling language (UML), group decision support systems (GDSS), and computer aided software engineering (CASE). We successfully reduced the SDLC time from fourteen to four days, a productivity increase of 250%.

Comparison of Requirements Elicitation Techniques

Many software development projects fail because the resulting software does not satisfy the end user’s needs. If requirement engineer have practiced more effectively requirements elicitation techniques, fewer projects will fail. There are numbers of techniques available which can be used by requirement engineers for taking requirements form their clients. Requirement engineer encounters number of difficulties while selecting one of the most suitable techniques of requirements elicitation for a particular project. A technique which is used in one project for taking requirements may not be suitable for another. Selecting a technique for taking requirements elicitation depends upon number of factors and as and when there is a change in these factors, techniques needs to be adjusted. This research work is a comparison of requirements elicitation techniques with a focus to find out most effective and most preferred requirements elicitation technique. In this research five elicitation techniques are taken for comparison. These techniques are Interview, Joint Application Design, Brainstorming, User Scenarios and Mind Mapping. These techniques are selected on the basis of their historical developments. The result of research shows that Interview is the best technique among these techniques. These results are based upon the empirical study and literature study. In empirical study a questionnaire was prepared related to these five techniques and responses are collected from requirements engineers working in various software development companies and people involved in website developments. In literature study, various research papers related to requirements engineering were studied. In literature review again interview technique was turned out to be an effective technique and new research also supports the same results.

Stakeholders' Involvement in KMS implementation for Thai Ceramic SMEs: A Conceptual Framework

Recently, over 80 percent of ceramic SMEs in Lampang, known as the biggest source of ceramic production in Thailand have been closed down rapidly due to several reasons such as the difficulties to find funds for sustainment and facing intensive competition in the global market. To overcome this situation, we propose a Knowledge Management System (KMS) framework based on Intellectual Capital (IC) theory. This framework is based on the identification of the various stakeholders of the enterprise and their roles in creating the knowledge. To improve performance of SMEs, we propose to develop four perspectives: Business Plan, Business Process Reengineering (BPR), Enterprise Resource Planning (ERP), and New Product Development (NPD) using the Joint Application Design (JAD).

Chapter 10 - WITHDRAWN: The participants and their roles

This article has been withdrawn: please see Elsevier Policy on Article Withdrawal (http://www.elsevier.com/locate/withdrawalpolicy). This book has been withdrawn as Elsevier no longer has the publishing rights.

Transforming society by transforming technology: the science and politics of participatory design

This article attempts to shed historical light on some of the social, political, and ethical issues that have arisen from two disparate perspectives on technology which have both come to integrate an explicit consideration of social factors into systems design. It presents two distinct historical traditions which have contributed to the current field of participatory design methodologies— Joint Application Design (JAD ®), and the British “socio-technical systems” and Scandinavian “collective resources” approaches—and which in practice integrated the end-users in different ways consequent upon their differing perspectives on workers, professional relationships to technology, and stated goals. One interest in examining the independent development of methodologies from these two perspectives is that, despite their differences, the approaches ultimately converged on a set of shared concerns and very similar practices. The paper also examines the relation of these traditions to transformations in the theorization of business organization and trends of corporate restructuring which helped to secure a place for variants of related methodologies in major US and multinational corporations. It concludes with an examination of some broader issues in the relationship between technology and society and the prospects for the critical study of technology. I argue that participatory design and its related methodologies are best understood as a model for involving users, designers and the technology itself in a process of technological development. Rather than seeing participatory design as merely the insertion of public dialog within technological design practices, as several observers have done, we should see it as a model for the critical practice of developing technological designs.

Joint application design (JAD) in practice

Joint application design (JAD) is an intuitively appealing systems development method that encompasses approaches for enhancing user participation, expediting development, and improving the quality of specifications. Although the JAD method has been widely acclaimed, little is actually known about its effectiveness in practice. This paper reports findings of a field study at three organizations in which JAD practices were examined to assess how practice influenced outcomes of JAD use. Findings suggest that the organizations realized modest improvements in systems development outcomes by using the JAD method. JAD use was most effective in small, clearly focused projects and less effective in large, complex projects. Findings also suggest that practices for using JAD at the research sites reduced its potential effectiveness by limiting user participation, focusing workshop exercises on developers' analytical models and terminology, and applying the JAD method prematurely in large projects. Adaptations of the JAD method in practice stemmed from unresolved conflicts between assumptions underlying the espoused JAD method and the status quo IS development approach at each organization. Implications for the effectiveness of the JAD method as a software process improvement are considered.

Business Process Modeling with Group Support Systems

:Much process modeling research has focused on the development of new modeling languages, but very little research has examined the process by which model information is collected from subject-matter experts. The goal of this research was to develop and evaluate an alternative process to the traditional sequence of interviews or the increasingly common use of JAD (Joint Application Design) meetings run by professional facilitators/modelers. We began by selecting one commonly used modeling technique (IDEFO) and adapting its traditional modeling process to use an enabling technology ofa group support system (GSS). We developed a special-purpose GSS tool to support the process and tested it through a series of eight field trials over a sixteen-month period. We then compared the new GSS-based technique with the traditional JAD technique in an additional series of eighteen field studies (nine JAD, nine GSS) over a two-year period. The results indicate that the GSS technique reduced the time required to build models by about 75 percent. Models built using GSS and the traditional JAD approach had similar numbers of syntax errors. Project managers perceived the GSS models to be as good as or better than the traditional JAD models in accurately defining the business process.

Simulating requirements gathering

One of the difficulties in teaching a project-based Software Engineering course for undergraduates is giving students experience with requirements gathering before they begin the course project. This paper describes a simulation of Joint Application Design (JAD), a technique used in industry to gather requirements from users. The simulation is a role-playing exercise in which students play the parts of both developers and customers involved in specifying a new software product. Each participant is given a script of behaviors to act out for his or her role and a set of specific requirements for the product. The participants must work out conflicts and ambiguities built into the simulation to produce a consistent product specification.

A CONCURRENT PROCESS FOR DEVELOPMENT AND VALIDATION OF OPERATIONAL REQUIREMENTS

AbstractThe FAA's Oceanic and Offshore Integrated Product Team has established a process for development and validation of system level requirements through the use of Joint Application Design. This process is initiated with operational requirements set in the context of a concept of operations. The concept and system behavior are wholly contained within a requirements model. The goal is to collect user inputs that compliment the operational requirements with a level of detail necessary to complete a system level specification in the model. The model will then be used to validate the requirements against the concept of operations and target benefits for the system build. This paper describes the requirements development and validation process and preliminary results of the application of the process.

Using joint application design to develop readable formal specifications

A requirements specification is a ‘contract’ between a client and a systems developer. This document is frequently written in some type of ‘computerese’ or formal specification that is unintelligible to most clients. Why can't we have a precise, formal specification that is understandable? In fact, why can't we let the client take charge of developing a formal specification? In this paper, we present OSS (Object-oriented Systems Specification), a graphical model with an embedded textual language that has a formal foundation, is suitable for requirements specification, and is understandable to at least technically oriented clients. We also introduce IPOST, a prototyping/specification tool to assist the client. We describe a Joint Application Development (JAD) scenario utilizing OSS and IPOST that involves heavy client participation in the development of formal requirements specifications.

Developing a Local Acquisitions System Using the Joint Application Design (JAD) Process

This article describes the joint application design process (JAD) within the context of a large academic research library system. It provides background infomation about this technique and discusse...