Architecting for Large Scale Agile Software Development: A Risk-Driven Approach

DTIC Science & Technology

2013-05-01

addressed aspect of scale in agile software development. Practices such as Scrum of Scrums are meant to address orchestration of multiple development...owner, Scrum master) have differing responsibilities from the roles in the existing phase-based waterfall program structures. Such differences may... Scrum . Communication with both internal and external stakeholders must be open and documentation should not be used as a substitute for communication

A Roadmap for Using Agile Development in a Traditional Environment

NASA Technical Reports Server (NTRS)

Streiffert, Barbara; Starbird, Thomas; Grenander, Sven

2006-01-01

One of the newer classes of software engineering techniques is called 'Agile Development'. In Agile Development software engineers take small implementation steps and, in some cases, they program in pairs. In addition, they develop automatic tests prior to implementing their small functional piece. Agile Development focuses on rapid turnaround, incremental planning, customer involvement and continuous integration. Agile Development is not the traditional waterfall method or even a rapid prototyping method (although this methodology is closer to Agile Development). At the Jet Propulsion Laboratory (JPL) a few groups have begun Agile Development software implementations. The difficulty with this approach becomes apparent when Agile Development is used in an organization that has specific criteria and requirements handed down for how software development is to be performed. The work at the JPL is performed for the National Aeronautics and Space Agency (NASA). Both organizations have specific requirements, rules and processes for developing software. This paper will discuss some of the initial uses of the Agile Development methodology, the spread of this method and the current status of the successful incorporation into the current JPL development policies and processes.

Insights into Global Health Practice from the Agile Software Development Movement

PubMed Central

Flood, David; Chary, Anita; Austad, Kirsten; Diaz, Anne Kraemer; García, Pablo; Martinez, Boris; Canú, Waleska López; Rohloff, Peter

2016-01-01

Global health practitioners may feel frustration that current models of global health research, delivery, and implementation are overly focused on specific interventions, slow to provide health services in the field, and relatively ill-equipped to adapt to local contexts. Adapting design principles from the agile software development movement, we propose an analogous approach to designing global health programs that emphasizes tight integration between research and implementation, early involvement of ground-level health workers and program beneficiaries, and rapid cycles of iterative program improvement. Using examples from our own fieldwork, we illustrate the potential of ‘agile global health’ and reflect on the limitations, trade-offs, and implications of this approach. PMID:27134081

Agile software development in an earned value world: a survival guide

NASA Astrophysics Data System (ADS)

Kantor, Jeffrey; Long, Kevin; Becla, Jacek; Economou, Frossie; Gelman, Margaret; Juric, Mario; Lambert, Ron; Krughoff, Simon; Swinbank, John D.; Wu, Xiuqin

2016-08-01

Agile methodologies are current best practice in software development. They are favored for, among other reasons, preventing premature optimization by taking a somewhat short-term focus, and allowing frequent replans/reprioritizations of upcoming development work based on recent results and current backlog. At the same time, funding agencies prescribe earned value management accounting for large projects which, these days, inevitably include substantial software components. Earned Value approaches emphasize a more comprehensive and typically longer-range plan, and tend to characterize frequent replans and reprioritizations as indicative of problems. Here we describe the planning, execution and reporting framework used by the LSST Data Management team, that navigates these opposite tensions.

Accelerating Software Development through Agile Practices--A Case Study of a Small-Scale, Time-Intensive Web Development Project at a College-Level IT Competition

ERIC Educational Resources Information Center

Zhang, Xuesong; Dorn, Bradley

2012-01-01

Agile development has received increasing interest both in industry and academia due to its benefits in developing software quickly, meeting customer needs, and keeping pace with the rapidly changing requirements. However, agile practices and scrum in particular have been mainly tested in mid- to large-size projects. In this paper, we present…

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.

Agile development approach for the observatory control software of the DAG 4m telescope

NASA Astrophysics Data System (ADS)

Güçsav, B. Bülent; ćoker, Deniz; Yeşilyaprak, Cahit; Keskin, Onur; Zago, Lorenzo; Yerli, Sinan K.

2016-08-01

Observatory Control Software for the upcoming 4m infrared telescope of DAG (Eastern Anatolian Observatory in Turkish) is in the beginning of its lifecycle. After the process of elicitation-validation of the initial requirements, we have been focused on preparation of a rapid conceptual design not only to see the big picture of the system but also to clarify the further development methodology. The existing preliminary designs for both software (including TCS and active optics control system) and hardware shall be presented here in brief to exploit the challenges the DAG software team has been facing with. The potential benefits of an agile approach for the development will be discussed depending on the published experience of the community and on the resources available to us.

Peridigm summary report : lessons learned in development with agile components.

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

Salinger, Andrew Gerhard; Mitchell, John Anthony; Littlewood, David John

2011-09-01

This report details efforts to deploy Agile Components for rapid development of a peridynamics code, Peridigm. The goal of Agile Components is to enable the efficient development of production-quality software by providing a well-defined, unifying interface to a powerful set of component-based software. Specifically, Agile Components facilitate interoperability among packages within the Trilinos Project, including data management, time integration, uncertainty quantification, and optimization. Development of the Peridigm code served as a testbed for Agile Components and resulted in a number of recommendations for future development. Agile Components successfully enabled rapid integration of Trilinos packages into Peridigm. A cost of thismore » approach, however, was a set of restrictions on Peridigm's architecture which impacted the ability to track history-dependent material data, dynamically modify the model discretization, and interject user-defined routines into the time integration algorithm. These restrictions resulted in modifications to the Agile Components approach, as implemented in Peridigm, and in a set of recommendations for future Agile Components development. Specific recommendations include improved handling of material states, a more flexible flow control model, and improved documentation. A demonstration mini-application, SimpleODE, was developed at the onset of this project and is offered as a potential supplement to Agile Components documentation.« less

Agile Development Methods for Space Operations

NASA Technical Reports Server (NTRS)

Trimble, Jay; Webster, Chris

2012-01-01

Main stream industry software development practice has gone from a traditional waterfall process to agile iterative development that allows for fast response to customer inputs and produces higher quality software at lower cost. How can we, the space ops community, adopt state of the art software development practice, achieve greater productivity at lower cost, and maintain safe and effective space flight operations? At NASA Ames, we are developing Mission Control Technologies Software, in collaboration with Johnson Space Center (JSC) and, more recently, the Jet Propulsion Laboratory (JPL).

An Agile Constructionist Mentoring Methodology for Software Projects in the High School

ERIC Educational Resources Information Center

Meerbaum-Salant, Orni; Hazzan, Orit

2010-01-01

This article describes the construction process and evaluation of the Agile Constructionist Mentoring Methodology (ACMM), a mentoring method for guiding software development projects in the high school. The need for such a methodology has arisen due to the complexity of mentoring software project development in the high school. We introduce the…

Balancing Plan-Driven and Agile Methods in Software Engineering Project Courses

NASA Astrophysics Data System (ADS)

Boehm, Barry; Port, Dan; Winsor Brown, A.

2002-09-01

For the past 6 years, we have been teaching a two-semester software engineering project course. The students organize into 5-person teams and develop largely web-based electronic services projects for real USC campus clients. We have been using and evolving a method called Model- Based (System) Architecting and Software Engineering (MBASE) for use in both the course and in industrial applications. The MBASE Guidelines include a lot of documents. We teach risk-driven documentation: if it is risky to document something, and not risky to leave it out (e.g., GUI screen placements), leave it out. Even so, students tend to associate more documentation with higher grades, although our grading eventually discourages this. We are always on the lookout for ways to have students learn best practices without having to produce excessive documentation. Thus, we were very interested in analyzing the various emerging agile methods. We found that agile methods and milestone plan-driven methods are part of a “how much planning is enough?” spectrum. Both agile and plan-driven methods have home grounds of project characteristics where they clearly work best, and where the other will have difficulties. Hybrid agile/plan-driven approaches are feasible, and necessary for projects having a mix of agile and plan-driven home ground characteristics. Information technology trends are going more toward the agile methods' home ground characteristics of emergent requirements and rapid change, although there is a concurrent increase in concern with dependability. As a result, we are currently experimenting with risk-driven combinations of MBASE and agile methods, such as integrating requirements, test plans, peer reviews, and pair programming into “agile quality management.”

Software ``Best'' Practices: Agile Deconstructed

NASA Astrophysics Data System (ADS)

Fraser, Steven

Software “best” practices depend entirely on context - in terms of the problem domain, the system constructed, the software designers, and the “customers” ultimately deriving value from the system. Agile practices no longer have the luxury of “choosing” small non-mission critical projects with co-located teams. Project stakeholders are selecting and adapting practices based on a combina tion of interest, need and staffing. For example, growing product portfolios through a merger or the acquisition of a company exposes legacy systems to new staff, new software integration challenges, and new ideas. Innovation in communications (tools and processes) to span the growth and contraction of both information and organizations, while managing the adoption of changing software practices, is imperative for success. Traditional web-based tools such as web pages, document libraries, and forums are not suf ficient. A blend of tweeting, blogs, wikis, instant messaging, web-based confer encing, and telepresence creates a new dimension of communication “best” practices.

Future Research in Agile Systems Development: Applying Open Innovation Principles Within the Agile Organisation

NASA Astrophysics Data System (ADS)

Conboy, Kieran; Morgan, Lorraine

A particular strength of agile approaches is that they move away from ‘introverted' development and intimately involve the customer in all areas of development, supposedly leading to the development of a more innovative and hence more valuable information system. However, we argue that a single customer representative is too narrow a focus to adopt and that involvement of stakeholders beyond the software development itself is still often quite weak and in some cases non-existent. In response, we argue that current thinking regarding innovation in agile development needs to be extended to include multiple stakeholders outside the business unit. This paper explores the intra-organisational applicability and implications of open innovation in agile systems development. Additionally, it argues for a different perspective of project management that includes collaboration and knowledge-sharing with other business units, customers, partners, and other relevant stakeholders pertinent to the business success of an organisation, thus embracing open innovation principles.

Addressing the Barriers to Agile Development in DoD

DTIC Science & Technology

2015-05-01

Acquisition Small, Frequent Releases Iteratively Developed Review Working Software Vice Extensive Docs Responsive to Changes...Distribution Unlimited. Case Number 15-1457’ JCIDS IT Box Model  Streamlined requirements process for software >$15M  JROC approves IS-ICD...Services (FAR Part 37) Product-based Pay for the time and expertise of an Agile development contractor Contract for a defined software delivery

Agile: From Software to Mission System

NASA Technical Reports Server (NTRS)

Trimble, Jay; Shirley, Mark H.; Hobart, Sarah Groves

2016-01-01

The Resource Prospector (RP) is an in-situ resource utilization (ISRU) technology demonstration mission, designed to search for volatiles at the Lunar South Pole. This is NASA's first near real time tele-operated rover on the Moon. The primary objective is to search for volatiles at one of the Lunar Poles. The combination of short mission duration, a solar powered rover, and the requirement to explore shadowed regions makes for an operationally challenging mission. To maximize efficiency and flexibility in Mission System design and thus to improve the performance and reliability of the resulting Mission System, we are tailoring Agile principles that we have used effectively in ground data system software development and applying those principles to the design of elements of the mission operations system.

Agile: From Software to Mission Systems

NASA Technical Reports Server (NTRS)

Trimble, Jay; Shirley, Mark; Hobart, Sarah

2017-01-01

To maximize efficiency and flexibility in Mission Operations System (MOS) design, we are evolving principles from agile and lean methods for software, to the complete mission system. This allows for reduced operational risk at reduced cost, and achieves a more effective design through early integration of operations into mission system engineering and flight system design. The core principles are assessment of capability through demonstration, risk reduction through targeted experiments, early test and deployment, and maturation of processes and tools through use.

Agile informatics: application of agile project management to the development of a personal health application.

PubMed

Chung, Jeanhee; Pankey, Evan; Norris, Ryan J

2007-10-11

We describe the application of the Agile method-- a short iteration cycle, user responsive, measurable software development approach-- to the project management of a modular personal health record, iHealthSpace, to be deployed to the patients and providers of a large academic primary care practice.

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?

Agile Acceptance Test-Driven Development of Clinical Decision Support Advisories: Feasibility of Using Open Source Software.

PubMed

Basit, Mujeeb A; Baldwin, Krystal L; Kannan, Vaishnavi; Flahaven, Emily L; Parks, Cassandra J; Ott, Jason M; Willett, Duwayne L

2018-04-13

Moving to electronic health records (EHRs) confers substantial benefits but risks unintended consequences. Modern EHRs consist of complex software code with extensive local configurability options, which can introduce defects. Defects in clinical decision support (CDS) tools are surprisingly common. Feasible approaches to prevent and detect defects in EHR configuration, including CDS tools, are needed. In complex software systems, use of test-driven development and automated regression testing promotes reliability. Test-driven development encourages modular, testable design and expanding regression test coverage. Automated regression test suites improve software quality, providing a "safety net" for future software modifications. Each automated acceptance test serves multiple purposes, as requirements (prior to build), acceptance testing (on completion of build), regression testing (once live), and "living" design documentation. Rapid-cycle development or "agile" methods are being successfully applied to CDS development. The agile practice of automated test-driven development is not widely adopted, perhaps because most EHR software code is vendor-developed. However, key CDS advisory configuration design decisions and rules stored in the EHR may prove amenable to automated testing as "executable requirements." We aimed to establish feasibility of acceptance test-driven development of clinical decision support advisories in a commonly used EHR, using an open source automated acceptance testing framework (FitNesse). Acceptance tests were initially constructed as spreadsheet tables to facilitate clinical review. Each table specified one aspect of the CDS advisory's expected behavior. Table contents were then imported into a test suite in FitNesse, which queried the EHR database to automate testing. Tests and corresponding CDS configuration were migrated together from the development environment to production, with tests becoming part of the production regression test

Enabling Agile Testing through Continuous Integration

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

Stolberg, Sean E.

2009-08-24

A Continuous Integration system is often considered one of the key elements involved in supporting an agile software development and testing environment. As a traditional software tester transitioning to an agile development environment it became clear to me that I would need to put this essential infrastructure in place and promote improved development practices in order to make the transition to agile testing possible. This experience report discusses a continuous integration implementation I lead last year. The initial motivations for implementing continuous integration are discussed and a pre and post-assessment using Martin Fowler's "Practices of Continuous Integration" is provided alongmore » with the technical specifics of the implementation. Finally, I’ll wrap up with a retrospective of my experiences implementing and promoting continuous integration within the context of agile testing.« less

Agile

NASA Technical Reports Server (NTRS)

Trimble, Jay Phillip

2013-01-01

This is based on a previous talk on agile development. Methods for delivering software on a short cycle are described, including interactions with the customer, the affect on the team, and how to be more effective, streamlined and efficient.

Agile Learning: Sprinting through the Semester

ERIC Educational Resources Information Center

Lang, Guido

2017-01-01

This paper introduces agile learning, a novel pedagogical approach that applies the processes and principles of agile software development to the context of learning. Agile learning is characterized by short project cycles, called sprints, in which a usable deliverable is fully planned, designed, built, tested, reviewed, and launched. An…

Agile hardware and software systems engineering for critical military space applications

NASA Astrophysics Data System (ADS)

Huang, Philip M.; Knuth, Andrew A.; Krueger, Robert O.; Garrison-Darrin, Margaret A.

2012-06-01

The Multi Mission Bus Demonstrator (MBD) is a successful demonstration of agile program management and system engineering in a high risk technology application where utilizing and implementing new, untraditional development strategies were necessary. MBD produced two fully functioning spacecraft for a military/DOD application in a record breaking time frame and at dramatically reduced costs. This paper discloses the adaptation and application of concepts developed in agile software engineering to hardware product and system development for critical military applications. This challenging spacecraft did not use existing key technology (heritage hardware) and created a large paradigm shift from traditional spacecraft development. The insertion of new technologies and methods in space hardware has long been a problem due to long build times, the desire to use heritage hardware, and lack of effective process. The role of momentum in the innovative process can be exploited to tackle ongoing technology disruptions and allowing risk interactions to be mitigated in a disciplined manner. Examples of how these concepts were used during the MBD program will be delineated. Maintaining project momentum was essential to assess the constant non recurring technological challenges which needed to be retired rapidly from the engineering risk liens. Development never slowed due to tactical assessment of the hardware with the adoption of the SCRUM technique. We adapted this concept as a representation of mitigation of technical risk while allowing for design freeze later in the program's development cycle. By using Agile Systems Engineering and Management techniques which enabled decisive action, the product development momentum effectively was used to produce two novel space vehicles in a fraction of time with dramatically reduced cost.

Built To Last: Using Iterative Development Models for Sustainable Scientific Software Development

NASA Astrophysics Data System (ADS)

Jasiak, M. E.; Truslove, I.; Savoie, M.

2013-12-01

In scientific research, software development exists fundamentally for the results they create. The core research must take focus. It seems natural to researchers, driven by grant deadlines, that every dollar invested in software development should be used to push the boundaries of problem solving. This system of values is frequently misaligned with those of the software being created in a sustainable fashion; short-term optimizations create longer-term sustainability issues. The National Snow and Ice Data Center (NSIDC) has taken bold cultural steps in using agile and lean development and management methodologies to help its researchers meet critical deadlines, while building in the necessary support structure for the code to live far beyond its original milestones. Agile and lean software development and methodologies including Scrum, Kanban, Continuous Delivery and Test-Driven Development have seen widespread adoption within NSIDC. This focus on development methods is combined with an emphasis on explaining to researchers why these methods produce more desirable results for everyone, as well as promoting developers interacting with researchers. This presentation will describe NSIDC's current scientific software development model, how this addresses the short-term versus sustainability dichotomy, the lessons learned and successes realized by transitioning to this agile and lean-influenced model, and the current challenges faced by the organization.

Agile Methods: Selected DoD Management and Acquisition Concerns

DTIC Science & Technology

2011-10-01

SIDRE Software Intensive Innovative Development and Reengineering/Evolution SLIM Software Lifecycle Management -Estimate SLOC source lines of code...ISBN #0321502752 Coaching Agile Teams Lyssa Adkins ISBN #0321637704 Agile Project Management : Creating Innovative Products – Second Edition Jim...Accessed July 13, 2011. [Highsmith 2009] Highsmith, J. Agile Project Management : Creating Innovative Products, 2nd ed. Addison- Wesley, 2009

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.

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.

An Agile Course-Delivery Approach

ERIC Educational Resources Information Center

Capellan, Mirkeya

2009-01-01

In the world of software development, agile methodologies have gained popularity thanks to their lightweight methodologies and flexible approach. Many advocates believe that agile methodologies can provide significant benefits if applied in the educational environment as a teaching method. The need for an approach that engages and motivates…

Integrating Low-Cost Rapid Usability Testing into Agile System Development of Healthcare IT: A Methodological Perspective.

PubMed

Kushniruk, Andre W; Borycki, Elizabeth M

2015-01-01

The development of more usable and effective healthcare information systems has become a critical issue. In the software industry methodologies such as agile and iterative development processes have emerged to lead to more effective and usable systems. These approaches highlight focusing on user needs and promoting iterative and flexible development practices. Evaluation and testing of iterative agile development cycles is considered an important part of the agile methodology and iterative processes for system design and re-design. However, the issue of how to effectively integrate usability testing methods into rapid and flexible agile design cycles has remained to be fully explored. In this paper we describe our application of an approach known as low-cost rapid usability testing as it has been applied within agile system development in healthcare. The advantages of the integrative approach are described, along with current methodological considerations.

A Roadmap for using Agile Development in a Traditional System

NASA Technical Reports Server (NTRS)

Streiffert, Barbara; Starbird, Thomas

2006-01-01

I. Ensemble Development Group: a) Produces activity planning software for in spacecraft; b) Built on Eclipse Rich Client Platform (open source development and runtime software); c) Funded by multiple sources including the Mars Technology Program; d) Incorporated the use of Agile Development. II. Next Generation Uplink Planning System: a) Researches the Activity Planning and Sequencing Subsystem for Mars Science Laboratory (APSS); b) APSS includes Ensemble, Activity Modeling, Constraint Checking, Command Editing and Sequencing tools plus other uplink generation utilities; c) Funded by the Mars Technology Program; d) Integrates all of the tools for APSS.

Tools for Supporting Distributed Agile Project Planning

NASA Astrophysics Data System (ADS)

Wang, Xin; Maurer, Frank; Morgan, Robert; Oliveira, Josyleuda

Agile project planning plays an important part in agile software development. In distributed settings, project planning is severely impacted by the lack of face-to-face communication and the inability to share paper index cards amongst all meeting participants. To address these issues, several distributed agile planning tools were developed. The tools vary in features, functions and running platforms. In this chapter, we first summarize the requirements for distributed agile planning. Then we give an overview on existing agile planning tools. We also evaluate existing tools based on tool requirements. Finally, we present some practical advices for both designers and users of distributed agile planning tools.

Kedalion: NASA's Adaptable and Agile Hardware/Software Integration and Test Lab

NASA Technical Reports Server (NTRS)

Mangieri, Mark L.; Vice, Jason

2011-01-01

NASA fs Kedalion engineering analysis lab at Johnson Space Center is on the forefront of validating and using many contemporary avionics hardware/software development and integration techniques, which represent new paradigms to heritage NASA culture. Kedalion has validated many of the Orion hardware/software engineering techniques borrowed from the adjacent commercial aircraft avionics solution space, with the intention to build upon such techniques to better align with today fs aerospace market. Using agile techniques, commercial products, early rapid prototyping, in-house expertise and tools, and customer collaboration, Kedalion has demonstrated that cost effective contemporary paradigms hold the promise to serve future NASA endeavors within a diverse range of system domains. Kedalion provides a readily adaptable solution for medium/large scale integration projects. The Kedalion lab is currently serving as an in-line resource for the project and the Multipurpose Crew Vehicle (MPCV) program.

Agile Software Development in the Department of Defense Environment

DTIC Science & Technology

2017-03-31

Research Methodology .............................................................................................. 17 Research Hypothesis...acquisition framework to enable greater adoption of Agile methodologies . Overview of the Research Methodology The strategy for this study was to...guidance. 17 Chapter 3 – Research Methodology This chapter defines the research methodology and processes used in the study, in an effort to

Agile Software Teams: How They Engage with Systems Engineering on DoD Acquisition Programs

DTIC Science & Technology

2014-07-01

under Contract No. FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineer- ing Institute, a federally funded...issues that would preclude or limit the use of Agile methods within the DoD” [Broadus 2013]. As operational tempos increase and programs fight to...environment in which it operates . This makes software different from other disciplines that have toleranc- es, generally resulting in software engineering

Combining Agile and Traditional: Customer Communication in Distributed Environment

NASA Astrophysics Data System (ADS)

Korkala, Mikko; Pikkarainen, Minna; Conboy, Kieran

Distributed development is a radically increasing phenomenon in modern software development environments. At the same time, traditional and agile methodologies and combinations of those are being used in the industry. Agile approaches place a large emphasis on customer communication. However, existing knowledge on customer communication in distributed agile development seems to be lacking. In order to shed light on this topic and provide practical guidelines for companies in distributed agile environments, a qualitative case study was conducted in a large globally distributed software company. The key finding was that it might be difficult for an agile organization to get relevant information from a traditional type of customer organization, even though the customer communication was indicated to be active and utilized via multiple different communication media. Several challenges discussed in this paper referred to "information blackout" indicating the importance of an environment fostering meaningful communication. In order to evaluate if this environment can be created a set of guidelines is proposed.

Introduction to Stand-up Meetings in Agile Methods

NASA Astrophysics Data System (ADS)

Hasnain, Eisha; Hall, Tracy

2009-05-01

In recent years, agile methods have become more popular in the software industry. Agile methods are a new approach compared to plan-driven approaches. One of the most important shifts in adopting an agile approach is the central focus given to people in the process. This is exemplified by the independence afforded to developers in the development work they do. This work investigates the opinions of practitioners about daily stand-up meetings in the agile methods and the role of developer in that. For our investigation we joined a yahoo group called "Extreme Programming". Our investigation suggests that although trust is an important factor in agile methods. But stand-ups are not the place to build trust.

Agile Manifesto for Teaching and Learning

ERIC Educational Resources Information Center

Krehbiel, Timothy C.; Salzarulo, Peter A.; Cosmah, Michelle L.; Forren, John; Gannod, Gerald; Havelka, Douglas; Hulshult, Andrea R.; Merhout, Jeffrey

2017-01-01

A group of faculty members representing six colleges at a public university formed a learning community to study the Agile Way of Working--a method of workplace collaboration widely used in software development--and to determine whether the concepts, practices, and benefits of Agile are applicable to higher education settings. After more than two…

Distilling Design Patterns From Agile Curation Case Studies

NASA Astrophysics Data System (ADS)

Benedict, K. K.; Lenhardt, W. C.; Young, J. W.

2016-12-01

In previous work the authors have argued that there is a need to take a new look at the data management lifecycle. Our core argument is that the data management lifecycle needs to be in essence deconstructed and rebuilt. As part of this process we also argue that much can be gained from applying ideas, concepts, and principles from agile software development methods. To be sure we are not arguing for a rote application of these agile software approaches, however, given various trends related to data and technology, it is imperative to update our thinking about how to approach the data management lifecycle, recognize differing project scales, corresponding variations in structure, and alternative models for solving the problems of scientific data curation. In this paper we will describe what we term agile curation design patterns, borrowing the concept of design patterns from the software world and we will present some initial thoughts on agile curation design patterns as informed by a sample of data curation case studies solicited from participants in agile data curation meeting sessions conducted in 2015-16.

Agile Acceptance Test–Driven Development of Clinical Decision Support Advisories: Feasibility of Using Open Source Software

PubMed Central

Baldwin, Krystal L; Kannan, Vaishnavi; Flahaven, Emily L; Parks, Cassandra J; Ott, Jason M; Willett, Duwayne L

2018-01-01

Background Moving to electronic health records (EHRs) confers substantial benefits but risks unintended consequences. Modern EHRs consist of complex software code with extensive local configurability options, which can introduce defects. Defects in clinical decision support (CDS) tools are surprisingly common. Feasible approaches to prevent and detect defects in EHR configuration, including CDS tools, are needed. In complex software systems, use of test–driven development and automated regression testing promotes reliability. Test–driven development encourages modular, testable design and expanding regression test coverage. Automated regression test suites improve software quality, providing a “safety net” for future software modifications. Each automated acceptance test serves multiple purposes, as requirements (prior to build), acceptance testing (on completion of build), regression testing (once live), and “living” design documentation. Rapid-cycle development or “agile” methods are being successfully applied to CDS development. The agile practice of automated test–driven development is not widely adopted, perhaps because most EHR software code is vendor-developed. However, key CDS advisory configuration design decisions and rules stored in the EHR may prove amenable to automated testing as “executable requirements.” Objective We aimed to establish feasibility of acceptance test–driven development of clinical decision support advisories in a commonly used EHR, using an open source automated acceptance testing framework (FitNesse). Methods Acceptance tests were initially constructed as spreadsheet tables to facilitate clinical review. Each table specified one aspect of the CDS advisory’s expected behavior. Table contents were then imported into a test suite in FitNesse, which queried the EHR database to automate testing. Tests and corresponding CDS configuration were migrated together from the development environment to production, with

What Does an Agile Coach Do?

NASA Astrophysics Data System (ADS)

Davies, Rachel; Pullicino, James

The surge in Agile adoption has created a demand for project managers rather than direct their teams. A sign of this trend is the ever-increasing number of people getting certified as scrum masters and agile leaders. Training courses that introduce agile practices are easy to find. But making the transition to coach is not as simple as understanding what agile practices are. Your challenge as an Agile Coach is to support your team in learning how to wield their new Agile tools in creating great software.

Pilot users in agile development processes: motivational factors.

PubMed

Johannessen, Liv Karen; Gammon, Deede

2010-01-01

Despite a wealth of research on user participation, few studies offer insights into how to involve multi-organizational users in agile development methods. This paper is a case study of user involvement in developing a system for electronic laboratory requisitions using agile methodologies in a multi-organizational context. Building on an interpretive approach, we illuminate questions such as: How does collaboration between users and developers evolve and how might it be improved? What key motivational aspects are at play when users volunteer and continue contributing in the face of considerable added burdens? The study highlights how agile methods in themselves appear to facilitate mutually motivating collaboration between user groups and developers. Lessons learned for leveraging the advantages of agile development processes include acknowledging the substantial and ongoing contributions of users and their roles as co-designers of the system.

Inserting Agility in System Development

DTIC Science & Technology

2012-07-01

Agile IT Acquisition, IT Box, Scrum Inserting Agility in System Development Matthew R. Kennedy and Lt Col Dan Ward, USAF With the fast-paced nature...1,700 individuals and 71 countries, found Scrum and eXtreme Programming to be the most widely followed method- ologies (VersionOne, 2007). Other...University http://www.dau.mil 259 Defense ARJ, July 2012, Vol. 19 No. 3 : 249–264 Scrum Scrum is a framework used for project management, which is

The NERV Methodology: Non-Functional Requirements Elicitation, Reasoning and Validation in Agile Processes

ERIC Educational Resources Information Center

Domah, Darshan

2013-01-01

Agile software development has become very popular around the world in recent years, with methods such as Scrum and Extreme Programming (XP). Literature suggests that functionality is the primary focus in Agile processes while non-functional requirements (NFR) are either ignored or ill-defined. However, for software to be of good quality both…

Project-Method Fit: Exploring Factors That Influence Agile Method Use

ERIC Educational Resources Information Center

Young, Diana K.

2013-01-01

While the productivity and quality implications of agile software development methods (SDMs) have been demonstrated, research concerning the project contexts where their use is most appropriate has yielded less definitive results. Most experts agree that agile SDMs are not suited for all project contexts. Several project and team factors have been…

Agile deployment and code coverage testing metrics of the boot software on-board Solar Orbiter's Energetic Particle Detector

NASA Astrophysics Data System (ADS)

Parra, Pablo; da Silva, Antonio; Polo, Óscar R.; Sánchez, Sebastián

2018-02-01

In this day and age, successful embedded critical software needs agile and continuous development and testing procedures. This paper presents the overall testing and code coverage metrics obtained during the unit testing procedure carried out to verify the correctness of the boot software that will run in the Instrument Control Unit (ICU) of the Energetic Particle Detector (EPD) on-board Solar Orbiter. The ICU boot software is a critical part of the project so its verification should be addressed at an early development stage, so any test case missed in this process may affect the quality of the overall on-board software. According to the European Cooperation for Space Standardization ESA standards, testing this kind of critical software must cover 100% of the source code statement and decision paths. This leads to the complete testing of fault tolerance and recovery mechanisms that have to resolve every possible memory corruption or communication error brought about by the space environment. The introduced procedure enables fault injection from the beginning of the development process and enables to fulfill the exigent code coverage demands on the boot software.

Development of an agility assessment module for preliminary fighter design

NASA Technical Reports Server (NTRS)

Ngan, Angelen; Bauer, Brent; Biezad, Daniel; Hahn, Andrew

1996-01-01

A FORTRAN computer program is presented to perform agility analysis on fighter aircraft configurations. This code is one of the modules of the NASA Ames ACSYNT (AirCraft SYNThesis) design code. The background of the agility research in the aircraft industry and a survey of a few agility metrics are discussed. The methodology, techniques, and models developed for the code are presented. FORTRAN programs were developed for two specific metrics, CCT (Combat Cycle Time) and PM (Pointing Margin), as part of the agility module. The validity of the code was evaluated by comparing with existing flight test data. Example trade studies using the agility module along with ACSYNT were conducted using Northrop F-20 Tigershark and McDonnell Douglas F/A-18 Hornet aircraft models. The sensitivity of thrust loading and wing loading on agility criteria were investigated. The module can compare the agility potential between different configurations and has the capability to optimize agility performance in the preliminary design process. This research provides a new and useful design tool for analyzing fighter performance during air combat engagements.

Agile Data Management with the Global Change Information System

NASA Astrophysics Data System (ADS)

Duggan, B.; Aulenbach, S.; Tilmes, C.; Goldstein, J.

2013-12-01

We describe experiences applying agile software development techniques to the realm of data management during the development of the Global Change Information System (GCIS), a web service and API for authoritative global change information under development by the US Global Change Research Program. Some of the challenges during system design and implementation have been : (1) balancing the need for a rigorous mechanism for ensuring information quality with the realities of large data sets whose contents are often in flux, (2) utilizing existing data to inform decisions about the scope and nature of new data, and (3) continuously incorporating new knowledge and concepts into a relational data model. The workflow for managing the content of the system has much in common with the development of the system itself. We examine various aspects of agile software development and discuss whether or how we have been able to use them for data curation as well as software development.

Implementing Extreme Programming in Distributed Software Project Teams: Strategies and Challenges

NASA Astrophysics Data System (ADS)

Maruping, Likoebe M.

Agile software development methods and distributed forms of organizing teamwork are two team process innovations that are gaining prominence in today's demanding software development environment. Individually, each of these innovations has yielded gains in the practice of software development. Agile methods have enabled software project teams to meet the challenges of an ever turbulent business environment through enhanced flexibility and responsiveness to emergent customer needs. Distributed software project teams have enabled organizations to access highly specialized expertise across geographic locations. Although much progress has been made in understanding how to more effectively manage agile development teams and how to manage distributed software development teams, managers have little guidance on how to leverage these two potent innovations in combination. In this chapter, I outline some of the strategies and challenges associated with implementing agile methods in distributed software project teams. These are discussed in the context of a study of a large-scale software project in the United States that lasted four months.

Measuring the Impact of Agile Coaching on Students' Performance

ERIC Educational Resources Information Center

Rodríguez, Guillermo; Soria, Álvaro; Campo, Marcelo

2016-01-01

Nowadays, considerable attention is paid to agile methods as a means to improve management of software development processes. The widespread use of such methods in professional contexts has encouraged their integration into software engineering training and undergraduate courses. Although several research efforts have focused on teaching Scrum…

Overview of the TriBITS Lifecycle Model: Lean/Agile Software Lifecycle Model for Research-based Computational Science and Engineering Software

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

Bartlett, Roscoe A; Heroux, Dr. Michael A; Willenbring, James

2012-01-01

Software lifecycles are becoming an increasingly important issue for computational science & engineering (CSE) software. The process by which a piece of CSE software begins life as a set of research requirements and then matures into a trusted high-quality capability is both commonplace and extremely challenging. Although an implicit lifecycle is obviously being used in any effort, the challenges of this process--respecting the competing needs of research vs. production--cannot be overstated. Here we describe a proposal for a well-defined software lifecycle process based on modern Lean/Agile software engineering principles. What we propose is appropriate for many CSE software projects thatmore » are initially heavily focused on research but also are expected to eventually produce usable high-quality capabilities. The model is related to TriBITS, a build, integration and testing system, which serves as a strong foundation for this lifecycle model, and aspects of this lifecycle model are ingrained in the TriBITS system. Indeed this lifecycle process, if followed, will enable large-scale sustainable integration of many complex CSE software efforts across several institutions.« less

Parallel Worlds: Agile and Waterfall Differences and Similarities

DTIC Science & Technology

2013-10-01

development model , and it is deliberately shorter than the Agile Overview as most readers are assumed to be from the Traditional World. For a more in...process of DODI 5000 does not forbid the iterative incremental software development model with frequent end-user interaction, it requires heroics on...added). Today, many of the DOD’s large IT programs therefore continue to adopt program structures and software development models closely

Current State of Agile User-Centered Design: A Survey

NASA Astrophysics Data System (ADS)

Hussain, Zahid; Slany, Wolfgang; Holzinger, Andreas

Agile software development methods are quite popular nowadays and are being adopted at an increasing rate in the industry every year. However, these methods are still lacking usability awareness in their development lifecycle, and the integration of usability/User-Centered Design (UCD) into agile methods is not adequately addressed. This paper presents the preliminary results of a recently conducted online survey regarding the current state of the integration of agile methods and usability/UCD. A world wide response of 92 practitioners was received. The results show that the majority of practitioners perceive that the integration of agile methods with usability/UCD has added value to their adopted processes and to their teams; has resulted in the improvement of usability and quality of the product developed; and has increased the satisfaction of the end-users of the product developed. The top most used HCI techniques are low-fidelity prototyping, conceptual designs, observational studies of users, usability expert evaluations, field studies, personas, rapid iterative testing, and laboratory usability testing.

Ground System Architectures Workshop GMSEC SERVICES SUITE (GSS): an Agile Development Story

NASA Technical Reports Server (NTRS)

Ly, Vuong

2017-01-01

The GMSEC (Goddard Mission Services Evolution Center) Services Suite (GSS) is a collection of tools and software services along with a robust customizable web-based portal that enables the user to capture, monitor, report, and analyze system-wide GMSEC data. Given our plug-and-play architecture and the needs for rapid system development, we opted to follow the Scrum Agile Methodology for software development. Being one of the first few projects to implement the Agile methodology at NASA GSFC, in this presentation we will present our approaches, tools, successes, and challenges in implementing this methodology. The GMSEC architecture provides a scalable, extensible ground and flight system for existing and future missions. GMSEC comes with a robust Application Programming Interface (GMSEC API) and a core set of Java-based GMSEC components that facilitate the development of a GMSEC-based ground system. Over the past few years, we have seen an upbeat in the number of customers who are moving from a native desktop application environment to a web based environment particularly for data monitoring and analysis. We also see a need to provide separation of the business logic from the GUI display for our Java-based components and also to consolidate all the GUI displays into one interface. This combination of separation and consolidation brings immediate value to a GMSEC-based ground system through increased ease of data access via a uniform interface, built-in security measures, centralized configuration management, and ease of feature extensibility.

Test Methods for Robot Agility in Manufacturing.

PubMed

Downs, Anthony; Harrison, William; Schlenoff, Craig

2016-01-01

The paper aims to define and describe test methods and metrics to assess industrial robot system agility in both simulation and in reality. The paper describes test methods and associated quantitative and qualitative metrics for assessing robot system efficiency and effectiveness which can then be used for the assessment of system agility. The paper describes how the test methods were implemented in a simulation environment and real world environment. It also shows how the metrics are measured and assessed as they would be in a future competition. The test methods described in this paper will push forward the state of the art in software agility for manufacturing robots, allowing small and medium manufacturers to better utilize robotic systems. The paper fulfills the identified need for standard test methods to measure and allow for improvement in software agility for manufacturing robots.

Future Software Sizing Metrics and Estimation Challenges

DTIC Science & Technology

2011-07-01

systems 4. Ultrahigh software system assurance 5. Legacy maintenance and Brownfield development 6. Agile and Lean/ Kanban development. This paper...refined as the design of the maintenance modifications or Brownfield re-engineering is determined. VII. 6. AGILE AND LEAN/ KANBAN DEVELOPMENT The...difficulties of software maintenance estimation can often be mitigated by using lean workflow management techniques such as Kanban [25]. In Kanban

Agile Preparation within a Traditional Project Management Course

ERIC Educational Resources Information Center

Landry, Jeffrey P.; McDaniel, Rachel

2016-01-01

Agile software approaches have seen a steady rise over a decade and a half, but agile's place in the information systems (IS) undergraduate curriculum is far from settled. While agile concepts may arguably be taught in multiple places in the IS curriculum, this paper argues for its inclusion in a project management course. This paper builds on…

Fostering soft skills in project-oriented learning within an agile atmosphere

NASA Astrophysics Data System (ADS)

Chassidim, Hadas; Almog, Dani; Mark, Shlomo

2018-07-01

The project-oriented and Agile approaches have motivated a new generation of software engineers. Within the academic curriculum, the issue of whether students are being sufficiently prepared for the future has been raised. The objective of this work is to present the project-oriented environment as an influential factor that software engineering profession requires, using the second year course 'Software Development and Management in Agile Approach' as a case-study. This course combines academic topics, self-learned and soft skills implementation, the call for creativity, and the recognition of updated technologies and dynamic circumstances. The results of a survey that evaluated the perceived value of the course showed that the highest contribution of our environment was in the effectiveness of the team-work and the overall development process of the project.

Test Methods for Robot Agility in Manufacturing

PubMed Central

Downs, Anthony; Harrison, William; Schlenoff, Craig

2017-01-01

Purpose The paper aims to define and describe test methods and metrics to assess industrial robot system agility in both simulation and in reality. Design/methodology/approach The paper describes test methods and associated quantitative and qualitative metrics for assessing robot system efficiency and effectiveness which can then be used for the assessment of system agility. Findings The paper describes how the test methods were implemented in a simulation environment and real world environment. It also shows how the metrics are measured and assessed as they would be in a future competition. Practical Implications The test methods described in this paper will push forward the state of the art in software agility for manufacturing robots, allowing small and medium manufacturers to better utilize robotic systems. Originality / value The paper fulfills the identified need for standard test methods to measure and allow for improvement in software agility for manufacturing robots. PMID:28203034

Towards a Better Understanding of CMMI and Agile Integration - Multiple Case Study of Four Companies

NASA Astrophysics Data System (ADS)

Pikkarainen, Minna

The amount of software is increasing in the different domains in Europe. This provides the industries in smaller countries good opportunities to work in the international markets. Success in the global markets however demands the rapid production of high quality, error free software. Both CMMI and agile methods seem to provide a ready solution for quality and lead time improvements. There is not, however, much empirical evidence available either about 1) how the integration of these two aspects can be done in practice or 2) what it actually demands from assessors and software process improvement groups. The goal of this paper is to increase the understanding of CMMI and agile integration, in particular, focusing on the research question: how to use ‘lightweight’ style of CMMI assessments in agile contexts. This is done via four case studies in which assessments were conducted using the goals of CMMI integrated project management and collaboration and coordination with relevant stakeholder process areas and practices from XP and Scrum. The study shows that the use of agile practices may support the fulfilment of the goals of CMMI process areas but there are still many challenges for the agile teams to be solved within the continuous improvement programs. It also identifies practical advices to the assessors and improvement groups to take into consideration when conducting assessment in the context of agile software development.

Customer Communication Challenges and Solutions in Globally Distributed Agile Software Development

NASA Astrophysics Data System (ADS)

Pikkarainen, Minna; Korkala, Mikko

Working in the globally distributed market is one of the key trends among the software organizations all over the world. [1-5]. Several factors have contributed to the growth of distributed software development; time-zone independent ”follow the sun” development, access to well-educated labour, maturation of the technical infrastructure and reduced costs are some of the most commonly cited benefits of distributed development [3, 6-8]. Furthermore, customers are often located in different countries because of the companies’ internationalization purposes or good market opportunities.

Onshore and Offshore Outsourcing with Agility: Lessons Learned

NASA Astrophysics Data System (ADS)

Kussmaul, Clifton

This chapter reflects on case study based an agile distributed project that ran for approximately three years (from spring 2003 to spring 2006). The project involved (a) a customer organization with key personnel distributed across the US, developing an application with rapidly changing requirements; (b) onshore consultants with expertise in project management, development processes, offshoring, and relevant technologies; and (c) an external offsite development team in a CMM-5 organization in southern India. This chapter is based on surveys and discussions with multiple participants. The several years since the project was completed allow greater perspective on both the strengths and weaknesses, since the participants can reflect on the entire life of the project, and compare it to subsequent experiences. Our findings emphasize the potential for agile project management in distributed software development, and the importance of people and interactions, taking many small steps to find and correct errors, and matching the structures of the project and product to support implementation of agility.

IT Software Development and IT Operations Strategic Alignment: An Agile DevOps Model

ERIC Educational Resources Information Center

Hart, Michael

2017-01-01

Information Technology (IT) departments that include development and operations are essential to develop software that meet customer needs. DevOps is a term originally constructed from software development and IT operations. DevOps includes the collaboration of all stakeholders such as software engineers and systems administrators involved in the…

Update 2016: Considerations for Using Agile in DoD Acquisition

DTIC Science & Technology

2016-12-01

What Is Agile? 4 2.1 Agile Manifesto and Principles—A Brief History 4 2.2 A Practical Definition 6 2.3 Example Agile Method 6 2.4 Example Agile...5.8 Team Composition 45 5.9 Culture 46 6 Conclusion 48 Appendix A: Examples of Agile Methods 50 Appendix B: Common Objections to Agile 53...thank all those who have contributed to our knowledge of apply- ing “other than traditional” methods for software system acquisition and management over

Agile Data Curation at a State Geological Survey

NASA Astrophysics Data System (ADS)

Hills, D. J.

2015-12-01

State agencies, including geological surveys, are often the gatekeepers for myriad data products essential for scientific research and economic development. For example, the Geological Survey of Alabama (GSA) is mandated to explore for, characterize, and report Alabama's mineral, energy, water, and biological resources in support of economic development, conservation, management, and public policy for the betterment of Alabama's citizens, communities, and businesses. As part of that mandate, the GSA has increasingly been called upon to make our data more accessible to stakeholders. Even as demand for greater data accessibility grows, budgets for such efforts are often small, meaning that agencies must do more for less. Agile software development has yielded efficient, effective products, most often at lower cost and in shorter time. Taking guidance from the agile software development model, the GSA is working towards more agile data management and curation. To date, the GSA's work has been focused primarily on data rescue. By using workflows that maximize clear communication while encouraging simplicity (e.g., maximizing the amount of work not done or that can be automated), the GSA is bringing decades of dark data into the light. Regular checks by the data rescuer with the data provider (or their proxy) provides quality control without adding an overt burden on either party. Moving forward, these workflows will also allow for more efficient and effective data management.

The Holy Grail of Agile Acquisition

DTIC Science & Technology

2010-04-01

Motivation • What is Agility? • Approach C t t Th A i iti S t (Th Bi “A” A i iti P )• on ex : e cqu s on ys em e g cqu s on rocess • Agile Software...Bestsellers…” [Erwin 2009] Motivation • Despite of Erwin’s recommendation… – Agility seems to be a simple concept and it is commonly perceived as a virtue...tension between the numerous stakeholders due to different motivation /behavior • The process elements themselves are complex and ambiguous Slide 16Peter

Preparing your Offshore Organization for Agility: Experiences in India

NASA Astrophysics Data System (ADS)

Srinivasan, Jayakanth

Two strategies that have significantly changed the way we conventionally think about managing software development and sustainment are the family of development approaches collectively referred to as agile methods, and the distribution of development efforts on a global scale. When you combine the two strategies, organizations have to address not only the technical challenges that arise from introducing new ways of working, but more importantly have to manage the 'soft' factors that if ignored lead to hard challenges. Using two case studies of distributed agile software development in India we illustrate the areas that organizations need to be aware of when transitioning work to India. The key issues that we emphasize are the need to recruit and retain personnel; the importance of teaching, mentoring and coaching; the need to manage customer expectations; the criticality of well-articulated senior leadership vision and commitment; and the reality of operating in a heterogeneous process environment.

Management Guidelines for Database Developers' Teams in Software Development Projects

NASA Astrophysics Data System (ADS)

Rusu, Lazar; Lin, Yifeng; Hodosi, Georg

Worldwide job market for database developers (DBDs) is continually increasing in last several years. In some companies, DBDs are organized as a special team (DBDs team) to support other projects and roles. As a new role, the DBDs team is facing a major problem that there are not any management guidelines for them. The team manager does not know which kinds of tasks should be assigned to this team and what practices should be used during DBDs work. Therefore in this paper we have developed a set of management guidelines, which includes 8 fundamental tasks and 17 practices from software development process, by using two methodologies Capability Maturity Model (CMM) and agile software development in particular Scrum in order to improve the DBDs team work. Moreover the management guidelines developed here has been complemented with practices from authors' experience in this area and has been evaluated in the case of a software company. The management guidelines for DBD teams presented in this paper could be very usefully for other companies too that are using a DBDs team and could contribute towards an increase of the efficiency of these teams in their work on software development projects.

Collaborative Software Development in Support of Fast Adaptive AeroSpace Tools (FAAST)

NASA Technical Reports Server (NTRS)

Kleb, William L.; Nielsen, Eric J.; Gnoffo, Peter A.; Park, Michael A.; Wood, William A.

2003-01-01

A collaborative software development approach is described. The software product is an adaptation of proven computational capabilities combined with new capabilities to form the Agency's next generation aerothermodynamic and aerodynamic analysis and design tools. To efficiently produce a cohesive, robust, and extensible software suite, the approach uses agile software development techniques; specifically, project retrospectives, the Scrum status meeting format, and a subset of Extreme Programming's coding practices are employed. Examples are provided which demonstrate the substantial benefits derived from employing these practices. Also included is a discussion of issues encountered when porting legacy Fortran 77 code to Fortran 95 and a Fortran 95 coding standard.

Exploring the Role of Value Networks for Software Innovation

NASA Astrophysics Data System (ADS)

Morgan, Lorraine; Conboy, Kieran

This paper describes a research-in-progress that aims to explore the applicability and implications of open innovation practices in two firms - one that employs agile development methods and another that utilizes open source software. The open innovation paradigm has a lot in common with open source and agile development methodologies. A particular strength of agile approaches is that they move away from 'introverted' development, involving only the development personnel, and intimately involves the customer in all areas of software creation, supposedly leading to the development of a more innovative and hence more valuable information system. Open source software (OSS) development also shares two key elements of the open innovation model, namely the collaborative development of the technology and shared rights to the use of the technology. However, one shortfall with agile development in particular is the narrow focus on a single customer representative. In response to this, we argue that current thinking regarding innovation needs to be extended to include multiple stakeholders both across and outside the organization. Additionally, for firms utilizing open source, it has been found that their position in a network of potential complementors determines the amount of superior value they create for their customers. Thus, this paper aims to get a better understanding of the applicability and implications of open innovation practices in firms that employ open source and agile development methodologies. In particular, a conceptual framework is derived for further testing.

ISS Double-Gimbaled CMG Subsystem Simulation Using the Agile Development Method

NASA Technical Reports Server (NTRS)

Inampudi, Ravi

2016-01-01

This paper presents an evolutionary approach in simulating a cluster of 4 Control Moment Gyros (CMG) on the International Space Station (ISS) using a common sense approach (the agile development method) for concurrent mathematical modeling and simulation of the CMG subsystem. This simulation is part of Training systems for the 21st Century simulator which will provide training for crew members, instructors, and flight controllers. The basic idea of how the CMGs on the space station are used for its non-propulsive attitude control is briefly explained to set up the context for simulating a CMG subsystem. Next different reference frames and the detailed equations of motion (EOM) for multiple double-gimbal variable-speed control moment gyroscopes (DGVs) are presented. Fixing some of the terms in the EOM becomes the special case EOM for ISS's double-gimbaled fixed speed CMGs. CMG simulation development using the agile development method is presented in which customer's requirements and solutions evolve through iterative analysis, design, coding, unit testing and acceptance testing. At the end of the iteration a set of features implemented in that iteration are demonstrated to the flight controllers thus creating a short feedback loop and helping in creating adaptive development cycles. The unified modeling language (UML) tool is used in illustrating the user stories, class designs and sequence diagrams. This incremental development approach of mathematical modeling and simulating the CMG subsystem involved the development team and the customer early on, thus improving the quality of the working CMG system in each iteration and helping the team to accurately predict the cost, schedule and delivery of the software.

Agile Task Tracking Tool

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

Duke, Roger T.; Crump, Thomas Vu

The work was created to provide a tool for the purpose of improving the management of tasks associated with Agile projects. Agile projects are typically completed in an iterative manner with many short duration tasks being performed as part of iterations. These iterations are generally referred to as sprints. The objective of this work is to create a single tool that enables sprint teams to manage all of their tasks in multiple sprints and automatically produce all standard sprint performance charts with minimum effort. The format of the printed work is designed to mimic a standard Kanban board. The workmore » is developed as a single Excel file with worksheets capable of managing up to five concurrent sprints and up to one hundred tasks. It also includes a summary worksheet providing performance information from all active sprints. There are many commercial project management systems typically designed with features desired by larger organizations with many resources managing multiple programs and projects. The audience for this work is the small organizations and Agile project teams desiring an inexpensive, simple, user-friendly, task management tool. This work uses standard readily available software, Excel, requiring minimum data entry and automatically creating summary charts and performance data. It is formatted to print out and resemble standard flip charts and provide the visuals associated with this type of work.« less

Agile Software Development in Defense Acquisition: A Mission Assurance Perspective

DTIC Science & Technology

2012-03-23

based information retrieval system, we might say that this program works like a hive of bees , going out for pollen and bringing it back to the hive...developers ® Six Siqma is reqistered in the U. S. Patent and Trademark Office by Motorola ^_ 33 @ AEROSPACE Major Areas in a Typical Software...requirements - Capturing and evaluating quality metrics, identifying common problem areas **» Despite its positive impact on quality, pair programming

Applying Standard Independent Verification and Validation (IVV) Techniques Within an Agile Framework: Is There a Compatibility Issue?

NASA Technical Reports Server (NTRS)

Dabney, James B.; Arthur, James Douglas

2017-01-01

Agile methods have gained wide acceptance over the past several years, to the point that they are now a standard management and execution approach for small-scale software development projects. While conventional Agile methods are not generally applicable to large multi-year and mission-critical systems, Agile hybrids are now being developed (such as SAFe) to exploit the productivity improvements of Agile while retaining the necessary process rigor and coordination needs of these projects. From the perspective of Independent Verification and Validation (IVV), however, the adoption of these hybrid Agile frameworks is becoming somewhat problematic. Hence, we find it prudent to question the compatibility of conventional IVV techniques with (hybrid) Agile practices.This paper documents our investigation of (a) relevant literature, (b) the modification and adoption of Agile frameworks to accommodate the development of large scale, mission critical systems, and (c) the compatibility of standard IVV techniques within hybrid Agile development frameworks. Specific to the latter, we found that the IVV methods employed within a hybrid Agile process can be divided into three groups: (1) early lifecycle IVV techniques that are fully compatible with the hybrid lifecycles, (2) IVV techniques that focus on tracing requirements, test objectives, etc. are somewhat incompatible, but can be tailored with a modest effort, and (3) IVV techniques involving an assessment requiring artifact completeness that are simply not compatible with hybrid Agile processes, e.g., those that assume complete requirement specification early in the development lifecycle.

DoD Acquisitions Reform: Embracing and Implementing Agile

DTIC Science & Technology

2015-12-01

required in the traditional waterfall approach.   Specific models for enterprise level efforts include Scaled Agile Framework, Disciplined Agile...and Acquisition Concerns. Pittsburgh: Carnegie Mellon.  Leffingwell, D. (2007). Why The Waterfall Model Doesn’t Work. In D. Leffingwell, Scaling...serious issue might be the acquisitions process itself. For the last twenty plus years, the Air Force has used the waterfall approach for software

Development of a Computer Program for Analyzing Preliminary Aircraft Configurations in Relationship to Emerging Agility Metrics

NASA Technical Reports Server (NTRS)

Bauer, Brent

1993-01-01

This paper discusses the development of a FORTRAN computer code to perform agility analysis on aircraft configurations. This code is to be part of the NASA-Ames ACSYNT (AirCraft SYNThesis) design code. This paper begins with a discussion of contemporary agility research in the aircraft industry and a survey of a few agility metrics. The methodology, techniques and models developed for the code are then presented. Finally, example trade studies using the agility module along with ACSYNT are illustrated. These trade studies were conducted using a Northrop F-20 Tigershark aircraft model. The studies show that the agility module is effective in analyzing the influence of common parameters such as thrust-to-weight ratio and wing loading on agility criteria. The module can compare the agility potential between different configurations. In addition, one study illustrates the module's ability to optimize a configuration's agility performance.

Towards seamless workflows in agile data science

NASA Astrophysics Data System (ADS)

Klump, J. F.; Robertson, J.

2017-12-01

Agile workflows are a response to projects with requirements that may change over time. They prioritise rapid and flexible responses to change, preferring to adapt to changes in requirements rather than predict them before a project starts. This suits the needs of research very well because research is inherently agile in its methodology. The adoption of agile methods has made collaborative data analysis much easier in a research environment fragmented across institutional data stores, HPC, personal and lab computers and more recently cloud environments. Agile workflows use tools that share a common worldview: in an agile environment, there may be more that one valid version of data, code or environment in play at any given time. All of these versions need references and identifiers. For example, a team of developers following the git-flow conventions (github.com/nvie/gitflow) may have several active branches, one for each strand of development. These workflows allow rapid and parallel iteration while maintaining identifiers pointing to individual snapshots of data and code and allowing rapid switching between strands. In contrast, the current focus of versioning in research data management is geared towards managing data for reproducibility and long-term preservation of the record of science. While both are important goals in the persistent curation domain of the institutional research data infrastructure, current tools emphasise planning over adaptation and can introduce unwanted rigidity by insisting on a single valid version or point of truth. In the collaborative curation domain of a research project, things are more fluid. However, there is no equivalent to the "versioning iso-surface" of the git protocol for the management and versioning of research data. At CSIRO we are developing concepts and tools for the agile management of software code and research data for virtual research environments, based on our experiences of actual data analytics projects in the

Software Intensive Systems Data Quality and Estimation Research in Support of Future Defense Cost Analysis

DTIC Science & Technology

2012-03-13

Legacy Maintenance and Brownfield Development 6.6.6 Agile and Kanban Development 6.6.7 Putting It All Together at the Large-Project or Enterprise Level...NDI)-intensive systems Ultrahigh software system assurance; Legacy maintenance and brownfield development; and Agile and kanban development. This...be furnished by NDI components or may need to be developed for special systems. Legacy Maintenance and Brownfield Development Fewer and fewer software

Rolling and tumbling: status of the SuperAGILE experiment

NASA Astrophysics Data System (ADS)

Del Monte, E.; Costa, E.; di Persio, G.; Donnarumma, I.; Evangelista, Y.; Feroci, M.; Lapshov, I.; Lazzarotto, F.; Mastropietro, M.; Morelli, E.; Pacciani, L.; Rapisarda, M.; Rubini, A.; Soffitta, P.; Tavani, M.; Argan, A.; Trois, A.

2010-07-01

The SuperAGILE experiment is the hard X-ray monitor of the AGILE mission. It is a 2 x one-dimensional imager, with 6-arcmin angular resolution in the energy range 18 - 60 keV and a field of view in excess of 1 steradian. SuperAGILE is successfully operating in orbit since Summer 2007, providing long-term monitoring of bright sources and prompt detection and localization of gamma-ray bursts. Starting on October 2009 the AGILE mission lost its reaction wheel and the satellite attitude is no longer stabilized. The current mode of operation of the AGILE satellite is a Spinning Mode, around the Sun-pointing direction, with an angular velocity of about 0.8 degree/s (corresponding to 8 times the SuperAGILE point spread function every second). In these new conditions, SuperAGILE continuously scans a much larger fraction of the sky, with much smaller exposure to each region. In this paper we review some of the results of the first 2.5 years of "standard" operation of SuperAGILE, and show how new implementations in the data analysis software allows to continue the hard X-ray sky monitoring by SuperAGILE also in the new attitude conditions.

Development of EarthCube Governance: An Agile Approach

NASA Astrophysics Data System (ADS)

Pearthree, G.; Allison, M. L.; Patten, K.

2013-12-01

Governance of geosciences cyberinfrastructure is a complex and essential undertaking, critical in enabling distributed knowledge communities to collaborate and communicate across disciplines, distances, and cultures. Advancing science with respect to 'grand challenges," such as global climate change, weather prediction, and core fundamental science, depends not just on technical cyber systems, but also on social systems for strategic planning, decision-making, project management, learning, teaching, and building a community of practice. Simply put, a robust, agile technical system depends on an equally robust and agile social system. Cyberinfrastructure development is wrapped in social, organizational and governance challenges, which may significantly impede progress. An agile development process is underway for governance of transformative investments in geosciences cyberinfrastructure through the NSF EarthCube initiative. Agile development is iterative and incremental, and promotes adaptive planning and rapid and flexible response. Such iterative deployment across a variety of EarthCube stakeholders encourages transparency, consensus, accountability, and inclusiveness. A project Secretariat acts as the coordinating body, carrying out duties for planning, organizing, communicating, and reporting. A broad coalition of stakeholder groups comprises an Assembly (Mainstream Scientists, Cyberinfrastructure Institutions, Information Technology/Computer Sciences, NSF EarthCube Investigators, Science Communities, EarthCube End-User Workshop Organizers, Professional Societies) to serve as a preliminary venue for identifying, evaluating, and testing potential governance models. To offer opportunity for broader end-user input, a crowd-source approach will engage stakeholders not involved otherwise. An Advisory Committee from the Earth, ocean, atmosphere, social, computer and library sciences is guiding the process from a high-level policy point of view. Developmental

The Impacts of Agile Development Methodology Use on Project Success: A Contingency View

ERIC Educational Resources Information Center

Tripp, John F.

2012-01-01

Agile Information Systems Development Methods have emerged in the past decade as an alternative manner of managing the work and delivery of information systems development teams, with a large number of organizations reporting the adoption & use of agile methods. The practitioners of these methods make broad claims as to the benefits of their…

AGILE/GRID Science Alert Monitoring System: The Workflow and the Crab Flare Case

NASA Astrophysics Data System (ADS)

Bulgarelli, A.; Trifoglio, M.; Gianotti, F.; Tavani, M.; Conforti, V.; Parmiggiani, N.

2013-10-01

During the first five years of the AGILE mission we have observed many gamma-ray transients of Galactic and extragalactic origin. A fast reaction to unexpected transient events is a crucial part of the AGILE monitoring program, because the follow-up of astrophysical transients is a key point for this space mission. We present the workflow and the software developed by the AGILE Team to perform the automatic analysis for the detection of gamma-ray transients. In addition, an App for iPhone will be released enabling the Team to access the monitoring system through mobile phones. In 2010 September the science alert monitoring system presented in this paper recorded a transient phenomena from the Crab Nebula, generating an automated alert sent via email and SMS two hours after the end of an AGILE satellite orbit, i.e. two hours after the Crab flare itself: for this discovery AGILE won the 2012 Bruno Rossi prize. The design of this alert system is maximized to reach the maximum speed, and in this, as in many other cases, AGILE has demonstrated that the reaction speed of the monitoring system is crucial for the scientific return of the mission.

Wired Widgets: Agile Visualization for Space Situational Awareness

NASA Astrophysics Data System (ADS)

Gerschefske, K.; Witmer, J.

2012-09-01

Continued advancement in sensors and analysis techniques have resulted in a wealth of Space Situational Awareness (SSA) data, made available via tools and Service Oriented Architectures (SOA) such as those in the Joint Space Operations Center Mission Systems (JMS) environment. Current visualization software cannot quickly adapt to rapidly changing missions and data, preventing operators and analysts from performing their jobs effectively. The value of this wealth of SSA data is not fully realized, as the operators' existing software is not built with the flexibility to consume new or changing sources of data or to rapidly customize their visualization as the mission evolves. While tools like the JMS user-defined operational picture (UDOP) have begun to fill this gap, this paper presents a further evolution, leveraging Web 2.0 technologies for maximum agility. We demonstrate a flexible Web widget framework with inter-widget data sharing, publish-subscribe eventing, and an API providing the basis for consumption of new data sources and adaptable visualization. Wired Widgets offers cross-portal widgets along with a widget communication framework and development toolkit for rapid new widget development, giving operators the ability to answer relevant questions as the mission evolves. Wired Widgets has been applied in a number of dynamic mission domains including disaster response, combat operations, and noncombatant evacuation scenarios. The variety of applications demonstrate that Wired Widgets provides a flexible, data driven solution for visualization in changing environments. In this paper, we show how, deployed in the Ozone Widget Framework portal environment, Wired Widgets can provide an agile, web-based visualization to support the SSA mission. Furthermore, we discuss how the tenets of agile visualization can generally be applied to the SSA problem space to provide operators flexibility, potentially informing future acquisition and system development.

RT 6 - Software Intensive Systems Data Quality and Estimation Research in Support of Future Defense Cost Analysis

DTIC Science & Technology

2012-03-13

Brownfield Development 6.6.6 Agile and Kanban Development 6.6.7 Putting It All Together at the Large-Project or Enterprise Level 6.7 References 7...Ultrahigh software system assurance; Legacy maintenance and brownfield development; and Agile and kanban development. This chapter summarizes each...components or may need to be developed for special systems. Legacy Maintenance and Brownfield Development Fewer and fewer software-intensive systems have

Agile Walker.

PubMed

Katz, Reuven

2015-01-01

The goal of the Agile Walker is to improve the outdoor mobility of healthy elderly people with some mobility limitations. It is a newly developed, all-terrain walker, equipped with an electric drive system and speed control that can assists elderly people to walk outdoors or to hike. The walker has a unique product design with an attractive look that will appeal to "active-agers" population. This paper describes product design requirements and the development process of the Agile Walker, its features and some preliminary testing results.

Coping with Uncertainty in an Agile Systems Development Course

ERIC Educational Resources Information Center

Taipalus, Toni; Seppänen, Ville; Pirhonen, Maritta

2018-01-01

Uncertain and ambiguous environments are commonplace in information systems development (ISD) projects, and while different Agile frameworks welcome changes in organizational, technical, and business environments, the incurred uncertainty is known to negatively affect the development process and the quality of the final product. The effects of…

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

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

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

effective communications; adopting an agile-based software development process across the observatory to enable frequent software releases to help mitigate subsystem interdependencies; defining concise scope and work packages for each of the OSW subsystems to facilitate effective outsourcing of software deliverables to the ITCC partner, and to enable performance monitoring and risk management. At this stage, the architecture and high-level design of the software system has been established and reviewed. During construction each subsystem will have a final design phase with reviews, followed by implementation and testing. The results of the TMT approach to the Observatory Software development process will only be preliminary at the time of the submittal of this paper, but it is anticipated that the early results will be a favorable indication of progress.

TriBITS lifecycle model. Version 1.0, a lean/agile software lifecycle model for research-based computational science and engineering and applied mathematical software.

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

Willenbring, James M.; Bartlett, Roscoe Ainsworth; Heroux, Michael Allen

2012-01-01

Software lifecycles are becoming an increasingly important issue for computational science and engineering (CSE) software. The process by which a piece of CSE software begins life as a set of research requirements and then matures into a trusted high-quality capability is both commonplace and extremely challenging. Although an implicit lifecycle is obviously being used in any effort, the challenges of this process - respecting the competing needs of research vs. production - cannot be overstated. Here we describe a proposal for a well-defined software lifecycle process based on modern Lean/Agile software engineering principles. What we propose is appropriate for manymore » CSE software projects that are initially heavily focused on research but also are expected to eventually produce usable high-quality capabilities. The model is related to TriBITS, a build, integration and testing system, which serves as a strong foundation for this lifecycle model, and aspects of this lifecycle model are ingrained in the TriBITS system. Here, we advocate three to four phases or maturity levels that address the appropriate handling of many issues associated with the transition from research to production software. The goals of this lifecycle model are to better communicate maturity levels with customers and to help to identify and promote Software Engineering (SE) practices that will help to improve productivity and produce better software. An important collection of software in this domain is Trilinos, which is used as the motivation and the initial target for this lifecycle model. However, many other related and similar CSE (and non-CSE) software projects can also make good use of this lifecycle model, especially those that use the TriBITS system. Indeed this lifecycle process, if followed, will enable large-scale sustainable integration of many complex CSE software efforts across several institutions.« less

Applying Agile Methods to the Development of a Community-Based Sea Ice Observations Database

NASA Astrophysics Data System (ADS)

Pulsifer, P. L.; Collins, J. A.; Kaufman, M.; Eicken, H.; Parsons, M. A.; Gearheard, S.

2011-12-01

Local and traditional knowledge and community-based monitoring programs are increasingly being recognized as an important part of establishing an Arctic observing network, and understanding Arctic environmental change. The Seasonal Ice Zone Observing Network (SIZONet, http://www.sizonet.org) project has implemented an integrated program for observing seasonal ice in Alaska. Observation and analysis by local sea ice experts helps track seasonal and inter-annual variability of the ice cover and its use by coastal communities. The ELOKA project (http://eloka-arctic.org) is collaborating with SIZONet on the development of a community accessible, Web-based application for collecting and distributing local observations. The SIZONet project is dealing with complicated qualitative and quantitative data collected from a growing number of observers in different communities while concurrently working to design a system that will serve a wide range of different end users including Arctic residents, scientists, educators, and other stakeholders with a need for sea ice information. The benefits of linking and integrating knowledge from communities and university-based researchers are clear, however, development of an information system in this multidisciplinary, multi-participant context is challenging. Participants are geographically distributed, have different levels of technical expertise, and have varying goals for how the system will be used. As previously reported (Pulsifer et al. 2010), new technologies have been used to deal with some of the challenges presented in this complex development context. In this paper, we report on the challenges and innovations related to working as a multi-disciplinary software development team. Specifically, we discuss how Agile software development methods have been used in defining and refining user needs, developing prototypes, and releasing a production level application. We provide an overview of the production application that

Lean Mission Operations Systems Design - Using Agile and Lean Development Principles for Mission Operations Design and Development

NASA Technical Reports Server (NTRS)

Trimble, Jay Phillip

2014-01-01

The Resource Prospector Mission seeks to rove the lunar surface with an in-situ resource utilization payload in search of volatiles at a polar region. The mission operations system (MOS) will need to perform the short-duration mission while taking advantage of the near real time control that the short one-way light time to the Moon provides. To maximize our use of limited resources for the design and development of the MOS we are utilizing agile and lean methods derived from our previous experience with applying these methods to software. By using methods such as "say it then sim it" we will spend less time in meetings and more time focused on the one outcome that counts - the effective utilization of our assets on the Moon to meet mission objectives.

Agile Data Curation Case Studies Leading to the Identification and Development of Data Curation Design Patterns

NASA Astrophysics Data System (ADS)

Benedict, K. K.; Lenhardt, W. C.; Young, J. W.; Gordon, L. C.; Hughes, S.; Santhana Vannan, S. K.

2017-12-01

The planning for and development of efficient workflows for the creation, reuse, sharing, documentation, publication and preservation of research data is a general challenge that research teams of all sizes face. In response to: requirements from funding agencies for full-lifecycle data management plans that will result in well documented, preserved, and shared research data products increasing requirements from publishers for shared data in conjunction with submitted papers interdisciplinary research team's needs for efficient data sharing within projects, and increasing reuse of research data for replication and new, unanticipated research, policy development, and public use alternative strategies to traditional data life cycle approaches must be developed and shared that enable research teams to meet these requirements while meeting the core science objectives of their projects within the available resources. In support of achieving these goals, the concept of Agile Data Curation has been developed in which there have been parallel activities in support of 1) identifying a set of shared values and principles that underlie the objectives of agile data curation, 2) soliciting case studies from the Earth science and other research communities that illustrate aspects of what the contributors consider agile data curation methods and practices, and 3) identifying or developing design patterns that are high-level abstractions from successful data curation practice that are related to common data curation problems for which common solution strategies may be employed. This paper provides a collection of case studies that have been contributed by the Earth science community, and an initial analysis of those case studies to map them to emerging shared data curation problems and their potential solutions. Following the initial analysis of these problems and potential solutions, existing design patterns from software engineering and related disciplines are identified as a

75 FR 11920 - Agilent Technologies, Eesof Division, Including On-Site Leased Workers From Volt and Managed...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-03-12

... software and related services including quality assurance and learning products, marketing, product development, marketing and administration. The company reports that on-site leased workers from Managed..., Santa Clara, California, and the Everett, Washington locations of Agilent Technologies, EEsof Division...

Software Development in the Water Sciences: a view from the divide (Invited)

NASA Astrophysics Data System (ADS)

Miles, B.; Band, L. E.

2013-12-01

While training in statistical methods is an important part of many earth scientists' training, these scientists often learn the bulk of their software development skills in an ad hoc, just-in-time manner. Yet to carry out contemporary research scientists are spending more and more time developing software. Here I present perspectives - as an earth sciences graduate student with professional software engineering experience - on the challenges scientists face adopting software engineering practices, with an emphasis on areas of the science software development lifecycle that could benefit most from improved engineering. This work builds on experience gained as part of the NSF-funded Water Science Software Institute (WSSI) conceptualization award (NSF Award # 1216817). Throughout 2013, the WSSI team held a series of software scoping and development sprints with the goals of: (1) adding features to better model green infrastructure within the Regional Hydro-Ecological Simulation System (RHESSys); and (2) infusing test-driven agile software development practices into the processes employed by the RHESSys team. The goal of efforts such as the WSSI is to ensure that investments by current and future scientists in software engineering training will enable transformative science by improving both scientific reproducibility and researcher productivity. Experience with the WSSI indicates: (1) the potential for achieving this goal; and (2) while scientists are willing to adopt some software engineering practices, transformative science will require continued collaboration between domain scientists and cyberinfrastructure experts for the foreseeable future.

Organizational Agility and Complex Enterprise System Innovations: A Mixed Methods Study of the Effects of Enterprise Systems on Organizational Agility

ERIC Educational Resources Information Center

Kharabe, Amol T.

2012-01-01

Over the last two decades, firms have operated in "increasingly" accelerated "high-velocity" dynamic markets, which require them to become "agile." During the same time frame, firms have increasingly deployed complex enterprise systems--large-scale packaged software "innovations" that integrate and automate…

Custom software development for use in a clinical laboratory

PubMed Central

Sinard, John H.; Gershkovich, Peter

2012-01-01

In-house software development for use in a clinical laboratory is a controversial issue. Many of the objections raised are based on outdated software development practices, an exaggeration of the risks involved, and an underestimation of the benefits that can be realized. Buy versus build analyses typically do not consider total costs of ownership, and unfortunately decisions are often made by people who are not directly affected by the workflow obstacles or benefits that result from those decisions. We have been developing custom software for clinical use for over a decade, and this article presents our perspective on this practice. A complete analysis of the decision to develop or purchase must ultimately examine how the end result will mesh with the departmental workflow, and custom-developed solutions typically can have the greater positive impact on efficiency and productivity, substantially altering the decision balance sheet. Involving the end-users in preparation of the functional specifications is crucial to the success of the process. A large development team is not needed, and even a single programmer can develop significant solutions. Many of the risks associated with custom development can be mitigated by a well-structured development process, use of open-source tools, and embracing an agile development philosophy. In-house solutions have the significant advantage of being adaptable to changing departmental needs, contributing to efficient and higher quality patient care. PMID:23372985

Custom software development for use in a clinical laboratory.

PubMed

Sinard, John H; Gershkovich, Peter

2012-01-01

In-house software development for use in a clinical laboratory is a controversial issue. Many of the objections raised are based on outdated software development practices, an exaggeration of the risks involved, and an underestimation of the benefits that can be realized. Buy versus build analyses typically do not consider total costs of ownership, and unfortunately decisions are often made by people who are not directly affected by the workflow obstacles or benefits that result from those decisions. We have been developing custom software for clinical use for over a decade, and this article presents our perspective on this practice. A complete analysis of the decision to develop or purchase must ultimately examine how the end result will mesh with the departmental workflow, and custom-developed solutions typically can have the greater positive impact on efficiency and productivity, substantially altering the decision balance sheet. Involving the end-users in preparation of the functional specifications is crucial to the success of the process. A large development team is not needed, and even a single programmer can develop significant solutions. Many of the risks associated with custom development can be mitigated by a well-structured development process, use of open-source tools, and embracing an agile development philosophy. In-house solutions have the significant advantage of being adaptable to changing departmental needs, contributing to efficient and higher quality patient care.

Agile Metrics: Progress Monitoring of Agile Contractors

DTIC Science & Technology

2014-01-01

epic. The short timeframe is usually called an itera- tion or, in Scrum -based teams, a sprint; multiple iterations make up a release [Lapham 2011...9769 [Rawsthorne 2012] Rawsthorne, Dan. Monitoring Scrum Projects with AgileEVM and Earned Business Value Metrics (EBV). 2012. http...AgileEVM – Earned Value Manage- ment in Scrum Projects.” Presented at Agile2006, 23-28 July 2006. [USAF 2008] United States Air Force. United

An Integrated Toolset for Agile Systems Engineering Requirements Analysis

DTIC Science & Technology

2011-05-19

Tool STDUse Cases Collaboration Tool Data Mgmt T l 1 e a a managemen oo Run the test in the test lab, redline the STD Update the collaboration...Boeing Defense, Space & Security Lean-Agile Software A I t t d T l t fn n egra e oo se or Agile Systems Engineering Requirements Analysis Phyllis...Regulations (ITAR) and the Export Administration R l ti (EAR) h i l bl b t h th i th BOEING is a trademark of Boeing Management Company. Copyright © 2010

Self-service for software development projects and HPC activities

NASA Astrophysics Data System (ADS)

Husejko, M.; Høimyr, N.; Gonzalez, A.; Koloventzos, G.; Asbury, D.; Trzcinska, A.; Agtzidis, I.; Botrel, G.; Otto, J.

2014-05-01

This contribution describes how CERN has implemented several essential tools for agile software development processes, ranging from version control (Git) to issue tracking (Jira) and documentation (Wikis). Running such services in a large organisation like CERN requires many administrative actions both by users and service providers, such as creating software projects, managing access rights, users and groups, and performing tool-specific customisation. Dealing with these requests manually would be a time-consuming task. Another area of our CERN computing services that has required dedicated manual support has been clusters for specific user communities with special needs. Our aim is to move all our services to a layered approach, with server infrastructure running on the internal cloud computing infrastructure at CERN. This contribution illustrates how we plan to optimise the management of our of services by means of an end-user facing platform acting as a portal into all the related services for software projects, inspired by popular portals for open-source developments such as Sourceforge, GitHub and others. Furthermore, the contribution will discuss recent activities with tests and evaluations of High Performance Computing (HPC) applications on different hardware and software stacks, and plans to offer a dynamically scalable HPC service at CERN, based on affordable hardware.

Contracting for Agile Software Development in the Department of Defense: An Introduction

DTIC Science & Technology

2015-08-01

Requirements are fixed at a more granular level; reviews of the work product happen more frequently and assess each individual increment rather than a “ big bang ...boundaries than “ big - bang ” development. The implementation of incremental or progressive reviews enables just that—any issues identified at the time of the...the contract needs to support the delivery of deployable software at defined increments/intervals, rather than incentivizing “ big - bang ” efforts or

Considerations for Using Agile in DoD Acquisition

DTIC Science & Technology

2010-04-01

successfully used in manufacturing throughout the world for decades, such as ―just-in- time,‖ Lean, Kanban , and work-flow-based planning. Another new...of this analysis is provided in Table 2. 29 Kanban / lean style of Agile might be the most relevant for this phase. 31 | CMU/SEI-2010-TN-002...family of approaches, including Kanban [14], Rational Unified Process (RUP), Personal Software Process (PSP), Team Software Process (TSP), and Cleanroom

Frequency-agile wireless sensor networks

NASA Astrophysics Data System (ADS)

Arms, Steven W.; Townsend, Christopher P.; Churchill, David L.; Hamel, Michael J.; Galbreath, Jacob H.; Mundell, Steven W.

2004-07-01

Our goal was to demonstrate a wireless communications system capable of simultaneous, high speed data communications from a variety of sensors. We have previously reported on the design and application of 2 KHz data logging transceiver nodes, however, only one node may stream data at a time, since all nodes on the network use the same communications frequency. To overcome these limitations, second generation data logging transceivers were developed with software programmable radio frequency (RF) communications. Each node contains on-board memory (2 Mbytes), sensor excitation, instrumentation amplifiers with programmable gains & offsets, multiplexer, 16 bit A/D converter, microcontroller, and frequency agile, bi-directional, frequency shift keyed (FSK) RF serial data link. These systems are capable of continuous data transmission from 26 distinct nodes (902-928 MHz band, 75 kbaud). The system was demonstrated in a compelling structural monitoring application. The National Parks Service requested a means for continual monitoring and recording of sensor data from the Liberty Bell during a move to a new location (Philadelphia, October 2003). Three distinct, frequency agile, wireless sensing nodes were used to detect visible crack shear/opening micromotions, triaxial accelerations, and hairline crack tip strains. The wireless sensors proved to be useful in protecting the Liberty Bell.

Agile parallel bioinformatics workflow management using Pwrake.

PubMed

Mishima, Hiroyuki; Sasaki, Kensaku; Tanaka, Masahiro; Tatebe, Osamu; Yoshiura, Koh-Ichiro

2011-09-08

In bioinformatics projects, scientific workflow systems are widely used to manage computational procedures. Full-featured workflow systems have been proposed to fulfil the demand for workflow management. However, such systems tend to be over-weighted for actual bioinformatics practices. We realize that quick deployment of cutting-edge software implementing advanced algorithms and data formats, and continuous adaptation to changes in computational resources and the environment are often prioritized in scientific workflow management. These features have a greater affinity with the agile software development method through iterative development phases after trial and error.Here, we show the application of a scientific workflow system Pwrake to bioinformatics workflows. Pwrake is a parallel workflow extension of Ruby's standard build tool Rake, the flexibility of which has been demonstrated in the astronomy domain. Therefore, we hypothesize that Pwrake also has advantages in actual bioinformatics workflows. We implemented the Pwrake workflows to process next generation sequencing data using the Genomic Analysis Toolkit (GATK) and Dindel. GATK and Dindel workflows are typical examples of sequential and parallel workflows, respectively. We found that in practice, actual scientific workflow development iterates over two phases, the workflow definition phase and the parameter adjustment phase. We introduced separate workflow definitions to help focus on each of the two developmental phases, as well as helper methods to simplify the descriptions. This approach increased iterative development efficiency. Moreover, we implemented combined workflows to demonstrate modularity of the GATK and Dindel workflows. Pwrake enables agile management of scientific workflows in the bioinformatics domain. The internal domain specific language design built on Ruby gives the flexibility of rakefiles for writing scientific workflows. Furthermore, readability and maintainability of rakefiles

Agile parallel bioinformatics workflow management using Pwrake

PubMed Central

2011-01-01

Background In bioinformatics projects, scientific workflow systems are widely used to manage computational procedures. Full-featured workflow systems have been proposed to fulfil the demand for workflow management. However, such systems tend to be over-weighted for actual bioinformatics practices. We realize that quick deployment of cutting-edge software implementing advanced algorithms and data formats, and continuous adaptation to changes in computational resources and the environment are often prioritized in scientific workflow management. These features have a greater affinity with the agile software development method through iterative development phases after trial and error. Here, we show the application of a scientific workflow system Pwrake to bioinformatics workflows. Pwrake is a parallel workflow extension of Ruby's standard build tool Rake, the flexibility of which has been demonstrated in the astronomy domain. Therefore, we hypothesize that Pwrake also has advantages in actual bioinformatics workflows. Findings We implemented the Pwrake workflows to process next generation sequencing data using the Genomic Analysis Toolkit (GATK) and Dindel. GATK and Dindel workflows are typical examples of sequential and parallel workflows, respectively. We found that in practice, actual scientific workflow development iterates over two phases, the workflow definition phase and the parameter adjustment phase. We introduced separate workflow definitions to help focus on each of the two developmental phases, as well as helper methods to simplify the descriptions. This approach increased iterative development efficiency. Moreover, we implemented combined workflows to demonstrate modularity of the GATK and Dindel workflows. Conclusions Pwrake enables agile management of scientific workflows in the bioinformatics domain. The internal domain specific language design built on Ruby gives the flexibility of rakefiles for writing scientific workflows. Furthermore, readability

Architecting for Sustainable Software Delivery

DTIC Science & Technology

2012-06-01

14 CrossTalk—May/June 2012 RAPID AND AGILE STABILITY Architecting for Sustainable Software Delivery Ronald J. Koontz , Boeing Robert L. Nord...Figure 2, and additional architecture documentation can be found in the work of Koontz [9, 10, 11]. Designing for extensibility promotes continued...Mapping of Practices to Agile and Architecture Criteria CrossTalk—May/June 2012 19 RAPID AND AGILE STABILITY ABOUT THE AUTHORS Ronald J. Koontz

Spacecraft Avionics Software Development Then and Now: Different but the Same

NASA Technical Reports Server (NTRS)

Mangieri, Mark L.; Garman, John (Jack); Vice, Jason

2012-01-01

NASA has always been in the business of balancing new technologies and techniques to achieve human space travel objectives. NASA s historic Software Production Facility (SPF) was developed to serve complex avionics software solutions during an era dominated by mainframes, tape drives, and lower level programming languages. These systems have proven themselves resilient enough to serve the Shuttle Orbiter Avionics life cycle for decades. The SPF and its predecessor the Software Development Lab (SDL) at NASA s Johnson Space Center (JSC) hosted flight software (FSW) engineering, development, simulation, and test. It was active from the beginning of Shuttle Orbiter development in 1972 through the end of the shuttle program in the summer of 2011 almost 40 years. NASA s Kedalion engineering analysis lab is on the forefront of validating and using many contemporary avionics HW/SW development and integration techniques, which represent new paradigms to NASA s heritage culture in avionics software engineering. Kedalion has validated many of the Orion project s HW/SW engineering techniques borrowed from the adjacent commercial aircraft avionics environment, inserting new techniques and skills into the Multi-Purpose Crew Vehicle (MPCV) Orion program. Using contemporary agile techniques, COTS products, early rapid prototyping, in-house expertise and tools, and customer collaboration, NASA has adopted a cost effective paradigm that is currently serving Orion effectively. This paper will explore and contrast differences in technology employed over the years of NASA s space program, due largely to technological advances in hardware and software systems, while acknowledging that the basic software engineering and integration paradigms share many similarities.

Tailoring Agility: Promiscuous Pair Story Authoring and Value Calculation

NASA Astrophysics Data System (ADS)

Tendon, Steve

This chapter describes how a multi-national software organization created a business plan involving business units from eight countries that followed an agile way, after two previously failed attempts with traditional approaches. The case is told by the consultant who initiated implementation of agility into requirements gathering, estimation and planning processes in an international setting. The agile approach was inspired by XP, but then tailored to meet the peculiar requirements. Two innovations were critical. The first innovation was promiscuous pair story authoring, where user stories were written by two people (similarly to pair programming), and the pairing changed very often (as frequently as every 15-20 minutes) to achieve promiscuity and cater for diverse point of views. The second innovation was an economic value evaluation (and not the cost) which was attributed to stories. Continuous recalculation of the financial value of the stories allowed to assess the projects financial return. In this case implementation of agility in the international context allowed the involved team members to reach consensus and unanimity of decisions, vision and purpose.

Developing a model for agile supply: an empirical study from Iranian pharmaceutical supply chain.

PubMed

Rajabzadeh Ghatari, Ali; Mehralian, Gholamhossein; Zarenezhad, Forouzandeh; Rasekh, Hamid Reza

2013-01-01

Agility is the fundamental characteristic of a supply chain needed for survival in turbulent markets, where environmental forces create additional uncertainty resulting in higher risk in the supply chain management. In addition, agility helps providing the right product, at the right time to the consumer. The main goal of this research is therefore to promote supplier selection in pharmaceutical industry according to the formative basic factors. Moreover, this paper can configure its supply network to achieve the agile supply chain. The present article analyzes the supply part of supply chain based on SCOR model, used to assess agile supply chains by highlighting their specific characteristics and applicability in providing the active pharmaceutical ingredient (API). This methodology provides an analytical modeling; the model enables potential suppliers to be assessed against the multiple criteria using both quantitative and qualitative measures. In addition, for making priority of critical factors, TOPSIS algorithm has been used as a common technique of MADM model. Finally, several factors such as delivery speed, planning and reorder segmentation, trust development and material quantity adjustment are identified and prioritized as critical factors for being agile in supply of API.

Developing a Model for Agile Supply: an Empirical Study from Iranian Pharmaceutical Supply Chain

PubMed Central

Rajabzadeh Ghatari, Ali; Mehralian, Gholamhossein; Zarenezhad, Forouzandeh; Rasekh, Hamid Reza

2013-01-01

Agility is the fundamental characteristic of a supply chain needed for survival in turbulent markets, where environmental forces create additional uncertainty resulting in higher risk in the supply chain management. In addition, agility helps providing the right product, at the right time to the consumer. The main goal of this research is therefore to promote supplier selection in pharmaceutical industry according to the formative basic factors. Moreover, this paper can configure its supply network to achieve the agile supply chain. The present article analyzes the supply part of supply chain based on SCOR model, used to assess agile supply chains by highlighting their specific characteristics and applicability in providing the active pharmaceutical ingredient (API). This methodology provides an analytical modeling; the model enables potential suppliers to be assessed against the multiple criteria using both quantitative and qualitative measures. In addition, for making priority of critical factors, TOPSIS algorithm has been used as a common technique of MADM model. Finally, several factors such as delivery speed, planning and reorder segmentation, trust development and material quantity adjustment are identified and prioritized as critical factors for being agile in supply of API. PMID:24250689

Proposing an Evidence-Based Strategy for Software Requirements Engineering.

PubMed

Lindoerfer, Doris; Mansmann, Ulrich

2016-01-01

This paper discusses an evidence-based approach to software requirements engineering. The approach is called evidence-based, since it uses publications on the specific problem as a surrogate for stakeholder interests, to formulate risks and testing experiences. This complements the idea that agile software development models are more relevant, in which requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The strategy is exemplified and applied to the development of a Software Requirements list used to develop software systems for patient registries.

Fostering Soft Skills in Project-Oriented Learning within an Agile Atmosphere

ERIC Educational Resources Information Center

Chassidim, Hadas; Almog, Dani; Mark, Shlomo

2018-01-01

The project-oriented and Agile approaches have motivated a new generation of software engineers. Within the academic curriculum, the issue of whether students are being sufficiently prepared for the future has been raised. The objective of this work is to present the project-oriented environment as an influential factor that software engineering…

Reactive Agility Performance in Handball; Development and Evaluation of a Sport-Specific Measurement Protocol

PubMed Central

Spasic, Miodrag; Krolo, Ante; Zenic, Natasa; Delextrat, Anne; Sekulic, Damir

2015-01-01

There is no current study that examined sport-specific tests of reactive-agility and change-of-direction-speed (CODS) to replicate real-sport environment in handball (team-handball). This investigation evaluated the reliability and validity of two novel tests designed to assess reactive-agility and CODS of handball players. Participants were female (25.14 ± 3.71 years of age; 1.77 ± 0.09 m and 74.1 ± 6.1 kg) and male handball players (26.9 ± 4.1 years of age; 1.90 ± 0.09 m and 93.90±4.6 kg). Variables included body height, body mass, body mass index, broad jump, 5-m sprint, CODS and reactive-agility tests. Results showed satisfactory reliability for reactive-agility-test and CODS-test (ICC of 0.85-0.93, and CV of 2.4-4.8%). The reactive-agility and CODS shared less than 20% of the common variance. The calculated index of perceptual and reactive capacity (P&RC; ratio between reactive-agility- and CODS-performance) is found to be valid measure in defining true-game reactive-agility performance in handball in both genders. Therefore, the handball athletes’ P&RC should be used in the evaluation of real-game reactive-agility performance. Future studies should explore other sport-specific reactive-agility tests and factors associated to such performance in sports involving agile maneuvers. Key points Reactive agility and change-of-direction-speed should be observed as independent qualities, even when tested over the same course and similar movement template The reactive-agility-performance of the handball athletes involved in defensive duties is closer to their non-reactive-agility-score than in their peers who are not involved in defensive duties The handball specific “true-game” reactive-agility-performance should be evaluated as the ratio between reactive-agility and corresponding CODS performance. PMID:26336335

Reactive Agility Performance in Handball; Development and Evaluation of a Sport-Specific Measurement Protocol.

PubMed

Spasic, Miodrag; Krolo, Ante; Zenic, Natasa; Delextrat, Anne; Sekulic, Damir

2015-09-01

There is no current study that examined sport-specific tests of reactive-agility and change-of-direction-speed (CODS) to replicate real-sport environment in handball (team-handball). This investigation evaluated the reliability and validity of two novel tests designed to assess reactive-agility and CODS of handball players. Participants were female (25.14 ± 3.71 years of age; 1.77 ± 0.09 m and 74.1 ± 6.1 kg) and male handball players (26.9 ± 4.1 years of age; 1.90 ± 0.09 m and 93.90±4.6 kg). Variables included body height, body mass, body mass index, broad jump, 5-m sprint, CODS and reactive-agility tests. Results showed satisfactory reliability for reactive-agility-test and CODS-test (ICC of 0.85-0.93, and CV of 2.4-4.8%). The reactive-agility and CODS shared less than 20% of the common variance. The calculated index of perceptual and reactive capacity (P&RC; ratio between reactive-agility- and CODS-performance) is found to be valid measure in defining true-game reactive-agility performance in handball in both genders. Therefore, the handball athletes' P&RC should be used in the evaluation of real-game reactive-agility performance. Future studies should explore other sport-specific reactive-agility tests and factors associated to such performance in sports involving agile maneuvers. Key pointsReactive agility and change-of-direction-speed should be observed as independent qualities, even when tested over the same course and similar movement templateThe reactive-agility-performance of the handball athletes involved in defensive duties is closer to their non-reactive-agility-score than in their peers who are not involved in defensive dutiesThe handball specific "true-game" reactive-agility-performance should be evaluated as the ratio between reactive-agility and corresponding CODS performance.

Evaluation of Basketball-Specific Agility: Applicability of Preplanned and Nonplanned Agility Performances for Differentiating Playing Positions and Playing Levels.

PubMed

Sekulic, Damir; Pehar, Miran; Krolo, Ante; Spasic, Miodrag; Uljevic, Ognjen; Calleja-González, Julio; Sattler, Tine

2017-08-01

Sekulic, D, Pehar, M, Krolo, A, Spasic, M, Uljevic, O, Calleja-González, J, and Sattler, T. Evaluation of basketball-specific agility: applicability of preplanned and nonplanned agility performances for differentiating playing positions and playing levels. J Strength Cond Res 31(8): 2278-2288, 2017-The importance of agility in basketball is well known, but there is an evident lack of studies examining basketball-specific agility performances in high-level players. The aim of this study was to determine the reliability and discriminative validity of 1 standard agility test (test of preplanned agility [change-of-direction speed] over T course, T-TEST), and 4 newly developed basketball-specific agility tests, in defining playing positions and performance levels in basketball. The study comprised 110 high-level male basketball players (height: 194.92 ± 8.09 cm; body mass: 89.33 ± 10.91 kg; age: 21.58 ± 3.92 years). The variables included playing position (Guard, Forward, Center), performance level (first division vs. second division), anthropometrics (body height, body mass, and percentage of body fat), T-TEST, nonplanned basketball agility test performed on dominant (BBAGILdom) and nondominant sides (BBAGILnond), and a preplanned (change-of-direction speed) basketball agility test performed on dominant (BBCODSdom) and nondominant sides (BBCODSnond). The reliability of agility tests was high (intraclass correlation coefficient of 0.81-0.95). Forwards were most successful in the T-TEST (F test: 13.57; p = 0.01). Guards outperformed Centers in BBCODSdom, BBCODSndom, BBAGILdom, and BBAGILnond (F test: 5.06, p = 0.01; 6.57, 0.01; 6.26, 0.01; 3.37, 0.04, respectively). First division Guards achieved better results than second division Guards in BBCODSdom (t: 2.55; p = 0.02; moderate effect size differences), BBAGILdom, and BBAGILnond (t: 3.04 and 3.06, respectively; both p = 0.01 and moderate effect size differences). First division Centers outperformed second division

Potential Use of Agile Methods in Selected DoD Acquisitions: Requirements Development and Management

DTIC Science & Technology

2014-04-01

understanding of common Agile meth- ods, particularly Scrum and eXtreme Programming. For those unfamiliar with the basics of Agile development, the... Scrum (namely, the concepts of product owner, product backlog and self- organized teams) and eXtreme Programming (epics and user stories). These concepts...also been adopted as a requirements specification mechanism by many teams using Scrum , even if those teams don’t use other aspects of eXtreme

Some Findings Concerning Requirements in Agile Methodologies

NASA Astrophysics Data System (ADS)

Rodríguez, Pilar; Yagüe, Agustín; Alarcón, Pedro P.; Garbajosa, Juan

Agile methods have appeared as an attractive alternative to conventional methodologies. These methods try to reduce the time to market and, indirectly, the cost of the product through flexible development and deep customer involvement. The processes related to requirements have been extensively studied in literature, in most cases in the frame of conventional methods. However, conclusions of conventional methodologies could not be necessarily valid for Agile; in some issues, conventional and Agile processes are radically different. As recent surveys report, inadequate project requirements is one of the most conflictive issues in agile approaches and better understanding about this is needed. This paper describes some findings concerning requirements activities in a project developed under an agile methodology. The project intended to evolve an existing product and, therefore, some background information was available. The major difficulties encountered were related to non-functional needs and management of requirements dependencies.

EDGE3: A web-based solution for management and analysis of Agilent two color microarray experiments

PubMed Central

Vollrath, Aaron L; Smith, Adam A; Craven, Mark; Bradfield, Christopher A

2009-01-01

Background The ability to generate transcriptional data on the scale of entire genomes has been a boon both in the improvement of biological understanding and in the amount of data generated. The latter, the amount of data generated, has implications when it comes to effective storage, analysis and sharing of these data. A number of software tools have been developed to store, analyze, and share microarray data. However, a majority of these tools do not offer all of these features nor do they specifically target the commonly used two color Agilent DNA microarray platform. Thus, the motivating factor for the development of EDGE3 was to incorporate the storage, analysis and sharing of microarray data in a manner that would provide a means for research groups to collaborate on Agilent-based microarray experiments without a large investment in software-related expenditures or extensive training of end-users. Results EDGE3 has been developed with two major functions in mind. The first function is to provide a workflow process for the generation of microarray data by a research laboratory or a microarray facility. The second is to store, analyze, and share microarray data in a manner that doesn't require complicated software. To satisfy the first function, EDGE3 has been developed as a means to establish a well defined experimental workflow and information system for microarray generation. To satisfy the second function, the software application utilized as the user interface of EDGE3 is a web browser. Within the web browser, a user is able to access the entire functionality, including, but not limited to, the ability to perform a number of bioinformatics based analyses, collaborate between research groups through a user-based security model, and access to the raw data files and quality control files generated by the software used to extract the signals from an array image. Conclusion Here, we present EDGE3, an open-source, web-based application that allows for the

EDGE(3): a web-based solution for management and analysis of Agilent two color microarray experiments.

PubMed

Vollrath, Aaron L; Smith, Adam A; Craven, Mark; Bradfield, Christopher A

2009-09-04

The ability to generate transcriptional data on the scale of entire genomes has been a boon both in the improvement of biological understanding and in the amount of data generated. The latter, the amount of data generated, has implications when it comes to effective storage, analysis and sharing of these data. A number of software tools have been developed to store, analyze, and share microarray data. However, a majority of these tools do not offer all of these features nor do they specifically target the commonly used two color Agilent DNA microarray platform. Thus, the motivating factor for the development of EDGE(3) was to incorporate the storage, analysis and sharing of microarray data in a manner that would provide a means for research groups to collaborate on Agilent-based microarray experiments without a large investment in software-related expenditures or extensive training of end-users. EDGE(3) has been developed with two major functions in mind. The first function is to provide a workflow process for the generation of microarray data by a research laboratory or a microarray facility. The second is to store, analyze, and share microarray data in a manner that doesn't require complicated software. To satisfy the first function, EDGE3 has been developed as a means to establish a well defined experimental workflow and information system for microarray generation. To satisfy the second function, the software application utilized as the user interface of EDGE(3) is a web browser. Within the web browser, a user is able to access the entire functionality, including, but not limited to, the ability to perform a number of bioinformatics based analyses, collaborate between research groups through a user-based security model, and access to the raw data files and quality control files generated by the software used to extract the signals from an array image. Here, we present EDGE(3), an open-source, web-based application that allows for the storage, analysis, and

Investigating the strategic antecedents of agility in humanitarian logistics.

PubMed

L'Hermitte, Cécile; Brooks, Benjamin; Bowles, Marcus; Tatham, Peter H

2017-10-01

This study investigates the strategic antecedents of operational agility in humanitarian logistics. It began by identifying the particular actions to be taken at the strategic level of a humanitarian organisation to support field-level agility. Next, quantitative data (n=59) were collected on four strategic-level capabilities (being purposeful, action-focused, collaborative, and learning-oriented) and on operational agility (field responsiveness and flexibility). Using a quantitative analysis, the study tested the relationship between organisational capacity building and operational agility and found that the four strategic-level capabilities are fundamental building blocks of agility. Collectively they account for 52 per cent of the ability of humanitarian logisticians to deal with ongoing changes and disruptions in the field. This study emphasises the need for researchers and practitioners to embrace a broader perspective of agility in humanitarian logistics. In addition, it highlights the inherently strategic nature of agility, the development of which involves focusing simultaneously on multiple drivers. © 2017 The Author(s). Disasters © Overseas Development Institute, 2017.

Fighter agility metrics, research, and test

NASA Technical Reports Server (NTRS)

Liefer, Randall K.; Valasek, John; Eggold, David P.

1990-01-01

Proposed new metrics to assess fighter aircraft agility are collected and analyzed. A framework for classification of these new agility metrics is developed and applied. A completed set of transient agility metrics is evaluated with a high fidelity, nonlinear F-18 simulation provided by the NASA Dryden Flight Research Center. Test techniques and data reduction methods are proposed. A method of providing cuing information to the pilot during flight test is discussed. The sensitivity of longitudinal and lateral agility metrics to deviations from the pilot cues is studied in detail. The metrics are shown to be largely insensitive to reasonable deviations from the nominal test pilot commands. Instrumentation required to quantify agility via flight test is also considered. With one exception, each of the proposed new metrics may be measured with instrumentation currently available. Simulation documentation and user instructions are provided in an appendix.

Development strategies for the satellite flight software on-board Meteosat Third Generation

NASA Astrophysics Data System (ADS)

Tipaldi, Massimo; Legendre, Cedric; Koopmann, Olliver; Ferraguto, Massimo; Wenker, Ralf; D'Angelo, Gianni

2018-04-01

Nowadays, satellites are becoming increasingly software dependent. Satellite Flight Software (FSW), that is to say, the application software running on the satellite main On-Board Computer (OBC), plays a relevant role in implementing complex space mission requirements. In this paper, we examine relevant technical approaches and programmatic strategies adopted for the development of the Meteosat Third Generation Satellite (MTG) FSW. To begin with, we present its layered model-based architecture, and the means for ensuring a robust and reliable interaction among the FSW components. Then, we focus on the selection of an effective software development life cycle model. In particular, by combining plan-driven and agile approaches, we can fulfill the need of having preliminary SW versions. They can be used for the elicitation of complex system-level requirements as well as for the initial satellite integration and testing activities. Another important aspect can be identified in the testing activities. Indeed, very demanding quality requirements have to be fulfilled in satellite SW applications. This manuscript proposes a test automation framework, which uses an XML-based test procedure language independent of the underlying test environment. Finally, a short overview of the MTG FSW sizing and timing budgets concludes the paper.

The Paving Stones: initial feed-back on an attempt to apply the AGILE principles for the development of a CubeSat space mission to Mars

NASA Astrophysics Data System (ADS)

Segret, Boris; Semery, Alain; Vannitsen, Jordan; Mosser, Benoît.; Miau, Jiun-Jih; Juang, Jyh-Ching; Deleflie, Florent

2014-08-01

The AGILE principles in the software industry seems well adapted to the paradigm of CubeSat missions that involve students for the development of space missions. Some of well-known engineering and program processes are revisited on the example of an interplanetary CubeSat mission profile that has been developed by several teams of students in various countries and at various educational levels since 02/2013. The lessons learned at adapting traditional space mission methods are emphasized and they produce a metaphoric image of paving stones.

Examination of the perceived agility and balance during a reactive agility task.

PubMed

Stirling, Leia; Eke, Chika; Cain, Stephen M

2018-01-01

In vehicle dynamics, it is commonly understood that there is an inverse relationship between stability and maneuverability. However, animal studies have found that stability and maneuverability can coincide. In this study, we examine humans running a reactive agility obstacle and consider the relationship between observational perceived agility and balance, as well as the relationship between quantified surrogates of agility and balance. Recreational athletes (n = 18) completed the agility task while wearing inertial measurement units (IMUs) on their body. The task was also video-recorded. An observational study was completed by a separate group of adults (n = 33) that were asked to view the videos and score each athlete on a Likert scale for balance and for agility. The data from the body-worn IMUs were used to estimate quantified surrogate measures for agility and balance, and to assess if the relationship between the quantified agility and balance was in the same direction as the perceived relationship from the Likert scale responses. Results indicate that athletes that were given a higher Likert agility score were also given a higher balance score (rs = 0.75,p < 0.001). Quantitative surrogates of agility and balance also showed this same relationship. Additional insights on technique for this reactive agility task were informed by the quantitative surrogates. We observed the importance of stepping technique in achieving the faster completion times. The fast performing athletes spent a greater proportion of the task in double support and lower overall time in single support indicating increased periods of static stability. The fast performing athletes did not have a higher body speed, but performed the task with a more efficient technique, using foot placement to enable heading changes, and thus may have had a more efficient path. Similar to animal studies, people use technique to enable agile strategies while also enabling increased balance across the task.

Agile Data Curation: A conceptual framework and approach for practitioner data management

NASA Astrophysics Data System (ADS)

Young, J. W.; Benedict, K. K.; Lenhardt, W. C.

2015-12-01

Data management occurs across a range of science and related activities such as decision-support. Exemplars within the science community operate data management systems that are extensively planned before implementation, staffed with robust data management expertise, equipped with appropriate services and technologies, and often highly structured. However, this is not the only approach to data management and almost certainly not the typical experience. The other end of the spectrum is often an ad hoc practitioner team, with changing requirements, limited training in data management, and resource constrained for both equipment and human resources. Much of the existing data management literature serves the exemplar community and ignores the ad hoc practitioners. Somewhere in the middle are examples where data are repurposed for new uses thereby generating new data management challenges. This submission presents a conceptualization of an Agile Data Curation approach that provides foundational principles for data management efforts operating across the spectrum of data generation and use from large science systems to efforts with constrained resources, limited expertise, and evolving requirements. The underlying principles to Agile Data Curation are a reapplication of agile software development principles to data management. The historical reality for many data management efforts is operating in a practioner environment so Agile Data Curation utilizes historical and current case studies to validate the foundational principles and through comparison learn lessons for future application. This submission will provide an overview of the Agile Data Curation, cover the foundational principles to the approach, and introduce a framework for gathering, classifying, and applying lessons from case studies of practitioner data management.

An Examination of an Information Security Framework Implementation Based on Agile Values to Achieve Health Insurance Portability and Accountability Act Security Rule Compliance in an Academic Medical Center: The Thomas Jefferson University Case Study

ERIC Educational Resources Information Center

Reis, David W.

2012-01-01

Agile project management is most often examined in relation to software development, while information security frameworks are often examined with respect to certain risk management capabilities rather than in terms of successful implementation approaches. This dissertation extended the study of both Agile project management and information…

Development of perceived competence, tactical skills, motivation, technical skills, and speed and agility in young soccer players.

PubMed

Forsman, Hannele; Gråstén, Arto; Blomqvist, Minna; Davids, Keith; Liukkonen, Jarmo; Konttinen, Niilo

2016-07-01

The objective of this 1-year, longitudinal study was to examine the development of perceived competence, tactical skills, motivation, technical skills, and speed and agility characteristics of young Finnish soccer players. We also examined associations between latent growth models of perceived competence and other recorded variables. Participants were 288 competitive male soccer players ranging from 12 to 14 years (12.7 ± 0.6) from 16 soccer clubs. Players completed the self-assessments of perceived competence, tactical skills, and motivation, and participated in technical, and speed and agility tests. Results of this study showed that players' levels of perceived competence, tactical skills, motivation, technical skills, and speed and agility characteristics remained relatively high and stable across the period of 1 year. Positive relationships were found between these levels and changes in perceived competence and motivation, and levels of perceived competence and speed and agility characteristics. Together these results illustrate the multi-dimensional nature of talent development processes in soccer. Moreover, it seems crucial in coaching to support the development of perceived competence and motivation in young soccer players and that it might be even more important in later maturing players.

Effect of Exercise Program Speed, Agility, and Quickness (SAQ) in Improving Speed, Agility, and Acceleration

NASA Astrophysics Data System (ADS)

Azmi, K.; Kusnanik, N. W.

2018-01-01

This study aimed to analyze the effect of speed, agility and quickness training program to increase in speed, agility and acceleration. This study was conducted at 26 soccer players and divided into 2 groups with 13 players each group. Group 1 was given SAQ training program, and Group 2 conventional training program for 8 weeks. This study used a quantitative approach with quasi-experimental method. The design of this study used a matching-only design. Data was collected by testing 30-meter sprint (speed), agility t-test (agility), and run 10 meters (acceleration) during the pretest and posttest. Furthermore, the data was analyzed using paired sample t-test and independent t-test. The results showed: that there was a significant effect of speed, agility and quickness training program in improving in speed, agility and acceleration. In summary, it can be concluded that the speed, agility and quickness training program can improve the speed, agility and acceleration of the soccer players.

An investigation of fighter aircraft agility

NASA Technical Reports Server (NTRS)

Valasek, John; Downing, David R.

1993-01-01

This report attempts to unify in a single document the results of a series of studies on fighter aircraft agility funded by the NASA Ames Research Center, Dryden Flight Research Facility and conducted at the University of Kansas Flight Research Laboratory during the period January 1989 through December 1993. New metrics proposed by pilots and the research community to assess fighter aircraft agility are collected and analyzed. The report develops a framework for understanding the context into which the various proposed fighter agility metrics fit in terms of application and testing. Since new metrics continue to be proposed, this report does not claim to contain every proposed fighter agility metric. Flight test procedures, test constraints, and related criteria are developed. Instrumentation required to quantify agility via flight test is considered, as is the sensitivity of the candidate metrics to deviations from nominal pilot command inputs, which is studied in detail. Instead of supplying specific, detailed conclusions about the relevance or utility of one candidate metric versus another, the authors have attempted to provide sufficient data and analyses for readers to formulate their own conclusions. Readers are therefore ultimately responsible for judging exactly which metrics are 'best' for their particular needs. Additionally, it is not the intent of the authors to suggest combat tactics or other actual operational uses of the results and data in this report. This has been left up to the user community. Twenty of the candidate agility metrics were selected for evaluation with high fidelity, nonlinear, non real-time flight simulation computer programs of the F-5A Freedom Fighter, F-16A Fighting Falcon, F-18A Hornet, and X-29A. The information and data presented on the 20 candidate metrics which were evaluated will assist interested readers in conducting their own extensive investigations. The report provides a definition and analysis of each metric; details

Pervasive Agility and Agile Fires in Support of Decisive Action

DTIC Science & Technology

2012-03-29

Pervasive Agility and Agile Fires in Support of Decisive Action FORMAT: Civilian Research Project DATE: 29 March 2012 WORD COUNT : 12,599 PAGES: 54...will face, this pollenization may require creative measures, perhaps virtual or constructive scenarios. The National Training Center at Fort Irwin

Agile science: creating useful products for behavior change in the real world.

PubMed

Hekler, Eric B; Klasnja, Predrag; Riley, William T; Buman, Matthew P; Huberty, Jennifer; Rivera, Daniel E; Martin, Cesar A

2016-06-01

Evidence-based practice is important for behavioral interventions but there is debate on how best to support real-world behavior change. The purpose of this paper is to define products and a preliminary process for efficiently and adaptively creating and curating a knowledge base for behavior change for real-world implementation. We look to evidence-based practice suggestions and draw parallels to software development. We argue to target three products: (1) the smallest, meaningful, self-contained, and repurposable behavior change modules of an intervention; (2) "computational models" that define the interaction between modules, individuals, and context; and (3) "personalization" algorithms, which are decision rules for intervention adaptation. The "agile science" process includes a generation phase whereby contender operational definitions and constructs of the three products are created and assessed for feasibility and an evaluation phase, whereby effect size estimates/casual inferences are created. The process emphasizes early-and-often sharing. If correct, agile science could enable a more robust knowledge base for behavior change.

AIM - Agile Instrumented Monitoring for Improving User Experience of Participation in HealthIT Development.

PubMed

Pitkänen, Janne; Nieminen, Marko

2017-01-01

Participation of healthcare professionals in information technology development has emerged as an important challenge. As end-users, the professionals are willing to participate in the development activities, but their experiences on the current methods of participation remain mostly negative. There is lack of applicable methods for meeting the needs of agile development approach and scaling up to the largest implementation projects, while maintaining the interest of the professional users to participate in development activities and keeping up their ability to continue working in a productive manner. In this paper, we describe the Agile Instrumented Monitoring as a methodology, based on the methods of instrumented usability evaluation, for improving user experience in HealthIT development. The contribution of the proposed methodology is analyzed in relation to activities of whole iteration cycle and chosen usability evaluation methods, while the user experience of participation is addressed regarding healthcare professionals. Prospective weak and strong market tests for AIM are discussed in the conclusions for future work.

Agile Methods in Air Force Sustainment: Status and Outlook

DTIC Science & Technology

2014-07-01

Schwaber ISBN10: 073561993X X X Agile Project Management : Creating Innovative Products – 2nd Edition Jim Highsmith ISBN 0321658396 X Agile...ISBN 0787974277 X Leading Change John Kotter ISBN 0875847471 X Leading Geeks: How to Manage and Lead the People Who Deliver Technology Paul ...Development: Achieving Enterprise Agility Alan Shalloway, Guy Beaver, and James R. Trott ISBN 0321532899 X Managing Transitions: Making the Most of

Agile Mcal, the Mini-Calorimeter

NASA Astrophysics Data System (ADS)

Bastia, Paolo; Poulsen, Jens Michael; Monzani, Franco; Radaelli, Paolo; Marchesi, Paolo; Labanti, Claudio; Marisaldi, Martino; Fuschino, Fabio; Bulgarelli, Andrea

2006-04-01

AGILE is a scientific mission dedicated to gamma-ray astrophysics in space, and the mini-calorimeter MCAL is one of four detector systems on the satellite. The MCAL instrument is sensitive in the energy range: 300 keV - 100 MeV. It has two main functions: one autonomous mode for detection of impulsive cosmic events and the other as “a slave” supporting the energy measurements of the pair-conversion tracker. The AGILE Small Mission is funded by the Italian Space Agency (ASI), and the INAF-IASF section at Bologna has the scientific responsibility for MCAL. LABEN develops the MCAL instrument with its detectors and electronics. This paper gives an overview of the detectors on AGILE, and then it gives details on the design of MCAL, and finally we report on the tests at instrument level.

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.

Analysis and optimization of preliminary aircraft configurations in relationship to emerging agility metrics

NASA Technical Reports Server (NTRS)

Sandlin, Doral R.; Bauer, Brent Alan

1993-01-01

This paper discusses the development of a FORTRAN computer code to perform agility analysis on aircraft configurations. This code is to be part of the NASA-Ames ACSYNT (AirCraft SYNThesis) design code. This paper begins with a discussion of contemporary agility research in the aircraft industry and a survey of a few agility metrics. The methodology, techniques and models developed for the code are then presented. Finally, example trade studies using the agility module along with ACSYNT are illustrated. These trade studies were conducted using a Northrop F-20 Tigershark aircraft model. The studies show that the agility module is effective in analyzing the influence of common parameters such as thrust-to-weight ratio and wing loading on agility criteria. The module can compare the agility potential between different configurations. In addition one study illustrates the module's ability to optimize a configuration's agility performance.

Information Models, Data Requirements, and Agile Data Curation

NASA Astrophysics Data System (ADS)

Hughes, John S.; Crichton, Dan; Ritschel, Bernd; Hardman, Sean; Joyner, Ron

2015-04-01

The Planetary Data System's next generation system, PDS4, is an example of the successful use of an ontology-based Information Model (IM) to drive the development and operations of a data system. In traditional systems engineering, requirements or statements about what is necessary for the system are collected and analyzed for input into the design stage of systems development. With the advent of big data the requirements associated with data have begun to dominate and an ontology-based information model can be used to provide a formalized and rigorous set of data requirements. These requirements address not only the usual issues of data quantity, quality, and disposition but also data representation, integrity, provenance, context, and semantics. In addition the use of these data requirements during system's development has many characteristics of Agile Curation as proposed by Young et al. [Taking Another Look at the Data Management Life Cycle: Deconstruction, Agile, and Community, AGU 2014], namely adaptive planning, evolutionary development, early delivery, continuous improvement, and rapid and flexible response to change. For example customers can be satisfied through early and continuous delivery of system software and services that are configured directly from the information model. This presentation will describe the PDS4 architecture and its three principle parts: the ontology-based Information Model (IM), the federated registries and repositories, and the REST-based service layer for search, retrieval, and distribution. The development of the IM will be highlighted with special emphasis on knowledge acquisition, the impact of the IM on development and operations, and the use of shared ontologies at multiple governance levels to promote system interoperability and data correlation.

Agile Mythbusting

DTIC Science & Technology

2015-01-01

0321502752 Coaching Agile Teams Lyssa Adkins ISBN #0321637704 Agile Project Management : Creating Innovative Products – Second Edition Jim Highsmith ISBN...Picatinny Arsenal Lapham, Wrubel Jan 2015 © 2015 Carnegie Mellon University. DoD Acquisition and Innovation Many regulated environments, like the DoD...NEED innovation and NEED incremental improvements to their systems. Many of them are now willing to consider changing their approach if they can do it

Behavior driven testing in ALMA telescope calibration software

NASA Astrophysics Data System (ADS)

Gil, Juan P.; Garces, Mario; Broguiere, Dominique; Shen, Tzu-Chiang

2016-07-01

ALMA software development cycle includes well defined testing stages that involves developers, testers and scientists. We adapted Behavior Driven Development (BDD) to testing activities applied to Telescope Calibration (TELCAL) software. BDD is an agile technique that encourages communication between roles by defining test cases using natural language to specify features and scenarios, what allows participants to share a common language and provides a high level set of automated tests. This work describes how we implemented and maintain BDD testing for TELCAL, the infrastructure needed to support it and proposals to expand this technique to other subsystems.

SuperAGILE Services at ASDC

NASA Astrophysics Data System (ADS)

Preger, B.; Verrecchia, F.; Pittori, C.; Antonelli, L. A.; Giommi, P.; Lazzarotto, F.; Evangelista, Y.

2008-05-01

The Italian Space Agency Science Data Center (ASDC) is a facility with several responsibilities including support to all the ASI scientific missions as for management and archival of the data, acting as the interface between ASI and the scientific community and providing on-line access to the data hosted. In this poster we describe the services that ASDC provides for SuperAGILE, in particular the ASDC public web pages devoted to the dissemination of SuperAGILE scientific results. SuperAGILE is the X-Ray imager onboard the AGILE mission, and provides the scientific community with orbit-by-orbit information on the observed sources. Crucial source information including position and flux in chosen energy bands will be reported in the SuperAGILE public web page at ASDC. Given their particular interest, another web page will be dedicated entirely to GRBs and other transients, where new event alerts will be notified and where users will find all the available informations on the GRBs detected by SuperAGILE.

Elements of an Art - Agile Coaching

NASA Astrophysics Data System (ADS)

Lundh, Erik

This tutorial gives you a lead on becoming or redefining yourself as an Agile Coach. Introduction to elements and dimensions of state-of-the-art Agile Coaching. How to position the agile coach to be effective in a larger setting. Making the agile transition - from a single team to thousands of people. How to support multiple teams as a coach. How to build a coaches network in your company. Challenges when the agile coach is a consultant and the organization is large.

Teaching Agile Software Engineering Using Problem-Based Learning

ERIC Educational Resources Information Center

El-Khalili, Nuha H.

2013-01-01

Many studies have reported the utilization of Problem-Based Learning (PBL) in teaching Software Engineering courses. However, these studies have different views of the effectiveness of PBL. This paper presents the design of an Advanced Software Engineering course for undergraduate Software Engineering students that uses PBL to teach them Agile…

The Mediating Role of Organizational Learning in the Relationship of Organizational Intelligence and Organizational Agility.

PubMed

Bahrami, Mohammad Amin; Kiani, Mohammad Mehdi; Montazeralfaraj, Raziye; Zadeh, Hossein Fallah; Zadeh, Morteza Mohammad

2016-06-01

Organizational learning is defined as creating, absorbing, retaining, transferring, and application of knowledge within an organization. This article aims to examine the mediating role of organizational learning in the relationship of organizational intelligence and organizational agility. This analytical and cross-sectional study was conducted in 2015 at four teaching hospitals of Yazd city, Iran. A total of 370 administrative and medical staff contributed to the study. We used stratified-random method for sampling. Required data were gathered using three valid questionnaires including Alberkht (2003) organizational intelligence, Neefe (2001) organizational learning, and Sharifi and Zhang (1999) organizational agility questionnaires. Data analysis was done through R and SPSS 18 statistical software. The results showed that organizational learning acts as a mediator in the relationship of organizational intelligence and organizational agility (path coefficient = 0.943). Also, organizational learning has a statistical relationship with organizational agility (path coefficient = 0.382). Our findings suggest that the improvement of organizational learning abilities can affect an organization's agility which is crucial for its survival.

Technology for Evolutionary Software Development (Technologies pour le developpement de logiciels evolutifs)

DTIC Science & Technology

2003-06-01

greater detail in the next section, is to achieve these principles. Besides the fact, that these principles illustrate the essence of agile software...like e.g. ADLER, JASMIN , SAMOC or HEROS. In all of these projects the framework for the process model was the Vorgehensmodell (V-Model) of the...practical essence of the solutions to manage projects within the constraints of cost, schedule, functionality and quality and ways to get the

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.

Strategic agility for nursing leadership.

PubMed

Shirey, Maria R

2015-06-01

This department highlights change management strategies that may be successful in strategically planning and executing organizational change. In this article, the author discusses strategic agility as an important leadership competency and offers approaches for incorporating strategic agility in healthcare systems. A strategic agility checklist and infrastructure-building approach are presented.

Development of an Agility Test for Badminton Players and Assessment of Its Validity and Test-Retest Reliability.

PubMed

Loureiro, Luiz de França Bahia; de Freitas, Paulo Barbosa

2016-04-01

Badminton requires open and fast actions toward the shuttlecock, but there is no specific agility test for badminton players with specific movements. To develop an agility test that simultaneously assesses perception and motor capacity and examine the test's concurrent and construct validity and its test-retest reliability. The Badcamp agility test consists of running as fast as possible to 6 targets placed on the corners and middle points of a rectangular area (5.6 × 4.2 m) from the start position located in the center of it, following visual stimuli presented in a luminous panel. The authors recruited 43 badminton players (17-32 y old) to evaluate concurrent (with shuttle-run agility test--SRAT) and construct validity and test-retest reliability. Results revealed that Badcamp presents concurrent and construct validity, as its performance is strongly related to SRAT (ρ = 0.83, P < .001), with performance of experts being better than nonexpert players (P < .01). In addition, Badcamp is reliable, as no difference (P = .07) and a high intraclass correlation (ICC = .93) were found in the performance of the players on 2 different occasions. The findings indicate that Badcamp is an effective, valid, and reliable tool to measure agility, allowing coaches and athletic trainers to evaluate players' athletic condition and training effectiveness and possibly detect talented individuals in this sport.

Agile Methodology - Past and Future

DTIC Science & Technology

2011-05-01

Takeuchi & Nonaka HBR 1986, p139 RUGBY Waterfall Red vs Agile Black Team- . - Manifesto 2001 SCRUM GRAPHIC* * Adapted from Schwaber (2007) Agile...learning will help Agile manage its vision • Rugby : All Blacks 36 v England 12 Auckland, NZ (6/19/04) Glossary • AFB – Air Force Base • MCS - Maneuver

Opening up the Agile Innovation Process

NASA Astrophysics Data System (ADS)

Conboy, Kieran; Donnellan, Brian; Morgan, Lorraine; Wang, Xiaofeng

The objective of this panel is to discuss how firms can operate both an open and agile innovation process. In an era of unprecedented changes, companies need to be open and agile in order to adapt rapidly and maximize their innovation processes. Proponents of agile methods claim that one of the main distinctions between agile methods and their traditional bureaucratic counterparts is their drive toward creativity and innovation. However, agile methods are rarely adopted in their textbook, "vanilla" format, and are usually adopted in part or are tailored or modified to suit the organization. While we are aware that this happens, there is still limited understanding of what is actually happening in practice. Using innovation adoption theory, this panel will discuss the issues and challenges surrounding the successful adoption of agile practices. In addition, this panel will report on the obstacles and benefits reported by over 20 industrial partners engaged in a pan-European research project into agile practices between 2006 and 2009.

Agile Development of Various Computational Power Adaptive Web-Based Mobile-Learning Software Using Mobile Cloud Computing

ERIC Educational Resources Information Center

Zadahmad, Manouchehr; Yousefzadehfard, Parisa

2016-01-01

Mobile Cloud Computing (MCC) aims to improve all mobile applications such as m-learning systems. This study presents an innovative method to use web technology and software engineering's best practices to provide m-learning functionalities hosted in a MCC-learning system as service. Components hosted by MCC are used to empower developers to create…

On the Biomimetic Design of Agile-Robot Legs

PubMed Central

Garcia, Elena; Arevalo, Juan Carlos; Muñoz, Gustavo; Gonzalez-de-Santos, Pablo

2011-01-01

The development of functional legged robots has encountered its limits in human-made actuation technology. This paper describes research on the biomimetic design of legs for agile quadrupeds. A biomimetic leg concept that extracts key principles from horse legs which are responsible for the agile and powerful locomotion of these animals is presented. The proposed biomimetic leg model defines the effective leg length, leg kinematics, limb mass distribution, actuator power, and elastic energy recovery as determinants of agile locomotion, and values for these five key elements are given. The transfer of the extracted principles to technological instantiations is analyzed in detail, considering the availability of current materials, structures and actuators. A real leg prototype has been developed following the biomimetic leg concept proposed. The actuation system is based on the hybrid use of series elasticity and magneto-rheological dampers which provides variable compliance for natural motion. From the experimental evaluation of this prototype, conclusions on the current technological barriers to achieve real functional legged robots to walk dynamically in agile locomotion are presented. PMID:22247667

On the biomimetic design of agile-robot legs.

PubMed

Garcia, Elena; Arevalo, Juan Carlos; Muñoz, Gustavo; Gonzalez-de-Santos, Pablo

2011-01-01

The development of functional legged robots has encountered its limits in human-made actuation technology. This paper describes research on the biomimetic design of legs for agile quadrupeds. A biomimetic leg concept that extracts key principles from horse legs which are responsible for the agile and powerful locomotion of these animals is presented. The proposed biomimetic leg model defines the effective leg length, leg kinematics, limb mass distribution, actuator power, and elastic energy recovery as determinants of agile locomotion, and values for these five key elements are given. The transfer of the extracted principles to technological instantiations is analyzed in detail, considering the availability of current materials, structures and actuators. A real leg prototype has been developed following the biomimetic leg concept proposed. The actuation system is based on the hybrid use of series elasticity and magneto-rheological dampers which provides variable compliance for natural motion. From the experimental evaluation of this prototype, conclusions on the current technological barriers to achieve real functional legged robots to walk dynamically in agile locomotion are presented.

Autonomous, agile micro-satellites and supporting technologies

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

Breitfeller, E; Dittman, M D; Gaughan, R J

1999-07-19

This paper updates the on-going effort at Lawrence Livermore National Laboratory to develop autonomous, agile micro-satellites (MicroSats). The objective of this development effort is to develop MicroSats weighing only a few tens of kilograms, that are able to autonomously perform precision maneuvers and can be used telerobotically in a variety of mission modes. The required capabilities include satellite rendezvous, inspection, proximity-operations, docking, and servicing. The MicroSat carries an integrated proximity-operations sensor-suite incorporating advanced avionics. A new self-pressurizing propulsion system utilizing a miniaturized pump and non-toxic mono-propellant hydrogen peroxide was successfully tested. This system can provide a nominal 25 kg MicroSatmore » with 200-300 m/s delta-v including a warm-gas attitude control system. The avionics is based on the latest PowerPC processor using a CompactPCI bus architecture, which is modular, high-performance and processor-independent. This leverages commercial-off-the-shelf (COTS) technologies and minimizes the effects of future changes in processors. The MicroSat software development environment uses the Vx-Works real-time operating system (RTOS) that provides a rapid development environment for integration of new software modules, allowing early integration and test. We will summarize results of recent integrated ground flight testing of our latest non-toxic pumped propulsion MicroSat testbed vehicle operated on our unique dynamic air-rail.« less

Agile rediscovering values: Similarities to continuous improvement strategies

NASA Astrophysics Data System (ADS)

Díaz de Mera, P.; Arenas, J. M.; González, C.

2012-04-01

Research in the late 80's on technological companies that develop products of high value innovation, with sufficient speed and flexibility to adapt quickly to changing market conditions, gave rise to the new set of methodologies known as Agile Management Approach. In the current changing economic scenario, we considered very interesting to study the similarities of these Agile Methodologies with other practices whose effectiveness has been amply demonstrated in both the West and Japan. Strategies such as Kaizen, Lean, World Class Manufacturing, Concurrent Engineering, etc, would be analyzed to check the values they have in common with the Agile Approach.

The Development of Delta: Using Agile to Develop a Decision Aid for Pediatric Oncology Clinical Trial Enrollment.

PubMed

Robertson, Eden G; Wakefield, Claire E; Cohn, Richard J; O'Brien, Tracey; Ziegler, David S; Fardell, Joanna E

2018-05-04

The internet is increasingly being used to disseminate health information. Given the complexity of pediatric oncology clinical trials, we developed Delta, a Web-based decision aid to support families deciding whether or not to enroll their child with cancer in a clinical trial. This paper details the Agile development process of Delta and user testing results of Delta. Development was iterative and involved 5 main stages: a requirements analysis, planning, design, development, and user testing. For user testing, we conducted 13 eye-tracking analyses and think-aloud interviews with health care professionals (n=6) and parents (n=7). Results suggested that there was minimal rereading of content and a high level of engagement in content. However, there were some navigational problems. Participants reported high acceptability (12/13) and high usability of the website (8/13). Delta demonstrates the utility for the use of Agile in the development of a Web-based decision aid for health purposes. Our study provides a clear step-by-step guide to develop a Web-based psychosocial tool within the health setting. ©Eden G Robertson, Claire E Wakefield, Richard J Cohn, Tracey O'Brien, David S Ziegler, Joanna E Fardell. Originally published in JMIR Research Protocols (http://www.researchprotocols.org), 04.05.2018.

A comparison of linear speed, closed-skill agility, and open-skill agility qualities between backcourt and frontcourt adult semiprofessional male basketball players.

PubMed

Scanlan, Aaron T; Tucker, Patrick S; Dalbo, Vincent J

2014-05-01

The measurement of fitness qualities relevant to playing position is necessary to inform basketball coaching and conditioning staff of role-related differences in playing groups. To date, sprinting and agility performance have not been compared between playing positions in adult male basketball players. Therefore, the purpose of this study was to describe and compare linear speed, closed-skill agility, and open-skill agility qualities between backcourt (point guard and shooting guard positions) and frontcourt (small forward, power forward, and center positions) semiprofessional basketball players. Six backcourt (mean ± SD: age, 24.3 ± 7.9 years; stature, 183.4 ± 4.0 cm; body mass, 85.5 ± 12.3 kg; VO2max, 51.9 ± 4.8 ml·kg(-1)·min(-1)) and 6 frontcourt (mean ± SD: age, 27.5 ± 5.5 years; stature, 194.4 ± 7.1 cm; body mass, 109.4 ± 8.8 kg; VO2max, 47.1 ± 5.0 ml·kg(-1)·min(-1)) adult male basketball players completed 20-m sprint, closed-skill agility, and open-skill agility performance tests. Magnitude-based inferences revealed that backcourt players (5 m, 1.048 ± 0.027 seconds; 10 m, 1.778 ± 0.048 seconds; 20 m, 3.075 ± 0.121 seconds) possessed likely quicker linear sprint times than frontcourt players (5 m, 1.095 ± 0.085 seconds; 10 m, 1.872 ± 0.127 seconds; 20 m, 3.242 ± 0.221 seconds). Conversely, frontcourt players (1.665 ± 0.096 seconds) held possible superior closed-skill agility performance than backcourt players (1.613 ± 0.111 seconds). In addition, unclear positional differences were apparent for open-skill agility qualities. These findings indicate that linear speed and change of direction speed might be differently developed across playing positions. Furthermore, position-related functions might similarly depend on the aspects of open-skill agility performance across backcourt and frontcourt players. Basketball coaching and conditioning staff should consider the development of position-targeted training drills to improve speed, agility

Utilization of an agility assessment module in analysis and optimization of preliminary fighter configuration

NASA Technical Reports Server (NTRS)

Ngan, Angelen; Biezad, Daniel

1996-01-01

A study has been conducted to develop and to analyze a FORTRAN computer code for performing agility analysis on fighter aircraft configurations. This program is one of the modules of the NASA Ames ACSYNT (AirCraft SYNThesis) design code. The background of the agility research in the aircraft industry and a survey of a few agility metrics are discussed. The methodology, techniques, and models developed for the code are presented. The validity of the existing code was evaluated by comparing with existing flight test data. A FORTRAN program was developed for a specific metric, PM (Pointing Margin), as part of the agility module. Example trade studies using the agility module along with ACSYNT were conducted using a McDonnell Douglas F/A-18 Hornet aircraft model. Tile sensitivity of thrust loading, wing loading, and thrust vectoring on agility criteria were investigated. The module can compare the agility potential between different configurations and has capability to optimize agility performance in the preliminary design process. This research provides a new and useful design tool for analyzing fighter performance during air combat engagements in the preliminary design.

Thinking Outside the Box: Agile Business Models for CNOs

NASA Astrophysics Data System (ADS)

Loss, Leandro; Crave, Servane

This paper introduces the idea of an agile Business Model for CNOs grounded on a new model of innovation based on the effects of globalization and of Knowledge Economy. The agile Business Model considers the resources that are spread out and available worldwide as well as the need for each customer to receive a unique customer experience. It aims at reinforcing in the context of the Knowledge Economy the different business models approaches developed so far. The paper also identifies the levers and the barriers of Agile Business Models Innovation in CNOs.

Agile manufacturing: The factory of the future

NASA Technical Reports Server (NTRS)

Loibl, Joseph M.; Bossieux, Terry A.

1994-01-01

The factory of the future will require an operating methodology which effectively utilizes all of the elements of product design, manufacturing and delivery. The process must respond rapidly to changes in product demand, product mix, design changes or changes in the raw materials. To achieve agility in a manufacturing operation, the design and development of the manufacturing processes must focus on customer satisfaction. Achieving greatest results requires that the manufacturing process be considered from product concept through sales. This provides the best opportunity to build a quality product for the customer at a reasonable rate. The primary elements of a manufacturing system include people, equipment, materials, methods and the environment. The most significant and most agile element in any process is the human resource. Only with a highly trained, knowledgeable work force can the proper methods be applied to efficiently process materials with machinery which is predictable, reliable and flexible. This paper discusses the affect of each element on the development of agile manufacturing systems.

I'll Txt U if I Have a Problem: How the Société Canadienne du Cancer in Quebec Applied Behavior-Change Theory, Data Mining and Agile Software Development to Help Young Adults Quit Smoking

PubMed Central

van Mierlo, Trevor; Fournier, Rachel; Jean-Charles, Anathalie; Hovington, Jacinthe; Ethier, Isabelle; Selby, Peter

2014-01-01

Introduction For many organizations, limited budgets and phased funding restrict the development of digital health tools. This problem is often exacerbated by the ever-increasing sophistication of technology and costs related to programming and maintenance. Traditional development methods tend to be costly and inflexible and not client centered. The purpose of this study is to analyze the use of Agile software development and outcomes of a three-phase mHealth program designed to help young adult Quebecers quit smoking. Methods In Phase I, literature reviews, focus groups, interviews, and behavior change theory were used in the adaption and re-launch of an existing evidence-based mHealth platform. Based on analysis of user comments and utilization data from Phase I, the second phase expanded the service to allow participants to live text-chat with counselors. Phase II evaluation led to the third and current phase, in which algorithms were introduced to target pregnant smokers, substance users, students, full-time workers, those affected by mood disorders and chronic disease. Results Data collected throughout the three phases indicate that the incremental evolution of the intervention has led to increasing numbers of smokers being enrolled while making functional enhancements. In Phase I (240 days) 182 smokers registered with the service. 51% (n = 94) were male and 61.5% (n = 112) were between the ages of 18–24. In Phase II (300 days), 994 smokers registered with the service. 51% (n = 508) were male and 41% (n = 403) were between the ages of 18–24. At 174 days to date 873 smokers have registered in the third phase. 44% (n = 388) were male and 24% (n = 212) were between the ages of 18–24. Conclusions Emerging technologies in behavioral science show potential, but do not have defined best practices for application development. In phased-based projects with limited funding, Agile appears to be a viable approach to building and expanding

I'll txt U if I have a problem: how the Société Canadienne du cancer in Quebec applied behavior-change theory, data mining and agile software development to help young adults quit smoking.

PubMed

van Mierlo, Trevor; Fournier, Rachel; Jean-Charles, Anathalie; Hovington, Jacinthe; Ethier, Isabelle; Selby, Peter

2014-01-01

For many organizations, limited budgets and phased funding restrict the development of digital health tools. This problem is often exacerbated by the ever-increasing sophistication of technology and costs related to programming and maintenance. Traditional development methods tend to be costly and inflexible and not client centered. The purpose of this study is to analyze the use of Agile software development and outcomes of a three-phase mHealth program designed to help young adult Quebecers quit smoking. In Phase I, literature reviews, focus groups, interviews, and behavior change theory were used in the adaption and re-launch of an existing evidence-based mHealth platform. Based on analysis of user comments and utilization data from Phase I, the second phase expanded the service to allow participants to live text-chat with counselors. Phase II evaluation led to the third and current phase, in which algorithms were introduced to target pregnant smokers, substance users, students, full-time workers, those affected by mood disorders and chronic disease. Data collected throughout the three phases indicate that the incremental evolution of the intervention has led to increasing numbers of smokers being enrolled while making functional enhancements. In Phase I (240 days) 182 smokers registered with the service. 51% (n = 94) were male and 61.5% (n = 112) were between the ages of 18-24. In Phase II (300 days), 994 smokers registered with the service. 51% (n = 508) were male and 41% (n = 403) were between the ages of 18-24. At 174 days to date 873 smokers have registered in the third phase. 44% (n = 388) were male and 24% (n = 212) were between the ages of 18-24. Emerging technologies in behavioral science show potential, but do not have defined best practices for application development. In phased-based projects with limited funding, Agile appears to be a viable approach to building and expanding digital tools.

Agile data management for curation of genomes to watershed datasets

NASA Astrophysics Data System (ADS)

Varadharajan, C.; Agarwal, D.; Faybishenko, B.; Versteeg, R.

2015-12-01

A software platform is being developed for data management and assimilation [DMA] as part of the U.S. Department of Energy's Genomes to Watershed Sustainable Systems Science Focus Area 2.0. The DMA components and capabilities are driven by the project science priorities and the development is based on agile development techniques. The goal of the DMA software platform is to enable users to integrate and synthesize diverse and disparate field, laboratory, and simulation datasets, including geological, geochemical, geophysical, microbiological, hydrological, and meteorological data across a range of spatial and temporal scales. The DMA objectives are (a) developing an integrated interface to the datasets, (b) storing field monitoring data, laboratory analytical results of water and sediments samples collected into a database, (c) providing automated QA/QC analysis of data and (d) working with data providers to modify high-priority field and laboratory data collection and reporting procedures as needed. The first three objectives are driven by user needs, while the last objective is driven by data management needs. The project needs and priorities are reassessed regularly with the users. After each user session we identify development priorities to match the identified user priorities. For instance, data QA/QC and collection activities have focused on the data and products needed for on-going scientific analyses (e.g. water level and geochemistry). We have also developed, tested and released a broker and portal that integrates diverse datasets from two different databases used for curation of project data. The development of the user interface was based on a user-centered design process involving several user interviews and constant interaction with data providers. The initial version focuses on the most requested feature - i.e. finding the data needed for analyses through an intuitive interface. Once the data is found, the user can immediately plot and download data

Agile manufacturing and constraints management: a strategic perspective

NASA Astrophysics Data System (ADS)

Stratton, Roy; Yusuf, Yahaya Y.

2000-10-01

The definition of the agile paradigm has proved elusive and is often viewed as a panacea, in contention with more traditional approaches to operations strategy development and Larkin its own methodology and tools. The Theory of Constraints (TOC) is also poorly understood, as it is commonly solely associated with production planning and control systems and bottleneck management. This paper will demonstrate the synergy between these two approaches together with the Theory of Inventive Problem Solving (TRIZ), and establish how the systematic elimination of trade-offs can support the agile paradigm. Whereas agility is often seen as a trade-off free destination, both TOC and TRIZ may be considered to be route finders, as they comprise methodologies that focus on the identification and elimination of the trade-offs that constrain the purposeful improvement of a system, be it organizational or mechanical. This paper will also show how the TOC thinking process may be combined with the TRIZ knowledge based approach and used in breaking contradictions within agile logistics.

Agile, a guiding principle for health care improvement?

PubMed

Tolf, Sara; Nyström, Monica E; Tishelman, Carol; Brommels, Mats; Hansson, Johan

2015-01-01

The purpose of this paper is to contribute to increased understanding of the concept agile and its potential for hospital managers to optimize design of organizational structures and processes to combine internal efficiency and external effectiveness. An integrative review was conducted using the reSEARCH database. Articles met the following criteria: first, a definition of agility; second, descriptions of enablers of becoming an agile organization; and finally, discussions of agile on multiple organizational levels. In total, 60 articles qualified for the final analysis. Organizational agility rests on the assumption that the environment is uncertain, ranging from frequently changing to highly unpredictable. Proactive, reactive or embracive coping strategies were described as possible ways to handle such uncertain environments. Five organizational capacities were derived as necessary for hospitals to use the strategies optimally: transparent and transient inter-organizational links; market sensitivity and customer focus; management by support for self-organizing employees; organic structures that are elastic and responsive; flexible human and resource capacity for timely delivery. Agile is portrayed as either the "new paradigm" following lean, the needed development on top of a lean base, or as complementary to lean in distinct hybrid strategies. Environmental uncertainty needs to be matched with coping strategies and organizational capacities to design processes responsive to real needs of health care. This implies that lean and agile can be combined to optimize the design of hospitals, to meet different variations in demand and create good patient management. While considerable value has been paid to strategies to improve the internal efficiency within hospitals, this review raise the attention to the value of strategies of external effectiveness.

Gamma-ray Astrophysics with AGILE

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

Longo, Francesco; Tavani, M.; Barbiellini, G.

2007-07-12

AGILE will explore the gamma-ray Universe with a very innovative instrument combining for the first time a gamma-ray imager and a hard X-ray imager. AGILE will be operational in spring 2007 and it will provide crucial data for the study of Active Galactic Nuclei, Gamma-Ray Bursts, unidentified gamma-ray sources. Galactic compact objects, supernova remnants, TeV sources, and fundamental physics by microsecond timing. The AGILE instrument is designed to simultaneously detect and image photons in the 30 MeV - 50 GeV and 15 - 45 keV energy bands with excellent imaging and timing capabilities, and a large field of view coveringmore » {approx} 1/5 of the entire sky at energies above 30 MeV. A CsI calorimeter is capable of GRB triggering in the energy band 0.3-50 MeV AGILE is now (March 2007) undergoing launcher integration and testing. The PLSV launch is planned in spring 2007. AGILE is then foreseen to be fully operational during the summer of 2007.« less

End-to-end observatory software modeling using domain specific languages

NASA Astrophysics Data System (ADS)

Filgueira, José M.; Bec, Matthieu; Liu, Ning; Peng, Chien; Soto, José

2014-07-01

The Giant Magellan Telescope (GMT) is a 25-meter extremely large telescope that is being built by an international consortium of universities and research institutions. Its software and control system is being developed using a set of Domain Specific Languages (DSL) that supports a model driven development methodology integrated with an Agile management process. This approach promotes the use of standardized models that capture the component architecture of the system, that facilitate the construction of technical specifications in a uniform way, that facilitate communication between developers and domain experts and that provide a framework to ensure the successful integration of the software subsystems developed by the GMT partner institutions.

Development of High-Fill-Factor Large-Aperture Micromirrors for Agile Optical Phased Arrays

DTIC Science & Technology

2010-02-28

Final Project Report Contract/Grant Title: Development of High-Fill-Factor Large-Aperture Micromirrors for Agile Optical Phased Arrays...factor (HFF) micromirror array (MMA) has been proposed, fabricated and tested. Optical-phased-array (OPA) beam steering based on the HFF MMA has also...electrically tuned to multiple 2. 1. Background High-fill-factor (HFF) micromirror arrays (MMAs) can form optical phased arrays (OPAs) for laser beam

Strategy quantification using body worn inertial sensors in a reactive agility task.

PubMed

Eke, Chika U; Cain, Stephen M; Stirling, Leia A

2017-11-07

Agility performance is often evaluated using time-based metrics, which provide little information about which factors aid or limit success. The objective of this study was to better understand agility strategy by identifying biomechanical metrics that were sensitive to performance speed, which were calculated with data from an array of body-worn inertial sensors. Five metrics were defined (normalized number of foot contacts, stride length variance, arm swing variance, mean normalized stride frequency, and number of body rotations) that corresponded to agility terms defined by experts working in athletic, clinical, and military environments. Eighteen participants donned 13 sensors to complete a reactive agility task, which involved navigating a set of cones in response to a vocal cue. Participants were grouped into fast, medium, and slow performance based on their completion time. Participants in the fast group had the smallest number of foot contacts (normalizing by height), highest stride length variance (normalizing by height), highest forearm angular velocity variance, and highest stride frequency (normalizing by height). The number of body rotations was not sensitive to speed and may have been determined by hand and foot dominance while completing the agility task. The results of this study have the potential to inform the development of a composite agility score constructed from the list of significant metrics. By quantifying the agility terms previously defined by expert evaluators through an agility score, this study can assist in strategy development for training and rehabilitation across athletic, clinical, and military domains. Copyright © 2017 Elsevier Ltd. All rights reserved.

Advancing cancer drug discovery towards more agile development of targeted combination therapies.

PubMed

Carragher, Neil O; Unciti-Broceta, Asier; Cameron, David A

2012-01-01

Current drug-discovery strategies are typically 'target-centric' and are based upon high-throughput screening of large chemical libraries against nominated targets and a selection of lead compounds with optimized 'on-target' potency and selectivity profiles. However, high attrition of targeted agents in clinical development suggest that combinations of targeted agents will be most effective in treating solid tumors if the biological networks that permit cancer cells to subvert monotherapies are identified and retargeted. Conventional drug-discovery and development strategies are suboptimal for the rational design and development of novel drug combinations. In this article, we highlight a series of emerging technologies supporting a less reductionist, more agile, drug-discovery and development approach for the rational design, validation, prioritization and clinical development of novel drug combinations.

Space Flight Software Development Software for Intelligent System Health Management

NASA Technical Reports Server (NTRS)

Trevino, Luis C.; Crumbley, Tim

2004-01-01

The slide presentation examines the Marshall Space Flight Center Flight Software Branch, including software development projects, mission critical space flight software development, software technical insight, advanced software development technologies, and continuous improvement in the software development processes and methods.

Research of real-time communication software

NASA Astrophysics Data System (ADS)

Li, Maotang; Guo, Jingbo; Liu, Yuzhong; Li, Jiahong

2003-11-01

Real-time communication has been playing an increasingly important role in our work, life and ocean monitor. With the rapid progress of computer and communication technique as well as the miniaturization of communication system, it is needed to develop the adaptable and reliable real-time communication software in the ocean monitor system. This paper involves the real-time communication software research based on the point-to-point satellite intercommunication system. The object-oriented design method is adopted, which can transmit and receive video data and audio data as well as engineering data by satellite channel. In the real-time communication software, some software modules are developed, which can realize the point-to-point satellite intercommunication in the ocean monitor system. There are three advantages for the real-time communication software. One is that the real-time communication software increases the reliability of the point-to-point satellite intercommunication system working. Second is that some optional parameters are intercalated, which greatly increases the flexibility of the system working. Third is that some hardware is substituted by the real-time communication software, which not only decrease the expense of the system and promotes the miniaturization of communication system, but also aggrandizes the agility of the system.

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

Focused Logistics: Putting Agility in Agile Logistics

DTIC Science & Technology

2011-05-19

list, ahead of companies like American Express, DuPont and Coca Cola ; Supports nearly 1,900 weapon systems; DLA manages eight supply chains and...35 7) Force Health Protection...Distribution, Information Fusion, Joint Theater Logistics Command and Control, Multinational Logistics, Joint Health Services Support, and Agile

Implementing Kanban for agile process management within the ALMA Software Operations Group

NASA Astrophysics Data System (ADS)

Reveco, Johnny; Mora, Matias; Shen, Tzu-Chiang; Soto, Ruben; Sepulveda, Jorge; Ibsen, Jorge

2014-07-01

After the inauguration of the Atacama Large Millimeter/submillimeter Array (ALMA), the Software Operations Group in Chile has refocused its objectives to: (1) providing software support to tasks related to System Integration, Scientific Commissioning and Verification, as well as Early Science observations; (2) testing the remaining software features, still under development by the Integrated Computing Team across the world; and (3) designing and developing processes to optimize and increase the level of automation of operational tasks. Due to their different stakeholders, each of these tasks presents a wide diversity of importances, lifespans and complexities. Aiming to provide the proper priority and traceability for every task without stressing our engineers, we introduced the Kanban methodology in our processes in order to balance the demand on the team against the throughput of the delivered work. The aim of this paper is to share experiences gained during the implementation of Kanban in our processes, describing the difficulties we have found, solutions and adaptations that led us to our current but still evolving implementation, which has greatly improved our throughput, prioritization and problem traceability.

Investigation into the impact of agility on conceptual fighter design

NASA Technical Reports Server (NTRS)

Engelbeck, R. M.

1995-01-01

The Agility Design Study was performed by the Boeing Defense and Space Group for the NASA Langley Research Center. The objective of the study was to assess the impact of agility requirements on new fighter configurations. Global trade issues investigated were the level of agility, the mission role of the aircraft (air-to-ground, multi-role, or air-to-air), and whether the customer is Air force, Navy, or joint service. Mission profiles and design objectives were supplied by NASA. An extensive technology assessment was conducted to establish the available technologies to industry for the aircraft. Conceptual level methodology is presented to assess the five NASA-supplied agility metrics. Twelve configurations were developed to address the global trade issues. Three-view drawings, inboard profiles, and performance estimates were made and are included in the report. A critical assessment and lessons learned from the study are also presented.

Agile Model Driven Development of Electronic Health Record-Based Specialty Population Registries

PubMed Central

Kannan, Vaishnavi; Fish, Jason C.; Willett, DuWayne L.

2018-01-01

The transformation of the American healthcare payment system from fee-for-service to value-based care increasingly makes it valuable to develop patient registries for specialized populations, to better assess healthcare quality and costs. Recent widespread adoption of Electronic Health Records (EHRs) in the U.S. now makes possible construction of EHR-based specialty registry data collection tools and reports, previously unfeasible using manual chart abstraction. But the complexities of specialty registry EHR tools and measures, along with the variety of stakeholders involved, can result in misunderstood requirements and frequent product change requests, as users first experience the tools in their actual clinical workflows. Such requirements churn could easily stall progress in specialty registry rollout. Modeling a system’s requirements and solution design can be a powerful way to remove ambiguities, facilitate shared understanding, and help evolve a design to meet newly-discovered needs. “Agile Modeling” retains these values while avoiding excessive unused up-front modeling in favor of iterative incremental modeling. Using Agile Modeling principles and practices, in calendar year 2015 one institution developed 58 EHR-based specialty registries, with 111 new data collection tools, supporting 134 clinical process and outcome measures, and enrolling over 16,000 patients. The subset of UML and non-UML models found most consistently useful in designing, building, and iteratively evolving EHR-based specialty registries included User Stories, Domain Models, Use Case Diagrams, Decision Trees, Graphical User Interface Storyboards, Use Case text descriptions, and Solution Class Diagrams. PMID:29750222

Agile Model Driven Development of Electronic Health Record-Based Specialty Population Registries.

PubMed

Kannan, Vaishnavi; Fish, Jason C; Willett, DuWayne L

2016-02-01

The transformation of the American healthcare payment system from fee-for-service to value-based care increasingly makes it valuable to develop patient registries for specialized populations, to better assess healthcare quality and costs. Recent widespread adoption of Electronic Health Records (EHRs) in the U.S. now makes possible construction of EHR-based specialty registry data collection tools and reports, previously unfeasible using manual chart abstraction. But the complexities of specialty registry EHR tools and measures, along with the variety of stakeholders involved, can result in misunderstood requirements and frequent product change requests, as users first experience the tools in their actual clinical workflows. Such requirements churn could easily stall progress in specialty registry rollout. Modeling a system's requirements and solution design can be a powerful way to remove ambiguities, facilitate shared understanding, and help evolve a design to meet newly-discovered needs. "Agile Modeling" retains these values while avoiding excessive unused up-front modeling in favor of iterative incremental modeling. Using Agile Modeling principles and practices, in calendar year 2015 one institution developed 58 EHR-based specialty registries, with 111 new data collection tools, supporting 134 clinical process and outcome measures, and enrolling over 16,000 patients. The subset of UML and non-UML models found most consistently useful in designing, building, and iteratively evolving EHR-based specialty registries included User Stories, Domain Models, Use Case Diagrams, Decision Trees, Graphical User Interface Storyboards, Use Case text descriptions, and Solution Class Diagrams.

Explaining the Obvious - How Do You Teach Agile?

NASA Astrophysics Data System (ADS)

Lundh, Erik

Agile is now a hot topic and many organizations decide on adopting “agile” without really knowing how and why. This workshop will explore how fresh and seasoned agile coaches teach traditional and novel agile concepts, by example, with discussions. All participants are invited to show and tell about agile with an audience of peers. It might be the fresh first time with an audience, or golden hits that served you well for years.

Agile-Lean Software Engineering (ALSE) Evaluating Kanban in Systems Engineering

DTIC Science & Technology

2013-03-06

Boeing)  Garry Roedler (Lockheed Martin)  Karl Scotland (Rally Software, UK)  Alan Shalloway (NetObjectives)  Neil Shirk (Lockheed Martin... Neil Siegel (Northrop Grumman)  James Sutton (Jubata Group) Thanks are also due to the members of the SERC Research Council, particularly Barry...Incremental Commitment Model to Brownfield Systems Development, Proceedings, CSER 2009, April 2009. 16. Heath , B. et al. (2009). A survey of agent-based

Microcomputer software development facilities

NASA Technical Reports Server (NTRS)

Gorman, J. S.; Mathiasen, C.

1980-01-01

A more efficient and cost effective method for developing microcomputer software is to utilize a host computer with high-speed peripheral support. Application programs such as cross assemblers, loaders, and simulators are implemented in the host computer for each of the microcomputers for which software development is a requirement. The host computer is configured to operate in a time share mode for multiusers. The remote terminals, printers, and down loading capabilities provided are based on user requirements. With this configuration a user, either local or remote, can use the host computer for microcomputer software development. Once the software is developed (through the code and modular debug stage) it can be downloaded to the development system or emulator in a test area where hardware/software integration functions can proceed. The microcomputer software program sources reside in the host computer and can be edited, assembled, loaded, and then downloaded as required until the software development project has been completed.

Frequency agile optical parametric oscillator

DOEpatents

Velsko, S.P.

1998-11-24

The frequency agile OPO device converts a fixed wavelength pump laser beam to arbitrary wavelengths within a specified range with pulse to pulse agility, at a rate limited only by the repetition rate of the pump laser. Uses of this invention include Laser radar, LIDAR, active remote sensing of effluents/pollutants, environmental monitoring, antisensor lasers, and spectroscopy. 14 figs.

Frequency agile optical parametric oscillator

DOEpatents

Velsko, Stephan P.

1998-01-01

The frequency agile OPO device converts a fixed wavelength pump laser beam to arbitrary wavelengths within a specified range with pulse to pulse agility, at a rate limited only by the repetition rate of the pump laser. Uses of this invention include Laser radar, LIDAR, active remote sensing of effluents/pollutants, environmental monitoring, antisensor lasers, and spectroscopy.

Documentation Driven Development for Complex Real-Time Systems

DTIC Science & Technology

2004-12-01

This paper presents a novel approach for development of complex real - time systems , called the documentation-driven development (DDD) approach. This... time systems . DDD will also support automated software generation based on a computational model and some relevant techniques. DDD includes two main...stakeholders to be easily involved in development processes and, therefore, significantly improve the agility of software development for complex real

Dynamic tumor tracking using the Elekta Agility MLC

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

Fast, Martin F., E-mail: martin.fast@icr.ac.uk; Nill, Simeon, E-mail: simeon.nill@icr.ac.uk; Bedford, James L.

2014-11-01

Purpose: To evaluate the performance of the Elekta Agility multileaf collimator (MLC) for dynamic real-time tumor tracking. Methods: The authors have developed a new control software which interfaces to the Agility MLC to dynamically program the movement of individual leaves, the dynamic leaf guides (DLGs), and the Y collimators (“jaws”) based on the actual target trajectory. A motion platform was used to perform dynamic tracking experiments with sinusoidal trajectories. The actual target positions reported by the motion platform at 20, 30, or 40 Hz were used as shift vectors for the MLC in beams-eye-view. The system latency of the MLCmore » (i.e., the average latency comprising target device reporting latencies and MLC adjustment latency) and the geometric tracking accuracy were extracted from a sequence of MV portal images acquired during irradiation for the following treatment scenarios: leaf-only motion, jaw + leaf motion, and DLG + leaf motion. Results: The portal imager measurements indicated a clear dependence of the system latency on the target position reporting frequency. Deducting the effect of the target frequency, the leaf adjustment latency was measured to be 38 ± 3 ms for a maximum target speed v of 13 mm/s. The jaw + leaf adjustment latency was 53 ± 3 at a similar speed. The system latency at a target position frequency of 30 Hz was in the range of 56–61 ms for the leaves (v ≤ 31 mm/s), 71–78 ms for the jaw + leaf motion (v ≤ 25 mm/s), and 58–72 ms for the DLG + leaf motion (v ≤ 59 mm/s). The tracking accuracy showed a similar dependency on the target position frequency and the maximum target speed. For the leaves, the root-mean-squared error (RMSE) was between 0.6–1.5 mm depending on the maximum target speed. For the jaw + leaf (DLG + leaf) motion, the RMSE was between 0.7–1.5 mm (1.9–3.4 mm). Conclusions: The authors have measured the latency and geometric accuracy of the Agility MLC, facilitating its future use for

Wavelength-Agile External-Cavity Diode Laser for DWDM

NASA Technical Reports Server (NTRS)

Pilgrim, Jeffrey S.; Bomse, David S.

2006-01-01

A prototype external-cavity diode laser (ECDL) has been developed for communication systems utilizing dense wavelength- division multiplexing (DWDM). This ECDL is an updated version of the ECDL reported in Wavelength-Agile External- Cavity Diode Laser (LEW-17090), NASA Tech Briefs, Vol. 25, No. 11 (November 2001), page 14a. To recapitulate: The wavelength-agile ECDL combines the stability of an external-cavity laser with the wavelength agility of a diode laser. Wavelength is modulated by modulating the injection current of the diode-laser gain element. The external cavity is a Littman-Metcalf resonator, in which the zeroth-order output from a diffraction grating is used as the laser output and the first-order-diffracted light is retro-reflected by a cavity feedback mirror, which establishes one end of the resonator. The other end of the resonator is the output surface of a Fabry-Perot resonator that constitutes the diode-laser gain element. Wavelength is selected by choosing the angle of the diffracted return beam, as determined by position of the feedback mirror. The present wavelength-agile ECDL is distinguished by design details that enable coverage of all 60 channels, separated by 100-GHz frequency intervals, that are specified in DWDM standards.

Embedding Agile Practices within a Plan-Driven Hierarchical Project Life Cycle

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

Millard, W. David; Johnson, Daniel M.; Henderson, John M.

2014-07-28

Organizations use structured, plan-driven approaches to provide continuity, direction, and control to large, multi-year programs. Projects within these programs vary greatly in size, complexity, level of maturity, technical risk, and clarity of the development objectives. Organizations that perform exploratory research, evolutionary development, and other R&D activities can obtain the benefits of Agile practices without losing the benefits of their program’s overarching plan-driven structure. This paper describes application of Agile development methods on a large plan-driven sensor integration program. While the client employed plan-driven, requirements flow-down methodologies, tight project schedules and complex interfaces called for frequent end-to-end demonstrations to provide feedbackmore » during system development. The development process maintained the many benefits of plan-driven project execution with the rapid prototyping, integration, demonstration, and client feedback possible through Agile development methods. This paper also describes some of the tools and implementing mechanisms used to transition between and take advantage of each methodology, and presents lessons learned from the project management, system engineering, and developer’s perspectives.« less

AGILE integration into APC for high mix logic fab

NASA Astrophysics Data System (ADS)

Gatefait, M.; Lam, A.; Le Gratiet, B.; Mikolajczak, M.; Morin, V.; Chojnowski, N.; Kocsis, Z.; Smith, I.; Decaunes, J.; Ostrovsky, A.; Monget, C.

2015-09-01

mix logic Fab) in term of product and technology portfolio AGILE corrects for up to 120nm of product topography error on process layer with less than 50nm depth of focus Based on tool functionalities delivered by ASML and on high volume manufacturing requirement, AGILE integration is a real challenge. Regarding ST requirements "Automatic AGILE" functionality developed by ASML was not a turnkey solution and a dedicated functionality was needed. A "ST homemade AGILE integration" has been fully developed and implemented within ASML and ST constraints. This paper describes this integration in our Advanced Process Control platform (APC).

Social Protocols for Agile Virtual Teams

NASA Astrophysics Data System (ADS)

Picard, Willy

Despite many works on collaborative networked organizations (CNOs), CSCW, groupware, workflow systems and social networks, computer support for virtual teams is still insufficient, especially support for agility, i.e. the capability of virtual team members to rapidly and cost efficiently adapt the way they interact to changes. In this paper, requirements for computer support for agile virtual teams are presented. Next, an extension of the concept of social protocol is proposed as a novel model supporting agile interactions within virtual teams. The extended concept of social protocol consists of an extended social network and a workflow model.

Network configuration management : paving the way to network agility.

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

Maestas, Joseph H.

2007-08-01

Sandia networks consist of nearly nine hundred routers and switches and nearly one million lines of command code, and each line ideally contributes to the capabilities of the network to convey information from one location to another. Sandia's Cyber Infrastructure Development and Deployment organizations recognize that it is therefore essential to standardize network configurations and enforce conformance to industry best business practices and documented internal configuration standards to provide a network that is agile, adaptable, and highly available. This is especially important in times of constrained budgets as members of the workforce are called upon to improve efficiency, effectiveness, andmore » customer focus. Best business practices recommend using the standardized configurations in the enforcement process so that when root cause analysis results in recommended configuration changes, subsequent configuration auditing will improve compliance to the standard. Ultimately, this minimizes mean time to repair, maintains the network security posture, improves network availability, and enables efficient transition to new technologies. Network standardization brings improved network agility, which in turn enables enterprise agility, because the network touches all facets of corporate business. Improved network agility improves the business enterprise as a whole.« less

Organizational Culture and the Deployment of Agile Methods: The Competing Values Model View

NASA Astrophysics Data System (ADS)

Iivari, Juhani; Iivari, Netta

A number of researchers have identified organizational culture as a factor that potentially affects the deployment of agile systems development methods. Inspired by the study of Iivari and Huisman (2007), which focused on the deployment of traditional systems development methods, the present paper proposes a number of hypotheses about the influence of organizational culture on the deployment of agile methods.

Agile based "Semi-"Automated Data ingest process : ORNL DAAC example

NASA Astrophysics Data System (ADS)

Santhana Vannan, S. K.; Beaty, T.; Cook, R. B.; Devarakonda, R.; Hook, L.; Wei, Y.; Wright, D.

2015-12-01

The ORNL DAAC archives and publishes data and information relevant to biogeochemical, ecological, and environmental processes. The data archived at the ORNL DAAC must be well formatted, self-descriptive, and documented, as well as referenced in a peer-reviewed publication. The ORNL DAAC ingest team curates diverse data sets from multiple data providers simultaneously. To streamline the ingest process, the data set submission process at the ORNL DAAC has been recently updated to use an agile process and a semi-automated workflow system has been developed to provide a consistent data provider experience and to create a uniform data product. The goals of semi-automated agile ingest process are to: 1.Provide the ability to track a data set from acceptance to publication 2. Automate steps that can be automated to improve efficiencies and reduce redundancy 3.Update legacy ingest infrastructure 4.Provide a centralized system to manage the various aspects of ingest. This talk will cover the agile methodology, workflow, and tools developed through this system.

Physical demand of seven closed agility drills.

PubMed

Atkinson, Mark; Rosalie, Simon; Netto, Kevin

2016-11-01

The present study aimed to quantify the demand of seven generic, closed agility drills. Twenty males with experience in invasion sports volunteered to participate in this study. They performed seven, closed agility drills over a standardised 30-m distance. Physical demand measures of peak velocity, total foot contacts, peak impacts, completion time, and maximum heart rate were obtained via the use of wearable sensor technologies. A subjective rating of perceived exertion (RPE) was also obtained. All measures, with the exception of maximum heart rates and RPE were able to delineate drills in terms of physical and physiological demand. The findings of this study exemplify the differences in demand of agility-type movements. Drill demand was dictated by the type of agility movement initiated with the increase in repetitiveness of a given movement type also contributing to increased demand. Findings from this study suggest agility drills can be manipulated to vary physical and physiological demand. This allows for the optimal application of training principles such as overload, progression, and periodisation.

The Introduction of Agility into Albania.

ERIC Educational Resources Information Center

Smith-Stevens, Eileen J.; Shkurti, Drita

1998-01-01

Describes a plan to introduce and achieve a national awareness of agility (and easy entry into the world market) for Albania through the relatively stable higher-education order. Agility's four strategic principles are enriching the customer, cooperating to enhance competitiveness, organizing to master change and uncertainty, and leveraging the…

Social media as an information system: improving the technological agility

NASA Astrophysics Data System (ADS)

Senadheera, Vindaya; Warren, Matthew; Leitch, Shona

2017-04-01

There is an increased focus on research involving social media. This research however has failed to catch up with the pace of the technology development and may prove disadvantageous for both practice and theory. The longitudinal study presented in the paper was conducted over a 3-year period involving Australian banks and popular social media technologies. The paper empirically tests the Honeycomb model as a tool that enhances the technological agility of social media. The paper fills a key research gap and provides dynamism to social media strategy formation, continuous improvement of strategy development in support of greater business agility.

The Impact of Software Culture on the Management of Community Data

NASA Astrophysics Data System (ADS)

Collins, J. A.; Pulsifer, P. L.; Sheffield, E.; Lewis, S.; Oldenburg, J.

2013-12-01

The Exchange for Local Observations and Knowledge of the Arctic (ELOKA), a program hosted at the National Snow and Ice Data Center (NSIDC), supports the collection, curation, and distribution of Local and Traditional Knowledge (LTK) data, as well as some quantitative data products. Investigations involving LTK data often involve community participation, and therefore require flexible and robust user interfaces to support a reliable process of data collection and management. Often, investigators focused on LTK and community-based monitoring choose to use ELOKA's data services based on our ability to provide rapid proof-of-concepts and economical delivery of a usable product. To satisfy these two overarching criteria, ELOKA is experimenting with modifications to its software development culture both in terms of how the software applications are developed as well as the kind of software applications (or components) being developed. Over the past several years, NSIDC has shifted its software development culture from one of assigning individual scientific programmers to support particular principal investigators or projects, to an Agile Software Methodology implementation using Scrum practices. ELOKA has participated in this process by working with other product owners to schedule and prioritize development work which is then implemented by a team of application developers. Scrum, along with practices such as Test Driven Development (TDD) and paired programming, improves the quality of the software product delivered to the user community. To meet the need for rapid prototyping and to maximize product development and support with limited developer input, our software development efforts are now focused on creating a platform of application modules that can be quickly customized to suit the needs of a variety of LTK projects. This approach is in contrast to the strategy of delivering custom applications for individual projects. To date, we have integrated components of

Frequency Agile Transceiver for Advanced Vehicle Data Links

NASA Technical Reports Server (NTRS)

Freudinger, Lawrence C.; Macias, Filiberto; Cornelius, Harold

2009-01-01

Emerging and next-generation test instrumentation increasingly relies on network communication to manage complex and dynamic test scenarios, particularly for uninhabited autonomous systems. Adapting wireless communication infrastructure to accommodate challenging testing needs can benefit from reconfigurable radio technology. Frequency agility is one characteristic of reconfigurable radios that to date has seen only limited progress toward programmability. This paper overviews an ongoing project to validate a promising chipset that performs conversion of RF signals directly into digital data for the wireless receiver and, for the transmitter, converts digital data into RF signals. The Software Configurable Multichannel Transceiver (SCMT) enables four transmitters and four receivers in a single unit, programmable for any frequency band between 1 MHz and 6 GHz.

Perspectives on Agile Coaching

NASA Astrophysics Data System (ADS)

Fraser, Steven; Lundh, Erik; Davies, Rachel; Eckstein, Jutta; Larsen, Diana; Vilkki, Kati

There are many perspectives to agile coaching including: growing coaching expertise, selecting the appropriate coach for your context; and eva luating value. A coach is often an itinerant who may observe, mentor, negotiate, influence, lead, and/or architect everything from team organization to system architecture. With roots in diverse fields ranging from technology to sociology coaches have differing motivations and experience bases. This panel will bring together coaches to debate and discuss various perspectives on agile coaching. Some of the questions to be addressed will include: What are the skills required for effective coaching? What should be the expectations for teams or individu als being coached? Should coaches be: a corporate resource (internal team of consultants working with multiple internal teams); an integral part of a specific team; or external contractors? How should coaches exercise influence and au thority? How should management assess the value of a coaching engagement? Do you have what it takes to be a coach? - This panel will bring together sea soned agile coaches to offer their experience and advice on how to be the best you can be!

Operational Agility (La Maniabilite Operationnelle)

DTIC Science & Technology

1994-04-01

the use of attitude projection 171. The procedure described above is schematically shown in figure 2.10. i Maneuvers...with the performance margins expected of future projects . (9,15) The agility factor concept was developed from that described in Reference 12 and...and in support of , a land battle between enemy forces. The nature of the combined arms battlefield and the terrain and environmental

Agile Systems Engineering-Kanban Scheduling Subsection

DTIC Science & Technology

2017-03-10

including both online and standalone versions. RESEARCH GOALS The overall Agile SE Management Project research goals are to: 1. Identify agile...March 10, 2017 5 Establish a better technical project management and... Project Management ,” Master of Science Project , Stevens Institute, to be completed in May, 2017. • Smith, Jeffrey, “System of Systems Task

Are Earth System model software engineering practices fit for purpose? A case study.

NASA Astrophysics Data System (ADS)

Easterbrook, S. M.; Johns, T. C.

2009-04-01

We present some analysis and conclusions from a case study of the culture and practices of scientists at the Met Office and Hadley Centre working on the development of software for climate and Earth System models using the MetUM infrastructure. The study examined how scientists think about software correctness, prioritize their requirements in making changes, and develop a shared understanding of the resulting models. We conclude that highly customized techniques driven strongly by scientific research goals have evolved for verification and validation of such models. In a formal software engineering context these represents costly, but invaluable, software integration tests with considerable benefits. The software engineering practices seen also exhibit recognisable features of both agile and open source software development projects - self-organisation of teams consistent with a meritocracy rather than top-down organisation, extensive use of informal communication channels, and software developers who are generally also users and science domain experts. We draw some general conclusions on whether these practices work well, and what new software engineering challenges may lie ahead as Earth System models become ever more complex and petascale computing becomes the norm.

Evaluation of agile designs in first-in-human (FIH) trials--a simulation study.

PubMed

Perlstein, Itay; Bolognese, James A; Krishna, Rajesh; Wagner, John A

2009-12-01

The aim of the investigation was to evaluate alternatives to standard first-in-human (FIH) designs in order to optimize the information gained from such studies by employing novel agile trial designs. Agile designs combine adaptive and flexible elements to enable optimized use of prior information either before and/or during conduct of the study to seamlessly update the study design. A comparison of the traditional 6 + 2 (active + placebo) subjects per cohort design with alternative, reduced sample size, agile designs was performed by using discrete event simulation. Agile designs were evaluated for specific adverse event models and rates as well as dose-proportional, saturated, and steep-accumulation pharmacokinetic profiles. Alternative, reduced sample size (hereafter referred to as agile) designs are proposed for cases where prior knowledge about pharmacokinetics and/or adverse event relationships are available or appropriately assumed. Additionally, preferred alternatives are proposed for a general case when prior knowledge is limited or unavailable. Within the tested conditions and stated assumptions, some agile designs were found to be as efficient as traditional designs. Thus, simulations demonstrated that the agile design is a robust and feasible approach to FIH clinical trials, with no meaningful loss of relevant information, as it relates to PK and AE assumptions. In some circumstances, applying agile designs may decrease the duration and resources required for Phase I studies, increasing the efficiency of early clinical development. We highlight the value and importance of useful prior information when specifying key assumptions related to safety, tolerability, and PK.

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.

Transitioning from Distributed and Traditional to Distributed and Agile: An Experience Report

NASA Astrophysics Data System (ADS)

Wildt, Daniel; Prikladnicki, Rafael

Global companies that experienced extensive waterfall phased plans are trying to improve their existing processes to expedite team engagement. Agile methodologies have become an acceptable path to follow because it comprises project management as part of its practices. Agile practices have been used with the objective of simplifying project control through simple processes, easy to update documentation and higher team iteration over exhaustive documentation, focusing rather on team continuous improvement and aiming to add value to business processes. The purpose of this chapter is to describe the experience of a global multinational company on transitioning from distributed and traditional to distributed and agile. This company has development centers across North America, South America and Asia. This chapter covers challenges faced by the project teams of two pilot projects, including strengths of using agile practices in a globally distributed environment and practical recommendations for similar endeavors.

UWB Tracking Software Development

NASA Technical Reports Server (NTRS)

Gross, Julia; Arndt, Dickey; Ngo, Phong; Phan, Chau; Dusl, John; Ni, Jianjun; Rafford, Melinda

2006-01-01

An Ultra-Wideband (UWB) two-cluster Angle of Arrival (AOA) tracking prototype system is currently being developed and tested at NASA Johnson Space Center for space exploration applications. This talk discusses the software development efforts for this UWB two-cluster AOA tracking system. The role the software plays in this system is to take waveform data from two UWB radio receivers as an input, feed this input into an AOA tracking algorithm, and generate the target position as an output. The architecture of the software (Input/Output Interface and Algorithm Core) will be introduced in this talk. The development of this software has three phases. In Phase I, the software is mostly Matlab driven and calls C++ socket functions to provide the communication links to the radios. This is beneficial in the early stage when it is necessary to frequently test changes in the algorithm. Phase II of the development is to have the software mostly C++ driven and call a Matlab function for the AOA tracking algorithm. This is beneficial in order to send the tracking results to other systems and also to improve the tracking update rate of the system. The third phase is part of future work and is to have the software completely C++ driven with a graphics user interface. This software design enables the fine resolution tracking of the UWB two-cluster AOA tracking system.

Search of GRB with AGILE Minicalorimeter

NASA Astrophysics Data System (ADS)

Fuschino, F.; Labanti, C.; Galli, M.; Marisaldi, M.; Bulgarelli, A.; Gianotti, F.; Trifoglio, M.; Argan, A.; Del Monte, E.; Donnarumma, I.; Feroci, M.; Lazzarotto, F.; Pacciani, L.; Tavani, M.; Trois, A.

2008-04-01

AGILE, the small scientific mission of the Italian Space Agency devoted to Hard-X and Gamma-ray astrophysics, was successfully launched on April 23, 2007. The AGILE payload is composed of a tungsten-silicon tracker (ST), operating in the gamma-ray energy range 30 MeV 50 GeV; Super-AGILE, an X-ray imager operating in the energy range 15 45 keV; the Minicalorimeter (MCAL) and an Anticoincidence shield. MCAL is a detector of about 1400 cm2 sensitive in the range 0.3 200 MeV, that can be used both as a slave of the ST to contribute to the AGILE Gamma Ray imaging Detector (GRID operative mode) and autonomously for detection of transient events (BURST operative mode). MCAL is made of 30 CsI(Tl) bar-shaped scintillation detectors with photodiode readout at both ends, arranged in two orthogonal layers. Energy and position of interaction can be derived from a proper composition of the signals readout at the bar's ends, absolute time tagging can be achieved with a μs resolution. The Burst logic deals with various rate-meters on different time scales, energy bands, and MCAL spatial zones. Different algorithms can be chosen for Burst triggering considering also the contribution of other detectors like Super AGILE. In this paper the various trigger logic will be reviewed as well as their on-ground test performed with a dedicated experimental setup.

Computer-Aided Software Engineering - An approach to real-time software development

NASA Technical Reports Server (NTRS)

Walker, Carrie K.; Turkovich, John J.

1989-01-01

A new software engineering discipline is Computer-Aided Software Engineering (CASE), a technology aimed at automating the software development process. This paper explores the development of CASE technology, particularly in the area of real-time/scientific/engineering software, and a history of CASE is given. The proposed software development environment for the Advanced Launch System (ALS CASE) is described as an example of an advanced software development system for real-time/scientific/engineering (RT/SE) software. The Automated Programming Subsystem of ALS CASE automatically generates executable code and corresponding documentation from a suitably formatted specification of the software requirements. Software requirements are interactively specified in the form of engineering block diagrams. Several demonstrations of the Automated Programming Subsystem are discussed.

Compact, Automated, Frequency-Agile Microspectrofluorimeter

NASA Technical Reports Server (NTRS)

Fernandez, Salvador M.; Guignon, Ernest F.

1995-01-01

Compact, reliable, rugged, automated cell-culture and frequency-agile microspectrofluorimetric apparatus developed to perform experiments involving photometric imaging observations of single live cells. In original application, apparatus operates mostly unattended aboard spacecraft; potential terrestrial applications include automated or semiautomated diagnosis of pathological tissues in clinical laboratories, biomedical instrumentation, monitoring of biological process streams, and portable instrumentation for testing biological conditions in various environments. Offers obvious advantages over present laboratory instrumentation.

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.

Agility assessment using fuzzy logic approach: a case of healthcare dispensary.

PubMed

Suresh, M; Patri, Rojalin

2017-06-09

Agile concepts are not only beneficial for manufacturing sector but also for service sector such as healthcare. However, assessment of agility has been predominantly done in manufacturing enterprises. This study demonstrates a means to measure agility of a healthcare organization by assessing agility of a university dispensary. Its contribution to the knowledge base is twofold. First, it proposes a means to measure the agility of a healthcare organization and second, it identifies the attributes that prevent agile performance and outlines the suggestive measure to enhance its agile capabilities. A case study approach has been adopted and fuzzy logic has been employed to measure the agility of the case dispensary. At first, the measures of assessment which include four enablers, fifteen criteria and forty-five attributes have been identified from the literature and rated by the experts indicating the importance of the measures in the assessment. Then, the case dispensary has been assessed on those measures by collecting observed performance rating from decision makers. At last, Fuzzy logic has been applied on the performance rating data to analyze and interpret the agile capability of the dispensary. The findings suggest that transparent information flow, adequate salary and bonuses for caregivers, reading error in medical descriptions, in house/nearby pathology laboratory services, technical up-gradation of dispensary equipments and facilities, minimization of patient throughput time and adequate training programme for safety practices are the attributes that weakens agile capability of the University dispensary. The current agility of the dispensary was found to be 'Agile' which is average in relation to the agility labels. Attributes such as transparent information flow, adequate salary and bonuses for caregivers, elimination of reading error in medical descriptions, in house/nearby pathology laboratory services, technical up-gradation of dispensary equipments

Automated Software Development Workstation (ASDW)

NASA Technical Reports Server (NTRS)

Fridge, Ernie

1990-01-01

Software development is a serious bottleneck in the construction of complex automated systems. An increase of the reuse of software designs and components has been viewed as a way to relieve this bottleneck. One approach to achieving software reusability is through the development and use of software parts composition systems. A software parts composition system is a software development environment comprised of a parts description language for modeling parts and their interfaces, a catalog of existing parts, a composition editor that aids a user in the specification of a new application from existing parts, and a code generator that takes a specification and generates an implementation of a new application in a target language. The Automated Software Development Workstation (ASDW) is an expert system shell that provides the capabilities required to develop and manipulate these software parts composition systems. The ASDW is now in Beta testing at the Johnson Space Center. Future work centers on responding to user feedback for capability and usability enhancement, expanding the scope of the software lifecycle that is covered, and in providing solutions to handling very large libraries of reusable components.

Safety Characteristics in System Application of Software for Human Rated Exploration Missions for the 8th IAASS Conference

NASA Technical Reports Server (NTRS)

Mango, Edward J.

2016-01-01

NASA and its industry and international partners are embarking on a bold and inspiring development effort to design and build an exploration class space system. The space system is made up of the Orion system, the Space Launch System (SLS) and the Ground Systems Development and Operations (GSDO) system. All are highly coupled together and dependent on each other for the combined safety of the space system. A key area of system safety focus needs to be in the ground and flight application software system (GFAS). In the development, certification and operations of GFAS, there are a series of safety characteristics that define the approach to ensure mission success. This paper will explore and examine the safety characteristics of the GFAS development. The GFAS system integrates the flight software packages of the Orion and SLS with the ground systems and launch countdown sequencers through the 'agile' software development process. A unique approach is needed to develop the GFAS project capabilities within this agile process. NASA has defined the software development process through a set of standards. The standards were written during the infancy of the so-called industry 'agile development' movement and must be tailored to adapt to the highly integrated environment of human exploration systems. Safety of the space systems and the eventual crew on board is paramount during the preparation of the exploration flight systems. A series of software safety characteristics have been incorporated into the development and certification efforts to ensure readiness for use and compatibility with the space systems. Three underlining factors in the exploration architecture require the GFAS system to be unique in its approach to ensure safety for the space systems, both the flight as well as the ground systems. The first are the missions themselves, which are exploration in nature, and go far beyond the comfort of low Earth orbit operations. The second is the current exploration

A Review of Agile and Lean Manufacturing as Issues in Selected International and National Research and Development Programs and Roadmaps

ERIC Educational Resources Information Center

Castro, Helio; Putnik, Goran D.; Shah, Vaibhav

2012-01-01

Purpose: The aim of this paper is to analyze international and national research and development (R&D) programs and roadmaps for the manufacturing sector, presenting how agile and lean manufacturing models are addressed in these programs. Design/methodology/approach: In this review, several manufacturing research and development programs and…

Results of an Experimental Exploration of Advanced Automated Geospatial Tools: Agility in Complex Planning

DTIC Science & Technology

2009-06-01

AUTOMATED GEOSPATIAL TOOLS : AGILITY IN COMPLEX PLANNING Primary Topic: Track 5 – Experimentation and Analysis Walter A. Powell [STUDENT] - GMU...TITLE AND SUBTITLE Results of an Experimental Exploration of Advanced Automated Geospatial Tools : Agility in Complex Planning 5a. CONTRACT NUMBER...Std Z39-18 Abstract Typically, the development of tools and systems for the military is requirement driven; systems are developed to meet

Laterality and performance of agility-trained dogs.

PubMed

Siniscalchi, Marcello; Bertino, Daniele; Quaranta, Angelo

2014-01-01

Correlations between lateralised behaviour and performance were investigated in 19 agility-trained dogs (Canis familiaris) by scoring paw preference to hold a food object and relating it to performance during typical agility obstacles (jump/A-frame and weave poles). In addition, because recent behavioural studies reported that visual stimuli of emotional valence presented to one visual hemifield at a time affect visually guided motor responses in dogs, the possibility that the position of the owner respectively in the left and in the right canine visual hemifield might be associated with quality of performance during agility was considered. Dogs' temperament was also measured by an owner-rated questionnaire. The most relevant finding was that agility-trained dogs displayed longer latencies to complete the obstacles with the owner located in their left visual hemifield compared to the right. Interestingly, the results showed that this phenomenon was significantly linked to both dogs' trainability and the strength of paw preference.

[Reporting echocardiography exams with the G8-Cardio ANMCO software].

PubMed

Badano, L P; Marchesini, A; Pizzuti, A; Mantero, A; Cianflone, D; Neri, E; Caira, P; Tubaro, M

2001-03-01

The availability of a common computerized program for echocardiographic study archiving and reporting at national and/or international level could make it possible to standardize the echo reports of different echocardiographic laboratories, and to use the wealth of data thus obtainable with echocardiography, and to exploit its capillary territorial distribution, with the aim of collecting echocardiographic data in a standard format for epidemiological, scientific and administrative purposes. To develop such a software, an ad hoc joint National Association of Hospital Cardiologists and Italian Society of Echocardiography task force worked in conjunction with the Italian Branch of Agilent Technologies to standardize the phraseology of accepted echocardiographic terms and of the quantitative parameters derived from transthoracic and transesophageal echocardiographic examination at rest as well as during exercise and pharmacological stress, and to develop an ad hoc software. This echocardiographic study archiving and reporting program is part of the whole G8-Cardio ANMCO software developed to computerize the whole cardiological chart. The software has been developed by Agilent Technologies to provide a fast, easy-access and easy to use report generator for the non-computer specialist using DBMS Oracle 7.3 database and Power Builder 5.0 to develop a user-friendly interface. The number of qualitative and quantitative variables contained in the program is 733 for echocardiography at rest, while it depends on the stressor and on the length of the examination for the stress echo (dipyridamole 214-384, dobutamine 236-406, exercise 198-392). The program was tested and refined in our laboratory between November 1999 and May 2000. During this time period, 291 resting and 56 stress echocardiographic studies were reported and recorded in a database. On average, each resting echocardiographic study lasting 10 +/- 4 (range 5-17) min was recorded using 50 +/- 11 (range 33

Agile Objects

ERIC Educational Resources Information Center

German, Senta; Harris, Jim

2017-01-01

In this article, the authors argue that the art-historical canon, however it is construed, has little relevance to the selection of objects for museum-based teaching. Their contention is that all objects are fundamentally agile and capable of interrogation from any number of disciplinary standpoints, and that the canon of museum education,…

Payload software technology: Software technology development plan

NASA Technical Reports Server (NTRS)

1977-01-01

Programmatic requirements for the advancement of software technology are identified for meeting the space flight requirements in the 1980 to 1990 time period. The development items are described, and software technology item derivation worksheets are presented along with the cost/time/priority assessments.

The agile alert system for gamma-ray transients

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

Bulgarelli, A.; Trifoglio, M.; Gianotti, F.

2014-01-20

In recent years, a new generation of space missions has offered great opportunities for discovery in high-energy astrophysics. In this article we focus on the scientific operations of the Gamma-Ray Imaging Detector (GRID) on board the AGILE space mission. AGILE-GRID, sensitive in the energy range of 30 MeV-30 GeV, has detected many γ-ray transients of both galactic and extragalactic origin. This work presents the AGILE innovative approach to fast γ-ray transient detection, which is a challenging task and a crucial part of the AGILE scientific program. The goals are to describe (1) the AGILE Gamma-Ray Alert System, (2) a newmore » algorithm for blind search identification of transients within a short processing time, (3) the AGILE procedure for γ-ray transient alert management, and (4) the likelihood of ratio tests that are necessary to evaluate the post-trial statistical significance of the results. Special algorithms and an optimized sequence of tasks are necessary to reach our goal. Data are automatically analyzed at every orbital downlink by an alert pipeline operating on different timescales. As proper flux thresholds are exceeded, alerts are automatically generated and sent as SMS messages to cellular telephones, via e-mail, and via push notifications from an application for smartphones and tablets. These alerts are crosschecked with the results of two pipelines, and a manual analysis is performed. Being a small scientific-class mission, AGILE is characterized by optimization of both scientific analysis and ground-segment resources. The system is capable of generating alerts within two to three hours of a data downlink, an unprecedented reaction time in γ-ray astrophysics.« less

The AGILE Alert System for Gamma-Ray Transients

NASA Astrophysics Data System (ADS)

Bulgarelli, A.; Trifoglio, M.; Gianotti, F.; Tavani, M.; Parmiggiani, N.; Fioretti, V.; Chen, A. W.; Vercellone, S.; Pittori, C.; Verrecchia, F.; Lucarelli, F.; Santolamazza, P.; Fanari, G.; Giommi, P.; Beneventano, D.; Argan, A.; Trois, A.; Scalise, E.; Longo, F.; Pellizzoni, A.; Pucella, G.; Colafrancesco, S.; Conforti, V.; Tempesta, P.; Cerone, M.; Sabatini, P.; Annoni, G.; Valentini, G.; Salotti, L.

2014-01-01

In recent years, a new generation of space missions has offered great opportunities for discovery in high-energy astrophysics. In this article we focus on the scientific operations of the Gamma-Ray Imaging Detector (GRID) on board the AGILE space mission. AGILE-GRID, sensitive in the energy range of 30 MeV-30 GeV, has detected many γ-ray transients of both galactic and extragalactic origin. This work presents the AGILE innovative approach to fast γ-ray transient detection, which is a challenging task and a crucial part of the AGILE scientific program. The goals are to describe (1) the AGILE Gamma-Ray Alert System, (2) a new algorithm for blind search identification of transients within a short processing time, (3) the AGILE procedure for γ-ray transient alert management, and (4) the likelihood of ratio tests that are necessary to evaluate the post-trial statistical significance of the results. Special algorithms and an optimized sequence of tasks are necessary to reach our goal. Data are automatically analyzed at every orbital downlink by an alert pipeline operating on different timescales. As proper flux thresholds are exceeded, alerts are automatically generated and sent as SMS messages to cellular telephones, via e-mail, and via push notifications from an application for smartphones and tablets. These alerts are crosschecked with the results of two pipelines, and a manual analysis is performed. Being a small scientific-class mission, AGILE is characterized by optimization of both scientific analysis and ground-segment resources. The system is capable of generating alerts within two to three hours of a data downlink, an unprecedented reaction time in γ-ray astrophysics.

Agility in Team Sports: Testing, Training and Factors Affecting Performance.

PubMed

Paul, Darren J; Gabbett, Tim J; Nassis, George P

2016-03-01

Agility is an important characteristic of team sports athletes. There is a growing interest in the factors that influence agility performance as well as appropriate testing protocols and training strategies to assess and improve this quality. The objective of this systematic review was to (1) evaluate the reliability and validity of agility tests in team sports, (2) detail factors that may influence agility performance, and (3) identify the effects of different interventions on agility performance. The review was undertaken in accordance with the Preferred Reporting Items for Systematic Reviews and Meta-Analyses guidelines. We conducted a search of PubMed, Google Scholar, Science Direct, and SPORTDiscus databases. We assessed the methodological quality of intervention studies using a customized checklist of assessment criteria. Intraclass correlation coefficient values were 0.80-0.91, 0.10-0.81, and 0.81-0.99 for test time using light, video, and human stimuli. A low-level reliability was reported for youth athletes using the video stimulus (0.10-0.30). Higher-level participants were shown to be, on average, 7.5% faster than their lower level counterparts. Reaction time and accuracy, foot placement, and in-line lunge movement have been shown to be related to agility performance. The contribution of strength remains unclear. Efficacy of interventions on agility performance ranged from 1% (vibration training) to 7.5% (small-sided games training). Agility tests generally offer good reliability, although this may be compromised in younger participants responding to various scenarios. A human and/or video stimulus seems the most appropriate method to discriminate between standard of playing ability. Decision-making and perceptual factors are often propositioned as discriminant factors; however, the underlying mechanisms are relatively unknown. Research has focused predominantly on the physical element of agility. Small-sided games and video training may offer effective

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.

CT-assisted agile manufacturing

NASA Astrophysics Data System (ADS)

Stanley, James H.; Yancey, Robert N.

1996-11-01

The next century will witness at least two great revolutions in the way goods are produced. First, workers will use the medium of virtual reality in all aspects of marketing, research, development, prototyping, manufacturing, sales and service. Second, market forces will drive manufacturing towards small-lot production and just-in-time delivery. Already, we can discern the merging of these megatrends into what some are calling agile manufacturing. Under this new paradigm, parts and processes will be designed and engineered within the mind of a computer, tooled and manufactured by the offspring of today's rapid prototyping equipment, and evaluated for performance and reliability by advanced nondestructive evaluation (NDE) techniques and sophisticated computational models. Computed tomography (CT) is the premier example of an NDE method suitable for future agile manufacturing activities. It is the only modality that provides convenient access to the full suite of engineering data that users will need to avail themselves of computer- aided design, computer-aided manufacturing, and computer- aided engineering capabilities, as well as newly emerging reverse engineering, rapid prototyping and solid freeform fabrication technologies. As such, CT is assured a central, utilitarian role in future industrial operations. An overview of this exciting future for industrial CT is presented.

Planned and reactive agility performance in semiprofessional and amateur basketball players.

PubMed

Lockie, Robert G; Jeffriess, Matthew D; McGann, Tye S; Callaghan, Samuel J; Schultz, Adrian B

2014-09-01

Research indicates that planned and reactive agility are different athletic skills. These skills have not been adequately assessed in male basketball players. To define whether 10-m-sprint performance and planned and reactive agility measured by the Y-shaped agility test can discriminate between semiprofessional and amateur basketball players. Ten semiprofessional and 10 amateur basketball players completed 10-m sprints and planned- and reactive-agility tests. The Y-shaped agility test involved subjects sprinting 5 m through a trigger timing gate, followed by a 45° cut and 5-m sprint to the left or right through a target gate. In the planned condition, subjects knew the cut direction. For reactive trials, subjects visually scanned to find the illuminated gate. A 1-way analysis of variance (P < .05) determined between-groups differences. Data were pooled (N = 20) for a correlation analysis (P < .05). The reactive tests differentiated between the groups; semiprofessional players were 6% faster for the reactive left (P = .036) and right (P = .029) cuts. The strongest correlations were between the 10-m sprints and planned-agility tests (r = .590-.860). The reactive left cut did not correlate with the planned tests. The reactive right cut moderately correlated with the 10-m sprint and planned right cut (r = .487-.485). The results reemphasized that planned and reactive agility are separate physical qualities. Reactive agility discriminated between the semiprofessional and amateur basketball players; planned agility did not. To distinguish between male basketball players of different ability levels, agility tests should include a perceptual and decision-making component.

The AGILE Mission and Gamma-Ray Bursts

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

Longo, Francesco; INFN, section of Trieste; Tavani, M.

2007-05-01

The AGILE Mission will explore the gamma-ray Universe with a very innovative instrument combining for the first time a gamma-ray imager and a hard X-ray imager. AGILE will be operational at the beginning of 2007 and it will provide crucial data for the study of Active Galactic Nuclei, Gamma-Ray Bursts, unidentified gamma-ray sources, Galactic compact objects, supernova remnants, TeV sources, and fundamental physics by microsecond timing. The AGILE instrument is designed to simultaneously detect and image photons in the 30 MeV - 50 GeV and 15 - 45 keV energy bands with excellent imaging and timing capabilities, and a largemore » field of view covering {approx} 1/5 of the entire sky at energies above 30 MeV. A CsI calorimeter is capable of GRB triggering in the energy band 0.3-50 MeV. The broadband detection of GRBs and the study of implications for particle acceleration and high energy emission are primary goals of the mission. AGILE can image GRBs with 2-3 arcminute error boxes in the hard X-ray range, and provide broadband photon-by photon detection in the 15-45 keV, 03-50 MeV, and 30 MeV-30 GeV energy ranges. Microsecond on-board photon tagging and a {approx} 100 microsecond gamma-ray detection deadtime will be crucial for fast GRB timing. On-board calculated GRB coordinates and energy fluxes will be quickly transmitted to the ground by an ORBCOMM transceiver. AGILE is now (January 2007) undergoing final satellite integration and testing. The PLS V launch is planned in spring 2007. AGILE is then foreseen to be fully operational during the summer of 2007.« less

Gender-specific influences of balance, speed, and power on agility performance.

PubMed

Sekulic, Damir; Spasic, Miodrag; Mirkov, Dragan; Cavar, Mile; Sattler, Tine

2013-03-01

The quick change of direction (i.e., agility) is an important athletic ability in numerous sports. Because of the diverse and therefore hardly predictable manifestations of agility in sports, studies noted that the improvement in speed, power, and balance should result in an improvement of agility. However, there is evident lack of data regarding the influence of potential predictors on different agility manifestations. The aim of this study was to determine the gender-specific influence of speed, power, and balance on different agility tests. A total of 32 college-aged male athletes and 31 college-aged female athletes (age 20.02 ± 1.89 years) participated in this study. The subjects were mostly involved in team sports (soccer, team handball, basketball, and volleyball; 80% of men, and 75% of women), martial arts, gymnastics, and dance. Anthropometric variables consisted of body height, body weight, and the body mass index. Five agility tests were used: a t-test (T-TEST), zig-zag test, 20-yard shuttle test, agility test with a 180-degree turn, and forward-backward running agility test (FWDBWD). Other tests included 1 jumping ability power test (squat jump, SQJ), 2 balance tests to determine the overall stability index and an overall limit of stability score (both measured by Biodex Balance System), and 2 running speed tests using a straight sprint for 10 and 20 m (S10 and S20, respectively). A reliability analysis showed that all the agility tests were reliable. Multiple regression and correlation analysis found speed and power (among women), and balance (among men), as most significant predictors of agility. The highest Pearson's correlation in both genders is found between the results of the FWDBWD and S10M tests (0.77 and 0.81 for men and women, respectively; p < 0.05). Power, measured using the SQJ, is significantly (p < 0.05) related to FWDBWD and T-TEST results but only for women (-0.44; -0.41). The balance measures were significantly related to the agility

Applying Agile Principles in Teaching Undergraduate Information Technology Project Management

ERIC Educational Resources Information Center

Budu, Joseph

2018-01-01

This article describes how the traditional teaching and learning activities over the years have been challenged to be agile--easily adaptable to changing classroom conditions. Despite this new phenomenon, there is a perceived paucity of agile-in-teaching research. Available studies neither focus on the use of agile principles beyond delivering…

The Earth System Documentation (ES-DOC) Software Process

NASA Astrophysics Data System (ADS)

Greenslade, M. A.; Murphy, S.; Treshansky, A.; DeLuca, C.; Guilyardi, E.; Denvil, S.

2013-12-01

Earth System Documentation (ES-DOC) is an international project supplying high-quality tools & services in support of earth system documentation creation, analysis and dissemination. It is nurturing a sustainable standards based documentation eco-system that aims to become an integral part of the next generation of exa-scale dataset archives. ES-DOC leverages open source software, and applies a software development methodology that places end-user narratives at the heart of all it does. ES-DOC has initially focused upon nurturing the Earth System Model (ESM) documentation eco-system and currently supporting the following projects: * Coupled Model Inter-comparison Project Phase 5 (CMIP5); * Dynamical Core Model Inter-comparison Project (DCMIP); * National Climate Predictions and Projections Platforms Quantitative Evaluation of Downscaling Workshop. This talk will demonstrate that ES-DOC implements a relatively mature software development process. Taking a pragmatic Agile process as inspiration, ES-DOC: * Iteratively develops and releases working software; * Captures user requirements via a narrative based approach; * Uses online collaboration tools (e.g. Earth System CoG) to manage progress; * Prototypes applications to validate their feasibility; * Leverages meta-programming techniques where appropriate; * Automates testing whenever sensibly feasible; * Streamlines complex deployments to a single command; * Extensively leverages GitHub and Pivotal Tracker; * Enforces strict separation of the UI from underlying API's; * Conducts code reviews.

SU-E-T-610: Comparison of Treatment Times Between the MLCi and Agility Multileaf Collimators

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

Ramsey, C; Bowling, J

2014-06-01

Purpose: The Agility is a new 160-leaf MLC developed by Elekta for use in their Infinity and Versa HD linacs. As compared to the MLCi, the Agility increased the maximum leaf speed from 2 cm/s to 3.5 cm/s, and the maximum primary collimator speed from 1.5 cm/s to 9.0 cm/s. The purpose of this study was to determine if the Agility MLC resulted in improved plan quality and/or shorter treatment times. Methods: An Elekta Infinity that was originally equipped with a 80 leaf MLCi was upgraded to an 160 leaf Agility. Treatment plan quality was evaluated using the Pinnacle planningmore » system with SmartArc. Optimization was performed once for the MLCi and once for the Agility beam models using the same optimization parameters and the same number of iterations. Patient treatment times were measured for all IMRT, VMAT, and SBRT patients treated on the Infinity with the MLCi and Agility MLCs. Treatment times were extracted from the EMR and measured from when the patient first walked into the treatment room until exiting the treatment room. Results: 11,380 delivery times were measured for patients treated with the MLCi, and 1,827 measurements have been made for the Agility MLC. The average treatment times were 19.1 minutes for the MLCi and 20.8 minutes for the Agility. Using a t-test analysis, there was no difference between the two groups (t = 0.22). The dose differences between patients planned with the MLCi and the Agility MLC were minimal. For example, the dose difference for the PTV, GTV, and cord for a head and neck patient planned using Pinnacle were effectively equivalent. However, the dose to the parotid glands was slightly worse with the Agility MLC. Conclusion: There was no statistical difference in treatment time, or any significant dosimetric difference between the Agility MLC and the MLCi.« less

A Quantitative Study of Global Software Development Teams, Requirements, and Software Projects

ERIC Educational Resources Information Center

Parker, Linda L.

2016-01-01

The study explored the relationship between global software development teams, effective software requirements, and stakeholders' perception of successful software development projects within the field of information technology management. It examined the critical relationship between Global Software Development (GSD) teams creating effective…

The impact of flying qualities on helicopter operational agility

NASA Technical Reports Server (NTRS)

Padfield, Gareth D.; Lappos, Nick; Hodgkinson, John

1993-01-01

Flying qualities standards are formally set to ensure safe flight and therefore reflect minimum, rather than optimum, requirements. Agility is a flying quality but relates to operations at high, if not maximum, performance. While the quality metrics and test procedures for flying, as covered for example in ADS33C, may provide an adequate structure to encompass agility, they do not currently address flight at high performance. This is also true in the fixed-wing world and a current concern in both communities is the absence of substantiated agility criteria and possible conflicts between flying qualities and high performance. AGARD is sponsoring a working group (WG19) title 'Operational Agility' that deals with these and a range of related issues. This paper is condensed from contributions by the three authors to WG19, relating to flying qualities. Novel perspectives on the subject are presented including the agility factor, that quantifies performance margins in flying qualities terms; a new parameter, based on maneuver acceleration is introduced as a potential candidate for defining upper limits to flying qualities. Finally, a probabilistic analysis of pilot handling qualities ratings is presented that suggests a powerful relationship between inherent airframe flying qualities and operational agility.

Software Development as Music Education Research

ERIC Educational Resources Information Center

Brown, Andrew R.

2007-01-01

This paper discusses how software development can be used as a method for music education research. It explains how software development can externalize ideas, stimulate action and reflection, and provide evidence to support the educative value of new software-based experiences. Parallels between the interactive software development process and…

Software for MR image overlay guided needle insertions: the clinical translation process

NASA Astrophysics Data System (ADS)

Ungi, Tamas; U-Thainual, Paweena; Fritz, Jan; Iordachita, Iulian I.; Flammang, Aaron J.; Carrino, John A.; Fichtinger, Gabor

2013-03-01

PURPOSE: Needle guidance software using augmented reality image overlay was translated from the experimental phase to support preclinical and clinical studies. Major functional and structural changes were needed to meet clinical requirements. We present the process applied to fulfill these requirements, and selected features that may be applied in the translational phase of other image-guided surgical navigation systems. METHODS: We used an agile software development process for rapid adaptation to unforeseen clinical requests. The process is based on iterations of operating room test sessions, feedback discussions, and software development sprints. The open-source application framework of 3D Slicer and the NA-MIC kit provided sufficient flexibility and stable software foundations for this work. RESULTS: All requirements were addressed in a process with 19 operating room test iterations. Most features developed in this phase were related to workflow simplification and operator feedback. CONCLUSION: Efficient and affordable modifications were facilitated by an open source application framework and frequent clinical feedback sessions. Results of cadaver experiments show that software requirements were successfully solved after a limited number of operating room tests.

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.

The Effects of a 6-Week Plyometric Training Program on Agility

PubMed Central

Miller, Michael G.; Herniman, Jeremy J.; Ricard, Mark D.; Cheatham, Christopher C.; Michael, Timothy J.

2006-01-01

The purpose of the study was to determine if six weeks of plyometric training can improve an athlete's agility. Subjects were divided into two groups, a plyometric training and a control group. The plyometric training group performed in a six week plyometric training program and the control group did not perform any plyometric training techniques. All subjects participated in two agility tests: T-test and Illinois Agility Test, and a force plate test for ground reaction times both pre and post testing. Univariate ANCOVAs were conducted to analyze the change scores (post - pre) in the independent variables by group (training or control) with pre scores as covariates. The Univariate ANCOVA revealed a significant group effect F2,26 = 25.42, p=0.0000 for the T-test agility measure. For the Illinois Agility test, a significant group effect F2,26 = 27.24, p = 0.000 was also found. The plyometric training group had quicker posttest times compared to the control group for the agility tests. A significant group effect F2,26 = 7.81, p = 0.002 was found for the Force Plate test. The plyometric training group reduced time on the ground on the posttest compared to the control group. The results of this study show that plyometric training can be an effective training technique to improve an athlete's agility. Key Points Plyometric training can enhance agility of athletes. 6 weeks of plyometric training is sufficient to see agility results. Ground reaction times are decreased with plyometric training PMID:24353464

Towards Archetypes-Based Software Development

NASA Astrophysics Data System (ADS)

Piho, Gunnar; Roost, Mart; Perkins, David; Tepandi, Jaak

We present a framework for the archetypes based engineering of domains, requirements and software (Archetypes-Based Software Development, ABD). An archetype is defined as a primordial object that occurs consistently and universally in business domains and in business software systems. An archetype pattern is a collaboration of archetypes. Archetypes and archetype patterns are used to capture conceptual information into domain specific models that are utilized by ABD. The focus of ABD is on software factories - family-based development artefacts (domain specific languages, patterns, frameworks, tools, micro processes, and others) that can be used to build the family members. We demonstrate the usage of ABD for developing laboratory information management system (LIMS) software for the Clinical and Biomedical Proteomics Group, at the Leeds Institute of Molecular Medicine, University of Leeds.

Application of side-oblique image-motion blur correction to Kuaizhou-1 agile optical images.

PubMed

Sun, Tao; Long, Hui; Liu, Bao-Cheng; Li, Ying

2016-03-21

Given the recent development of agile optical satellites for rapid-response land observation, side-oblique image-motion (SOIM) detection and blur correction have become increasingly essential for improving the radiometric quality of side-oblique images. The Chinese small-scale agile mapping satellite Kuaizhou-1 (KZ-1) was developed by the Harbin Institute of Technology and launched for multiple emergency applications. Like other agile satellites, KZ-1 suffers from SOIM blur, particularly in captured images with large side-oblique angles. SOIM detection and blur correction are critical for improving the image radiometric accuracy. This study proposes a SOIM restoration method based on segmental point spread function detection. The segment region width is determined by satellite parameters such as speed, height, integration time, and side-oblique angle. The corresponding algorithms and a matrix form are proposed for SOIM blur correction. Radiometric objective evaluation indices are used to assess the restoration quality. Beijing regional images from KZ-1 are used as experimental data. The radiometric quality is found to increase greatly after SOIM correction. Thus, the proposed method effectively corrects image motion for KZ-1 agile optical satellites.

Insights into software development in Japan

NASA Technical Reports Server (NTRS)

Duvall, Lorraine M.

1992-01-01

The interdependence of the U.S.-Japanese economies makes it imperative that we in the United States understand how business and technology developments take place in Japan. We can gain insight into these developments in software engineering by studying the context in which Japanese software is developed, the practices that are used, the problems encountered, the setting surrounding these problems, and the resolution of these problems. Context includes the technological and sociological characteristics of the software development environment, the software processes applied, personnel involved in the development process, and the corporate and social culture surrounding the development. Presented in this paper is a summary of results of a study that addresses these issues. Data for this study was collected during a three month visit to Japan where the author interviewed 20 software managers representing nine companies involved in developing software in Japan. These data are compared to similar data from the United States in which 12 managers from five companies were interviewed.

Creating IT agility.

PubMed

Glaser, John

2008-04-01

Seven steps healthcare organizations can take to improve IT agility are: Pay attention to the capabilities of IT applications. Establish short project phases. Stage the release of capital and new IT positions. Cross-train IT staff. Adopt technology standards. Shorten IT plan time horizons. Align IT with organizational strategies and priorities.

Happy software developers solve problems better: psychological measurements in empirical software engineering.

PubMed

Graziotin, Daniel; Wang, Xiaofeng; Abrahamsson, Pekka

2014-01-01

For more than thirty years, it has been claimed that a way to improve software developers' productivity and software quality is to focus on people and to provide incentives to make developers satisfied and happy. This claim has rarely been verified in software engineering research, which faces an additional challenge in comparison to more traditional engineering fields: software development is an intellectual activity and is dominated by often-neglected human factors (called human aspects in software engineering research). Among the many skills required for software development, developers must possess high analytical problem-solving skills and creativity for the software construction process. According to psychology research, affective states-emotions and moods-deeply influence the cognitive processing abilities and performance of workers, including creativity and analytical problem solving. Nonetheless, little research has investigated the correlation between the affective states, creativity, and analytical problem-solving performance of programmers. This article echoes the call to employ psychological measurements in software engineering research. We report a study with 42 participants to investigate the relationship between the affective states, creativity, and analytical problem-solving skills of software developers. The results offer support for the claim that happy developers are indeed better problem solvers in terms of their analytical abilities. The following contributions are made by this study: (1) providing a better understanding of the impact of affective states on the creativity and analytical problem-solving capacities of developers, (2) introducing and validating psychological measurements, theories, and concepts of affective states, creativity, and analytical-problem-solving skills in empirical software engineering, and (3) raising the need for studying the human factors of software engineering by employing a multidisciplinary viewpoint.

Relationship between agility and lower limb muscle strength, targeting university badminton players.

PubMed

Sonoda, Takuya; Tashiro, Yuto; Suzuki, Yusuke; Kajiwara, Yu; Zeidan, Hala; Yokota, Yuki; Kawagoe, Mirei; Nakayama, Yasuaki; Bito, Tsubasa; Shimoura, Kanako; Tatsumi, Masataka; Nakai, Kengo; Nishida, Yuichi; Yoshimi, Soyoka; Aoyama, Tomoki

2018-02-01

[Purpose] Targeting university badminton players, this study investigated the relationship between agility, which is associated with performance in badminton, and lower limb muscle strength, and examined which muscles influence agility. [Subjects and Methods] A total of 23 male university badminton players were evaluated for side-shuffle test scores and lower limb strength. The relationships between agility, lower limb strength, and duration of experience playing badminton were evaluated using a correlation analysis. Moreover, the relationship between agility and lower limb strength was evaluated by partial correlation analysis, adjusting for the effects of experience of each badminton player. [Results] The agility score correlated with hip extension and ankle plantar flexion strength, with adjustment for badminton experience. [Conclusion] This study suggests that hip extension training and improvement in ankle plantar flexion strength may improve agility.

Visual preference in a human-reared agile gibbon (Hylobates agilis).

PubMed

Tanaka, Masayuki; Uchikoshi, Makiko

2010-01-01

Visual preference was evaluated in a male agile gibbon. The subject was raised by humans immediately after birth, but lived with his biological family from one year of age. Visual preference was assessed using a free-choice task in which five or six photographs of different primate species, including humans, were presented on a touch-sensitive screen. The subject touched one of them. Food rewards were delivered irrespective of the subject's responses. We prepared two types of stimulus sets. With set 1, the subject touched photographs of humans more frequently than those of other species, recalling previous findings in human-reared chimpanzees. With set 2, photographs of nine species of gibbons were presented. Chimpanzees touched photographs of white-handed gibbons more than those of other gibbon species. The gibbon subject initially touched photographs of agile gibbons more than white-handed gibbons, but after one and two years his choice patterns resembled the chimpanzees'. The results suggest that, as in chimpanzees, visual preferences of agile gibbons are not genetically programmed but develop through social experience during infancy.

Architecture-Centric Development in Globally Distributed Projects

NASA Astrophysics Data System (ADS)

Sauer, Joachim

In this chapter architecture-centric development is proposed as a means to strengthen the cohesion of distributed teams and to tackle challenges due to geographical and temporal distances and the clash of different cultures. A shared software architecture serves as blueprint for all activities in the development process and ties them together. Architecture-centric development thus provides a plan for task allocation, facilitates the cooperation of globally distributed developers, and enables continuous integration reaching across distributed teams. Advice is also provided for software architects who work with distributed teams in an agile manner.

Parallelization of fine-scale computation in Agile Multiscale Modelling Methodology

NASA Astrophysics Data System (ADS)

Macioł, Piotr; Michalik, Kazimierz

2016-10-01

Nowadays, multiscale modelling of material behavior is an extensively developed area. An important obstacle against its wide application is high computational demands. Among others, the parallelization of multiscale computations is a promising solution. Heterogeneous multiscale models are good candidates for parallelization, since communication between sub-models is limited. In this paper, the possibility of parallelization of multiscale models based on Agile Multiscale Methodology framework is discussed. A sequential, FEM based macroscopic model has been combined with concurrently computed fine-scale models, employing a MatCalc thermodynamic simulator. The main issues, being investigated in this work are: (i) the speed-up of multiscale models with special focus on fine-scale computations and (ii) on decreasing the quality of computations enforced by parallel execution. Speed-up has been evaluated on the basis of Amdahl's law equations. The problem of `delay error', rising from the parallel execution of fine scale sub-models, controlled by the sequential macroscopic sub-model is discussed. Some technical aspects of combining third-party commercial modelling software with an in-house multiscale framework and a MPI library are also discussed.

Knowledge Sharing through Pair Programming in Learning Environments: An Empirical Study

ERIC Educational Resources Information Center

Kavitha, R. K.; Ahmed, M. S.

2015-01-01

Agile software development is an iterative and incremental methodology, where solutions evolve from self-organizing, cross-functional teams. Pair programming is a type of agile software development technique where two programmers work together with one computer for developing software. This paper reports the results of the pair programming…

Development of a comprehensive software engineering environment

NASA Technical Reports Server (NTRS)

Hartrum, Thomas C.; Lamont, Gary B.

1987-01-01

The generation of a set of tools for software lifecycle is a recurring theme in the software engineering literature. The development of such tools and their integration into a software development environment is a difficult task because of the magnitude (number of variables) and the complexity (combinatorics) of the software lifecycle process. An initial development of a global approach was initiated in 1982 as the Software Development Workbench (SDW). Continuing efforts focus on tool development, tool integration, human interfacing, data dictionaries, and testing algorithms. Current efforts are emphasizing natural language interfaces, expert system software development associates and distributed environments with Ada as the target language. The current implementation of the SDW is on a VAX-11/780. Other software development tools are being networked through engineering workstations.

Project Success in Agile Development Software Projects

ERIC Educational Resources Information Center

Farlik, John T.

2016-01-01

Project success has multiple definitions in the scholarly literature. Research has shown that some scholars and practitioners define project success as the completion of a project within schedule and within budget. Others consider a successful project as one in which the customer is satisfied with the product. This quantitative study was conducted…

Exploring the possibility of modeling a genetic counseling guideline using agile methodology.

PubMed

Choi, Jeeyae

2013-01-01

Increased demand of genetic counseling services heightened the necessity of a computerized genetic counseling decision support system. In order to develop an effective and efficient computerized system, modeling of genetic counseling guideline is an essential step. Throughout this pilot study, Agile methodology with United Modeling Language (UML) was utilized to model a guideline. 13 tasks and 14 associated elements were extracted. Successfully constructed conceptual class and activity diagrams revealed that Agile methodology with UML was a suitable tool to modeling a genetic counseling guideline.

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.

Happy software developers solve problems better: psychological measurements in empirical software engineering

PubMed Central

Wang, Xiaofeng; Abrahamsson, Pekka

2014-01-01

For more than thirty years, it has been claimed that a way to improve software developers’ productivity and software quality is to focus on people and to provide incentives to make developers satisfied and happy. This claim has rarely been verified in software engineering research, which faces an additional challenge in comparison to more traditional engineering fields: software development is an intellectual activity and is dominated by often-neglected human factors (called human aspects in software engineering research). Among the many skills required for software development, developers must possess high analytical problem-solving skills and creativity for the software construction process. According to psychology research, affective states—emotions and moods—deeply influence the cognitive processing abilities and performance of workers, including creativity and analytical problem solving. Nonetheless, little research has investigated the correlation between the affective states, creativity, and analytical problem-solving performance of programmers. This article echoes the call to employ psychological measurements in software engineering research. We report a study with 42 participants to investigate the relationship between the affective states, creativity, and analytical problem-solving skills of software developers. The results offer support for the claim that happy developers are indeed better problem solvers in terms of their analytical abilities. The following contributions are made by this study: (1) providing a better understanding of the impact of affective states on the creativity and analytical problem-solving capacities of developers, (2) introducing and validating psychological measurements, theories, and concepts of affective states, creativity, and analytical-problem-solving skills in empirical software engineering, and (3) raising the need for studying the human factors of software engineering by employing a multidisciplinary viewpoint

Software Development Standard Processes (SDSP)

NASA Technical Reports Server (NTRS)

Lavin, Milton L.; Wang, James J.; Morillo, Ronald; Mayer, John T.; Jamshidian, Barzia; Shimizu, Kenneth J.; Wilkinson, Belinda M.; Hihn, Jairus M.; Borgen, Rosana B.; Meyer, Kenneth N.;

Control design for future agile fighters

NASA Technical Reports Server (NTRS)

Murphy, Patrick C.; Davidson, John B.

1991-01-01

The CRAFT control design methodology is presented. CRAFT stands for the design objectives addressed, namely, Control power, Robustness, Agility, and Flying Qualities Tradeoffs. The approach combines eigenspace assignment, which allows for direct specification of eigenvalues and eigenvectors, and a graphical approach for representing control design metrics that captures numerous design goals in one composite illustration. The methodology makes use of control design metrics from four design objective areas, namely, control power, robustness, agility, and flying qualities. An example of the CRAFT methodology as well as associated design issues are presented.

Computer-aided software development process design

NASA Technical Reports Server (NTRS)

Lin, Chi Y.; Levary, Reuven R.

1989-01-01

The authors describe an intelligent tool designed to aid managers of software development projects in planning, managing, and controlling the development process of medium- to large-scale software projects. Its purpose is to reduce uncertainties in the budget, personnel, and schedule planning of software development projects. It is based on dynamic model for the software development and maintenance life-cycle process. This dynamic process is composed of a number of time-varying, interacting developmental phases, each characterized by its intended functions and requirements. System dynamics is used as a modeling methodology. The resulting Software LIfe-Cycle Simulator (SLICS) and the hybrid expert simulation system of which it is a subsystem are described.

Understanding Organizational Agility: A Work-Design Perspective

DTIC Science & Technology

2008-06-01

NG SDG Proactive Yes Yes Yes Yes Yes Yes N/S N/S N/S Reactive Simultaneity of work design at three levels Yes Supply Chain Network Agility High Table...firm can take effective action to benefit itself and its customers. In analyzing representative supply - chain definitions of agility, the main theme...and Heppard 2000). Third, as effective supply chain management has come to be regarded as major source of competitive advantage for many firms

Software development for teleroentgenogram analysis

NASA Astrophysics Data System (ADS)

Goshkoderov, A. A.; Khlebnikov, N. A.; Obabkov, I. N.; Serkov, K. V.; Gajniyarov, I. M.; Aliev, A. A.

2017-09-01

A framework for the analysis and calculation of teleroentgenograms was developed. Software development was carried out in the Department of Children's Dentistry and Orthodontics in Ural State Medical University. The software calculates the teleroentgenogram by the original method which was developed in this medical department. Program allows designing its own methods for calculating the teleroentgenograms by new methods. It is planned to use the technology of machine learning (Neural networks) in the software. This will help to make the process of calculating the teleroentgenograms easier because methodological points will be placed automatically.

Sensory enhancing insoles improve athletic performance during a hexagonal agility task.

PubMed

Miranda, Daniel L; Hsu, Wen-Hao; Gravelle, Denise C; Petersen, Kelsey; Ryzman, Rachael; Niemi, James; Lesniewski-Laas, Nicholas

2016-05-03

Athletes incorporate afferent signals from the mechanoreceptors of their plantar feet to provide information about posture, stability, and joint position. Sub-threshold stochastic resonance (SR) sensory enhancing insoles have been shown to improve balance and proprioception in young and elderly participant populations. Balance and proprioception are correlated with improved athletic performance, such as agility. Agility is defined as the ability to quickly change direction. An athlete's agility is commonly evaluated during athletic performance testing to assess their ability to participate in a competitive sporting event. Therefore, the purpose of this study was to examine the effects of SR insoles during a hexagonal agility task routinely used by coaches and sports scientists. Twenty recreational athletes were recruited to participate in this study. Each athlete was asked to perform a set of hexagonal agility trials while SR stimulation was either on or off. Vicon motion capture was used to measure feet position during six successful trials for each stimulation condition. Stimulation condition was randomized in a pairwise fashion. The study outcome measures were the task completion time and the positional accuracy of footfalls. Pairwise comparisons revealed a 0.12s decrease in task completion time (p=0.02) with no change in hopping accuracy (p=0.99) when SR stimulation was on. This is the first study to show athletic performance benefits while wearing proprioception and balance improving equipment on healthy participants. With further development, a self-contained sensory enhancing insole device could be used by recreational and professional athletes to improve movements that require rapid changes in direction. Copyright © 2016 The Authors. Published by Elsevier Ltd.. All rights reserved.

CrossTalk: The Journal of Defense Software Engineering. Volume 26, Number 3, May-June 2013

DTIC Science & Technology

2013-06-01

in which the pieces are being shaped at the same time they are being as- sembled. If I am honest, software is probably more like a Rube Goldberg ...losing the focus on architecting activities that help maintain the desired state, enable cost savings, and ensure delivery tempo when other agile...masters degrees and working as developers), accepted by the same in- structor, with counted LOC identically, yielded variations as great as 22:1, and

Educational Software: A Developer's Perspective.

ERIC Educational Resources Information Center

Armstrong, Timothy C.; Loane, Russell F.

1994-01-01

Examines the current status and short-term future of computer software development in higher education. Topics discussed include educational advantages of software; current program development techniques, including object oriented programming; and market trends, including IBM versus Macintosh and multimedia programs. (LRW)

Automated software development workstation

NASA Technical Reports Server (NTRS)

Prouty, Dale A.; Klahr, Philip

1988-01-01

A workstation is being developed that provides a computational environment for all NASA engineers across application boundaries, which automates reuse of existing NASA software and designs, and efficiently and effectively allows new programs and/or designs to be developed, catalogued, and reused. The generic workstation is made domain specific by specialization of the user interface, capturing engineering design expertise for the domain, and by constructing/using a library of pertinent information. The incorporation of software reusability principles and expert system technology into this workstation provide the obvious benefits of increased productivity, improved software use and design reliability, and enhanced engineering quality by bringing engineering to higher levels of abstraction based on a well tested and classified library.

78 FR 64019 - Manufacturer of Controlled Substances; Notice of Registration; Agilent Technologies

Federal Register 2010, 2011, 2012, 2013, 2014

2013-10-25

...; Notice of Registration; Agilent Technologies By Notice dated May 24, 2013, and published in the Federal Register on June 4, 2013, 78 FR 33441, Agilent Technologies, 25200 Commercentre Drive, Lake Forest... of Agilent Technologies to manufacture the listed basic classes of controlled substances is...

2011 Agile (Scrum) Workshop Held in Baltimore, Maryland on November 14-15, 2011

DTIC Science & Technology

2011-11-15

have success- fully implemented Agile Development within DoD. SUSI MCKEE OC2IS Program Manager, U.S. Air Force Susana V. McKee has 25 years of DoD T...AGILE WILL WORK IN DOD: THREE EXAMPLES u Ms. Kelly Goshorn, Patriot Excalibur (PEX) Program Manager, U.S. Air Force u Ms. Susi McKee, Operational...OPS PEX Team: Internal •Devs/SMEs/Testers •Architecture Committee •Etc. none Future implementation, not Current release Big R/ Little r I n

The use of autologous concentrated growth factors to promote syndesmosis fusion in the Agility total ankle replacement. A preliminary study.

PubMed

Coetzee, J Chris; Pomeroy, Gregory C; Watts, J David; Barrow, Craig

2005-10-01

The Agility (DePuy, Warsaw, Indiana) total ankle replacement has been in use since 1984. One of the most common complications continues to be delayed union or nonunions of the distal tibiofibular syndesmosis. In the reported studies on the Agility ankle the delayed union and nonunion rate can be as high as 38%. Since 1999, 114 Agility total ankle replacements were done at two centers in the United States without the use of autologous concentrated growth factors. Since July of 2001, 66 Agility ankles were implanted with Symphony (DePuy, Warsaw, Indiana) augmented bone grafting. The standard operative technique was followed in all the patients. Prospective data was collected on all patients. The standard ankle radiographs were taken preoperatively and postoperative at 8 weeks, 12 weeks, 16 weeks, 6 months, and yearly. CT scans were obtained at 6 months if fusion at the syndesmosis was questionable. The Graphpad Instat software (Graphpad Software Inc., San Diego, CA) was used for statistical analysis. The two-tailed unpaired t-test was used, and the value <0.05 was considered significant. There was no statistical difference in the demographic data for the two groups. In 114 ankle replacements without autologous concentrated growth factors 70 fused at 8 weeks (61%), 14 fused at 12 weeks (12%), 13 fused at 6 months (12%). There were 17 nonunions (15%); delayed unions (3 to 6 months) and nonunions, therefore, equaled 27%. The syndesmosis fused in 50 of the 66 ankle replacements (76%) that had autologous concentrated growth fractures at 8 weeks (76%); 12 fused at 3 months (18%), 2 fused at 6 months (3%), 2 had nonunions (3%). Delayed unions (3 to 6 months) and nonunions equaled 6%. There was a statistically significant improvement in the 8- and 12-week fusion rates, and a statistically significant reduction in delayed unions and nonunions. Autologous concentrated growth factors appear to make a significant positive difference in the syndesmosis union rate in total ankle

Enhancing the Student Learning Experience in Software Engineering Project Courses

ERIC Educational Resources Information Center

Marques, Maira; Ochoa, Sergio F.; Bastarrica, Maria Cecilia; Gutierrez, Francisco J.

2018-01-01

Carrying out real-world software projects in their academic studies helps students to understand what they will face in industry, and to experience first-hand the challenges involved when working collaboratively. Most of the instructional strategies used to help students take advantage of these activities focus on supporting agile programming,…

PDS4 - Some Principles for Agile Data Curation

NASA Astrophysics Data System (ADS)

Hughes, J. S.; Crichton, D. J.; Hardman, S. H.; Joyner, R.; Algermissen, S.; Padams, J.

2015-12-01

PDS4, a research data management and curation system for NASA's Planetary Science Archive, was developed using principles that promote the characteristics of agile development. The result is an efficient system that produces better research data products while using less resources (time, effort, and money) and maximizes their usefulness for current and future scientists. The key principle is architectural. The PDS4 information architecture is developed and maintained independent of the infrastructure's process, application and technology architectures. The information architecture is based on an ontology-based information model developed to leverage best practices from standard reference models for digital archives, digital object registries, and metadata registries and capture domain knowledge from a panel of planetary science domain experts. The information model provides a sharable, stable, and formal set of information requirements for the system and is the primary source for information to configure most system components, including the product registry, search engine, validation and display tools, and production pipelines. Multi-level governance is also allowed for the effective management of the informational elements at the common, discipline, and project level. This presentation will describe the development principles, components, and uses of the information model and how an information model-driven architecture exhibits characteristics of agile curation including early delivery, evolutionary development, adaptive planning, continuous improvement, and rapid and flexible response to change.

Software Quality Perceptions of Stakeholders Involved in the Software Development Process

ERIC Educational Resources Information Center

Padmanabhan, Priya

2013-01-01

Software quality is one of the primary determinants of project management success. Stakeholders involved in software development widely agree that quality is important (Barney and Wohlin 2009). However, they may differ on what constitutes software quality, and which of its attributes are more important than others. Although, software quality…

Managers Handbook for Software Development

NASA Technical Reports Server (NTRS)

Agresti, W.; Mcgarry, F.; Card, D.; Page, J.; Church, V.; Werking, R.

1984-01-01

Methods and aids for the management of software development projects are presented. The recommendations are based on analyses and experiences with flight dynamics software development. The management aspects of organizing the project, producing a development plan, estimation costs, scheduling, staffing, preparing deliverable documents, using management tools, monitoring the project, conducting reviews, auditing, testing, and certifying are described.

Space Shuttle Software Development and Certification

NASA Technical Reports Server (NTRS)

Orr, James K.; Henderson, Johnnie A

2000-01-01

Man-rated software, "software which is in control of systems and environments upon which human life is critically dependent," must be highly reliable. The Space Shuttle Primary Avionics Software System is an excellent example of such a software system. Lessons learn from more than 20 years of effort have identified basic elements that must be present to achieve this high degree of reliability. The elements include rigorous application of appropriate software development processes, use of trusted tools to support those processes, quantitative process management, and defect elimination and prevention. This presentation highlights methods used within the Space Shuttle project and raises questions that must be addressed to provide similar success in a cost effective manner on future long-term projects where key application development tools are COTS rather than internally developed custom application development tools

Quantifying performance on an outdoor agility drill using foot-mounted inertial measurement units.

PubMed

Zaferiou, Antonia M; Ojeda, Lauro; Cain, Stephen M; Vitali, Rachel V; Davidson, Steven P; Stirling, Leia; Perkins, Noel C

2017-01-01

Running agility is required for many sports and other physical tasks that demand rapid changes in body direction. Quantifying agility skill remains a challenge because measuring rapid changes of direction and quantifying agility skill from those measurements are difficult to do in ways that replicate real task/game play situations. The objectives of this study were to define and to measure agility performance for a (five-cone) agility drill used within a military obstacle course using data harvested from two foot-mounted inertial measurement units (IMUs). Thirty-two recreational athletes ran an agility drill while wearing two IMUs secured to the tops of their athletic shoes. The recorded acceleration and angular rates yield estimates of the trajectories, velocities and accelerations of both feet as well as an estimate of the horizontal velocity of the body mass center. Four agility performance metrics were proposed and studied including: 1) agility drill time, 2) horizontal body speed, 3) foot trajectory turning radius, and 4) tangential body acceleration. Additionally, the average horizontal ground reaction during each footfall was estimated. We hypothesized that shorter agility drill performance time would be observed with small turning radii and large tangential acceleration ranges and body speeds. Kruskal-Wallis and mean rank post-hoc statistical analyses revealed that shorter agility drill performance times were observed with smaller turning radii and larger tangential acceleration ranges and body speeds, as hypothesized. Moreover, measurements revealed the strategies that distinguish high versus low performers. Relative to low performers, high performers used sharper turns, larger changes in body speed (larger tangential acceleration ranges), and shorter duration footfalls that generated larger horizontal ground reactions during the turn phases. Overall, this study advances the use of foot-mounted IMUs to quantify agility performance in contextually

Speed and agility of 12- and 14-year-old elite male basketball players.

PubMed

Jakovljevic, Sasa T; Karalejic, Milivoje S; Pajic, Zoran B; Macura, Marija M; Erculj, Frane F

2012-09-01

The aims of this study were (a) to identify and compare the speed and agility of 12- and 14-year-old elite male basketball players and (b) to investigate relations between speed and agility for both age groups of basketball players, to help coaches to improve their work. Sixty-four players aged 12 (M = 11.98 years, SD = 0.311) and 54 players aged 14 (M = 14.092 years, SD = 0.275) were tested. Three agility tests: agility t-test, zigzag agility drill, and agility run 4 × 15 m and 3 speed tests: 20-m run, 30-m run, and 50-m run were applied. Fourteen-year-old players achieved significantly better results in all speed and agility tests compared with 12-year-old players. The correlation coefficient (r = 0.81, p = 0.001) showed that 12-year-old players have the same ability in the 30- and 50-m runs. The other correlation coefficient (r = 0.59, p = 0.001) indicated that 20- and 30-m runs had inherently different qualities. The correlation coefficients between agility tests were <0.71, and therefore, each test in this group represents a specific task. In 14-year-old players, the correlation coefficients between the speed test results were <0.71. In contrast, the correlation coefficients between the agility tests were >0.71, which means that all the 3 tests represent the same quality. During the speed training of 12-year-old players, it is advisable to focus on shorter running distances, up to 30 m. During the agility training of the same players, it is useful to apply exercises with various complexities. In speed training of the 14-year-old players, the 30- and 50-m runs should be applied, and agility training should include more specific basketball movements and activities.

Delaying Mobility Disability in People With Parkinson Disease Using a Sensorimotor Agility Exercise Program

PubMed Central

King, Laurie A; Horak, Fay B

2009-01-01

This article introduces a new framework for therapists to develop an exercise program to delay mobility disability in people with Parkinson disease (PD). Mobility, or the ability to efficiently navigate and function in a variety of environments, requires balance, agility, and flexibility, all of which are affected by PD. This article summarizes recent research identifying how constraints on mobility specific to PD, such as rigidity, bradykinesia, freezing, poor sensory integration, inflexible program selection, and impaired cognitive processing, limit mobility in people with PD. Based on these constraints, a conceptual framework for exercises to maintain and improve mobility is presented. An example of a constraint-focused agility exercise program, incorporating movement principles from tai chi, kayaking, boxing, lunges, agility training, and Pilates exercises, is presented. This new constraint-focused agility exercise program is based on a strong scientific framework and includes progressive levels of sensorimotor, resistance, and coordination challenges that can be customized for each patient while maintaining fidelity. Principles for improving mobility presented here can be incorporated into an ongoing or long-term exercise program for people with PD. PMID:19228832

Delaying mobility disability in people with Parkinson disease using a sensorimotor agility exercise program.

PubMed

King, Laurie A; Horak, Fay B

2009-04-01

This article introduces a new framework for therapists to develop an exercise program to delay mobility disability in people with Parkinson disease (PD). Mobility, or the ability to efficiently navigate and function in a variety of environments, requires balance, agility, and flexibility, all of which are affected by PD. This article summarizes recent research identifying how constraints on mobility specific to PD, such as rigidity, bradykinesia, freezing, poor sensory integration, inflexible program selection, and impaired cognitive processing, limit mobility in people with PD. Based on these constraints, a conceptual framework for exercises to maintain and improve mobility is presented. An example of a constraint-focused agility exercise program, incorporating movement principles from tai chi, kayaking, boxing, lunges, agility training, and Pilates exercises, is presented. This new constraint-focused agility exercise program is based on a strong scientific framework and includes progressive levels of sensorimotor, resistance, and coordination challenges that can be customized for each patient while maintaining fidelity. Principles for improving mobility presented here can be incorporated into an ongoing or long-term exercise program for people with PD.

Toolpack mathematical software development environment

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

Osterweil, L.

1982-07-21

The purpose of this research project was to produce a well integrated set of tools for the support of numerical computation. The project entailed the specification, design and implementation of both a diversity of tools and an innovative tool integration mechanism. This large configuration of tightly integrated tools comprises an environment for numerical software development, and has been named Toolpack/IST (Integrated System of Tools). Following the creation of this environment in prototype form, the environment software was readied for widespread distribution by transitioning it to a development organization for systematization, documentation and distribution. It is expected that public release ofmore » Toolpack/IST will begin imminently and will provide a basis for evaluation of the innovative software approaches taken as well as a uniform set of development tools for the numerical software community.« less

Advanced Software Development Workstation Project

NASA Technical Reports Server (NTRS)

Lee, Daniel

1989-01-01

The Advanced Software Development Workstation Project, funded by Johnson Space Center, is investigating knowledge-based techniques for software reuse in NASA software development projects. Two prototypes have been demonstrated and a third is now in development. The approach is to build a foundation that provides passive reuse support, add a layer that uses domain-independent programming knowledge, add a layer that supports the acquisition of domain-specific programming knowledge to provide active support, and enhance maintainability and modifiability through an object-oriented approach. The development of new application software would use specification-by-reformulation, based on a cognitive theory of retrieval from very long-term memory in humans, and using an Ada code library and an object base. Current tasks include enhancements to the knowledge representation of Ada packages and abstract data types, extensions to support Ada package instantiation knowledge acquisition, integration with Ada compilers and relational databases, enhancements to the graphical user interface, and demonstration of the system with a NASA contractor-developed trajectory simulation package. Future work will focus on investigating issues involving scale-up and integration.

Exercise-Based Fall Prevention in the Elderly: What About Agility?

PubMed

Donath, Lars; van Dieën, Jaap; Faude, Oliver

2016-02-01

Annually, one in three seniors aged over 65 years fall. Balance and strength training can reduce neuromuscular fall risk factors and fall rates. Besides conventional balance and strength training, explosive or high-velocity strength training, eccentric exercises, perturbation-based balance training, trunk strength, and trunk control have also been emphasized. In contrast, aerobic exercise has to date not been included in fall-prevention studies. However, well-developed endurance capacity might attenuate fatigue-induced declines in postural control in sports-related or general activities of daily living. Physical performance indices, such as balance, strength, and endurance, are generally addressed independently in exercise guidelines. This approach seems time consuming and may impede integrative training of sensorimotor, neuromuscular, and cardiocirculatory functions required to deal with balance-threatening situations in the elderly. An agility-based conceptual training framework comprising perception and decision making (e.g., visual scanning, pattern recognition, anticipation) and changes of direction (e.g., sudden starts, stops and turns; reactive control; concentric and eccentric contractions) might enable an integrative neuromuscular, cardiocirculatory, and cognitive training. The present paper aims to provide a scientific sketch of how to build such an integrated modular training approach, allowing adaptation of intensity, complexity, and cognitive challenge of the agility tasks to the participant's capacity. Subsequent research should address the (1) link between agility and fall risk factors as well as fall rates, (2) benefit-risk ratios of the proposed approach, (3) psychosocial aspects of agility training (e.g., motivation), and (4) logistical requirements (e.g., equipment needed).

Open Technology Development: Roadmap Plan

DTIC Science & Technology

2006-04-01

65 RECOMMENDATION 1: APPROVE AND FUND AN OTD STRIKE TEAM................. 67 Senior Leadership...negotiated, rather than an innate property of the product. Software’s replicability also means it can be incorporated into other software systems without...to leverage an open code development model, DoD would provide the market incentives to increase the agility and competitiveness of the industrial

Software Development Life Cycle Security Issues

NASA Astrophysics Data System (ADS)

Kaur, Daljit; Kaur, Parminder

2011-12-01

Security is now-a-days one of the major problems because of many reasons. Security is now-a-days one of the major problems because of many reasons. The main cause is that software can't withstand security attacks because of vulnerabilities in it which are caused by defective specifications design and implementation. We have conducted a survey asking software developers, project managers and other people in software development about their security awareness and implementation in Software Development Life Cycle (SDLC). The survey was open to participation for three weeks and this paper explains the survey results.

Reliability and Validity of a New Test of Agility and Skill for Female Amateur Soccer Players

PubMed Central

Kutlu, Mehmet; Yapici, Hakan; Yilmaz, Abdullah

2017-01-01

Abstract The aim of this study was to evaluate the Agility and Skill Test, which had been recently developed to assess agility and skill in female athletes. Following a 10 min warm-up, two trials to test the reliability and validity of the test were conducted one week apart. Measurements were collected to compare soccer players’ physical performance in a 20 m sprint, a T-Drill test, the Illinois Agility Run Test, change-of-direction and acceleration, as well as agility and skill. All tests were completed following the same order. Thirty-four amateur female soccer players were recruited (age = 20.8 ± 1.9 years; body height = 166 ± 6.9 cm; body mass = 55.5 ± 5.8 kg). To determine the reliability and usefulness of these tests, paired sample t-tests, intra-class correlation coefficients, typical error, coefficient of variation, and differences between the typical error and smallest worthwhile change statistics were computed. Test results showed no significant differences between the two sessions (p > 0.01). There were higher intra-class correlations between the test and retest values (r = 0.94–0.99) for all tests. Typical error values were below the smallest worthwhile change, indicating ‘good’ usefulness for these tests. A near perfect Pearson correlation between the Agility and Skill Test (r = 0.98) was found, and there were moderate-to-large levels of correlation between the Agility and Skill Test and other measures (r = 0.37 to r = 0.56). The results of this study suggest that the Agility and Skill Test is a reliable and valid test for female soccer players and has significant value for assessing the integrative agility and skill capability of soccer players. PMID:28469760

Agile battle management efficiency for command, control, communications, computers and intelligence (C4I)

NASA Astrophysics Data System (ADS)

Blasch, Erik; Bélanger, Micheline

2016-05-01

Various operations such as civil-military co-operation (CIMIC) affairs require orchestration of communications, assets, and actors. A key component includes technology advancements to enable coordination among people and machines the ability to know where things are, who to coordinate with, and open and consistent lines of communication. In this paper, we explore concepts of battle management (BM) to support high-tempo emergency response scenarios such as a disaster action response team (DART). Three concepts highlighted of agile battle management (ABM) include source orchestration (e.g., sensors and domains), battle management language (BML) development (e.g., software and ontologies), and command and control (C2) coordination (e.g., people and visualization); which require correlation and de-confliction. These concepts of ABM support the physical, information, and cognitive domains for efficient command, control, communications, and information (C3I) to synchronize data and people for efficient and effective operations.

Allometric multilevel modelling of agility and dribbling speed by skeletal age and playing position in youth soccer players.

PubMed

Valente-dos-Santos, J; Coelho-e-Silva, M J; Duarte, J; Pereira, J; Rebelo-Gonçalves, R; Figueiredo, A; Mazzuco, M A; Sherar, L B; Elferink-Gemser, M T; Malina, R M

2014-08-01

This study evaluates the contributions of age, skeletal maturation, body size and composition, training and playing position to the development of agility and dribbling speed in young male soccer players (10-18 years) followed longitudinally. 83 players [defenders (n=35), midfielders (n=27), forwards (n=21)] were followed annually over 5 years (average: 4.4 observations per player). Skeletal age (SA), stature, body mass, triceps and subscapular skinfolds, agility and dribbling speed were measured annually. Body composition was estimated from the 2 skinfolds. Annual training volume was estimated from weekly participation forms completed by coaches. The multiplicative allometric models with the best statistical fit showed that statural growth of 1 cm predicts 1.334 s and 1.927 s of improvement in agility and dribbling speed, respectively. Significant independent effects of fat-free mass and annual volume training were found for agility and dribbling speed, respectively (P<0.05). Predicted agility (from 12 to 18 years of SA) and dribbling speed (from 13 to 18 years of SA) differed significantly among players by playing positions (midfielders>forwards>defenders). The present results provide developmental models for the interpretation of intra- and inter-individual variability in agility and dribbling speed among youth soccer players across adolescence, and may provide a framework for trainers and coaches to develop and evaluate individualized training protocols. © Georg Thieme Verlag KG Stuttgart · New York.

Astronomers as Software Developers

NASA Astrophysics Data System (ADS)

Pildis, Rachel A.

2016-01-01

Astronomers know that their research requires writing, adapting, and documenting computer software. Furthermore, they often have to learn new computer languages and figure out how existing programs work without much documentation or guidance and with extreme time pressure. These are all skills that can lead to a software development job, but recruiters and employers probably won't know that. I will discuss all the highly useful experience that astronomers may not know that they already have, and how to explain that knowledge to others when looking for non-academic software positions. I will also talk about some of the pitfalls I have run into while interviewing for jobs and working as a developer, and encourage you to embrace the curiosity employers might have about your non-standard background.

Software development predictors, error analysis, reliability models and software metric analysis

NASA Technical Reports Server (NTRS)

Basili, Victor

1983-01-01

The use of dynamic characteristics as predictors for software development was studied. It was found that there are some significant factors that could be useful as predictors. From a study on software errors and complexity, it was shown that meaningful results can be obtained which allow insight into software traits and the environment in which it is developed. Reliability models were studied. The research included the field of program testing because the validity of some reliability models depends on the answers to some unanswered questions about testing. In studying software metrics, data collected from seven software engineering laboratory (FORTRAN) projects were examined and three effort reporting accuracy checks were applied to demonstrate the need to validate a data base. Results are discussed.

Development of a low-cost, low micro-vibration CMG for small agile satellite applications

NASA Astrophysics Data System (ADS)

Kawak, B. J.

2017-02-01

The agility of the spacecraft which refers to the spacecraft's ability to execute fast and accurate manoeuvers within a fixed period of time, is a key satellite parameter. The spacecraft' s agility is directly proportional to the spacecraft actuators' output torque. For high torque inertial actuators (>0.5 Nm), Control Moment Gyroscope (CMG) exhibits better performances in terms of mass and electrical power consumption than reaction wheels. However, in addition to the complex steering law required to avoid CMG singularities, one of the reasons why CMGs are not widely used is also due to their high micro-vibration emission which may interfere and disrupt the spacecraft' s sensitive instruments such as optical payloads. In this paper, an innovative two-stage viscoelastic isolation system has been designed and implemented in a new low micro-vibration CMG prototype. The first stage of the damping system acts at bearing level to attenuate the possible shock vibrations while the second stage acts at mechanism level to attenuate the structural resonances and motor noise. The developed CMG enables to combine high actuator output torque with a low micro-vibration signature. The viscoelastic damping system is cost effective as it is a fully passive system which requires no thermal control and no electronics. Furthermore, the attenuation provided by this innovative two stage damping system can reach a slope up to -80 dB/dec which leads to a Mini-CMG micro-vibration signature lower than similar output torque reaction wheels not equipped with a damping system.

A toolbox for developing bioinformatics software

PubMed Central

Potrzebowski, Wojciech; Puton, Tomasz; Rother, Magdalena; Wywial, Ewa; Bujnicki, Janusz M.

2012-01-01

Creating useful software is a major activity of many scientists, including bioinformaticians. Nevertheless, software development in an academic setting is often unsystematic, which can lead to problems associated with maintenance and long-term availibility. Unfortunately, well-documented software development methodology is difficult to adopt, and technical measures that directly improve bioinformatic programming have not been described comprehensively. We have examined 22 software projects and have identified a set of practices for software development in an academic environment. We found them useful to plan a project, support the involvement of experts (e.g. experimentalists), and to promote higher quality and maintainability of the resulting programs. This article describes 12 techniques that facilitate a quick start into software engineering. We describe 3 of the 22 projects in detail and give many examples to illustrate the usage of particular techniques. We expect this toolbox to be useful for many bioinformatics programming projects and to the training of scientific programmers. PMID:21803787

Software requirements: Guidance and control software development specification

NASA Technical Reports Server (NTRS)

Withers, B. Edward; Rich, Don C.; Lowman, Douglas S.; Buckland, R. C.

1990-01-01

The software requirements for an implementation of Guidance and Control Software (GCS) are specified. The purpose of the GCS is to provide guidance and engine control to a planetary landing vehicle during its terminal descent onto a planetary surface and to communicate sensory information about that vehicle and its descent to some receiving device. The specification was developed using the structured analysis for real time system specification methodology by Hatley and Pirbhai and was based on a simulation program used to study the probability of success of the 1976 Viking Lander missions to Mars. Three versions of GCS are being generated for use in software error studies.

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.

X-36 Tailless Fighter Agility Research Aircraft arrival at Dryden

NASA Technical Reports Server (NTRS)

1996-01-01

NASA and McDonnell Douglas Corporation (MDC) personnel remove protective covers from the newly arrived NASA/McDonnell Douglas Corporation X-36 Tailless Fighter Agility Research Aircraft. It arrived at NASA Dryden Flight Research Center, Edwards, California, on July 2, 1996. The NASA/Boeing X-36 Tailless Fighter Agility Research Aircraft program successfully demonstrated the tailless fighter design using advanced technologies to improve the maneuverability and survivability of possible future fighter aircraft. The program met or exceeded all project goals. For 31 flights during 1997 at the Dryden Flight Research Center, Edwards, California, the project team examined the aircraft's agility at low speed / high angles of attack and at high speed / low angles of attack. The aircraft's speed envelope reached up to 206 knots (234 mph). This aircraft was very stable and maneuverable. It handled very well. The X-36 vehicle was designed to fly without the traditional tail surfaces common on most aircraft. Instead, a canard forward of the wing was used as well as split ailerons and an advanced thrust-vectoring nozzle for directional control. The X-36 was unstable in both pitch and yaw axes, so an advanced, single-channel digital fly-by-wire control system (developed with some commercially available components) was put in place to stabilize the aircraft. Using a video camera mounted in the nose of the aircraft and an onboard microphone, the X-36 was remotely controlled by a pilot in a ground station virtual cockpit. A standard fighter-type head-up display (HUD) and a moving-map representation of the vehicle's position within the range in which it flew provided excellent situational awareness for the pilot. This pilot-in-the-loop approach eliminated the need for expensive and complex autonomous flight control systems and the risks associated with their inability to deal with unknown or unforeseen phenomena in flight. Fully fueled the X-36 prototype weighed approximately 1

X-36 Tailless Fighter Agility Research Aircraft arrival at Dryden

NASA Technical Reports Server (NTRS)

1996-01-01

The NASA/McDonnell Douglas Corporation (MDC) X-36 Tailless Fighter Agility Research Aircraft in it's hangar at NASA Dryden Flight Research Center, Edwards, California, following its arrival on July 2, 1996. The NASA/Boeing X-36 Tailless Fighter Agility Research Aircraft program successfully demonstrated the tailless fighter design using advanced technologies to improve the maneuverability and survivability of possible future fighter aircraft. The program met or exceeded all project goals. For 31 flights during 1997 at the Dryden Flight Research Center, Edwards, California, the project team examined the aircraft's agility at low speed / high angles of attack and at high speed / low angles of attack. The aircraft's speed envelope reached up to 206 knots (234 mph). This aircraft was very stable and maneuverable. It handled very well. The X-36 vehicle was designed to fly without the traditional tail surfaces common on most aircraft. Instead, a canard forward of the wing was used as well as split ailerons and an advanced thrust-vectoring nozzle for directional control. The X-36 was unstable in both pitch and yaw axes, so an advanced, single-channel digital fly-by-wire control system (developed with some commercially available components) was put in place to stabilize the aircraft. Using a video camera mounted in the nose of the aircraft and an onboard microphone, the X-36 was remotely controlled by a pilot in a ground station virtual cockpit. A standard fighter-type head-up display (HUD) and a moving-map representation of the vehicle's position within the range in which it flew provided excellent situational awareness for the pilot. This pilot-in-the-loop approach eliminated the need for expensive and complex autonomous flight control systems and the risks associated with their inability to deal with unknown or unforeseen phenomena in flight. Fully fueled the X-36 prototype weighed approximately 1,250 pounds. It was 19 feet long and three feet high with a wingspan of

X-36 Tailless Fighter Agility Research Aircraft arrival at Dryden

NASA Technical Reports Server (NTRS)

1996-01-01

NASA and McDonnell Douglas Corporation (MDC) personnel wait to attach a hoist to the X-36 Tailless Fighter Agility Research Aircraft, which arrived at NASA Dryden Flight Research Center, Edwards, California, on July 2, 1996. The NASA/Boeing X-36 Tailless Fighter Agility Research Aircraft program successfully demonstrated the tailless fighter design using advanced technologies to improve the maneuverability and survivability of possible future fighter aircraft. The program met or exceeded all project goals. For 31 flights during 1997 at the Dryden Flight Research Center, Edwards, California, the project team examined the aircraft's agility at low speed / high angles of attack and at high speed / low angles of attack. The aircraft's speed envelope reached up to 206 knots (234 mph). This aircraft was very stable and maneuverable. It handled very well. The X-36 vehicle was designed to fly without the traditional tail surfaces common on most aircraft. Instead, a canard forward of the wing was used as well as split ailerons and an advanced thrust-vectoring nozzle for directional control. The X-36 was unstable in both pitch and yaw axes, so an advanced, single-channel digital fly-by-wire control system (developed with some commercially available components) was put in place to stabilize the aircraft. Using a video camera mounted in the nose of the aircraft and an onboard microphone, the X-36 was remotely controlled by a pilot in a ground station virtual cockpit. A standard fighter-type head-up display (HUD) and a moving-map representation of the vehicle's position within the range in which it flew provided excellent situational awareness for the pilot. This pilot-in-the-loop approach eliminated the need for expensive and complex autonomous flight control systems and the risks associated with their inability to deal with unknown or unforeseen phenomena in flight. Fully fueled the X-36 prototype weighed approximately 1,250 pounds. It was 19 feet long and three feet high

X-36 Tailless Fighter Agility Research Aircraft arrival at Dryden

NASA Technical Reports Server (NTRS)

1996-01-01

The NASA/McDonnell Douglas Corporation (MDC) X-36 Tailless Fighter Agility Research Aircraft is steered to it's hangar at NASA Dryden Flight Research Center, Edwards, California, following arrival on July 2, 1996. The NASA/Boeing X-36 Tailless Fighter Agility Research Aircraft program successfully demonstrated the tailless fighter design using advanced technologies to improve the maneuverability and survivability of possible future fighter aircraft. The program met or exceeded all project goals. For 31 flights during 1997 at the Dryden Flight Research Center, Edwards, California, the project team examined the aircraft's agility at low speed / high angles of attack and at high speed / low angles of attack. The aircraft's speed envelope reached up to 206 knots (234 mph). This aircraft was very stable and maneuverable. It handled very well. The X-36 vehicle was designed to fly without the traditional tail surfaces common on most aircraft. Instead, a canard forward of the wing was used as well as split ailerons and an advanced thrust-vectoring nozzle for directional control. The X-36 was unstable in both pitch and yaw axes, so an advanced, single-channel digital fly-by-wire control system (developed with some commercially available components) was put in place to stabilize the aircraft. Using a video camera mounted in the nose of the aircraft and an onboard microphone, the X-36 was remotely controlled by a pilot in a ground station virtual cockpit. A standard fighter-type head-up display (HUD) and a moving-map representation of the vehicle's position within the range in which it flew provided excellent situational awareness for the pilot. This pilot-in-the-loop approach eliminated the need for expensive and complex autonomous flight control systems and the risks associated with their inability to deal with unknown or unforeseen phenomena in flight. Fully fueled the X-36 prototype weighed approximately 1,250 pounds. It was 19 feet long and three feet high with a

Some Future Software Engineering Opportunities and Challenges

NASA Astrophysics Data System (ADS)

Boehm, Barry

This paper provides an update and extension of a 2006 paper, “Some Future Trends and Implications for Systems and Software Engineering Processes,” Systems Engineering, Spring 2006. Some of its challenges and opportunities are similar, such as the need to simultaneously achieve high levels of both agility and assurance. Others have emerged as increasingly important, such as the challenges of dealing with ultralarge volumes of data, with multicore chips, and with software as a service. The paper is organized around eight relatively surprise-free trends and two “wild cards” whose trends and implications are harder to foresee. The eight surprise-free trends are:

Pathways to agility in the production of neutron generators

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

Stoltz, R.E.; Beavis, L.C.; Cutchen, J.T.

1994-02-01

This report is the result of a study team commissioned to explore pathways for increased agility in the manufacture of neutron generators. As a part of Sandia`s new responsibility for generator production, the goal of the study was to identify opportunities to reduce costs and increase flexibility in the manufacturing operation. Four parallel approaches (or pathways) were recommended: (1) Know the goal, (2) Use design leverage effectively, (3) Value simplicity, and (4) Configure for flexibility. Agility in neutron generator production can be enhanced if all of these pathways are followed. The key role of the workforce in achieving agility wasmore » also noted, with emphasis on ownership, continuous learning, and a supportive environment.« less

A fuzzy MCDM framework based on fuzzy measure and fuzzy integral for agile supplier evaluation

NASA Astrophysics Data System (ADS)

Dursun, Mehtap

2017-06-01

Supply chains need to be agile in order to response quickly to the changes in today's competitive environment. The success of an agile supply chain depends on the firm's ability to select the most appropriate suppliers. This study proposes a multi-criteria decision making technique for conducting an analysis based on multi-level hierarchical structure and fuzzy logic for the evaluation of agile suppliers. The ideal and anti-ideal solutions are taken into consideration simultaneously in the developed approach. The proposed decision approach enables the decision-makers to use linguistic terms, and thus, reduce their cognitive burden in the evaluation process. Furthermore, a hierarchy of evaluation criteria and their related sub-criteria is employed in the presented approach in order to conduct a more effective analysis.

A Legal Guide for the Software Developer.

ERIC Educational Resources Information Center

Minnesota Small Business Assistance Office, St. Paul.

This booklet has been prepared to familiarize the inventor, creator, or developer of a new computer software product or software invention with the basic legal issues involved in developing, protecting, and distributing the software in the United States. Basic types of software protection and related legal matters are discussed in detail,…

Development of a high-speed wavelength-agile CO2 local oscillator for heterodyne DIAL measurements

NASA Astrophysics Data System (ADS)

Senft, Daniel C.; Pierrottet, Diego F.

2002-06-01

A high repetition rate, wavelength agile CO2 laser has been developed at the Air Force Research Laboratory for use as a local oscillator in a heterodyne detection receiver. Fats wavelength selection is required for measurements of airborne chemical vapors using the differential absorption lidar (DIAL) technique. Acousto-optic modulator are used to tune between different wavelengths at high speeds without the need for moving mechanical parts. Other advantages obtained by the use of acousto-optic modulators are laser output power control per wavelength and rugged packaging for field applications. The local oscillator design is described, and the results from laboratory DIAL measurements are presented. The coherent remote optical sensor system is an internal research project being conducted by the Air Force Research Laboratory Directed Energy Directorate, Active Remote Sensing Branch. The objective of the project is to develop a new long-range standoff spectral sensor that takes advantage of the enhanced performance capabilities coherent detection can provide. Emphasis of the development is on a low cost, compact, and rugged active sensor exclusively designed for heterodyne detection using the differential absorption lidar technique. State of the art technologies in waveguide laser construction and acousto- optics make feasible the next generation of lasers capable of supporting coherent lidar system requirements. Issues addressed as part of the development include optoelectronic engineering of a low cost rugged system, and fast data throughput for real time chemical concentration measurements. All hardware used in this sensor are off-the- shelf items, so only minor hardware modifications were required for the system as it stands. This paper describes a high-speed heterodyne detection CO2 DIAL system that employs a wavelength agile, acousto-optically tuned local oscillator in the receiver. Sample experimental data collected in a controlled environment are presented as

Rapid Development of Specialty Population Registries and Quality Measures from Electronic Health Record Data*. An Agile Framework.

PubMed

Kannan, Vaishnavi; Fish, Jason S; Mutz, Jacqueline M; Carrington, Angela R; Lai, Ki; Davis, Lisa S; Youngblood, Josh E; Rauschuber, Mark R; Flores, Kathryn A; Sara, Evan J; Bhat, Deepa G; Willett, DuWayne L

2017-06-14

Creation of a new electronic health record (EHR)-based registry often can be a "one-off" complex endeavor: first developing new EHR data collection and clinical decision support tools, followed by developing registry-specific data extractions from the EHR for analysis. Each development phase typically has its own long development and testing time, leading to a prolonged overall cycle time for delivering one functioning registry with companion reporting into production. The next registry request then starts from scratch. Such an approach will not scale to meet the emerging demand for specialty registries to support population health and value-based care. To determine if the creation of EHR-based specialty registries could be markedly accelerated by employing (a) a finite core set of EHR data collection principles and methods, (b) concurrent engineering of data extraction and data warehouse design using a common dimensional data model for all registries, and (c) agile development methods commonly employed in new product development. We adopted as guiding principles to (a) capture data as a byproduct of care of the patient, (b) reinforce optimal EHR use by clinicians, (c) employ a finite but robust set of EHR data capture tool types, and (d) leverage our existing technology toolkit. Registries were defined by a shared condition (recorded on the Problem List) or a shared exposure to a procedure (recorded on the Surgical History) or to a medication (recorded on the Medication List). Any EHR fields needed - either to determine registry membership or to calculate a registry-associated clinical quality measure (CQM) - were included in the enterprise data warehouse (EDW) shared dimensional data model. Extract-transform-load (ETL) code was written to pull data at defined "grains" from the EHR into the EDW model. All calculated CQM values were stored in a single Fact table in the EDW crossing all registries. Registry-specific dashboards were created in the EHR to display

Rapid Development of Specialty Population Registries and Quality Measures from Electronic Health Record Data: An Agile Framework

PubMed Central

Kannan, V; Fish, JS; Mutz, JM; Carrington, AR; Lai, K; Davis, LS; Youngblood, JE; Rauschuber, MR; Flores, KA; Sara, EJ; Bhat, DG; Willett, DL

2017-01-01

Summary Background Creation of a new electronic health record (EHR)-based registry often can be a "one-off" complex endeavor: first developing new EHR data collection and clinical decision support tools, followed by developing registry-specific data extractions from the EHR for analysis. Each development phase typically has its own long development and testing time, leading to a prolonged overall cycle time for delivering one functioning registry with companion reporting into production. The next registry request then starts from scratch. Such an approach will not scale to meet the emerging demand for specialty registries to support population health and value-based care. Objective To determine if the creation of EHR-based specialty registries could be markedly accelerated by employing (a) a finite core set of EHR data collection principles and methods, (b) concurrent engineering of data extraction and data warehouse design using a common dimensional data model for all registries, and (c) agile development methods commonly employed in new product development. Methods We adopted as guiding principles to (a) capture data as a by product of care of the patient, (b) reinforce optimal EHR use by clinicians, (c) employ a finite but robust set of EHR data capture tool types, and (d) leverage our existing technology toolkit. Registries were defined by a shared condition (recorded on the Problem List) or a shared exposure to a procedure (recorded on the Surgical History) or to a medication (recorded on the Medication List). Any EHR fields needed—either to determine registry membership or to calculate a registry-associated clinical quality measure (CQM)—were included in the enterprise data warehouse (EDW) shared dimensional data model. Extract-transform-load (ETL) code was written to pull data at defined “grains” from the EHR into the EDW model. All calculated CQM values were stored in a single Fact table in the EDW crossing all registries. Registry

A survey of risk factors for digit injuries among dogs training and competing in agility events.

PubMed

Sellon, Debra C; Martucci, Katherine; Wenz, John R; Marcellin-Little, Denis J; Powers, Michelle; Cullen, Kimberley L

2018-01-01

OBJECTIVE To identify potential risk factors for digit injuries in dogs training and competing in agility events. DESIGN Internet-based, retrospective, cross-sectional survey. ANIMALS 1,081 dogs training or competing in agility events. PROCEDURES Data were collected for eligible animals via retrospective surveys distributed electronically to handlers of dogs participating in agility-related activities. Variables evaluated included demographic (handlers) and signalment (dogs) information, physical characteristics of dogs, and injury characteristics. A separate survey of dogs competing in similar agility-related activities but without digit injuries was also administered. Multivariable logistic regression was used to develop a model for assessment of risk factors. RESULTS Data were collected from 207 agility dogs with digit injuries and 874 agility dogs without digit injuries. Factors associated with significantly increased odds of injury included Border Collie breed (OR, 2.3; 95% confidence interval [CI], 1.5 to 3.3), long nails (OR, 2.4; 95% CI, 1.3 to 4.5), absence of front dewclaws (OR, 1.9; 95% CI, 1.3 to 2.6), and greater weight-to-height ratio (OR, 1.5; 95% CI, 1.1 to 2.0). Odds of injury decreased with increasing age of the dog (OR, 0.8; 95% CI, 0.76 to 0.86). CONCLUSIONS AND CLINICAL RELEVANCE Results should be cautiously interpreted because of potential respondent and recall bias and lack of review of medical records. Nevertheless, results suggested that retaining healthy dewclaws, maintaining lean body mass, and trimming nails short for training and competition may decrease the likelihood of digit injuries. Research to investigate training practices, obstacle construction specifcations, and surface considerations for dogs competing in agility activities is indicated.

Moving target detection for frequency agility radar by sparse reconstruction

NASA Astrophysics Data System (ADS)

Quan, Yinghui; Li, YaChao; Wu, Yaojun; Ran, Lei; Xing, Mengdao; Liu, Mengqi

2016-09-01

Frequency agility radar, with randomly varied carrier frequency from pulse to pulse, exhibits superior performance compared to the conventional fixed carrier frequency pulse-Doppler radar against the electromagnetic interference. A novel moving target detection (MTD) method is proposed for the estimation of the target's velocity of frequency agility radar based on pulses within a coherent processing interval by using sparse reconstruction. Hardware implementation of orthogonal matching pursuit algorithm is executed on Xilinx Virtex-7 Field Programmable Gata Array (FPGA) to perform sparse optimization. Finally, a series of experiments are performed to evaluate the performance of proposed MTD method for frequency agility radar systems.

Moving target detection for frequency agility radar by sparse reconstruction.

PubMed

Quan, Yinghui; Li, YaChao; Wu, Yaojun; Ran, Lei; Xing, Mengdao; Liu, Mengqi

2016-09-01

Frequency agility radar, with randomly varied carrier frequency from pulse to pulse, exhibits superior performance compared to the conventional fixed carrier frequency pulse-Doppler radar against the electromagnetic interference. A novel moving target detection (MTD) method is proposed for the estimation of the target's velocity of frequency agility radar based on pulses within a coherent processing interval by using sparse reconstruction. Hardware implementation of orthogonal matching pursuit algorithm is executed on Xilinx Virtex-7 Field Programmable Gata Array (FPGA) to perform sparse optimization. Finally, a series of experiments are performed to evaluate the performance of proposed MTD method for frequency agility radar systems.

Supply chain network design problem for a new market opportunity in an agile manufacturing system

NASA Astrophysics Data System (ADS)

Babazadeh, Reza; Razmi, Jafar; Ghodsi, Reza

2012-08-01

The characteristics of today's competitive environment, such as the speed with which products are designed, manufactured, and distributed, and the need for higher responsiveness and lower operational cost, are forcing companies to search for innovative ways to do business. The concept of agile manufacturing has been proposed in response to these challenges for companies. This paper copes with the strategic and tactical level decisions in agile supply chain network design. An efficient mixed-integer linear programming model that is able to consider the key characteristics of agile supply chain such as direct shipments, outsourcing, different transportation modes, discount, alliance (process and information integration) between opened facilities, and maximum waiting time of customers for deliveries is developed. In addition, in the proposed model, the capacity of facilities is determined as decision variables, which are often assumed to be fixed. Computational results illustrate that the proposed model can be applied as a power tool in agile supply chain network design as well as in the integration of strategic decisions with tactical decisions.

Estimating Software-Development Costs With Greater Accuracy

NASA Technical Reports Server (NTRS)

Baker, Dan; Hihn, Jairus; Lum, Karen

2008-01-01

COCOMOST is a computer program for use in estimating software development costs. The goal in the development of COCOMOST was to increase estimation accuracy in three ways: (1) develop a set of sensitivity software tools that return not only estimates of costs but also the estimation error; (2) using the sensitivity software tools, precisely define the quantities of data needed to adequately tune cost estimation models; and (3) build a repository of software-cost-estimation information that NASA managers can retrieve to improve the estimates of costs of developing software for their project. COCOMOST implements a methodology, called '2cee', in which a unique combination of well-known pre-existing data-mining and software-development- effort-estimation techniques are used to increase the accuracy of estimates. COCOMOST utilizes multiple models to analyze historical data pertaining to software-development projects and performs an exhaustive data-mining search over the space of model parameters to improve the performances of effort-estimation models. Thus, it is possible to both calibrate and generate estimates at the same time. COCOMOST is written in the C language for execution in the UNIX operating system.

Analysis of Agility Performance of Supply Chain: A Case Study on Indian Automotive Manufacturer

NASA Astrophysics Data System (ADS)

Routroy, S.; Sharma, S.; Bhardwaj, A.

2018-04-01

Manufacturing companies should understand the changing customer needs and expectations, access and defend the competitive pressure, anticipate and manage the uncertain demand and supply chain risk, and implement the appropriate technology to survive and excel in today’s marketplace. Therefore, they are moving away from mass production (i.e. lean supply chain) to one based on fast-responsiveness and flexibility, capitalizing on the rapid advancement in internet technologies and factory-on-demand mode of production (i.e. agile supply chain). It is observed that manufacturing companies in India in general and automotive supply chain in specific are compelled to cultivate supply chain agility for enhancing its performance level on continuous basis and comparing its supply chain agility performance with competitors to survive and sustain in the competitive business environment. Therefore, a methodology is proposed to evaluate the supply chain agility of a manufacturing supply chain and compare its performance level with competitors using Fuzzy Analytic Hierarchy Process and Taguchi Loss Function. A case study is developed and the proposed methodology is applied to Indian automotive supply chain for explaining the salient features of it.

Monitoring software development through dynamic variables

NASA Technical Reports Server (NTRS)

Doerflinger, Carl W.; Basili, Victor R.

1983-01-01

Research conducted by the Software Engineering Laboratory (SEL) on the use of dynamic variables as a tool to monitor software development is described. Project independent measures which may be used in a management tool for monitoring software development are identified. Several FORTRAN projects with similar profiles are examined. The staff was experienced in developing these types of projects. The projects developed serve similar functions. Because these projects are similar some underlying relationships exist that are invariant between projects. These relationships, once well defined, may be used to compare the development of different projects to determine whether they are evolving the same way previous projects in this environment evolved.

Managing the Software Development Process

NASA Technical Reports Server (NTRS)

Lubelczky, Jeffrey T.; Parra, Amy

1999-01-01

The goal of any software development project is to produce a product that is delivered on time, within the allocated budget, and with the capabilities expected by the customer and unfortunately, this goal is rarely achieved. However, a properly managed project in a mature software engineering environment can consistently achieve this goal. In this paper we provide an introduction to three project success factors, a properly managed project, a competent project manager, and a mature software engineering environment. We will also present an overview of the benefits of a mature software engineering environment based on 24 years of data from the Software Engineering Lab, and suggest some first steps that an organization can take to begin benefiting from this environment. The depth and breadth of software engineering exceeds this paper, various references are cited with a goal of raising awareness and encouraging further investigation into software engineering and project management practices.

Scrum-Based Learning Environment: Fostering Self-Regulated Learning

ERIC Educational Resources Information Center

Linden, Tanya

2018-01-01

Academics teaching software development courses are experimenting with teaching methods aiming to improve students' learning experience and learning outcomes. Since Agile software development is gaining popularity in industry due to positive effects on managing projects, academics implement similar Agile approaches in student-centered learning…

Wavelength-Agile Optical Sensor for Exhaust Plume and Cryogenic Fluid Interrogation

NASA Technical Reports Server (NTRS)

Sanders, Scott T.; Chiaverini, Martin J.; Gramer, Daniel J.

2004-01-01

Two optical sensors developed in UW-Madison labs were evaluated for their potential to characterize rocket engine exhaust plumes and liquid oxygen (LOX) fluid properties. The plume sensor is based on wavelength-agile absorption spectroscopy A device called a chirped white pulse emitter (CWPE) is used to generate the wavelength agile light, scanning, for example, 1340 - 1560 nm every microsecond. Properties of the gases in the rocket plume (for example temperature and water mole fraction) can be monitored using these wavelength scans. We have performed preliminary tests in static gas cells, a laboratory GOX/GH2 thrust chamber, and a solid-fuel hybrid thrust chamber, and these initial tests demonstrate the potential of the CWPE for monitoring rocket plumes. The LOX sensor uses an alternative to wavelength agile sensing: two independent, fixed-wavelength lasers are combined into a single fiber. One laser is absorbed by LOX and the other not: by monitoring the differential transmission the LOX concentration in cryogenic feed lines can be inferred. The sensor was successful in interrogating static LOX pools in laboratory tests. Even in ice- and bubble-laden cryogenic fluids, LOX concentrations were measured to better than 1% with a 3 microsec time constant.

Firing Room Remote Application Software Development

NASA Technical Reports Server (NTRS)

Liu, Kan

2015-01-01

The Engineering and Technology Directorate (NE) at National Aeronautics and Space Administration (NASA) Kennedy Space Center (KSC) is designing a new command and control system for the checkout and launch of Space Launch System (SLS) and future rockets. The purposes of the semester long internship as a remote application software developer include the design, development, integration, and verification of the software and hardware in the firing rooms, in particular with the Mobile Launcher (ML) Launch Accessories (LACC) subsystem. In addition, a software test verification procedure document was created to verify and checkout LACC software for Launch Equipment Test Facility (LETF) testing.

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

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…

Automated software development workstation

NASA Technical Reports Server (NTRS)

1986-01-01

Engineering software development was automated using an expert system (rule-based) approach. The use of this technology offers benefits not available from current software development and maintenance methodologies. A workstation was built with a library or program data base with methods for browsing the designs stored; a system for graphical specification of designs including a capability for hierarchical refinement and definition in a graphical design system; and an automated code generation capability in FORTRAN. The workstation was then used in a demonstration with examples from an attitude control subsystem design for the space station. Documentation and recommendations are presented.

The influence of physical and cognitive factors on reactive agility performance in men basketball players.

PubMed

Scanlan, Aaron; Humphries, Brendan; Tucker, Patrick S; Dalbo, Vincent

2014-01-01

This study explored the influence of physical and cognitive measures on reactive agility performance in basketball players. Twelve men basketball players performed multiple sprint, Change of Direction Speed Test, and Reactive Agility Test trials. Pearson's correlation analyses were used to determine relationships between the predictor variables (stature, mass, body composition, 5-m, 10-m and 20-m sprint times, peak speed, closed-skill agility time, response time and decision-making time) and reactive agility time (response variable). Simple and stepwise regression analyses determined the individual influence of each predictor variable and the best predictor model for reactive agility time. Morphological (r = -0.45 to 0.19), sprint (r = -0.40 to 0.41) and change-of-direction speed measures (r = 0.43) had small to moderate correlations with reactive agility time. Response time (r = 0.76, P = 0.004) and decision-making time (r = 0.58, P = 0.049) had large to very large relationships with reactive agility time. Response time was identified as the sole predictor variable for reactive agility time in the stepwise model (R(2) = 0.58, P = 0.004). In conclusion, cognitive measures had the greatest influence on reactive agility performance in men basketball players. These findings suggest reaction and decision-making drills should be incorporated in basketball training programmes.

The advanced software development workstation project

NASA Technical Reports Server (NTRS)

Fridge, Ernest M., III; Pitman, Charles L.

1991-01-01

The Advanced Software Development Workstation (ASDW) task is researching and developing the technologies required to support Computer Aided Software Engineering (CASE) with the emphasis on those advanced methods, tools, and processes that will be of benefit to support all NASA programs. Immediate goals are to provide research and prototype tools that will increase productivity, in the near term, in projects such as the Software Support Environment (SSE), the Space Station Control Center (SSCC), and the Flight Analysis and Design System (FADS) which will be used to support the Space Shuttle and Space Station Freedom. Goals also include providing technology for development, evolution, maintenance, and operations. The technologies under research and development in the ASDW project are targeted to provide productivity enhancements during the software life cycle phase of enterprise and information system modeling, requirements generation and analysis, system design and coding, and system use and maintenance. On-line user's guides will assist users in operating the developed information system with knowledge base expert assistance.

Gamma-ray blazars: the combined AGILE and MAGIC views

NASA Astrophysics Data System (ADS)

Persic, M.; De Angelis, A.; Longo, F.; Tavani, M.

The large FOV of the AGILE Gamma-Ray Imaging Detector (GRID), 2.5 sr, will allow the whole sky to be surveyed once every 10 days in the 30 MeV - 50 GeV energy band down to 0.05 Crab Units. This fact gives the opportunity of performing the first flux-limited, high-energy g-ray all-sky survey. The high Galactic latitude point-source population is expected to be largely dominated by blazars. Several tens of blazars are expected to be detected by AGILE (e.g., Costamante & Ghisellini 2002), about half of which accessible to the ground-based MAGIC Cherenkov telescope. The latter can then carry out pointed observations of this subset of AGILE sources in the 50GeV - 10TeV band. Given the comparable sensitivities of AGILE/GRID and MAGIC in adjacent energy bands where the emitted radiation is produced by the same (e.g., SSC) mechanism, we expect that most of these sources can be detected by MAGIC. We expect this broadband g-ray strategy to enable discovery by MAGIC of 10-15 previously unknown TeV blazars.

Agile Methods in Air Force Sustainment: Status and Outlook

DTIC Science & Technology

2014-10-01

manage for it through iterations, anticipation and adaptation  unleash creativity and innovation by recognizing that individuals are the ultimate...073561993X X X Agile Project Management : Creating Innovative Products – 2nd Edition Jim Highsmith ISBN 0321658396 X Agile Retrospectives...X Leading Change John Kotter ISBN 0875847471 X Leading Geeks: How to Manage and Lead the People Who Deliver Technology Paul Glen ISBN

Learning Human Aspects of Collaborative Software Development

ERIC Educational Resources Information Center

Hadar, Irit; Sherman, Sofia; Hazzan, Orit

2008-01-01

Collaboration has become increasingly widespread in the software industry as systems have become larger and more complex, adding human complexity to the technological complexity already involved in developing software systems. To deal with this complexity, human-centric software development methods, such as Extreme Programming and other agile…

Framework Support For Knowledge-Based Software Development

NASA Astrophysics Data System (ADS)

Huseth, Steve

1988-03-01

The advent of personal engineering workstations has brought substantial information processing power to the individual programmer. Advanced tools and environment capabilities supporting the software lifecycle are just beginning to become generally available. However, many of these tools are addressing only part of the software development problem by focusing on rapid construction of self-contained programs by a small group of talented engineers. Additional capabilities are required to support the development of large programming systems where a high degree of coordination and communication is required among large numbers of software engineers, hardware engineers, and managers. A major player in realizing these capabilities is the framework supporting the software development environment. In this paper we discuss our research toward a Knowledge-Based Software Assistant (KBSA) framework. We propose the development of an advanced framework containing a distributed knowledge base that can support the data representation needs of tools, provide environmental support for the formalization and control of the software development process, and offer a highly interactive and consistent user interface.

Framework for Development of Object-Oriented Software

NASA Technical Reports Server (NTRS)

Perez-Poveda, Gus; Ciavarella, Tony; Nieten, Dan

2004-01-01

The Real-Time Control (RTC) Application Framework is a high-level software framework written in C++ that supports the rapid design and implementation of object-oriented application programs. This framework provides built-in functionality that solves common software development problems within distributed client-server, multi-threaded, and embedded programming environments. When using the RTC Framework to develop software for a specific domain, designers and implementers can focus entirely on the details of the domain-specific software rather than on creating custom solutions, utilities, and frameworks for the complexities of the programming environment. The RTC Framework was originally developed as part of a Space Shuttle Launch Processing System (LPS) replacement project called Checkout and Launch Control System (CLCS). As a result of the framework s development, CLCS software development time was reduced by 66 percent. The framework is generic enough for developing applications outside of the launch-processing system domain. Other applicable high-level domains include command and control systems and simulation/ training systems.

Effects of Ankle Braces Upon Agility Course Performance in High School Athletes

PubMed Central

Beriau, Mark R.; Cox, William B.; Manning, James

1994-01-01

The purpose of this study was to compare the effects of wearing the AircastTM Sports Stirrup, AircastTM Training brace, Swede-OTM brace, and DonJoyTM Ankle Ligament Protector while running an agility course. Eighty-five high school athletes with no history of ankle injury and no experience in wearing any ankle support served as subjects. Each subject participated in four separate testing sessions. During sessions 1 and 4, subjects ran the agility course under the control (unbraced) conditions. Sessions 2 and 3 consisted of randomly wearing the ankle braces while running the agility course. A questionnaire concerning support, comfort, and restriction was completed by each subject after wearing each of the braces. An analysis of variance (ANOVA) with repeated measures revealed that a significant difference existed between the agility times. Tukey's post hoc test indicated that a significant difference existed between each ankle brace and the control 2 agility times as well as a control 1 and control 2 time difference. The control time difference was attributed to a learning effect. An ANOVA with repeated measures of only the four braces revealed that a significant difference existed between the agility times. Tukey's post hoc test showed the only difference was between the DonJoy Ankle Ligament Protector and the Aircast Training brace. We concluded: 1) there is limited practical performance effect upon agility while wearing an ankle brace; and 2) an athlete's perceived comfort, support, and performance restriction are contributing factors that may directly influence the effectiveness of ankle bracing. PMID:16558284

Automated Estimation Of Software-Development Costs

NASA Technical Reports Server (NTRS)

Roush, George B.; Reini, William

1993-01-01

COSTMODL is automated software development-estimation tool. Yields significant reduction in risk of cost overruns and failed projects. Accepts description of software product developed and computes estimates of effort required to produce it, calendar schedule required, and distribution of effort and staffing as function of defined set of development life-cycle phases. Written for IBM PC(R)-compatible computers.

Software development: A paradigm for the future

NASA Technical Reports Server (NTRS)

Basili, Victor R.

1989-01-01

A new paradigm for software development that treats software development as an experimental activity is presented. It provides built-in mechanisms for learning how to develop software better and reusing previous experience in the forms of knowledge, processes, and products. It uses models and measures to aid in the tasks of characterization, evaluation and motivation. An organization scheme is proposed for separating the project-specific focus from the organization's learning and reuse focuses of software development. The implications of this approach for corporations, research and education are discussed and some research activities currently underway at the University of Maryland that support this approach are presented.

Manager's handbook for software development, revision 1

NASA Technical Reports Server (NTRS)

1990-01-01

Methods and aids for the management of software development projects are presented. The recommendations are based on analyses and experiences of the Software Engineering Laboratory (SEL) with flight dynamics software development. The management aspects of the following subjects are described: organizing the project, producing a development plan, estimating costs, scheduling, staffing, preparing deliverable documents, using management tools, monitoring the project, conducting reviews, auditing, testing, and certifying.

Starlink Software Developments

NASA Astrophysics Data System (ADS)

Bly, M. J.; Giaretta, D.; Currie, M. J.; Taylor, M.

Some current and upcoming software developments from Starlink were demonstrated. These included invoking traditional Starlink applications via web services, the current version of the ORAC-DR reduction pipeline, and some new Java-based tools including Treeview, an interactive explorer of hierarchical data structures.

Surface friction alters the agility of a small Australian marsupial.

PubMed

Wheatley, Rebecca; Clemente, Christofer J; Niehaus, Amanda C; Fisher, Diana O; Wilson, Robbie S

2018-04-23

Movement speed can underpin an animal's probability of success in ecological tasks. Prey often use agility to outmanoeuvre predators; however, faster speeds increase inertia and reduce agility. Agility is also constrained by grip, as the foot must have sufficient friction with the ground to apply the forces required for turning. Consequently, ground surface should affect optimum turning speed. We tested the speed-agility trade-off in buff-footed antechinus ( Antechinus mysticus ) on two different surfaces. Antechinus used slower turning speeds over smaller turning radii on both surfaces, as predicted by the speed-agility trade-off. Slipping was 64% more likely on the low-friction surface, and had a higher probability of occurring the faster the antechinus were running before the turn. However, antechinus compensated for differences in surface friction by using slower pre-turn speeds as their amount of experience on the low-friction surface increased, which consequently reduced their probability of slipping. Conversely, on the high-friction surface, antechinus used faster pre-turn speeds in later trials, which had no effect on their probability of slipping. Overall, antechinus used larger turning radii (0.733±0.062 versus 0.576±0.051 m) and slower pre-turn (1.595±0.058 versus 2.174±0.050 m s -1 ) and turning speeds (1.649±0.061 versus 2.01±0.054 m s -1 ) on the low-friction surface. Our results demonstrate the interactive effect of surface friction and the speed-agility trade-off on speed choice. To predict wild animals' movement speeds, future studies should examine the interactions between biomechanical trade-offs and terrain, and quantify the costs of motor mistakes in different ecological activities. © 2018. Published by The Company of Biologists Ltd.

Resource utilization during software development

NASA Technical Reports Server (NTRS)

Zelkowitz, Marvin V.

1988-01-01

This paper discusses resource utilization over the life cycle of software development and discusses the role that the current 'waterfall' model plays in the actual software life cycle. Software production in the NASA environment was analyzed to measure these differences. The data from 13 different projects were collected by the Software Engineering Laboratory at NASA Goddard Space Flight Center and analyzed for similarities and differences. The results indicate that the waterfall model is not very realistic in practice, and that as technology introduces further perturbations to this model with concepts like executable specifications, rapid prototyping, and wide-spectrum languages, we need to modify our model of this process.

First GRB detections with the AGILE Minicalorimeter

NASA Astrophysics Data System (ADS)

Marisaldi, M.; Labanti, C.; Fuschino, F.; Galli, M.; Tavani, M.; Bulgarelli, A.; Gianotti, F.; Trifoglio, M.; Argan, A.

2008-05-01

The Minicalorimeter (MCAL) onboard the AGILE satellite is a 1400 cm2 scintillation detector sensitive in the energy range 0.3-200 MeV. MCAL works both as a slave of the AGILE Silicon Tracker and as an autonomous detector for transient events (BURST mode). A dedicated onboard Burst Search logic scans BURST mode data in search of count rate increase. Peculiar characteristics of the detector are the high energy spectral coverage and a timing resolution of about 2 microseconds. Even if a trigger is not issued, BURST mode data are used to build a broad band energy spectrum (scientific ratemeters) organized in 11 bands for each of the two MCAL detection planes, with a time resolution of 1 second. After the first engineering commissioning phase, following the AGILE launch on 23rd April 2007, between 22nd June and 5th November 2007 eighteen GRBs were detected offline in the scientific ratemeters data, with a detection rate of about one per week. In this paper the capabilities of the detector will be described and an overview of the first detected GRBs will be given.

Evaluating software development by analysis of changes: The data from the software engineering laboratory

NASA Technical Reports Server (NTRS)

1982-01-01

An effective data collection methodology for evaluating software development methodologies was applied to four different software development projects. Goals of the data collection included characterizing changes and errors, characterizing projects and programmers, identifying effective error detection and correction techniques, and investigating ripple effects. The data collected consisted of changes (including error corrections) made to the software after code was written and baselined, but before testing began. Data collection and validation were concurrent with software development. Changes reported were verified by interviews with programmers.

Testing Software Development Project Productivity Model

NASA Astrophysics Data System (ADS)

Lipkin, Ilya

Software development is an increasingly influential factor in today's business environment, and a major issue affecting software development is how an organization estimates projects. If the organization underestimates cost, schedule, and quality requirements, the end results will not meet customer needs. On the other hand, if the organization overestimates these criteria, resources that could have been used more profitably will be wasted. There is no accurate model or measure available that can guide an organization in a quest for software development, with existing estimation models often underestimating software development efforts as much as 500 to 600 percent. To address this issue, existing models usually are calibrated using local data with a small sample size, with resulting estimates not offering improved cost analysis. This study presents a conceptual model for accurately estimating software development, based on an extensive literature review and theoretical analysis based on Sociotechnical Systems (STS) theory. The conceptual model serves as a solution to bridge organizational and technological factors and is validated using an empirical dataset provided by the DoD. Practical implications of this study allow for practitioners to concentrate on specific constructs of interest that provide the best value for the least amount of time. This study outlines key contributing constructs that are unique for Software Size E-SLOC, Man-hours Spent, and Quality of the Product, those constructs having the largest contribution to project productivity. This study discusses customer characteristics and provides a framework for a simplified project analysis for source selection evaluation and audit task reviews for the customers and suppliers. Theoretical contributions of this study provide an initial theory-based hypothesized project productivity model that can be used as a generic overall model across several application domains such as IT, Command and Control

Miniature EVA Software Defined Radio

NASA Technical Reports Server (NTRS)

Pozhidaev, Aleksey

2012-01-01

As NASA embarks upon developing the Next-Generation Extra Vehicular Activity (EVA) Radio for deep space exploration, the demands on EVA battery life will substantially increase. The number of modes and frequency bands required will continue to grow in order to enable efficient and complex multi-mode operations including communications, navigation, and tracking applications. Whether conducting astronaut excursions, communicating to soldiers, or first responders responding to emergency hazards, NASA has developed an innovative, affordable, miniaturized, power-efficient software defined radio that offers unprecedented power-efficient flexibility. This lightweight, programmable, S-band, multi-service, frequency- agile EVA software defined radio (SDR) supports data, telemetry, voice, and both standard and high-definition video. Features include a modular design, an easily scalable architecture, and the EVA SDR allows for both stationary and mobile battery powered handheld operations. Currently, the radio is equipped with an S-band RF section. However, its scalable architecture can accommodate multiple RF sections simultaneously to cover multiple frequency bands. The EVA SDR also supports multiple network protocols. It currently implements a Hybrid Mesh Network based on the 802.11s open standard protocol. The radio targets RF channel data rates up to 20 Mbps and can be equipped with a real-time operating system (RTOS) that can be switched off for power-aware applications. The EVA SDR's modular design permits implementation of the same hardware at all Network Nodes concept. This approach assures the portability of the same software into any radio in the system. It also brings several benefits to the entire system including reducing system maintenance, system complexity, and development cost.

Flight dynamics research for highly agile aircraft

NASA Technical Reports Server (NTRS)

Nguyen, Luat T.

1989-01-01

This paper highlights recent results of research conducted at the NASA Langley Research Center as part of a broad flight dynamics program aimed at developing technology that will enable future combat aircraft to achieve greatly enhanced agility capability at subsonic combat conditions. Studies of advanced control concepts encompassing both propulsive and aerodynamic approaches are reviewed. Dynamic stall phenomena and their potential impact on maneuvering performance and stability are summarized. Finally, issues of mathematical modeling of complex aerodynamics occurring during rapid, large amplitude maneuvers are discussed.

Team-based work and work system balance in the context of agile manufacturing.

PubMed

Yauch, Charlene A

2007-01-01

Manufacturing agility is the ability to prosper in an environment characterized by constant and unpredictable change. The purpose of this paper is to analyze team attributes necessary to facilitate agile manufacturing, and using Balance Theory as a framework, it evaluates the potential positive and negative impacts related to these team attributes that could alter the balance of work system elements and resulting "stress load" experienced by persons working on agile teams. Teams operating within the context of agile manufacturing are characterized as multifunctional, dynamic, cooperative, and virtual. A review of the literature relevant to each of these attributes is provided, as well as suggestions for future research.

Software Engineering Principles for Courseware Development.

ERIC Educational Resources Information Center

Magel, Kenneth

1980-01-01

Courseware (computer based curriculum materials) development should follow the lessons learned by software engineers. The most important of 28 principles of software development presented here include a stress on human readability, the importance of early planning and analysis, the need for independent evaluation, and the need to be flexible.…

Handbook for Implementing Agile in Department of Defense Information Technology Acquisition

DTIC Science & Technology

2010-12-15

Wire-frame Mockup of iTunes Cover Flow Feature (source: http://www.balsamiq.com/products/mockups/examples#mytunez...programming. The JOPES customer was included early in the development process in order to understand requirements management (story cards ), observe...transition by teaching the new members Agile processes, such as story card development, refactoring, and pair programming. Additionally, the team worked to

Red Teaming Agility (Briefing Charts)

DTIC Science & Technology

2014-06-01

are termed “ antifragile ”. Black Swan Model for Deep Red Futures The future is dominated not by trends, but by outliers, extreme events that lie...disproportionately higher mission impact. Agility is a measure of antifragile systems Red Teaming Defined Red Teaming is a function to provide

Recommended approach to software development, revision 3

NASA Technical Reports Server (NTRS)

Landis, Linda; Waligora, Sharon; Mcgarry, Frank; Pajerski, Rose; Stark, Mike; Johnson, Kevin Orlin; Cover, Donna

1992-01-01

Guidelines for an organized, disciplined approach to software development that is based on studies conducted by the Software Engineering Laboratory (SEL) since 1976 are presented. It describes methods and practices for each phase of a software development life cycle that starts with requirements definition and ends with acceptance testing. For each defined life cycle phase, guidelines for the development process and its management, and for the products produced and their reviews are presented.

COSTMODL: An automated software development cost estimation tool

NASA Technical Reports Server (NTRS)

Roush, George B.

1991-01-01

The cost of developing computer software continues to consume an increasing portion of many organizations' total budgets, both in the public and private sector. As this trend develops, the capability to produce reliable estimates of the effort and schedule required to develop a candidate software product takes on increasing importance. The COSTMODL program was developed to provide an in-house capability to perform development cost estimates for NASA software projects. COSTMODL is an automated software development cost estimation tool which incorporates five cost estimation algorithms including the latest models for the Ada language and incrementally developed products. The principal characteristic which sets COSTMODL apart from other software cost estimation programs is its capacity to be completely customized to a particular environment. The estimation equations can be recalibrated to reflect the programmer productivity characteristics demonstrated by the user's organization, and the set of significant factors which effect software development costs can be customized to reflect any unique properties of the user's development environment. Careful use of a capability such as COSTMODL can significantly reduce the risk of cost overruns and failed projects.

Reducing Risk in DoD Software-Intensive Systems Development

DTIC Science & Technology

2016-03-01

intensive systems development risk. This research addresses the use of the Technical Readiness Assessment (TRA) using the nine-level software Technology...The software TRLs are ineffective in reducing technical risk for the software component development. • Without the software TRLs, there is no...effective method to perform software TRA or reduce the technical development risk. The software component will behave as a new, untried technology in nearly

Software Development Group. Software Review Center. Microcomputing Working Paper Series.

ERIC Educational Resources Information Center

Perkey, Nadine; Smith, Shirley C.

Two papers describe the roles of the Software Development Group (SDG) and the Software Review Center (SRC) at Drexel University. The first paper covers the primary role of the SDG, which is designed to assist Drexel faculty with the technical design and programming of courseware for the Apple Macintosh microcomputer; the relationship of the SDG…

Understanding Acceptance of Software Metrics--A Developer Perspective

ERIC Educational Resources Information Center

Umarji, Medha

2009-01-01

Software metrics are measures of software products and processes. Metrics are widely used by software organizations to help manage projects, improve product quality and increase efficiency of the software development process. However, metrics programs tend to have a high failure rate in organizations, and developer pushback is one of the sources…

Enhanced detection of terrestrial gamma-ray flashes by AGILE.

PubMed

Marisaldi, M; Argan, A; Ursi, A; Gjesteland, T; Fuschino, F; Labanti, C; Galli, M; Tavani, M; Pittori, C; Verrecchia, F; D'Amico, F; Østgaard, N; Mereghetti, S; Campana, R; Cattaneo, P W; Bulgarelli, A; Colafrancesco, S; Dietrich, S; Longo, F; Gianotti, F; Giommi, P; Rappoldi, A; Trifoglio, M; Trois, A

2015-11-16

At the end of March 2015 the onboard software configuration of the Astrorivelatore Gamma a Immagini Leggero (AGILE) satellite was modified in order to disable the veto signal of the anticoincidence shield for the minicalorimeter instrument. The motivation for such a change was the understanding that the dead time induced by the anticoincidence prevented the detection of a large fraction of Terrestrial Gamma-Ray Flashes (TGFs). The configuration change was highly successful resulting in an increase of one order of magnitude in TGF detection rate. As expected, the largest fraction of the new events has short duration (<100 μs), and part of them has simultaneous association with lightning sferics detected by the World Wide Lightning Location Network. The new configuration provides the largest TGF detection rate surface density (TGFs/km 2 /yr) to date, opening prospects for improved correlation studies with lightning and atmospheric parameters on short spatial and temporal scales along the equatorial region.

Importance of Reactive Agility and Change of Direction Speed in Differentiating Performance Levels in Junior Soccer Players: Reliability and Validity of Newly Developed Soccer-Specific Tests

PubMed Central

Pojskic, Haris; Åslin, Erik; Krolo, Ante; Jukic, Ivan; Uljevic, Ognjen; Spasic, Miodrag; Sekulic, Damir

2018-01-01

Agility is a significant determinant of success in soccer; however, studies have rarely presented and evaluated soccer-specific tests of reactive agility (S_RAG) and non-reactive agility (change of direction speed – S_CODS) or their applicability in this sport. The aim of this study was to define the reliability and validity of newly developed tests of the S_RAG and S_CODS to discriminate between the performance levels of junior soccer players. The study consisted of 20 players who were involved at the highest national competitive rank (all males; age: 17.0 ± 0.9 years), divided into three playing positions (defenders, midfielders, and forwards) and two performance levels (U17 and U19). Variables included body mass (BM), body height, body fat percentage, 20-m sprint, squat jump, countermovement jump, reactive-strength-index, unilateral jump, 1RM-back-squat, S_CODS, and three protocols of S_RAG. The reliabilities of the S_RAG and S_CODS were appropriate to high (ICC: 0.70 to 0.92), with the strongest reliability evidenced for the S_CODS. The S_CODS and S_RAG shared 25–40% of the common variance. Playing positions significantly differed in BM (large effect-size differences [ES]; midfielders were lightest) and 1RM-back-squat (large ES; lowest results in midfielders). The performance levels significantly differed in age and experience in soccer; U19 achieved better results in the S_CODS (t-test: 3.61, p < 0.05, large ES) and two S_RAG protocols (t-test: 2.14 and 2.41, p < 0.05, moderate ES). Newly developed tests of soccer-specific agility are applicable to differentiate U17 and U19 players. Coaches who work with young soccer athletes should be informed that the development of soccer-specific CODS and RAG in this age is mostly dependent on training of the specific motor proficiency. PMID:29867552

Modular Infrastructure for Rapid Flight Software Development

NASA Technical Reports Server (NTRS)

Pires, Craig

2010-01-01

This slide presentation reviews the use of modular infrastructure to assist in the development of flight software. A feature of this program is the use of model based approach for application unique software. A review of two programs that this approach was use on are: the development of software for Hover Test Vehicle (HTV), and Lunar Atmosphere and Dust Environment Experiment (LADEE).

General guidelines for biomedical software development

PubMed Central

Silva, Luis Bastiao; Jimenez, Rafael C.; Blomberg, Niklas; Luis Oliveira, José

2017-01-01

Most bioinformatics tools available today were not written by professional software developers, but by people that wanted to solve their own problems, using computational solutions and spending the minimum time and effort possible, since these were just the means to an end. Consequently, a vast number of software applications are currently available, hindering the task of identifying the utility and quality of each. At the same time, this situation has hindered regular adoption of these tools in clinical practice. Typically, they are not sufficiently developed to be used by most clinical researchers and practitioners. To address these issues, it is necessary to re-think how biomedical applications are built and adopt new strategies that ensure quality, efficiency, robustness, correctness and reusability of software components. We also need to engage end-users during the development process to ensure that applications fit their needs. In this review, we present a set of guidelines to support biomedical software development, with an explanation of how they can be implemented and what kind of open-source tools can be used for each specific topic. PMID:28443186

Developing the E-Scape Software System

ERIC Educational Resources Information Center

Derrick, Karim

2012-01-01

Most innovations have contextual pre-cursors that prompt new ways of thinking and in their turn help to give form to the new reality. This was the case with the e-scape software development process. The origins of the system existed in software components and ideas that we had developed through previous projects, but the ultimate direction we took…

Smart Healthcare Agility Management - Tojisha Doctrine by Self-synchronization

DTIC Science & Technology

2014-06-01

impossibility at our age. One is the technology of space elevator and another is the space-walk tourism which the project has existed since the mid-20 th...In regards to the technologies of space-walk tourism , increase of patents related to the technologies of Pulse Detention Engine worldwide is some...medicine, and there is some reference cases such as "open agility" and "closed agility" is immersed in training specifically in sports science which

Adaptive Global Innovative Learning Environment for Glioblastoma: GBM AGILE.

PubMed

Alexander, Brian M; Ba, Sujuan; Berger, Mitchel S; Berry, Donald A; Cavenee, Webster K; Chang, Susan M; Cloughesy, Timothy F; Jiang, Tao; Khasraw, Mustafa; Li, Wenbin; Mittman, Robert; Poste, George H; Wen, Patrick Y; Yung, W K Alfred; Barker, Anna D

2018-02-15

Glioblastoma (GBM) is a deadly disease with few effective therapies. Although much has been learned about the molecular characteristics of the disease, this knowledge has not been translated into clinical improvements for patients. At the same time, many new therapies are being developed. Many of these therapies have potential biomarkers to identify responders. The result is an enormous amount of testable clinical questions that must be answered efficiently. The GBM Adaptive Global Innovative Learning Environment (GBM AGILE) is a novel, multi-arm, platform trial designed to address these challenges. It is the result of the collective work of over 130 oncologists, statisticians, pathologists, neurosurgeons, imagers, and translational and basic scientists from around the world. GBM AGILE is composed of two stages. The first stage is a Bayesian adaptively randomized screening stage to identify effective therapies based on impact on overall survival compared with a common control. This stage also finds the population in which the therapy shows the most promise based on clinical indication and biomarker status. Highly effective therapies transition in an inferentially seamless manner in the identified population to a second confirmatory stage. The second stage uses fixed randomization to confirm the findings from the first stage to support registration. Therapeutic arms with biomarkers may be added to the trial over time, while others complete testing. The design of GBM AGILE enables rapid clinical testing of new therapies and biomarkers to speed highly effective therapies to clinical practice. Clin Cancer Res; 24(4); 737-43. ©2017 AACR . ©2017 American Association for Cancer Research.

Software Engineering Research/Developer Collaborations in 2005

NASA Technical Reports Server (NTRS)

Pressburger, Tom

2006-01-01

In CY 2005, three collaborations between software engineering technology providers and NASA software development personnel deployed three software engineering technologies on NASA development projects (a different technology on each project). The main purposes were to benefit the projects, infuse the technologies if beneficial into NASA, and give feedback to the technology providers to improve the technologies. Each collaboration project produced a final report. Section 2 of this report summarizes each project, drawing from the final reports and communications with the software developers and technology providers. Section 3 indicates paths to further infusion of the technologies into NASA practice. Section 4 summarizes some technology transfer lessons learned. Also included is an acronym list.

Concept Development for Software Health Management

NASA Technical Reports Server (NTRS)

Riecks, Jung; Storm, Walter; Hollingsworth, Mark

2011-01-01

This report documents the work performed by Lockheed Martin Aeronautics (LM Aero) under NASA contract NNL06AA08B, delivery order NNL07AB06T. The Concept Development for Software Health Management (CDSHM) program was a NASA funded effort sponsored by the Integrated Vehicle Health Management Project, one of the four pillars of the NASA Aviation Safety Program. The CD-SHM program focused on defining a structured approach to software health management (SHM) through the development of a comprehensive failure taxonomy that is used to characterize the fundamental failure modes of safety-critical software.

The mini-calorimeter of the AGILE satellite

NASA Astrophysics Data System (ADS)

Labanti, C.; Marisaldi, M.; Fuschino, F.; Galli, M.; Argan, A.; Bulgarelli, A.; Costa, E.; Di Cocco, G.; Gianotti, F.; Tavani, M.; Trifoglio, M.

2006-06-01

AGILE is a small space mission of the Italian Space Agency (ASI) devoted to astrophysics in the gamma-ray energy range 30 MeV - 50 GeV, and in the X-ray band 15 keV - 45 keV. The AGILE Payload is composed of three instruments: a gamma-ray imager based on a Tungsten-Silicon Tracker (ST), for observations in the gamma ray energy range 30 MeV - 50 GeV, a Silicon based X-ray detector, Super-Agile (SA), for imaging in the range 15 keV - 40 keV and a CsI(Tl) Mini-Calorimeter (MCAL) that detects gamma rays or particle energy deposits between 300 keV and 200 MeV. The payload is currently fully integrated and the satellite is expected to be launched in the second half of 2006. MCAL is composed of 30 CsI(Tl) scintillator detectors with the shape of a bar with photodiode readout at both ends, arranged in two orthogonal layers. MCAL can work both as a slave of the ST and as an independent gamma-ray detector for the detection of transients and Gamma Ray Bursts. In this paper a detailed description of MCAL is presented together with the first on ground calibration results.

Assessment of Specificity of the Badcamp Agility test for Badminton Players

PubMed Central

de França Bahia Loureiro, Luiz; Costa Dias, Mário Oliveira; Cremasco, Felipe Couto; da Silva, Maicon Guimarães; de Freitas, Paulo Barbosa

2017-01-01

Abstract The Badcamp agility test was created to evaluate agility of badminton players. The Badcamp is a valid and reliable test, however, a doubt about the need for the use of this test exists as simpler tests could provide similar information about agility in badminton players. Thus, the aim of this study was to examine the specificity of the Badcamp, comparing the performance of badminton players and athletes from other sports in the Badcamp and the shuttle run agility test (SRAT). Sixty-four young male and female athletes aged between 14 and 16 years participated in the study. They were divided into 4 groups of 16 according to their sport practices: badminton, tennis, team sport (basketball and volleyball), and track and field. We compared the groups in both tests, the Badcamp and SRAT. The results revealed that the group of badminton players was faster compared to all other groups in the Badcamp. However, in the SRAT there were no differences among groups composed of athletes from open skill sports (e.g., badminton, tennis, and team sports), and a considerable reduction of the difference between badminton players and track and field athletes. Thus, we concluded that the Badcamp test is a specific agility test for badminton players and should be considered in evaluating athletes of this sport modality. PMID:28713471

Assessment of Specificity of the Badcamp Agility test for Badminton Players.

PubMed

de França Bahia Loureiro, Luiz; Costa Dias, Mário Oliveira; Cremasco, Felipe Couto; da Silva, Maicon Guimarães; de Freitas, Paulo Barbosa

2017-06-01

The Badcamp agility test was created to evaluate agility of badminton players. The Badcamp is a valid and reliable test, however, a doubt about the need for the use of this test exists as simpler tests could provide similar information about agility in badminton players. Thus, the aim of this study was to examine the specificity of the Badcamp, comparing the performance of badminton players and athletes from other sports in the Badcamp and the shuttle run agility test (SRAT). Sixty-four young male and female athletes aged between 14 and 16 years participated in the study. They were divided into 4 groups of 16 according to their sport practices: badminton, tennis, team sport (basketball and volleyball), and track and field. We compared the groups in both tests, the Badcamp and SRAT. The results revealed that the group of badminton players was faster compared to all other groups in the Badcamp. However, in the SRAT there were no differences among groups composed of athletes from open skill sports (e.g., badminton, tennis, and team sports), and a considerable reduction of the difference between badminton players and track and field athletes. Thus, we concluded that the Badcamp test is a specific agility test for badminton players and should be considered in evaluating athletes of this sport modality.

Automated real-time software development

NASA Technical Reports Server (NTRS)

Jones, Denise R.; Walker, Carrie K.; Turkovich, John J.

1993-01-01

A Computer-Aided Software Engineering (CASE) system has been developed at the Charles Stark Draper Laboratory (CSDL) under the direction of the NASA Langley Research Center. The CSDL CASE tool provides an automated method of generating source code and hard copy documentation from functional application engineering specifications. The goal is to significantly reduce the cost of developing and maintaining real-time scientific and engineering software while increasing system reliability. This paper describes CSDL CASE and discusses demonstrations that used the tool to automatically generate real-time application code.

Software development for airborne radar

NASA Astrophysics Data System (ADS)

Sundstrom, Ingvar G.

Some aspects for development of software in a modern multimode airborne nose radar are described. First, an overview of where software is used in the radar units is presented. The development phases-system design, functional design, detailed design, function verification, and system verification-are then used as the starting point for the discussion. Methods, tools, and the most important documents are described. The importance of video flight recording in the early stages and use of a digital signal generators for performance verification is emphasized. Some future trends are discussed.

Survey-based analysis of risk factors for injury among dogs participating in agility training and competition events.

PubMed

Cullen, Kimberley L; Dickey, James P; Bent, Leah R; Thomason, Jeffrey J; Moëns, Noel M M

2013-10-01

To identify potential risk factors for agility-related injuries among dogs. Internet-based, retrospective, cross-sectional survey. 3,801 privately owned dogs participating in agility training or trials. A retrospective electronic survey was used to investigate potential risk factors for injury among dogs participating in agility-related activities. Respondents were handlers recruited through member lists of large canine agility associations in Canada and the United Kingdom and through promotion on an agility blog site. Variables evaluated included demographic information for handlers and dogs, exposure variables (eg, frequency of agility practice and competition in the past year), and use of preventive measures intended to keep dogs fit for agility (warmup, cooldown, or conditioning exercises; alternative therapeutic treatments [eg, acupuncture, massage, or chiropractic care]; or dietary supplement products). Data were collected from 1,669 handlers of 3,801 agility dogs internationally; 1,209 (32%) dogs incurred ≥ 1 injury. Previous injury (OR, 100.5), ≤ 4 years of agility experience for dogs (OR, 1.5), use of alternative therapeutic treatments (OR, 1.5), and Border Collie breed (OR, 1.7) were associated with increased odds of injury. Handlers having 5 to 10 or > 10 years of experience (OR, 0.8 and 0.6, respectively) and dogs having > 4 years of experience in the sport (OR, 0.6) were associated with decreased odds of injury. Specific factors were associated with agility-related injuries in dogs. Educational prevention strategies should target at-risk populations in an effort to reduce potential injuries. Future research should focus on the biomechanical factors associated with agility-related injuries.

Global Software Development with Cloud Platforms

NASA Astrophysics Data System (ADS)

Yara, Pavan; Ramachandran, Ramaseshan; Balasubramanian, Gayathri; Muthuswamy, Karthik; Chandrasekar, Divya

Offshore and outsourced distributed software development models and processes are facing challenges, previously unknown, with respect to computing capacity, bandwidth, storage, security, complexity, reliability, and business uncertainty. Clouds promise to address these challenges by adopting recent advances in virtualization, parallel and distributed systems, utility computing, and software services. In this paper, we envision a cloud-based platform that addresses some of these core problems. We outline a generic cloud architecture, its design and our first implementation results for three cloud forms - a compute cloud, a storage cloud and a cloud-based software service- in the context of global distributed software development (GSD). Our ”compute cloud” provides computational services such as continuous code integration and a compile server farm, ”storage cloud” offers storage (block or file-based) services with an on-line virtual storage service, whereas the on-line virtual labs represent a useful cloud service. We note some of the use cases for clouds in GSD, the lessons learned with our prototypes and identify challenges that must be conquered before realizing the full business benefits. We believe that in the future, software practitioners will focus more on these cloud computing platforms and see clouds as a means to supporting a ecosystem of clients, developers and other key stakeholders.

Software Architecture Evaluation in Global Software Development Projects

NASA Astrophysics Data System (ADS)

Salger, Frank

Due to ever increasing system complexity, comprehensive methods for software architecture evaluation become more and more important. This is further stressed in global software development (GSD), where the software architecture acts as a central knowledge and coordination mechanism. However, existing methods for architecture evaluation do not take characteristics of GSD into account. In this paper we discuss what aspects are specific for architecture evaluations in GSD. Our experiences from GSD projects at Capgemini sd&m indicate, that architecture evaluations differ in how rigorously one has to assess modularization, architecturally relevant processes, knowledge transfer and process alignment. From our project experiences, we derive nine good practices, the compliance to which should be checked in architecture evaluations in GSD. As an example, we discuss how far the standard architecture evaluation method used at Capgemini sd&m already considers the GSD-specific good practices, and outline what extensions are necessary to achieve a comprehensive architecture evaluation framework for GSD.

Clustering-based urbanisation to improve enterprise information systems agility

NASA Astrophysics Data System (ADS)

Imache, Rabah; Izza, Said; Ahmed-Nacer, Mohamed

2015-11-01

Enterprises are daily facing pressures to demonstrate their ability to adapt quickly to the unpredictable changes of their dynamic in terms of technology, social, legislative, competitiveness and globalisation. Thus, to ensure its place in this hard context, enterprise must always be agile and must ensure its sustainability by a continuous improvement of its information system (IS). Therefore, the agility of enterprise information systems (EISs) can be considered today as a primary objective of any enterprise. One way of achieving this objective is by the urbanisation of the EIS in the context of continuous improvement to make it a real asset servicing enterprise strategy. This paper investigates the benefits of EISs urbanisation based on clustering techniques as a driver for agility production and/or improvement to help managers and IT management departments to improve continuously the performance of the enterprise and make appropriate decisions in the scope of the enterprise objectives and strategy. This approach is applied to the urbanisation of a tour operator EIS.

Design of a Wireless Sensor System with the Algorithms of Heart Rate and Agility Index for Athlete Evaluation

PubMed Central

Li, Meina; Kim, Youn Tae

2017-01-01

Athlete evaluation systems can effectively monitor daily training and boost performance to reduce injuries. Conventional heart-rate measurement systems can be easily affected by artifact movement, especially in the case of athletes. Significant noise can be generated owing to high-intensity activities. To improve the comfort for athletes and the accuracy of monitoring, we have proposed to combine robust heart rate and agility index monitoring algorithms into a small, light, and single node. A band-pass-filter-based R-wave detection algorithm was developed. The agility index was calculated by preprocessing with band-pass filtering and employing the zero-crossing detection method. The evaluation was conducted under both laboratory and field environments to verify the accuracy and reliability of the algorithm. The heart rate and agility index measurements can be wirelessly transmitted to a personal computer in real time by the ZigBee telecommunication system. The results show that the error rate of measurement of the heart rate is within 2%, which is comparable with that of the traditional wired measurement method. The sensitivity of the agility index, which could be distinguished as the activity speed, changed slightly. Thus, we confirmed that the developed algorithm could be used in an effective and safe exercise-evaluation system for athletes. PMID:29039763

The Effect of Acceleration Sprint and Zig-zag Drill Combination to Increase Students’ Speed and Agility

NASA Astrophysics Data System (ADS)

Bana, O.; Mintarto, E.; Kusnanik, N. W.

2018-01-01

The purpose of this research is to analyze the following factors: (1) how far the effect of exercise acceleration sprint on the speed and agility (2) how much influence the zig-zag drill combination to the speed and agility (3) and is there any difference between the effects of exercise acceleration sprint and practice zig-zag drill combination of the speed and agility. This research is quantitative with quasi-experimental approach. The design of this study is matching only design.This study was conducted on 33 male students who take part in extracurricular and divided into 3 groups with 11 students in each group. Group 1 was given training of acceleration sprint, group 2 was given zig-zag training combination drills of conventional and exercises for group 3, for 8 weeks. The data collection was using sprint 30 meter to test the speed and agility t-test to test agility. Data were analyzed using t-test and analysis of variance. The conclusion of the research is (1) there is a significant effect of exercise acceleration sprint for the speed and agility, (2) there is a significant influence combination zig-zag drills, on speed and agility (3) and exercise acceleration sprint have more effect on the speed and agility.

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

Agile Infrastructure Monitoring

NASA Astrophysics Data System (ADS)

Andrade, P.; Ascenso, J.; Fedorko, I.; Fiorini, B.; Paladin, M.; Pigueiras, L.; Santos, M.

2014-06-01

At the present time, data centres are facing a massive rise in virtualisation and cloud computing. The Agile Infrastructure (AI) project is working to deliver new solutions to ease the management of CERN data centres. Part of the solution consists in a new "shared monitoring architecture" which collects and manages monitoring data from all data centre resources. In this article, we present the building blocks of this new monitoring architecture, the different open source technologies selected for each architecture layer, and how we are building a community around this common effort.

Agile Walking Robot

NASA Technical Reports Server (NTRS)

Larimer, Stanley J.; Lisec, Thomas R.; Spiessbach, Andrew J.; Waldron, Kenneth J.

1990-01-01

Proposed agile walking robot operates over rocky, sandy, and sloping terrain. Offers stability and climbing ability superior to other conceptual mobile robots. Equipped with six articulated legs like those of insect, continually feels ground under leg before applying weight to it. If leg sensed unexpected object or failed to make contact with ground at expected point, seeks alternative position within radius of 20 cm. Failing that, robot halts, examines area around foot in detail with laser ranging imager, and replans entire cycle of steps for all legs before proceeding.

The MINERVA Software Development Process

NASA Technical Reports Server (NTRS)

Narkawicz, Anthony; Munoz, Cesar A.; Dutle, Aaron M.

2017-01-01

This paper presents a software development process for safety-critical software components of cyber-physical systems. The process is called MINERVA, which stands for Mirrored Implementation Numerically Evaluated against Rigorously Verified Algorithms. The process relies on formal methods for rigorously validating code against its requirements. The software development process uses: (1) a formal specification language for describing the algorithms and their functional requirements, (2) an interactive theorem prover for formally verifying the correctness of the algorithms, (3) test cases that stress the code, and (4) numerical evaluation on these test cases of both the algorithm specifications and their implementations in code. The MINERVA process is illustrated in this paper with an application to geo-containment algorithms for unmanned aircraft systems. These algorithms ensure that the position of an aircraft never leaves a predetermined polygon region and provide recovery maneuvers when the region is inadvertently exited.

Effective Software Engineering Leadership for Development Programs

ERIC Educational Resources Information Center

Cagle West, Marsha

2010-01-01

Software is a critical component of systems ranging from simple consumer appliances to complex health, nuclear, and flight control systems. The development of quality, reliable, and effective software solutions requires the incorporation of effective software engineering processes and leadership. Processes, approaches, and methodologies for…

Modification of Agility Running Technique in Reaction to a Defender in Rugby Union

PubMed Central

Wheeler, Keane W.; Sayers, Mark G.L.

2010-01-01

Three-dimensional kinematic analysis examined agility running technique during pre-planned and reactive performance conditions specific to attacking ball carries in rugby union. The variation to running technique of 8 highly trained rugby union players was compared between agility conditions (pre-planned and reactive) and also agility performance speeds (fast, moderate and slow). Kinematic measures were used to determine the velocity of the centre of mass (COM) in the anteroposterior (running speed) and mediolateral (lateral movement speed) planes. The position of foot-strike and toe-off was also examined for the step prior to the agility side- step (pre-change of direction phase) and then the side-step (change of direction phase). This study demonstrated that less lateral movement speed towards the intended direction change occurred during reactive compared to pre-planned conditions at pre-change of direction (0.08 ± 0.28 m·s-1 and 0.42 ± 0.25 m·s-1, respectively) and change of direction foot-strikes (0.25 ± 0.42 m·s-1 and 0.69 ± 0.43 m·s-1, respectively). Less lateral movement speed during reactive conditions was associated with greater lateral foot displacement (44.52 ± 6.10% leg length) at the change of direction step compared to pre-planned conditions (41.35 ± 5.85%). Importantly, the anticipation abilities during reactive conditions provided a means to differentiate between speeds of agility performance, with faster performances displaying greater lateral movement speed at the change of direction foot- strike (0.52 ± 0.34 m·s-1) compared to moderate (0.20 ± 0.37 m·s-1) and slow (-0.08 ± 0.31 m·s-1). The changes to running technique during reactive conditions highlight the need to incorporate decision-making in rugby union agility programs. Key points Changes to running technique occur when required to make a decision. Fast agility performers use different stepping strategies in reactive conditions. Decision-making must be incorporated in

The Effects of Development Team Skill on Software Product Quality

NASA Technical Reports Server (NTRS)

Beaver, Justin M.; Schiavone, Guy A.

2006-01-01

This paper provides an analysis of the effect of the skill/experience of the software development team on the quality of the final software product. A method for the assessment of software development team skill and experience is proposed, and was derived from a workforce management tool currently in use by the National Aeronautics and Space Administration. Using data from 26 smallscale software development projects, the team skill measures are correlated to 5 software product quality metrics from the ISO/IEC 9126 Software Engineering Product Quality standard. in the analysis of the results, development team skill is found to be a significant factor in the adequacy of the design and implementation. In addition, the results imply that inexperienced software developers are tasked with responsibilities ill-suited to their skill level, and thus have a significant adverse effect on the quality of the software product. Keywords: software quality, development skill, software metrics

Quality Assurance in Software Development: An Exploratory Investigation in Software Project Failures and Business Performance

ERIC Educational Resources Information Center

Ichu, Emmanuel A.

2010-01-01

Software quality is perhaps one of the most sought-after attributes in product development, however; this goal is unattained. Problem factors in software development and how these have affected the maintainability of the delivered software systems requires a thorough investigation. It was, therefore, very important to understand software…

Software Development Management: Empirical and Analytical Perspectives

ERIC Educational Resources Information Center

Kang, Keumseok

2011-01-01

Managing software development is a very complex activity because it must deal with people, organizations, technologies, and business processes. My dissertation consists of three studies that examine software development management from various perspectives. The first study empirically investigates the impacts of prior experience with similar…

SDN-Enabled Dynamic Feedback Control and Sensing in Agile Optical Networks

NASA Astrophysics Data System (ADS)

Lin, Likun

Fiber optic networks are no longer just pipelines for transporting data in the long haul backbone. Exponential growth in traffic in metro-regional areas has pushed higher capacity fiber toward the edge of the network, and highly dynamic patterns of heterogeneous traffic have emerged that are often bursty, severely stressing the historical "fat and dumb pipe" static optical network, which would need to be massively over-provisioned to deal with these loads. What is required is a more intelligent network with a span of control over the optical as well as electrical transport mechanisms which enables handling of service requests in a fast and efficient way that guarantees quality of service (QoS) while optimizing capacity efficiency. An "agile" optical network is a reconfigurable optical network comprised of high speed intelligent control system fed by real-time in situ network sensing. It provides fast response in the control and switching of optical signals in response to changing traffic demands and network conditions. This agile control of optical signals is enabled by pushing switching decisions downward in the network stack to the physical layer. Implementing such agility is challenging due to the response dynamics and interactions of signals in the physical layer. Control schemes must deal with issues such as dynamic power equalization, EDFA transients and cascaded noise effects, impairments due to self-phase modulation and dispersion, and channel-to-channel cross talk. If these issues are not properly predicted and mitigated, attempts at dynamic control can drive the optical network into an unstable state. In order to enable high speed actuation of signal modulators and switches, the network controller must be able to make decisions based on predictive models. In this thesis, we consider how to take advantage of Software Defined Networking (SDN) capabilities for network reconfiguration, combined with embedded models that access updates from deployed network

The Relevance of Software Development Education for Students

ERIC Educational Resources Information Center

Liebenberg, Janet; Huisman, Magda; Mentz, Elsa

2015-01-01

Despite a widely-acknowledged shortage of software developers, and reports of a gap between industry needs and software education, the possible gap between students' needs and software development education has not been explored in detail. In their university education, students want to take courses and carry out projects that clearly relate to…

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.

APPLICATION OF SOFTWARE QUALITY ASSURANCE CONCEPTS AND PROCEDURES TO ENVIORNMENTAL RESEARCH INVOLVING SOFTWARE DEVELOPMENT

EPA Science Inventory

As EPA’s environmental research expands into new areas that involve the development of software, quality assurance concepts and procedures that were originally developed for environmental data collection may not be appropriate. Fortunately, software quality assurance is a ...

Automation of Flight Software Regression Testing

NASA Technical Reports Server (NTRS)

Tashakkor, Scott B.

2016-01-01

NASA is developing the Space Launch System (SLS) to be a heavy lift launch vehicle supporting human and scientific exploration beyond earth orbit. SLS will have a common core stage, an upper stage, and different permutations of boosters and fairings to perform various crewed or cargo missions. Marshall Space Flight Center (MSFC) is writing the Flight Software (FSW) that will operate the SLS launch vehicle. The FSW is developed in an incremental manner based on "Agile" software techniques. As the FSW is incrementally developed, testing the functionality of the code needs to be performed continually to ensure that the integrity of the software is maintained. Manually testing the functionality on an ever-growing set of requirements and features is not an efficient solution and therefore needs to be done automatically to ensure testing is comprehensive. To support test automation, a framework for a regression test harness has been developed and used on SLS FSW. The test harness provides a modular design approach that can compile or read in the required information specified by the developer of the test. The modularity provides independence between groups of tests and the ability to add and remove tests without disturbing others. This provides the SLS FSW team a time saving feature that is essential to meeting SLS Program technical and programmatic requirements. During development of SLS FSW, this technique has proved to be a useful tool to ensure all requirements have been tested, and that desired functionality is maintained, as changes occur. It also provides a mechanism for developers to check functionality of the code that they have developed. With this system, automation of regression testing is accomplished through a scheduling tool and/or commit hooks. Key advantages of this test harness capability includes execution support for multiple independent test cases, the ability for developers to specify precisely what they are testing and how, the ability to add

Ethics in computer software design and development

Treesearch

Alan J. Thomson; Daniel L. Schmoldt

2001-01-01

Over the past 20 years, computer software has become integral and commonplace for operational and management tasks throughout agricultural and natural resource disciplines. During this software infusion, however, little thought has been afforded human impacts, both good and bad. This paper examines current ethical issues of software system design and development in...

An assessment of space shuttle flight software development processes

NASA Technical Reports Server (NTRS)

1993-01-01

In early 1991, the National Aeronautics and Space Administration's (NASA's) Office of Space Flight commissioned the Aeronautics and Space Engineering Board (ASEB) of the National Research Council (NRC) to investigate the adequacy of the current process by which NASA develops and verifies changes and updates to the Space Shuttle flight software. The Committee for Review of Oversight Mechanisms for Space Shuttle Flight Software Processes was convened in Jan. 1992 to accomplish the following tasks: (1) review the entire flight software development process from the initial requirements definition phase to final implementation, including object code build and final machine loading; (2) review and critique NASA's independent verification and validation process and mechanisms, including NASA's established software development and testing standards; (3) determine the acceptability and adequacy of the complete flight software development process, including the embedded validation and verification processes through comparison with (1) generally accepted industry practices, and (2) generally accepted Department of Defense and/or other government practices (comparing NASA's program with organizations and projects having similar volumes of software development, software maturity, complexity, criticality, lines of code, and national standards); (4) consider whether independent verification and validation should continue. An overview of the study, independent verification and validation of critical software, and the Space Shuttle flight software development process are addressed. Findings and recommendations are presented.

77 FR 50724 - Developing Software Life Cycle Processes for Digital Computer Software Used in Safety Systems of...

Federal Register 2010, 2011, 2012, 2013, 2014

2012-08-22

... NUCLEAR REGULATORY COMMISSION [NRC-2012-0195] Developing Software Life Cycle Processes for Digital... Software Life Cycle Processes for Digital Computer Software used in Safety Systems of Nuclear Power Plants... clarifications, the enhanced consensus practices for developing software life-cycle processes for digital...

5th Annual AGILE Science Workshop

NASA Technical Reports Server (NTRS)

Hunter, Stanley

2008-01-01

The EGRET model of the galactic diffuse gamma-ray emission (GALDIF) has been extended to provide full-sky coverage and improved to address the discrepancies with the EGRET data. This improved model is compared with the AGILE results from the Galactic center. The comparison is discussed.

Development of a New VLBI Data Analysis Software

NASA Technical Reports Server (NTRS)

Bolotin, Sergei; Gipson, John M.; MacMillan, Daniel S.

2010-01-01

We present an overview of a new VLBI analysis software under development at NASA GSFC. The new software will replace CALC/SOLVE and many related utility programs. It will have the capabilities of the current system as well as incorporate new models and data analysis techniques. In this paper we give a conceptual overview of the new software. We formulate the main goals of the software. The software should be flexible and modular to implement models and estimation techniques that currently exist or will appear in future. On the other hand it should be reliable and possess production quality for processing standard VLBI sessions. Also, it needs to be capable of processing observations from a fully deployed network of VLBI2010 stations in a reasonable time. We describe the software development process and outline the software architecture.

Towards a New Paradigm of Software Development: an Ambassador Driven Process in Distributed Software Companies

NASA Astrophysics Data System (ADS)

Kumlander, Deniss

The globalization of companies operations and competitor between software vendors demand improving quality of delivered software and decreasing the overall cost. The same in fact introduce a lot of problem into software development process as produce distributed organization breaking the co-location rule of modern software development methodologies. Here we propose a reformulation of the ambassador position increasing its productivity in order to bridge communication and workflow gap by managing the entire communication process rather than concentrating purely on the communication result.

The ALMA Common Software as a Basis for a Distributed Software Development

NASA Astrophysics Data System (ADS)

Raffi, Gianni; Chiozzi, Gianluca; Glendenning, Brian

The Atacama Large Millimeter Array (ALMA) is a joint project involving astronomical organizations in Europe, North America and Japan. ALMA will consist of 64 12-m antennas operating in the millimetre and sub-millimetre wavelength range, with baselines of more than 10 km. It will be located at an altitude above 5000 m in the Chilean Atacama desert. The ALMA Computing group is a joint group with staff scattered on 3 continents and is responsible for all the control and data flow software related to ALMA, including tools ranging from support of proposal preparation to archive access of automatically created images. Early in the project it was decided that an ALMA Common Software (ACS) would be developed as a way to provide to all partners involved in the development a common software platform. The original assumption was that some key middleware like communication via CORBA and the use of XML and Java would be part of the project. It was intended from the beginning to develop this software in an incremental way based on releases, so that it would then evolve into an essential embedded part of all ALMA software applications. In this way we would build a basic unity and coherence into a system that will have been developed in a distributed fashion. This paper evaluates our progress after 1.5 year of work, following a few tests and preliminary releases. It analyzes the advantages and difficulties of such an ambitious approach, which creates an interface across all the various control and data flow applications.

Software project management tools in global software development: a systematic mapping study.

PubMed

Chadli, Saad Yasser; Idri, Ali; Ros, Joaquín Nicolás; Fernández-Alemán, José Luis; de Gea, Juan M Carrillo; Toval, Ambrosio

2016-01-01

Global software development (GSD) which is a growing trend in the software industry is characterized by a highly distributed environment. Performing software project management (SPM) in such conditions implies the need to overcome new limitations resulting from cultural, temporal and geographic separation. The aim of this research is to discover and classify the various tools mentioned in literature that provide GSD project managers with support and to identify in what way they support group interaction. A systematic mapping study has been performed by means of automatic searches in five sources. We have then synthesized the data extracted and presented the results of this study. A total of 102 tools were identified as being used in SPM activities in GSD. We have classified these tools, according to the software life cycle process on which they focus and how they support the 3C collaboration model (communication, coordination and cooperation). The majority of the tools found are standalone tools (77%). A small number of platforms (8%) also offer a set of interacting tools that cover the software development lifecycle. Results also indicate that SPM areas in GSD are not adequately supported by corresponding tools and deserve more attention from tool builders.

Candidate control design metrics for an agile fighter

NASA Technical Reports Server (NTRS)

Murphy, Patrick C.; Bailey, Melvin L.; Ostroff, Aaron J.

1991-01-01

Success in the fighter combat environment of the future will certainly demand increasing capability from aircraft technology. These advanced capabilities in the form of superagility and supermaneuverability will require special design techniques which translate advanced air combat maneuvering requirements into design criteria. Control design metrics can provide some of these techniques for the control designer. Thus study presents an overview of control design metrics and investigates metrics for advanced fighter agility. The objectives of various metric users, such as airframe designers and pilots, are differentiated from the objectives of the control designer. Using an advanced fighter model, metric values are documented over a portion of the flight envelope through piloted simulation. These metric values provide a baseline against which future control system improvements can be compared and against which a control design methodology can be developed. Agility is measured for axial, pitch, and roll axes. Axial metrics highlight acceleration and deceleration capabilities under different flight loads and include specific excess power measurements to characterize energy meneuverability. Pitch metrics cover both body-axis and wind-axis pitch rates and accelerations. Included in pitch metrics are nose pointing metrics which highlight displacement capability between the nose and the velocity vector. Roll metrics (or torsion metrics) focus on rotational capability about the wind axis.

Optical flows method for lightweight agile remote sensor design and instrumentation

NASA Astrophysics Data System (ADS)

Wang, Chong; Xing, Fei; Wang, Hongjian; You, Zheng

2013-08-01

Lightweight agile remote sensors have become one type of the most important payloads and were widely utilized in space reconnaissance and resource survey. These imaging sensors are designed to obtain the high spatial, temporary and spectral resolution imageries. Key techniques in instrumentation include flexible maneuvering, advanced imaging control algorithms and integrative measuring techniques, which are closely correlative or even acting as the bottle-necks for each other. Therefore, mutual restrictive problems must be solved and optimized. Optical flow is the critical model which to be fully represented in the information transferring as well as radiation energy flowing in dynamic imaging. For agile sensors, especially with wide-field-of view, imaging optical flows may distort and deviate seriously when they perform large angle attitude maneuvering imaging. The phenomena are mainly attributed to the geometrical characteristics of the three-dimensional earth surface as well as the coupled effects due to the complicated relative motion between the sensor and scene. Under this circumstance, velocity fields distribute nonlinearly, the imageries may badly be smeared or probably the geometrical structures are changed since the image velocity matching errors are not having been eliminated perfectly. In this paper, precise imaging optical flow model is established for agile remote sensors, for which optical flows evolving is factorized by two forms, which respectively due to translational movement and image shape changing. Moreover, base on that, agile remote sensors instrumentation was investigated. The main techniques which concern optical flow modeling include integrative design with lightweight star sensors along with micro inertial measurement units and corresponding data fusion, the assemblies of focal plane layout and control, imageries post processing for agile remote sensors etc. Some experiments show that the optical analyzing method is effective to

Development of a fast, lean and agile direct pelletization process using experimental design techniques.

PubMed

Politis, Stavros N; Rekkas, Dimitrios M

2017-04-01

A novel hot melt direct pelletization method was developed, characterized and optimized, using statistical thinking and experimental design tools. Mixtures of carnauba wax (CW) and HPMC K100M were spheronized using melted gelucire 50-13 as a binding material (BM). Experimentation was performed sequentially; a fractional factorial design was set up initially to screen the factors affecting the process, namely spray rate, quantity of BM, rotor speed, type of rotor disk, lubricant-glidant presence, additional spheronization time, powder feeding rate and quantity. From the eight factors assessed, three were further studied during process optimization (spray rate, quantity of BM and powder feeding rate), at different ratios of the solid mixture of CW and HPMC K100M. The study demonstrated that the novel hot melt process is fast, efficient, reproducible and predictable. Therefore, it can be adopted in a lean and agile manufacturing setting for the production of flexible pellet dosage forms with various release rates easily customized between immediate and modified delivery.

Advanced software development workstation project: Engineering scripting language. Graphical editor

NASA Technical Reports Server (NTRS)

1992-01-01

Software development is widely considered to be a bottleneck in the development of complex systems, both in terms of development and in terms of maintenance of deployed systems. Cost of software development and maintenance can also be very high. One approach to reducing costs and relieving this bottleneck is increasing the reuse of software designs and software components. A method for achieving such reuse is a software parts composition system. Such a system consists of a language for modeling software parts and their interfaces, a catalog of existing parts, an editor for combining parts, and a code generator that takes a specification and generates code for that application in the target language. The Advanced Software Development Workstation is intended to be an expert system shell designed to provide the capabilities of a software part composition system.

Pragmatic quality metrics for evolutionary software development models

NASA Technical Reports Server (NTRS)

Royce, Walker

1990-01-01

Due to the large number of product, project, and people parameters which impact large custom software development efforts, measurement of software product quality is a complex undertaking. Furthermore, the absolute perspective from which quality is measured (customer satisfaction) is intangible. While we probably can't say what the absolute quality of a software product is, we can determine the relative quality, the adequacy of this quality with respect to pragmatic considerations, and identify good and bad trends during development. While no two software engineers will ever agree on an optimum definition of software quality, they will agree that the most important perspective of software quality is its ease of change. We can call this flexibility, adaptability, or some other vague term, but the critical characteristic of software is that it is soft. The easier the product is to modify, the easier it is to achieve any other software quality perspective. This paper presents objective quality metrics derived from consistent lifecycle perspectives of rework which, when used in concert with an evolutionary development approach, can provide useful insight to produce better quality per unit cost/schedule or to achieve adequate quality more efficiently. The usefulness of these metrics is evaluated by applying them to a large, real world, Ada project.

Measures and metrics for software development

NASA Technical Reports Server (NTRS)

1984-01-01

The evaluations of and recommendations for the use of software development measures based on the practical and analytical experience of the Software Engineering Laboratory are discussed. The basic concepts of measurement and system of classification for measures are described. The principal classes of measures defined are explicit, analytic, and subjective. Some of the major software measurement schemes appearing in the literature are derived. The applications of specific measures in a production environment are explained. These applications include prediction and planning, review and assessment, and evaluation and selection.

Software Development Standard for Mission Critical Systems

DTIC Science & Technology

2014-03-17

new development, modification, reuse, reengineering, maintenance , or any other activity or combination of activities resulting in products . Within...develops” includes new development, modification, integration, reuse, reengineering, maintenance , or any other activity that results in products ... Maintenance organization. The organization that is responsible for modifying and otherwise sustaining the software and other software products and

Frequency Agile Microwave Photonic Notch Filter in a Photonic Chip

DTIC Science & Technology

2016-10-21

AFRL-AFOSR-JP-TR-2016-0087 Frequency Agile Microwave Photonic Notch Filter in a Photonic Chip Benjamin Eggleton UNIVERSITY OF SYDNEY Final Report 10...REPORT TYPE      Final 3.  DATES COVERED (From - To)      14 May 2014 to 13 May 2016 4.  TITLE AND SUBTITLE Frequency Agile Microwave Photonic Notch Filter ...primary objective is to explore a novel class microwave photonic (MWP) notch filter with a very narrow isolation bandwidth, an ultrahigh stopband

A Literature Review on the Progression of Agile Manufacturing Paradigm and Its Scope of Application in Pump Industry

PubMed Central

Devadasan, S. R.; Sivaram, N. M.

2015-01-01

During the recent years, the manufacturing world has been witnessing the application of agile manufacturing paradigm. The literature review reported in this paper was carried out to study this progression. This literature review was carried out in two phases. In the first phase, the literature was reviewed to trace the origin of agile manufacturing paradigm and identify its enablers. Further, during this phase, the applications of agile manufacturing reported in literature arena were reviewed. It was also discernable that certain research works have been initiated to apply agile manufacturing paradigm in pump industry. During the second phase, the researches reported on applying agile manufacturing in pump industry were reviewed. At the end of this review, it was found that so far the implementation of agile manufacturing in pump industry has been examined by the researchers by considering only certain components of pumps. In fact, the holistic implementation of agile manufacturing in the pump industry is yet to be examined by the researchers. In the context of drawing this inference, this paper has been concluded by stating that high scope exists in examining the infusing of agility characteristics in designing and manufacturing of pumps. PMID:26065016

A Literature Review on the Progression of Agile Manufacturing Paradigm and Its Scope of Application in Pump Industry.

PubMed

Thilak, V M M; Devadasan, S R; Sivaram, N M

2015-01-01

During the recent years, the manufacturing world has been witnessing the application of agile manufacturing paradigm. The literature review reported in this paper was carried out to study this progression. This literature review was carried out in two phases. In the first phase, the literature was reviewed to trace the origin of agile manufacturing paradigm and identify its enablers. Further, during this phase, the applications of agile manufacturing reported in literature arena were reviewed. It was also discernable that certain research works have been initiated to apply agile manufacturing paradigm in pump industry. During the second phase, the researches reported on applying agile manufacturing in pump industry were reviewed. At the end of this review, it was found that so far the implementation of agile manufacturing in pump industry has been examined by the researchers by considering only certain components of pumps. In fact, the holistic implementation of agile manufacturing in the pump industry is yet to be examined by the researchers. In the context of drawing this inference, this paper has been concluded by stating that high scope exists in examining the infusing of agility characteristics in designing and manufacturing of pumps.

Scheduling algorithms for rapid imaging using agile Cubesat constellations

NASA Astrophysics Data System (ADS)

Nag, Sreeja; Li, Alan S.; Merrick, James H.

2018-02-01

Distributed Space Missions such as formation flight and constellations, are being recognized as important Earth Observation solutions to increase measurement samples over space and time. Cubesats are increasing in size (27U, ∼40 kg in development) with increasing capabilities to host imager payloads. Given the precise attitude control systems emerging in the commercial market, Cubesats now have the ability to slew and capture images within short notice. We propose a modular framework that combines orbital mechanics, attitude control and scheduling optimization to plan the time-varying, full-body orientation of agile Cubesats in a constellation such that they maximize the number of observed images and observation time, within the constraints of Cubesat hardware specifications. The attitude control strategy combines bang-bang and PD control, with constraints such as power consumption, response time, and stability factored into the optimality computations and a possible extension to PID control to account for disturbances. Schedule optimization is performed using dynamic programming with two levels of heuristics, verified and improved upon using mixed integer linear programming. The automated scheduler is expected to run on ground station resources and the resultant schedules uplinked to the satellites for execution, however it can be adapted for onboard scheduling, contingent on Cubesat hardware and software upgrades. The framework is generalizable over small steerable spacecraft, sensor specifications, imaging objectives and regions of interest, and is demonstrated using multiple 20 kg satellites in Low Earth Orbit for two case studies - rapid imaging of Landsat's land and coastal images and extended imaging of global, warm water coral reefs. The proposed algorithm captures up to 161% more Landsat images than nadir-pointing sensors with the same field of view, on a 2-satellite constellation over a 12-h simulation. Integer programming was able to verify that