How to manage quality up, and risk down. This invaluable guide to project planning and strategic decision making for software developers presents practical and realistic planning techniques to increase chances of a project delivering to time and budget. Offering clear explanations and real-world experiences, the key components of technical management are laid out as templates and checklists to assist managers with their project development. With thirty years of experience in software development, Martyn Ould provides:<br> <br> * Proven strategies for a disciplined approach to project planning<br> <br> * Steps to take in risks and uncertainties in the project<br> <br> * Reliable methods for reducing risks to an acceptable level<br> <br> * A quality planning process that is rooted in the technical requirements of the system<br> <br> * Insight into monitoring and measuring project progress<br> <br> * Real-world experience through case studies and examples
I N T R O D U C T I O N How to Write Software Quality Management Plans is a plain-english, simplified version of IEEE 730 Standard for Software Quality Assurance Plans. This how to guide specifies the format and contents of a quality plan. It identifies the practices and processes to be applied during a project to ensure that the deliverables conform to the agreed requirements. It also identifies the quality objectives of the project, which are statements about measurable aspects of project and quality management. The quality plan includes the: - scope and objectives of the quality aspects of the project - quality deliverables that the project will produce - process by which those deliverables are produced - organisation and staffing which will perform the quality functions - responsibilities of those involved S C O P E How to Write Software Quality Management Plans applies to the medium to large scale software development projects. O B J E C T I V E S How to Write Software Quality Management Plans provides project and quality managers with a guide for the development of the quality plan. It addresses: - quality related aspects of the project to be considered during the planning stage of the project - the project's quality objectives, quality deliverables and how they are to be managed - the need for consistent content and format Contribution to IS Quality. As with the Project Plan, the literature of software quality recognises the importance of comprehensive planning for those aspects of a software development project that bear most closely upon its success. Given that up to 70% of IT development projects fail (in terms of either not being completed, or completed but not used by the client due to it unsuitability), due in part to inadequate planning and execution of the project, this how to guide is an valuable aid for project planners to address the important quality-related activities. It is is an easy to use checklist, as defined by IEEE 730, and template to achieve this end. In the same way as a systematic and comprehensive Statement of User Requirements can capture a more complete set of requirements, a project plan as provided by this how to guide allows the project manager to make sure he/she has considered all relevant quality matters in the planning stage, allowing them to avoid, as far as possible, unpleasant surprizes later.
<b>Praise from the Reviewers:</b> <p> "The practicality of the subject in a real-world situation distinguishes this book from others available on the market."<br> —<b>Professor Behrouz Far</b>, University of Calgary <p> "This book could replace the computer organization texts now in use that every CS and CpE student must take. . . . It is much needed, well written, and thoughtful."<br> —<b>Professor Larry Bernstein</b>, Stevens Institute of Technology <p> <b>A distinctive, educational text onsoftware performance and scalability</b> <p> This is the first book to take a quantitative approach to the subject of software performance and scalability. It brings together three unique perspectives to demonstrate how your products can be optimized and tuned for the best possible performance and scalability: <ul> <li> <div><b>The Basics</b>—introduces the computer hardware and software architectures that predetermine the performance and scalability of a software product as well as the principles of measuring the performance and scalability of a software product</div> <li> <div><b>Queuing Theory</b>—helps you learn the performance laws and queuing models for interpreting the underlying physics behind software performance and scalability, supplemented with ready-to-apply techniques for improving the performance and scalability of a software system</div> <li> <div><b>API Profiling</b>—shows you how to design more efficient algorithms and achieve optimized performance and scalability, aided by adopting an API profiling framework (perfBasic) built on the concept of a performance map for drilling down performance root causes at the API level</div> </ul> <p> <i>Software Performance and Scalability</i> gives you a specialized skill set that will enable you to design and build performance into your products with immediate, measurable improvements. Complemented with real-world case studies, it is an indispensable resource for software developers, quality and performance assurance engineers, architects, and managers. It is anideal text for university courses related to computer and software performance evaluation and can also be used to supplement a course in computer organization or in queuing theory for upper-division and graduate computer science students. <p>
Website Developers Articles
Website Developers Books