Implementing large projects in software engineering courses

NASA Astrophysics Data System (ADS)

Coppit, David

2006-03-01

In software engineering education, large projects are widely recognized as a useful way of exposing students to the real-world difficulties of team software development. But large projects are difficult to put into practice. First, educators rarely have additional time to manage software projects. Second, classrooms have inherent limitations that threaten the realism of large projects. Third, quantitative evaluation of individuals who work in groups is notoriously difficult. As a result, many software engineering courses compromise the project experience by reducing the team sizes, project scope, and risk. In this paper, we present an approach to teaching a one-semester software engineering course in which 20 to 30 students work together to construct a moderately sized (15KLOC) software system. The approach combines carefully coordinated lectures and homeworks, a hierarchical project management structure, modern communication technologies, and a web-based project tracking and individual assessment system. Our approach provides a more realistic project experience for the students, without incurring significant additional overhead for the instructor. We present our experiences using the approach the last 2 years for the software engineering course at The College of William and Mary. Although the approach has some weaknesses, we believe that they are strongly outweighed by the pedagogical benefits.

Implementing a rapid response team: factors influencing success.

PubMed

Murray, Theresa; Kleinpell, Ruth

2006-12-01

Rapid response teams (RRTs), or medical emergency teams, focus on preventing a patient crisis by addressing changes in patient status before a cardiopulmonary arrest occurs. Responding to acute changes, RRTs and medical emergency teams are similar to "code" teams. The exception, however is that they step into action before a patient arrests. Although RRTs are acknowledge as an important initiative, implementation can present many challenges. This article reports on the implementation and ongoing use of a RRT at a community health care setting, highlighting important considerations and strategies for success.

Reduction in Mortality Following Pediatric Rapid Response Team Implementation.

PubMed

Kolovos, Nikoleta S; Gill, Jeff; Michelson, Peter H; Doctor, Allan; Hartman, Mary E

2018-05-01

To evaluate the effectiveness of a physician-led rapid response team program on morbidity and mortality following unplanned admission to the PICU. Before-after study. Single-center quaternary-referral PICU. All unplanned PICU admissions from the ward from 2005 to 2011. The dataset was divided into pre- and post-rapid response team groups for comparison. A Cox proportional hazards model was used to identify the patient characteristics associated with mortality following unplanned PICU admission. Following rapid response team implementation, Pediatric Risk of Mortality, version 3, illness severity was reduced (28.7%), PICU length of stay was less (19.0%), and mortality declined (22%). Relative risk of death following unplanned admission to the PICU after rapid response team implementation was 0.685. For children requiring unplanned admission to the PICU, rapid response team implementation is associated with reduced mortality, admission severity of illness, and length of stay. Rapid response team implementation led to more proximal capture and aggressive intervention in the trajectory of a decompensating pediatric ward patient.

Understanding Implementation of Complex Interventions in Primary Care Teams.

PubMed

Luig, Thea; Asselin, Jodie; Sharma, Arya M; Campbell-Scherer, Denise L

2018-01-01

The implementation of interventions to support practice change in primary care settings is complex. Pragmatic strategies, grounded in empiric data, are needed to navigate real-world challenges and unanticipated interactions with context that can impact implementation and outcomes. This article uses the example of the "5As Team" randomized control trial to explore implementation strategies to promote knowledge transfer, capacity building, and practice integration, and their interaction within the context of an interdisciplinary primary care team. We performed a qualitative evaluation of the implementation process of the 5As Team intervention study, a randomized control trial of a complex intervention in primary care. We conducted thematic analysis of field notes of intervention sessions, log books of the practice facilitation team members, and semistructured interviews with 29 interdisciplinary clinician participants. We used and further developed the Interactive Systems Framework for dissemination and implementation to interpret and structure findings. Three themes emerged that illuminate interactions between implementation processes, context, and outcomes: (1) facilitating team communication supported collective and individual sense-making and adoption of the innovation, (2) iterative evaluation of the implementation process and real-time feedback-driven adaptions of the intervention proved crucial for sustainable, context-appropriate intervention impact, (3) stakeholder engagement led to both knowledge exchange that contributes to local problem solving and to shaping a clinical context that is supportive to practice change. Our findings contribute pragmatic strategies that can help practitioners and researchers to navigate interactions between context, intervention, and implementation factors to increase implementation success. We further developed an implementation framework that includes sustained engagement with stakeholders, facilitation of team sense

Software-implemented fault insertion: An FTMP example

NASA Technical Reports Server (NTRS)

Czeck, Edward W.; Siewiorek, Daniel P.; Segall, Zary Z.

1987-01-01

This report presents a model for fault insertion through software; describes its implementation on a fault-tolerant computer, FTMP; presents a summary of fault detection, identification, and reconfiguration data collected with software-implemented fault insertion; and compares the results to hardware fault insertion data. Experimental results show detection time to be a function of time of insertion and system workload. For the fault detection time, there is no correlation between software-inserted faults and hardware-inserted faults; this is because hardware-inserted faults must manifest as errors before detection, whereas software-inserted faults immediately exercise the error detection mechanisms. In summary, the software-implemented fault insertion is able to be used as an evaluation technique for the fault-handling capabilities of a system in fault detection, identification and recovery. Although the software-inserted faults do not map directly to hardware-inserted faults, experiments show software-implemented fault insertion is capable of emulating hardware fault insertion, with greater ease and automation.

Exploring interpersonal behavior and team sensemaking during health information technology implementation.

PubMed

Kitzmiller, Rebecca R; McDaniel, Reuben R; Johnson, Constance M; Lind, E Allan; Anderson, Ruth A

2013-01-01

We examine how interpersonal behavior and social interaction influence team sensemaking and subsequent team actions during a hospital-based health information technology (HIT) implementation project. Over the course of 18 months, we directly observed the interpersonal interactions of HIT implementation teams using a sensemaking lens. We identified three voice-promoting strategies enacted by team leaders that fostered team member voice and sensemaking; communicating a vision; connecting goals to team member values; and seeking team member input. However, infrequent leader expressions of anger quickly undermined team sensemaking, halting dialog essential to problem solving. By seeking team member opinions, team leaders overcame the negative effects of anger. Leaders must enact voice-promoting behaviors and use them throughout a team's engagement. Further, training teams in how to use conflict to achieve greater innovation may improve sensemaking essential to project risk mitigation. Health care work processes are complex; teams involved in implementing improvements must be prepared to deal with conflicting, contentious issues, which will arise during change. Therefore, team conflict training may be essential to sustaining sensemaking. Future research should seek to identify team interactions that foster sensemaking, especially when topics are difficult or unwelcome, then determine the association between staff sensemaking and the impact on HIT implementation outcomes. We are among the first to focus on project teams tasked with HIT implementation. This research extends our understanding of how leaders' behaviors might facilitate or impeded speaking up among project teams in health care settings.

Teaching Tip: Managing Software Engineering Student Teams Using Pellerin's 4-D System

ERIC Educational Resources Information Center

Doman, Marguerite; Besmer, Andrew; Olsen, Anne

2015-01-01

In this article, we discuss the use of Pellerin's Four Dimension Leadership System (4-D) as a way to manage teams in a classroom setting. Over a 5-year period, we used a modified version of the 4-D model to manage teams within a senior level Software Engineering capstone course. We found that this approach for team management in a classroom…

Self-Managed Work Teams in Nursing Homes: Implementing and Empowering Nurse Aide Teams

ERIC Educational Resources Information Center

Yeatts, Dale E.; Cready, Cynthia; Ray, Beth; DeWitt, Amy; Queen, Courtney

2004-01-01

Purpose: This article describes the progress of our study to examine the advantages and costs of using self-managed nurse aide teams in nursing homes, steps that are being taken to implement such teams, and management strategies being used to manage the teams. Design and Methods: A quasi-experimental design is underway where certified nurse aide…

Improving Video Game Development: Facilitating Heterogeneous Team Collaboration through Flexible Software Processes

NASA Astrophysics Data System (ADS)

Musil, Juergen; Schweda, Angelika; Winkler, Dietmar; Biffl, Stefan

Based on our observations of Austrian video game software development (VGSD) practices we identified a lack of systematic processes/method support and inefficient collaboration between various involved disciplines, i.e. engineers and artists. VGSD includes heterogeneous disciplines, e.g. creative arts, game/content design, and software. Nevertheless, improving team collaboration and process support is an ongoing challenge to enable a comprehensive view on game development projects. Lessons learned from software engineering practices can help game developers to increase game development processes within a heterogeneous environment. Based on a state of the practice survey in the Austrian games industry, this paper presents (a) first results with focus on process/method support and (b) suggests a candidate flexible process approach based on Scrum to improve VGSD and team collaboration. Results showed (a) a trend to highly flexible software processes involving various disciplines and (b) identified the suggested flexible process approach as feasible and useful for project application.

Fault-tolerant software - Experiment with the sift operating system. [Software Implemented Fault Tolerance computer

NASA Technical Reports Server (NTRS)

Brunelle, J. E.; Eckhardt, D. E., Jr.

1985-01-01

Results are presented of an experiment conducted in the NASA Avionics Integrated Research Laboratory (AIRLAB) to investigate the implementation of fault-tolerant software techniques on fault-tolerant computer architectures, in particular the Software Implemented Fault Tolerance (SIFT) computer. The N-version programming and recovery block techniques were implemented on a portion of the SIFT operating system. The results indicate that, to effectively implement fault-tolerant software design techniques, system requirements will be impacted and suggest that retrofitting fault-tolerant software on existing designs will be inefficient and may require system modification.

Streamlining Software Aspects of Certification: Technical Team Report on the First Industry Workshop

NASA Technical Reports Server (NTRS)

Hayhurst, Kelly J.; Holloway, C. Michael; Knight, John C.; Leveson, Nancy G.; Yang, Jeffrey C.; Dorsey, Cheryl A.; McCormick, G. Frank

1998-01-01

To address concerns about time and expense associated with software aspects of certification, the Federal Aviation Administration (FAA) began the Streamlining Software Aspects of Certification (SSAC) program. As part of this program, a Technical Team was established to determine whether the cost and time associated with certifying aircraft can be reduced while maintaining or improving safety, with the intent of impacting the FAA's Flight 2000 program. The Technical Team conducted a workshop to gain a better understanding of the major concerns in industry about software cost and schedule. Over 120 people attended the workshop, including representatives from the FAA,commercial transport and general aviation aircraft manufacturers and suppliers, and procurers and developers of non-airborne systems; and, more than 200 issues about software aspects of certification were recorded. This paper provides an overview of the SSAC program, motivation for the workshop, details of the workshop activities and outcomes, and recommendations for follow-on work.

Interprofessional Health Team Communication About Hospital Discharge: An Implementation Science Evaluation Study.

PubMed

Bahr, Sarah J; Siclovan, Danielle M; Opper, Kristi; Beiler, Joseph; Bobay, Kathleen L; Weiss, Marianne E

The Consolidated Framework for Implementation Research guided formative evaluation of the implementation of a redesigned interprofessional team rounding process. The purpose of the redesigned process was to improve health team communication about hospital discharge. Themes emerging from interviews of patients, nurses, and providers revealed the inherent value and positive characteristics of the new process, but also workflow, team hierarchy, and process challenges to successful implementation. The evaluation identified actionable recommendations for modifying the implementation process.

TeamWATCH: Visualizing development activities using a 3-D city metaphor to improve conflict detection and team awareness

PubMed Central

Ye, Xin

2018-01-01

The awareness of others’ activities has been widely recognized as essential in facilitating coordination in a team among Computer-Supported Cooperative Work communities. Several field studies of software developers in large software companies such as Microsoft have shown that coworker and artifact awareness are the most common information needs for software developers; however, they are also two of the seven most frequently unsatisfied information needs. To address this problem, we built a workspace awareness tool named TeamWATCH to visualize developer activities using a 3-D city metaphor. In this paper, we discuss the importance of awareness in software development, review existing workspace awareness tools, present the design and implementation of TeamWATCH, and evaluate how it could help detect and resolve conflicts earlier and better maintain group awareness via a controlled experiment. The experimental results showed that the subjects using TeamWATCH performed significantly better with respect to early conflict detection and resolution. PMID:29558519

Using "Facebook" to Improve Communication in Undergraduate Software Development Teams

ERIC Educational Resources Information Center

Charlton, Terence; Devlin, Marie; Drummond, Sarah

2009-01-01

As part of the CETL ALiC initiative (Centre of Excellence in Teaching and Learning: Active Learning in Computing), undergraduate computing science students at Newcastle and Durham universities participated in a cross-site team software development project. To ensure we offer adequate resources to support this collaboration, we conducted an…

Sandia National Laboratories Advanced Simulation and Computing (ASC) software quality plan : ASC software quality engineering practices Version 3.0.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Turgeon, Jennifer L.; Minana, Molly A.; Hackney, Patricia

2009-01-01

The purpose of the Sandia National Laboratories (SNL) Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. Quality is defined in the US Department of Energy/National Nuclear Security Agency (DOE/NNSA) Quality Criteria, Revision 10 (QC-1) as 'conformance to customer requirements and expectations'. This quality plan defines the SNL ASC Program software quality engineering (SQE) practices and provides a mapping of these practices to the SNL Corporate Process Requirement (CPR) 001.3.6; 'Corporate Software Engineering Excellence'. This plan also identifies ASC management's and themore » software project teams responsibilities in implementing the software quality practices and in assessing progress towards achieving their software quality goals. This SNL ASC Software Quality Plan establishes the signatories commitments to improving software products by applying cost-effective SQE practices. This plan enumerates the SQE practices that comprise the development of SNL ASC's software products and explains the project teams opportunities for tailoring and implementing the practices.« less

Systematic review of practice guideline dissemination and implementation strategies for healthcare teams and team-based practice.

PubMed

Medves, Jennifer; Godfrey, Christina; Turner, Carly; Paterson, Margo; Harrison, Margaret; MacKenzie, Lindsay; Durando, Paola

2010-06-01

To synthesis the literature relevant to guideline dissemination and implementation strategies for healthcare teams and team-based practice. Systematic approach utilising Joanna Briggs Institute methods. Two reviewers screened all articles and where there was disagreement, a third reviewer determined inclusion. Initial search revealed 12,083 of which 88 met the inclusion criteria. Ten dissemination and implementation strategies identified with distribution of educational materials the most common. Studies were assessed for patient or practitioner outcomes and changes in practice, knowledge and economic outcomes. A descriptive analysis revealed multiple approaches using teams of healthcare providers were reported to have statistically significant results in knowledge, practice and/or outcomes for 72.7% of the studies. Team-based care using practice guidelines locally adapted can affect positively patient and provider outcomes. © 2010 The Authors. Journal Compilation © Blackwell Publishing Asia Pty Ltd.

Promoting Action on Research Implementation in Health Services framework applied to TeamSTEPPS implementation in small rural hospitals.

PubMed

Ward, Marcia M; Baloh, Jure; Zhu, Xi; Stewart, Greg L

A particularly useful model for examining implementation of quality improvement interventions in health care settings is the PARIHS (Promoting Action on Research Implementation in Health Services) framework developed by Kitson and colleagues. The PARIHS framework proposes three elements (evidence, context, and facilitation) that are related to successful implementation. An evidence-based program focused on quality enhancement in health care, termed TeamSTEPPS (Team Strategies and Tools to Enhance Performance and Patient Safety), has been widely promoted by the Agency for Healthcare Research and Quality, but research is needed to better understand its implementation. We apply the PARIHS framework in studying TeamSTEPPS implementation to identify elements that are most closely related to successful implementation. Quarterly interviews were conducted over a 9-month period in 13 small rural hospitals that implemented TeamSTEPPS. Interview quotes that were related to each of the PARIHS elements were identified using directed content analysis. Transcripts were also scored quantitatively, and bivariate regression analysis was employed to explore relationships between PARIHS elements and successful implementation related to planning activities. The current findings provide support for the PARIHS framework and identified two of the three PARIHS elements (context and facilitation) as important contributors to successful implementation. This study applies the PARIHS framework to TeamSTEPPS, a widely used quality initiative focused on improving health care quality and patient safety. By focusing on small rural hospitals that undertook this quality improvement activity of their own accord, our findings represent effectiveness research in an understudied segment of the health care delivery system. By identifying context and facilitation as the most important contributors to successful implementation, these analyses provide a focus for efficient and effective sustainment of Team

The Cooperate Assistive Teamwork Environment for Software Description Languages.

PubMed

Groenda, Henning; Seifermann, Stephan; Müller, Karin; Jaworek, Gerhard

2015-01-01

Versatile description languages such as the Unified Modeling Language (UML) are commonly used in software engineering across different application domains in theory and practice. They often use graphical notations and leverage visual memory for expressing complex relations. Those notations are hard to access for people with visual impairment and impede their smooth inclusion in an engineering team. Existing approaches provide textual notations but require manual synchronization between the notations. This paper presents requirements for an accessible and language-aware team work environment as well as our plan for the assistive implementation of Cooperate. An industrial software engineering team consisting of people with and without visual impairment will evaluate the implementation.

Practical Team-Based Learning from Planning to Implementation

PubMed Central

Bell, Edward; Eng, Marty; Fuentes, David G.; Helms, Kristen L.; Maki, Erik D.; Vyas, Deepti

2015-01-01

Team-based learning (TBL) helps instructors develop an active teaching approach for the classroom through group work. The TBL infrastructure engages students in the learning process through the Readiness Assessment Process, problem-solving through team discussions, and peer feedback to ensure accountability. This manuscript describes the benefits and barriers of TBL, and the tools necessary for developing, implementing, and critically evaluating the technique within coursework in a user-friendly method. Specifically, the manuscript describes the processes underpinning effective TBL development, preparation, implementation, assessment, and evaluation, as well as practical techniques and advice from authors’ classroom experiences. The paper also highlights published articles in the area of TBL in education, with a focus on pharmacy education. PMID:26889061

Career Development via Counselor/Teacher Teams; Guide for Implementation.

ERIC Educational Resources Information Center

Royal Oak City School District, MI.

The career development modules of the implementation guide, designed by counselor/teacher teams in Royal Oak, Michigan for junior high students, are intended to be used as a working copy for counselor/teacher teams. Career education concepts of self-awareness, assessment, and decision-making are correlated with the broad questions of: Who am I?…

Software Quality Assurance Metrics

NASA Technical Reports Server (NTRS)

McRae, Kalindra A.

2004-01-01

Software Quality Assurance (SQA) is a planned and systematic set of activities that ensures conformance of software life cycle processes and products conform to requirements, standards and procedures. In software development, software quality means meeting requirements and a degree of excellence and refinement of a project or product. Software Quality is a set of attributes of a software product by which its quality is described and evaluated. The set of attributes includes functionality, reliability, usability, efficiency, maintainability, and portability. Software Metrics help us understand the technical process that is used to develop a product. The process is measured to improve it and the product is measured to increase quality throughout the life cycle of software. Software Metrics are measurements of the quality of software. Software is measured to indicate the quality of the product, to assess the productivity of the people who produce the product, to assess the benefits derived from new software engineering methods and tools, to form a baseline for estimation, and to help justify requests for new tools or additional training. Any part of the software development can be measured. If Software Metrics are implemented in software development, it can save time, money, and allow the organization to identify the caused of defects which have the greatest effect on software development. The summer of 2004, I worked with Cynthia Calhoun and Frank Robinson in the Software Assurance/Risk Management department. My task was to research and collect, compile, and analyze SQA Metrics that have been used in other projects that are not currently being used by the SA team and report them to the Software Assurance team to see if any metrics can be implemented in their software assurance life cycle process.

Team Software Process (TSP) Coach Mentoring Program Guidebook Version 1.1

DTIC Science & Technology

2010-06-01

All training was conducted in English only, and observations were limited to English- speaking coaches and teams. The SEI-Certified TSP Coach...programs also enable the expansion of TSP implementation to non-English- speaking teams and organizations. This expanded capacity for qualifying candidate...Improvement Could Benefit from Development Capable and Effective Role Model 1. I listen before speaking . 2. I demonstrate persuasiveness in

Design study of Software-Implemented Fault-Tolerance (SIFT) computer

NASA Technical Reports Server (NTRS)

Wensley, J. H.; Goldberg, J.; Green, M. W.; Kutz, W. H.; Levitt, K. N.; Mills, M. E.; Shostak, R. E.; Whiting-Okeefe, P. M.; Zeidler, H. M.

1982-01-01

Software-implemented fault tolerant (SIFT) computer design for commercial aviation is reported. A SIFT design concept is addressed. Alternate strategies for physical implementation are considered. Hardware and software design correctness is addressed. System modeling and effectiveness evaluation are considered from a fault-tolerant point of view.

Team Software Development for Aerothermodynamic and Aerodynamic Analysis and Design

NASA Technical Reports Server (NTRS)

Alexandrov, N.; Atkins, H. L.; Bibb, K. L.; Biedron, R. T.; Carpenter, M. H.; Gnoffo, P. A.; Hammond, D. P.; Jones, W. T.; Kleb, W. L.; Lee-Rausch, E. M.

2003-01-01

A collaborative approach to software development is described. The approach employs the agile development techniques: project retrospectives, Scrum status meetings, and elements of Extreme Programming to efficiently develop a cohesive and extensible software suite. The software product under development is a fluid dynamics simulator for performing aerodynamic and aerothermodynamic analysis and design. The functionality of the software product is achieved both through the merging, with substantial rewrite, of separate legacy codes and the authorship of new routines. Examples of rapid implementation of new functionality demonstrate the benefits obtained with this agile software development process. The appendix contains a discussion of coding issues encountered while porting legacy Fortran 77 code to Fortran 95, software design principles, and a Fortran 95 coding standard.

Developing high-quality educational software.

PubMed

Johnson, Lynn A; Schleyer, Titus K L

2003-11-01

The development of effective educational software requires a systematic process executed by a skilled development team. This article describes the core skills required of the development team members for the six phases of successful educational software development. During analysis, the foundation of product development is laid including defining the audience and program goals, determining hardware and software constraints, identifying content resources, and developing management tools. The design phase creates the specifications that describe the user interface, the sequence of events, and the details of the content to be displayed. During development, the pieces of the educational program are assembled. Graphics and other media are created, video and audio scripts written and recorded, the program code created, and support documentation produced. Extensive testing by the development team (alpha testing) and with students (beta testing) is conducted. Carefully planned implementation is most likely to result in a flawless delivery of the educational software and maintenance ensures up-to-date content and software. Due to the importance of the sixth phase, evaluation, we have written a companion article on it that follows this one. The development of a CD-ROM product is described including the development team, a detailed description of the development phases, and the lessons learned from the project.

ERP Software Implementation Best Practices.

ERIC Educational Resources Information Center

Frantz, Pollyanne S.; Southerland, Arthur R.; Johnson, James T.

2002-01-01

Studied the perceptions of chief financial and information officers of enterprise resource planning (ERP) software implementation best practices. Usable responses from 159 respondents show consensus for the most part between the perceptions of the two groups and describe some best practices that represent common ground. (SLD)

Effective Team Support: From Task and Cognitive Modeling to Software Agents for Time-Critical Complex Work Environments

NASA Technical Reports Server (NTRS)

Remington, Roger W. (Technical Monitor); John, Bonnie E.; Sycara, Katia

2005-01-01

The purpose of this research contract was to perform multidisciplinary research between CMU psychologists, computer scientists and NASA researchers to design a next generation collaborative system to support a team of human experts and intelligent agents. To achieve robust performance enhancement of such a system, we had proposed to perform task and cognitive modeling to thoroughly understand the impact technology makes on the organization and on key individual personnel. Guided by cognitively-inspired requirements, we would then develop software agents that support the human team in decision making, information filtering, information distribution and integration to enhance team situational awareness. During the period covered by this final report, we made substantial progress in completing a system for empirical data collection, cognitive modeling, and the building of software agents to support a team's tasks, and in running experiments for the collection of baseline data.

Interprofessional Team's Perception of Care Delivery After Implementation of a Pediatric Pain and Sedation Protocol.

PubMed

Staveski, Sandra L; Wu, May; Tesoro, Tiffany M; Roth, Stephen J; Cisco, Michael J

2017-06-01

Pain and agitation are common experiences of patients in pediatric cardiac intensive care units. Variability in assessments by health care providers, communication, and treatment of pain and agitation creates challenges in management of pain and sedation. To develop guidelines for assessment and treatment of pain, agitation, and delirium in the pediatric cardiac intensive unit in an academic children's hospital and to document the effects of implementation of the guidelines on the interprofessional team's perception of care delivery and team function. Before and after implementation of the guidelines, interprofessional team members were surveyed about the members' perception of analgesia, sedation, and delirium management RESULTS: Members of the interprofessional team felt more comfortable with pain and sedation management after implementation of the guidelines. Team members reported improvements in team communication on patients' comfort. Members thought that important information was less likely to be lost during transfer of care. They also noted that the team carried out comfort management plans and used pharmacological and nonpharmacological therapies better after implementation of the guidelines than they did before implementation. Guidelines for pain and sedation management were associated with perceived improvements in team function and patient care by members of the interprofessional team. ©2017 American Association of Critical-Care Nurses.

ICU team composition and its association with ABCDE implementation in a quality collaborative.

PubMed

Costa, Deena Kelly; Valley, Thomas S; Miller, Melissa A; Manojlovich, Milisa; Watson, Sam R; McLellan, Phyllis; Pope, Corine; Hyzy, Robert C; Iwashyna, Theodore J

2018-04-01

Awakening, Breathing Coordination, Delirium, and Early Mobility bundle (ABCDE) should involve an interprofessional team, yet no studies describe what team composition supports implementation. We administered a survey at MHA Keystone Center ICU 2015 workshop. We measured team composition by the frequency of nurse, respiratory therapist, physician, physical therapist, nurse practitioner/physician assistant or nursing assistant involvement in 1) spontaneous awakening trials (SATs), 2) spontaneous breathing trials, 3) delirium and 4) early mobility. We assessed ABCDE implementation using a 5-point Likert ("routine part of every patient's care" - "no plans to implement"). We used ordinal logistic regression to examine team composition and ABCDE implementation, adjusting for confounders and clustering. From 293 surveys (75% response rate), we found that frequent nurse [OR 6.1 (1.1-34.9)] and physician involvement [OR 4.2 (1.3-13.4)] in SATs, nurse [OR 4.7 (1.6-13.4)] and nursing assistant's involvement [OR 3.9 (1.2-13.5)] in delirium and nurse [OR 2.8 (1.2-6.7)], physician [OR (3.6 (1.2-10.3)], and nursing assistants' involvement [OR 2.3 (1.1-4.8)] in early mobility were significantly associated with higher odds of routine ABCDE implementation. ABCDE implementation was associated with frequent involvement of team members, suggesting a need for role articulation and coordination. Copyright © 2017 Elsevier Inc. All rights reserved.

Repository-based software engineering program

NASA Technical Reports Server (NTRS)

Wilson, James

1992-01-01

The activities performed during September 1992 in support of Tasks 01 and 02 of the Repository-Based Software Engineering Program are outlined. The recommendations and implementation strategy defined at the September 9-10 meeting of the Reuse Acquisition Action Team (RAAT) are attached along with the viewgraphs and reference information presented at the Institute for Defense Analyses brief on legal and patent issues related to software reuse.

Project SYNERGY: Software Support for Underprepared Students. Software Implementation Report.

ERIC Educational Resources Information Center

Anandam, Kamala; And Others

Miami-Dade Community College's (MDCC's) implementation and assessment of computer software as a part of Project SYNERGY, a multi-institutional project funded by the International Business Machines (IBM) Corporation designed to seek technological solutions for helping students underprepared in reading, writing and mathematics, is described in this…

Implementing the Team Approach in Higher Education: Important Questions and Advice for Administrators

ERIC Educational Resources Information Center

Lara, Tracy M.; Hughey, Aaron W.

2008-01-01

Many companies have implemented the team approach as a way to empower their employees in an effort to enhance productivity, quality and overall profitability. While application of the concept to higher education administration has been limited, colleges and universities could benefit from the team approach if implemented appropriately and…

Reference software implementation for GIFTS ground data processing

NASA Astrophysics Data System (ADS)

Garcia, R. K.; Howell, H. B.; Knuteson, R. O.; Martin, G. D.; Olson, E. R.; Smuga-Otto, M. J.

2006-08-01

Future satellite weather instruments such as high spectral resolution imaging interferometers pose a challenge to the atmospheric science and software development communities due to the immense data volumes they will generate. An open-source, scalable reference software implementation demonstrating the calibration of radiance products from an imaging interferometer, the Geosynchronous Imaging Fourier Transform Spectrometer1 (GIFTS), is presented. This paper covers essential design principles laid out in summary system diagrams, lessons learned during implementation and preliminary test results from the GIFTS Information Processing System (GIPS) prototype.

Software Implemented Fault-Tolerant (SIFT) user's guide

NASA Technical Reports Server (NTRS)

Green, D. F., Jr.; Palumbo, D. L.; Baltrus, D. W.

1984-01-01

Program development for a Software Implemented Fault Tolerant (SIFT) computer system is accomplished in the NASA LaRC AIRLAB facility using a DEC VAX-11 to interface with eight Bendix BDX 930 flight control processors. The interface software which provides this SIFT program development capability was developed by AIRLAB personnel. This technical memorandum describes the application and design of this software in detail, and is intended to assist both the user in performance of SIFT research and the systems programmer responsible for maintaining and/or upgrading the SIFT programming environment.

Generalized implementation of software safety policies

NASA Technical Reports Server (NTRS)

Knight, John C.; Wika, Kevin G.

1994-01-01

As part of a research program in the engineering of software for safety-critical systems, we are performing two case studies. The first case study, which is well underway, is a safety-critical medical application. The second, which is just starting, is a digital control system for a nuclear research reactor. Our goal is to use these case studies to permit us to obtain a better understanding of the issues facing developers of safety-critical systems, and to provide a vehicle for the assessment of research ideas. The case studies are not based on the analysis of existing software development by others. Instead, we are attempting to create software for new and novel systems in a process that ultimately will involve all phases of the software lifecycle. In this abstract, we summarize our results to date in a small part of this project, namely the determination and classification of policies related to software safety that must be enforced to ensure safe operation. We hypothesize that this classification will permit a general approach to the implementation of a policy enforcement mechanism.

Team Collaboration Software

NASA Technical Reports Server (NTRS)

Wang, Yeou-Fang; Schrock, Mitchell; Baldwin, John R.; Borden, Charles S.

2010-01-01

The Ground Resource Allocation and Planning Environment (GRAPE 1.0) is a Web-based, collaborative team environment based on the Microsoft SharePoint platform, which provides Deep Space Network (DSN) resource planners tools and services for sharing information and performing analysis.

Software implementation of the SKIPSM paradigm under PIP

NASA Astrophysics Data System (ADS)

Hack, Ralf; Waltz, Frederick M.; Batchelor, Bruce G.

1997-09-01

SKIPSM (separated-kernel image processing using finite state machines) is a technique for implementing large-kernel binary- morphology operators and many other operations. While earlier papers on SKIPSM concentrated mainly on implementations using pipelined hardware, there is considerable scope for achieving major speed improvements in software systems. Using identical control software, one-pass binary erosion and dilation structuring elements (SEs) ranging from the trivial (3 by 3) to the gigantic (51 by 51, or even larger), are readily available. Processing speed is independent of the size of the SE, making the SKIPSM approach practical for work with very large SEs on ordinary desktop computers. PIP (prolog image processing) is an interactive machine vision prototyping environment developed at the University of Wales Cardiff. It consists of a large number of image processing operators embedded within the standard AI language Prolog. This paper describes the SKIPSM implementation of binary morphology operators within PIP. A large set of binary erosion and dilation operations (circles, squares, diamonds, octagons, etc.) is available to the user through a command-line driven dialogue, via pull-down menus, or incorporated into standard (Prolog) programs. Little has been done thus far to optimize speed on this first software implementation of SKIPSM. Nevertheless, the results are impressive. The paper describes sample applications and presents timing figures. Readers have the opportunity to try out these operations on demonstration software written by the University of Wales, or via their WWW home page at http://bruce.cs.cf.ac.uk/bruce/index.html .

Spacelab user implementation assessment study. (Software requirements analysis). Volume 2: Technical report

NASA Technical Reports Server (NTRS)

1976-01-01

The engineering analyses and evaluation studies conducted for the Software Requirements Analysis are discussed. Included are the development of the study data base, synthesis of implementation approaches for software required by both mandatory onboard computer services and command/control functions, and identification and implementation of software for ground processing activities.

A systematic review of team formulation in clinical psychology practice: Definition, implementation, and outcomes.

PubMed

Geach, Nicole; Moghaddam, Nima G; De Boos, Danielle

2018-06-01

Team formulation is promoted by professional practice guidelines for clinical psychologists. However, it is unclear whether team formulation is understood/implemented in consistent ways - or whether there is outcome evidence to support the promotion of this practice. This systematic review aimed to (1) synthesize how team formulation practice is defined and implemented by practitioner psychologists and (2) analyse the range of team formulation outcomes in the peer-reviewed literature. Seven electronic bibliographic databases were searched in June 2016. Eleven articles met inclusion criteria and were quality assessed. Extracted data were synthesized using content analysis. Descriptions of team formulation revealed three main forms of instantiation: (1) a structured, consultation approach; (2) semi-structured, reflective practice meetings; and (3) unstructured/informal sharing of ideas through routine interactions. Outcome evidence linked team formulation to a range of outcomes for staff teams and service users, including some negative outcomes. Quality appraisal identified significant issues with evaluation methods; such that, overall, outcomes were not well-supported. There is weak evidence to support the claimed beneficial outcomes of team formulation in practice. There is a need for greater specification and standardization of 'team formulation' practices, to enable a clearer understanding of any relationships with outcomes and implications for best-practice implementations. Under the umbrella term of 'team formulation', three types of practice are reported: (1) highly structured consultation; (2) reflective practice meetings; and (3) informal sharing of ideas. Outcomes linked to team formulation, including some negative outcomes, were not well evidenced. Research using robust study designs is required to investigate the process and outcomes of team formulation practice. © 2017 The British Psychological Society.

Relating Communications Mode Choice and Teamwork Quality: Conversational versus Textual Communication in IT System and Software Development Teams

ERIC Educational Resources Information Center

Smith, James Robert

2012-01-01

This cross-sectional study explored how IT system and software development team members communicated in the workplace and whether teams that used more verbal communication (and less text-based communication) experienced higher levels of collaboration as measured using the Teamwork Quality (TWQ) scale. Although computer-mediated communication tools…

Improving collaborative learning in online software engineering education

NASA Astrophysics Data System (ADS)

Neill, Colin J.; DeFranco, Joanna F.; Sangwan, Raghvinder S.

2017-11-01

Team projects are commonplace in software engineering education. They address a key educational objective, provide students critical experience relevant to their future careers, allow instructors to set problems of greater scale and complexity than could be tackled individually, and are a vehicle for socially constructed learning. While all student teams experience challenges, those in fully online programmes must also deal with remote working, asynchronous coordination, and computer-mediated communications all of which contribute to greater social distance between team members. We have developed a facilitation framework to aid team collaboration and have demonstrated its efficacy, in prior research, with respect to team performance and outcomes. Those studies indicated, however, that despite experiencing improved project outcomes, students working in effective software engineering teams did not experience significantly improved individual achievement. To address this deficiency we implemented theoretically grounded refinements to the collaboration model based upon peer-tutoring research. Our results indicate a modest, but statistically significant (p = .08), improvement in individual achievement using this refined model.

Tips for Ensuring Successful Software Implementation

ERIC Educational Resources Information Center

Weathers, Robert

2013-01-01

Implementing an enterprise-level, mission-critical software system is an infrastructure project akin to other sizable projects, such as building a school. It's costly and complex, takes a year or more to complete, requires the collaboration of many different parties, involves uncertainties, results in a long-lived asset requiring ongoing…

Small PACS implementation using publicly available software

NASA Astrophysics Data System (ADS)

Passadore, Diego J.; Isoardi, Roberto A.; Gonzalez Nicolini, Federico J.; Ariza, P. P.; Novas, C. V.; Omati, S. A.

1998-07-01

Building cost effective PACS solutions is a main concern in developing countries. Hardware and software components are generally much more expensive than in developed countries and also more tightened financial constraints are the main reasons contributing to a slow rate of implementation of PACS. The extensive use of Internet for sharing resources and information has brought a broad number of freely available software packages to an ever-increasing number of users. In the field of medical imaging is possible to find image format conversion packages, DICOM compliant servers for all kinds of service classes, databases, web servers, image visualization, manipulation and analysis tools, etc. This paper describes a PACS implementation for review and storage built on freely available software. It currently integrates four diagnostic modalities (PET, CT, MR and NM), a Radiotherapy Treatment Planning workstation and several computers in a local area network, for image storage, database management and image review, processing and analysis. It also includes a web-based application that allows remote users to query the archive for studies from any workstation and to view the corresponding images and reports. We conclude that the advantage of using this approach is twofold. It allows a full understanding of all the issues involved in the implementation of a PACS and also contributes to keep costs down while enabling the development of a functional system for storage, distribution and review that can prove to be helpful for radiologists and referring physicians.

Team Training in the Perioperative Arena: A Methodology for Implementation and Auditing Behavior.

PubMed

Rhee, Amanda J; Valentin-Salgado, Yessenia; Eshak, David; Feldman, David; Kischak, Pat; Reich, David L; LoPachin, Vicki; Brodman, Michael

Preventable medical errors in the operating room are most often caused by ineffective communication and suboptimal team dynamics. TeamSTEPPS is a government-funded, evidence-based program that provides tools and education to improve teamwork in medicine. The study hospital implemented TeamSTEPPS in the operating room and merged the program with a surgical safety checklist. Audits were performed to collect both quantitative and qualitative information on time out (brief) and debrief conversations, using a standardized audit tool. A total of 1610 audits over 6 months were performed by live auditors. Performance was sustained at desired levels or improved for all qualitative metrics using χ 2 and linear regression analyses. Additionally, the absolute number of wrong site/side/person surgery and unintentionally retained foreign body counts decreased after TeamSTEPPS implementation.

Implementing Educational Software and Evaluating Its Academic Effectiveness: Part I.

ERIC Educational Resources Information Center

Jolicoeur, Karen; Berger, Dale E.

1988-01-01

This basic plan for implementing educational software in the classroom incorporates a research design for evaluating its effectiveness. A study of fifth grade classrooms using game and tutorial software for spelling and fractions is used as an example. Topics discussed include software selection, selecting groups of comparable ability, and use of…

Sandia National Laboratories Advanced Simulation and Computing (ASC) software quality plan. Part 1: ASC software quality engineering practices, Version 2.0.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Sturtevant, Judith E.; Heaphy, Robert; Hodges, Ann Louise

2006-09-01

The purpose of the Sandia National Laboratories Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. The plan defines the ASC program software quality practices and provides mappings of these practices to Sandia Corporate Requirements CPR 1.3.2 and 1.3.6 and to a Department of Energy document, ASCI Software Quality Engineering: Goals, Principles, and Guidelines. This document also identifies ASC management and software project teams responsibilities in implementing the software quality practices and in assessing progress towards achieving their software quality goals.

Swarming Robot Design, Construction and Software Implementation

NASA Technical Reports Server (NTRS)

Stolleis, Karl A.

2014-01-01

In this paper is presented an overview of the hardware design, construction overview, software design and software implementation for a small, low-cost robot to be used for swarming robot development. In addition to the work done on the robot, a full simulation of the robotic system was developed using Robot Operating System (ROS) and its associated simulation. The eventual use of the robots will be exploration of evolving behaviors via genetic algorithms and builds on the work done at the University of New Mexico Biological Computation Lab.

Simplifying applications software for vision guided robot implementation

NASA Technical Reports Server (NTRS)

Duncheon, Charlie

1994-01-01

A simple approach to robot applications software is described. The idea is to use commercially available software and hardware wherever possible to minimize system costs, schedules and risks. The U.S. has been slow in the adaptation of robots and flexible automation compared to the fluorishing growth of robot implementation in Japan. The U.S. can benefit from this approach because of a more flexible array of vision guided robot technologies.

Evaluation of Multi-Age Team (MAT): Implementation at Crabapple Middle School: Report for 1995-1996.

ERIC Educational Resources Information Center

Elmore, Randy; Wisenbaker, Joseph

In fall 1993, administrators and faculty at the Crabapple Middle School in Roswell, Georgia, implemented the Multi-Age Team (MAT) program, creating multiage teams of sixth-, seventh-, and eighth-grade students. The project's main goal was to enhance self-esteem. Additional goals included implementation of interdisciplinary, thematic instruction;…

A Capstone Course on Agile Software Development Using Scrum

ERIC Educational Resources Information Center

Mahnic, V.

2012-01-01

In this paper, an undergraduate capstone course in software engineering is described that not only exposes students to agile software development, but also makes it possible to observe the behavior of developers using Scrum for the first time. The course requires students to work as Scrum Teams, responsible for the implementation of a set of user…

Evaluation of Multi-Age Team (MAT) Implementation at Crabapple Middle School: Report for 1994-1995.

ERIC Educational Resources Information Center

Elmore, Randy; Wisenbaker, Joseph

In fall 1993, administrators and faculty at the Crabappple Middle School in Roswell, Georgia, implemented the Multi-Age Team (MAT) program, creating multi-age teams of sixth-, seventh-, and eighth-grade students. The projects' main goal was to enhance self-esteem. Additional goals included implementation of interdisciplinary, thematic instruction;…

Design and implementation of Skype USB user gateway software

NASA Astrophysics Data System (ADS)

Qi, Yang

2017-08-01

With the widespread application of VoIP, the client with private protocol becomes more and more popular. Skype is one of the representatives. How to connect Skype with PSTN just by Skype client has gradually become hot. This paper design and implement the software based on a kind of USB User Gateway. With the software Skype user can freely communicate with PSTN phone. FSM is designed as the core of the software, and Skype control is separated by the USB Gateway control. In this way, the communication becomes more flexible and efficient. In the actual user testing, the software obtains good results.

A Genuine TEAM Player

NASA Technical Reports Server (NTRS)

2001-01-01

Qualtech Systems, Inc. developed a complete software system with capabilities of multisignal modeling, diagnostic analysis, run-time diagnostic operations, and intelligent interactive reasoners. Commercially available as the TEAMS (Testability Engineering and Maintenance System) tool set, the software can be used to reveal unanticipated system failures. The TEAMS software package is broken down into four companion tools: TEAMS-RT, TEAMATE, TEAMS-KB, and TEAMS-RDS. TEAMS-RT identifies good, bad, and suspect components in the system in real-time. It reports system health results from onboard tests, and detects and isolates failures within the system, allowing for rapid fault isolation. TEAMATE takes over from where TEAMS-RT left off by intelligently guiding the maintenance technician through the troubleshooting procedure, repair actions, and operational checkout. TEAMS-KB serves as a model management and collection tool. TEAMS-RDS (TEAMS-Remote Diagnostic Server) has the ability to continuously assess a system and isolate any failure in that system or its components, in real time. RDS incorporates TEAMS-RT, TEAMATE, and TEAMS-KB in a large-scale server architecture capable of providing advanced diagnostic and maintenance functions over a network, such as the Internet, with a web browser user interface.

Decentralized Formation Flying Control in a Multiple-Team Hierarchy

NASA Technical Reports Server (NTRS)

Mueller, Joseph .; Thomas, Stephanie J.

2005-01-01

This paper presents the prototype of a system that addresses these objectives-a decentralized guidance and control system that is distributed across spacecraft using a multiple-team framework. The objective is to divide large clusters into teams of manageable size, so that the communication and computational demands driven by N decentralized units are related to the number of satellites in a team rather than the entire cluster. The system is designed to provide a high-level of autonomy, to support clusters with large numbers of satellites, to enable the number of spacecraft in the cluster to change post-launch, and to provide for on-orbit software modification. The distributed guidance and control system will be implemented in an object-oriented style using MANTA (Messaging Architecture for Networking and Threaded Applications). In this architecture, tasks may be remotely added, removed or replaced post-launch to increase mission flexibility and robustness. This built-in adaptability will allow software modifications to be made on-orbit in a robust manner. The prototype system, which is implemented in MATLAB, emulates the object-oriented and message-passing features of the MANTA software. In this paper, the multiple-team organization of the cluster is described, and the modular software architecture is presented. The relative dynamics in eccentric reference orbits is reviewed, and families of periodic, relative trajectories are identified, expressed as sets of static geometric parameters. The guidance law design is presented, and an example reconfiguration scenario is used to illustrate the distributed process of assigning geometric goals to the cluster. Next, a decentralized maneuver planning approach is presented that utilizes linear-programming methods to enact reconfiguration and coarse formation keeping maneuvers. Finally, a method for performing online collision avoidance is discussed, and an example is provided to gauge its performance.

Implementation of a Surgical Safety Checklist: Impact on Surgical Team Perspectives

PubMed Central

Papaconstantinou, Harry T.; Jo, ChanHee; Reznik, Scott I.; Smythe, W. Roy; Wehbe-Janek, Hania

2013-01-01

Background The World Health Organization (WHO) surgical safety checklist has been shown to decrease mortality and complications and has been adopted worldwide. However, system flaws and human errors persist. Identifying provider perspectives of patient safety initiatives may identify strategies for improvement. The purpose of this study was to determine provider perspectives of surgical safety checklist implementation in an effort to improve initiatives that enhance surgical patients' safety. Methods In September 2010, a WHO-adapted surgical safety checklist was implemented at our institution. Surgical teams were invited to complete a checklist-focused questionnaire 1 month before and 1 year after implementation. Baseline and follow-up results were compared. Results A total of 437 surgical care providers responded to the survey: 45% of providers responded at baseline and 64% of providers responded at follow-up. Of the total respondents, 153 (35%) were nurses, 104 (24%) were anesthesia providers, and 180 (41%) were surgeons. Overall, we found an improvement in the awareness of patient safety and quality of care, with significant improvements in the perception of the value of and participation in the time-out process, in surgical team communication, and in the establishment and clarity of patient care needs. Some discordance was noted between surgeons and other surgical team members, indicating that barriers in communication still exist. Overall, approximately 65% of respondents perceived that the checklist improved patient safety and patient care; however, we found a strong negative perception of operating room efficiency. Conclusion Implementation of a surgical safety checklist improves perceptions of surgical safety. Barriers to implementation exist, but staff feedback may be used to enhance the sustainability and success of patient safety initiatives. PMID:24052757

Sandia National Laboratories Advanced Simulation and Computing (ASC) software quality plan. Part 1 : ASC software quality engineering practices version 1.0.

DOE Office of Scientific and Technical Information (OSTI.GOV)

Minana, Molly A.; Sturtevant, Judith E.; Heaphy, Robert

2005-01-01

The purpose of the Sandia National Laboratories (SNL) Advanced Simulation and Computing (ASC) Software Quality Plan is to clearly identify the practices that are the basis for continually improving the quality of ASC software products. Quality is defined in DOE/AL Quality Criteria (QC-1) as conformance to customer requirements and expectations. This quality plan defines the ASC program software quality practices and provides mappings of these practices to the SNL Corporate Process Requirements (CPR 1.3.2 and CPR 1.3.6) and the Department of Energy (DOE) document, ASCI Software Quality Engineering: Goals, Principles, and Guidelines (GP&G). This quality plan identifies ASC management andmore » software project teams' responsibilities for cost-effective software engineering quality practices. The SNL ASC Software Quality Plan establishes the signatories commitment to improving software products by applying cost-effective software engineering quality practices. This document explains the project teams opportunities for tailoring and implementing the practices; enumerates the practices that compose the development of SNL ASC's software products; and includes a sample assessment checklist that was developed based upon the practices in this document.« less

Combining Architecture-Centric Engineering with the Team Software Process

DTIC Science & Technology

2010-12-01

colleagues from Quarksoft and CIMAT have re- cently reported on their experiences in “Introducing Software Architecture Development Methods into a TSP...Postmortem Lessons, new goals, new requirements, new risk , etc. Business and technical goals Estimates, plans, process, commitment Work products...architecture to mitigate the risks unco- vered by the ATAM. At the end of the iteration, version 1.0 of the architec- ture is available. Implement a second

Top Down Implementation Plan for system performance test software

NASA Technical Reports Server (NTRS)

Jacobson, G. N.; Spinak, A.

1982-01-01

The top down implementation plan used for the development of system performance test software during the Mark IV-A era is described. The plan is based upon the identification of the hierarchical relationship of the individual elements of the software design, the development of a sequence of functionally oriented demonstrable steps, the allocation of subroutines to the specific step where they are first required, and objective status reporting. The results are: determination of milestones, improved managerial visibility, better project control, and a successful software development.

Team functioning as a predictor of patient outcomes in early medical home implementation.

PubMed

Wu, Frances M; Rubenstein, Lisa V; Yoon, Jean

New models of patient-centered primary care such as the patient-centered medical home (PCMH) depend on high levels of interdisciplinary primary care team functioning to achieve improved outcomes. A few studies have qualitatively assessed barriers and facilitators to optimal team functioning; however, we know of no prior study that assesses PCMH team functioning in relationship to patient health outcomes. The aim of the study was to assess the relationships between primary care team functioning, patients' use of acute care, and mortality. Retrospective longitudinal cohort analysis of patient outcomes measured at two time points (2012 and 2013) after PCMH implementation began in Veterans Health Administration practices. Multilevel models examined practice-level measures of team functioning in relationship to patient outcomes (all-cause and ambulatory care-sensitive condition-related hospitalizations, emergency department visits, and mortality). We controlled for practice-level factors likely to affect team functioning, including leadership support, provider and staff burnout, and staffing sufficiency, as well as for individual patient characteristics. We also tested the model among a subgroup of vulnerable patients (homeless, mentally ill, or with dementia). In adjusted analyses, higher team functioning was associated with lower mortality (OR = 0.92, p = .04) among all patients and with fewer all-cause admissions (incidence rate ratio [IRR] = 0.90, p < 0.01), ambulatory care-sensitive condition-related admissions (IRR = 0.91, p = .04), and emergency department visits (IRR = 0.91, p = .03) in the vulnerable patient subgroup. These early findings give support for the importance of team functioning within PCMH models for achieving improved patient outcomes. A focus on team functioning is important especially in the early implementation of team-based primary care models.

Considering Subcontractors in Distributed Scrum Teams

NASA Astrophysics Data System (ADS)

Rudzki, Jakub; Hammouda, Imed; Mikkola, Tuomas; Mustonen, Karri; Systä, Tarja

In this chapter we present our experiences with working with subcontractors in distributed Scrum teams. The context of our experiences is a medium size software service provider company. We present the way the subcontractors are selected and how Scrum practices can be used in real-life projects. We discuss team arrangements and tools used in distributed development teams highlighting aspects that are important when working with subcontractors. We also present an illustrative example where different phases of a project working with subcontractors are described. The example also provides practical tips on work in such projects. Finally, we present a summary of our data that was collected from Scrum and non-Scrum projects implemented over a few years. This chapter should provide a practical point of view on working with subcontractors in Scrum teams for those who are considering such cooperation.

High quality diabetes care: testing the effectiveness of strategies of regional implementation teams.

PubMed

Drach-Zahavy, Anat; Shadmi, Efrat; Freund, Anat; Goldfracht, Margalit

2009-01-01

The purpose of this article is to identify and test the effectiveness of work strategies employed by regional implementation teams to attain high quality care for diabetes patients. The study was conducted in a major health maintenance organization (HMO) that provides care for 70 per cent of Israel's diabetes patients. A sequential mixed model design, combining qualitative and quantitative methods was employed. In-depth interviews were conducted with members of six regional implementation teams, each responsible for the care of 25,000-34,000 diabetic patients. Content analysis of the interviews revealed that teams employed four key strategies: task-interdependence, goal-interdependence, reliance on top-down standardised processes and team-learning. These strategies were used to predict the mean percentage performance of eight evidence-based indicators of diabetes care: percentage of patients with HbA1c < 7 per cent, blood pressure < or = 130/80 and cholesterol < or = 100; and performance of: HbA1c tests, LDL cholesterol tests, blood pressure measurements, urine protein tests, and ophthalmic examinations. Teams were found to vary in their use of the four strategies. Mixed linear models analysis indicated that type of indicator (simple process, compound process, and outcome) and goal interdependence were significantly linked to team effectiveness. For simple-process indicators, reliance on top-down standardised processes led to team effectiveness, but for outcome measures this strategy was ineffective, and even counter-effective. For outcome measures, team-learning was more beneficial. The findings have implications for the management of chronic diseases. The advantage of allowing team members flexibility in the choice of the best work strategy to attain high quality diabetes care is attested.

A prospective analysis of implementation of multi-disciplinary team decisions in breast cancer.

PubMed

English, Rachel; Metcalfe, Chris; Day, James; Rayter, Zenon; Blazeby, Jane M

2012-09-01

Multi-disciplinary teams (MDTs) management of patients with cancer is mandatory in the United Kingdom, and auditing team decision-making by examining rates of decision implementation and reasons for nonimplementation may inform this practice. Consecutive breast cancer MDT decisions, subsequent decision implementation, and reasons for nonimplementation were prospectively recorded. Factors associated with nonimplementation of the MDT decision were analyzed with logistic regression. Of 289 consecutive MDT decisions involving 210 women, 20 (6.9%, 95% CIs 4.3%-10.5%) were not implemented. Most changed MDT decisions did so because of patient preferences (n = 13, 65%), with the discovery of new clinical information (n = 3) and individual doctor's views (n = 4) also leading to decision nonimplementation. MDT decisions were significantly less likely to be adhered to in patients with confirmed malignant disease compared to those with benign or 'unknown' disease categories (p < 0.001) and MDT decisions in older patients were significantly more likely not to be implemented than in younger patients (p = 0.002). Auditing nonimplementation of MDT recommendations and examining reasons for changed decisions is a useful process to monitor team performance and to identify factors that need more attention during the MDT meeting to ensure that the process makes optimal patient centered decisions. © 2012 Wiley Periodicals, Inc.

Effective organizational solutions for implementation of DBMS software packages

NASA Technical Reports Server (NTRS)

Jones, D.

1984-01-01

The space telescope management information system development effort is a guideline for discussing effective organizational solutions used in implementing DBMS software. Focus is on the importance of strategic planning. The value of constructing an information system architecture to conform to the organization's managerial needs, the need for a senior decision maker, dealing with shifting user requirements, and the establishment of a reliable working relationship with the DBMS vendor are examined. Requirements for a schedule to demonstrate progress against a defined timeline and the importance of continued monitoring for production software control, production data control, and software enhancements are also discussed.

Development and analysis of the Software Implemented Fault-Tolerance (SIFT) computer

NASA Technical Reports Server (NTRS)

Goldberg, J.; Kautz, W. H.; Melliar-Smith, P. M.; Green, M. W.; Levitt, K. N.; Schwartz, R. L.; Weinstock, C. B.

1984-01-01

SIFT (Software Implemented Fault Tolerance) is an experimental, fault-tolerant computer system designed to meet the extreme reliability requirements for safety-critical functions in advanced aircraft. Errors are masked by performing a majority voting operation over the results of identical computations, and faulty processors are removed from service by reassigning computations to the nonfaulty processors. This scheme has been implemented in a special architecture using a set of standard Bendix BDX930 processors, augmented by a special asynchronous-broadcast communication interface that provides direct, processor to processor communication among all processors. Fault isolation is accomplished in hardware; all other fault-tolerance functions, together with scheduling and synchronization are implemented exclusively by executive system software. The system reliability is predicted by a Markov model. Mathematical consistency of the system software with respect to the reliability model has been partially verified, using recently developed tools for machine-aided proof of program correctness.

Software Users Manual (SUM): Extended Testability Analysis (ETA) Tool

NASA Technical Reports Server (NTRS)

Maul, William A.; Fulton, Christopher E.

2011-01-01

This software user manual describes the implementation and use the Extended Testability Analysis (ETA) Tool. The ETA Tool is a software program that augments the analysis and reporting capabilities of a commercial-off-the-shelf (COTS) testability analysis software package called the Testability Engineering And Maintenance System (TEAMS) Designer. An initial diagnostic assessment is performed by the TEAMS Designer software using a qualitative, directed-graph model of the system being analyzed. The ETA Tool utilizes system design information captured within the diagnostic model and testability analysis output from the TEAMS Designer software to create a series of six reports for various system engineering needs. The ETA Tool allows the user to perform additional studies on the testability analysis results by determining the detection sensitivity to the loss of certain sensors or tests. The ETA Tool was developed to support design and development of the NASA Ares I Crew Launch Vehicle. The diagnostic analysis provided by the ETA Tool was proven to be valuable system engineering output that provided consistency in the verification of system engineering requirements. This software user manual provides a description of each output report generated by the ETA Tool. The manual also describes the example diagnostic model and supporting documentation - also provided with the ETA Tool software release package - that were used to generate the reports presented in the manual

Deliberation Makes a Difference: Preparation Strategies for TeamSTEPPS Implementation in Small and Rural Hospitals

PubMed Central

Zhu, Xi; Baloh, Jure; Ward, Marcia M.; Stewart, Greg L.

2016-01-01

Small and rural hospitals face special challenges to implement and sustain organization-wide quality improvement (QI) initiatives due to limited resources and infrastructures. We studied the implementation of TeamSTEPPS, a national QI initiative, in 14 critical access hospitals. Drawing on QI and organization development theories, we propose five strategic preparation steps for TeamSTEPPS: assess needs, reflect on the context, set goals, develop a shared understanding, and select change agents. We explore how hospitals’ practices correspond to suggested best practices by analyzing qualitative data collected through quarterly interviews with key informants. We find that the level of deliberation was a key factor that differentiated hospitals’ practices. Hospitals that were more deliberate in preparing for the five strategic steps were more likely to experience engagement, perceive efficacy, foresee and manage barriers, and achieve progress during implementation. We discuss potential steps that hospitals may take to better prepare for TeamSTEPPS implementation. PMID:26429835

TEAMS Model Analyzer

NASA Technical Reports Server (NTRS)

Tijidjian, Raffi P.

2010-01-01

The TEAMS model analyzer is a supporting tool developed to work with models created with TEAMS (Testability, Engineering, and Maintenance System), which was developed by QSI. In an effort to reduce the time spent in the manual process that each TEAMS modeler must perform in the preparation of reporting for model reviews, a new tool has been developed as an aid to models developed in TEAMS. The software allows for the viewing, reporting, and checking of TEAMS models that are checked into the TEAMS model database. The software allows the user to selectively model in a hierarchical tree outline view that displays the components, failure modes, and ports. The reporting features allow the user to quickly gather statistics about the model, and generate an input/output report pertaining to all of the components. Rules can be automatically validated against the model, with a report generated containing resulting inconsistencies. In addition to reducing manual effort, this software also provides an automated process framework for the Verification and Validation (V&V) effort that will follow development of these models. The aid of such an automated tool would have a significant impact on the V&V process.

Implementing Team-Based Learning in Middle School Social Studies Classes

ERIC Educational Resources Information Center

Wanzek, Jeanne; Kent, Shawn C.; Vaughn, Sharon; Swanson, Elizabeth A.; Roberts, Greg; Haynes, Martha

2015-01-01

The authors examined the effects of team-based learning (TBL) implemented in Grade 8 social studies classes on student content acquisition. Twenty-four classes were randomly assigned to treatment or comparison blocking on teacher. In the treatment classes teachers integrated TBL practices in the content instruction. The authors examined teacher…

Implementing team huddles in small rural hospitals: How does the Kotter model of change apply?

PubMed

Baloh, Jure; Zhu, Xi; Ward, Marcia M

2017-12-17

To examine how the process of change prescribed in Kotter's change model applies in implementing team huddles, and to assess the impact of the execution of early change phases on change success in later phases. Kotter's model can help to guide hospital leaders to implement change and potentially to improve success rates. However, the model is under studied, particularly in health care. We followed eight hospitals implementing team huddles for 2 years, interviewing the change teams quarterly to inquire about implementation progress. We assessed how the hospitals performed in the three overarching phases of the Kotter model, and examined whether performance in the initial phase influenced subsequent performance. In half of the hospitals, change processes were congruent with Kotter's model, where performance in the initial phase influenced their success in subsequent phases. In other hospitals, change processes were incongruent with the model, and their success depended on implementation scope and the strategies employed. We found mixed support for the Kotter model. It better fits implementation that aims to spread to multiple hospital units. When the scope is limited, changes can be successful even when steps are skipped. Kotter's model can be a useful guide for nurse managers implementing changes. © 2017 John Wiley & Sons Ltd.

Reconfigurable Software for Controlling Formation Flying

NASA Technical Reports Server (NTRS)

Mueller, Joseph B.

2006-01-01

Software for a system to control the trajectories of multiple spacecraft flying in formation is being developed to reflect underlying concepts of (1) a decentralized approach to guidance and control and (2) reconfigurability of the control system, including reconfigurability of the software and of control laws. The software is organized as a modular network of software tasks. The computational load for both determining relative trajectories and planning maneuvers is shared equally among all spacecraft in a cluster. The flexibility and robustness of the software are apparent in the fact that tasks can be added, removed, or replaced during flight. In a computational simulation of a representative formation-flying scenario, it was demonstrated that the following are among the services performed by the software: Uploading of commands from a ground station and distribution of the commands among the spacecraft, Autonomous initiation and reconfiguration of formations, Autonomous formation of teams through negotiations among the spacecraft, Working out details of high-level commands (e.g., shapes and sizes of geometrically complex formations), Implementation of a distributed guidance law providing autonomous optimization and assignment of target states, and Implementation of a decentralized, fuel-optimal, impulsive control law for planning maneuvers.

A randomized wait-list controlled analysis of the implementation integrity of team-initiated problem solving processes.

PubMed

Newton, J Stephen; Horner, Robert H; Algozzine, Bob; Todd, Anne W; Algozzine, Kate

2012-08-01

Members of Positive Behavior Interventions and Supports (PBIS) teams from 34 elementary schools participated in a Team-Initiated Problem Solving (TIPS) Workshop and follow-up technical assistance. Within the context of a randomized wait-list controlled trial, team members who were the first recipients of the TIPS intervention demonstrated greater implementation integrity in using the problem-solving processes during their team meetings than did members of PBIS Teams in the Wait-List Control group. The success of TIPS at improving implementation integrity of the problem-solving processes is encouraging and suggests the value of conducting additional research focused on determining whether there is a functional relation between use of these problem-solving processes and actual resolution of targeted student academic and social problems. Copyright © 2012 Society for the Study of School Psychology. Published by Elsevier Ltd. All rights reserved.

SLS Flight Software Testing: Using a Modified Agile Software Testing Approach

NASA Technical Reports Server (NTRS)

Bolton, Albanie T.

2016-01-01

NASA's Space Launch System (SLS) is an advanced launch vehicle for a new era of exploration beyond earth's orbit (BEO). The world's most powerful rocket, SLS, will launch crews of up to four astronauts in the agency's Orion spacecraft on missions to explore multiple deep-space destinations. Boeing is developing the SLS core stage, including the avionics that will control vehicle during flight. The core stage will be built at NASA's Michoud Assembly Facility (MAF) in New Orleans, LA using state-of-the-art manufacturing equipment. At the same time, the rocket's avionics computer software is being developed here at Marshall Space Flight Center in Huntsville, AL. At Marshall, the Flight and Ground Software division provides comprehensive engineering expertise for development of flight and ground software. Within that division, the Software Systems Engineering Branch's test and verification (T&V) team uses an agile test approach in testing and verification of software. The agile software test method opens the door for regular short sprint release cycles. The idea or basic premise behind the concept of agile software development and testing is that it is iterative and developed incrementally. Agile testing has an iterative development methodology where requirements and solutions evolve through collaboration between cross-functional teams. With testing and development done incrementally, this allows for increased features and enhanced value for releases. This value can be seen throughout the T&V team processes that are documented in various work instructions within the branch. The T&V team produces procedural test results at a higher rate, resolves issues found in software with designers at an earlier stage versus at a later release, and team members gain increased knowledge of the system architecture by interfacing with designers. SLS Flight Software teams want to continue uncovering better ways of developing software in an efficient and project beneficial manner

An agile implementation of SCRUM

NASA Astrophysics Data System (ADS)

Gannon, Michele

Is Agile a way to cut corners? To some, the use of an Agile Software Development Methodology has a negative connotation - “ Oh, you're just not producing any documentation” . So can a team with no experience in Agile successfully implement and use SCRUM?

Circles of Care: Implementation and Evaluation of Support Teams for African Americans with Cancer

ERIC Educational Resources Information Center

Hanson, Laura C.; Green, Melissa A.; Hayes, Michelle; Diehl, Sandra J.; Warnock, Steven; Corbie-Smith, Giselle; Lin, Feng-Chang; Earp, Jo Anne

2014-01-01

Background: Community-based peer support may help meet the practical, emotional, and spiritual needs of African Americans with advanced cancer. Support teams are a unique model of peer support for persons facing serious illness, but research is rare. This study sought to (a) implement new volunteer support teams for African Americans with advanced…

Generalized Support Software: Domain Analysis and Implementation

NASA Technical Reports Server (NTRS)

Stark, Mike; Seidewitz, Ed

1995-01-01

For the past five years, the Flight Dynamics Division (FDD) at NASA's Goddard Space Flight Center has been carrying out a detailed domain analysis effort and is now beginning to implement Generalized Support Software (GSS) based on this analysis. GSS is part of the larger Flight Dynamics Distributed System (FDDS), and is designed to run under the FDDS User Interface / Executive (UIX). The FDD is transitioning from a mainframe based environment to systems running on engineering workstations. The GSS will be a library of highly reusable components that may be configured within the standard FDDS architecture to quickly produce low-cost satellite ground support systems. The estimates for the first release is that this library will contain approximately 200,000 lines of code. The main driver for developing generalized software is development cost and schedule improvement. The goal is to ultimately have at least 80 percent of all software required for a spacecraft mission (within the domain supported by the GSS) to be configured from the generalized components.

Maneuver Automation Software

NASA Technical Reports Server (NTRS)

Uffelman, Hal; Goodson, Troy; Pellegrin, Michael; Stavert, Lynn; Burk, Thomas; Beach, David; Signorelli, Joel; Jones, Jeremy; Hahn, Yungsun; Attiyah, Ahlam;

Multidisciplinary teams of case managers in the implementation of an innovative integrated services delivery for the elderly in France.

PubMed

de Stampa, Matthieu; Vedel, Isabelle; Trouvé, Hélène; Ankri, Joël; Saint Jean, Olivier; Somme, Dominique

2014-04-07

The case management process is now well defined, and teams of case managers have been implemented in integrated services delivery. However, little is known about the role played by the team of case managers and the value in having multidisciplinary case management teams. The objectives were to develop a fuller understanding of the role played by the case manager team and identify the value of inter-professional collaboration in multidisciplinary teams during the implementation of an innovative integrated service in France. We conducted a qualitative study with focus groups comprising 14 multidisciplinary teams for a total of 59 case managers, six months after their recruitment to the MAIA program (Maison Autonomie Integration Alzheimer). Most of the case managers saw themselves as being part of a team of case managers (91.5%). Case management teams help case managers develop a comprehensive understanding of the integration concept, meet the complex needs of elderly people and change their professional practices. Multidisciplinary case management teams add value by helping case managers move from theory to practice, by encouraging them develop a comprehensive clinical vision, and by initiating the interdisciplinary approach. The multidisciplinary team of case managers is central to the implementation of case management and helps case managers develop their new role and a core inter-professional competency.

Implementation of the AES as a Hash Function for Confirming the Identity of Software on a Computer System

DOE Office of Scientific and Technical Information (OSTI.GOV)

Hansen, Randy R.; Bass, Robert B.; Kouzes, Richard T.

2003-01-20

This paper provides a brief overview of the implementation of the Advanced Encryption Standard (AES) as a hash function for confirming the identity of software resident on a computer system. The PNNL Software Authentication team chose to use a hash function to confirm software identity on a system for situations where: (1) there is limited time to perform the confirmation and (2) access to the system is restricted to keyboard or thumbwheel input and output can only be displayed on a monitor. PNNL reviewed three popular algorithms: the Secure Hash Algorithm - 1 (SHA-1), the Message Digest - 5 (MD-5),more » and the Advanced Encryption Standard (AES) and selected the AES to incorporate in software confirmation tool we developed. This paper gives a brief overview of the SHA-1, MD-5, and the AES and sites references for further detail. It then explains the overall processing steps of the AES to reduce a large amount of generic data-the plain text, such is present in memory and other data storage media in a computer system, to a small amount of data-the hash digest, which is a mathematically unique representation or signature of the former that could be displayed on a computer's monitor. This paper starts with a simple definition and example to illustrate the use of a hash function. It concludes with a description of how the software confirmation tool uses the hash function to confirm the identity of software on a computer system.« less

Determinants of treatment plan implementation in multidisciplinary team meetings for patients with chronic diseases: a mixed-methods study

PubMed Central

Raine, Rosalind; Xanthopoulou, Penny; Wallace, Isla; Nic a’ Bháird, Caoimhe; Lanceley, Anne; Clarke, Alex; Livingston, Gill; Prentice, Archie; Ardron, Dave; Harris, Miriam; King, Michael; Michie, Susan; Blazeby, Jane M; Austin-Parsons, Natalie; Gibbs, Simon; Barber, Julie

2014-01-01

Objective Multidisciplinary team (MDT) meetings are assumed to produce better decisions and are extensively used to manage chronic disease in the National Health Service (NHS). However, evidence for their effectiveness is mixed. Our objective was to investigate determinants of MDT effectiveness by examining factors influencing the implementation of MDT treatment plans. This is a proxy measure of effectiveness, because it lies on the pathway to improvements in health, and reflects team decision making which has taken account of clinical and non-clinical information. Additionally, this measure can be compared across MDTs for different conditions. Methods We undertook a prospective mixed-methods study of 12 MDTs in London and North Thames. Data were collected by observation of 370 MDT meetings, interviews with 53 MDT members, and from 2654 patient medical records. We examined the influence of patient-related factors (disease, age, sex, deprivation, whether their preferences and other clinical/health behaviours were mentioned) and MDT features (as measured using the ‘Team Climate Inventory’ and skill mix) on the implementation of MDT treatment plans. Results The adjusted odds (or likelihood) of implementation was reduced by 25% for each additional professional group represented at the MDT meeting. Implementation was more likely in MDTs with clear goals and processes and a good ‘Team Climate’ (adjusted OR 1.96; 95% CI 1.15 to 3.31 for a unit increase in Team Climate Inventory (TCI) score). Implementation varied by disease category, with the lowest adjusted odds of implementation in mental health teams. Implementation was also lower for patients living in more deprived areas (adjusted odds of implementation for patients in the most compared with least deprived areas was 0.60, 95% CI 0.39 to 0.91). Conclusions Greater multidisciplinarity is not necessarily associated with more effective decision making. Explicit goals and procedures are also crucial. Decision

Implementation of consumer providers into mental health intensive case management teams.

PubMed

Hamilton, Alison B; Chinman, Matthew; Cohen, Amy N; Oberman, Rebecca Shoai; Young, Alexander S

2015-01-01

In mental health care, consumer providers (CPs) are individuals with serious mental illness (SMI) who draw upon their lived experiences while providing services to others with SMI. Implementation of CPs has proven to be challenging in a variety of settings. The PEER project (Peers Enhancing Recovery) involved rolling out CPs using an implementation science model and evaluating implementation and impact in mental health treatment settings (three intervention, three control). In qualitative interviews, facilitators and challenges to implementation were described by the CPs, their team members, clients, and study researchers. Site preparation, external facilitation, and positive, reinforcing experiences with CPs facilitated implementation. Role definitions and deficiencies in CPs' technical knowledge posed challenges to implementation. Sustainability was not realized due to insufficient resources. However, implementation was positive overall, characterized by diffusion of innovation concepts of high relative advantage, strong trialability, compatibility with prevailing norms, compelling observability, and relatively low complexity. By preparing and working systematically with intervention sites to incorporate new services, implementation was strengthened and challenges were minimized.

Implementation and Testing of VLBI Software Correlation at the USNO

NASA Technical Reports Server (NTRS)

Fey, Alan; Ojha, Roopesh; Boboltz, Dave; Geiger, Nicole; Kingham, Kerry; Hall, David; Gaume, Ralph; Johnston, Ken

2010-01-01

The Washington Correlator (WACO) at the U.S. Naval Observatory (USNO) is a dedicated VLBI processor based on dedicated hardware of ASIC design. The WACO is currently over 10 years old and is nearing the end of its expected lifetime. Plans for implementation and testing of software correlation at the USNO are currently being considered. The VLBI correlation process is, by its very nature, well suited to a parallelized computing environment. Commercial off-the-shelf computer hardware has advanced in processing power to the point where software correlation is now both economically and technologically feasible. The advantages of software correlation are manifold but include flexibility, scalability, and easy adaptability to changing environments and requirements. We discuss our experience with and plans for use of software correlation at USNO with emphasis on the use of the DiFX software correlator.

How to implement quality indicators successfully in palliative care services: perceptions of team members about facilitators of and barriers to implementation.

PubMed

Leemans, Kathleen; Van den Block, Lieve; Vander Stichele, Robert; Francke, Anneke L; Deliens, Luc; Cohen, Joachim

2015-12-01

There is an increasing demand for the use of quality indicators in palliative care. With previous research about implementation in this field lacking, we aimed to evaluate the barriers to and facilitators of implementation. Three focus group interviews were organized with 21 caregivers from 18 different specialized palliative care services in Belgium. Four had already worked with the indicators during a pilot study. The focus group discussions were transcribed verbatim and analyzed using the thematic framework approach. The caregivers anticipated that a positive attitude by the team towards quality improvement, the presence of a good leader, and the possible link between quality indicators and reimbursement might facilitate the implementation of quality indicators in specialized palliative care services. Other facilitators concerned the presence of a need to demonstrate quality of care, to perform improvement actions, and to learn from other caregivers and services in the field. A negative attitude by caregivers towards quality measurement and a lack of skills, time, and staff were mentioned as barriers to successful implementation. Palliative caregivers anticipate a number of opportunities and problems when implementing quality indicators. These relate to the attitudes of the team regarding quality measurement; the attitudes, knowledge, and skills of the individual caregivers within the team; and the organizational context and the economic and political context. Training in the advantages of quality indicators and how to use them is indispensable, as are structural changes in the policy concerning palliative care, in order to progress towards systematic quality monitoring.

First experiences with the implementation of the European standard EN 62304 on medical device software for the quality assurance of a radiotherapy unit

PubMed Central

2014-01-01

Background According to the latest amendment of the Medical Device Directive standalone software qualifies as a medical device when intended by the manufacturer to be used for medical purposes. In this context, the EN 62304 standard is applicable which defines the life-cycle requirements for the development and maintenance of medical device software. A pilot project was launched to acquire skills in implementing this standard in a hospital-based environment (in-house manufacture). Methods The EN 62304 standard outlines minimum requirements for each stage of the software life-cycle, defines the activities and tasks to be performed and scales documentation and testing according to its criticality. The required processes were established for the pre-existent decision-support software FlashDumpComparator (FDC) used during the quality assurance of treatment-relevant beam parameters. As the EN 62304 standard implicates compliance with the EN ISO 14971 standard on the application of risk management to medical devices, a risk analysis was carried out to identify potential hazards and reduce the associated risks to acceptable levels. Results The EN 62304 standard is difficult to implement without proper tools, thus open-source software was selected and integrated into a dedicated development platform. The control measures yielded by the risk analysis were independently implemented and verified, and a script-based test automation was retrofitted to reduce the associated test effort. After all documents facilitating the traceability of the specified requirements to the corresponding tests and of the control measures to the proof of execution were generated, the FDC was released as an accessory to the HIT facility. Conclusions The implementation of the EN 62304 standard was time-consuming, and a learning curve had to be overcome during the first iterations of the associated processes, but many process descriptions and all software tools can be re-utilized in follow-up projects

First experiences with the implementation of the European standard EN 62304 on medical device software for the quality assurance of a radiotherapy unit.

PubMed

Höss, Angelika; Lampe, Christian; Panse, Ralf; Ackermann, Benjamin; Naumann, Jakob; Jäkel, Oliver

2014-03-21

According to the latest amendment of the Medical Device Directive standalone software qualifies as a medical device when intended by the manufacturer to be used for medical purposes. In this context, the EN 62304 standard is applicable which defines the life-cycle requirements for the development and maintenance of medical device software. A pilot project was launched to acquire skills in implementing this standard in a hospital-based environment (in-house manufacture). The EN 62304 standard outlines minimum requirements for each stage of the software life-cycle, defines the activities and tasks to be performed and scales documentation and testing according to its criticality. The required processes were established for the pre-existent decision-support software FlashDumpComparator (FDC) used during the quality assurance of treatment-relevant beam parameters. As the EN 62304 standard implicates compliance with the EN ISO 14971 standard on the application of risk management to medical devices, a risk analysis was carried out to identify potential hazards and reduce the associated risks to acceptable levels. The EN 62304 standard is difficult to implement without proper tools, thus open-source software was selected and integrated into a dedicated development platform. The control measures yielded by the risk analysis were independently implemented and verified, and a script-based test automation was retrofitted to reduce the associated test effort. After all documents facilitating the traceability of the specified requirements to the corresponding tests and of the control measures to the proof of execution were generated, the FDC was released as an accessory to the HIT facility. The implementation of the EN 62304 standard was time-consuming, and a learning curve had to be overcome during the first iterations of the associated processes, but many process descriptions and all software tools can be re-utilized in follow-up projects. It has been demonstrated that a

Software design and implementation concepts for an interoperable medical communication framework.

PubMed

Besting, Andreas; Bürger, Sebastian; Kasparick, Martin; Strathen, Benjamin; Portheine, Frank

2018-02-23

The new IEEE 11073 service-oriented device connectivity (SDC) standard proposals for networked point-of-care and surgical devices constitutes the basis for improved interoperability due to its independence of vendors. To accelerate the distribution of the standard a reference implementation is indispensable. However, the implementation of such a framework has to overcome several non-trivial challenges. First, the high level of complexity of the underlying standard must be reflected in the software design. An efficient implementation has to consider the limited resources of the underlying hardware. Moreover, the frameworks purpose of realizing a distributed system demands a high degree of reliability of the framework itself and its internal mechanisms. Additionally, a framework must provide an easy-to-use and fail-safe application programming interface (API). In this work, we address these challenges by discussing suitable software engineering principles and practical coding guidelines. A descriptive model is developed that identifies key strategies. General feasibility is shown by outlining environments in which our implementation has been utilized.

NA-42 TI Shared Software Component Library FY2011 Final Report

DOE Office of Scientific and Technical Information (OSTI.GOV)

Knudson, Christa K.; Rutz, Frederick C.; Dorow, Kevin E.

The NA-42 TI program initiated an effort in FY2010 to standardize its software development efforts with the long term goal of migrating toward a software management approach that will allow for the sharing and reuse of code developed within the TI program, improve integration, ensure a level of software documentation, and reduce development costs. The Pacific Northwest National Laboratory (PNNL) has been tasked with two activities that support this mission. PNNL has been tasked with the identification, selection, and implementation of a Shared Software Component Library. The intent of the library is to provide a common repository that is accessiblemore » by all authorized NA-42 software development teams. The repository facilitates software reuse through a searchable and easy to use web based interface. As software is submitted to the repository, the component registration process captures meta-data and provides version control for compiled libraries, documentation, and source code. This meta-data is then available for retrieval and review as part of library search results. In FY2010, PNNL and staff from the Remote Sensing Laboratory (RSL) teamed up to develop a software application with the goal of replacing the aging Aerial Measuring System (AMS). The application under development includes an Advanced Visualization and Integration of Data (AVID) framework and associated AMS modules. Throughout development, PNNL and RSL have utilized a common AMS code repository for collaborative code development. The AMS repository is hosted by PNNL, is restricted to the project development team, is accessed via two different geographic locations and continues to be used. The knowledge gained from the collaboration and hosting of this repository in conjunction with PNNL software development and systems engineering capabilities were used in the selection of a package to be used in the implementation of the software component library on behalf of NA-42 TI. The second task managed

Implementing healthy lifestyle promotion in primary care: a quasi-experimental cross-sectional study evaluating a team initiative.

PubMed

Thomas, Kristin; Krevers, Barbro; Bendtsen, Preben

2015-01-22

Non-communicable diseases are a leading cause of death and can largely be prevented by healthy lifestyles. Health care organizations are encouraged to integrate healthy lifestyle promotion in routine care. This study evaluates the impact of a team initiative on healthy lifestyle promotion in primary care. A quasi-experimental, cross-sectional design compared three intervention centres that had implemented lifestyle teams with three control centres that used a traditional model of care. Outcomes were defined using the RE-AIM framework: reach, the proportion of patients receiving lifestyle promotion; effectiveness, self-reported attitudes and competency among staff; adoption, proportion of staff reporting regular practice of lifestyle promotion; implementation, fidelity to the original lifestyle team protocol. Data collection methods included a patient questionnaire (n = 888), a staff questionnaire (n = 120) and structured interviews with all practice managers and, where applicable, team managers (n = 8). The chi square test and problem-driven content analysis was used to analyse the questionnaire and interview data, respectively. Reach: patients at control centres (48%, n = 211) received lifestyle promotion significantly more often compared with patients at intervention centres (41%, n = 169). Effectiveness: intervention staff was significantly more positive towards the effectiveness of lifestyle promotion, shared competency and how lifestyle promotion was prioritized at their centre. Adoption: 47% of staff at intervention centres and 58% at control centres reported that they asked patients about their lifestyle on a daily basis. all intervention centres had implemented multi-professional teams and team managers and held regular meetings but struggled to implement in-house referral structures for lifestyle promotion, which was used consistently among staff. Intervention centres did not show higher rates than control centres on reach of patients

Software Program: Software Management Guidebook

NASA Technical Reports Server (NTRS)

1996-01-01

The purpose of this NASA Software Management Guidebook is twofold. First, this document defines the core products and activities required of NASA software projects. It defines life-cycle models and activity-related methods but acknowledges that no single life-cycle model is appropriate for all NASA software projects. It also acknowledges that the appropriate method for accomplishing a required activity depends on characteristics of the software project. Second, this guidebook provides specific guidance to software project managers and team leaders in selecting appropriate life cycles and methods to develop a tailored plan for a software engineering project.

Introduction to the Navigation Team: Johnson Space Center EG6 Internship

NASA Technical Reports Server (NTRS)

Gualdoni, Matthew

2017-01-01

The EG6 navigation team at NASA Johnson Space Center, like any team of engineers, interacts with the engineering process from beginning to end; from exploring solutions to a problem, to prototyping and studying the implementations, all the way to polishing and verifying a final flight-ready design. This summer, I was privileged enough to gain exposure to each of these processes, while also getting to truly experience working within a team of engineers. My summer can be broken up into three projects: i) Initial study and prototyping: investigating a manual navigation method that can be utilized onboard Orion in the event of catastrophic failure of navigation systems; ii) Finalizing and verifying code: altering a software routine to improve its robustness and reliability, as well as designing unit tests to verify its performance; and iii) Development of testing equipment: assisting in developing and integrating of a high-fidelity testbed to verify the performance of software and hardware.

Implementation and consistency of Heart Team decision-making in complex coronary revascularisation.

PubMed

Pavlidis, Antonis N; Perera, Divaka; Karamasis, Grigoris V; Bapat, Vinayak; Young, Chris; Clapp, Brian R; Blauth, Chris; Roxburgh, James; Thomas, Martyn R; Redwood, Simon R

2016-03-01

A multidisciplinary team (MDT) approach for decision-making in patients with complex coronary artery disease (CAD) is now a class IC recommendation in the European and American guidelines for myocardial revascularisation. The aim of this study was to evaluate the implementation and consistency of Heart Team HT decision-making in complex coronary revascularisation. We prospectively evaluated the data of 399 patients derived from 51 consecutive MDT meetings held in a tertiary cardiac centre. A subset of cases was randomly selected and re-presented with the same clinical data to a panel blinded to the initial outcome, at least 6 months after the initial discussion, in order to evaluate the reproducibility of decision-making. The most common decisions included continued medical management (30%), coronary artery bypass grafting (CABG) (26%) and percutaneous coronary intervention (PCI) (17%). Other decisions, such as further assessment of symptoms or evaluation with further invasive or non-invasive tests were made in 25% of the cases. Decisions were implemented in 93% of the cases. On re-discussion of the same data (n=40) within a median period of 9 months 80% of the initial HT recommendations were successfully reproduced. The Heart Team is a robust process in the management of patient with complex CAD and decisions are largely reproducible. Although outcomes are successfully implemented in the majority of the cases, it is important that all clinical information is available during discussion and patient preference is taken into account. Copyright © 2016 Elsevier Ireland Ltd. All rights reserved.

Software development to implement the TxDOT culvert rating guide.

DOT National Transportation Integrated Search

2013-05-01

This implementation project created CULVLR: Culvert Load Rating, Version 1.0.0, a Windows-based : desktop application software package that automates the process by which Texas Department of Transportation : (TxDOT) engineers and their consultants ...

TMT approach to observatory software development process

NASA Astrophysics Data System (ADS)

Buur, Hanne; Subramaniam, Annapurni; Gillies, Kim; Dumas, Christophe; Bhatia, Ravinder

2016-07-01

The purpose of the Observatory Software System (OSW) is to integrate all software and hardware components of the Thirty Meter Telescope (TMT) to enable observations and data capture; thus it is a complex software system that is defined by four principal software subsystems: Common Software (CSW), Executive Software (ESW), Data Management System (DMS) and Science Operations Support System (SOSS), all of which have interdependencies with the observatory control systems and data acquisition systems. Therefore, the software development process and plan must consider dependencies to other subsystems, manage architecture, interfaces and design, manage software scope and complexity, and standardize and optimize use of resources and tools. Additionally, the TMT Observatory Software will largely be developed in India through TMT's workshare relationship with the India TMT Coordination Centre (ITCC) and use of Indian software industry vendors, which adds complexity and challenges to the software development process, communication and coordination of activities and priorities as well as measuring performance and managing quality and risk. The software project management challenge for the TMT OSW is thus a multi-faceted technical, managerial, communications and interpersonal relations challenge. The approach TMT is using to manage this multifaceted challenge is a combination of establishing an effective geographically distributed software team (Integrated Product Team) with strong project management and technical leadership provided by the TMT Project Office (PO) and the ITCC partner to manage plans, process, performance, risk and quality, and to facilitate effective communications; establishing an effective cross-functional software management team composed of stakeholders, OSW leadership and ITCC leadership to manage dependencies and software release plans, technical complexities and change to approved interfaces, architecture, design and tool set, and to facilitate

Implementing a Trauma-Informed Model of Care in a Community Acute Mental Health Team.

PubMed

Moloney, Bill; Cameron, Ian; Baker, Ashley; Feeney, Johanna; Korner, Anthony; Kornhaber, Rachel; Cleary, Michelle; McLean, Loyola

2018-04-12

In this paper, we demonstrate the value of implementing a Trauma-Informed Model of Care in a Community Acute Mental Health Team by providing brief intensive treatment (comprising risk interventions, brief counselling, collaborative formulation and pharmacological treatment). The team utilised the Conversational Model (CM), a psychotherapeutic approach for complex trauma. Key features of the CM are described in this paper using a clinical case study. The addition of the Conversational Model approach to practice has enabled better understandings of consumers' capacities and ways to then engage, converse, and intervene. The implementation of this intervention has led to a greater sense of self-efficacy amongst clinicians, who can now articulate a clear counselling model of care.

Performance of Student Software Development Teams: The Influence of Personality and Identifying as Team Members

ERIC Educational Resources Information Center

Monaghan, Conal; Bizumic, Boris; Reynolds, Katherine; Smithson, Michael; Johns-Boast, Lynette; van Rooy, Dirk

2015-01-01

One prominent approach in the exploration of the variations in project team performance has been to study two components of the aggregate personalities of the team members: conscientiousness and agreeableness. A second line of research, known as self-categorisation theory, argues that identifying as team members and the team's performance norms…

The development and implementation of a Hospital Emergency Response Team (HERT) for out-of-hospital surgical care.

PubMed

Scott, Christopher; Putnam, Brant; Bricker, Scott; Schneider, Laura; Raby, Stephanie; Koenig, William; Gausche-Hill, Marianne

2012-06-01

Over the past two decades, Los Angeles County has implemented a Hospital Emergency Response Team (HERT) to provide on-scene, advanced surgical care of injured patients as an element of the local Emergency Medical Services (EMS) system. Since 2008, the primary responsibility of the team has been to perform surgical procedures in the austere field setting when prolonged extrication is anticipated. Following the maxim of "life over limb," the team is equipped to provide rapid amputation of an entrapped extremity as well as other procedures and medical care, such as anxiolytics and advanced pain control. This report describes the development and implementation of a local EMS system HERT.

Software engineering and Ada (Trademark) training: An implementation model for NASA

NASA Technical Reports Server (NTRS)

Legrand, Sue; Freedman, Glenn

1988-01-01

The choice of Ada for software engineering for projects such as the Space Station has resulted in government and industrial groups considering training programs that help workers become familiar with both a software culture and the intricacies of a new computer language. The questions of how much time it takes to learn software engineering with Ada, how much an organization should invest in such training, and how the training should be structured are considered. Software engineering is an emerging, dynamic discipline. It is defined by the author as the establishment and application of sound engineering environments, tools, methods, models, principles, and concepts combined with appropriate standards, guidelines, and practices to support computing which is correct, modifiable, reliable and safe, efficient, and understandable throughout the life cycle of the application. Neither the training programs needed, nor the content of such programs, have been well established. This study addresses the requirements for training for NASA personnel and recommends an implementation plan. A curriculum and a means of delivery are recommended. It is further suggested that a knowledgeable programmer may be able to learn Ada in 5 days, but that it takes 6 to 9 months to evolve into a software engineer who uses the language correctly and effectively. The curriculum and implementation plan can be adapted for each NASA Center according to the needs dictated by each project.

OUTCOME OF IMPLEMENTATION OF A MULTIDISCIPLINARY TEAM APPROACH TO THE CARE OF PATIENTS AFTER TRANSSPHENOIDAL SURGERY.

PubMed

Carminucci, Arthur S; Ausiello, John C; Page-Wilson, Gabrielle; Lee, Michelle; Good, Laura; Bruce, Jeffrey N; Freda, Pamela U

2016-01-01

Transsphenoidal surgery (TS) for sellar lesions is an established and safe procedure, but complications can occur, particularly involving the neuroendocrine system. We hypothesized that postoperative care of TS patients would be optimized when performed by a coordinated team including a pituitary neurosurgeon, endocrinologists, and a specialty nurse. We implemented a formalized, multidisciplinary team approach and standardized postoperative protocols for the care of adult patients undergoing TS by a single surgeon (J.N.B.) at our institution beginning in July 2009. We retrospectively compared the outcomes of 214 consecutive TS-treated cases: 113 cases prior to and 101 following the initiation of the team approach and protocol implementation. Outcomes assessed included the incidence of neurosurgical and endocrine complications, length of stay (LOS), and rates of hospital readmission and unscheduled clinical visits. The median LOS decreased from 3 days preteam to 2 days postteam (P<.01). Discharge occurred on postoperative day 2 in 46% of the preteam group patients compared to 69% of the postteam group (P<.01). Rates of early postoperative diabetes insipidus (DI) and readmissions within 30 days for syndrome of inappropriate antidiuretic hormone (SIADH) or other complications did not differ between groups. Implementation of a multidisciplinary team approach was associated with a reduction of LOS. Despite earlier discharge, postoperative outcomes were not compromised. The endocrinologist is central to the success of this team approach, which could be successfully applied to care of patients undergoing TS, as well as other types of endocrine surgery at other centers.

A Comparison of Authoring Software for Developing Mathematics Self-Learning Software Packages.

ERIC Educational Resources Information Center

Suen, Che-yin; Pok, Yang-ming

Four years ago, the authors started to develop a self-paced mathematics learning software called NPMaths by using an authoring package called Tencore. However, NPMaths had some weak points. A development team was hence formed to develop similar software called Mathematics On Line. This time the team used another development language called…

Ada Implementation Guide. Software Engineering With Ada. Volume 1

DTIC Science & Technology

1994-04-01

Staff, Department ofDefense Dictionary of Military and Associated Terms, Washington, D.C., 1989. STARS McDonal , C., and S . Redwine, *STARS Glossary: A...ADýA28 357> offj I Volume I I SI I t Ada Implementation II Guide 5 Software Engineering With AdaI I S DTIC QUALITY INSPECTED S 5 April 1994 g " 94...and Abbreviations ...................... I I N p a S I I I i I Libt of F4g u OW Tahl Figures 2-1 DON Directives and Instructions for Implementing Public

Extra-team connections for knowledge transfer between staff teams

PubMed Central

Ramanadhan, Shoba; Wiecha, Jean L.; Emmons, Karen M.; Gortmaker, Steven L.; Viswanath, Kasisomayajula

2009-01-01

As organizations implement novel health promotion programs across multiple sites, they face great challenges related to knowledge management. Staff social networks may be a useful medium for transferring program-related knowledge in multi-site implementation efforts. To study this potential, we focused on the role of extra-team connections (ties between staff members based in different site teams) as potential channels for knowledge sharing. Data come from a cross-sectional study of afterschool childcare staff implementing a health promotion program at 20 urban sites of the Young Men's Christian Association of Greater Boston. We conducted a sociometric social network analysis and attempted a census of 91 program staff members. We surveyed 80 individuals, and included 73 coordinators and general staff, who lead and support implementation, respectively, in this study. A multiple linear regression model demonstrated a positive relationship between extra-team connections (β = 3.41, P < 0.0001) and skill receipt, a measure of knowledge transfer. We also found that intra-team connections (within-team ties between staff members) were also positively related to skill receipt. Connections between teams appear to support knowledge transfer in this network, but likely require greater active facilitation, perhaps via organizational changes. Further research on extra-team connections and knowledge transfer in low-resource, high turnover environments is needed. PMID:19528313

Continuous Energy Photon Transport Implementation in MCATK

DOE Office of Scientific and Technical Information (OSTI.GOV)

Adams, Terry R.; Trahan, Travis John; Sweezy, Jeremy Ed

2016-10-31

The Monte Carlo Application ToolKit (MCATK) code development team has implemented Monte Carlo photon transport into the MCATK software suite. The current particle transport capabilities in MCATK, which process the tracking and collision physics, have been extended to enable tracking of photons using the same continuous energy approximation. We describe the four photoatomic processes implemented, which are coherent scattering, incoherent scattering, pair-production, and photoelectric absorption. The accompanying background, implementation, and verification of these processes will be presented.

Implementing a modeling software for animated protein-complex interactions using a physics simulation library.

PubMed

Ueno, Yutaka; Ito, Shuntaro; Konagaya, Akihiko

2014-12-01

To better understand the behaviors and structural dynamics of proteins within a cell, novel software tools are being developed that can create molecular animations based on the findings of structural biology. This study proposes our method developed based on our prototypes to detect collisions and examine the soft-body dynamics of molecular models. The code was implemented with a software development toolkit for rigid-body dynamics simulation and a three-dimensional graphics library. The essential functions of the target software system included the basic molecular modeling environment, collision detection in the molecular models, and physical simulations of the movement of the model. Taking advantage of recent software technologies such as physics simulation modules and interpreted scripting language, the functions required for accurate and meaningful molecular animation were implemented efficiently.

Putting the "Team" in the Fine Arts Team: An Application of Business Management Team Concepts

ERIC Educational Resources Information Center

Fisher, Ryan

2007-01-01

In this article, the author discusses current challenges to the idea of teamwork in fine arts teams, redefines the terms team and collaboration using a business management perspective, discusses the success of effective teams in the business world and the characteristics of those teams, and proposes the implementation of the business model of…

A Matrix Approach to Software Process Definition

NASA Technical Reports Server (NTRS)

Schultz, David; Bachman, Judith; Landis, Linda; Stark, Mike; Godfrey, Sally; Morisio, Maurizio; Powers, Edward I. (Technical Monitor)

2000-01-01

The Software Engineering Laboratory (SEL) is currently engaged in a Methodology and Metrics program for the Information Systems Center (ISC) at Goddard Space Flight Center (GSFC). This paper addresses the Methodology portion of the program. The purpose of the Methodology effort is to assist a software team lead in selecting and tailoring a software development or maintenance process for a specific GSFC project. It is intended that this process will also be compliant with both ISO 9001 and the Software Engineering Institute's Capability Maturity Model (CMM). Under the Methodology program, we have defined four standard ISO-compliant software processes for the ISC, and three tailoring criteria that team leads can use to categorize their projects. The team lead would select a process and appropriate tailoring factors, from which a software process tailored to the specific project could be generated. Our objective in the Methodology program is to present software process information in a structured fashion, to make it easy for a team lead to characterize the type of software engineering to be performed, and to apply tailoring parameters to search for an appropriate software process description. This will enable the team lead to follow a proven, effective software process and also satisfy NASA's requirement for compliance with ISO 9001 and the anticipated requirement for CMM assessment. This work is also intended to support the deployment of sound software processes across the ISC.

Workflow-Based Software Development Environment

NASA Technical Reports Server (NTRS)

Izygon, Michel E.

2013-01-01

The Software Developer's Assistant (SDA) helps software teams more efficiently and accurately conduct or execute software processes associated with NASA mission-critical software. SDA is a process enactment platform that guides software teams through project-specific standards, processes, and procedures. Software projects are decomposed into all of their required process steps or tasks, and each task is assigned to project personnel. SDA orchestrates the performance of work required to complete all process tasks in the correct sequence. The software then notifies team members when they may begin work on their assigned tasks and provides the tools, instructions, reference materials, and supportive artifacts that allow users to compliantly perform the work. A combination of technology components captures and enacts any software process use to support the software lifecycle. It creates an adaptive workflow environment that can be modified as needed. SDA achieves software process automation through a Business Process Management (BPM) approach to managing the software lifecycle for mission-critical projects. It contains five main parts: TieFlow (workflow engine), Business Rules (rules to alter process flow), Common Repository (storage for project artifacts, versions, history, schedules, etc.), SOA (interface to allow internal, GFE, or COTS tools integration), and the Web Portal Interface (collaborative web environment

Decentralized formation flying control in a multiple-team hierarchy.

PubMed

Mueller, Joseph B; Thomas, Stephanie J

2005-12-01

In recent years, formation flying has been recognized as an enabling technology for a variety of mission concepts in both the scientific and defense arenas. Examples of developing missions at NASA include magnetospheric multiscale (MMS), solar imaging radio array (SIRA), and terrestrial planet finder (TPF). For each of these missions, a multiple satellite approach is required in order to accomplish the large-scale geometries imposed by the science objectives. In addition, the paradigm shift of using a multiple satellite cluster rather than a large, monolithic spacecraft has also been motivated by the expected benefits of increased robustness, greater flexibility, and reduced cost. However, the operational costs of monitoring and commanding a fleet of close-orbiting satellites is likely to be unreasonable unless the onboard software is sufficiently autonomous, robust, and scalable to large clusters. This paper presents the prototype of a system that addresses these objectives-a decentralized guidance and control system that is distributed across spacecraft using a multiple team framework. The objective is to divide large clusters into teams of "manageable" size, so that the communication and computation demands driven by N decentralized units are related to the number of satellites in a team rather than the entire cluster. The system is designed to provide a high level of autonomy, to support clusters with large numbers of satellites, to enable the number of spacecraft in the cluster to change post-launch, and to provide for on-orbit software modification. The distributed guidance and control system will be implemented in an object-oriented style using a messaging architecture for networking and threaded applications (MANTA). In this architecture, tasks may be remotely added, removed, or replaced post launch to increase mission flexibility and robustness. This built-in adaptability will allow software modifications to be made on-orbit in a robust manner. The

Investigating Team Cohesion in COCOMO II.2000

ERIC Educational Resources Information Center

Snowdeal-Carden, Betty A.

2013-01-01

Software engineering is team oriented and intensely complex, relying on human collaboration and creativity more than any other engineering discipline. Poor software estimation is a problem that within the United States costs over a billion dollars per year. Effective measurement of team cohesion is foundationally important to gain accurate…

Enhanced clarity and holism: the outcome of implementing the ICF with an acute stroke multidisciplinary team in England.

PubMed

Tempest, Stephanie; Harries, Priscilla; Kilbride, Cherry; De Souza, Lorraine

2013-01-01

Although it is recommended that the ICF (International Classification of Functioning, Disability and Health) should be implemented to aid communication within multidisciplinary stroke services, there is no empirical evidence to demonstrate the outcomes of such implementation. Working with one stroke service, this project aimed to address this gap and sought to evaluate the outcomes of implementing an ICF-based clinical tool into practice. Using an action research framework with mixed methods, data were collected from individual interviews, a focus group, questionnaires, email communications, minutes from relevant meetings and field notes. Thematic analysis was undertaken, using immersion and crystallisation, to define overall themes. Descriptive statistics were used to analyse quantitative data. Data from both sources were combined to create key findings. Three findings were determined from the data analysis. The ICF (1) fosters communication within and beyond the multidisciplinary stroke team; (2) promotes holistic thinking; and (3) helps to clarify team roles. The ICF enhanced clarity of communication and team roles within the acute stroke multidisciplinary team as well as with other clinicians, patients and their relatives. In addition, the ICF challenged stroke clinicians to think holistically, thereby appropriately extending their domain of concern beyond their traditional remit. The ICF is a globally accepted framework to describe functioning and is in use in a variety of clinical settings. Yet, the outcomes of using it in clinical practice have yet to be fully explored. This study found that the ICF enhanced clarity of communication and team roles within an acute stroke multidisciplinary team and to others beyond the team, including clinicians, patients and their relatives. Using the ICF also challenged clinicians to think holistically about patient needs following a stroke.

GFAST Software Demonstration

NASA Image and Video Library

2017-03-17

NASA engineers and test directors gather in Firing Room 3 in the Launch Control Center at NASA's Kennedy Space Center in Florida, to watch a demonstration of the automated command and control software for the agency's Space Launch System (SLS) and Orion spacecraft. The software is called the Ground Launch Sequencer. It will be responsible for nearly all of the launch commit criteria during the final phases of launch countdowns. The Ground and Flight Application Software Team (GFAST) demonstrated the software. It was developed by the Command, Control and Communications team in the Ground Systems Development and Operations (GSDO) Program. GSDO is helping to prepare the center for the first test flight of Orion atop the SLS on Exploration Mission 1.

Effects of implementation of a team model on physician and staff perceptions of a clinic's organizational and learning environments.

PubMed

Roth, Linda M; Markova, Tsveti; Monsur, Joseph C; Severson, Richard K

2009-06-01

Although teamwork is widely promoted by the Institute of Medicine, the American Academy of Family Physicians, and the Future of Family Medicine project, the health care literature does not provide clear direction on how to create or maintain high-functioning teams in ambulatory residency education. In 2004, we reorganized the clinical operation of our family medicine residency clinic into teams, each consisting of faculty, residents, and nursing and administrative staff. We hypothesized that operating within teams would have a positive effect on employees' job satisfaction and perceptions of our clinic's organizational and learning environments. We administered a confidential survey to faculty, residents, and staff annually over 5 years (2002-2006). Using questionnaire data from 2002-2003 as a baseline and data from 2004-2006 as a post-intervention measurement, we performed Mann-Whitney tests to assess the effect of the implementation of teams on employees' ratings of job satisfaction, individual autonomy, organizational commitment, goal attainment, physical characteristics and personnel arrangements within the clinic, learning opportunities for residents, teaching behaviors of faculty, roles of staff, and learning organization characteristics. After the implementation of teams, there was an improvement in ratings of learning opportunities and quality of teaching, job satisfaction, employee autonomy, staff roles, and staff attitudes toward residents. Implementing a team approach in a residency clinic can improve measures of physician and staff satisfaction and organizational function.

Transitions in Classroom Technology: Instructor Implementation of Classroom Management Software

ERIC Educational Resources Information Center

Ackerman, David; Chung, Christina; Sun, Jerry Chih-Yuan

2014-01-01

The authors look at how business instructor needs are fulfilled by classroom management software (CMS), such as Moodle, and why instructors are sometimes slow to implement it. Instructors at different universities provided both qualitative and quantitative responses regarding their use of CMS. The results indicate that the top needs fulfilled by…

Do primary care professionals agree about progress with implementation of primary care teams: results from a cross sectional study.

PubMed

Tierney, E; O'Sullivan, M; Hickey, L; Hannigan, A; May, C; Cullen, W; Kennedy, N; Kineen, L; MacFarlane, A

2016-11-22

Primary care is the cornerstone of healthcare reform with policies across jurisdictions promoting interdisciplinary team working. The effective implementation of such health policies requires understanding the perspectives of all actors. However, there is a lack of research about health professionals' views of this process. This study compares Primary Healthcare Professionals' perceptions of the effectiveness of the Primary Care Strategy and Primary Care Team (PCT) implementation in Ireland. Design and Setting: e-survey of (1) General Practitioners (GPs) associated with a Graduate Medical School (N = 100) and (2) Primary Care Professionals in 3 of 4 Health Service Executive (HSE) regions (N = 2309). After piloting, snowball sampling was used to administer the survey. Descriptive analysis was carried out using SPSS. Ratings across groups were compared using non-parametric tests. There were 569 responses. Response rates varied across disciplines (71 % for GPs, 22 % for other Primary Healthcare Professionals (PCPs). Respondents across all disciplines viewed interdisciplinary working as important. Respondents agreed on lack of progress of implementation of formal PCTs (median rating of 2, where 1 is no progress at all and 5 is complete implementation). GPs were more negative about the effectiveness of the Strategy to promote different disciplines to work together (median rating of 2 compared to 3 for clinical therapists and 3.5 for nurses, P = 0.001). Respondents identified resources and GP participation as most important for effective team working. Protected time for meetings and capacity to manage workload for meetings were rated as very important factors for effective team working by GPs, clinical therapists and nurses. A building for co-location of teams was rated as an important factor by nurses and clinical therapists though GPs rated it as less important. Payment to attend meetings and contractual arrangements were considered important factors by

Idea Paper: The Lifecycle of Software for Scientific Simulations

DOE Office of Scientific and Technical Information (OSTI.GOV)

Dubey, Anshu; McInnes, Lois C.

The software lifecycle is a well researched topic that has produced many models to meet the needs of different types of software projects. However, one class of projects, software development for scientific computing, has received relatively little attention from lifecycle researchers. In particular, software for end-to-end computations for obtaining scientific results has received few lifecycle proposals and no formalization of a development model. An examination of development approaches employed by the teams implementing large multicomponent codes reveals a great deal of similarity in their strategies. This idea paper formalizes these related approaches into a lifecycle model for end-to-end scientific applicationmore » software, featuring loose coupling between submodels for development of infrastructure and scientific capability. We also invite input from stakeholders to converge on a model that captures the complexity of this development processes and provides needed lifecycle guidance to the scientific software community.« less

Total Quality Management: Analysis, Evaluation and Implementation Within ACRV Project Teams

NASA Technical Reports Server (NTRS)

Raiman, Laura B.

1991-01-01

Total quality management (TQM) is a cooperative form of doing business that relies on the talents of everyone in an organization to continually improve quality and productivity, using teams and an assortment of statistical and measurement tools. The Assured Crew Return Vehicle (ACRV) Project Office was identified as an excellent project in which to demonstrate the applications and benefits of TQM processes. As the ACRV Program moves through its various stages of development, it is vital that effectiveness and efficiency be maintained in order to provide the Space Station Freedom (SSF) crew an affordable, on-time assured return to Earth. A critical factor for the success of the ACRV is attaining the maximum benefit from the resources applied to the program. Through a series of four tutorials on various quality improvement techniques, and numerous one-on-one sessions during the SSF's 10-week term in the project office, results were obtained which are aiding the ACRV Office in implementing a disciplined, ongoing process for generating fundamental decisions and actions that shape and guide the organization. Significant advances were made in improving the processes for two particular groups - the correspondence distribution team and the WATER Test team. Numerous people from across JSC were a part of the various team activities including engineering, man systems, and safety. The work also included significant interaction with the support contractor to the ACRV Project. The results of the improvement activities can be used as models for other organizations desiring to operate under a system of continuous improvement. In particular, they have advanced the ACRV Project Teams further down the path of continuous improvement, in support of a working philosophy of TQM.

Staff turnover in statewide implementation of ACT: relationship with ACT fidelity and other team characteristics

PubMed Central

Rollins, Angela L.; Salyers, Michelle P.; Tsai, Jack; Lydick, Jennifer M.

2010-01-01

Staff turnover on assertive community treatment (ACT) teams is a poorly understood phenomenon. This study examined annual turnover and fidelity data collected in a statewide implementation of ACT over a 5-year period. Mean annual staff turnover across all observations was 30.0%. Turnover was negatively correlated with overall fidelity at Year 1 and 3. The team approach fidelity item was negatively correlated with staff turnover at Year 3. For 13 teams with 3 years of follow-up data, turnover rates did not change over time. Most ACT staff turnover rates were comparable or better than other turnover rates reported in the mental health and substance abuse literature. PMID:20012481

Staff turnover in statewide implementation of ACT: relationship with ACT fidelity and other team characteristics.

PubMed

Rollins, Angela L; Salyers, Michelle P; Tsai, Jack; Lydick, Jennifer M

2010-09-01

Staff turnover on assertive community treatment (ACT) teams is a poorly understood phenomenon. This study examined annual turnover and fidelity data collected in a statewide implementation of ACT over a 5-year period. Mean annual staff turnover across all observations was 30.0%. Turnover was negatively correlated with overall fidelity at Year 1 and 3. The team approach fidelity item was negatively correlated with staff turnover at Year 3. For 13 teams with 3 years of follow-up data, turnover rates did not change over time. Most ACT staff turnover rates were comparable or better than other turnover rates reported in the mental health and substance abuse literature.

Sobriety Treatment and Recovery Teams: Implementation Fidelity and Related Outcomes.

PubMed

Huebner, Ruth A; Posze, Lynn; Willauer, Tina M; Hall, Martin T

2015-01-01

Although integrated programs between child welfare and substance abuse treatment are recommended for families with co-occurring child maltreatment and substance use disorders, implementing integrated service delivery strategies with fidelity is a challenging process. This study of the first five years of the Sobriety Treatment and Recovery Team (START) program examines implementation fidelity using a model proposed by Carroll et al. (2007). The study describes the process of strengthening moderators of implementation fidelity, trends in adherence to START service delivery standards, and trends in parent and child outcomes. Qualitative and quantitative measures were used to prospectively study three START sites serving 341 families with 550 parents and 717 children. To achieve implementation fidelity to service delivery standards required a pre-service year and two full years of operation, persistent leadership, and facilitative actions that challenged the existing paradigm. Over four years of service delivery, the time from the child protective services report to completion of five drug treatment sessions was reduced by an average of 75 days. This trend was associated with an increase in parent retention, parental sobriety, and parent retention of child custody. Conclusions/Importance: Understanding the implementation processes necessary to establish complex integrated programs may support realistic allocation of resources. Although implementation fidelity is a moderator of program outcome, complex inter-agency interventions may benefit from innovative measures of fidelity that promote improvement without extensive cost and data collection burden. The implementation framework applied in this study was useful in examining implementation processes, fidelity, and related outcomes.

Virtual Team Governance: Addressing the Governance Mechanisms and Virtual Team Performance

NASA Astrophysics Data System (ADS)

Zhan, Yihong; Bai, Yu; Liu, Ziheng

As technology has improved and collaborative software has been developed, virtual teams with geographically dispersed members spread across diverse physical locations have become increasingly prominent. Virtual team is supported by advancing communication technologies, which makes virtual teams able to largely transcend time and space. Virtual teams have changed the corporate landscape, which are more complex and dynamic than traditional teams since the members of virtual teams are spread on diverse geographical locations and their roles in the virtual team are different. Therefore, how to realize good governance of virtual team and arrive at good virtual team performance is becoming critical and challenging. Good virtual team governance is essential for a high-performance virtual team. This paper explores the performance and the governance mechanism of virtual team. It establishes a model to explain the relationship between the performance and the governance mechanisms in virtual teams. This paper is focusing on managing virtual teams. It aims to find the strategies to help business organizations to improve the performance of their virtual teams and arrive at the objectives of good virtual team management.

Implementing and Evaluating a Peer-Led Team Learning Approach in Undergraduate Anatomy and Physiology

ERIC Educational Resources Information Center

Finn, Kevin; Campisi, Jay

2015-01-01

This article describes how a Peer-Led Team Learning (PLTL) program was implemented in a first-year, undergraduate Anatomy and Physiology course sequence to examine the student perceptions of the program and determine the effects of PLTL on student performance.

Project Management Software for Distributed Industrial Companies

NASA Astrophysics Data System (ADS)

Dobrojević, M.; Medjo, B.; Rakin, M.; Sedmak, A.

This paper gives an overview of the development of a new software solution for project management, intended mainly to use in industrial environment. The main concern of the proposed solution is application in everyday engineering practice in various, mainly distributed industrial companies. Having this in mind, special care has been devoted to development of appropriate tools for tracking, storing and analysis of the information about the project, and in-time delivering to the right team members or other responsible persons. The proposed solution is Internet-based and uses LAMP/WAMP (Linux or Windows - Apache - MySQL - PHP) platform, because of its stability, versatility, open source technology and simple maintenance. Modular structure of the software makes it easy for customization according to client specific needs, with a very short implementation period. Its main advantages are simple usage, quick implementation, easy system maintenance, short training and only basic computer skills needed for operators.

Enhanced clarity and holism: the outcome of implementing the ICF with an acute stroke multidisciplinary team in England

PubMed Central

Harries, Priscilla; Kilbride, Cherry; De Souza, Lorraine

2013-01-01

Purpose: Although it is recommended that the ICF (International Classification of Functioning, Disability and Health) should be implemented to aid communication within multidisciplinary stroke services, there is no empirical evidence to demonstrate the outcomes of such implementation. Working with one stroke service, this project aimed to address this gap and sought to evaluate the outcomes of implementing an ICF-based clinical tool into practice. Method: Using an action research framework with mixed methods, data were collected from individual interviews, a focus group, questionnaires, email communications, minutes from relevant meetings and field notes. Thematic analysis was undertaken, using immersion and crystallisation, to define overall themes. Descriptive statistics were used to analyse quantitative data. Data from both sources were combined to create key findings. Results: Three findings were determined from the data analysis. The ICF (1) fosters communication within and beyond the multidisciplinary stroke team; (2) promotes holistic thinking; and (3) helps to clarify team roles. Conclusions: The ICF enhanced clarity of communication and team roles within the acute stroke multidisciplinary team as well as with other clinicians, patients and their relatives. In addition, the ICF challenged stroke clinicians to think holistically, thereby appropriately extending their domain of concern beyond their traditional remit. Implications for Rehabilitation The ICF is a globally accepted framework to describe functioning and is in use in a variety of clinical settings. Yet, the outcomes of using it in clinical practice have yet to be fully explored. This study found that the ICF enhanced clarity of communication and team roles within an acute stroke multidisciplinary team and to others beyond the team, including clinicians, patients and their relatives. Using the ICF also challenged clinicians to think holistically about patient needs following a stroke. PMID:23530624

Dedication increases productivity: an analysis of the implementation of a dedicated medical team in the emergency department.

PubMed

Ramos, Pedro; Paiva, José Artur

2017-12-01

In several European countries, emergency departments (EDs) now employ a dedicated team of full-time emergency medicine (EM) physicians, with a distinct leadership and bed-side emergency training, in all similar to other hospital departments. In Portugal, however, there are still two very different models for staffing EDs: a classic model, where EDs are mostly staffed with young inexperienced physicians from different medical departments who take turns in the ED in 12-h shifts and a dedicated model, recently implemented in some hospitals, where the ED is staffed by a team of doctors with specific medical competencies in emergency medicine that work full-time in the ED. Our study assesses the effect of an intervention in a large academic hospital ED in Portugal in 2002, and it is the first to test the hypothesis that implementing a dedicated team of doctors with EM expertise increases the productivity and reduces costs in the ED, maintaining the quality of care provided to patients. A pre-post design was used for comparing the change on the organisational model of delivering care in our medical ED. All emergency medical admissions were tracked in 2002 (classic model with 12-h shift in the ED) and 2005/2006 (dedicated team with full-time EM physicians), and productivity, costs with medical human resources and quality of care measures were compared. We found that medical productivity (number of patients treated per hour of medical work) increased dramatically after the creation of the dedicated team (X 2 KW = 31.135; N = 36; p < 0.001) and costs with ED medical work reduced both in regular hours and overtime. Moreover, hospitalisation rates decreased and the length of stay in the ED increased significantly after the creation of the dedicated team. Implementing a dedicated team of doctors increased the medical productivity and reduced costs in our ED. Our findings have straightforward implication for Portuguese policymakers aiming at reducing hospital costs

Implementation of the Geriatric Patient-Aligned Care Team Model in the Veterans Health Administration (VA).

PubMed

Sullivan, Jennifer L; Eisenstein, Rina; Price, Thomas; Solimeo, Samantha; Shay, Kenneth

2018-01-01

Here, we describe the implementation of a specialty primary care medical home (PCMH) model called Geriatric Patient-Aligned Care Teams (GeriPACT) in the Veterans' Health Administration (VA) that is focused on serving older complex patients. In particular, our aims in this article are to describe how the GeriPACT model was developed and implemented in VA sites, provide a closer look at how GeriPACT functions by presenting a case study, and highlight data showing national variation in the implementation of GeriPACT staffing models and PCMH practices. Stakeholder feedback regarding the GeriPACT model was obtained from a GeriPACT team and the director of GeriPACT in VA. Here, we present national data regarding variations in GeriPACT staffing and PCMH practices. Following the adoption and implementation of the GeriPACT model and release of the GeriPACT handbook, sites were able to adopt the model's principles. The VA's adoption of PCMH reinforced the mission of patient-centered primary care by integrating psychosocial and environmental determinants of health. This was accomplished with enhancements to staff support through new full-time employment equivalents, but also by optimizing staff productivity through improved team function and interpersonal care. The GeriPACT model was implemented in a bottom-up fashion that has led to variation in how GeriPACTs are structured and staffed, as well as how they conform to various PCMH principles. GeriPACT is one approach for bringing an interdisciplinary, patient-centric perspective to primary care in a manner that can likely support the higher staffing costs with economies realized from diminished reliance on institutional placement and highly technologic health care. It is a model which can provide training for the next generation of providers and clinicians. © Copyright 2018 by the American Board of Family Medicine.

Computer Software Configuration Item-Specific Flight Software Image Transfer Script Generator

NASA Technical Reports Server (NTRS)

Bolen, Kenny; Greenlaw, Ronald

2010-01-01

A K-shell UNIX script enables the International Space Station (ISS) Flight Control Team (FCT) operators in NASA s Mission Control Center (MCC) in Houston to transfer an entire or partial computer software configuration item (CSCI) from a flight software compact disk (CD) to the onboard Portable Computer System (PCS). The tool is designed to read the content stored on a flight software CD and generate individual CSCI transfer scripts that are capable of transferring the flight software content in a given subdirectory on the CD to the scratch directory on the PCS. The flight control team can then transfer the flight software from the PCS scratch directory to the Electronically Erasable Programmable Read Only Memory (EEPROM) of an ISS Multiplexer/ Demultiplexer (MDM) via the Indirect File Transfer capability. The individual CSCI scripts and the CSCI Specific Flight Software Image Transfer Script Generator (CFITSG), when executed a second time, will remove all components from their original execution. The tool will identify errors in the transfer process and create logs of the transferred software for the purposes of configuration management.

Collaborative Falls Prevention: Interprofessional Team Formation, Implementation, and Evaluation.

PubMed

Lasater, Kathie; Cotrell, Victoria; McKenzie, Glenise; Simonson, William; Morgove, Megan W; Long, Emily E; Eckstrom, Elizabeth

2016-12-01

As health care rapidly evolves to promote person-centered care, evidence-based practice, and team-structured environments, nurses must lead interprofessional (IP) teams to collaborate for optimal health of the populations and more cost-effective health care. Four professions-nursing, medicine, social work, and pharmacy-formed a teaching team to address fall prevention among older adults in Oregon using an IP approach. The teaching team developed training sessions that included interactive, evidence-based sessions, followed by individualized team coaching. This article describes how the IP teaching team came together to use a unique cross-training approach to teach each other. They then taught and coached IP teams from a variety of community practice settings to foster their integration of team-based falls-prevention strategies into practice. After coaching 25 teams for a year each, the authors present the lessons learned from the teaching team's formation and experiences, as well as feedback from practice team participants that can provide direction for other IP teams. J Contin Educ Nurs. 2016;47(12):545-550. Copyright 2016, SLACK Incorporated.

Antiterrorist Software

NASA Technical Reports Server (NTRS)

Clark, David A.

1998-01-01

In light of the escalation of terrorism, the Department of Defense spearheaded the development of new antiterrorist software for all Government agencies by issuing a Broad Agency Announcement to solicit proposals. This Government-wide competition resulted in a team that includes NASA Lewis Research Center's Computer Services Division, who will develop the graphical user interface (GUI) and test it in their usability lab. The team launched a program entitled Joint Sphere of Security (JSOS), crafted a design architecture (see the following figure), and is testing the interface. This software system has a state-ofthe- art, object-oriented architecture, with a main kernel composed of the Dynamic Information Architecture System (DIAS) developed by Argonne National Laboratory. DIAS will be used as the software "breadboard" for assembling the components of explosions, such as blast and collapse simulations.

Software analysis handbook: Software complexity analysis and software reliability estimation and prediction

NASA Technical Reports Server (NTRS)

Lee, Alice T.; Gunn, Todd; Pham, Tuan; Ricaldi, Ron

1994-01-01

This handbook documents the three software analysis processes the Space Station Software Analysis team uses to assess space station software, including their backgrounds, theories, tools, and analysis procedures. Potential applications of these analysis results are also presented. The first section describes how software complexity analysis provides quantitative information on code, such as code structure and risk areas, throughout the software life cycle. Software complexity analysis allows an analyst to understand the software structure, identify critical software components, assess risk areas within a software system, identify testing deficiencies, and recommend program improvements. Performing this type of analysis during the early design phases of software development can positively affect the process, and may prevent later, much larger, difficulties. The second section describes how software reliability estimation and prediction analysis, or software reliability, provides a quantitative means to measure the probability of failure-free operation of a computer program, and describes the two tools used by JSC to determine failure rates and design tradeoffs between reliability, costs, performance, and schedule.

Verifying Architectural Design Rules of the Flight Software Product Line

NASA Technical Reports Server (NTRS)

Ganesan, Dharmalingam; Lindvall, Mikael; Ackermann, Chris; McComas, David; Bartholomew, Maureen

2009-01-01

This paper presents experiences of verifying architectural design rules of the NASA Core Flight Software (CFS) product line implementation. The goal of the verification is to check whether the implementation is consistent with the CFS architectural rules derived from the developer's guide. The results indicate that consistency checking helps a) identifying architecturally significant deviations that were eluded during code reviews, b) clarifying the design rules to the team, and c) assessing the overall implementation quality. Furthermore, it helps connecting business goals to architectural principles, and to the implementation. This paper is the first step in the definition of a method for analyzing and evaluating product line implementations from an architecture-centric perspective.

Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts.

PubMed

Shah, Hemant; Allard, Raymond D; Enberg, Robert; Krishnan, Ganesh; Williams, Patricia; Nadkarni, Prakash M

2012-03-09

A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies.

Requirements for guidelines systems: implementation challenges and lessons from existing software-engineering efforts

PubMed Central

2012-01-01

Background A large body of work in the clinical guidelines field has identified requirements for guideline systems, but there are formidable challenges in translating such requirements into production-quality systems that can be used in routine patient care. Detailed analysis of requirements from an implementation perspective can be useful in helping define sub-requirements to the point where they are implementable. Further, additional requirements emerge as a result of such analysis. During such an analysis, study of examples of existing, software-engineering efforts in non-biomedical fields can provide useful signposts to the implementer of a clinical guideline system. Methods In addition to requirements described by guideline-system authors, comparative reviews of such systems, and publications discussing information needs for guideline systems and clinical decision support systems in general, we have incorporated additional requirements related to production-system robustness and functionality from publications in the business workflow domain, in addition to drawing on our own experience in the development of the Proteus guideline system (http://proteme.org). Results The sub-requirements are discussed by conveniently grouping them into the categories used by the review of Isern and Moreno 2008. We cite previous work under each category and then provide sub-requirements under each category, and provide example of similar work in software-engineering efforts that have addressed a similar problem in a non-biomedical context. Conclusions When analyzing requirements from the implementation viewpoint, knowledge of successes and failures in related software-engineering efforts can guide implementers in the choice of effective design and development strategies. PMID:22405400

The Texas Children's Hospital immunization forecaster: conceptualization to implementation.

PubMed

Cunningham, Rachel M; Sahni, Leila C; Kerr, G Brady; King, Laura L; Bunker, Nathan A; Boom, Julie A

2014-12-01

Immunization forecasting systems evaluate patient vaccination histories and recommend the dates and vaccines that should be administered. We described the conceptualization, development, implementation, and distribution of a novel immunization forecaster, the Texas Children's Hospital (TCH) Forecaster. In 2007, TCH convened an internal expert team that included a pediatrician, immunization nurse, software engineer, and immunization subject matter experts to develop the TCH Forecaster. Our team developed the design of the model, wrote the software, populated the Excel tables, integrated the software, and tested the Forecaster. We created a table of rules that contained each vaccine's recommendations, minimum ages and intervals, and contraindications, which served as the basis for the TCH Forecaster. We created 15 vaccine tables that incorporated 79 unique dose states and 84 vaccine types to operationalize the entire United States recommended immunization schedule. The TCH Forecaster was implemented throughout the TCH system, the Indian Health Service, and the Virginia Department of Health. The TCH Forecast Tester is currently being used nationally. Immunization forecasting systems might positively affect adherence to vaccine recommendations. Efforts to support health care provider utilization of immunization forecasting systems and to evaluate their impact on patient care are needed.

Using Modern Methodologies with Maintenance Software

NASA Technical Reports Server (NTRS)

Streiffert, Barbara A.; Francis, Laurie K.; Smith, Benjamin D.

2014-01-01

Jet Propulsion Laboratory uses multi-mission software produced by the Mission Planning and Sequencing (MPS) team to process, simulate, translate, and package the commands that are sent to a spacecraft. MPS works under the auspices of the Multi-Mission Ground Systems and Services (MGSS). This software consists of nineteen applications that are in maintenance. The MPS software is classified as either class B (mission critical) or class C (mission important). The scheduling of tasks is difficult because mission needs must be addressed prior to performing any other tasks and those needs often spring up unexpectedly. Keeping track of the tasks that everyone is working on is also difficult because each person is working on a different software component. Recently the group adopted the Scrum methodology for planning and scheduling tasks. Scrum is one of the newer methodologies typically used in agile development. In the Scrum development environment, teams pick their tasks that are to be completed within a sprint based on priority. The team specifies the sprint length usually a month or less. Scrum is typically used for new development of one application. In the Scrum methodology there is a scrum master who is a facilitator who tries to make sure that everything moves smoothly, a product owner who represents the user(s) of the software and the team. MPS is not the traditional environment for the Scrum methodology. MPS has many software applications in maintenance, team members who are working on disparate applications, many users, and is interruptible based on mission needs, issues and requirements. In order to use scrum, the methodology needed adaptation to MPS. Scrum was chosen because it is adaptable. This paper is about the development of the process for using scrum, a new development methodology, with a team that works on disparate interruptible tasks on multiple software applications.

Consequences of team charter quality: Teamwork mental model similarity and team viability in engineering design student teams

NASA Astrophysics Data System (ADS)

Conway Hughston, Veronica

Since 1996 ABET has mandated that undergraduate engineering degree granting institutions focus on learning outcomes such as professional skills (i.e. solving unstructured problems and working in teams). As a result, engineering curricula were restructured to include team based learning---including team charters. Team charters were diffused into engineering education as one of many instructional activities to meet the ABET accreditation mandates. However, the implementation and execution of team charters into engineering team based classes has been inconsistent and accepted without empirical evidence of the consequences. The purpose of the current study was to investigate team effectiveness, operationalized as team viability, as an outcome of team charter implementation in an undergraduate engineering team based design course. Two research questions were the focus of the study: a) What is the relationship between team charter quality and viability in engineering student teams, and b) What is the relationship among team charter quality, teamwork mental model similarity, and viability in engineering student teams? Thirty-eight intact teams, 23 treatment and 15 comparison, participated in the investigation. Treatment teams attended a team charter lecture, and completed a team charter homework assignment. Each team charter was assessed and assigned a quality score. Comparison teams did not join the lecture, and were not asked to create a team charter. All teams completed each data collection phase: a) similarity rating pretest; b) similarity posttest; and c) team viability survey. Findings indicate that team viability was higher in teams that attended the lecture and completed the charter assignment. Teams with higher quality team charter scores reported higher levels of team viability than teams with lower quality charter scores. Lastly, no evidence was found to support teamwork mental model similarity as a partial mediator of the team charter quality on team viability

Huddle up!: The adoption and use of structured team communication for VA medical home implementation.

PubMed

Rodriguez, Hector P; Meredith, Lisa S; Hamilton, Alison B; Yano, Elizabeth M; Rubenstein, Lisa V

2015-01-01

Daily clinical team meetings (i.e., "huddles") may be helpful in implementing new roles and responsibilities for patient care because they provide a regular opportunity for member learning and feedback. We examined how huddles were implemented in the context of the VA patient-centered medical home (PCMH) transformation, including assessing barriers and facilitators to regular huddling among small teams ("teamlets"). We assessed the extent to which teamlet members that huddled had higher self-efficacy for PCMH changes, reported better teamwork experiences, and perceived more supportive practice environments. We used a convergent mixed-methods approach to analyze 79 teamlet member interviews from six VA primary care practices and 418 clinician and staff PCMH survey responses from the six interviewed practices and 13 additional practices in the same region. Most members reported participating in teamlet huddles when asked in surveys (85%). A minority of interview participants, however, described routine huddling focused on previsit planning that included all members. When members reported routine teamlet huddling, activities included (a) previsit planning, (b) strategizing treatment plans for patients with special or complex needs, (c) addressing daily workflow and communication issues through collective problem solving, and (d) ensuring awareness of what team members do and what actions are happening on the teamlet and in the practice. Primary care providers (PCPs) were least likely to report routine huddling. PCP huddlers reported greater self-efficacy for implementing PCMH changes. All huddlers, irrespective of role, reported better teamwork and more supportive practice climates. The most common barriers to teamlet huddling were limited time and operational constraints. In order to improve the impact of huddles on patient care, practice leaders should clearly communicate the goals, requirements, and benefits of huddling and provide adequate time and resources to

Mitigating Motion Base Safety Issues: The NASA LaRC CMF Implementation

NASA Technical Reports Server (NTRS)

Bryant, Richard B., Jr.; Grupton, Lawrence E.; Martinez, Debbie; Carrelli, David J.

2005-01-01

The NASA Langley Research Center (LaRC), Cockpit Motion Facility (CMF) motion base design has taken advantage of inherent hydraulic characteristics to implement safety features using hardware solutions only. Motion system safety has always been a concern and its implementation is addressed differently by each organization. Some approaches rely heavily on software safety features. Software which performs safety functions is subject to more scrutiny making its approval, modification, and development time consuming and expensive. The NASA LaRC's CMF motion system is used for research and, as such, requires that the software be updated or modified frequently. The CMF's customers need the ability to update the simulation software frequently without the associated cost incurred with safety critical software. This paper describes the CMF engineering team's approach to achieving motion base safety by designing and implementing all safety features in hardware, resulting in applications software (including motion cueing and actuator dynamic control) being completely independent of the safety devices. This allows the CMF safety systems to remain intact and unaffected by frequent research system modifications.

The image-guided surgery toolkit IGSTK: an open source C++ software toolkit.

PubMed

Enquobahrie, Andinet; Cheng, Patrick; Gary, Kevin; Ibanez, Luis; Gobbi, David; Lindseth, Frank; Yaniv, Ziv; Aylward, Stephen; Jomier, Julien; Cleary, Kevin

2007-11-01

This paper presents an overview of the image-guided surgery toolkit (IGSTK). IGSTK is an open source C++ software library that provides the basic components needed to develop image-guided surgery applications. It is intended for fast prototyping and development of image-guided surgery applications. The toolkit was developed through a collaboration between academic and industry partners. Because IGSTK was designed for safety-critical applications, the development team has adopted lightweight software processes that emphasizes safety and robustness while, at the same time, supporting geographically separated developers. A software process that is philosophically similar to agile software methods was adopted emphasizing iterative, incremental, and test-driven development principles. The guiding principle in the architecture design of IGSTK is patient safety. The IGSTK team implemented a component-based architecture and used state machine software design methodologies to improve the reliability and safety of the components. Every IGSTK component has a well-defined set of features that are governed by state machines. The state machine ensures that the component is always in a valid state and that all state transitions are valid and meaningful. Realizing that the continued success and viability of an open source toolkit depends on a strong user community, the IGSTK team is following several key strategies to build an active user community. These include maintaining a users and developers' mailing list, providing documentation (application programming interface reference document and book), presenting demonstration applications, and delivering tutorial sessions at relevant scientific conferences.

Catalyst for Change: A Case Report of a Campus-wide Student Information System Software Implementation Project

ERIC Educational Resources Information Center

Stivers, Jan; Garrity, N. B.

2004-01-01

When a mid-sized public college made a politically unpopular decision to purchase new student information system software, a team of fourteen people from across campus was assembled and charged with facilitating the transition from the home-grown system. This case report describes the challenges they faced as they worked to understand their…

Advancing Perspectives of Sustainability and Large-Scale Implementation of Design Teams in Ghana's Polytechnics: Issues and Opportunities

ERIC Educational Resources Information Center

Bakah, Marie Afua Baah; Voogt, Joke M.; Pieters, Jules M.

2012-01-01

Polytechnic staff perspectives are sought on the sustainability and large-scale implementation of design teams (DT), as a means for collaborative curriculum design and teacher professional development in Ghana's polytechnics, months after implementation. Data indicates that teachers still collaborate in DTs for curriculum design and professional…

GFAST Software Demonstration

NASA Image and Video Library

2017-03-17

NASA engineers and test directors gather in Firing Room 3 in the Launch Control Center at NASA's Kennedy Space Center in Florida, to watch a demonstration of the automated command and control software for the agency's Space Launch System (SLS) and Orion spacecraft. In front, far right, is Charlie Blackwell-Thompson, launch director for Exploration Mission 1 (EM-1). The software is called the Ground Launch Sequencer. It will be responsible for nearly all of the launch commit criteria during the final phases of launch countdowns. The Ground and Flight Application Software Team (GFAST) demonstrated the software. It was developed by the Command, Control and Communications team in the Ground Systems Development and Operations (GSDO) Program. GSDO is helping to prepare the center for the first test flight of Orion atop the SLS on EM-1.

The effect of implementing a care coordination program on team dynamics and the patient experience.

PubMed

Di Capua, Paul; Clarke, Robin; Tseng, Chi-Hong; Wilhalme, Holly; Sednew, Renee; McDonald, Kathryn M; Skootsky, Samuel A; Wenger, Neil

2017-08-01

Care coordination programs are frequently implemented in the redesign of primary care systems, focused on improving patient outcomes and reducing utilization. However, redesign can be disruptive, affect patient experiences, and undermine elements in the patient-centered medical home, such as team-based care. Case-controlled study with difference-in-differences (DID) and cross-sectional analyses. The phased implementation of a care coordination program permitted evaluation of a natural experiment to compare measures of patient experience and teamwork in practices with and without care coordinators. Patient experience scores were compared before and after the introduction of care coordinators, using DID analyses. Cross-sectional data were used to compare teamwork, based on the relational coordination survey, and physician-perceived barriers to coordinated care between clinics with and without care coordinators. We evaluated survey responses from 459 staff and physicians and 13,441 patients in 26 primary care practices. Practices with care coordinators did not have significantly different relational coordination scores compared with practices without care coordinators, and physicians in these practices did not report reduced barriers to coordinated care. After implementation of the program, patients in practices with care coordinators reported a more positive experience with staff over time (DID, 2.6 percentage points; P = .0009). A flexible program that incorporates care coordinators into the existing care team was minimally disruptive to existing team dynamics, and the embedded care coordinators were associated with a small increase in patient ratings that reflected a more positive experience with staff.

Design and implementation of the mobility assessment tool: software description.

PubMed

Barnard, Ryan T; Marsh, Anthony P; Rejeski, Walter Jack; Pecorella, Anthony; Ip, Edward H

2013-07-23

In previous work, we described the development of an 81-item video-animated tool for assessing mobility. In response to criticism levied during a pilot study of this tool, we sought to develop a new version built upon a flexible framework for designing and administering the instrument. Rather than constructing a self-contained software application with a hard-coded instrument, we designed an XML schema capable of describing a variety of psychometric instruments. The new version of our video-animated assessment tool was then defined fully within the context of a compliant XML document. Two software applications--one built in Java, the other in Objective-C for the Apple iPad--were then built that could present the instrument described in the XML document and collect participants' responses. Separating the instrument's definition from the software application implementing it allowed for rapid iteration and easy, reliable definition of variations. Defining instruments in a software-independent XML document simplifies the process of defining instruments and variations and allows a single instrument to be deployed on as many platforms as there are software applications capable of interpreting the instrument, thereby broadening the potential target audience for the instrument. Continued work will be done to further specify and refine this type of instrument specification with a focus on spurring adoption by researchers in gerontology and geriatric medicine.

Design and implementation of the mobility assessment tool: software description

PubMed Central

2013-01-01

Background In previous work, we described the development of an 81-item video-animated tool for assessing mobility. In response to criticism levied during a pilot study of this tool, we sought to develop a new version built upon a flexible framework for designing and administering the instrument. Results Rather than constructing a self-contained software application with a hard-coded instrument, we designed an XML schema capable of describing a variety of psychometric instruments. The new version of our video-animated assessment tool was then defined fully within the context of a compliant XML document. Two software applications—one built in Java, the other in Objective-C for the Apple iPad—were then built that could present the instrument described in the XML document and collect participants’ responses. Separating the instrument’s definition from the software application implementing it allowed for rapid iteration and easy, reliable definition of variations. Conclusions Defining instruments in a software-independent XML document simplifies the process of defining instruments and variations and allows a single instrument to be deployed on as many platforms as there are software applications capable of interpreting the instrument, thereby broadening the potential target audience for the instrument. Continued work will be done to further specify and refine this type of instrument specification with a focus on spurring adoption by researchers in gerontology and geriatric medicine. PMID:23879716

SU-F-P-04: Implementation of Dose Monitoring Software: Successes and Pitfalls

DOE Office of Scientific and Technical Information (OSTI.GOV)

Och, J

2016-06-15

Purpose: to successfully install a dose monitoring software (DMS) application to assist in CT protocol and dose management. Methods: Upon selecting the DMS, we began our implementation of the application. A working group composed of Medical Physics, Radiology Administration, Information Technology, and CT technologists was formed. On-site training in the application was supplied by the vendor. The decision was made to apply the process for all the CT protocols on all platforms at all facilities. Protocols were painstakingly mapped to the correct masters, and the system went ‘live’. Results: We are routinely using DMS as a tool in our Clinicalmore » Performance CT QA program. It is useful in determining the effectiveness of revisions to existing protocols, and establishing performance baselines for new units. However, the implementation was not without difficulty. We identified several pitfalls and obstacles which frustrated progress. Including: Training deficiencies, Nomenclature problems, Communication, DICOM variability. Conclusion: Dose monitoring software can be a potent tool for QA. However, implementation of the program can be problematic and requires planning, organization and commitment.« less

Fully Employing Software Inspections Data

NASA Technical Reports Server (NTRS)

Shull, Forrest; Feldmann, Raimund L.; Seaman, Carolyn; Regardie, Myrna; Godfrey, Sally

2009-01-01

Software inspections provide a proven approach to quality assurance for software products of all kinds, including requirements, design, code, test plans, among others. Common to all inspections is the aim of finding and fixing defects as early as possible, and thereby providing cost savings by minimizing the amount of rework necessary later in the lifecycle. Measurement data, such as the number and type of found defects and the effort spent by the inspection team, provide not only direct feedback about the software product to the project team but are also valuable for process improvement activities. In this paper, we discuss NASA's use of software inspections and the rich set of data that has resulted. In particular, we present results from analysis of inspection data that illustrate the benefits of fully utilizing that data for process improvement at several levels. Examining such data across multiple inspections or projects allows team members to monitor and trigger cross project improvements. Such improvements may focus on the software development processes of the whole organization as well as improvements to the applied inspection process itself.

Teams communicating through STEPPS.

PubMed

Stead, Karen; Kumar, Saravana; Schultz, Timothy J; Tiver, Sue; Pirone, Christy J; Adams, Robert J; Wareham, Conrad A

2009-06-01

To evaluate the effectiveness of the implementation of a TeamSTEPPS (Team Strategies and Tools to Enhance Performance and Patient Safety) program at an Australian mental health facility. TeamSTEPPS is an evidence-based teamwork training system developed in the United States. Five health care sites in South Australia implemented TeamSTEPPS using a train-the-trainer model over an 8-month intervention period commencing January 2008 and concluding September 2008. A team of senior clinical staff was formed at each site to drive the improvement process. Independent researchers used direct observation and questionnaire surveys to evaluate the effectiveness of the implementation in three outcome areas: observed team behaviours; staff attitudes and opinions; and clinical performance and outcome. The results reported here focus on one site, an inpatient mental health facility. Team knowledge, skills and attitudes; patient safety culture; incident reporting rates; seclusion rates; observation for the frequency of use of TeamSTEPPS tools. Outcomes included restructuring of multidisciplinary meetings and the introduction of structured communication tools. The evaluation of patient safety culture and of staff knowledge, skills and attitudes (KSA) to teamwork and communication indicated a significant improvement in two dimensions of patient safety culture (frequency of event reporting, and organisational learning) and a 6.8% increase in the total KSA score. Clinical outcomes included reduced rates of seclusion. TeamSTEPPS implementation had a substantial impact on patient safety culture, teamwork and communication at an Australian mental health facility. It encouraged a culture of learning from patient safety incidents and making continuous improvements.

Payload Operations Support Team Tools

NASA Technical Reports Server (NTRS)

Askew, Bill; Barry, Matthew; Burrows, Gary; Casey, Mike; Charles, Joe; Downing, Nicholas; Jain, Monika; Leopold, Rebecca; Luty, Roger; McDill, David;

Implementation of team training in medical education in Denmark.

PubMed

Østergaard, H T; Østergaard, D; Lippert, A

2004-10-01

In the field of medicine, team training aiming at improving team skills such as leadership, communication, co-operation, and followership at the individual and the team level seems to reduce risk of serious events and therefore increase patient safety. The preferred educational method for this type of training is simulation. Team training is not, however, used routinely in the hospital. In this paper, we describe a framework for the development of a team training course based on need assessment, learning objectives, educational methods including full-scale simulation and evaluations strategies. The use of this framework is illustrated by the present multiprofessional team training in advanced cardiac life support, trauma team training and neonatal resuscitation in Denmark. The challenges of addressing all aspects of team skills, the education of the facilitators, and establishment of evaluation strategies to document the effect of the different types of training on patient safety are discussed.

Implementation of team training in medical education in Denmark.

PubMed

Østergaard, H T; Østergaard, D; Lippert, A

2008-10-01

In the field of medicine, team training aiming at improving team skills such as leadership, communication, co-operation, and followership at the individual and the team level seems to reduce risk of serious events and therefore increase patient safety. The preferred educational method for this type of training is simulation. Team training is not, however, used routinely in the hospital. In this paper, we describe a framework for the development of a team training course based on need assessment, learning objectives, educational methods including full-scale simulation and evaluations strategies. The use of this framework is illustrated by the present multiprofessional team training in advanced cardiac life support, trauma team training and neonatal resuscitation in Denmark. The challenges of addressing all aspects of team skills, the education of the facilitators, and establishment of evaluation strategies to document the effect of the different types of training on patient safety are discussed.

Co-design of software and hardware to implement remote sensing algorithms

NASA Astrophysics Data System (ADS)

Theiler, James P.; Frigo, Janette R.; Gokhale, Maya; Szymanski, John J.

2002-01-01

Both for offline searches through large data archives and for onboard computation at the sensor head, there is a growing need for ever-more rapid processing of remote sensing data. For many algorithms of use in remote sensing, the bulk of the processing takes place in an ``inner loop'' with a large number of simple operations. For these algorithms, dramatic speedups can often be obtained with specialized hardware. The difficulty and expense of digital design continues to limit applicability of this approach, but the development of new design tools is making this approach more feasible, and some notable successes have been reported. On the other hand, it is often the case that processing can also be accelerated by adopting a more sophisticated algorithm design. Unfortunately, a more sophisticated algorithm is much harder to implement in hardware, so these approaches are often at odds with each other. With careful planning, however, it is sometimes possible to combine software and hardware design in such a way that each complements the other, and the final implementation achieves speedup that would not have been possible with a hardware-only or a software-only solution. We will in particular discuss the co-design of software and hardware to achieve substantial speedup of algorithms for multispectral image segmentation and for endmember identification.

Towards easing the configuration and new team member accommodation for open source software based portals

NASA Astrophysics Data System (ADS)

Fu, L.; West, P.; Zednik, S.; Fox, P. A.

2013-12-01

For simple portals such as vocabulary based services, which contain small amounts of data and require only hyper-textual representation, it is often an overkill to adopt the whole software stack of database, middleware and front end, or to use a general Web development framework as the starting point of development. Directly combining open source software is a much more favorable approach. However, our experience with the Coastal and Marine Spatial Planning Vocabulary (CMSPV) service portal shows that there are still issues such as system configuration and accommodating a new team member that need to be handled carefully. In this contribution, we share our experience in the context of the CMSPV portal, and focus on the tools and mechanisms we've developed to ease the configuration job and the incorporation process of new project members. We discuss the configuration issues that arise when we don't have complete control over how the software in use is configured and need to follow existing configuration styles that may not be well documented, especially when multiple pieces of such software need to work together as a combined system. As for the CMSPV portal, it is built on two pieces of open source software that are still under rapid development: a Fuseki data server and Epimorphics Linked Data API (ELDA) front end. Both lack mature documentation and tutorials. We developed comparison and labeling tools to ease the problem of system configuration. Another problem that slowed down the project is that project members came and went during the development process, so new members needed to start with a partially configured system and incomplete documentation left by old members. We developed documentation/tutorial maintenance mechanisms based on our comparison and labeling tools to make it easier for the new members to be incorporated into the project. These tools and mechanisms also provided benefit to other projects that reused the software components from the CMSPV

Omics Metadata Management Software v. 1 (OMMS)

DOE Office of Scientific and Technical Information (OSTI.GOV)

Our application, the Omics Metadata Management Software (OMMS), answers both needs, empowering experimentalists to generate intuitive, consistent metadata, and to perform bioinformatics analyses and information management tasks via a simple and intuitive web-based interface. Several use cases with short-read sequence datasets are provided to showcase the full functionality of the OMMS, from metadata curation tasks, to bioinformatics analyses and results management and downloading. The OMMS can be implemented as a stand alone-package for individual laboratories, or can be configured for web-based deployment supporting geographically dispersed research teams. Our software was developed with open-source bundles, is flexible, extensible and easily installedmore » and run by operators with general system administration and scripting language literacy.« less

Point of care use of a personal digital assistant for patient consultation management: experience of an intravenous resource nurse team in a major Canadian teaching hospital.

PubMed

Bosma, Laine; Balen, Robert M; Davidson, Erin; Jewesson, Peter J

2003-01-01

The development and integration of a personal digital assistant (PDA)-based point-of-care database into an intravenous resource nurse (IVRN) consultation service for the purposes of consultation management and service characterization are described. The IVRN team provides a consultation service 7 days a week in this 1000-bed tertiary adult care teaching hospital. No simple, reliable method for documenting IVRN patient care activity and facilitating IVRN-initiated patient follow-up evaluation was available. Implementation of a PDA database with exportability of data to statistical analysis software was undertaken in July 2001. A Palm IIIXE PDA was purchased and a three-table, 13-field database was developed using HanDBase software. During the 7-month period of data collection, the IVRN team recorded 4868 consultations for 40 patient care areas. Full analysis of service characteristics was conducted using SPSS 10.0 software. Team members adopted the new technology with few problems, and the authors now can efficiently track and analyze the services provided by their IVRN team.

A Core Plug and Play Architecture for Reusable Flight Software Systems

NASA Technical Reports Server (NTRS)

Wilmot, Jonathan

2006-01-01

The Flight Software Branch, at Goddard Space Flight Center (GSFC), has been working on a run-time approach to facilitate a formal software reuse process. The reuse process is designed to enable rapid development and integration of high-quality software systems and to more accurately predict development costs and schedule. Previous reuse practices have been somewhat successful when the same teams are moved from project to project. But this typically requires taking the software system in an all-or-nothing approach where useful components cannot be easily extracted from the whole. As a result, the system is less flexible and scalable with limited applicability to new projects. This paper will focus on the rationale behind, and implementation of the run-time executive. This executive is the core for the component-based flight software commonality and reuse process adopted at Goddard.

Team Teaching among Mixed Messages: Implementing Two-Way Dual Language Bilingual Education at Third Grade in Texas

ERIC Educational Resources Information Center

Palmer, Deborah; Henderson, Kathryn; Wall, Dorothy; Zúñiga, Christian E.; Berthelsen, Stefan

2016-01-01

This article documents and interrogates top-down district-wide implementation of a two-way dual language bilingual education (DLBE) program in a large urban district. We carried out a language policy ethnography to explore the way two schools' teams of third grade teachers worked together to negotiate the intersection of DLBE implementation and…

Implementation of team training in medical education in Denmark

PubMed Central

Ostergaard, H; Ostergaard, D; Lippert, A

2004-01-01

In the field of medicine, team training aiming at improving team skills such as leadership, communication, co-operation, and followership at the individual and the team level seems to reduce risk of serious events and therefore increase patient safety. The preferred educational method for this type of training is simulation. Team training is not, however, used routinely in the hospital. In this paper, we describe a framework for the development of a team training course based on need assessment, learning objectives, educational methods including full-scale simulation and evaluations strategies. The use of this framework is illustrated by the present multiprofessional team training in advanced cardiac life support, trauma team training and neonatal resuscitation in Denmark. The challenges of addressing all aspects of team skills, the education of the facilitators, and establishment of evaluation strategies to document the effect of the different types of training on patient safety are discussed. PMID:15465962

The Implementation of Satellite Attitude Control System Software Using Object Oriented Design

NASA Technical Reports Server (NTRS)

Reid, W. Mark; Hansell, William; Phillips, Tom; Anderson, Mark O.; Drury, Derek

1998-01-01

NASA established the Small Explorer (SNMX) program in 1988 to provide frequent opportunities for highly focused and relatively inexpensive space science missions. The SMEX program has produced five satellites, three of which have been successfully launched. The remaining two spacecraft are scheduled for launch within the coming year. NASA has recently developed a prototype for the next generation Small Explorer spacecraft (SMEX-Lite). This paper describes the object-oriented design (OOD) of the SMEX-Lite Attitude Control System (ACS) software. The SMEX-Lite ACS is three-axis controlled and is capable of performing sub-arc-minute pointing. This paper first describes high level requirements governing the SMEX-Lite ACS software architecture. Next, the context in which the software resides is explained. The paper describes the principles of encapsulation, inheritance, and polymorphism with respect to the implementation of an ACS software system. This paper will also discuss the design of several ACS software components. Specifically, object-oriented designs are presented for sensor data processing, attitude determination, attitude control, and failure detection. Finally, this paper will address the establishment of the ACS Foundation Class (AFC) Library. The AFC is a large software repository, requiring a minimal amount of code modifications to produce ACS software for future projects.

Lessons Learned on Implementing Fault Detection, Isolation, and Recovery (FDIR) in a Ground Launch Environment

NASA Technical Reports Server (NTRS)

Ferrell, Bob A.; Lewis, Mark E.; Perotti, Jose M.; Brown, Barbara L.; Oostdyk, Rebecca L.; Goetz, Jesse W.

2010-01-01

This paper's main purpose is to detail issues and lessons learned regarding designing, integrating, and implementing Fault Detection Isolation and Recovery (FDIR) for Constellation Exploration Program (CxP) Ground Operations at Kennedy Space Center (KSC). Part of the0 overall implementation of National Aeronautics and Space Administration's (NASA's) CxP, FDIR is being implemented in three main components of the program (Ares, Orion, and Ground Operations/Processing). While not initially part of the design baseline for the CxP Ground Operations, NASA felt that FDIR is important enough to develop, that NASA's Exploration Systems Mission Directorate's (ESMD's) Exploration Technology Development Program (ETDP) initiated a task for it under their Integrated System Health Management (ISHM) research area. This task, referred to as the FDIIR project, is a multi-year multi-center effort. The primary purpose of the FDIR project is to develop a prototype and pathway upon which Fault Detection and Isolation (FDI) may be transitioned into the Ground Operations baseline. Currently, Qualtech Systems Inc (QSI) Commercial Off The Shelf (COTS) software products Testability Engineering and Maintenance System (TEAMS) Designer and TEAMS RDS/RT are being utilized in the implementation of FDI within the FDIR project. The TEAMS Designer COTS software product is being utilized to model the system with Functional Fault Models (FFMs). A limited set of systems in Ground Operations are being modeled by the FDIR project, and the entire Ares Launch Vehicle is being modeled under the Functional Fault Analysis (FFA) project at Marshall Space Flight Center (MSFC). Integration of the Ares FFMs and the Ground Processing FFMs is being done under the FDIR project also utilizing the TEAMS Designer COTS software product. One of the most significant challenges related to integration is to ensure that FFMs developed by different organizations can be integrated easily and without errors. Software Interface

Software Defined Radio with Parallelized Software Architecture

NASA Technical Reports Server (NTRS)

Heckler, Greg

2013-01-01

This software implements software-defined radio procession over multicore, multi-CPU systems in a way that maximizes the use of CPU resources in the system. The software treats each processing step in either a communications or navigation modulator or demodulator system as an independent, threaded block. Each threaded block is defined with a programmable number of input or output buffers; these buffers are implemented using POSIX pipes. In addition, each threaded block is assigned a unique thread upon block installation. A modulator or demodulator system is built by assembly of the threaded blocks into a flow graph, which assembles the processing blocks to accomplish the desired signal processing. This software architecture allows the software to scale effortlessly between single CPU/single-core computers or multi-CPU/multi-core computers without recompilation. NASA spaceflight and ground communications systems currently rely exclusively on ASICs or FPGAs. This software allows low- and medium-bandwidth (100 bps to approx.50 Mbps) software defined radios to be designed and implemented solely in C/C++ software, while lowering development costs and facilitating reuse and extensibility.

Software Defined Radio with Parallelized Software Architecture

NASA Technical Reports Server (NTRS)

Heckler, Greg

2013-01-01

This software implements software-defined radio procession over multi-core, multi-CPU systems in a way that maximizes the use of CPU resources in the system. The software treats each processing step in either a communications or navigation modulator or demodulator system as an independent, threaded block. Each threaded block is defined with a programmable number of input or output buffers; these buffers are implemented using POSIX pipes. In addition, each threaded block is assigned a unique thread upon block installation. A modulator or demodulator system is built by assembly of the threaded blocks into a flow graph, which assembles the processing blocks to accomplish the desired signal processing. This software architecture allows the software to scale effortlessly between single CPU/single-core computers or multi-CPU/multi-core computers without recompilation. NASA spaceflight and ground communications systems currently rely exclusively on ASICs or FPGAs. This software allows low- and medium-bandwidth (100 bps to .50 Mbps) software defined radios to be designed and implemented solely in C/C++ software, while lowering development costs and facilitating reuse and extensibility.

Cost-minimization model of a multidisciplinary antibiotic stewardship team based on a successful implementation on a urology ward of an academic hospital.

PubMed

Dik, Jan-Willem H; Hendrix, Ron; Friedrich, Alex W; Luttjeboer, Jos; Panday, Prashant Nannan; Wilting, Kasper R; Lo-Ten-Foe, Jerome R; Postma, Maarten J; Sinha, Bhanu

2015-01-01

In order to stimulate appropriate antimicrobial use and thereby lower the chances of resistance development, an Antibiotic Stewardship Team (A-Team) has been implemented at the University Medical Center Groningen, the Netherlands. Focus of the A-Team was a pro-active day 2 case-audit, which was financially evaluated here to calculate the return on investment from a hospital perspective. Effects were evaluated by comparing audited patients with a historic cohort with the same diagnosis-related groups. Based upon this evaluation a cost-minimization model was created that can be used to predict the financial effects of a day 2 case-audit. Sensitivity analyses were performed to deal with uncertainties. Finally, the model was used to financially evaluate the A-Team. One whole year including 114 patients was evaluated. Implementation costs were calculated to be €17,732, which represent total costs spent to implement this A-Team. For this specific patient group admitted to a urology ward and consulted on day 2 by the A-Team, the model estimated total savings of €60,306 after one year for this single department, leading to a return on investment of 5.9. The implemented multi-disciplinary A-Team performing a day 2 case-audit in the hospital had a positive return on investment caused by a reduced length of stay due to a more appropriate antibiotic therapy. Based on the extensive data analysis, a model of this intervention could be constructed. This model could be used by other institutions, using their own data to estimate the effects of a day 2 case-audit in their hospital.

Implementing Role-Changing Versus Time-Changing Innovations in Health Care: Differences in Helpfulness of Staff Improvement Teams, Management, and Network for Learning.

PubMed

Nembhard, Ingrid M; Morrow, Christopher T; Bradley, Elizabeth H

2015-12-01

Health care organizations often fail in their effort to implement care-improving innovations. This article differentiates role-changing innovations, altering what workers do, from time-changing innovations, altering when tasks are performed or for how long. We examine our hypothesis that the degree to which access to groups that can alter organizational learning--staff, management, and external network--facilitates implementation depends on innovation type. Our longitudinal study using ordinal logistic regression and survey data on 517 hospitals' implementation of evidence-based practices for treating heart attack confirmed our thesis for factors granting access to each group: improvement team's representativeness (of affected staff), senior management engagement, and network membership. Although team representativeness and network membership were positively associated with implementing role-changing practices, senior management engagement was not. In contrast, senior management engagement was positively associated with implementing time-changing practices, whereas team representativeness was not, and network membership was not unless there was limited management engagement. These findings advance implementation science by explaining mixed results across past studies: Nature of change for workers alters potential facilitators' effects on implementation. © The Author(s) 2015.

Unobtrusive Monitoring of Spaceflight Team Functioning

NASA Technical Reports Server (NTRS)

Maidel, Veronica; Stanton, Jeffrey M.

2010-01-01

This document contains a literature review suggesting that research on industrial performance monitoring has limited value in assessing, understanding, and predicting team functioning in the context of space flight missions. The review indicates that a more relevant area of research explores the effectiveness of teams and how team effectiveness may be predicted through the elicitation of individual and team mental models. Note that the mental models referred to in this literature typically reflect a shared operational understanding of a mission setting such as the cockpit controls and navigational indicators on a flight deck. In principle, however, mental models also exist pertaining to the status of interpersonal relations on a team, collective beliefs about leadership, success in coordination, and other aspects of team behavior and cognition. Pursuing this idea, the second part of this document provides an overview of available off-the-shelf products that might assist in extraction of mental models and elicitation of emotions based on an analysis of communicative texts among mission personnel. The search for text analysis software or tools revealed no available tools to enable extraction of mental models automatically, relying only on collected communication text. Nonetheless, using existing software to analyze how a team is functioning may be relevant for selection or training, when human experts are immediately available to analyze and act on the findings. Alternatively, if output can be sent to the ground periodically and analyzed by experts on the ground, then these software packages might be employed during missions as well. A demonstration of two text analysis software applications is presented. Another possibility explored in this document is the option of collecting biometric and proxemic measures such as keystroke dynamics and interpersonal distance in order to expose various individual or dyadic states that may be indicators or predictors of certain

Enhancing Collaborative Learning through Group Intelligence Software

NASA Astrophysics Data System (ADS)

Tan, Yin Leng; Macaulay, Linda A.

Employers increasingly demand not only academic excellence from graduates but also excellent interpersonal skills and the ability to work collaboratively in teams. This paper discusses the role of Group Intelligence software in helping to develop these higher order skills in the context of an enquiry based learning (EBL) project. The software supports teams in generating ideas, categorizing, prioritizing, voting and multi-criteria decision making and automatically generates a report of each team session. Students worked in a Group Intelligence lab designed to support both face to face and computer-mediated communication and employers provided feedback at two key points in the year long team project. Evaluation of the effectiveness of Group Intelligence software in collaborative learning was based on five key concepts of creativity, participation, productivity, engagement and understanding.

Absorbing Software Testing into the Scrum Method

NASA Astrophysics Data System (ADS)

Tuomikoski, Janne; Tervonen, Ilkka

In this paper we study, how to absorb software testing into the Scrum method. We conducted the research as an action research during the years 2007-2008 with three iterations. The result showed that testing can and even should be absorbed to the Scrum method. The testing team was merged into the Scrum teams. The teams can now deliver better working software in a shorter time, because testing keeps track of the progress of the development. Also the team spirit is higher, because the Scrum team members are committed to the same goal. The biggest change from test manager’s point of view was the organized Product Owner Team. Test manager don’t have testing team anymore, and in the future all the testing tasks have to be assigned through the Product Backlog.

Requirements Engineering in Building Climate Science Software

NASA Astrophysics Data System (ADS)

Batcheller, Archer L.

Software has an important role in supporting scientific work. This dissertation studies teams that build scientific software, focusing on the way that they determine what the software should do. These requirements engineering processes are investigated through three case studies of climate science software projects. The Earth System Modeling Framework assists modeling applications, the Earth System Grid distributes data via a web portal, and the NCAR (National Center for Atmospheric Research) Command Language is used to convert, analyze and visualize data. Document analysis, observation, and interviews were used to investigate the requirements-related work. The first research question is about how and why stakeholders engage in a project, and what they do for the project. Two key findings arise. First, user counts are a vital measure of project success, which makes adoption important and makes counting tricky and political. Second, despite the importance of quantities of users, a few particular "power users" develop a relationship with the software developers and play a special role in providing feedback to the software team and integrating the system into user practice. The second research question focuses on how project objectives are articulated and how they are put into practice. The team seeks to both build a software system according to product requirements but also to conduct their work according to process requirements such as user support. Support provides essential communication between users and developers that assists with refining and identifying requirements for the software. It also helps users to learn and apply the software to their real needs. User support is a vital activity for scientific software teams aspiring to create infrastructure. The third research question is about how change in scientific practice and knowledge leads to changes in the software, and vice versa. The "thickness" of a layer of software infrastructure impacts whether the

Developing a Multidisciplinary Team for Disorders of Sex Development: Planning, Implementation, and Operation Tools for Care Providers

PubMed Central

Moran, Mary Elizabeth; Karkazis, Katrina

2012-01-01

In the treatment of patients with disorders of sex development (DSD), multidisciplinary teams (MDTs) represent a new standard of care. While DSDs are too complex for care to be delivered effectively without specialized team management, these conditions are often considered to be too rare for their medical management to be a hospital priority. Many specialists involved in DSD care want to create a clinic or team, but there is no available guidance that bridges the gap between a group of like-minded DSD providers who want to improve care and the formation of a functional MDT. This is an important dilemma, and one with serious implications for the future of DSD care. If a network of multidisciplinary DSD teams is to be a reality, those directly involved in DSD care must be given the necessary program planning and team implementation tools. This paper offers a protocol and set of tools to meet this need. We present a 6-step process to team formation, and a sample set of tools that can be used to guide, develop, and evaluate a team throughout the course of its operation. PMID:22792098

Software Project Management and Measurement on the World-Wide-Web (WWW)

NASA Technical Reports Server (NTRS)

Callahan, John; Ramakrishnan, Sudhaka

1996-01-01

We briefly describe a system for forms-based, work-flow management that helps members of a software development team overcome geographical barriers to collaboration. Our system, called the Web Integrated Software Environment (WISE), is implemented as a World-Wide-Web service that allows for management and measurement of software development projects based on dynamic analysis of change activity in the workflow. WISE tracks issues in a software development process, provides informal communication between the users with different roles, supports to-do lists, and helps in software process improvement. WISE minimizes the time devoted to metrics collection and analysis by providing implicit delivery of messages between users based on the content of project documents. The use of a database in WISE is hidden from the users who view WISE as maintaining a personal 'to-do list' of tasks related to the many projects on which they may play different roles.

Implementing Software Safety in the NASA Environment

NASA Technical Reports Server (NTRS)

Wetherholt, Martha S.; Radley, Charles F.

1994-01-01

Until recently, NASA did not consider allowing computers total control of flight systems. Human operators, via hardware, have constituted the ultimate safety control. In an attempt to reduce costs, NASA has come to rely more and more heavily on computers and software to control space missions. (For example. software is now planned to control most of the operational functions of the International Space Station.) Thus the need for systematic software safety programs has become crucial for mission success. Concurrent engineering principles dictate that safety should be designed into software up front, not tested into the software after the fact. 'Cost of Quality' studies have statistics and metrics to prove the value of building quality and safety into the development cycle. Unfortunately, most software engineers are not familiar with designing for safety, and most safety engineers are not software experts. Software written to specifications which have not been safety analyzed is a major source of computer related accidents. Safer software is achieved step by step throughout the system and software life cycle. It is a process that includes requirements definition, hazard analyses, formal software inspections, safety analyses, testing, and maintenance. The greatest emphasis is placed on clearly and completely defining system and software requirements, including safety and reliability requirements. Unfortunately, development and review of requirements are the weakest link in the process. While some of the more academic methods, e.g. mathematical models, may help bring about safer software, this paper proposes the use of currently approved software methodologies, and sound software and assurance practices to show how, to a large degree, safety can be designed into software from the start. NASA's approach today is to first conduct a preliminary system hazard analysis (PHA) during the concept and planning phase of a project. This determines the overall hazard potential of

Maintaining Quality and Confidence in Open-Source, Evolving Software: Lessons Learned with PFLOTRAN

NASA Astrophysics Data System (ADS)

Frederick, J. M.; Hammond, G. E.

2017-12-01

Software evolution in an open-source framework poses a major challenge to a geoscientific simulator, but when properly managed, the pay-off can be enormous for both the developers and the community at large. Developers must juggle implementing new scientific process models, adopting increasingly efficient numerical methods and programming paradigms, changing funding sources (or total lack of funding), while also ensuring that legacy code remains functional and reported bugs are fixed in a timely manner. With robust software engineering and a plan for long-term maintenance, a simulator can evolve over time incorporating and leveraging many advances in the computational and domain sciences. In this positive light, what practices in software engineering and code maintenance can be employed within open-source development to maximize the positive aspects of software evolution and community contributions while minimizing its negative side effects? This presentation will discusses steps taken in the development of PFLOTRAN (www.pflotran.org), an open source, massively parallel subsurface simulator for multiphase, multicomponent, and multiscale reactive flow and transport processes in porous media. As PFLOTRAN's user base and development team continues to grow, it has become increasingly important to implement strategies which ensure sustainable software development while maintaining software quality and community confidence. In this presentation, we will share our experiences and "lessons learned" within the context of our open-source development framework and community engagement efforts. Topics discussed will include how we've leveraged both standard software engineering principles, such as coding standards, version control, and automated testing, as well unique advantages of object-oriented design in process model coupling, to ensure software quality and confidence. We will also be prepared to discuss the major challenges faced by most open-source software teams, such

An Investigation of Agility Issues in Scrum Teams Using Agility Indicators

NASA Astrophysics Data System (ADS)

Pikkarainen, Minna; Wang, Xiaofeng

Agile software development methods have emerged and become increasingly popular in recent years; yet the issues encountered by software development teams that strive to achieve agility using agile methods are yet to be explored systematically. Built upon a previous study that has established a set of indicators of agility, this study investigates what issues are manifested in software development teams using agile methods. It is focussed on Scrum teams particularly. In other words, the goal of the chapter is to evaluate Scrum teams using agility indicators and therefore to further validate previously presented agility indicators within the additional cases. A multiple case study research method is employed. The findings of the study reveal that the teams using Scrum do not necessarily achieve agility in terms of team autonomy, sharing, stability and embraced uncertainty. The possible reasons include previous organizational plan-driven culture, resistance towards the Scrum roles and changing resources.

Using failure mode and effects analysis to plan implementation of smart i.v. pump technology.

PubMed

Wetterneck, Tosha B; Skibinski, Kathleen A; Roberts, Tanita L; Kleppin, Susan M; Schroeder, Mark E; Enloe, Myra; Rough, Steven S; Hundt, Ann Schoofs; Carayon, Pascale

2006-08-15

Failure mode and effects analysis (FMEA) was used to evaluate a smart i.v. pump as it was implemented into a redesigned medication-use process. A multidisciplinary team conducted a FMEA to guide the implementation of a smart i.v. pump that was designed to prevent pump programming errors. The smart i.v. pump was equipped with a dose-error reduction system that included a pre-defined drug library in which dosage limits were set for each medication. Monitoring for potential failures and errors occurred for three months postimplementation of FMEA. Specific measures were used to determine the success of the actions that were implemented as a result of the FMEA. The FMEA process at the hospital identified key failure modes in the medication process with the use of the old and new pumps, and actions were taken to avoid errors and adverse events. I.V. pump software and hardware design changes were also recommended. Thirteen of the 18 failure modes reported in practice after pump implementation had been identified by the team. A beneficial outcome of FMEA was the development of a multidisciplinary team that provided the infrastructure for safe technology implementation and effective event investigation after implementation. With the continual updating of i.v. pump software and hardware after implementation, FMEA can be an important starting place for safe technology choice and implementation and can produce site experts to follow technology and process changes over time. FMEA was useful in identifying potential problems in the medication-use process with the implementation of new smart i.v. pumps. Monitoring for system failures and errors after implementation remains necessary.

A performance improvement plan to increase nurse adherence to use of medication safety software.

PubMed

Gavriloff, Carrie

2012-08-01

Nurses can protect patients receiving intravenous (IV) medication by using medication safety software to program "smart" pumps to administer IV medications. After a patient safety event identified inconsistent use of medication safety software by nurses, a performance improvement team implemented the Deming Cycle performance improvement methodology. The combined use of improved direct care nurse communication, programming strategies, staff education, medication safety champions, adherence monitoring, and technology acquisition resulted in a statistically significant (p < .001) increase in nurse adherence to using medication safety software from 28% to above 85%, exceeding national benchmark adherence rates (Cohen, Cooke, Husch & Woodley, 2007; Carefusion, 2011). Copyright © 2012 Elsevier Inc. All rights reserved.

Speeding Up Team Learning.

ERIC Educational Resources Information Center

Edmondson, Amy; Bohmer, Richard; Pisano, Gary

2001-01-01

A study of 16 cardiac surgery teams looked at how the teams adapted to new ways of working. The challenge of team management is to implement new processes as quickly as possible. Steps for creating a learning team include selecting a mix of skills and expertise, framing the challenge, and creating an environment of psychological safety. (JOW)

The human side of lean teams.

PubMed

Wackerbarth, Sarah B; Strawser-Srinath, Jamie R; Conigliaro, Joseph C

2015-05-01

Organizations use lean principles to increase quality and decrease costs. Lean projects require an understanding of systems-wide processes and utilize interdisciplinary teams. Most lean tools are straightforward, and the biggest barrier to successful implementation is often development of the team aspect of the lean approach. The purpose of this article is to share challenges experienced by a lean team charged with improving a hospital discharge process. Reflection on the experience provides an opportunity to highlight lessons from The Team Handbook by Peter Scholtes and colleagues. To improve the likelihood that process improvement initiatives, including lean projects, will be successful, organizations should consider providing training in organizational change principles and team building. The authors' lean team learned these lessons the hard way. Despite the challenges, the team successfully implemented changes throughout the organization that have had a positive impact. Training to understand the psychology of change might have decreased the resistance faced in implementing these changes. © 2014 by the American College of Medical Quality.

Distributed teaming on JPL projects

NASA Technical Reports Server (NTRS)

Baroff, L. E.

2002-01-01

This paper addresses structures, actions and technologies that contribute to real team development of a distributed team, and the leadership skills and tools that are used to implement that team development.

Software algorithm and hardware design for real-time implementation of new spectral estimator

PubMed Central

2014-01-01

Background Real-time spectral analyzers can be difficult to implement for PC computer-based systems because of the potential for high computational cost, and algorithm complexity. In this work a new spectral estimator (NSE) is developed for real-time analysis, and compared with the discrete Fourier transform (DFT). Method Clinical data in the form of 216 fractionated atrial electrogram sequences were used as inputs. The sample rate for acquisition was 977 Hz, or approximately 1 millisecond between digital samples. Real-time NSE power spectra were generated for 16,384 consecutive data points. The same data sequences were used for spectral calculation using a radix-2 implementation of the DFT. The NSE algorithm was also developed for implementation as a real-time spectral analyzer electronic circuit board. Results The average interval for a single real-time spectral calculation in software was 3.29 μs for NSE versus 504.5 μs for DFT. Thus for real-time spectral analysis, the NSE algorithm is approximately 150× faster than the DFT. Over a 1 millisecond sampling period, the NSE algorithm had the capability to spectrally analyze a maximum of 303 data channels, while the DFT algorithm could only analyze a single channel. Moreover, for the 8 second sequences, the NSE spectral resolution in the 3-12 Hz range was 0.037 Hz while the DFT spectral resolution was only 0.122 Hz. The NSE was also found to be implementable as a standalone spectral analyzer board using approximately 26 integrated circuits at a cost of approximately $500. The software files used for analysis are included as a supplement, please see the Additional files 1 and 2. Conclusions The NSE real-time algorithm has low computational cost and complexity, and is implementable in both software and hardware for 1 millisecond updates of multichannel spectra. The algorithm may be helpful to guide radiofrequency catheter ablation in real time. PMID:24886214

Spacelab user implementation assessment study (software requirements analysis). Volume 1: Executive study

NASA Technical Reports Server (NTRS)

1976-01-01

The primary objective of this study was to develop an integrated approach for the development, implementation, and utilization of all software that is required to efficiently and cost-effectively support advanced technology laboratory flight and ground operations. It was recognized that certain aspects of the operations would be mandatory computerized services; computerization of other aspects would be optional. Thus, the analyses encompassed not only alternate computer utilization and implementations but trade studies of the programmatic effects of non-computerized versus computerized approaches to the operations. A general overview of the study is presented.

Implementation of an OAIS Repository Using Free, Open Source Software

NASA Astrophysics Data System (ADS)

Flathers, E.; Gessler, P. E.; Seamon, E.

2015-12-01

The Northwest Knowledge Network (NKN) is a regional data repository located at the University of Idaho that focuses on the collection, curation, and distribution of research data. To support our home institution and others in the region, we offer services to researchers at all stages of the data lifecycle—from grant application and data management planning to data distribution and archive. In this role, we recognize the need to work closely with other data management efforts at partner institutions and agencies, as well as with larger aggregation efforts such as our state geospatial data clearinghouses, data.gov, DataONE, and others. In the past, one of our challenges with monolithic, prepackaged data management solutions is that customization can be difficult to implement and maintain, especially as new versions of the software are released that are incompatible with our local codebase. Our solution is to break the monolith up into its constituent parts, which offers us several advantages. First, any customizations that we make are likely to fall into areas that can be accessed through Application Program Interfaces (API) that are likely to remain stable over time, so our code stays compatible. Second, as components become obsolete or insufficient to meet new demands that arise, we can replace the individual components with minimal effect on the rest of the infrastructure, causing less disruption to operations. Other advantages include increased system reliability, staggered rollout of new features, enhanced compatibility with legacy systems, reduced dependence on a single software company as a point of failure, and the separation of development into manageable tasks. In this presentation, we describe our application of the Service Oriented Architecture (SOA) design paradigm to assemble a data repository that conforms to the Open Archival Information System (OAIS) Reference Model primarily using a collection of free and open-source software. We detail the design

The Implementation of Satellite Control System Software Using Object Oriented Design

NASA Technical Reports Server (NTRS)

Anderson, Mark O.; Reid, Mark; Drury, Derek; Hansell, William; Phillips, Tom

1998-01-01

NASA established the Small Explorer (SMEX) program in 1988 to provide frequent opportunities for highly focused and relatively inexpensive space science missions that can be launched into low earth orbit by small expendable vehicles. The development schedule for each SMEX spacecraft was three years from start to launch. The SMEX program has produced five satellites; Solar Anomalous and Magnetospheric Particle Explorer (SAMPEX), Fast Auroral Snapshot Explorer (FAST), Submillimeter Wave Astronomy Satellite (SWAS), Transition Region and Coronal Explorer (TRACE) and Wide-Field Infrared Explorer (WIRE). SAMPEX and FAST are on-orbit, TRACE is scheduled to be launched in April of 1998, WIRE is scheduled to be launched in September of 1998, and SWAS is scheduled to be launched in January of 1999. In each of these missions, the Attitude Control System (ACS) software was written using a modular procedural design. Current program goals require complete spacecraft development within 18 months. This requirement has increased pressure to write reusable flight software. Object-Oriented Design (OOD) offers the constructs for developing an application that only needs modification for mission unique requirements. This paper describes the OOD that was used to develop the SMEX-Lite ACS software. The SMEX-Lite ACS is three-axis controlled, momentum stabilized, and is capable of performing sub-arc-minute pointing. The paper first describes the high level requirements which governed the architecture of the SMEX-Lite ACS software. Next, the context in which the software resides is explained. The paper describes the benefits of encapsulation, inheritance and polymorphism with respect to the implementation of an ACS software system. This paper will discuss the design of several software components that comprise the ACS software. Specifically, Object-Oriented designs are presented for sensor data processing, attitude control, attitude determination and failure detection. The paper addresses

A Comparison Study and Software Implementation of NORDA Ocean Models.

DTIC Science & Technology

1980-10-08

L01?C07 ’EEEEElshhhh A COMPARISON STUDY AND SOFTWARE IMPLEMENTATION OF NORDA OCEAN MODELS J&IEA m/ MST* f-....~ cre mx IRSD~I?( J 300 Unicorn Park...34- NOO-79- 741 9. PERFORMING ORGANIZATION NAME AND ADDRESS 10. PROGRAM ELEMENT. PROJECT, TASK AREA 6 WORK UNIT NUMBERSJAYC0, 300 Unicorn Park Drive...before another execution of the energetics program, move them back to disk. Note that the outputs of the preprocessor reside on disk, they should not be

PPM Receiver Implemented in Software

NASA Technical Reports Server (NTRS)

Gray, Andrew; Kang, Edward; Lay, Norman; Vilnrotter, Victor; Srinivasan, Meera; Lee, Clement

2010-01-01

A computer program has been written as a tool for developing optical pulse-position- modulation (PPM) receivers in which photodetector outputs are fed to analog-to-digital converters (ADCs) and all subsequent signal processing is performed digitally. The program can be used, for example, to simulate an all-digital version of the PPM receiver described in Parallel Processing of Broad-Band PPM Signals (NPO-40711), which appears elsewhere in this issue of NASA Tech Briefs. The program can also be translated into a design for digital PPM receiver hardware. The most notable innovation embodied in the software and the underlying PPM-reception concept is a digital processing subsystem that performs synchronization of PPM time slots, even though the digital processing is, itself, asynchronous in the sense that no attempt is made to synchronize it with the incoming optical signal a priori and there is no feedback to analog signal processing subsystems or ADCs. Functions performed by the software receiver include time-slot synchronization, symbol synchronization, coding preprocessing, and diagnostic functions. The program is written in the MATLAB and Simulink software system. The software receiver is highly parameterized and, hence, programmable: for example, slot- and symbol-synchronization filters have programmable bandwidths.

A Knowledge Management Approach to Support Software Process Improvement Implementation Initiatives

NASA Astrophysics Data System (ADS)

Montoni, Mariano Angel; Cerdeiral, Cristina; Zanetti, David; Cavalcanti da Rocha, Ana Regina

The success of software process improvement (SPI) implementation initiatives depends fundamentally of the strategies adopted to support the execution of such initiatives. Therefore, it is essential to define adequate SPI implementation strategies aiming to facilitate the achievement of organizational business goals and to increase the benefits of process improvements. The objective of this work is to present an approach to support the execution of SPI implementation initiatives. We also describe a methodology applied to capture knowledge related to critical success factors that influence SPI initiatives. This knowledge was used to define effective SPI strategies aiming to increase the success of SPI initiatives coordinated by a specific SPI consultancy organization. This work also presents the functionalities of a set of tools integrated in a process-centered knowledge management environment, named CORE-KM, customized to support the presented approach.

Automated Software Acceleration in Programmable Logic for an Efficient NFFT Algorithm Implementation: A Case Study.

PubMed

Rodríguez, Manuel; Magdaleno, Eduardo; Pérez, Fernando; García, Cristhian

2017-03-28

Non-equispaced Fast Fourier transform (NFFT) is a very important algorithm in several technological and scientific areas such as synthetic aperture radar, computational photography, medical imaging, telecommunications, seismic analysis and so on. However, its computation complexity is high. In this paper, we describe an efficient NFFT implementation with a hardware coprocessor using an All-Programmable System-on-Chip (APSoC). This is a hybrid device that employs an Advanced RISC Machine (ARM) as Processing System with Programmable Logic for high-performance digital signal processing through parallelism and pipeline techniques. The algorithm has been coded in C language with pragma directives to optimize the architecture of the system. We have used the very novel Software Develop System-on-Chip (SDSoC) evelopment tool that simplifies the interface and partitioning between hardware and software. This provides shorter development cycles and iterative improvements by exploring several architectures of the global system. The computational results shows that hardware acceleration significantly outperformed the software based implementation.

Automated Software Acceleration in Programmable Logic for an Efficient NFFT Algorithm Implementation: A Case Study

PubMed Central

Rodríguez, Manuel; Magdaleno, Eduardo; Pérez, Fernando; García, Cristhian

2017-01-01

Non-equispaced Fast Fourier transform (NFFT) is a very important algorithm in several technological and scientific areas such as synthetic aperture radar, computational photography, medical imaging, telecommunications, seismic analysis and so on. However, its computation complexity is high. In this paper, we describe an efficient NFFT implementation with a hardware coprocessor using an All-Programmable System-on-Chip (APSoC). This is a hybrid device that employs an Advanced RISC Machine (ARM) as Processing System with Programmable Logic for high-performance digital signal processing through parallelism and pipeline techniques. The algorithm has been coded in C language with pragma directives to optimize the architecture of the system. We have used the very novel Software Develop System-on-Chip (SDSoC) evelopment tool that simplifies the interface and partitioning between hardware and software. This provides shorter development cycles and iterative improvements by exploring several architectures of the global system. The computational results shows that hardware acceleration significantly outperformed the software based implementation. PMID:28350358

A learning curve-based method to implement multifunctional work teams in the Brazilian footwear sector.

PubMed

Guimarães, L B de M; Anzanello, M J; Renner, J S

2012-05-01

This paper presents a method for implementing multifunctional work teams in a footwear company that followed the Taylor/Ford system for decades. The suggested framework first applies a Learning Curve (LC) modeling to assess whether rotation between tasks of different complexities affects workers' learning rate and performance. Next, the Macroergonomic Work Analysis (MA) method (Guimarães, 1999, 2009) introduces multifunctional principles in work teams towards workers' training and resources improvement. When applied to a pilot line consisting of 100 workers, the intervention-reduced work related accidents in 80%, absenteeism in 45.65%, and eliminated work related musculoskeletal disorders (WMSD), medical consultations, and turnover. Further, the output rate of the multifunctional team increased average 3% compared to the production rate of the regular lines following the Taylor/Ford system (with the same shoe model being manufactured), while the rework and spoilage rates were reduced 85% and 69%, respectively. Copyright © 2011 Elsevier Ltd and The Ergonomics Society. All rights reserved.

Cognon Neural Model Software Verification and Hardware Implementation Design

NASA Astrophysics Data System (ADS)

Haro Negre, Pau

Little is known yet about how the brain can recognize arbitrary sensory patterns within milliseconds using neural spikes to communicate information between neurons. In a typical brain there are several layers of neurons, with each neuron axon connecting to ˜104 synapses of neurons in an adjacent layer. The information necessary for cognition is contained in theses synapses, which strengthen during the learning phase in response to newly presented spike patterns. Continuing on the model proposed in "Models for Neural Spike Computation and Cognition" by David H. Staelin and Carl H. Staelin, this study seeks to understand cognition from an information theoretic perspective and develop potential models for artificial implementation of cognition based on neuronal models. To do so we focus on the mathematical properties and limitations of spike-based cognition consistent with existing neurological observations. We validate the cognon model through software simulation and develop concepts for an optical hardware implementation of a network of artificial neural cognons.

The ALMA software architecture

NASA Astrophysics Data System (ADS)

Schwarz, Joseph; Farris, Allen; Sommer, Heiko

2004-09-01

The software for the Atacama Large Millimeter Array (ALMA) is being developed by many institutes on two continents. The software itself will function in a distributed environment, from the 0.5-14 kmbaselines that separate antennas to the larger distances that separate the array site at the Llano de Chajnantor in Chile from the operations and user support facilities in Chile, North America and Europe. Distributed development demands 1) interfaces that allow separated groups to work with minimal dependence on their counterparts at other locations; and 2) a common architecture to minimize duplication and ensure that developers can always perform similar tasks in a similar way. The Container/Component model provides a blueprint for the separation of functional from technical concerns: application developers concentrate on implementing functionality in Components, which depend on Containers to provide them with services such as access to remote resources, transparent serialization of entity objects to XML, logging, error handling and security. Early system integrations have verified that this architecture is sound and that developers can successfully exploit its features. The Containers and their services are provided by a system-orienteddevelopment team as part of the ALMA Common Software (ACS), middleware that is based on CORBA.

The Feasibility of Implementing Multicommand Software Functions on a Microcomputer Network.

DTIC Science & Technology

1979-10-01

studies 20 ABSTRACT fConllnuo on revete &Ide it necessary and Identify by block number) ’This report presents the results of a study of design...considerations for hybrid monitor systems for distributed microcomputer networks. The objective of the study was to determine the feasibility of such monitor...Management Informa- tion and Computer Sciences. The study was one task on a project bentitled "The Feasibility of Implementing Multicommand Software

Improving Care Teams' Functioning: Recommendations from Team Science.

PubMed

Fiscella, Kevin; Mauksch, Larry; Bodenheimer, Thomas; Salas, Eduardo

2017-07-01

Team science has been applied to many sectors including health care. Yet there has been relatively little attention paid to the application of team science to developing and sustaining primary care teams. Application of team science to primary care requires adaptation of core team elements to different types of primary care teams. Six elements of teams are particularly relevant to primary care: practice conditions that support or hinder effective teamwork; team cognition, including shared understanding of team goals, roles, and how members will work together as a team; leadership and coaching, including mutual feedback among members that promotes teamwork and moves the team closer to achieving its goals; cooperation supported by an emotionally safe climate that supports expression and resolution of conflict and builds team trust and cohesion; coordination, including adoption of processes that optimize efficient performance of interdependent activities among team members; and communication, particularly regular, recursive team cycles involving planning, action, and debriefing. These six core elements are adapted to three prototypical primary care teams: teamlets, health coaching, and complex care coordination. Implementation of effective team-based models in primary care requires adaptation of core team science elements coupled with relevant, practical training and organizational support, including adequate time to train, plan, and debrief. Training should be based on assessment of needs and tasks and the use of simulations and feedback, and it should extend to live action. Teamlets represent a potential launch point for team development and diffusion of teamwork principles within primary care practices. Copyright © 2017 The Joint Commission. Published by Elsevier Inc. All rights reserved.

How Do Staff Perceive Schoolwide Positive Behavior Supports? Implications for Teams in Planning and Implementing Schools

ERIC Educational Resources Information Center

Feuerborn, Laura L.; Tyre, Ashli D.

2016-01-01

Schoolwide Positive Behavior Support (SWPBS) offers an alternative to reactive and exclusionary school discipline practices. However, the shift to SWPBS requires substantial change in the practices of staff, and many leadership teams struggle to rally staff support for implementation. With a more thorough understanding of staff perceptions, level…

Implementation of a software for REmote COMparison of PARticlE and photon treatment plans: ReCompare.

PubMed

Löck, Steffen; Roth, Klaus; Skripcak, Tomas; Worbs, Mario; Helmbrecht, Stephan; Jakobi, Annika; Just, Uwe; Krause, Mechthild; Baumann, Michael; Enghardt, Wolfgang; Lühr, Armin

2015-09-01

To guarantee equal access to optimal radiotherapy, a concept of patient assignment to photon or particle radiotherapy using remote treatment plan exchange and comparison - ReCompare - was proposed. We demonstrate the implementation of this concept and present its clinical applicability. The ReCompare concept was implemented using a client-server based software solution. A clinical workflow for the remote treatment plan exchange and comparison was defined. The steps required by the user and performed by the software for a complete plan transfer were described and an additional module for dose-response modeling was added. The ReCompare software was successfully tested in cooperation with three external partner clinics and worked meeting all required specifications. It was compatible with several standard treatment planning systems, ensured patient data protection, and integrated in the clinical workflow. The ReCompare software can be applied to support non-particle radiotherapy institutions with the patient-specific treatment decision on the optimal irradiation modality by remote treatment plan exchange and comparison. Copyright © 2015. Published by Elsevier GmbH.

A Bibliography of the Personal Software Process (PSP) and the Team Software Process (TSP)

DTIC Science & Technology

2009-10-01

Postmortem.‖ Proceedings of the TSP Symposium (September 2007). http://www.sei.cmu.edu/tspsymposium/ Rickets , Chris; Lindeman, Robert; & Hodgins, Brad... Rickets , Chris A. ―A TSP Software Maintenance Life Cycle.‖ CrossTalk (March 2005). Rozanc, I. & Mahnic, V. ―Teaching Software Quality with Emphasis on PSP

Implementing critical pathways and a multidisciplinary team approach to cardiovascular disease management.

PubMed

Peterson, Eric D; Albert, Nancy M; Amin, Alpesh; Patterson, J Herbert; Fonarow, Gregg C

2008-09-08

According to several medical registries, there is a need to improve the care of post-myocardial infarction (MI) patients, especially those with left ventricular dysfunction (LVD) and heart failure. This can potentially be achieved by implementing disease management programs, which include critical pathways, patient education, and multidisciplinary hospital teams. Currently, algorithms for critical pathways, including discharge processes, are lacking for post-MI LVD patients. Such schemes can increase the use of evidence-based medicines proved to reduce mortality. Educational programs are aimed at increasing patients' awareness of their condition, promoting medication compliance, and encouraging the adoption of healthy behaviors; such programs have been shown to be effective in improving outcomes of post-MI LVD patients. Reductions in all-cause hospitalizations and medical costs as well as improved survival rates have been observed when a multidisciplinary team (a nurse, a pharmacist, and a hospitalist) is engaged in patient care. In addition, the use of the "pay for performance" method, which can be advantageous for patients, physicians, and hospitals, may potentially improve the care of post-MI patients with LVD.

Design and Multicentric Implementation of a Generic Software Architecture for Patient Recruitment Systems Re-Using Existing HIS Tools and Routine Patient Data

PubMed Central

Trinczek, B.; Köpcke, F.; Leusch, T.; Majeed, R.W.; Schreiweis, B.; Wenk, J.; Bergh, B.; Ohmann, C.; Röhrig, R.; Prokosch, H.U.; Dugas, M.

2014-01-01

Summary Objective (1) To define features and data items of a Patient Recruitment System (PRS); (2) to design a generic software architecture of such a system covering the requirements; (3) to identify implementation options available within different Hospital Information System (HIS) environments; (4) to implement five PRS following the architecture and utilizing the implementation options as proof of concept. Methods Existing PRS were reviewed and interviews with users and developers conducted. All reported PRS features were collected and prioritized according to their published success and user’s request. Common feature sets were combined into software modules of a generic software architecture. Data items to process and transfer were identified for each of the modules. Each site collected implementation options available within their respective HIS environment for each module, provided a prototypical implementation based on available implementation possibilities and supported the patient recruitment of a clinical trial as a proof of concept. Results 24 commonly reported and requested features of a PRS were identified, 13 of them prioritized as being mandatory. A UML version 2 based software architecture containing 5 software modules covering these features was developed. 13 data item groups processed by the modules, thus required to be available electronically, have been identified. Several implementation options could be identified for each module, most of them being available at multiple sites. Utilizing available tools, a PRS could be implemented in each of the five participating German university hospitals. Conclusion A set of required features and data items of a PRS has been described for the first time. The software architecture covers all features in a clear, well-defined way. The variety of implementation options and the prototypes show that it is possible to implement the given architecture in different HIS environments, thus enabling more sites to

Design and multicentric implementation of a generic software architecture for patient recruitment systems re-using existing HIS tools and routine patient data.

PubMed

Trinczek, B; Köpcke, F; Leusch, T; Majeed, R W; Schreiweis, B; Wenk, J; Bergh, B; Ohmann, C; Röhrig, R; Prokosch, H U; Dugas, M

2014-01-01

(1) To define features and data items of a Patient Recruitment System (PRS); (2) to design a generic software architecture of such a system covering the requirements; (3) to identify implementation options available within different Hospital Information System (HIS) environments; (4) to implement five PRS following the architecture and utilizing the implementation options as proof of concept. Existing PRS were reviewed and interviews with users and developers conducted. All reported PRS features were collected and prioritized according to their published success and user's request. Common feature sets were combined into software modules of a generic software architecture. Data items to process and transfer were identified for each of the modules. Each site collected implementation options available within their respective HIS environment for each module, provided a prototypical implementation based on available implementation possibilities and supported the patient recruitment of a clinical trial as a proof of concept. 24 commonly reported and requested features of a PRS were identified, 13 of them prioritized as being mandatory. A UML version 2 based software architecture containing 5 software modules covering these features was developed. 13 data item groups processed by the modules, thus required to be available electronically, have been identified. Several implementation options could be identified for each module, most of them being available at multiple sites. Utilizing available tools, a PRS could be implemented in each of the five participating German university hospitals. A set of required features and data items of a PRS has been described for the first time. The software architecture covers all features in a clear, well-defined way. The variety of implementation options and the prototypes show that it is possible to implement the given architecture in different HIS environments, thus enabling more sites to successfully support patient recruitment in

Technique adaptation, strategic replanning, and team learning during implementation of MR-guided brachytherapy for cervical cancer.

PubMed

Skliarenko, Julia; Carlone, Marco; Tanderup, Kari; Han, Kathy; Beiki-Ardakani, Akbar; Borg, Jette; Chan, Kitty; Croke, Jennifer; Rink, Alexandra; Simeonov, Anna; Ujaimi, Reem; Xie, Jason; Fyles, Anthony; Milosevic, Michael

MR-guided brachytherapy (MRgBT) with interstitial needles is associated with improved outcomes in cervical cancer patients. However, there are implementation barriers, including magnetic resonance (MR) access, practitioner familiarity/comfort, and efficiency. This study explores a graded MRgBT implementation strategy that included the adaptive use of needles, strategic use of MR imaging/planning, and team learning. Twenty patients with cervical cancer were treated with high-dose-rate MRgBT (28 Gy in four fractions, two insertions, daily MR imaging/planning). A tandem/ring applicator alone was used for the first insertion in most patients. Needles were added for the second insertion based on evaluation of the initial dosimetry. An interdisciplinary expert team reviewed and discussed the MR images and treatment plans. Dosimetry-trigger technique adaptation with the addition of needles for the second insertion improved target coverage in all patients with suboptimal dosimetry initially without compromising organ-at-risk (OAR) sparing. Target and OAR planning objectives were achieved in most patients. There were small or no systematic differences in tumor or OAR dosimetry between imaging/planning once per insertion vs. daily and only small random variations. Peer review and discussion of images, contours, and plans promoted learning and process development. Technique adaptation based on the initial dosimetry is an efficient approach to implementing MRgBT while gaining comfort with the use of needles. MR imaging and planning once per insertion is safe in most patients as long as applicator shifts, and large anatomical changes are excluded. Team learning is essential to building individual and programmatic competencies. Copyright © 2017 American Brachytherapy Society. Published by Elsevier Inc. All rights reserved.

Implementing reusable software components for SNOMED CT diagram and expression concept representations.

PubMed

Bánfai, Balázs; Porció, Roland; Kovács, Tibor

2014-01-01

SNOMED CT is a vital component in the future of semantic interoperability in healthcare as it provides the meaning to EHRs via its semantically rich, controlled terminology. Communicating the concepts of this terminology to both humans and machines is crucial therefore formal guidelines for diagram and expression representations have been developed by the curators of SNOMED CT. This paper presents a novel, model-based approach to implementing these guidelines that allows simultaneous editing of a concept via both diagram and expression editors. The implemented extensible software component can be embedded both both desktop and web applications.

Support of Herschel Key Programme Teams at the NASA Herschel Science Center

NASA Astrophysics Data System (ADS)

Shupe, David L.; Appleton, P. N.; Ardila, D.; Bhattacharya, B.; Mei, Y.; Morris, P.; Rector, J.; NHSC Team

2010-01-01

The first science data from the Herschel Space Observatory were distributed to Key Programme teams in September 2009. This poster describes a number of resources that have been developed by the NASA Herschel Science Center (NHSC) to support the first users of the observatory. The NHSC webpages and Helpdesk serve as the starting point for information and queries from the US community. Details about the use of the Herschel Common Science Software can be looked up in the Helpdesk Knowledgebase. The capability of real-time remote support through desktop sharing has been implemented. The NHSC continues to host workshops on data analysis and observation planning. Key Programme teams have been provided Wiki sites upon request for their team's private use and for sharing information with other teams. A secure data storage area is in place for troubleshooting purposes and for use by visitors. The NHSC draws upon close working relationships with Instrument Control Centers and the Herschel Science Center in Madrid in order to have the necessary expertise on hand to assist Herschel observers, including both Key Programme teams and respondents to upcoming open time proposal calls.

The Elements of an Effective Software Development Plan - Software Development Process Guidebook

DTIC Science & Technology

2011-11-11

standards and practices required for all XMPL software development. This SDP implements the <corporate> Standard Software Process (SSP). as tailored...Developing and integrating reusable software products • Approach to managing COTS/Reuse software implementation • COTS/Reuse software selection...final selection and submit to change board for approval MAINTENANCE Monitor current products for obsolescence or end of support Track new

Successful strategies in implementing a multidisciplinary team working in the care of patients with cancer: an overview and synthesis of the available literature.

PubMed

Soukup, Tayana; Lamb, Benjamin W; Arora, Sonal; Darzi, Ara; Sevdalis, Nick; Green, James Sa

2018-01-01

In many health care systems globally, cancer care is driven by multidisciplinary cancer teams (MDTs). A large number of studies in the past few years and across different literature have been performed to better understand how these teams work and how they manage patient care. The aim of our literature review is to synthesize current scientific and clinical understanding on cancer MDTs and their organization; this, in turn, should provide an up-to-date summary of the current knowledge that those planning or leading cancer services can use as a guide for service implementation or improvement. We describe the characteristics of an effective MDT and factors that influence how these teams work. A range of factors pertaining to teamwork, availability of patient information, leadership, team and meeting management, and workload can affect how well MDTs are implemented within patient care. We also review how to assess and improve these teams. We present a range of instruments designed to be used with cancer MDTs - including observational tools, self-assessments, and checklists. We conclude with a practical outline of what appears to be the best practices to implement (Dos) and practices to avoid (Don'ts) when setting up MDT-driven cancer care.

Successful strategies in implementing a multidisciplinary team working in the care of patients with cancer: an overview and synthesis of the available literature

PubMed Central

Soukup, Tayana; Lamb, Benjamin W; Arora, Sonal; Darzi, Ara; Sevdalis, Nick; Green, James SA

2018-01-01

In many health care systems globally, cancer care is driven by multidisciplinary cancer teams (MDTs). A large number of studies in the past few years and across different literature have been performed to better understand how these teams work and how they manage patient care. The aim of our literature review is to synthesize current scientific and clinical understanding on cancer MDTs and their organization; this, in turn, should provide an up-to-date summary of the current knowledge that those planning or leading cancer services can use as a guide for service implementation or improvement. We describe the characteristics of an effective MDT and factors that influence how these teams work. A range of factors pertaining to teamwork, availability of patient information, leadership, team and meeting management, and workload can affect how well MDTs are implemented within patient care. We also review how to assess and improve these teams. We present a range of instruments designed to be used with cancer MDTs – including observational tools, self-assessments, and checklists. We conclude with a practical outline of what appears to be the best practices to implement (Dos) and practices to avoid (Don’ts) when setting up MDT-driven cancer care. PMID:29403284

Pre-Hardware Optimization of Spacecraft Image Processing Software Algorithms and Hardware Implementation

NASA Technical Reports Server (NTRS)

Kizhner, Semion; Flatley, Thomas P.; Hestnes, Phyllis; Jentoft-Nilsen, Marit; Petrick, David J.; Day, John H. (Technical Monitor)

2001-01-01

Spacecraft telemetry rates have steadily increased over the last decade presenting a problem for real-time processing by ground facilities. This paper proposes a solution to a related problem for the Geostationary Operational Environmental Spacecraft (GOES-8) image processing application. Although large super-computer facilities are the obvious heritage solution, they are very costly, making it imperative to seek a feasible alternative engineering solution at a fraction of the cost. The solution is based on a Personal Computer (PC) platform and synergy of optimized software algorithms and re-configurable computing hardware technologies, such as Field Programmable Gate Arrays (FPGA) and Digital Signal Processing (DSP). It has been shown in [1] and [2] that this configuration can provide superior inexpensive performance for a chosen application on the ground station or on-board a spacecraft. However, since this technology is still maturing, intensive pre-hardware steps are necessary to achieve the benefits of hardware implementation. This paper describes these steps for the GOES-8 application, a software project developed using Interactive Data Language (IDL) (Trademark of Research Systems, Inc.) on a Workstation/UNIX platform. The solution involves converting the application to a PC/Windows/RC platform, selected mainly by the availability of low cost, adaptable high-speed RC hardware. In order for the hybrid system to run, the IDL software was modified to account for platform differences. It was interesting to examine the gains and losses in performance on the new platform, as well as unexpected observations before implementing hardware. After substantial pre-hardware optimization steps, the necessity of hardware implementation for bottleneck code in the PC environment became evident and solvable beginning with the methodology described in [1], [2], and implementing a novel methodology for this specific application [6]. The PC-RC interface bandwidth problem for the

Practical Issues in Implementing Software Reliability Measurement

NASA Technical Reports Server (NTRS)

Nikora, Allen P.; Schneidewind, Norman F.; Everett, William W.; Munson, John C.; Vouk, Mladen A.; Musa, John D.

1999-01-01

Many ways of estimating software systems' reliability, or reliability-related quantities, have been developed over the past several years. Of particular interest are methods that can be used to estimate a software system's fault content prior to test, or to discriminate between components that are fault-prone and those that are not. The results of these methods can be used to: 1) More accurately focus scarce fault identification resources on those portions of a software system most in need of it. 2) Estimate and forecast the risk of exposure to residual faults in a software system during operation, and develop risk and safety criteria to guide the release of a software system to fielded use. 3) Estimate the efficiency of test suites in detecting residual faults. 4) Estimate the stability of the software maintenance process.

Implementation of a Cardiogenic Shock Team and Clinical Outcomes (INOVA-SHOCK Registry): Observational and Retrospective Study.

PubMed

Tehrani, Behnam; Truesdell, Alexander; Singh, Ramesh; Murphy, Charles; Saulino, Patricia

2018-06-28

The development and implementation of a Cardiogenic Shock initiative focused on increased disease awareness, early multidisciplinary team activation, rapid initiation of mechanical circulatory support, and hemodynamic-guided management and improvement of outcomes in cardiogenic shock. The objectives of this study are (1) to collect retrospective clinical outcomes for acute decompensated heart failure cardiogenic shock and acute myocardial infarction cardiogenic shock, and compare current versus historical survival rates and clinical outcomes; (2) to evaluate Inova Heart and Vascular Institute site specific outcomes before and after initiation of the Cardiogenic Shock team on January 1, 2017; (3) to compare outcomes related to early implementation of mechanical circulatory support and hemodynamic-guided management versus historical controls; (4) to assess survival to discharge rate in patients receiving intervention from the designated shock team and (5) create a clinical archive of Cardiogenic Shock patient characteristics for future analysis and the support of translational research studies. This is an observational, retrospective, single center study. Retrospective and prospective data will be collected in patients treated at the Inova Heart and Vascular Institute with documented cardiogenic shock as a result of acute decompensated heart failure or acute myocardial infarction. This registry will include data from patients prior to and after the initiation of the multidisciplinary Cardiogenic Shock team on January 1, 2017. Clinical outcomes associated with early multidisciplinary team intervention will be analyzed. In the study group, all patients evaluated for documented cardiogenic shock (acute decompensated heart failure cardiogenic shock, acute myocardial infarction cardiogenic shock) treated at the Inova Heart and Vascular Institute by the Cardiogenic Shock team will be included. An additional historical Inova Heart and Vascular Institute control group will

Requirements Engineering in Building Climate Science Software

ERIC Educational Resources Information Center

Batcheller, Archer L.

2011-01-01

Software has an important role in supporting scientific work. This dissertation studies teams that build scientific software, focusing on the way that they determine what the software should do. These requirements engineering processes are investigated through three case studies of climate science software projects. The Earth System Modeling…

[Team Development in Medical Rehabilitation: Concept and Evaluation of a Team Intervention].

PubMed

Körner, M; Luzay, L; Becker, S; Rundel, M; Müller, C; Zimmermann, L

2016-04-01

Interprofessional collaboration is a main precondition of successful treatment in rehabilitation. In order to improve interprofessional collaboration, a clinic-specific, goal- and solution-oriented and systemic team development approach was designed. The aim of the study is the evaluation of this approach. A multi-centre cluster-randomized controlled study with staff questionnaires. The team development could be implemented successfully in 4 of 5 clinics and led to significant improvements in team organisation, willingness to accept responsibility and knowledge integration. The effects are small and are caused by the opposed development of intervention and control group. The team development approach can be recommended for rehabilitation practice. A train-the-trainer approach will be developed and further studies are planned in order to disseminate the approach and to investigate the conditions of implementation. © Georg Thieme Verlag KG Stuttgart · New York.

Predicting Software Suitability Using a Bayesian Belief Network

NASA Technical Reports Server (NTRS)

Beaver, Justin M.; Schiavone, Guy A.; Berrios, Joseph S.

2005-01-01

The ability to reliably predict the end quality of software under development presents a significant advantage for a development team. It provides an opportunity to address high risk components earlier in the development life cycle, when their impact is minimized. This research proposes a model that captures the evolution of the quality of a software product, and provides reliable forecasts of the end quality of the software being developed in terms of product suitability. Development team skill, software process maturity, and software problem complexity are hypothesized as driving factors of software product quality. The cause-effect relationships between these factors and the elements of software suitability are modeled using Bayesian Belief Networks, a machine learning method. This research presents a Bayesian Network for software quality, and the techniques used to quantify the factors that influence and represent software quality. The developed model is found to be effective in predicting the end product quality of small-scale software development efforts.

User systems guidelines for software projects

DOE Office of Scientific and Technical Information (OSTI.GOV)

Abrahamson, L.

1986-04-01

This manual presents guidelines for software standards which were developed so that software project-development teams and management involved in approving the software could have a generalized view of all phases in the software production procedure and the steps involved in completing each phase. Guidelines are presented for six phases of software development: project definition, building a user interface, designing software, writing code, testing code, and preparing software documentation. The discussions for each phase include examples illustrating the recommended guidelines. 45 refs. (DWL)

An interprofessional team approach to tracheostomy care: a mixed-method investigation into the mechanisms explaining tracheostomy team effectiveness.

PubMed

Mitchell, Rebecca; Parker, Vicki; Giles, Michelle

2013-04-01

In an effort to reduce tracheostomy-related complications, many acute care facilities have implemented specialist tracheostomy teams. Some studies, however, generate only mixed support for the connection between tracheostomy teams and patient outcomes. This suggests that the effect of collaborative teamwork in tracheostomy care is still not well understood. The aim of this paper is to investigate the mechanisms through which an interprofessional team approach can improve the management of patients with a tracheostomy. The achievement of this research objective requires the collection of rich empirical data, which indicates the use of a qualitative methodology. A case study approach provided an opportunity to collect a wealth of data on tracheostomy team activities and dynamics. Data were collected on an interprofessional tracheostomy team in a large tertiary referral hospital in Australia. The team was composed of clinical nurse consultants, a physiotherapist, a speech pathologist, a dietician, a social worker and medical officers. Data were collected through a focus group and one-to-one, semi-structured in-depth interviews, and thematic analysis was used to analyse experiences of tracheostomy team members. Qualitative analysis resulted in two main themes: interprofessional protocol development and implementation; and interprofessional decision-making. Our findings suggest that tracheostomy teams enhance consistency of care through the development and implementation of interprofessional protocol. In addition, such team allow more efficient and effective communication and decision-making consequent to the collocation of diverse professionals. These findings provide new insight into the role of tracheostomy teams in successfully implementing complex protocol and the explanatory mechanisms through which interprofessional teams may generate positive outcomes for tracheostomy patients. Copyright © 2012. Published by Elsevier Ltd.

The Implementation Process of Two Multigrade/Multiyear Teams in Two Middle Schools in South Florida: A Cross-Site Case Study.

ERIC Educational Resources Information Center

Heeney, Margaret R.

Multigrade grouping is the practice of intentionally grouping two or more grade levels in the same classroom to enhance learning. It is becoming a much discussed and implemented alternative grouping practice in middle level education. This paper describes the implementation process of two multigrade "teams" in two Florida middle schools,…

Reported implementation lessons from a national quality improvement initiative; Productive Ward: Releasing Time to Care™. A qualitative, ward-based team perspective.

PubMed

White, Mark; Butterworth, Tony; Wells, John S G

2017-10-01

To explore the experiences of participants involved in the implementation of the Productive Ward: Releasing Time to Care™ initiative in Ireland, identifying key implementation lessons. A large-scale quality improvement programme Productive Ward: Releasing Time to Care™ was introduced nationwide into Ireland in 2011. We captured accounts from ward-based teams in an implementation phase during 2013-14 to explore their experiences. Semi-structured, in-depth interviews with a purposive sample of 24 members of ward-based teams from nine sites involved in the second national phase of the initiative were conducted. Interviews were analysed and coded under themes, using a seven-stage iterative process. The predominant theme identified was associated with the implementation and management of the initiative and included: project management; training; preparation; information and communication; and participant's negative experiences. The most prominent challenge reported related to other competing clinical priorities. Despite the structured approach of Productive Ward: Releasing Time to Care™, it appears that overstretched and busy clinical environments struggle to provide the right climate and context for ward-based teams to engage and interact actively with quality improvement tools, methods and activities. Findings highlight five key aspects of implementation and management that will help facilitate successful adoption of large-scale, ward-based quality improvement programmes such as Productive Ward: Releasing Time to Care™. Utilising pre-existing implementation or quality frameworks to assess each ward/unit for 'readiness' prior to commencing a quality improvement intervention such as Productive Ward: Releasing Time to Care™ should be considered. © 2017 John Wiley & Sons Ltd.

Does team training work? Principles for health care.

PubMed

Salas, Eduardo; DiazGranados, Deborah; Weaver, Sallie J; King, Heidi

2008-11-01

Teamwork is integral to a working environment conducive to patient safety and care. Team training is one methodology designed to equip team members with the competencies necessary for optimizing teamwork. There is evidence of team training's effectiveness in highly complex and dynamic work environments, such as aviation and health care. However, most quantitative evaluations of training do not offer any insight into the actual reasons why, how, and when team training is effective. To address this gap in understanding, and to provide guidance for members of the health care community interested in implementing team training programs, this article presents both quantitative results and a specific qualitative review and content analysis of team training implemented in health care. Based on this review, we offer eight evidence-based principles for effective planning, implementation, and evaluation of team training programs specific to health care.

Analysis of Software Development Methodologies to Build Safety Software Applications for the SATEX-II: A Mexican Experimental Satellite

NASA Astrophysics Data System (ADS)

Aguilar Cisneros, Jorge; Vargas Martinez, Hector; Pedroza Melendez, Alejandro; Alonso Arevalo, Miguel

2013-09-01

Mexico is a country where the experience to build software for satellite applications is beginning. This is a delicate situation because in the near future we will need to develop software for the SATEX-II (Mexican Experimental Satellite). SATEX- II is a SOMECyTA's project (the Mexican Society of Aerospace Science and Technology). We have experienced applying software development methodologies, like TSP (Team Software Process) and SCRUM in other areas. Then, we analyzed these methodologies and we concluded: these can be applied to develop software for the SATEX-II, also, we supported these methodologies with SSP-05-0 Standard in particular with ESA PSS-05-11. Our analysis was focusing on main characteristics of each methodology and how these methodologies could be used with the ESA PSS 05-0 Standards. Our outcomes, in general, may be used by teams who need to build small satellites, but, in particular, these are going to be used when we will build the on board software applications for the SATEX-II.

Extra-team Connections for Knowledge Transfer between Staff Teams

ERIC Educational Resources Information Center

Ramanadhan, Shoba; Wiecha, Jean L.; Emmons, Karen M.; Gortmaker, Steven L.; Viswanath, Kasisomayajula

2009-01-01

As organizations implement novel health promotion programs across multiple sites, they face great challenges related to knowledge management. Staff social networks may be a useful medium for transferring program-related knowledge in multi-site implementation efforts. To study this potential, we focused on the role of extra-team connections (ties…

Software Capability Evaluation Version 2.0 Method Description

DTIC Science & Technology

1994-06-01

These criteria are discussed below; they include training, team composition, team leadership , team member experience and knowledge, individual...previous SCEs. No more than one team member should have less than two years of professional software experience. 3 Leadership . Ideally, the team leader...features: e leadership - the assignment of responsibility the presence of sponsorship. * organizational policies - there are written po! ;goveming the

Team dynamics within quality improvement teams: a scoping review.

PubMed

Rowland, Paula; Lising, Dean; Sinclair, Lynne; Baker, G Ross

2018-03-31

This scoping review examines what is known about the processes of quality improvement (QI) teams, particularly related to how teams impact outcomes. The aim is to provide research-informed guidance for QI leaders and to inform future research questions. Databases searched included: MedLINE, EMBASE, CINAHL, Web of Science and SCOPUS. Eligible publications were written in English, published between 1999 and 2016. Articles were included in the review if they examined processes of the QI team, were related to healthcare QI and were primary research studies. Studies were excluded if they had insufficient detail regarding QI team processes. Descriptive detail extracted included: authors, geographical region and health sector. The Integrated (Health Care) Team Effectiveness Model was used to synthesize findings of studies along domains of team effectiveness: task design, team process, psychosocial traits and organizational context. Over two stages of searching, 4813 citations were reviewed. Of those, 48 full-text articles are included in the synthesis. This review demonstrates that QI teams are not immune from dysfunction. Further, a dysfunctional QI team is not likely to influence practice. However, a functional QI team alone is unlikely to create change. A positive QI team dynamic may be a necessary but insufficient condition for implementing QI strategies. Areas for further research include: interactions between QI teams and clinical microsystems, understanding the role of interprofessional representation on QI teams and exploring interactions between QI team task, composition and process.

Architecture and Implementation of OpenPET Firmware and Embedded Software

DOE PAGES

Abu-Nimeh, Faisal T.; Ito, Jennifer; Moses, William W.; ...

2016-01-11

OpenPET is an open source, modular, extendible, and high-performance platform suitable for multi-channel data acquisition and analysis. Due to the versatility of the hardware, firmware, and software architectures, the platform is capable of interfacing with a wide variety of detector modules not only in medical imaging but also in homeland security applications. Analog signals from radiation detectors share similar characteristics-a pulse whose area is proportional to the deposited energy and whose leading edge is used to extract a timing signal. As a result, a generic design method of the platform is adopted for the hardware, firmware, and software architectures andmore » implementations. The analog front-end is hosted on a module called a Detector Board, where each board can filter, combine, timestamp, and process multiple channels independently. The processed data is formatted and sent through a backplane bus to a module called Support Board, where 1 Support Board can host up to eight Detector Board modules. The data in the Support Board, coming from 8 Detector Board modules, can be aggregated or correlated (if needed) depending on the algorithm implemented or runtime mode selected. It is then sent out to a computer workstation for further processing. The number of channels (detector modules), to be processed, mandates the overall OpenPET System Configuration, which is designed to handle up to 1,024 channels using 16-channel Detector Boards in the Standard System Configuration and 16,384 channels using 32-channel Detector Boards in the Large System Configuration.« less

Architecture and Implementation of OpenPET Firmware and Embedded Software

PubMed Central

Abu-Nimeh, Faisal T.; Ito, Jennifer; Moses, William W.; Peng, Qiyu; Choong, Woon-Seng

2016-01-01

OpenPET is an open source, modular, extendible, and high-performance platform suitable for multi-channel data acquisition and analysis. Due to the flexibility of the hardware, firmware, and software architectures, the platform is capable of interfacing with a wide variety of detector modules not only in medical imaging but also in homeland security applications. Analog signals from radiation detectors share similar characteristics – a pulse whose area is proportional to the deposited energy and whose leading edge is used to extract a timing signal. As a result, a generic design method of the platform is adopted for the hardware, firmware, and software architectures and implementations. The analog front-end is hosted on a module called a Detector Board, where each board can filter, combine, timestamp, and process multiple channels independently. The processed data is formatted and sent through a backplane bus to a module called Support Board, where 1 Support Board can host up to eight Detector Board modules. The data in the Support Board, coming from 8 Detector Board modules, can be aggregated or correlated (if needed) depending on the algorithm implemented or runtime mode selected. It is then sent out to a computer workstation for further processing. The number of channels (detector modules), to be processed, mandates the overall OpenPET System Configuration, which is designed to handle up to 1,024 channels using 16-channel Detector Boards in the Standard System Configuration and 16,384 channels using 32-channel Detector Boards in the Large System Configuration. PMID:27110034

Software Engineering Program: Software Process Improvement Guidebook

NASA Technical Reports Server (NTRS)

1996-01-01

The purpose of this document is to provide experience-based guidance in implementing a software process improvement program in any NASA software development or maintenance community. This guidebook details how to define, operate, and implement a working software process improvement program. It describes the concept of the software process improvement program and its basic organizational components. It then describes the structure, organization, and operation of the software process improvement program, illustrating all these concepts with specific NASA examples. The information presented in the document is derived from the experiences of several NASA software organizations, including the SEL, the SEAL, and the SORCE. Their experiences reflect many of the elements of software process improvement within NASA. This guidebook presents lessons learned in a form usable by anyone considering establishing a software process improvement program within his or her own environment. This guidebook attempts to balance general and detailed information. It provides material general enough to be usable by NASA organizations whose characteristics do not directly match those of the sources of the information and models presented herein. It also keeps the ideas sufficiently close to the sources of the practical experiences that have generated the models and information.

Freight Advanced Traveler Information System (FRATIS) Dallas-Fort Worth : software architecture design and implementation options.

DOT National Transportation Integrated Search

2013-05-01

This document describes the Software Architecture Design and Implementation Options for FRATIS system. The demonstration component of this task will serve to test the technical feasibility of the FRATIS prototype while also facilitating the collectio...

Effects of a Brief Team Training Program on Surgical Teams' Nontechnical Skills: An Interrupted Time-Series Study.

PubMed

Gillespie, Brigid M; Harbeck, Emma; Kang, Evelyn; Steel, Catherine; Fairweather, Nicole; Panuwatwanich, Kriengsak; Chaboyer, Wendy

2017-04-27

Up to 60% of adverse events in surgery are the result of poor communication and teamwork. Nontechnical skills in surgery (NOTSS) are critical to the success of surgery and patient safety. The study aim was to evaluate the effect of a brief team training intervention on teams' observed NOTSS. Pretest-posttest interrupted time-series design with statistical process control analysis was used to detect longitudinal changes in teams' NOTSS. We evaluated NOTSS using the revised NOTECHS weekly for 20 to 25 weeks before and after implementation of a team training program. We observed 179 surgical procedures with cardiac, vascular, upper gastrointestinal, and hepatobiliary teams. Mean posttest NOTECHS scores increased across teams, showing special cause variation. There were also significant before and after improvements in NOTECHS scores in respect to professional role and in the use of the Surgical Safety Checklist. Our results suggest associated improvements in teams' NOTSS after implementation of the team training program.

Teaming for Speech and Auditory Training.

ERIC Educational Resources Information Center

Nussbaum, Debra B.; Waddy-Smith, Bettie

1985-01-01

The article suggests three strategies for the audiologist and speech/communication specialist to use in assisting the preschool teacher to implement student's individualized education program: (1) demonstration teaming, (2) dual teaming; and (3) rotation teaming. (CL)

To adopt is to adapt: the process of implementing the ICF with an acute stroke multidisciplinary team in England.

PubMed

Tempest, Stephanie; Harries, Priscilla; Kilbride, Cherry; De Souza, Lorraine

2012-01-01

The success of the International Classification of Functioning, Disability and Health (ICF) depends on its uptake in clinical practice. This project aimed to explore ways the ICF could be used with an acute stroke multidisciplinary team and identify key learning from the implementation process. Using an action research approach, iterative cycles of observe, plan, act and evaluate were used within three phases: exploratory; innovatory and reflective. Thematic analysis was undertaken, using a model of immersion and crystallisation, on data collected via interview and focus groups, e-mail communications, minutes from relevant meetings, field notes and a reflective diary. Two overall themes were determined from the data analysis which enabled implementation. There is a need to: (1) adopt the ICF in ways that meet local service needs; and (2) adapt the ICF language and format. The empirical findings demonstrate how to make the ICF classification a clinical reality. First, we need to adopt the ICF as a vehicle to implement local service priorities e.g. to structure a multidisciplinary team report, thus enabling ownership of the implementation process. Second, we need to adapt the ICF terminology and format to make it acceptable for use by clinicians.

Implementation of software-based sensor linearization algorithms on low-cost microcontrollers.

PubMed

Erdem, Hamit

2010-10-01

Nonlinear sensors and microcontrollers are used in many embedded system designs. As the input-output characteristic of most sensors is nonlinear in nature, obtaining data from a nonlinear sensor by using an integer microcontroller has always been a design challenge. This paper discusses the implementation of six software-based sensor linearization algorithms for low-cost microcontrollers. The comparative study of the linearization algorithms is performed by using a nonlinear optical distance-measuring sensor. The performance of the algorithms is examined with respect to memory space usage, linearization accuracy and algorithm execution time. The implementation and comparison results can be used for selection of a linearization algorithm based on the sensor transfer function, expected linearization accuracy and microcontroller capacity. Copyright © 2010 ISA. Published by Elsevier Ltd. All rights reserved.

NASA software specification and evaluation system: Software verification/validation techniques

NASA Technical Reports Server (NTRS)

1977-01-01

NASA software requirement specifications were used in the development of a system for validating and verifying computer programs. The software specification and evaluation system (SSES) provides for the effective and efficient specification, implementation, and testing of computer software programs. The system as implemented will produce structured FORTRAN or ANSI FORTRAN programs, but the principles upon which SSES is designed allow it to be easily adapted to other high order languages.

Putting the MeaT into TeaM Training: Development, Delivery, and Evaluation of a Surgical Team-Training Workshop.

PubMed

Seymour, Neal E; Paige, John T; Arora, Sonal; Fernandez, Gladys L; Aggarwal, Rajesh; Tsuda, Shawn T; Powers, Kinga A; Langlois, Gerard; Stefanidis, Dimitrios

2016-01-01

Despite importance to patient care, team training is infrequently used in surgical education. To address this, a workshop was developed by the Association for Surgical Education Simulation Committee to teach team training using high-fidelity patient simulators and the American College of Surgeons-Association of Program Directors in Surgery team-training curriculum. Workshops were conducted at 3 national meetings. Participants completed preworkshop and postworkshop questionnaires to define experience, confidence in using simulation, intention to implement, as well as workshop content quality. The course consisted of (A) a didactic review of Preparation, Implementation, and Debriefing and (B) facilitated small group simulation sessions followed by debriefings. Of 78 participants, 51 completed the workshops. Overall, 65% indicated that residents at their institutions used patient simulation, but only 33% used the American College of Surgeons-the Association of Program Directors in Surgery team-training modules. The workshop increased confidence to implement simulation team training (3.4 ± 1.3 vs 4.5 ± 0.9). Quality and importance were rated highly (5.4 ± 00.6, highest score = 6). Preparation for simulation-based team training is possible in this workshop setting, although the effect on actual implementation remains to be determined. Copyright © 2015 Association of Program Directors in Surgery. Published by Elsevier Inc. All rights reserved.

Multistage switching hardware and software implementations for student experiment purpose

NASA Astrophysics Data System (ADS)

Sani, A.; Suherman

2018-02-01

Current communication and internet networks are underpinned by the switching technologies that interconnect one network to the others. Students’ understanding on networks rely on how they conver the theories. However, understanding theories without touching the reality may exert spots in the overall knowledge. This paper reports the progress of the multistage switching design and implementation for student laboratory activities. The hardware and software designs are based on three stages clos switching architecture with modular 2x2 switches, controlled by an arduino microcontroller. The designed modules can also be extended for batcher and bayan switch, and working on circuit and packet switching systems. The circuit analysis and simulation show that the blocking probability for each switch combinations can be obtained by generating random or patterned traffics. The mathematic model and simulation analysis shows 16.4% blocking probability differences as the traffic generation is uniform. The circuits design components and interfacing solution have been identified to allow next step implementation.

Methodology for Software Reliability Prediction. Volume 2.

DTIC Science & Technology

1987-11-01

The overall acquisition ,z program shall include the resources, schedule, management, structure , and controls necessary to ensure that specified AD...Independent Verification/Validation - Programming Team Structure - Educational Level of Team Members - Experience Level of Team Members * Methods Used...Prediction or Estimation Parameter Supported: Software - Characteristics 3. Objectives: Structured programming studies and Government Ur.’.. procurement

Interdisciplinary team interactions: a qualitative study of perceptions of team function in simulated anaesthesia crises.

PubMed

Weller, Jennifer M; Janssen, Anna L; Merry, Alan F; Robinson, Brian

2008-04-01

We placed anaesthesia teams into a stressful environment in order to explore interactions between members of different professional groups and to investigate their perspectives on the impact of these interactions on team performance. Ten anaesthetists, 5 nurses and 5 trained anaesthetic assistants each participated in 2 full-immersion simulations of critical events using a high-fidelity computerised patient simulator. Their perceptions of team interactions were explored through questionnaires and semi-structured interviews. Written questionnaire data and interview transcriptions were entered into N6 qualitative software. Data were analysed by 2 investigators for emerging themes and coded to produce reports on each theme. We found evidence of limited understanding of the roles and capabilities of team members across professional boundaries, different perceptions of appropriate roles and responsibilities for different members of the team, limited sharing of information between team members and limited team input into decision making. There was a perceived impact on task distribution and the optimal utilisation of resources within the team. Effective management of medical emergencies depends on optimal team function. We have identified important factors affecting interactions between different health professionals in the anaesthesia team, and their perceived influences on team function. This provides evidence on which to build appropriate and specific strategies for interdisciplinary team training in operating theatre staff.

Evolution of Software-Only-Simulation at NASA IV and V

NASA Technical Reports Server (NTRS)

McCarty, Justin; Morris, Justin; Zemerick, Scott

2014-01-01

Software-Only-Simulations have been an emerging but quickly developing field of study throughout NASA. The NASA Independent Verification Validation (IVV) Independent Test Capability (ITC) team has been rapidly building a collection of simulators for a wide range of NASA missions. ITC specializes in full end-to-end simulations that enable developers, VV personnel, and operators to test-as-you-fly. In four years, the team has delivered a wide variety of spacecraft simulations that have ranged from low complexity science missions such as the Global Precipitation Management (GPM) satellite and the Deep Space Climate Observatory (DSCOVR), to the extremely complex missions such as the James Webb Space Telescope (JWST) and Space Launch System (SLS).This paper describes the evolution of ITCs technologies and processes that have been utilized to design, implement, and deploy end-to-end simulation environments for various NASA missions. A comparison of mission simulators are discussed with focus on technology and lessons learned in complexity, hardware modeling, and continuous integration. The paper also describes the methods for executing the missions unmodified flight software binaries (not cross-compiled) for verification and validation activities.

Command and Control Software Development Memory Management

NASA Technical Reports Server (NTRS)

Joseph, Austin Pope

2017-01-01

This internship was initially meant to cover the implementation of unit test automation for a NASA ground control project. As is often the case with large development projects, the scope and breadth of the internship changed. Instead, the internship focused on finding and correcting memory leaks and errors as reported by a COTS software product meant to track such issues. Memory leaks come in many different flavors and some of them are more benign than others. On the extreme end a program might be dynamically allocating memory and not correctly deallocating it when it is no longer in use. This is called a direct memory leak and in the worst case can use all the available memory and crash the program. If the leaks are small they may simply slow the program down which, in a safety critical system (a system for which a failure or design error can cause a risk to human life), is still unacceptable. The ground control system is managed in smaller sub-teams, referred to as CSCIs. The CSCI that this internship focused on is responsible for monitoring the health and status of the system. This team's software had several methods/modules that were leaking significant amounts of memory. Since most of the code in this system is safety-critical, correcting memory leaks is a necessity.

Developing the green house nursing care team: variations on development and implementation.

PubMed

Bowers, Barbara J; Nolet, Kimberly

2014-02-01

A core component of the Green House nursing home model is an altered supervisory relationship between the nurse and direct care workers. Some have expressed concern that the Green House model might weaken professional nursing oversight, threatening the quality of clinical care. This qualitative research study explores the role of the nurse as implemented in the Green House model, focusing on how variations in the nursing team influence clinical care practices. Dimensional analysis, a "second generation" grounded theory methodology, was used to conduct this study. Data were collected through observations and interviews with 37 nurses, 68 CNAs, and 11 Guides working at 11 Green House sites. Implementation of the nursing role within the Green House model varied both within and across sites. Four nursing model types were identified: Traditional, Visitor, Parallel, and Integrated. Care processes, CNA/Shahbaz skill development, and worker stress varied with each nursing model. Government policies have been enacted to support culture change. However, there is currently little guidance for regulators, providers, or consumers regarding variability in how culture change practices are implemented and consequences of these variations. This article outlines the importance of understanding these practices at a level of detail that distinguishes and supports those that are most promising.

Software-Implemented Fault Tolerance in Communications Systems

NASA Technical Reports Server (NTRS)

Gantenbein, Rex E.

1994-01-01

Software-implemented fault tolerance (SIFT) is used in many computer-based command, control, and communications (C(3)) systems to provide the nearly continuous availability that they require. In the communications subsystem of Space Station Alpha, SIFT algorithms are used to detect and recover from failures in the data and command link between the Station and its ground support. The paper presents a review of these algorithms and discusses how such techniques can be applied to similar systems found in applications such as manufacturing control, military communications, and programmable devices such as pacemakers. With support from the Tracking and Communication Division of NASA's Johnson Space Center, researchers at the University of Wyoming are developing a testbed for evaluating the effectiveness of these algorithms prior to their deployment. This testbed will be capable of simulating a variety of C(3) system failures and recording the response of the Space Station SIFT algorithms to these failures. The design of this testbed and the applicability of the approach in other environments is described.

Software verification plan for GCS. [guidance and control software

NASA Technical Reports Server (NTRS)

Dent, Leslie A.; Shagnea, Anita M.; Hayhurst, Kelly J.

1990-01-01

This verification plan is written as part of an experiment designed to study the fundamental characteristics of the software failure process. The experiment will be conducted using several implementations of software that were produced according to industry-standard guidelines, namely the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, Software Consideration in Airborne Systems and Equipment Certification, for the development of flight software. This plan fulfills the DO-178A requirements for providing instructions on the testing of each implementation of software. The plan details the verification activities to be performed at each phase in the development process, contains a step by step description of the testing procedures, and discusses all of the tools used throughout the verification process.

ThermoData Engine (TDE): software implementation of the dynamic data evaluation concept. 5. Experiment planning and product design.

PubMed

Diky, Vladimir; Chirico, Robert D; Kazakov, Andrei F; Muzny, Chris D; Magee, Joseph W; Abdulagatov, Ilmutdin; Kang, Jeong Won; Kroenlein, Kenneth; Frenkel, Michael

2011-01-24

ThermoData Engine (TDE) is the first full-scale software implementation of the dynamic data evaluation concept, as reported recently in this journal. In the present paper, we describe development of an algorithmic approach to assist experiment planning through assessment of the existing body of knowledge, including availability of experimental thermophysical property data, variable ranges studied, associated uncertainties, state of prediction methods, and parameters for deployment of prediction methods and how these parameters can be obtained using targeted measurements, etc., and, indeed, how the intended measurement may address the underlying scientific or engineering problem under consideration. A second new feature described here is the application of the software capabilities for aid in the design of chemical products through identification of chemical systems possessing desired values of thermophysical properties within defined ranges of tolerance. The algorithms and their software implementation to achieve this are described. Finally, implementation of a new data validation and weighting system is described for vapor-liquid equilibrium (VLE) data, and directions for future enhancements are outlined.

Introductory Molecular Orbital Theory: An Honors General Chemistry Computational Lab as Implemented Using Three-Dimensional Modeling Software

ERIC Educational Resources Information Center

Ruddick, Kristie R.; Parrill, Abby L.; Petersen, Richard L.

2012-01-01

In this study, a computational molecular orbital theory experiment was implemented in a first-semester honors general chemistry course. Students used the GAMESS (General Atomic and Molecular Electronic Structure System) quantum mechanical software (as implemented in ChemBio3D) to optimize the geometry for various small molecules. Extended Huckel…

Virtual Teams and Human Work Interaction Design - Learning to Work in and Designing for Virtual Teams

NASA Astrophysics Data System (ADS)

Orngreen, Rikke; Clemmensen, Torkil; Pejtersen, Annelise Mark

The boundaries and work processes for how virtual teams interact are undergoing changes, from a tool and stand-alone application orientation, to the use of multiple generic platforms chosen and redesigned to the specific context. These are often at the same time designed both by professional software developers and the individual members of the virtual teams, rather than determined on a single organizational level. There may be no impact of the technology per se on individuals, groups or organizations, as the technology for virtual teams rather enhance situation ambiguity and disrupt existing task-artifact cycles. This ambiguous situation calls for new methods for empirical work analysis and interaction design that can help us understand how organizations, teams and individuals learn to organize, design and work in virtual teams in various networked contexts.

Software-centric View on OVMS for LBT

NASA Astrophysics Data System (ADS)

Trowitzsch, J.; Borelli, J.; Pott, J.; Kürster, M.

2012-09-01

The performance of infrared interferometry (IF) and adaptive optics (AO) strongly depends on the mitigation and correction of telescope vibrations. Therefore, at the Large Binocular Telescope (LBT) the OVMS, the Optical Path Difference and Vibration Monitoring System, is being installed. It is meant to ensure suitable conditions for adaptive optics and interferometry. The vibration information is collected from accelerometers that are distributed over the optical elements of the LBT. The collected vibration measurements are converted into tip-tilt and optical path difference data. That data is utilized in the control strategies of the LBT adaptive secondary mirrors and the beam combining interferometers, LINC-NIRVANA and LBTI. Within the OVMS the software part is responsibility of the LINC-NIRVANA team at MPIA Heidelberg. It comprises the software for the real-time data acquisition from the accelerometers as well as the related telemetry interface and the vibration monitoring quick look tools. The basic design ideas, implementation details and special features are explained here.

Team Expo: A State-of-the-Art JSC Advanced Design Team

NASA Technical Reports Server (NTRS)

Tripathi, Abhishek

2001-01-01

In concert with the NASA-wide Intelligent Synthesis Environment Program, the Exploration Office at the Johnson Space Center has assembled an Advanced Design Team. The purpose of this team is two-fold. The first is to identify, use, and develop software applications, tools, and design processes that streamline and enhance a collaborative engineering environment. The second is to use this collaborative engineering environment to produce conceptual, system-level-of-detail designs in a relatively short turnaround time, using a standing team of systems and integration experts. This includes running rapid trade studies on varying mission architectures, as well as producing vehicle and/or subsystem designs. The standing core team is made up of experts from all of the relevant engineering divisions (e.g. Power, Thermal, Structures, etc.) as well as representatives from Risk and Safety, Mission Operations, and Crew Life Sciences among others. The Team works together during 2- hour sessions in the same specially enhanced room to ensure real-time integration/identification of cross-disciplinary issues and solutions. All subsystem designs are collectively reviewed and approved during these same sessions. In addition there is an Information sub-team that captures and formats all data and makes it accessible for use by the following day. The result is Team Expo: an Advanced Design Team that is leading the change from a philosophy of "over the fence" design to one of collaborative engineering that pushes the envelope to achieve the next-generation analysis and design environment.

Road map for implementing the AASHTO pavement ME design software for the Idaho Transportation Department.

DOT National Transportation Integrated Search

2014-04-01

This report provides a Road Map for implementing the AASHTOWare Pavement ME Design software for the Idaho Transportation Department (ITD). The Road Map calls for a series of three stages: Stage 1 - Immediate, Stage 2 - Near Term, and Stage 3 - Future...

A new approach for instrument software at Gemini

NASA Astrophysics Data System (ADS)

Gillies, Kim; Nunez, Arturo; Dunn, Jennifer

2008-07-01

Gemini Observatory is now developing its next generation of astronomical instruments, the Aspen instruments. These new instruments are sophisticated and costly requiring large distributed, collaborative teams. Instrument software groups often include experienced team members with existing mature code. Gemini has taken its experience from the previous generation of instruments and current hardware and software technology to create an approach for developing instrument software that takes advantage of the strengths of our instrument builders and our own operations needs. This paper describes this new software approach that couples a lightweight infrastructure and software library with aspects of modern agile software development. The Gemini Planet Imager instrument project, which is currently approaching its critical design review, is used to demonstrate aspects of this approach. New facilities under development will face similar issues in the future, and the approach presented here can be applied to other projects.

Team Nutrition School Activity Planner. A How-To Guide for Team Nutrition Schools and Supporters.

ERIC Educational Resources Information Center

Food and Consumer Service (USDA), Washington, DC.

This "how-to" guide for Team Nutrition fairs and tasting activities helps Team Nutrition supporters and schools understand how to work together to improve the health and education of children. Team Nutrition is the implementation tool for the U.S. Department of Agriculture's School Meals Initiative for Healthy Children. Section 1 of the guide…

The innovative rehabilitation team: an experiment in team building.

PubMed

Halstead, L S; Rintala, D H; Kanellos, M; Griffin, B; Higgins, L; Rheinecker, S; Whiteside, W; Healy, J E

1986-06-01

This article describes an effort by one rehabilitation team to create innovative approaches to team care in a medical rehabilitation hospital. The major arena for implementing change was the weekly patient rounds. We worked to increase patient involvement, developed a rounds coordinator role, used a structured format, and tried to integrate research findings into team decision making. Other innovations included use of a preadmission questionnaire, a discharge check list, and a rounds evaluation questionnaire. The impact of these changes was evaluated using the Group Environment Scale and by analyzing participation in rounds based on verbatim transcripts obtained prior to and 20 months after formation of the Innovative Rehabilitation Team (IRT). The results showed decreased participation by medical personnel during rounds, and increased participation by patients. The rounds coordinator role increased participation rates of staff from all disciplines and the group environment improved within the IRT. These data are compared with similar evaluations made of two other groups, which served as control teams. The problems inherent in making effective, lasting changes in interdisciplinary rehabilitation teams are reviewed, and a plea is made for other teams to explore additional ways to use the collective creativity and resources latent in the team membership.

Linguistic correlates of team performance: toward a tool for monitoring team functioning during space missions.

PubMed

Fischer, Ute; McDonnell, Lori; Orasanu, Judith

2007-05-01

Approaches to mitigating the likelihood of psychosocial problems during space missions emphasize preflight measures such as team training and team composition. Additionally, it may be necessary to monitor team interactions during missions for signs of interpersonal stress. The present research was conducted to identify features in team members' communications indicative of team functioning. Team interactions were studied in the context of six computer-simulated search and rescue missions. There were 12 teams of 4 U.S. men who participated; however, the present analyses contrast the top two teams with the two least successful teams. Communications between team members were analyzed using linguistic analysis software and a coding scheme developed to characterize task-related and social dimensions of team interactions. Coding reliability was established by having two raters independently code three transcripts. Between-rater agreement ranged from 78.1 to 97.9%. Team performance was significantly associated with team members' task-related communications, specifically with the extent to which task-critical information was shared. Successful and unsuccessful teams also showed different interactive patterns, in particular concerning the frequencies of elaborations and no-responses. Moreover, task success was negatively correlated with variability in team members' word count, and positively correlated with the number of positive emotion words and the frequency of assenting relative to dissenting responses. Analyses isolated certain task-related and social features of team communication related to team functioning. Team success was associated with the extent to which team members shared task-critical information, equally participated and built on each other's contributions, showed agreement, and positive affect.

The (mis)use of subjective process measures in software engineering

NASA Technical Reports Server (NTRS)

Valett, Jon D.; Condon, Steven E.

1993-01-01

A variety of measures are used in software engineering research to develop an understanding of the software process and product. These measures fall into three broad categories: quantitative, characteristics, and subjective. Quantitative measures are those to which a numerical value can be assigned, for example effort or lines of code (LOC). Characteristics describe the software process or product; they might include programming language or the type of application. While such factors do not provide a quantitative measurement of a process or product, they do help characterize them. Subjective measures (as defined in this study) are those that are based on the opinion or opinions of individuals; they are somewhat unique and difficult to quantify. Capturing of subjective measure data typically involves development of some type of scale. For example, 'team experience' is one of the subjective measures that were collected and studied by the Software Engineering Laboratory (SEL). Certainly, team experience could have an impact on the software process or product; actually measuring a team's experience, however, is not a strictly mathematical exercise. Simply adding up each team member's years of experience appears inadequate. In fact, most researchers would agree that 'years' do not directly translate into 'experience.' Team experience must be defined subjectively and then a scale must be developed e.g., high experience versus low experience; or high, medium, low experience; or a different or more granular scale. Using this type of scale, a particular team's overall experience can be compared with that of other teams in the development environment. Defining, collecting, and scaling subjective measures is difficult. First, precise definitions of the measures must be established. Next, choices must be made about whose opinions will be solicited to constitute the data. Finally, care must be given to defining the right scale and level of granularity for measurement.

The SOFIA Mission Control System Software

NASA Astrophysics Data System (ADS)

Heiligman, G. M.; Brock, D. R.; Culp, S. D.; Decker, P. H.; Estrada, J. C.; Graybeal, J. B.; Nichols, D. M.; Paluzzi, P. R.; Sharer, P. J.; Pampell, R. J.; Papke, B. L.; Salovich, R. D.; Schlappe, S. B.; Spriestersbach, K. K.; Webb, G. L.

1999-05-01

The Stratospheric Observatory for Infrared Astronomy (SOFIA) will be delivered with a computerized mission control system (MCS). The MCS communicates with the aircraft's flight management system and coordinates the operations of the telescope assembly, mission-specific subsystems, and the science instruments. The software for the MCS must be reliable and flexible. It must be easily usable by many teams of observers with widely differing needs, and it must support non-intrusive access for education and public outreach. The technology must be appropriate for SOFIA's 20-year lifetime. The MCS software development process is an object-oriented, use case driven approach. The process is iterative: delivery will be phased over four "builds"; each build will be the result of many iterations; and each iteration will include analysis, design, implementation, and test activities. The team is geographically distributed, coordinating its work via Web pages, teleconferences, T.120 remote collaboration, and CVS (for Internet-enabled configuration management). The MCS software architectural design is derived in part from other observatories' experience. Some important features of the MCS are: * distributed computing over several UNIX and VxWorks computers * fast throughput of time-critical data * use of third-party components, such as the Adaptive Communications Environment (ACE) and the Common Object Request Broker Architecture (CORBA) * extensive configurability via stored, editable configuration files * use of several computer languages so developers have "the right tool for the job". C++, Java, scripting languages, Interactive Data Language (from Research Systems, Int'l.), XML, and HTML will all be used in the final deliverables. This paper reports on work in progress, with the final product scheduled for delivery in 2001. This work was performed for Universities Space Research Association for NASA under contract NAS2-97001.

A Brief Survey of the Team Software ProcessSM (TSPSM)

DTIC Science & Technology

2011-10-24

spent more than 20 years in industry as a software engineer, system designer, project leader, and development manager working on control systems...InnerWorkings, Inc. Instituto Tecnologico y de Estudios Superiores de Monterrey Siemens AG SILAC Ingenieria de Software S.A. de C.V

Multidisciplinary team functioning.

PubMed

Kovitz, K E; Dougan, P; Riese, R; Brummitt, J R

1984-01-01

This paper advocates the need to move beyond interdisciplinary team composition as a minimum criterion for multidisciplinary functioning in child abuse treatment. Recent developments within the field reflect the practice of shared professional responsibility for detection, case management and treatment. Adherence to this particular model for intervention requires cooperative service planning and implementation as task related functions. Implicitly, this model also carries the potential to incorporate the supportive functioning essential to effective group process. However, explicit attention to the dynamics and process of small groups has been neglected in prescriptive accounts of multidisciplinary child abuse team organization. The present paper therefore focuses upon the maintenance and enhancement aspects of multidisciplinary group functioning. First, the development and philosophy of service for the Alberta Children's Hospital Child Abuse Program are reviewed. Second, composition of the team, it's mandate for service, and the population it serves are briefly described. Third, the conceptual framework within which the program functions is outlined. Strategies for effective group functioning are presented and the difficulties encountered with this model are highlighted. Finally, recommendations are offered for planning and implementing a multidisciplinary child abuse team and for maintaining its effective group functioning.

To adopt is to adapt: the process of implementing the ICF with an acute stroke multidisciplinary team in England

PubMed Central

Tempest, Stephanie; Harries, Priscilla; Kilbride, Cherry; De Souza, Lorraine

2012-01-01

Purpose: The success of the International Classifcation of Functioning, Disability and Health (ICF) depends on its uptake in clinical practice. This project aimed to explore ways the ICF could be used with an acute stroke multidisciplinary team and identify key learning from the implementation process. Method: Using an action research approach, iterative cycles of observe, plan, act and evaluate were used within three phases: exploratory; innovatory and refective. Thematic analysis was undertaken, using a model of immersion and crystallisation, on data collected via interview and focus groups, e-mail communications, minutes from relevant meetings, feld notes and a refective diary. Results: Two overall themes were determined from the data analysis which enabled implementation. There is a need to: (1) adopt the ICF in ways that meet local service needs; and (2) adapt the ICF language and format. Conclusions: The empirical fndings demonstrate how to make the ICF classifcation a clinical reality. First, we need to adopt the ICF as a vehicle to implement local service priorities e.g. to structure a multidisciplinary team report, thus enabling ownership of the implementation process. Second, we need to adapt the ICF terminology and format to make it acceptable for use by clinicians. PMID:22372376

"RAPID" team triage: one hospital's approach to patient-centered team triage.

PubMed

Shea, Sheila Sanning; Hoyt, K Sue

2012-01-01

Patients who present to the emergency department want definitive care by a health care provider who can perform an initial assessment, initiate treatment, and implement a disposition plan. The traditional "nurse triage" model often creates barriers to the process of rapidly evaluating patients. Therefore, innovative strategies must be explored to improve the time of patient arrival to the time seen by a qualified provider in order to complete a thorough medical screening examination. One such approach is a rapid team triage system that provides a patient-centered process. This article describes the implementation of a rapid team triage model in an urban community hospital.

Architecture-Based Unit Testing of the Flight Software Product Line

NASA Technical Reports Server (NTRS)

Ganesan, Dharmalingam; Lindvall, Mikael; McComas, David; Bartholomew, Maureen; Slegel, Steve; Medina, Barbara

2010-01-01

This paper presents an analysis of the unit testing approach developed and used by the Core Flight Software (CFS) product line team at the NASA GSFC. The goal of the analysis is to understand, review, and reconunend strategies for improving the existing unit testing infrastructure as well as to capture lessons learned and best practices that can be used by other product line teams for their unit testing. The CFS unit testing framework is designed and implemented as a set of variation points, and thus testing support is built into the product line architecture. The analysis found that the CFS unit testing approach has many practical and good solutions that are worth considering when deciding how to design the testing architecture for a product line, which are documented in this paper along with some suggested innprovennents.

Tracking Team Dynamic Strategy Implemented in Sly Fox Mission 22

DTIC Science & Technology

communication between team members and track the overall status of the team social dynamic. This paper provides a detailed account of the need, methodology , results, benefits, and limitations of this strategy.

Electronic Help for the Harried Team Chair.

ERIC Educational Resources Information Center

Polis, A. Richard

This paper describes one accreditation team leader's experience with coordinating the entire team accreditation review process on personal computer and offers 14 suggestions for future implementation. The leaders of the accreditation team describes pre-accreditation visit arrangements to facilitate the use of computers. He polled team members on…

Team Software Process (TSP) Body of Knowledge (BOK)

DTIC Science & Technology

2010-07-01

styles that correspond stereotypical extremes of group control and coordination, as shown in Figure 5. closed, random, open, and synchronous group ...and confirming the resolutions • managing the design change process and coordinating changes with the configuration control board • reporting...members. 123 | CMU/SEI-2010-TR-020 4. Coaching – Obtain a lead coach and the coaches for each team. 5. Conceptual design – Form a working group of

Developing the Green House Nursing Care Team: Variations on Development and Implementation

PubMed Central

Bowers, Barbara J.

2014-01-01

Purpose of the Study: A core component of the Green House nursing home model is an altered supervisory relationship between the nurse and direct care workers. Some have expressed concern that the Green House model might weaken professional nursing oversight, threatening the quality of clinical care. This qualitative research study explores the role of the nurse as implemented in the Green House model, focusing on how variations in the nursing team influence clinical care practices. Design and Methods: Dimensional analysis, a “second generation” grounded theory methodology, was used to conduct this study. Data were collected through observations and interviews with 37 nurses, 68 CNAs, and 11 Guides working at 11 Green House sites. Results: Implementation of the nursing role within the Green House model varied both within and across sites. Four nursing model types were identified: Traditional, Visitor, Parallel, and Integrated. Care processes, CNA/Shahbaz skill development, and worker stress varied with each nursing model. Implications: Government policies have been enacted to support culture change. However, there is currently little guidance for regulators, providers, or consumers regarding variability in how culture change practices are implemented and consequences of these variations. This article outlines the importance of understanding these practices at a level of detail that distinguishes and supports those that are most promising. PMID:24443606

JRTF: A Flexible Software Framework for Real-Time Control in Magnetic Confinement Nuclear Fusion Experiments

NASA Astrophysics Data System (ADS)

Zhang, M.; Zheng, G. Z.; Zheng, W.; Chen, Z.; Yuan, T.; Yang, C.

2016-04-01

The magnetic confinement nuclear fusion experiments require various real-time control applications like plasma control. ITER has designed the Fast Plant System Controller (FPSC) for this job. ITER provided hardware and software standards and guidelines for building a FPSC. In order to develop various real-time FPSC applications efficiently, a flexible real-time software framework called J-TEXT real-time framework (JRTF) is developed by J-TEXT tokamak team. JRTF allowed developers to implement different functions as independent and reusable modules called Application Blocks (AB). The AB developers only need to focus on implementing the control tasks or the algorithms. The timing, scheduling, data sharing and eventing are handled by the JRTF pipelines. JRTF provides great flexibility on developing ABs. Unit test against ABs can be developed easily and ABs can even be used in non-JRTF applications. JRTF also provides interfaces allowing JRTF applications to be configured and monitored at runtime. JRTF is compatible with ITER standard FPSC hardware and ITER (Control, Data Access and Communication) CODAC Core software. It can be configured and monitored using (Experimental Physics and Industrial Control System) EPICS. Moreover the JRTF can be ported to different platforms and be integrated with supervisory control software other than EPICS. The paper presents the design and implementation of JRTF as well as brief test results.

Sustainability of cross-functional teams for marketing strategy development and implementation.

PubMed

Kono, Ken; Antonucci, Don

2006-01-01

This article presents a case study on a cross-functional team used for marketing strategy development and execution at a health insurance company. The study found a set of success factors that contributed to the initial success of the team, but the factors were not enough to maintain the team's high level of productivity over time. The study later identified a set of 8 factors that helped sustain the team's high-productivity level. The 2 sets (ie, success and its subsequent sustainability factors) are analyzed against a normative model of team effectiveness. All the factors are explained by the normative model except for 1 sustainability factor, "challenge motivator." In fact, the study found the "challenge motivator" to be the most critical factor to keep up the team's productivity over time. Apart from a performance crisis, the authors developed 3 "challenge motivators"--first, more granular market information that could unearth hidden performance issues; second, constant value creation to shareholders as the firm being publicly traded; and third, the firm's strategic mandate to meet and exceed customer expectations that puts ultimate performance pressure on the marketing strategy team.

Terra Harvest software architecture

NASA Astrophysics Data System (ADS)

Humeniuk, Dave; Klawon, Kevin

2012-06-01

Under the Terra Harvest Program, the DIA has the objective of developing a universal Controller for the Unattended Ground Sensor (UGS) community. The mission is to define, implement, and thoroughly document an open architecture that universally supports UGS missions, integrating disparate systems, peripherals, etc. The Controller's inherent interoperability with numerous systems enables the integration of both legacy and future UGS System (UGSS) components, while the design's open architecture supports rapid third-party development to ensure operational readiness. The successful accomplishment of these objectives by the program's Phase 3b contractors is demonstrated via integration of the companies' respective plug-'n'-play contributions that include controllers, various peripherals, such as sensors, cameras, etc., and their associated software drivers. In order to independently validate the Terra Harvest architecture, L-3 Nova Engineering, along with its partner, the University of Dayton Research Institute, is developing the Terra Harvest Open Source Environment (THOSE), a Java Virtual Machine (JVM) running on an embedded Linux Operating System. The Use Cases on which the software is developed support the full range of UGS operational scenarios such as remote sensor triggering, image capture, and data exfiltration. The Team is additionally developing an ARM microprocessor-based evaluation platform that is both energy-efficient and operationally flexible. The paper describes the overall THOSE architecture, as well as the design decisions for some of the key software components. Development process for THOSE is discussed as well.

The effects of team reflexivity on psychological well-being in manufacturing teams.

PubMed

Chen, Jingqiu; Bamberger, Peter A; Song, Yifan; Vashdi, Dana R

2018-04-01

While the impact of team reflexivity (a.k.a. after-event-reviews, team debriefs) on team performance has been widely examined, we know little about its implications on other team outcomes such as member well-being. Drawing from prior team reflexivity research, we propose that reflexivity-related team processes reduce demands, and enhance control and support. Given the centrality of these factors to work-based strain, we posit that team reflexivity, by affecting these factors, may have beneficial implications on 3 core dimensions of employee burnout, namely exhaustion, cynicism, and inefficacy (reduced personal accomplishment). Using a sample of 469 unskilled manufacturing workers employed in 73 production teams in a Southern Chinese factory, we implemented a time lagged, quasi-field experiment, with half of the teams trained in and executing an end-of-shift team debriefing, and the other half assigned to a control condition and undergoing periodic postshift team-building exercises. Our findings largely supported our hypotheses, demonstrating that relative to team members assigned to the control condition, those assigned to the reflexivity condition experienced a significant improvement in all 3 burnout dimensions over time. These effects were mediated by control and support (but not demands) and amplified as a function of team longevity. (PsycINFO Database Record (c) 2018 APA, all rights reserved).

Understanding medical practice team roles.

PubMed

Hills, Laura

2015-01-01

Do you believe that the roles your employees play on your medical practice team are identical to their job titles or job descriptions? Do you believe that team roles are determined by personality type? This article suggests that a more effective way to build and manage your medical practice team is to define team roles through employee behaviors. It provides 10 rules of behavioral team roles that can help practice managers to select and build high-performing teams, build more productive team relationships, improve the employee recruitment process, build greater team trust and understanding; and increase their own effectiveness. This article describes in detail Belbin's highly regarded and widely used team role theory and summarizes four additional behavioral team role theories and systems. It offers lessons learned when applying team role theory to practice. Finally, this article offers an easy-to-implement method for assessing current team roles. It provides a simple four-question checklist that will help practice managers balance an imbalanced medical practice team.

Standard practices for the implementation of computer software

NASA Technical Reports Server (NTRS)

Irvine, A. P. (Editor)

1978-01-01

A standard approach to the development of computer program is provided that covers the file cycle of software development from the planning and requirements phase through the software acceptance testing phase. All documents necessary to provide the required visibility into the software life cycle process are discussed in detail.

Software Engineering for Human Spaceflight

NASA Technical Reports Server (NTRS)

Fredrickson, Steven E.

2014-01-01

The Spacecraft Software Engineering Branch of NASA Johnson Space Center (JSC) provides world-class products, leadership, and technical expertise in software engineering, processes, technology, and systems management for human spaceflight. The branch contributes to major NASA programs (e.g. ISS, MPCV/Orion) with in-house software development and prime contractor oversight, and maintains the JSC Engineering Directorate CMMI rating for flight software development. Software engineering teams work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements. They seek to infuse automation and autonomy into missions, and apply new technologies to flight processor and computational architectures. This presentation will provide an overview of key software-related projects, software methodologies and tools, and technology pursuits of interest to the JSC Spacecraft Software Engineering Branch.

Augmenting team cognition in human-automation teams performing in complex operational environments.

PubMed

Cuevas, Haydee M; Fiore, Stephen M; Caldwell, Barrett S; Strater, Laura

2007-05-01

There is a growing reliance on automation (e.g., intelligent agents, semi-autonomous robotic systems) to effectively execute increasingly cognitively complex tasks. Successful team performance for such tasks has become even more dependent on team cognition, addressing both human-human and human-automation teams. Team cognition can be viewed as the binding mechanism that produces coordinated behavior within experienced teams, emerging from the interplay between each team member's individual cognition and team process behaviors (e.g., coordination, communication). In order to better understand team cognition in human-automation teams, team performance models need to address issues surrounding the effect of human-agent and human-robot interaction on critical team processes such as coordination and communication. Toward this end, we present a preliminary theoretical framework illustrating how the design and implementation of automation technology may influence team cognition and team coordination in complex operational environments. Integrating constructs from organizational and cognitive science, our proposed framework outlines how information exchange and updating between humans and automation technology may affect lower-level (e.g., working memory) and higher-level (e.g., sense making) cognitive processes as well as teams' higher-order "metacognitive" processes (e.g., performance monitoring). Issues surrounding human-automation interaction are discussed and implications are presented within the context of designing automation technology to improve task performance in human-automation teams.

Empirical studies of software design: Implications for SSEs

NASA Technical Reports Server (NTRS)

Krasner, Herb

1988-01-01

Implications for Software Engineering Environments (SEEs) are presented in viewgraph format for characteristics of projects studied; significant problems and crucial problem areas in software design for large systems; layered behavioral model of software processes; implications of field study results; software project as an ecological system; results of the LIFT study; information model of design exploration; software design strategies; results of the team design study; and a list of publications.

Evaluating Sustainability Models for Interoperability through Brokering Software

NASA Astrophysics Data System (ADS)

Pearlman, Jay; Benedict, Karl; Best, Mairi; Fyfe, Sue; Jacobs, Cliff; Michener, William; Nativi, Stefano; Powers, Lindsay; Turner, Andrew

2016-04-01

Sustainability of software and research support systems is an element of innovation that is not often discussed. Yet, sustainment is essential if we expect research communities to make the time investment to learn and adopt new technologies. As the Research Data Alliance (RDA) is developing new approaches to interoperability, the question of uptake and sustainability is important. Brokering software sustainability is one of the areas that is being addressed in RDA. The Business Models Team of the Research Data Alliance Brokering Governance Working Group examined several support models proposed to promote the long-term sustainability of brokering middleware. The business model analysis includes examination of funding source, implementation frameworks and challenges, and policy and legal considerations. Results of this comprehensive analysis highlight advantages and disadvantages of the various models with respect to the specific requirements for brokering services. We offer recommendations based on the outcomes of this analysis that suggest that hybrid funding models present the most likely avenue to long term sustainability.

Knowledge and attitude toward interdisciplinary team working among obstetricians and gynecologists in teaching hospitals in South East Nigeria.

PubMed

Iyoke, Chukwuemeka Anthony; Lawani, Lucky Osaheni; Ugwu, George Onyemaechi; Ajah, Leonard Ogbonna; Ezugwu, Euzebus Chinonye; Onah, Paul; Onwuka, Chidinma Ifechi

2015-01-01

Interdisciplinary team working could facilitate the efficient provision and coordination of increasingly diverse health services, thereby improving the quality of patient care. The purpose of this study was to describe knowledge of interdisciplinary team working among obstetricians and gynecologists in two teaching hospitals in South East Nigeria and to determine their attitude toward an interdisciplinary collaborative approach to patient care in these institutions. This was a questionnaire-based cross-sectional study. Data analysis involved descriptive statistics and was carried out using Statistical Package for the Social Sciences software version 17.0 for Windows. In total, 116 doctors participated in the study. The mean age of the respondents was 31.9±7.0 (range 22-51) years. Approximately 74% of respondents were aware of the concept of interdisciplinary team working. Approximately 15% of respondents who were aware of the concept of interdisciplinary team working had very good knowledge of it; 52% had good knowledge and 33% had poor knowledge. Twenty-nine percent of knowledgeable respondents reported ever receiving formal teaching/training on interdisciplinary team working in the course of their professional development. About 78% of those aware of team working believed that interdisciplinary teams would be useful in obstetrics and gynecology practice in Nigeria, with 89% stating that it would be very useful. Approximately 77% of those aware of team working would support establishment and implementation of interdisciplinary teams at their centers. There was a high degree of knowledge of the concept and a positive attitude toward interdisciplinary team working among obstetricians and gynecologists in the study centers. This suggests that the attitude of physicians may not be an impediment to implementation of a collaborative interdisciplinary approach to clinical care in the study centers.

Knowledge and attitude toward interdisciplinary team working among obstetricians and gynecologists in teaching hospitals in South East Nigeria

PubMed Central

Iyoke, Chukwuemeka Anthony; Lawani, Lucky Osaheni; Ugwu, George Onyemaechi; Ajah, Leonard Ogbonna; Ezugwu, Euzebus Chinonye; Onah, Paul; Onwuka, Chidinma Ifechi

2015-01-01

Background Interdisciplinary team working could facilitate the efficient provision and coordination of increasingly diverse health services, thereby improving the quality of patient care. The purpose of this study was to describe knowledge of interdisciplinary team working among obstetricians and gynecologists in two teaching hospitals in South East Nigeria and to determine their attitude toward an interdisciplinary collaborative approach to patient care in these institutions. Methods This was a questionnaire-based cross-sectional study. Data analysis involved descriptive statistics and was carried out using Statistical Package for the Social Sciences software version 17.0 for Windows. Results In total, 116 doctors participated in the study. The mean age of the respondents was 31.9±7.0 (range 22–51) years. Approximately 74% of respondents were aware of the concept of interdisciplinary team working. Approximately 15% of respondents who were aware of the concept of interdisciplinary team working had very good knowledge of it; 52% had good knowledge and 33% had poor knowledge. Twenty-nine percent of knowledgeable respondents reported ever receiving formal teaching/training on interdisciplinary team working in the course of their professional development. About 78% of those aware of team working believed that interdisciplinary teams would be useful in obstetrics and gynecology practice in Nigeria, with 89% stating that it would be very useful. Approximately 77% of those aware of team working would support establishment and implementation of interdisciplinary teams at their centers. Conclusion There was a high degree of knowledge of the concept and a positive attitude toward interdisciplinary team working among obstetricians and gynecologists in the study centers. This suggests that the attitude of physicians may not be an impediment to implementation of a collaborative interdisciplinary approach to clinical care in the study centers. PMID:26064058

Interdisciplinary Team Collaboration during Discharge of Depressed Older Persons: A Norwegian Qualitative Implementation Study

PubMed Central

Holm, Anne Lise; Severinsson, Elisabeth

2013-01-01

In order to deliver effective care, it is necessary to organise interdisciplinary activities for older persons who suffer from depressive disorders. This paper evaluated the interdisciplinary team members' perceptions of cooperation in the discharge planning of depressed older persons based on the Chronic Care Model (CCM). A qualitative implementation design was used, data were collected by means of multistage focus groups, and a thematic analysis was performed. Three themes emerged: lack of effective team leadership in the community, the need to change the delivery system, and enhancing self-management support for depressed older persons as well as the participation of their families. It was concluded that nurse managers must find ways of supporting the depressed older persons by better structuring the care, increasing cooperation with organisational leadership, and creating an environment characterised by trust and mutual respect. Distrust can have serious implications for discharge planning collaboration. The development of a common vision of transparency in the organization is important as is a policy of change among leadership and in clinical practice. PMID:23766896

Analysis, Design and Implementation of a Networking Proof-of-Concept Prototype to Support Maritime Visit, Board, Search and Seizure Teams

DTIC Science & Technology

2014-03-01

M. Callaghan ( AKR -1001). Retrieved from http://www.navsource.org/archives/09/54/541001.htm Nguyen, H., & Baker, M. (2012). Characteristics of a ...AND IMPLEMENTATION OF A NETWORKING PROOF-OF-CONCEPT PROTOTYPE TO SUPPORT MARITIME VISIT, BOARD, SEARCH AND SEIZURE TEAMS by Van E. Stewart...2. REPORT DATE March 2014 3. REPORT TYPE AND DATES COVERED Master’s Thesis 4. TITLE AND SUBTITLE ANALYSIS, DESIGN AND IMPLEMENTATION OF A

Achieving Agility and Stability in Large-Scale Software Development

DTIC Science & Technology

2013-01-16

temporary team is assigned to prepare layers and frameworks for future feature teams. Presentation Layer Domain Layer Data Access Layer...http://www.sei.cmu.edu/training/ elearning ~ Software Engineering Institute CarnegieMellon

Managing Communication among Geographically Distributed Teams: A Brazilian Case

NASA Astrophysics Data System (ADS)

Almeida, Ana Carina M.; de Farias Junior, Ivaldir H.; de S. Carneiro, Pedro Jorge

The growing demand for qualified professionals is making software companies opt for distributed software development (DSD). At the project conception, communication and synchronization of information are critical factors for success. However problems such as time-zone difference between teams, culture, language and different development processes among sites could difficult the communication among teams. In this way, the main goal of this paper is to describe the solution adopted by a Brazilian team to improve communication in a multisite project environment. The purposed solution was based on the best practices described in the literature, and the communication plan was created based on the infrastructure needed by the project. The outcome of this work is to minimize the impact of communication issues in multisite projects, increasing productivity, good understanding and avoiding rework on code and document writing.

Software interface verifier

NASA Technical Reports Server (NTRS)

Soderstrom, Tomas J.; Krall, Laura A.; Hope, Sharon A.; Zupke, Brian S.

1994-01-01

A Telos study of 40 recent subsystem deliveries into the DSN at JPL found software interface testing to be the single most expensive and error-prone activity, and the study team suggested creating an automated software interface test tool. The resulting Software Interface Verifier (SIV), which was funded by NASA/JPL and created by Telos, employed 92 percent software reuse to quickly create an initial version which incorporated early user feedback. SIV is now successfully used by developers for interface prototyping and unit testing, by test engineers for formal testing, and by end users for non-intrusive data flow tests in the operational environment. Metrics, including cost, are included. Lessons learned include the need for early user training. SIV is ported to many platforms and can be successfully used or tailored by other NASA groups.

Team-based Learning in Therapeutics Workshop Sessions

PubMed Central

Kelley, Katherine A.; Metzger, Anne H.; Bellebaum, Katherine L.; McAuley, James W.

2009-01-01

Objectives To implement team-based learning in the workshop portion of a pathophysiology and therapeutics sequence of courses to promote integration of concepts across the pharmacy curriculum, provide a consistent problem-solving approach to patient care, and determine the impact on student perceptions of professionalism and teamwork. Design Team-based learning was incorporated into the workshop portion of 3 of 6 pathophysiology and therapeutics courses. Assignments that promoted team-building and application of key concepts were created. Assessment Readiness assurance tests were used to assess individual and team understanding of course materials. Students consistently scored 20% higher on team assessments compared with individual assessments. Mean professionalism and teamwork scores were significantly higher after implementation of team-based learning; however, this improvement was not considered educationally significant. Approximately 91% of students felt team-based learning improved understanding of course materials and 93% of students felt teamwork should continue in workshops. Conclusion Team-based learning is an effective teaching method to ensure a consistent approach to problem-solving and curriculum integration in workshop sessions for a pathophysiology and therapeutics course sequence. PMID:19885069

Team-based learning in therapeutics workshop sessions.

PubMed

Beatty, Stuart J; Kelley, Katherine A; Metzger, Anne H; Bellebaum, Katherine L; McAuley, James W

2009-10-01

To implement team-based learning in the workshop portion of a pathophysiology and therapeutics sequence of courses to promote integration of concepts across the pharmacy curriculum, provide a consistent problem-solving approach to patient care, and determine the impact on student perceptions of professionalism and teamwork. Team-based learning was incorporated into the workshop portion of 3 of 6 pathophysiology and therapeutics courses. Assignments that promoted team-building and application of key concepts were created. Readiness assurance tests were used to assess individual and team understanding of course materials. Students consistently scored 20% higher on team assessments compared with individual assessments. Mean professionalism and teamwork scores were significantly higher after implementation of team-based learning; however, this improvement was not considered educationally significant. Approximately 91% of students felt team-based learning improved understanding of course materials and 93% of students felt teamwork should continue in workshops. Team-based learning is an effective teaching method to ensure a consistent approach to problem-solving and curriculum integration in workshop sessions for a pathophysiology and therapeutics course sequence.

Improving service user self-management: development and implementation of a strategy for the Richmond Response and Rehabilitation Team.

PubMed

Sanders, Julie; Fitzpatrick, Joanne M

2017-01-01

Community rapid response and rehabilitation teams are used to prevent avoidable hospital admissions for adults living with multiple long-term conditions and to support early hospital discharge by providing short-term intensive multidisciplinary support. Supporting self-management is an important service intervention if desired outcomes are to be achieved. A Care Quality Commission inspection of the Richmond Response and Rehabilitation Team in 2014 identified that self-management plans were not routinely developed with service users and reported this as requiring improvement. This quality improvement project aimed to develop and implement a self-management strategy for service users and for 90% of service users to have a personalised self-management plan within 3 months. The quality improvement intervention used the Plan-Do-Study-Act model comprising: (1) the development of a self-management plan, (2) staff education to support service users to self-manage using motivational interviewing techniques, (3) piloting the self-management plan with service users, (4) implementation of the self-management plan and (5) monthly audit and feedback. Evaluation involved an audit of the number and quality of self-management plans developed with service users and a survey of staff knowledge and confidence to support service users to self-manage. Following implementation of the intervention, the number of self-management plans developed in collaboration with service users increased from 0 to 187 over a 4-week period. Monthly audit data confirmed that this improvement has been sustained. Results indicated that staff knowledge and confidence improved after an education intervention. Quality improvement methods facilitated development and operationalisation of a self-management strategy by a community rapid response and rehabilitation team. The next phase of the project is to evaluate the impact of the self-management strategy on key service outcomes including self-efficacy, unplanned

Implementation of a model of robotic tele-presence (RTP) in the neuro-ICU: effect on critical care nursing team satisfaction.

PubMed

Rincon, Fred; Vibbert, Matthew; Childs, Valerie; Fry, Robin; Caliguri, Dennis; Urtecho, Jacqueline; Rosenwasser, Robert; Jallo, Jack

2012-08-01

Robotic tele-presence (RTP) is a form of mobile telemedicine, which enables a direct face-to-face rapid response by the physician, instead of the traditional telephonic paradigm. We hypothesized that a model of RTP for after-hour ICU rounds and emergencies would be associated with improved ICU nurse satisfaction. We implemented a prospective nighttime multidisciplinary ICU round time, using RTP at our neuro-ICU. To test for critical ICU nurse team satisfaction, a questionnaire was implemented. The primary outcome was nurse satisfaction measured through a questionnaire with answers trichotomized into: agreement, disagreement, and no opinion. The occurrence of outcomes was compared between the groups by χ2 or Fisher exact tests for the difference in proportions (PD) with Bonferroni correction for multiple pairwise comparisons. In total, 34 nurses completed the pre-survey and 40 nurses completed the post-survey. Night nurses were more likely to agree that RTP was associated with: ICU physicians being sufficiently available in the ICU (agreement 6-20%, PD 14%, p = 0.008), present during acute emergencies (agreement 44-65%, PD 21%, p = 0.007), and had enough time to get questions answered from the physician team (agreement 41-53%, PD 11%, p = NS). This data suggest improvement in critical care nursing team satisfaction with a model of RTP in the neuroscience ICU, particularly during nighttime hours. RTP is a tool that may enhance communication among components of the ICU team.

Countywide implementation of crisis intervention teams: Multiple methods, measures and sustained outcomes.

PubMed

Kubiak, Sheryl; Comartin, Erin; Milanovic, Edita; Bybee, Deborah; Tillander, Elizabeth; Rabaut, Celeste; Bisson, Heidi; Dunn, Lisa M; Bouchard, Michael J; Hill, Todd; Schneider, Steven

2017-09-01

The crisis intervention team (CIT) is a tool that can be used to foster pre-booking diversion of individuals with mental illness from the criminal justice system and into community treatment services. Although CIT is often implemented solely as the training of law enforcement officers, the model stipulates that CIT is a vehicle for collaboration with community stakeholders who share a similar philosophy, as well as expanded mental health services offering a 24 hour-seven days per week drop-off option for law enforcement officers. This case study presents the countywide implementation of CIT and expands previous findings on the prevalence of officer interaction with persons with mental health issues and CIT training outcomes, including changes in officer perception of individuals with mental health issues. Furthermore, analysis of the disposition of calls for officer assistance coded as mental health or suicide found significant increases in officer drop-offs to the mental health crisis center post-CIT training. Interrupted time series analysis determined that this change has been sustained over time, perhaps owing to the unique communication between county law enforcement and mental health staff. Implications for policy and practice are discussed. Copyright © 2017 John Wiley & Sons, Ltd.

WebStruct and VisualStruct: Web interfaces and visualization for Structure software implemented in a cluster environment.

PubMed

Jayashree, B; Rajgopal, S; Hoisington, D; Prasanth, V P; Chandra, S

2008-09-24

Structure, is a widely used software tool to investigate population genetic structure with multi-locus genotyping data. The software uses an iterative algorithm to group individuals into "K" clusters, representing possibly K genetically distinct subpopulations. The serial implementation of this programme is processor-intensive even with small datasets. We describe an implementation of the program within a parallel framework. Speedup was achieved by running different replicates and values of K on each node of the cluster. A web-based user-oriented GUI has been implemented in PHP, through which the user can specify input parameters for the programme. The number of processors to be used can be specified in the background command. A web-based visualization tool "Visualstruct", written in PHP (HTML and Java script embedded), allows for the graphical display of population clusters output from Structure, where each individual may be visualized as a line segment with K colors defining its possible genomic composition with respect to the K genetic sub-populations. The advantage over available programs is in the increased number of individuals that can be visualized. The analyses of real datasets indicate a speedup of up to four, when comparing the speed of execution on clusters of eight processors with the speed of execution on one desktop. The software package is freely available to interested users upon request.

Achieving Agility and Stability in Large-Scale Software Development

DTIC Science & Technology

2013-01-16

temporary team is assigned to prepare layers and frameworks for future feature teams. Presentation Layer Domain Layer Data Access Layer Framework...http://www.sei.cmu.edu/training/ elearning ~ Software Engineering Institute CarnegieMellon

Managing MDO Software Development Projects

NASA Technical Reports Server (NTRS)

Townsend, J. C.; Salas, A. O.

2002-01-01

Over the past decade, the NASA Langley Research Center developed a series of 'grand challenge' applications demonstrating the use of parallel and distributed computation and multidisciplinary design optimization. All but the last of these applications were focused on the high-speed civil transport vehicle; the final application focused on reusable launch vehicles. Teams of discipline experts developed these multidisciplinary applications by integrating legacy engineering analysis codes. As teams became larger and the application development became more complex with increasing levels of fidelity and numbers of disciplines, the need for applying software engineering practices became evident. This paper briefly introduces the application projects and then describes the approaches taken in project management and software engineering for each project; lessons learned are highlighted.

UTM TCL2 Software Requirements

NASA Technical Reports Server (NTRS)

Smith, Irene S.; Rios, Joseph L.; McGuirk, Patrick O.; Mulfinger, Daniel G.; Venkatesan, Priya; Smith, David R.; Baskaran, Vijayakumar; Wang, Leo

2017-01-01

The Unmanned Aircraft Systems (UAS) Traffic Management (UTM) Technical Capability Level (TCL) 2 software implements the UTM TCL 2 software requirements described herein. These software requirements are linked to the higher level UTM TCL 2 System Requirements. Each successive TCL implements additional UTM functionality, enabling additional use cases. TCL 2 demonstrated how to enable expanded multiple operations by implementing automation for beyond visual line-of-sight, tracking operations, and operations flying over sparsely populated areas.

Innovating team-based outpatient mental health care in the Veterans Health Administration: Staff-perceived benefits and challenges to pilot implementation of the Behavioral Health Interdisciplinary Program (BHIP).

PubMed

Barry, Catherine N; Abraham, Kristen M; Weaver, Kendra R; Bowersox, Nicholas W

2016-05-01

In the past decade, the demand for Veterans Health Administration (VHA) mental health care has increased rapidly. In response to the increased demand, the VHA developed the Behavioral Health Interdisciplinary Program (BHIP) team model as an innovative approach to transform VHA general outpatient mental health delivery. The present formative evaluation gathered information about pilot implementation of BHIP to understand the struggles and successes that staff experienced during facility transitions to the BHIP model. Using a purposive, nonrandom sampling approach, we conducted 1-on-1, semistructured interviews with 37 licensed and nonlicensed clinical providers and 13 clerical support staff assigned to BHIP teams in 21 facilities across the VHA. Interviews revealed that having actively involved facility mental health leaders, obtaining adequate staffing for teams to meet the requirements of the BHIP model, creating clear descriptions and expectations for team member roles within the BHIP framework, and allocating designated time for BHIP team meetings challenged many VHA sites but are crucial for successful BHIP implementation. Despite the challenges, staff reported that the transition to BHIP improved team work and improved patient care. Staff specifically highlighted the potential for the BHIP model to improve staff working relationships and enhance communication, collaboration, morale, and veteran treatment consistency. Future evaluations of the BHIP implementation process and BHIP team functioning focusing on patient outcomes, organizational outcomes, and staff functioning are recommended for fully understanding effects of transitioning to the BHIP model within VHA general mental health clinics and to identify best practices and areas for improvement. (PsycINFO Database Record (c) 2016 APA, all rights reserved).

Implementation and Evaluation of a Team Simulation Training Program.

PubMed

Rice, Yvonne; DeLetter, Mary; Fryman, Lisa; Parrish, Evelyn; Velotta, Cathie; Talley, Cynthia

2016-01-01

Care of the trauma patient requires a well-coordinated intensive effort during the golden hour to optimize survival. We hypothesized that this program would improve knowledge, satisfaction, self-confidence, and simulated team performance. A pre-, post-test design with N = 7 BSN nurses, 21 years of age, less than 2 years of intensive care unit and nursing experience. Trauma intensive care unit, single-center academic Level 1 trauma center. Improvement was shown in perception of team structure (paired t test 13.71-12.57; p = .0001) and communication (paired t test 14.85-12.14; p = .009). Improvement was shown in observed situation monitoring (paired t test 17.42-25.28; p = .000), mutual support (paired t test 12.57-18.57; p = .000), and communication (paired t test 15.42-25.00; p = .001). A decrease was shown in attitudes of mutual support (paired t test 25.85-19.71; p = .04) and communication (paired t test 26.14-23.00; p = .001). Mean satisfaction scores were 21.5 of a possible 25 points. Mean self-confidence scores were 38.83 out of a possible 40 points. Simulation-based team training improved teamwork attitudes, perceptions, and performance. Team communication demonstrated significant improvement in 2 of the 3 instruments. Most participants agreed or strongly agreed that they were satisfied with simulation and had gained self-confidence.

ToxPredictor: a Toxicity Estimation Software Tool

EPA Science Inventory

The Computational Toxicology Team within the National Risk Management Research Laboratory has developed a software tool that will allow the user to estimate the toxicity for a variety of endpoints (such as acute aquatic toxicity). The software tool is coded in Java and can be ac...

Software thresholds alter the bias of actigraphy for monitoring sleep in team-sport athletes.

PubMed

Fuller, Kate L; Juliff, Laura; Gore, Christopher J; Peiffer, Jeremiah J; Halson, Shona L

2017-08-01

Actical ® actigraphy is commonly used to monitor athlete sleep. The proprietary software, called Actiware ® , processes data with three different sleep-wake thresholds (Low, Medium or High), but there is no standardisation regarding their use. The purpose of this study was to examine validity and bias of the sleep-wake thresholds for processing Actical ® sleep data in team sport athletes. Validation study comparing actigraph against accepted gold standard polysomnography (PSG). Sixty seven nights of sleep were recorded simultaneously with polysomnography and Actical ® devices. Individual night data was compared across five sleep measures for each sleep-wake threshold using Actiware ® software. Accuracy of each sleep-wake threshold compared with PSG was evaluated from mean bias with 95% confidence limits, Pearson moment-product correlation and associated standard error of estimate. The Medium threshold generated the smallest mean bias compared with polysomnography for total sleep time (8.5min), sleep efficiency (1.8%) and wake after sleep onset (-4.1min); whereas the Low threshold had the smallest bias (7.5min) for wake bouts. Bias in sleep onset latency was the same across thresholds (-9.5min). The standard error of the estimate was similar across all thresholds; total sleep time ∼25min, sleep efficiency ∼4.5%, wake after sleep onset ∼21min, and wake bouts ∼8 counts. Sleep parameters measured by the Actical ® device are greatly influenced by the sleep-wake threshold applied. In the present study the Medium threshold produced the smallest bias for most parameters compared with PSG. Given the magnitude of measurement variability, confidence limits should be employed when interpreting changes in sleep parameters. Copyright © 2017 Sports Medicine Australia. All rights reserved.

An SAS Macro for Implementing the Modified Bollen-Stine Bootstrap for Missing Data: Implementing the Bootstrap Using Existing Structural Equation Modeling Software

ERIC Educational Resources Information Center

Enders, Craig K.

2005-01-01

The Bollen-Stine bootstrap can be used to correct for standard error and fit statistic bias that occurs in structural equation modeling (SEM) applications due to nonnormal data. The purpose of this article is to demonstrate the use of a custom SAS macro program that can be used to implement the Bollen-Stine bootstrap with existing SEM software.…

The Navy’s Management of Software Licenses Needs Improvement

DTIC Science & Technology

2013-08-07

Enterprise Software Licensing ( ESL ) as a primary DON etliciency target. Through policy and Integrated Product Team actions, this efficiency...review, as well as with DoD Enterprise Software Initiative ( ESl ) Blanket Pw·chase Agreements and any r•elated fedeml Acquisition Regulation and General...organizational and multi-functional DON ESL team. The DON is also participating in DoD level enterprise softwru·e licensing project~ through the Dol

NASA Software Engineering Benchmarking Study

NASA Technical Reports Server (NTRS)

Rarick, Heather L.; Godfrey, Sara H.; Kelly, John C.; Crumbley, Robert T.; Wifl, Joel M.

2013-01-01

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths

Team learning and innovation in nursing, a review of the literature.

PubMed

Timmermans, Olaf; Van Linge, Roland; Van Petegem, Peter; Van Rompaey, Bart; Denekens, Joke

2012-01-01

The capability to learn and innovate has been recognized as a key-factor for nursing teams to deliver high quality performance. Researchers suggest there is a relation between team-learning activities and changes in nursing teams throughout the implementation of novelties. A review of the literature was conducted in regard to the relation between team learning and implementation of innovations in nursing teams and to explore factors that contribute or hinder team learning. The search was limited to studies that were published in English or Dutch between 1998 and 2010. Eight studies were included in the review. The results of this review revealed that research on team learning and innovation in nursing is limited. The included studies showed moderate methodological quality and low levels of evidence. Team learning included processes to gather, process, and store information from different innovations within the nursing team and the prevalence of team-learning activities was contributed or hindered by individual and contextual factors. Further research is needed on the relation between team learning and implementation of innovations in nursing. Copyright © 2011 Elsevier Ltd. All rights reserved.

Fault tolerant software modules for SIFT

NASA Technical Reports Server (NTRS)

Hecht, M.; Hecht, H.

1982-01-01

The implementation of software fault tolerance is investigated for critical modules of the Software Implemented Fault Tolerance (SIFT) operating system to support the computational and reliability requirements of advanced fly by wire transport aircraft. Fault tolerant designs generated for the error reported and global executive are examined. A description of the alternate routines, implementation requirements, and software validation are included.

Evaluation of tactical training in team handball by means of artificial neural networks.

PubMed

Hassan, Amr; Schrapf, Norbert; Ramadan, Wael; Tilp, Markus

2017-04-01

While tactical performance in competition has been analysed extensively, the assessment of training processes of tactical behaviour has rather been neglected in the literature. Therefore, the purpose of this study is to provide a methodology to assess the acquisition and implementation of offensive tactical behaviour in team handball. The use of game analysis software combined with an artificial neural network (ANN) software enabled identifying tactical target patterns from high level junior players based on their positions during offensive actions. These patterns were then trained by an amateur junior handball team (n = 14, 17 (0.5) years)). Following 6 weeks of tactical training an exhibition game was performed where the players were advised to use the target patterns as often as possible. Subsequently, the position data of the game was analysed with an ANN. The test revealed that 58% of the played patterns could be related to the trained target patterns. The similarity between executed patterns and target patterns was assessed by calculating the mean distance between key positions of the players in the game and the target pattern which was 0.49 (0.20) m. In summary, the presented method appears to be a valid instrument to assess tactical training.

NASA's Software Safety Standard

NASA Technical Reports Server (NTRS)

Ramsay, Christopher M.

2007-01-01

NASA relies more and more on software to control, monitor, and verify its safety critical systems, facilities and operations. Since the 1960's there has hardly been a spacecraft launched that does not have a computer on board that will provide command and control services. There have been recent incidents where software has played a role in high-profile mission failures and hazardous incidents. For example, the Mars Orbiter, Mars Polar Lander, the DART (Demonstration of Autonomous Rendezvous Technology), and MER (Mars Exploration Rover) Spirit anomalies were all caused or contributed to by software. The Mission Control Centers for the Shuttle, ISS, and unmanned programs are highly dependant on software for data displays, analysis, and mission planning. Despite this growing dependence on software control and monitoring, there has been little to no consistent application of software safety practices and methodology to NASA's projects with safety critical software. Meanwhile, academia and private industry have been stepping forward with procedures and standards for safety critical systems and software, for example Dr. Nancy Leveson's book Safeware: System Safety and Computers. The NASA Software Safety Standard, originally published in 1997, was widely ignored due to its complexity and poor organization. It also focused on concepts rather than definite procedural requirements organized around a software project lifecycle. Led by NASA Headquarters Office of Safety and Mission Assurance, the NASA Software Safety Standard has recently undergone a significant update. This new standard provides the procedures and guidelines for evaluating a project for safety criticality and then lays out the minimum project lifecycle requirements to assure the software is created, operated, and maintained in the safest possible manner. This update of the standard clearly delineates the minimum set of software safety requirements for a project without detailing the implementation for those

Experimental research control software system

NASA Astrophysics Data System (ADS)

Cohn, I. A.; Kovalenko, A. G.; Vystavkin, A. N.

2014-05-01

A software system, intended for automation of a small scale research, has been developed. The software allows one to control equipment, acquire and process data by means of simple scripts. The main purpose of that development is to increase experiment automation easiness, thus significantly reducing experimental setup automation efforts. In particular, minimal programming skills are required and supervisors have no reviewing troubles. Interactions between scripts and equipment are managed automatically, thus allowing to run multiple scripts simultaneously. Unlike well-known data acquisition commercial software systems, the control is performed by an imperative scripting language. This approach eases complex control and data acquisition algorithms implementation. A modular interface library performs interaction with external interfaces. While most widely used interfaces are already implemented, a simple framework is developed for fast implementations of new software and hardware interfaces. While the software is in continuous development with new features being implemented, it is already used in our laboratory for automation of a helium-3 cryostat control and data acquisition. The software is open source and distributed under Gnu Public License.

Design and implementation of software for automated quality control and data analysis for a complex LC/MS/MS assay for urine opiates and metabolites.

PubMed

Dickerson, Jane A; Schmeling, Michael; Hoofnagle, Andrew N; Hoffman, Noah G

2013-01-16

Mass spectrometry provides a powerful platform for performing quantitative, multiplexed assays in the clinical laboratory, but at the cost of increased complexity of analysis and quality assurance calculations compared to other methodologies. Here we describe the design and implementation of a software application that performs quality control calculations for a complex, multiplexed, mass spectrometric analysis of opioids and opioid metabolites. The development and implementation of this application improved our data analysis and quality assurance processes in several ways. First, use of the software significantly improved the procedural consistency for performing quality control calculations. Second, it reduced the amount of time technologists spent preparing and reviewing the data, saving on average over four hours per run, and in some cases improving turnaround time by a day. Third, it provides a mechanism for coupling procedural and software changes with the results of each analysis. We describe several key details of the implementation including the use of version control software and automated unit tests. These generally useful software engineering principles should be considered for any software development project in the clinical lab. Copyright © 2012 Elsevier B.V. All rights reserved.

The design and implementation of a parallel unstructured Euler solver using software primitives

NASA Technical Reports Server (NTRS)

Das, R.; Mavriplis, D. J.; Saltz, J.; Gupta, S.; Ponnusamy, R.

1992-01-01

This paper is concerned with the implementation of a three-dimensional unstructured grid Euler-solver on massively parallel distributed-memory computer architectures. The goal is to minimize solution time by achieving high computational rates with a numerically efficient algorithm. An unstructured multigrid algorithm with an edge-based data structure has been adopted, and a number of optimizations have been devised and implemented in order to accelerate the parallel communication rates. The implementation is carried out by creating a set of software tools, which provide an interface between the parallelization issues and the sequential code, while providing a basis for future automatic run-time compilation support. Large practical unstructured grid problems are solved on the Intel iPSC/860 hypercube and Intel Touchstone Delta machine. The quantitative effect of the various optimizations are demonstrated, and we show that the combined effect of these optimizations leads to roughly a factor of three performance improvement. The overall solution efficiency is compared with that obtained on the CRAY-YMP vector supercomputer.

Toward fidelity between specification and implementation

NASA Technical Reports Server (NTRS)

Callahan, John R.; Montgomery, Todd L.; Morrison, Jeff; Wu, Yunqing

1994-01-01

This paper describes the methods used to specify and implement a complex communications protocol that provides reliable delivery of data in multicast-capable, packet-switching telecommunication networks. The protocol, called the Reliable Multicasting Protocol (RMP), was developed incrementally by two complementary teams using a combination of formal and informal techniques in an attempt to ensure the correctness of the protocol implementation. The first team, called the Design team, initially specified protocol requirements using a variant of SCR requirements tables and implemented a prototype solution. The second team, called the V&V team, developed a state model based on the requirements tables and derived test cases from these tables to exercise the implementation. In a series of iterative steps, the Design team added new functionality to the implementation while the V&V team kept the state model in fidelity with the implementation through testing. Test cases derived from state transition paths in the formal model formed the dialogue between teams during development and served as the vehicles for keeping the model and implementation in fidelity with each other. This paper describes our experiences in developing our process model, details of our approach, and some example problems found during the development of RMP.

Leader Humility and Team Innovation: Investigating the Substituting Role of Task Interdependence and the Mediating Role of Team Voice Climate

PubMed Central

Liu, Wenxing; Mao, Jianghua; Chen, Xiao

2017-01-01

Leadership has been found to be linked with team innovation. Based on social information processing theory and substitutes for leadership theory, this paper examines the influence of leader humility on team innovation. Results from 90 teams showed that leader humility will enhance team innovation by fostering team voice climate. Further, task interdependence substitutes the effect of leader humility on team innovation through an indirect way via team voice climate. This study discussed the theoretical and practical implementations of these observations. PMID:28713316

Leader Humility and Team Innovation: Investigating the Substituting Role of Task Interdependence and the Mediating Role of Team Voice Climate.

PubMed

Liu, Wenxing; Mao, Jianghua; Chen, Xiao

2017-01-01

Leadership has been found to be linked with team innovation. Based on social information processing theory and substitutes for leadership theory, this paper examines the influence of leader humility on team innovation. Results from 90 teams showed that leader humility will enhance team innovation by fostering team voice climate. Further, task interdependence substitutes the effect of leader humility on team innovation through an indirect way via team voice climate. This study discussed the theoretical and practical implementations of these observations.

STAR Algorithm Integration Team - Facilitating operational algorithm development

NASA Astrophysics Data System (ADS)

Mikles, V. J.

2015-12-01

The NOAA/NESDIS Center for Satellite Research and Applications (STAR) provides technical support of the Joint Polar Satellite System (JPSS) algorithm development and integration tasks. Utilizing data from the S-NPP satellite, JPSS generates over thirty Environmental Data Records (EDRs) and Intermediate Products (IPs) spanning atmospheric, ocean, cryosphere, and land weather disciplines. The Algorithm Integration Team (AIT) brings technical expertise and support to product algorithms, specifically in testing and validating science algorithms in a pre-operational environment. The AIT verifies that new and updated algorithms function in the development environment, enforces established software development standards, and ensures that delivered packages are functional and complete. AIT facilitates the development of new JPSS-1 algorithms by implementing a review approach based on the Enterprise Product Lifecycle (EPL) process. Building on relationships established during the S-NPP algorithm development process and coordinating directly with science algorithm developers, the AIT has implemented structured reviews with self-contained document suites. The process has supported algorithm improvements for products such as ozone, active fire, vegetation index, and temperature and moisture profiles.

A qualitative study identifying the cost categories associated with electronic health record implementation in the UK

PubMed Central

Slight, Sarah P; Quinn, Casey; Avery, Anthony J; Bates, David W; Sheikh, Aziz

2014-01-01

Objective We conducted a prospective evaluation of different forms of electronic health record (EHR) systems to better understand the costs incurred during implementation and the factors that can influence these costs. Methods We selected a range of diverse organizations across three different geographical areas in England that were at different stages of implementing three centrally procured applications, that is, iSOFT's Lorenzo Regional Care, Cerner's Millennium, and CSE's RiO. 41 semi-structured interviews were conducted with hospital staff, members of the implementation team, and those involved in the implementation at a national level. Results Four main overarching cost categories were identified: infrastructure (eg, hardware and software), personnel (eg, training team), estates/facilities (eg, space), and other (eg, training materials). Many factors were felt to impact on these costs, with different hospitals choosing varying amounts and types of infrastructure, diverse training approaches for staff, and different software applications to integrate with the new system. Conclusions Improving the quality and safety of patient care through EHR adoption is a priority area for UK and US governments and policy makers worldwide. With cost considered one of the most significant barriers, it is important for hospitals and governments to be clear from the outset of the major cost categories involved and the factors that may impact on these costs. Failure to adequately train staff or to follow key steps in implementation has preceded many of the failures in this domain, which can create new safety hazards. PMID:24523391

Software engineering risk factors in the implementation of a small electronic medical record system: the problem of scalability.

PubMed

Chiang, Michael F; Starren, Justin B

2002-01-01

The successful implementation of clinical information systems is difficult. In examining the reasons and potential solutions for this problem, the medical informatics community may benefit from the lessons of a rich body of software engineering and management literature about the failure of software projects. Based on previous studies, we present a conceptual framework for understanding the risk factors associated with large-scale projects. However, the vast majority of existing literature is based on large, enterprise-wide systems, and it unclear whether those results may be scaled down and applied to smaller projects such as departmental medical information systems. To examine this issue, we discuss the case study of a delayed electronic medical record implementation project in a small specialty practice at Columbia-Presbyterian Medical Center. While the factors contributing to the delay of this small project share some attributes with those found in larger organizations, there are important differences. The significance of these differences for groups implementing small medical information systems is discussed.

Reinventing The Design Process: Teams and Models

NASA Technical Reports Server (NTRS)

Wall, Stephen D.

1999-01-01

The future of space mission designing will be dramatically different from the past. Formerly, performance-driven paradigms emphasized data return with cost and schedule being secondary issues. Now and in the future, costs are capped and schedules fixed-these two variables must be treated as independent in the design process. Accordingly, JPL has redesigned its design process. At the conceptual level, design times have been reduced by properly defining the required design depth, improving the linkages between tools, and managing team dynamics. In implementation-phase design, system requirements will be held in crosscutting models, linked to subsystem design tools through a central database that captures the design and supplies needed configuration management and control. Mission goals will then be captured in timelining software that drives the models, testing their capability to execute the goals. Metrics are used to measure and control both processes and to ensure that design parameters converge through the design process within schedule constraints. This methodology manages margins controlled by acceptable risk levels. Thus, teams can evolve risk tolerance (and cost) as they would any engineering parameter. This new approach allows more design freedom for a longer time, which tends to encourage revolutionary and unexpected improvements in design.

Building the dream team: don't make it a nightmare.

PubMed

Nelson, M; Nelson, S

1997-11-01

This article covers the often overlooked area of team management concepts through a discussion of what many companies have done to implement these new concepts successfully. It describes the basics of how to and also explains why people resist the process of implementation. The main topics are (1) team formation, (2) pitfalls to avoid, and (3) team measurement.

Trainees as Teachers in Team-Based Learning

ERIC Educational Resources Information Center

Ravindranath, Divy; Gay, Tamara L.; Riba, Michelle B.

2010-01-01

Objective: Team-based learning is an active learning modality that is gaining popularity in medical education. The authors studied the effect of using trainees as facilitators of team-based learning sessions. Methods: Team-based learning modules were developed and implemented by faculty members and trainees for the third-year medical student…

What is needed to implement a web-based audit and feedback intervention with outreach visits to improve care quality: A concept mapping study among cardiac rehabilitation teams.

PubMed

van Engen-Verheul, Mariëtte M; Peek, Niels; Haafkens, Joke A; Joukes, Erik; Vromen, Tom; Jaspers, Monique W M; de Keizer, Nicolette F

2017-01-01

Evidence on successful quality improvement (QI) in health care requires quantitative information from randomized clinical trials (RCTs) on the effectiveness of QI interventions, but also qualitative information from professionals to understand factors influencing QI implementation. Using a structured qualitative approach, concept mapping, this study determines factors identified by cardiac rehabilitation (CR) teams on what is needed to successfully implement a web-based audit and feedback (A&F) intervention with outreach visits to improve the quality of CR care. Participants included 49 CR professionals from 18 Dutch CR centres who had worked with the A&F system during a RCT. In three focus group sessions participants formulated statements on factors needed to implement QI successfully. Subsequently, participants rated all statements for importance and feasibility and grouped them thematically. Multi dimensional scaling was used to produce a final concept map. Forty-two unique statements were formulated and grouped into five thematic clusters in the concept map. The cluster with the highest importance was QI team commitment, followed by organisational readiness, presence of an adequate A&F system, access to an external quality assessor, and future use and functionalities of the A&F system. Concept mapping appeared efficient and useful to understand contextual factors influencing QI implementation as perceived by healthcare teams. While presence of a web-based A&F system and external quality assessor were seen as instrumental for gaining insight into performance and formulating QI actions, QI team commitment and organisational readiness were perceived as essential to actually implement and carry out these actions. These two sociotechnical factors should be taken into account when implementing and evaluating the success of QI implementations in future research. Copyright © 2016. Published by Elsevier Ireland Ltd.

NASA Software Safety Standard

NASA Technical Reports Server (NTRS)

Rosenberg, Linda

1997-01-01

If software is a critical element in a safety critical system, it is imperative to implement a systematic approach to software safety as an integral part of the overall system safety programs. The NASA-STD-8719.13A, "NASA Software Safety Standard", describes the activities necessary to ensure that safety is designed into software that is acquired or developed by NASA, and that safety is maintained throughout the software life cycle. A PDF version, is available on the WWW from Lewis. A Guidebook that will assist in the implementation of the requirements in the Safety Standard is under development at the Lewis Research Center (LeRC). After completion, it will also be available on the WWW from Lewis.

The Virtual Intercultural Team Tool

ERIC Educational Resources Information Center

Rus, Calin

2010-01-01

This article describes the Virtual Intercultural Team Tool (VITT) and discusses its processes and benefits. VIIT is a virtual platform designed with the aim of assisting European project teams to improve intercultural communication and build on their cultural diversity for effective implementation of their projects. It is a process-focused tool,…

Space and Missile Systems Center Standard: Software Development

DTIC Science & Technology

2015-01-16

maintenance , or any other activity or combination of activities resulting in products . Within this standard, requirements to “develop,” “define...integration, reuse, reengineering, maintenance , or any other activity that results in products ). The term “developer” encompasses all software team...activities that results in software products . Software development includes new development, modification, reuse, reengineering, maintenance , and any other

Insights of health district managers on the implementation of primary health care outreach teams in Johannesburg, South Africa: a descriptive study with focus group discussions.

PubMed

Moosa, Shabir; Derese, Anselme; Peersman, Wim

2017-01-21

Primary health care (PHC) outreach teams are part of a policy of PHC re-engineering in South Africa. It attempts to move the deployment of community health workers (CHWs) from vertical programmes into an integrated generalised team-based approach to care for defined populations in municipal wards. There has little evaluation of PHC outreach teams. Managers' insights are anecdotal. This is descriptive qualitative study with focus group discussions with health district managers of Johannesburg, the largest city in South Africa. This was conducted in a sequence of three meetings with questions around implementation, human resources, and integrated PHC teamwork. There was a thematic content analysis of validated transcripts using the framework method. There were two major themes: leadership-management challenges and human resource challenges. Whilst there was some positive sentiment, leadership-management challenges loomed large: poor leadership and planning with an under-resourced centralised approach, poor communications both within the service and with community, concerns with its impact on current services and resistance to change, and poor integration, both with other streams of PHC re-engineering and current district programmes. Discussion by managers on human resources was mostly on the plight of CHWs and calls for formalisation of CHWs functioning and training and nurse challenges with inappropriate planning and deployment of the team structure, with brief mention of the extended team. Whilst there is positive sentiment towards intent of the PHC outreach team, programme managers in Johannesburg were critical of management of the programme in their health district. Whilst the objective of PHC reform is people-centred health care, its implementation struggles with a centralising tendency amongst managers in the health service in South Africa. Managers in Johannesburg advocated for decentralisation. The implementation of PHC outreach teams is also limited by

Streamlining Software Aspects of Certification: Report on the SSAC Survey

NASA Technical Reports Server (NTRS)

Hayhurst, Kelly J.; Dorsey, Cheryl A.; Knight, John C.; Leveson, Nancy G.; McCormick, G. Frank

1999-01-01

The aviation system now depends on information technology more than ever before to ensure safety and efficiency. To address concerns about the efficacy of software aspects of the certification process, the Federal Aviation Administration (FAA) began the Streamlining Software Aspects of Certification (SSAC) program. The SSAC technical team was commissioned to gather data, analyze results, and propose recommendations to maximize efficiency and minimize cost and delay, without compromising safety. The technical team conducted two public workshops to identify and prioritize software approval issues, and conducted a survey to validate the most urgent of those issues. The SSAC survey, containing over two hundred questions about the FAA's software approval process, reached over four hundred industry software developers, aircraft manufacturers, and FAA designated engineering representatives. Three hundred people responded. This report presents the SSAC program rationale, survey process, preliminary findings, and recommendations.

PopED lite: An optimal design software for preclinical pharmacokinetic and pharmacodynamic studies.

PubMed

Aoki, Yasunori; Sundqvist, Monika; Hooker, Andrew C; Gennemark, Peter

2016-04-01

Optimal experimental design approaches are seldom used in preclinical drug discovery. The objective is to develop an optimal design software tool specifically designed for preclinical applications in order to increase the efficiency of drug discovery in vivo studies. Several realistic experimental design case studies were collected and many preclinical experimental teams were consulted to determine the design goal of the software tool. The tool obtains an optimized experimental design by solving a constrained optimization problem, where each experimental design is evaluated using some function of the Fisher Information Matrix. The software was implemented in C++ using the Qt framework to assure a responsive user-software interaction through a rich graphical user interface, and at the same time, achieving the desired computational speed. In addition, a discrete global optimization algorithm was developed and implemented. The software design goals were simplicity, speed and intuition. Based on these design goals, we have developed the publicly available software PopED lite (http://www.bluetree.me/PopED_lite). Optimization computation was on average, over 14 test problems, 30 times faster in PopED lite compared to an already existing optimal design software tool. PopED lite is now used in real drug discovery projects and a few of these case studies are presented in this paper. PopED lite is designed to be simple, fast and intuitive. Simple, to give many users access to basic optimal design calculations. Fast, to fit a short design-execution cycle and allow interactive experimental design (test one design, discuss proposed design, test another design, etc). Intuitive, so that the input to and output from the software tool can easily be understood by users without knowledge of the theory of optimal design. In this way, PopED lite is highly useful in practice and complements existing tools. Copyright © 2016 Elsevier Ireland Ltd. All rights reserved.

A multidisciplinary approach to team nursing within a low secure service: the team leader role.

PubMed

Nagi, Claire; Davies, Jason; Williams, Marie; Roberts, Catherine; Lewis, Roger

2012-01-01

This article critically examines the clinical utility of redesigning a nursing practice model within the Intensive Support and Intervention Service, a new low secure mental health facility in the United Kingdom. Specifically, the "team nursing" approach to care delivery has been adapted to consist of multidisciplinary team leaders as opposed to nursing team leaders. The authors describe the role, properties, and functions of the multidisciplinary team leader approach. The authors provide examples of the benefits and challenges posed to date and the ways in which potential barriers have been overcome. Nursing care leadership can be provided by multidisciplinary staff. An adapted model of team nursing can be implemented in a low secure setting. © 2011 Wiley Periodicals, Inc.

Distributed subterranean exploration and mapping with teams of UAVs

NASA Astrophysics Data System (ADS)

Rogers, John G.; Sherrill, Ryan E.; Schang, Arthur; Meadows, Shava L.; Cox, Eric P.; Byrne, Brendan; Baran, David G.; Curtis, J. Willard; Brink, Kevin M.

2017-05-01

Teams of small autonomous UAVs can be used to map and explore unknown environments which are inaccessible to teams of human operators in humanitarian assistance and disaster relief efforts (HA/DR). In addition to HA/DR applications, teams of small autonomous UAVs can enhance Warfighter capabilities and provide operational stand-off for military operations such as cordon and search, counter-WMD, and other intelligence, surveillance, and reconnaissance (ISR) operations. This paper will present a hardware platform and software architecture to enable distributed teams of heterogeneous UAVs to navigate, explore, and coordinate their activities to accomplish a search task in a previously unknown environment.

WFF TOPEX Software Documentation Overview, May 1999. Volume 2

NASA Technical Reports Server (NTRS)

Brooks, Ronald L.; Lee, Jeffrey

2003-01-01

This document provides an overview'of software development activities and the resulting products and procedures developed by the TOPEX Software Development Team (SWDT) at Wallops Flight Facility, in support of the WFF TOPEX Engineering Assessment and Verification efforts.

Integrated Transdisciplinary Teams.

ERIC Educational Resources Information Center

Gallivan-Fenlon, Amanda

1994-01-01

This article reviews the use of transdisciplinary teaming and integrated therapy for young children with multiple disabilities. It presents examples and suggestions for implementation, in the areas of flexibility, Individualized Education Program development, and parent participation. (JDD)

[Developing team reflexivity as a learning and working tool for medical teams].

PubMed

Riskin, Arieh; Bamberger, Peter

2014-01-01

Team reflexivity is a collective activity in which team members review their previous work, and develop ideas on how to modify their work behavior in order to achieve better future results. It is an important learning tool and a key factor in explaining the varying effectiveness of teams. Team reflexivity encompasses both self-awareness and agency, and includes three main activities: reflection, planning, and adaptation. The model of briefing-debriefing cycles promotes team reflexivity. Its key elements include: Pre-action briefing--setting objectives, roles, and strategies the mission, as well as proposing adaptations based on what was previously learnt from similar procedures; Post-action debriefing--reflecting on the procedure performed and reviewing the extent to which objectives were met, and what can be learnt for future tasks. Given the widespread attention to team-based work systems and organizational learning, efforts should be made toward ntroducing team reflexivity in health administration systems. Implementation could be difficult because most teams in hospitals are short-lived action teams formed for a particular event, with limited time and opportunity to consciously reflect upon their actions. But it is precisely in these contexts that reflexive processes have the most to offer instead of the natural impulsive collective logics. Team reflexivity suggests a potential solution to the major problems of iatorgenesis--avoidable medical errors, as it forces all team members to participate in a reflexive process together. Briefing-debriefing technology was studied mainly in surgical teams and was shown to enhance team-based learning and to improve quality-related outcomes and safety.

Team Faces Tough Odds to Implement New Phone Network | Poster

Cancer.gov

It was a Saturday, in the final stretch of winter in late February, and the temperature peaked to a pleasant 66 degrees. Many people were outside enjoying the spring-like weather; however, the Voice over Internet Protocol (VoIP) Deployment Team was hard at work at Industry Lane. The team of 10 was installing the new voice-only network, including deploying 145 phones, switching

Implementing smart infusion pumps with dose-error reduction software: real-world experiences.

PubMed

Heron, Claire

2017-04-27

Intravenous (IV) drug administration, especially with 'smart pumps', is complex and susceptible to errors. Although errors can occur at any stage of the IV medication process, most errors occur during reconstitution and administration. Dose-error reduction software (DERS) loaded on to infusion pumps incorporates a drug library with predefined upper and lower drug dose limits and infusion rates, which can reduce IV infusion errors. Although this is an important advance for patient safety at the point of care, uptake is still relatively low. This article discuses the challenges and benefits of implementing DERS in clinical practice as experienced by three UK trusts.

Bridging the gap between PAT concepts and implementation: An integrated software platform for fermentation.

PubMed

Chopda, Viki R; Gomes, James; Rathore, Anurag S

2016-01-01

Bioreactor control significantly impacts both the amount and quality of the product being manufactured. The complexity of the control strategy that is implemented increases with reactor size, which may vary from thousands to tens of thousands of litres in commercial manufacturing. The Process Analytical Technology (PAT) initiative has highlighted the need for having robust monitoring tools and effective control schemes that are capable of taking real time information about the critical quality attributes (CQA) and the critical process parameters (CPP) and executing immediate response as soon as a deviation occurs. However, the limited flexibility that present commercial software packages offer creates a hurdle. Visual programming environments have gradually emerged as potential alternatives to the available text based languages. This paper showcases development of an integrated programme using a visual programming environment for a Sartorius BIOSTAT® B Plus 5L bioreactor through which various peripheral devices are interfaced. The proposed programme facilitates real-time access to data and allows for execution of control actions to follow the desired trajectory. Major benefits of such integrated software system include: (i) improved real time monitoring and control; (ii) reduced variability; (iii) improved performance; (iv) reduced operator-training time; (v) enhanced knowledge management; and (vi) easier PAT implementation. © 2015 WILEY-VCH Verlag GmbH & Co. KGaA, Weinheim.

Final Report of the NASA Office of Safety and Mission Assurance Agile Benchmarking Team

NASA Technical Reports Server (NTRS)

Wetherholt, Martha

2016-01-01

To ensure that the NASA Safety and Mission Assurance (SMA) community remains in a position to perform reliable Software Assurance (SA) on NASAs critical software (SW) systems with the software industry rapidly transitioning from waterfall to Agile processes, Terry Wilcutt, Chief, Safety and Mission Assurance, Office of Safety and Mission Assurance (OSMA) established the Agile Benchmarking Team (ABT). The Team's tasks were: 1. Research background literature on current Agile processes, 2. Perform benchmark activities with other organizations that are involved in software Agile processes to determine best practices, 3. Collect information on Agile-developed systems to enable improvements to the current NASA standards and processes to enhance their ability to perform reliable software assurance on NASA Agile-developed systems, 4. Suggest additional guidance and recommendations for updates to those standards and processes, as needed. The ABT's findings and recommendations for software management, engineering and software assurance are addressed herein.

A Comparison of Four Software Programs for Implementing Decision Analytic Cost-Effectiveness Models.

PubMed

Hollman, Chase; Paulden, Mike; Pechlivanoglou, Petros; McCabe, Christopher

2017-08-01

The volume and technical complexity of both academic and commercial research using decision analytic modelling has increased rapidly over the last two decades. The range of software programs used for their implementation has also increased, but it remains true that a small number of programs account for the vast majority of cost-effectiveness modelling work. We report a comparison of four software programs: TreeAge Pro, Microsoft Excel, R and MATLAB. Our focus is on software commonly used for building Markov models and decision trees to conduct cohort simulations, given their predominance in the published literature around cost-effectiveness modelling. Our comparison uses three qualitative criteria as proposed by Eddy et al.: "transparency and validation", "learning curve" and "capability". In addition, we introduce the quantitative criterion of processing speed. We also consider the cost of each program to academic users and commercial users. We rank the programs based on each of these criteria. We find that, whilst Microsoft Excel and TreeAge Pro are good programs for educational purposes and for producing the types of analyses typically required by health technology assessment agencies, the efficiency and transparency advantages of programming languages such as MATLAB and R become increasingly valuable when more complex analyses are required.

Barriers and facilitators to the implementation of an evidence-based electronic minimum dataset for nursing team leader handover: A descriptive survey.

PubMed

Spooner, Amy J; Aitken, Leanne M; Chaboyer, Wendy

2017-11-15

There is widespread use of clinical information systems in intensive care units however, the evidence to support electronic handover is limited. The study aim was to assess the barriers and facilitators to use of an electronic minimum dataset for nursing team leader shift-to-shift handover in the intensive care unit prior to its implementation. The study was conducted in a 21-bed medical/surgical intensive care unit, specialising in cardiothoracic surgery at a tertiary referral hospital, in Queensland, Australia. An established tool was modified to the intensive care nursing handover context and a survey of all 63 nursing team leaders was undertaken. Survey statements were rated using a 6-point Likert scale with selections from 'strongly disagree' to 'strongly agree', and open-ended questions. Descriptive statistics were used to summarise results. A total of 39 team leaders responded to the survey (62%). Team leaders used general intensive care work unit guidelines to inform practice however they were less familiar with the intensive care handover work unit guideline. Barriers to minimum dataset uptake included: a tool that was not user friendly, time consuming and contained too much information. Facilitators to minimum dataset adoption included: a tool that was user friendly, saved time and contained relevant information. Identifying the complexities of a healthcare setting prior to the implementation of an intervention assists researchers and clinicians to integrate new knowledge into healthcare settings. Barriers and facilitators to knowledge use focused on usability, content and efficiency of the electronic minimum dataset and can be used to inform tailored strategies to optimise team leaders' adoption of a minimum dataset for handover. Copyright © 2017 Australian College of Critical Care Nurses Ltd. Published by Elsevier Ltd. All rights reserved.

FMT (Flight Software Memory Tracker) For Cassini Spacecraft-Software Engineering Using JAVA

NASA Technical Reports Server (NTRS)

Kan, Edwin P.; Uffelman, Hal; Wax, Allan H.

1997-01-01

The software engineering design of the Flight Software Memory Tracker (FMT) Tool is discussed in this paper. FMT is a ground analysis software set, consisting of utilities and procedures, designed to track the flight software, i.e., images of memory load and updatable parameters of the computers on-board Cassini spacecraft. FMT is implemented in Java.

Empirical studies of design software: Implications for software engineering environments

NASA Technical Reports Server (NTRS)

Krasner, Herb

1988-01-01

The empirical studies team of MCC's Design Process Group conducted three studies in 1986-87 in order to gather data on professionals designing software systems in a range of situations. The first study (the Lift Experiment) used thinking aloud protocols in a controlled laboratory setting to study the cognitive processes of individual designers. The second study (the Object Server Project) involved the observation, videotaping, and data collection of a design team of a medium-sized development project over several months in order to study team dynamics. The third study (the Field Study) involved interviews with the personnel from 19 large development projects in the MCC shareholders in order to study how the process of design is affected by organizationl and project behavior. The focus of this report will be on key observations of design process (at several levels) and their implications for the design of environments.

Can hospital audit teams identify case management problems, analyse their causes, identify and implement improvements? A cross-sectional process evaluation of obstetric near-miss case reviews in Benin.

PubMed

Borchert, Matthias; Goufodji, Sourou; Alihonou, Eusèbe; Delvaux, Thérèse; Saizonou, Jacques; Kanhonou, Lydie; Filippi, Véronique

2012-10-11

Obstetric near-miss case reviews are being promoted as a quality assurance intervention suitable for hospitals in low income countries. We introduced such reviews in five district, regional and national hospitals in Benin, West Africa. In a cross-sectional study we analysed the extent to which the hospital audit teams were able to identify case management problems (CMPs), analyse their causes, agree on solutions and put these solutions into practice. We analysed case summaries, women's interview transcripts and audit minutes produced by the audit teams for 67 meetings concerning one woman with near-miss complications each. We compared the proportion of CMPs identified by an external assessment team to the number found by the audit teams. For the latter, we described the CMP causes identified, solutions proposed and implemented by the audit teams. Audit meetings were conducted regularly and were well attended. Audit teams identified half of the 714 CMPs; they were more likely to find managerial ones (71%) than the ones relating to treatment (30%). Most identified CMPs were valid. Almost all causes of CMPs were plausible, but often too superficial to be of great value for directing remedial action. Audit teams suggested solutions, most of them promising ones, for 38% of the CMPs they had identified, but recorded their implementation only for a minority (8.5%). The importance of following-up and documenting the implementation of solutions should be stressed in future audit interventions. Tools facilitating the follow-up should be made available. Near-miss case reviews hold promise, but their effectiveness to improve the quality of care sustainably and on a large scale still needs to be established.

Can hospital audit teams identify case management problems, analyse their causes, identify and implement improvements? A cross-sectional process evaluation of obstetric near-miss case reviews in Benin

PubMed Central

2012-01-01

Background Obstetric near-miss case reviews are being promoted as a quality assurance intervention suitable for hospitals in low income countries. We introduced such reviews in five district, regional and national hospitals in Benin, West Africa. In a cross-sectional study we analysed the extent to which the hospital audit teams were able to identify case management problems (CMPs), analyse their causes, agree on solutions and put these solutions into practice. Methods We analysed case summaries, women’s interview transcripts and audit minutes produced by the audit teams for 67 meetings concerning one woman with near-miss complications each. We compared the proportion of CMPs identified by an external assessment team to the number found by the audit teams. For the latter, we described the CMP causes identified, solutions proposed and implemented by the audit teams. Results Audit meetings were conducted regularly and were well attended. Audit teams identified half of the 714 CMPs; they were more likely to find managerial ones (71%) than the ones relating to treatment (30%). Most identified CMPs were valid. Almost all causes of CMPs were plausible, but often too superficial to be of great value for directing remedial action. Audit teams suggested solutions, most of them promising ones, for 38% of the CMPs they had identified, but recorded their implementation only for a minority (8.5%). Conclusions The importance of following-up and documenting the implementation of solutions should be stressed in future audit interventions. Tools facilitating the follow-up should be made available. Near-miss case reviews hold promise, but their effectiveness to improve the quality of care sustainably and on a large scale still needs to be established. PMID:23057707

Design and implementation of a compliant robot with force feedback and strategy planning software

NASA Technical Reports Server (NTRS)

Premack, T.; Strempek, F. M.; Solis, L. A.; Brodd, S. S.; Cutler, E. P.; Purves, L. R.

1984-01-01

Force-feedback robotics techniques are being developed for automated precision assembly and servicing of NASA space flight equipment. Design and implementation of a prototype robot which provides compliance and monitors forces is in progress. Computer software to specify assembly steps and makes force feedback adjustments during assembly are coded and tested for three generically different precision mating problems. A model program demonstrates that a suitably autonomous robot can plan its own strategy.

The benefits of flexible team interaction during crises.

PubMed

Stachowski, Alicia A; Kaplan, Seth A; Waller, Mary J

2009-11-01

Organizations increasingly rely on teams to respond to crises. While research on team effectiveness during nonroutine events is growing, naturalistic studies examining team behaviors during crises are relatively scarce. Furthermore, the relevant literature offers competing theoretical rationales concerning effective team response to crises. In this article, the authors investigate whether high- versus average-performing teams can be distinguished on the basis of the number and complexity of their interaction patterns. Using behavioral observation methodology, the authors coded the discrete verbal and nonverbal behaviors of 14 nuclear power plant control room crews as they responded to a simulated crisis. Pattern detection software revealed systematic differences among crews in their patterns of interaction. Mean comparisons and discriminant function analysis indicated that higher performing crews exhibited fewer, shorter, and less complex interaction patterns. These results illustrate the limitations of standardized response patterns and highlight the importance of team adaptability. Implications for future research and for team training are included.

Development of an Integrated Team Training Design and Assessment Architecture to Support Adaptability in Healthcare Teams

DTIC Science & Technology

2016-10-01

and implementation of embedded, adaptive feedback and performance assessment. The investigators also initiated work designing a Bayesian Belief ...training; Teamwork; Adaptive performance; Leadership; Simulation; Modeling; Bayesian belief networks (BBN) 16. SECURITY CLASSIFICATION OF: 17. LIMITATION...Trauma teams Team training Teamwork Adaptability Adaptive performance Leadership Simulation Modeling Bayesian belief networks (BBN) 6

The KSC Simulation Team practices for contingencies in Firing Room 1

NASA Technical Reports Server (NTRS)

1998-01-01

In Firing Room 1 at KSC, Shuttle launch team members put the Shuttle system through an integrated simulation. The control room is set up with software used to simulate flight and ground systems in the launch configuration. A Simulation Team, comprised of KSC engineers, introduce 12 or more major problems to prepare the launch team for worst-case scenarios. Such tests and simulations keep the Shuttle launch team sharp and ready for liftoff. The next liftoff is targeted for Oct. 29.

Process-based quality management for clinical implementation of adaptive radiotherapy.

PubMed

Noel, Camille E; Santanam, Lakshmi; Parikh, Parag J; Mutic, Sasa

2014-08-01

Intensity-modulated adaptive radiotherapy (ART) has been the focus of considerable research and developmental work due to its potential therapeutic benefits. However, in light of its unique quality assurance (QA) challenges, no one has described a robust framework for its clinical implementation. In fact, recent position papers by ASTRO and AAPM have firmly endorsed pretreatment patient-specific IMRT QA, which limits the feasibility of online ART. The authors aim to address these obstacles by applying failure mode and effects analysis (FMEA) to identify high-priority errors and appropriate risk-mitigation strategies for clinical implementation of intensity-modulated ART. An experienced team of two clinical medical physicists, one clinical engineer, and one radiation oncologist was assembled to perform a standard FMEA for intensity-modulated ART. A set of 216 potential radiotherapy failures composed by the forthcoming AAPM task group 100 (TG-100) was used as the basis. Of the 216 failures, 127 were identified as most relevant to an ART scheme. Using the associated TG-100 FMEA values as a baseline, the team considered how the likeliness of occurrence (O), outcome severity (S), and likeliness of failure being undetected (D) would change for ART. New risk priority numbers (RPN) were calculated. Failures characterized by RPN ≥ 200 were identified as potentially critical. FMEA revealed that ART RPN increased for 38% (n = 48/127) of potential failures, with 75% (n = 36/48) attributed to failures in the segmentation and treatment planning processes. Forty-three of 127 failures were identified as potentially critical. Risk-mitigation strategies include implementing a suite of quality control and decision support software, specialty QA software/hardware tools, and an increase in specially trained personnel. Results of the FMEA-based risk assessment demonstrate that intensity-modulated ART introduces different (but not necessarily more) risks than standard IMRT and may be

CONRAD Software Architecture

NASA Astrophysics Data System (ADS)

Guzman, J. C.; Bennett, T.

2008-08-01

The Convergent Radio Astronomy Demonstrator (CONRAD) is a collaboration between the computing teams of two SKA pathfinder instruments, MeerKAT (South Africa) and ASKAP (Australia). Our goal is to produce the required common software to operate, process and store the data from the two instruments. Both instruments are synthesis arrays composed of a large number of antennas (40 - 100) operating at centimeter wavelengths with wide-field capabilities. Key challenges are the processing of high volume of data in real-time as well as the remote mode of operations. Here we present the software architecture for CONRAD. Our design approach is to maximize the use of open solutions and third-party software widely deployed in commercial applications, such as SNMP and LDAP, and to utilize modern web-based technologies for the user interfaces, such as AJAX.

Perfecting scientists’ collaboration and problem-solving skills in the virtual team environment

USDA-ARS?s Scientific Manuscript database

Perfecting Scientists’ Collaboration and Problem-Solving Skills in the Virtual Team Environment Numerous factors have contributed to the proliferation of conducting work in virtual teams at the domestic, national, and global levels: innovations in technology, critical developments in software, co-lo...

The NASA Software Research Infusion Initiative: Successful Technology Transfer for Software Assurance

NASA Technical Reports Server (NTRS)

Hinchey, Michael G.; Pressburger, Thomas; Markosian, Lawrence; Feather, Martin S.

2006-01-01

New processes, methods and tools are constantly appearing in the field of software engineering. Many of these augur great potential in improving software development processes, resulting in higher quality software with greater levels of assurance. However, there are a number of obstacles that impede their infusion into software development practices. These are the recurring obstacles common to many forms of research. Practitioners cannot readily identify the emerging techniques that may most benefit them, and cannot afford to risk time and effort in evaluating and experimenting with them while there is still uncertainty about whether they will have payoff in this particular context. Similarly, researchers cannot readily identify those practitioners whose problems would be amenable to their techniques and lack the feedback from practical applications necessary to help them to evolve their techniques to make them more likely to be successful. This paper describes an ongoing effort conducted by a software engineering research infusion team, and the NASA Research Infusion Initiative, established by NASA s Software Engineering Initiative, to overcome these obstacles.

TReacLab: An object-oriented implementation of non-intrusive splitting methods to couple independent transport and geochemical software

NASA Astrophysics Data System (ADS)

Jara, Daniel; de Dreuzy, Jean-Raynald; Cochepin, Benoit

2017-12-01

Reactive transport modeling contributes to understand geophysical and geochemical processes in subsurface environments. Operator splitting methods have been proposed as non-intrusive coupling techniques that optimize the use of existing chemistry and transport codes. In this spirit, we propose a coupler relying on external geochemical and transport codes with appropriate operator segmentation that enables possible developments of additional splitting methods. We provide an object-oriented implementation in TReacLab developed in the MATLAB environment in a free open source frame with an accessible repository. TReacLab contains classical coupling methods, template interfaces and calling functions for two classical transport and reactive software (PHREEQC and COMSOL). It is tested on four classical benchmarks with homogeneous and heterogeneous reactions at equilibrium or kinetically-controlled. We show that full decoupling to the implementation level has a cost in terms of accuracy compared to more integrated and optimized codes. Use of non-intrusive implementations like TReacLab are still justified for coupling independent transport and chemical software at a minimal development effort but should be systematically and carefully assessed.

A season-long team-building intervention: examining the effect of team goal setting on cohesion.

PubMed

Senécal, Julie; Loughead, Todd M; Bloom, Gordon A

2008-04-01

The purpose of the current study was to determine whether the implementation of a season-long team-building intervention program using team goal setting increased perceptions of cohesion. The participants were 86 female high school basketball players from 8 teams. The teams were randomly assigned to either an experimental team goal-setting or control condition. Each participant completed the Group Environment Questionnaire (GEQ; Carron, Brawley, & Widmeyer, 2002; Carron, Widmeyer, & Brawley, 1985), which assessed cohesion at both the beginning and end of the season. Overall, the results revealed a significant multivariate effect, Pillai's trace F(12, 438) = 2.68, p = .002. Post hoc analyses showed that at the beginning of the season, athletes from both conditions did not differ in their perceptions of cohesion. However, at the end of the season, athletes in the team goal-setting condition held higher perceptions of cohesion than athletes in the control condition. Overall, the results indicated that team goal setting was an effective team-building tool for influencing cohesiveness in sport teams.

Implementation of metal-friendly EAM/FS-type semi-empirical potentials in HOOMD-blue: A GPU-accelerated molecular dynamics software

NASA Astrophysics Data System (ADS)

Yang, Lin; Zhang, Feng; Wang, Cai-Zhuang; Ho, Kai-Ming; Travesset, Alex

2018-04-01

We present an implementation of EAM and FS interatomic potentials, which are widely used in simulating metallic systems, in HOOMD-blue, a software designed to perform classical molecular dynamics simulations using GPU accelerations. We first discuss the details of our implementation and then report extensive benchmark tests. We demonstrate that single-precision floating point operations efficiently implemented on GPUs can produce sufficient accuracy when compared against double-precision codes, as demonstrated in test simulations of calculations of the glass-transition temperature of Cu64.5Zr35.5, and pair correlation function g (r) of liquid Ni3Al. Our code scales well with the size of the simulating system on NVIDIA Tesla M40 and P100 GPUs. Compared with another popular software LAMMPS running on 32 cores of AMD Opteron 6220 processors, the GPU/CPU performance ratio can reach as high as 4.6. The source code can be accessed through the HOOMD-blue web page for free by any interested user.

Collaboration, Communication and Co-ordination in Agile Software Development Practice

NASA Astrophysics Data System (ADS)

Robinson, Hugh; Sharp, Helen

This chapter analyses the results of a series of observational studies of agile software developmentagile software development teams, identifying commonalities in collaboration, co-ordination and communication activities. Pairing and customer collaborationcustomer collaboration are focussed on to illustrate the nature of collaboration and communication, as are two simple physical artefacts that emerged through analysis as being an information-rich focal point for the co-ordination of collaboration and communication activities. The analysis shows that pairingpairing has common characteristics across all teams, while customer collaboration differs between the teams depending on the application and organisational context of development.

Implementation of the Crisis Resolution Team model in adult mental health settings: a systematic review.

PubMed

Wheeler, Claire; Lloyd-Evans, Brynmor; Churchard, Alasdair; Fitzgerald, Caroline; Fullarton, Kate; Mosse, Liberty; Paterson, Bethan; Zugaro, Clementina Galli; Johnson, Sonia

2015-04-08

Crisis Resolution Teams (CRTs) aim to offer an alternative to hospital admission during mental health crises, providing rapid assessment, home treatment, and facilitation of early discharge from hospital. CRTs were implemented nationally in England following the NHS Plan of 2000. Single centre studies suggest CRTs can reduce hospital admissions and increase service users' satisfaction: however, there is also evidence that model implementation and outcomes vary considerably. Evidence on crucial characteristics of effective CRTs is needed to allow team functioning to be optimised. This review aims to establish what evidence, if any, is available regarding the characteristics of effective and acceptable CRTs. A systematic review was conducted. MEDLINE, Embase, PsycINFO, CINAHL and Web of Science were searched to November 2013. A further web-based search was conducted for government and expert guidelines on CRTs. We analysed studies separately as: comparing CRTs to Treatment as Usual; comparing two or more CRT models; national or regional surveys of CRT services; qualitative studies of stakeholders' views regarding best practice in CRTs; and guidelines from government and expert organisations regarding CRT service delivery. Quality assessment and narrative synthesis were conducted. Statistical meta-analysis was not feasible due to the variety of design of retrieved studies. Sixty-nine studies were included. Studies varied in quality and in the composition and activities of the clinical services studied. Quantitative studies suggested that longer opening hours and the presence of a psychiatrist in the team may increase CRTs' ability to prevent hospital admissions. Stakeholders emphasised communication and integration with other local mental health services; provision of treatment at home; and limiting the number of different staff members visiting a service user. Existing guidelines prioritised 24-hour, seven-day-a-week CRT service provision (including psychiatrist and

Biotechnology software in the digital age: are you winning?

PubMed

Scheitz, Cornelia Johanna Franziska; Peck, Lawrence J; Groban, Eli S

2018-01-16

There is a digital revolution taking place and biotechnology companies are slow to adapt. Many pharmaceutical, biotechnology, and industrial bio-production companies believe that software must be developed and maintained in-house and that data are more secure on internal servers than on the cloud. In fact, most companies in this space continue to employ large IT and software teams and acquire computational infrastructure in the form of in-house servers. This is due to a fear of the cloud not sufficiently protecting in-house resources and the belief that their software is valuable IP. Over the next decade, the ability to quickly adapt to changing market conditions, with agile software teams, will quickly become a compelling competitive advantage. Biotechnology companies that do not adopt the new regime may lose on key business metrics such as return on invested capital, revenue, profitability, and eventually market share.

Facilitating the implementation of the American College of Surgeons/Association of Program Directors in Surgery phase III skills curriculum: training faculty in the assessment of team skills.

PubMed

Hull, Louise; Arora, Sonal; Stefanidis, Dimitrios; Sevdalis, Nick

2015-11-01

Effective teamwork is critical to safety in the operating room; however, implementation of phase III of the American College of Surgeons (ACS) and Association of Program Directors in Surgery (APDS) Curriculum that focuses on team-based skills remains worryingly low. Training and assessing the complexities of teamwork is challenging. The objective of this study was to establish guidelines and recommendations for training faculty in assessing/debriefing team skills. A multistage survey-based consensus study was completed by 108 experts responsible for training and assessing surgical residents from the ACS Accredited Educational Institutes. Experts agreed that a program to teach faculty to assess team-based skills should include training in the recognition of teamwork skills, practice rating these skills, and training in the provision of feedback/debriefing. Agreement was reached that faculty responsible for conducting team-based skills assessment should be revalidated every 2 years and stringent proficiency criteria should be met. Faculty development is critical to ensure high-quality, standardized training and assessment. Training faculty to assess team-based skills has the potential to facilitate the effective implementation of phase III of the ACS and APDS Curriculum. Copyright © 2015 Elsevier Inc. All rights reserved.

Teacher Design Teams (TDTs)--Building Capacity for Innovation, Learning and Curriculum Implementation in the Continuing Professional Development of In-Career Teachers

ERIC Educational Resources Information Center

Simmie, Geraldine Mooney

2007-01-01

From October to December 2005, six biology associates were employed to progress the connection between curriculum implementation and the continuing professional development of teachers at regional level. The associates worked with one hundred biology teachers in Teacher Design Teams (TDTs) and together they produced eighteen innovative classroom…

Orbit Determination and Navigation Software Testing for the Mars Reconnaissance Orbiter

NASA Technical Reports Server (NTRS)

Pini, Alex

2011-01-01

During the extended science phase of the Mars Reconnaissance Orbiter's lifecycle, the operational duties pertaining to navigation primarily involve orbit determination. The orbit determination process utilizes radiometric tracking data and is used for the prediction and reconstruction of MRO's trajectories. Predictions are done twice per week for ephemeris updates on-board the spacecraft and for planning purposes. Orbit Trim Maneuvers (OTM-s) are also designed using the predicted trajectory. Reconstructions, which incorporate a batch estimator, provide precise information about the spacecraft state to be synchronized with scientific measurements. These tasks were conducted regularly to validate the results obtained by the MRO Navigation Team. Additionally, the team is in the process of converting to newer versions of the navigation software and operating system. The capability to model multiple densities in the Martian atmosphere is also being implemented. However, testing outputs among these different configurations was necessary to ensure compliance to a satisfactory degree.

Team Faces Tough Odds to Implement New Phone Network | Poster

Cancer.gov

It was a Saturday, in the final stretch of winter in late February, and the temperature peaked to a pleasant 66 degrees. Many people were outside enjoying the spring-like weather; however, the Voice over Internet Protocol (VoIP) Deployment Team was hard at work at Industry Lane. The team of 10 was installing the new voice-only network, including deploying 145 phones, switching and testing the 911 feature, connecting wall mounts, and verifying each phone... Read more

Computing and software

USGS Publications Warehouse

White, Gary C.; Hines, J.E.

2004-01-01

The reality is that the statistical methods used for analysis of data depend upon the availability of software. Analysis of marked animal data is no different than the rest of the statistical field. The methods used for analysis are those that are available in reliable software packages. Thus, the critical importance of having reliable, up–to–date software available to biologists is obvious. Statisticians have continued to develop more robust models, ever expanding the suite of potential analysis methodsavailable. But without software to implement these newer methods, they will languish in the abstract, and not be applied to the problems deserving them.In the Computers and Software Session, two new software packages are described, a comparison of implementation of methods for the estimation of nest survival is provided, and a more speculative paper about how the next generation of software might be structured is presented.Rotella et al. (2004) compare nest survival estimation with different software packages: SAS logistic regression, SAS non–linear mixed models, and Program MARK. Nests are assumed to be visited at various, possibly infrequent, intervals. All of the approaches described compute nest survival with the same likelihood, and require that the age of the nest is known to account for nests that eventually hatch. However, each approach offers advantages and disadvantages, explored by Rotella et al. (2004).Efford et al. (2004) present a new software package called DENSITY. The package computes population abundance and density from trapping arrays and other detection methods with a new and unique approach. DENSITY represents the first major addition to the analysis of trapping arrays in 20 years.Barker & White (2004) discuss how existing software such as Program MARK require that each new model’s likelihood must be programmed specifically for that model. They wishfully think that future software might allow the user to combine pieces of likelihood

A management system for evaluating the Virginia periodic motor vehicle inspection program : software manual and implementation procedures : final report.

DOT National Transportation Integrated Search

1978-01-01

This report deals with the Periodic Motor Vehicle Inspection Management Evaluation System software documentation and implementation procedures. A companion report entitled "A Management System for Evaluating the Virginia Periodic Motor Vehicle Inspec...

Software Technology Transfer and Export Control.

DTIC Science & Technology

1981-01-01

development projects of their own. By analogy, a Soviet team might be able to repeat the learning experience of the ADEPT-50 junior staff...recommendations concerning product form and further study . The posture of this group has been to consider software technology and its transfer as a process...and views of the Software Subgroup of Technical Working Group 7 (Computers) of the Critical Technologies Project . The work reported

Software Capability Evaluation (SCE) Version 2.0 Implementation Guide

DTIC Science & Technology

1994-02-01

Affected By SCE B-40 Figure 3-1 SCE Usage Decision Making Criteria 3-44 Figure 3-2 Estimated SCE Labor For One Source Selection 3-53 Figure 3-3 SCE...incorporated into the source selection sponsoring organization’s technical/management team for incorporation into acquisition decisions . The SCE team...expertise, past performance, and organizational capacity in acquisition decisions . The Capability Maturity Model Basic Concepts The CMM is based on the

Cleanroom Software Engineering Reference Model. Version 1.0.

DTIC Science & Technology

1996-11-01

teams. It also serves as a baseline for continued evolution of Cleanroom practice. The scope of the CRM is software management , specification...addition to project staff, participants include management , peer organization representatives, and customer representatives as appropriate for...2 Review the status of the process with management , the project team, peer groups, and the customer . These verification activities include

Which factors affect software projects maintenance cost more?

PubMed

Dehaghani, Sayed Mehdi Hejazi; Hajrahimi, Nafiseh

2013-03-01

The software industry has had significant progress in recent years. The entire life of software includes two phases: production and maintenance. Software maintenance cost is increasingly growing and estimates showed that about 90% of software life cost is related to its maintenance phase. Extraction and considering the factors affecting the software maintenance cost help to estimate the cost and reduce it by controlling the factors. In this study, the factors affecting software maintenance cost were determined then were ranked based on their priority and after that effective ways to reduce the maintenance costs were presented. This paper is a research study. 15 software related to health care centers information systems in Isfahan University of Medical Sciences and hospitals function were studied in the years 2010 to 2011. Among Medical software maintenance team members, 40 were selected as sample. After interviews with experts in this field, factors affecting maintenance cost were determined. In order to prioritize the factors derived by AHP, at first, measurement criteria (factors found) were appointed by members of the maintenance team and eventually were prioritized with the help of EC software. Based on the results of this study, 32 factors were obtained which were classified in six groups. "Project" was ranked the most effective feature in maintenance cost with the highest priority. By taking into account some major elements like careful feasibility of IT projects, full documentation and accompany the designers in the maintenance phase good results can be achieved to reduce maintenance costs and increase longevity of the software.

Implementation of a data management software system for SSME test history data

NASA Technical Reports Server (NTRS)

Abernethy, Kenneth

1986-01-01

The implementation of a software system for managing Space Shuttle Main Engine (SSME) test/flight historical data is presented. The software system uses the database management system RIM7 for primary data storage and routine data management, but includes several FORTRAN programs, described here, which provide customized access to the RIM7 database. The consolidation, modification, and transfer of data from the database THIST, to the RIM7 database THISRM is discussed. The RIM7 utility modules for generating some standard reports from THISRM and performing some routine updating and maintenance are briefly described. The FORTRAN accessing programs described include programs for initial loading of large data sets into the database, capturing data from files for database inclusion, and producing specialized statistical reports which cannot be provided by the RIM7 report generator utility. An expert system tutorial, constructed using the expert system shell product INSIGHT2, is described. Finally, a potential expert system, which would analyze data in the database, is outlined. This system could use INSIGHT2 as well and would take advantage of RIM7's compatibility with the microcomputer database system RBase 5000.

NASA PC software evaluation project

NASA Technical Reports Server (NTRS)

Dominick, Wayne D. (Editor); Kuan, Julie C.

1986-01-01

The USL NASA PC software evaluation project is intended to provide a structured framework for facilitating the development of quality NASA PC software products. The project will assist NASA PC development staff to understand the characteristics and functions of NASA PC software products. Based on the results of the project teams' evaluations and recommendations, users can judge the reliability, usability, acceptability, maintainability and customizability of all the PC software products. The objective here is to provide initial, high-level specifications and guidelines for NASA PC software evaluation. The primary tasks to be addressed in this project are as follows: to gain a strong understanding of what software evaluation entails and how to organize a structured software evaluation process; to define a structured methodology for conducting the software evaluation process; to develop a set of PC software evaluation criteria and evaluation rating scales; and to conduct PC software evaluations in accordance with the identified methodology. Communication Packages, Network System Software, Graphics Support Software, Environment Management Software, General Utilities. This report represents one of the 72 attachment reports to the University of Southwestern Louisiana's Final Report on NASA Grant NGT-19-010-900. Accordingly, appropriate care should be taken in using this report out of context of the full Final Report.

Development and Implementation of Team-Based Panel Management Tools: Filling the Gap between Patient and Population Information Systems.

PubMed

Watts, Brook; Lawrence, Renée H; Drawz, Paul; Carter, Cameron; Shumaker, Amy Hirsch; Kern, Elizabeth F

2016-08-01

Effective team-based models of care, such as the Patient-Centered Medical Home, require electronic tools to support proactive population management strategies that emphasize care coordination and quality improvement. Despite the spread of electronic health records (EHRs) and vendors marketing population health tools, clinical practices still may lack the ability to have: (1) local control over types of data collected/reports generated, (2) timely data (eg, up-to-date data, not several months old), and accordingly (3) the ability to efficiently monitor and improve patient outcomes. This article describes a quality improvement project at the hospital system level to develop and implement a flexible panel management (PM) tool to improve care of subpopulations of patients (eg, panels of patients with diabetes) by clinical teams. An in-depth case analysis approach is used to explore barriers and facilitators in building a PM registry tool for team-based management needs using standard data elements (eg, laboratory values, pharmacy records) found in EHRs. Also described are factors that may contribute to sustainability; to date the tool has been adapted to 6 disease-focused subpopulations encompassing more than 200,000 patients. Two key lessons emerged from this initiative: (1) though challenging, team-based clinical end users and information technology needed to work together consistently to refine the product, and (2) locally developed population management tools can provide efficient data tracking for frontline clinical teams and leadership. The preliminary work identified critical gaps that were successfully addressed by building local PM registry tools from EHR-derived data and offers lessons learned for others engaged in similar work. (Population Health Management 2016;19:232-239).

Student Team Projects in Information Systems Development: Measuring Collective Creative Efficacy

ERIC Educational Resources Information Center

Cheng, Hsiu-Hua; Yang, Heng-Li

2011-01-01

For information systems development project student teams, learning how to improve software development processes is an important training. Software process improvement is an outcome of a number of creative behaviours. Social cognitive theory states that the efficacy of judgment influences behaviours. This study explores the impact of three types…

CMMI Level 5 and the Team Software Process

DTIC Science & Technology

2007-04-01

could meet the rigors of a CMMI assessment and achieve their group’s goal of Level 5. Watts Humphrey , who is widely acknowledged as the founder of the...Capability Maturity Model® (CMM®) approach to improvement and who later created the Personal Software Process ( PSP )SM and TSP, has noted that one of the...intents of PSP and TSP is to be an operational process enactment of CMM Level 5 processes at the personal and pro- ject levels respectively [1]. CMM

Implementation and Simulation Results using Autonomous Aerobraking Development Software

NASA Technical Reports Server (NTRS)

Maddock, Robert W.; DwyerCianciolo, Alicia M.; Bowes, Angela; Prince, Jill L. H.; Powell, Richard W.

2011-01-01

An Autonomous Aerobraking software system is currently under development with support from the NASA Engineering and Safety Center (NESC) that would move typically ground-based operations functions to onboard an aerobraking spacecraft, reducing mission risk and mission cost. The suite of software that will enable autonomous aerobraking is the Autonomous Aerobraking Development Software (AADS) and consists of an ephemeris model, onboard atmosphere estimator, temperature and loads prediction, and a maneuver calculation. The software calculates the maneuver time, magnitude and direction commands to maintain the spacecraft periapsis parameters within design structural load and/or thermal constraints. The AADS is currently tested in simulations at Mars, with plans to also evaluate feasibility and performance at Venus and Titan.

Student Teachers' Team Teaching: How Do Learners in the Classroom Experience Team-Taught Lessons by Student Teachers?

ERIC Educational Resources Information Center

Baeten, Marlies; Simons, Mathea

2016-01-01

This study focuses on student teachers' team teaching. Two team teaching models (sequential and parallel teaching) were applied by 14 student teachers in a quasi-experimental design. When implementing new teaching models, it is important to take into account the perspectives of all actors involved. Although learners are key actors in the teaching…

Florida alternative NTCIP testing software (ANTS) for actuated signal controllers.

DOT National Transportation Integrated Search

2009-01-01

The scope of this research project did include the development of a software tool to test devices for NTCIP compliance. Development of the Florida Alternative NTCIP Testing Software (ANTS) was developed by the research team due to limitations found w...

Why and how Mastering an Incremental and Iterative Software Development Process

NASA Astrophysics Data System (ADS)

Dubuc, François; Guichoux, Bernard; Cormery, Patrick; Mescam, Jean Christophe

2004-06-01

One of the key issues regularly mentioned in the current software crisis of the space domain is related to the software development process that must be performed while the system definition is not yet frozen. This is especially true for complex systems like launchers or space vehicles.Several more or less mature solutions are under study by EADS SPACE Transportation and are going to be presented in this paper. The basic principle is to develop the software through an iterative and incremental process instead of the classical waterfall approach, with the following advantages:- It permits systematic management and incorporation of requirements changes over the development cycle with a minimal cost. As far as possible the most dimensioning requirements are analyzed and developed in priority for validating very early the architecture concept without the details.- A software prototype is very quickly available. It improves the communication between system and software teams, as it enables to check very early and efficiently the common understanding of the system requirements.- It allows the software team to complete a whole development cycle very early, and thus to become quickly familiar with the software development environment (methodology, technology, tools...). This is particularly important when the team is new, or when the environment has changed since the previous development. Anyhow, it improves a lot the learning curve of the software team.These advantages seem very attractive, but mastering efficiently an iterative development process is not so easy and induces a lot of difficulties such as:- How to freeze one configuration of the system definition as a development baseline, while most of thesystem requirements are completely and naturally unstable?- How to distinguish stable/unstable and dimensioning/standard requirements?- How to plan the development of each increment?- How to link classical waterfall development milestones with an iterative approach: when

Team Collaboration: Lessons Learned Report

NASA Technical Reports Server (NTRS)

Arterberrie, Rhonda Y.; Eubanks, Steven W.; Kay, Dennis R.; Prahst, Stephen E.; Wenner, David P.

2005-01-01

An Agency team collaboration pilot was conducted from July 2002 until June 2003 and then extended for an additional year. The objective of the pilot was to assess the value of collaboration tools and adoption processes as applied to NASA teams. In an effort to share knowledge and experiences, the lessons that have been learned thus far are documented in this report. Overall, the pilot has been successful. An entire system has been piloted - tools, adoption, and support. The pilot consisted of two collaboration tools, a team space and a virtual team meeting capability. Of the two tools that were evaluated, the team meeting tool has been more widely accepted. Though the team space tool has been met with a lesser degree of acceptance, the need for such a tool in the NASA environment has been evidenced. Both adoption techniques and support were carefully developed and implemented in a way that has been well received by the pilot participant community.

Building a leadership team that works.

PubMed

Blomenberg, Emily M

2005-01-01

Radiology administrators often are challenged to do more with less. In today's fast-paced work environment, leaders must be creative. They must surround themselves with good people in order to successfully achieve their organizations' goals. Once a radiology administrator is satisfied and comfortable that he or she has, the right staff involved, a leadership team can be formally establislished. Howard Regional Health System established an Imaging Services Leadership Team with a vision to provide leaders for the staff to "follow," just as team members learn from the radiology administrator. In addition, team members are vital in assisting the radiology administrator in managing the department The process of building the team consisted of 3 steps: selecting team members (the most challenging and time-consuming component), formalizing a functional team, and putting the team into action. Finding the right people, holding regular meetings, and making those team meetings meaningful are keys to a successful leadership team. The implementation of the team has had a positive effect on imaging services: the number of procedures has increased, the team is used as a communication tool for front-line staff, front-line staff are becoming more comfortable with making decisions.

Gathering, strategizing, motivating and celebrating: the team huddle in a teaching general practice.

PubMed

Walsh, Allyn; Moore, Ainsley; Everson, Jennifer; DeCaire, Katharine

2018-03-01

To understand how implementing a daily team huddle affected the function of a complex interprofessional team including learners. A qualitative descriptive study using semi-structured interviews in focus groups. An academic general practice teaching practice. All members of one interprofessional team, including nurses, general practitioners, junior doctors, and support staff. Focus group interviews using semi-structured guidance were transcribed and the results analysed using qualitative content analysis. Four interrelated themes were identified: communication and knowledge sharing; efficiency of care; relationship and team building; and shared responsibility for team function. The implementation of the daily team huddle was seen by participants to enhance the collaboration within the team and to contribute to work life enjoyment. Participants perceived that problems were anticipated and solved quickly. Clinical updates and information about patients benefited the team including learners. Junior doctors quickly understood the scope of practice of other team members, but some felt reluctant to offer clinical opinions. The implementation of a daily team huddle was viewed as worthwhile by this large interprofessional general practice team. The delivery of patient care was more efficient, knowledge was readily distributed, and problem solving was shared across the team, including junior doctors.

Secure software practices among Malaysian software practitioners: An exploratory study

NASA Astrophysics Data System (ADS)

Mohamed, Shafinah Farvin Packeer; Baharom, Fauziah; Deraman, Aziz; Yahya, Jamaiah; Mohd, Haslina

2016-08-01

Secure software practices is increasingly gaining much importance among software practitioners and researchers due to the rise of computer crimes in the software industry. It has become as one of the determinant factors for producing high quality software. Even though its importance has been revealed, its current practice in the software industry is still scarce, particularly in Malaysia. Thus, an exploratory study is conducted among software practitioners in Malaysia to study their experiences and practices in the real-world projects. This paper discusses the findings from the study, which involved 93 software practitioners. Structured questionnaire is utilized for data collection purpose whilst statistical methods such as frequency, mean, and cross tabulation are used for data analysis. Outcomes from this study reveal that software practitioners are becoming increasingly aware on the importance of secure software practices, however, they lack of appropriate implementation, which could affect the quality of produced software.

Impact of agile methodologies on team capacity in automotive radio-navigation projects

NASA Astrophysics Data System (ADS)

Prostean, G.; Hutanu, A.; Volker, S.

2017-01-01

The development processes used in automotive radio-navigation projects are constantly under adaption pressure. While the software development models are based on automotive production processes, the integration of peripheral components into an automotive system will trigger a high number of requirement modifications. The use of traditional development models in automotive industry will bring team’s development capacity to its boundaries. The root cause lays in the inflexibility of actual processes and their adaption limits. This paper addresses a new project management approach for the development of radio-navigation projects. The understanding of weaknesses of current used models helped us in development and integration of agile methodologies in traditional development model structure. In the first part we focus on the change management methods to reduce request for change inflow. Established change management risk analysis processes enables the project management to judge the impact of a requirement change and also gives time to the project to implement some changes. However, in big automotive radio-navigation projects the saved time is not enough to implement the large amount of changes, which are submitted to the project. In the second phase of this paper we focus on increasing team capacity by integrating at critical project phases agile methodologies into the used traditional model. The overall objective of this paper is to prove the need of process adaption in order to solve project team capacity bottlenecks.

Building a culture of safety through team training and engagement.

PubMed

Thomas, Lily; Galla, Catherine

2013-05-01

Medical errors continue to occur despite multiple strategies devised for their prevention. Although many safety initiatives lead to improvement, they are often short lived and unsustainable. Our goal was to build a culture of patient safety within a structure that optimised teamwork and ongoing engagement of the healthcare team. Teamwork impacts the effectiveness of care, patient safety and clinical outcomes, and team training has been identified as a strategy for enhancing teamwork, reducing medical errors and building a culture of safety in healthcare. Therefore, we implemented Team Strategies and Tools to Enhance Performance and Patient Safety (TeamSTEPPS), an evidence-based framework which was used for team training to create transformational and/or incremental changes; facilitating transformation of organisational culture, or solving specific problems. To date, TeamSTEPPS (TS) has been implemented in 14 hospitals, two Long Term Care Facilities, and outpatient areas across the North Shore LIJ Health System. 32 150 members of the healthcare team have been trained. TeamSTEPPS was piloted at a community hospital within the framework of the health system's organisational care delivery model, the Collaborative Care Model to facilitate sustainment. AHRQ's Hospital Survey on Patient Safety Culture, (HSOPSC), was administered before and after implementation of TeamSTEPPS, comparing the perception of patient safety by the heathcare team. Pilot hospital results of HSOPSC show significant improvement from 2007 (pre-TeamSTEPPS) to 2010. System-wide results of HSOPSC show similar trends to those seen in the pilot hospital. Valuable lessons for organisational success from the pilot hospital enabled rapid spread of TeamSTEPPS across the rest of the health system.

Technology-driven dietary assessment: a software developer’s perspective

PubMed Central

Buday, Richard; Tapia, Ramsey; Maze, Gary R.

2015-01-01

Dietary researchers need new software to improve nutrition data collection and analysis, but creating information technology is difficult. Software development projects may be unsuccessful due to inadequate understanding of needs, management problems, technology barriers or legal hurdles. Cost overruns and schedule delays are common. Barriers facing scientific researchers developing software include workflow, cost, schedule, and team issues. Different methods of software development and the role that intellectual property rights play are discussed. A dietary researcher must carefully consider multiple issues to maximize the likelihood of success when creating new software. PMID:22591224

Staff perceptions of a Productive Community Services implementation: A qualitative interview study.

PubMed

Bradley, Dominique Kim Frances; Griffin, Murray

2015-06-01

The Productive Series is a collection of change programmes designed by the English National Health Service (NHS) Institute for Innovation and Improvement to help frontline healthcare staff improve quality and reduce wasted time, so that this time can be reinvested into time spent with patients. The programmes have been implemented in at least 14 countries around the world. This study examines an implementation of the Productive Community Services programme that took place in a Community healthcare organisation in England from July 2010 to March 2012. To explore staff members' perceptions of a Productive Community Services implementation. Cross-sectional interview. Community Healthcare Organisation in East Anglia, England. 45 participants were recruited using purposive, snowballing and opportunistic sampling methods to represent five main types of staff group in the organisation; clinical team members, administrative team members, service managers/team leaders, senior managers and software support staff. Team members were recruited on the basis that they had submitted data for at least one Productive Community Services module. Semi-structured individual and group interviews were carried out after the programme concluded and analysed using thematic analysis. This report focuses on six of the themes identified. The analysis found that communication was not always effective, and there was a lack of awareness, knowledge and understanding of the programme. Many staff did not find the Productive Community Services work relevant, and although certain improvements were sustained, suboptimal practices crept back. Although negative outcomes were reported, such as the programme taking time away from patients initially, many benefits were described including improved stock control and work environments, and better use of the Electronic Patient Record system. One of the themes identified highlighted the positive perceptions of the programme, however a focus on five other themes

Evidence-based development of a diagnosis-dependent therapy planning system and its implementation in modern diagnostic software.

PubMed

Ahlers, M O; Jakstat, H A

2005-07-01

The prerequisite for structured individual therapy of craniomandibular dysfunctions is differential diagnostics. Suggestions for the structured recording of findings and their structured evaluation beyond the global diagnosis of "craniomandibular disorders" have been published. Only this structured approach enables computerization of the diagnostic process. The respective software is available for use in practice (CMDcheck for CMD screening, CMDfact for the differential diagnostics). Based on this structured diagnostics, knowledge-based therapy planning is also conceivable. The prerequisite for this would be a model of achieving consensus on the indicated forms of therapy related to the diagnosis. Therefore, a procedure for evidence-based achievement of consensus on suitable forms of therapy in CMD was developed first in multicentric cooperation, and then implemented in corresponding software. The clinical knowledge of experienced specialists was included consciously for the consensus achievement process. At the same time, anonymized mathematical statistical evaluations were used for control and objectification. Different examiners form different departments of several universities working independently of one another assigned the theoretically conceiveable therapeutic alternatives to the already published diagnostic scheme. After anonymization, the correlation of these assignments was then calculated mathematically. For achieving consensus in those cases for which no agreement initally existed, agreement was subsequently arrived at in the course of a consensus conference on the basis of literature evaluations and the discussion of clinical case examples. This consensus in turn finally served as the basis of a therapy planner implemented in the above-mentioned diagnostic software CMDfact. Contributing to quality assurance, the principles of programming this assistant as well as the interface for linking into the diagnostic software are documented and also published

Portal for Families Overcoming Neurodevelopmental Disorders (PFOND): Implementation of a Software Framework for Facilitated Community Website Creation by Nontechnical Volunteers.

PubMed

Ye, Xin Cynthia; Ng, Isaiah; Seid-Karbasi, Puya; Imam, Tuhina; Lee, Cheryl E; Chen, Shirley Yu; Herman, Adam; Sharma, Balraj; Johal, Gurinder; Gu, Bobby; Wasserman, Wyeth W

2013-08-06

The Portal for Families Overcoming Neurodevelopmental Disorders (PFOND) provides a structured Internet interface for the sharing of information with individuals struggling with the consequences of rare developmental disorders. Large disease-impacted communities can support fundraising organizations that disseminate Web-based information through elegant websites run by professional staff. Such quality resources for families challenged by rare disorders are infrequently produced and, when available, are often dependent upon the continued efforts of a single individual. The project endeavors to create an intuitive Web-based software system that allows a volunteer with limited technical computer skills to produce a useful rare disease website in a short time period. Such a system should provide access to emerging news and research findings, facilitate community participation, present summary information about the disorder, and allow for transient management by volunteers who are likely to change periodically. The prototype portal was implemented using the WordPress software system with both existing and customized supplementary plug-in software modules. Gamification scoring features were implemented in a module, allowing editors to measure progress. The system was installed on a Linux-based computer server, accessible across the Internet through standard Web browsers. A prototype PFOND system was implemented and tested. The prototype system features a structured organization with distinct partitions for background information, recent publications, and community discussions. The software design allows volunteer editors to create a themed website, implement a limited set of topic pages, and connect the software to dynamic RSS feeds providing information about recent news or advances. The prototype was assessed by a fraction of the disease sites developed (8 out of 27), including Aarskog-Scott syndrome, Aniridia, Adams-Oliver syndrome, Cat Eye syndrome, Kabuki syndrome

Portal for Families Overcoming Neurodevelopmental Disorders (PFOND): Implementation of a Software Framework for Facilitated Community Website Creation by Nontechnical Volunteers

PubMed Central

Imam, Tuhina; Lee, Cheryl E; Chen, Shirley Yu; Herman, Adam; Sharma, Balraj; Johal, Gurinder; Gu, Bobby

2013-01-01

Background The Portal for Families Overcoming Neurodevelopmental Disorders (PFOND) provides a structured Internet interface for the sharing of information with individuals struggling with the consequences of rare developmental disorders. Large disease-impacted communities can support fundraising organizations that disseminate Web-based information through elegant websites run by professional staff. Such quality resources for families challenged by rare disorders are infrequently produced and, when available, are often dependent upon the continued efforts of a single individual. Objective The project endeavors to create an intuitive Web-based software system that allows a volunteer with limited technical computer skills to produce a useful rare disease website in a short time period. Such a system should provide access to emerging news and research findings, facilitate community participation, present summary information about the disorder, and allow for transient management by volunteers who are likely to change periodically. Methods The prototype portal was implemented using the WordPress software system with both existing and customized supplementary plug-in software modules. Gamification scoring features were implemented in a module, allowing editors to measure progress. The system was installed on a Linux-based computer server, accessible across the Internet through standard Web browsers. Results A prototype PFOND system was implemented and tested. The prototype system features a structured organization with distinct partitions for background information, recent publications, and community discussions. The software design allows volunteer editors to create a themed website, implement a limited set of topic pages, and connect the software to dynamic RSS feeds providing information about recent news or advances. The prototype was assessed by a fraction of the disease sites developed (8 out of 27), including Aarskog-Scott syndrome, Aniridia, Adams-Oliver syndrome

Autonomous robot software development using simple software components

NASA Astrophysics Data System (ADS)

Burke, Thomas M.; Chung, Chan-Jin

2004-10-01

Developing software to control a sophisticated lane-following, obstacle-avoiding, autonomous robot can be demanding and beyond the capabilities of novice programmers - but it doesn"t have to be. A creative software design utilizing only basic image processing and a little algebra, has been employed to control the LTU-AISSIG autonomous robot - a contestant in the 2004 Intelligent Ground Vehicle Competition (IGVC). This paper presents a software design equivalent to that used during the IGVC, but with much of the complexity removed. The result is an autonomous robot software design, that is robust, reliable, and can be implemented by programmers with a limited understanding of image processing. This design provides a solid basis for further work in autonomous robot software, as well as an interesting and achievable robotics project for students.

Design software for reuse

NASA Technical Reports Server (NTRS)

Tracz, Will

1990-01-01

Viewgraphs are presented on the designing of software for reuse. Topics include terminology, software reuse maxims, the science of programming, an interface design example, a modularization example, and reuse and implementation guidelines.

Firing Room Remote Application Software Development & Swamp Works Laboratory Robot Software Development

NASA Technical Reports Server (NTRS)

Garcia, Janette

2016-01-01

The National Aeronautics and Space Administration (NASA) is creating a way to send humans beyond low Earth orbit, and later to Mars. Kennedy Space Center (KSC) is working to make this possible by developing a Spaceport Command and Control System (SCCS) which will allow the launch of Space Launch System (SLS). This paper's focus is on the work performed by the author in her first and second part of the internship as a remote application software developer. During the first part of her internship, the author worked on the SCCS's software application layer by assisting multiple ground subsystems teams including Launch Accessories (LACC) and Environmental Control System (ECS) on the design, development, integration, and testing of remote control software applications. Then, on the second part of the internship, the author worked on the development of robot software at the Swamp Works Laboratory which is a research and technology development group which focuses on inventing new technology to help future In-Situ Resource Utilization (ISRU) missions.

Implementation of metal-friendly EAM/FS-type semi-empirical potentials in HOOMD-blue: A GPU-accelerated molecular dynamics software

DOE PAGES

Yang, Lin; Zhang, Feng; Wang, Cai-Zhuang; ...

2018-01-12

We present an implementation of EAM and FS interatomic potentials, which are widely used in simulating metallic systems, in HOOMD-blue, a software designed to perform classical molecular dynamics simulations using GPU accelerations. We first discuss the details of our implementation and then report extensive benchmark tests. We demonstrate that single-precision floating point operations efficiently implemented on GPUs can produce sufficient accuracy when compared against double-precision codes, as demonstrated in test simulations of calculations of the glass-transition temperature of Cu 64.5Zr 35.5, and pair correlation function of liquid Ni 3Al. Our code scales well with the size of the simulating systemmore » on NVIDIA Tesla M40 and P100 GPUs. Compared with another popular software LAMMPS running on 32 cores of AMD Opteron 6220 processors, the GPU/CPU performance ratio can reach as high as 4.6. In conclusion, the source code can be accessed through the HOOMD-blue web page for free by any interested user.« less

Implementation of metal-friendly EAM/FS-type semi-empirical potentials in HOOMD-blue: A GPU-accelerated molecular dynamics software

DOE Office of Scientific and Technical Information (OSTI.GOV)

Yang, Lin; Zhang, Feng; Wang, Cai-Zhuang

We present an implementation of EAM and FS interatomic potentials, which are widely used in simulating metallic systems, in HOOMD-blue, a software designed to perform classical molecular dynamics simulations using GPU accelerations. We first discuss the details of our implementation and then report extensive benchmark tests. We demonstrate that single-precision floating point operations efficiently implemented on GPUs can produce sufficient accuracy when compared against double-precision codes, as demonstrated in test simulations of calculations of the glass-transition temperature of Cu 64.5Zr 35.5, and pair correlation function of liquid Ni 3Al. Our code scales well with the size of the simulating systemmore » on NVIDIA Tesla M40 and P100 GPUs. Compared with another popular software LAMMPS running on 32 cores of AMD Opteron 6220 processors, the GPU/CPU performance ratio can reach as high as 4.6. In conclusion, the source code can be accessed through the HOOMD-blue web page for free by any interested user.« less

An Implementation of Active Learning: Assessing the Effectiveness of the Team Infomercial Assignment

ERIC Educational Resources Information Center

Matveev, Alexei V.; Milter, Richard G.

2010-01-01

This article examines the effectiveness of the team infomercial assignment as an active learning tool in undergraduate courses. The structure and three phases of the team infomercial assignment, as well as student evaluations and feedback, are presented. We investigated student experiences working on the team infomercial assignment, the common…

Transportable Payload Operations Control Center reusable software: Building blocks for quality ground data systems

NASA Technical Reports Server (NTRS)

Mahmot, Ron; Koslosky, John T.; Beach, Edward; Schwarz, Barbara

1994-01-01

The Mission Operations Division (MOD) at Goddard Space Flight Center builds Mission Operations Centers which are used by Flight Operations Teams to monitor and control satellites. Reducing system life cycle costs through software reuse has always been a priority of the MOD. The MOD's Transportable Payload Operations Control Center development team established an extensive library of 14 subsystems with over 100,000 delivered source instructions of reusable, generic software components. Nine TPOCC-based control centers to date support 11 satellites and achieved an average software reuse level of more than 75 percent. This paper shares experiences of how the TPOCC building blocks were developed and how building block developer's, mission development teams, and users are all part of the process.

Development and implementation of software systems for imaging spectroscopy

USGS Publications Warehouse

Boardman, J.W.; Clark, R.N.; Mazer, A.S.; Biehl, L.L.; Kruse, F.A.; Torson, J.; Staenz, K.

2006-01-01

Specialized software systems have played a crucial role throughout the twenty-five year course of the development of the new technology of imaging spectroscopy, or hyperspectral remote sensing. By their very nature, hyperspectral data place unique and demanding requirements on the computer software used to visualize, analyze, process and interpret them. Often described as a marriage of the two technologies of reflectance spectroscopy and airborne/spaceborne remote sensing, imaging spectroscopy, in fact, produces data sets with unique qualities, unlike previous remote sensing or spectrometer data. Because of these unique spatial and spectral properties hyperspectral data are not readily processed or exploited with legacy software systems inherited from either of the two parent fields of study. This paper provides brief reviews of seven important software systems developed specifically for imaging spectroscopy.

Models for Deploying Open Source and Commercial Software to Support Earth Science Data Processing and Distribution

NASA Astrophysics Data System (ADS)

Yetman, G.; Downs, R. R.

2011-12-01

Software deployment is needed to process and distribute scientific data throughout the data lifecycle. Developing software in-house can take software development teams away from other software development projects and can require efforts to maintain the software over time. Adopting and reusing software and system modules that have been previously developed by others can reduce in-house software development and maintenance costs and can contribute to the quality of the system being developed. A variety of models are available for reusing and deploying software and systems that have been developed by others. These deployment models include open source software, vendor-supported open source software, commercial software, and combinations of these approaches. Deployment in Earth science data processing and distribution has demonstrated the advantages and drawbacks of each model. Deploying open source software offers advantages for developing and maintaining scientific data processing systems and applications. By joining an open source community that is developing a particular system module or application, a scientific data processing team can contribute to aspects of the software development without having to commit to developing the software alone. Communities of interested developers can share the work while focusing on activities that utilize in-house expertise and addresses internal requirements. Maintenance is also shared by members of the community. Deploying vendor-supported open source software offers similar advantages to open source software. However, by procuring the services of a vendor, the in-house team can rely on the vendor to provide, install, and maintain the software over time. Vendor-supported open source software may be ideal for teams that recognize the value of an open source software component or application and would like to contribute to the effort, but do not have the time or expertise to contribute extensively. Vendor-supported software may

Language and Program for Documenting Software Design

NASA Technical Reports Server (NTRS)

Kleine, H.; Zepko, T. M.

1986-01-01

Software Design and Documentation Language (SDDL) provides effective communication medium to support design and documentation of complex software applications. SDDL supports communication among all members of software design team and provides for production of informative documentation on design effort. Use of SDDL-generated document to analyze design makes it possible to eliminate many errors not detected until coding and testing attempted. SDDL processor program translates designer's creative thinking into effective document for communication. Processor performs as many automatic functions as possible, freeing designer's energy for creative effort. SDDL processor program written in PASCAL.

Publishing Platform for Scientific Software - Lessons Learned

NASA Astrophysics Data System (ADS)

Hammitzsch, Martin; Fritzsch, Bernadette; Reusser, Dominik; Brembs, Björn; Deinzer, Gernot; Loewe, Peter; Fenner, Martin; van Edig, Xenia; Bertelmann, Roland; Pampel, Heinz; Klump, Jens; Wächter, Joachim

2015-04-01

Scientific software has become an indispensable commodity for the production, processing and analysis of empirical data but also for modelling and simulation of complex processes. Software has a significant influence on the quality of research results. For strengthening the recognition of the academic performance of scientific software development, for increasing its visibility and for promoting the reproducibility of research results, concepts for the publication of scientific software have to be developed, tested, evaluated, and then transferred into operations. For this, the publication and citability of scientific software have to fulfil scientific criteria by means of defined processes and the use of persistent identifiers, similar to data publications. The SciForge project is addressing these challenges. Based on interviews a blueprint for a scientific software publishing platform and a systematic implementation plan has been designed. In addition, the potential of journals, software repositories and persistent identifiers have been evaluated to improve the publication and dissemination of reusable software solutions. It is important that procedures for publishing software as well as methods and tools for software engineering are reflected in the architecture of the platform, in order to improve the quality of the software and the results of research. In addition, it is necessary to work continuously on improving specific conditions that promote the adoption and sustainable utilization of scientific software publications. Among others, this would include policies for the development and publication of scientific software in the institutions but also policies for establishing the necessary competencies and skills of scientists and IT personnel. To implement the concepts developed in SciForge a combined bottom-up / top-down approach is considered that will be implemented in parallel in different scientific domains, e.g. in earth sciences, climate research and

Work in Progress: The Seven Rs of Team Building

ERIC Educational Resources Information Center

Brunelli, Jean; Schneider, Elaine Fogel