Security Requirements Management in Software Product Line Engineering

NASA Astrophysics Data System (ADS)

Mellado, Daniel; Fernández-Medina, Eduardo; Piattini, Mario

Security requirements engineering is both a central task and a critical success factor in product line development due to the complexity and extensive nature of product lines. However, most of the current product line practices in requirements engineering do not adequately address security requirements engineering. Therefore, in this chapter we will propose a security requirements engineering process (SREPPLine) driven by security standards and based on a security requirements decision model along with a security variability model to manage the variability of the artefacts related to security requirements. The aim of this approach is to deal with security requirements from the early stages of the product line development in a systematic way, in order to facilitate conformance with the most relevant security standards with regard to the management of security requirements, such as ISO/IEC 27001 and ISO/IEC 15408.

Molecular modeling of lipase binding to a substrate-water interface.

PubMed

Gruber, Christian C; Pleiss, Jürgen

2012-01-01

Interactions of lipases with hydrophobic substrate-water interfaces are of great interest to design improved lipase variants and engineer reaction conditions. This chapter describes the necessary steps to carry out molecular dynamics simulations of Candida antarctica lipase B at tributyrin-water interface using the GROMACS simulation software. Special attention is drawn to the preparation of the protein and the substrate-water interface and to the analysis of the obtained trajectory.

Modification Site Localization in Peptides.

PubMed

Chalkley, Robert J

2016-01-01

There are a large number of search engines designed to take mass spectrometry fragmentation spectra and match them to peptides from proteins in a database. These peptides could be unmodified, but they could also bear modifications that were added biologically or during sample preparation. As a measure of reliability for the peptide identification, software normally calculates how likely a given quality of match could have been achieved at random, most commonly through the use of target-decoy database searching (Elias and Gygi, Nat Methods 4(3): 207-214, 2007). Matching the correct peptide but with the wrong modification localization is not a random match, so results with this error will normally still be assessed as reliable identifications by the search engine. Hence, an extra step is required to determine site localization reliability, and the software approaches to measure this are the subject of this part of the chapter.

Multi-Agent Software Design and Engineering for Human Centered Collaborative Autonomous Space Systems: NASA Intelligent Systems

NASA Technical Reports Server (NTRS)

Bradshaw, Jeffrey M.

2005-01-01

Detailed results of this three-year project are available in 37 publications, including 7 book chapters, 3 journal articles, and 27 refereed conference proceedings. In addition, various aspects of the project were the subject of 31 invited presentations and 6 tutorials at international conferences and workshops. Good descriptions of prior and ongoing work on foundational technologies in Brahms, KAoS, NOMADS, and the PSA project can be found in numerous publications not listed here.

Analytical Design of Evolvable Software for High-Assurance Computing

DTIC Science & Technology

2001-02-14

Mathematical expression for the Total Sum of Squares which measures the variability that results when all values are treated as a combined sample coming from...primarily interested in background on software design and high-assurance computing, research in software architecture generation or evaluation...respectively. Those readers solely interested in the validation of a software design approach should at the minimum read Chapter 6 followed by Chapter

Multidisciplinary Design Optimization for Aeropropulsion Engines and Solid Modeling/Animation via the Integrated Forced Methods

NASA Technical Reports Server (NTRS)

2004-01-01

The grant closure report is organized in the following four chapters: Chapter describes the two research areas Design optimization and Solid mechanics. Ten journal publications are listed in the second chapter. Five highlights is the subject matter of chapter three. CHAPTER 1. The Design Optimization Test Bed CometBoards. CHAPTER 2. Solid Mechanics: Integrated Force Method of Analysis. CHAPTER 3. Five Highlights: Neural Network and Regression Methods Demonstrated in the Design Optimization of a Subsonic Aircraft. Neural Network and Regression Soft Model Extended for PX-300 Aircraft Engine. Engine with Regression and Neural Network Approximators Designed. Cascade Optimization Strategy with Neural network and Regression Approximations Demonstrated on a Preliminary Aircraft Engine Design. Neural Network and Regression Approximations Used in Aircraft Design.

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2010 CFR

2010-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2014 CFR

2014-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2013 CFR

2013-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2011 CFR

2011-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

46 CFR 107.231 - Inspection for certification.

Code of Federal Regulations, 2012 CFR

2012-10-01

... chapter, Electrical Engineering; 1 1 Requirements for industrial systems and components are in Subpart 111.94 of this chapter. (3) Subchapter F of this chapter, Marine Engineering; 2 2 Requirements for industrial systems and components are in Subpart 58.60 of this chapter. (4) Subchapter E of this chapter...

NASA/WVU Software Research Laboratory, 1995

NASA Technical Reports Server (NTRS)

Sabolish, George J.; Callahan, John R.

1995-01-01

In our second year, the NASA/WVU Software Research Lab has made significant strides toward analysis and solution of major software problems related to V&V activities. We have established working relationships with many ongoing efforts within NASA and continue to provide valuable input into policy and decision-making processes. Through our publications, technical reports, lecture series, newsletters, and resources on the World-Wide-Web, we provide information to many NASA and external parties daily. This report is a summary and overview of some of our activities for the past year. This report is divided into 6 chapters: Introduction, People, Support Activities, Process, Metrics, and Testing. The Introduction chapter (this chapter) gives an overview of our project beginnings and targets. The People chapter focuses on new people who have joined the Lab this year. The Support chapter briefly lists activities like our WWW pages, Technical Report Series, Technical Lecture Series, and Research Quarterly newsletter. Finally, the remaining four chapters discuss the major research areas that we have made significant progress towards producing meaningful task reports. These chapters can be regarded as portions of drafts of our task reports.

Quality Assurance in the Presence of Variability

NASA Astrophysics Data System (ADS)

Lauenroth, Kim; Metzger, Andreas; Pohl, Klaus

Software Product Line Engineering (SPLE) is a reuse-driven development paradigm that has been applied successfully in information system engineering and other domains. Quality assurance of the reusable artifacts of the product line (e.g. requirements, design, and code artifacts) is essential for successful product line engineering. As those artifacts are reused in several products, a defect in a reusable artifact can affect several products of the product line. A central challenge for quality assurance in product line engineering is how to consider product line variability. Since the reusable artifacts contain variability, quality assurance techniques from single-system engineering cannot directly be applied to those artifacts. Therefore, different strategies and techniques have been developed for quality assurance in the presence of variability. In this chapter, we describe those strategies and discuss in more detail one of those strategies, the so called comprehensive strategy. The comprehensive strategy aims at checking the quality of all possible products of the product line and thus offers the highest benefits, since it is able to uncover defects in all possible products of the product line. However, the central challenge for applying the comprehensive strategy is the complexity that results from the product line variability and the large number of potential products of a product line. In this chapter, we present one concrete technique that we have developed to implement the comprehensive strategy that addresses this challenge. The technique is based on model checking technology and allows for a comprehensive verification of domain artifacts against temporal logic properties.

Search Engine Liability for Copyright Infringement

NASA Astrophysics Data System (ADS)

Fitzgerald, B.; O'Brien, D.; Fitzgerald, A.

The chapter provides a broad overview to the topic of search engine liability for copyright infringement. In doing so, the chapter examines some of the key copyright law principles and their application to search engines. The chapter also provides a discussion of some of the most important cases to be decided within the courts of the United States, Australia, China and Europe regarding the liability of search engines for copyright infringement. Finally, the chapter will conclude with some thoughts for reform, including how copyright law can be amended in order to accommodate and realise the great informative power which search engines have to offer society.

Intellectual Property, Digital Technology and the Developing World

NASA Astrophysics Data System (ADS)

Pupillo, Lorenzo Maria

This chapter provides an overview of how the converging ICTs are challenging the traditional off-line copyright doctrine and suggests how developing countries should approach issues such as copyright in the digital world, software (Protection, Open Source, Reverse Engineering), and data base protection. The balance of the chapter is organized into three sections. After the introduction, the second section explains how digital technology is dramatically changing the entertainment industry, what are the major challenges to the industry, and what are the approaches that the economic literature suggest to face the structural changes that the digital revolution is bringing forward. Starting from the assumption that IPRs frameworks need to be customized to the countries’ development needs, the third section makes recommendations on how developing countries should use copyright to support access to information and to creative industries.

Opportunities in Civil Engineering. [VGM Career Horizons Series].

ERIC Educational Resources Information Center

Hagerty, D. Joseph; Heer, John E., Jr.

This book presents information on career opportunities in civil engineering. Chapter 1 focuses on the scope of civil engineering, discussing: role of scientist, engineer, and technologists; engineering and engineering technology; civil engineer's role and obligations; and other information. Chapter 2 considers such aspects of the education for…

Tandem Mass Spectrum Sequencing: An Alternative to Database Search Engines in Shotgun Proteomics.

PubMed

Muth, Thilo; Rapp, Erdmann; Berven, Frode S; Barsnes, Harald; Vaudel, Marc

2016-01-01

Protein identification via database searches has become the gold standard in mass spectrometry based shotgun proteomics. However, as the quality of tandem mass spectra improves, direct mass spectrum sequencing gains interest as a database-independent alternative. In this chapter, the general principle of this so-called de novo sequencing is introduced along with pitfalls and challenges of the technique. The main tools available are presented with a focus on user friendly open source software which can be directly applied in everyday proteomic workflows.

Cloud Security: Issues and Research Directions

DTIC Science & Technology

2014-11-18

4. Cloud Computing Security: What Changes with Software - Defined Networking ? Maur´ıcio Tsugawa, Andr´ea Matsunaga, and Jos´e A. B. Fortes 5...machine’s memory from an untrusted or malicious hypervisor. In Chapter 4, Tsugawa et al. discuss the security issues introduced when Software - Defined ... Networking ( SDN ) is deployed within and across clouds. Chapters 5-9 are focused on the protection of data stored in the cloud. In Chapter 5, Wang et

Scrum and Global Delivery: Pitfalls and Lessons Learned

NASA Astrophysics Data System (ADS)

Sadun, Cristiano

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

Spec UV-Vis: An Ultraviolet-Visible Spectrophotometer Simulation

NASA Astrophysics Data System (ADS)

Papadopoulos, N.; Limniou, Maria; Koklamanis, Giannis; Tsarouxas, Apostolos; Roilidis, Mpampis; Bigger, Stephen W.

2001-11-01

The software and its accompanying manual can be used to illustrate the recording of an absorption spectrum and the Beer-Lambert law (5-7) as well as various aspects of acid-base indicators such as the spectrophotometric determination of pKa (8), the isosbestic point (6, 9), and distribution diagrams (10, 11).

Literature Cited

1. Shiowatana, J. J. Chem. Educ. 1997, 74, 730.
2. Altemose, I. R. J. Chem. Educ. 1986, 63, A216, A262.
3. Piepmeier, E. H. J. Chem. Educ. 1973, 50, 640.
4. Lott, P. F. J. Chem. Educ. 1968, 45, A89, A169, A182, A273.
5. Skoog, D. A.; West, D. M.; Holler, F. J. Fundamentals of Analytical Chemistry, 7th ed.; Saunders College Publishing: Fort Worth, TX, 1996, Chapters 22-24.
6. Christian, G. D. Analytical Chemistry, 5th ed.; Wiley: New York, 1994; Chapter 14.
7. Kennedy, J. H. Analytical Chemistry--Principles, 2nd ed.; Saunders College Publishing: New York, 1990; Chapters 11,12.
8. Patterson, G. S. J. Chem. Educ. 1999, 76, 395.
9. Harris, D. C. Quantitative Chemical Analysis, 5th ed.; Freeman: New York, 1997; Chapters 19, 20.
10. Butler, J. N. Ionic Equilibrium--A Mathematical Approach; Addison-Wesley: Reading, MA, 1964; Chapter 5.
11. Sawyer, C. A.; McCarty, P. L.; Parkin, G. F. Chemistry for Environmental Engineering, 4th ed.; McGraw-Hill: Singapore, 1994; Chapter 4.

BioBrick assembly standards and techniques and associated software tools.

PubMed

Røkke, Gunvor; Korvald, Eirin; Pahr, Jarle; Oyås, Ove; Lale, Rahmi

2014-01-01

The BioBrick idea was developed to introduce the engineering principles of abstraction and standardization into synthetic biology. BioBricks are DNA sequences that serve a defined biological function and can be readily assembled with any other BioBrick parts to create new BioBricks with novel properties. In order to achieve this, several assembly standards can be used. Which assembly standards a BioBrick is compatible with, depends on the prefix and suffix sequences surrounding the part. In this chapter, five of the most common assembly standards will be described, as well as some of the most used assembly techniques, cloning procedures, and a presentation of the available software tools that can be used for deciding on the best method for assembling of different BioBricks, and searching for BioBrick parts in the Registry of Standard Biological Parts database.

Measurement and Instrumentation

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

Kirkham, Harold

This is a chapter for a book called the Standard Handbook for Electrical Engineering. Though it is not obvious from the title, the book deals mainly with power engineering. The first chapter (not mine) is about the fundamental quantities used in measurement. This chapter is about the process and the instrumentation.

46 CFR 167.25-1 - Boilers, pressure vessels, piping and appurtenances.

Code of Federal Regulations, 2014 CFR

2014-10-01

... SCHOOLS PUBLIC NAUTICAL SCHOOL SHIPS Marine Engineering § 167.25-1 Boilers, pressure vessels, piping and... engineering regulations in parts 50 to 63, inclusive, of Subchapter F (Marine Engineering) of this chapter. (2... part 52 of Subchapter F (Marine Engineering) of this chapter. All alterations, replacements or repairs...

46 CFR 167.25-1 - Boilers, pressure vessels, piping and appurtenances.

Code of Federal Regulations, 2010 CFR

2010-10-01

... SCHOOLS PUBLIC NAUTICAL SCHOOL SHIPS Marine Engineering § 167.25-1 Boilers, pressure vessels, piping and... engineering regulations in parts 50 to 63, inclusive, of Subchapter F (Marine Engineering) of this chapter. (2... part 52 of Subchapter F (Marine Engineering) of this chapter. All alterations, replacements or repairs...

Chapter 24: Programmatic Interfaces - IDL VOlib

NASA Astrophysics Data System (ADS)

Miller, C. J.

In this chapter, we describe a library for working with the VO using IDL (the Interactive Data Language). IDL is a software environment for data analysis, visualization, and cross-platform application development. It has wide-usage in astronomy, including NASA (e.g. http://seadas.gsfc.nasa.gov/), the Sloan Digital Sky Survey (http://www.sdss.org), and the Spitzer Infrared Spectrograph Instrument (http://ssc.spitzer.caltech.edu/archanaly/contributed/smart/). David Stern, the founder of Research Systems, Inc. (RSI), began the development of IDL while working with NASA's Mars Mariner 7 and 9 data at the Laboratory for Atmospheric and Space Physics at the University of Colorado. In 1981, IDL was rewritten in assembly language and FORTRAN for VAX/VMS. IDL's usage has expanded over the last decade into the fields of medical imaging and engineering, among many others. IDL's programming style carries over much of this FORTRAN-legacy, and has a familiar feel to many astronomers who learned their trade using FORTRAN. The spread of IDL-usage amongst astronomers can in part be attributed to the wealth of publicly astronomical libraries. The Goddard Space Flight Center (GSFC) maintains a list of astronomy-related IDL libraries, including the well known Astronomy User's Library (hereafter ASTROLIB2). We will use some of these GSFC IDL libraries. We note that while IDL is a licensed-software product, the source code of user-written procedures are typically freely available to the community. To make the most out of this section as a reader, it is important that many of the data discovery, access, and analysis protocols are understood before reading this chapter. In the next section, we provide an overview of some of the NVO terminology with which the reader should be familiar. The IDL library discussed here is specifically for use with the Virtual Observatory and is named VOlib. IDL's VOlib is available at http://nvo.noao.edu and is included with the software distrubution for this book.

Science and Engineering Education: Data and Information.

ERIC Educational Resources Information Center

Buccino, Alphonse; And Others

Science and Engineering Education data and information are presented in six chapters, each chapter containing detailed statistical charts and tables. Resources data contained in chapter 1 are grouped into four categories: K-12, higher education, funding, and informal education. Resources may take the form of capital, personnel, and teaching…

Hydraulic modeling development and application in water resources engineering

USGS Publications Warehouse

Simoes, Francisco J.; Yang, Chih Ted; Wang, Lawrence K.

2015-01-01

The use of modeling has become widespread in water resources engineering and science to study rivers, lakes, estuaries, and coastal regions. For example, computer models are commonly used to forecast anthropogenic effects on the environment, and to help provide advanced mitigation measures against catastrophic events such as natural and dam-break floods. Linking hydraulic models to vegetation and habitat models has expanded their use in multidisciplinary applications to the riparian corridor. Implementation of these models in software packages on personal desktop computers has made them accessible to the general engineering community, and their use has been popularized by the need of minimal training due to intuitive graphical user interface front ends. Models are, however, complex and nontrivial, to the extent that even common terminology is sometimes ambiguous and often applied incorrectly. In fact, many efforts are currently under way in order to standardize terminology and offer guidelines for good practice, but none has yet reached unanimous acceptance. This chapter provides a view of the elements involved in modeling surface flows for the application in environmental water resources engineering. It presents the concepts and steps necessary for rational model development and use by starting with the exploration of the ideas involved in defining a model. Tangible form of those ideas is provided by the development of a mathematical and corresponding numerical hydraulic model, which is given with a substantial amount of detail. The issues of model deployment in a practical and productive work environment are also addressed. The chapter ends by presenting a few model applications highlighting the need for good quality control in model validation.

UltraNet Target Parameters. Chapter 1

NASA Technical Reports Server (NTRS)

Kislitzin, Katherine T.; Blaylock, Bruce T. (Technical Monitor)

1992-01-01

The UltraNet is a high speed network capable of rates up to one gigabit per second. It is a hub based network with four optical fiber links connecting each hub. Each link can carry up to 256 megabits of data, and the hub backplane is capable of one gigabit aggregate throughput. Host connections to the hub may be fiber, coax, or channel based. Bus based machines have adapter boards that connect to transceivers in the hub, while channel based machines use a personality module in the hub. One way that the UltraNet achieves its high transfer rates is by off-loading the protocol processing from the hosts to special purpose protocol engines in the UltraNet hubs. In addition, every hub has a PC connected to it by StarLAN for network management purposes. Although there is hub resident and PC resident UltraNet software, this document treats only the host resident UltraNet software.

Applying Use Cases to Describe the Role of Standards in e-Health Information Systems

NASA Astrophysics Data System (ADS)

Chávez, Emma; Finnie, Gavin; Krishnan, Padmanabhan

Individual health records (IHRs) contain a person's lifetime records of their key health history and care within a health system (National E-Health Transition Authority, Retrieved Jan 12, 2009 from http://www.nehta.gov.au/coordinated-care/whats-in-iehr, 2004). This information can be processed and stored in different ways. The record should be available electronically to authorized health care providers and the individual anywhere, anytime, to support high-quality care. Many organizations provide a diversity of solutions for e-health and its services. Standards play an important role to enable these organizations to support information interchange and improve efficiency of health care delivery. However, there are numerous standards to choose from and not all of them are accessible to the software developer. This chapter proposes a framework to describe the e-health standards that can be used by software engineers to implement e-health information systems.

The Western Aeronautical Test Range. Chapter 10 Tools

NASA Technical Reports Server (NTRS)

Knudtson, Kevin; Park, Alice; Downing, Robert; Sheldon, Jack; Harvey, Robert; Norcross, April

2011-01-01

The Western Aeronautical Test Range (WATR) staff at the NASA Dryden Flight Research Center is developing a translation software called Chapter 10 Tools in response to challenges posed by post-flight processing data files originating from various on-board digital recorders that follow the Range Commanders Council Inter-Range Instrumentation Group (IRIG) 106 Chapter 10 Digital Recording Standard but use differing interpretations of the Standard. The software will read the date files regardless of the vendor implementation of the source recorder, displaying data, identifying and correcting errors, and producing a data file that can be successfully processed post-flight

Final Technical Report on Quantifying Dependability Attributes of Software Based Safety Critical Instrumentation and Control Systems in Nuclear Power Plants

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

Smidts, Carol; Huang, Funqun; Li, Boyuan

With the current transition from analog to digital instrumentation and control systems in nuclear power plants, the number and variety of software-based systems have significantly increased. The sophisticated nature and increasing complexity of software raises trust in these systems as a significant challenge. The trust placed in a software system is typically termed software dependability. Software dependability analysis faces uncommon challenges since software systems’ characteristics differ from those of hardware systems. The lack of systematic science-based methods for quantifying the dependability attributes in software-based instrumentation as well as control systems in safety critical applications has proved itself to be amore » significant inhibitor to the expanded use of modern digital technology in the nuclear industry. Dependability refers to the ability of a system to deliver a service that can be trusted. Dependability is commonly considered as a general concept that encompasses different attributes, e.g., reliability, safety, security, availability and maintainability. Dependability research has progressed significantly over the last few decades. For example, various assessment models and/or design approaches have been proposed for software reliability, software availability and software maintainability. Advances have also been made to integrate multiple dependability attributes, e.g., integrating security with other dependability attributes, measuring availability and maintainability, modeling reliability and availability, quantifying reliability and security, exploring the dependencies between security and safety and developing integrated analysis models. However, there is still a lack of understanding of the dependencies between various dependability attributes as a whole and of how such dependencies are formed. To address the need for quantification and give a more objective basis to the review process -- therefore reducing regulatory uncertainty -- measures and methods are needed to assess dependability attributes early on, as well as throughout the life-cycle process of software development. In this research, extensive expert opinion elicitation is used to identify the measures and methods for assessing software dependability. Semi-structured questionnaires were designed to elicit expert knowledge. A new notation system, Causal Mechanism Graphing, was developed to extract and represent such knowledge. The Causal Mechanism Graphs were merged, thus, obtaining the consensus knowledge shared by the domain experts. In this report, we focus on how software contributes to dependability. However, software dependability is not discussed separately from the context of systems or socio-technical systems. Specifically, this report focuses on software dependability, reliability, safety, security, availability, and maintainability. Our research was conducted in the sequence of stages found below. Each stage is further examined in its corresponding chapter. Stage 1 (Chapter 2): Elicitation of causal maps describing the dependencies between dependability attributes. These causal maps were constructed using expert opinion elicitation. This chapter describes the expert opinion elicitation process, the questionnaire design, the causal map construction method and the causal maps obtained. Stage 2 (Chapter 3): Elicitation of the causal map describing the occurrence of the event of interest for each dependability attribute. The causal mechanisms for the “event of interest” were extracted for each of the software dependability attributes. The “event of interest” for a dependability attribute is generally considered to be the “attribute failure”, e.g. security failure. The extraction was based on the analysis of expert elicitation results obtained in Stage 1. Stage 3 (Chapter 4): Identification of relevant measurements. Measures for the “events of interest” and their causal mechanisms were obtained from expert opinion elicitation for each of the software dependability attributes. The measures extracted are presented in this chapter. Stage 4 (Chapter 5): Assessment of the coverage of the causal maps via measures. Coverage was assessed to determine whether the measures obtained were sufficient to quantify software dependability, and what measures are further required. Stage 5 (Chapter 6): Identification of “missing” measures and measurement approaches for concepts not covered. New measures, for concepts that had not been covered sufficiently as determined in Stage 4, were identified using supplementary expert opinion elicitation as well as literature reviews. Stage 6 (Chapter 7): Building of a detailed quantification model based on the causal maps and measurements obtained. Ability to derive such a quantification model shows that the causal models and measurements derived from the previous stages (Stage 1 to Stage 5) can form the technical basis for developing dependability quantification models. Scope restrictions have led us to prioritize this demonstration effort. The demonstration was focused on a critical system, i.e. the reactor protection system. For this system, a ranking of the software dependability attributes by nuclear stakeholders was developed. As expected for this application, the stakeholder ranking identified safety as the most critical attribute to be quantified. A safety quantification model limited to the requirements phase of development was built. Two case studies were conducted for verification. A preliminary control gate for software safety for the requirements stage was proposed and applied to the first case study. The control gate allows a cost effective selection of the duration of the requirements phase.« less

Engineering Aid 1 & C. Rate Training Manual.

ERIC Educational Resources Information Center

Naval Education and Training Command, Pensacola, FL.

The manual is written primarily to aid in the training of personnel to meet the professional qualifications of the engineering aid, first class and chief. In chapter one, the trainee becomes familiar with the rewards and responsibilities of an engineering aid. Chapter two deals with principles of SEABEE administration, the organization and…

Science & Engineering Indicators 2016. National Science Board

ERIC Educational Resources Information Center

National Science Foundation, 2016

2016-01-01

"Science and Engineering Indicators" (SEI) is first and foremost a volume of record comprising high-quality quantitative data on the U.S. and international science and engineering enterprise. SEI includes an overview and seven chapters that follow a generally consistent pattern. The chapter titles are as follows: (1) Elementary and…

Core Ideas of Engineering and Technology

ERIC Educational Resources Information Center

Sneider, Cary

2012-01-01

Last month, Rodger Bybee's article, "Scientific and Engineering Practices in K-12 Classrooms," provided an overview of Chapter 3 in "A Framework for K-12 Science Education: Practices, Crosscutting Concepts, and Core Ideas" (NRC 2011). Chapter 3 describes the practices of science and engineering that students are expected to develop during 13 years…

High/Scope Buyer's Guide to Children's Software. 11th Edition.

ERIC Educational Resources Information Center

Hohmann, Charles; And Others

This 11th edition of the High/Scope Buyer's Guide to Children's Software was designed to help teachers, caregivers, and parents make good choices when purchasing software to enhance children's learning. The book consists of an introduction, a chapter on finding the best software, software reviews for 48 different software products. The…

NASA Systems Engineering Handbook

NASA Technical Reports Server (NTRS)

Hirshorn, Steven R.; Voss, Linda D.; Bromley, Linda K.

2017-01-01

The update of this handbook continues the methodology of the previous revision: a top-down compatibility with higher level Agency policy and a bottom-up infusion of guidance from the NASA practitioners in the field. This approach provides the opportunity to obtain best practices from across NASA and bridge the information to the established NASA systems engineering processes and to communicate principles of good practice as well as alternative approaches rather than specify a particular way to accomplish a task. The result embodied in this handbook is a top-level implementation approach on the practice of systems engineering unique to NASA. Material used for updating this handbook has been drawn from many sources, including NPRs, Center systems engineering handbooks and processes, other Agency best practices, and external systems engineering textbooks and guides. This handbook consists of six chapters: (1) an introduction, (2) a systems engineering fundamentals discussion, (3) the NASA program project life cycles, (4) systems engineering processes to get from a concept to a design, (5) systems engineering processes to get from a design to a final product, and (6) crosscutting management processes in systems engineering. The chapters are supplemented by appendices that provide outlines, examples, and further information to illustrate topics in the chapters. The handbook makes extensive use of boxes and figures to define, refine, illustrate, and extend concepts in the chapters.

Multiobjective Decision Analysis With Engineering and Business Applications

NASA Astrophysics Data System (ADS)

Wood, Eric

The last 15 years have witnessed the development of a large number of multiobjective decision techniques. Applying these techniques to environmental, engineering, and business problems has become well accepted. Multiobjective Decision Analysis With Engineering and Business Applications attempts to cover the main multiobjective techniques both in their mathematical treatment and in their application to real-world problems.The book is divided into 12 chapters plus three appendices. The main portion of the book is represented by chapters 3-6, Where the various approaches are identified, classified, and reviewed. Chapter 3 covers methods for generating nondominated solutions; chapter 4, continuous methods with prior preference articulation; chapter 5, discrete methods with prior preference articulation; and chapter 6, methods of progressive articulation of preferences. In these four chapters, close to 20 techniques are discussed with over 20 illustrative examples. This is both a strength and a weakness; the breadth of techniques and examples provide comprehensive coverage, but it is in a style too mathematically compact for most readers. By my count, the presentation of the 20 techniques in chapters 3-6 covered 85 pages, an average of about 4.5 pages each; therefore, a sound basis in linear algebra and linear programing is required if the reader hopes to follow the material. Chapter 2, “Concepts in Multiobjective Analysis,” also assumes such a background.

Training Course in Geotechnical and Foundation Engineering. Geotechnical Earthquake Engineering: Reference Manual. Chapters 4, Ground Motion Characterization, and 8, Liquefaction and Seismic Settlement.

DOT National Transportation Integrated Search

1998-12-01

This manual was written to provide training on how to apply principles of geotechnical earthquake engineering to planning, design, and retrofit of highway facilities. Reproduced here are two chapters 4 and 8 in the settlement, respectively. These cha...

Automation of reverse engineering process in aircraft modeling and related optimization problems

NASA Technical Reports Server (NTRS)

Li, W.; Swetits, J.

1994-01-01

During the year of 1994, the engineering problems in aircraft modeling were studied. The initial concern was to obtain a surface model with desirable geometric characteristics. Much of the effort during the first half of the year was to find an efficient way of solving a computationally difficult optimization model. Since the smoothing technique in the proposal 'Surface Modeling and Optimization Studies of Aerodynamic Configurations' requires solutions of a sequence of large-scale quadratic programming problems, it is important to design algorithms that can solve each quadratic program in a few interactions. This research led to three papers by Dr. W. Li, which were submitted to SIAM Journal on Optimization and Mathematical Programming. Two of these papers have been accepted for publication. Even though significant progress has been made during this phase of research and computation times was reduced from 30 min. to 2 min. for a sample problem, it was not good enough for on-line processing of digitized data points. After discussion with Dr. Robert E. Smith Jr., it was decided not to enforce shape constraints in order in order to simplify the model. As a consequence, P. Dierckx's nonparametric spline fitting approach was adopted, where one has only one control parameter for the fitting process - the error tolerance. At the same time the surface modeling software developed by Imageware was tested. Research indicated a substantially improved fitting of digitalized data points can be achieved if a proper parameterization of the spline surface is chosen. A winning strategy is to incorporate Dierckx's surface fitting with a natural parameterization for aircraft parts. The report consists of 4 chapters. Chapter 1 provides an overview of reverse engineering related to aircraft modeling and some preliminary findings of the effort in the second half of the year. Chapters 2-4 are the research results by Dr. W. Li on penalty functions and conjugate gradient methods for quadratic programming problems.

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.

OMOGENIA: A Semantically Driven Collaborative Environment

NASA Astrophysics Data System (ADS)

Liapis, Aggelos

Ontology creation can be thought of as a social procedure. Indeed the concepts involved in general need to be elicited from communities of domain experts and end-users by teams of knowledge engineers. Many problems in ontology creation appear to resemble certain problems in software design, particularly with respect to the setup of collaborative systems. For instance, the resolution of conceptual conflicts between formalized ontologies is a major engineering problem as ontologies move into widespread use on the semantic web. Such conflict resolution often requires human collaboration and cannot be achieved by automated methods with the exception of simple cases. In this chapter we discuss research in the field of computer-supported cooperative work (CSCW) that focuses on classification and which throws light on ontology building. Furthermore, we present a semantically driven collaborative environment called OMOGENIA as a natural way to display and examine the structure of an evolving ontology in a collaborative setting.

Novel 3D Tissue Engineered Bone Model, Biomimetic Nanomaterials, and Cold Atmospheric Plasma Technique for Biomedical Applications

NASA Astrophysics Data System (ADS)

Wang, Mian

This thesis research is consist of four chapters, including biomimetic three-dimensional tissue engineered nanostructured bone model for breast cancer bone metastasis study (Chapter one), cold atmospheric plasma for selectively ablating metastatic breast cancer (Chapter two), design of biomimetic and bioactive cold plasma modified nanostructured scaffolds for enhanced osteogenic differentiation of bone marrow derived mesenchymal stem cells (Chapter three), and enhanced osteoblast and mesenchymal stem cell functions on titanium with hydrothermally treated nanocrystalline hydroxyapatite/magnetically treated carbon nanotubes for orthopedic applications (Chapter four). All the thesis research is focused on nanomaterials and the use of cold plasma technique for various biomedical applications.

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.

Using Scrum Practices in GSD Projects

NASA Astrophysics Data System (ADS)

Paasivaara, Maria; Lassenius, Casper

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

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.

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.

nu-TRLan User Guide Version 1.0: A High-Performance Software Package for Large-Scale Harmitian Eigenvalue Problems

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

Yamazaki, Ichitaro; Wu, Kesheng; Simon, Horst

2008-10-27

The original software package TRLan, [TRLan User Guide], page 24, implements the thick restart Lanczos method, [Wu and Simon 2001], page 24, for computing eigenvalues {lambda} and their corresponding eigenvectors v of a symmetric matrix A: Av = {lambda}v. Its effectiveness in computing the exterior eigenvalues of a large matrix has been demonstrated, [LBNL-42982], page 24. However, its performance strongly depends on the user-specified dimension of a projection subspace. If the dimension is too small, TRLan suffers from slow convergence. If it is too large, the computational and memory costs become expensive. Therefore, to balance the solution convergence and costs,more » users must select an appropriate subspace dimension for each eigenvalue problem at hand. To free users from this difficult task, nu-TRLan, [LNBL-1059E], page 23, adjusts the subspace dimension at every restart such that optimal performance in solving the eigenvalue problem is automatically obtained. This document provides a user guide to the nu-TRLan software package. The original TRLan software package was implemented in Fortran 90 to solve symmetric eigenvalue problems using static projection subspace dimensions. nu-TRLan was developed in C and extended to solve Hermitian eigenvalue problems. It can be invoked using either a static or an adaptive subspace dimension. In order to simplify its use for TRLan users, nu-TRLan has interfaces and features similar to those of TRLan: (1) Solver parameters are stored in a single data structure called trl-info, Chapter 4 [trl-info structure], page 7. (2) Most of the numerical computations are performed by BLAS, [BLAS], page 23, and LAPACK, [LAPACK], page 23, subroutines, which allow nu-TRLan to achieve optimized performance across a wide range of platforms. (3) To solve eigenvalue problems on distributed memory systems, the message passing interface (MPI), [MPI forum], page 23, is used. The rest of this document is organized as follows. In Chapter 2 [Installation], page 2, we provide an installation guide of the nu-TRLan software package. In Chapter 3 [Example], page 3, we present a simple nu-TRLan example program. In Chapter 4 [trl-info structure], page 7, and Chapter 5 [trlan subroutine], page 14, we describe the solver parameters and interfaces in detail. In Chapter 6 [Solver parameters], page 21, we discuss the selection of the user-specified parameters. In Chapter 7 [Contact information], page 22, we give the acknowledgements and contact information of the authors. In Chapter 8 [References], page 23, we list reference to related works.« less

Further Developments of BEM for Micro and Macromechanical Analyses of Composites: Boundary Element Software Technology-Composite User's Manual

NASA Technical Reports Server (NTRS)

Banerjee, P. K.; Henry, D. P.; Hopkins, D. A.; Goldberg, R. K.

1997-01-01

BEST-CMS (Boundary Element Solution Technology - Composite Modeling System) is an advanced engineering system for the micro-analysis of fiber composite structures. BEST-CMS is based upon the boundary element program BEST3D which was developed for NASA by Pratt and Whitney Aircraft and the State University of New York at Buffalo under contract NAS3-23697. BEST-CMS presently has the capabilities for elastostatic analysis, steady-state and transient heat transfer analysis, steady-state and transient concurrent thermoelastic analysis and elastoplastic and creep analysis. The fibers are assumed to be perfectly bonded to the composite matrix, or in the case of static or steady-state analysis, the fibers may be assumed to have spring connections, thermal resistance, and/or frictional sliding between the fibers and the composite matrix. The primary objective of this User's Manual is to provide an overview of all BEST-CMS capabilities, along with detailed descriptions of the input data requirements. A brief review of the theoretical background is presented for each analysis category. Then, Chapter 3 discusses the key aspects of the numerical implementation, while Chapter 4 provides a tutorial for the beginning BEST-CMS user. The heart of the manual, however, is in Chapter 5, where a complete description of all data input items is provided. Within this chapter, the individual entries are grouped on a functional basis for a more coherent presentation. Chapter 6 includes sample problems and should be of considerable assistance to the novice. Chapter 7 includes capsules of a number of fiber-composite analysis problems that have been solved using BEST-CMS. This chapter is primarily descriptive in nature and is intended merely to illustrate the level of analysis that is possible within the present BEST-CMS system. Chapter 8 contains a detailed description of the BEST-CMS Neutral File which is helpful in writing an interface between BEST- CMS and any graphic post-processor program. Finally, all pertinent references are listed in Chapter 9.

The Science Race: Training and Utilization of Scientists and Engineers, US and USSR.

ERIC Educational Resources Information Center

Ailes, Catherine P.; Rushing, Francis W.

This book represents a comparison of the systems of training and utilization of scientists/engineers in the United States and Soviet Union. Chapter 1 provides a general description of the economic structure and organization in which the training of scientists/engineers is conducted and in which such trained personnel are employed. In chapters 2-5,…

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.

Nonlinear Elasticity

NASA Astrophysics Data System (ADS)

Fu, Y. B.; Ogden, R. W.

2001-05-01

This collection of papers by leading researchers in the field of finite, nonlinear elasticity concerns itself with the behavior of objects that deform when external forces or temperature gradients are applied. This process is extremely important in many industrial settings, such as aerospace and rubber industries. This book covers the various aspects of the subject comprehensively with careful explanations of the basic theories and individual chapters each covering a different research direction. The authors discuss the use of symbolic manipulation software as well as computer algorithm issues. The emphasis is placed firmly on covering modern, recent developments, rather than the very theoretical approach often found. The book will be an excellent reference for both beginners and specialists in engineering, applied mathematics and physics.

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.

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.

KISS--a new approach to self-controlled e-learning of selected chapters in Medical Engineering and other fields at bachelor and master course level.

PubMed

Hutten, Helmut; Stiegmaier, Wolfgang; Rauchegger, Günter

2005-09-01

Modern life style requires new methods for individual lifelong learning, based on access at every time and from every place. This fundamental requirement is provided by the Internet. The Internet technology promises an increasing potential in the future for e-learning or tele-learning. Some special requirements are password-controlled access, applicability of most commercially available PCs and laptops equipped with standard software (Microsoft Internet Explorer 6.0), central evaluation of the students' performance, inclusion of an examination part, provision of a picture gallery and a comprehensive glossary accessible in the learning mode. The KISS-shell has been developed based on the Oracle 10g application server in combination with a relational data base (Oracle 8i) on the server side and a web browser based interface using JavaScript for user control of data input on the client side (Kontrolliertes Intelligentes Selbstgesteuertes Studium, KISS). The first tutorial application has been realized with a chapter about cardiac pacemakers. The weight of that chapter (or module) is about 2 ECTS (i.e. the equivalent of 30 working hours; European Credit Transfer System, ECTS). The internal structure of the chapter is organized in sequential mode. It consists of five main sections. Each of those five sections is subdivided into five subsections of comparable length. Progression from one subsection to the next is possible only after successfully passing through the respective examination. The whole learning programme with the pacemaker chapter has been evaluated by 10 students. The system will be presented together with first experiences including the evaluation results. Until now the program has not been used for training purposes.

Dependency visualization for complex system understanding

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

Smart, J. Allison Cory

1994-09-01

With the volume of software in production use dramatically increasing, the importance of software maintenance has become strikingly apparent. Techniques now sought and developed for reverse engineering and design extraction and recovery. At present, numerous commercial products and research tools exist which are capable of visualizing a variety of programming languages and software constructs. The list of new tools and services continues to grow rapidly. Although the scope of the existing commercial and academic product set is quite broad, these tools still share a common underlying problem. The ability of each tool to visually organize object representations is increasingly impairedmore » as the number of components and component dependencies within systems increases. Regardless of how objects are defined, complex ``spaghetti`` networks result in nearly all large system cases. While this problem is immediately apparent in modem systems analysis involving large software implementations, it is not new. As will be discussed in Chapter 2, related problems involving the theory of graphs were identified long ago. This important theoretical foundation provides a useful vehicle for representing and analyzing complex system structures. While the utility of directed graph based concepts in software tool design has been demonstrated in literature, these tools still lack the capabilities necessary for large system comprehension. This foundation must therefore be expanded with new organizational and visualization constructs necessary to meet this challenge. This dissertation addresses this need by constructing a conceptual model and a set of methods for interactively exploring, organizing, and understanding the structure of complex software systems.« less

LIFE Materials: Thermomechanical Effects Volume 5 - Part I

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

Caro, M; DeMange, P; Marian, J

2009-05-07

Improved fuel performance is a key issue in the current Laser Inertial-Confinement Fusion-Fission Energy (LIFE) engine design. LIFE is a fusion-fission engine composed of a {approx}40-tons fuel blanket surrounding a pulsed fusion neutron source. Fusion neutrons get multiplied and moderated in a Beryllium blanket before penetrating the subcritical fission blanket. The fuel in the blanket is composed of millions of fuel pebbles, and can in principle be burned to over 99% FIMA without refueling or reprocessing. This report contains the following chapters: Chapter A: LIFE Requirements for Materials -- LIFE Fuel; Chapter B: Summary of Existing Knowledge; Chapter C: Identificationmore » of Gaps in Knowledge & Vulnerabilities; and Chapter D: Strategy and Future Work.« less

Chapter D. The Loma Prieta, California, Earthquake of October 17, 1989 - Earth Structures and Engineering Characterization of Ground Motion

USGS Publications Warehouse

Holzer, Thomas L.

1998-01-01

This chapter contains two papers that summarize the performance of engineered earth structures, dams and stabilized excavations in soil, and two papers that characterize for engineering purposes the attenuation of ground motion with distance during the Loma Prieta earthquake. Documenting the field performance of engineered structures and confirming empirically based predictions of ground motion are critical for safe and cost effective seismic design of future structures as well as the retrofitting of existing ones.

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.

Designing Distributed Learning Environments with Intelligent Software Agents

ERIC Educational Resources Information Center

Lin, Fuhua, Ed.

2005-01-01

"Designing Distributed Learning Environments with Intelligent Software Agents" reports on the most recent advances in agent technologies for distributed learning. Chapters are devoted to the various aspects of intelligent software agents in distributed learning, including the methodological and technical issues on where and how intelligent agents…

Software Development for EECU Platform of Turbofan Engine

NASA Astrophysics Data System (ADS)

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

2017-04-01

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

Software engineering methodologies and tools

NASA Technical Reports Server (NTRS)

Wilcox, Lawrence M.

1993-01-01

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

Annotated bibliography of software engineering laboratory literature

NASA Technical Reports Server (NTRS)

Kistler, David; Bristow, John; Smith, Don

1994-01-01

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

Software Engineering Improvement Activities/Plan

NASA Technical Reports Server (NTRS)

2003-01-01

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

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

BOOK REVIEW: The Illustrated Wavelet Transform Handbook: Introductory Theory and Applications in Science, Engineering, Medicine and Finance

NASA Astrophysics Data System (ADS)

Ng, J.; Kingsbury, N. G.

2004-02-01

This book provides an overview of the theory and practice of continuous and discrete wavelet transforms. Divided into seven chapters, the first three chapters of the book are introductory, describing the various forms of the wavelet transform and their computation, while the remaining chapters are devoted to applications in fluids, engineering, medicine and miscellaneous areas. Each chapter is well introduced, with suitable examples to demonstrate key concepts. Illustrations are included where appropriate, thus adding a visual dimension to the text. A noteworthy feature is the inclusion, at the end of each chapter, of a list of further resources from the academic literature which the interested reader can consult. The first chapter is purely an introduction to the text. The treatment of wavelet transforms begins in the second chapter, with the definition of what a wavelet is. The chapter continues by defining the continuous wavelet transform and its inverse and a description of how it may be used to interrogate signals. The continuous wavelet transform is then compared to the short-time Fourier transform. Energy and power spectra with respect to scale are also discussed and linked to their frequency counterparts. Towards the end of the chapter, the two-dimensional continuous wavelet transform is introduced. Examples of how the continuous wavelet transform is computed using the Mexican hat and Morlet wavelets are provided throughout. The third chapter introduces the discrete wavelet transform, with its distinction from the discretized continuous wavelet transform having been made clear at the end of the second chapter. In the first half of the chapter, the logarithmic discretization of the wavelet function is described, leading to a discussion of dyadic grid scaling, frames, orthogonal and orthonormal bases, scaling functions and multiresolution representation. The fast wavelet transform is introduced and its computation is illustrated with an example using the Haar wavelet. The second half of the chapter groups together miscellaneous points about the discrete wavelet transform, including coefficient manipulation for signal denoising and smoothing, a description of Daubechies’ wavelets, the properties of translation invariance and biorthogonality, the two-dimensional discrete wavelet transforms and wavelet packets. The fourth chapter is dedicated to wavelet transform methods in the author’s own specialty, fluid mechanics. Beginning with a definition of wavelet-based statistical measures for turbulence, the text proceeds to describe wavelet thresholding in the analysis of fluid flows. The remainder of the chapter describes wavelet analysis of engineering flows, in particular jets, wakes, turbulence and coherent structures, and geophysical flows, including atmospheric and oceanic processes. The fifth chapter describes the application of wavelet methods in various branches of engineering, including machining, materials, dynamics and information engineering. Unlike previous chapters, this (and subsequent) chapters are styled more as literature reviews that describe the findings of other authors. The areas addressed in this chapter include: the monitoring of machining processes, the monitoring of rotating machinery, dynamical systems, chaotic systems, non-destructive testing, surface characterization and data compression. The sixth chapter continues in this vein with the attention now turned to wavelets in the analysis of medical signals. Most of the chapter is devoted to the analysis of one-dimensional signals (electrocardiogram, neural waveforms, acoustic signals etc.), although there is a small section on the analysis of two-dimensional medical images. The seventh and final chapter of the book focuses on the application of wavelets in three seemingly unrelated application areas: fractals, finance and geophysics. The treatment on wavelet methods in fractals focuses on stochastic fractals with a short section on multifractals. The treatment on finance touches on the use of wavelets by other authors in studying stock prices, commodity behaviour, market dynamics and foreign exchange rates. The treatment on geophysics covers what was omitted from the fourth chapter, namely, seismology, well logging, topographic feature analysis and the analysis of climatic data. The text concludes with an assortment of other application areas which could only be mentioned in passing. Unlike most other publications in the subject, this book does not treat wavelet transforms in a mathematically rigorous manner but rather aims to explain the mechanics of the wavelet transform in a way that is easy to understand. Consequently, it serves as an excellent overview of the subject rather than as a reference text. Keeping the mathematics to a minimum and omitting cumbersome and detailed proofs from the text, the book is best-suited to those who are new to wavelets or who want an intuitive understanding of the subject. Such an audience may include graduate students in engineering and professionals and researchers in engineering and the applied sciences.

Administrator's Guide to Technology: Planning, Funding & Implementation.

ERIC Educational Resources Information Center

Aspen Education Development Group, Gaithersburg, MD.

This document provides guidelines for administrators related to instructional technology and planning. Chapter 1 discusses planning, including developing a technology plan, facility assessment, e-rate planning, formation of a technology committee, budget planning, and hardware/software replacement plan and costs. Chapter 2 addresses…

Software Engineering for Human Spaceflight

NASA Technical Reports Server (NTRS)

Fredrickson, Steven E.

2014-01-01

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

Software engineering from a Langley perspective

NASA Technical Reports Server (NTRS)

Voigt, Susan

1994-01-01

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

The need for scientific software engineering in the pharmaceutical industry

NASA Astrophysics Data System (ADS)

Luty, Brock; Rose, Peter W.

2017-03-01

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

The need for scientific software engineering in the pharmaceutical industry.

PubMed

Luty, Brock; Rose, Peter W

2017-03-01

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

Engineering Aid 3 & 2, Vol. 1. Rate Training Manual and Nonresident Career Course.

ERIC Educational Resources Information Center

Naval Education and Training Command, Washington, DC.

Designed for individual study and not formal classroom instruction, this rate training manual provides subject matter that relates directly to the occupational qualifications of the Engineering Aid (EA) rating. This eight-chapter volume focuses on administrative matters, mathematics, and basic drafting. Chapter 1 discusses the scope of the EA…

Turbojet-engine Starting and Acceleration

NASA Technical Reports Server (NTRS)

Mc Cafferty, R. J.; Straight, D. M.

1956-01-01

From considerations of safety and reliability in performance of gas-turbine aircraft, it is clear that engine starting and acceleration are of utmost importance. For this reason extensive efforts have been devoted to the investigation of the factors involved in the starting and acceleration of engines. In chapter III it is shown that certain basic combustion requirements must be met before ignition can occur; consequently, the design and operation of an engine must be tailored to provide these basic requirements in the combustion zone of the engine, particularly in the vicinity of the ignition source. It is pointed out in chapter III that ignition by electrical discharges is aided by high pressure, high temperature, low gas velocity and turbulence, gaseous fuel-air mixture, proper mixture strength, and-an optimum spark. duration. The simultaneous achievement of all these requirements in an actual turbojet-engine combustor is obviously impossible, yet any attempt to satisfy as many requirements as possible will result in lower ignition energies, lower-weight ignition systems, and greater reliability. These factors together with size and cost considerations determine the acceptability of the final ignition system. It is further shown in chapter III that the problem of wall quenching affects engine starting. For example, the dimensions of the volume to be burned must be larger than the quenching distance at the lowest pressure and the most adverse fuel-air ratio encountered. This fact affects the design of cross-fire tubes between adjacent combustion chambers in a tubular-combustor turbojet engine. Only two chambers in these engines contain spark plugs; therefore, the flame must propagate through small connecting tubes between the chambers. The quenching studies indicate that if the cross-fire tubes are too narrow the flame will not propagate from one chamber to another. In order to better understand the role of the basic factors in actual engine operation, many investigations have been conducted in single combustors from gas-turbine engines and in full-scale engines in altitude tanks and in flight. The purpose of the present chapter is to discuss the results of such studies and, where possible, to interpret these results qualitatively in terms of the basic requirements reported in chapter III. The discussion parallels the three phases of turbojet engine starting: (1) Ignition of the fuel-air mixture (2) Propagation of flame throughout the combustion zone (3) Acceleration of the engine to operating speed.

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.

Engineering mechanics: statics and dynamics. [Textbook

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

Sandor, B.I.

1983-01-01

The purpose of this textbook is to provide engineering students with basic learning material about statics and dynamics which are fundamental engineering subjects. The chapters contain information on: an introduction to engineering mechanics; forces on particles, rigid bodies, and structures; kinetics of particles, particle systems, and rigid bodies in motion; kinematics; mechanical vibrations; and friction, work, moments of inertia, and potential energy. Each chapter contains introductory material, the development of the essential equations, worked-out example problems, homework problems, and, finally, summaries of the essential methods and equations, graphically illustrated where appropriate. (LCL)

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.

Modular Knowledge Representation and Reasoning in the Semantic Web

NASA Astrophysics Data System (ADS)

Serafini, Luciano; Homola, Martin

Construction of modular ontologies by combining different modules is becoming a necessity in ontology engineering in order to cope with the increasing complexity of the ontologies and the domains they represent. The modular ontology approach takes inspiration from software engineering, where modularization is a widely acknowledged feature. Distributed reasoning is the other side of the coin of modular ontologies: given an ontology comprising of a set of modules, it is desired to perform reasoning by combination of multiple reasoning processes performed locally on each of the modules. In the last ten years, a number of approaches for combining logics has been developed in order to formalize modular ontologies. In this chapter, we survey and compare the main formalisms for modular ontologies and distributed reasoning in the Semantic Web. We select four formalisms build on formal logical grounds of Description Logics: Distributed Description Logics, ℰ-connections, Package-based Description Logics and Integrated Distributed Description Logics. We concentrate on expressivity and distinctive modeling features of each framework. We also discuss reasoning capabilities of each framework.

Regional demand forecasting and simulation model: user's manual. Task 4, final report

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

Parhizgari, A M

1978-09-25

The Department of Energy's Regional Demand Forecasting Model (RDFOR) is an econometric and simulation system designed to estimate annual fuel-sector-region specific consumption of energy for the US. Its purposes are to (1) provide the demand side of the Project Independence Evaluation System (PIES), (2) enhance our empirical insights into the structure of US energy demand, and (3) assist policymakers in their decisions on and formulations of various energy policies and/or scenarios. This report provides a self-contained user's manual for interpreting, utilizing, and implementing RDFOR simulation software packages. Chapters I and II present the theoretical structure and the simulation of RDFOR,more » respectively. Chapter III describes several potential scenarios which are (or have been) utilized in the RDFOR simulations. Chapter IV presents an overview of the complete software package utilized in simulation. Chapter V provides the detailed explanation and documentation of this package. The last chapter describes step-by-step implementation of the simulation package using the two scenarios detailed in Chapter III. The RDFOR model contains 14 fuels: gasoline, electricity, natural gas, distillate and residual fuels, liquid gases, jet fuel, coal, oil, petroleum products, asphalt, petroleum coke, metallurgical coal, and total fuels, spread over residential, commercial, industrial, and transportation sectors.« less

Spacecraft Systems Engineering, 3rd Edition

NASA Astrophysics Data System (ADS)

Fortescue, Peter; Stark, John; Swinerd, Graham

2003-03-01

Following on from the hugely successful previous editions, the third edition of Spacecraft Systems Engineering incorporates the most recent technological advances in spacecraft and satellite engineering. With emphasis on recent developments in space activities, this new edition has been completely revised. Every chapter has been updated and rewritten by an expert engineer in the field, with emphasis on the bus rather than the payload. Encompassing the fundamentals of spacecraft engineering, the book begins with front-end system-level issues, such as environment, mission analysis and system engineering, and progresses to a detailed examination of subsystem elements which represent the core of spacecraft design - mechanical, electrical, propulsion, thermal, control etc. This quantitative treatment is supplemented by an appreciation of the interactions between the elements, which deeply influence the process of spacecraft systems design. In particular the revised text includes * A new chapter on small satellites engineering and applications which has been contributed by two internationally-recognised experts, with insights into small satellite systems engineering. * Additions to the mission analysis chapter, treating issues of aero-manouevring, constellation design and small body missions. In summary, this is an outstanding textbook for aerospace engineering and design students, and offers essential reading for spacecraft engineers, designers and research scientists. The comprehensive approach provides an invaluable resource to spacecraft manufacturers and agencies across the world.

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.

The Profiles in Practice School Reporting Software.

ERIC Educational Resources Information Center

Griffin, Patrick

"The Profiles in Practice: School Reporting Software" provides a framework for reports on different aspects of performance in an assessment program. This booklet is the installation guide and user manual for the Profiles in Practice software, which is included as a CD-ROM. The chapters of the guide are: (1) "Installation"; (2) "Starting the…

j5 DNA assembly design automation.

PubMed

Hillson, Nathan J

2014-01-01

Modern standardized methodologies, described in detail in the previous chapters of this book, have enabled the software-automated design of optimized DNA construction protocols. This chapter describes how to design (combinatorial) scar-less DNA assembly protocols using the web-based software j5. j5 assists biomedical and biotechnological researchers construct DNA by automating the design of optimized protocols for flanking homology sequence as well as type IIS endonuclease-mediated DNA assembly methodologies. Unlike any other software tool available today, j5 designs scar-less combinatorial DNA assembly protocols, performs a cost-benefit analysis to identify which portions of an assembly process would be less expensive to outsource to a DNA synthesis service provider, and designs hierarchical DNA assembly strategies to mitigate anticipated poor assembly junction sequence performance. Software integrated with j5 add significant value to the j5 design process through graphical user-interface enhancement and downstream liquid-handling robotic laboratory automation.

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.

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.

46 CFR 119.425 - Engine exhaust cooling.

Code of Federal Regulations, 2010 CFR

2010-10-01

..., all engine exhaust pipes must be water cooled. (1) Vertical dry exhaust pipes are permissible if installed in compliance with §§ 116.405(c) and 116.970 of this chapter. (2) Horizontal dry exhaust pipes are...) They are installed in compliance with §§ 116.405(c) and 116.970 of this chapter. (b) The exhaust pipe...

Software Defined Network Monitoring Scheme Using Spectral Graph Theory and Phantom Nodes

DTIC Science & Technology

2014-09-01

networks is the emergence of software - defined networking ( SDN ) [1]. SDN has existed for the...Chapter III for network monitoring. A. SOFTWARE DEFINED NETWORKS SDNs provide a new and innovative method to simplify network hardware by logically...and R. Giladi, “Performance analysis of software - defined networking ( SDN ),” in Proc. of IEEE 21st International Symposium on Modeling, Analysis

A Mechanized Decision Support System for Academic Scheduling.

DTIC Science & Technology

1986-03-01

an operational system called software. The first step in the development phase is Design . Designers destribute software control by factoring the Data...SUBJECT TERMS (Continue on reverse if necessary and identify by block number) ELD GROUP SUB-GROUP Scheduling, Decision Support System , Software Design ...scheduling system . It will also examine software - design techniques to identify the most appropriate method- ology for this problem. " - Chapter 3 will

Student Tracking.

ERIC Educational Resources Information Center

Donovan, Kevin

1996-01-01

This report explains how student tracking systems work and why they are important. It is designed for British funding bodies, further education (FE) colleges, college staff, and software developers to introduce and support systems of student tracking. Chapter 1 provides background information on tracking and the FE sector. Chapter 2 discusses the…

Genetic data analysis for plant and animal breeding

USDA-ARS?s Scientific Manuscript database

This book is an advanced textbook covering the application of quantitative genetics theory to analysis of actual data (both trait and DNA marker information) for breeding populations of crops, trees, and animals. Chapter 1 is an introduction to basic software used for trait data analysis. Chapter 2 ...

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…

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.

Agile Software Development in the Department of Defense Environment

DTIC Science & Technology

2017-03-31

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

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.

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

46 CFR 70.20-1 - Marine engineering details.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 3 2011-10-01 2011-10-01 false Marine engineering details. 70.20-1 Section 70.20-1... General Marine Engineering Requirements § 70.20-1 Marine engineering details. All marine engineering... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 70.20-1 - Marine engineering details.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 3 2013-10-01 2013-10-01 false Marine engineering details. 70.20-1 Section 70.20-1... General Marine Engineering Requirements § 70.20-1 Marine engineering details. All marine engineering... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 70.20-1 - Marine engineering details.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 3 2014-10-01 2014-10-01 false Marine engineering details. 70.20-1 Section 70.20-1... General Marine Engineering Requirements § 70.20-1 Marine engineering details. All marine engineering... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 70.20-1 - Marine engineering details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 3 2010-10-01 2010-10-01 false Marine engineering details. 70.20-1 Section 70.20-1... General Marine Engineering Requirements § 70.20-1 Marine engineering details. All marine engineering... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 70.20-1 - Marine engineering details.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 3 2012-10-01 2012-10-01 false Marine engineering details. 70.20-1 Section 70.20-1... General Marine Engineering Requirements § 70.20-1 Marine engineering details. All marine engineering... subchapter F (Marine Engineering) of this chapter. ...

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

DTIC Science & Technology

1992-08-01

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

A report on NASA software engineering and Ada training requirements

NASA Technical Reports Server (NTRS)

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

1987-01-01

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

Beaming Electricity via Relay Satellites in Support of Deployed Combat Forces

DTIC Science & Technology

2012-09-01

Power kHz Kilohertz km Kilometer kW Kilowatt kW/h Kilowatt/hour LEO Low Earth Orbit MEO Medium Earth Orbit MW Megawatt RF Radio Frequency STK ...using the Satellite Tool Kit ( STK ) software suite. D. CHAPTER SUMMARY 1. Chapter II - Background This chapter contains background information to...are modeled using STK . The results of those models are presented. A description of how each model took shape was developed is provided followed

Linking Goal-Oriented Requirements and Model-Driven Development

NASA Astrophysics Data System (ADS)

Pastor, Oscar; Giachetti, Giovanni

In the context of Goal-Oriented Requirement Engineering (GORE) there are interesting modeling approaches for the analysis of complex scenarios that are oriented to obtain and represent the relevant requirements for the development of software products. However, the way to use these GORE models in an automated Model-Driven Development (MDD) process is not clear, and, in general terms, the translation of these models into the final software products is still manually performed. Therefore, in this chapter, we show an approach to automatically link GORE models and MDD processes, which has been elaborated by considering the experience obtained from linking the i * framework with an industrially applied MDD approach. The linking approach proposed is formulated by means of a generic process that is based on current modeling standards and technologies in order to facilitate its application for different MDD and GORE approaches. Special attention is paid to how this process generates appropriate model transformation mechanisms to automatically obtain MDD conceptual models from GORE models, and how it can be used to specify validation mechanisms to assure the correct model transformations.

Performance Evaluation and Benchmarking of Next Intelligent Systems

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

del Pobil, Angel; Madhavan, Raj; Bonsignorio, Fabio

Performance Evaluation and Benchmarking of Intelligent Systems presents research dedicated to the subject of performance evaluation and benchmarking of intelligent systems by drawing from the experiences and insights of leading experts gained both through theoretical development and practical implementation of intelligent systems in a variety of diverse application domains. This contributed volume offers a detailed and coherent picture of state-of-the-art, recent developments, and further research areas in intelligent systems. The chapters cover a broad range of applications, such as assistive robotics, planetary surveying, urban search and rescue, and line tracking for automotive assembly. Subsystems or components described in this bookmore » include human-robot interaction, multi-robot coordination, communications, perception, and mapping. Chapters are also devoted to simulation support and open source software for cognitive platforms, providing examples of the type of enabling underlying technologies that can help intelligent systems to propagate and increase in capabilities. Performance Evaluation and Benchmarking of Intelligent Systems serves as a professional reference for researchers and practitioners in the field. This book is also applicable to advanced courses for graduate level students and robotics professionals in a wide range of engineering and related disciplines including computer science, automotive, healthcare, manufacturing, and service robotics.« less

V&V Within Reuse-Based Software Engineering

NASA Technical Reports Server (NTRS)

Addy, Edward A.

1996-01-01

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

Professional Ethics of Software Engineers: An Ethical Framework.

PubMed

Lurie, Yotam; Mark, Shlomo

2016-04-01

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

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

NASA Technical Reports Server (NTRS)

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

2004-01-01

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

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

NASA Astrophysics Data System (ADS)

Deqiang, Hu

2018-03-01

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

Real-Time Considerations for Rugged Embedded Systems

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

Tumeo, Antonino; Ceriani, Marco; Palermo, Gianluca

This chapter introduces the characterizing aspects of embedded systems, and discusses the specific features that a designer should address to an embedded system “rugged”, i.e., able to operate reliably in harsh environments. The chapter addresses both the hardware and the less obvious software aspect. After presenting a current list of certifications for ruggedization, the chapters present a case study that focuses on the interaction of the hardware and software layers in reactive real-time system. In particular, it shows how the use of fast FPGA prototyping could provide insights on unexpected factors that influence the performance and thus responsiveness to eventsmore » of a scheduling algorithm for multiprocessor systems that manages both periodic, hard real-time task, and aperiodic tasks. The main lesson is that to make the system “rugged”, a designer should consider these issues by, for example, overprovisioning resources and/or computation capabilities.« less

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.

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 And Systems Engineering Risk Management

DTIC Science & Technology

2010-04-01

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

Proceedings of the 19th Annual Software Engineering Workshop

NASA Technical Reports Server (NTRS)

1994-01-01

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

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

NASA Technical Reports Server (NTRS)

Heller, Gerard; Valett, Jon; Wild, Mary

1992-01-01

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

Annotated bibliography of Software Engineering Laboratory literature

NASA Technical Reports Server (NTRS)

1985-01-01

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

Modular Rocket Engine Control Software (MRECS)

NASA Technical Reports Server (NTRS)

Tarrant, Charlie; Crook, Jerry

1997-01-01

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

Software Engineering Improvement Plan

NASA Technical Reports Server (NTRS)

2006-01-01

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

Steam jet ejectors for the process industries. [Glossary included

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

Power, R.B.

1994-01-01

Steam jet ejectors were for many years the workhorse of the chemical process industries for producing vacuum. With increasing emphasis on stricter pollution control, their use was curtailed. There are still many applications, however, such as those with large capacity requirements, where ejectors are the only equipment that can produce sufficient vacuum. Chapter 1 is a short overview on how to use the text. Chapter 2 discusses what an ejector is and how it works. How ejector stages work is reviewed in Chapter 3. Engineering calculations for ejector stages is thoroughly discussed in Chapter 4. In Chapter 5, contact andmore » surface condensers are reviewed, and calculation procedures are presented. The various types of pressure control are discussed in Chapter 6. Chapter 7 is an excellent review of installation of ejector vacuum systems. The final chapter of Part 2 (Chapters 3--8) thoroughly covers all aspects of operation, testing, troubleshooting and maintenance. Part 3, consisting of two chapters, is devoted to specifying and purchasing steam jet ejectors. Part 4 on other ejector applications and upgrading ejector usage also consists of two chapters. Chapter 11 reviews steam-jet refrigeration, steam-jet and gas-jet compressors, liquid jet eductors, desuperheaters, special design situations, and designing one's own systems. Upgrading of existing ejector procedures and hardware is reviewed in Chapter 12. The 12 appendixes cover: physical properties of common fluids; handy vacuum engineering data and rules of thumb; SI unit conversions; sizing air and steam metering orifices for testing; drill sizes; ejector operating costs and design optimization; forms for ejector calculations, tests, and inspections; instructions for preparing ejector specifications; test kit contents list; ejector manufacturers and suppliers of referenced hardware and information; and failure modes and symptoms.« less

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

Electronic Job Search Revolution. Win with the New Technology that's Reshaping Today's Job Market.

ERIC Educational Resources Information Center

Kennedy, Joyce Lain; Morrow, Thomas J.

This book contains information about the resources available to merge new technology and the search for employment. It offers suggestions from human resource specialists, software authors, and database experts. Chapter 1 is an overview of how the computer has become indispensable in a job search. Chapter 2 focuses on external, third-party resume…

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.

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…

46 CFR 188.20-1 - Marine engineering details.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 7 2012-10-01 2012-10-01 false Marine engineering details. 188.20-1 Section 188.20-1... PROVISIONS General Marine Engineering Requirements § 188.20-1 Marine engineering details. (a) The marine engineering details shall be in accordance with Subchapter F (Marine Engineering) of this chapter. ...

46 CFR 188.20-1 - Marine engineering details.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 7 2014-10-01 2014-10-01 false Marine engineering details. 188.20-1 Section 188.20-1... PROVISIONS General Marine Engineering Requirements § 188.20-1 Marine engineering details. (a) The marine engineering details shall be in accordance with Subchapter F (Marine Engineering) of this chapter. ...

46 CFR 188.20-1 - Marine engineering details.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 7 2011-10-01 2011-10-01 false Marine engineering details. 188.20-1 Section 188.20-1... PROVISIONS General Marine Engineering Requirements § 188.20-1 Marine engineering details. (a) The marine engineering details shall be in accordance with Subchapter F (Marine Engineering) of this chapter. ...

46 CFR 24.20-1 - Marine engineering details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 1 2010-10-01 2010-10-01 false Marine engineering details. 24.20-1 Section 24.20-1... Engineering Requirements § 24.20-1 Marine engineering details. (a) All marine engineering details relative to... 40 feet in length will be found in subchapter F (Marine Engineering) of this chapter. ...

46 CFR 188.20-1 - Marine engineering details.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 7 2013-10-01 2013-10-01 false Marine engineering details. 188.20-1 Section 188.20-1... PROVISIONS General Marine Engineering Requirements § 188.20-1 Marine engineering details. (a) The marine engineering details shall be in accordance with Subchapter F (Marine Engineering) of this chapter. ...

46 CFR 188.20-1 - Marine engineering details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 7 2010-10-01 2010-10-01 false Marine engineering details. 188.20-1 Section 188.20-1... PROVISIONS General Marine Engineering Requirements § 188.20-1 Marine engineering details. (a) The marine engineering details shall be in accordance with Subchapter F (Marine Engineering) of this chapter. ...

46 CFR 24.20-1 - Marine engineering details.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 1 2011-10-01 2011-10-01 false Marine engineering details. 24.20-1 Section 24.20-1... Engineering Requirements § 24.20-1 Marine engineering details. (a) All marine engineering details relative to... 40 feet in length will be found in subchapter F (Marine Engineering) of this chapter. ...

A Knowledge Engineering Approach to Analysis and Evaluation of Construction Schedules

DTIC Science & Technology

1990-02-01

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

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

NASA Technical Reports Server (NTRS)

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

2006-01-01

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

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.

46 CFR 119.430 - Engine exhaust pipe installation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... protected from mechanical damage. (e) Where flexibility is necessary, a section of flexible metallic hose... the material requirements of part 56 of subchapter F (Marine Engineering) of this chapter. (k) Engine...

46 CFR 119.430 - Engine exhaust pipe installation.

Code of Federal Regulations, 2014 CFR

2014-10-01

... protected from mechanical damage. (e) Where flexibility is necessary, a section of flexible metallic hose... the material requirements of part 56 of subchapter F (Marine Engineering) of this chapter. (k) Engine...

46 CFR 119.430 - Engine exhaust pipe installation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... protected from mechanical damage. (e) Where flexibility is necessary, a section of flexible metallic hose... the material requirements of part 56 of subchapter F (Marine Engineering) of this chapter. (k) Engine...

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.

The self-assembling process and applications in tissue engineering

PubMed Central

Lee, Jennifer K.; Link, Jarrett M.; Hu, Jerry C. Y.; Athanasiou, Kyriacos A.

2018-01-01

Tissue engineering strives to create neotissues capable of restoring function. Scaffold-free technologies have emerged that can recapitulate native tissue function without the use of an exogenous scaffold. This chapter will survey, in particular, the self-assembling and self-organization processes as scaffold-free techniques. Characteristics and benefits of each process are described, and key examples of tissues created using these scaffold-free processes are examined to provide guidance for future tissue engineering developments. This chapter aims to explore the potential of self-assembly and self-organization scaffold-free approaches, detailing the recent progress in the in vitro tissue engineering of biomimetic tissues with these methods, toward generating functional tissue replacements. PMID:28348174

46 CFR 107.305 - Plans and information.

Code of Federal Regulations, 2013 CFR

2013-10-01

... systems. Marine Engineering (z) Plans required for marine engineering equipment and systems by Subchapter F of this chapter. Electrical Engineering (aa) Plans required for electrical engineering equipment... materials that do not conform to ABS or ASTM specifications, complete specifications, including chemical and...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 2 2012-10-01 2012-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 2 2010-10-01 2010-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 2 2014-10-01 2014-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 2 2013-10-01 2013-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

46 CFR 46.15-5 - Engineering requirements.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 2 2011-10-01 2011-10-01 false Engineering requirements. 46.15-5 Section 46.15-5... Lakes Voyages § 46.15-5 Engineering requirements. (a) Bilge and ballast systems, piping, inlets and... subchapter F (Marine Engineering) of this chapter. ...

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

Teacher's Guide to SERAPHIM Software I. Chemistry: Experimental Foundations.

ERIC Educational Resources Information Center

Bogner, Donna J.

Designed to assist chemistry teachers in selecting appropriate software programs, this publication is the first in a series of six teacher's guides from Project SERAPHIM, a program sponsored by the National Science Foundation. This guide is keyed to the chapters of the text "Chemistry: Experimental Foundations." Program suggestions are…

Teacher's Guide to SERAPHIM Software II. Chemical Principles.

ERIC Educational Resources Information Center

Bogner, Donna J.

Designed to assist chemistry teachers in selecting appropriate software programs, this publication is the second in a series of six teacher's guides from Project SERAPHIM, a program sponsored by the National Science Foundation. This guide is keyed to the chapters of the text "Chemical Principles." Program suggestions are arranged in the…

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

A Content Markup Language for Data Services

NASA Astrophysics Data System (ADS)

Noviello, C.; Acampa, P.; Mango Furnari, M.

Network content delivery and documents sharing is possible using a variety of technologies, such as distributed databases, service-oriented applications, and so forth. The development of such systems is a complex job, because document life cycle involves a strong cooperation between domain experts and software developers. Furthermore, the emerging software methodologies, such as the service-oriented architecture and knowledge organization (e.g., semantic web) did not really solve the problems faced in a real distributed and cooperating settlement. In this chapter the authors' efforts to design and deploy a distribute and cooperating content management system are described. The main features of the system are a user configurable document type definition and a management middleware layer. It allows CMS developers to orchestrate the composition of specialized software components around the structure of a document. In this chapter are also reported some of the experiences gained on deploying the developed framework in a cultural heritage dissemination settlement.

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.

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.

46 CFR 24.20-1 - Marine engineering details.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 1 2014-10-01 2014-10-01 false Marine engineering details. 24.20-1 Section 24.20-1... Engineering Requirements § 24.20-1 Marine engineering details. All marine engineering details relative to the... in length will be found in subchapter F (Marine Engineering) of this chapter. [USCG-2012-0832, 77 FR...

46 CFR 24.20-1 - Marine engineering details.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 1 2013-10-01 2013-10-01 false Marine engineering details. 24.20-1 Section 24.20-1... Engineering Requirements § 24.20-1 Marine engineering details. All marine engineering details relative to the... in length will be found in subchapter F (Marine Engineering) of this chapter. [USCG-2012-0832, 77 FR...

46 CFR 24.20-1 - Marine engineering details.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 1 2012-10-01 2012-10-01 false Marine engineering details. 24.20-1 Section 24.20-1... Engineering Requirements § 24.20-1 Marine engineering details. All marine engineering details relative to the... in length will be found in subchapter F (Marine Engineering) of this chapter. [USCG-2012-0832, 77 FR...

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.

46 CFR 126.470 - Marine-engineering systems.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 4 2010-10-01 2010-10-01 false Marine-engineering systems. 126.470 Section 126.470... CERTIFICATION Inspection for Certification § 126.470 Marine-engineering systems. The inspection procedures for marine-engineering systems contained in subchapter F of this chapter apply. ...

46 CFR 126.470 - Marine-engineering systems.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 4 2011-10-01 2011-10-01 false Marine-engineering systems. 126.470 Section 126.470... CERTIFICATION Inspection for Certification § 126.470 Marine-engineering systems. The inspection procedures for marine-engineering systems contained in subchapter F of this chapter apply. ...

46 CFR 126.470 - Marine-engineering systems.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 4 2014-10-01 2014-10-01 false Marine-engineering systems. 126.470 Section 126.470... CERTIFICATION Inspection for Certification § 126.470 Marine-engineering systems. The inspection procedures for marine-engineering systems contained in subchapter F of this chapter apply. ...

46 CFR 126.470 - Marine-engineering systems.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 4 2013-10-01 2013-10-01 false Marine-engineering systems. 126.470 Section 126.470... CERTIFICATION Inspection for Certification § 126.470 Marine-engineering systems. The inspection procedures for marine-engineering systems contained in subchapter F of this chapter apply. ...

46 CFR 126.470 - Marine-engineering systems.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 4 2012-10-01 2012-10-01 false Marine-engineering systems. 126.470 Section 126.470... CERTIFICATION Inspection for Certification § 126.470 Marine-engineering systems. The inspection procedures for marine-engineering systems contained in subchapter F of this chapter apply. ...

Metals and Ceramics Division progress report for period ending June 30, 1984

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

Brogden, I.

1984-09-01

This progress report covers the research and development activities of the Metals and Ceramics Division from January 1, 1983, through June 30, 1984. The format of the report follows the organizational structure of the division. Short summaries of technical work in progress in the various experimental groups are presented in six parts. Chapter 1 deals with the research and development activities of the Engineering Materials Section, Chapter 2 with the Processing Science and Technology Section, Chapter 3 with the Materials Science Section, Chapter 4 with Project Activities, Chapter 5 with Specialized Research Facilities and Equipment, and Chapter 6 with Miscellaneousmore » Activities.« less

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.

Opportunities in Mechnical Engineering. [VGM Career Horizons Series].

ERIC Educational Resources Information Center

Konzo, Seichi; Bayne, James W.

This book presents information on career opportunities in mechanical engineering. Chapter 1 describes the historical development of mechanical engineering and its interactions with society, considers the growth of the American Society of Mechanical Engineers, and discusses the relevance of mechanical engineering to present-day and future society.…

46 CFR 31.30-1 - Marine engineering regulations and material specifications-TB/ALL.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 1 2012-10-01 2012-10-01 false Marine engineering regulations and material... INSPECTION AND CERTIFICATION Marine Engineering § 31.30-1 Marine engineering regulations and material..., of subchapter F (Marine Engineering) of this chapter, whenever applicable, except as such regulations...

46 CFR 71.25-35 - Marine engineering equipment.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 3 2013-10-01 2013-10-01 false Marine engineering equipment. 71.25-35 Section 71.25-35... CERTIFICATION Annual Inspection § 71.25-35 Marine engineering equipment. (a) For inspection procedures of marine engineering equipment and systems, see subchapter F. (Marine Engineering) of this chapter. (b) [Reserved] ...

46 CFR 31.30-1 - Marine engineering regulations and material specifications-TB/ALL.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 1 2011-10-01 2011-10-01 false Marine engineering regulations and material... INSPECTION AND CERTIFICATION Marine Engineering § 31.30-1 Marine engineering regulations and material..., of subchapter F (Marine Engineering) of this chapter, whenever applicable, except as such regulations...

46 CFR 71.25-35 - Marine engineering equipment.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 3 2010-10-01 2010-10-01 false Marine engineering equipment. 71.25-35 Section 71.25-35... CERTIFICATION Annual Inspection § 71.25-35 Marine engineering equipment. (a) For inspection procedures of marine engineering equipment and systems, see subchapter F. (Marine Engineering) of this chapter. (b) [Reserved] ...

46 CFR 71.25-35 - Marine engineering equipment.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 3 2014-10-01 2014-10-01 false Marine engineering equipment. 71.25-35 Section 71.25-35... CERTIFICATION Annual Inspection § 71.25-35 Marine engineering equipment. (a) For inspection procedures of marine engineering equipment and systems, see subchapter F. (Marine Engineering) of this chapter. (b) [Reserved] ...

46 CFR 31.30-1 - Marine engineering regulations and material specifications-TB/ALL.

Code of Federal Regulations, 2014 CFR

2014-10-01

... 46 Shipping 1 2014-10-01 2014-10-01 false Marine engineering regulations and material... INSPECTION AND CERTIFICATION Marine Engineering § 31.30-1 Marine engineering regulations and material..., of subchapter F (Marine Engineering) of this chapter, whenever applicable, except as such regulations...

46 CFR 31.30-1 - Marine engineering regulations and material specifications-TB/ALL.

Code of Federal Regulations, 2010 CFR

2010-10-01

... 46 Shipping 1 2010-10-01 2010-10-01 false Marine engineering regulations and material... INSPECTION AND CERTIFICATION Marine Engineering § 31.30-1 Marine engineering regulations and material..., of subchapter F (Marine Engineering) of this chapter, whenever applicable, except as such regulations...

46 CFR 71.25-35 - Marine engineering equipment.

Code of Federal Regulations, 2012 CFR

2012-10-01

... 46 Shipping 3 2012-10-01 2012-10-01 false Marine engineering equipment. 71.25-35 Section 71.25-35... CERTIFICATION Annual Inspection § 71.25-35 Marine engineering equipment. (a) For inspection procedures of marine engineering equipment and systems, see subchapter F. (Marine Engineering) of this chapter. (b) [Reserved] ...

46 CFR 31.30-1 - Marine engineering regulations and material specifications-TB/ALL.

Code of Federal Regulations, 2013 CFR

2013-10-01

... 46 Shipping 1 2013-10-01 2013-10-01 false Marine engineering regulations and material... INSPECTION AND CERTIFICATION Marine Engineering § 31.30-1 Marine engineering regulations and material..., of subchapter F (Marine Engineering) of this chapter, whenever applicable, except as such regulations...

46 CFR 71.25-35 - Marine engineering equipment.

Code of Federal Regulations, 2011 CFR

2011-10-01

... 46 Shipping 3 2011-10-01 2011-10-01 false Marine engineering equipment. 71.25-35 Section 71.25-35... CERTIFICATION Annual Inspection § 71.25-35 Marine engineering equipment. (a) For inspection procedures of marine engineering equipment and systems, see subchapter F. (Marine Engineering) of this chapter. (b) [Reserved] ...

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.

Gaia DR1 documentation Chapter 6: Variability

NASA Astrophysics Data System (ADS)

Eyer, L.; Rimoldini, L.; Guy, L.; Holl, B.; Clementini, G.; Cuypers, J.; Mowlavi, N.; Lecoeur-Taïbi, I.; De Ridder, J.; Charnas, J.; Nienartowicz, K.

2017-12-01

This chapter describes the photometric variability processing of the Gaia DR1 data. Coordination Unit 7 is responsible for the variability analysis of over a billion celestial sources. In particular the definition, design, development, validation and provision of a software package for the data processing of photometrically variable objects. Data Processing Centre Geneva (DPCG) responsibilities cover all issues related to the computational part of the CU7 analysis. These span: hardware provisioning, including selection, deployment and optimisation of suitable hardware, choosing and developing software architecture, defining data and scientific workflows as well as operational activities such as configuration management, data import, time series reconstruction, storage and processing handling, visualisation and data export. CU7/DPCG is also responsible for interaction with other DPCs and CUs, software and programming training for the CU7 members, scientific software quality control and management of software and data lifecycle. Details about the specific data treatment steps of the Gaia DR1 data products are found in Eyer et al. (2017) and are not repeated here. The variability content of the Gaia DR1 focusses on a subsample of Cepheids and RR Lyrae stars around the South ecliptic pole, showcasing the performance of the Gaia photometry with respect to variable objects.

A network-oriented business modeling environment

NASA Astrophysics Data System (ADS)

Bisconti, Cristian; Storelli, Davide; Totaro, Salvatore; Arigliano, Francesco; Savarino, Vincenzo; Vicari, Claudia

The development of formal models related to the organizational aspects of an enterprise is fundamental when these aspects must be re-engineered and digitalized, especially when the enterprise is involved in the dynamics and value flows of a business network. Business modeling provides an opportunity to synthesize and make business processes, business rules and the structural aspects of an organization explicit, allowing business managers to control their complexity and guide an enterprise through effective decisional and strategic activities. This chapter discusses the main results of the TEKNE project in terms of software components that enable enterprises to configure, store, search and share models of any aspects of their business while leveraging standard and business-oriented technologies and languages to bridge the gap between the world of business people and IT experts and to foster effective business-to-business collaborations.

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…

KEPCO‧s Activity to Power-Engineer Human Resource Development

NASA Astrophysics Data System (ADS)

Kobashi, Kazushi

While business environment changes a lot, in order to aim at realization of “what we want the Group to look like in 2030” , it is necessary to cultivate human resources with a strong sense of mission. We need to prepare an opportunity to teach and to be taught, in order to cultivate resources and a measure for connecting every person‧s growth to growth of a company. In chapter one, we show Five Trends for attaining what KANSAI Electric Power Corporation wants to be and explain the importance of human resource development under the changing environment. In chapter two, we explain the fundamental policy of human resource cultivation and describe the development plan and the facilities for training based on the policy in chapter two. In chapter three, we express the specific efforts in the field of maintenance, construction, and operation at the department of Engineering and Operation.

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

Friendly Neighborhood Computer Project. Extension of the IBM NJE network to DEC VAX computers

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

Raffenetti, R.C.; Bertoncini, P.J.; Engert, D.E.

1984-07-01

This manual is divided into six chapters. The first is an overview of the VAX NJE emulator system and describes what can be done with the VAX NJE emulator software. The second chapter describes the commands that users of the VAX systems will use. Each command description includes the format of the command, a list of valid options and parameters and their meanings, and several short examples of command use. The third chapter describes the commands and capabilities for sending general, sequential files from and to VAX VMS nodes. The fourth chapter describes how to transmit data to a VAXmore » from other computer systems on the network. The fifth chapter explains how to exchange electronic mail with IBM CMS users and with users of other VAX VMS systems connected by NJE communications. The sixth chapter describes operator procedures and the additional commands operators may use.« less

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.

Returning to the Moon: Building the Systems Engineering Base for Successful Science Missions

NASA Astrophysics Data System (ADS)

Eppler, D.; Young, K.; Bleacher, J.; Klaus, K.; Barker, D.; Evans, C.; Tewksbury, B.; Schmitt, H.; Hurtado, J.; Deans, M.; Yingst, A.; Spudis, P.; Bell, E.; Skinner, J.; Cohen, B.; Head, J.

2018-04-01

Enabling science return on future lunar missions will require coordination between the science community, design engineers, and mission operators. Our chapter is based on developing science-based systems engineering and operations requirements.

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

Teacher's Guide to SERAPHIM Software III. Modern Chemistry.

ERIC Educational Resources Information Center

Bogner, Donna J.

Designed to assist chemistry teachers in selecting appropriate software programs, this publication is the third in a series of six teacher's guides from Project SERAPHIM, a program sponsored by the National Science Foundation. This guide is keyed to the chapters of the text "Modern Chemistry." Program suggestions are arranged in the same…

Teacher's Guide to SERAPHIM Software IV Chemistry: A Modern Course.

ERIC Educational Resources Information Center

Bogner, Donna J.

Designed to assist chemistry teachers in selecting appropriate software programs, this publication is the fourth in a series of six teacher's guides from Project SERAPHIM, a program sponsored by the National Science Foundation. This guide is keyed to the chapters of the text "Chemistry: A Modern Course." Program suggestions are arranged…

Teacher's Guide to SERAPHIM Software VI. Chemistry: The Study of Matter.

ERIC Educational Resources Information Center

Bogner, Donna J.

Designed to assist chemistry teachers in selecting appropriate software programs, this publication is the sixth in a series of six teacher's guides from Project SERAPHIM, a program sponsored by the National Science Foundation. This guide is keyed to the chapters of the text "Chemistry: The Study of Matter." Program suggestions are…

Securing PCs and Data in Libraries and Schools: A Handbook with Menuing, Anti-Virus, and Other Protective Software.

ERIC Educational Resources Information Center

Benson, Allen C.

This handbook is designed to help readers identify and eliminate security risks, with sound recommendations and library-tested security software. Chapter 1 "Managing Your Facilities and Assessing Your Risks" addresses fundamental management responsibilities including planning for a secure system, organizing computer-related information, assessing…

Teacher's Guide to SERAPHIM Software V. Chemistry: The Central Science.

ERIC Educational Resources Information Center

Bogner, Donna J.

Designed to assist chemistry teachers in selecting appropriate software programs, this publication is the fifth in a series of six teacher's guides from Project SERAPHIM, a program sponsored by the National Science Foundation. This guide is keyed to the chapters of the text "Chemistry: The Central Science." Program suggestions are…

47 CFR 61.22 - Composition of tariffs.

Code of Federal Regulations, 2010 CFR

2010-10-01

...Perfect 5.1, Microsoft Word 6, or Microsoft Word 97 software. No diskettes shall contain more than one... clearly labelled with the carrier's name, Tariff Number, software used, and the date of submission. When... defined in § 1.4(e)(2) of this chapter. (d) Domestic and international nondominant carriers subject to the...

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…

AstroGrid-D: Grid technology for astronomical science

NASA Astrophysics Data System (ADS)

Enke, Harry; Steinmetz, Matthias; Adorf, Hans-Martin; Beck-Ratzka, Alexander; Breitling, Frank; Brüsemeister, Thomas; Carlson, Arthur; Ensslin, Torsten; Högqvist, Mikael; Nickelt, Iliya; Radke, Thomas; Reinefeld, Alexander; Reiser, Angelika; Scholl, Tobias; Spurzem, Rainer; Steinacker, Jürgen; Voges, Wolfgang; Wambsganß, Joachim; White, Steve

2011-02-01

We present status and results of AstroGrid-D, a joint effort of astrophysicists and computer scientists to employ grid technology for scientific applications. AstroGrid-D provides access to a network of distributed machines with a set of commands as well as software interfaces. It allows simple use of computer and storage facilities and to schedule or monitor compute tasks and data management. It is based on the Globus Toolkit middleware (GT4). Chapter 1 describes the context which led to the demand for advanced software solutions in Astrophysics, and we state the goals of the project. We then present characteristic astrophysical applications that have been implemented on AstroGrid-D in chapter 2. We describe simulations of different complexity, compute-intensive calculations running on multiple sites (Section 2.1), and advanced applications for specific scientific purposes (Section 2.2), such as a connection to robotic telescopes (Section 2.2.3). We can show from these examples how grid execution improves e.g. the scientific workflow. Chapter 3 explains the software tools and services that we adapted or newly developed. Section 3.1 is focused on the administrative aspects of the infrastructure, to manage users and monitor activity. Section 3.2 characterises the central components of our architecture: The AstroGrid-D information service to collect and store metadata, a file management system, the data management system, and a job manager for automatic submission of compute tasks. We summarise the successfully established infrastructure in chapter 4, concluding with our future plans to establish AstroGrid-D as a platform of modern e-Astronomy.

PINS Spectrum Identification Guide

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

A.J. Caffrey

2012-03-01

The Portable Isotopic Neutron Spectroscopy—PINS, for short—system identifies the chemicals inside munitions and containers without opening them, a decided safety advantage if the fill chemical is a hazardous substance like a chemical warfare agent or an explosive. The PINS Spectrum Identification Guide is intended as a reference for technical professionals responsible for the interpretation of PINS gamma-ray spectra. The guide is divided into two parts. The three chapters that constitute Part I cover the science and technology of PINS. Neutron activation analysis is the focus of Chapter 1. Chapter 2 explores PINS hardware, software, and related operational issues. Gamma-ray spectralmore » analysis basics are introduced in Chapter 3. The six chapters of Part II cover the identification of PINS spectra in detail. Like the PINS decision tree logic, these chapters are organized by chemical element: phosphorus-based chemicals, chlorine-based chemicals, etc. These descriptions of hazardous, toxic, and/or explosive chemicals conclude with a chapter on the identification of the inert chemicals, e.g. sand, used to fill practice munitions.« less

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

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

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…

46 CFR 162.018-1 - Applicable specifications, and referenced material.

Code of Federal Regulations, 2012 CFR

2012-10-01

...) The ASME Code may be obtained from the American Society of Mechanical Engineers, United Engineering..., CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Safety Relief Valves, Liquefied... (Procedures Applicable to the Public) and Subpart 50.15 of Subchapter F (Marine Engineering) of this chapter...

46 CFR 162.018-1 - Applicable specifications, and referenced material.

Code of Federal Regulations, 2013 CFR

2013-10-01

...) The ASME Code may be obtained from the American Society of Mechanical Engineers, United Engineering..., CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Safety Relief Valves, Liquefied... (Procedures Applicable to the Public) and Subpart 50.15 of Subchapter F (Marine Engineering) of this chapter...

46 CFR 162.018-1 - Applicable specifications, and referenced material.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) The ASME Code may be obtained from the American Society of Mechanical Engineers, United Engineering..., CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Safety Relief Valves, Liquefied... (Procedures Applicable to the Public) and Subpart 50.15 of Subchapter F (Marine Engineering) of this chapter...

46 CFR 162.018-1 - Applicable specifications, and referenced material.

Code of Federal Regulations, 2014 CFR

2014-10-01

...) The ASME Code may be obtained from the American Society of Mechanical Engineers, United Engineering..., CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Safety Relief Valves, Liquefied... (Procedures Applicable to the Public) and Subpart 50.15 of Subchapter F (Marine Engineering) of this chapter...

46 CFR 162.018-1 - Applicable specifications, and referenced material.

Code of Federal Regulations, 2011 CFR

2011-10-01

...) The ASME Code may be obtained from the American Society of Mechanical Engineers, United Engineering..., CONSTRUCTION, AND MATERIALS: SPECIFICATIONS AND APPROVAL ENGINEERING EQUIPMENT Safety Relief Valves, Liquefied... (Procedures Applicable to the Public) and Subpart 50.15 of Subchapter F (Marine Engineering) of this chapter...

40 CFR 1068.5 - How must manufacturers apply good engineering judgment?

Code of Federal Regulations, 2010 CFR

2010-07-01

... engineering judgment? 1068.5 Section 1068.5 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY... Miscellaneous Provisions § 1068.5 How must manufacturers apply good engineering judgment? (a) You must use good engineering judgment for decisions related to any requirements under this chapter. This includes your...

40 CFR 1068.5 - How must manufacturers apply good engineering judgment?

Code of Federal Regulations, 2011 CFR

2011-07-01

... engineering judgment? 1068.5 Section 1068.5 Protection of Environment ENVIRONMENTAL PROTECTION AGENCY... Miscellaneous Provisions § 1068.5 How must manufacturers apply good engineering judgment? (a) You must use good engineering judgment for decisions related to any requirements under this chapter. This includes your...

46 CFR 71.65-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2010 CFR

2010-10-01

... dioxide, foam, and sprinkling systems. (7) Supervised Patrol Route. (e) Marine engineering. (1) For plans required for marine engineering equipment and systems, see subchapter F (Marine Engineering) of this... equipment and systems, see subchapter J (Electrical Engineering) of this chapter. (2) [Reserved] (g...

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

NASA Technical Reports Server (NTRS)

1983-01-01

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

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

NASA Technical Reports Server (NTRS)

1983-01-01

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

Software engineering standards and practices

NASA Technical Reports Server (NTRS)

Durachka, R. W.

1981-01-01

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

46 CFR 31.35-5 - Communications; alarm systems, telephone and voice tube systems, engine telegraph systems, etc...

Code of Federal Regulations, 2014 CFR

2014-10-01

... OF HOMELAND SECURITY TANK VESSELS INSPECTION AND CERTIFICATION Electrical Engineering § 31.35-5... vessels are subject to the regulations contained in subchapter J (Electrical Engineering) of this chapter...

46 CFR 31.35-5 - Communications; alarm systems, telephone and voice tube systems, engine telegraph systems, etc...

Code of Federal Regulations, 2010 CFR

2010-10-01

... OF HOMELAND SECURITY TANK VESSELS INSPECTION AND CERTIFICATION Electrical Engineering § 31.35-5... vessels are subject to the regulations contained in subchapter J (Electrical Engineering) of this chapter...

46 CFR 31.35-5 - Communications; alarm systems, telephone and voice tube systems, engine telegraph systems, etc...

Code of Federal Regulations, 2011 CFR

2011-10-01

... OF HOMELAND SECURITY TANK VESSELS INSPECTION AND CERTIFICATION Electrical Engineering § 31.35-5... vessels are subject to the regulations contained in subchapter J (Electrical Engineering) of this chapter...

Landslides and engineering geology of the Seattle, Washington, area

USGS Publications Warehouse

Baum, Rex L.; Godt, Jonathan W.; Highland, Lynn M.

2008-01-01

This volume brings together case studies and summary papers describing the application of state-of-the-art engineering geologic methods to landslide hazard analysis for the Seattle, Washington, area. An introductory chapter provides a thorough description of the Quaternary and bedrock geology of Seattle. Nine additional chapters review the history of landslide mapping in Seattle, present case studies of individual landslides, describe the results of spatial assessments of landslide hazard, discuss hydrologic controls on landsliding, and outline an early warning system for rainfall-induced landslides.

The Aerothermodynamics of Aircraft Gas Turbine Engines

DTIC Science & Technology

1978-07-01

engine will deteriorate. 1.6.2 Experimental Testing It is easy to fall int9 the organiza- tional trap of four isolated groups . One group does the... Quasi -Dne-Dimensional Fluid Flows The First Law for a F1mdng System-- The Control Volume • . • The Channel Flow Equations Stagnation Properties...exit to control volume (Eq • 2. 14 . 2) CHAPTER TWO THERMODYNAMICS AND QUASI -ONE-DUlENSIONAL FLUID FLO’’{S 2.0 INTRODUCTION This chapter "ill be

A Generic Evaluation Model for Semantic Web Services

NASA Astrophysics Data System (ADS)

Shafiq, Omair

Semantic Web Services research has gained momentum over the last few Years and by now several realizations exist. They are being used in a number of industrial use-cases. Soon software developers will be expected to use this infrastructure to build their B2B applications requiring dynamic integration. However, there is still a lack of guidelines for the evaluation of tools developed to realize Semantic Web Services and applications built on top of them. In normal software engineering practice such guidelines can already be found for traditional component-based systems. Also some efforts are being made to build performance models for servicebased systems. Drawing on these related efforts in component-oriented and servicebased systems, we identified the need for a generic evaluation model for Semantic Web Services applicable to any realization. The generic evaluation model will help users and customers to orient their systems and solutions towards using Semantic Web Services. In this chapter, we have presented the requirements for the generic evaluation model for Semantic Web Services and further discussed the initial steps that we took to sketch such a model. Finally, we discuss related activities for evaluating semantic technologies.

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

Software-Defined Architectures for Spectrally Efficient Cognitive Networking in Extreme Environments

NASA Astrophysics Data System (ADS)

Sklivanitis, Georgios

The objective of this dissertation is the design, development, and experimental evaluation of novel algorithms and reconfigurable radio architectures for spectrally efficient cognitive networking in terrestrial, airborne, and underwater environments. Next-generation wireless communication architectures and networking protocols that maximize spectrum utilization efficiency in congested/contested or low-spectral availability (extreme) communication environments can enable a rich body of applications with unprecedented societal impact. In recent years, underwater wireless networks have attracted significant attention for military and commercial applications including oceanographic data collection, disaster prevention, tactical surveillance, offshore exploration, and pollution monitoring. Unmanned aerial systems that are autonomously networked and fully mobile can assist humans in extreme or difficult-to-reach environments and provide cost-effective wireless connectivity for devices without infrastructure coverage. Cognitive radio (CR) has emerged as a promising technology to maximize spectral efficiency in dynamically changing communication environments by adaptively reconfiguring radio communication parameters. At the same time, the fast developing technology of software-defined radio (SDR) platforms has enabled hardware realization of cognitive radio algorithms for opportunistic spectrum access. However, existing algorithmic designs and protocols for shared spectrum access do not effectively capture the interdependencies between radio parameters at the physical (PHY), medium-access control (MAC), and network (NET) layers of the network protocol stack. In addition, existing off-the-shelf radio platforms and SDR programmable architectures are far from fulfilling runtime adaptation and reconfiguration across PHY, MAC, and NET layers. Spectrum allocation in cognitive networks with multi-hop communication requirements depends on the location, network traffic load, and interference profile at each network node. As a result, the development and implementation of algorithms and cross-layer reconfigurable radio platforms that can jointly treat space, time, and frequency as a unified resource to be dynamically optimized according to inter- and intra-network interference constraints is of fundamental importance. In the next chapters, we present novel algorithmic and software/hardware implementation developments toward the deployment of spectrally efficient terrestrial, airborne, and underwater wireless networks. In Chapter 1 we review the state-of-art in commercially available SDR platforms, describe their software and hardware capabilities, and classify them based on their ability to enable rapid prototyping and advance experimental research in wireless networks. Chapter 2 discusses system design and implementation details toward real-time evaluation of a software-radio platform for all-spectrum cognitive channelization in the presence of narrowband or wideband primary stations. All-spectrum channelization is achieved by designing maximum signal-to-interference-plus-noise ratio (SINR) waveforms that span the whole continuum of the device-accessible spectrum, while satisfying peak power and interference temperature (IT) constraints for the secondary and primary users, respectively. In Chapter 3, we introduce the concept of all-spectrum channelization based on max-SINR optimized sparse-binary waveforms, we propose optimal and suboptimal waveform design algorithms, and evaluate their SINR and bit-error-rate (BER) performance in an SDR testbed. Chapter 4 considers the problem of channel estimation with minimal pilot signaling in multi-cell multi-user multi-input multi-output (MIMO) systems with very large antenna arrays at the base station, and proposes a least-squares (LS)-type algorithm that iteratively extracts channel and data estimates from a short record of data measurements. Our algorithmic developments toward spectrally-efficient cognitive networking through joint optimization of channel access code-waveforms and routes in a multi-hop network are described in Chapter 5. Algorithmic designs are software optimized on heterogeneous multi-core general-purpose processor (GPP)-based SDR architectures by leveraging a novel software-radio framework that offers self-optimization and real-time adaptation capabilities at the PHY, MAC, and NET layers of the network protocol stack. Our system design approach is experimentally validated under realistic conditions in a large-scale hybrid ground-air testbed deployment. Chapter 6 reviews the state-of-art in software and hardware platforms for underwater wireless networking and proposes a software-defined acoustic modem prototype that enables (i) cognitive reconfiguration of PHY/MAC parameters, and (ii) cross-technology communication adaptation. The proposed modem design is evaluated in terms of effective communication data rate in both water tank and lake testbed setups. In Chapter 7, we present a novel receiver configuration for code-waveform-based multiple-access underwater communications. The proposed receiver is fully reconfigurable and executes (i) all-spectrum cognitive channelization, and (ii) combined synchronization, channel estimation, and demodulation. Experimental evaluation in terms of SINR and BER show that all-spectrum channelization is a powerful proposition for underwater communications. At the same time, the proposed receiver design can significantly enhance bandwidth utilization. Finally, in Chapter 8, we focus on challenging practical issues that arise in underwater acoustic sensor network setups where co-located multi-antenna sensor deployment is not feasible due to power, computation, and hardware limitations, and design, implement, and evaluate an underwater receiver structure that accounts for multiple carrier frequency and timing offsets in virtual (distributed) MIMO underwater systems.

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.

Perceived Noise Analysis for Offset Jets Applied to Commercial Supersonic Aircraft

NASA Technical Reports Server (NTRS)

Huff, Dennis L.; Henderson, Brenda S.; Berton, Jeffrey J.; Seidel, Jonathan A.

2016-01-01

A systems analysis was performed with experimental jet noise data, engine/aircraft performance codes and aircraft noise prediction codes to assess takeoff noise levels and mission range for conceptual supersonic commercial aircraft. A parametric study was done to identify viable engine cycles that meet NASA's N+2 goals for noise and performance. Model scale data from offset jets were used as input to the aircraft noise prediction code to determine the expected sound levels for the lateral certification point where jet noise dominates over all other noise sources. The noise predictions were used to determine the optimal orientation of the offset nozzles to minimize the noise at the lateral microphone location. An alternative takeoff procedure called "programmed lapse rate" was evaluated for noise reduction benefits. Results show there are two types of engines that provide acceptable mission range performance; one is a conventional mixed-flow turbofan and the other is a three-stream variable-cycle engine. Separate flow offset nozzles reduce the noise directed toward the thicker side of the outer flow stream, but have less benefit as the core nozzle pressure ratio is reduced. At the systems level for a three-engine N+2 aircraft with full throttle takeoff, there is a 1.4 EPNdB margin to Chapter 3 noise regulations predicted for the lateral certification point (assuming jet noise dominates). With a 10% reduction in thrust just after clearing the runway, the margin increases to 5.5 EPNdB. Margins to Chapter 4 and Chapter 14 levels will depend on the cumulative split between the three certification points, but it appears that low specific thrust engines with a 10% reduction in thrust (programmed lapse rate) can come close to meeting Chapter 14 noise levels. Further noise reduction is possible with engine oversizing and derated takeoff, but more detailed mission studies are needed to investigate the range impacts as well as the practical limits for safety and takeoff regulations.

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.

14 CFR 25.903 - Engines.

Code of Federal Regulations, 2010 CFR

2010-01-01

... chapter. (2) Each turbine engine must comply with one of the following: (i) Sections 33.76, 33.77 and 33... any engine individually in flight, except that, for turbine engine installations, the means for... might be exposed to fire must be at least fire-resistant. If hydraulic propeller feathering systems are...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

46 CFR 91.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2010 CFR

2010-10-01

... systems. (e) Marine engineering. For plans required for marine engineering equipment and systems, see... electrical engineering, equipment and systems, see subchapter J (Electrical Engineering) of this chapter. (g... bottoms, etc., and including inboard and outboard profile. (b) Hull structure. 1 (1) *Inner Bottom Plating...

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.

Tabular data and graphical images in support of the U.S. Geological Survey National Oil and Gas Assessment -- San Joaquin Basin (5010): Chapter 28 in Petroleum systems and geologic assessment of oil and gas in the San Joaquin Basin Province, California

USGS Publications Warehouse

Klett, T.R.; Le, P.A.

2007-01-01

This chapter describes data used in support of the assessment process. Digital tabular data used in this report and archival data that permit the user to perform further analyses are available elsewhere on this CD–ROM. Computers and software may import the data without transcription from the portable document format (.pdf) files of the text by the reader. Because of the number and variety of platforms and software available, graphical images are provided as .pdf files and tabular data are provided in a raw form as tab-delimited text files (.tab files).

Chapter 2: Tabular Data and Graphical Images in Support of the U.S. Geological Survey National Oil and Gas Assessment - The Wind River Basin Province

USGS Publications Warehouse

Klett, T.R.; Le, P.A.

2007-01-01

This chapter describes data used in support of the process being applied by the U.S. Geological Survey (USGS) National Oil and Gas Assessment (NOGA) project. Digital tabular data used in this report and archival data that permit the user to perform further analyses are available elsewhere on this CD-ROM. Computers and software may import the data without transcription from the Portable Document Format files (.pdf files) of the text by the reader. Graphical images are provided as .pdf files and tabular data are provided in a raw form as tab-delimited text files (.tab files) because of the number and variety of platforms and software available.

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…

Index map of cross sections through parts of the Appalachian basin (Kentucky, New York, Ohio, Pennsylvania, Tennessee, Virginia, West Virginia): Chapter E.1 in Coal and petroleum resources in the Appalachian basin: distribution, geologic framework, and geochemical character

USGS Publications Warehouse

Ryder, Robert T.; Trippi, Michael H.; Ruppert, Leslie F.; Ryder, Robert T.

2014-01-01

The appendixes in chapters E.4.1 and E.4.2 include (1) Log ASCII Standard (LAS) files, which encode gamma-ray, neutron, density, and other logs in text files that can be used by most well-logging software programs; and (2) graphic well-log traces. In the appendix to chapter E.4.1, the well-log traces are accompanied by lithologic descriptions with formation tops.

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.

Software reengineering

NASA Technical Reports Server (NTRS)

Fridge, Ernest M., III

1991-01-01

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

A Recommended Framework for the Network-Centric Acquisition Process

DTIC Science & Technology

2009-09-01

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

Software Engineering Education Directory. Software Engineering Curriculum Project

DTIC Science & Technology

1991-05-01

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

Development of a Conference Planning Model Using Integrated Database, Word Processing, and Spreadsheet Software.

ERIC Educational Resources Information Center

Stevens, William E.

This report presents a model for conducting a statewide conference for the approximately 900 members of the South Carolina Council of Teachers of Mathematics (SCCTM) using the AppleWorks integrated software as the basis of the implementation plan. The first and second chapters provide background information on the conference and the…

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

DTIC Science & Technology

2012-03-13

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

Estimating abundance: Chapter 27

USGS Publications Warehouse

Royle, J. Andrew

2016-01-01

This chapter provides a non-technical overview of ‘closed population capture–recapture’ models, a class of well-established models that are widely applied in ecology, such as removal sampling, covariate models, and distance sampling. These methods are regularly adopted for studies of reptiles, in order to estimate abundance from counts of marked individuals while accounting for imperfect detection. Thus, the chapter describes some classic closed population models for estimating abundance, with considerations for some recent extensions that provide a spatial context for the estimation of abundance, and therefore density. Finally, the chapter suggests some software for use in data analysis, such as the Windows-based program MARK, and provides an example of estimating abundance and density of reptiles using an artificial cover object survey of Slow Worms (Anguis fragilis).

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

ERIC Educational Resources Information Center

Hata, David M.

1986-01-01

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

Software engineering

NASA Technical Reports Server (NTRS)

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

1993-01-01

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

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

Materials for Liquid Propulsion Systems. Chapter 12

NASA Technical Reports Server (NTRS)

Halchak, John A.; Cannon, James L.; Brown, Corey

2016-01-01

Earth to orbit launch vehicles are propelled by rocket engines and motors, both liquid and solid. This chapter will discuss liquid engines. The heart of a launch vehicle is its engine. The remainder of the vehicle (with the notable exceptions of the payload and guidance system) is an aero structure to support the propellant tanks which provide the fuel and oxidizer to feed the engine or engines. The basic principle behind a rocket engine is straightforward. The engine is a means to convert potential thermochemical energy of one or more propellants into exhaust jet kinetic energy. Fuel and oxidizer are burned in a combustion chamber where they create hot gases under high pressure. These hot gases are allowed to expand through a nozzle. The molecules of hot gas are first constricted by the throat of the nozzle (de-Laval nozzle) which forces them to accelerate; then as the nozzle flares outwards, they expand and further accelerate. It is the mass of the combustion gases times their velocity, reacting against the walls of the combustion chamber and nozzle, which produce thrust according to Newton's third law: for every action there is an equal and opposite reaction. Solid rocket motors are cheaper to manufacture and offer good values for their cost. Liquid propellant engines offer higher performance, that is, they deliver greater thrust per unit weight of propellant burned. They also have a considerably higher thrust to weigh ratio. Since liquid rocket engines can be tested several times before flight, they have the capability to be more reliable, and their ability to shut down once started provides an extra margin of safety. Liquid propellant engines also can be designed with restart capability to provide orbital maneuvering capability. In some instances, liquid engines also can be designed to be reusable. On the solid side, hybrid solid motors also have been developed with the capability to stop and restart. Solid motors are covered in detail in chapter 11. Liquid rocket engine operational factors can be described in terms of extremes: temperatures ranging from that of liquid hydrogen (-423 F) to 6000 F hot gases; enormous thermal shock (7000 F/sec); large temperature differentials between contiguous components; reactive propellants; extreme acoustic environments; high rotational speeds for turbo machinery and extreme power densities. These factors place great demands on materials selection and each must be dealt with while maintaining an engine of the lightest possible weight. This chapter will describe the design considerations for the materials used in the various components of liquid rocket engines and provide examples of usage and experiences in each.

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

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.

Secret Key Crypto Implementations

NASA Astrophysics Data System (ADS)

Bertoni, Guido Marco; Melzani, Filippo

This chapter presents the algorithm selected in 2001 as the Advanced Encryption Standard. This algorithm is the base for implementing security and privacy based on symmetric key solutions in almost all new applications. Secret key algorithms are used in combination with modes of operation to provide different security properties. The most used modes of operation are presented in this chapter. Finally an overview of the different techniques of software and hardware implementations is given.

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.

The History of the Internet Search Engine: Navigational Media and the Traffic Commodity

NASA Astrophysics Data System (ADS)

van Couvering, E.

This chapter traces the economic development of the search engine industry over time, beginning with the earliest Web search engines and ending with the domination of the market by Google, Yahoo! and MSN. Specifically, it focuses on the ways in which search engines are similar to and different from traditional media institutions, and how the relations between traditional and Internet media have changed over time. In addition to its historical overview, a core contribution of this chapter is the analysis of the industry using a media value chain based on audiences rather than on content, and the development of traffic as the core unit of exchange. It shows that traditional media companies failed when they attempted to create vertically integrated portals in the late 1990s, based on the idea of controlling Internet content, while search engines succeeded in creating huge "virtually integrated" networks based on control of Internet traffic rather than Internet content.

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.

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.

Chapter 15: Reliability of Wind Turbines

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

Sheng, Shuangwen; O'Connor, Ryan

The global wind industry has witnessed exciting developments in recent years. The future will be even brighter with further reductions in capital and operation and maintenance costs, which can be accomplished with improved turbine reliability, especially when turbines are installed offshore. One opportunity for the industry to improve wind turbine reliability is through the exploration of reliability engineering life data analysis based on readily available data or maintenance records collected at typical wind plants. If adopted and conducted appropriately, these analyses can quickly save operation and maintenance costs in a potentially impactful manner. This chapter discusses wind turbine reliability bymore » highlighting the methodology of reliability engineering life data analysis. It first briefly discusses fundamentals for wind turbine reliability and the current industry status. Then, the reliability engineering method for life analysis, including data collection, model development, and forecasting, is presented in detail and illustrated through two case studies. The chapter concludes with some remarks on potential opportunities to improve wind turbine reliability. An owner and operator's perspective is taken and mechanical components are used to exemplify the potential benefits of reliability engineering analysis to improve wind turbine reliability and availability.« less

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.

A practical primer on geostatistics

USGS Publications Warehouse

Olea, Ricardo A.

2009-01-01

The Challenge—Most geological phenomena are extraordinarily complex in their interrelationships and vast in their geographical extension. Ordinarily, engineers and geoscientists are faced with corporate or scientific requirements to properly prepare geological models with measurements involving a small fraction of the entire area or volume of interest. Exact description of a system such as an oil reservoir is neither feasible nor economically possible. The results are necessarily uncertain. Note that the uncertainty is not an intrinsic property of the systems; it is the result of incomplete knowledge by the observer.The Aim of Geostatistics—The main objective of geostatistics is the characterization of spatial systems that are incompletely known, systems that are common in geology. A key difference from classical statistics is that geostatistics uses the sampling location of every measurement. Unless the measurements show spatial correlation, the application of geostatistics is pointless. Ordinarily the need for additional knowledge goes beyond a few points, which explains the display of results graphically as fishnet plots, block diagrams, and maps.Geostatistical Methods—Geostatistics is a collection of numerical techniques for the characterization of spatial attributes using primarily two tools: probabilistic models, which are used for spatial data in a manner similar to the way in which time-series analysis characterizes temporal data, or pattern recognition techniques. The probabilistic models are used as a way to handle uncertainty in results away from sampling locations, making a radical departure from alternative approaches like inverse distance estimation methods.Differences with Time Series—On dealing with time-series analysis, users frequently concentrate their attention on extrapolations for making forecasts. Although users of geostatistics may be interested in extrapolation, the methods work at their best interpolating. This simple difference has significant methodological implications.Historical Remarks—As a discipline, geostatistics was firmly established in the 1960s by the French engineer Georges Matheron, who was interested in the appraisal of ore reserves in mining. Geostatistics did not develop overnight. Like other disciplines, it has built on previous results, many of which were formulated with different objectives in various fields.Pioneers—Seminal ideas conceptually related to what today we call geostatistics or spatial statistics are found in the work of several pioneers, including: 1940s: A.N. Kolmogorov in turbulent flow and N. Wiener in stochastic processing; 1950s: D. Krige in mining; 1960s: B. Mathern in forestry and L.S. Gandin in meteorologyCalculations—Serious applications of geostatistics require the use of digital computers. Although for most geostatistical techniques rudimentary implementation from scratch is fairly straightforward, coding programs from scratch is recommended only as part of a practice that may help users to gain a better grasp of the formulations.Software—For professional work, the reader should employ software packages that have been thoroughly tested to handle any sampling scheme, that run as efficiently as possible, and that offer graphic capabilities for the analysis and display of results. This primer employs primarily the package Stanford Geomodeling Software (SGeMS) - recently developed at the Energy Resources Engineering Department at Stanford University - as a way to show how to obtain results practically. This applied side of the primer should not be interpreted as the notes being a manual for the use of SGeMS. The main objective of the primer is to help the reader gain an understanding of the fundamental concepts and tools in geostatistics.Organization of the Primer—The chapters of greatest importance are those covering kriging and simulation. All other materials are peripheral and are included for better comprehension of these main geostatistical modeling tools. The choice of kriging versus simulation is often a big puzzle to the uninitiated, let alone the different variants of both of them. Chapters 14, 18, and 19 are intended to shed light on those subjects. The critical aspect of assessing and modeling spatial correlation is covered in chapter 7. Chapters 2 and 3 review relevant concepts in classical statistics.Course Objectives—This course offers stochastic solutions to common problems in the characterization of complex geological systems. At the end of the course, participants should have: an understanding of the theoretical foundations of geostatistics; a good grasp of its possibilities and limitations; and reasonable familiarity with the SGeMS software, thus opening the possibility of practically applying geostatistics.

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.

Undergraduate Women's Participation in Professional Organizations

NASA Astrophysics Data System (ADS)

Hartman, Moshe; Hartman, Harriet

This article focuses on the differences among female undergraduate engineering students who choose to affiliate with student chapters of discipline-specific, mixed-gender professional organizations, the student chapter of the Society of Women Engineers (SWE), or not to affiliate at all. Participants in the different kinds of organizations are compared to nonparticipants to explore how participation is related to professionalization and the development of engineering social capital. Compared with nonparticipants, participants were more involved in extracurricular enrichment and "help" activities; they were more satisfied with most aspects of the engineering program; they had higher grades; they were more self-confident about themselves as engineers, and by the end of the academic year, about their engineering competencies; and they were more strongly committed to a future in engineering. Participation in SWE was associated with greater involvement in study activities, higher satisfaction with the coursework load, and a different perception of the problems women face in the field. Data were taken from a survey of engineering students at Rowan University during the 2000-2001 academic year, which was funded by the National Science Foundation.

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

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

46 CFR 182.430 - Engine exhaust pipe installation.

Code of Federal Regulations, 2012 CFR

2012-10-01

... adequately protected from mechanical damage. (e) Where flexibility is necessary, a section of flexible... meet the material requirements of part 56 of subchapter F (Marine Engineering) of this chapter. (k...

46 CFR 182.430 - Engine exhaust pipe installation.

Code of Federal Regulations, 2013 CFR

2013-10-01

... adequately protected from mechanical damage. (e) Where flexibility is necessary, a section of flexible... meet the material requirements of part 56 of subchapter F (Marine Engineering) of this chapter. (k...

NASA RECON: Course development, administration, and evaluation. A research and development proposal

NASA Technical Reports Server (NTRS)

Dominick, Wayne D. (Editor); Roquemore, Leroy

1984-01-01

This proposal addresses the development, administration, and evaluation of a set of transportable, college-level courses to educate science and engineering students in the effective use of automated scientific and technical information storage and retrieval systems, and, in particular, in the use of the NASA RECON system. Chapter 1 presents a brief introduction. Chapter 2 identifies general and specific objectives, i.e., needs analysis, course development, course administration, and course evaluation. Chapter 3 proposes the methodology to be used in successfully accomplishing these objectives. Chapter 4 highlights expected results and product deliverables, and Chapter 5 presents the project evaluation plan to be followed. Chapter 6 is a brief overview of the institutional resources available at the proposing institutions, i.e., at the University of Southwestern Louisiana and at Southern University to support the project. Chapter 7 proposes a budget, time schedule, and management plan. Chapter 8 is a summary of the foregoing.

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

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

Software Safety Analysis of a Flight Guidance System

NASA Technical Reports Server (NTRS)

Butler, Ricky W. (Technical Monitor); Tribble, Alan C.; Miller, Steven P.; Lempia, David L.

2004-01-01

This document summarizes the safety analysis performed on a Flight Guidance System (FGS) requirements model. In particular, the safety properties desired of the FGS model are identified and the presence of the safety properties in the model is formally verified. Chapter 1 provides an introduction to the entire project, while Chapter 2 gives a brief overview of the problem domain, the nature of accidents, model based development, and the four-variable model. Chapter 3 outlines the approach. Chapter 4 presents the results of the traditional safety analysis techniques and illustrates how the hazardous conditions associated with the system trace into specific safety properties. Chapter 5 presents the results of the formal methods analysis technique model checking that was used to verify the presence of the safety properties in the requirements model. Finally, Chapter 6 summarizes the main conclusions of the study, first and foremost that model checking is a very effective verification technique to use on discrete models with reasonable state spaces. Additional supporting details are provided in the appendices.

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.

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2013 CFR

2013-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2014 CFR

2014-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2012 CFR

2012-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2012 CFR

2012-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2014 CFR

2014-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2011 CFR

2011-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 96.05-1 - Installation and details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communications Systems § 96.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or... be in accordance with the requirements of subchapter J (Electrical Engineering) of this chapter...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2011 CFR

2011-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

46 CFR 77.05-1 - Installation and details.

Code of Federal Regulations, 2013 CFR

2013-10-01

... MISCELLANEOUS SYSTEMS AND EQUIPMENT Electrical Engineering and Interior Communication Systems § 77.05-1 Installation and details. (a) The installation of all systems of an electrical engineering or interior... accordance with the requirements of subchapter J (Electrical Engineering) of this chapter. Systems of this...

Engineering and Software Engineering

NASA Astrophysics Data System (ADS)

Jackson, Michael

The phrase ‘software engineering' has many meanings. One central meaning is the reliable development of dependable computer-based systems, especially those for critical applications. This is not a solved problem. Failures in software development have played a large part in many fatalities and in huge economic losses. While some of these failures may be attributable to programming errors in the narrowest sense—a program's failure to satisfy a given formal specification—there is good reason to think that most of them have other roots. These roots are located in the problem of software engineering rather than in the problem of program correctness. The famous 1968 conference was motivated by the belief that software development should be based on “the types of theoretical foundations and practical disciplines that are traditional in the established branches of engineering.” Yet after forty years of currency the phrase ‘software engineering' still denotes no more than a vague and largely unfulfilled aspiration. Two major causes of this disappointment are immediately clear. First, too many areas of software development are inadequately specialised, and consequently have not developed the repertoires of normal designs that are the indispensable basis of reliable engineering success. Second, the relationship between structural design and formal analytical techniques for software has rarely been one of fruitful synergy: too often it has defined a boundary between competing dogmas, at which mutual distrust and incomprehension deprive both sides of advantages that should be within their grasp. This paper discusses these causes and their effects. Whether the common practice of software development will eventually satisfy the broad aspiration of 1968 is hard to predict; but an understanding of past failure is surely a prerequisite of future success.

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.

NACA Investigation of Fuel Performance in Piston-Type Engines

NASA Technical Reports Server (NTRS)

Barnett, Henry C

1951-01-01

This report is a compilation of many of the pertinent research data acquired by the National Advisory Committee for Aeronautics on fuel performance in piston engines. The original data for this compilation are contained in many separate NACA reports which have in the present report been assembled in logical chapters that summarize the main conclusions of the various investigations. Complete details of each investigation are not included in this summary; however, such details may be found, in the original reports cited at the end of each chapter.

Engineering Design Handbook. Maintainability Engineering Theory and Practice

DTIC Science & Technology

1976-01-01

5—46 5—8.4.1.1 Human Body Measurement ( Anthropometry ) . 5—46 5-8.4.1.2 Man’s Sensory Capability and Psychological Makeup 5-46 5—8.4.1.3...Availability of System With Maintenance Time Ratio 1:4 2-32 2—9 Average and Pointwise Availability 2—34 2—10 Hypothetical...density function ( pdf ) of the normal distribution (Ref. 22, Chapter 10, and Ref. 23, Chapter 1) has the equation where cr is the standard deviation of

Automotive Lubricant Specification and Testing

NASA Astrophysics Data System (ADS)

Fox, M. F.

This chapter concerns commercial lubricant specification and testing, drawing together the many themes of previous chapters. Military lubricant standards were a very strong initial influence during World War II and led to the separate historical development of the North American and European specification systems. The wide range of functions that a successful lubricant must satisfy is discussed, together with issues of balancing special or universal applications, single or multiple engine tests, the philosophy of accelerated testing and the question of 'who sets the standards?' The role of engine tests and testing organisations is examined.

Model-driven Service Engineering with SoaML

NASA Astrophysics Data System (ADS)

Elvesæter, Brian; Carrez, Cyril; Mohagheghi, Parastoo; Berre, Arne-Jørgen; Johnsen, Svein G.; Solberg, Arnor

This chapter presents a model-driven service engineering (MDSE) methodology that uses OMG MDA specifications such as BMM, BPMN and SoaML to identify and specify services within a service-oriented architecture. The methodology takes advantage of business modelling practices and provides a guide to service modelling with SoaML. The presentation is case-driven and illuminated using the telecommunication example. The chapter focuses in particular on the use of the SoaML modelling language as a means for expressing service specifications that are aligned with business models and can be realized in different platform technologies.

Propagation effects handbook for satellite systems design. A summary of propagation impairments on 10 to 100 GHz satellite links with techniques for system design

NASA Technical Reports Server (NTRS)

Ippolito, L. J.; Kaul, R. D.; Wallace, R. G.

1983-01-01

This Propagation Handbook provides satellite system engineers with a concise summary of the major propagation effects experienced on Earth-space paths in the 10 to 100 GHz frequency range. The dominant effect, attenuation due to rain, is dealt with in some detail, in terms of both experimental data from measurements made in the U.S. and Canada, and the mathematical and conceptual models devised to explain the data. In order to make the Handbook readily usable to many engineers, it has been arranged in two parts. Chapters 2-5 comprise the descriptive part. They deal in some detail with rain systems, rain and attenuation models, depolarization and experimental data. Chapters 6 and 7 make up the design part of the Handbook and may be used almost independently of the earlier chapters. In Chapter 6, the design techniques recommended for predicting propagation effects in Earth-space communications systems are presented. Chapter 7 addresses the questions of where in the system design process the effects of propagation should be considered, and what precautions should be taken when applying the propagation results.

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

33 CFR 143.120 - Floating OCS facilities.

Code of Federal Regulations, 2014 CFR

2014-07-01

... (Marine Engineering) and J (Electrical Engineering) of 46 CFR chapter I and 46 CFR part 108 (Design and... that provide an equivalent level of safety may be accepted. These requirements do not apply to...

33 CFR 143.120 - Floating OCS facilities.

Code of Federal Regulations, 2012 CFR

2012-07-01

... (Marine Engineering) and J (Electrical Engineering) of 46 CFR chapter I and 46 CFR part 108 (Design and... that provide an equivalent level of safety may be accepted. These requirements do not apply to...

33 CFR 143.120 - Floating OCS facilities.

Code of Federal Regulations, 2011 CFR

2011-07-01

... (Marine Engineering) and J (Electrical Engineering) of 46 CFR chapter I and 46 CFR part 108 (Design and... that provide an equivalent level of safety may be accepted. These requirements do not apply to...

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.

Chapter 3: Tabular Data and Graphical Images in Support of the U.S. Geological Survey National Oil and Gas Assessment - Western Gulf Province, Smackover-Austin-Eagle Ford Composite Total Petroleum System (504702)

USGS Publications Warehouse

Klett, T.R.; Le, P.A.

2006-01-01

This chapter describes data used in support of the process being applied by the U.S. Geological Survey (USGS) National Oil and Gas Assessment (NOGA) project. Digital tabular data used in this report and archival data that permit the user to perform further analyses are available elsewhere on this CD-ROM. Computers and software may import the data without transcription from the Portable Document Format files (.pdf files) of the text by the reader. Because of the number and variety of platforms and software available, graphical images are provided as .pdf files and tabular data are provided in a raw form as tab-delimited text files (.tab files).

Software Tool Issues

NASA Astrophysics Data System (ADS)

Hennell, Michael

This chapter relies on experience with tool development gained over the last thirty years. It shows that there are a large number of techniques that contribute to any successful project, and that formality is always the key: a modern software test tool is based on a firm mathematical foundation. After a brief introduction, Section 2 recalls and extends the terminology of Chapter 1. Section 3 discusses the the design of different sorts of static and dynamic analysis tools. Nine important issues to be taken into consideration when evaluating such tools are presented in Section 4. Section 5 investigates the interplay between testing and proof. In Section 6, we call for developers to take their own medicine and verify their tools. Finally, we conclude in Section 7 with a summary of our main messages, emphasising the important role of testing.

The Emergence of a Community of Practice in Engineering Education

ERIC Educational Resources Information Center

Kolikant, Yifat Ben-David; McKenna, Ann; Yalvac, Bugrahan

2006-01-01

This chapter describes how engineering faculty and learning scientists developed a collective wisdom--shared language, capabilities, and world view--in order to work together to achieve a common goal of developing course materials in the domain of biomedical engineering. (Contains 1 table and 1 figure.)

46 CFR 96.03-1 - Installation and details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Marine Engineering Systems § 96.03-1 Installation and details. (a) The installation of all systems of a marine engineering nature, together with the details of... (Marine Engineering) of this chapter. Systems of this type include the following: Steering Systems. Bilge...

46 CFR 195.03-1 - Installation and details.

Code of Federal Regulations, 2010 CFR

2010-10-01

... CONTROL AND MISCELLANEOUS SYSTEMS AND EQUIPMENT Marine Engineering Systems § 195.03-1 Installation and details. (a) The installation of all systems of a marine engineering nature, together with the details of... (Marine Engineering) of this chapter. Systems of this type include the following: Steering Systems. Bilge...

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2011 CFR

2011-10-01

...) OCEANOGRAPHIC RESEARCH VESSELS INSPECTION AND CERTIFICATION Plan Approval § 189.55-5 Plans and specifications..., carbon dioxide, foam and sprinkling systems. (e) Marine engineering. For plans required for marine engineering equipment and systems. See Subchapter F (Marine Engineering) of this chapter. (f) Electrical...

46 CFR 189.55-5 - Plans and specifications required for new construction.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) OCEANOGRAPHIC RESEARCH VESSELS INSPECTION AND CERTIFICATION Plan Approval § 189.55-5 Plans and specifications..., carbon dioxide, foam and sprinkling systems. (e) Marine engineering. For plans required for marine engineering equipment and systems. See Subchapter F (Marine Engineering) of this chapter. (f) Electrical...

Self-assembled Nanofibrils for Immunomodulation

NASA Astrophysics Data System (ADS)

Zhao, Fan

This thesis has been mainly focused on applying self-assembled nanofibrils as unique depots for controlled release to modulate immune system, with two major chapters on modulation of innate immunity in chapter 2 and adaptive immunity in chapter 3, respectively. There are 5 chapters in the thesis. Chapter 1 gives a detailed review on the discovery, synthesis and application of self-assembled nanofibrils of therapeutic agents (termed as "self-delivery drugs"), including bioactive molecules; Chapter 2 demonstrates the supramolecular hydrogel of chemotactic peptides as a prolonged inflammation model through proper molecular engineering; Chapter 3 reports a suppressive antibody response achieved by encapsulation of antigens by supramolecular hydrogel of glycopeptide; Chapter 4 illustrates an example of supramolecular hydrogel formation of molecules with extremely low solubility, based on the fact that many small organic drugs have poor solubility. Chapter 5 used beta-galatosidase as a model to study glycosidase-instructed supramolecular hydrogel formation, with potential to target cancer cells due to their distinct metabolic profile.

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.

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…

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

77 FR 16139 - Airworthiness Directives; Pratt & Whitney (PW) Turbofan Engines

Federal Register 2010, 2011, 2012, 2013, 2014

2012-03-20

... Airworthiness Directives; Pratt & Whitney (PW) Turbofan Engines AGENCY: Federal Aviation Administration (FAA... & Whitney (PW) PW2037, PW2037(M), and PW2040 turbofan engines with certain fan blades with a cutback leading..., PW2040, PW2240, PW2337 Turbofan Engine Manual, Part No. 1A6231, Chapter/Section 72-31-12, Repair-14 and...

Digest of Key Science and Engineering Indicators, 2008. NSB-08-2

ERIC Educational Resources Information Center

National Science Foundation, 2008

2008-01-01

This digest of key science and engineering indicators draws primarily from the National Science Board's two-volume "Science and Engineering Indicators, 2008" report. The digest serves two purposes: (1) to draw attention to important trends and data points from across the chapters and volumes of "Science and Engineering Indicators, 2008," and (2)…

Biomedical learning experiences for middle school girls sponsored by the Kansas State University Student Chapter of the IEEE EMBS.

PubMed

Gruber, Lucinda; Griffith, Connor; Young, Ethan; Sullivan, Adriann; Schuler, Jeff; Arnold-Christian, Susan; Warren, Steve

2009-01-01

Learning experiences for middle school girls are an effective means to steer young women toward secondary engineering curricula that they might not have otherwise considered. Sponsorship of such experiences by a collegiate student group is worthwhile, as it gives the group common purpose and places college students in a position to mentor these young women. This paper addresses learning experiences in different areas of bio-medical engineering offered to middle school girls in November 2008 via a day-long workshop entitled "Engineering The Body." The Kansas State University (KSU) Student Chapter of the IEEE Engineering in Medicine and Biology Society (EMBS) worked with the KSU Women in Engineering and Science Program (WESP) to design and sponsor these experiences, which addressed the areas of joint mechanics, electrocardiograms, membrane transport, computer mouse design, and audio filters for cochlear implants. Fifty five middle-school girls participated in this event, affirming the notion that biomedical engineering appeals to young women and that early education and recruitment efforts have the potential to expand the biomedical engineering talent pool.

OHD/HL - Staff

Science.gov Websites

Laboratory Branches Hydrologic Software Engineering Branch (HSEB) Hydrologic Science and Modeling Branch (HSMB) General Info Publications Documentation Software Standard and Guidelines Contact Us HL Staff resources and services. Staff Directory Chief, Hydrology Laboratory; Chief, Hydrologic Software Engineering

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.

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

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

14 CFR 135.421 - Additional maintenance requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... programs, or a program approved by the Administrator, for each aircraft engine, propeller, rotor, and each... instructions set forth by the manufacturer as required by this chapter for the aircraft, aircraft engine, propeller, rotor or item of emergency equipment. (c) For each single engine aircraft to be used in passenger...

14 CFR 135.421 - Additional maintenance requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... programs, or a program approved by the Administrator, for each aircraft engine, propeller, rotor, and each... instructions set forth by the manufacturer as required by this chapter for the aircraft, aircraft engine, propeller, rotor or item of emergency equipment. (c) For each single engine aircraft to be used in passenger...

14 CFR 135.421 - Additional maintenance requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... programs, or a program approved by the Administrator, for each aircraft engine, propeller, rotor, and each... instructions set forth by the manufacturer as required by this chapter for the aircraft, aircraft engine, propeller, rotor or item of emergency equipment. (c) For each single engine aircraft to be used in passenger...

14 CFR 135.421 - Additional maintenance requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... programs, or a program approved by the Administrator, for each aircraft engine, propeller, rotor, and each... instructions set forth by the manufacturer as required by this chapter for the aircraft, aircraft engine, propeller, rotor or item of emergency equipment. (c) For each single engine aircraft to be used in passenger...

14 CFR 135.421 - Additional maintenance requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... programs, or a program approved by the Administrator, for each aircraft engine, propeller, rotor, and each... instructions set forth by the manufacturer as required by this chapter for the aircraft, aircraft engine, propeller, rotor or item of emergency equipment. (c) For each single engine aircraft to be used in passenger...

On the Cost of Engineering Education.

ERIC Educational Resources Information Center

Black, Guy

This study examines how the cost of engineering education changes with the size and characteristics of programs, and tries to establish whether there is some minimum scale at which point engineering education becomes financially viable, and considers the manner in which financial viability is affected by program characteristics. Chapter I presents…

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.

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

5 CFR 304.102 - Definitions.

Code of Federal Regulations, 2013 CFR

2013-01-01

... develop a complex software system, or a plate maker may engrave a novel design. (f) Intemittent employment, as defined in part 340, subpart D, of this chapter, means employment without a regularly scheduled...

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

Solar Electric Propulsion Triple-Satellite-Aided Capture With Mars Flyby

NASA Astrophysics Data System (ADS)

Patrick, Sean

Triple-Satellite-aided-capture sequences use gravity-assists at three of Jupiter's four massive Galilean moons to reduce the DeltaV required to enter into Jupiter orbit. A triple-satellite-aided capture at Callisto, Ganymede, and Io is proposed to capture a SEP spacecraft into Jupiter orbit from an interplanetary Earth-Jupiter trajectory that employs low-thrust maneuvers. The principal advantage of this method is that it combines the ISP efficiency of ion propulsion with nearly impulsive but propellant-free gravity assists. For this thesis, two main chapters are devoted to the exploration of low-thrust triple-flyby capture trajectories. Specifically, the design and optimization of these trajectories are explored heavily. The first chapter explores the design of two solar electric propulsion (SEP), low-thrust trajectories developed using the JPL's MALTO software. The two trajectories combined represent a full Earth to Jupiter capture split into a heliocentric Earth to Jupiter Sphere of Influence (SOI) trajectory and a Joviocentric capture trajectory. The Joviocentric trajectory makes use of gravity assist flybys of Callisto, Ganymede, and Io to capture into Jupiter orbit with a period of 106.3 days. Following this, in chapter two, three more SEP low-thrust trajectories were developed based upon those in chapter one. These trajectories, devised using the high-fidelity Mystic software, also developed by JPL, improve upon the original trajectories developed in chapter one. Here, the developed trajectories are each three separate, full Earth to Jupiter capture orbits. As in chapter one, a Mars gravity assist is used to augment the heliocentric trajectories. Gravity-assist flybys of Callisto, Ganymede, and Io or Europa are used to capture into Jupiter Orbit. With between 89.8 and 137.2-day periods, the orbits developed in chapters one and two are shorter than most Jupiter capture orbits achieved using low-thrust propulsion techniques. Finally, chapter 3 presents an original trajectory design for a Very-Long-Baseline Interferometry (VLBI) satellite constellation. The design was created for the 8th Global Trajectory Optimization Competition (GTOC8) in which participants are tasked with creating and optimizing low-thrust trajectories to place a series of three space craft into formation to map given radio sources.

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…

Perceived Noise Analysis for Offset Jets Applied to Commercial Supersonic Aircraft

NASA Technical Reports Server (NTRS)

Huff, Dennis L.; Henderson, Brenda S.; Berton, Jeffrey J.; Seidel, Jonathan A.

2016-01-01

A systems analysis was performed with experimental jet noise data, engine/aircraft performance codes and aircraft noise prediction codes to assess takeoff noise levels and mission range for conceptual supersonic commercial aircraft. A parametric study was done to identify viable engine cycles that meet NASAs N+2 goals for noise and performance. Model scale data from offset jets was used as input to the aircraft noise prediction code to determine the expected sound levels for the lateral certification point where jet noise dominates over all other noise sources. The noise predictions were used to determine the optimal orientation of the offset nozzles to minimize the noise at the lateral microphone location. An alternative takeoff procedure called programmed lapse rate was evaluated for noise reduction benefits. Results show there are two types of engines that provide acceptable range performance; one is a standard mixed-flow turbofan with a single-stage fan, and the other is a three-stream variable-cycle engine with a multi-stage fan. The engine with a single-stage fan has a lower specific thrust and is 8 to 10 EPNdB quieter for takeoff. Offset nozzles reduce the noise directed toward the thicker side of the outer flow stream, but have less benefit as the core nozzle pressure ratio is reduced and the bypass-to-core area ratio increases. At the systems level for a three-engine N+2 aircraft with full throttle takeoff, there is a 1.4 EPNdB margin to Chapter 3 noise regulations predicted for the lateral certification point (assuming jet noise dominates). With a 10 reduction in thrust just after takeoff rotation, the margin increases to 5.5 EPNdB. Margins to Chapter 4 and Chapter 14 levels will depend on the cumulative split between the three certification points, but it appears that low specific thrust engines with a 10 reduction in thrust (programmed lapse rate) can come close to meeting Chapter 14 noise levels. Further noise reduction is possible with additional reduction in takeoff thrust using programmed lapse rate, but studies are needed to investigate the practical limits for safety and takeoff regulations.

Software Assurance Curriculum Project Volume 1: Master of Software Assurance Reference Curriculum

DTIC Science & Technology

2010-08-01

activity by providing a check on the relevance and currency of the process used to develop the MSwA2010 curriculum content. Figure 2 is an expansion of...random oracle model, symmetric crypto primitives, modes of operations, asymmetric crypto primitives (Chapter 5) [16] Detailed design...encryption, public key encryption, digital signatures, message authentication codes, crypto protocols, cryptanalysis, and further detailed crypto

Quantum chemical parameters in QSAR: what do I use when?

USGS Publications Warehouse

Hickey, James P.; Ostrander, Gary K.

1996-01-01

This chapter provides a brief overview of the numerous quantum chemical parameters that have been/are currently being used in quantitative structure activity relationships (QSAR), along with a representative bibliography. The parameters will be grouped according to their mechanistic interpretations, and representative biological and physical chemical applications will be mentioned. Parmater computation methods and the appropriate software are highlighted, as are sources for software.

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.

Prototype Engineered Barrier System Field Test (PEBSFT); Final report

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

Ramirez, A.L.; Buscheck, T.; Carlson, R.

1991-08-01

This final report represents a summary of data and interpretations obtained from the Prototype Engineered Barrier System Field Test (PEBSFT) performed in G-Tunnel within the Nevada Test Site. The PEBSFT was conducted to evaluate the applicability of measurement techniques, numerical models, and procedures developed for future field tests that will be conducted in the Exploratory Studies Facilities (ESF) at Yucca Mountain. The primary objective of the test was to provide a basis for determining whether tests planned for the ESF have the potential to be successful. Chapter 1 on high frequency electromagnetic tomography discusses the rock mass electromagnetic permittivity andmore » attenuation rate changes that were measured to characterize the water distribution in the near field of a simulated waste container. The data are used to obtain quantitative estimates of how the moisture content in the rock mass changes during heating and to infer properties of the spatial variability of water distribution, leading to conclusions about the role of fractures in the system. Chapter 2 discusses the changes in rock moisture content detected by the neutron logging probe. Chapter 3 permeability tests discusses the characterization of the in-situ permeability of the fractured tuff around the borehole. The air permeability testing apparatus, the testing procedures, and the data analysis are presented. Chapter 4 describes the moisture collection system installed in the heater borehole to trap and measure the moisture volumes. Chapter 5 describes relative humidity measurements made with the thermocouple psychrometer and capacitance sensors. Chapter 6 discusses gas pressure measurements in the G-Tunnel, addressing the calibration and installation of piezoresistive-gaged transducers. Chapter 7 describes the calibration and installation of thermocouples for temperature measurements. Chapter 8 discusses the results of the PEBSFT.« less

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.

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

A Study of the Relationship Between the Practice of Civil Engineering and Student Courses: Volume 1.

ERIC Educational Resources Information Center

Bull, A. J. U.; Richardson, E.

Australian civil engineers were surveyed for a study intended to establish a model for development based on a list of the basic stock of knowledge and techniques that need to be mastered by the graduate civil engineer. Following a brief introduction and summary, chapters 3-7 review the survey objectives, civil engineering definitions and…

46 CFR 167.25-5 - Inspection of boilers, pressure vessels, piping and appurtenances.

Code of Federal Regulations, 2014 CFR

2014-10-01

...) NAUTICAL SCHOOLS PUBLIC NAUTICAL SCHOOL SHIPS Marine Engineering § 167.25-5 Inspection of boilers, pressure... (Marine Engineering) of this chapter, insofar as they relate to tests and inspection of cargo vessels...

46 CFR 167.25-5 - Inspection of boilers, pressure vessels, piping and appurtenances.

Code of Federal Regulations, 2010 CFR

2010-10-01

...) NAUTICAL SCHOOLS PUBLIC NAUTICAL SCHOOL SHIPS Marine Engineering § 167.25-5 Inspection of boilers, pressure... (Marine Engineering) of this chapter, insofar as they relate to tests and inspection of cargo vessels...

In-Plant Technical Assistance for Software

DTIC Science & Technology

1986-09-29

engineer who has had a few programming courses (or send him to a few), and then he will be your software engineer." ( Pressman , 1982.)* Generally, It...1984. Program Office/AFCMD Interface. AFSCR 800-42, November 1982. Pressman , Roger S., Software Engineering. McGraw-Hill, New York, 1982. Dennis...B.M.C., Norton AFB Darrah Whitlock QA Specialist, Plans & Eval. Branch Rockwell-Anaheim AFPRO Lt. Col. Barry Prins HQ/AFCMD Kirtland AFB Stan

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

A compendium of solar dish/Stirling technology

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

Stine, W.B.; Diver, R.B.

1994-01-01

This report surveys the emerging dish/Stirling technology. It documents -- using consistent terminology the design characteristics of dish concentrators, receivers, and Stirling engines applicable to solar electric power generation. Development status and operating experience for each system and an overview of dish/Stirling technology are also presented. This report enables comparisons of concentrator, receiver, and engine technologies. Specifications and performance data are presented on systems and on components that are in use or that could be used in dish/Stirling systems. This report is organized into two parts: The first part (Chapters 1 through 4) provides an overview of dish/Stirling technology --more » the dish/ Stirling components (concentrator, receiver, and engine/alternator), current technology, basic theory, and technology development. The second part (Chapters 5 through 7) provides a detailed survey of the existing dish/Stirling concentrators, receivers, and engine/alternators.« less

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…

Failure Assessment of Brazed Structures

NASA Technical Reports Server (NTRS)

Flom, Yuri

2012-01-01

Despite the great advances in analytical methods available to structural engineers, designers of brazed structures have great difficulties in addressing fundamental questions related to the loadcarrying capabilities of brazed assemblies. In this chapter we will review why such common engineering tools as Finite Element Analysis (FEA) as well as many well-established theories (Tresca, von Mises, Highest Principal Stress, etc) don't work well for the brazed joints. This chapter will show how the classic approach of using interaction equations and the less known Coulomb-Mohr failure criterion can be employed to estimate Margins of Safety (MS) in brazed joints.

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

A supply chain approach to biochar systems [Chapter 2

Treesearch

Nathaniel M. Anderson; Richard D. Bergman; Deborah S. Page-Dumroese

2017-01-01

Biochar systems are designed to meet four related primary objectives: improve soils, manage waste, generate renewable energy, and mitigate climate change. Supply chain models provide a holistic framework for examining biochar systems with an emphasis on product life cycle and end use. Drawing on concepts in supply chain management and engineering, this chapter presents...

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.

Chapter 6. Tabular data and graphical images in support of the U.S. Geological Survey National Oil and Gas Assessment-East Texas basin and Louisiana-Mississippi salt basins provinces, Jurassic Smackover interior salt basins total petroleum system (504902), Travis Peak and Hosston formations.

USGS Publications Warehouse

,

2006-01-01

This chapter describes data used in support of the process being applied by the U.S. Geological Survey (USGS) National Oil and Gas Assessment (NOGA) project. Digital tabular data used in this report and archival data that permit the user to perform further analyses are available elsewhere on the CD-ROM. Computers and software may import the data without transcription from the Portable Document Format files (.pdf files) of the text by the reader. Because of the number and variety of platforms and software available, graphical images are provided as .pdf files and tabular data are provided in a raw form as tab-delimited text files (.tab files).

Chapter 3. Tabular data and graphical images in support of the U.S. Geological Survey National Oil and Gas Assessment--East Texas basin and Louisiana-Mississippi salt basins provinces, Jurassic Smackover Interior salt basins total petroleum system (504902), Cotton Valley group.

USGS Publications Warehouse

Klett, T.R.; Le, P.A.

2006-01-01

This chapter describes data used in support of the process being applied by the U.S. Geological Survey (USGS) National Oil and Gas Assessment (NOGA) project. Digital tabular data used in this report and archival data that permit the user to perform further analyses are available elsewhere on the CD-ROM. Computers and software may import the data without transcription from the Portable Document Format files (.pdf files) of the text by the reader. Because of the number and variety of platforms and software available, graphical images are provided as .pdf files and tabular data are provided in a raw form as tab-delimited text files (.tab files).

Skills Conversion Project: Chapter 10, Ocean Engineering and Oceanography. Final Report.

ERIC Educational Resources Information Center

National Society of Professional Engineers, Washington, DC.

In order to determine the potential utilization of displaced aerospace and defense technical professionals in oceanography and ocean engineering, a study of ocean-oriented industry in Florida and Southern California was conducted by The National Society of Professional Engineers for the U.S. Department of Labor. After recent consolidation, this…

40 CFR 270.18 - Specific part B information requirements for waste piles.

Code of Federal Regulations, 2010 CFR

2010-07-01

... complied with or detailed plans and an engineering report describing how the requirements of § 264.90(b)(2) will be met. (c) Detailed plans and an engineering report describing how the waste pile is designed and...(b) of this chapter, submit detailed plans, and engineering and hydrogeological reports, as...

40 CFR 270.18 - Specific part B information requirements for waste piles.

Code of Federal Regulations, 2011 CFR

2011-07-01

... complied with or detailed plans and an engineering report describing how the requirements of § 264.90(b)(2) will be met. (c) Detailed plans and an engineering report describing how the waste pile is designed and...(b) of this chapter, submit detailed plans, and engineering and hydrogeological reports, as...

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.

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.

Factors that Influence First-Career Choice of Undergraduate Engineers in Software Services Companies: A South Indian Experience

ERIC Educational Resources Information Center

Gokuladas, V. K.

2010-01-01

Purpose: The purpose of this paper is to identify how undergraduate engineering students differ in their perception about software services companies in India based on variables like gender, locations of the college and branches of engineering. Design/methodology/approach: Data obtained from 560 undergraduate engineering students who had the…

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.

Architecture Views Illustrating the Service Automation Aspect of SOA

NASA Astrophysics Data System (ADS)

Gu, Qing; Cuadrado, Félix; Lago, Patricia; Duenãs, Juan C.

Earlier in this book, Chapter 8 provided a detailed analysis of service engineering, including a review of service engineering techniques and methodologies. This chapter is closely related to Chapter 8 as shows how such approaches can be used to develop a service, with particular emphasis on the identification of three views (the automation decision view, degree of service automation view and service automation related data view) that structure and ease elicitation and documentation of stakeholders' concerns. This is carried out through two large case studies to learn the industrial needs in illustrating services deployment and configuration automation. This set of views adds to the more traditional notations like UML, the visual power of attracting the attention of their users to the addressed concerns, and assist them in their work. This is especially crucial in service oriented architecting where service automation is highly demanded.

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.

The Prospects of SAS Interferometry for Detection and Classification (SAS Interferometrie voor Detectie en Classificatie)

DTIC Science & Technology

2008-10-01

DV2008A176 Opdrachtnummer Datum October 2008 Auteur (s) dr. R. van Vossen B.A.J. Quesson dr.ir. J.C. Sabel Rubricering rapport Ongerubriceerd TH9...TNO report | TNO-DV 2008 A176 4/44 Summary This report presents an overview of the theory and implementation of interferometric SAS processing at TNO... theory in software has been tested on two types of data, simulated and measured. Chapter 3 presents results obtained with simulated data; Chapter 4

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…

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.

BOOK REVIEW Handbook of Physics in Medicine and Biology Handbook of Physics in Medicine and Biology

NASA Astrophysics Data System (ADS)

Tabakov, Slavik

2010-11-01

This is a multi-author handbook (66 authors) aiming to describe various applications of physics to medicine and biology, from anatomy and physiology to medical equipment. This unusual reference book has 44 chapters organized in seven sections: 1. Anatomical physics; 2. Physics of perception; 3. Biomechanics; 4. Electrical physics; 5. Diagnostic physics; 6. Physics of accessory medicine; 7. Physics of bioengineering. Each chapter has separate page numbering, which is inconvenient but understandable with the number of authors. Similarly there is some variation in the emphasis of chapters: for some the emphasis is more technical and for others clinical. Each chapter has a separate list of references. The handbook includes hundreds of diagrams, images and tables, making it a useful tool for both medical physicists/engineers and other medical/biology specialists. The first section (about 40 pages) includes five chapters on physics of the cell membrane; protein signaling; cell biology and biophysics of the cell membrane; cellular thermodynamics; action potential transmission and volume conduction. The physics of these is well explained and illustrated with clear diagrams and formulae, so it could be a suitable reference for physicists/engineers. The chapters on cellular thermodynamics and action potential transmission have a very good balance of technical/clinical content. The second section (about 85 pages) includes six chapters on medical decision making; senses; somatic senses: touch and pain; hearing; vision; electroreception. Again these are well illustrated and a suitable reference for physicists/engineers. The chapter on hearing stands out with good balance and treatment of material, but some other chapters contain less physics and are close to typical physiological explanations. One could query the inclusion of the chapter on medical decision making, which also needs more detail. The third section (about 80 pages) includes eight chapters on biomechanics; artificial muscle; cardiovascular system; control of cardiac output and arterial blood pressure regulation; fluid dynamics of the cardiovascular system; fluid dynamics; modeling and simulation of the cardiovascular system to determine work using bond graphs; anatomy and physics of respiration. The diagrams and data in this section could be used as reference material, but some chapters (such as that on the cardiovascular system) again take the form of physiological explanations. The best chapters in this section are on fluid dynamics and modeling. The fourth section (about 30 pages) includes two chapters on electrodes and recording of bioelectrical signals: theory and practice. Both chapters deal with electrodes and are well written and illustrated reference materials. This section could have been larger but the equipment associated with bioelectrical signals (such as ECG and EEG) is described in the next section. The fifth section (about 210 pages) includes 19 chapters on medical sensing and imaging; electrocardiogram: electrical information retrieval and diagnostics from the beating heart; electroencephalography: basic concepts and brain applications; bioelectric impedance analysis; x-ray and computed tomography; confocal microscopy; magnetic resonance imaging; positron emission tomography; in vivo fluorescence imaging and spectroscopy; optical coherence tomography; ultrasonic imaging; near-field imaging; atomic force microscopy; scanning ion conductance microscopy; quantitative thermographic imaging; intracoronary thermography; schlieren imaging: optical techniques to visualize thermal interactions with biological tissues; helium ion microscopy; electron microscopy: SEM/TEM. This is by far the largest section covering various methods and medical equipment and the variation in emphasis/quality is more prominent. The chapters on ECG and EEG are again more physiological with less physics, but the chapter on bioelectric impedance analysis is a good interdisciplinary article. The imaging chapters also vary in style and quality: while those on MRI and ultrasound provide a suitable introduction to the methods, the chapters on x-ray and PET need more detail. However this section includes some methods/equipment rarely featured in medical physics/engineering books (such as OCT or HIM). From this point of view the last eight chapters in the section will be a very useful reference for various specialists. The sixth section (about 30 pages) includes three chapters on lab-on-a-chip; the biophysics of DNA microarrays; nuclear medicine. While the first two could provide an interesting reference, the chapter on nuclear medicine needs much more detail. The last (seventh) section (15 pages) has only one chapter on biophysics of regenerative medicine, which is a good introduction, emphasizing biochemical factors important for improving/replacing tissues or tissue structures. The book ends with an index covering about 1400 terms. The handbook will be useful for the preparation of teaching materials and for undergraduate students, but should be complemented with more detailed/specific reference materials such as the Encyclopedia of Medical Devices and Instrumentation, the Encyclopedia of Medical Physics Emitel, or others. Parts of the handbook would be less suitable for more demanding readers (such as trainee medical physicists or radiologists, for example). In conclusion, the Handbook of Physics in Medicine and Biology includes materials that are rarely combined together, which strengthens its interdisciplinary approach and makes it an additional reference for a departmental library.

31 CFR 536.306 - Information and informational materials.

Code of Federal Regulations, 2010 CFR

2010-07-01

... materials, artworks must be classified under chapter subheading 9701, 9702, or 9703 of the Harmonized Tariff... antiterrorism policies of the United States, including software as defined in 15 CFR part 772 that is not...

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.

Massachusetts Science and Technology Engineering Curriculum Framework

ERIC Educational Resources Information Center

Massachusetts Department of Education, 2006

2006-01-01

This 2006 "Massachusetts Science and Technology/Engineering Curriculum Framework" provides a guide for teachers and curriculum coordinators regarding specific content to be taught from PreK through high school. Following this "Organization" chapter, the "Framework" contains the following sections: (1) Philosophy and…

14 CFR 135.413 - Responsibility for airworthiness.

Code of Federal Regulations, 2011 CFR

2011-01-01

... engines, propellers, rotors, appliances, and parts, and shall have its aircraft maintained under this... maintenance, preventive maintenance, and alteration of its aircraft, including airframe, aircraft engines, propellers, rotors, appliances, emergency equipment and parts, under its manual and this chapter; or (2) Make...

14 CFR 135.413 - Responsibility for airworthiness.

Code of Federal Regulations, 2014 CFR

2014-01-01

... engines, propellers, rotors, appliances, and parts, and shall have its aircraft maintained under this... maintenance, preventive maintenance, and alteration of its aircraft, including airframe, aircraft engines, propellers, rotors, appliances, emergency equipment and parts, under its manual and this chapter; or (2) Make...

14 CFR 135.413 - Responsibility for airworthiness.

Code of Federal Regulations, 2013 CFR

2013-01-01

... engines, propellers, rotors, appliances, and parts, and shall have its aircraft maintained under this... maintenance, preventive maintenance, and alteration of its aircraft, including airframe, aircraft engines, propellers, rotors, appliances, emergency equipment and parts, under its manual and this chapter; or (2) Make...

14 CFR 135.413 - Responsibility for airworthiness.

Code of Federal Regulations, 2010 CFR

2010-01-01

... engines, propellers, rotors, appliances, and parts, and shall have its aircraft maintained under this... maintenance, preventive maintenance, and alteration of its aircraft, including airframe, aircraft engines, propellers, rotors, appliances, emergency equipment and parts, under its manual and this chapter; or (2) Make...

14 CFR 135.413 - Responsibility for airworthiness.

Code of Federal Regulations, 2012 CFR

2012-01-01

... engines, propellers, rotors, appliances, and parts, and shall have its aircraft maintained under this... maintenance, preventive maintenance, and alteration of its aircraft, including airframe, aircraft engines, propellers, rotors, appliances, emergency equipment and parts, under its manual and this chapter; or (2) Make...

14 CFR 91.611 - Authorization for ferry flight with one engine inoperative.

Code of Federal Regulations, 2010 CFR

2010-01-01

... chapter but with— (i) The actual steady gradient of the final takeoff climb requirement not less than 1.2... less than the two-engine inoperative trim speed for the actual steady gradient of the final takeoff...

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.

Alternative Dispute Resolution in the Construction Process: A Course of Study for Construction Managers

DTIC Science & Technology

1988-11-22

focus on ADR education, and provide a sampling of how law and business schools are presenting the topics. The course syllabus is presented in Chapter...course. ADR education has taken hold in many law and business schools , but the topic has yet to gain the attention of engineering educators. This chapter

NASA Engineering Design Challenges: Environmental Control and Life Support Systems. Water Filtration Challenge. EG-2008-09-134-MSFC

ERIC Educational Resources Information Center

Schneider, Twila, Ed.

2010-01-01

This educator guide is organized into seven chapters: (1) Overview; (2) The Design Challenge; (3) Connections to National Curriculum Standards; (4) Preparing to Teach; (5) Classroom Sessions; (6) Opportunities for Extension; and (7) Teacher Resources. Chapter 1 provides information about Environmental Control and Life Support Systems used on NASA…

The Grantwriter's Internet Companion: A Resource for Educators and Others Seeking Grants and Funding.

ERIC Educational Resources Information Center

Peterson, Susan

This book offers a review of Web sites useful to educational grant writers. Chapter 1, "The Internet Advantage," examines the benefits that the Internet offers grant writers. These benefits include greater accessibility and savings in cost and time. Chapter 2, "Learning To Look: The World of Search Engines," examines strategies for effective use…

Chapter II 1985-86 End-of-Year Report. OEA Evaluation Report.

ERIC Educational Resources Information Center

New York City Board of Education, Brooklyn. Office of Educational Assessment.

During the 1985-86 school year the following three New York City high schools received federal funds under Chapter II, Subchapter C, for the development of special programs in the following subjects: (1) A. Philip Randolph--engineering; (2) Townsend Harris--the humanities; and (3) The Paul Robeson School--business and technology. Each of these…

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.