A quality management based on the Quality Model life cycle

Managing quality is a hard and expensive task that involves the execution and control of processes and techniques. For a good quality management, it is important to know the current state and the objective to be achieved. It is essential to take into account with a Quality Model that specifies the purposes of managing quality. QuEF (Quality Evaluation Framework) is a framework to manage quality in MDWE (Model-driven Web Engineering). This paper suggests managing quality but pointing out the Quality Model life cycle. The purpose is to converge toward a quality continuous improvement by means of reducing effort and time.Ministerio de Ciencia e Innovación TIN2010-20057-C03-02Ministerio de Ciencia e Innovación TIN 2010-12312-EJunta de Andalucía TIC-578

Managers Handbook for Software Development

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

New approaches to the measurement of chlorophyll, related pigments and productivity in the sea

In the 1984 SBIR Call for Proposals, NASA solicited new methods to measure primary production and chlorophyll in the ocean. Biospherical Instruments Inc. responded to this call with a proposal first to study a variety of approaches to this problem. A second phase of research was then funded to pursue instrumentation to measure the sunlight stimulated naturally occurring fluorescence of chlorophyll in marine phytoplankton. The monitoring of global productivity, global fisheries resources, application of above surface-to-underwater optical communications systems, submarine detection applications, correlation, and calibration of remote sensing systems are but some of the reasons for developing inexpensive sensors to measure chlorophyll and productivity. Normally, productivity measurements are manpower and cost intensive and, with the exception of a very few expensive multiship research experiments, provide no contemporaneous data. We feel that the patented, simple sensors that we have designed will provide a cost effective method for large scale, synoptic, optical measurements in the ocean. This document is the final project report for a NASA sponsored SBIR Phase 2 effort to develop new methods for the measurements of primary production in the ocean. This project has been successfully completed, a U.S. patent was issued covering the methodology and sensors, and the first production run of instrumentation developed under this contract has sold out and been delivered

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

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

Advanced Artificial Intelligence Technology Testbed

The Advanced Artificial Intelligence Technology Testbed (AAITT) is a laboratory testbed for the design, analysis, integration, evaluation, and exercising of large-scale, complex, software systems, composed of both knowledge-based and conventional components. The AAITT assists its users in the following ways: configuring various problem-solving application suites; observing and measuring the behavior of these applications and the interactions between their constituent modules; gathering and analyzing statistics about the occurrence of key events; and flexibly and quickly altering the interaction of modules within the applications for further study

Biometric E-Commerce: Security in B2C (Business-to-Consumer)

Every e-commerce transaction done online seemed to be a secure transaction. However, many users do not realize the fraud that happens while doing transactions. Of course, there are ways to curd this rising problem. The objective of this project is to study the feasibility and the security of e-commerce by implementing fingerprint biometric during transaction. The key point is to create a safe and secure environment for users to do transactions on the Internet without the need to worry about fraud. The methodology used will be Retotype, a combination of research and prototype. A Retotype will be modeled to capture the most efficient and secure e-commerce transaction method. The final product would be a prototype of an e-commerce website incorporated with fingerprint biometric as an authentication method. An implementation strategy would be analyzed to weigh how practical can this system work in the real world. I

Recommended approach to sofware development

A set of guideline for an organized, disciplined approach to software development, based on data collected and studied for 46 flight dynamics software development projects. Methods and practices for each phase of a software development life cycle that starts with requirements analysis and ends with acceptance testing are described; maintenance and operation is not addressed. For each defined life cycle phase, guidelines for the development process and its management, and the products produced and their reviews are presented

Sixth Annual Users' Conference

Conference papers and presentation outlines which address the use of the Transportable Applications Executive (TAE) and its various applications programs are compiled. Emphasis is given to the design of the user interface and image processing workstation in general. Alternate ports of TAE and TAE subsystems are also covered

The cleanroom case study in the Software Engineering Laboratory: Project description and early analysis

This case study analyzes the application of the cleanroom software development methodology to the development of production software at the NASA/Goddard Space Flight Center. The cleanroom methodology emphasizes human discipline in program verification to produce reliable software products that are right the first time. Preliminary analysis of the cleanroom case study shows that the method can be applied successfully in the FDD environment and may increase staff productivity and product quality. Compared to typical Software Engineering Laboratory (SEL) activities, there is evidence of lower failure rates, a more complete and consistent set of inline code documentation, a different distribution of phase effort activity, and a different growth profile in terms of lines of code developed. The major goals of the study were to: (1) assess the process used in the SEL cleanroom model with respect to team structure, team activities, and effort distribution; (2) analyze the products of the SEL cleanroom model and determine the impact on measures of interest, including reliability, productivity, overall life-cycle cost, and software quality; and (3) analyze the residual products in the application of the SEL cleanroom model, such as fault distribution, error characteristics, system growth, and computer usage

Feasibility study of an Integrated Program for Aerospace vehicle Design (IPAD). Volume 1B: Concise review

Reports on the design process, support of the design process, IPAD System design catalog of IPAD technical program elements, IPAD System development and operation, and IPAD benefits and impact are concisely reviewed. The approach used to define the design is described. Major activities performed during the product development cycle are identified. The computer system requirements necessary to support the design process are given as computational requirements of the host system, technical program elements and system features. The IPAD computer system design is presented as concepts, a functional description and an organizational diagram of its major components. The cost and schedules and a three phase plan for IPAD implementation are presented. The benefits and impact of IPAD technology are discussed