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

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.

Scrum and Global Delivery: Pitfalls and Lessons Learned

NASA Astrophysics Data System (ADS)

Sadun, Cristiano

Two trends are becoming widespread in software development work—agile development processes and global delivery, both promising sizable benefits in productivity, capacity and so on. Combining the two is a highly attractive possibility, even more so in fast-paced and constrained commercial software engineering projects. However, a degree of conflict exists between the assumptions underlying the two ideas, leading to pitfalls and challenges in agile/distributed projects which are new, both with respect to traditional development and agile or distributed efforts adopted separately. Succeeding in commercial agile/distributed projects implies recognizing these new challenges, proactively planning for them, and actively put in place solutions and methods to overcome them. This chapter illustrates some of the typical challenges that were met during real-world commercial projects, and how they were solved.

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

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.

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…

A Novel Approach for Collaborative Pair Programming

ERIC Educational Resources Information Center

Goel, Sanjay; Kathuria, Vanshi

2010-01-01

The majority of an engineer's time in the software industry is spent working with other programmers. Agile methods of software development like eXtreme Programming strongly rely upon practices like daily meetings and pair programming. Hence, the need to learn the skill of working collaboratively is of primary importance for software developers.…

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-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

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.

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,…

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:

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

Agile Software Development

ERIC Educational Resources Information Center

Biju, Soly Mathew

2008-01-01

Many software development firms are now adopting the agile software development method. This method involves the customer at every level of software development, thus reducing the impact of change in the requirement at a later stage. In this article, the principles of the agile method for software development are explored and there is a focus on…

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…

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.

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.

CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 4

DTIC Science & Technology

2007-04-01

and test markets . The decision fails the review, gets marked for adjustment, or passes. • The decision gets pushed out into the world. At this point...STD- 1521, Institute for Electrical and Electronics Engineers [IEEE]-15288). Myopically focused on early correctness, systems engineering can seem to...based on Mishkin Berteig’s experiences as an agile coach, consultant or trainer to teams and management in organizations across North America. From

Research and realization of signal simulation on virtual instrument

NASA Astrophysics Data System (ADS)

Zhao, Qi; He, Wenting; Guan, Xiumei

2010-02-01

In the engineering project, arbitrary waveform generator controlled by software interface is needed by simulation and test. This article discussed the program using the SCPI (Standard Commands For Programmable Instruments) protocol and the VISA (Virtual Instrument System Architecture) library to control the Agilent signal generator (Agilent N5182A) by instrument communication over the LAN interface. The program can conduct several signal generations such as CW (continuous wave), AM (amplitude modulation), FM (frequency modulation), ΦM (phase modulation), Sweep. As the result, the program system has good operability and portability.

Information System Engineering Supporting Observation, Orientation, Decision, and Compliant Action

NASA Astrophysics Data System (ADS)

Georgakopoulos, Dimitrios

The majority of today's software systems and organizational/business structures have been built on the foundation of solving problems via long-term data collection, analysis, and solution design. This traditional approach of solving problems and building corresponding software systems and business processes, falls short in providing the necessary solutions needed to deal with many problems that require agility as the main ingredient of their solution. For example, such agility is needed in responding to an emergency, in military command control, physical security, price-based competition in business, investing in the stock market, video gaming, network monitoring and self-healing, diagnosis in emergency health care, and many other areas that are too numerous to list here. The concept of Observe, Orient, Decide, and Act (OODA) loops is a guiding principal that captures the fundamental issues and approach for engineering information systems that deal with many of these problem areas. However, there are currently few software systems that are capable of supporting OODA. In this talk, we provide a tour of the research issues and state of the art solutions for supporting OODA. In addition, we provide specific examples of OODA solutions we have developed for the video surveillance and emergency response domains.

A New Overview of The Trilinos Project

DOE PAGES

Heroux, Michael A.; Willenbring, James M.

2012-01-01

Since An Overview of the Trilinos Project [ACM Trans. Math. Softw. 31(3) (2005), 397–423] was published in 2005, Trilinos has grown significantly. It now supports the development of a broad collection of libraries for scalable computational science and engineering applications, and a full-featured software infrastructure for rigorous lean/agile software engineering. This growth has created significant opportunities and challenges. This paper focuses on some of the most notable changes to the Trilinos project in the last few years. At the time of the writing of this article, the current release version of Trilinos was 10.12.2.

Agile and Lean Systems Engineering: Kanban in Systems Engineering

DTIC Science & Technology

2011-12-31

Rico (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...Commitment Model to Brownfield Systems Development, Proceedings, CSER 2009, April 2009. 14. Heath , B. et al. (2009). A survey of agent-based modeling

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.

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

Impact of Agile Software Development Model on Software Maintainability

ERIC Educational Resources Information Center

Gawali, Ajay R.

2012-01-01

Software maintenance and support costs account for up to 60% of the overall software life cycle cost and often burdens tightly budgeted information technology (IT) organizations. Agile software development approach delivers business value early, but implications on software maintainability are still unknown. The purpose of this quantitative study…

The method to divide a sentence of requirement into individual requirements and the development of requirement specification editor which can describe individual requirements.

PubMed

Sato, Kuniya; Ooba, Masahiro; Takagi, Tomohiko; Furukawa, Zengo; Komiya, Seiichi; Yaegashi, Rihito

2013-12-01

Agile software development gains requirements from the direct discussion with customers and the development staff each time, and the customers evaluate the appropriateness of the requirement. If the customers divide the complicated requirement into individual requirements, the engineer who is in charge of software development can understand it easily. This is called division of requirement. However, the customers do not understand how much and how to divide the requirements. This paper proposes the method to divide a complicated requirement into individual requirements. Also, it shows the development of requirement specification editor which can describe individual requirements. The engineer who is in charge of software development can understand requirements easily.

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.

Time-Reversal Based Range Extension Technique for Ultra-wideband (UWB) Sensors and Applications in Tactical Communications and Networking

DTIC Science & Technology

2008-04-16

Zhen (Edward) Hu Peng (Peter) Zhang Yu Song Amanpreet Singh Saini Corey Cooke April 16, 2006 Department of Electrical and Computer Engineering Center...and RF frequency agility is the most challenging issue for spectrum sensing. The radio under development is an ultra-wideband software -defined radio...PC USB programming cable and accom- panying PC software as well as download test vectors to the waveform memory module, as shown in Figure 3.25,3I

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

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.

A Virtual World Workshop Environment for Learning Agile Software Development Techniques

ERIC Educational Resources Information Center

Parsons, David; Stockdale, Rosemary

2012-01-01

Multi-User Virtual Environments (MUVEs) are the subject of increasing interest for educators and trainers. This article reports on a longitudinal project that seeks to establish a virtual agile software development workshop hosted in the Open Wonderland MUVE, designed to help learners to understand the basic principles of some core agile software…

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…

Architected Agile Solutions for Software-Reliant Systems

NASA Astrophysics Data System (ADS)

Boehm, Barry; Lane, Jo Ann; Koolmanojwong, Supannika; Turner, Richard

Systems are becoming increasingly reliant on software due to needs for rapid fielding of “70% capabilities,” interoperability, net-centricity, and rapid adaptation to change. The latter need has led to increased interest in agile methods of software development, in which teams rely on shared tacit interpersonal knowledge rather than explicit documented knowledge. However, such systems often need to be scaled up to higher level of performance and assurance, requiring stronger architectural support. Several organizations have recently transformed themselves by developing successful combinations of agility and architecture that can scale to projects of up to 100 personnel. This chapter identifies a set of key principles for such architected agile solutions for software-reliant systems, provides guidance for how much architecting is enough, and illustrates the key principles with several case studies.

A Case Study of Coordination in Distributed Agile Software Development

NASA Astrophysics Data System (ADS)

Hole, Steinar; Moe, Nils Brede

Global Software Development (GSD) has gained significant popularity as an emerging paradigm. Companies also show interest in applying agile approaches in distributed development to combine the advantages of both approaches. However, in their most radical forms, agile and GSD can be placed in each end of a plan-based/agile spectrum because of how work is coordinated. We describe how three GSD projects applying agile methods coordinate their work. We found that trust is needed to reduce the need of standardization and direct supervision when coordinating work in a GSD project, and that electronic chatting supports mutual adjustment. Further, co-location and modularization mitigates communication problems, enables agility in at least part of a GSD project, and renders the implementation of Scrum of Scrums possible.

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…

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?

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.

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

RFP Patterns and Techniques for Successful Agile Contracting

DTIC Science & Technology

2016-11-01

2016-SR-025 SOFTWARE ENGINEERING INSTITUTE | CARNEGIE MELLON UNIVERSITY [Distribution Statement A] This material has been approved for public...release and unlimited distribution. Please see Copyright notice for non-U.S. Government use and distribution. Copyright 2016 Carnegie Mellon University...This material is based upon work funded and supported by the Department of Defense under Contract No. FA8721-05-C-0003 with Carnegie Mellon

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…

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…

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 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…

A Quantitative Inquiry into Software Developers' Intentions to Use Agile Scrum Method

ERIC Educational Resources Information Center

Huq, M. Shamsul

2017-01-01

In recent years, organizations have shown increasing willingness to adopt agile scrum method (ASM) to meet the demand of modern-day software development; that is to deliver faster and better software, with a built-in flexibility to absorb last minute changes in requirements. This research study was undertaken to uncover the underlying factors that…

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

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.

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.

Adopting best practices: "Agility" moves from software development to healthcare project management.

PubMed

Kitzmiller, Rebecca; Hunt, Eleanor; Sproat, Sara Breckenridge

2006-01-01

It is time for a change in mindset in how nurses operationalize system implementations and manage projects. Computers and systems have evolved over time from unwieldy mysterious machines of the past to ubiquitous computer use in every aspect of daily lives and work sites. Yet, disconcertingly, the process used to implement these systems has not evolved. Technology implementation does not need to be a struggle. It is time to adapt traditional plan-driven implementation methods to incorporate agile techniques. Agility is a concept borrowed from software development and is presented here because it encourages flexibility, adaptation, and continuous learning as part of the implementation process. Agility values communication and harnesses change to an advantage, which facilitates the natural evolution of an adaptable implementation process. Specific examples of agility in an implementation are described, and plan-driven implementation stages are adapted to incorporate relevant agile techniques. This comparison demonstrates how an agile approach enhances traditional implementation techniques to meet the demands of today's complex healthcare environments.

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

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…

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 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…

Computational Fluid Dynamics Technology for Hypersonic Applications

NASA Technical Reports Server (NTRS)

Gnoffo, Peter A.

2003-01-01

Several current challenges in computational fluid dynamics and aerothermodynamics for hypersonic vehicle applications are discussed. Example simulations are presented from code validation and code benchmarking efforts to illustrate capabilities and limitations. Opportunities to advance the state-of-art in algorithms, grid generation and adaptation, and code validation are identified. Highlights of diverse efforts to address these challenges are then discussed. One such effort to re-engineer and synthesize the existing analysis capability in LAURA, VULCAN, and FUN3D will provide context for these discussions. The critical (and evolving) role of agile software engineering practice in the capability enhancement process is also noted.

Cross Sectional Study of Agile Software Development Methods and Project Performance

ERIC Educational Resources Information Center

Lambert, Tracy

2011-01-01

Agile software development methods, characterized by delivering customer value via incremental and iterative time-boxed development processes, have moved into the mainstream of the Information Technology (IT) industry. However, despite a growing body of research which suggests that a predictive manufacturing approach, with big up-front…

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.

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).

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

NASA Astrophysics Data System (ADS)

Robinson, Hugh; Sharp, Helen

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

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

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…

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.

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

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

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.

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.

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

Software ``Best'' Practices: Agile Deconstructed

NASA Astrophysics Data System (ADS)

Fraser, Steven

This workshop will explore the intersection of agility and software development in a world of legacy code-bases and large teams. Organizations with hundreds of developers and code-bases exceeding a million or tens of millions of lines of code are seeking new ways to expedite development while retaining and attracting staff who desire to apply “agile” methods. This is a situation where specific agile practices may be embraced outside of their usual zone of applicability. Here is where practitioners must understand both what “best practices” already exist in the organization - and how they might be improved or modified by applying “agile” approaches.

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…

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 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.

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…

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.

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

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.

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.

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

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

Insights into Global Health Practice from the Agile Software Development Movement.

PubMed

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.

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

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

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.

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

Experiences with Extreme Programming

ERIC Educational Resources Information Center

Sherrell, Linda; Krishna, Bhagavathy; Velaga, Natasha; Vejandla, Pavan; Satharla, Mahesh

2010-01-01

Agile methodologies have become increasingly popular among software developers as evidenced by industrial participation at related conferences. The popularity of agile practices over traditional techniques partly stems from the fact that these practices provide for more customer involvement and better accommodate rapidly changing requirements,…

Identification, Characterization, and Evaluation Criteria for Systems Engineering Agile Enablers

DTIC Science & Technology

2015-01-16

Identification, Characterization, and Evaluation Criteria for Systems Engineering Agile Enablers Technical Report SERC -2015-TR-049-1...Task Order 024, RT 124 Report No. SERC -2015-TR-049-1 Report Documentation Page Form ApprovedOMB No. 0704-0188 Public reporting burden for the...Technology The Systems Engineering Research Center ( SERC ) is a federally funded University Affiliated Research Center managed by Stevens Institute of

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.

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…

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.

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...

Mapping CMMI Level 2 to Scrum Practices: An Experience Report

NASA Astrophysics Data System (ADS)

Diaz, Jessica; Garbajosa, Juan; Calvo-Manzano, Jose A.

CMMI has been adopted advantageously in large companies for improvements in software quality, budget fulfilling, and customer satisfaction. However SPI strategies based on CMMI-DEV require heavy software development processes and large investments in terms of cost and time that medium/small companies do not deal with. The so-called light software development processes, such as Agile Software Development (ASD), deal with these challenges. ASD welcomes changing requirements and stresses the importance of adaptive planning, simplicity and continuous delivery of valuable software by short time-framed iterations. ASD is becoming convenient in a more and more global, and changing software market. It would be greatly useful to be able to introduce agile methods such as Scrum in compliance with CMMI process model. This paper intends to increase the understanding of the relationship between ASD and CMMI-DEV reporting empirical results that confirm theoretical comparisons between ASD practices and CMMI level2.

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

Systems 2020: Strategic Initiative

DTIC Science & Technology

2010-08-29

research areas that enable agile, assured, efficient, and scalable systems engineering approaches to support the development of these systems. This...To increase development efficiency and ensure flexible solutions in the field, systems engineers need powerful, agile, interoperable, and scalable...design and development will be transformed as a result of Systems 2020, along with complementary enabling acquisition practice improvements initiated in

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.

Origami: An Active Learning Exercise for Scrum Project Management

ERIC Educational Resources Information Center

Sibona, Christopher; Pourreza, Saba; Hill, Stephen

2018-01-01

Scrum is a popular project management model for iterative delivery of software that subscribes to Agile principles. This paper describes an origami active learning exercise to teach the principles of Scrum in management information systems courses. The exercise shows students how Agile methods respond to changes in requirements during project…

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 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.

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.

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.

Design and Development of Wireless Power Transmission for Unmanned Air Vehicles

DTIC Science & Technology

2012-09-01

ELECTRONIC WARFARE SYSTEMS ENGINEERING and MASTER OF SCIENCE IN ELECTRICAL ENGINEERING from the NAVAL POSTGRADUATE SCHOOL September 2012...Agilent Advanced Design System (ADS). Tuning elements were added and adjusted in order to optimize the efficiency. A maximum efficiency of 57% was...investigated by a series of simulations using Agilent Advanced Design System (ADS). Tuning elements were added and adjusted

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.

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.

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.

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.

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.

Agile SE Enablers and Quantification Project: Identification, Characterization, and Evaluation Criteria for Systems Engineering Agile Enablers

DTIC Science & Technology

2015-01-16

Enablers Draft Technical Report SERC -2015-049-1 January 16, 2015 Principal Investigator: Dr. Richard Turner, Stevens Institute of...Hudson, Hoboken, NJ 07030 1 Copyright © 2015 Stevens Institute of Technology The Systems Engineering Research Center ( SERC ) is a federally...inappropriate enablers are not pursued. The identification criteria developed for RT-124 are based on earlier SERC work. [4, 5, 6]: 1 Operated by DAU

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.

An intelligent CNC machine control system architecture

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

Miller, D.J.; Loucks, C.S.

1996-10-01

Intelligent, agile manufacturing relies on automated programming of digitally controlled processes. Currently, processes such as Computer Numerically Controlled (CNC) machining are difficult to automate because of highly restrictive controllers and poor software environments. It is also difficult to utilize sensors and process models for adaptive control, or to integrate machining processes with other tasks within a factory floor setting. As part of a Laboratory Directed Research and Development (LDRD) program, a CNC machine control system architecture based on object-oriented design and graphical programming has been developed to address some of these problems and to demonstrate automated agile machining applications usingmore » platform-independent software.« less

Leadership Behaviors of Management for Complex Adaptive Systems

DTIC Science & Technology

2010-04-01

arson • The Five Dysfunctions of a Team - Patrick M. Lencioni Agile Development Practices • Agile Project Management with Scrum – Ken Schwaber...and down to the individual and team level – Relationships are not defined hierarchically, but rather through interactions across References: Mike...n – Consisting of parts intricately combined © Copyright 2009 Northrop GrummanCopyright 2010 Northrop Grumman 5 Predictable or Adaptive Software/IT

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.

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

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.

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.

The Software Element of the NASA Portable Electronic Device Radiated Emissions Investigation

NASA Technical Reports Server (NTRS)

Koppen, Sandra V.; Williams, Reuben A. (Technical Monitor)

2002-01-01

NASA Langley Research Center's (LaRC) High Intensity Radiated Fields Laboratory (HIRF Lab) recently conducted a series of electromagnetic radiated emissions tests under a cooperative agreement with Delta Airlines and an interagency agreement with the FAA. The frequency spectrum environment at a commercial airport was measured on location. The environment survey provides a comprehensive picture of the complex nature of the electromagnetic environment present in those areas outside the aircraft. In addition, radiated emissions tests were conducted on portable electronic devices (PEDs) that may be brought onboard aircraft. These tests were performed in both semi-anechoic and reverberation chambers located in the HIRF Lab. The PEDs included cell phones, laptop computers, electronic toys, and family radio systems. The data generated during the tests are intended to support the research on the effect of radiated emissions from wireless devices on aircraft systems. Both tests systems relied on customized control and data reduction software to provide test and instrument control, data acquisition, a user interface, real time data reduction, and data analysis. The software executed on PC's running MS Windows 98 and 2000, and used Agilent Pro Visual Engineering Environment (VEE) development software, Common Object Model (COM) technology, and MS Excel.

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.

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.

Extreme Programming: A Kuhnian Revolution?

NASA Astrophysics Data System (ADS)

Northover, Mandy; Northover, Alan; Gruner, Stefan; Kourie, Gerrick G.; Boake, Andrew

This paper critically assesses the extent to which the Agile Software community's use of Thomas Kuhn's theory of revolutionary scientific change is justified. It will be argued that Kuhn's concepts of "scientific revolution" and "paradigm shift" cannot adequately explain the change from one type of software methodology to another.

DoD Information Assurance and Agile: Challenges and Recommendations Gathered Through Interviews with Agile Program Managers and DoD Accreditation Reviewers

DTIC Science & Technology

2012-11-01

Tradeoff Analysis Method; ATAM, Capability Maturity Model , Capability Maturity Modeling , Carnegie Mellon, CERT, CERT Coordination Center, CMM, CMMI...Hermansen, Product Design, Sphere of Influence (https://www.SphereOfInfluence.com) Joel McAteer, Information Assurance Manager, Modeling ...use of them does introduce some challenges related to delivering software features rapidly and/or in- crementally . • Challenges with respect to

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.

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.

Cyber Fighter Associate

DTIC Science & Technology

2016-01-01

accomplish a patch- management mission while securing a critical path. As a first proof of concept a simulation with a network of 10 nodes and 4...software-agility walk of the “PERFORMANCE Each Threat Managed ” tree is slightly more complex than the network -agility walk. The original design of the...CyFiA was tested to accomplish a patch- management mission while securing a critical path. As a first proof of concept a simulation with a network of 10

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 GBT Dynamic Scheduling System: Development and Testing

NASA Astrophysics Data System (ADS)

McCarty, M.; Clark, M.; Marganian, P.; O'Neil, K.; Shelton, A.; Sessoms, E.

2009-09-01

During the summer trimester of 2008, all observations on the Robert C. Byrd Green Bank Telescope (GBT) were scheduled using the new Dynamic Scheduling System (DSS). Beta testing exercised the policies, algorithms, and software developed for the DSS project. Since observers are located all over the world, the DSS was implemented as a web application. Technologies such as iCalendar, Really Simple Syndication (RSS) feeds, email, and instant messaging are used to transfer as much or as little information to observers as they request. We discuss the software engineering challenges leading to our implementation such as information distribution and building rich user interfaces in the web browser. We also relate our adaptation of agile development practices to design and develop the DSS. Additionally, we describe handling differences in expected versus actual initial conditions in the pool of project proposals for the 08B trimester. We then identify lessons learned from beta testing and present statistics on how the DSS was used during the trimester.

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 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 starting point for the development of a catalog of data curation design patterns that may be reused in the design and execution of new data curation processes.

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.

Distributed agile software development for the SKA

NASA Astrophysics Data System (ADS)

Wicenec, Andreas; Parsons, Rebecca; Kitaeff, Slava; Vinsen, Kevin; Wu, Chen; Nelson, Paul; Reed, David

2012-09-01

The SKA software will most probably be developed by many groups distributed across the globe and coming from dierent backgrounds, like industries and research institutions. The SKA software subsystems will have to cover a very wide range of dierent areas, but still they have to react and work together like a single system to achieve the scientic goals and satisfy the challenging data ow requirements. Designing and developing such a system in a distributed fashion requires proper tools and the setup of an environment to allow for ecient detection and tracking of interface and integration issues in particular in a timely way. Agile development can provide much faster feedback mechanisms and also much tighter collaboration between the customer (scientist) and the developer. Continuous integration and continuous deployment on the other hand can provide much faster feedback of integration issues from the system level to the subsystem developers. This paper describes the results obtained from trialing a potential SKA development environment based on existing science software development processes like ALMA, the expected distribution of the groups potentially involved in the SKA development and experience gained in the development of large scale commercial software projects.

Implications of the Social Web Environment for User Story Education

ERIC Educational Resources Information Center

Fancott, Terrill; Kamthan, Pankaj; Shahmir, Nazlie

2012-01-01

In recent years, user stories have emerged in academia, as well as industry, as a notable approach for expressing user requirements of interactive software systems that are developed using agile methodologies. There are social aspects inherent to software development, in general, and user stories, in particular. This paper presents directions and…

Real-Time Data Display

NASA Technical Reports Server (NTRS)

Pedings, Marc

2007-01-01

RT-Display is a MATLAB-based data acquisition environment designed to use a variety of commercial off-the-shelf (COTS) hardware to digitize analog signals to a standard data format usable by other post-acquisition data analysis tools. This software presents the acquired data in real time using a variety of signal-processing algorithms. The acquired data is stored in a standard Operator Interactive Signal Processing Software (OISPS) data-formatted file. RT-Display is primarily configured to use the Agilent VXI (or equivalent) data acquisition boards used in such systems as MIDDAS (Multi-channel Integrated Dynamic Data Acquisition System). The software is generalized and deployable in almost any testing environment, without limitations or proprietary configuration for a specific test program or project. With the Agilent hardware configured and in place, users can start the program and, in one step, immediately begin digitizing multiple channels of data. Once the acquisition is completed, data is converted into a common binary format that also can be translated to specific formats used by external analysis software, such as OISPS and PC-Signal (product of AI Signal Research Inc.). RT-Display at the time of this reporting was certified on Agilent hardware capable of acquisition up to 196,608 samples per second. Data signals are presented to the user on-screen simultaneously for 16 channels. Each channel can be viewed individually, with a maximum capability of 160 signal channels (depending on hardware configuration). Current signal presentations include: time data, fast Fourier transforms (FFT), and power spectral density plots (PSD). Additional processing algorithms can be easily incorporated into this environment.

Invocation oriented architecture for agile code and agile data

NASA Astrophysics Data System (ADS)

Verma, Dinesh; Chan, Kevin; Leung, Kin; Gkelias, Athanasios

2017-05-01

In order to address the unique requirements of sensor information fusion in a tactical coalition environment, we are proposing a new architecture - one based on the concept of invocations. An invocation is a combination of a software code and a piece of data, both managed using techniques from Information Centric networking. This paper will discuss limitations of current approaches, present the architecture for an invocation oriented architecture, illustrate how it works with an example scenario, and provide reasons for its suitability in a coalition environment.

The Consumer Juggernaut: Web-Based and Mobile Applications as Innovation Pioneer

NASA Astrophysics Data System (ADS)

Messerschmitt, David G.

As happened previously in electronics, software targeted at consumers is increasingly the focus of investment and innovation. Some of the areas where it is leading is animated interfaces, treating users as a community, audio and video information, software as a service, agile software development, and the integration of business models with software design. As a risk-taking and experimental market, and as a source of ideas, consumer software can benefit other areas of applications software. The influence of consumer software can be magnified by research into the internal organizations and processes of the innovative firms at its foundation.

Using CORBA to integrate manufacturing cells to a virtual enterprise

NASA Astrophysics Data System (ADS)

Pancerella, Carmen M.; Whiteside, Robert A.

1997-01-01

It is critical in today's enterprises that manufacturing facilities are not isolated from design, planning, and other business activities and that information flows easily and bidirectionally between these activities. It is also important and cost-effective that COTS software, databases, and corporate legacy codes are well integrated in the information architecture. Further, much of the information generated during manufacturing must be dynamically accessible to engineering and business operations both in a restricted corporate intranet and on the internet. The software integration strategy in the Sandia Agile Manufacturing Testbed supports these enterprise requirements. We are developing a CORBA-based distributed object software system for manufacturing. Each physical machining device is a CORBA object and exports a common IDL interface to allow for rapid and dynamic insertion, deletion, and upgrading within the manufacturing cell. Cell management CORBA components access manufacturing devices without knowledge of any device-specific implementation. To support information flow from design to planning data is accessible to machinists on the shop floor. CORBA allows manufacturing components to be easily accessible to the enterprise. Dynamic clients can be created using web browsers and portable Java GUI's. A CORBA-OLE adapter allows integration to PC desktop applications. Other commercial software can access CORBA network objects in the information architecture through vendor API's.

Collaborative environments for capability-based planning

NASA Astrophysics Data System (ADS)

McQuay, William K.

2005-05-01

Distributed collaboration is an emerging technology for the 21st century that will significantly change how business is conducted in the defense and commercial sectors. Collaboration involves two or more geographically dispersed entities working together to create a "product" by sharing and exchanging data, information, and knowledge. A product is defined broadly to include, for example, writing a report, creating software, designing hardware, or implementing robust systems engineering and capability planning processes in an organization. Collaborative environments provide the framework and integrate models, simulations, domain specific tools, and virtual test beds to facilitate collaboration between the multiple disciplines needed in the enterprise. The Air Force Research Laboratory (AFRL) is conducting a leading edge program in developing distributed collaborative technologies targeted to the Air Force's implementation of systems engineering for a simulation-aided acquisition and capability-based planning. The research is focusing on the open systems agent-based framework, product and process modeling, structural architecture, and the integration technologies - the glue to integrate the software components. In past four years, two live assessment events have been conducted to demonstrate the technology in support of research for the Air Force Agile Acquisition initiatives. The AFRL Collaborative Environment concept will foster a major cultural change in how the acquisition, training, and operational communities conduct business.

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 storage, analysis, and controlled sharing of transcription-based microarray data generated on the Agilent DNA platform. In addition, EDGE3 provides a means for managing RNA samples and arrays during the hybridization process. EDGE3 is freely available for download at . PMID:19732451

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 controlled sharing of transcription-based microarray data generated on the Agilent DNA platform. In addition, EDGE(3) provides a means for managing RNA samples and arrays during the hybridization process. EDGE(3) is freely available for download at http://edge.oncology.wisc.edu/.

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.

High-end food, low-wage labor.

PubMed

Woolever, Laurie

2012-01-01

Some people work in restaurants as a lifestyle choice: they love the fast pace, the quick jokes, the often easy-flowing booze. At the height of a busy shift, if everything's going right, a team of skilled cooks and waiters can enter a kind of adrenaline-fueled flow state that's hypnotic and addictive. Some people choose it because they got burned out as grad students or software engineers or attorneys. Some people work in restaurants to make money until they graduate or get their big break in show business. It can be lucrative, especially for young, good-looking, and agile waiters, working for a great employer in a big city, where customers practically fight for the chance to buy expensive wines and $50 entrées and truffle supplements from the latest hotspot.

DoD Agile Adoption: Necessary Considerations, Concerns, and Changes

DTIC Science & Technology

2012-01-01

a large, highly visible display used by software development teams to track progress. The term was first coined by Alistar Cockburn. See <http://www.atlassian.com/ wallboards /information-radiators.jsp>

Free-standing leaping experiments with a power-autonomous elastic-spined quadruped

NASA Astrophysics Data System (ADS)

Pusey, Jason L.; Duperret, Jeffrey M.; Haynes, G. Clark; Knopf, Ryan; Koditschek, Daniel E.

2013-05-01

We document initial experiments with Canid, a freestanding, power-autonomous quadrupedal robot equipped with a parallel actuated elastic spine. Research into robotic bounding and galloping platforms holds scientific and engineering interest because it can both probe biological hypotheses regarding bounding and galloping mammals and also provide the engineering community with a new class of agile, efficient and rapidly-locomoting legged robots. We detail the design features of Canid that promote our goals of agile operation in a relatively cheap, conventionally prototyped, commercial off-the-shelf actuated platform. We introduce new measurement methodology aimed at capturing our robot's "body energy" during real time operation as a means of quantifying its potential for agile behavior. Finally, we present joint motor, inertial and motion capture data taken from Canid's initial leaps into highly energetic regimes exhibiting large accelerations that illustrate the use of this measure and suggest its future potential as a platform for developing efficient, stable, hence useful bounding gaits.

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

DoD Application Store: Enabling C2 Agility?

DTIC Science & Technology

2014-06-01

Framework, will include automated delivery of software patches, web applications, widgets and mobile application packages. The envisioned DoD...Marketplace within the Ozone Widget Framework, will include automated delivery of software patches, web applications, widgets and mobile application...current needs. DoD has started to make inroads within this environment with several Programs of Record (PoR) embracing widgets and other mobile

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.

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.

Scanned-wavelength diode laser sensors for harsh environments

NASA Astrophysics Data System (ADS)

Jeffries, Jay B.; Sanders, Scott T.; Zhou, Xin; Ma, Lin; Mattison, Daniel W.; Hanson, Ronald K.

2002-09-01

Diode laser absorption offers the possibility of high-speed, robust, and rugged sensors for a wide variety of practical applications. Pressure broadening complicates absorption measurements of gas temperature and species concentrations in high-pressure, high-temperature practical environments. More agile wavelength scanning can enable measurements of temperature and species concentrations in flames and engines as demonstrated by example measurements using wavelength scanning of a single DFB in laboratory flames or a vertical cavity surface emitting laser (VCSEL) in a pulse detonation engine environment. Although the blending of multiple transitions by pressure broadening complicates the atmospheric pressure spectrum of C2H4 fuel, a scanned wavelength strategy enables quantitative measurement of fuel/oxidizer stoichiometry. Wavelength-agile scanning techniques enable high-speed measurements in these harsh environments.

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.

Observing System Simulation Experiment (OSSE) for the HyspIRI Spectrometer Mission

NASA Technical Reports Server (NTRS)

Turmon, Michael J.; Block, Gary L.; Green, Robert O.; Hua, Hook; Jacob, Joseph C.; Sobel, Harold R.; Springer, Paul L.; Zhang, Qingyuan

2010-01-01

The OSSE software provides an integrated end-to-end environment to simulate an Earth observing system by iteratively running a distributed modeling workflow based on the HyspIRI Mission, including atmospheric radiative transfer, surface albedo effects, detection, and retrieval for agile exploration of the mission design space. The software enables an Observing System Simulation Experiment (OSSE) and can be used for design trade space exploration of science return for proposed instruments by modeling the whole ground truth, sensing, and retrieval chain and to assess retrieval accuracy for a particular instrument and algorithm design. The OSSE in fra struc ture is extensible to future National Research Council (NRC) Decadal Survey concept missions where integrated modeling can improve the fidelity of coupled science and engineering analyses for systematic analysis and science return studies. This software has a distributed architecture that gives it a distinct advantage over other similar efforts. The workflow modeling components are typically legacy computer programs implemented in a variety of programming languages, including MATLAB, Excel, and FORTRAN. Integration of these diverse components is difficult and time-consuming. In order to hide this complexity, each modeling component is wrapped as a Web Service, and each component is able to pass analysis parameterizations, such as reflectance or radiance spectra, on to the next component downstream in the service workflow chain. In this way, the interface to each modeling component becomes uniform and the entire end-to-end workflow can be run using any existing or custom workflow processing engine. The architecture lets users extend workflows as new modeling components become available, chain together the components using any existing or custom workflow processing engine, and distribute them across any Internet-accessible Web Service endpoints. The workflow components can be hosted on any Internet-accessible machine. This has the advantages that the computations can be distributed to make best use of the available computing resources, and each workflow component can be hosted and maintained by their respective domain experts.

The Army Digital Terrain Catalog II (ADTC)

DTIC Science & Technology

2006-06-01

Engineering (Eds.). Readings for Systems Engineering & Engineering Management. Mason, OH: Thomson Customer Publishing, 2004, p. 2. [3] E. von Hippel ...responsive, deployable, agile, versatile, lethal, survivable, and sustainable force. --Former Army Chief of Staff General Eric Shinseki and former...to advance the tenets of Army Transformation. As former Army Chief of Staff General Eric Shinseki and former Army Secretary Thomas White have stated

Anatomy of a hash-based long read sequence mapping algorithm for next generation DNA sequencing.

PubMed

Misra, Sanchit; Agrawal, Ankit; Liao, Wei-keng; Choudhary, Alok

2011-01-15

Recently, a number of programs have been proposed for mapping short reads to a reference genome. Many of them are heavily optimized for short-read mapping and hence are very efficient for shorter queries, but that makes them inefficient or not applicable for reads longer than 200 bp. However, many sequencers are already generating longer reads and more are expected to follow. For long read sequence mapping, there are limited options; BLAT, SSAHA2, FANGS and BWA-SW are among the popular ones. However, resequencing and personalized medicine need much faster software to map these long sequencing reads to a reference genome to identify SNPs or rare transcripts. We present AGILE (AliGnIng Long rEads), a hash table based high-throughput sequence mapping algorithm for longer 454 reads that uses diagonal multiple seed-match criteria, customized q-gram filtering and a dynamic incremental search approach among other heuristics to optimize every step of the mapping process. In our experiments, we observe that AGILE is more accurate than BLAT, and comparable to BWA-SW and SSAHA2. For practical error rates (< 5%) and read lengths (200-1000 bp), AGILE is significantly faster than BLAT, SSAHA2 and BWA-SW. Even for the other cases, AGILE is comparable to BWA-SW and several times faster than BLAT and SSAHA2. http://www.ece.northwestern.edu/~smi539/agile.html.

Towards Rapid Re-Certification Using Formal Analysis

DTIC Science & Technology

2015-07-22

profiles will help ensure that information assurance requirements are commensurate with risk and scalable based on an application’s changing external...20 Scalability Evaluation .......................................................................................................... 22...agility in certification processes. Software re-certification processes require significant expenditure in order to provide evidence of information

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.

Agility: Agent - Ility Architecture

DTIC Science & Technology

2002-10-01

existing and emerging standards (e.g., distributed objects, email, web, search engines , XML, Java, Jini). Three agent system components resulted from...agents and other Internet resources and operate over the web (AgentGram), a yellow pages service that uses Internet search engines to locate XML ads for agents and other Internet resources (WebTrader).

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

Using Scrum Practices in GSD Projects

NASA Astrophysics Data System (ADS)

Paasivaara, Maria; Lassenius, Casper

In this chapter we present advice for applying Scrum practices to globally distributed software development projects. The chapter is based on a multiple-case study of four distributed Scrum projects. We discuss the use of distributed daily Scrums, Scrum-of-Scrums, Sprints, Sprint planning meetings, Sprint Demos, Retrospective meetings, and Backlogs. Moreover, we present lessons that distributed Scrum projects can benefit from non-agile globally distributed software development projects: frequent visits and multiple communication modes.

Characterizing Cyclostationary Features of Digital Modulated Signals with Empirical Measurements using Spectral Correlation Function

DTIC Science & Technology

2011-06-01

USING SPECTRAL CORRELATION FUNCTION THESIS Mujun Song, Captain, ROKA AFIT/GCE/ENG/11-09 DEPARTMENT OF THE AIR FORCE AIR UNIVERSITY AIR...Management Air Force Institute of Technology Air University Air Education and Training Command In Partial Fulfillment of the Requirements for the...generator, Agilent E4438C, ESG Vector Signal Generator. Universal Software Radio Peripheral 2 (USRP2), which is a Software Defined Radio (SDR), is used

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

Why are things where they are

NASA Astrophysics Data System (ADS)

Rathod, Nakul Pravin

The type of stores in an area gives us great insight into the people who live there. The geographic distribution of stores can be used to solve a variety of problems. Towards my goal of leveraging these patterns to solve novel problems, I have built a system to help new business owners figure out the most desirable place to open their store. I have also come up with a visualization that communicates the brands that any specific store likes to be near (or far from). This brand affinity can be used to rank the desirability of prospective rental locations. I present an analysis of how this idea went from conception to its final form with commentary on challenges faced and lessons learned. My hope is that this project not only serves as an interesting GIS project, but also a useful case study of implementing a complex software engineering project using Agile Development Methodology.

A coupling strategy for nonlocal and local diffusion models with mixed volume constraints and boundary conditions

DOE PAGES

D'Elia, Marta; Perego, Mauro; Bochev, Pavel B.; ...

2015-12-21

We develop and analyze an optimization-based method for the coupling of nonlocal and local diffusion problems with mixed volume constraints and boundary conditions. The approach formulates the coupling as a control problem where the states are the solutions of the nonlocal and local equations, the objective is to minimize their mismatch on the overlap of the nonlocal and local domains, and the controls are virtual volume constraints and boundary conditions. When some assumptions on the kernel functions hold, we prove that the resulting optimization problem is well-posed and discuss its implementation using Sandia’s agile software components toolkit. As a result,more » the latter provides the groundwork for the development of engineering analysis tools, while numerical results for nonlocal diffusion in three-dimensions illustrate key properties of the optimization-based coupling method.« less

Universal mechatronics coordinator

NASA Astrophysics Data System (ADS)

Muir, Patrick F.

1999-11-01

Mechatronic systems incorporate multiple actuators and sensor which must be properly coordinated to achieve the desired system functionality. Many mechatronic systems are designed as one-of-a-kind custom projects without consideration for facilitating future system or alterations and extensions to the current syste. Thus, subsequent changes to the system are slow, different, and costly. It has become apparent that manufacturing processes, and thus the mechatronics which embody them, need to be agile in order to more quickly and easily respond to changing customer demands or market pressures. To achieve agility, both the hardware and software of the system need to be designed such that the creation of new system and the alteration and extension of current system is fast and easy. This paper describes the design of a Universal Mechatronics Coordinator (UMC) which facilitates agile setup and changeover of coordination software for mechatronic systems. The UMC is capable of sequencing continuous and discrete actions that are programmed as stimulus-response pairs, as state machines, or a combination of the two. It facilitates the modular, reusable programing of continuous actions such as servo control algorithms, data collection code, and safety checking routines; and discrete actions such as reporting achieved states, and turning on/off binary devices. The UMC has been applied to the control of a z- theta assembly robot for the Minifactory project and is applicable to a spectrum of widely differing mechatronic systems.

Coaching for Better (Software) Buying Power in an Agile World

DTIC Science & Technology

2013-06-01

believes that DevOps , the process of warfighters and developers work- ing together throughout the project, is superior to volumes of detailed...ride on the Consolidated Afloat Networks and Enterprise Services (CANES) infrastructure. This transformation is not easy. It requires a change in

Smart Manufacturing.

PubMed

Davis, Jim; Edgar, Thomas; Graybill, Robert; Korambath, Prakashan; Schott, Brian; Swink, Denise; Wang, Jianwu; Wetzel, Jim

2015-01-01

Historic manufacturing enterprises based on vertically optimized companies, practices, market share, and competitiveness are giving way to enterprises that are responsive across an entire value chain to demand dynamic markets and customized product value adds; increased expectations for environmental sustainability, reduced energy usage, and zero incidents; and faster technology and product adoption. Agile innovation and manufacturing combined with radically increased productivity become engines for competitiveness and reinvestment, not simply for decreased cost. A focus on agility, productivity, energy, and environmental sustainability produces opportunities that are far beyond reducing market volatility. Agility directly impacts innovation, time-to-market, and faster, broader exploration of the trade space. These changes, the forces driving them, and new network-based information technologies offering unprecedented insights and analysis are motivating the advent of smart manufacturing and new information technology infrastructure for manufacturing.

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 replacements.

Development of an Agile Knowledge Engineering Framework in Support of Multi-Disciplinary Translational Research

PubMed Central

Borlawsky, Tara B.; Dhaval, Rakesh; Hastings, Shannon L.; Payne, Philip R. O.

2009-01-01

In October 2006, the National Institutes of Health launched a new national consortium, funded through Clinical and Translational Science Awards (CTSA), with the primary objective of improving the conduct and efficiency of the inherently multi-disciplinary field of translational research. To help meet this goal, the Ohio State University Center for Clinical and Translational Science has launched a knowledge management initiative that is focused on facilitating widespread semantic interoperability among administrative, basic science, clinical and research computing systems, both internally and among the translational research community at-large, through the integration of domain-specific standard terminologies and ontologies with local annotations. This manuscript describes an agile framework that builds upon prevailing knowledge engineering and semantic interoperability methods, and will be implemented as part this initiative. PMID:21347164

Development of an agile knowledge engineering framework in support of multi-disciplinary translational research.

PubMed

Borlawsky, Tara B; Dhaval, Rakesh; Hastings, Shannon L; Payne, Philip R O

2009-03-01

In October 2006, the National Institutes of Health launched a new national consortium, funded through Clinical and Translational Science Awards (CTSA), with the primary objective of improving the conduct and efficiency of the inherently multi-disciplinary field of translational research. To help meet this goal, the Ohio State University Center for Clinical and Translational Science has launched a knowledge management initiative that is focused on facilitating widespread semantic interoperability among administrative, basic science, clinical and research computing systems, both internally and among the translational research community at-large, through the integration of domain-specific standard terminologies and ontologies with local annotations. This manuscript describes an agile framework that builds upon prevailing knowledge engineering and semantic interoperability methods, and will be implemented as part this initiative.

Principles and Best Practices Emerging from Data Basin: A Data Platform Supporting Scientific Research and Landscape Conservation Planning

NASA Astrophysics Data System (ADS)

Comendant, T.; Strittholt, J. R.; Ward, B. C.; Bachelet, D. M.; Grossman, D.; Stevenson-Molnar, N.; Henifin, K.; Lundin, M.; Marvin, T. S.; Peterman, W. L.; Corrigan, G. N.; O'Connor, K.

2013-12-01

A multi-disciplinary team of scientists, software engineers, and outreach staff at the Conservation Biology Institute launched an open-access, web-based spatial data platform called Data Basin (www.databasin.org) in 2010. Primarily built to support research and environmental resource planning, Data Basin provides the capability for individuals and organizations to explore, create, interpret, and collaborate around their priority topics and geographies. We used a stakeholder analysis to assess the needs of data consumers/produces and help prioritize primary and secondary audiences. Data Basin's simple and user-friendly interface makes mapping and geo-processing tools more accessible to less technical audiences. Input from users is considered in system planning, testing, and implementation. The team continually develops using an agile software development approach, which allows new features, improvements, and bug fixes to be deployed to the live system on a frequent basis. The data import process is handled through administrative approval and Data Basin requires spatial data (biological, physical, and socio-economic) to be well-documented. Outreach and training is used to convey the scope and appropriate use of the scientific information and available resources.

POLARIS: Agent-based modeling framework development and implementation for integrated travel demand and network and operations simulations

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

Auld, Joshua; Hope, Michael; Ley, Hubert

This paper discusses the development of an agent-based modelling software development kit, and the implementation and validation of a model using it that integrates dynamic simulation of travel demand, network supply and network operations. A description is given of the core utilities in the kit: a parallel discrete event engine, interprocess exchange engine, and memory allocator, as well as a number of ancillary utilities: visualization library, database IO library, and scenario manager. The overall framework emphasizes the design goals of: generality, code agility, and high performance. This framework allows the modeling of several aspects of transportation system that are typicallymore » done with separate stand-alone software applications, in a high-performance and extensible manner. The issue of integrating such models as dynamic traffic assignment and disaggregate demand models has been a long standing issue for transportation modelers. The integrated approach shows a possible way to resolve this difficulty. The simulation model built from the POLARIS framework is a single, shared-memory process for handling all aspects of the integrated urban simulation. The resulting gains in computational efficiency and performance allow planning models to be extended to include previously separate aspects of the urban system, enhancing the utility of such models from the planning perspective. Initial tests with case studies involving traffic management center impacts on various network events such as accidents, congestion and weather events, show the potential of the system.« less

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

Creating an Agile ECE Learning Environment through Engineering Clinics

ERIC Educational Resources Information Center

Jansson, P. M.; Ramachandran, R. P.; Schmalzel, J. L.; Mandayam, S. A.

2010-01-01

To keep up with rapidly advancing technology, numerous innovations to the electrical and computer engineering (ECE) curriculum, learning methods and pedagogy have been envisioned, tested, and implemented. It is safe to say that no single approach will work for all of the diverse ECE technologies and every type of learner. However, a few key…

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.

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.

Extreme Programming: Maestro Style

NASA Technical Reports Server (NTRS)

Norris, Jeffrey; Fox, Jason; Rabe, Kenneth; Shu, I-Hsiang; Powell, Mark

2009-01-01

"Extreme Programming: Maestro Style" is the name of a computer programming methodology that has evolved as a custom version of a methodology, called extreme programming that has been practiced in the software industry since the late 1990s. The name of this version reflects its origin in the work of the Maestro team at NASA's Jet Propulsion Laboratory that develops software for Mars exploration missions. Extreme programming is oriented toward agile development of software resting on values of simplicity, communication, testing, and aggressiveness. Extreme programming involves use of methods of rapidly building and disseminating institutional knowledge among members of a computer-programming team to give all the members a shared view that matches the view of the customers for whom the software system is to be developed. Extreme programming includes frequent planning by programmers in collaboration with customers, continually examining and rewriting code in striving for the simplest workable software designs, a system metaphor (basically, an abstraction of the system that provides easy-to-remember software-naming conventions and insight into the architecture of the system), programmers working in pairs, adherence to a set of coding standards, collaboration of customers and programmers, frequent verbal communication, frequent releases of software in small increments of development, repeated testing of the developmental software by both programmers and customers, and continuous interaction between the team and the customers. The environment in which the Maestro team works requires the team to quickly adapt to changing needs of its customers. In addition, the team cannot afford to accept unnecessary development risk. Extreme programming enables the Maestro team to remain agile and provide high-quality software and service to its customers. However, several factors in the Maestro environment have made it necessary to modify some of the conventional extreme-programming practices. The single most influential of these factors is that continuous interaction between customers and programmers is not feasible.

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.

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…

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.

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

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.

Research on Automatic Positioning System of Ultrasonic Testing of Wind Turbine Blade Flaws

NASA Astrophysics Data System (ADS)

Liu, Q. X.; Wang, Z. H.; Long, S. G.; Cai, M.; Cai, M.; Wang, X.; Chen, X. Y.; Bu, J. L.

2017-11-01

Ultrasonic testing technology has been used essentially in non-destructive testing of wind turbine blades. However, it is fact that the ultrasonic flaw detection method has inefficiently employed in recent years. This is because the testing result will illustrate a small deviation due to the artificial, environmental and technical factors. Therefore, it is an urgent technical demand for engineers to test the various flaws efficiently and quickly. An automatic positioning system has been designed in this paper to record the moving coordinates and the target distance in real time. Simultaneously, it could launch and acquire the sonic wave automatically. The ADNS-3080 optoelectronic chip is manufactured by Agilent Technologies Inc, which is also utilized in the system. With the combination of the chip, the power conversion module and the USB transmission module, the collected data can be transmitted from the upper monitor to the hardware that could process and control the data through software programming. An experiment has been designed to prove the reliability of automotive positioning system. The result has been validated by comparing the result collected form LABVIEW and actual plots on Perspex plane, it concludes that the system possesses high accuracy and magnificent meanings in practical engineering.

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

Biomechanical, Physiological, and Agility Performance of Soldiers Carrying Loads: A Comparison of the Modular Lightweight Load Carrying Equipment and a Lightning Packs, LLC, Prototype

DTIC Science & Technology

2016-12-27

2015 Approved for public release; distribution is unlimited U.S. Army Natick Soldier Research, Development and Engineering Center...is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and...MODULAR LIGHTWEIGHT LOAD CARRYING EQUIPMENT) HUMAN FACTORS ENGINEERING U.S. Army Natick Soldier Research, Development and Engineering Center ATTN

Clinician user involvement in the real world: Designing an electronic tool to improve interprofessional communication and collaboration in a hospital setting.

PubMed

Tang, Terence; Lim, Morgan E; Mansfield, Elizabeth; McLachlan, Alexander; Quan, Sherman D

2018-02-01

User involvement is vital to the success of health information technology implementation. However, involving clinician users effectively and meaningfully in complex healthcare organizations remains challenging. The objective of this paper is to share our real-world experience of applying a variety of user involvement methods in the design and implementation of a clinical communication and collaboration platform aimed at facilitating care of complex hospitalized patients by an interprofessional team of clinicians. We designed and implemented an electronic clinical communication and collaboration platform in a large community teaching hospital. The design team consisted of both technical and healthcare professionals. Agile software development methodology was used to facilitate rapid iterative design and user input. We involved clinician users at all stages of the development lifecycle using a variety of user-centered, user co-design, and participatory design methods. Thirty-six software releases were delivered over 24 months. User involvement has resulted in improvement in user interface design, identification of software defects, creation of new modules that facilitated workflow, and identification of necessary changes to the scope of the project early on. A variety of user involvement methods were complementary and benefited the design and implementation of a complex health IT solution. Combining these methods with agile software development methodology can turn designs into functioning clinical system to support iterative improvement. Copyright © 2017 The Authors. Published by Elsevier B.V. All rights reserved.

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.

Agile Methods and Request for Change (RFC): Observations from DoD Acquisition Programs

DTIC Science & Technology

2014-01-01

at the Software Development Plan, then it’s worth having a conversation with the contractor that includes answering the above questions. MSA TD EMD...Lap- ham 2010] CMU/SEI-2013-TN-031 | 18 those undertaken in more traditional waterfall-based developments. Some of the government PMO enabling

The Challenges of Being Agile in DoD

DTIC Science & Technology

2013-02-01

term “Agile” will serve as an overarching term to represent all forms of iterative development whether Scrum , Lean Software Development, extreme...occur? • How do we know what the development team will deliver at the end of the Sprint? (A basic unit of development in Scrum that lasts for “time

Using the Agile Development Methodology and Applying Best Practice Project Management Processes

DTIC Science & Technology

2014-12-01

side of this writing: Like finicky domestic helpers who announce that they ‘don’t do windows,’ I’ve often heard software developers state proudly...positioned or motivated, but rather because they were the least skilled developer (2012, 34). This result turned a team of what should be generalists

Real-time access of large volume imagery through low-bandwidth links

NASA Astrophysics Data System (ADS)

Phillips, James; Grohs, Karl; Brower, Bernard; Kelly, Lawrence; Carlisle, Lewis; Pellechia, Matthew

2010-04-01

Providing current, time-sensitive imagery and geospatial information to deployed tactical military forces or first responders continues to be a challenge. This challenge is compounded through rapid increases in sensor collection volumes, both with larger arrays and higher temporal capture rates. Focusing on the needs of these military forces and first responders, ITT developed a system called AGILE (Advanced Geospatial Imagery Library Enterprise) Access as an innovative approach based on standard off-the-shelf techniques to solving this problem. The AGILE Access system is based on commercial software called Image Access Solutions (IAS) and incorporates standard JPEG 2000 processing. Our solution system is implemented in an accredited, deployable form, incorporating a suite of components, including an image database, a web-based search and discovery tool, and several software tools that act in concert to process, store, and disseminate imagery from airborne systems and commercial satellites. Currently, this solution is operational within the U.S. Government tactical infrastructure and supports disadvantaged imagery users in the field. This paper presents the features and benefits of this system to disadvantaged users as demonstrated in real-world operational environments.

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.

Agile Port and High Speed Ship Technologies

DTIC Science & Technology

2009-12-31

Alternative Shipboard Powering Systems for Naval and Regulatory Review • The Evaluation and Implementation Plan for Southern California Maglev ...Ackerman". CSULB Foundation Annual Report. CSULB Foundation, Long Beach, CA. December 2005. " Maglev Technology ’Conveys’ Port Transportation Solutions...34. Newsflash. College of Engineering, California State University, Long Beach. Cover page. Spring 2006 Hanson, Kristopher. "Engineers Tout Maglev at

Motivating Company Personnel by Applying the Semi-self-organized Teams Principle

NASA Astrophysics Data System (ADS)

Kumlander, Deniss

The only way nowadays to improve stability of software development process in the global rapidly evolving world is to be innovative and involve professionals into projects motivating them using both material and non material factors. In this paper self-organized teams are discussed. Unfortunately not all kind of organizations can benefit directly from agile method including applying self-organized teams. The paper proposes semi-self-organized teams presenting it as a new and promising motivating factor allowing deriving many positive sides of been self-organized and partly agile and been compliant to less strict conditions for following this innovating process. The semi-self organized teams are reliable at least in the short-term perspective and are simple to organize and support.

NASA Tech Briefs, November 2012

NASA Technical Reports Server (NTRS)

2012-01-01

The topics include: Visual System for Browsing, Analysis, and Retrieval of Data (ViSBARD); Time-Domain Terahertz Computed Axial Tomography NDE System; Adaptive Sampling of Time Series During Remote Exploration; A Tracking Sun Photometer Without Moving Parts; Surface Temperature Data Analysis; Modular, Autonomous Command and Data Handling Software with Built-In Simulation and Test; In-Situ Wire Damage Detection System; Amplifier Module for 260-GHz Band Using Quartz Waveguide Transitions; Wideband Agile Digital Microwave Radiometer; Buckyball Nucleation of HiPco Tubes; FACT, Mega-ROSA, SOLAROSA; An Integrated, Layered-Spinel Composite Cathode for Energy Storage Applications; Engineered Multifunctional Surfaces for Fluid Handling; Polyolefin-Based Aerogels; Adjusting Permittivity by Blending Varying Ratios of SWNTs; Gravity-Assist Mechanical Simulator for Outreach; Concept for Hydrogen-Impregnated Nanofiber/Photovoltaic Cargo Stowage System; DROP: Durable Reconnaissance and Observation Platform; Developing Physiologic Models for Emergency Medical Procedures Under Microgravity; Spectroscopic Chemical Analysis Methods and Apparatus; Low Average Sidelobe Slot Array Antennas for Radiometer Applications; Motion-Corrected 3D Sonic Anemometer for Tethersondes and Other Moving Platforms; Water Treatment Systems for Long Spaceflights; Microchip Non-Aqueous Capillary Electrophoresis (MicronNACE) Method to Analyze Long-Chain Primary Amines; Low-Cost Phased Array Antenna for Sounding Rockets, Missiles, and Expendable Launch Vehicles; Mars Science Laboratory Engineering Cameras; Seismic Imager Space Telescope; Estimating Sea Surface Salinity and Wind Using Combined Passive and Active L-Band Microwave Observations; A Posteriori Study of a DNS Database Describing Super critical Binary-Species Mixing; Scalable SCPPM Decoder; QuakeSim 2.0; HURON (HUman and Robotic Optimization Network) Multi-Agent Temporal Activity Planner/Scheduler; MPST Software: MoonKommand

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 system will launch only one mission per year even less during its developmental phases. Finally, the third is the partnered approach through the use of many different prime contractors, including commercial and international partners, to design and build the exploration systems. These three factors make the challenges to meet the mission preparations and the safety expectations extremely difficult to implement. As NASA leads a team of partners in the exploration beyond earth's influence, it is a safety imperative that the application software used to test, checkout, prepare and launch the exploration systems put safety of the hardware and mission first. Software safety characteristics are built into the design and development process to enable the human rated systems to begin their missions safely and successfully. Exploration missions beyond Earth are inherently risky, however, with solid safety approaches in both hardware and software, the boldness of these missions can be realized for all on the home planet.

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.

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.

Content Documents Management

NASA Technical Reports Server (NTRS)

Muniz, R.; Hochstadt, J.; Boelke J.; Dalton, A.

2011-01-01

The Content Documents are created and managed under the System Software group with. Launch Control System (LCS) project. The System Software product group is lead by NASA Engineering Control and Data Systems branch (NEC3) at Kennedy Space Center. The team is working on creating Operating System Images (OSI) for different platforms (i.e. AIX, Linux, Solaris and Windows). Before the OSI can be created, the team must create a Content Document which provides the information of a workstation or server, with the list of all the software that is to be installed on it and also the set where the hardware belongs. This can be for example in the LDS, the ADS or the FR-l. The objective of this project is to create a User Interface Web application that can manage the information of the Content Documents, with all the correct validations and filters for administrator purposes. For this project we used one of the most excellent tools in agile development applications called Ruby on Rails. This tool helps pragmatic programmers develop Web applications with Rails framework and Ruby programming language. It is very amazing to see how a student can learn about OOP features with the Ruby language, manage the user interface with HTML and CSS, create associations and queries with gems, manage databases and run a server with MYSQL, run shell commands with command prompt and create Web frameworks with Rails. All of this in a real world project and in just fifteen weeks!

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 suite. We used test-driven development to construct a new CDS tool advising Emergency Department nurses to perform a swallowing assessment prior to administering oral medication to a patient with suspected stroke. Test tables specified desired behavior for (1) applicable clinical settings, (2) triggering action, (3) rule logic, (4) user interface, and (5) system actions in response to user input. Automated test suite results for the "executable requirements" are shown prior to building the CDS alert, during build, and after successful build. Automated acceptance test-driven development and continuous regression testing of CDS configuration in a commercial EHR proves feasible with open source software. Automated test-driven development offers one potential contribution to achieving high-reliability EHR configuration. Vetting acceptance tests with clinicians elicits their input on crucial configuration details early during initial CDS design and iteratively during rapid-cycle optimization. ©Mujeeb A Basit, Krystal L Baldwin, Vaishnavi Kannan, Emily L Flahaven, Cassandra J Parks, Jason M Ott, Duwayne L Willett. Originally published in JMIR Medical Informatics (http://medinform.jmir.org), 13.04.2018.

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 geosciences. We use code management that allows researchers to interact with the code through tools like Jupyter Notebooks while data are held in an object store. Our aim is an architecture allowing seamless integration of code development, data management, and data processing in virtual research environments.

Fostering Cooperative Learning with Scrum in a Semi-Capstone Systems Analysis and Design Course

ERIC Educational Resources Information Center

Magana, Alejandra J.; Seah, Ying Ying; Thomas, Paul

2018-01-01

Agile methods such as Scrum that emphasize technical, communication, and teamwork skills have been practiced by IT professionals to effectively deliver software products of good quality. The same methods combined with pedagogies of engagement can potentially be used in the setting of higher education to promote effective group learning in software…

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

First-Year Students' Impressions of Pair Programming in CS1

ERIC Educational Resources Information Center

Simon, Beth; Hanks, Brian

2008-01-01

Pair programming, as part of the Agile Development process, has noted benefits in professional software development scenarios. These successes have led to a rise in use of pair programming in educational settings, particularly in Computer Science 1 (CS1). Specifically, McDowell et al. [2006] has shown that students using pair programming in CS1 do…

Model based design introduction: modeling game controllers to microprocessor architectures

NASA Astrophysics Data System (ADS)

Jungwirth, Patrick; Badawy, Abdel-Hameed

2017-04-01

We present an introduction to model based design. Model based design is a visual representation, generally a block diagram, to model and incrementally develop a complex system. Model based design is a commonly used design methodology for digital signal processing, control systems, and embedded systems. Model based design's philosophy is: to solve a problem - a step at a time. The approach can be compared to a series of steps to converge to a solution. A block diagram simulation tool allows a design to be simulated with real world measurement data. For example, if an analog control system is being upgraded to a digital control system, the analog sensor input signals can be recorded. The digital control algorithm can be simulated with the real world sensor data. The output from the simulated digital control system can then be compared to the old analog based control system. Model based design can compared to Agile software develop. The Agile software development goal is to develop working software in incremental steps. Progress is measured in completed and tested code units. Progress is measured in model based design by completed and tested blocks. We present a concept for a video game controller and then use model based design to iterate the design towards a working system. We will also describe a model based design effort to develop an OS Friendly Microprocessor Architecture based on the RISC-V.

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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

The ATLAS Software Installation System v2: a highly available system to install and validate Grid and Cloud sites via Panda

NASA Astrophysics Data System (ADS)

De Salvo, A.; Kataoka, M.; Sanchez Pineda, A.; Smirnov, Y.

2015-12-01

The ATLAS Installation System v2 is the evolution of the original system, used since 2003. The original tool has been completely re-designed in terms of database backend and components, adding support for submission to multiple backends, including the original Workload Management Service (WMS) and the new PanDA modules. The database engine has been changed from plain MySQL to Galera/Percona and the table structure has been optimized to allow a full High-Availability (HA) solution over Wide Area Network. The servlets, running on each frontend, have been also decoupled from local settings, to allow an easy scalability of the system, including the possibility of an HA system with multiple sites. The clients can also be run in multiple copies and in different geographical locations, and take care of sending the installation and validation jobs to the target Grid or Cloud sites. Moreover, the Installation Database is used as source of parameters by the automatic agents running in CVMFS, in order to install the software and distribute it to the sites. The system is in production for ATLAS since 2013, having as main sites in HA the INFN Roma Tier 2 and the CERN Agile Infrastructure. The Light Job Submission Framework for Installation (LJSFi) v2 engine is directly interfacing with PanDA for the Job Management, the Atlas Grid Information System (AGIS) for the site parameter configurations, and CVMFS for both core components and the installation of the software itself. LJSFi2 is also able to use other plugins, and is essentially Virtual Organization (VO) agnostic, so can be directly used and extended to cope with the requirements of any Grid or Cloud enabled VO. In this work we will present the architecture, performance, status and possible evolutions to the system for the LHC Run2 and beyond.

Calibration of X-Ray diffractometer by the experimental comparison method

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

Dudka, A. P., E-mail: dudka@ns.crys.ras.ru

2015-07-15

A software for calibrating an X-ray diffractometer with area detector has been developed. It is proposed to search for detector and goniometer calibration models whose parameters are reproduced in a series of measurements on a reference crystal. Reference (standard) crystals are prepared during the investigation; they should provide the agreement of structural models in repeated analyses. The technique developed has been used to calibrate Xcalibur Sapphire and Eos, Gemini Ruby (Agilent) and Apex x8 and Apex Duo (Bruker) diffractometers. The main conclusions are as follows: the calibration maps are stable for several years and can be used to improve structuralmore » results, verified CCD detectors exhibit significant inhomogeneity of the efficiency (response) function, and a Bruker goniometer introduces smaller distortions than an Agilent goniometer.« less

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.

Research to Operations of Ionospheric Scintillation Detection and Forecasting

NASA Astrophysics Data System (ADS)

Jones, J.; Scro, K.; Payne, D.; Ruhge, R.; Erickson, B.; Andorka, S.; Ludwig, C.; Karmann, J.; Ebelhar, D.

Ionospheric Scintillation refers to random fluctuations in phase and amplitude of electromagnetic waves caused by a rapidly varying refractive index due to turbulent features in the ionosphere. Scintillation of transionospheric UHF and L-Band radio frequency signals is particularly troublesome since this phenomenon can lead to degradation of signal strength and integrity that can negatively impact satellite communications and navigation, radar, or radio signals from other systems that traverse or interact with the ionosphere. Although ionospheric scintillation occurs in both the equatorial and polar regions of the Earth, the focus of this modeling effort is on equatorial scintillation. The ionospheric scintillation model is data-driven in a sense that scintillation observations are used to perform detection and characterization of scintillation structures. These structures are then propagated to future times using drift and decay models to represent the natural evolution of ionospheric scintillation. The impact on radio signals is also determined by the model and represented in graphical format to the user. A frequency scaling algorithm allows for impact analysis on frequencies other than the observation frequencies. The project began with lab-grade software and through a tailored Agile development process, deployed operational-grade code to a DoD operational center. The Agile development process promotes adaptive promote adaptive planning, evolutionary development, early delivery, continuous improvement, regular collaboration with the customer, and encourage rapid and flexible response to customer-driven changes. The Agile philosophy values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a rigid plan. The end result was an operational capability that met customer expectations. Details of the model and the process of operational integration are discussed as well as lessons learned to improve performance on future projects.

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 may facilitate sharing workflows among the scientific community. Workflows for GATK and Dindel are available at http://github.com/misshie/Workflows.

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 and maintainability of rakefiles may facilitate sharing workflows among the scientific community. Workflows for GATK and Dindel are available at http://github.com/misshie/Workflows. PMID:21899774

David S. Ginley | NREL

Science.gov Websites

is on the development of new nanomaterials for organic electronics and as biofilters etc. Dr are applying what they learn to improved devices, i.e. batteries, frequency agile electronics Society (ECS) Institute of Electrical and Electronics Engineers (IEEE) American Association for the

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.

Towards Agile Ontology Maintenance

NASA Astrophysics Data System (ADS)

Luczak-Rösch, Markus

Ontologies are an appropriate means to represent knowledge on the Web. Research on ontology engineering reached practices for an integrative lifecycle support. However, a broader success of ontologies in Web-based information systems remains unreached while the more lightweight semantic approaches are rather successful. We assume, paired with the emerging trend of services and microservices on the Web, new dynamic scenarios gain momentum in which a shared knowledge base is made available to several dynamically changing services with disparate requirements. Our work envisions a step towards such a dynamic scenario in which an ontology adapts to the requirements of the accessing services and applications as well as the user's needs in an agile way and reduces the experts' involvement in ontology maintenance processes.

A Simulated Learning Environment for Teaching Medicine Dispensing Skills

PubMed Central

Styles, Kim; Sewell, Keith; Trinder, Peta; Marriott, Jennifer; Maher, Sheryl; Naidu, Som

2016-01-01

Objective. To develop an authentic simulation of the professional practice dispensary context for students to develop their dispensing skills in a risk-free environment. Design. A development team used an Agile software development method to create MyDispense, a web-based simulation. Modeled on virtual learning environments elements, the software employed widely available standards-based technologies to create a virtual community pharmacy environment. Assessment. First-year pharmacy students who used the software in their tutorials, were, at the end of the second semester, surveyed on their prior dispensing experience and their perceptions of MyDispense as a tool to learn dispensing skills. Conclusion. The dispensary simulation is an effective tool for helping students develop dispensing competency and knowledge in a safe environment. PMID:26941437

Early Formulation Model-centric Engineering on Nasa's Europa Mission Concept Study

NASA Technical Reports Server (NTRS)

Bayer, Todd; Chung, Seung; Cole, Bjorn; Cooke, Brian; Dekens, Frank; Delp, Chris; Gontijo, I.; Lewis, Kari; Moshir, Mehrdad; Rasmussen, Robert;

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.

Gaps in the Body of Knowledge of Systems Engineering

DTIC Science & Technology

2012-07-01

practices, agile development, Kanban , risk management, and decision management. This focus is being driven by the need to reduce time for delivery of...to incorporate Kanban approaches to scheduling the SE activities based on value. Rapid Fielding. In this situation, there is a short time to

SERC 2011 Annual Report

DTIC Science & Technology

2011-01-01

control number. 1. REPORT DATE 2011 2. REPORT TYPE 3. DATES COVERED 00-00-2011 to 00-00-2011 4. TITLE AND SUBTITLE SERC 2011 Annual Report...2 SERC Operational Accomplishments .................................................................4 An Evolving Role for the... SERC Research Council ................................5 Systems Engineering for an Agile and Lean World ....................................6 Annual

Investigation of a Graphical CONOPS Development Environment for Agile Systems Engineering - Phase 2

DTIC Science & Technology

2010-05-31

Westerman, Crawshaw , Hockey, and Sauer, 1998) for practitioners. Thus, CTA extends research by providing a toolbox of methods for understanding teams...drive process and performance. Washington, DC: American Psychological Association. pp. 3-8. Shrayne, N. M., Westerman, S. J., Crawshaw , C. M

Software Engineering Guidebook

NASA Technical Reports Server (NTRS)

Connell, John; Wenneson, Greg

1993-01-01

The Software Engineering Guidebook describes SEPG (Software Engineering Process Group) supported processes and techniques for engineering quality software in NASA environments. Three process models are supported: structured, object-oriented, and evolutionary rapid-prototyping. The guidebook covers software life-cycles, engineering, assurance, and configuration management. The guidebook is written for managers and engineers who manage, develop, enhance, and/or maintain software under the Computer Software Services Contract.

Software Acquisition Patterns of Failure and How to Recognize Them

DTIC Science & Technology

2013-04-01

Acquisition Processes Danielle Worger and Teresa Wu, Arizona State University Eugene Rex Jalao, Arizona State University and University of the Philippines...Robert Wirthlin Air Force Institute of Technology The RITE Approach to Agile Acquisition Timothy Boyce, Iva Sherman, and Nicholas Roussel Space...the Joint Capabilities Technology Demonstration Office: Ad Hoc Problem Solving as a Mechanism for Adaptive Change Kathryn Aten and John T . Dillard

Evolution of the Scope and Capabilities of Uplink Support Software for Mars Surface Operations

NASA Technical Reports Server (NTRS)

Pack, Marc; Laubach, Sharon

2014-01-01

In January of 2004 both of the Mars Exploration Rover spacecraft landed safely, initiating daily surface operations at the Jet Propulsion Laboratory for what was anticipated to be approximately three months of mobile exploration. The longevity of this mission, still ongoing after ten years, has provided not only a tremendous return of scientific data but also the opportunity to refine and improve the methodology by which robotic Mars surface missions are commanded. Since the landing of the Mars Science Laboratory spacecraft in August of 2012, this methodology has been successfully applied to operate a Martian rover which is both similar to, and quite different from, its predecessors. For MER and MSL, daily uplink operations can be most broadly viewed as converting the combined interests of both the science and engineering teams into a spacecraft-safe set of transmittable command files. In order to accomplish these ends a discrete set of mission-critical software tools were developed which not only allowed for conformation to established JPL standards and practices but also enabled innovative technologies specific to each mission. Although these primary programs provided the requisite capabilities for meeting the high-level goals of each distinct phase of the uplink process, there was little in the way of secondary software to support the smooth flow of data from one phase to the next. In order to address this shortcoming a suite of small software tools was developed to aid in phase transitions, as well as to automate some of the more laborious and error-prone aspects of uplink operations. This paper describes the evolution of this software suite, from its initial attempts to merely shorten the duration of the operator's shift, to its current role as an indispensable tool enforcing workflow of the uplink operations process and agilely responding to the new and unexpected challenges of missions which can, and have, lasted many years longer than originally anticipated.

Proceedings of the Seventeenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1992-01-01

Proceedings of the Seventeenth Annual Software Engineering Workshop are presented. The software Engineering Laboratory (SEL) is an organization sponsored by NASA/Goddard Space Flight Center and created to investigate the effectiveness of software engineering technologies when applied to the development of applications software. Topics covered include: the Software Engineering Laboratory; process measurement; software reuse; software quality; lessons learned; and is Ada dying.

Software Past, Present, and Future: Views from Government, Industry and Academia

NASA Technical Reports Server (NTRS)

Holcomb, Lee; Page, Jerry; Evangelist, Michael

2000-01-01

Views from the NASA CIO NASA Software Engineering Workshop on software development from the past, present, and future are presented. The topics include: 1) Software Past; 2) Software Present; 3) NASA's Largest Software Challenges; 4) 8330 Software Projects in Industry Standish Groups 1994 Report; 5) Software Future; 6) Capability Maturity Model (CMM): Software Engineering Institute (SEI) levels; 7) System Engineering Quality Also Part of the Problem; 8) University Environment Trends Will Increase the Problem in Software Engineering; and 9) NASA Software Engineering Goals.

20th Annual Systems Engineering Conference. Volume 2, Wednesday

DTIC Science & Technology

2017-10-26

Assurance Center (JFAC) 2017 Update u Mr. Thomas Hurt, Department of Defense 4B1 Tr a c k 2 m il le r Education & Training 19813 Shaping the... J . C . S. P. (2002, September). Agile requirements definition: A view from requirements engineering. In Proceedings of the International Workshop on...Management 52.2 (2005): 199-212. Web. 4. R. J . Calantone, and C . A. Di Benedetto. "Performance and Time to Market: Accelerating Cycle Time with

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,250 pounds. It was 19 feet long and three feet high with a wingspan of just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

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 with a wingspan of just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Tailless Fighter Agility Research Aircraft on lakebed during high-speed taxi tests

NASA Technical Reports Server (NTRS)

1996-01-01

The NASA/McDonnell Douglas Corporation (MDC) X-36 Tailless Fighter Agility Research Aircraft undergoes high-speed taxi tests on Rogers Dry Lake at NASA Dryden Flight Research Center, Edwards, California, on October 17, 1996. The aircraft was tested at speeds up to 85 knots. Normal takeoff speed would be 110 knots. More taxi and radio frequency tests were slated before it's first flight would be made. This took place on May 17, 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Tailless Fighter Agility Research Aircraft on lakebed during high-speed taxi tests

NASA Technical Reports Server (NTRS)

1996-01-01

The NASA/McDonnell Douglas Corporation (MDC) X-36 Tailless Fighter Agility Research Aircraft undergoes high-speed taxi tests on Rogers Dry Lake at NASA Dryden Flight Research Center, Edwards, California, on October 17, 1996. The aircraft was tested at speeds up to 85 knots. Normal takeoff speed would be 110 knots. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

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 wingspan of just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

Software engineering as an engineering discipline

NASA Technical Reports Server (NTRS)

Gibbs, Norman

1988-01-01

The goals of the Software Engineering Institute's Education Program are as follows: to increase the number of highly qualified software engineers--new software engineers and existing practitioners; and to be the leading center of expertise for software engineering education and training. A discussion of these goals is presented in vugraph form.

Software engineering as an engineering discipline

NASA Technical Reports Server (NTRS)

Berard, Edward V.

1988-01-01

The following topics are discussed in the context of software engineering: early use of the term; the 1968 NATO conference; Barry Boehm's definition; four requirements fo software engineering; and additional criteria for software engineering. Additionally, the four major requirements for software engineering--computer science, mathematics, engineering disciplines, and excellent communication skills--are discussed. The presentation is given in vugraph form.

Low Power, Low Mass, Modular, Multi-band Software-defined Radios

NASA Technical Reports Server (NTRS)

Haskins, Christopher B. (Inventor); Millard, Wesley P. (Inventor)

2013-01-01

Methods and systems to implement and operate software-defined radios (SDRs). An SDR may be configured to perform a combination of fractional and integer frequency synthesis and direct digital synthesis under control of a digital signal processor, which may provide a set of relatively agile, flexible, low-noise, and low spurious, timing and frequency conversion signals, and which may be used to maintain a transmit path coherent with a receive path. Frequency synthesis may include dithering to provide additional precision. The SDR may include task-specific software-configurable systems to perform tasks in accordance with software-defined parameters or personalities. The SDR may include a hardware interface system to control hardware components, and a host interface system to provide an interface to the SDR with respect to a host system. The SDR may be configured for one or more of communications, navigation, radio science, and sensors.

From Exotic to Mainstream: A 10-year Odyssey from Internet Speed to Boundary Spanning with Scrum

NASA Astrophysics Data System (ADS)

Baskerville, Richard; Pries-Heje, Jan; Madsen, Sabine

Based on four empirical studies conducted over a 10-year time period from 1999 to 2008 we investigate how local software processes interact with global changes in the software development context. In 1999 companies were developing software at high speed in a desperate rush to be first-to-market. In 2001 a new high speed/quick results development process had become established practice. In 2003 changes in the market created the need for a more balanced view on speed and quality, and in 2008 companies were successfully combining agile and plan driven approaches to achieve the benefits of both. The studies reveal a twostage pattern in which dramatic changes in the market causes disruption of established practices, experimentation, and process adaptations followed by consolidation of lessons learnt into a new (and once again mature) software development process. Limitations, implications, and areas for future research are discussed.

Toward effectiveness and agility of network security situational awareness using moving target defense (MTD)

NASA Astrophysics Data System (ADS)

Ge, Linqiang; Yu, Wei; Shen, Dan; Chen, Genshe; Pham, Khanh; Blasch, Erik; Lu, Chao

2014-06-01

Most enterprise networks are built to operate in a static configuration (e.g., static software stacks, network configurations, and application deployments). Nonetheless, static systems make it easy for a cyber adversary to plan and launch successful attacks. To address static vulnerability, moving target defense (MTD) has been proposed to increase the difficulty for the adversary to launch successful attacks. In this paper, we first present a literature review of existing MTD techniques. We then propose a generic defense framework, which can provision an incentive-compatible MTD mechanism through dynamically migrating server locations. We also present a user-server mapping mechanism, which not only improves system resiliency, but also ensures network performance. We demonstrate a MTD with a multi-user network communication and our data shows that the proposed framework can effectively improve the resiliency and agility of the system while achieving good network timeliness and throughput performance.

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.

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.

Information Sharing for Computing Trust Metrics on COTS Electronic Components

DTIC Science & Technology

2008-09-01

8 a. Standard SDLCs ...........................8 b. The Waterfall Model ......................9 c. V -shaped Model ...development of a system. There are many well-known SDLC models , the most popular of which are: • Waterfall • V -shaped • Spiral • Agile a. Standard...the SDLC or applied to software and hardware distribution chain. A. JØSANG’S MODEL DEFINED Jøsang expresses "opinions" mathematically as: 1

Annotated bibliography of Software Engineering Laboratory literature

NASA Technical Reports Server (NTRS)

Morusiewicz, Linda; Valett, Jon D.

1991-01-01

An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. All materials have been grouped into eight general subject areas for easy reference: The Software Engineering Laboratory; The Software Engineering Laboratory: Software Development Documents; Software Tools; Software Models; Software Measurement; Technology Evaluations; Ada Technology; and Data Collection. Subject and author indexes further classify these documents by specific topic and individual author.

Computational study of engine external aerodynamics as a part of multidisciplinary optimization procedure

NASA Astrophysics Data System (ADS)

Savelyev, Andrey; Anisimov, Kirill; Kazhan, Egor; Kursakov, Innocentiy; Lysenkov, Alexandr

2016-10-01

The paper is devoted to the development of methodology to optimize external aerodynamics of the engine. Optimization procedure is based on numerical solution of the Reynolds-averaged Navier-Stokes equations. As a method of optimization the surrogate based method is used. As a test problem optimal shape design of turbofan nacelle is considered. The results of the first stage, which investigates classic airplane configuration with engine located under the wing, are presented. Described optimization procedure is considered in the context of multidisciplinary optimization of the 3rd generation, developed in the project AGILE.

Software Engineering Laboratory Series: Proceedings of the Twentieth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1995-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 15

NASA Technical Reports Server (NTRS)

1997-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 14

NASA Technical Reports Server (NTRS)

1996-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

Software Engineering Laboratory Series: Collected Software Engineering Papers. Volume 13

NASA Technical Reports Server (NTRS)

1995-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

Supporting interoperability of collaborative networks through engineering of a service-based Mediation Information System (MISE 2.0)

NASA Astrophysics Data System (ADS)

Benaben, Frederick; Mu, Wenxin; Boissel-Dallier, Nicolas; Barthe-Delanoe, Anne-Marie; Zribi, Sarah; Pingaud, Herve

2015-08-01

The Mediation Information System Engineering project is currently finishing its second iteration (MISE 2.0). The main objective of this scientific project is to provide any emerging collaborative situation with methods and tools to deploy a Mediation Information System (MIS). MISE 2.0 aims at defining and designing a service-based platform, dedicated to initiating and supporting the interoperability of collaborative situations among potential partners. This MISE 2.0 platform implements a model-driven engineering approach to the design of a service-oriented MIS dedicated to supporting the collaborative situation. This approach is structured in three layers, each providing their own key innovative points: (i) the gathering of individual and collaborative knowledge to provide appropriate collaborative business behaviour (key point: knowledge management, including semantics, exploitation and capitalisation), (ii) deployment of a mediation information system able to computerise the previously deduced collaborative processes (key point: the automatic generation of collaborative workflows, including connection with existing devices or services) (iii) the management of the agility of the obtained collaborative network of organisations (key point: supervision of collaborative situations and relevant exploitation of the gathered data). MISE covers business issues (through BPM), technical issues (through an SOA) and agility issues of collaborative situations (through EDA).

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.

Software engineering laboratory series: Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Morusiewicz, Linda; Valett, Jon

1992-01-01

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) the Software Engineering Laboratory; (2) the Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.

Software Engineering Laboratory Series: Proceedings of the Twenty-First Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1996-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

Software Engineering Laboratory Series: Proceedings of the Twenty-Second Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1997-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of application software. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that includes this document.

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 the Nunaliit Atlas framework (a Java/JavaScript client-server web-based application) with an existing Ruby on Rails application. This approach requires transitioning individual applications to expose a service layer, thus allowing interapplication communication via RESTful services. In this presentation we will report on our experiences using Agile Scrum practices, our efforts to move from custom solutions to a platform of customizable modules, and the impact of each on our ability to support researchers and Arctic residents in the domain of community-based observations and knowledge.

Cybersecurity Protection: Design Science Research toward an Intercloud Transparent Bridge Architecture (ITCOBRA)

ERIC Educational Resources Information Center

Wilson, Joe M.

2013-01-01

This dissertation uses design science research and engineering to develop a cloud-based simulator for modeling next-generation cybersecurity protection frameworks in the United States. The claim is made that an agile and neutral framework extending throughout the cyber-threat plane is needed for critical infrastructure protection (CIP). This…

Software engineering and the role of Ada: Executive seminar

NASA Technical Reports Server (NTRS)

Freedman, Glenn B.

1987-01-01

The objective was to introduce the basic terminology and concepts of software engineering and Ada. The life cycle model is reviewed. The application of the goals and principles of software engineering is applied. An introductory understanding of the features of the Ada language is gained. Topics addressed include: the software crises; the mandate of the Space Station Program; software life cycle model; software engineering; and Ada under the software engineering umbrella.

[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-67) variables and 41,566 bytes of hard-disk memory space. Stress echocardiographic studies, each lasting 7 +/- 5 (range 5-21) min, were recorded using 143 +/- 74 (range 38-194) variables and 38,531 bytes of hard-disk memory space. To our knowledge this software represents the first experience of a common computerized program for echo archiving and reporting carried out at national level.

Aspects of the BPRIM Language for Risk Driven Process Engineering

NASA Astrophysics Data System (ADS)

Sienou, Amadou; Lamine, Elyes; Pingaud, Hervé; Karduck, Achim

Nowadays organizations are exposed to frequent changes in business environment requiring continuous alignment of business processes on business strategies. This agility requires methods promoted in enterprise engineering approaches. Risk consideration in enterprise engineering is getting important since the business environment is becoming more and more competitive and unpredictable. Business processes are subject to the same quality requirements as material and human resources. Thus, process management is supposed to tackle value creation challenges but also the ones related to value preservation. Our research considers risk driven business process design as an integral part of enterprise engineering. A graphical modelling language for risk driven business process engineering was introduced in former research. This paper extends the language and handles questions related to modelling risk in organisational context.

Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Groves, Paula; Valett, Jon

1990-01-01

An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is given. More than 100 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory-software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. Subject and author indexes further classify these documents by specific topic and individual author.

Annotated bibliography of Software Engineering Laboratory literature

NASA Technical Reports Server (NTRS)

Morusiewicz, Linda; Valett, Jon

1993-01-01

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: the Software Engineering Laboratory; the Software Engineering Laboratory: software development documents; software tools; software models; software measurement; technology evaluations; Ada technology; and data collection. This document contains an index of these publications classified by individual author.

Software Sustainment -- Now and Future

DTIC Science & Technology

2014-01-01

today the commercial environment is using something referred to as DevOps . What is DevOps ? What it is. A way of working that encourages the Develop...section. However, there are some major differences. DevOps seems to be the Agile community’s term for doing sustainment and opera- tions in parallel...methods in sustainment within the federal government. This research is how I came upon the term DevOps . In addition, Gene Kim provided a keynote

Guide for SCAMPI Appraisals: Accelerated Improvement Method (AIM)

DTIC Science & Technology

2010-12-01

discussion of TSP introduction strategy appears in Leadership, Teamwork, and Trust: Building a Com- petitive Software Capability by Watts S . Humphrey and...have more life cycles (e.g., Agile, RUP) reflected in the OSSP or the project note- book ( s ). A CMMI start-up pack- age should include documenta...to appraisers, is well docu- mented in the PSP /TSP books MA SP 1.3 Specify how measurement data will be obtained and stored. Forms SUMS

LCG/AA build infrastructure

NASA Astrophysics Data System (ADS)

Hodgkins, Alex Liam; Diez, Victor; Hegner, Benedikt

2012-12-01

The Software Process & Infrastructure (SPI) project provides a build infrastructure for regular integration testing and release of the LCG Applications Area software stack. In the past, regular builds have been provided using a system which has been constantly growing to include more features like server-client communication, long-term build history and a summary web interface using present-day web technologies. However, the ad-hoc style of software development resulted in a setup that is hard to monitor, inflexible and difficult to expand. The new version of the infrastructure is based on the Django Python framework, which allows for a structured and modular design, facilitating later additions. Transparency in the workflows and ease of monitoring has been one of the priorities in the design. Formerly missing functionality like on-demand builds or release triggering will support the transition to a more agile development process.

Software Development for EECU Platform of Turbofan Engine

NASA Astrophysics Data System (ADS)

Kim, Bo Gyoung; Kwak, Dohyup; Kim, Byunghyun; Choi, Hee ju; Kong, Changduk

2017-04-01

The turbofan engine operation consists of a number of hardware and software. The engine is controlled by Electronic Engine Control Unit (EECU). In order to control the engine, EECU communicates with an aircraft system, Actuator Drive Unit (ADU), Engine Power Unit (EPU) and sensors on the engine. This paper tried to investigate the process form starting to taking-off and aims to design the EECU software mode and defined communication data format. The software is implemented according to the designed software mode.

Software engineering methodologies and tools

NASA Technical Reports Server (NTRS)

Wilcox, Lawrence M.

1993-01-01

Over the years many engineering disciplines have developed, including chemical, electronic, etc. Common to all engineering disciplines is the use of rigor, models, metrics, and predefined methodologies. Recently, a new engineering discipline has appeared on the scene, called software engineering. For over thirty years computer software has been developed and the track record has not been good. Software development projects often miss schedules, are over budget, do not give the user what is wanted, and produce defects. One estimate is there are one to three defects per 1000 lines of deployed code. More and more systems are requiring larger and more complex software for support. As this requirement grows, the software development problems grow exponentially. It is believed that software quality can be improved by applying engineering principles. Another compelling reason to bring the engineering disciplines to software development is productivity. It has been estimated that productivity of producing software has only increased one to two percent a year in the last thirty years. Ironically, the computer and its software have contributed significantly to the industry-wide productivity, but computer professionals have done a poor job of using the computer to do their job. Engineering disciplines and methodologies are now emerging supported by software tools that address the problems of software development. This paper addresses some of the current software engineering methodologies as a backdrop for the general evaluation of computer assisted software engineering (CASE) tools from actual installation of and experimentation with some specific tools.

Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Kistler, David; Bristow, John; Smith, Don

1994-01-01

This document is an annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. Nearly 200 publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials have been grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. This document contains an index of these publications classified by individual author.

Software Engineering Improvement Activities/Plan

NASA Technical Reports Server (NTRS)

2003-01-01

bd Systems personnel accomplished the technical responsibilities for this reporting period, as planned. A close working relationship was maintained with personnel of the MSFC Avionics Department Software Group (ED14). Work accomplishments included development, evaluation, and enhancement of a software cost model, performing literature search and evaluation of software tools available for code analysis and requirements analysis, and participating in other relevant software engineering activities. Monthly reports were submitted. This support was provided to the Flight Software Group/ED 1 4 in accomplishing the software engineering improvement engineering activities of the Marshall Space Flight Center (MSFC) Software Engineering Improvement Plan.

Ensuring Agile Power to the Edge Approach in Cyberspace

DTIC Science & Technology

2011-06-01

University, , 2. Musical Director, The Nagaokakyo Chamber Ensemble, Kyoto, Japan Former Professor, Roosevelt University Chicago College of...Performing Arts The Music Conservatory 3. Professor Emeritus, Department of Electrical Engineering & Computer Science University of California...of musical ensemble without conductor. Second, we discuss to evaluate the feasibility on the Network Centric Warfare / Power to the Edge approach

Engineering bioinformatics: building reliability, performance and productivity into bioinformatics software.

PubMed

Lawlor, Brendan; Walsh, Paul

2015-01-01

There is a lack of software engineering skills in bioinformatic contexts. We discuss the consequences of this lack, examine existing explanations and remedies to the problem, point out their shortcomings, and propose alternatives. Previous analyses of the problem have tended to treat the use of software in scientific contexts as categorically different from the general application of software engineering in commercial settings. In contrast, we describe bioinformatic software engineering as a specialization of general software engineering, and examine how it should be practiced. Specifically, we highlight the difference between programming and software engineering, list elements of the latter and present the results of a survey of bioinformatic practitioners which quantifies the extent to which those elements are employed in bioinformatics. We propose that the ideal way to bring engineering values into research projects is to bring engineers themselves. We identify the role of Bioinformatic Engineer and describe how such a role would work within bioinformatic research teams. We conclude by recommending an educational emphasis on cross-training software engineers into life sciences, and propose research on Domain Specific Languages to facilitate collaboration between engineers and bioinformaticians.

Engineering bioinformatics: building reliability, performance and productivity into bioinformatics software

PubMed Central

Lawlor, Brendan; Walsh, Paul

2015-01-01

There is a lack of software engineering skills in bioinformatic contexts. We discuss the consequences of this lack, examine existing explanations and remedies to the problem, point out their shortcomings, and propose alternatives. Previous analyses of the problem have tended to treat the use of software in scientific contexts as categorically different from the general application of software engineering in commercial settings. In contrast, we describe bioinformatic software engineering as a specialization of general software engineering, and examine how it should be practiced. Specifically, we highlight the difference between programming and software engineering, list elements of the latter and present the results of a survey of bioinformatic practitioners which quantifies the extent to which those elements are employed in bioinformatics. We propose that the ideal way to bring engineering values into research projects is to bring engineers themselves. We identify the role of Bioinformatic Engineer and describe how such a role would work within bioinformatic research teams. We conclude by recommending an educational emphasis on cross-training software engineers into life sciences, and propose research on Domain Specific Languages to facilitate collaboration between engineers and bioinformaticians. PMID:25996054

Software Engineering for Human Spaceflight

NASA Technical Reports Server (NTRS)

Fredrickson, Steven E.

2014-01-01

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

Software engineering from a Langley perspective

NASA Technical Reports Server (NTRS)

Voigt, Susan

1994-01-01

A brief introduction to software engineering is presented. The talk is divided into four sections beginning with the question 'What is software engineering', followed by a brief history of the progression of software engineering at the Langley Research Center in the context of an expanding computing environment. Several basic concepts and terms are introduced, including software development life cycles and maturity levels. Finally, comments are offered on what software engineering means for the Langley Research Center and where to find more information on the subject.

The need for scientific software engineering in the pharmaceutical industry

NASA Astrophysics Data System (ADS)

Luty, Brock; Rose, Peter W.

2017-03-01

Scientific software engineering is a distinct discipline from both computational chemistry project support and research informatics. A scientific software engineer not only has a deep understanding of the science of drug discovery but also the desire, skills and time to apply good software engineering practices. A good team of scientific software engineers can create a software foundation that is maintainable, validated and robust. If done correctly, this foundation enable the organization to investigate new and novel computational ideas with a very high level of efficiency.

The need for scientific software engineering in the pharmaceutical industry.

PubMed

Luty, Brock; Rose, Peter W

2017-03-01

Scientific software engineering is a distinct discipline from both computational chemistry project support and research informatics. A scientific software engineer not only has a deep understanding of the science of drug discovery but also the desire, skills and time to apply good software engineering practices. A good team of scientific software engineers can create a software foundation that is maintainable, validated and robust. If done correctly, this foundation enable the organization to investigate new and novel computational ideas with a very high level of efficiency.

The influence of nontraditional training modalities on physical performance: review of the literature.

PubMed

O'Hara, Reginald B; Serres, Jennifer; Traver, Kyle L; Wright, Bruce; Vojta, Chris; Eveland, Ed

2012-10-01

The primary purpose of this effort was to review several forms of nontraditional (NT) training programs, including heavy lower extremity strength training, CrossFit training, kettlebell training, and agility training, and discuss the effects of these exercise regimens on physical performance. The secondary purpose was to evaluate NT fitness training programs for evidence that they may provide beneficial options to help airmen improve their fitness scores. A search of the literature for 1980-2010 was performed using the Franzello Aeromedical Library, Public Medicine, and Air Force Institute of Technology search engines. There were 50 articles located and the authors selected 29 articles that specifically addressed the primary and secondary purposes of this literature review. This review indicates that an NT training approach is warranted in the general Air Force population. Heavy leg strength training and agility training show promise in enhancing aerobic fitness and improving fitness scores, particularly among members who have difficulty passing a physical fitness test. Most of the nontraditional forms of physical training are not supported in the scientific literature, with the exception of heavy leg strength training and agility training. However, even these NT forms of training require further investigation.

Experimentation in software engineering

NASA Technical Reports Server (NTRS)

Basili, V. R.; Selby, R. W.; Hutchens, D. H.

1986-01-01

Experimentation in software engineering supports the advancement of the field through an iterative learning process. In this paper, a framework for analyzing most of the experimental work performed in software engineering over the past several years is presented. A variety of experiments in the framework is described and their contribution to the software engineering discipline is discussed. Some useful recommendations for the application of the experimental process in software engineering are included.

SAGA: A project to automate the management of software production systems

NASA Technical Reports Server (NTRS)

Campbell, Roy H.; Beckman-Davies, C. S.; Benzinger, L.; Beshers, G.; Laliberte, D.; Render, H.; Sum, R.; Smith, W.; Terwilliger, R.

1986-01-01

Research into software development is required to reduce its production cost and to improve its quality. Modern software systems, such as the embedded software required for NASA's space station initiative, stretch current software engineering techniques. The requirements to build large, reliable, and maintainable software systems increases with time. Much theoretical and practical research is in progress to improve software engineering techniques. One such technique is to build a software system or environment which directly supports the software engineering process, i.e., the SAGA project, comprising the research necessary to design and build a software development which automates the software engineering process. Progress under SAGA is described.

A Study on Aircraft Engine Control Systems for Integrated Flight and Propulsion Control

NASA Astrophysics Data System (ADS)

Yamane, Hideaki; Matsunaga, Yasushi; Kusakawa, Takeshi; Yasui, Hisako

The Integrated Flight and Propulsion Control (IFPC) for a highly maneuverable aircraft and a fighter-class engine with pitch/yaw thrust vectoring is described. Of the two IFPC functions the aircraft maneuver control utilizes the thrust vectoring based on aerodynamic control surfaces/thrust vectoring control allocation specified by the Integrated Control Unit (ICU) of a FADEC (Full Authority Digital Electronic Control) system. On the other hand in the Performance Seeking Control (PSC) the ICU identifies engine's various characteristic changes, optimizes manipulated variables and finally adjusts engine control parameters in cooperation with the Engine Control Unit (ECU). It is shown by hardware-in-the-loop simulation that the thrust vectoring can enhance aircraft maneuverability/agility and that the PSC can improve engine performance parameters such as SFC (specific fuel consumption), thrust and gas temperature.

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

Software development environments: Status and trends

NASA Technical Reports Server (NTRS)

Duffel, Larry E.

1988-01-01

Currently software engineers are the essential integrating factors tying several components together. The components consist of process, methods, computers, tools, support environments, and software engineers. The engineers today empower the tools versus the tools empowering the engineers. Some of the issues in software engineering are quality, managing the software engineering process, and productivity. A strategy to accomplish this is to promote the evolution of software engineering from an ad hoc, labor intensive activity to a managed, technology supported discipline. This strategy may be implemented by putting the process under management control, adopting appropriate methods, inserting the technology that provides automated support for the process and methods, collecting automated tools into an integrated environment and educating the personnel.

Technical Reference Suite Addressing Challenges of Providing Assurance for Fault Management Architectural Design

NASA Technical Reports Server (NTRS)

Fitz, Rhonda; Whitman, Gerek

2016-01-01

Research into complexities of software systems Fault Management (FM) and how architectural design decisions affect safety, preservation of assets, and maintenance of desired system functionality has coalesced into a technical reference (TR) suite that advances the provision of safety and mission assurance. The NASA Independent Verification and Validation (IVV) Program, with Software Assurance Research Program support, extracted FM architectures across the IVV portfolio to evaluate robustness, assess visibility for validation and test, and define software assurance methods applied to the architectures and designs. This investigation spanned IVV projects with seven different primary developers, a wide range of sizes and complexities, and encompassed Deep Space Robotic, Human Spaceflight, and Earth Orbiter mission FM architectures. The initiative continues with an expansion of the TR suite to include Launch Vehicles, adding the benefit of investigating differences intrinsic to model-based FM architectures and insight into complexities of FM within an Agile software development environment, in order to improve awareness of how nontraditional processes affect FM architectural design and system health management.

Proceedings of Tenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1985-01-01

Papers are presented on the following topics: measurement of software technology, recent studies of the Software Engineering Lab, software management tools, expert systems, error seeding as a program validation technique, software quality assurance, software engineering environments (including knowledge-based environments), the Distributed Computing Design System, and various Ada experiments.

Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Buhler, Melanie; Valett, Jon

1989-01-01

An annotated bibliography is presented of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory. The bibliography was updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials were grouped into eight general subject areas for easy reference: (1) The Software Engineering Laboratory; (2) The Software Engineering Laboratory: Software Development Documents; (3) Software Tools; (4) Software Models; (5) Software Measurement; (6) Technology Evaluations; (7) Ada Technology; and (8) Data Collection. Subject and author indexes further classify these documents by specific topic and individual author.

In the soft-to-hard technical spectrum: Where is software engineering?

NASA Technical Reports Server (NTRS)

Leibfried, Theodore F.; Macdonald, Robert B.

1992-01-01

In the computer journals and tabloids, there have been a plethora of articles written about the software engineering field. But while advocates of the need for an engineering approach to software development, it is impressive how many authors have treated the subject of software engineering without adequately addressing the fundamentals of what engineering as a discipline consists of. A discussion is presented of the various related facets of this issue in a logical framework to advance the thesis that the software development process is necessarily an engineering process. The purpose is to examine more of the details of the issue of whether or not the design and development of software for digital computer processing systems should be both viewed and treated as a legitimate field of professional engineering. Also, the type of academic and professional level education programs that would be required to support a software engineering discipline is examined.

Software Engineering Education Directory

DTIC Science & Technology

1990-04-01

and Engineering (CMSC 735) Codes: GPEV2 * Textiooks: IEEE Tutoria on Models and Metrics for Software Management and Engameeing by Basi, Victor R...Software Engineering (Comp 227) Codes: GPRY5 Textbooks: IEEE Tutoria on Software Design Techniques by Freeman, Peter and Wasserman, Anthony 1. Software

The research and practice of spacecraft software engineering

NASA Astrophysics Data System (ADS)

Chen, Chengxin; Wang, Jinghua; Xu, Xiaoguang

2017-06-01

In order to ensure the safety and reliability of spacecraft software products, it is necessary to execute engineering management. Firstly, the paper introduces the problems of unsystematic planning, uncertain classified management and uncontinuous improved mechanism in domestic and foreign spacecraft software engineering management. Then, it proposes a solution for software engineering management based on system-integrated ideology in the perspective of spacecraft system. Finally, a application result of spacecraft is given as an example. The research can provides a reference for executing spacecraft software engineering management and improving software product quality.

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.

Data systems and computer science: Software Engineering Program

NASA Technical Reports Server (NTRS)

Zygielbaum, Arthur I.

1991-01-01

An external review of the Integrated Technology Plan for the Civil Space Program is presented. This review is specifically concerned with the Software Engineering Program. The goals of the Software Engineering Program are as follows: (1) improve NASA's ability to manage development, operation, and maintenance of complex software systems; (2) decrease NASA's cost and risk in engineering complex software systems; and (3) provide technology to assure safety and reliability of software in mission critical applications.

Modeling software systems by domains

NASA Technical Reports Server (NTRS)

Dippolito, Richard; Lee, Kenneth

1992-01-01

The Software Architectures Engineering (SAE) Project at the Software Engineering Institute (SEI) has developed engineering modeling techniques that both reduce the complexity of software for domain-specific computer systems and result in systems that are easier to build and maintain. These techniques allow maximum freedom for system developers to apply their domain expertise to software. We have applied these techniques to several types of applications, including training simulators operating in real time, engineering simulators operating in non-real time, and real-time embedded computer systems. Our modeling techniques result in software that mirrors both the complexity of the application and the domain knowledge requirements. We submit that the proper measure of software complexity reflects neither the number of software component units nor the code count, but the locus of and amount of domain knowledge. As a result of using these techniques, domain knowledge is isolated by fields of engineering expertise and removed from the concern of the software engineer. In this paper, we will describe kinds of domain expertise, describe engineering by domains, and provide relevant examples of software developed for simulator applications using the techniques.

Modular Rocket Engine Control Software (MRECS)

NASA Technical Reports Server (NTRS)

Tarrant, C.; Crook, J.

1998-01-01

The Modular Rocket Engine Control Software (MRECS) Program is a technology demonstration effort designed to advance the state-of-the-art in launch vehicle propulsion systems. Its emphasis is on developing and demonstrating a modular software architecture for advanced engine control systems that will result in lower software maintenance (operations) costs. It effectively accommodates software requirement changes that occur due to hardware technology upgrades and engine development testing. Ground rules directed by MSFC were to optimize modularity and implement the software in the Ada programming language. MRECS system software and the software development environment utilize Commercial-Off-the-Shelf (COTS) products. This paper presents the objectives, benefits, and status of the program. The software architecture, design, and development environment are described. MRECS tasks are defined and timing relationships given. Major accomplishments are listed. MRECS offers benefits to a wide variety of advanced technology programs in the areas of modular software architecture, reuse software, and reduced software reverification time related to software changes. MRECS was recently modified to support a Space Shuttle Main Engine (SSME) hot-fire test. Cold Flow and Flight Readiness Testing were completed before the test was cancelled. Currently, the program is focused on supporting NASA MSFC in accomplishing development testing of the Fastrac Engine, part of NASA's Low Cost Technologies (LCT) Program. MRECS will be used for all engine development testing.

Software-defined optical network for metro-scale geographically distributed data centers.

PubMed

Samadi, Payman; Wen, Ke; Xu, Junjie; Bergman, Keren

2016-05-30

The emergence of cloud computing and big data has rapidly increased the deployment of small and mid-sized data centers. Enterprises and cloud providers require an agile network among these data centers to empower application reliability and flexible scalability. We present a software-defined inter data center network to enable on-demand scale out of data centers on a metro-scale optical network. The architecture consists of a combined space/wavelength switching platform and a Software-Defined Networking (SDN) control plane equipped with a wavelength and routing assignment module. It enables establishing transparent and bandwidth-selective connections from L2/L3 switches, on-demand. The architecture is evaluated in a testbed consisting of 3 data centers, 5-25 km apart. We successfully demonstrated end-to-end bulk data transfer and Virtual Machine (VM) migrations across data centers with less than 100 ms connection setup time and close to full link capacity utilization.

Biological Inspiration for Agile Autonomous Air Vehicles

DTIC Science & Technology

2007-11-01

rhythmically contract the thorax; the hind wings have become specialized as small body rotation sensors (halteres). Butterflies and moths have two pairs of...orthogonal pairs of power muscles that produce alternating dorso-ventral and longitudinal flexure of the thorax from rhythmic contractions similar to...other physical sciences lend themselves to somewhat reductionist approaches for both analysis and synthesis. Complex engineered systems are built from

Becoming Artifacts Medieval Seals, Passports and the Future of Digital Identity

ERIC Educational Resources Information Center

Chango, Mawaki

2012-01-01

What does a digital identity token have to do with medieval seals? Is the history of passports of any use for enabling the discovery of Internet users' identity when crossing virtual domain boundaries during their digital browsing and transactions? The agility of the Internet architecture and its simplicity of use have been the engines of its…

Software Engineering Frameworks: Textbooks vs. Student Perceptions

ERIC Educational Resources Information Center

McMaster, Kirby; Hadfield, Steven; Wolthuis, Stuart; Sambasivam, Samuel

2012-01-01

This research examines the frameworks used by Computer Science and Information Systems students at the conclusion of their first semester of study of Software Engineering. A questionnaire listing 64 Software Engineering concepts was given to students upon completion of their first Software Engineering course. This survey was given to samples of…

Intertwining Risk Insights and Design Decisions

NASA Technical Reports Server (NTRS)

Cornford, Steven L.; Feather, Martin S.; Jenkins, J. Steven

2006-01-01

The state of systems engineering is such that a form of early and continued use of risk assessments is conducted (as evidenced by NASA's adoption and use of the 'Continuous Risk Management' paradigm developed by SEI). ... However, these practices fall short of theideal: (1) Integration between risk assessment techniques and other systems engineering tools is weak. (2) Risk assessment techniques and the insights they yield are only informally coupled to design decisions. (3) Individual riskassessment techniques lack the mix of breadth, fidelity and agility required to span the gamut of the design space. In this paper we present an approach that addresses these shortcomings. The hallmark of our approach is a simple representation comprising objectives (what the system is to do), risks (whose occurrence would detract from attainment of objectives) and activities (a.k.a. 'mitigations') that, if performed, will decrease those risks. These are linked to indicate by how much a risk would detract from attainment of an objective, and by how much an activity would reduce a risk. The simplicity of our representational framework gives it the breadth to encompass the gamut of the design space concerns, the agility to be utilized in even the earliest phases of designs, and the capability to connect to system engineering models and higher-fidelity risk tools. It is through this integration that we address the shortcomings listed above, and so achieve the intertwining between risk insights and design decisions needed to guide systems engineering towards superior final designs while avoiding costly rework to achieve them. The paper will use an example, constructed to be representative of space mission design, to illustrate our approach.

Performing Verification and Validation in Reuse-Based Software Engineering

NASA Technical Reports Server (NTRS)

Addy, Edward A.

1999-01-01

The implementation of reuse-based software engineering not only introduces new activities to the software development process, such as domain analysis and domain modeling, it also impacts other aspects of software engineering. Other areas of software engineering that are affected include Configuration Management, Testing, Quality Control, and Verification and Validation (V&V). Activities in each of these areas must be adapted to address the entire domain or product line rather than a specific application system. This paper discusses changes and enhancements to the V&V process, in order to adapt V&V to reuse-based software engineering.

The LSST Scheduler from design to construction

NASA Astrophysics Data System (ADS)

Delgado, Francisco; Reuter, Michael A.

2016-07-01

The Large Synoptic Survey Telescope (LSST) will be a highly robotic facility, demanding a very high efficiency during its operation. To achieve this, the LSST Scheduler has been envisioned as an autonomous software component of the Observatory Control System (OCS), that selects the sequence of targets in real time. The Scheduler will drive the survey using optimization of a dynamic cost function of more than 200 parameters. Multiple science programs produce thousands of candidate targets for each observation, and multiple telemetry measurements are received to evaluate the external and the internal conditions of the observatory. The design of the LSST Scheduler started early in the project supported by Model Based Systems Engineering, detailed prototyping and scientific validation of the survey capabilities required. In order to build such a critical component, an agile development path in incremental releases is presented, integrated to the development plan of the Operations Simulator (OpSim) to allow constant testing, integration and validation in a simulated OCS environment. The final product is a Scheduler that is also capable of running 2000 times faster than real time in simulation mode for survey studies and scientific validation during commissioning and operations.

The Many Faces of a Software Engineer in a Research Community

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

Marinovici, Maria C.; Kirkham, Harold

2013-10-14

The ability to gather, analyze and make decisions based on real world data is changing nearly every field of human endeavor. These changes are particularly challenging for software engineers working in a scientific community, designing and developing large, complex systems. To avoid the creation of a communications gap (almost a language barrier), the software engineers should possess an ‘adaptive’ skill. In the science and engineering research community, the software engineers must be responsible for more than creating mechanisms for storing and analyzing data. They must also develop a fundamental scientific and engineering understanding of the data. This paper looks atmore » the many faces that a software engineer should have: developer, domain expert, business analyst, security expert, project manager, tester, user experience professional, etc. Observations made during work on a power-systems scientific software development are analyzed and extended to describe more generic software development projects.« less

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.

Conceptual Design of Targeted Scrum: Applying Mission Command to Agile Software Development

DTIC Science & Technology

2014-06-01

on design. Drury et al. (2012) report that many of the decisions made during Scrum planning were more tactical in nature (i.e., which tasks to...Coram, R. (2002). Boyd: The fighter pilot who changed the art of war. Boston, MA: Little, Brown and Company. Drury , M., Conboy, K., & Power, K. (2012...responsiveness (Hochmüller, 2011) (Hoda et al., 2010) • Lack of design focus → Planning decisions more tactical than strategic ( Drury et al., 2012

Collected software engineering papers, volume 2

NASA Technical Reports Server (NTRS)

1983-01-01

Topics addressed include: summaries of the software engineering laboratory (SEL) organization, operation, and research activities; results of specific research projects in the areas of resource models and software measures; and strategies for data collection for software engineering research.

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.

Proceedings of the Eighth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1983-01-01

The four major topics of discussion included: the NASA Software Engineering Laboratory, software testing, human factors in software engineering and software quality assessment. As in the past years, there were 12 position papers presented (3 for each topic) followed by questions and very heavy participation by the general audience.

Use of Soft Computing Technologies For Rocket Engine Control

NASA Technical Reports Server (NTRS)

Trevino, Luis C.; Olcmen, Semih; Polites, Michael

2003-01-01

The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to further improve overall engine system reliability and performance. Specifically, this will be presented by enhancing rocket engine control and engine health management (EHM) using SCT coupled with conventional control technologies, and sound software engineering practices used in Marshall s Flight Software Group. The principle goals are to improve software management, software development time and maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control and EHM methodologies, but to provide alternative design choices for control, EHM, implementation, performance, and sustaining engineering. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion, software engineering for embedded systems, and soft computing technologies (i.e., neural networks, fuzzy logic, and Bayesian belief networks), much of which is presented in this paper. The first targeted demonstration rocket engine platform is the MC-1 (formerly FASTRAC Engine) which is simulated with hardware and software in the Marshall Avionics & Software Testbed laboratory that

A Bibliography of Externally Published Works by the SEI Engineering Techniques Program

DTIC Science & Technology

1992-08-01

media, and virtual reality * model- based engineering * programming languages * reuse * software architectures * software engineering as a discipline...Knowledge- Based Engineering Environments." IEEE Expert 3, 2 (May 1988): 18-23, 26-32. Audience: Practitioner [Klein89b] Klein, D.V. "Comparison of...Terms with Software Reuse Terminology: A Model- Based Approach." ACM SIGSOFT Software Engineering Notes 16, 2 (April 1991): 45-51. Audience: Practitioner

A report on NASA software engineering and Ada training requirements

NASA Technical Reports Server (NTRS)

Legrand, Sue; Freedman, Glenn B.; Svabek, L.

1987-01-01

NASA's software engineering and Ada skill base are assessed and information that may result in new models for software engineering, Ada training plans, and curricula are provided. A quantitative assessment which reflects the requirements for software engineering and Ada training across NASA is provided. A recommended implementation plan including a suggested curriculum with associated duration per course and suggested means of delivery is also provided. The distinction between education and training is made. Although it was directed to focus on NASA's need for the latter, the key relationships to software engineering education are also identified. A rationale and strategy for implementing a life cycle education and training program are detailed in support of improved software engineering practices and the transition to Ada.

Scaling Agile Methods for Department of Defense Programs

DTIC Science & Technology

2016-12-01

concepts that drive the design of scaling frameworks, the contextual drivers that shape implementation, and widely known frameworks available today...Barlow probably governs some of the design choices you make. Barlow’s formula helps us understand the relationship between the outside diameter of a...encouraged to cross-train engineering staff and move away from a team structure where people focus on only one specialty, such as design

The Perfect Process Storm: Integration of CMMI, Agile, and Lean Six Sigma

DTIC Science & Technology

2012-12-01

struggled over the past few decades with a blizzard of process improvement methodologies such as Total Quality Manage- ment (TQM), Kaizen , JIT...the Japanese Kaizen system, targeting quality, effort, employee involvement, willingness to change, communication, and elimina- tion of waste in...blizzard of process improvement methodologies such as Total Quality Management (TQM), Kaizen , JIT Production, and Re-Engineering. These operations are

Integrating Agile Combat Support within Title 10 Wargames

DTIC Science & Technology

2015-03-26

STAT C7 PCT TIME WAITING TO FLY D1 MANHOURS AVAILABLE D20 NMCM INDICATOR C8 ...Technology Graduate School of Engineering and Management (AFIT/ENS) 2950 Hobson Way, Building 640 WPAFB OH 45433-8865 8. PERFORMING ORGANIZATION...Branch Air Force Material Command Wright Patterson AFB, OH Email: omar.mendoza@us.af.mil 10. SPONSOR/MONITOR’S ACRONYM(S) AFMC/A4 11

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.

V&V Within Reuse-Based Software Engineering

NASA Technical Reports Server (NTRS)

Addy, Edward A.

1996-01-01

Verification and Validation (V&V) is used to increase the level of assurance of critical software, particularly that of safety-critical and mission-critical software. V&V is a systems engineering discipline that evaluates the software in a systems context, and is currently applied during the development of a specific application system. In order to bring the effectiveness of V&V to bear within reuse-based software engineering, V&V must be incorporated within the domain engineering process.

Professional Ethics of Software Engineers: An Ethical Framework.

PubMed

Lurie, Yotam; Mark, Shlomo

2016-04-01

The purpose of this article is to propose an ethical framework for software engineers that connects software developers' ethical responsibilities directly to their professional standards. The implementation of such an ethical framework can overcome the traditional dichotomy between professional skills and ethical skills, which plagues the engineering professions, by proposing an approach to the fundamental tasks of the practitioner, i.e., software development, in which the professional standards are intrinsically connected to the ethical responsibilities. In so doing, the ethical framework improves the practitioner's professionalism and ethics. We call this approach Ethical-Driven Software Development (EDSD), as an approach to software development. EDSD manifests the advantages of an ethical framework as an alternative to the all too familiar approach in professional ethics that advocates "stand-alone codes of ethics". We believe that one outcome of this synergy between professional and ethical skills is simply better engineers. Moreover, since there are often different software solutions, which the engineer can provide to an issue at stake, the ethical framework provides a guiding principle, within the process of software development, that helps the engineer evaluate the advantages and disadvantages of different software solutions. It does not and cannot affect the end-product in and of-itself. However, it can and should, make the software engineer more conscious and aware of the ethical ramifications of certain engineering decisions within the process.

Engineering Complex Embedded Systems with State Analysis and the Mission Data System

NASA Technical Reports Server (NTRS)

Ingham, Michel D.; Rasmussen, Robert D.; Bennett, Matthew B.; Moncada, Alex C.

2004-01-01

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer s intent, potentially leading to software errors. This problem is addressed by a systems engineering methodology called State Analysis, which provides a process for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using State Analysis and how these requirements inform the design of the system software, using representative spacecraft examples.

Research on Visualization Design Method in the Field of New Media Software Engineering

NASA Astrophysics Data System (ADS)

Deqiang, Hu

2018-03-01

In the new period of increasingly developed science and technology, with the increasingly fierce competition in the market and the increasing demand of the masses, new design and application methods have emerged in the field of new media software engineering, that is, the visualization design method. Applying the visualization design method to the field of new media software engineering can not only improve the actual operation efficiency of new media software engineering but more importantly the quality of software development can be enhanced by means of certain media of communication and transformation; on this basis, the progress and development of new media software engineering in China are also continuously promoted. Therefore, the application of visualization design method in the field of new media software engineering is analysed concretely in this article from the perspective of the overview of visualization design methods and on the basis of systematic analysis of the basic technology.

State analysis requirements database for engineering complex embedded systems

NASA Technical Reports Server (NTRS)

Bennett, Matthew B.; Rasmussen, Robert D.; Ingham, Michel D.

2004-01-01

It has become clear that spacecraft system complexity is reaching a threshold where customary methods of control are no longer affordable or sufficiently reliable. At the heart of this problem are the conventional approaches to systems and software engineering based on subsystem-level functional decomposition, which fail to scale in the tangled web of interactions typically encountered in complex spacecraft designs. Furthermore, there is a fundamental gap between the requirements on software specified by systems engineers and the implementation of these requirements by software engineers. Software engineers must perform the translation of requirements into software code, hoping to accurately capture the systems engineer's understanding of the system behavior, which is not always explicitly specified. This gap opens up the possibility for misinterpretation of the systems engineer's intent, potentially leading to software errors. This problem is addressed by a systems engineering tool called the State Analysis Database, which provides a tool for capturing system and software requirements in the form of explicit models. This paper describes how requirements for complex aerospace systems can be developed using the State Analysis Database.

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.

X-36 Tailless Fighter Agility Research Aircraft in flight

NASA Technical Reports Server (NTRS)

1997-01-01

The X-36 technology demonstrator shows off its distinctive shape as the remotely piloted aircraft flies a research mission over the Southern California desert on October 30, 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Taking off during First Flight

NASA Technical Reports Server (NTRS)

1997-01-01

The remotely-piloted X-36 Tailless Fighter Agility Research Aircraft lifts off from Rogers Dry Lake at the Dryden Flight Research Center on its first flight on May 17, 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Tailless Fighter Agility Research Aircraft in flight

NASA Technical Reports Server (NTRS)

1997-01-01

The tailless X-36 technology demonstrator research aircraft cruises over the California desert at low altitude during a 1997 research flight. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

The TAME Project: Towards improvement-oriented software environments

NASA Technical Reports Server (NTRS)

Basili, Victor R.; Rombach, H. Dieter

1988-01-01

Experience from a dozen years of analyzing software engineering processes and products is summarized as a set of software engineering and measurement principles that argue for software engineering process models that integrate sound planning and analysis into the construction process. In the TAME (Tailoring A Measurement Environment) project at the University of Maryland, such an improvement-oriented software engineering process model was developed that uses the goal/question/metric paradigm to integrate the constructive and analytic aspects of software development. The model provides a mechanism for formalizing the characterization and planning tasks, controlling and improving projects based on quantitative analysis, learning in a deeper and more systematic way about the software process and product, and feeding the appropriate experience back into the current and future projects. The TAME system is an instantiation of the TAME software engineering process model as an ISEE (integrated software engineering environment). The first in a series of TAME system prototypes has been developed. An assessment of experience with this first limited prototype is presented including a reassessment of its initial architecture.

An integrated radar model solution for mission level performance and cost trades

NASA Astrophysics Data System (ADS)

Hodge, John; Duncan, Kerron; Zimmerman, Madeline; Drupp, Rob; Manno, Mike; Barrett, Donald; Smith, Amelia

2017-05-01

A fully integrated Mission-Level Radar model is in development as part of a multi-year effort under the Northrop Grumman Mission Systems (NGMS) sector's Model Based Engineering (MBE) initiative to digitally interconnect and unify previously separate performance and cost models. In 2016, an NGMS internal research and development (IR and D) funded multidisciplinary team integrated radio frequency (RF), power, control, size, weight, thermal, and cost models together using a commercial-off-the-shelf software, ModelCenter, for an Active Electronically Scanned Array (AESA) radar system. Each represented model was digitally connected with standard interfaces and unified to allow end-to-end mission system optimization and trade studies. The radar model was then linked to the Air Force's own mission modeling framework (AFSIM). The team first had to identify the necessary models, and with the aid of subject matter experts (SMEs) understand and document the inputs, outputs, and behaviors of the component models. This agile development process and collaboration enabled rapid integration of disparate models and the validation of their combined system performance. This MBE framework will allow NGMS to design systems more efficiently and affordably, optimize architectures, and provide increased value to the customer. The model integrates detailed component models that validate cost and performance at the physics level with high-level models that provide visualization of a platform mission. This connectivity of component to mission models allows hardware and software design solutions to be better optimized to meet mission needs, creating cost-optimal solutions for the customer, while reducing design cycle time through risk mitigation and early validation of design decisions.

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.

Impacts of Technological Changes in the Cyber Environment on Software/Systems Engineering Workforce Development

DTIC Science & Technology

2010-04-01

for decoupled parallel development Ref: Barry Boehm 12 Impacts of Technological Changes in the Cyber Environment on Software/Systems Engineering... Pressman , R.S., Software Engineering: A Practitioner’s Approach, 13 Impacts of Technological Changes in the Cyber Environment on Software/Systems

ENGINES: exploring single nucleotide variation in entire human genomes.

PubMed

Amigo, Jorge; Salas, Antonio; Phillips, Christopher

2011-04-19

Next generation ultra-sequencing technologies are starting to produce extensive quantities of data from entire human genome or exome sequences, and therefore new software is needed to present and analyse this vast amount of information. The 1000 Genomes project has recently released raw data for 629 complete genomes representing several human populations through their Phase I interim analysis and, although there are certain public tools available that allow exploration of these genomes, to date there is no tool that permits comprehensive population analysis of the variation catalogued by such data. We have developed a genetic variant site explorer able to retrieve data for Single Nucleotide Variation (SNVs), population by population, from entire genomes without compromising future scalability and agility. ENGINES (ENtire Genome INterface for Exploring SNVs) uses data from the 1000 Genomes Phase I to demonstrate its capacity to handle large amounts of genetic variation (>7.3 billion genotypes and 28 million SNVs), as well as deriving summary statistics of interest for medical and population genetics applications. The whole dataset is pre-processed and summarized into a data mart accessible through a web interface. The query system allows the combination and comparison of each available population sample, while searching by rs-number list, chromosome region, or genes of interest. Frequency and FST filters are available to further refine queries, while results can be visually compared with other large-scale Single Nucleotide Polymorphism (SNP) repositories such as HapMap or Perlegen. ENGINES is capable of accessing large-scale variation data repositories in a fast and comprehensive manner. It allows quick browsing of whole genome variation, while providing statistical information for each variant site such as allele frequency, heterozygosity or FST values for genetic differentiation. Access to the data mart generating scripts and to the web interface is granted from http://spsmart.cesga.es/engines.php. © 2011 Amigo et al; licensee BioMed Central Ltd.

Software And Systems Engineering Risk Management

DTIC Science & Technology

2010-04-01

RSKM 2004 COSO Enterprise RSKM Framework 2006 ISO/IEC 16085 Risk Management Process 2008 ISO/IEC 12207 Software Lifecycle Processes 2009 ISO/IEC...1 Software And Systems Engineering Risk Management John Walz VP Technical and Conferences Activities, IEEE Computer Society Vice-Chair Planning...Software & Systems Engineering Standards Committee, IEEE Computer Society US TAG to ISO TMB Risk Management Working Group Systems and Software

Proceedings of the 19th Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1994-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by NASA/GSFC and created to investigate the effectiveness of software engineering technologies when applied to the development of applications software. The goals of the SEL are: (1) to understand the software development process in the GSFC environment; (2) to measure the effects of various methodologies, tools, and models on this process; and (3) to identify and then to apply successful development practices. The activities, findings, and recommendations of the SEL are recorded in the Software Engineering Laboratory Series, a continuing series of reports that include this document.

Data collection procedures for the Software Engineering Laboratory (SEL) database

NASA Technical Reports Server (NTRS)

Heller, Gerard; Valett, Jon; Wild, Mary

1992-01-01

This document is a guidebook to collecting software engineering data on software development and maintenance efforts, as practiced in the Software Engineering Laboratory (SEL). It supersedes the document entitled Data Collection Procedures for the Rehosted SEL Database, number SEL-87-008 in the SEL series, which was published in October 1987. It presents procedures to be followed on software development and maintenance projects in the Flight Dynamics Division (FDD) of Goddard Space Flight Center (GSFC) for collecting data in support of SEL software engineering research activities. These procedures include detailed instructions for the completion and submission of SEL data collection forms.

Annotated bibliography of Software Engineering Laboratory literature

NASA Technical Reports Server (NTRS)

1985-01-01

An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is presented. More than 100 publications are summarized. These publications are summarized. These publications cover many areas of software engineering and range from research reports to software documentation. This document has been updated and reorganized substantially since the original version (SEL-82-006, November 1982). All materials are grouped into five general subject areas for easy reference: (1) the software engineering laboratory; (2) software tools; (3) models and measures; (4) technology evaluations; and (5) data collection. An index further classifies these documents by specific topic.

Modular Rocket Engine Control Software (MRECS)

NASA Technical Reports Server (NTRS)

Tarrant, Charlie; Crook, Jerry

1997-01-01

The Modular Rocket Engine Control Software (MRECS) Program is a technology demonstration effort designed to advance the state-of-the-art in launch vehicle propulsion systems. Its emphasis is on developing and demonstrating a modular software architecture for a generic, advanced engine control system that will result in lower software maintenance (operations) costs. It effectively accommodates software requirements changes that occur due to hardware. technology upgrades and engine development testing. Ground rules directed by MSFC were to optimize modularity and implement the software in the Ada programming language. MRECS system software and the software development environment utilize Commercial-Off-the-Shelf (COTS) products. This paper presents the objectives and benefits of the program. The software architecture, design, and development environment are described. MRECS tasks are defined and timing relationships given. Major accomplishment are listed. MRECS offers benefits to a wide variety of advanced technology programs in the areas of modular software, architecture, reuse software, and reduced software reverification time related to software changes. Currently, the program is focused on supporting MSFC in accomplishing a Space Shuttle Main Engine (SSME) hot-fire test at Stennis Space Center and the Low Cost Boost Technology (LCBT) Program.

Software Engineering Improvement Plan

NASA Technical Reports Server (NTRS)

2006-01-01

In performance of this task order, bd Systems personnel provided support to the Flight Software Branch and the Software Working Group through multiple tasks related to software engineering improvement and to activities of the independent Technical Authority (iTA) Discipline Technical Warrant Holder (DTWH) for software engineering. To ensure that the products, comments, and recommendations complied with customer requirements and the statement of work, bd Systems personnel maintained close coordination with the customer. These personnel performed work in areas such as update of agency requirements and directives database, software effort estimation, software problem reports, a web-based process asset library, miscellaneous documentation review, software system requirements, issue tracking software survey, systems engineering NPR, and project-related reviews. This report contains a summary of the work performed and the accomplishments in each of these areas.

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.

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.

Software engineering as an engineering discipline

NASA Technical Reports Server (NTRS)

Freedman, Glenn B.

1988-01-01

The purpose of this panel is to explore the emerging field of software engineering from a variety of perspectives: university programs; industry training and definition; government development; and technology transfer. In doing this, the panel will address the issues of distinctions among software engineering, computer science, and computer hardware engineering as they relate to the challenges of large, complex 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 digital tools. PMID:24647098

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 includes discussion of a hybrid architecture that combines a traditional relational database, schema-less database, advanced free text search, and the preliminary framework for Semantic Web support. The current version of the SIZONet web application is discussed in relation to the high-value features defined as part of the Agile approach. Preliminary feedback indicates a system that meets the needs of multiple user groups.

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 through the portal. The resulting product has an interface that is more intuitive and presents the highest priority datasets that are needed by the users. Our agile approach has enabled us to build a system that is keeping pace with the science needs while utilizing limited resources.

Applying formal methods and object-oriented analysis to existing flight software

NASA Technical Reports Server (NTRS)

Cheng, Betty H. C.; Auernheimer, Brent

1993-01-01

Correctness is paramount for safety-critical software control systems. Critical software failures in medical radiation treatment, communications, and defense are familiar to the public. The significant quantity of software malfunctions regularly reported to the software engineering community, the laws concerning liability, and a recent NRC Aeronautics and Space Engineering Board report additionally motivate the use of error-reducing and defect detection software development techniques. The benefits of formal methods in requirements driven software development ('forward engineering') is well documented. One advantage of rigorously engineering software is that formal notations are precise, verifiable, and facilitate automated processing. This paper describes the application of formal methods to reverse engineering, where formal specifications are developed for a portion of the shuttle on-orbit digital autopilot (DAP). Three objectives of the project were to: demonstrate the use of formal methods on a shuttle application, facilitate the incorporation and validation of new requirements for the system, and verify the safety-critical properties to be exhibited by the software.

Proceedings of the Annual Ada Software Engineering Education and Training Symposium (3rd) Held in Denver, Colorado on June 14-16, 1988

DTIC Science & Technology

1988-06-01

Based Software Engineering Project Course .............. 83 SSoftware Engineering, Software Engineering Concepts: The Importance of Object-Based...quality assurance, and independent system testing . The Chief Programmer is responsible for all software development activities, including prototyping...during the Requirements Analysis phase, the Preliminary Design, the Detailed Design, Coding and Unit Testing , CSC Integration and Testing , and informal

Proceedings of the Fifteenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1990-01-01

The Software Engineering Laboratory (SEL) is an organization sponsored by GSFC and created for the purpose of investigating the effectiveness of software engineering technologies when applied to the development of applications software. The goals of the SEL are: (1) to understand the software development process in the GSFC environment; (2) to measure the effect of various methodologies, tools, and models on this process; and (3) to identify and then to apply successful development practices. Fifteen papers were presented at the Fifteenth Annual Software Engineering Workshop in five sessions: (1) SEL at age fifteen; (2) process improvement; (3) measurement; (4) reuse; and (5) process assessment. The sessions were followed by two panel discussions: (1) experiences in implementing an effective measurement program; and (2) software engineering in the 1980's. A summary of the presentations and panel discussions is given.

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.

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.

Multidisciplinary and Active/Collaborative Approaches in Teaching Requirements Engineering

ERIC Educational Resources Information Center

Rosca, Daniela

2005-01-01

The requirements engineering course is a core component of the curriculum for the Master's in Software Engineering programme, at Monmouth University (MU). It covers the process, methods and tools specific to this area, together with the corresponding software quality issues. The need to produce software engineers with strong teamwork and…

A Knowledge Engineering Approach to Analysis and Evaluation of Construction Schedules

DTIC Science & Technology

1990-02-01

software engineering discipline focusing on constructing KBSs. It is an incremental and cyclical process that requires the interaction of a domain expert(s...the U.S. Army Coips of Engineers ; and (3) the project management software developer, represented by Pinnell Engineering , Inc. Since the primary...the programming skills necessary to convert the raw knowledge intn a form a computer can understand. knowledge engineering : The software engineering

Questioning the Role of Requirements Engineering in the Causes of Safety-Critical Software Failures

NASA Technical Reports Server (NTRS)

Johnson, C. W.; Holloway, C. M.

2006-01-01

Many software failures stem from inadequate requirements engineering. This view has been supported both by detailed accident investigations and by a number of empirical studies; however, such investigations can be misleading. It is often difficult to distinguish between failures in requirements engineering and problems elsewhere in the software development lifecycle. Further pitfalls arise from the assumption that inadequate requirements engineering is a cause of all software related accidents for which the system fails to meet its requirements. This paper identifies some of the problems that have arisen from an undue focus on the role of requirements engineering in the causes of major accidents. The intention is to provoke further debate within the emerging field of forensic software engineering.

Applying the Kanban Method in Problem-Based Project Work: A Case Study in A Manufacturing Engineering Bachelor's Programme at Aalborg University Copenhagen

ERIC Educational Resources Information Center

Balve, Patrick; Krüger, Volker; Tolstrup Sørensen, Lene

2017-01-01

Problem-based learning (PBL) has proven to be highly effective for educating students in an active and self-motivated manner in various disciplines. Student projects carried out following PBL principles are very dynamic and carry a high level of uncertainty, both conditions under which agile project management approaches are assumed to be highly…

Computer systems and software engineering

NASA Technical Reports Server (NTRS)

Mckay, Charles W.

1988-01-01

The High Technologies Laboratory (HTL) was established in the fall of 1982 at the University of Houston Clear Lake. Research conducted at the High Tech Lab is focused upon computer systems and software engineering. There is a strong emphasis on the interrelationship of these areas of technology and the United States' space program. In Jan. of 1987, NASA Headquarters announced the formation of its first research center dedicated to software engineering. Operated by the High Tech Lab, the Software Engineering Research Center (SERC) was formed at the University of Houston Clear Lake. The High Tech Lab/Software Engineering Research Center promotes cooperative research among government, industry, and academia to advance the edge-of-knowledge and the state-of-the-practice in key topics of computer systems and software engineering which are critical to NASA. The center also recommends appropriate actions, guidelines, standards, and policies to NASA in matters pertinent to the center's research. Results of the research conducted at the High Tech Lab/Software Engineering Research Center have given direction to many decisions made by NASA concerning the Space Station Program.

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 and facilities, minimization of patient throughput time and adequate training programme for safety practices are extremely crucial for enhancing agile capability of a healthcare organization.

Annotated bibliography of Software Engineering Laboratory (SEL) literature

NASA Technical Reports Server (NTRS)

Card, D.

1982-01-01

An annotated bibliography of technical papers, documents, and memorandums produced by or related to the Software Engineering Laboratory is presented. More than 75 publications are summarized. An index of these publications by subject is also included. These publications cover many areas of software engineering and range from research reports to software documentation.

Towards a Controlled Vocabulary on Software Engineering Education

ERIC Educational Resources Information Center

Pizard, Sebastián; Vallespir, Diego

2017-01-01

Software engineering is the discipline that develops all the aspects of the production of software. Although there are guidelines about what topics to include in a software engineering curricula, it is usually unclear which are the best methods to teach them. In any science discipline the construction of a classification schema is a common…

AADL and Model-based Engineering

DTIC Science & Technology

2014-10-20

and MBE Feiler, Oct 20, 2014 © 2014 Carnegie Mellon University We Rely on Software for Safe Aircraft Operation Embedded software systems ...D eveloper Compute Platform Runtime Architecture Application Software Embedded SW System Engineer Data Stream Characteristics Latency...confusion Hardware Engineer Why do system level failures still occur despite fault tolerance techniques being deployed in systems ? Embedded software

Intelligent Agents for Design and Synthesis Environments: My Summary

NASA Technical Reports Server (NTRS)

Norvig, Peter

1999-01-01

This presentation gives a summary of intelligent agents for design synthesis environments. We'll start with the conclusions, and work backwards to justify them. First, an important assumption is that agents (whatever they are) are good for software engineering. This is especially true for software that operates in an uncertain, changing environment. The "real world" of physical artifacts is like that: uncertain in what we can measure, changing in that things are always breaking down, and we must interact with non-software entities. The second point is that software engineering techniques can contribute to good design. There may have been a time when we wanted to build simple artifacts containing little or no software. But modern aircraft and spacecraft are complex, and rely on a great deal of software. So better software engineering leads to better designed artifacts, especially when we are designing a series of related artifacts and can amortize the costs of software development. The third point is that agents are especially useful for design tasks, above and beyond their general usefulness for software engineering, and the usefulness of software engineering to design.

NASA software documentation standard software engineering program

NASA Technical Reports Server (NTRS)

1991-01-01

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Improving Software Engineering on NASA Projects

NASA Technical Reports Server (NTRS)

Crumbley, Tim; Kelly, John C.

2010-01-01

Software Engineering Initiative: Reduces risk of software failure -Increases mission safety. More predictable software cost estimates and delivery schedules. Smarter buyer of contracted out software. More defects found and removed earlier. Reduces duplication of efforts between projects. Increases ability to meet the challenges of evolving software technology.

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.

Automating Software Design Metrics.

DTIC Science & Technology

1984-02-01

INTRODUCTION 1 ", ... 0..1 1.2 HISTORICAL PERSPECTIVE High quality software is of interest to both the software engineering com- munity and its users. As...contributions of many other software engineering efforts, most notably [MCC 77] and [Boe 83b], which have defined and refined a framework for quantifying...AUTOMATION OF DESIGN METRICS Software metrics can be useful within the context of an integrated soft- ware engineering environment. The purpose of this

Use of Soft Computing Technologies for a Qualitative and Reliable Engine Control System for Propulsion Systems

NASA Technical Reports Server (NTRS)

Trevino, Luis; Brown, Terry; Crumbley, R. T. (Technical Monitor)

2001-01-01

The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to improve overall vehicle system safety, reliability, and rocket engine performance by development of a qualitative and reliable engine control system (QRECS). Specifically, this will be addressed by enhancing rocket engine control using SCT, innovative data mining tools, and sound software engineering practices used in Marshall's Flight Software Group (FSG). The principle goals for addressing the issue of quality are to improve software management, software development time, software maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control methodologies, but to provide alternative design choices for control, implementation, performance, and sustaining engineering, all relative to addressing the issue of reliability. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion (system level), software engineering for embedded flight software systems, and soft computing technologies (i.e., neural networks, fuzzy logic, data mining, and Bayesian belief networks); some of which are briefed in this paper. For this effort, the targeted demonstration rocket engine testbed is the MC-1 engine (formerly FASTRAC) which is simulated with hardware and software in the Marshall Avionics & Software Testbed (MAST) laboratory that currently resides at NASA's Marshall Space Flight Center, building 4476, and is managed by the Avionics Department. A brief plan of action for design, development, implementation, and testing a Phase One effort for QRECS is given, along with expected results. Phase One will focus on development of a Smart Start Engine Module and a Mainstage Engine Module for proper engine start and mainstage engine operations. The overall intent is to demonstrate that by employing soft computing technologies, the quality and reliability of the overall scheme to engine controller development is further improved and vehicle safety is further insured. The final product that this paper proposes is an approach to development of an alternative low cost engine controller that would be capable of performing in unique vision spacecraft vehicles requiring low cost advanced avionics architectures for autonomous operations from engine pre-start to engine shutdown.

A Review of the Suitability of Available Computer Aided Software Engineering (CASE) Tools for the Small Software Development Environment

DTIC Science & Technology

1989-07-11

LITERATURE CITED [Boeh73] Boehm, Barry W., "Software and its Impact: A Quantitative Assessment," Datamation, 19, 5, (May 1973), pp 48-59. [Boeh76...Boehm, Barry W., "Software Engineering," IEEE Transactions on Computers, C-25, 12, (December 1976), pp 1226-1241. [Boeh81a] Boehm, Barry W., Software...Engineering Economics, Prentice-Hall, Inc., Englewood Cliffs, NJ, (1981). [Boeh8lb] Boehm, Barry W., "An Experiment in Small Scale Application Software

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.

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. PMID:24688866

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.

Software technology insertion: A study of success factors

NASA Technical Reports Server (NTRS)

Lydon, Tom

1990-01-01

Managing software development in large organizations has become increasingly difficult due to increasing technical complexity, stricter government standards, a shortage of experienced software engineers, competitive pressure for improved productivity and quality, the need to co-develop hardware and software together, and the rapid changes in both hardware and software technology. The 'software factory' approach to software development minimizes risks while maximizing productivity and quality through standardization, automation, and training. However, in practice, this approach is relatively inflexible when adopting new software technologies. The methods that a large multi-project software engineering organization can use to increase the likelihood of successful software technology insertion (STI), especially in a standardized engineering environment, are described.

Defense AT&L Magazine: A Publication of the Defense Acquisition University. Volume 34, Number 3, DAU 184

DTIC Science & Technology

2005-01-01

developed a partnership with the Defense Acquisition University to in- tegrate DISA’s systems engineering processes, software , and network...in place, with processes being implemented: deployment management; systems engineering ; software engineering ; configuration man- agement; test and...CSS systems engineering is a transition partner with Carnegie Mellon University’s Software Engineering Insti- tute and its work on the capability

Application of Nexus copy number software for CNV detection and analysis.

PubMed

Darvishi, Katayoon

2010-04-01

Among human structural genomic variation, copy number variants (CNVs) are the most frequently known component, comprised of gains/losses of DNA segments that are generally 1 kb in length or longer. Array-based comparative genomic hybridization (aCGH) has emerged as a powerful tool for detecting genomic copy number variants (CNVs). With the rapid increase in the density of array technology and with the adaptation of new high-throughput technology, a reliable and computationally scalable method for accurate mapping of recurring DNA copy number aberrations has become a main focus in research. Here we introduce Nexus Copy Number software, a platform-independent tool, to analyze the output files of all types of commercial and custom-made comparative genomic hybridization (CGH) and single-nucleotide polymorphism (SNP) arrays, such as those manufactured by Affymetrix, Agilent Technologies, Illumina, and Roche NimbleGen. It also supports data generated by various array image-analysis software tools such as GenePix, ImaGene, and BlueFuse. (c) 2010 by John Wiley & Sons, Inc.

Shuttle avionics software trials, tribulations and success

NASA Technical Reports Server (NTRS)

Henderson, O. L.

1985-01-01

The early problems and the solutions developed to provide the required quality software needed to support the space shuttle engine development program are described. The decision to use a programmable digital control system on the space shuttle engine was primarily based upon the need for a flexible control system capable of supporting the total engine mission on a large complex pump fed engine. The mission definition included all control phases from ground checkout through post shutdown propellant dumping. The flexibility of the controller through reprogrammable software allowed the system to respond to the technical challenges and innovation required to develop both the engine and controller hardware. This same flexibility, however, placed a severe strain on the capability of the software development and verification organization. The overall development program required that the software facility accommodate significant growth in both the software requirements and the number of software packages delivered. This challenge was met by reorganization and evolution in the process of developing and verifying software.

Autonomous Scheduling Requirements for Agile Cubesat Constellations in Earth Observation

NASA Astrophysics Data System (ADS)

Nag, S.; Li, A. S. X.; Kumar, S.

2017-12-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) with increasing capabilities to host imager payloads. Given the precise attitude control systems emerging commercially, Cubesats now have the ability to slew and capture images within short notice. Prior literature has demonstrated a modular framework that combines orbital mechanics, attitude control and scheduling optimization to plan the time-varying orientation of agile Cubesats in a constellation such that they maximize the number of observed images, within the constraints of hardware specs. Schedule optimization is performed on the ground autonomously, using dynamic programming with two levels of heuristics, verified and improved upon using mixed integer linear programming. Our algorithm-in-the-loop simulation applied to Landsat's use case, captured up to 161% more Landsat images than nadir-pointing sensors with the same field of view, on a 2-satellite constellation over a 12-hour simulation. In this paper, we will derive the requirements for the above algorithm to run onboard small satellites such that the constellation can make time-sensitive decisions to slew and capture images autonomously, without ground support. We will apply the above autonomous algorithm to a time critical use case - monitoring of precipitation and subsequent effects on floods, landslides and soil moisture, as quantified by the NASA Unified Weather Research and Forecasting Model. Since the latency between these event occurrences is quite low, they make a strong case for autonomous decisions among satellites in a constellation. The algorithm can be implemented in the Plan Execution Interchange Language - NASA's open source technology for automation, used to operate the International Space Station and LADEE's in flight software - enabling a controller-in-the-loop demonstration. The autonomy software can then be integrated with NASA's open source Core Flight Software, ported onto a Raspberry Pi 3.0 for a software-in-the-loop demonstration. Future use cases can be time critical events such as cloud movement, storms or other disasters, and in conjunction with other platforms in a Sensor Web.

Shaping Software Engineering Curricula Using Open Source Communities: A Case Study

ERIC Educational Resources Information Center

Bowring, James; Burke, Quinn

2016-01-01

This paper documents four years of a novel approach to teaching a two-course sequence in software engineering as part of the ABET-accredited computer science curriculum at the College of Charleston. This approach is team-based and centers on learning software engineering in the context of open source software projects. In the first course, teams…

Proceedings of the Thirteenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1988-01-01

Topics covered in the workshop included studies and experiments conducted in the Software Engineering Laboratory (SEL), a cooperative effort of NASA Goddard Space Flight Center, the University of Maryland, and Computer Sciences Corporation; software models; software products; and software tools.

Averting Denver Airports on a Chip

NASA Technical Reports Server (NTRS)

Sullivan, Kevin J.

1995-01-01

As a result of recent advances in software engineering capabilities, we are now in a more stable environment. De-facto hardware and software standards are emerging. Work on software architecture and design patterns signals a consensus on the importance of early system-level design decisions, and agreements on the uses of certain paradigmatic software structures. We now routinely build systems that would have been risky or infeasible a few years ago. Unfortunately, technological developments threaten to destabilize software design again. Systems designed around novel computing and peripheral devices will spark ambitious new projects that will stress current software design and engineering capabilities. Micro-electro-mechanical systems (MEMS) and related technologies provide the physical basis for new systems with the potential to produce this kind of destabilizing effect. One important response to anticipated software engineering and design difficulties is carefully directed engineering-scientific research. Two specific problems meriting substantial research attention are: A lack of sufficient means to build software systems by generating, extending, specializing, and integrating large-scale reusable components; and a lack of adequate computational and analytic tools to extend and aid engineers in maintaining intellectual control over complex software designs.

Software Management Metrics

DTIC Science & Technology

1988-05-01

obtained from Dr. Barry Boehm’s Software 5650, Contract No. F19628-86-C-O001, Engineering Economics [1] and from T. J. ESD/MITRE Software Center Acquisition...of References 1. Boehm, Barry W., SoJtware Engineering 3. Halstead, M. H., Elements of SoJhtare Economics, Englewood Cliffs, New Science, New York...1983, pp. 639-648. 35 35 - Bibliography Beizer, B., Software System Testing and Pressman , Roger S., Software Engineering:QualtyO Assurance, New York: Van

SOFTWARE ENGINEERING INSTITUTE (SEI)

EPA Science Inventory

The Software Engineering Institute (SEI) is a federally funded research and development center established in 1984 by the U.S. Department of Defense and operated by Carnegie Mellon University. SEI has a broad charter to provide leadership in the practice of software engineering t...

7 Processes that Enable NASA Software Engineering Technologies: Value-Added Process Engineering

NASA Technical Reports Server (NTRS)

Housch, Helen; Godfrey, Sally

2011-01-01

The presentation reviews Agency process requirements and the purpose, benefits, and experiences or seven software engineering processes. The processes include: product integration, configuration management, verification, software assurance, measurement and analysis, requirements management, and planning and monitoring.

Methodology for automating software systems. Task 1 of the foundations for automating software systems

NASA Technical Reports Server (NTRS)

Moseley, Warren

1989-01-01

The early stages of a research program designed to establish an experimental research platform for software engineering are described. Major emphasis is placed on Computer Assisted Software Engineering (CASE). The Poor Man's CASE Tool is based on the Apple Macintosh system, employing available software including Focal Point II, Hypercard, XRefText, and Macproject. These programs are functional in themselves, but through advanced linking are available for operation from within the tool being developed. The research platform is intended to merge software engineering technology with artificial intelligence (AI). In the first prototype of the PMCT, however, the sections of AI are not included. CASE tools assist the software engineer in planning goals, routes to those goals, and ways to measure progress. The method described allows software to be synthesized instead of being written or built.

IEEE Conference on Software Engineering Education and Training (CSEE&T 2012) Proceedings (25th, Nanjing, Jiangsu, China, April 17-19, 2012)

ERIC Educational Resources Information Center

IEEE Conference on Software Engineering Education and Training, Proceedings (MS), 2012

2012-01-01

The Conference on Software Engineering Education and Training (CSEE&T) is the premier international peer-reviewed conference, sponsored by the Institute of Electrical and Electronics Engineers, Inc. (IEEE) Computer Society, which addresses all major areas related to software engineering education, training, and professionalism. This year, as…

Modelling of diesel engine fuelled with biodiesel using engine simulation software

NASA Astrophysics Data System (ADS)

Said, Mohd Farid Muhamad; Said, Mazlan; Aziz, Azhar Abdul

2012-06-01

This paper is about modelling of a diesel engine that operates using biodiesel fuels. The model is used to simulate or predict the performance and combustion of the engine by simplified the geometry of engine component in the software. The model is produced using one-dimensional (1D) engine simulation software called GT-Power. The fuel properties library in the software is expanded to include palm oil based biodiesel fuels. Experimental works are performed to investigate the effect of biodiesel fuels on the heat release profiles and the engine performance curves. The model is validated with experimental data and good agreement is observed. The simulation results show that combustion characteristics and engine performances differ when biodiesel fuels are used instead of no. 2 diesel fuel.

Milestones in Software Engineering and Knowledge Engineering History: A Comparative Review

PubMed Central

del Águila, Isabel M.; Palma, José; Túnez, Samuel

2014-01-01

We present a review of the historical evolution of software engineering, intertwining it with the history of knowledge engineering because “those who cannot remember the past are condemned to repeat it.” This retrospective represents a further step forward to understanding the current state of both types of engineerings; history has also positive experiences; some of them we would like to remember and to repeat. Two types of engineerings had parallel and divergent evolutions but following a similar pattern. We also define a set of milestones that represent a convergence or divergence of the software development methodologies. These milestones do not appear at the same time in software engineering and knowledge engineering, so lessons learned in one discipline can help in the evolution of the other one. PMID:24624046

Milestones in software engineering and knowledge engineering history: a comparative review.

PubMed

del Águila, Isabel M; Palma, José; Túnez, Samuel

2014-01-01

We present a review of the historical evolution of software engineering, intertwining it with the history of knowledge engineering because "those who cannot remember the past are condemned to repeat it." This retrospective represents a further step forward to understanding the current state of both types of engineerings; history has also positive experiences; some of them we would like to remember and to repeat. Two types of engineerings had parallel and divergent evolutions but following a similar pattern. We also define a set of milestones that represent a convergence or divergence of the software development methodologies. These milestones do not appear at the same time in software engineering and knowledge engineering, so lessons learned in one discipline can help in the evolution of the other one.

A software engineering approach to expert system design and verification

NASA Technical Reports Server (NTRS)

Bochsler, Daniel C.; Goodwin, Mary Ann

1988-01-01

Software engineering design and verification methods for developing expert systems are not yet well defined. Integration of expert system technology into software production environments will require effective software engineering methodologies to support the entire life cycle of expert systems. The software engineering methods used to design and verify an expert system, RENEX, is discussed. RENEX demonstrates autonomous rendezvous and proximity operations, including replanning trajectory events and subsystem fault detection, onboard a space vehicle during flight. The RENEX designers utilized a number of software engineering methodologies to deal with the complex problems inherent in this system. An overview is presented of the methods utilized. Details of the verification process receive special emphasis. The benefits and weaknesses of the methods for supporting the development life cycle of expert systems are evaluated, and recommendations are made based on the overall experiences with the methods.

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.

Consistent Evolution of Software Artifacts and Non-Functional Models

DTIC Science & Technology

2014-11-14

induce bad software performance)? 15. SUBJECT TERMS EOARD, Nano particles, Photo-Acoustic Sensors, Model-Driven Engineering ( MDE ), Software Performance...Università degli Studi dell’Aquila, Via Vetoio, 67100 L’Aquila, Italy Email: vittorio.cortellessa@univaq.it Web : http: // www. di. univaq. it/ cortelle/ Phone...Model-Driven Engineering ( MDE ), Software Performance Engineering (SPE), Change Propagation, Performance Antipatterns. For sake of readability of the

A self-referential HOWTO on release engineering

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

Galassi, Mark C.

Release engineering is a fundamental part of the software development cycle: it is the point at which quality control is exercised and bug fixes are integrated. The way in which software is released also gives the end user her first experience of a software package, while in scientific computing release engineering can guarantee reproducibility. For these reasons and others, the release process is a good indicator of the maturity and organization of a development team. Software teams often do not put in place a release process at the beginning. This is unfortunate because the team does not have early andmore » continuous execution of test suites, and it does not exercise the software in the same conditions as the end users. I describe an approach to release engineering based on the software tools developed and used by the GNU project, together with several specific proposals related to packaging and distribution. I do this in a step-by-step manner, demonstrating how this very paper is written and built using proper release engineering methods. Because many aspects of release engineering are not exercised in the building of the paper, the accompanying software repository also contains examples of software libraries.« less

The Effect of AOP on Software Engineering, with Particular Attention to OIF and Event Quantification

NASA Technical Reports Server (NTRS)

Havelund, Klaus; Filman, Robert; Korsmeyer, David (Technical Monitor)

2003-01-01

We consider the impact of Aspect-Oriented Programming on Software Engineering, and, in particular, analyze two AOP systems, one of which does component wrapping and the other, quantification over events, for their software engineering effects.

Second Generation Product Line Engineering Takes Hold in the DoD

DTIC Science & Technology

2014-01-01

Feature- Oriented Domain Analysis ( FODA ) Feasibility Study” (CMU/SEI-90- TR-021, ADA235785). Pittsburgh, PA: Software Engineering Institute...software product line engineering and software architecture documentation and analysis . Clements is co-author of three practitioner-oriented books about

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 Centers in BBAGILdom (t: 2.50; p = 0.02; moderate effect size differences). The developed basketball-specific agility tests are applicable when defining position-specific agility. Both preplanned and nonplanned agilities are important qualities in differentiating between Guards of 2 performance levels. The results confirmed the importance of testing basketball-specific nonplanned agility when evaluating the performance level of Centers.

Collected Software Engineering Papers, Volume 10

NASA Technical Reports Server (NTRS)

1992-01-01

This document is a collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) from Oct. 1991 - Nov. 1992. The purpose of the document is to make available, in one reference, some results of SEL research that originally appeared in a number of different forums. Although these papers cover several topics related to software engineering, they do not encompass the entire scope of SEL activities and interests. Additional information about the SEL and its research efforts may be obtained from the sources listed in the bibliography at the end of this document. For the convenience of this presentation, the 11 papers contained here are grouped into 5 major sections: (1) the Software Engineering Laboratory; (2) software tools studies; (3) software models studies; (4) software measurement studies; and (5) Ada technology studies.

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.

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.

An Agile Systems Engineering Process: The Missing Link?

DTIC Science & Technology

2011-05-01

has a num- ber of standards available such as ISO 12207 , ISO 9001 and the Capability Maturity Model Integrated (CMMI®) [24,25,26]. The CMMI was a...addressing activities throughout the products lifecycle [24]. ISO 12207 “contains processes, activities and tasks that are to be applied during...the acquisition of a system that contains software” [26]. A limitation identified within ISO 12207 is that it does not specify details on how to

Strategic Technology Selection and Classification in Multimodel Environments

DTIC Science & Technology

2008-05-01

processes. Specifically, the organization chose a blend of CMMI (portions of which were being implemented in engineering), ISO 12207 and the SA CMM...whole- product support Improve product field performance Strategy to accomplish goal Reference models CMMI, SA CMM, IEEE/ ISO 12207 Leverage CMMI...ro u p Lean Six Sigma SOX ISO /IEC 15288 ISO 9000 CMMI ISO 12207 P-CMM AS9100 IEEE 830 PSMIDEAL PPSLockheed Martin Integrated Enterprise Process Agile

Investigation of a Graphical CONOPS Development Environment for Agile Systems Engineering

DTIC Science & Technology

2009-10-30

their first session, the team, using ACS, identifies potential stakeholders within the DHS, the CDC, state emergency response agencies, city governments ...variety of government and private sector institutions for new systems, modifications to existing systems and for mapping out operational strategies...irspace syst em," in 11th Confer ence on Aviation, Range, and Ae rospace, 2004, The Boeing Company and Lockheed Martin Corporation , " CONOPS for the syst

Reshaping the Army Corps of Engineers’ Workforce

DTIC Science & Technology

2013-03-01

Collins, “Good to Great: Why Some Companies Make the Leap…and Others Don’t”, (Boulder, CO: Harper Business , 2001) iPhone – ebook , 24-28. 3 Ibid...getting the “right” people to whom Collins refers in the “Disciplined People” stage, this paper analyzes how private sector businesses recruit, hire, and...strategic agility, and ultimately generate a competitive advantage for the VUCA operating environment. In the 2012-13 Key Strategic Issues List assembled

Biomimetic Oscillating Foil Propulsion to Enhance Underwater Vehicle Agility and Maneuverability

DTIC Science & Technology

2008-06-01

Blake, A.W. Trites, and K.H.S. Chan. Turning maneuvers in steller sea lions (eumatopias jubatus). Marine Mammal Science, 23(1):94-109, 2007. [10] E.G...degree of Doctor of Philosophy in Oceanographic and Mechanical Engineering Abstract Inspired by the swimming abilities of marine animals, this thesis...with various conventional thruster /control sur- face combinations, as well as sealion (Zalophus californianus and Eu- matopias jubatus ) turning rates

Automated toxicological screening reports of modified Agilent MSD Chemstation combined with Microsoft Visual Basic application programs.

PubMed

Choe, Sanggil; Kim, Suncheun; Choi, Hyeyoung; Choi, Hwakyoung; Chung, Heesun; Hwang, Bangyeon

2010-06-15

Agilent GC-MS MSD Chemstation offers automated library search report for toxicological screening using total ion chromatogram (TIC) and mass spectroscopy in normal mode. Numerous peaks appear in the chromatogram of biological specimen such as blood or urine and often large migrating peaks obscure small target peaks, in addition, any target peaks of low abundance regularly give wrong library search result or low matching score. As a result, retention time and mass spectrum of all the peaks in the chromatogram have to be checked to see if they are relevant. These repeated actions are very tedious and time-consuming to toxicologists. MSD Chemstation software operates using a number of macro files which give commands and instructions on how to work on and extract data from the chromatogram and spectroscopy. These macro files are developed by the own compiler of the software. All the original macro files can be modified and new macro files can be added to the original software by users. To get more accurate results with more convenient method and to save time for data analysis, we developed new macro files for reports generation and inserted new menus in the Enhanced Data Analysis program. Toxicological screening reports generated by these new macro files are in text mode or graphic mode and these reports can be generated with three different automated subtraction options. Text reports have Brief mode and Full mode and graphic reports have the option with or without mass spectrum mode. Matched mass spectrum and matching score for detected compounds are printed in reports by modified library searching modules. We have also developed an independent application program named DrugMan. This program manages drug groups, lists and parameters that are in use in MSD Chemstation. The incorporation of DrugMan with modified macro modules provides a powerful tool for toxicological screening and save a lot of valuable time on toxicological work. (c) 2010 Elsevier Ireland Ltd. All rights reserved.

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

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.

An Architecture, System Engineering, and Acquisition Approach for Space System Software Resiliency

NASA Astrophysics Data System (ADS)

Phillips, Dewanne Marie

Software intensive space systems can harbor defects and vulnerabilities that may enable external adversaries or malicious insiders to disrupt or disable system functions, risking mission compromise or loss. Mitigating this risk demands a sustained focus on the security and resiliency of the system architecture including software, hardware, and other components. Robust software engineering practices contribute to the foundation of a resilient system so that the system "can take a hit to a critical component and recover in a known, bounded, and generally acceptable period of time". Software resiliency must be a priority and addressed early in the life cycle development to contribute a secure and dependable space system. Those who develop, implement, and operate software intensive space systems must determine the factors and systems engineering practices to address when investing in software resiliency. This dissertation offers methodical approaches for improving space system resiliency through software architecture design, system engineering, increased software security, thereby reducing the risk of latent software defects and vulnerabilities. By providing greater attention to the early life cycle phases of development, we can alter the engineering process to help detect, eliminate, and avoid vulnerabilities before space systems are delivered. To achieve this objective, this dissertation will identify knowledge, techniques, and tools that engineers and managers can utilize to help them recognize how vulnerabilities are produced and discovered so that they can learn to circumvent them in future efforts. We conducted a systematic review of existing architectural practices, standards, security and coding practices, various threats, defects, and vulnerabilities that impact space systems from hundreds of relevant publications and interviews of subject matter experts. We expanded on the system-level body of knowledge for resiliency and identified a new software architecture framework and acquisition methodology to improve the resiliency of space systems from a software perspective with an emphasis on the early phases of the systems engineering life cycle. This methodology involves seven steps: 1) Define technical resiliency requirements, 1a) Identify standards/policy for software resiliency, 2) Develop a request for proposal (RFP)/statement of work (SOW) for resilient space systems software, 3) Define software resiliency goals for space systems, 4) Establish software resiliency quality attributes, 5) Perform architectural tradeoffs and identify risks, 6) Conduct architecture assessments as part of the procurement process, and 7) Ascertain space system software architecture resiliency metrics. Data illustrates that software vulnerabilities can lead to opportunities for malicious cyber activities, which could degrade the space mission capability for the user community. Reducing the number of vulnerabilities by improving architecture and software system engineering practices can contribute to making space systems more resilient. Since cyber-attacks are enabled by shortfalls in software, robust software engineering practices and an architectural design are foundational to resiliency, which is a quality that allows the system to "take a hit to a critical component and recover in a known, bounded, and generally acceptable period of time". To achieve software resiliency for space systems, acquirers and suppliers must identify relevant factors and systems engineering practices to apply across the lifecycle, in software requirements analysis, architecture development, design, implementation, verification and validation, and maintenance phases.

Evan Weaver | NREL

Science.gov Websites

Evan Weaver Photo of Evan Weaver Evan Weaver Researcher III-Software Engineering Evan.Weaver , he works as a software engineer developing whole-building energy modeling tools. Prior to joining NREL, he worked in the biomedical industry as a software engineer, specializing in graphical user

Requirements Engineering in Building Climate Science Software

ERIC Educational Resources Information Center

Batcheller, Archer L.

2011-01-01

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

The Accuracy of GBM GRB Localizations

NASA Astrophysics Data System (ADS)

Briggs, Michael Stephen; Connaughton, V.; Meegan, C.; Hurley, K.

2010-03-01

We report an study of the accuracy of GBM GRB localizations, analyzing three types of localizations: those produced automatically by the GBM Flight Software on board GBM, those produced automatically with ground software in near real time, and localizations produced with human guidance. The two types of automatic locations are distributed in near real-time via GCN Notices; the human-guided locations are distributed on timescale of many minutes or hours using GCN Circulars. This work uses a Bayesian analysis that models the distribution of the GBM total location error by comparing GBM locations to more accurate locations obtained with other instruments. Reference locations are obtained from Swift, Super-AGILE, the LAT, and with the IPN. We model the GBM total location errors as having systematic errors in addition to the statistical errors and use the Bayesian analysis to constrain the systematic errors.

Lessons Learned from Deploying an Analytical Task Management Database

NASA Technical Reports Server (NTRS)

O'Neil, Daniel A.; Welch, Clara; Arceneaux, Joshua; Bulgatz, Dennis; Hunt, Mitch; Young, Stephen

2007-01-01

Defining requirements, missions, technologies, and concepts for space exploration involves multiple levels of organizations, teams of people with complementary skills, and analytical models and simulations. Analytical activities range from filling a To-Be-Determined (TBD) in a requirement to creating animations and simulations of exploration missions. In a program as large as returning to the Moon, there are hundreds of simultaneous analysis activities. A way to manage and integrate efforts of this magnitude is to deploy a centralized database that provides the capability to define tasks, identify resources, describe products, schedule deliveries, and generate a variety of reports. This paper describes a web-accessible task management system and explains the lessons learned during the development and deployment of the database. Through the database, managers and team leaders can define tasks, establish review schedules, assign teams, link tasks to specific requirements, identify products, and link the task data records to external repositories that contain the products. Data filters and spreadsheet export utilities provide a powerful capability to create custom reports. Import utilities provide a means to populate the database from previously filled form files. Within a four month period, a small team analyzed requirements, developed a prototype, conducted multiple system demonstrations, and deployed a working system supporting hundreds of users across the aeros pace community. Open-source technologies and agile software development techniques, applied by a skilled team enabled this impressive achievement. Topics in the paper cover the web application technologies, agile software development, an overview of the system's functions and features, dealing with increasing scope, and deploying new versions of the system.

Glossary of Software Engineering Laboratory terms

NASA Technical Reports Server (NTRS)

1983-01-01

A glossary of terms used in the Software Engineering Laboratory (SEL) is given. The terms are defined within the context of the software development environment for flight dynamics at the Goddard Space Flight Center. A concise reference for clarifying the language employed in SEL documents and data collection forms is given. Basic software engineering concepts are explained and standard definitions for use by SEL personnel are established.

Software Reporting Metrics. Revision 2.

DTIC Science & Technology

1985-11-01

MITRE Corporation and ESD. Some of the data has been obtained from Dr. Barry Boehm’s Software Engineering Economics (Ref. 1). Thanks are also given to...data level control management " SP = structured programming Barry W. Boehm, Software Engineering Economics, &©1981, p. 122. Reprinted by permission of...investigated and implemented in future prototypes. 43 REFERENCES For further reading: " 1. Boehm, Barry W. Software Engineering Economics; Englewood

Toward Reusable Graphics Components in Ada

DTIC Science & Technology

1993-03-01

Then alternatives for obtaining well- engineered reusable software components were examined. Finally, the alternatives were analyzed, and the most...reusable software components. Chapter 4 describes detailed design and implementation strategies in building a well- engineered reusable set of components in...study. 2.2 The Object-Oriented Paradigm 2.2.1 The Need for Object-Oriented Techniques. Among software engineers the software crisis is a well known

Object oriented development of engineering software using CLIPS

NASA Technical Reports Server (NTRS)

Yoon, C. John

1991-01-01

Engineering applications involve numeric complexity and manipulations of a large amount of data. Traditionally, numeric computation has been the concern in developing an engineering software. As engineering application software became larger and more complex, management of resources such as data, rather than the numeric complexity, has become the major software design problem. Object oriented design and implementation methodologies can improve the reliability, flexibility, and maintainability of the resulting software; however, some tasks are better solved with the traditional procedural paradigm. The C Language Integrated Production System (CLIPS), with deffunction and defgeneric constructs, supports the procedural paradigm. The natural blending of object oriented and procedural paradigms has been cited as the reason for the popularity of the C++ language. The CLIPS Object Oriented Language's (COOL) object oriented features are more versatile than C++'s. A software design methodology based on object oriented and procedural approaches appropriate for engineering software, and to be implemented in CLIPS was outlined. A method for sensor placement for Space Station Freedom is being implemented in COOL as a sample problem.

Software requirements specification for the GIS-T/ISTEA pooled fund study phase C linear referencing engine

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

Amai, W.; Espinoza, J. Jr.; Fletcher, D.R.

1997-06-01

This Software Requirements Specification (SRS) describes the features to be provided by the software for the GIS-T/ISTEA Pooled Fund Study Phase C Linear Referencing Engine project. This document conforms to the recommendations of IEEE Standard 830-1984, IEEE Guide to Software Requirements Specification (Institute of Electrical and Electronics Engineers, Inc., 1984). The software specified in this SRS is a proof-of-concept implementation of the Linear Referencing Engine as described in the GIS-T/ISTEA pooled Fund Study Phase B Summary, specifically Sheet 13 of the Phase B object model. The software allows an operator to convert between two linear referencing methods and a datummore » network.« less

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.

A Software Engineering Approach based on WebML and BPMN to the Mediation Scenario of the SWS Challenge

NASA Astrophysics Data System (ADS)

Brambilla, Marco; Ceri, Stefano; Valle, Emanuele Della; Facca, Federico M.; Tziviskou, Christina

Although Semantic Web Services are expected to produce a revolution in the development of Web-based systems, very few enterprise-wide design experiences are available; one of the main reasons is the lack of sound Software Engineering methods and tools for the deployment of Semantic Web applications. In this chapter, we present an approach to software development for the Semantic Web based on classical Software Engineering methods (i.e., formal business process development, computer-aided and component-based software design, and automatic code generation) and on semantic methods and tools (i.e., ontology engineering, semantic service annotation and discovery).

Software Engineering Education: Some Important Dimensions

ERIC Educational Resources Information Center

Mishra, Alok; Cagiltay, Nergiz Ercil; Kilic, Ozkan

2007-01-01

Software engineering education has been emerging as an independent and mature discipline. Accordingly, various studies are being done to provide guidelines for curriculum design. The main focus of these guidelines is around core and foundation courses. This paper summarizes the current problems of software engineering education programs. It also…

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.

Software Engineering Laboratory (SEL) data base reporting software user's guide and system description. Volume 1: Introduction and user's guide

NASA Technical Reports Server (NTRS)

1983-01-01

Reporting software programs provide formatted listings and summary reports of the Software Engineering Laboratory (SEL) data base contents. The operating procedures and system information for 18 different reporting software programs are described. Sample output reports from each program are provided.

Software Engineering Laboratory (SEL) data base reporting software user's guide and system description. Volume 2: Program descriptions

NASA Technical Reports Server (NTRS)

1983-01-01

The structure and functions of each reporting software program for the Software Engineering Laboratory data base are described. Baseline diagrams, module descriptions, and listings of program generation files are included.

Software engineering standards and practices

NASA Technical Reports Server (NTRS)

Durachka, R. W.

1981-01-01

Guidelines are presented for the preparation of a software development plan. The various phases of a software development project are discussed throughout its life cycle including a general description of the software engineering standards and practices to be followed during each phase.

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.

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.

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.

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.

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 performance for men but not for women. In addition to demonstrating a known relationship between speed and agility in both genders, and a small but statistically significant relationship between power and agility in women, these results indicate that balance should be considered as a potential predictor of agility in trained adult men.

Socio-Cultural Challenges in Global Software Engineering Education

ERIC Educational Resources Information Center

Hoda, Rashina; Babar, Muhammad Ali; Shastri, Yogeshwar; Yaqoob, Humaa

2017-01-01

Global software engineering education (GSEE) is aimed at providing software engineering (SE) students with knowledge, skills, and understanding of working in globally distributed arrangements so they can be prepared for the global SE (GSE) paradigm. It is important to understand the challenges involved in GSEE for improving the quality and…

Experiences with Integrating Simulation into a Software Engineering Curriculum

ERIC Educational Resources Information Center

Bollin, Andreas; Hochmuller, Elke; Mittermeir, Roland; Samuelis, Ladislav

2012-01-01

Software Engineering education must account for a broad spectrum of knowledge and skills software engineers will be required to apply throughout their professional life. Covering all the topics in depth within a university setting is infeasible due to curricular constraints as well as due to the inherent differences between educational…

An Engineering Context for Software Engineering

DTIC Science & Technology

2008-09-01

medium in which I can plant the ideas from this dissertation. I have also written a book on requirements development that is used at NPS by myself and...Addison-Wesley, Anniversary ed., 1995. [Bry00] Bryant, A., “Metaphor, Myth, and Mimicry : The Bases of Software Engineering,” Annals of Software

Applying the Kanban method in problem-based project work: a case study in a manufacturing engineering bachelor's programme at Aalborg University Copenhagen

NASA Astrophysics Data System (ADS)

Balve, Patrick; Krüger, Volker; Tolstrup Sørensen, Lene

2017-11-01

Problem-based learning (PBL) has proven to be highly effective for educating students in an active and self-motivated manner in various disciplines. Student projects carried out following PBL principles are very dynamic and carry a high level of uncertainty, both conditions under which agile project management approaches are assumed to be highly supportive. The paper describes an empirical case study carried out at Aalborg University Copenhagen involving students from two different semesters of a Bachelor of Science programme. While executing the study, compelling examples of how PBL and the agile project management method Kanban blend could be identified. A final survey reveals that applying Kanban produces noticeable improvements with respect to creating, assigning and coordinating project tasks. Other improvements were found in group communication, knowledge about the work progress with regards to both the individual and the collective and the students' way of continuously improving their own teamwork.

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

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.

Selection of software for mechanical engineering undergraduates

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

Cheah, C. T.; Yin, C. S.; Halim, T.

A major problem with the undergraduate mechanical course is the limited exposure of students to software packages coupled with the long learning curve on the existing software packages. This work proposes the use of appropriate software packages for the entire mechanical engineering curriculum to ensure students get sufficient exposure real life design problems. A variety of software packages are highlighted as being suitable for undergraduate work in mechanical engineering, e.g. simultaneous non-linear equations; uncertainty analysis; 3-D modeling software with the FEA; analysis tools for the solution of problems in thermodynamics, fluid mechanics, mechanical system design, and solid mechanics.

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.

Proceedings of the Twenty-Fourth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

2000-01-01

On December 1 and 2, the Software Engineering Laboratory (SEL), a consortium composed of NASA/Goddard, the University of Maryland, and CSC, held the 24th Software Engineering Workshop (SEW), the last of the millennium. Approximately 240 people attended the 2-day workshop. Day 1 was composed of four sessions: International Influence of the Software Engineering Laboratory; Object Oriented Testing and Reading; Software Process Improvement; and Space Software. For the first session, three internationally known software process experts discussed the influence of the SEL with respect to software engineering research. In the Space Software session, prominent representatives from three different NASA sites- GSFC's Marti Szczur, the Jet Propulsion Laboratory's Rick Doyle, and the Ames Research Center IV&V Facility's Lou Blazy- discussed the future of space software in their respective centers. At the end of the first day, the SEW sponsored a reception at the GSFC Visitors' Center. Day 2 also provided four sessions: Using the Experience Factory; A panel discussion entitled "Software Past, Present, and Future: Views from Government, Industry, and Academia"; Inspections; and COTS. The day started with an excellent talk by CSC's Frank McGarry on "Attaining Level 5 in CMM Process Maturity." Session 2, the panel discussion on software, featured NASA Chief Information Officer Lee Holcomb (Government), our own Jerry Page (Industry), and Mike Evangelist of the National Science Foundation (Academia). Each presented his perspective on the most important developments in software in the past 10 years, in the present, and in the future.

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 tests becoming part of the production regression test suite. Results We used test–driven development to construct a new CDS tool advising Emergency Department nurses to perform a swallowing assessment prior to administering oral medication to a patient with suspected stroke. Test tables specified desired behavior for (1) applicable clinical settings, (2) triggering action, (3) rule logic, (4) user interface, and (5) system actions in response to user input. Automated test suite results for the “executable requirements” are shown prior to building the CDS alert, during build, and after successful build. Conclusions Automated acceptance test–driven development and continuous regression testing of CDS configuration in a commercial EHR proves feasible with open source software. Automated test–driven development offers one potential contribution to achieving high-reliability EHR configuration. Vetting acceptance tests with clinicians elicits their input on crucial configuration details early during initial CDS design and iteratively during rapid-cycle optimization. PMID:29653922

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.

Proceedings of the Ninth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1984-01-01

Experiences in measurement, utilization, and evaluation of software methodologies, models, and tools are discussed. NASA's involvement in ever larger and more complex systems, like the space station project, provides a motive for the support of software engineering research and the exchange of ideas in such forums. The topics of current SEL research are software error studies, experiments with software development, and software tools.

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

NASA Technical Reports Server (NTRS)

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

1997-01-01

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

Requirements: Towards an understanding on why software projects fail

NASA Astrophysics Data System (ADS)

Hussain, Azham; Mkpojiogu, Emmanuel O. C.

2016-08-01

Requirement engineering is at the foundation of every successful software project. There are many reasons for software project failures; however, poorly engineered requirements process contributes immensely to the reason why software projects fail. Software project failure is usually costly and risky and could also be life threatening. Projects that undermine requirements engineering suffer or are likely to suffer from failures, challenges and other attending risks. The cost of project failures and overruns when estimated is very huge. Furthermore, software project failures or overruns pose a challenge in today's competitive market environment. It affects the company's image, goodwill, and revenue drive and decreases the perceived satisfaction of customers and clients. In this paper, requirements engineering was discussed. Its role in software projects success was elaborated. The place of software requirements process in relation to software project failure was explored and examined. Also, project success and failure factors were also discussed with emphasis placed on requirements factors as they play a major role in software projects' challenges, successes and failures. The paper relied on secondary data and empirical statistics to explore and examine factors responsible for the successes, challenges and failures of software projects in large, medium and small scaled software companies.

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

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

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

2005-01-01

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

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

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...

Proceedings of the 14th Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1989-01-01

Several software related topics are presented. Topics covered include studies and experiment at the Software Engineering Laboratory at the Goddard Space Flight Center, predicting project success from the Software Project Management Process, software environments, testing in a reuse environment, domain directed reuse, and classification tree analysis using the Amadeus measurement and empirical analysis.

Software Process Improvement through the Removal of Project-Level Knowledge Flow Obstacles: The Perceptions of Software Engineers

ERIC Educational Resources Information Center

Mitchell, Susan Marie

2012-01-01

Uncontrollable costs, schedule overruns, and poor end product quality continue to plague the software engineering field. Innovations formulated with the expectation to minimize or eliminate cost, schedule, and quality problems have generally fallen into one of three categories: programming paradigms, software tools, and software process…

RICIS Software Engineering 90 Symposium: Aerospace Applications and Research Directions Proceedings Appendices

NASA Technical Reports Server (NTRS)

1990-01-01

Papers presented at RICIS Software Engineering Symposium are compiled. The following subject areas are covered: flight critical software; management of real-time Ada; software reuse; megaprogramming software; Ada net; POSIX and Ada integration in the Space Station Freedom Program; and assessment of formal methods for trustworthy computer systems.

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.

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.

Collaborative business processes for enhancing partnerships among software services providers

NASA Astrophysics Data System (ADS)

Heil Cancian, Maiara; Rabelo, Ricardo; Gresse von Wangenheim, Christiane

2015-08-01

Software services have represented a powerful view to support the realisation of the service-oriented architecture (SOA) paradigm. Using open standards and facilitating systems projects, they have increasingly been used as a corporate architectural approach to create interoperable services-based software solutions that can more easily be reused and shared across disparate applications. In the context of software companies, most of them are small firms having enormous difficulties to keep competitive. One strategy to enhance their sustainability is to enlarge partnerships among them at a more valuable level by jointly offering (web) services-based solutions. However, their culture of collaboration is low, and partnerships are usually done with the same companies and sporadically. This article presents an approach to support a more intense collaboration among software companies to attend business opportunities in a more agile way, joining capacities and capabilities which they would not have if they worked alone. This requires, however, some preparedness. From the perspective of business processes, they should understand how to carry out a collaboration more properly. This is essentially what this article is about. It presents a comprehensive list of collaborative business processes and base practices that can also act as a guide for service providers' managers to implement and manage the collaboration along its lifecycle. Processes have been validated and results are discussed.

Technology transfer in software engineering

NASA Technical Reports Server (NTRS)

Bishop, Peter C.

1989-01-01

The University of Houston-Clear Lake is the prime contractor for the AdaNET Research Project under the direction of NASA Johnson Space Center. AdaNET was established to promote the principles of software engineering to the software development industry. AdaNET will contain not only environments and tools, but also concepts, principles, models, standards, guidelines and practices. Initially, AdaNET will serve clients from the U.S. government and private industry who are working in software development. It will seek new clients from those who have not yet adopted the principles and practices of software engineering. Some of the goals of AdaNET are to become known as an objective, authoritative source of new software engineering information and parts, to provide easy access to information and parts, and to keep abreast of innovations in the field.

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…

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.

Using a Functional Simulation of Crisis Management to Test the C2 Agility Model Parameters on Key Performance Variables

DTIC Science & Technology

2013-06-01

1 18th ICCRTS Using a Functional Simulation of Crisis Management to Test the C2 Agility Model Parameters on Key Performance Variables...AND SUBTITLE Using a Functional Simulation of Crisis Management to Test the C2 Agility Model Parameters on Key Performance Variables 5a. CONTRACT...command in crisis management. C2 Agility Model Agility can be conceptualized at a number of different levels; for instance at the team

Managing Transitions: Examining the Institutional Army’s Transformation Following the Vietnam War and Operation Iraqi Freedom

DTIC Science & Technology

2015-05-23

combat vehicles to fight at night. Another relatable lesson was the need to increase the engine strength and propulsion from a diesel to a turbine ...technologies integrated by means of advanced wireless networks. The FCS was built on the premise of mobile, agile formations that could embark to a theater...Robert Gates cancelled the program, developmental cost reached $212 billion dollars, fielding unattended ground sensors (UGS) and the Warfighter

X-36 Being Prepared on Lakebed for First Flight

NASA Technical Reports Server (NTRS)

1997-01-01

Lit by the rays of the morning sunrise on Rogers Dry Lake, adjacent to NASA's Dryden Flight Research Center, Edwards, California, technicians prepare the remotely-piloted X-36 Tailless Fighter Agility Research Aircraft for its first flight in May 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 on Ground after Radio and Telemetry Tests

NASA Technical Reports Server (NTRS)

1996-01-01

A UH-1 helicopter lowers the X-36 Tailless Fighter Agility Research Aircraft to the ground after radio frequency and telemetry tests above Rogers Dry Lake at NASA Dryden Flight Research Center, Edwards, California, in November 1996. The purpose of taking the X-36 aloft for the radio and telemetry system checkouts was to test the systems more realistically while airborne. More taxi and radio frequency tests were conducted before the aircraft's first flight in early 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 in Flight over Mojave Desert during 5th Flight

NASA Technical Reports Server (NTRS)

1997-01-01

The unusual lines of the X-36 Tailless Fighter Agility Research Aircraft contrast sharply with the desert floor as the remotely-piloted aircraft flies over the Mojave Desert on a June 1997 research flight. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Carried Aloft by Helicopter during Radio and Telemetry Tests

NASA Technical Reports Server (NTRS)

1996-01-01

A Bell UH-1 helicopter lifts the X-36 Tailless Fighter Agility Research Aircraft off the ground for radio frequency and telemetry tests above Rogers Dry Lake at NASA Dryden Flight Research Center, Edwards, California, in November 1996. The purpose of taking the X-36 aloft for the radio and telemetry system checkouts was to test the systems more realistically while airborne. More taxi and radio frequency tests were conducted before the aircraft's first flight in early 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 during First Flight

NASA Technical Reports Server (NTRS)

1997-01-01

The remotely-piloted X-36 Tailless Fighter Agility Research Aircraft climbs out from Rogers Dry Lake at the Dryden Flight Research Center on its first flight in May 1997. The aircraft flew for five minutes and reached an altitude of approximately 4,900 feet. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 in Flight near Edge of Rogers Dry Lake during 5th Flight

NASA Technical Reports Server (NTRS)

1997-01-01

This photo shows the X-36 Tailless Fighter Agility Research Aircraft passing over the edge of Rogers Dry Lake as the remotely-piloted aircraft flies over Edwards Air Force Base on a June 1997 research flight. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Being Prepared on Lakebed for First Flight

NASA Technical Reports Server (NTRS)

1997-01-01

Lit by the rays of the morning sunrise on Rogers Dry Lake, adjacent to NASA's Dryden Flight Research Center, Edwards, California, a technician prepares the remotely-piloted X-36 Tailless Fighter Agility Research Aircraft for its first flight on May 17, 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 on Ramp Viewed from Above

NASA Technical Reports Server (NTRS)

1997-01-01

This look-down view of the X-36 Tailless Fighter Agility Research Aircraft on the ramp at NASA's Dryden Flight Research Center, Edwards, California, clearly shows the unusual wing and canard design of the remotely-piloted aircraft. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Being Prepared on Lakebed for First Flight

NASA Technical Reports Server (NTRS)

1997-01-01

Lit by the rays of the morning sunrise on Rogers Dry Lake, adjacent to NASA's Dryden Flight Research Center, Edwards, California, technicians prepares the remotely-piloted X-36 Tailless Fighter Agility Research Aircraft for its first flight on May 17, 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Carried Aloft by Helicopter during Radio and Telemetry Tests

NASA Technical Reports Server (NTRS)

1996-01-01

A Bell UH-1 helicopter lifts the X-36 Tailless Fighter Agility Research Aircraft off the ground for radio frequency and telemetry tests above Rogers Dry Lake at NASA Dryden Flight Research Center, Edwards, California, in November 1996. The purpose of taking the X-36 aloft for the radio and telemetry system checkouts was to test the systems more realistically while airborne. More taxi and radio frequency tests were conducted before the aircraft's first flight in early 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Being Prepared on Lakebed for First Flight

NASA Technical Reports Server (NTRS)

1997-01-01

As the sun creeps above the horizon of Rogers Dry Lake at NASA's Dryden Flight Research Center, Edwards, California, technicians make final preparations for the first flight of the X-36 Tailless Fighter Agility Research Aircraft. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 Tailless Fighter Agility Research Aircraft in flight

NASA Technical Reports Server (NTRS)

1997-01-01

The lack of a vertical tail on the X-36 technology demonstrator is evident as the remotely piloted aircraft flies a low-altitude research flight above Rogers Dry Lake at Edwards Air Force Base in the California desert on October 30, 1997. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

X-36 arrival at Dryden

NASA Technical Reports Server (NTRS)

1996-01-01

NASA and McDonnell Douglas Corporation (MDC) personnel steady the X-36 Tailless Fighter Agility Research Aircraft following arrival at NASA Dryden Flight Research Center, Edwards, California, on July 2, 1996. The aircraft is being hoisted out of it's shipping crate. 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 just over 10 feet. A Williams International F112 turbofan engine provided close to 700 pounds of thrust. A typical research flight lasted 35 to 45 minutes from takeoff to touchdown. A total of 31 successful research flights were flown from May 17, 1997, to November 12, 1997, amassing 15 hours and 38 minutes of flight time. The aircraft reached an altitude of 20,200 feet and a maximum angle of attack of 40 degrees. In a follow-on effort, the Air Force Research Laboratory (AFRL), Wright-Patterson Air Force Base, Ohio, contracted with Boeing to fly AFRL's Reconfigurable Control for Tailless Fighter Aircraft (RESTORE) software as a demonstration of the adaptability of the neural-net algorithm to compensate for in-flight damage or malfunction of effectors, such as flaps, ailerons and rudders. Two RESTORE research flights were flown in December 1998, proving the viability of the software approach. The X-36 aircraft flown at the Dryden Flight Research Center in 1997 was a 28-percent scale representation of a theoretical advanced fighter aircraft. The Boeing Phantom Works (formerly McDonnell Douglas) in St. Louis, Missouri, built two of the vehicles in a cooperative agreement with the Ames Research Center, Moffett Field, California.

Software reengineering

NASA Technical Reports Server (NTRS)

Fridge, Ernest M., III

1991-01-01

Today's software systems generally use obsolete technology, are not integrated properly with other software systems, and are difficult and costly to maintain. The discipline of reverse engineering is becoming prominent as organizations try to move their systems up to more modern and maintainable technology in a cost effective manner. JSC created a significant set of tools to develop and maintain FORTRAN and C code during development of the Space Shuttle. This tool set forms the basis for an integrated environment to re-engineer existing code into modern software engineering structures which are then easier and less costly to maintain and which allow a fairly straightforward translation into other target languages. The environment will support these structures and practices even in areas where the language definition and compilers do not enforce good software engineering. The knowledge and data captured using the reverse engineering tools is passed to standard forward engineering tools to redesign or perform major upgrades to software systems in a much more cost effective manner than using older technologies. A beta vision of the environment was released in Mar. 1991. The commercial potential for such re-engineering tools is very great. CASE TRENDS magazine reported it to be the primary concern of over four hundred of the top MIS executives.

A Recommended Framework for the Network-Centric Acquisition Process

DTIC Science & Technology

2009-09-01

ISO /IEC 12207 , Systems and Software Engineering-Software Life-Cycle Processes  ANSI/EIA 632, Processes for Engineering a System. There are...engineering [46]. Some of the process models presented in the DAG are:  ISO /IEC 15288, Systems and Software Engineering-System Life-Cycle Processes...e.g., ISO , IA, Security, etc.). Vetting developers helps ensure that they are using industry best industry practices and maximize the IA compliance

Software Engineering Education Directory. Software Engineering Curriculum Project

DTIC Science & Technology

1991-05-01

1986 with a questionnaire mailed to schools selected from Peterson’s Graduate Programs in Engineering and Applied Sciences 1986. We contacted schools...the publi- cation more complete. To discuss any issues related to this report, please contact: Education Program Software Engineering Institute...considered to be required course reading. How to Use This Section This portion of the directory is organized by state (in the U.S.), province (in

Single-crystal diffraction at the Extreme Conditions beamline P02.2: procedure for collecting and analyzing high-pressure single-crystal data.

PubMed

Rothkirch, André; Gatta, G Diego; Meyer, Mathias; Merkel, Sébastien; Merlini, Marco; Liermann, Hanns Peter

2013-09-01

Fast detectors employed at third-generation synchrotrons have reduced collection times significantly and require the optimization of commercial as well as customized software packages for data reduction and analysis. In this paper a procedure to collect, process and analyze single-crystal data sets collected at high pressure at the Extreme Conditions beamline (P02.2) at PETRA III, DESY, is presented. A new data image format called `Esperanto' is introduced that is supported by the commercial software package CrysAlis(Pro) (Agilent Technologies UK Ltd). The new format acts as a vehicle to transform the most common area-detector data formats via a translator software. Such a conversion tool has been developed and converts tiff data collected on a Perkin Elmer detector, as well as data collected on a MAR345/555, to be imported into the CrysAlis(Pro) software. In order to demonstrate the validity of the new approach, a complete structure refinement of boron-mullite (Al5BO9) collected at a pressure of 19.4 (2) GPa is presented. Details pertaining to the data collections and refinements of B-mullite are presented.

The Impact of Software on Associate Degree Programs in Electronic Engineering Technology.

ERIC Educational Resources Information Center

Hata, David M.

1986-01-01

Assesses the range and extent of computer assisted instruction software available in electronic engineering technology education. Examines the need for software skills in four areas: (1) high-level languages; (2) assembly language; (3) computer-aided engineering; and (4) computer-aided instruction. Outlines strategies for the future in three…

Software engineering

NASA Technical Reports Server (NTRS)

Fridge, Ernest M., III; Hiott, Jim; Golej, Jim; Plumb, Allan

1993-01-01

Today's software systems generally use obsolete technology, are not integrated properly with other software systems, and are difficult and costly to maintain. The discipline of reverse engineering is becoming prominent as organizations try to move their systems up to more modern and maintainable technology in a cost effective manner. The Johnson Space Center (JSC) created a significant set of tools to develop and maintain FORTRAN and C code during development of the space shuttle. This tool set forms the basis for an integrated environment to reengineer existing code into modern software engineering structures which are then easier and less costly to maintain and which allow a fairly straightforward translation into other target languages. The environment will support these structures and practices even in areas where the language definition and compilers do not enforce good software engineering. The knowledge and data captured using the reverse engineering tools is passed to standard forward engineering tools to redesign or perform major upgrades to software systems in a much more cost effective manner than using older technologies. The latest release of the environment was in Feb. 1992.

The GenABEL Project for statistical genomics.

PubMed

Karssen, Lennart C; van Duijn, Cornelia M; Aulchenko, Yurii S

2016-01-01

Development of free/libre open source software is usually done by a community of people with an interest in the tool. For scientific software, however, this is less often the case. Most scientific software is written by only a few authors, often a student working on a thesis. Once the paper describing the tool has been published, the tool is no longer developed further and is left to its own device. Here we describe the broad, multidisciplinary community we formed around a set of tools for statistical genomics. The GenABEL project for statistical omics actively promotes open interdisciplinary development of statistical methodology and its implementation in efficient and user-friendly software under an open source licence. The software tools developed withing the project collectively make up the GenABEL suite, which currently consists of eleven tools. The open framework of the project actively encourages involvement of the community in all stages, from formulation of methodological ideas to application of software to specific data sets. A web forum is used to channel user questions and discussions, further promoting the use of the GenABEL suite. Developer discussions take place on a dedicated mailing list, and development is further supported by robust development practices including use of public version control, code review and continuous integration. Use of this open science model attracts contributions from users and developers outside the "core team", facilitating agile statistical omics methodology development and fast dissemination.

The Personal Software Process (PSPSM): An Empirical Study of the Impact of PSP on Individual Engineers.

DTIC Science & Technology

1997-12-01

Watts Humphrey and is described in his book A Discipline for Software Engineering [ Humphrey 95]. Its intended use is to guide the planning and...Pat; Humphrey , Watts S .; Khajenoori, Soheil; Macke, Susan; & Matvya, Annette. "Introducing the Personal Software Process: Three Industry Case... Humphrey 95] Humphrey , Watts S . A Discipline for Software Engineering. Reading, Ma.: Addison-Wesley, 1995. [Mauchly 40] Mauchly, J.W. "Significance

Large-scale visualization projects for teaching software engineering.

PubMed

Müller, Christoph; Reina, Guido; Burch, Michael; Weiskopf, Daniel

2012-01-01

The University of Stuttgart's software engineering major complements the traditional computer science major with more practice-oriented education. Two-semester software projects in various application areas offered by the university's different computer science institutes are a successful building block in the curriculum. With this realistic, complex project setting, students experience the practice of software engineering, including software development processes, technologies, and soft skills. In particular, visualization-based projects are popular with students. Such projects offer them the opportunity to gain profound knowledge that would hardly be possible with only regular lectures and homework assignments.

Proposal of Evolutionary Simplex Method for Global Optimization Problem

NASA Astrophysics Data System (ADS)

Shimizu, Yoshiaki

To make an agile decision in a rational manner, role of optimization engineering has been notified increasingly under diversified customer demand. With this point of view, in this paper, we have proposed a new evolutionary method serving as an optimization technique in the paradigm of optimization engineering. The developed method has prospects to solve globally various complicated problem appearing in real world applications. It is evolved from the conventional method known as Nelder and Mead’s Simplex method by virtue of idea borrowed from recent meta-heuristic method such as PSO. Mentioning an algorithm to handle linear inequality constraints effectively, we have validated effectiveness of the proposed method through comparison with other methods using several benchmark problems.

48 CFR 227.7206 - Contracts for architect-engineer services.

Code of Federal Regulations, 2014 CFR

2014-10-01

... Rights in Computer Software and Computer Software Documentation 227.7206 Contracts for architect-engineer services. Follow 227.7107 when contracting for architect-engineer services. ...-engineer services. 227.7206 Section 227.7206 Federal Acquisition Regulations System DEFENSE ACQUISITION...

48 CFR 227.7206 - Contracts for architect-engineer services.

Code of Federal Regulations, 2011 CFR

2011-10-01

... Rights in Computer Software and Computer Software Documentation 227.7206 Contracts for architect-engineer services. Follow 227.7107 when contracting for architect-engineer services. ...-engineer services. 227.7206 Section 227.7206 Federal Acquisition Regulations System DEFENSE ACQUISITION...

48 CFR 227.7206 - Contracts for architect-engineer services.

Code of Federal Regulations, 2013 CFR

2013-10-01

... Rights in Computer Software and Computer Software Documentation 227.7206 Contracts for architect-engineer services. Follow 227.7107 when contracting for architect-engineer services. ...-engineer services. 227.7206 Section 227.7206 Federal Acquisition Regulations System DEFENSE ACQUISITION...

48 CFR 227.7206 - Contracts for architect-engineer services.

Code of Federal Regulations, 2012 CFR

2012-10-01

... Rights in Computer Software and Computer Software Documentation 227.7206 Contracts for architect-engineer services. Follow 227.7107 when contracting for architect-engineer services. ...-engineer services. 227.7206 Section 227.7206 Federal Acquisition Regulations System DEFENSE ACQUISITION...

48 CFR 227.7206 - Contracts for architect-engineer services.

Code of Federal Regulations, 2010 CFR

2010-10-01

...-engineer services. 227.7206 Section 227.7206 Federal Acquisition Regulations System DEFENSE ACQUISITION... Rights in Computer Software and Computer Software Documentation 227.7206 Contracts for architect-engineer services. Follow 227.7107 when contracting for architect-engineer services. ...

A Novel Coupling Pattern in Computational Science and Engineering Software

EPA Science Inventory

Computational science and engineering (CSE) software is written by experts of certain area(s). Due to the specialization, existing CSE software may need to integrate other CSE software systems developed by different groups of experts. The coupling problem is one of the challenges...

A Novel Coupling Pattern in Computational Science and Engineering Software

EPA Science Inventory

Computational science and engineering (CSE) software is written by experts of certain area(s). Due to the specialization,existing CSE software may need to integrate other CSE software systems developed by different groups of experts. Thecoupling problem is one of the challenges f...

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…

Modeling a distributed environment for a petroleum reservoir engineering application with software product line

NASA Astrophysics Data System (ADS)

de Faria Scheidt, Rafael; Vilain, Patrícia; Dantas, M. A. R.

2014-10-01

Petroleum reservoir engineering is a complex and interesting field that requires large amount of computational facilities to achieve successful results. Usually, software environments for this field are developed without taking care out of possible interactions and extensibilities required by reservoir engineers. In this paper, we present a research work which it is characterized by the design and implementation based on a software product line model for a real distributed reservoir engineering environment. Experimental results indicate successfully the utilization of this approach for the design of distributed software architecture. In addition, all components from the proposal provided greater visibility of the organization and processes for the reservoir engineers.

Virtualized Networks and Virtualized Optical Line Terminal (vOLT)

NASA Astrophysics Data System (ADS)

Ma, Jonathan; Israel, Stephen

2017-03-01

The success of the Internet and the proliferation of the Internet of Things (IoT) devices is forcing telecommunications carriers to re-architecture a central office as a datacenter (CORD) so as to bring the datacenter economics and cloud agility to a central office (CO). The Open Network Operating System (ONOS) is the first open-source software-defined network (SDN) operating system which is capable of managing and controlling network, computing, and storage resources to support CORD infrastructure and network virtualization. The virtualized Optical Line Termination (vOLT) is one of the key components in such virtualized networks.

Sensor fusion and augmented reality with the SAFIRE system

NASA Astrophysics Data System (ADS)

Saponaro, Philip; Treible, Wayne; Phelan, Brian; Sherbondy, Kelly; Kambhamettu, Chandra

2018-04-01

The Spectrally Agile Frequency-Incrementing Reconfigurable (SAFIRE) mobile radar system was developed and exercised at an arid U.S. test site. The system can detect hidden target using radar, a global positioning system (GPS), dual stereo color cameras, and dual stereo thermal cameras. An Augmented Reality (AR) software interface allows the user to see a single fused video stream containing the SAR, color, and thermal imagery. The stereo sensors allow the AR system to display both fused 2D imagery and 3D metric reconstructions, where the user can "fly" around the 3D model and switch between the modalities.

orthAgogue: an agile tool for the rapid prediction of orthology relations.

PubMed

Ekseth, Ole Kristian; Kuiper, Martin; Mironov, Vladimir

2014-03-01

The comparison of genes and gene products across species depends on high-quality tools to determine the relationships between gene or protein sequences from various species. Although some excellent applications are available and widely used, their performance leaves room for improvement. We developed orthAgogue: a multithreaded C application for high-speed estimation of homology relations in massive datasets, operated via a flexible and easy command-line interface. The orthAgogue software is distributed under the GNU license. The source code and binaries compiled for Linux are available at https://code.google.com/p/orthagogue/.

Software IV and V Research Priorities and Applied Program Accomplishments Within NASA

NASA Technical Reports Server (NTRS)

Blazy, Louis J.

2000-01-01

The mission of this research is to be world-class creators and facilitators of innovative, intelligent, high performance, reliable information technologies that enable NASA missions to (1) increase software safety and quality through error avoidance, early detection and resolution of errors, by utilizing and applying empirically based software engineering best practices; (2) ensure customer software risks are identified and/or that requirements are met and/or exceeded; (3) research, develop, apply, verify, and publish software technologies for competitive advantage and the advancement of science; and (4) facilitate the transfer of science and engineering data, methods, and practices to NASA, educational institutions, state agencies, and commercial organizations. The goals are to become a national Center Of Excellence (COE) in software and system independent verification and validation, and to become an international leading force in the field of software engineering for improving the safety, quality, reliability, and cost performance of software systems. This project addresses the following problems: Ensure safety of NASA missions, ensure requirements are met, minimize programmatic and technological risks of software development and operations, improve software quality, reduce costs and time to delivery, and improve the science of software engineering

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.

Implementing large projects in software engineering courses

NASA Astrophysics Data System (ADS)

Coppit, David

2006-03-01

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

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

A Role-Playing Game for a Software Engineering Lab: Developing a Product Line

ERIC Educational Resources Information Center

Zuppiroli, Sara; Ciancarini, Paolo; Gabbrielli, Maurizio

2012-01-01

Software product line development refers to software engineering practices and techniques for creating families of similar software systems from a basic set of reusable components, called shared assets. Teaching how to deal with software product lines in a university lab course is a challenging task, because there are several practical issues that…

On the Prospects and Concerns of Integrating Open Source Software Environment in Software Engineering Education

ERIC Educational Resources Information Center

Kamthan, Pankaj

2007-01-01

Open Source Software (OSS) has introduced a new dimension in software community. As the development and use of OSS becomes prominent, the question of its integration in education arises. In this paper, the following practices fundamental to projects and processes in software engineering are examined from an OSS perspective: project management;…

Ten recommendations for software engineering in research.

PubMed

Hastings, Janna; Haug, Kenneth; Steinbeck, Christoph

2014-01-01

Research in the context of data-driven science requires a backbone of well-written software, but scientific researchers are typically not trained at length in software engineering, the principles for creating better software products. To address this gap, in particular for young researchers new to programming, we give ten recommendations to ensure the usability, sustainability and practicality of research software.

Model Driven Engineering

NASA Astrophysics Data System (ADS)

Gaševic, Dragan; Djuric, Dragan; Devedžic, Vladan

A relevant initiative from the software engineering community called Model Driven Engineering (MDE) is being developed in parallel with the Semantic Web (Mellor et al. 2003a). The MDE approach to software development suggests that one should first develop a model of the system under study, which is then transformed into the real thing (i.e., an executable software entity). The most important research initiative in this area is the Model Driven Architecture (MDA), which is Model Driven Architecture being developed under the umbrella of the Object Management Group (OMG). This chapter describes the basic concepts of this software engineering effort.

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-relevant settings (e.g., field of play, training facilities, obstacle courses, etc.).

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.