Software Quality Engineering Research Articles

Critères et mesures de performance d'un progiciel d'éléments finis—Propositions

ABSTRACT The software market is now increasingly subject to budget restrictions and quality imperatives. Customers justify their choice by technical performances and economical criteria (price and profitability). Faced with financial constraint, it must be repeated that there is a fundamental need of good softwares which would be able to modelize civil engineering structures and a need of qualified users. This paper follows the qualified user's point of view and presents performance criteria which allow to characterize a software and quantify its quality. These performances are linked to the development of software (Quality Insurance and software engineering tools), to the software validation, its current use and its interoperability with other sofwares.

Software Quality Engineering

Software Quality Engineering

Negotiated learning contracts in team projects

The successful evolution of a negotiated learning practice in software engineering team projects is described. The background to negotiated learning practices is reviewed and it is noted that a concern for process issues might be related to software quality management concerns. Negotiated learning was used to develop learning autonomy and to encourage process improvement. The integration of learning contracts and existing software engineering quality management techniques has produced an approach which has enabled teams of students to effectively define and reflect on systems development and learning processes. Individual assessment was enhanced by including processes for the visibility and traceability of contributions in the negotiation process. The gradual evolution of the practice is described with some detail of the current context provided. Evaluations have indicated that teams can become more actively engaged in learning and develop reflective skills in a structured manner by exploiting mechanisms for negotiation.

Requirements traceability: Theory and practice

Current literature as well as standards that mandate requirements traceability do not provide a comprehensive model of what information should be captured and used as a part of a traceability scheme, leading to wide variation in the quality and usefulness of traceability practice across systems development efforts. In this paper, we present a framework for representing and developing a traceability scheme. The experiences of an organization using traceability as an important component of a quality software engineering process are discussed. Models describing the traceability practice in the organization, as well as issues and lessons learned, both from organizational and technical perspectives, from implementing a comprehensive traceability practice are presented.

Metrics and Models in Software Quality Engineering

Metrics and Models in Software Quality Engineering

Quality and knowledge in software engineering

Celite corporation and Andersen Consulting have developed an advanced approach to traditional software development called the application software factory (ASF). The approach is an integration of technology and total quality management techniques that includes the use of an expert system to guide design and perform module programming. The expert system component is called the knowledge-based design assistant and its inclusion in the ASF methodology has significantly reduced development time, training time, and and communication errors.

Message from Academia to Industry－Striving to Establish Software Quality Engineering

Message from Academia to Industry－Striving to Establish Software Quality Engineering

Parallels between Object-Oriented Software Development and Total Quality Management

The object-oriented (OO) approach to building information systems, if applied correctly, can greatly enhance the quality of the finished software product. This emphasis on greater quality is paralleled by the management philosophy known as Total Quality Management (TQM). Based on the common theme of ‘quality’, parallels are drawn between the OO and TQM philosophies in order to optimize on the benefits to quality software engineering offered by the object-oriented approach.

Parallels between object-oriented software development and total quality management

The object-oriented (OO) approach to building information systems, if applied correctly, can greatly enhance the quality of the finished software product. This emphasis on greater quality is paralleled by the management philosophy known as Total Quality Management (TQM). Based on the common theme of ‘quality’, parallels are drawn between the OO and TQM philosophies in order to optimize on the benefits to quality software engineering offered by the object-oriented approach.

Software Quality Engineering: A Total Technical and Management Approach

"Software Quality Engineering: A Total Technical and Management Approach." Journal of the Operational Research Society, 41(3), p. 268

Software Quality Engineering: A Total Technical and Management Approach

Software Quality Engineering: A Total Technical and Management Approach

Software quality engineering

An integrated approach to software quality, reliability, and safety is described that is termed ‘software quality engineering’. It encompasses the three levels of quality assurance technology generally recognised in manufacturing, namely, product inspection, process control, and design improvement. Most software organizations today operate at the product-inspection level of technology (or lower). Achieving higher levels of quality assurance technology depends on establishing effective measurement, control, and process improvement mechanisms within the software enterprise.

Introducing Software Quality Engineering into a Telecommunications Development Environment

This paper summarizes the author's experience in introducing software quality engineering methodology into a telecomm system design organization. The discussion covers: how software quality was marketed and managed as a profit maker and time saver, the multiphase introduction timetable for diverse quality concepts, criteria for hiring and training staff, and the operating guidelines for the Quality Group. In less than two years, a quality-oriented development culture has been established. Substantially shorter development times, and lower design costs per line of code are being routinely attained while guaranteeing a high level of operational reliability at product introduction.

Module size: A standard or heuristic?

Current and proposed national software development specifications include module size limits in the form of an upper bound per module and an average for a group of modules. This paper claims that commonly specified limits such as 200 executable source statements have little practical value for programmers, and that the limits have not been validated. Module size guidelines based on corresponding complexity are derived for identifying extremly long modules, and are recommended for use by software quality engineers in monitoring development methodologies and by test engineers during preacceptance testing. Finally, research to derive a lower bound guideline for module size is recommended.

Necessary Skills For A Software Quality Engineer

The demand for quality in software engineering raises new challenges for software engineers. The solutions proposed for the quality problem are based on standards which provide an abstract frame and drive further tailoring and installation of quality control principles. These principles encompass a rational design process supported by design rationales and defect prevention & immediate defect removal techniques. The present paper discusses some new topics such as design rationale, CSCW, TQM and CASE, which a software engineer should master and applies these to a new type of review a collaborative review.

The Impact Of Clinical Testers On SoftwareQuality Engineering

This paper will focus on the addition of clinical personnel to the software quality process and its impact on final test validation of medical products. As medical designs have become more software based, issues of building quality and maintainability into products have increased and early clinical input has become critical especially since the competitive global nature of doing business has made time to market another key issue.