Systems engineering training and consulting for project success ...
This recommended practice provides individuals and organisations a process for the evaluation and selection of computer-aided software engineering (CASE) tools. The recommended practice addresses the evaluation and selection of tools supporting software engineering processes including project management processes, development processes and integral processes.
IEEE Std 1074. This standard defines the set of activities that constitute the processes that are mandatory for the development and maintenance of software. The management and support processes that continue throughout the entire life cycle, as well as all aspects of the software life cycle from concept exploration through retirement, are covered. Associated input and output information is also provided. Utilisation of the processes and their component activities maximises the benefits to the user when the use of this standard is initiated early in the software life cycle. This standard requires definition of a user’s software life cycle and shows its mapping into typical software life cycles. It is not intended to define or imply a software life cycle of its own.
IEEE Std 1045. This standard defines a framework for measuring and reporting productivity of the software process. It focuses on definitions of how to measure software process productivity and what to report when giving productivity results. It is meant for those who want to measure the productivity of the software process for creating code and documentation products.
FROM 2010 THIS JOURNAL WILL BE INCORPORATED IN: JOURNAL OF SOFTWARE MAINTENANCE AND EVOLUTION: RESEARCH AND PRACTICE.
Related documents (backlinks)
This is a concise, straight forward, and clear discussion of the value of using process. Examples of cutting time-to-market and reducing costs and defects by factors of 3 to 10 are provided from actual organizations. The author challenges the view that process is rigid, restrictive, and inefficient. This article is valuable reading for managers of systems and software projects.
This is a practical handbook for software construction. McConnell's focus in this book was to advance the common practice of software development to leading edge. He provides research and programming experience to facilitate development of high-quality software. The author provides a chapter on "Where to Go for More Information," with descriptions of some of the industry's best books, articles, and organizations. Recommended reading for any software developer. Although the book pre-dates the web and client-server technology, most developers I know continue to value the practical and useful advice provided here.