Volume 1 (of 2) of the Software Development Project How To Guide: Project document templates library is a practical, no-nonsense, cost-effective way to improve the conduct of software development projects. The book is written by an experienced Software Engineer who moved from the world of projects to academia, completing a PhD in software process in 2009. Earlier editions of this book have been successfully used since the 1990's by software development project managers and staff around the world. It has also been used by Universities in Australia to support their IT degrees. This book is essentially a toolkit that project managers and development organisations generally can use to good effect on projects. It can also serve as the basis for defining their own processes, their own software quality management system. Volume 1 has the following parts: A. SOFTWARE PROJECT PLAN B. SOFTWARE QUALITY PLAN C. CONFIGURATION MANAGEMENT PLAN D. REQUIREMENTS LIST E. STATEMENT OF USER REQUIREMENTS F. SOFTWARE REQUIREMENTS SPECIFICATION G. SOFTWARE DESIGN DESCRIPTIONS H. SOFTWARE QUALITY METRICS I. SOFTWARE TEST PLAN J. SOFTWARE REVIEWS & AUDITS K. SOFTWARE USER DOCUMENTATION A Proven Approach. The approach the author suggests when establishing software quality management systems is to first take the time to understand the organisation's established ways of undertaking projects, then 'graft' onto these existing processes appropriate material from this book. Not more bureaucracy, please This approach recognises that any new quality management system that simply places a new layer of bureaucracy onto an already over-burdened staff is doomed to failure because staff will resist it. Both Sound and User-friendly. When that system is based on sound software engineering principles, as outlined by the IEEE software engineering standards, the system becomes both sound and user-friendly. Profitability through Higher Capability. Development organisation's that have defined their processes and who can demonstrate that they follow these processes will likely rate at level 3 or higher on both the CMMI (TM) and ISO 15504 SPICE. Achieving level 3 or higher can place development organisations more competitively in the tendering process, as well as making the organisation more profitable by reducing the time-to-market and re-work through increased efficiency. This book is supported by a (free) library of forms available for download. Volume 2 (available separately) has the following parts: A. PROJECT INITIATION B. REQUEST TO QUOTE PROCEDURE C. PROJECT ESTIMATING D. DOCUMENT PRODUCTION E. SUPPORT DOCUMENTATION PRODUCTION F. TERMS OF REFERENC G. SOFTWARE PROJECT AGREEMENTS H. PROCUREMENT & HANDLING CLIENT SUPPLIED MATERIALS I. VERSION CONTROL OF DELIVERABLES J. PROJECT DOCUMENT FILING K. PROJECT STATUS REPORTING L. RISK MANAGEMENT M. CHANGE CONTROL N. ISSUES MANAGEMENT O. CONTROL OF DEVELOPMENT ENVIRONMENT P. PROGRESS CONTROL Q. CLIENT FEEDBACK R. PROJECT END REPORT The free Forms library contain the following: FM-01Change request form FM-02Issue notification FM-03Change log FM-04Issue log FM-05Error log FM-06Quality control log FM-07Error notification FM-08Training course assessment FM-09Training gap analysis FM-10Project risk analysis - detailed FM-11Impact analysis FM-12Consultancy feedback FM-13Consultancy log FM-14Role skill matrix FM-15Project risk analysis - summary FM-16Team weekly report FM-17Team member weekly report FM-18Quality control record FM-19Internal Audit Notification FM-20Standards FM-21Pre-Project Initiation Checklist FM-22Lunchtime Seminar Assessment Form FM-23Workshop Evaluation Form FM-24Lunch Time Seminar Schedule FM-25Stage End Customer Stakeholder Feedback Form FM-26Section Customer Feedback Register FM-27Section Customer Complaints Register FM-28Configuration Register