1,801 research outputs found
Exploring Documentation: A Trivial Dimension of RUP
The Unified Process (UP) methodology is a commonly used methodology which can be followed by that entire process model where perfectly documented and well defined structure of team is needed, like Rational Unified Process (RUP) model which follows the UP methodology. During documentation, the defect rate of software can be reduced and software quality can be improved. Quality is the sole objective which is pursued by stakeholders throughout the whole life cycle of software development. Quality is not the outcome of an accident; it is the fruit of the continual labor of devoted professionals. As the size of software increases, it is natural for the number of errors and defects to increase. The Cleanroom Software engineering process is a process for software development. The basic objective of Cleanroom Software engineering is to produce high quality of software emphasizing to increase the level of reliability to its utmost efficiency. Moreover, the Cleanroom process is involved in each and every phase of software development life cycle i.e. planning; measurement; specifying design; verifying code; testing; and certifying to mold the entire engineering discipline that the end product should result ideally in zero defect-rate. Keywords: Cleanroom software Engineering process, Documentation, Defect rate, Rational Unified process, quality and reliability
An Analysis of Early Software Reliability Improvement Techniques
This research explores early life cycle software reliability prediction models or techniques to predict the reliability of software prior to writing code, and a method for increasing or improving the reliability of software products early in the development life cycle. Five prediction models and two development techniques are examined. Each model is statically analyzed in terms of availability of data early in the life cycle, ease of data collection, and whether data is currently collected. One model and the two techniques satisfied those requirements and are further analyzed for their ability to predict or improve software reliability. While the researchers offer no significant statistical results of the model\u27s ability to predict software reliability, important conclusions are drawn about the cost and time savings of using inspections as a means of improving software reliability. The results indicate that the current software development paradigm needs to be changed to use the Cleanroom Software Development Process for fixture software development. This proactive approach to developing reliable software saves development and testing costs. One obvious benefit of this research is that cost savings realized earlier in the software development cycle have a dramatic effect on making software development practices better and more efficient
Foundations of Empirical Software Engineering: The Legacy of Victor R. Basili
This book captures the main scientific contributions of Victor R. Basili, who has significantly shaped the field of empirical software engineering from its very start. He was the first to claim that software engineering needed to follow the model of other physical sciences and develop an experimental paradigm. By working on this postulate, he developed concepts that today are well known and widely used, including the Goal-Question-Metric method, the Quality-Improvement paradigm, and the Experience Factory. He is one of the few software pioneers who can aver that their research results are not just scientifically acclaimed but are also used as industry standards. On the occasion of his 65th birthday, celebrated with a symposium in his honor at the International Conference on Software Engineering in St. Louis, MO, USA in May 2005, Barry Boehm, Hans Dieter Rombach, and Marvin V. Zelkowitz, each a long-time collaborator of Victor R. Basili, selected the 20 most important research papers of their friend, and arranged these according to subject field. They then invited renowned researchers to write topical introductions. The result is this commented collection of timeless cornerstones of software engineering, hitherto available only in scattered publications
Box-Structured Requirement Determination Methods
Requirements determination is an iterative process of eliciting, gathering, modeling, specifying, and analyzing system requirements information. It is the most critical, yet least understood, phase of systems development. This paper presents a rigorous approach for performing requirements determination with box-structured methods. By capturing requirements information in black box transactions and transaction hierarchies, intellectual control is maintained over large amounts of requirements information. The results of the box-structured requirements determination methods provide the basis for formal system design techniques. A concise example of box-structured requirements determination is included in an appendix
Cost-benefit analysis for software process improvement
Justification of investments to improve software development processes and technol- ogy continues to be a significant challenge for software management. Managers interested in improving quality, cost, and cycle-time of their products have a large set of methods, tools, and techniques from which to choose. The implementation of one or more of these potential improvements can require considerable time and cost. Decision makers must be able to understand the benefits from each proposed improvement and decide which improvements to implement. While a variety of approaches exist for evaluating the costs and benefits of a few specific improvements such as inspections or systematic reuse, there is no general model for evaluating software process improvements.
The result of this research is a practical, useful framework to assist practitioners in evaluating potential process improvements. This general framework can accommodate a variety of methods for estimating the cost-benefit effects of a process change. To illustrate this framework a set of cost-benefit templates for Emerald and Cleanroom technologies were developed and validated. Methods for evaluating effects range from constants and simple equations to bayesian decision models and dynamic process simulations. A prototype tool was developed to assist in performing cost-benefit analysis of software process improvements
- …