scholarly journals Lessons Learned from SunDEW: A Self Defense Environment for Web Applications

2020 ◽  
Author(s):  
Merve Sahin ◽  
Cedric Hebert ◽  
Anderson Santana De Oliveira
Keyword(s):  
Web Applications ◽  
Lessons Learned ◽  
Self Defense

WITHWomen: User Centered Approach to the Design and Development of a suite of Intimate Partner Violence Screening and Safety Planning Web-Applications (Preprint)

2020 ◽  
Author(s):  
Patricia O'Campo ◽  
Alisa Velonis ◽  
Pearl Buhariwala ◽  
Janisha Kamalanathan ◽  
Maha Awaiz Hassan
Keyword(s):  
Partner Violence ◽  
Web Applications ◽  
Lessons Learned ◽  
Evidence Based ◽  
Safety Planning ◽  
Future Design ◽  
Mhealth Technology ◽  
The Right ◽  
Safe Access ◽  
Health Applications

BACKGROUND The popularity of mHealth technology has resulted in the development of numerous applications for almost every type of self-improvement or disease management. M- and e-health solutions for increasing awareness about and safety around partner violence is no exception. OBJECTIVE These applications allow women to control access to these resources and provide unlimited, and with the right design features, safe access when these resources are needed. Few applications, however, have been designed in close collaboration with intended users to ensure relevance and effectiveness. METHODS We report here on the design of a pair of evidence-based m- and e-health applications to facilitate early identification of unsafe relationship behaviors and tailored safety planning to reduce harm from violence including the methods by which we collaborated with and sought input from population of intended users. RESULTS The demographic characteristics of those who participated in the various surveys and interviews to inform the development of our screening and safety-decision support app are presented in (Table 2). CONCLUSIONS Finally, we share challenges we faced and lessons learned that might inform future design efforts of m- and e-health evidence-based applications.

Tool Support for Model-Driven Development of Web Applications

2009 ◽  
pp. 331-344
Author(s):  
Jaime Gomez ◽  
Alejandro Bia ◽  
Antonio Parraga
Keyword(s):  
Rapid Prototyping ◽  
Case Studies ◽  
Web Applications ◽  
Lessons Learned ◽  
Tool Support ◽  
Natural Consequence ◽  
Model Driven ◽  
High Level ◽  
Model Driven Approach ◽  
Industrial Context

This paper describes the engineering foundations of VisualWADE, a CASE tool to automate the production of Web applications. VisualWADE follows a model-driven approach focusing on requirements analysis, high level design, and rapid prototyping. In this way, an application evolves smoothly from the first prototype to the final product, and its maintenance is a natural consequence of development. The paper also discusses the lessons learned in the development of the tool and its application to several case studies in the industrial context.

Lessons learned from the total evacuation of a hospital after the 2016 Kumamoto Earthquake

2017 ◽  
Vol 15 (4) ◽  
pp. 259 ◽  
Author(s):  
Youichi Yanagawa, MD, PhD ◽  
Hisayoshi Kondo, MD, PhD ◽  
Takashi Okawa, MD, PhD ◽  
Fumio Ochi, MD, PhD
Keyword(s):  
Large Scale ◽  
Medical Information ◽  
Lessons Learned ◽  
Medical Information System ◽  
Activity Data ◽  
Self Defense ◽  
The 2016 Kumamoto Earthquake ◽  
The 2016 Kumamoto Earthquakes ◽  
Combined Use ◽  
Frequent Reason

Background: The 2016 Kumamoto Earthquakes were a series of earthquakes that included a foreshock earthquake (magnitude 6.2) on April 14 and a main shock (magnitude 7.0) on April 16, 2016. A number of hospitals in Kumamoto were severely damaged by the two major earthquakes and required total evacuation.Methods: The authors retrospectively analyzed the activity data of the Disaster Medical Assistance Teams using the Emergency Medical Information System records to investigate the cases in which the total evacuation of a hospital was attempted following the 2016 Kumamoto Earthquake.Results: Total evacuation was attempted at 17 hospitals. The evacuation of one of these hospitals was canceled. Most of the hospital buildings were more than 20 years old. The danger of collapse was the most frequent reason for evacuation. Various transportation methods were employed, some of which involved the Japan Ground Self-Defense Force; no preventable deaths occurred during transportation.Conclusions: The hospitals must now be renovated to improve their earthquake resistance. The coordinated and combined use of military and civilian resources is beneficial and can significantly reduce human suffering in large-scale disasters.

Disaster Relief Activities of the Japan Self-Defense Force Following the Great East Japan Earthquake

2014 ◽  
Vol 8 (3) ◽  
pp. 194-198 ◽  
Author(s):  
Yasumasa Nishiyama
Keyword(s):  
Chronic Disease ◽  
Natural Disasters ◽  
Disaster Relief ◽  
Lessons Learned ◽  
Great East Japan Earthquake ◽  
Medical Aid ◽  
Medical Response ◽  
Self Defense ◽  
Disaster Situation

ABSTRACTCooperation between civilian and military forces, including the Japan Self-Defense Force (JSDF), enabled wide-ranging disaster relief after the Great East Japan Earthquake. Nevertheless, many preventable fatalities occurred, particularly related to an inability to treat chronic disease, indicating the need to plan for the provision of long-term medical aid after natural disasters in stricken areas and evacuation shelters. To assist in this effort, this report (1) provides an overview of the consequences of the medical response to the Great East Japan Earthquake, the largest natural disaster ever to hit Japan, focusing on the role and actions of the JSDF; (2) discusses the lessons learned regarding the provision of medical aid and management by the JSDF after this disaster, looking at the special challenges of meeting the needs of a rapidly aging population in a disaster situation; and (3) provides recommendations for the development of strategies for the long-term medical aid and support after natural disasters, especially with regard to the demographics of the Japanese population.

scholarly journals Lessons Learned about FOLIO’s APIs

2021 ◽  
Vol 6 (2) ◽  
pp. 30-39
Author(s):  
Guy Dobson
Keyword(s):  
User Interface ◽  
Web Applications ◽  
Application Programming Interface ◽  
Building Blocks ◽  
Lessons Learned ◽  
Library Services ◽  
Library System ◽  
Application Programming ◽  
Programming Interface

APIs (Application Programming Interface) provide the ability to do what needs to be done. The fact that FOLIO includes API as one of its building blocks makes it that much more attractive. When my library’s administration decided to switch from a legacy ILS (Integrated Library System) to a FOLIO LSP (Library Services Platform) the first thing that I looked at was the API. The lessons learned helped me to configure the system and massage the data from ILS output to FOLIO-friendly input. By building web applications and writing Perl scripts our staff is able to get the job done even when it is impossible to accomplish the task through the user interface (UI).

scholarly journals Ten Simple Rules for Researchers Who Want to Develop Web Apps

2021 ◽  
Author(s):  
Sheila Saia ◽  
Natalie Nelson ◽  
Sierra Young ◽  
Stanton Parham ◽  
Micah Vandegrift
Keyword(s):  
Decision Support ◽  
Web Applications ◽  
Decision Support Tool ◽  
Lessons Learned ◽  
Decision Support Tools ◽  
Support Tool ◽  
Support Tools ◽  
Simple Rules ◽  
Web App ◽  
Scenario Testing

Growing interest in data-driven, decision-support tools across the life sciences and physical sciences has motivated development of web applications, also known as web apps. Web apps can help disseminate research findings and present research outputs in ways that are more accessible and meaningful to the general public--from individuals, to governments, to companies. Specifically, web apps enable exploration of scenario testing and policy analysis (i.e., to answer “what if?”) as well as co-evolution of scientific and public knowledge. However, the majority of researchers developing web apps receive little formal training or technical guidance on how to develop and evaluate the effectiveness of their web-based decision support tools. Take some of us for example. We (Saia and Nelson) are agricultural and environmental engineers with little experience in web app development, but we are interested in creating web apps to support sustainable aquaculture production in the Southeast. We had user (i.e., shellfish growers) interest, a goal in mind (i.e., develop a new forecast product and decision-support tool for shellfish aquaculturalists), and received funding to support this work. Yet, we experienced several unexpected hurdles from the start of our project that ended up being fairly common hiccups to the seasoned web app developers among us (Young, Parham). As a result, we share the following Ten Simple Rules, which highlight take home messages, including lessons learned and practical tips, of our experience as burgeoning web app developers. We hope researchers interested in developing web apps draw insights from our (in)experience as they set out on their decision support tool development journey.

Requirements for Semantic Web Applications in Engineering

2010 ◽  
Author(s):  
David Fowler ◽  
Richard M. Crowder ◽  
Tao Guan ◽  
Nigel Shadbolt ◽  
Gary Wills
Keyword(s):  
Fluid Dynamics ◽  
Semantic Web ◽  
Web Applications ◽  
Lessons Learned ◽  
Semantic Search ◽  
Semantic Web Technologies ◽  
Web Technologies ◽  
Computational Fluid Dynamics Simulations ◽  
Dynamics Simulations ◽  
Semantic Search Engine

In this paper we describe some applications of Semantic Web technologies for the engineering design community. Specifically, we use Semantic Wikis to form a central knowledge base, which other applications then refer to. The developed applications include an advisor for performing Computational Fluid Dynamics simulations, a Semantic search engine, and an assistant for airfoil design. In the conclusions we discuss lessons learned and subsequently requirements for future systems.

Sign in / Sign up

Export Citation Format

Share Document