75 FR 21258 - Privacy Act of 1974; System of Records

Federal Register 2010, 2011, 2012, 2013, 2014

2010-04-23

..., and potential as a military career officer. Also used to document faculty contributions as part of the...(s) and address: Delete entry and replace with ``Chief, Software Engineering Branch, U.S. Military..., motivation, discipline, final standing and potential as a military career officer. Also used to document...

cFE/CFS (Core Flight Executive/Core Flight System)

NASA Technical Reports Server (NTRS)

Wildermann, Charles P.

2008-01-01

This viewgraph presentation describes in detail the requirements and goals of the Core Flight Executive (cFE) and the Core Flight System (CFS). The Core Flight Software System is a mission independent, platform-independent, Flight Software (FSW) environment integrating a reusable core flight executive (cFE). The CFS goals include: 1) Reduce time to deploy high quality flight software; 2) Reduce project schedule and cost uncertainty; 3) Directly facilitate formalized software reuse; 4) Enable collaboration across organizations; 5) Simplify sustaining engineering (AKA. FSW maintenance); 6) Scale from small instruments to System of Systems; 7) Platform for advanced concepts and prototyping; and 7) Common standards and tools across the branch and NASA wide.

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

NASA Technical Reports Server (NTRS)

Bolton, Albanie T.

2016-01-01

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

Path generation algorithm for UML graphic modeling of aerospace test software

NASA Astrophysics Data System (ADS)

Qu, MingCheng; Wu, XiangHu; Tao, YongChao; Chen, Chao

2018-03-01

Aerospace traditional software testing engineers are based on their own work experience and communication with software development personnel to complete the description of the test software, manual writing test cases, time-consuming, inefficient, loopholes and more. Using the high reliability MBT tools developed by our company, the one-time modeling can automatically generate test case documents, which is efficient and accurate. UML model to describe the process accurately express the need to rely on the path is reached, the existing path generation algorithm are too simple, cannot be combined into a path and branch path with loop, or too cumbersome, too complicated arrangement generates a path is meaningless, for aerospace software testing is superfluous, I rely on our experience of ten load space, tailor developed a description of aerospace software UML graphics path generation algorithm.

More Than A SketchUp

NASA Technical Reports Server (NTRS)

Davis, Derrick D.

2014-01-01

This 2014 summer internship assignment at John F. Kennedy Space Center (K.S.C) was conducted with the National Aeronautics and Space Administration (NASA) Engineering and Technology (NE) group in support of the Control and Data Systems Division (NE-C) within the Test, Operations & Support Software Engineering Branch (NE-C2). The primary focus of this project was to assist Branch Chief Laurie B. Griffin, to support NASA's Small Payload Launch Integrated Testing Services (SPLITS) mission, by mastering the capabilities of 3-D modeling software called SketchUp. I used SketchUp to create a virtual environment for different laboratories of the NE-00 Division. My mission was to have these models uploaded into a K.S.C Partnerships Website and be used as a visual aid to viewers who browsed the site. The leads of this project were Kay L. Craig, Business and Industry Specialist (AD-A) and Steven E. Cain, (FA-C). I teamed with fellow intern Tait Sorenson of the Flight Structures and Thermal Protection Systems Branch (NE-M5) and met with many K.S.C lab managers willing to display their lab's structure and capabilities. The information collected during these lab tours was vital to the building of the K.S.C Partnerships Website. To accomplish this goal Sorenson and I later teamed with fellow Marketing intern Marlee Pereda-Ramos, of the Spaceport Planning Office In Center Planning And Development (AD-A) Along with Ramos, Tait and I toured an array of laboratories and got first hand exposure to their functions and capabilities.

Launch Commit Criteria Monitoring Agent

NASA Technical Reports Server (NTRS)

Semmel, Glenn S.; Davis, Steven R.; Leucht, Kurt W.; Rowe, Dan A.; Kelly, Andrew O.; Boeloeni, Ladislau

2005-01-01

The Spaceport Processing Systems Branch at NASA Kennedy Space Center has developed and deployed a software agent to monitor the Space Shuttle's ground processing telemetry stream. The application, the Launch Commit Criteria Monitoring Agent, increases situational awareness for system and hardware engineers during Shuttle launch countdown. The agent provides autonomous monitoring of the telemetry stream, automatically alerts system engineers when predefined criteria have been met, identifies limit warnings and violations of launch commit criteria, aids Shuttle engineers through troubleshooting procedures, and provides additional insight to verify appropriate troubleshooting of problems by contractors. The agent has successfully detected launch commit criteria warnings and violations on a simulated playback data stream. Efficiency and safety are improved through increased automation.

Software engineering and automatic continuous verification of scientific software

NASA Astrophysics Data System (ADS)

Piggott, M. D.; Hill, J.; Farrell, P. E.; Kramer, S. C.; Wilson, C. R.; Ham, D.; Gorman, G. J.; Bond, T.

2011-12-01

Software engineering of scientific code is challenging for a number of reasons including pressure to publish and a lack of awareness of the pitfalls of software engineering by scientists. The Applied Modelling and Computation Group at Imperial College is a diverse group of researchers that employ best practice software engineering methods whilst developing open source scientific software. Our main code is Fluidity - a multi-purpose computational fluid dynamics (CFD) code that can be used for a wide range of scientific applications from earth-scale mantle convection, through basin-scale ocean dynamics, to laboratory-scale classic CFD problems, and is coupled to a number of other codes including nuclear radiation and solid modelling. Our software development infrastructure consists of a number of free tools that could be employed by any group that develops scientific code and has been developed over a number of years with many lessons learnt. A single code base is developed by over 30 people for which we use bazaar for revision control, making good use of the strong branching and merging capabilities. Using features of Canonical's Launchpad platform, such as code review, blueprints for designing features and bug reporting gives the group, partners and other Fluidity uers an easy-to-use platform to collaborate and allows the induction of new members of the group into an environment where software development forms a central part of their work. The code repositoriy are coupled to an automated test and verification system which performs over 20,000 tests, including unit tests, short regression tests, code verification and large parallel tests. Included in these tests are build tests on HPC systems, including local and UK National HPC services. The testing of code in this manner leads to a continuous verification process; not a discrete event performed once development has ceased. Much of the code verification is done via the "gold standard" of comparisons to analytical solutions via the method of manufactured solutions. By developing and verifying code in tandem we avoid a number of pitfalls in scientific software development and advocate similar procedures for other scientific code applications.

Airborne Navigation Remote Map Reader Evaluation.

DTIC Science & Technology

1986-03-01

EVALUATION ( James C. Byrd Intergrated Controls/Displays Branch SAvionics Systems Division Directorate of Avionics Engineering SMarch 1986 Final Report...Resolution 15 3.2 Accuracy 15 3.3 Symbology 15 3.4 Video Standard 18 3.5 Simulator Control Box 18 3.6 Software 18 3.7 Display Performance 21 3.8 Reliability 24...can be selected depending on the detail required and will automatically be presented at his present position. .The French RMR uses a Flying Spot Scanner

Software Development Processes Applied to Computational Icing Simulation

NASA Technical Reports Server (NTRS)

Levinson, Laurie H.; Potapezuk, Mark G.; Mellor, Pamela A.

1999-01-01

The development of computational icing simulation methods is making the transition form the research to common place use in design and certification efforts. As such, standards of code management, design validation, and documentation must be adjusted to accommodate the increased expectations of the user community with respect to accuracy, reliability, capability, and usability. This paper discusses these concepts with regard to current and future icing simulation code development efforts as implemented by the Icing Branch of the NASA Lewis Research Center in collaboration with the NASA Lewis Engineering Design and Analysis Division. With the application of the techniques outlined in this paper, the LEWICE ice accretion code has become a more stable and reliable software product.

Multidisciplinary Optimization Branch Experience Using iSIGHT Software

NASA Technical Reports Server (NTRS)

Padula, S. L.; Korte, J. J.; Dunn, H. J.; Salas, A. O.

1999-01-01

The Multidisciplinary Optimization (MDO) Branch at NASA Langley Research Center is investigating frameworks for supporting multidisciplinary analysis and optimization research. An optimization framework call improve the design process while reducing time and costs. A framework provides software and system services to integrate computational tasks and allows the researcher to concentrate more on the application and less on the programming details. A framework also provides a common working environment and a full range of optimization tools, and so increases the productivity of multidisciplinary research teams. Finally, a framework enables staff members to develop applications for use by disciplinary experts in other organizations. Since the release of version 4.0, the MDO Branch has gained experience with the iSIGHT framework developed by Engineous Software, Inc. This paper describes experiences with four aerospace applications: (1) reusable launch vehicle sizing, (2) aerospike nozzle design, (3) low-noise rotorcraft trajectories, and (4) acoustic liner design. All applications have been successfully tested using the iSIGHT framework, except for the aerospike nozzle problem, which is in progress. Brief overviews of each problem are provided. The problem descriptions include the number and type of disciplinary codes, as well as all estimate of the multidisciplinary analysis execution time. In addition, the optimization methods, objective functions, design variables, and design constraints are described for each problem. Discussions on the experience gained and lessons learned are provided for each problem. These discussions include the advantages and disadvantages of using the iSIGHT framework for each case as well as the ease of use of various advanced features. Potential areas of improvement are identified.

Enhancement of computer system for applications software branch

NASA Technical Reports Server (NTRS)

Bykat, Alex

1987-01-01

Presented is a compilation of the history of a two-month project concerned with a survey, evaluation, and specification of a new computer system for the Applications Software Branch of the Software and Data Management Division of Information and Electronic Systems Laboratory of Marshall Space Flight Center, NASA. Information gathering consisted of discussions and surveys of branch activities, evaluation of computer manufacturer literature, and presentations by vendors. Information gathering was followed by evaluation of their systems. The criteria of the latter were: the (tentative) architecture selected for the new system, type of network architecture supported, software tools, and to some extent the price. The information received from the vendors, as well as additional research, lead to detailed design of a suitable system. This design included considerations of hardware and software environments as well as personnel issues such as training. Design of the system culminated in a recommendation for a new computing system for the Branch.

Closed-Cycle Engine Program Used to Study Brayton Power Conversion

NASA Technical Reports Server (NTRS)

Johnson, Paul K.

2005-01-01

One form of power conversion under consideration in NASA Glenn Research Center's Thermal Energy Conversion Branch is the closed-Brayton-cycle engine. In the tens-of-kilowatts to multimegawatt class, the Brayton engine lends itself to potential space nuclear power applications such as electric propulsion or surface power. The Thermal Energy Conversion Branch has most recently concentrated its Brayton studies on electric propulsion for Prometheus. One piece of software used for evaluating such designs over a limited tradeoff space has been the Closed Cycle Engine Program (CCEP). The CCEP originated in the mid-1980s from a Fortran aircraft engine code known as the Navy/NASA Engine Program (NNEP). Components such as a solar collector, heat exchangers, ducting, a pumped-loop radiator, a nuclear heat source, and radial turbomachinery were added to NNEP, transforming it into a high-fidelity design and performance tool for closed-Brayton-cycle power conversion and heat rejection. CCEP was used in the 1990s in conjunction with the Solar Dynamic Ground Test Demonstration conducted at Glenn. Over the past year, updates were made to CCEP to adapt it for an electric propulsion application. The pumped-loop radiator coolant can now be n-heptane, water, or sodium-potassium (NaK); liquid-metal pump design tables were added to accommodate the NaK fluid. For the reactor and shield, a user can now elect to calculate a higher fidelity mass estimate. In addition, helium-xenon working-fluid properties were recalculated and updated.

The TSO Logic and G2 Software Product

NASA Technical Reports Server (NTRS)

Davis, Derrick D.

2014-01-01

This internship assignment for spring 2014 was at John F. Kennedy Space Center (KSC), in NASAs Engineering and Technology (NE) group in support of the Control and Data Systems Division (NE-C) within the Systems Hardware Engineering Branch. (NEC-4) The primary focus was in system integration and benchmarking utilizing two separate computer software products. The first half of this 2014 internship is spent in assisting NE-C4s Electronics and Embedded Systems Engineer, Kelvin Ruiz and fellow intern Scott Ditto with the evaluation of a newly piece of software, called G2. Its developed by the Gensym Corporation and introduced to the group as a tool used in monitoring launch environments. All fellow interns and employees of the G2 group have been working together in order to better understand the significance of the G2 application and how KSC can benefit from its capabilities. The second stage of this Spring project is to assist with an ongoing integration of a benchmarking tool, developed by a group of engineers from a Canadian based organization known as TSO Logic. Guided by NE-C4s Computer Engineer, Allen Villorin, NASA 2014 interns put forth great effort in helping to integrate TSOs software into the Spaceport Processing Systems Development Laboratory (SPSDL) for further testing and evaluating. The TSO Logic group claims that their software is designed for, monitoring and reducing energy consumption at in-house server farms and large data centers, allows data centers to control the power state of servers, without impacting availability or performance and without changes to infrastructure and the focus of the assignment is to test this theory. TSOs Aaron Rallo Founder and CEO, and Chris Tivel CTO, both came to KSC to assist with the installation of their software in the SPSDL laboratory. TSOs software is installed onto 24 individual workstations running three different operating systems. The workstations were divided into three groups of 8 with each group having its own operating system. The first group is comprised of Ubuntus Debian -based Linux the second group is windows 7 Professional and the third group ran Red Hat Linux. The highlight of this portion of the assignment is to compose documentation expressing the overall impression of the software and its capabilities.

System requirements specification for SMART structures mode

NASA Technical Reports Server (NTRS)

1992-01-01

Specified here are the functional and informational requirements for software modules which address the geometric and data modeling needs of the aerospace structural engineer. The modules are to be included as part of the Solid Modeling Aerospace Research Tool (SMART) package developed for the Vehicle Analysis Branch (VAB) at the NASA Langley Research Center (LaRC). The purpose is to precisely state what the SMART Structures modules will do, without consideration of how it will be done. Each requirement is numbered for reference in development and testing.

Geographic Information Systems and Web Page Development

NASA Technical Reports Server (NTRS)

Reynolds, Justin

2004-01-01

The Facilities Engineering and Architectural Branch is responsible for the design and maintenance of buildings, laboratories, and civil structures. In order to improve efficiency and quality, the FEAB has dedicated itself to establishing a data infrastructure based on Geographic Information Systems, GIs. The value of GIS was explained in an article dating back to 1980 entitled "Need for a Multipurpose Cadastre which stated, "There is a critical need for a better land-information system in the United States to improve land-conveyance procedures, furnish a basis for equitable taxation, and provide much-needed information for resource management and environmental planning." Scientists and engineers both point to GIS as the solution. What is GIS? According to most text books, Geographic Information Systems is a class of software that stores, manages, and analyzes mapable features on, above, or below the surface of the earth. GIS software is basically database management software to the management of spatial data and information. Simply put, Geographic Information Systems manage, analyze, chart, graph, and map spatial information. At the outset, I was given goals and expectations from my branch and from my mentor with regards to the further implementation of GIs. Those goals are as follows: (1) Continue the development of GIS for the underground structures. (2) Extract and export annotated data from AutoCAD drawing files and construct a database (to serve as a prototype for future work). (3) Examine existing underground record drawings to determine existing and non-existing underground tanks. Once this data was collected and analyzed, I set out on the task of creating a user-friendly database that could be assessed by all members of the branch. It was important that the database be built using programs that most employees already possess, ruling out most AutoCAD-based viewers. Therefore, I set out to create an Access database that translated onto the web using Internet Explorer as the foundation. After some programming, it was possible to view AutoCAD files and other GIS-related applications on Internet Explorer, while providing the user with a variety of editing commands and setting options. I was also given the task of launching a divisional website using Macromedia Flash and other web- development programs.

Simscape Modeling Verification in the Simulink Development Environment

NASA Technical Reports Server (NTRS)

Volle, Christopher E. E.

2014-01-01

The purpose of the Simulation Product Group of the Control and Data Systems division of the NASA Engineering branch at Kennedy Space Center is to provide a realtime model and simulation of the Ground Subsystems participating in vehicle launching activities. The simulation software is part of the Spaceport Command and Control System (SCCS) and is designed to support integrated launch operation software verification, and console operator training. Using Mathworks Simulink tools, modeling engineers currently build models from the custom-built blocks to accurately represent ground hardware. This is time consuming and costly due to required rigorous testing and peer reviews to be conducted for each custom-built block. Using Mathworks Simscape tools, modeling time can be reduced since there would be no custom-code developed. After careful research, the group came to the conclusion it is feasible to use Simscape's blocks in MatLab's Simulink. My project this fall was to verify the accuracy of the Crew Access Arm model developed using Simscape tools running in the Simulink development environment.

Engineering Software Suite Validates System Design

NASA Technical Reports Server (NTRS)

2007-01-01

EDAptive Computing Inc.'s (ECI) EDAstar engineering software tool suite, created to capture and validate system design requirements, was significantly funded by NASA's Ames Research Center through five Small Business Innovation Research (SBIR) contracts. These programs specifically developed Syscape, used to capture executable specifications of multi-disciplinary systems, and VectorGen, used to automatically generate tests to ensure system implementations meet specifications. According to the company, the VectorGen tests considerably reduce the time and effort required to validate implementation of components, thereby ensuring their safe and reliable operation. EDASHIELD, an additional product offering from ECI, can be used to diagnose, predict, and correct errors after a system has been deployed using EDASTAR -created models. Initial commercialization for EDASTAR included application by a large prime contractor in a military setting, and customers include various branches within the U.S. Department of Defense, industry giants like the Lockheed Martin Corporation, Science Applications International Corporation, and Ball Aerospace and Technologies Corporation, as well as NASA's Langley and Glenn Research Centers

Some issues related to simulation of the tracking and communications computer network

NASA Technical Reports Server (NTRS)

Lacovara, Robert C.

1989-01-01

The Communications Performance and Integration branch of the Tracking and Communications Division has an ongoing involvement in the simulation of its flight hardware for Space Station Freedom. Specifically, the communication process between central processor(s) and orbital replaceable units (ORU's) is simulated with varying degrees of fidelity. The results of investigations into three aspects of this simulation effort are given. The most general area involves the use of computer assisted software engineering (CASE) tools for this particular simulation. The second area of interest is simulation methods for systems of mixed hardware and software. The final area investigated is the application of simulation methods to one of the proposed computer network protocols for space station, specifically IEEE 802.4.

Some issues related to simulation of the tracking and communications computer network

NASA Astrophysics Data System (ADS)

Lacovara, Robert C.

1989-12-01

The Communications Performance and Integration branch of the Tracking and Communications Division has an ongoing involvement in the simulation of its flight hardware for Space Station Freedom. Specifically, the communication process between central processor(s) and orbital replaceable units (ORU's) is simulated with varying degrees of fidelity. The results of investigations into three aspects of this simulation effort are given. The most general area involves the use of computer assisted software engineering (CASE) tools for this particular simulation. The second area of interest is simulation methods for systems of mixed hardware and software. The final area investigated is the application of simulation methods to one of the proposed computer network protocols for space station, specifically IEEE 802.4.

PyPWA: A partial-wave/amplitude analysis software framework

NASA Astrophysics Data System (ADS)

Salgado, Carlos

2016-05-01

The PyPWA project aims to develop a software framework for Partial Wave and Amplitude Analysis of data; providing the user with software tools to identify resonances from multi-particle final states in photoproduction. Most of the code is written in Python. The software is divided into two main branches: one general-shell where amplitude's parameters (or any parametric model) are to be estimated from the data. This branch also includes software to produce simulated data-sets using the fitted amplitudes. A second branch contains a specific realization of the isobar model (with room to include Deck-type and other isobar model extensions) to perform PWA with an interface into the computer resources at Jefferson Lab. We are currently implementing parallelism and vectorization using the Intel's Xeon Phi family of coprocessors.

Computational and Experimental Evaluation of a Complex Inlet Swirl Pattern Generation System (POSTPRINT)

DTIC Science & Technology

2016-08-01

Sanders, Chase A. Nessler, William W. Copenhaver, Michael G. List, and Timothy J. Janczewski Turbomachinery Branch Turbine Engine Division AUGUST...Branch Turbine Engine Division Turbine Engine Division Aerospace Systems Directorate //Signature// ROBERT D. HANCOCK Principal Scientist Turbine ...ORGANIZATION Turbomachinery Branch Turbine Engine Division Air Force Research Laboratory, Aerospace Systems Directorate Wright-Patterson Air Force

77 FR 40823 - Airworthiness Directives; Airbus Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2012-07-11

... INFORMATION CONTACT: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116, Transport Airplane... International Branch, send it to ATTN: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116...

National Program for Inspection of Non-Federal Dams. Scovill Reservoir Dam (CT 00431), Lower Connecticut River Basin, Haddam, Connecticut. Phase I Inspection Report.

DTIC Science & Technology

1980-01-01

Engineering Branch Engineering Division CARNEY M. TERZIAN, MEMBER Design Branch Engineering Division S, RICHARD DIE O CHIRA Water Control Branch...Associates, P.C. under a letter of 19 October 1979 from William E. Hodgson, Jr., Colonel, Corps of Engineers. Contract No. DACW33-80-C-0001 has been assigned

Towards organ printing: engineering an intra-organ branched vascular tree.

PubMed

Visconti, Richard P; Kasyanov, Vladimir; Gentile, Carmine; Zhang, Jing; Markwald, Roger R; Mironov, Vladimir

2010-03-01

Effective vascularization of thick three-dimensional engineered tissue constructs is a problem in tissue engineering. As in native organs, a tissue-engineered intra-organ vascular tree must be comprised of a network of hierarchically branched vascular segments. Despite this requirement, current tissue-engineering efforts are still focused predominantly on engineering either large-diameter macrovessels or microvascular networks. We present the emerging concept of organ printing or robotic additive biofabrication of an intra-organ branched vascular tree, based on the ability of vascular tissue spheroids to undergo self-assembly. The feasibility and challenges of this robotic biofabrication approach to intra-organ vascularization for tissue engineering based on organ-printing technology using self-assembling vascular tissue spheroids including clinically relevantly vascular cell sources are analyzed. It is not possible to engineer 3D thick tissue or organ constructs without effective vascularization. An effective intra-organ vascular system cannot be built by the simple connection of large-diameter vessels and microvessels. Successful engineering of functional human organs suitable for surgical implantation will require concomitant engineering of a 'built in' intra-organ branched vascular system. Organ printing enables biofabrication of human organ constructs with a 'built in' intra-organ branched vascular tree.

Space Flight Software Development Software for Intelligent System Health Management

NASA Technical Reports Server (NTRS)

Trevino, Luis C.; Crumbley, Tim

2004-01-01

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

Using the Git Software Tool on the Peregrine System | High-Performance

Science.gov Websites

branch workflow. Create a local branch called "experimental" based on the current master... git branch experimental Use your branch (start working on that experimental branch....) git checkout experimental git pull origin experimental # work, work, work, commit.... Send local branch to the repo git push

Black hole thermodynamics and heat engines in conformal gravity

NASA Astrophysics Data System (ADS)

Xu, Hao; Sun, Yuan; Zhao, Liu

The extended phase-space thermodynamics and heat engines for static spherically symmetric black hole solutions of four-dimensional conformal gravity are studied in detail. It is argued that the equation of states (EOS) for such black holes is always branched, any continuous thermodynamical process cannot drive the system from one branch of the EOS into another branch. Meanwhile, the thermodynamical volume is bounded from above, making the black holes always super-entropic in one branch and may also be super-entropic in another branch in certain range of the temperature. The Carnot and Stirling heat engines associated to such black holes are shown to be distinct from each other. For rectangular heat engines, the efficiency always approaches zero when the rectangle becomes extremely narrow, and given the highest and lowest working temperatures fixed, there is always a maximum for the efficiency of such engines.

Internship Abstract - Aerosciences and Flight Mechanics Intern

NASA Technical Reports Server (NTRS)

Rangel, John

2015-01-01

Mars is a hard place to land on, but my internship with NASA's Aerosciences & Flight Mechanics branch has shown me the ways in which men and women will one day land safely. I work on Mars Aerocapture, an aeroassist maneuver that reduces the fuel necessary to "capture" into Martian orbit before a descent. The spacecraft flies through the Martian atmosphere to lose energy through heating before it exits back into space, this time at a slower velocity and in orbit around Mars. Spacecraft will need to maneuver through the Martian atmosphere to accurately hit their orbit, and they will need to survive the generated heat. Engineering teams need simulation data to continue their designs, and the guidance algorithm that ensures a proper orbit insertion needs to be refined - two jobs that fell to me at the summer's start. Engineers within my branch have developed two concept aerocapture vehicles, and I run simulations on their behavior during the maneuver. I also test and refine the guidance algorithm. I spent the first few weeks familiarizing myself with the simulation software, troubleshooting various guidance bugs and writing code. Everything runs smoothly now, and I recently sent my first set of trajectory data to a Thermal Protection System group so they can incorporate it into their heat-bearing material designs. I hope to generate plenty of data in the next few weeks for various engineering groups before my internship ends mid-August. My major accomplishment so far is improving the guidance algorithm. It is a relatively new algorithm that promises higher accuracy and fuel efficiency, but it hasn't undergone extensive testing yet. I've had the opportunity to work with the principal developer - a professor at Iowa State University - to find and fix several issues. I was also assigned the task of expanding the branch's aerodynamic heating simulation software. I am excited to do this because engineers in the future will use my work to generate meaningful data and make design decisions. My internship has taught me to how to teach myself. There are no tutors, study sessions or professor office hours. When I am given an assignment I am expected to figure out how to accomplish it, and I have grown in my problem solving abilities. My summer experience has reinforced my drive to work at NASA, and I can definitely see myself working full time on the aerocapture project, or something similar.

Towards organ printing: engineering an intra-organ branched vascular tree

PubMed Central

Visconti, Richard P; Kasyanov, Vladimir; Gentile, Carmine; Zhang, Jing; Markwald, Roger R; Mironov, Vladimir

2013-01-01

Importance of the field Effective vascularization of thick three-dimensional engineered tissue constructs is a problem in tissue engineering. As in native organs, a tissue-engineered intra-organ vascular tree must be comprised of a network of hierarchically branched vascular segments. Despite this requirement, current tissue-engineering efforts are still focused predominantly on engineering either large-diameter macrovessels or microvascular networks. Areas covered in this review We present the emerging concept of organ printing or robotic additive biofabrication of an intra-organ branched vascular tree, based on the ability of vascular tissue spheroids to undergo self-assembly. What the reader will gain The feasibility and challenges of this robotic biofabrication approach to intra-organ vascularization for tissue engineering based on organ-printing technology using self-assembling vascular tissue spheroids including clinically relevantly vascular cell sources are analyzed. Take home message It is not possible to engineer 3D thick tissue or organ constructs without effective vascularization. An effective intra-organ vascular system cannot be built by the simple connection of large-diameter vessels and microvessels. Successful engineering of functional human organs suitable for surgical implantation will require concomitant engineering of a ‘built in’ intra-organ branched vascular system. Organ printing enables biofabrication of human organ constructs with a ‘built in’ intra-organ branched vascular tree. PMID:20132061

National Program for Inspection of Non-Federal Dams. Millen Lake Dam (NH 00236), NHWRB Number 245.04, Connecticut River Basin, Washington, New Hampshire. Phase I Inspection Report.

DTIC Science & Technology

1980-03-01

Engineering Branch Engineering Division CARNEY M. TERZIAN, KENBER Design Branch Engineering Division RICHARD DIBKO CHIRA Water Control Branch...State of New Hampshire. Authorization and notice to proceed were issued to S E A Consultants Inc. under a letter of November 5, 1979 from William

Modern software approaches applied to a Hydrological model: the GEOtop Open-Source Software Project

NASA Astrophysics Data System (ADS)

Cozzini, Stefano; Endrizzi, Stefano; Cordano, Emanuele; Bertoldi, Giacomo; Dall'Amico, Matteo

2017-04-01

The GEOtop hydrological scientific package is an integrated hydrological model that simulates the heat and water budgets at and below the soil surface. It describes the three-dimensional water flow in the soil and the energy exchange with the atmosphere, considering the radiative and turbulent fluxes. Furthermore, it reproduces the highly non-linear interactions between the water and energy balance during soil freezing and thawing, and simulates the temporal evolution of snow cover, soil temperature and moisture. The core components of the package were presented in the 2.0 version (Endrizzi et al, 2014), which was released as Free Software Open-source project. However, despite the high scientific quality of the project, a modern software engineering approach was still missing. Such weakness hindered its scientific potential and its use both as a standalone package and, more importantly, in an integrate way with other hydrological software tools. In this contribution we present our recent software re-engineering efforts to create a robust and stable scientific software package open to the hydrological community, easily usable by researchers and experts, and interoperable with other packages. The activity takes as a starting point the 2.0 version, scientifically tested and published. This version, together with several test cases based on recent published or available GEOtop applications (Cordano and Rigon, 2013, WRR, Kollet et al, 2016, WRR) provides the baseline code and a certain number of referenced results as benchmark. Comparison and scientific validation can then be performed for each software re-engineering activity performed on the package. To keep track of any single change the package is published on its own github repository geotopmodel.github.io/geotop/ under GPL v3.0 license. A Continuous Integration mechanism by means of Travis-CI has been enabled on the github repository on master and main development branches. The usage of CMake configuration tool and the suite of tests (easily manageable by means of ctest tools) greatly reduces the burden of the installation and allows us to enhance portability on different compilers and Operating system platforms. The package was also complemented by several software tools which provide web-based visualization of results based on R plugins, in particular "shiny" (Chang at al, 2016), "geotopbricks" and "geotopOptim2" (Cordano et al, 2016) packages, which allow rapid and efficient scientific validation of new examples and tests. The software re-engineering activities are still under development. However, our first results are promising enough to eventually reach a robust and stable software project that manages in a flexible way a complex state-of-the-art hydrological model like GEOtop and integrates it into wider workflows.

Doppler Lidar System Design via Interdisciplinary Design Concept at NASA Langley Research Center - Part II

NASA Technical Reports Server (NTRS)

Crasner, Aaron I.; Scola,Salvatore; Beyon, Jeffrey Y.; Petway, Larry B.

2014-01-01

Optimized designs of the Navigation Doppler Lidar (NDL) instrument for Autonomous Landing Hazard Avoidance Technology (ALHAT) were accomplished via Interdisciplinary Design Concept (IDEC) at NASA Langley Research Center during the summer of 2013. Three branches in the Engineering Directorate and three students were involved in this joint task through the NASA Langley Aerospace Research Summer Scholars (LARSS) Program. The Laser Remote Sensing Branch (LRSB), Mechanical Systems Branch (MSB), and Structural and Thermal Systems Branch (STSB) were engaged to achieve optimal designs through iterative and interactive collaborative design processes. A preliminary design iteration was able to reduce the power consumption, mass, and footprint by removing redundant components and replacing inefficient components with more efficient ones. A second design iteration reduced volume and mass by replacing bulky components with excessive performance with smaller components custom-designed for the power system. Thermal modeling software was used to run steady state thermal analyses, which were used to both validate the designs and recommend further changes. Analyses were run on each redesign, as well as the original system. Thermal Desktop was used to run trade studies to account for uncertainty and assumptions about fan performance and boundary conditions. The studies suggested that, even if the assumptions were significantly wrong, the redesigned systems would remain within operating temperature limits.

Protection of Mobile Agents Execution Using a Modified Self-Validating Branch-Based Software Watermarking with External Sentinel

NASA Astrophysics Data System (ADS)

Tomàs-Buliart, Joan; Fernández, Marcel; Soriano, Miguel

Critical infrastructures are usually controlled by software entities. To monitor the well-function of these entities, a solution based in the use of mobile agents is proposed. Some proposals to detect modifications of mobile agents, as digital signature of code, exist but they are oriented to protect software against modification or to verify that an agent have been executed correctly. The aim of our proposal is to guarantee that the software is being executed correctly by a non trusted host. The way proposed to achieve this objective is by the improvement of the Self-Validating Branch-Based Software Watermarking by Myles et al.. The proposed modification is the incorporation of an external element called sentinel which controls branch targets. This technique applied in mobile agents can guarantee the correct operation of an agent or, at least, can detect suspicious behaviours of a malicious host during the execution of the agent instead of detecting when the execution of the agent have finished.

77 FR 34283 - Airworthiness Directives; Airbus Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2012-06-11

... after receipt. FOR FURTHER INFORMATION CONTACT: Sanjay Ralhan, Aerospace Engineer, International Branch... it to ATTN: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116, Transport Airplane...

76 FR 46701 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-08-03

..., identified by Docket No. FEMA-B-1207, to Luis Rodriguez, Chief, Engineering Management Branch, Federal... Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal...

Demonstration of Novel Sampling Techniques for Measurement of Turbine Engine Volatile and Non-Volatile Particulate Matter (PM) Emissions

DTIC Science & Technology

2016-09-01

AFRL-RQ-WP-TR-2016-0131 DEMONSTRATION OF NOVEL SAMPLING TECHNIQUES FOR MEASUREMENT OF TURBINE ENGINE VOLATILE AND NON-VOLATILE PARTICULATE...MATTER (PM) EMISSIONS Edwin Corporan Fuels and Energy Branch Turbine Engine Division Matthew DeWitt and Chris Klingshirn University of...Energy Branch Turbine Engine Division Turbine Engine Division Aerospace Systems Directorate //Signature// CHARLES W. STEVENS Lead Engineer

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.

Supporting Development of Satellite's Guidance Navigation and Control Software: A Product Line Approach

NASA Technical Reports Server (NTRS)

McComas, David; Stark, Michael; Leake, Stephen; White, Michael; Morisio, Maurizio; Travassos, Guilherme H.; Powers, Edward I. (Technical Monitor)

2000-01-01

The NASA Goddard Space Flight Center Flight Software Branch (FSB) is developing a Guidance, Navigation, and Control (GNC) Flight Software (FSW) product line. The demand for increasingly more complex flight software in less time while maintaining the same level of quality has motivated us to look for better FSW development strategies. The GNC FSW product line has been planned to address the core GNC FSW functionality very similar on many recent low/near Earth missions in the last ten years. Unfortunately these missions have not accomplished significant drops in development cost since a systematic approach towards reuse has not been adopted. In addition, new demands are continually being placed upon the FSW which means the FSB must become more adept at providing GNC FSW functionality's core so it can accommodate additional requirements. These domain features together with engineering concepts are influencing the specification, description and evaluation of FSW product line. Domain engineering is the foundation for emerging product line software development approaches. A product line is 'A family of products designed to take advantage of their common aspects and predicted variabilities'. In our product line approach, domain engineering includes the engineering activities needed to produce reusable artifacts for a domain. Application engineering refers to developing an application in the domain starting from reusable artifacts. The focus of this paper is regarding the software process, lessons learned and on how the GNC FSW product line manages variability. Existing domain engineering approaches do not enforce any specific notation for domain analysis or commonality and variability analysis. Usually, natural language text is the preferred tool. The advantage is the flexibility and adapt ability of natural language. However, one has to be ready to accept also its well-known drawbacks, such as ambiguity, inconsistency, and contradictions. While most domain analysis approaches are functionally oriented, the idea of applying the object-oriented approach in domain analysis is not new. Some authors propose to use UML as the notation underlying domain analysis. Our work is based on the same idea of merging UML and domain analysis. Further, we propose a few extensions to UML in order to express variability, and we define precisely their semantics so that a tool can support them. The extensions are designed to be implemented on the API of a popular industrial CASE tool, with obvious advantages in cost and availability of tool support. The paper outlines the product line processes and identifies where variability must be addressed. Then it describes the product line products with respect to how they accommodate variability. The Celestial Body subdomain is used as a working example. Our results to date are summarized and plans for the future are described.

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.

Integration of MSFC Usability Lab with Usability Testing

NASA Technical Reports Server (NTRS)

Cheng, Yiwei; Richardson, Sally

2010-01-01

As part of the Stage Analysis Branch, human factors engineering plays an important role in relating humans to the systems of hardware and structure designs of the new launch vehicle. While many branches are involved in the technical aspects of creating a launch vehicle, human factors connects humans to the scientific systems with the goal of improving operational performance and safety while reducing operational error and damage to the hardware. Human factors engineers use physical and computerized models to visualize possible areas for improvements to ensure human accessibility to components requiring maintenance and that the necessary maintenance activities can be accomplished with minimal risks to human and hardware. Many methods of testing are used to fulfill this goal, such as physical mockups, computerized visualization, and usability testing. In this analysis, a usability test is conducted to test how usable a website is to users who are and are not familiar with it. The testing is performed using participants and Morae software to record and analyze the results. This analysis will be a preliminary test of the usability lab in preparation for use in new spacecraft programs, NASA Enterprise, or other NASA websites. The usability lab project is divided into two parts: integration of the usability lab and a preliminary test of the usability lab.

EM-1 Countdown Simulation with Charlie Blackwell-Thompson

NASA Image and Video Library

2018-03-29

NASA Launch Director Charlie Blackwell-Thompson, center, stands next to her console in Firing Room 1 at the Kennedy Space Center's Launch Control Center. With her, from the left, are NASA intern Justin Connolly, NASA Engineering Project Manager Dan Tran, Blackwell-Thompson, Shawn Reverter, Project Manager for Red Canyon Software, Inc., and NASA Structures and Mechanisms Design Branch Chief Adam Dokos, during a countdown simulation for Exploration Mission 1. It was the agency's first simulation of a portion of the countdown for the first launch of a Space Launch System rocket and Orion spacecraft that will eventually take astronauts beyond low-Earth orbit to destinations such as the Moon and Mars.

78 FR 28128 - Airworthiness Directives; the Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2013-05-14

...., Washington, DC 20590. FOR FURTHER INFORMATION CONTACT: Sue Lucier, Aerospace Engineer, Propulsion Branch, ANM... Lucier, Aerospace Engineer, Propulsion Branch, ANM-140S, Seattle Aircraft Certification Office, FAA, 1601...

77 FR 16432 - Airworthiness Directives; Cessna Aircraft Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2012-03-21

... CONTACT: David Fairback, Aerospace Engineer, Mechanical Systems and Propulsion Branch, ACE-116W, FAA... Fairback, Aerospace Engineer, Mechanical Systems and Propulsion Branch, ACE- 116W, FAA, Wichita Aircraft...

76 FR 82111 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2011-12-30

.... FOR FURTHER INFORMATION CONTACT: Chris Parker, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA... Information For more information about this AD, contact Chris Parker, Aerospace Engineer, Propulsion Branch...

75 FR 31329 - Airworthiness Directives; The Boeing Company Model 757 Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2010-06-03

... after receipt. FOR FURTHER INFORMATION CONTACT: Tak Kobayashi, Aerospace Engineer, Propulsion Branch..., Aerospace Engineer, Propulsion Branch, ANM- 140S, FAA, Seattle Aircraft Certification Office, 1601 Lind...

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.

76 FR 19714 - Airworthiness Directives; Airbus Model A320-214, -232, and -233 Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2011-04-08

... after receipt. FOR FURTHER INFORMATION CONTACT: Sanjay Ralhan, Aerospace Engineer, International Branch... ATTN: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116, Transport Airplane Directorate...

75 FR 61352 - Airworthiness Directives; McDonnell Douglas Corporation Model DC-10-30, DC-10-30F, DC-10-30F (KC...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-10-05

...: Samuel Lee, Aerospace Engineer, Propulsion Branch, ANM-140L, FAA, Los Angeles Aircraft Certification... procedures found in 14 CFR 39.19. Send information to ATTN: Samuel Lee, Aerospace Engineer, Propulsion Branch..., Propulsion Branch, ANM-140L, FAA, Los Angeles Aircraft Certification Office, 3960 Paramount Boulevard...

75 FR 47197 - Airworthiness Directives; Schweizer Aircraft Corporation (Schweizer) Model 269D Helicopters

Federal Register 2010, 2011, 2012, 2013, 2014

2010-08-05

..., Aviation Safety Engineer, FAA, New York Aircraft Certification Office, Airframe and Propulsion Branch, 1600..., Aerospace Engineer, Aviation Safety Engineer, FAA, New York Aircraft Certification Office, Airframe and Propulsion Branch, 1600 Stewart Ave., suite 410, Westbury, New York 11590, telephone (516) 228-7304, fax (516...

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.

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.

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.

76 FR 6535 - Airworthiness Directives; The Boeing Company Model MD-90-30 Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2011-02-07

.... FOR FURTHER INFORMATION CONTACT: William S. Bond, Aerospace Engineer, Propulsion Branch, ANM-140L, FAA..., contact William S. Bond, Aerospace Engineer, Propulsion Branch, ANM-140L, FAA, Los Angeles Aircraft...

Side branch absorber for exhaust manifold of two-stroke internal combustion engine

DOEpatents

Harris, Ralph E [San Antonio, TX; Broerman, III, Eugene L.; Bourn, Gary D [Laramie, WY

2011-01-11

A method of improving scavenging operation of a two-stroke internal combustion engine. The exhaust pressure of the engine is analyzed to determine if there is a pulsation frequency. Acoustic modeling is used to design an absorber. An appropriately designed side branch absorber may be attached to the exhaust manifold.

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.

Influence of gender in choosing a career amongst engineering fields: a survey study from Turkey

NASA Astrophysics Data System (ADS)

Bucak, Seyda; Kadirgan, Neset

2011-10-01

The aim of this study is to understand the motivating factors behind students' choices in their decision-making process and also get an insight on their perception of different engineering branches. A survey was prepared and the results were evaluated amongst 1163 answers. Two major influences on student's decision in their professional choices are shown to be career services and family members. Generally, students have claimed to choose a profession based on 'finding a job' and 'being happy'. Some engineering branches such as Genetic and Bioengineering, Chemical Engineering, Environmental Engineering and Industrial Engineering, are shown to be distinctly preferred by female students, whereas mechanical, civil and electronic engineering are favourites for male students. The survey results were also compared with the distribution of male and female students in various engineering departments. This study clearly shows that certain engineering branches are perceived as more appropriate for women and are thus favoured by female students, while those perceived as more appropriate for men are favoured by male students.

76 FR 38332 - Airworthiness Directives; The Boeing Company Model MD-11 and MD-11F Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2011-06-30

... Engineer, Propulsion Branch, ANM-140L, FAA, Los Angeles Aircraft Certification Office, 3960 Paramount..., Aerospace Engineer, Propulsion Branch, ANM-140L, FAA, Los Angeles ACO, 3960 Paramount Boulevard, Lakewood...

76 FR 21693 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-04-18

... Creek, Union Grove Industrial Tributary, Unnamed Tributary No. 18 to Kilbourn Road Ditch, Unnamed...- 7755, to Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation..., Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal Emergency Management...

Protein engineering and its applications in food industry.

PubMed

Kapoor, Swati; Rafiq, Aasima; Sharma, Savita

2017-07-24

Protein engineering is a young discipline that has been branched out from the field of genetic engineering. Protein engineering is based on the available knowledge about the proteins structure/function(s), tools/instruments, software, bioinformatics database, available cloned gene, knowledge about available protein, vectors, recombinant strains and other materials that could lead to change in the protein backbone. Protein produced properly from genetic engineering process means a protein that is able to fold correctly and to do particular function(s) efficiently even after being subjected to engineering practices. Protein is modified through its gene or chemically. However, modification of protein through gene is easier. There is no specific limitation of Protein Engineering tools; any technique that can lead to change the protein constituent of amino acid and result in the modification of protein structure/function is in the frame of Protein Engineering. Meanwhile, there are some common tools used to reach a specific target. More active industrial and pharmaceutical based proteins have been invented by the field of Protein Engineering to introduce new function as well as to change its interaction with surrounding environment. A variety of protein engineering applications have been reported in the literature. These applications range from biocatalysis for food and industry to environmental, medical and nanobiotechnology applications. Successful combinations of various protein engineering methods had led to successful results in food industries and have created a scope to maintain the quality of finished product after processing.

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 for Aerospace Education. A Bibliography (Second Edition).

ERIC Educational Resources Information Center

Vogt, Gregory L.; And Others

The software described in this bibliography represents programs made available to the National Aeronautics and Space Administration (NASA) Educational Technology Branch by software producers and vendors. More than 200 computer software programs and 12 laser videodisk programs are reviewed in terms of title, copyright, subject, application, type,…

Practical Pocket PC Application w/Biometric Security

NASA Technical Reports Server (NTRS)

Logan, Julian

2004-01-01

I work in the Flight Software Engineering Branch, where we provide design and development of embedded real-time software applications for flight and supporting ground systems to support the NASA Aeronautics and Space Programs. In addition, this branch evaluates, develops and implements new technologies for embedded real-time systems, and maintains a laboratory for applications of embedded technology. The majority of microchips that are used in modern society have been programmed using embedded technology. These small chips can be found in microwaves, calculators, home security systems, cell phones and more. My assignment this summer entails working with an iPAQ HP 5500 Pocket PC. This top-of-the-line hand-held device is one of the first mobile PC's to introduce biometric security capabilities. Biometric security, in this case a fingerprint authentication system, is on the edge of technology as far as securing information. The benefits of fingerprint authentication are enormous. The most significant of them are that it is extremely difficult to reproduce someone else's fingerprint, and it is equally difficult to lose or forget your own fingerprint as opposed to a password or pin number. One of my goals for this summer is to integrate this technology with another Pocket PC application. The second task for the summer is to develop a simple application that provides an Astronaut EVA (Extravehicular Activity) Log Book capability. The Astronaut EVA Log Book is what an astronaut would use to report the status of field missions, crew physical health, successes, future plans, etc. My goal is to develop a user interface into which these data fields can be entered and stored. The applications that I am developing are created using eMbedded Visual C++ 4.0 with the Pocket PC 2003 Software Development Kit provided by Microsoft.

High Bypass Turbofan Component Development. Amendment I. Small Fan Redesign.

DTIC Science & Technology

1980-02-01

A0A89 67 BENRAL EECTRIC CO LYNN MA AIRCRAFT ENGINE GROUP P’S 21 5 HIGH BYPASS TURBOFAN COMPONENT DEVELOPMENT. AMENDMENT I. SMALL -ETC(U) FEB 80 H...Weldon Aircraft Engine Group S General Electric Co. Lynn, Massachusetts 01910 0 February 1980 DTC Technical Report AF.AL-TR-80-2011 Final Report for...LARRY W.4ILL, CAPT, USAF ERIK W. LINDNER, TAM Project Engineer Special Engines Performance Branch Performance Branch Turbine Engine Division FOR THE

A Procedure for Structural Weight Estimation of Single Stage to Orbit Launch Vehicles (Interim User's Manual)

NASA Technical Reports Server (NTRS)

Martinovic, Zoran N.; Cerro, Jeffrey A.

2002-01-01

This is an interim user's manual for current procedures used in the Vehicle Analysis Branch at NASA Langley Research Center, Hampton, Virginia, for launch vehicle structural subsystem weight estimation based on finite element modeling and structural analysis. The process is intended to complement traditional methods of conceptual and early preliminary structural design such as the application of empirical weight estimation or application of classical engineering design equations and criteria on one dimensional "line" models. Functions of two commercially available software codes are coupled together. Vehicle modeling and analysis are done using SDRC/I-DEAS, and structural sizing is performed with the Collier Research Corp. HyperSizer program.

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.

Kodiak: An Implementation Framework for Branch and Bound Algorithms

NASA Technical Reports Server (NTRS)

Smith, Andrew P.; Munoz, Cesar A.; Narkawicz, Anthony J.; Markevicius, Mantas

2015-01-01

Recursive branch and bound algorithms are often used to refine and isolate solutions to several classes of global optimization problems. A rigorous computation framework for the solution of systems of equations and inequalities involving nonlinear real arithmetic over hyper-rectangular variable and parameter domains is presented. It is derived from a generic branch and bound algorithm that has been formally verified, and utilizes self-validating enclosure methods, namely interval arithmetic and, for polynomials and rational functions, Bernstein expansion. Since bounds computed by these enclosure methods are sound, this approach may be used reliably in software verification tools. Advantage is taken of the partial derivatives of the constraint functions involved in the system, firstly to reduce the branching factor by the use of bisection heuristics and secondly to permit the computation of bifurcation sets for systems of ordinary differential equations. The associated software development, Kodiak, is presented, along with examples of three different branch and bound problem types it implements.

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.

76 FR 26976 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-05-10

..., identified by Docket No. FEMA-B-1193, to Luis Rodriguez, Chief, Engineering Management Branch, Federal... Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal... Order 12988, Civil Justice Reform. This proposed rule meets the applicable standards of Executive Order...

75 FR 78647 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2010-12-16

..., identified by Docket No. FEMA-B-1163, to Luis Rodriguez, Chief, Engineering Management Branch, Federal... Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal.... Executive Order 12988, Civil Justice Reform. This proposed rule meets the applicable standards of Executive...

76 FR 3590 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-01-20

..., identified by Docket No. FEMA-B-1171, to Luis Rodriguez, Chief, Engineering Management Branch, Federal... Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal..., Civil Justice Reform. This proposed rule meets the applicable standards of Executive Order 12988. List...

76 FR 59960 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-09-28

..., identified by Docket No. FEMA-B-1220, to Luis Rodriguez, Chief, Engineering Management Branch, Federal... Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal..., Civil Justice Reform. This proposed rule meets the applicable standards of Executive Order 12988. [[Page...

76 FR 19018 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-04-06

..., identified by Docket No. FEMA-B-1179, to Luis Rodriguez, Chief, Engineering Management Branch, Federal... Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal..., Civil Justice Reform. This proposed rule meets the applicable standards of Executive Order 12988. List...

76 FR 19005 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-04-06

..., identified by Docket No. FEMA-B-1187, to Luis Rodriguez, Chief, Engineering Management Branch, Federal... Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration, Federal..., Civil Justice Reform. This proposed rule meets the applicable standards of Executive Order 12988. List...

75 FR 5909 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2010-02-05

..., identified by Docket No. FEMA-B-1085, to Kevin C. Long, Acting Chief, Engineering Management Branch... Chief, Engineering Management Branch, Mitigation Directorate, Federal Emergency Management Agency, 500 C... federalism implications under Executive Order 13132. Executive Order 12988, Civil Justice Reform. This...

75 FR 31373 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2010-06-03

..., identified by Docket No. FEMA-B-1105, to Kevin C. Long, Acting Chief, Engineering Management Branch... Chief, Engineering Management Branch, Mitigation Directorate, Federal Emergency Management Agency, 500 C... federalism implications under Executive Order 13132. Executive Order 12988, Civil Justice Reform. This...

75 FR 34415 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2010-06-17

..., identified by Docket No. FEMA-B-1114, to Kevin C. Long, Acting Chief, Engineering Management Branch... Chief, Engineering Management Branch, Mitigation Directorate, Federal Emergency Management Agency, 500 C... federalism implications under Executive Order 13132. Executive Order 12988, Civil Justice Reform. This...

76 FR 66887 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2011-10-28

..., identified by Docket No. FEMA-B-1226, to Luis Rodriguez, Chief, Engineering Management Branch, Federal...: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration..., Civil Justice Reform. This proposed rule meets the applicable standards of Executive Order 12988. [[Page...

75 FR 70044 - Withdrawal of Regulatory Guide 1.39

Federal Register 2010, 2011, 2012, 2013, 2014

2010-11-16

...: Hector L. Rodriguez-Luccioni, Regulatory Guide Development Branch, Division of Engineering, Office of...-251-7685 or e-mail [email protected] . SUPPLEMENTARY INFORMATION: I. Introduction The... N. Ridgely, Acting Chief, Regulatory Guide Development Branch, Division of Engineering, Office of...

Implementation of NASA Materials and Processes Requirements at the Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Powers, Charles E.

2009-01-01

This slide presentation reviews the history and current practices of the Materials Engineering Branch (MEB) at the Goddard Space Flight Center. Included in the presentation is a review of the general Materials and Processes (M&P) requirements in the NASA-STD-6016. The work that the Materials Engineering Branch does to support GSFC Projects is also reviewed. The Materials Engineering Branch capabilities are listed, the expertise that is available to GSFC projects is also listed. Included in the backup slides are forms that the MEB uses to identify the materials in the spacecraft under development.

Structural Mechanics and Dynamics Branch

NASA Technical Reports Server (NTRS)

Stefko, George

2003-01-01

The 2002 annual report of the Structural Mechanics and Dynamics Branch reflects the majority of the work performed by the branch staff during the 2002 calendar year. Its purpose is to give a brief review of the branch s technical accomplishments. The Structural Mechanics and Dynamics Branch develops innovative computational tools, benchmark experimental data, and solutions to long-term barrier problems in the areas of propulsion aeroelasticity, active and passive damping, engine vibration control, rotor dynamics, magnetic suspension, structural mechanics, probabilistics, smart structures, engine system dynamics, and engine containment. Furthermore, the branch is developing a compact, nonpolluting, bearingless electric machine with electric power supplied by fuel cells for future "more electric" aircraft. An ultra-high-power-density machine that can generate projected power densities of 50 hp/lb or more, in comparison to conventional electric machines, which generate usually 0.2 hp/lb, is under development for application to electric drives for propulsive fans or propellers. In the future, propulsion and power systems will need to be lighter, to operate at higher temperatures, and to be more reliable in order to achieve higher performance and economic viability. The Structural Mechanics and Dynamics Branch is working to achieve these complex, challenging goals.

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

Concise review: can the intrinsic power of branching morphogenesis be used for engineering epithelial tissues and organs?

PubMed

Nigam, Sanjay K

2013-12-01

Branching morphogenesis is critical to the development of organs such as kidney, lung, mammary gland, prostate, pancreas, and salivary gland. Essentially, an epithelial bud becomes an iterative tip-stalk generator (ITSG) able to form a tree of branching ducts and/or tubules. In different organs, branching morphogenesis is governed by similar sets of genes. Epithelial branching has been recapitulated in vitro (or ex vivo) using three-dimensional cell culture and partial organ culture systems, and several such systems relevant to kidney tissue engineering are discussed here. By adapting systems like these it may be possible to harness the power inherent in the ITSG program to propagate and engineer epithelial tissues and organs. It is also possible to conceive of a universal ITSG capable of propagation that may, by recombination with organ-specific mesenchymal cells, be used for engineering many organ-like tissues similar to the organ from which the mesenchyme cells were derived, or toward which they are differentiated (from stem cells). The three-dimensional (3D) branched epithelial structure could act as a dynamic branching cellular scaffold to establish the architecture for the rest of the tissue. Another strategy-that of recombining propagated organ-specific ITSGs in 3D culture with undifferentiated mesenchymal stem cells-is also worth exploring. If feasible, such engineered tissues may be useful for the ex vivo study of drug toxicity, developmental biology, and physiology in the laboratory. Over the long term, they have potential clinical applications in the general fields of transplantation, regenerative medicine, and bioartificial medical devices to aid in the treatment of chronic kidney disease, diabetes, and other diseases.

The Specific Features of design and process engineering in branch of industrial enterprise

NASA Astrophysics Data System (ADS)

Sosedko, V. V.; Yanishevskaya, A. G.

2017-06-01

Production output of industrial enterprise is organized in debugged working mechanisms at each stage of product’s life cycle from initial design documentation to product and finishing it with utilization. The topic of article is mathematical model of the system design and process engineering in branch of the industrial enterprise, statistical processing of estimated implementation results of developed mathematical model in branch, and demonstration of advantages at application at this enterprise. During the creation of model a data flow about driving of information, orders, details and modules in branch of enterprise groups of divisions were classified. Proceeding from the analysis of divisions activity, a data flow, details and documents the state graph of design and process engineering was constructed, transitions were described and coefficients are appropriated. To each condition of system of the constructed state graph the corresponding limiting state probabilities were defined, and also Kolmogorov’s equations are worked out. When integration of sets of equations of Kolmogorov the state probability of system activity the specified divisions and production as function of time in each instant is defined. On the basis of developed mathematical model of uniform system of designing and process engineering and manufacture, and a state graph by authors statistical processing the application of mathematical model results was carried out, and also advantage at application at this enterprise is shown. Researches on studying of loading services probability of branch and third-party contractors (the orders received from branch within a month) were conducted. The developed mathematical model of system design and process engineering and manufacture can be applied to definition of activity state probability of divisions and manufacture as function of time in each instant that will allow to keep account of loading of performance of work in branches of the enterprise.

78 FR 21279 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2013-04-10

... (1) For more information about this AD, contact Suzanne Lucier, Aerospace Engineer, Propulsion Branch... the AD docket shortly after receipt. FOR FURTHER INFORMATION CONTACT: Suzanne Lucier, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue SW...

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.

Improving the Capture and Re-Use of Data with Wearable Computers

NASA Technical Reports Server (NTRS)

Pfarr, Barbara; Fating, Curtis C.; Green, Daniel; Powers, Edward I. (Technical Monitor)

2001-01-01

At the Goddard Space Flight Center, members of the Real-Time Software Engineering Branch are developing a wearable, wireless, voice-activated computer for use in a wide range of crosscutting space applications that would benefit from having instant Internet, network, and computer access with complete mobility and hands-free operations. These applications can be applied across many fields and disciplines including spacecraft fabrication, integration and testing (including environmental testing), and astronaut on-orbit control and monitoring of experiments with ground based experimenters. To satisfy the needs of NASA customers, this wearable computer needs to be connected to a wireless network, to transmit and receive real-time video over the network, and to receive updated documents via the Internet or NASA servers. The voice-activated computer, with a unique vocabulary, will allow the users to access documentation in a hands free environment and interact in real-time with remote users. We will discuss wearable computer development, hardware and software issues, wireless network limitations, video/audio solutions and difficulties in language development.

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.

Compressor Research Facility F100 High Pressure Compressor Inlet Total Pressure and Swirl Profile Simulation.

DTIC Science & Technology

1984-10-01

SECTION I INTRODUCTION 1. GENERAL -.The F100 gas turbine engine currently powers the Air Force F-15 and F-16 aircraft . The compression section of this... Aircraft in designing these vanes and screens to provide the measured engine profiles. lata acquisition system was defined and transported to Pratt and...WILLIAM W. COEHVRWALKER H. MITCHELL Compressor Test Group Chief, Technology Branch Technology Branch Turbine Engine Division Turbine Engine Division

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.

78 FR 42415 - Airworthiness Directives; the Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2013-07-16

... INFORMATION CONTACT: Suzanne Lucier, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft... Lucier, Aerospace Engineer, Propulsion Branch, ANM-140S, FAA, Seattle Aircraft Certification Office, 1601... 737-28-1286, dated January 10, 2012. (d) Subject Joint Aircraft System Component (JASC)/Air Transport...

76 FR 76066 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2011-12-06

... Sutherland, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle Aircraft Certification Office, 1601...: james.sutherland@faa.gov . SUPPLEMENTARY INFORMATION: Comments Invited We invite you to send any written... about this AD, contact James Sutherland, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle...

77 FR 32889 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2012-06-04

...., Washington, DC 20590. FOR FURTHER INFORMATION CONTACT: James Sutherland, Aerospace Engineer, Airframe Branch... 98057-3356; phone: 425- 917-6533; fax: 425-917-6590; email: James.Sutherland@faa.gov . SUPPLEMENTARY... more information about this AD, contact James Sutherland, Aerospace Engineer, Airframe Branch, ANM-120S...

77 FR 42962 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2012-07-23

... INFORMATION CONTACT: James Sutherland, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle Aircraft...-6590; email: James.Sutherland@faa.gov . SUPPLEMENTARY INFORMATION: Discussion We issued a notice of... this AD, contact James Sutherland, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle Aircraft...

75 FR 37842 - Notice of Issuance of Regulatory Guide

Federal Register 2010, 2011, 2012, 2013, 2014

2010-06-30

... INFORMATION CONTACT: R. A. Jervey, Regulatory Guide Development Branch, Division of Engineering, Office of...) 251-7404 or e-mail [email protected] . SUPPLEMENTARY INFORMATION: I. Introduction The U.S. Nuclear..., Regulatory Guide Development Branch, Division of Engineering, Office of Nuclear Regulatory Research. [FR Doc...

77 FR 39721 - Proposed Flood Hazard Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2012-07-05

..., identified by Docket No. FEMA-B-1256, to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., Engineering Management Branch, Federal Insurance and Mitigation Administration, FEMA, 500 C Street SW..., 2040 Hay Terrace, Easton, PA 18042. Borough of Wind Gap Borough Offices, 29 Mechanic Street, Wind Gap...

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.

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.

NCEP BUFRLIB Software User Guide

Science.gov Websites

Integration Branch > Decoders > BUFRLIB BUFRLIB Software User Guide This document set describes how to use the NCEP BUFRLIB software to encode or decode BUFR messages. It is not intended to be a primer on background knowledge of the basic concepts of BUFR and will focus solely on how to use the BUFRLIB software

Validation of CFD/Heat Transfer Software for Turbine Blade Analysis

NASA Technical Reports Server (NTRS)

Kiefer, Walter D.

2004-01-01

I am an intern in the Turbine Branch of the Turbomachinery and Propulsion Systems Division. The division is primarily concerned with experimental and computational methods of calculating heat transfer effects of turbine blades during operation in jet engines and land-based power systems. These include modeling flow in internal cooling passages and film cooling, as well as calculating heat flux and peak temperatures to ensure safe and efficient operation. The branch is research-oriented, emphasizing the development of tools that may be used by gas turbine designers in industry. The branch has been developing a computational fluid dynamics (CFD) and heat transfer code called GlennHT to achieve the computational end of this analysis. The code was originally written in FORTRAN 77 and run on Silicon Graphics machines. However the code has been rewritten and compiled in FORTRAN 90 to take advantage of more modem computer memory systems. In addition the branch has made a switch in system architectures from SGI's to Linux PC's. The newly modified code therefore needs to be tested and validated. This is the primary goal of my internship. To validate the GlennHT code, it must be run using benchmark fluid mechanics and heat transfer test cases, for which there are either analytical solutions or widely accepted experimental data. From the solutions generated by the code, comparisons can be made to the correct solutions to establish the accuracy of the code. To design and create these test cases, there are many steps and programs that must be used. Before a test case can be run, pre-processing steps must be accomplished. These include generating a grid to describe the geometry, using a software package called GridPro. Also various files required by the GlennHT code must be created including a boundary condition file, a file for multi-processor computing, and a file to describe problem and algorithm parameters. A good deal of this internship will be to become familiar with these programs and the structure of the GlennHT code. Additional information is included in the original extended abstract.

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.

78 FR 29696 - Proposed Flood Elevation Determinations for Lake County, Illinois, and Incorporated Areas

Federal Register 2010, 2011, 2012, 2013, 2014

2013-05-21

..., identified by Docket No. FEMA-B- 1196, to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

78 FR 28780 - Proposed Flood Elevation Determinations for Greene County, Pennsylvania (All Jurisdictions)

Federal Register 2010, 2011, 2012, 2013, 2014

2013-05-16

..., identified by Docket No. FEMA-B- 1190 to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

77 FR 65843 - Proposed Flood Elevation Determinations for Montgomery County, Alabama and Incorporated Areas

Federal Register 2010, 2011, 2012, 2013, 2014

2012-10-31

..., identified by Docket No. FEMA-B- 1223, to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

78 FR 75542 - Proposed Flood Elevation Determinations for Fayette County, Pennsylvania (All Jurisdictions)

Federal Register 2010, 2011, 2012, 2013, 2014

2013-12-12

..., identified by Docket No. FEMA-B- 1147 to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

77 FR 66791 - Proposed Flood Elevation Determinations for Yakima County, WA, and Incorporated Areas

Federal Register 2010, 2011, 2012, 2013, 2014

2012-11-07

..., identified by Docket No. FEMA-B- 1233, to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

78 FR 28779 - Proposed Flood Elevation Determinations for Armstrong County, Pennsylvania (All Jurisdictions)

Federal Register 2010, 2011, 2012, 2013, 2014

2013-05-16

..., identified by Docket No. FEMA-B- 1152 to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

78 FR 28780 - Proposed Flood Elevation Determinations for Beaver County, Pennsylvania (All Jurisdictions)

Federal Register 2010, 2011, 2012, 2013, 2014

2013-05-16

..., identified by Docket No. FEMA-B- 1147 to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

77 FR 55787 - Proposed Flood Elevation Determinations for Hampden County, MA, and Incorporated Areas

Federal Register 2010, 2011, 2012, 2013, 2014

2012-09-11

... comments, identified by Docket No. FEMA-B- 1066, to Luis Rodriguez, Chief, Engineering Management Branch...., Washington, DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation...

77 FR 55787 - Proposed Flood Elevation Determinations for Clay County, FL, and Incorporated Areas

Federal Register 2010, 2011, 2012, 2013, 2014

2012-09-11

..., identified by Docket No. FEMA-B- 1222, to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

77 FR 76998 - Proposed Flood Elevation Determinations for Nobles County, MN, and Incorporated Areas

Federal Register 2010, 2011, 2012, 2013, 2014

2012-12-31

..., identified by Docket No. FEMA-B- 1184, to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation Administration...

National Program for Inspection of Non-Federal Dams. Collins Company Upper Dam (CT 00674), Connecticut River Basin, Canton, Connecticut. Phase I Inspection Report.

DTIC Science & Technology

1979-07-01

Engineering Division p 0 CAR WE H FRZIAN, NENBER Design Branch Engineering Division J SEPE FIN~EGAN, JR.,CIV ater Control Branch * Engineering Division...Operator g. Purpose of Dam h. Design and Construction History i. Normal Operational Procedures 1.3 PERTINENT DATA ........................... 4 a...Tunnel i. Spillways j. Regulating Outlets SECTION 2: ENGINEERING DATA 2.1 DESIGN .............................. 9 a. Available Data b. Design Features c

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.

Teaching Agile Software Engineering Using Problem-Based Learning

ERIC Educational Resources Information Center

El-Khalili, Nuha H.

2013-01-01

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

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…

Geographic Information Systems and Web Page Development

NASA Technical Reports Server (NTRS)

Reynolds, Justin

2004-01-01

The Facilities Engineering and Architectural Branch is responsible for the design and maintenance of buildings, laboratories, and civil structures. In order to improve efficiency and quality, the FEAB has dedicated itself to establishing a data infrastructure based on Geographic Information Systems, GIS. The value of GIS was explained in an article dating back to 1980 entitled "Need for a Multipurpose Cadastre" which stated, "There is a critical need for a better land-information system in the United States to improve land-conveyance procedures, furnish a basis for equitable taxation, and provide much-needed information for resource management and environmental planning." Scientists and engineers both point to GIS as the solution. What is GIS? According to most text books, Geographic Information Systems is a class of software that stores, manages, and analyzes mapable features on, above, or below the surface of the earth. GIS software is basically database management software to the management of spatial data and information. Simply put, Geographic Information Systems manage, analyze, chart, graph, and map spatial information. GIS can be broken down into two main categories, urban GIS and natural resource GIS. Further still, natural resource GIS can be broken down into six sub-categories, agriculture, forestry, wildlife, catchment management, archaeology, and geology/mining. Agriculture GIS has several applications, such as agricultural capability analysis, land conservation, market analysis, or whole farming planning. Forestry GIs can be used for timber assessment and management, harvest scheduling and planning, environmental impact assessment, and pest management. GIS when used in wildlife applications enables the user to assess and manage habitats, identify and track endangered and rare species, and monitor impact assessment.

77 FR 58507 - Proposed Flood Elevation Determinations for the Unincorporated Areas of Highlands County, FL

Federal Register 2010, 2011, 2012, 2013, 2014

2012-09-21

... comments, identified by Docket No. FEMA-B- 1204, to Luis Rodriguez, Chief, Engineering Management Branch...., Washington, DC 20472, (202) 646-4064, or (email) Luis[email protected] . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation...

Flight Planning Branch NASA Co-op Tour

NASA Technical Reports Server (NTRS)

Marr, Aja M.

2013-01-01

This semester I worked with the Flight Planning Branch at the NASA Johnson Space Center. I learned about the different aspects of flight planning for the International Space Station as well as the software that is used internally and ISSLive! which is used to help educate the public on the space program. I had the opportunity to do on the job training in the Mission Control Center with the planning team. I transferred old timeline records from the planning team's old software to the new software in order to preserve the data for the future when the software is retired. I learned about the operations of the International Space Station, the importance of good communication between the different parts of the planning team, and enrolled in professional development classes as well as technical classes to learn about the space station.

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.

Ecosystem engineering and manipulation of host plant tissues by the insect borer Oncideres albomarginata chamela.

PubMed

Calderón-Cortés, Nancy; Uribe-Mú, Claudia A; Martínez-Méndez, A Karen; Escalera-Vázquez, Luis H; Cristobal-Pérez, E Jacob; García-Oliva, Felipe; Quesada, Mauricio

2016-01-01

Ecosystem engineering by insect herbivores occurs as the result of structural modification of plants manipulated by insects. However, only few studies have evaluated the effect of these modifications on the plant responses induced by stem-borers that act as ecosystem engineers. In this study, we evaluated the responses induced by the herbivory of the twig-girdler beetle Oncideres albomarginata chamela (Cerambycidae: Lamiinae) on its host plant Spondias purpurea (Anacardiaceae), and its relationship with the ecosystem engineering process carried out by this stem-borer. Our results demonstrated that O. albomarginata chamela branch removal induced the development of lateral branches increasing the resources needed for the development of future insect generations, of its own offspring and of many other insect species. Detached branches represent habitats with high content of nitrogen and phosphorous, which eventually can be incorporated into the ecosystem, increasing nutrient cycling efficiency. Consequently, branch removal and the subsequent plant tissue regeneration induced by O. albomarginata chamela represent key mechanisms underlying the ecosystem engineering process carried out by this stem-borer, which enhances arthropod diversity in the ecosystem. Copyright © 2015 Elsevier Ltd. All rights reserved.

Gas Flow Detection System

NASA Technical Reports Server (NTRS)

Moss, Thomas; Ihlefeld, Curtis; Slack, Barry

2010-01-01

This system provides a portable means to detect gas flow through a thin-walled tube without breaking into the tubing system. The flow detection system was specifically designed to detect flow through two parallel branches of a manifold with only one inlet and outlet, and is a means for verifying a space shuttle program requirement that saves time and reduces the risk of flight hardware damage compared to the current means of requirement verification. The prototype Purge Vent and Drain Window Cavity Conditioning System (PVD WCCS) Flow Detection System consists of a heater and a temperature-sensing thermistor attached to a piece of Velcro to be attached to each branch of a WCCS manifold for the duration of the requirement verification test. The heaters and thermistors are connected to a shielded cable and then to an electronics enclosure, which contains the power supplies, relays, and circuit board to provide power, signal conditioning, and control. The electronics enclosure is then connected to a commercial data acquisition box to provide analog to digital conversion as well as digital control. This data acquisition box is then connected to a commercial laptop running a custom application created using National Instruments LabVIEW. The operation of the PVD WCCS Flow Detection System consists of first attaching a heater/thermistor assembly to each of the two branches of one manifold while there is no flow through the manifold. Next, the software application running on the laptop is used to turn on the heaters and to monitor the manifold branch temperatures. When the system has reached thermal equilibrium, the software application s graphical user interface (GUI) will indicate that the branch temperatures are stable. The operator can then physically open the flow control valve to initiate the test flow of gaseous nitrogen (GN2) through the manifold. Next, the software user interface will be monitored for stable temperature indications when the system is again at thermal equilibrium with the test flow of GN2. The temperature drop of each branch from its "no flow" stable temperature peak to its stable "with flow" temperature will allow the operator to determine whether a minimum level of flow exists. An alternative operation has the operator turning on the software only long enough to record the ambient temperature of the tubing before turning on the heaters and initiating GN2 flow. The stable temperature of the heated tubing with GN2 flow is then compared with the ambient tubing temperature to determine if flow is present in each branch. To help quantify the level of flow in the manifolds, each branch will be bench calibrated to establish its thermal properties using the flow detection system and different flow rates. These calibration values can then be incorporated into the software application to provide more detailed flow rate information.

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

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.

Machine learning and data science in soft materials engineering

NASA Astrophysics Data System (ADS)

Ferguson, Andrew L.

2018-01-01

In many branches of materials science it is now routine to generate data sets of such large size and dimensionality that conventional methods of analysis fail. Paradigms and tools from data science and machine learning can provide scalable approaches to identify and extract trends and patterns within voluminous data sets, perform guided traversals of high-dimensional phase spaces, and furnish data-driven strategies for inverse materials design. This topical review provides an accessible introduction to machine learning tools in the context of soft and biological materials by ‘de-jargonizing’ data science terminology, presenting a taxonomy of machine learning techniques, and surveying the mathematical underpinnings and software implementations of popular tools, including principal component analysis, independent component analysis, diffusion maps, support vector machines, and relative entropy. We present illustrative examples of machine learning applications in soft matter, including inverse design of self-assembling materials, nonlinear learning of protein folding landscapes, high-throughput antimicrobial peptide design, and data-driven materials design engines. We close with an outlook on the challenges and opportunities for the field.

Machine learning and data science in soft materials engineering.

PubMed

Ferguson, Andrew L

2018-01-31

In many branches of materials science it is now routine to generate data sets of such large size and dimensionality that conventional methods of analysis fail. Paradigms and tools from data science and machine learning can provide scalable approaches to identify and extract trends and patterns within voluminous data sets, perform guided traversals of high-dimensional phase spaces, and furnish data-driven strategies for inverse materials design. This topical review provides an accessible introduction to machine learning tools in the context of soft and biological materials by 'de-jargonizing' data science terminology, presenting a taxonomy of machine learning techniques, and surveying the mathematical underpinnings and software implementations of popular tools, including principal component analysis, independent component analysis, diffusion maps, support vector machines, and relative entropy. We present illustrative examples of machine learning applications in soft matter, including inverse design of self-assembling materials, nonlinear learning of protein folding landscapes, high-throughput antimicrobial peptide design, and data-driven materials design engines. We close with an outlook on the challenges and opportunities for the field.

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

Data Integration Framework Data Management Plan Remote Sensing Dataset

DTIC Science & Technology

2016-07-01

performed by the Coastal Observations and Analysis Branch (CEERD-HFA) of the Flood and Storm Protection Division (CEERD-HF), U.S. Army Engineer Research... Protection Division, Coastal Observations and Analysis Branch CESAM U.S. Army Corps of Engineers, Mobile District CESAM-OP-J U.S. Army Corps of Engineers...ER D C/ CH L SR -1 6- 2 Coastal Ocean Data Systems Program Data Integration Framework Data Management Plan Remote Sensing Dataset Co

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.

78 FR 34014 - Proposed Flood Elevation Determinations for Bolivar County, Mississippi and Incorporated Areas

Federal Register 2010, 2011, 2012, 2013, 2014

2013-06-06

..., identified by Docket No. FEMA-B- 1178, to Luis Rodriguez, Chief, Engineering Management Branch, Federal..., DC 20472, (202) 646-4064, or (email) fema.dhs.gov ">Luis[email protected] fema.dhs.gov . FOR FURTHER INFORMATION CONTACT: Luis Rodriguez, Chief, Engineering Management Branch, Federal Insurance and Mitigation...

[The Engineering and Technical Services Directorate at the Glenn Research Center

NASA Technical Reports Server (NTRS)

Moon, James

2004-01-01

My name is James Moon and I am a senior at Tennessee State University where my major is Aeronautical and Industrial Technology with a concentration in industrial electronics. I am currently serving my internship in the Engineering and Technical Services Directorate at the Glenn Research Center (GRC). The Engineering and Technical Service Directorate provides the services and infrastructure for the Glenn Research Center to take research concepts to reality. They provide a full range of integrated services including engineering, advanced prototyping and testing, facility management, and information technology for NASA, industry, and academia. Engineering and Technical Services contains the core knowledge in Information Technology (IT). This includes data systems and analysis, inter and intranet based systems design and data security. Including the design and development of embedded real-time s o h a r e applications for flight and supporting ground systems, Engineering and Technical Services provide a wide range of IT services and products specific to the Glenn Research Center research and engineering community. In the 7000 Directorate I work directly in the 7611 organization. This organization is known as the Aviation Environments Technical Branch. My mentor is Vincent Satterwhite who is also the Branch Chief of the Aviation Environments Technical Branch. In this branch, I serve as the Assistant program manager of the Engineering Technology Program. The Engineering Technology Program (ETP) is one of three components of the High School L.E.R.C.I.P. This is an Agency-sponsored, eight-week research-based apprenticeship program designed to attract traditionally underrepresented high school students that demonstrate an aptitude for and interest in mathematics, science, engineering, and technology.

Thermal Energy Conversion Branch

NASA Technical Reports Server (NTRS)

Bielozer, Matthew C.; Schreiber, Jeffrey, G.; Wilson, Scott D.

2004-01-01

The Thermal Energy Conversion Branch (5490) leads the way in designing, conducting, and implementing research for the newest thermal systems used in space applications at the NASA Glenn Research Center. Specifically some of the most advanced technologies developed in this branch can be broken down into four main areas: Dynamic Power Systems, Primary Solar Concentrators, Secondary Solar Concentrators, and Thermal Management. Work was performed in the Dynamic Power Systems area, specifically the Stirling Engine subdivision. Today, the main focus of the 5490 branch is free-piston Stirling cycle converters, Brayton cycle nuclear reactors, and heat rejection systems for long duration mission spacecraft. All space exploring devices need electricity to operate. In most space applications, heat energy from radioisotopes is converted to electrical power. The Radioisotope Thermoelectric Generator (RTG) already supplies electricity for missions such as the Cassini Spacecraft. The focus of today's Stirling research at GRC is aimed at creating an engine that can replace the RTG. The primary appeal of the Stirling engine is its high system efficiency. Because it is so efficient, the Stirling engine will significantly reduce the plutonium fuel mission requirements compared to the RTG. Stirling is also being considered for missions such as the lunar/Mars bases and rovers. This project has focused largely on Stirling Engines of all types, particularly the fluidyne liquid piston engine. The fluidyne was developed by Colin D. West. This engine uses the same concepts found in any type of Stirling engine, with the exception of missing mechanical components. All the working components are fluid. One goal was to develop and demonstrate a working Stirling Fluidyne Engine at the 2nd Annual International Energy Conversion Engineering Conference in Providence, Rhode Island.

Woods Hole Image Processing System Software implementation; using NetCDF as a software interface for image processing

USGS Publications Warehouse

Paskevich, Valerie F.

1992-01-01

The Branch of Atlantic Marine Geology has been involved in the collection, processing and digital mosaicking of high, medium and low-resolution side-scan sonar data during the past 6 years. In the past, processing and digital mosaicking has been accomplished with a dedicated, shore-based computer system. With the need to process sidescan data in the field with increased power and reduced cost of major workstations, a need to have an image processing package on a UNIX based computer system which could be utilized in the field as well as be more generally available to Branch personnel was identified. This report describes the initial development of that package referred to as the Woods Hole Image Processing System (WHIPS). The software was developed using the Unidata NetCDF software interface to allow data to be more readily portable between different computer operating systems.

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.

Proceedings of the First NASA Formal Methods Symposium

NASA Technical Reports Server (NTRS)

Denney, Ewen (Editor); Giannakopoulou, Dimitra (Editor); Pasareanu, Corina S. (Editor)

2009-01-01

Topics covered include: Model Checking - My 27-Year Quest to Overcome the State Explosion Problem; Applying Formal Methods to NASA Projects: Transition from Research to Practice; TLA+: Whence, Wherefore, and Whither; Formal Methods Applications in Air Transportation; Theorem Proving in Intel Hardware Design; Building a Formal Model of a Human-Interactive System: Insights into the Integration of Formal Methods and Human Factors Engineering; Model Checking for Autonomic Systems Specified with ASSL; A Game-Theoretic Approach to Branching Time Abstract-Check-Refine Process; Software Model Checking Without Source Code; Generalized Abstract Symbolic Summaries; A Comparative Study of Randomized Constraint Solvers for Random-Symbolic Testing; Component-Oriented Behavior Extraction for Autonomic System Design; Automated Verification of Design Patterns with LePUS3; A Module Language for Typing by Contracts; From Goal-Oriented Requirements to Event-B Specifications; Introduction of Virtualization Technology to Multi-Process Model Checking; Comparing Techniques for Certified Static Analysis; Towards a Framework for Generating Tests to Satisfy Complex Code Coverage in Java Pathfinder; jFuzz: A Concolic Whitebox Fuzzer for Java; Machine-Checkable Timed CSP; Stochastic Formal Correctness of Numerical Algorithms; Deductive Verification of Cryptographic Software; Coloured Petri Net Refinement Specification and Correctness Proof with Coq; Modeling Guidelines for Code Generation in the Railway Signaling Context; Tactical Synthesis Of Efficient Global Search Algorithms; Towards Co-Engineering Communicating Autonomous Cyber-Physical Systems; and Formal Methods for Automated Diagnosis of Autosub 6000.

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.

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.

75 FR 23571 - Airworthiness Directives; McDonnell Douglas Corporation Model DC-10-10, DC-10-10F, DC-10-15, DC...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-05-04

.... FOR FURTHER INFORMATION CONTACT: Philip Kush, Aerospace Engineer, Propulsion Branch, ANM-140L, FAA... ATTN: Philip Kush, Aerospace Engineer, Propulsion Branch, ANM-140L, FAA, Los Angeles ACO, 3960... AD results from fuel system reviews conducted by the manufacturer. We are issuing this AD to prevent...

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

Software for aerospace education: A bibliography, 2nd edition

NASA Technical Reports Server (NTRS)

Vogt, Gregory L.; Roth, Susan Kies; Phelps, Malcom V.

1990-01-01

This is the second aerospace education software bibliography to be published by the NASA Educational Technology Branch in Washington, DC. Unlike many software bibliographies, this bibliography does not evaluate and grade software according to its quality and value to the classroom, nor does it make any endorsements or warrant scientific accuracy. Rather, it describes software, its subject, approach, and technical details. This bibliography is intended as a convenience to educators. The specific software included represents replies to more than 300 queries to software producers for aerospace education programs.

Principles of Biomimetic Vascular Network Design Applied to a Tissue-Engineered Liver Scaffold

PubMed Central

Hoganson, David M.; Pryor, Howard I.; Spool, Ira D.; Burns, Owen H.; Gilmore, J. Randall

2010-01-01

Branched vascular networks are a central component of scaffold architecture for solid organ tissue engineering. In this work, seven biomimetic principles were established as the major guiding technical design considerations of a branched vascular network for a tissue-engineered scaffold. These biomimetic design principles were applied to a branched radial architecture to develop a liver-specific vascular network. Iterative design changes and computational fluid dynamic analysis were used to optimize the network before mold manufacturing. The vascular network mold was created using a new mold technique that achieves a 1:1 aspect ratio for all channels. In vitro blood flow testing confirmed the physiologic hemodynamics of the network as predicted by computational fluid dynamic analysis. These results indicate that this biomimetic liver vascular network design will provide a foundation for developing complex vascular networks for solid organ tissue engineering that achieve physiologic blood flow. PMID:20001254

Principles of biomimetic vascular network design applied to a tissue-engineered liver scaffold.

PubMed

Hoganson, David M; Pryor, Howard I; Spool, Ira D; Burns, Owen H; Gilmore, J Randall; Vacanti, Joseph P

2010-05-01

Branched vascular networks are a central component of scaffold architecture for solid organ tissue engineering. In this work, seven biomimetic principles were established as the major guiding technical design considerations of a branched vascular network for a tissue-engineered scaffold. These biomimetic design principles were applied to a branched radial architecture to develop a liver-specific vascular network. Iterative design changes and computational fluid dynamic analysis were used to optimize the network before mold manufacturing. The vascular network mold was created using a new mold technique that achieves a 1:1 aspect ratio for all channels. In vitro blood flow testing confirmed the physiologic hemodynamics of the network as predicted by computational fluid dynamic analysis. These results indicate that this biomimetic liver vascular network design will provide a foundation for developing complex vascular networks for solid organ tissue engineering that achieve physiologic blood flow.

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

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.

Symbol Tables and Branch Tables: Linking Applications Together

NASA Technical Reports Server (NTRS)

Handler, Louis M.

2011-01-01

This document explores the computer techniques used to execute software whose parts are compiled and linked separately. The computer techniques include using a branch table or indirect address table to connect the parts. Methods of storing the information in data structures are discussed as well as differences between C and C++.

ISS Operations Cost Reductions Through Automation of Real-Time Planning Tasks

NASA Technical Reports Server (NTRS)

Hall, Timothy A.; Clancey, William J.; McDonald, Aaron; Toschlog, Jason; Tucker, Tyson; Khan, Ahmed; Madrid, Steven (Eric)

2011-01-01

In 2007 the Johnson Space Center s Mission Operations Directorate (MOD) management team challenged their organizations to find ways to reduce the cost of operations for supporting the International Space Station (ISS) in the Mission Control Center (MCC). Each MOD organization was asked to define and execute projects that would help them attain cost reductions by 2012. The MOD Operations Division Flight Planning Branch responded to this challenge by launching several software automation projects that would allow them to greatly improve console operations and reduce ISS console staffing and intern reduce operating costs. These tasks ranged from improving the management and integration mission plan changes, to automating the uploading and downloading of information to and from the ISS and the associated ground complex tasks that required multiple decision points. The software solutions leveraged several different technologies including customized web applications and implementation of industry standard web services architecture; as well as engaging a previously TRL 4-5 technology developed by Ames Research Center (ARC) that utilized an intelligent agent-based system to manage and automate file traffic flow, archive data, and generate console logs. These projects to date have allowed the MOD Operations organization to remove one full time (7 x 24 x 365) ISS console position in 2010; with the goal of eliminating a second full time ISS console support position by 2012. The team will also reduce one long range planning console position by 2014. When complete, these Flight Planning Branch projects will account for the elimination of 3 console positions and a reduction in staffing of 11 engineering personnel (EP) for ISS.

Dental Informatics tool "SOFPRO" for the study of oral submucous fibrosis.

PubMed

Erlewad, Dinesh Masajirao; Mundhe, Kalpana Anandrao; Hazarey, Vinay K

2016-01-01

Dental informatics is an evolving branch widely used in dental education and practice. Numerous applications that support clinical care, education and research have been developed. However, very few such applications are developed and utilized in the epidemiological studies of oral submucous fibrosis (OSF) which is affecting a significant population of Asian countries. To design and develop an user friendly software for the descriptive epidemiological study of OSF. With the help of a software engineer a computer program SOFPRO was designed and developed by using, Ms-Visual Basic 6.0 (VB), Ms-Access 2000, Crystal Report 7.0 and Ms-Paint in operating system XP. For the analysis purpose the available OSF data from the departmental precancer registry was fed into the SOFPRO. Known data, not known and null data are successfully accepted in data entry and represented in data analysis of OSF. Smooth working of SOFPRO and its correct data flow was tested against real-time data of OSF. SOFPRO was found to be a user friendly automated tool for easy data collection, retrieval, management and analysis of OSF patients.

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

Composite Overview and Composite Aerocover Overview

NASA Technical Reports Server (NTRS)

Caraccio, Anne; Tate, LaNetra; Dokos, Adam; Taylor, Brian; Brown, Chad

2014-01-01

Materials Science Division within the Engineering Directorate tasked by the Ares Launch Vehicle Division (LX-V) and the Fluids Testing and Technology Development Branch (NE-F6) to design, fabricate and test an aerodynamic composite shield for potential Heavy Lift Launch Vehicle infusion and a composite strut that will serve as a pathfinder in evaluating calorimeter data for the CRYOSTAT (cryogenic on orbit storage and transfer) Project. ATP project is to carry the design and development of the aerodynamic composite cover or "bracket" from cradle to grave including materials research, purchasing, design, fabrication, testing, analysis and presentation of the final product. Effort consisted of support from the Materials Testing & Corrosion Control Branch (NE-L2) for mechanical testing, the Prototype Development Branch (NE-L3) for CAD drawing, design/analysis, and fabrication, Materials & Processes Engineering Branch (NE-L4) for project management and materials selection; the Applied Physics Branch (NE-LS) for NDE/NDI support; and the Chemical Analysis Branch (NE-L6) for developmental systems evaluation. Funded by the Ares Launch Vehicle Division and the Fluids Testing and Technology Development Branch will provide ODC

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.

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.

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.

VESGEN Software for Mapping and Quantification of Vascular Regulators

NASA Technical Reports Server (NTRS)

Parsons-Wingerter, Patricia A.; Vickerman, Mary B.; Keith, Patricia A.

2012-01-01

VESsel GENeration (VESGEN) Analysis is an automated software that maps and quantifies effects of vascular regulators on vascular morphology by analyzing important vessel parameters. Quantification parameters include vessel diameter, length, branch points, density, and fractal dimension. For vascular trees, measurements are reported as dependent functions of vessel branching generation. VESGEN maps and quantifies vascular morphological events according to fractal-based vascular branching generation. It also relies on careful imaging of branching and networked vascular form. It was developed as a plug-in for ImageJ (National Institutes of Health, USA). VESGEN uses image-processing concepts of 8-neighbor pixel connectivity, skeleton, and distance map to analyze 2D, black-and-white (binary) images of vascular trees, networks, and tree-network composites. VESGEN maps typically 5 to 12 (or more) generations of vascular branching, starting from a single parent vessel. These generations are tracked and measured for critical vascular parameters that include vessel diameter, length, density and number, and tortuosity per branching generation. The effects of vascular therapeutics and regulators on vascular morphology and branching tested in human clinical or laboratory animal experimental studies are quantified by comparing vascular parameters with control groups. VESGEN provides a user interface to both guide and allow control over the users vascular analysis process. An option is provided to select a morphological tissue type of vascular trees, network or tree-network composites, which determines the general collections of algorithms, intermediate images, and output images and measurements that will be produced.

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

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

Software Management Environment (SME) installation guide

NASA Technical Reports Server (NTRS)

Kistler, David; Jeletic, Kellyann

1992-01-01

This document contains installation information for the Software Management Environment (SME), developed for the Systems Development Branch (Code 552) of the Flight Dynamics Division of Goddard Space Flight Center (GSFC). The SME provides an integrated set of management tools that can be used by software development managers in their day-to-day management and planning activities. This document provides a list of hardware and software requirements as well as detailed installation instructions and trouble-shooting information.

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.

Agricultural Engineering Education in Nigeria

ERIC Educational Resources Information Center

Aboaba, F. O.

1974-01-01

Agricultural engineering, an important new branch of engineering in Nigeria, is discussed in relation to available training programs, diploma and certificate courses, and evaluation of training programs. (Author/PG)

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.

Metabolic engineering of Saccharomyces cerevisiae for production of fatty acid short- and branched-chain alkyl esters biodiesel.

PubMed

Teo, Wei Suong; Ling, Hua; Yu, Ai-Qun; Chang, Matthew Wook

2015-01-01

Biodiesel is a mixture of fatty acid short-chain alkyl esters of different fatty acid carbon chain lengths. However, while fatty acid methyl or ethyl esters are useful biodiesel produced commercially, fatty acid esters with branched-chain alcohol moieties have superior fuel properties. Crucially, this includes improved cold flow characteristics, as one of the major problems associated with biodiesel use is poor low-temperature flow properties. Hence, microbial production as a renewable, nontoxic and scalable method to produce fatty acid esters with branched-chain alcohol moieties from biomass is critical. We engineered Saccharomyces cerevisiae to produce fatty acid short- and branched-chain alkyl esters, including ethyl, isobutyl, isoamyl and active amyl esters using endogenously synthesized fatty acids and alcohols. Two wax ester synthase genes (ws2 and Maqu_0168 from Marinobacter sp.) were cloned and expressed. Both enzymes were found to catalyze the formation of fatty acid esters, with different alcohol preferences. To boost the ability of S. cerevisiae to produce the aforementioned esters, negative regulators of the INO1 gene in phospholipid metabolism, Rpd3 and Opi1, were deleted to increase flux towards fatty acyl-CoAs. In addition, five isobutanol pathway enzymes (Ilv2, Ilv5, Ilv3, Aro10, and Adh7) targeted into the mitochondria were overexpressed to enhance production of alcohol precursors. By combining these engineering strategies with high-cell-density fermentation, over 230 mg/L fatty acid short- and branched-chain alkyl esters were produced, which is the highest titer reported in yeast to date. In this work, we engineered the metabolism of S. cerevisiae to produce biodiesels in the form of fatty acid short- and branched-chain alkyl esters, including ethyl, isobutyl, isoamyl and active amyl esters. To our knowledge, this is the first report of the production of fatty acid isobutyl and active amyl esters in S. cerevisiae. Our findings will be useful for engineering S. cerevisiae strains toward high-level and sustainable biodiesel production.

46 CFR 111.75-5 - Lighting branch circuits.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 4 2010-10-01 2010-10-01 false Lighting branch circuits. 111.75-5 Section 111.75-5 Shipping COAST GUARD, DEPARTMENT OF HOMELAND SECURITY (CONTINUED) ELECTRICAL ENGINEERING ELECTRIC SYSTEMS-GENERAL REQUIREMENTS Lighting Circuits and Protection § 111.75-5 Lighting branch circuits. (a) Loads. A...

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…

National Program for Inspection of Non-Federal Dams. Keyser Dam (VT 00097), Connecticut River Basin, Chelsea, Vermont. Phase I Inspection Report.

DTIC Science & Technology

1980-04-01

CARNEY M. TERZIAN, HENBER I Design Branch Engineering Division RICHARD DIB * Water Control Branch Engineering Division [ hPIPWVAL 220ininu: Chief...2 f. Operator 2 I g. Purpose of Dam 2 h. Design and Construction History 2 i. Normal Operational Procedure 2 1.3 Pertinent Data 2 a. Drainage...i. Spillway 5 J. Regulating Outlets 5 [I h] Section Page 2. ENGINEERING DATA 6 2.1 Design Data 6 2.2 Construction Data 6 2.3 Operation Data 6 2.4

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.

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

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.

Science and Engineering

ERIC Educational Resources Information Center

Cowin, Roy; Reyes-Guerra, David

1977-01-01

Engineers may be involved in various functions such as research, development, planning, design (analysis and synthesis), construction, operation and management of engineering projects. This article discusses some branches of accredited engineering curricula, employment opportunities, the preparation for management, minimum education needed, women…

Re-engineering specificity in 1,3-1, 4-β-glucanase to accept branched xyloglucan substrates.

PubMed

Addington, Trevor; Calisto, Barbara; Alfonso-Prieto, Mercedes; Rovira, Carme; Fita, Ignasi; Planas, Antoni

2011-02-01

Family 16 carbohydrate active enzyme members Bacillus licheniformis 1,3-1,4-β-glucanase and Populus tremula x tremuloides xyloglucan endotransglycosylase (XET16-34) are highly structurally related but display different substrate specificities. Although the first binds linear gluco-oligosaccharides, the second binds branched xylogluco-oligosaccharides. Prior engineered nucleophile mutants of both enzymes are glycosynthases that catalyze the condensation between a glycosyl fluoride donor and a glycoside acceptor. With the aim of expanding the glycosynthase technology to produce designer oligosaccharides consisting of hybrids between branched xylogluco- and linear gluco-oligosaccharides, enzyme engineering on the negative subsites of 1,3-1,4-β-glucanase to accept branched substrates has been undertaken. Removal of the 1,3-1,4-β-glucanase major loop and replacement with that of XET16-34 to open the binding cleft resulted in a folded protein, which still maintained some β-glucan hydrolase activity, but the corresponding nucleophile mutant did not display glycosynthase activity with either linear or branched glycosyl donors. Next, point mutations of the 1,3-1,4-β-glucanase β-sheets forming the binding site cleft were mutated to resemble XET16-34 residues. The final chimeric protein acquired binding affinity for xyloglucan and did not bind β-glucan. Therefore, binding specificity has been re-engineered, but affinity was low and the nucleophile mutant of the chimeric enzyme did not show glycosynthase activity to produce the target hybrid oligosaccharides. Structural analysis by X-ray crystallography explains these results in terms of changes in the protein structure and highlights further engineering approaches toward introducing the desired activity. © 2010 Wiley-Liss, Inc.

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

Mapping and Quantification of Vascular Branching in Plants, Animals and Humans by VESGEN Software

NASA Technical Reports Server (NTRS)

Parsons-Wingerter, Patricia A.; Vickerman, Mary B.; Keith, Patricia A.

2010-01-01

Humans face daunting challenges in the successful exploration and colonization of space, including adverse alterations in gravity and radiation. The Earth-determined biology of humans, animals and plants is significantly modified in such extraterrestrial environments. One physiological requirement shared by humans with larger plants and animals is a complex, highly branching vascular system that is dynamically responsive to cellular metabolism, immunological protection and specialized cellular/tissue function. The VESsel GENeration (VESGEN) Analysis has been developed as a mature beta version, pre-release research software for mapping and quantification of the fractal-based complexity of vascular branching. Alterations in vascular branching pattern can provide informative read-outs of altered vascular regulation. Originally developed for biomedical applications in angiogenesis, VESGEN 2D has provided novel insights into the cytokine, transgenic and therapeutic regulation of angiogenesis, lymphangiogenesis and other microvascular remodeling phenomena. Vascular trees, networks and tree-network composites are mapped and quantified. Applications include disease progression from clinical ophthalmic images of the human retina; experimental regulation of vascular remodeling in the mouse retina; avian and mouse coronary vasculature, and other experimental models in vivo. We envision that altered branching in the leaves of plants studied on ISS such as Arabidopsis thaliana cans also be analyzed.

Mapping and Quantification of Vascular Branching in Plants, Animals and Humans by VESGEN Software

NASA Technical Reports Server (NTRS)

Parsons-Wingerter, P. A.; Vickerman, M. B.; Keith, P. A.

2010-01-01

Humans face daunting challenges in the successful exploration and colonization of space, including adverse alterations in gravity and radiation. The Earth-determined biology of plants, animals and humans is significantly modified in such extraterrestrial environments. One physiological requirement shared by larger plants and animals with humans is a complex, highly branching vascular system that is dynamically responsive to cellular metabolism, immunological protection and specialized cellular/tissue function. VESsel GENeration (VESGEN) Analysis has been developed as a mature beta version, pre-release research software for mapping and quantification of the fractal-based complexity of vascular branching. Alterations in vascular branching pattern can provide informative read-outs of altered vascular regulation. Originally developed for biomedical applications in angiogenesis, VESGEN 2D has provided novel insights into the cytokine, transgenic and therapeutic regulation of angiogenesis, lymphangiogenesis and other microvascular remodeling phenomena. Vascular trees, networks and tree-network composites are mapped and quantified. Applications include disease progression from clinical ophthalmic images of the human retina; experimental regulation of vascular remodeling in the mouse retina; avian and mouse coronary vasculature, and other experimental models in vivo. We envision that altered branching in the leaves of plants studied on ISS such as Arabidopsis thaliana cans also be analyzed.

The Direction of Fluid Dynamics for Liquid Propulsion at NASA Marshall Space Flight Center

NASA Technical Reports Server (NTRS)

Griffin, Lisa W.

2012-01-01

Marshall Space Flight Center (MSFC) is the National Aeronautics and Space Administration (NASA)-designated center for the development of space launch systems. MSFC is particularly known for propulsion system development. Many engineering skills and technical disciplines are needed to accomplish this mission. This presentation will focus on the work of the Fluid Dynamics Branch (ER42). ER42 resides in the Propulsion Systems Department at MSFC. The branch is responsible for all aspects of the discipline of fluid dynamics applied to propulsion or propulsion-induced loads and environments. This work begins with design trades and parametric studies, and continues through development, risk assessment, anomaly investigation and resolution, and failure investigations. Applications include the propellant delivery system including the main propulsion system (MPS) and turbomachinery; combustion devices for liquid engines and solid rocket motors; coupled systems; and launch environments. An advantage of the branch is that it is neither analysis nor test centric, but discipline centric. Fluid dynamics assessments are made by analysis, from lumped parameter modeling through unsteady computational fluid dynamics (CFD); testing, which can be cold flow or hot fire; or a combination of analysis and testing. Integration of all discipline methods into one branch enables efficient and accurate support to the projects. To accomplish this work, the branch currently employs approximately fifty engineers divided into four teams -- Propellant Delivery CFD, Combustion Driven Flows CFD, Unsteady and Experimental Flows, and Acoustics and Stability. This discussion will highlight some of the work performed in the branch and the direction in which the branch is headed.

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…

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

48 CFR 852.236-82 - Payments under fixed-price construction contracts (without NAS).

Code of Federal Regulations, 2013 CFR

2013-10-01

... “Network Analysis System (NAS).” Payments Under Fixed-Price Construction Contracts (APR 1984) The clause..., as applied to each branch, shall equal the total cost of such branch. The total cost of all branches... readily available for inspection and inventory by the resident engineer. (4) Such materials and/or...

48 CFR 852.236-82 - Payments under fixed-price construction contracts (without NAS).

Code of Federal Regulations, 2011 CFR

2011-10-01

... “Network Analysis System (NAS).” Payments Under Fixed-Price Construction Contracts (APR 1984) The clause..., as applied to each branch, shall equal the total cost of such branch. The total cost of all branches... readily available for inspection and inventory by the resident engineer. (4) Such materials and/or...

48 CFR 852.236-82 - Payments under fixed-price construction contracts (without NAS).

Code of Federal Regulations, 2012 CFR

2012-10-01

... “Network Analysis System (NAS).” Payments Under Fixed-Price Construction Contracts (APR 1984) The clause..., as applied to each branch, shall equal the total cost of such branch. The total cost of all branches... readily available for inspection and inventory by the resident engineer. (4) Such materials and/or...

48 CFR 852.236-82 - Payments under fixed-price construction contracts (without NAS).

Code of Federal Regulations, 2014 CFR

2014-10-01

... “Network Analysis System (NAS).” Payments Under Fixed-Price Construction Contracts (APR 1984) The clause..., as applied to each branch, shall equal the total cost of such branch. The total cost of all branches... readily available for inspection and inventory by the resident engineer. (4) Such materials and/or...

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…

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.

Fusible core molding for the fabrication of branched, perfusable, three-dimensional microvessels for vascular tissue engineering.

PubMed

Martin, Cristina; Sofla, Aarash; Zhang, Boyang; Nunes, Sara S; Radisic, Milica

2013-03-01

A novel method for fabrication of branched, tubular, perfusable microvessels for use in vascular tissue engineering is reported. A tubular, elastomeric, biodegradable scaffold is first fabricated via a new, double fusible injection molding technique that uses a ternary alloy with a low melting temperature, Field's metal, and paraffin as sacrificial components. A cylindrical core metal of 500 μm or lower dia-meter with the target branching scaffold geometry is first constructed, then the metal structure is coated with paraffin and, finally, the metal-paraffin construct is embedded in polydimethylsiloxane (PDMS). The paraffin layer is then removed by heating and replaced by a biodegradable elastomeric pre-polymer that is subsequently UV-cured inside the PDMS. Next, the metal core is melted away and the PDMS is removed to attain the branched tubular elastomeric biodegradable scaffold. Finally, it is also demonstrated that human umbilical vein endothelial cells (HUVEC) were able to spread on the surface of the scaffold and form a confluent monolayer, confirming the potential of this new technique for making engineered blood vessels.

Assessing the Potential of Low-Cost 3D Cameras for the Rapid Measurement of Plant Woody Structure

PubMed Central

Nock, Charles A; Taugourdeau, Olivier; Delagrange, Sylvain; Messier, Christian

2013-01-01

Detailed 3D plant architectural data have numerous applications in plant science, but many existing approaches for 3D data collection are time-consuming and/or require costly equipment. Recently, there has been rapid growth in the availability of low-cost, 3D cameras and related open source software applications. 3D cameras may provide measurements of key components of plant architecture such as stem diameters and lengths, however, few tests of 3D cameras for the measurement of plant architecture have been conducted. Here, we measured Salix branch segments ranging from 2–13 mm in diameter with an Asus Xtion camera to quantify the limits and accuracy of branch diameter measurement with a 3D camera. By scanning at a variety of distances we also quantified the effect of scanning distance. In addition, we also test the sensitivity of the program KinFu for continuous 3D object scanning and modeling as well as other similar software to accurately record stem diameters and capture plant form (<3 m in height). Given its ability to accurately capture the diameter of branches >6 mm, Asus Xtion may provide a novel method for the collection of 3D data on the branching architecture of woody plants. Improvements in camera measurement accuracy and available software are likely to further improve the utility of 3D cameras for plant sciences in the future. PMID:24287538

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.

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

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.

Software Management Environment (SME) release 9.4 user reference material

NASA Technical Reports Server (NTRS)

Hendrick, R.; Kistler, D.; Manter, K.

1992-01-01

This document contains user reference material for the Software Management Environment (SME) prototype, developed for the Systems Development Branch (Code 552) of the Flight Dynamics Division (FDD) of Goddard Space Flight Center (GSFC). The SME provides an integrated set of management tools that can be used by software development managers in their day-to-day management and planning activities. This document provides an overview of the SME, a description of all functions, and detailed instructions concerning the software's installation and use.

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.

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

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.

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.

Lightning Protection Guidelines for Aerospace Vehicles

NASA Technical Reports Server (NTRS)

Goodloe, C. C.

1999-01-01

This technical memorandum provides lightning protection engineering guidelines and technical procedures used by the George C. Marshall Space Flight Center (MSFC) Electromagnetics and Aerospace Environments Branch for aerospace vehicles. The overviews illustrate the technical support available to project managers, chief engineers, and design engineers to ensure that aerospace vehicles managed by MSFC are adequately protected from direct and indirect effects of lightning. Generic descriptions of the lightning environment and vehicle protection technical processes are presented. More specific aerospace vehicle requirements for lightning protection design, performance, and interface characteristics are available upon request to the MSFC Electromagnetics and Aerospace Environments Branch, mail code EL23.

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.

pyam: Python Implementation of YaM

NASA Technical Reports Server (NTRS)

Myint, Steven; Jain, Abhinandan

2012-01-01

pyam is a software development framework with tools for facilitating the rapid development of software in a concurrent software development environment. pyam provides solutions for development challenges associated with software reuse, managing multiple software configurations, developing software product lines, and multiple platform development and build management. pyam uses release-early, release-often development cycles to allow developers to integrate their changes incrementally into the system on a continual basis. It facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. It uses modules and packages to organize and share software across multiple software products, and uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One sidebenefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability, and software reuse. pyam is written in Python and is organized as a set of utilities on top of the open source SVN software version control package. All development software is organized into a collection of modules. pyam packages are defined as sub-collections of the available modules. Developers can set up private sandboxes for module/package development. All module/package development takes place on private SVN branches. High-level pyam commands support the setup, update, and release of modules and packages. Released and pre-built versions of modules are available to developers. Developers can tailor the source/link module mix for their sandboxes so that new sandboxes (even large ones) can be built up easily and quickly by pointing to pre-existing module releases. All inter-module interfaces are publicly exported via links. A minimal, but uniform, convention is used for building modules.

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.

SLAC-standard CAMAC branch terminator (Engineering Materials)

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

Not Available

1980-04-04

The drawings listed on the drawing list provide the data and specifications for constructing a Branch Terminator for the SLAC standard CAMAC units. This is a device for matching the cables and other branch lines in the system. This unit is designed for a certain group of SLAC CAMAC units which are referred to as SLAC-Standard CAMAC Units.

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

A demonstration of expert systems applications in transportation engineering : volume I, transportation engineers and expert systems.

DOT National Transportation Integrated Search

1987-01-01

Expert systems, a branch of artificial-intelligence studies, is introduced with a view to its relevance in transportation engineering. Knowledge engineering, the process of building expert systems or transferring knowledge from human experts to compu...

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.

Experimental cross-correlation nitrogen Q-branch CARS thermometry in a spark ignition engine

NASA Astrophysics Data System (ADS)

Lockett, R. D.; Ball, D.; Robertson, G. N.

2013-07-01

A purely experimental technique was employed to derive temperatures from nitrogen Q-branch Coherent Anti-Stokes Raman Scattering (CARS) spectra, obtained in a high pressure, high temperature environment (spark ignition Otto engine). This was in order to obviate any errors arising from deficiencies in the spectral scaling laws which are commonly used to represent nitrogen Q-branch CARS spectra at high pressure. The spectra obtained in the engine were compared with spectra obtained in a calibrated high pressure, high temperature cell, using direct cross-correlation in place of the minimisation of sums of squares of residuals. The technique is demonstrated through the measurement of air temperature as a function of crankshaft angle inside the cylinder of a motored single-cylinder Ricardo E6 research engine, followed by the measurement of fuel-air mixture temperatures obtained during the compression stroke in a knocking Ricardo E6 engine. A standard CARS programme (SANDIA's CARSFIT) was employed to calibrate the altered non-resonant background contribution to the CARS spectra that was caused by the alteration to the mole fraction of nitrogen in the unburned fuel-air mixture. The compression temperature profiles were extrapolated in order to predict the auto-ignition temperatures.

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.

76 FR 67625 - Airworthiness Directives; Airbus Model A319 and A320 Series Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2011-11-02

... receipt. FOR FURTHER INFORMATION CONTACT: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116... appropriate. If sending information directly to the International Branch, send it to ATTN: Sanjay Ralhan...

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

Engineered short branched-chain acyl-CoA synthesis in E. coli and acylation of chloramphenicol to branched-chain derivatives.

PubMed

Bi, Huiping; Bai, Yanfen; Cai, Tao; Zhuang, Yibin; Liang, Xiaomei; Zhang, Xueli; Liu, Tao; Ma, Yanhe

2013-12-01

Short branched-chain acyl-CoAs are important building blocks for a wide variety of pharmaceutically valuable natural products. Escherichia coli has been used as a heterologous host for the production of a variety of natural compounds for many years. In the current study, we engineered synthesis of isobutyryl-CoA and isovaleryl-CoA from glucose in E. coli by integration of the branched-chain α-keto acid dehydrogenase complex from Streptomyces avermitilis. In the presence of the chloramphenicol acetyltransferase (cat) gene, chloramphenicol was converted to both chloramphenicol-3-isobutyrate and chloramphenicol-3-isovalerate by the recombinant E. coli strains, which suggested successful synthesis of isobutyryl-CoA and isovaleryl-CoA. Furthermore, we improved the α-keto acid precursor supply by overexpressing the alsS gene from Bacillus subtilis and the ilvC and ilvD genes from E. coli and thus enhanced the synthesis of short branched-chain acyl-CoAs. By feeding 25 mg/L chloramphenicol, 2.96 ± 0.06 mg/L chloramphenicol-3-isobutyrate and 3.94 ± 0.06 mg/L chloramphenicol-3-isovalerate were generated by the engineered E. coli strain, which indicated efficient biosynthesis of short branched-chain acyl-CoAs. HPLC analysis showed that the most efficient E. coli strain produced 80.77 ± 3.83 nmol/g wet weight isovaleryl-CoA. To our knowledge, this is the first report of production of short branched-chain acyl-CoAs in E. coli and opens a way to biosynthesize various valuable natural compounds based on these special building blocks from renewable carbon sources.

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.

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

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.

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.

Assurance Policy Evaluation - Spacecraft and Strategic Systems

DTIC Science & Technology

2014-09-17

electromechanical (EEE) parts, software, design and workmanship, work instructions, manufacturing and tooling, cleanrooms, electrostatic discharge ...T9001B.  An external group, called the Evaluation and Assessment Team, made up of product assurance subject matter experts from NSWC Corona performs...NSWC, Corona and SSP Technical Branch(es). The FTPE, performed every 3 years, is an objective evaluation of facility performance to assure proper

Diffusion pseudotime robustly reconstructs lineage branching.

PubMed

Haghverdi, Laleh; Büttner, Maren; Wolf, F Alexander; Buettner, Florian; Theis, Fabian J

2016-10-01

The temporal order of differentiating cells is intrinsically encoded in their single-cell expression profiles. We describe an efficient way to robustly estimate this order according to diffusion pseudotime (DPT), which measures transitions between cells using diffusion-like random walks. Our DPT software implementations make it possible to reconstruct the developmental progression of cells and identify transient or metastable states, branching decisions and differentiation endpoints.

Architecture independent environment for developing engineering software on MIMD computers

NASA Technical Reports Server (NTRS)

Valimohamed, Karim A.; Lopez, L. A.

1990-01-01

Engineers are constantly faced with solving problems of increasing complexity and detail. Multiple Instruction stream Multiple Data stream (MIMD) computers have been developed to overcome the performance limitations of serial computers. The hardware architectures of MIMD computers vary considerably and are much more sophisticated than serial computers. Developing large scale software for a variety of MIMD computers is difficult and expensive. There is a need to provide tools that facilitate programming these machines. First, the issues that must be considered to develop those tools are examined. The two main areas of concern were architecture independence and data management. Architecture independent software facilitates software portability and improves the longevity and utility of the software product. It provides some form of insurance for the investment of time and effort that goes into developing the software. The management of data is a crucial aspect of solving large engineering problems. It must be considered in light of the new hardware organizations that are available. Second, the functional design and implementation of a software environment that facilitates developing architecture independent software for large engineering applications are described. The topics of discussion include: a description of the model that supports the development of architecture independent software; identifying and exploiting concurrency within the application program; data coherence; engineering data base and memory management.

NASA Software Documentation Standard

NASA Technical Reports Server (NTRS)

1991-01-01

The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The 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. The 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.

Training, Quality Assurance Factors, and Tools Investigation: a Work Report and Suggestions on Software Quality Assurance

NASA Technical Reports Server (NTRS)

Lee, Pen-Nan

1991-01-01

Previously, several research tasks have been conducted, some observations were obtained, and several possible suggestions have been contemplated involving software quality assurance engineering at NASA Johnson. These research tasks are briefly described. Also, a brief discussion is given on the role of software quality assurance in software engineering along with some observations and suggestions. A brief discussion on a training program for software quality assurance engineers is provided. A list of assurance factors as well as quality factors are also included. Finally, a process model which can be used for searching and collecting software quality assurance tools is presented.

EngineSim: Turbojet Engine Simulator Adapted for High School Classroom Use

NASA Technical Reports Server (NTRS)

Petersen, Ruth A.

2001-01-01

EngineSim is an interactive educational computer program that allows users to explore the effect of engine operation on total aircraft performance. The software is supported by a basic propulsion web site called the Beginner's Guide to Propulsion, which includes educator-created, web-based activities for the classroom use of EngineSim. In addition, educators can schedule videoconferencing workshops in which EngineSim's creator demonstrates the software and discusses its use in the educational setting. This software is a product of NASA Glenn Research Center's Learning Technologies Project, an educational outreach initiative within the High Performance Computing and Communications Program.

Evaluating software development characteristics: Assessment of software measures in the Software Engineering Laboratory. [reliability engineering

NASA Technical Reports Server (NTRS)

Basili, V. R.

1981-01-01

Work on metrics is discussed. Factors that affect software quality are reviewed. Metrics is discussed in terms of criteria achievements, reliability, and fault tolerance. Subjective and objective metrics are distinguished. Product/process and cost/quality metrics are characterized and discussed.

Space Electronic Test Engineering

NASA Technical Reports Server (NTRS)

Chambers, Rodney D.

2004-01-01

The Space Power and Propulsion Test Engineering Branch at NASA Glenn Research center has the important duty of controlling electronic test engineering services. These services include test planning and early assessment of Space projects, management and/or technical support required to safely and effectively prepare the article and facility for testing, operation of test facilities, and validation/delivery of data to customer. The Space Electronic Test Engineering Branch is assigned electronic test engineering responsibility for the GRC Space Simulation, Microgravity, Cryogenic, and Combustion Test Facilities. While working with the Space Power and Propulsion Test Engineering Branch I am working on several different assignments. My primary assignment deals with an electrical hardware unit known as Sunny Boy. Sunny Boy is a DC load Bank that is designed for solar arrays in which it is used to convert DC power form the solar arrays into AC power at 60 hertz to pump back into the electricity grid. However, there are some researchers who decided that they would like to use the Sunny Boy unit in a space simulation as a DC load bank for a space shuttle or even the International Space Station hardware. In order to do so I must create a communication link between a computer and the Sunny Boy unit so that I can preset a few of the limits (such power, set & constant voltage levels) that Sunny Boy will need to operate using the applied DC load. Apart from this assignment I am also working on a hi-tech circuit that I need to have built at a researcher s request. This is a high voltage analog to digital circuit that will be used to record data from space ion propulsion rocket booster tests. The problem that makes building this circuit so difficult is that it contains high voltage we must find a way to lower the voltage signal before the data is transferred into the computer to be read. The solution to this problem was to transport the signal using infrared light which will lower the voltage signal down low enough so that it is harmless to a computer. Along with my involvement in the Space Power and Propulsion Test Engineering Branch, I am obligated to assist all other members of the branch in their work. This will help me to strengthen and extend my knowledge of Electrical Engineering.

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.

Software engineering and Ada in design

NASA Technical Reports Server (NTRS)

Oneill, Don

1986-01-01

Modern software engineering promises significant reductions in software costs and improvements in software quality. The Ada language is the focus for these software methodology and tool improvements. The IBM FSD approach, including the software engineering practices that guide the systematic design and development of software products and the management of the software process are examined. The revised Ada design language adaptation is revealed. This four level design methodology is detailed including the purpose of each level, the management strategy that integrates the software design activity with the program milestones, and the technical strategy that maps the Ada constructs to each level of design. A complete description of each design level is provided along with specific design language recording guidelines for each level. Finally, some testimony is offered on education, tools, architecture, and metrics resulting from project use of the four level Ada design language adaptation.

CrossTalk: The Journal of Defense Software Engineering. Volume 20, Number 6, June 2007

DTIC Science & Technology

2007-06-01

California. He has co-authored the book Software Cost Estimation With COCOMO II with Barry Boehm and others. Clark helped define the COCOMO II model...Software Engineering at the University of Southern California. She worked with Barry Boehm and Chris Abts to develop and calibrate a cost-estimation...2003/02/ schorsch.html>. 2. See “Software Engineering, A Practitioners Approach” by Roger Pressman for a good description of coupling, cohesion

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

DTIC Science & Technology

2014-07-01

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

SSME Post Test Diagnostic System: Systems Section

NASA Technical Reports Server (NTRS)

Bickmore, Timothy

1995-01-01

An assessment of engine and component health is routinely made after each test firing or flight firing of a Space Shuttle Main Engine (SSME). Currently, this health assessment is done by teams of engineers who manually review sensor data, performance data, and engine and component operating histories. Based on review of information from these various sources, an evaluation is made as to the health of each component of the SSME and the preparedness of the engine for another test or flight. The objective of this project - the SSME Post Test Diagnostic System (PTDS) - is to develop a computer program which automates the analysis of test data from the SSME in order to detect and diagnose anomalies. This report primarily covers work on the Systems Section of the PTDS, which automates the analyses performed by the systems/performance group at the Propulsion Branch of NASA Marshall Space Flight Center (MSFC). This group is responsible for assessing the overall health and performance of the engine, and detecting and diagnosing anomalies which involve multiple components (other groups are responsible for analyzing the behavior of specific components). The PTDS utilizes several advanced software technologies to perform its analyses. Raw test data is analyzed using signal processing routines which detect features in the data, such as spikes, shifts, peaks, and drifts. Component analyses are performed by expert systems, which use 'rules-of-thumb' obtained from interviews with the MSFC data analysts to detect and diagnose anomalies. The systems analysis is performed using case-based reasoning. Results of all analyses are stored in a relational database and displayed via an X-window-based graphical user interface which provides ranked lists of anomalies and observations by engine component, along with supporting data plots for each.

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

Peck, T; Sparkman, D; Storch, N

''The LLNL Site-Specific Advanced Simulation and Computing (ASCI) Software Quality Engineering Recommended Practices VI.I'' document describes a set of recommended software quality engineering (SQE) practices for ASCI code projects at Lawrence Livermore National Laboratory (LLNL). In this context, SQE is defined as the process of building quality into software products by applying the appropriate guiding principles and management practices. Continual code improvement and ongoing process improvement are expected benefits. Certain practices are recommended, although projects may select the specific activities they wish to improve, and the appropriate time lines for such actions. Additionally, projects can rely on the guidance ofmore » this document when generating ASCI Verification and Validation (VSrV) deliverables. ASCI program managers will gather information about their software engineering practices and improvement. This information can be shared to leverage the best SQE practices among development organizations. It will further be used to ensure the currency and vitality of the recommended practices. This Overview is intended to provide basic information to the LLNL ASCI software management and development staff from the ''LLNL Site-Specific ASCI Software Quality Engineering Recommended Practices VI.I'' document. Additionally the Overview provides steps to using the ''LLNL Site-Specific ASCI Software Quality Engineering Recommended Practices VI.I'' document. For definitions of terminology and acronyms, refer to the Glossary and Acronyms sections in the ''LLNL Site-Specific ASCI Software Quality Engineering Recommended Practices VI.I''.« less

Expanding the chemical diversity of natural esters by engineering a polyketide-derived pathway into Escherichia coli.

PubMed

Menendez-Bravo, Simón; Comba, Santiago; Sabatini, Martín; Arabolaza, Ana; Gramajo, Hugo

2014-07-01

Microbial fatty acid (FA)-derived molecules have emerged as promising alternatives to petroleum-based chemicals for reducing dependence on fossil hydrocarbons. However, native FA biosynthetic pathways often yield limited structural diversity, and therefore restricted physicochemical properties, of the end products by providing only a limited variety of usually linear hydrocarbons. Here we have engineered into Escherichia coli a mycocerosic polyketide synthase-based biosynthetic pathway from Mycobacterium tuberculosis and redefined its biological role towards the production of multi-methyl-branched-esters (MBEs) with novel chemical structures. Expression of FadD28, Mas and PapA5 enzymes enabled the biosynthesis of multi-methyl-branched-FA and their further esterification to an alcohol. The high substrate tolerance of these enzymes towards different FA and alcohol moieties resulted in the biosynthesis of a broad range of MBE. Further metabolic engineering of the MBE producer strain coupled this system to long-chain-alcohol biosynthetic pathways resulting in de novo production of branched wax esters following addition of only propionate. Copyright © 2014 International Metabolic Engineering Society. Published by Elsevier Inc. All rights reserved.

The Effective Use of Professional Software in an Undergraduate Mining Engineering Curriculum

ERIC Educational Resources Information Center

Kecojevic, Vladislav; Bise, Christopher; Haight, Joel

2005-01-01

The use of professional software is an integral part of a student's education in the mining engineering curriculum at The Pennsylvania State University. Even though mining engineering represents a limited market across U.S. educational institutions, the goal still exists for using this type of software to enrich the learning environment with…

The Curiosity Mars Rover's Fault Protection Engine

NASA Technical Reports Server (NTRS)

Benowitz, Ed

2014-01-01

The Curiosity Rover, currently operating on Mars, contains flight software onboard to autonomously handle aspects of system fault protection. Over 1000 monitors and 39 responses are present in the flight software. Orchestrating these behaviors is the flight software's fault protection engine. In this paper, we discuss the engine's design, responsibilities, and present some lessons learned for future missions.

A Guideline of Using Case Method in Software Engineering Courses

ERIC Educational Resources Information Center

Zainal, Dzulaiha Aryanee Putri; Razali, Rozilawati; Shukur, Zarina

2014-01-01

Software Engineering (SE) education has been reported to fall short in producing high quality software engineers. In seeking alternative solutions, Case Method (CM) is regarded as having potential to solve the issue. CM is a teaching and learning (T&L) method that has been found to be effective in Social Science education. In principle,…

Success Factors for Using Case Method in Teaching and Learning Software Engineering

ERIC Educational Resources Information Center

Razali, Rozilawati; Zainal, Dzulaiha Aryanee Putri

2013-01-01

The Case Method (CM) has long been used effectively in Social Science education. Its potential use in Applied Science such as Software Engineering (SE) however has yet to be further explored. SE is an engineering discipline that concerns the principles, methods and tools used throughout the software development lifecycle. In CM, subjects are…

Network Profiling Using Flow

DTIC Science & Technology

2012-08-01

Software Engineering Institute, a federally funded research and development center. Any opinions, findings and conclusions or recommendations...CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF...required for any other external and/or commercial use. Requests for permission should be directed to the Software Engineering Institute at permission

Engineering Three-dimensional Epithelial Tissues Embedded within Extracellular Matrix.

PubMed

Piotrowski-Daspit, Alexandra S; Nelson, Celeste M

2016-07-10

The architecture of branched organs such as the lungs, kidneys, and mammary glands arises through the developmental process of branching morphogenesis, which is regulated by a variety of soluble and physical signals in the microenvironment. Described here is a method created to study the process of branching morphogenesis by forming engineered three-dimensional (3D) epithelial tissues of defined shape and size that are completely embedded within an extracellular matrix (ECM). This method enables the formation of arrays of identical tissues and enables the control of a variety of environmental factors, including tissue geometry, spacing, and ECM composition. This method can also be combined with widely used techniques such as traction force microscopy (TFM) to gain more information about the interactions between cells and their surrounding ECM. The protocol can be used to investigate a variety of cell and tissue processes beyond branching morphogenesis, including cancer invasion.

Dental Informatics tool “SOFPRO” for the study of oral submucous fibrosis

PubMed Central

Erlewad, Dinesh Masajirao; Mundhe, Kalpana Anandrao; Hazarey, Vinay K

2016-01-01

Background: Dental informatics is an evolving branch widely used in dental education and practice. Numerous applications that support clinical care, education and research have been developed. However, very few such applications are developed and utilized in the epidemiological studies of oral submucous fibrosis (OSF) which is affecting a significant population of Asian countries. Aims and Objectives: To design and develop an user friendly software for the descriptive epidemiological study of OSF. Materials and Methods: With the help of a software engineer a computer program SOFPRO was designed and developed by using, Ms-Visual Basic 6.0 (VB), Ms-Access 2000, Crystal Report 7.0 and Ms-Paint in operating system XP. For the analysis purpose the available OSF data from the departmental precancer registry was fed into the SOFPRO. Results: Known data, not known and null data are successfully accepted in data entry and represented in data analysis of OSF. Smooth working of SOFPRO and its correct data flow was tested against real-time data of OSF. Conclusion: SOFPRO was found to be a user friendly automated tool for easy data collection, retrieval, management and analysis of OSF patients. PMID:27601808

IPAD project overview

NASA Technical Reports Server (NTRS)

Fulton, R. E.

1980-01-01

To respond to national needs for improved productivity in engineering design and manufacturing, a NASA supported joint industry/government project is underway denoted Integrated Programs for Aerospace-Vehicle Design (IPAD). The objective is to improve engineering productivity through better use of computer technology. It focuses on development of technology and associated software for integrated company-wide management of engineering information. The project has been underway since 1976 under the guidance of an Industry Technical Advisory Board (ITAB) composed of representatives of major engineering and computer companies and in close collaboration with the Air Force Integrated Computer-Aided Manufacturing (ICAM) program. Results to date on the IPAD project include an in-depth documentation of a representative design process for a large engineering project, the definition and design of computer-aided design software needed to support that process, and the release of prototype software to integrate selected design functions. Ongoing work concentrates on development of prototype software to manage engineering information, and initial software is nearing release.

A Discussion of the Software Quality Assurance Role

NASA Technical Reports Server (NTRS)

Kandt, Ronald Kirk

2010-01-01

The basic idea underlying this paper is that the conventional understanding of the role of a Software Quality Assurance (SQA) engineer is unduly limited. This is because few have asked who the customers of a SQA engineer are. Once you do this, you can better define what tasks a SQA engineer should perform, as well as identify the knowledge and skills that such a person should have. The consequence of doing this is that a SQA engineer can provide greater value to his or her customers. It is the position of this paper that a SQA engineer providing significant value to his or her customers must not only assume the role of an auditor, but also that of a software and systems engineer. This is because software engineers and their managers particularly value contributions that directly impact products and their development. These ideas are summarized as lessons learned, based on my experience at Jet Propulsion Laboratory (JPL).

Resources for Teachers. "Turning Ideas Into Reality: The Executive Branch Fosters Engineering Excellence." An Institute for Pre-College Science and Social Studies Teachers (West Hartford, Connecticut, February 18-19, 24-26, 1989). Revised.

ERIC Educational Resources Information Center

Pierce, Preston E., Comp.

A compilation of resources is provided for those interested in examining action taken by the executive branch of the federal government to foster scientific and engineering excellence in the United States in the nineteenth century. The resources are intended for use by pre-college secondary science and social studies teachers. Each of the…

Measured Properties of Turbulent Premixed Flames for Model Assessment, Including Burning Velocities, Stretch Rates, and Surface Densities (Postprint)

DTIC Science & Technology

2006-10-01

Engineering) Campbell D. Carter and Jeffrey M. Donbar (Aerospace Propulsion Division, Propulsion Sciences Branch (AFRL/ PRAS )) 5f. WORK UNIT NUMBER...Sciences Branch (AFRL/ PRAS ) Propulsion Directorate Air Force Research Laboratory, Air Force Materiel Command Wright-Patterson AFB, OH 45433-7251 Uni. of...M. Donbar b a Department of Aerospace Engineering, University of Michigan, Ann Arbor, MI 48109, USA b Air Force Research Laboratory AFRL/ PRAS , Wright

Testing Scientific Software: A Systematic Literature Review.

PubMed

Kanewala, Upulee; Bieman, James M

2014-10-01

Scientific software plays an important role in critical decision making, for example making weather predictions based on climate models, and computation of evidence for research publications. Recently, scientists have had to retract publications due to errors caused by software faults. Systematic testing can identify such faults in code. This study aims to identify specific challenges, proposed solutions, and unsolved problems faced when testing scientific software. We conducted a systematic literature survey to identify and analyze relevant literature. We identified 62 studies that provided relevant information about testing scientific software. We found that challenges faced when testing scientific software fall into two main categories: (1) testing challenges that occur due to characteristics of scientific software such as oracle problems and (2) testing challenges that occur due to cultural differences between scientists and the software engineering community such as viewing the code and the model that it implements as inseparable entities. In addition, we identified methods to potentially overcome these challenges and their limitations. Finally we describe unsolved challenges and how software engineering researchers and practitioners can help to overcome them. Scientific software presents special challenges for testing. Specifically, cultural differences between scientist developers and software engineers, along with the characteristics of the scientific software make testing more difficult. Existing techniques such as code clone detection can help to improve the testing process. Software engineers should consider special challenges posed by scientific software such as oracle problems when developing testing techniques.

An Investigation of an Open-Source Software Development Environment in a Software Engineering Graduate Course

ERIC Educational Resources Information Center

Ge, Xun; Huang, Kun; Dong, Yifei

2010-01-01

A semester-long ethnography study was carried out to investigate project-based learning in a graduate software engineering course through the implementation of an Open-Source Software Development (OSSD) learning environment, which featured authentic projects, learning community, cognitive apprenticeship, and technology affordances. The study…

Implementing Large Projects in Software Engineering Courses

ERIC Educational Resources Information Center

Coppit, David

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

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.

IMCAT: Image and Catalogue Manipulation Software

NASA Astrophysics Data System (ADS)

Kaiser, Nick

2011-08-01

The IMCAT software was developed initially to do faint galaxy photometry for weak lensing studies, and provides a fairly complete set of tools for this kind of work. Unlike most packages for doing data analysis, the tools are standalone unix commands which you can invoke from the shell, via shell scripts or from perl scripts. The tools are arranges in a tree of directories. One main branch is the ’imtools’. These deal only with fits files. The most important imtool is the ’image calculator’ ’ic’ which allows one to do rather general operations on fits images. A second branch is the ’catools’ which operate only on catalogues. The key cattool is ’lc’; this effectively defines the format of IMCAT catalogues, and allows one to do very general operations on and filtering of such catalogues. A third branch is the ’imcattools’. These tend to be much more specialised than the cattools and imcattools and are focussed on faint galaxy photometry.

Enhancing requirements engineering for patient registry software systems with evidence-based components.

PubMed

Lindoerfer, Doris; Mansmann, Ulrich

2017-07-01

Patient registries are instrumental for medical research. Often their structures are complex and their implementations use composite software systems to meet the wide spectrum of challenges. Commercial and open-source systems are available for registry implementation, but many research groups develop their own systems. Methodological approaches in the selection of software as well as the construction of proprietary systems are needed. We propose an evidence-based checklist, summarizing essential items for patient registry software systems (CIPROS), to accelerate the requirements engineering process. Requirements engineering activities for software systems follow traditional software requirements elicitation methods, general software requirements specification (SRS) templates, and standards. We performed a multistep procedure to develop a specific evidence-based CIPROS checklist: (1) A systematic literature review to build a comprehensive collection of technical concepts, (2) a qualitative content analysis to define a catalogue of relevant criteria, and (3) a checklist to construct a minimal appraisal standard. CIPROS is based on 64 publications and covers twelve sections with a total of 72 items. CIPROS also defines software requirements. Comparing CIPROS with traditional software requirements elicitation methods, SRS templates and standards show a broad consensus but differences in issues regarding registry-specific aspects. Using an evidence-based approach to requirements engineering for registry software adds aspects to the traditional methods and accelerates the software engineering process for registry software. The method we used to construct CIPROS serves as a potential template for creating evidence-based checklists in other fields. The CIPROS list supports developers in assessing requirements for existing systems and formulating requirements for their own systems, while strengthening the reporting of patient registry software system descriptions. It may be a first step to create standards for patient registry software system assessments. Copyright © 2017 Elsevier Inc. All rights reserved.

Proceedings of the Eighteenth Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1993-01-01

The workshop provided a forum for software practitioners from around the world to exchange information on the measurement, use, and evaluation of software methods, models, and tools. This year, approximately 450 people attended the workshop, which consisted of six sessions on the following topics: the Software Engineering Laboratory, measurement, technology assessment, advanced concepts, process, and software engineering issues in NASA. Three presentations were given in each of the topic areas. The content of those presentations and the research papers detailing the work reported are included in these proceedings. The workshop concluded with a tutorial session on how to start an Experience Factory.

A Brief Study of Software Engineering Professional Continuing Education in DoD Acquisition

DTIC Science & Technology

2010-04-01

Lifecycle Processes (IEEE 12207 ) (810) 37% 61% 2% Guide to the Software Engineering Body of K l d (SWEBOK) (804) 67% 31% 2% now e ge Software...Engineering-Software Measurement Process ( ISO /IEC 15939) (797) 55% 44% 2% Capability Maturity Model Integration (806) 17% 81% 2% Six Sigma Process...Improvement (804) 7% 91% 1% ISO 9000 Quality Management Systems (803) 10% 89% 1% 28 Conclusions Significant problem areas R i tequ remen s Management Very

Materials Test Branch

NASA Technical Reports Server (NTRS)

Gordon, Gail

2012-01-01

The Materials Test Branch resides at Marshall Space Flight Center's Materials and Processing laboratory and has a long history of supporting NASA programs from Mercury to the recently retired Space Shuttle. The Materials Test Branch supports its customers by supplying materials testing expertise in a wide range of applications. The Materials Test Branch is divided into three Teams, The Chemistry Team, The Tribology Team and the Mechanical Test Team. Our mission and goal is to provide world-class engineering excellence in materials testing with a special emphasis on customer service.

Midwest Structural Sciences Center 2010 Annual Report

DTIC Science & Technology

2011-06-01

S. MICHAEL SPOTTSWOOD MICHAEL J. SHEPARD , Chief Senior Aerospace Engineer Analytical Mechanics Branch Analytical Mechanics Branch Structures...Structural Dynamics & Materials Confe- rence, Chicago , IL, Apr. 7-10, 2008. AIAA 2008-2077. Efstathiou C., Carroll J., Sehitoglu H., Lambros J

Proceedings of the Twenty-Third Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1999-01-01

The Twenty-third Annual Software Engineering Workshop (SEW) provided 20 presentations designed to further the goals of the Software Engineering Laboratory (SEL) of the NASA-GSFC. The presentations were selected on their creativity. The sessions which were held on 2-3 of December 1998, centered on the SEL, Experimentation, Inspections, Fault Prediction, Verification and Validation, and Embedded Systems and Safety-Critical Systems.

Reverse Engineering and Software Products Reuse to Teach Collaborative Web Portals: A Case Study with Final-Year Computer Science Students

ERIC Educational Resources Information Center

Medina-Dominguez, Fuensanta; Sanchez-Segura, Maria-Isabel; Mora-Soto, Arturo; Amescua, Antonio

2010-01-01

The development of collaborative Web applications does not follow a software engineering methodology. This is because when university students study Web applications in general, and collaborative Web portals in particular, they are not being trained in the use of software engineering techniques to develop collaborative Web portals. This paper…

A Structured Approach for Reviewing Architecture Documentation

DTIC Science & Technology

2009-12-01

as those found in ISO 12207 [ ISO /IEC 12207 :2008] (for software engineering), ISO 15288 [ ISO /IEC 15288:2008] (for systems engineering), the Rational...Open Distributed Processing - Reference Model: Foundations ( ISO /IEC 10746-2). 1996. [ ISO /IEC 12207 :2008] International Organization for...Standardization & International Electrotechnical Commission. Sys- tems and software engineering – Software life cycle processes ( ISO /IEC 12207 ). 2008. [ ISO

Changes in Transferable Knowledge Resulting from Study in a Graduate Software Engineering Curriculum

ERIC Educational Resources Information Center

Bareiss, Ray; Sedano, Todd; Katz, Edward

2012-01-01

This paper presents the initial results of a study of the evolution of students' knowledge of software engineering from the beginning to the end of a master's degree curriculum in software engineering. Students were presented with a problem involving the initiation of a complex new project at the beginning of the program and again at the end of…

The Relationship between Job Satisfaction and Intent to Turnover among Software Engineers in the Information Technology Industry

ERIC Educational Resources Information Center

Agada, Chuks N.

2013-01-01

The focus of this study was to examine the relationship between job satisfaction and intent to turnover among software engineers in the information technology (IT) industry. The population that was analyzed in this study was software engineers in the IT industry to determine whether there is a relationship between job satisfaction and intent to…

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

NASA Technical Reports Server (NTRS)

1990-01-01

Papers presented at RICIS Software Engineering Symposium are compiled. The following subject areas are covered: synthesis - integrating product and process; Serpent - a user interface management system; prototyping distributed simulation networks; and software reuse.

Software Engineering Laboratory (SEL) data and information policy

NASA Technical Reports Server (NTRS)

Mcgarry, Frank

1991-01-01

The policies and overall procedures that are used in distributing and in making available products of the Software Engineering Laboratory (SEL) are discussed. The products include project data and measures, project source code, reports, and software tools.

Modernizing Systems and Software: How Evolving Trends in Future Trends in Systems and Software Technology Bode Well for Advancing the Precision of Technology

DTIC Science & Technology

2009-04-23

of Code Need for increased functionality will be a forcing function to bring the fields of software and systems engineering... of Software-Intensive Systems is Increasing 3 How Evolving Trends in Systems and Software Technologies Bode Well for Advancing the Precision of ...Engineering in Continued Partnership 4 How Evolving Trends in Systems and Software Technologies Bode Well for Advancing the

Assessing students' performance in software requirements engineering education using scoring rubrics

NASA Astrophysics Data System (ADS)

Mkpojiogu, Emmanuel O. C.; Hussain, Azham

2017-10-01

The study investigates how helpful the use of scoring rubrics is, in the performance assessment of software requirements engineering students and whether its use can lead to students' performance improvement in the development of software requirements artifacts and models. Scoring rubrics were used by two instructors to assess the cognitive performance of a student in the design and development of software requirements artifacts. The study results indicate that the use of scoring rubrics is very helpful in objectively assessing the performance of software requirements or software engineering students. Furthermore, the results revealed that the use of scoring rubrics can also produce a good achievement assessments direction showing whether a student is either improving or not in a repeated or iterative assessment. In a nutshell, its use leads to the performance improvement of students. The results provided some insights for further investigation and will be beneficial to researchers, requirements engineers, system designers, developers and project managers.

Framework Support For Knowledge-Based Software Development

NASA Astrophysics Data System (ADS)

Huseth, Steve

1988-03-01

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

Engine Structures Modeling Software System (ESMOSS)

NASA Technical Reports Server (NTRS)

1991-01-01

Engine Structures Modeling Software System (ESMOSS) is the development of a specialized software system for the construction of geometric descriptive and discrete analytical models of engine parts, components, and substructures which can be transferred to finite element analysis programs such as NASTRAN. The NASA Lewis Engine Structures Program is concerned with the development of technology for the rational structural design and analysis of advanced gas turbine engines with emphasis on advanced structural analysis, structural dynamics, structural aspects of aeroelasticity, and life prediction. Fundamental and common to all of these developments is the need for geometric and analytical model descriptions at various engine assembly levels which are generated using ESMOSS.

Flowfield computer graphics

NASA Technical Reports Server (NTRS)

Desautel, Richard

1993-01-01

The objectives of this research include supporting the Aerothermodynamics Branch's research by developing graphical visualization tools for both the branch's adaptive grid code and flow field ray tracing code. The completed research for the reporting period includes development of a graphical user interface (GUI) and its implementation into the NAS Flowfield Analysis Software Tool kit (FAST), for both the adaptive grid code (SAGE) and the flow field ray tracing code (CISS).

Increasing the reliability of ecological models using modern software engineering techniques

Treesearch

Robert M. Scheller; Brian R. Sturtevant; Eric J. Gustafson; Brendan C. Ward; David J. Mladenoff

2009-01-01

Modern software development techniques are largely unknown to ecologists. Typically, ecological models and other software tools are developed for limited research purposes, and additional capabilities are added later, usually in an ad hoc manner. Modern software engineering techniques can substantially increase scientific rigor and confidence in ecological models and...

Effects of the Meetings-Flow Approach on Quality Teamwork in the Training of Software Capstone Projects

ERIC Educational Resources Information Center

Chen, Chung-Yang; Hong, Ya-Chun; Chen, Pei-Chi

2014-01-01

Software development relies heavily on teamwork; determining how to streamline this collaborative development is an essential training subject in computer and software engineering education. A team process known as the meetings-flow (MF) approach has recently been introduced in software capstone projects in engineering programs at various…

The Significance of Including an Entrepreneurship Course in Engineering Programs

ERIC Educational Resources Information Center

Mosly, Ibrahim

2017-01-01

This paper studied the significance of entrepreneurship education in engineering programs. It looked into its influence on engineering students' perception and willingness to change their future job direction. The study was performed at the College of Engineering-Rabigh Branch, of King Abdulaiziz University in Saudi Arabia. Entrepreneurship…

Interpreting CMMI High Maturity for Small Organizations

DTIC Science & Technology

2008-09-01

Stoddard September, 2008 Congreso Internacional en Ingeniería de Software y sus Aplicaciones (International Congress of Software Engineering d...Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18 Congreso Internacional en Ingeniería de Software y sus Aplicaciones (International Congress of...de Software y sus Aplicaciones (International Congress of Software Engineering and its Applications) Why This Workshop? CMMI Process Performance

National Program for Inspection of Non-Federal Dams. Knox Mill Dam (ME 00276), Megunticook River Basin, Camden, Maine. Phase I Inspection Report.

DTIC Science & Technology

1978-08-01

been furnished the owner, Camden Water & Power Co., 33 Mechanic Street, ..... a ine 0,-43. Co-ies of this report will be made available to the public...gn Branch Engineering Division SAUL CO ER, Member Chief, Water Control Branch Engineering Division APPROVAL RECOMMENDED: JOE B. FRYAR Chief...Camden Water & Power Co. 33 Mechanic Street Camden, Maine 04843 Tne Camden Water and Power Company is an affiliate of Knox Woolen Mills Company. f

A Broadband High-Gain Bi-Layer Log-Periodic Dipole Array (LPDA) for Ultra High Frequency (UHF) Conformal Load Bearing Antenna Structures (CLAS) Applications

DTIC Science & Technology

2014-08-01

AFRL-RQ-WP-TR-2014-0212 University of South Carolina Department of Electrical Engineering Columbia, SC 29208 Structures Technology Branch...S2603-04-C01. Cleared for Public Release - Case Number: . Nicholas Bishop and M. Ali are with the Department of Electrical Engineering, University of...Lower substrate Upper substrate Foam core Coax Feed tube LPDA traces Coax inner conductor Feed tube Copper plate Input 88ABW-2014-3668, 8

Method and apparatus for rapid stopping and starting of a thermoacoustic engine

DOEpatents

Swift, Gregory W.; Backhaus, Scott N.; Gardner, David L.

2003-11-11

A thermoacoustic engine-driven system with a hot heat exchanger, a regenerator or stack, and an ambient heat exchanger includes a side branch load for rapid stopping and starting, the side branch load being attached to a location in the thermoacoustic system having a nonzero oscillating pressure and comprising a valve, a flow resistor, and a tank connected in series. The system is rapidly stopped simply by opening the valve and rapidly started by closing the valve.

ETICS: the international software engineering service for the grid

NASA Astrophysics Data System (ADS)

Meglio, A. D.; Bégin, M.-E.; Couvares, P.; Ronchieri, E.; Takacs, E.

2008-07-01

The ETICS system is a distributed software configuration, build and test system designed to fulfil the needs of improving the quality, reliability and interoperability of distributed software in general and grid software in particular. The ETICS project is a consortium of five partners (CERN, INFN, Engineering Ingegneria Informatica, 4D Soft and the University of Wisconsin-Madison). The ETICS service consists of a build and test job execution system based on the Metronome software and an integrated set of web services and software engineering tools to design, maintain and control build and test scenarios. The ETICS system allows taking into account complex dependencies among applications and middleware components and provides a rich environment to perform static and dynamic analysis of the software and execute deployment, system and interoperability tests. This paper gives an overview of the system architecture and functionality set and then describes how the EC-funded EGEE, DILIGENT and OMII-Europe projects are using the software engineering services to build, validate and distribute their software. Finally a number of significant use and test cases will be described to show how ETICS can be used in particular to perform interoperability tests of grid middleware using the grid itself.

76 FR 61641 - Airworthiness Directives; Airbus Model A319-111, -112, and -132 Airplanes; Model A320-111, -211...

Federal Register 2010, 2011, 2012, 2013, 2014

2011-10-05

.... Comments will be available in the AD docket shortly after receipt. FOR FURTHER INFORMATION CONTACT: Sanjay... International Branch, send it to ATTN: Sanjay Ralhan, Aerospace Engineer, International Branch, ANM-116...

Testing Scientific Software: A Systematic Literature Review

PubMed Central

Kanewala, Upulee; Bieman, James M.

2014-01-01

Context Scientific software plays an important role in critical decision making, for example making weather predictions based on climate models, and computation of evidence for research publications. Recently, scientists have had to retract publications due to errors caused by software faults. Systematic testing can identify such faults in code. Objective This study aims to identify specific challenges, proposed solutions, and unsolved problems faced when testing scientific software. Method We conducted a systematic literature survey to identify and analyze relevant literature. We identified 62 studies that provided relevant information about testing scientific software. Results We found that challenges faced when testing scientific software fall into two main categories: (1) testing challenges that occur due to characteristics of scientific software such as oracle problems and (2) testing challenges that occur due to cultural differences between scientists and the software engineering community such as viewing the code and the model that it implements as inseparable entities. In addition, we identified methods to potentially overcome these challenges and their limitations. Finally we describe unsolved challenges and how software engineering researchers and practitioners can help to overcome them. Conclusions Scientific software presents special challenges for testing. Specifically, cultural differences between scientist developers and software engineers, along with the characteristics of the scientific software make testing more difficult. Existing techniques such as code clone detection can help to improve the testing process. Software engineers should consider special challenges posed by scientific software such as oracle problems when developing testing techniques. PMID:25125798

The Ignition of Two Phase Detonation by a Branching Detonation Tube

NASA Astrophysics Data System (ADS)

Xiong, Cha; Qiu, Hua; Lu, Qinwei

2017-11-01

A branching tube is available to deliver sufficient energy to directly initiate a detonation wave. But sustaining the detonation wave through a branching tube is a challenge. In this study, a preliminary exploration about a branching pulsed detonation engine with a gas-liquid mixture was carried out to evaluate filling conditions on detonation initiation. Two detonation tubes were connected by three different schemes, such as Tail-Tail, Tail-Mid, and Tail-Head. Experimental results showed only end-head connected tubes can be ignited by the branching tube, which is quite different from the results using gas fuels or pre-evaporated liquid fuel. Liquid fuel distribution is crucial for successful detonation traveling through the branching tube.

Naming in a Programming Support Environment.

DTIC Science & Technology

1984-02-01

and Control, 1974. 10. T. E. Cheatham. An Overview of the Harvard Program Development System. I; Software Engineering Environments, H. Hunke, Ed.. North...Holland Publishing Compary, 1981, pp. 253-266. 11. T. E. Cheatham. Comparing Programming Support Environments. In Software Engineering Environments...Company. 1981. Third Edition 16. F. DeRemer and H Kron Programming -inthe Large Versus Programming -in-theSmall. IEEE Transactions on Software Engineering

Data and Analysis Center for Software: An IAC in Transition.

DTIC Science & Technology

1983-06-01

reviewed and is approved for publication. * APPROVEDt Proj ect Engineer . JOHN J. MARCINIAK, Colonel, USAF Chief, Command and Control Division . FOR THE CO...SUPPLEMENTARY NOTES RADC Project Engineer : John Palaimo (COEE) It. KEY WORDS (Conilnuo n rever*e aide if necessary and identify by block numober...Software Engineering Software Technology Information Analysis Center Database Scientific and Technical Information 20. ABSTRACT (Continue on reverse side It

Interoperability in the e-Government Context

DTIC Science & Technology

2012-01-01

Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. Any opinions...Hanscom AFB, MA 01731-2125 NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS... Software Engineering Institute at permission@sei.cmu.edu. * These restrictions do not apply to U.S. government entities. CMU/SEI-2011-TN-014 | i Table

Software Safety Risk in Legacy Safety-Critical Computer Systems

NASA Technical Reports Server (NTRS)

Hill, Janice; Baggs, Rhoda

2007-01-01

Safety-critical computer systems must be engineered to meet system and software safety requirements. For legacy safety-critical computer systems, software safety requirements may not have been formally specified during development. When process-oriented software safety requirements are levied on a legacy system after the fact, where software development artifacts don't exist or are incomplete, the question becomes 'how can this be done?' The risks associated with only meeting certain software safety requirements in a legacy safety-critical computer system must be addressed should such systems be selected as candidates for reuse. This paper proposes a method for ascertaining formally, a software safety risk assessment, that provides measurements for software safety for legacy systems which may or may not have a suite of software engineering documentation that is now normally required. It relies upon the NASA Software Safety Standard, risk assessment methods based upon the Taxonomy-Based Questionnaire, and the application of reverse engineering CASE tools to produce original design documents for legacy systems.

The Flight Optimization System Weights Estimation Method

NASA Technical Reports Server (NTRS)

Wells, Douglas P.; Horvath, Bryce L.; McCullers, Linwood A.

2017-01-01

FLOPS has been the primary aircraft synthesis software used by the Aeronautics Systems Analysis Branch at NASA Langley Research Center. It was created for rapid conceptual aircraft design and advanced technology impact assessments. FLOPS is a single computer program that includes weights estimation, aerodynamics estimation, engine cycle analysis, propulsion data scaling and interpolation, detailed mission performance analysis, takeoff and landing performance analysis, noise footprint estimation, and cost analysis. It is well known as a baseline and common denominator for aircraft design studies. FLOPS is capable of calibrating a model to known aircraft data, making it useful for new aircraft and modifications to existing aircraft. The weight estimation method in FLOPS is known to be of high fidelity for conventional tube with wing aircraft and a substantial amount of effort went into its development. This report serves as a comprehensive documentation of the FLOPS weight estimation method. The development process is presented with the weight estimation process.

Impact of Ada and object-oriented design in the flight dynamics division at Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Waligora, Sharon; Bailey, John; Stark, Mike

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 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 includes this document.

Software Engineering Research/Developer Collaborations in 2005

NASA Technical Reports Server (NTRS)

Pressburger, Tom

2006-01-01

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

Certified Binaries for Software Components

DTIC Science & Technology

2007-09-01

is sponsored by the U.S. Department of Defense. The Software Engineering Institute is a federally funded research and development center sponsored...by the U.S. Department of Defense. Copyright 2007 Carnegie Mellon University. NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING

Production of branched-chain alcohols by recombinant Ralstonia eutropha in fed-batch cultivation

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

Fei, Q; Brigham, CJ; Lu, JN

Branched-chain alcohols are considered promising green energy sources due to their compatibility with existing infrastructure and their high energy density. We utilized a strain of Ralstonia eutropha capable of producing branched-chain alcohols and examined its production in flask cultures. In order to increase isobutanol and 3-methyl-1-butanol (isoamyl alcohol) productivity in the engineered strain, batch, fed-batch, and two-stage fed-batch cultures were carried out in this work. The effects of nitrogen source concentration on branched-chain alcohol production were investigated under four different initial concentrations in fermenters. A maximum 380 g m(-3) of branched-chain alcohol production was observed with 2 kg m(-3) initialmore » NH4Cl concentration in batch cultures. A pH-stat control strategy was utilized to investigate the optimum carbon source amount fed during fed-batch cultures for higher cell density. In cultures of R. eutropha strains that did not produce polyhydroxyalkanoate or branched-chain alcohols, a maximum cell dry weight of 36 kg m(-3) was observed using a fed-batch strategy, when 10 kg m(-3) carbon source was fed into culture medium. Finally, a total branched-chain alcohol titer of 790 g m(-3), the highest branched-chain alcohol yield of 0.03 g g(-1), and the maximum branched-chain alcohol productivity of 8.23 g m(-3) h(-1) were obtained from the engineered strain Re2410/pJL26 in a two-stage fed-batch culture system with pH-stat control. Isobutanol made up over 95% (mass fraction) of the total branched-chain alcohols titer produced in this study. (C) 2013 Published by Elsevier Ltd.« less

Seeing believes: Watching entangled sculpted branched DNA in real time

NASA Astrophysics Data System (ADS)

Jee, Ah-Young; Guan, Juan; Chen, Kejia; Granick, Steve

2015-03-01

The importance of branching in polymer physics is universally accepted but the details are disputed. We have sculpted DNA to various degrees of branching and used single-molecule tracking to image its diffusion in real time when entangled. By ligating three identical or varying length DNA segments, we construct symmetric and asymmetric ?Y? branches from elements of lambda-DNA with 16 um contour length, allowing for single-molecule visualization of equilibrium dynamics. Using home-written software, a full statistical distribution based on at least hundreds of trajectories is quantified with focus on discriminating arm-retraction from branch point motion. Some part of our observations is consistent with the anticipated ?relaxation through arm retraction? mechanism but other observations do not appear to be anticipated theoretically. Currently working as a researcher in Institute for Basic Science.

Statistical modeling of software reliability

NASA Technical Reports Server (NTRS)

Miller, Douglas R.

1992-01-01

This working paper discusses the statistical simulation part of a controlled software development experiment being conducted under the direction of the System Validation Methods Branch, Information Systems Division, NASA Langley Research Center. The experiment uses guidance and control software (GCS) aboard a fictitious planetary landing spacecraft: real-time control software operating on a transient mission. Software execution is simulated to study the statistical aspects of reliability and other failure characteristics of the software during development, testing, and random usage. Quantification of software reliability is a major goal. Various reliability concepts are discussed. Experiments are described for performing simulations and collecting appropriate simulated software performance and failure data. This data is then used to make statistical inferences about the quality of the software development and verification processes as well as inferences about the reliability of software versions and reliability growth under random testing and debugging.

An information model for use in software management estimation and prediction

NASA Technical Reports Server (NTRS)

Li, Ningda R.; Zelkowitz, Marvin V.

1993-01-01

This paper describes the use of cluster analysis for determining the information model within collected software engineering development data at the NASA/GSFC Software Engineering Laboratory. We describe the Software Management Environment tool that allows managers to predict development attributes during early phases of a software project and the modifications we propose to allow it to develop dynamic models for better predictions of these attributes.

CrossTalk: The Journal of Defense Software Engineering. Volume 18, Number 9

DTIC Science & Technology

2005-09-01

2004. 12. Humphrey , Watts . Introduction to the Personal Software Process SM. Addison- Wesley 1997. 13. Humphrey , Watts . Introduction to the Team...Personal Software ProcessSM (PSPSM)is a software development process orig- inated by Watts Humphrey at the Software Engineering Institute (SEI) in the...meets its commitments and bring a sense of control and predictability into an apparently chaotic project.u References 1. Humphrey , Watts . Coaching

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

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

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

2009-01-01

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

Using UML Modeling to Facilitate Three-Tier Architecture Projects in Software Engineering Courses

ERIC Educational Resources Information Center

Mitra, Sandeep

2014-01-01

This article presents the use of a model-centric approach to facilitate software development projects conforming to the three-tier architecture in undergraduate software engineering courses. Many instructors intend that such projects create software applications for use by real-world customers. While it is important that the first version of these…

Middleware Case Study: MeDICi

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

Wynne, Adam S.

2011-05-05

In many application domains in science and engineering, data produced by sensors, instruments and networks is naturally processed by software applications structured as a pipeline . Pipelines comprise a sequence of software components that progressively process discrete units of data to produce a desired outcome. For example, in a Web crawler that is extracting semantics from text on Web sites, the first stage in the pipeline might be to remove all HTML tags to leave only the raw text of the document. The second step may parse the raw text to break it down into its constituent grammatical parts, suchmore » as nouns, verbs and so on. Subsequent steps may look for names of people or places, interesting events or times so documents can be sequenced on a time line. Each of these steps can be written as a specialized program that works in isolation with other steps in the pipeline. In many applications, simple linear software pipelines are sufficient. However, more complex applications require topologies that contain forks and joins, creating pipelines comprising branches where parallel execution is desirable. It is also increasingly common for pipelines to process very large files or high volume data streams which impose end-to-end performance constraints. Additionally, processes in a pipeline may have specific execution requirements and hence need to be distributed as services across a heterogeneous computing and data management infrastructure. From a software engineering perspective, these more complex pipelines become problematic to implement. While simple linear pipelines can be built using minimal infrastructure such as scripting languages, complex topologies and large, high volume data processing requires suitable abstractions, run-time infrastructures and development tools to construct pipelines with the desired qualities-of-service and flexibility to evolve to handle new requirements. The above summarizes the reasons we created the MeDICi Integration Framework (MIF) that is designed for creating high-performance, scalable and modifiable software pipelines. MIF exploits a low friction, robust, open source middleware platform and extends it with component and service-based programmatic interfaces that make implementing complex pipelines simple. The MIF run-time automatically handles queues between pipeline elements in order to handle request bursts, and automatically executes multiple instances of pipeline elements to increase pipeline throughput. Distributed pipeline elements are supported using a range of configurable communications protocols, and the MIF interfaces provide efficient mechanisms for moving data directly between two distributed pipeline elements.« less

Survey on Intelligent Assistance for Workplace Learning in Software Engineering

NASA Astrophysics Data System (ADS)

Ras, Eric; Rech, Jörg

Technology-enhanced learning (TEL) systems and intelligent assistance systems aim at supporting software engineers during learning and work. A questionnaire-based survey with 89 responses from industry was conducted to find out what kinds of services should be provided and how, as well as to determine which software engineering phases they should focus on. In this paper, we present the survey results regarding intelligent assistance for workplace learning in software engineering. We analyzed whether specific types of assistance depend on the organization's size, the respondent's role, and the experience level. The results show a demand for TEL that supports short-term problem solving and long-term competence development at the workplace.

Automated software development workstation

NASA Technical Reports Server (NTRS)

Prouty, Dale A.; Klahr, Philip

1988-01-01

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

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. This paper describes the working group's success in identifying V&V tasks that could be performed in the domain engineering and transition levels of reuse-based software engineering. The primary motivation for V&V at the domain level is to provide assurance that the domain requirements are correct and that the domain artifacts correctly implement the domain requirements. A secondary motivation is the possible elimination of redundant V&V activities at the application level. The group also considered the criteria and motivation for performing V&V in domain engineering.

Performance Engineering as an Expert System.

ERIC Educational Resources Information Center

Harmon, Paul

1984-01-01

Considers three powerful techniques--heuristics, context trees, and search via backward chaining--that a knowledge engineer might employ to develop an expert system to automate performance engineering, i.e., the branch of instructional technology that focuses on the problems of business and industry. (MBR)

Resilience Engineering in Critical Long Term Aerospace Software Systems: A New Approach to Spacecraft Software Safety

NASA Astrophysics Data System (ADS)

Dulo, D. A.

Safety critical software systems permeate spacecraft, and in a long term venture like a starship would be pervasive in every system of the spacecraft. Yet software failure today continues to plague both the systems and the organizations that develop them resulting in the loss of life, time, money, and valuable system platforms. A starship cannot afford this type of software failure in long journeys away from home. A single software failure could have catastrophic results for the spaceship and the crew onboard. This paper will offer a new approach to developing safe reliable software systems through focusing not on the traditional safety/reliability engineering paradigms but rather by focusing on a new paradigm: Resilience and Failure Obviation Engineering. The foremost objective of this approach is the obviation of failure, coupled with the ability of a software system to prevent or adapt to complex changing conditions in real time as a safety valve should failure occur to ensure safe system continuity. Through this approach, safety is ensured through foresight to anticipate failure and to adapt to risk in real time before failure occurs. In a starship, this type of software engineering is vital. Through software developed in a resilient manner, a starship would have reduced or eliminated software failure, and would have the ability to rapidly adapt should a software system become unstable or unsafe. As a result, long term software safety, reliability, and resilience would be present for a successful long term starship mission.

Electronics and telecommunications in Poland, issues and perspectives: Part I. Society and education

NASA Astrophysics Data System (ADS)

Modelski, Józef; Romaniuk, Ryszard

2010-09-01

Electronics is under development in this country in an organized and institutional way since the beginning of 30-ties of the previous century. It grew up from electrical engineering of weak currents and its first name used popularly was communications. It was time when television was born and the radio was maturing. Electronics is a branch of research and technology which deals with generation and processing of electrical and electromagnetic signals. A subject of telecommunications is signal transmission for a distance. Electronics and telecommunications (ET) includes or is combined with other branches like: microelectronics, radioelectronics, optoelectronics, photonics, acoustoelectronics, magnetronics, bioelectronics, energoelectronics, material engineering, semiconductor physics, automation and robotics, mechatronics and microsystems, informatics, teleinformatics, software engineering and other. Devices and functional systems of ET such as computers, data warehouses, cell phones, TV sets, Internet, GPS are build of electronic components and circuits. ET is a branch which belongs to hi-tech area, where the products gather a large load of knowledge of value overcoming frequently the price of work and material. ET has recently turned to an active participant of the processes of generation, storing, processing, transportation, distribution and usage of knowledge in the society. ET started to create artificial intelligence, co-creates intellectual property, searches for knowledge in big data sets, aids medicine, extends virtual/augmented reality, builds Internet of persons and things, strengthens security, protects natural environment, facilitates our life, aids our decisions, activates individuals, equalizes chances, provides convenient personal communications and access to data, starts building a penetrating ubiquitous infrastructure, ceases to be only a branch of technology, grows into the social space, touches culture, sociology, psychology and art. Such an important role of ET is combined with the existence in the society of an adequate infrastructure which recreates the full development cycle of high technology embracing: people, institutions, finances and logistics, in this also science, higher education, education, continuous training, dissemination and outreach, professional social environment, legal basis, political support and lobbying, innovation structures, applications, industry and economy. The digest of chosen development tendencies in ET was made here from the academic perspective, in a wider scale and on this background the national one, trying to situate this branch in the society, determine its changing role to build a new technical infrastructure of a society based on knowledge, a role of builder of many practical gadgets facilitating life, a role of a big future integrator of today's single bricks into certain more useful unity. This digest does not have a character of a systematic analysis of ET. It is a kind of an arbitrary utterance of the authors inside their field of competence. The aim of this paper is to take an active part in the discussion of the academic community in this country on the development strategy of ET, choice of priorities for cyclically rebuilding economy, in competitive environments. The review paper was initiated by the Committee of Electronics and Telecommunications of Polish Academy of Sciences and was published in Polish as introductory chapter of a dedicated expertise, printed in a book format. This version makes the included opinions available for a wider community.

Electronics and telecommunications in Poland, issues and perspectives: Part II. Science, research, development, higher education

NASA Astrophysics Data System (ADS)

Modelski, Józef; Romaniuk, Ryszard

2010-09-01

Electronics is under development in this country in an organized and institutional way since the beginning of 30-ties of the previous century. It grew up from electrical engineering of weak currents and its first name used popularly was communications. It was time when television was born and the radio was maturing. Electronics is a branch of research and technology which deals with generation and processing of electrical and electromagnetic signals. A subject of telecommunications is signal transmission for a distance. Electronics and telecommunications (ET) includes or is combined with other branches like: microelectronics, radioelectronics, optoelectronics, photonics, acoustoelectronics, magnetronics, bioelectronics, energoelectronics, material engineering, semiconductor physics, automation and robotics, mechatronics and microsystems, informatics, teleinformatics, software engineering and other. Devices and functional systems of ET such as computers, data warehouses, cell phones, TV sets, Internet, GPS are build of electronic components and circuits. ET is a branch which belongs to hi-tech area, where the products gather a large load of knowledge of value overcoming frequently the price of work and material. ET has recently turned to an active participant of the processes of generation, storing, processing, transportation, distribution and usage of knowledge in the society. ET started to create artificial intelligence, co-creates intellectual property, searches for knowledge in big data sets, aids medicine, extends virtual/augmented reality, builds Internet of persons and things, strengthens security, protects natural environment, facilitates our life, aids our decisions, activates individuals, equalizes chances, provides convenient personal communications and access to data, starts building a penetrating ubiquitous infrastructure, ceases to be only a branch of technology, grows into the social space, touches culture, sociology, psychology and art. Such an important role of ET is combined with the existence in the society of an adequate infrastructure which recreates the full development cycle of high technology embracing: people, institutions, finances and logistics, in this also science, higher education, education, continuous training, dissemination and outreach, professional social environment, legal basis, political support and lobbying, innovation structures, applications, industry and economy. The digest of chosen development tendencies in ET was made here from the academic perspective, in a wider scale and on this background the national one, trying to situate this branch in the society, determine its changing role to build a new technical infrastructure of a society based on knowledge, a role of builder of many practical gadgets facilitating life, a role of a big future integrator of today's single bricks into certain more useful unity. This digest does not have a character of a systematic analysis of ET. It is a kind of an arbitrary utterance of the authors inside their field of competence. The aim of this paper is to take an active part in the discussion of the academic community in this country on the development strategy of ET, choice of priorities for cyclically rebuilding economy, in competitive environments. The review paper was initiated by the Committee of Electronics and Telecommunications of Polish Academy of Sciences and was published in Polish as introductory chapter of a dedicated expertise, printed in a book format. This version makes the included opinions available for a wider community.

Electronics and telecommunications in Poland, issues and perspectives: Part III. Innovativeness, applications, economy, development scenarios, politics

NASA Astrophysics Data System (ADS)

Modelski, Józef; Romaniuk, Ryszard

2010-09-01

Electronics is under development in this country in an organized and institutional way since the beginning of 30-ties of the previous century. It grew up from electrical engineering of weak currents and its first name used popularly was communications. It was time when television was born and the radio was maturing. Electronics is a branch of research and technology which deals with generation and processing of electrical and electromagnetic signals. A subject of telecommunications is signal transmission for a distance. Electronics and telecommunications (ET) includes or is combined with other branches like: microelectronics, radioelectronics, optoelectronics, photonics, acoustoelectronics, magnetronics, bioelectronics, energoelectronics, material engineering, semiconductor physics, automation and robotics, mechatronics and microsystems, informatics, teleinformatics, software engineering and other. Devices and functional systems of ET such as computers, data warehouses, cell phones, TV sets, Internet, GPS are build of electronic components and circuits. ET is a branch which belongs to hi-tech area, where the products gather a large load of knowledge of value overcoming frequently the price of work and material. ET has recently turned to an active participant of the processes of generation, storing, processing, transportation, distribution and usage of knowledge in the society. ET started to create artificial intelligence, co-creates intellectual property, searches for knowledge in big data sets, aids medicine, extends virtual/augmented reality, builds Internet of persons and things, strengthens security, protects natural environment, facilitates our life, aids our decisions, activates individuals, equalizes chances, provides convenient personal communications and access to data, starts building a penetrating ubiquitous infrastructure, ceases to be only a branch of technology, grows into the social space, touches culture, sociology, psychology and art. Such an important role of ET is combined with the existence in the society of an adequate infrastructure which recreates the full development cycle of high technology embracing: people, institutions, finances and logistics, in this also science, higher education, education, continuous training, dissemination and outreach, professional social environment, legal basis, political support and lobbying, innovation structures, applications, industry and economy. The digest of chosen development tendencies in ET was made here from the academic perspective, in a wider scale and on this background the national one, trying to situate this branch in the society, determine its changing role to build a new technical infrastructure of a society based on knowledge, a role of builder of many practical gadgets facilitating life, a role of a big future integrator of today's single bricks into certain more useful unity. This digest does not have a character of a systematic analysis of ET. It is a kind of an arbitrary utterance of the authors inside their field of competence. The aim of this paper is to take an active part in the discussion of the academic community in this country on the development strategy of ET, choice of priorities for cyclically rebuilding economy, in competitive environments. The review paper was initiated by the Committee of Electronics and Telecommunications of Polish Academy of Sciences and was published in Polish as introductory chapter of a dedicated expertise, printed in a book format. This version makes the included opinions available for a wider community.

Complexity Measure for the Prototype System Description Language (PSDL)

DTIC Science & Technology

2002-06-01

Albrecht, A. and Gaffney , J., Software Function Source Lines of Code and Development Effort Prediction, IEEE Transactions on Software Engineering...Through Meausrement”; Proceedings of the IEEE, Vol. 77, No. 4, April 89. Schach, Stephen, R., Software Engineering, Second Edition, IRWIN, Burr Ridge

The Hidden Job Requirements for a Software Engineer

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

Marinovici, Maria C.; Kirkham, Harold; Glass, Kevin A.

In a world increasingly operated by computers, where innovation depends on software, the software engineer’s role is changing continuously and gaining new dimensions. In commercial software development as well as scientific research environments, the way software developers are perceived is changing, because they are more important to the business than ever before. Nowadays, their job requires skills extending beyond the regular job description posted by HR, and more is expected. To advance and thrive in their new roles, the software engineers must embrace change, and practice the themes of the new era (integration, collaboration and optimization). The challenges may bemore » somehow intimidating for freshly graduated software engineers. Through this paper the authors hope to set them on a path for success, by helping them relinquish their fear of the unknown.« less

The Generalized Support Software (GSS) Domain Engineering Process: An Object-Oriented Implementation and Reuse Success at Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Condon, Steven; Hendrick, Robert; Stark, Michael E.; Steger, Warren

1997-01-01

The Flight Dynamics Division (FDD) of NASA's Goddard Space Flight Center (GSFC) recently embarked on a far-reaching revision of its process for developing and maintaining satellite support software. The new process relies on an object-oriented software development method supported by a domain specific library of generalized components. This Generalized Support Software (GSS) Domain Engineering Process is currently in use at the NASA GSFC Software Engineering Laboratory (SEL). The key facets of the GSS process are (1) an architecture for rapid deployment of FDD applications, (2) a reuse asset library for FDD classes, and (3) a paradigm shift from developing software to configuring software for mission support. This paper describes the GSS architecture and process, results of fielding the first applications, lessons learned, and future directions

Warfighting Concepts to Future Weapon System Designs (WARCON)

DTIC Science & Technology

2003-09-12

34* Software design documents rise to litigation. "* A Material List "Cost information that may support, or may * Final Engineering Process Maps be...document may include design the system as derived from the engineering design, software development, SRD. MTS Technologies, Inc. 26 FOR OFFICIAL USE...document, early in the development phase. It is software engineers produce the vision of important to establish a standard, formal the design effort. As

Building Safer Systems With SpecTRM

NASA Technical Reports Server (NTRS)

2003-01-01

System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.System safety, an integral component in software development, often poses a challenge to engineers designing computer-based systems. While the relaxed constraints on software design allow for increased power and flexibility, this flexibility introduces more possibilities for error. As a result, system engineers must identify the design constraints necessary to maintain safety and ensure that the system and software design enforces them. Safeware Engineering Corporation, of Seattle, Washington, provides the information, tools, and techniques to accomplish this task with its Specification Tools and Requirements Methodology (SpecTRM). NASA assisted in developing this engineering toolset by awarding the company several Small Business Innovation Research (SBIR) contracts with Ames Research Center and Langley Research Center. The technology benefits NASA through its applications for Space Station rendezvous and docking. SpecTRM aids system and software engineers in developing specifications for large, complex safety critical systems. The product enables engineers to find errors early in development so that they can be fixed with the lowest cost and impact on the system design. SpecTRM traces both the requirements and design rationale (including safety constraints) throughout the system design and documentation, allowing engineers to build required system properties into the design from the beginning, rather than emphasizing assessment at the end of the development process when changes are limited and costly.

The Use of the Software MATLAB To Improve Chemical Engineering Education.

ERIC Educational Resources Information Center

Damatto, T.; Maegava, L. M.; Filho, R. Maciel

In all the Brazilian Universities involved with the project "Prodenge-Reenge", the main objective is to improve teaching and learning procedures for the engineering disciplines. The Chemical Engineering College of Campinas State University focused its effort on the use of engineering softwares. The work developed by this project has…

Caltrans WeatherShare Phase II System: An Application of Systems and Software Engineering Process to Project Development

DOT National Transportation Integrated Search

2009-08-25

In cooperation with the California Department of Transportation, Montana State University's Western Transportation Institute has developed the WeatherShare Phase II system by applying Systems Engineering and Software Engineering processes. The system...

AUTOMOTIVE DIESEL MAINTENANCE 1. UNIT VII, ENGINE TUNE-UP--DETROIT DIESEL ENGINE.

ERIC Educational Resources Information Center

Human Engineering Inst., Cleveland, OH.

THIS MODULE OF A 30-MODULE COURSE IS DESIGNED TO DEVELOP AN UNDERSTANDING OF TUNE-UP PROCEDURES FOR DIESEL ENGINES. TOPICS ARE SCHEDULING TUNE-UPS, AND TUNE-UP PROCEDURES. THE MODULE CONSISTS OF A SELF-INSTRUCTIONAL BRANCH PROGRAMED TRAINING FILM "ENGINE TUNE-UP--DETROIT DIESEL ENGINE" AND OTHER MATERIALS. SEE VT 005 655 FOR FURTHER INFORMATION.…

Type Safe Extensible Programming

NASA Astrophysics Data System (ADS)

Chae, Wonseok

2009-10-01

Software products evolve over time. Sometimes they evolve by adding new features, and sometimes by either fixing bugs or replacing outdated implementations with new ones. When software engineers fail to anticipate such evolution during development, they will eventually be forced to re-architect or re-build from scratch. Therefore, it has been common practice to prepare for changes so that software products are extensible over their lifetimes. However, making software extensible is challenging because it is difficult to anticipate successive changes and to provide adequate abstraction mechanisms over potential changes. Such extensibility mechanisms, furthermore, should not compromise any existing functionality during extension. Software engineers would benefit from a tool that provides a way to add extensions in a reliable way. It is natural to expect programming languages to serve this role. Extensible programming is one effort to address these issues. In this thesis, we present type safe extensible programming using the MLPolyR language. MLPolyR is an ML-like functional language whose type system provides type-safe extensibility mechanisms at several levels. After presenting the language, we will show how these extensibility mechanisms can be put to good use in the context of product line engineering. Product line engineering is an emerging software engineering paradigm that aims to manage variations, which originate from successive changes in software.

Development of a Unix/VME data acquisition system

NASA Astrophysics Data System (ADS)

Miller, M. C.; Ahern, S.; Clark, S. M.

1992-01-01

The current status of a Unix-based VME data acquisition development project is described. It is planned to use existing Fortran data collection software to drive the existing CAMAC electronics via a VME CAMAC branch driver card and associated Daresbury Unix driving software. The first usable Unix driver has been written and produces single-action CAMAC cycles from test software. The data acquisition code has been implemented in test mode under Unix with few problems and effort is now being directed toward finalizing calls to the CAMAC-driving software and ultimate evaluation of the complete system.

Collected software engineering papers, volume 8

NASA Technical Reports Server (NTRS)

1990-01-01

A collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) during the period November 1989 through October 1990 is presented. 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. The seven presented papers are grouped into four major categories: (1) experimental research and evaluation of software measurement; (2) studies on models for software reuse; (3) a software tool evaluation; and (4) Ada technology and studies in the areas of reuse and specification.

Experimental software engineering: Seventeen years of lessons in the SEL

NASA Technical Reports Server (NTRS)

Mcgarry, Frank E.

1992-01-01

Seven key principles developed by the Software Engineering Laboratory (SEL) at the Goddard Space Flight Center (GSFC) of the National Aeronautics and Space Administration (NASA) are described. For the past 17 years, the SEL has been experimentally analyzing the development of production software as varying techniques and methodologies are applied in this one environment. The SEL has collected, archived, and studied detailed measures from more than 100 flight dynamics projects, thereby gaining significant insight into the effectiveness of numerous software techniques, as well as extensive experience in the overall effectiveness of 'Experimental Software Engineering'. This experience has helped formulate follow-on studies in the SEL, and it has helped other software organizations better understand just what can be accomplished and what cannot be accomplished through experimentation.

Automated Reuse of Scientific Subroutine Libraries through Deductive Synthesis

NASA Technical Reports Server (NTRS)

Lowry, Michael R.; Pressburger, Thomas; VanBaalen, Jeffrey; Roach, Steven

1997-01-01

Systematic software construction offers the potential of elevating software engineering from an art-form to an engineering discipline. The desired result is more predictable software development leading to better quality and more maintainable software. However, the overhead costs associated with the formalisms, mathematics, and methods of systematic software construction have largely precluded their adoption in real-world software development. In fact, many mainstream software development organizations, such as Microsoft, still maintain a predominantly oral culture for software development projects; which is far removed from a formalism-based culture for software development. An exception is the limited domain of safety-critical software, where the high-assuiance inherent in systematic software construction justifies the additional cost. We believe that systematic software construction will only be adopted by mainstream software development organization when the overhead costs have been greatly reduced. Two approaches to cost mitigation are reuse (amortizing costs over many applications) and automation. For the last four years, NASA Ames has funded the Amphion project, whose objective is to automate software reuse through techniques from systematic software construction. In particular, deductive program synthesis (i.e., program extraction from proofs) is used to derive a composition of software components (e.g., subroutines) that correctly implements a specification. The construction of reuse libraries of software components is the standard software engineering solution for improving software development productivity and quality.

Triamcinolone Acetonide Selectively Inhibits Angiogenesis in Small Blood Vessels and Decreases Vessel Diameter within the Vascular Tree

NASA Technical Reports Server (NTRS)

McKay, Terri L.; Gredeon, Dan J.; Vickerman, Mary B.; Hylton, alan G.; Ribita, Daniela; Olar, Harry H.; Kaiser, Peter K.; Parsons-Wingerter, Patricia

2007-01-01

The steroid triamcinolone acetonide (TA) is a potent anti-angiogenesis drug used to treat retinal vascular diseases that include diabetic retinopathy, vascular occlusions and choroidal neovascularization. To quantify the effects of TA on branching morphology within the angiogenic microvascular tree of the chorioallantoic membrane (CAM) of quail embryos. Increasing concentrations of TA (0-16 ng/ml) were applied topically on embryonic day 7 (E7) to the chorioallantoic membrane (CAM) of quail embryos cultured in Petri dishes, and incubated for an additional 24 or 48 hours until fixation. Binary (black/white) microscopic images of arterial end points were quantified by VESGEN software (for Generational Analysis of Vessel Branching) to obtain major vascular parameters that include vessel diameter (Dv), fractal dimension (Df), tortuosity (Tv) and densities of vessel area, length, number and branch point (Av, Lv, Nv and Brv). For assessment of specific changes in vascular morphology induced by TA, the VESGEN software automatically segmented the vascular tree into branching generations (G1...G10) according to changes in vessel diameter and branching. Vessel density decreased significantly up to 34% as the function of increasing concentration of TA according to Av, Lv, Brv, Nv and Df. TA selectively inhibited the growth of new, small vessels, because Lv decreased from 13.14plus or minus 0.61 cm/cm2 for controls to 8.012 plus or minus 0.82 cm/cm2 at 16 ng TA/ml in smaller branching generations (G7-G10), and for Nv from 473.83 plus or minus 29.85 cm(-)2 to 302.32 plus or minus 33.09 cm-()2. In contrast, vessel diameter (Dv) decreased throughout the vascular tree (G1-G10).

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!

Ada Software Engineering Education and Training Requirements Within the U.S. Army

DTIC Science & Technology

1988-12-01

Services and DoD. DoD Directive 3405.1 requires the use of Ada in all applications and DoD Directive 3405.2 establishes the policy of using Ada in...covers DoD structure and procedures, Army policies , and all aspects of software engineering theory, systems engineering, and software development and...acquisition policy , concept development, workload requirements, contracting, and maintenance. The second course covers many of the same areas

Commonality and Variability Analysis for Xenon Family of Separation Virtual Machine Monitors (CVAX)

DTIC Science & Technology

2017-07-18

technical approach is a systematic application of Software Product Line Engineering (SPLE). A systematic application requires describing the family and... engineering Software family September 2016 – October 2016 OSD/OUSD/ATL/ASD(R&E)/RDOffice of Information Systems & Cyber Security RD / ASD(R&E) / AT&L...by the evolving open-source Xen hypervisor. The technical approach is a systematic application of Software Product Line Engineering (SPLE). A

CrossTalk: The Journal of Defense Software Engineering. Volume 21, Number 9

DTIC Science & Technology

2008-09-01

including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson...SEP 2008 2. REPORT TYPE 3. DATES COVERED 00-00-2008 to 00-00-2008 4. TITLE AND SUBTITLE CrossTalk: The Journal of Defense Software Engineering...The Journal of Defense Software Engineering September 2008 4 10 15 19 24 26 Securing Legacy C Applications Using Dynamic Data Flow Analysis This

Investigation of the current requirements engineering practices among software developers at the Universiti Utara Malaysia Information Technology (UUMIT) centre

NASA Astrophysics Data System (ADS)

Hussain, Azham; Mkpojiogu, Emmanuel O. C.; Abdullah, Inam

2016-08-01

Requirements Engineering (RE) is a systemic and integrated process of eliciting, elaborating, negotiating, validating and managing of the requirements of a system in a software development project. UUM has been supported by various systems developed and maintained by the UUM Information Technology (UUMIT) Centre. The aim of this study was to assess the current requirements engineering practices at UUMIT. The main problem that prompted this research is the lack of studies that support software development activities at the UUMIT. The study is geared at helping UUMIT produce quality but time and cost saving software products by implementing cutting edge and state of the art requirements engineering practices. Also, the study contributes to UUM by identifying the activities needed for software development so that the management will be able to allocate budget to provide adequate and precise training for the software developers. Three variables were investigated: Requirement Description, Requirements Development (comprising: Requirements Elicitation, Requirements Analysis and Negotiation, Requirements Validation), and Requirement Management. The results from the study showed that the current practice of requirement engineering in UUMIT is encouraging, but still need further development and improvement because a few RE practices were seldom practiced.

Software engineering technology transfer: Understanding the process

NASA Technical Reports Server (NTRS)

Zelkowitz, Marvin V.

1993-01-01

Technology transfer is of crucial concern to both government and industry today. In this report, the mechanisms developed by NASA to transfer technology are explored and the actual mechanisms used to transfer software development technologies are investigated. Time, cost, and effectiveness of software engineering technology transfer is reported.

Information Systems and Software Engineering Research and Education in Oulu until the 1990s

NASA Astrophysics Data System (ADS)

Oinas-Kukkonen, Henry; Kerola, Pentti; Oinas-Kukkonen, Harri; Similä, Jouni; Pulli, Petri

This paper discusses the internationalization of software business in the Oulu region. Despite its small size, the region grew rapidly and very successfully into a global information and communication technology business center. The University of Oulu, which was the northern most university in the world at the time of its establishment (1958) had a strong emphasis on engineering since its very beginning. Research on electronics was carried out since the early 1960s. Later, when the Department of Information Processing Science was founded in 1969, research on information systems and later also on software engineering was carried out. This paper discusses the role of the information systems and software engineering research for the business growth of the region. Special emphasis is put on understanding the role of system-theoretical and software development expertise for transferring research knowledge into practice.

Towards a controlled vocabulary on software engineering education

NASA Astrophysics Data System (ADS)

Pizard, Sebastián; Vallespir, Diego

2017-11-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 approach to understand a thematic area. This study examines previous publications in software engineering education to obtain a first controlled vocabulary (a more formal definition of a classification schema) in the field. Publications from 1988 to 2014 were collected and processed using automatic clustering techniques and the outcomes were analysed manually. The result is an initial controlled vocabulary with a taxonomy form with 43 concepts that were identified as the most used in the research publications. We present the classification of the concepts in three facets: 'what to teach', 'how to teach' and 'where to teach' and the evolution of concepts over time.

Research progress of microbial corrosion of reinforced concrete structure

NASA Astrophysics Data System (ADS)

Li, Shengli; Li, Dawang; Jiang, Nan; Wang, Dongwei

2011-04-01

Microbial corrosion of reinforce concrete structure is a new branch of learning. This branch deals with civil engineering , environment engineering, biology, chemistry, materials science and so on and is a interdisciplinary area. Research progress of the causes, research methods and contents of microbial corrosion of reinforced concrete structure is described. The research in the field is just beginning and concerted effort is needed to go further into the mechanism of reinforce concrete structure and assess the security and natural life of reinforce concrete structure under the special condition and put forward the protective methods.

Mission and spacecraft support functions of the Materials Engineering Branch: A space oriented technology resource

NASA Technical Reports Server (NTRS)

Fisher, A.; Staugaitis, C. L.

1974-01-01

The capabilities of the Materials Engineering Branch (MEB) of the Goddard Space Flight Center, Greenbelt, Maryland, are surveyed. The specific functions of spacecraft materials review, materials processing and information dissemination, and laboratory support, are outlined in the Activity Report. Further detail is provided by case histories of laboratory satellite support and equipment. Project support statistics are shown, and complete listings of MEB publications, patents, and tech briefs are included. MEB staff, and their respective discipline areas and spacecraft liaison associations, are listed.

Mental Models of Software Forecasting

NASA Technical Reports Server (NTRS)

Hihn, J.; Griesel, A.; Bruno, K.; Fouser, T.; Tausworthe, R.

1993-01-01

The majority of software engineers resist the use of the currently available cost models. One problem is that the mathematical and statistical models that are currently available do not correspond with the mental models of the software engineers. In an earlier JPL funded study (Hihn and Habib-agahi, 1991) it was found that software engineers prefer to use analogical or analogy-like techniques to derive size and cost estimates, whereas curren CER's hide any analogy in the regression equations. In addition, the currently available models depend upon information which is not available during early planning when the most important forecasts must be made.

The Environment for Application Software Integration and Execution (EASIE) version 1.0. Volume 1: Executive overview

NASA Technical Reports Server (NTRS)

Rowell, Lawrence F.; Davis, John S.

1989-01-01

The Environment for Application Software Integration and Execution (EASIE) provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating many stand-alone engineering analysis programs. Using EASIE, programs are integrated through a relational database management system. Volume 1, Executive Overview, gives an overview of the functions provided by EASIE and describes their use. Three operational design systems based upon the EASIE software are briefly described.

Software engineering project management - A state-of-the-art report

NASA Technical Reports Server (NTRS)

Thayer, R. H.; Lehman, J. H.

1977-01-01

The management of software engineering projects in the aerospace industry was investigated. The survey assessed such features as contract type, specification preparation techniques, software documentation required by customers, planning and cost-estimating, quality control, the use of advanced program practices, software tools and test procedures, the education levels of project managers, programmers and analysts, work assignment, automatic software monitoring capabilities, design and coding reviews, production times, success rates, and organizational structure of the projects.

The Cloud-Based Integrated Data Viewer (IDV)

NASA Astrophysics Data System (ADS)

Fisher, Ward

2015-04-01

Maintaining software compatibility across new computing environments and the associated underlying hardware is a common problem for software engineers and scientific programmers. While there are a suite of tools and methodologies used in traditional software engineering environments to mitigate this issue, they are typically ignored by developers lacking a background in software engineering. The result is a large body of software which is simultaneously critical and difficult to maintain. Visualization software is particularly vulnerable to this problem, given the inherent dependency on particular graphics hardware and software API's. The advent of cloud computing has provided a solution to this problem, which was not previously practical on a large scale; Application Streaming. This technology allows a program to run entirely on a remote virtual machine while still allowing for interactivity and dynamic visualizations, with little-to-no re-engineering required. Through application streaming we are able to bring the same visualization to a desktop, a netbook, a smartphone, and the next generation of hardware, whatever it may be. Unidata has been able to harness Application Streaming to provide a tablet-compatible version of our visualization software, the Integrated Data Viewer (IDV). This work will examine the challenges associated with adapting the IDV to an application streaming platform, and include a brief discussion of the underlying technologies involved. We will also discuss the differences between local software and software-as-a-service.

Directed branch growth in aligned nanowire arrays.

PubMed

Beaudry, Allan L; LaForge, Joshua M; Tucker, Ryan T; Sorge, Jason B; Adamski, Nicholas L; Li, Peng; Taschuk, Michael T; Brett, Michael J

2014-01-01

Branch growth is directed along two, three, or four in-plane directions in vertically aligned nanowire arrays using vapor-liquid-solid glancing angle deposition (VLS-GLAD) flux engineering. In this work, a dynamically controlled collimated vapor flux guides branch placement during the self-catalyzed epitaxial growth of branched indium tin oxide nanowire arrays. The flux is positioned to grow branches on select nanowire facets, enabling fabrication of aligned nanotree arrays with L-, T-, or X-branching. In addition, a flux motion algorithm is designed to selectively elongate branches along one in-plane axis. Nanotrees are found to be aligned across large areas by X-ray diffraction pole figure analysis and through branch length and orientation measurements collected over 140 μm(2) from scanning electron microscopy images for each array. The pathway to guided assembly of nanowire architectures with controlled interconnectivity in three-dimensions using VLS-GLAD is discussed.

AUTOMOTIVE DIESEL MAINTENANCE 1. UNIT XX, CUMMINS DIESEL ENGINE, MAINTENANCE SUMMARY.

ERIC Educational Resources Information Center

Minnesota State Dept. of Education, St. Paul. Div. of Vocational and Technical Education.

THIS MODULE OF A 30-MODULE COURSE IS DESIGNED TO PROVIDE A SUMMARY OF THE REASONS AND PROCEDURES FOR DIESEL ENGINE MAINTENANCE. TOPICS ARE WHAT ENGINE BREAK-IN MEANS, ENGINE BREAK-IN, TORQUING BEARINGS (TEMPLATE METHOD), AND THE NEED FOR MAINTENANCE. THE MODULE CONSISTS OF A SELF-INSTRUCTIONAL BRANCH PROGRAMED TRAINING FILM "CUMMINS DIESEL ENGINE…

A Multidimensional Software Engineering Course

ERIC Educational Resources Information Center

Barzilay, O.; Hazzan, O.; Yehudai, A.

2009-01-01

Software engineering (SE) is a multidimensional field that involves activities in various areas and disciplines, such as computer science, project management, and system engineering. Though modern SE curricula include designated courses that address these various subjects, an advanced summary course that synthesizes them is still missing. Such a…

Chicago Sanitary and Ship Canal (CSSC) Marine Safety Risk Assessment

DTIC Science & Technology

2013-12-01

calculation of the rate of loss events and the associated consequences. Further, the selected tool supports a clear understanding of the drivers of failures...spreadsheet software. The event tree has a series of events stated in a success mode, or simply as the occurrence of a phenomenological condition. The...Public | December 2013 of a “transit” (when applicable). As subsequent events occur, there is a branch point, one branch representing success and the

Software Engineering Principles for Courseware Development.

ERIC Educational Resources Information Center

Magel, Kenneth

1980-01-01

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

Glossary of software engineering laboratory terms

NASA Technical Reports Server (NTRS)

1982-01-01

A glossary of terms used in the Software Engineering Laboratory (SEL) is presented. The terms are defined within the context of the software development environment for flight dynamics at Goddard Space Flight Center. A concise reference for clarifying and understanding the language employed in SEL documents and data collection forms is provided.

Software Engineering Infrastructure in a Large Virtual Campus

ERIC Educational Resources Information Center

Cristobal, Jesus; Merino, Jorge; Navarro, Antonio; Peralta, Miguel; Roldan, Yolanda; Silveira, Rosa Maria

2011-01-01

Purpose: The design, construction and deployment of a large virtual campus are a complex issue. Present virtual campuses are made of several software applications that complement e-learning platforms. In order to develop and maintain such virtual campuses, a complex software engineering infrastructure is needed. This paper aims to analyse the…

Future of Software Engineering Standards

NASA Technical Reports Server (NTRS)

Poon, Peter T.

1997-01-01

In the new millennium, software engineering standards are expected to continue to influence the process of producing software-intensive systems which are cost-effetive and of high quality. These sytems may range from ground and flight systems used for planetary exploration to educational support systems used in schools as well as consumer-oriented systems.

Evaluating Games-Based Learning

ERIC Educational Resources Information Center

Hainey, Thomas; Connolly, Thomas

2010-01-01

A highly important part of software engineering education is requirements collection and analysis, one of the initial stages of the Software Development Lifecycle. No other conceptual work is as difficult to rectify at a later stage or as damaging to the overall system if performed incorrectly. As software engineering is a field with a reputation…

Imprinting Community College Computer Science Education with Software Engineering Principles

ERIC Educational Resources Information Center

Hundley, Jacqueline Holliday

2012-01-01

Although the two-year curriculum guide includes coverage of all eight software engineering core topics, the computer science courses taught in Alabama community colleges limit student exposure to the programming, or coding, phase of the software development lifecycle and offer little experience in requirements analysis, design, testing, and…

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

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

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

2006-09-01

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

Unified Engineering Software System

NASA Technical Reports Server (NTRS)

Purves, L. R.; Gordon, S.; Peltzman, A.; Dube, M.

1989-01-01

Collection of computer programs performs diverse functions in prototype engineering. NEXUS, NASA Engineering Extendible Unified Software system, is research set of computer programs designed to support full sequence of activities encountered in NASA engineering projects. Sequence spans preliminary design, design analysis, detailed design, manufacturing, assembly, and testing. Primarily addresses process of prototype engineering, task of getting single or small number of copies of product to work. Written in FORTRAN 77 and PROLOG.

Description and field analysis of a coupled ground-water/surface-water flow model (MODFLOW/BRANCH) with modifications for structures and wetlands in southern Dade County, Florida

USGS Publications Warehouse

Swain, E.D.; Howie, Barbara; Dixon, Joann

1996-01-01

A coupled surface-water model (BRANCH) and ground-water model (MODFLOW) model were tested to simulate the interacting wetlands/surface-water/ ground-water system of southern Dade County. Several options created for the MODFLOW ground- ground-water model were used in representing this field situation. The primary option is the MODBRANCH interfacing software, which allows leakage to be accounted for between the MODFLOW ground-water model and the BRANCH dynamic model for simulation of flow in an interconnected network of open channels. A modification to an existing software routine, which is referred to as BCF2, allows cells in MODFLOW to rewet when dry--a requirement in representing the seasonal wetlands in Dade County. A companion to BCF2 is the modified evapotranspiration routine EVT2. The EVT2 routine changes the cells where evapotranspiration occurs, depending on which cells are wet. The Streamlink package represents direct connections between the canals and wetlands at locations where canals open directly into overland flow. Within the BRANCH model, the capability to represent the numerous hydraulic structures, gated spillways, gated culverts, and pumps was added. The application of these modifications to model surface-water/ground-water interactions in southern Dade County demonstrated the usefulness of the coupled MODFLOW/BRANCH model. Ground-water and surface-water flows are both simulated with dynamic models. Flow exchange between models, intermittent wetting and drying, evapotranspiration, and hydraulic structure operations are all represented appropriately. Comparison was made with a simulation using the RIV1 package instead of MODBRANCH to represent the canals. RIV1 represents the canals by user-defined stages, and computes leakage to the aquifer. Greater accuracy in reproducing measured ground- water heads was achieved with MODBRANCH, which also computes dynamic flow conditions in the canals, unlike RIV1. The surface-water integrated flow and transport two-dimensional model (SWIFT2D) was also applied to the southeastern coastal wetlands for comparison with the wetlands flow approximation made in MODFLOW. MODFLOW simulates the wetlands as a highly conductive upper layer of the aquifer, whereas SWIFT2D solves the hydrodynamic equations. Comparison in this limited test demonstrated no specific advantage for either method of representation. However, much additional testing on a wider variety of geometric and hydraulic situations, such as in areas with greater tidal or other dynamic forcing effects, is needed to make definite conclusions. A submodel of the existing southern Dade County model schematization was used to examine water-delivery alternatives proposed by the U.S. Army Corps of Engineers. For this application, the coupled MODFLOW/BRANCH model was used as a design tool. A new canal and several pumps to be tested to maintain lower water levels in a residential area (while water levels in the Everglades are raised) were added to the model schematization. The pumps were assumed to have infinite supply capacity in the model so that their maximum pumping rates during the simulation could be used to determine pump sizes.

The State of Software for Evolutionary Biology.

PubMed

Darriba, Diego; Flouri, Tomáš; Stamatakis, Alexandros

2018-05-01

With Next Generation Sequencing data being routinely used, evolutionary biology is transforming into a computational science. Thus, researchers have to rely on a growing number of increasingly complex software. All widely used core tools in the field have grown considerably, in terms of the number of features as well as lines of code and consequently, also with respect to software complexity. A topic that has received little attention is the software engineering quality of widely used core analysis tools. Software developers appear to rarely assess the quality of their code, and this can have potential negative consequences for end-users. To this end, we assessed the code quality of 16 highly cited and compute-intensive tools mainly written in C/C++ (e.g., MrBayes, MAFFT, SweepFinder, etc.) and JAVA (BEAST) from the broader area of evolutionary biology that are being routinely used in current data analysis pipelines. Because, the software engineering quality of the tools we analyzed is rather unsatisfying, we provide a list of best practices for improving the quality of existing tools and list techniques that can be deployed for developing reliable, high quality scientific software from scratch. Finally, we also discuss journal as well as science policy and, more importantly, funding issues that need to be addressed for improving software engineering quality as well as ensuring support for developing new and maintaining existing software. Our intention is to raise the awareness of the community regarding software engineering quality issues and to emphasize the substantial lack of funding for scientific software development.

Repository-Based Software Engineering Program: Working Program Management Plan

NASA Technical Reports Server (NTRS)

1993-01-01

Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents.

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

NASA Technical Reports Server (NTRS)

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

2006-01-01

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

U.S. Army Armament Research, Development and Engineering Center Grain Evaluation Software to Numerically Predict Linear Burn Regression for Solid Propellant Grain Geometries

DTIC Science & Technology

2017-10-01

ENGINEERING CENTER GRAIN EVALUATION SOFTWARE TO NUMERICALLY PREDICT LINEAR BURN REGRESSION FOR SOLID PROPELLANT GRAIN GEOMETRIES Brian...author(s) and should not be construed as an official Department of the Army position, policy, or decision, unless so designated by other documentation...U.S. ARMY ARMAMENT RESEARCH, DEVELOPMENT AND ENGINEERING CENTER GRAIN EVALUATION SOFTWARE TO NUMERICALLY PREDICT LINEAR BURN REGRESSION FOR SOLID

Infusing Software Engineering Technology into Practice at NASA

NASA Technical Reports Server (NTRS)

Pressburger, Thomas; Feather, Martin S.; Hinchey, Michael; Markosia, Lawrence

2006-01-01

We present an ongoing effort of the NASA Software Engineering Initiative to encourage the use of advanced software engineering technology on NASA projects. Technology infusion is in general a difficult process yet this effort seems to have found a modest approach that is successful for some types of technologies. We outline the process and describe the experience of the technology infusions that occurred over a two year period. We also present some lessons from the experiences.

A Model-Driven Co-Design Framework for Fusing Control and Scheduling Viewpoints.

PubMed

Sundharam, Sakthivel Manikandan; Navet, Nicolas; Altmeyer, Sebastian; Havet, Lionel

2018-02-20

Model-Driven Engineering (MDE) is widely applied in the industry to develop new software functions and integrate them into the existing run-time environment of a Cyber-Physical System (CPS). The design of a software component involves designers from various viewpoints such as control theory, software engineering, safety, etc. In practice, while a designer from one discipline focuses on the core aspects of his field (for instance, a control engineer concentrates on designing a stable controller), he neglects or considers less importantly the other engineering aspects (for instance, real-time software engineering or energy efficiency). This may cause some of the functional and non-functional requirements not to be met satisfactorily. In this work, we present a co-design framework based on timing tolerance contract to address such design gaps between control and real-time software engineering. The framework consists of three steps: controller design, verified by jitter margin analysis along with co-simulation, software design verified by a novel schedulability analysis, and the run-time verification by monitoring the execution of the models on target. This framework builds on CPAL (Cyber-Physical Action Language), an MDE design environment based on model-interpretation, which enforces a timing-realistic behavior in simulation through timing and scheduling annotations. The application of our framework is exemplified in the design of an automotive cruise control system.

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

NASA Technical Reports Server (NTRS)

Legrand, Sue; Freedman, Glenn

1988-01-01

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

A Model-Driven Co-Design Framework for Fusing Control and Scheduling Viewpoints

PubMed Central

Navet, Nicolas; Havet, Lionel

2018-01-01

Model-Driven Engineering (MDE) is widely applied in the industry to develop new software functions and integrate them into the existing run-time environment of a Cyber-Physical System (CPS). The design of a software component involves designers from various viewpoints such as control theory, software engineering, safety, etc. In practice, while a designer from one discipline focuses on the core aspects of his field (for instance, a control engineer concentrates on designing a stable controller), he neglects or considers less importantly the other engineering aspects (for instance, real-time software engineering or energy efficiency). This may cause some of the functional and non-functional requirements not to be met satisfactorily. In this work, we present a co-design framework based on timing tolerance contract to address such design gaps between control and real-time software engineering. The framework consists of three steps: controller design, verified by jitter margin analysis along with co-simulation, software design verified by a novel schedulability analysis, and the run-time verification by monitoring the execution of the models on target. This framework builds on CPAL (Cyber-Physical Action Language), an MDE design environment based on model-interpretation, which enforces a timing-realistic behavior in simulation through timing and scheduling annotations. The application of our framework is exemplified in the design of an automotive cruise control system. PMID:29461489

Repository-Based Software Engineering (RBSE) program

NASA Technical Reports Server (NTRS)

1992-01-01

Support of a software engineering program was provided in the following areas: client/customer liaison; research representation/outreach; and program support management. Additionally, a list of deliverables is presented.

The IEEE Software Engineering Standards Process

PubMed Central

Buckley, Fletcher J.

1984-01-01

Software Engineering has emerged as a field in recent years, and those involved increasingly recognize the need for standards. As a result, members of the Institute of Electrical and Electronics Engineers (IEEE) formed a subcommittee to develop these standards. This paper discusses the ongoing standards development, and associated efforts.

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.

Investigation of near-surface chemical, physical and mechanical properties of silicon carbide crystals and fibers modified by ion implantation

NASA Astrophysics Data System (ADS)

Spitznagel, J. A.; Wood, Susan

1988-08-01

The Software Engineering institute is a federally funded research and development center sponsored by the Department of Defense (DOD). It was chartered by the Undersecretary of Defense for Research and Engineering on June 15, 1984. The SEI was established and is operated by Carnegie Mellon University (CUM) under contract F19628-C-0003, which was competitively awarded on December 28, 1984, by the Air Force Electronic Systems Division. The mission of the SEI is to provide the means to bring the ablest minds and the most effective technology to bear on the rapid improvement of the quality of operational software in mission-critical computer systems; to accelerate the reduction to practice of modern software engineering techniques and methods; to promulgate the use of modern techniques and methods throughout the mission-critical systems community; and to establish standards of excellence for the practice of software engineering. This report provides a summary of the programs and projects, staff, facilities, and service accomplishments of the Software Engineering Institute during 1987.

Software Engineering Research/Developer Collaborations in 2004 (C104)

NASA Technical Reports Server (NTRS)

Pressburger, Tom; Markosian, Lawrance

2005-01-01

In 2004, six collaborations between software engineering technology providers and NASA software development personnel deployed a total of five software engineering technologies (for references, see Section 7.2) on the NASA projects. The main purposes were to benefit the projects, infuse the technologies if beneficial into NASA, and give feedback to the technology providers to improve the technologies. Each collaboration project produced a final report (for references, see Section 7.1). Section 2 of this report summarizes each project, drawing from the final reports and communications with the software developers and technology providers. Section 3 indicates paths to further infusion of the technologies into NASA practice. Section 4 summarizes some technology transfer lessons learned. Section 6 lists the acronyms used in this report.

Implementing Software Safety in the NASA Environment

NASA Technical Reports Server (NTRS)

Wetherholt, Martha S.; Radley, Charles F.

1994-01-01

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

Collaborative Research and Development (CR&D) III Task Order 0077: Fundamental Studies of Plasticity, Interfacial Boundaries and Liquid Metals

DTIC Science & Technology

2013-06-01

Interfacial Boundaries and Liquid Metals Dallas Trinkle Independent Contractor JUNE 2013 Final Report Approved for public...SIGNATURE//_________________ CHRISTOPHER WOODWARD, Project Engineer DANIEL EVANS, Chief Metals Branch Metals Branch Structural ...Materials Division Structural Materials Division ____//SIGNATURE//___________________ ROBERT T. MARSHALL, Deputy Chief

Using microsoft excel applications in the graduate intern program at Goddard Space Flight Center. M.S. Thesis

NASA Technical Reports Server (NTRS)

Antoine, Lisa

1992-01-01

An outline of the Project Operations Branch at Goddard Space Flight Center is presented that describes the management of the division and each subgroup's responsibility. The paper further describes the development of software tools for the Macintosh personal computer, and their impending implementation. A detailed step by step procedure is given for using these software tools.

Reliability Engineering for Service Oriented Architectures

DTIC Science & Technology

2013-02-01

Common Object Request Broker Architecture Ecosystem In software , an ecosystem is a set of applications and/or services that grad- ually build up over time...Enterprise Service Bus Foreign In an SOA context: Any SOA, service or software which the owners of the calling software do not have control of, either...SOA Service Oriented Architecture SRE Software Reliability Engineering System Mode Many systems exhibit different modes of operation. E.g. the cockpit

Collected software engineering papers, volume 9

NASA Technical Reports Server (NTRS)

1991-01-01

This document is a collection of selected technical papers produced by participants in the Software Engineering Laboratory (SEL) from November 1990 through October 1991. 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. This is the ninth such volume of technical papers produced by the SEL. Although these papers cover several topics related to software engineering, they do not encompass the entire scope of SEL activities and interests. For the convenience of this presentation, the eight papers contained here are grouped into three major categories: (1) software models studies; (2) software measurement studies; and (3) Ada technology studies. The first category presents studies on reuse models, including a software reuse model applied to maintenance and a model for an organization to support software reuse. The second category includes experimental research methods and software measurement techniques. The third category presents object-oriented approaches using Ada and object-oriented features proposed for Ada. The SEL is actively working to understand and improve the software development process at GSFC.

Incorporating Computer-Aided Software in the Undergraduate Chemical Engineering Core Courses

ERIC Educational Resources Information Center

Alnaizy, Raafat; Abdel-Jabbar, Nabil; Ibrahim, Taleb H.; Husseini, Ghaleb A.

2014-01-01

Introductions of computer-aided software and simulators are implemented during the sophomore-year of the chemical engineering (ChE) curriculum at the American University of Sharjah (AUS). Our faculty concurs that software integration within the curriculum is beneficial to our students, as evidenced by the positive feedback received from industry…

Artificial Intelligence Software Acquisition Program. Volume 2.

DTIC Science & Technology

1987-12-01

34Architect tire prototyping in the software engineering environment". 1BBA! .’ qtins Jo urnal, vol. 23, No. 1, p. 4-18, 1984. 3v Boehmi, Barry W_. Gray...on Artificial Intelligence, Sponsored by AAAI, December 1986. ..- ~[31] Pressman , Roger S. "Software Engineering: A Practitioner’s Approach". McGraw

An Ontology for Software Engineering Education

ERIC Educational Resources Information Center

Ling, Thong Chee; Jusoh, Yusmadi Yah; Adbullah, Rusli; Alwi, Nor Hayati

2013-01-01

Software agents communicate using ontology. It is important to build an ontology for specific domain such as Software Engineering Education. Building an ontology from scratch is not only hard, but also incur much time and cost. This study aims to propose an ontology through adaptation of the existing ontology which is originally built based on a…

Software engineering ethics

NASA Technical Reports Server (NTRS)

Bown, Rodney L.

1991-01-01

Software engineering ethics is reviewed. The following subject areas are covered: lack of a system viewpoint; arrogance of PC DOS software vendors; violation od upward compatibility; internet worm; internet worm revisited; student cheating and company hiring interviews; computing practitioners and the commodity market; new projects and old programming languages; schedule and budget; and recent public domain comments.

1001518

NASA Image and Video Library

2010-09-01

DEVELOPMENT TESTING BEING CONDUCTED AT THE REQUEST OF THE MSFC DYNAMICS, LOADS, AND STRENGTH BRANCH (EV31) TO STUDY THE FAILURE BEHAVIOR OF FASTENERS SUBJECTED TO COMBINED SHEAR AND TENSION LOADING. THE DATA FROM THIS TESTING WILL BE USED TO DEVELOP APPROPRIATE STRUCTURAL ANALYSIS METHODS AS PART OF A FASTENER STANDARDS EFFORT SPONSORED BY THE NASA ENGINEERING SAFETY CENTER (NESC). THE TEST FIXTURE WAS DESIGNED AND FABRICATED THROUGH THE MSFC MECHANICAL FABRICATION BRANCH (ES23). THE TESTING ORGANIZATION IS THE MSFC MATERIALS TEST BRANCH (EM10).

1001519

NASA Image and Video Library

2010-09-01

DEVELOPMENT TESTING BEING CONDUCTED AT THE REQUEST OF THE MSFC DYNAMICS, LOADS, AND STRENGTH BRANCH (EV31) TO STUDY THE FAILURE BEHAVIOR OF FASTENERS SUBJECTED TO COMBINED SHEAR AND TENSION LOADING. THE DATA FROM THIS TESTING WILL BE USED TO DEVELOP APPROPRIATE STRUCTURAL ANALYSIS METHODS AS PART OF A FASTENER STANDARDS EFFORT SPONSORED BY THE NASA ENGINEERING SAFETY CENTER (NESC). THE TEST FIXTURE WAS DESIGNED AND FABRICATED THROUGH THE MSFC MECHANICAL FABRICATION BRANCH (ES23). THE TESTING ORGANIZATION IS THE MSFC MATERIALS TEST BRANCH (EM10).

1001520

NASA Image and Video Library

2010-09-01

DEVELOPMENT TESTING BEING CONDUCTED AT THE REQUEST OF THE MSFC DYNAMICS, LOADS, AND STRENGTH BRANCH (EV31) TO STUDY THE FAILURE BEHAVIOR OF FASTENERS SUBJECTED TO COMBINED SHEAR AND TENSION LOADING. THE DATA FROM THIS TESTING WILL BE USED TO DEVELOP APPROPRIATE STRUCTURAL ANALYSIS METHODS AS PART OF A FASTENER STANDARDS EFFORT SPONSORED BY THE NASA ENGINEERING SAFETY CENTER (NESC). THE TEST FIXTURE WAS DESIGNED AND FABRICATED THROUGH THE MSFC MECHANICAL FABRICATION BRANCH (ES23). THE TESTING ORGANIZATION IS THE MSFC MATERIALS TEST BRANCH (EM10).

1001521

NASA Image and Video Library

2010-09-01

DEVELOPMENT TESTING BEING CONDUCTED AT THE REQUEST OF THE MSFC DYNAMICS, LOADS, AND STRENGTH BRANCH (EV31) TO STUDY THE FAILURE BEHAVIOR OF FASTENERS SUBJECTED TO COMBINED SHEAR AND TENSION LOADING. THE DATA FROM THIS TESTING WILL BE USED TO DEVELOP APPROPRIATE STRUCTURAL ANALYSIS METHODS AS PART OF A FASTENER STANDARDS EFFORT SPONSORED BY THE NASA ENGINEERING SAFETY CENTER (NESC). THE TEST FIXTURE WAS DESIGNED AND FABRICATED THROUGH THE MSFC MECHANICAL FABRICATION BRANCH (ES23). THE TESTING ORGANIZATION IS THE MSFC MATERIALS TEST BRANCH (EM10).

Aligned Carbon Nanotube Carpets on Carbon Substrates for High Power Electronic Applications

DTIC Science & Technology

2016-06-01

SiOx by a vapor-solid-solid mechanism ,” J. Am. Chem. Soc., vol. 133, pp. 197–199, 2011. [146] B. Liu, W. Ren, C. Liu, C.-H. Sun , L. Gao, S. Li, C... Mechanical and Thermal Systems Branch Power and Control Division JUNE 2016 Interim Report DISTRIBUTION STATEMENT A: Approved for public release...Advisor Program Engineer Mechanical and Thermal Systems Branch Mechanical and Thermal Systems Branch Power and Control Division Power and Control

Water-Based Coating Simplifies Circuit Board Manufacturing

NASA Technical Reports Server (NTRS)

2008-01-01

The Structures and Materials Division at Glenn Research Center is devoted to developing advanced, high-temperature materials and processes for future aerospace propulsion and power generation systems. The Polymers Branch falls under this division, and it is involved in the development of high-performance materials, including polymers for high-temperature polymer matrix composites; nanocomposites for both high- and low-temperature applications; durable aerogels; purification and functionalization of carbon nanotubes and their use in composites; computational modeling of materials and biological systems and processes; and developing polymer-derived molecular sensors. Essentially, this branch creates high-performance materials to reduce the weight and boost performance of components for space missions and aircraft engine components. Under the leadership of chemical engineer, Dr. Michael Meador, the Polymers Branch boasts world-class laboratories, composite manufacturing facilities, testing stations, and some of the best scientists in the field.

Automated real-time software development

NASA Technical Reports Server (NTRS)

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

1993-01-01

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

Proceedings of the Annual Ada Software Engineering Education and Training Symposium (6th), Held in Alexandria, Virginia on September 11-13, 1991

DTIC Science & Technology

1991-09-01

level are, by necessity, designed to be accomplished by one or a few students in the course of a single academic term. Moreover, the software is seldom...that are covered in Computer Science curricula today, but with more of an engineering structure added. A stronger engineering design component is...ing, and sound software design principles found throughout Ada, and they are unambiguously specified. These are not features which were grafted onto a

2016 KIVA-hpFE Development: A Robust and Accurate Engine Modeling Software

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

Carrington, David Bradley; Waters, Jiajia

Los Alamos National Laboratory and its collaborators are facilitating engine modeling by improving accuracy and robustness of the modeling, and improving the robustness of software. We also continue to improve the physical modeling methods. We are developing and implementing new mathematical algorithms, those that represent the physics within an engine. We provide software that others may use directly or that they may alter with various models e.g., sophisticated chemical kinetics, different turbulent closure methods or other fuel injection and spray systems.

The Research of Software Engineering Curriculum Reform

NASA Astrophysics Data System (ADS)

Kuang, Li-Qun; Han, Xie

With the problem that software engineering training can't meet the needs of the community, this paper analysis some outstanding reasons in software engineering curriculum teaching, such as old teaching contents, weak in practice and low quality of teachers etc. We propose the methods of teaching reform as guided by market demand, update the teaching content, optimize the teaching methods, reform the teaching practice, strengthen the teacher-student exchange and promote teachers and students together. We carried out the reform and explore positive and achieved the desired results.

A Survey On Management Of Software Engineering In Japan

NASA Astrophysics Data System (ADS)

Kadono, Yasuo; Tsubaki, Hiroe; Tsuruho, Seishiro

2008-05-01

The purpose of this study is to clarity the mechanism of how software engineering capabilities relate to the business performance of IT vendors in Japan. To do this, we developed a structural model using factors related to software engineering, business performance and competitive environment. By analyzing the data collected from 78 major IT vendors in Japan, we found that superior deliverables and business performance were correlated with the effort expended particularly on human resource development, quality assurance, research and development and process improvement.

AUTOMOTIVE DIESEL MAINTENANCE 1. UNIT XXX, I--CATERPILLAR DIESEL ENGINE MAINTENANCE SUMMARY, II--REIEWING FACTS ABOUT ALTERNATORS.

ERIC Educational Resources Information Center

Minnesota State Dept. of Education, St. Paul. Div. of Vocational and Technical Education.

THIS MODULE OF A 30-MODULE COURSE IS DESIGNED TO PROVIDE A SUMMARY OF DIESEL ENGINE MAINTENANCE FACTORS AND A REVIEW OF DIESEL ENGINE ALTERNATOR OPERATION. THE SEVEN SECTIONS COVER DIESEL ENGINE TROUBLESHOOTING AND THE OPERATION, TESTING, AND ADJUSTING OF ALTERNATORS. THE MODULE CONSISTS OF A SELF-INSTRUCTIONAL BRANCH PROGRAMED TRAINING FILM…

NASA Software Engineering Benchmarking Study

NASA Technical Reports Server (NTRS)

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

2013-01-01

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

OHD/HL/HSMB - Hydrologic Science & Modeling Branch

Science.gov Websites

apply these sciences to application software and data products developed within the HL and as a hydrologic services program. HSMB applies its scientific expertise to training material developed

Software-Engineering Process Simulation (SEPS) model

NASA Technical Reports Server (NTRS)

Lin, C. Y.; Abdel-Hamid, T.; Sherif, J. S.

1992-01-01

The Software Engineering Process Simulation (SEPS) model is described which was developed at JPL. SEPS is a dynamic simulation model of the software project development process. It uses the feedback principles of system dynamics to simulate the dynamic interactions among various software life cycle development activities and management decision making processes. The model is designed to be a planning tool to examine tradeoffs of cost, schedule, and functionality, and to test the implications of different managerial policies on a project's outcome. Furthermore, SEPS will enable software managers to gain a better understanding of the dynamics of software project development and perform postmodern assessments.

Teaching transportation systems thinking concepts to undergraduates.

DOT National Transportation Integrated Search

2013-05-01

Systems thinking is thought by many academics to be a graduate level educational venture. : Many traditional educators in the engineering field argue that first a student should gain a : grounding in some traditional branch of engineering (civil and ...

TIA Software User's Manual

NASA Technical Reports Server (NTRS)

Cramer, K. Elliott; Syed, Hazari I.

1995-01-01

This user's manual describes the installation and operation of TIA, the Thermal-Imaging acquisition and processing Application, developed by the Nondestructive Evaluation Sciences Branch at NASA Langley Research Center, Hampton, Virginia. TIA is a user friendly graphical interface application for the Macintosh 2 and higher series computers. The software has been developed to interface with the Perceptics/Westinghouse Pixelpipe(TM) and PixelStore(TM) NuBus cards and the GW Instruments MacADIOS(TM) input-output (I/O) card for the Macintosh for imaging thermal data. The software is also capable of performing generic image-processing functions.

76 FR 70382 - Airworthiness Directives; General Electric Company (GE) CF6-80C2B Series Turbofan Engines

Federal Register 2010, 2011, 2012, 2013, 2014

2011-11-14

... installing software version 8.2.Q1 to the engine electronic control unit (ECU), which increases the engine's... proposed AD would require the removal of the affected ECUs from service. We are proposing this AD to... software version 8.2.Q1 to the ECU, which increases the engine's margin to flameout. That AD was prompted...

CrossTalk: The Journal of Defense Software Engineering. Volume 18, Number 11

DTIC Science & Technology

2005-11-01

languages. Our discipline of software engineering has really experienced phenomenal growth right before our eyes. A sign that software design has...approach on a high level of abstraction. The main emphasis is on the identification and allocation of a needed functionality (e.g., a target tracker ), rather...messaging software that is the backbone of teenage culture. As increasing security constraints will increase the cost of developing and main- taining any

The Development of Ada (Trademark) Software for Secure Environments

DTIC Science & Technology

1986-05-23

Telecommunications environment, This paper discusses software socurity and seeks to demostrate how the Ada programming language can be utilizec as a tool...complexity 4 . We use abstraction in our lives every day to control complexity; the principles of abstraction for software engineering are ro different...systems. These features directly sup,) )-t t.ie m odernp software engineering principles d1 s I , , 1 t, thne previous section. This is not surprising

Closing the loop on improvement: Packaging experience in the Software Engineering Laboratory

NASA Technical Reports Server (NTRS)

Waligora, Sharon R.; Landis, Linda C.; Doland, Jerry T.

1994-01-01

As part of its award-winning software process improvement program, the Software Engineering Laboratory (SEL) has developed an effective method for packaging organizational best practices based on real project experience into useful handbooks and training courses. This paper shares the SEL's experience over the past 12 years creating and updating software process handbooks and training courses. It provides cost models and guidelines for successful experience packaging derived from SEL experience.

Process Tailoring and the Software Capability Maturity Model(sm).

DTIC Science & Technology

1995-11-01

A Discipline For Software Engineering, Addison-Wesley, 1995; Humphrey . This book summarizes the costs and benefits of a Personal Software Process ( PSP ...1994. [Humphrey95] Humphrey , Watts S . A Discipline For Software Engineering. Reading, MA: Addison-Wesley Publishing Company, 1995. CMUISEI-94-TR-24 43...practiced and institutionalized. 8 CMU/SEI-94-TR-24 . Leveraging mo n o s I cDocument" IRevise & Analyze Organizational LessonsApproach ’"- Define Processes

The Software Engineering Laboratory: An operational software experience factory

NASA Technical Reports Server (NTRS)

Basili, Victor R.; Caldiera, Gianluigi; Mcgarry, Frank; Pajerski, Rose; Page, Gerald; Waligora, Sharon

1992-01-01

For 15 years, the Software Engineering Laboratory (SEL) has been carrying out studies and experiments for the purpose of understanding, assessing, and improving software and software processes within a production software development environment at NASA/GSFC. The SEL comprises three major organizations: (1) NASA/GSFC, Flight Dynamics Division; (2) University of Maryland, Department of Computer Science; and (3) Computer Sciences Corporation, Flight Dynamics Technology Group. These organizations have jointly carried out several hundred software studies, producing hundreds of reports, papers, and documents, all of which describe some aspect of the software engineering technology that was analyzed in the flight dynamics environment at NASA. The studies range from small, controlled experiments (such as analyzing the effectiveness of code reading versus that of functional testing) to large, multiple project studies (such as assessing the impacts of Ada on a production environment). The organization's driving goal is to improve the software process continually, so that sustained improvement may be observed in the resulting products. This paper discusses the SEL as a functioning example of an operational software experience factory and summarizes the characteristics of and major lessons learned from 15 years of SEL operations.

The State of Software for Evolutionary Biology

PubMed Central

Darriba, Diego; Flouri, Tomáš; Stamatakis, Alexandros

2018-01-01

Abstract With Next Generation Sequencing data being routinely used, evolutionary biology is transforming into a computational science. Thus, researchers have to rely on a growing number of increasingly complex software. All widely used core tools in the field have grown considerably, in terms of the number of features as well as lines of code and consequently, also with respect to software complexity. A topic that has received little attention is the software engineering quality of widely used core analysis tools. Software developers appear to rarely assess the quality of their code, and this can have potential negative consequences for end-users. To this end, we assessed the code quality of 16 highly cited and compute-intensive tools mainly written in C/C++ (e.g., MrBayes, MAFFT, SweepFinder, etc.) and JAVA (BEAST) from the broader area of evolutionary biology that are being routinely used in current data analysis pipelines. Because, the software engineering quality of the tools we analyzed is rather unsatisfying, we provide a list of best practices for improving the quality of existing tools and list techniques that can be deployed for developing reliable, high quality scientific software from scratch. Finally, we also discuss journal as well as science policy and, more importantly, funding issues that need to be addressed for improving software engineering quality as well as ensuring support for developing new and maintaining existing software. Our intention is to raise the awareness of the community regarding software engineering quality issues and to emphasize the substantial lack of funding for scientific software development. PMID:29385525

Artificial intelligence approaches to software engineering

NASA Technical Reports Server (NTRS)

Johannes, James D.; Macdonald, James R.

1988-01-01

Artificial intelligence approaches to software engineering are examined. The software development life cycle is a sequence of not so well-defined phases. Improved techniques for developing systems have been formulated over the past 15 years, but pressure continues to attempt to reduce current costs. Software development technology seems to be standing still. The primary objective of the knowledge-based approach to software development presented in this paper is to avoid problem areas that lead to schedule slippages, cost overruns, or software products that fall short of their desired goals. Identifying and resolving software problems early, often in the phase in which they first occur, has been shown to contribute significantly to reducing risks in software development. Software development is not a mechanical process but a basic human activity. It requires clear thinking, work, and rework to be successful. The artificial intelligence approaches to software engineering presented support the software development life cycle through the use of software development techniques and methodologies in terms of changing current practices and methods. These should be replaced by better techniques that that improve the process of of software development and the quality of the resulting products. The software development process can be structured into well-defined steps, of which the interfaces are standardized, supported and checked by automated procedures that provide error detection, production of the documentation and ultimately support the actual design of complex programs.

Software architecture and engineering for patient records: current and future.

PubMed

Weng, Chunhua; Levine, Betty A; Mun, Seong K

2009-05-01

During the "The National Forum on the Future of the Defense Health Information System," a track focusing on "Systems Architecture and Software Engineering" included eight presenters. These presenters identified three key areas of interest in this field, which include the need for open enterprise architecture and a federated database design, net centrality based on service-oriented architecture, and the need for focus on software usability and reusability. The eight panelists provided recommendations related to the suitability of service-oriented architecture and the enabling technologies of grid computing and Web 2.0 for building health services research centers and federated data warehouses to facilitate large-scale collaborative health care and research. Finally, they discussed the need to leverage industry best practices for software engineering to facilitate rapid software development, testing, and deployment.

Advances in knowledge-based software engineering

NASA Technical Reports Server (NTRS)

Truszkowski, Walt

1991-01-01

The underlying hypothesis of this work is that a rigorous and comprehensive software reuse methodology can bring about a more effective and efficient utilization of constrained resources in the development of large-scale software systems by both government and industry. It is also believed that correct use of this type of software engineering methodology can significantly contribute to the higher levels of reliability that will be required of future operational systems. An overview and discussion of current research in the development and application of two systems that support a rigorous reuse paradigm are presented: the Knowledge-Based Software Engineering Environment (KBSEE) and the Knowledge Acquisition fo the Preservation of Tradeoffs and Underlying Rationales (KAPTUR) systems. Emphasis is on a presentation of operational scenarios which highlight the major functional capabilities of the two systems.

Engineering Documentation and Data Control

NASA Technical Reports Server (NTRS)

Matteson, Michael J.; Bramley, Craig; Ciaruffoli, Veronica

2001-01-01

Mississippi Space Services (MSS) the facility services contractor for NASA's John C. Stennis Space Center (SSC), is utilizing technology to improve engineering documentation and data control. Two identified improvement areas, labor intensive documentation research and outdated drafting standards, were targeted as top priority. MSS selected AutoManager(R) WorkFlow from Cyco software to manage engineering documentation. The software is currently installed on over 150 desctops. The outdated SSC drafting standard was written for pre-CADD drafting methods, in other words, board drafting. Implementation of COTS software solutions to manage engineering documentation and update the drafting standard resulted in significant increases in productivity by reducing the time spent searching for documents.

The Application of V&V within Reuse-Based Software Engineering

NASA Technical Reports Server (NTRS)

Addy, Edward

1996-01-01

Verification and Validation (V&V) is performed during application development for many systems, especially safety-critical and mission-critical systems. The V&V process is intended to discover errors as early as possible during the development process. Early discovery is important in order to minimize the cost and other impacts of correcting these errors. In reuse-based software engineering, decisions on the requirements, design and even implementation of domain assets can can be made prior to beginning development of a specific 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.

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

Kirby, M.J.; Kramer, S.R.; Pittard, G.T.

Jason Consultants International, Inc., under the sponsorship of the Gas Research Institute (GRI), has developed guidelines, procedures and software, which are described in this paper, for the installation of polyethylene gas pipe using guided horizontal drilling. Jason was aided in this development by two key subcontractors; Maurer Engineering who wrote the software and NICOR Technologies who reviewed the software and guidelines from a utility perspective. This program resulted in the development of commerically viable software for utilities, contractors, engineering firms, and others involved with the installation of pipes using guided horizontal drilling. The software is an interactive design tool thatmore » allows the user to enter ground elevation data, alignment information and pipe data. The software aides the engineer in designing a drill path and provides plan and profile views along with tabular data for pipe depth and surface profile. Finally, the software calculates installation loads and pipe stresses, compares these values against pipe manufacturer`s recommendations, and provides this information graphically and in tabular form. 5 refs., 18 figs., 2 tabs.« less

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.

75 FR 7342 - Airworthiness Directives; SICLI Halon 1211 Portable Fire Extinguishers as Installed on Various...

Federal Register 2010, 2011, 2012, 2013, 2014

2010-02-19

... INFORMATION CONTACT: For transport airplanes: Dan Rodina, Aerospace Engineer, International Branch, ANM-116...) 227-2125; fax (425) 227-1149. For small airplanes: Leslie B. Taylor, Aerospace Engineer, Standards... concern. The results of the ongoing investigation have now established that LyonTech Engineering Ltd, a UK...

SIApopr: a computational method to simulate evolutionary branching trees for analysis of tumor clonal evolution.

PubMed

McDonald, Thomas O; Michor, Franziska

2017-07-15

SIApopr (Simulating Infinite-Allele populations) is an R package to simulate time-homogeneous and inhomogeneous stochastic branching processes under a very flexible set of assumptions using the speed of C ++. The software simulates clonal evolution with the emergence of driver and passenger mutations under the infinite-allele assumption. The software is an application of the Gillespie Stochastic Simulation Algorithm expanded to a large number of cell types and scenarios, with the intention of allowing users to easily modify existing models or create their own. SIApopr is available as an R library on Github ( https://github.com/olliemcdonald/siapopr ). Supplementary data are available at Bioinformatics online. michor@jimmy.harvard.edu. © The Author (2017). Published by Oxford University Press. All rights reserved. For Permissions, please email: journals.permissions@oup.com

The School Advanced Ventilation Engineering Software (SAVES)

EPA Pesticide Factsheets

The School Advanced Ventilation Engineering Software (SAVES) package is a tool to help school designers assess the potential financial payback and indoor humidity control benefits of Energy Recovery Ventilation (ERV) systems for school applications.

The MDE Diploma: First International Postgraduate Specialization in Model-Driven Engineering

ERIC Educational Resources Information Center

Cabot, Jordi; Tisi, Massimo

2011-01-01

Model-Driven Engineering (MDE) is changing the way we build, operate, and maintain our software-intensive systems. Several projects using MDE practices are reporting significant improvements in quality and performance but, to be able to handle these projects, software engineers need a set of technical and interpersonal skills that are currently…

The Effects of Computer-Aided Design Software on Engineering Students' Spatial Visualisation Skills

ERIC Educational Resources Information Center

Kösa, Temel; Karakus, Fatih

2018-01-01

The purpose of this study was to determine the influence of computer-aided design (CAD) software-based instruction on the spatial visualisation skills of freshman engineering students in a computer-aided engineering drawing course. A quasi-experimental design was applied, using the Purdue Spatial Visualization Test-Visualization of Rotations…

Characterizing Employers' Expectations of the Communication Abilities of New Engineering Graduates

ERIC Educational Resources Information Center

Ruff, Susan; Carter, Michael

2015-01-01

To better understand the gap between recent graduates' communication abilities and employers' expectations, the authors surveyed software engineering professionals. They asked which of 67 communication abilities are unimportant for software engineers, which ones are learned on the job, which ones recent graduates are expected to have but lack, and…

Reuseable Objects Software Environment (ROSE): Introduction to Air Force Software Reuse Workshop

NASA Technical Reports Server (NTRS)

Cottrell, William L.

1994-01-01

The Reusable Objects Software Environment (ROSE) is a common, consistent, consolidated implementation of software functionality using modern object oriented software engineering including designed-in reuse and adaptable requirements. ROSE is designed to minimize abstraction and reduce complexity. A planning model for the reverse engineering of selected objects through object oriented analysis is depicted. Dynamic and functional modeling are used to develop a system design, the object design, the language, and a database management system. The return on investment for a ROSE pilot program and timelines are charted.

Process Based on SysML for New Launchers System and Software Developments

NASA Astrophysics Data System (ADS)

Hiron, Emmanuel; Miramont, Philippe

2010-08-01

The purpose of this paper is to present the Astrium-ST engineering process based on SysML. This process is currently set-up in the frame of common CNES /Astrium-ST R&T studies related to the Ariane 5 electrical system and flight software modelling. The tool used to set up this process is Rhapsody release 7.3 from IBM-Software firm [1]. This process focuses on the system engineering phase dedicated to Software with the objective to generate both System documents (sequential system design and flight control) and Software specifications.

Software Engineering Laboratory (SEL) Data Base Maintenance System (DBAM) user's guide and system description

NASA Technical Reports Server (NTRS)

Lo, P. S.; Card, D.

1983-01-01

The Software Engineering Laboratory (SEL) Data Base Maintenance System (DBAM) is explained. The various software facilities of the SEL, DBAM operating procedures, and DBAM system information are described. The relationships among DBAM components (baseline diagrams), component descriptions, overlay descriptions, indirect command file listings, file definitions, and sample data collection forms are provided.

A Middleware Platform for Providing Mobile and Embedded Computing Instruction to Software Engineering Students

ERIC Educational Resources Information Center

Mattmann, C. A.; Medvidovic, N.; Malek, S.; Edwards, G.; Banerjee, S.

2012-01-01

As embedded software systems have grown in number, complexity, and importance in the modern world, a corresponding need to teach computer science students how to effectively engineer such systems has arisen. Embedded software systems, such as those that control cell phones, aircraft, and medical equipment, are subject to requirements and…

Building 5 Manufacturing Branch. Explore@NASAGoddard celebrates

NASA Image and Video Library

2015-09-26

Building 5 Manufacturing Branch. Explore@NASAGoddard celebrates the 25th anniversary of the launch of the Hubble Space Telescope. All areas of Goddard’s research – Earth science, heliophysics, planetary science, astrophysics, and engineering and technology – will be presented, as each discipline plays a critical part in NASA's ongoing journey to reach new heights.

Giving More Realistic Definitions of Trigonometric Ratios

ERIC Educational Resources Information Center

Bhattacharjee, Pramode Ranjan

2012-01-01

Trigonometry is a well known branch of Mathematics. The study of trigonometry is of great importance in surveying, astronomy, navigation, engineering, and in different branches of science. This paper reports on the discovery of flaws in the traditional definitions of trigonometric ratios of an angle, which (in most cases) make use of the most…

Towards engineered branch placement: Unreal™ match between vapour-liquid-solid glancing angle deposition nanowire growth and simulation

NASA Astrophysics Data System (ADS)

Taschuk, M. T.; Tucker, R. T.; LaForge, J. M.; Beaudry, A. L.; Kupsta, M. R.; Brett, M. J.

2013-12-01

The vapour-liquid-solid glancing angle deposition (VLS-GLAD) process is capable of producing complex nanotree structures with control over azimuthal branch orientation and height. We have developed a thin film growth simulation including ballistic deposition, simplified surface diffusion, and droplet-mediated cubic crystal growth for the VLS-GLAD process using the UnrealTM Development Kit. The use of a commercial game engine has provided an interactive environment while allowing a custom physics implementation. Our simulation's output is verified against experimental data, including a volumetric film reconstruction produced using focused ion beam and scanning-electron microscopy (SEM), crystallographic texture, and morphological characteristics such as branch orientation. We achieve excellent morphological and texture agreement with experimental data, as well as qualitative agreement with SEM imagery. The simplified physics in our model reproduces the experimental films, indicating that the dominant role flux geometry plays in the VLS-GLAD competitive growth process responsible for azimuthally oriented branches and biaxial crystal texture evolution. The simulation's successful reproduction of experimental data indicates that it should have predictive power in designing novel VLS-GLAD structures.

Performance and driveline analyses of engine capacity in range extender engine hybrid vehicle

NASA Astrophysics Data System (ADS)

Praptijanto, Achmad; Santoso, Widodo Budi; Nur, Arifin; Wahono, Bambang; Putrasari, Yanuandri

2017-01-01

In this study, range extender engine designed should be able to meet the power needs of a power generator of hybrid electrical vehicle that has a minimum of 18 kW. Using this baseline model, the following range extenders will be compared between conventional SI piston engine (Baseline, BsL), engine capacity 1998 cm3, and efficiency-oriented SI piston with engine capacity 999 cm3 and 499 cm3 with 86 mm bore and stroke square gasoline engine in the performance, emission prediction of range extender engine, standard of charge by using engine and vehicle simulation software tools. In AVL Boost simulation software, range extender engine simulated from 1000 to 6000 rpm engine loads. The highest peak engine power brake reached up to 38 kW at 4500 rpm. On the other hand the highest torque achieved in 100 Nm at 3500 rpm. After that using AVL cruise simulation software, the model of range extended electric vehicle in series configuration with main components such as internal combustion engine, generator, electric motor, battery and the arthemis model rural road cycle was used to simulate the vehicle model. The simulation results show that engine with engine capacity 999 cm3 reported the economical performances of the engine and the emission and the control of engine cycle parameters.

75 FR 5925 - Proposed Flood Elevation Determinations

Federal Register 2010, 2011, 2012, 2013, 2014

2010-02-05

... comments, identified by Docket No. FEMA-B-1091, to Kevin C. Long, Acting Chief, Engineering Management..., Acting Chief, Engineering Management Branch, Mitigation Directorate, Federal Emergency Management Agency... federalism implications under Executive Order 13132. Executive Order 12988, Civil Justice Reform. This...

Automated Translation of Safety Critical Application Software Specifications into PLC Ladder Logic

NASA Technical Reports Server (NTRS)

Leucht, Kurt W.; Semmel, Glenn S.

2008-01-01

The numerous benefits of automatic application code generation are widely accepted within the software engineering community. A few of these benefits include raising the abstraction level of application programming, shorter product development time, lower maintenance costs, and increased code quality and consistency. Surprisingly, code generation concepts have not yet found wide acceptance and use in the field of programmable logic controller (PLC) software development. Software engineers at the NASA Kennedy Space Center (KSC) recognized the need for PLC code generation while developing their new ground checkout and launch processing system. They developed a process and a prototype software tool that automatically translates a high-level representation or specification of safety critical application software into ladder logic that executes on a PLC. This process and tool are expected to increase the reliability of the PLC code over that which is written manually, and may even lower life-cycle costs and shorten the development schedule of the new control system at KSC. This paper examines the problem domain and discusses the process and software tool that were prototyped by the KSC software engineers.