Research Prototypes versus Products: Lessons Learned from Software Development Processes in Research Projects

Author(s):  
Dietmar Winkler ◽  
Richard Mordinyi ◽  
Stefan Biffl
Author(s):  
Sampada G.C ◽  
Tende Ivo Sake ◽  
Amrita

Background: With the advancement in the field of software development, software poses threats and risks to customers’ data and privacy. Most of these threats are persistent because security is mostly considered as a feature or a non-functional requirement, not taken into account during the software development life cycle (SDLC). Introduction: In order to evaluate the security performance of a software system, it is necessary to integrate the security metrics during the SDLC. The appropriate security metrics adopted for each phase of SDLC aids in defining the security goals and objectives of the software as well as quantify the security in the software. Methods: This paper presents systematic review and catalog of security metrics that can be adopted during the distinguishable phases of SDLC, security metrics for vulnerability and risk assessment reported in the literature for secure development of software. The practices of these metrics enable software security experts to improve the security characteristics of the software being developed. The critical analysis of security metrics of each phase and their comparison are also discussed. Results: Security metrics obtained during the development processes help to improve the confidentiality, integrity, and availability of software. Hence, it is imperative to consider security during the development of the software, which can be done with the use of software security metrics. Conclusion: This paper reviews the various security metrics that are meditated in the copious phases during the progression of the SDLC in order to provide researchers and practitioners with substantial knowledge for adaptation and further security assessment.


2021 ◽  
Vol 13 (11) ◽  
pp. 5985
Author(s):  
Bryan Weichelt ◽  
Jeffrey VanWormer ◽  
Yin Xu ◽  
Chris Kadolph ◽  
Simon Lin

Cardiovascular disease (CVD) is a major public health concern in the United States. In response to the federally sponsored Million Hearts Risk Check Challenge, a team of programmers, software developers, health-information technologists, and clinicians in an integrated healthcare system in Wisconsin collaborated to develop Heart Health MobileTM (HHM), designed to improve awareness of cardiovascular disease risk and promote risk factor control among users. This paper outlines the development processes and highlights key lessons learned for mobile health applications. An agile project management methodology was used to dedicate adequate resources and employ adaptive planning and iterative development processes with a self-organized, cross-functional team. The initial HHM iOS app was developed and tested, and after additional modifications, gamified and HTML 5 versions of the app were released. The development of an iOS app is low in cost and sustainable by a healthcare system. Future app modifications to enhance data security and link self-reported cardiovascular risk assessment data to patient medical records may improve performance, patient relevance, and clinician acceptance of HHM in the primary-care setting. Legal and institutional barriers regarding the capture and analyses of protected health information must be mitigated to fully capture, analyze, and report patient health outcomes for future studies.


2021 ◽  
Vol 37 (2) ◽  
pp. 244-256
Author(s):  
Ava T. Carcirieri

Academics and practitioners all too often have little or no contact with each other; the practitioner does not know what research exists that can inform their practices, and the academic does not know enough about the institutions they primarily study to make recommendations that are specific enough to inform a concrete practice or policy. I leverage my experiences both as an academic and as a data analyst and domestic violence coordinator at Family Court to outline lessons learned in the field. I detail how my academic training hindered my work as a practitioner, and how practitioners differ in terms of conducting internal research and presenting data and findings. I use my lessons learned and subsequently list several concrete practices that academics can begin to work into their work to increase communication with important stakeholders, and tailor their work to practical systemic improvement. Bridging the gap between academics and practitioners will lead to better research projects, and findings that will be able to actively enact changes within systems that academics focus on.


2005 ◽  
Vol 16 (4) ◽  
pp. 62-87 ◽  
Author(s):  
Daniel Turk ◽  
France. Robert ◽  
Bernhard Rumpe

i-com ◽  
2016 ◽  
Vol 15 (1) ◽  
Author(s):  
Holger Fischer ◽  
Michaela Kauer-Franz ◽  
Dominique Winter ◽  
Stefan Latt

AbstractThe establishment of human-centered design within software development processes is still a challenge. Numerous methods exist that aim to increase the usability and user experience of an interactive system. Nevertheless, the selection of appropriate methods remains to be challenging, as there are multiple different factors that have a significant impact on the appropriateness of the methods in their context of use. The present article investigates current strategies of method selection based on a conference workshop with practitioners. The results show that usability and user experience professionals concentrate on five to seven well-known methods and will need more support to select and use further ones.


Sign in / Sign up

Export Citation Format

Share Document