Supporting Work Practice Through End-User Development Environments

2008 ◽  
pp. 1823-1842
Author(s):  
M. F. Costabile ◽  
D. Fogli ◽  
R. Lanzilotti
Keyword(s):  
Software Development ◽  
Competitive Advantage ◽  
Field Study ◽  
Work Practice ◽  
End Users ◽  
Interactive System ◽  
Software Development Process ◽  
End User ◽  
And Performance

End-user development means the active participation of end users in the software development process. In this perspective, tasks that are traditionally performed by professional software developers are transferred to end users, who need to be specifically supported in performing these tasks. We have developed a methodology that supports user work practice and metadesign, allowing experts in a domain to personalize and evolve their own software environments. In this article we illustrate how this methodology is applied to a project for the development of an interactive system in the medical domain. Physicians and their activities have been carefully analyzed through a field study that is reported in the article, in order to provide them with computer systems that may improve their work practice and determine an increase in their productivity and performance, that is, a better quality of diagnosis and medical cure, with the achievement of competitive advantage for the organization they work in.

Advancing End User Development Through Metadesign

2011 ◽  
pp. 143-167 ◽  
Author(s):  
Maria Francesca Costabile ◽  
Daniela Fogli ◽  
Rosa Lanzilotti ◽  
Piero Mussio ◽  
Loredana Parasiliti Provenza ◽  
...  
Keyword(s):  
Work Practice ◽  
End Users ◽  
Software Systems ◽  
Specific Work ◽  
End User ◽  
User Communities ◽  
Design Paradigm ◽  
Software Engineers ◽  
New Perspective ◽  
And Performance

End-user development means the active participation of end users in the software development process. In this perspective, tasks that are traditionally performed by professional software developers at design time are transferred to end users at use time. This creates a new challenge for software engineers: designing software systems that can be evolved by end users. Metadesign, a new design paradigm discussed in this chapter, is regarded as a possible answer to this challenge. In this line, we have developed a metadesign methodology, called Software Shaping Workshop methodology, that supports user work practice and allows experts in a domain to personalize and evolve their own software environments. We illustrate the Software Shaping Workshop methodology and describe its application to a project in the medical domain. The work proposes a new perspective on system personalization, distinguishing between customization and tailoring of software environments. The software environments are customized by the design team to the work context, culture, experience, and skills of the user communities; they are also tailorable by end users at runtime in order to adapt them to the specific work situation and users’ preferences and habits. The aim is to provide the physicians with software environments that are easy to use and adequate for their tasks, capable to improve their work practice and determine an increase in their productivity and performance.

DESIGN AND MODELING IN THE SOFTWARE PERFORMANCE ENGINEERING DEVELOPMENT PROCESS

2010 ◽  
Vol 19 (01) ◽  
pp. 307-323 ◽  
Author(s):  
SALVATORE DISTEFANO ◽  
ANTONIO PULIAFITO ◽  
MARCO SCARPA
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Performance ◽  
Software Development Process ◽  
Early Integration ◽  
Performance Engineering ◽  
Software Performance Engineering ◽  
Engineering Development ◽  
And Performance ◽  
A Performance

Performance related problems are becoming more and more strategic in the software development, especially recently with the advent of Web Services and related business-oriented composition techniques (software as a service, Web 2.0, orchestration, choreography, etc.). In particular, an early integration of performance specifications in the SDP has been recognized during the last few years as an effective approach to improve the overall quality of a software. The goal of our work is the definition of a software development process that integrates performance evaluation and prediction. The software performance engineering development process (SPEDP) we specify is focused on performance, which plays a key role driving the software development process, thus implementing a performance/QoS-driven (software) development process. More specifically, in this paper our aim is to formally define the SPEDP design process, posing particular interest on the basis, on the first step of SPEDP, the software/system architecture design, modeling and/or representation. We define both the diagrams to use and show how to model the structure of the software architecture, its behavior and performance requirements. This is the first mandatory step for the automation of the SPEDP into a specific tool, which we have partially implemented as a performance plug-in for ArgoUML, ArgoPerformance.

scholarly journals Measuring the Quality Of the Development Process Academic System with E-GQM Method

2021 ◽  
Vol 5 (1) ◽  
Author(s):  
Sarwosri Sarwosri ◽  
Umi Laili Yuhana ◽  
Siti Rochimah ◽  
Rizky Januar Akbar ◽  
Maidina Choirun Nisa
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Process ◽  
Development Project ◽  
Average Score ◽  
Software Development Process ◽  
Software Development Project ◽  
Software Products ◽  
Academic System

In a software development project, aspects of software quality are very important. All stakeholders expect high quality of software. To ensure the quality of software products, it is also necessary to ensure that the process that is carried out have a quality. Research that is mostly done is in terms of assessing the quality of software products. But the software process is also very important to be assessed from their quality too. In every software development process, the developer needs guidance in carrying out every aspect of it. In each of these aspects, it must be determined what goals are to be achieved and how to measure whether those goals have been achieved or not. One method that can be used for this is the Extended Goal Question Metric method. In this method, for each development process in software, will be determined what aspects must be achieved, from each aspect there are defined a number of goals to measure these aspects. For each goal, one or more goal will be determined one or more questions that are relevant to that. For each Question an appropriate metric will be determined. The next step is mapping between G to Q and Q to M. The measurement is done by calculating the goal value obtained from the metric calculation. From this metric, the value of each Goal will be obtained, whether it was achieved or not. Tests were carried out on the software process for the development of academic system features at DPTSI ITS. The value of each goal has exceeded 0.51 (for a scale of 0-1) so that it achieved the quality of the Software development process. The total average score was 0.889. 

scholarly journals RANCANG BANGUN SISTEM PEMESANAN CATERING DAN DEKORASI DI SUMBAWA BESAR BERBASIS ANDROID

Kilat ◽  
2018 ◽  
Vol 7 (2) ◽  
pp. 160-168
Author(s):  
Rodianto Rodianto ◽  
Arni Safitri
Keyword(s):  
Software Development ◽  
Programming Languages ◽  
Process Model ◽  
Human Error ◽  
Short Message ◽  
Software Development Process ◽  
Program Testing ◽  
Waterfall Model ◽  
Order Paper

The catering and decorating process in Sumbawa is still conventional. So that the service procedure which applied for now are still less effective and efficient. This process incude to the owners of catering  and decoration that could does a mistake, among others, the double order, the order making was not in order due to the accumulation of order notes, especially when crowded customers ordered by telephone or short message which could occur human error such as forgetting the order customer, and pen or order paper that runs out. The software is built by using the programming languages PHP, MySQL, Java and Android Studio. The purpose of making this ordering system is to help the owner of catering nusiness and decoration in Sumbawa besar to improving the quality of their business in the eyes of customers. This ordering system has a service that makes customers know the that location of the place of residence of the business owner as to minimize the occurrence of customer concers for message that are not served. The method used is a method of data collection and software development. The software development process model is used in the waterfall model which consist (1) analysis, (2) design, (3) coding, (4) program testing, (5) maintance.

scholarly journals Building a web-based app for persons with physical disabilities: A collaboration between game developers and rehabilitation researchers (Preprint)

2019 ◽  
Author(s):  
Alexandra Terrill ◽  
Justin J. MacKenzie ◽  
Maija Reblin ◽  
Jackie Tyne Einers ◽  
Jesse Ferraro ◽  
...  
Keyword(s):  
Mental Health ◽  
Software Development ◽  
Development Process ◽  
Physical Disabilities ◽  
End Users ◽  
Lessons Learned ◽  
Software Development Process ◽  
Web Based ◽  
Cord Injury

BACKGROUND Individuals with disability and their partners, who often provide care, are both at risk for depression and lower quality of life. Mobile health (mHealth) interventions are promising to address barriers for mental health care. Rehabilitation researchers and software development researchers must collaborate effectively with each other, and with clinical and patient stakeholders to ensure successful mHealth development. OBJECTIVE To aid researchers interested in mHealth software development by describing the collaborative process between a team of rehabilitation researchers, software development researchers, and stakeholders. Thus, we provide a framework (conceptual model) for other teams to replicate in order to build a web-based mHealth app for individuals with physical disability. METHODS Rehabilitation researchers, software development researchers, and stakeholders (people with physical disabilities and clinicians) are involved in an iterative software development process. The overall process to develop an mHealth intervention includes initial development meetings and a co-design method called “designbox”, in which the needs and key elements of the app are discussed. Based on the objectives outlined, a prototype is developed and goes through scoping iterations with feedback from stakeholders and end-users. The prototype is then tested by users to identify technical errors and gather feedback on usability and accessibility. RESULTS Illustrating the overall development process, we present a case study based on our experience developing an app (SupportGroove) for couples coping with spinal cord injury. Examples of how we addressed specific challenges are also included. For example, feedback from stakeholders resulted in development of app features for individuals with limited functional ability. Initial designs lacked accessibility design principles made visible by end-users. Solutions included large text, single-click, and minimal scrolling to facilitate menu navigation for individuals using eye-gaze technology. Prototype testing allowed further refinement and demonstrated high usability and engagement with activities in the app. Qualitative feedback indicated high levels of satisfaction, accessibility, and confidence in potential utility. We also present key lessons learned about working in a collaborative interdisciplinary team. CONCLUSIONS mHealth promises to help overcome barriers to mental health intervention access. However, the development of these interventions can be challenging because of the disparate and often siloed expertise required. By describing the mHealth software development process and illustrating it with a successful case study of rehabilitation researchers, software development researchers, and stakeholders collaborating effectively, our goal is to help other teams avoid challenges we faced and benefit from our lessons learned. Ultimately, good interdisciplinary collaboration will benefit individuals with disabilities and their families. CLINICALTRIAL n/a

scholarly journals Software Development Technique for the Betterment of End User Satisfaction using Agile Methodology

TEM Journal ◽  
2020 ◽  
pp. 992-1002
Author(s):  
Lalband Neelu ◽  
D. Kavitha
Keyword(s):  
Customer Satisfaction ◽  
Software Development ◽  
Present State ◽  
User Satisfaction ◽  
Development Process ◽  
Software Development Process ◽  
End User ◽  
Traditional System ◽  
Agile Methodology ◽  
User Priority

Agile methodology mainly focuses on the end user priority during the each and every stage of software development process. There is a huge scope in this technique in order to alter the major/minor modifications at each stage of software development for attaining the customer satisfaction. The main aim of the present work is to compare agile methodology with the traditional system methodologies. The present state of using the agile technologies for customer satisfaction at every phase by delivering valuable software continuously is also discussed in the present work. Based on the pitfalls in the existing models, a new model is proposed here in the present study.

A Proposal to Elicit Usability Requirements within a Model-Driven Development Environment

2014 ◽  
Vol 5 (4) ◽  
pp. 1-21
Author(s):  
Yeshica Isela Ormeño ◽  
Jose Ignacio Panach ◽  
Nelly Condori-Fernández ◽  
Óscar Pastor
Keyword(s):  
Software Development ◽  
Development Process ◽  
Design Guidelines ◽  
Tree Structure ◽  
Software Development Process ◽  
End User ◽  
Model Driven Development ◽  
Model Driven ◽  
Early Stages ◽  
Usability Requirements

Nowadays there are sound Model-Driven Development (MDD) methods that deal with functional requirements, but in general, usability is not considered from the early stages of the development. Analysts that work with MDD implement usability features manually once the code has been generated. This manual implementation contradicts the MDD paradigm and it may involve much rework. This paper proposes a method to elicit usability requirements at early stages of the software development process such a way non-experts at usability can use it. The approach consists of organizing several interface design guidelines and usability guidelines in a tree structure. These guidelines are shown to the analyst through questions that she/he must ask to the end-user. Answers to these questions mark the path throughout the tree structure. At the end of the process, the paper gathers all the answers of the end-user to obtain the set of usability requirements. If it represents usability requirements according to the conceptual models that compose the framework of a MDD method, these requirements can be the input for next steps of the software development process. The approach is validated with a laboratory demonstration.

Covert End User Development

2008 ◽  
pp. 309-316
Author(s):  
Elaine H. Ferneley
Keyword(s):  
Software Development ◽  
Development Strategy ◽  
Dynamic Environments ◽  
End Users ◽  
Small Scale ◽  
End User ◽  
Technological Artifacts ◽  
External Stakeholders ◽  
Full Knowledge ◽  
Wide Group

End User Development (EUD) of system applications is typically undertaken by end users for their own, or closely aligned colleagues, business needs. EUD studies have focused on activity that is small scale, is undertaken with management consent and will ultimately be brought into alignment with the organisation’s software development strategy. However, due to the increase pace of today’s organisations EUD activity increasing takes place without the full knowledge or consent of management, such developments can be defined as covert rather than subversive, they emerge in response to the dynamic environments in which today’s organisations operate. This paper reports on a covert EUD project where a wide group of internal and external stakeholders worked collaboratively to drive an organisation’s software development strategy. The research highlights the future inevitability of external stakeholders engaging in end user development as, with the emergence of wiki and blog-like environments, the boundaries of organisations’ technological artifacts become increasingly hard to define.

Sign in / Sign up

Export Citation Format

Share Document