Cross-functional communication. Pg.___
Response to problems. Pg.___
Code quality. Pg.___
Structural integrity. Pg.___
Attitude—teamwork/team development and key core competencies. Pg.___
Reviews—how to measure incremental success; tips and traps associated with the review process. Pg.___
Design Specs—key issues surrounding this difficult document. Pg.___
OOP Best Practices—the increased need for methodology in object-oriented analysis, design and implementation. Pg.___
Prototypes, Specs and Reviews—best practices for the development of gui and non-gui software applications. Pg.___
Assertions in source code—how to increase testability and reliability using assertions in source code. Pg.___
Acceptance Testing—a success metric to ensure that what is delivered meets the customer acceptance criteria.
Checklist for Best Practices—summary of key methods, tools and processes for successful software engineering and product development. Pg.___
In one neat package, this book brings together information on every aspect of developing quality software.KEY TOPICS:Introduces a phased approach for delivering software quality. Presents the role of reviews and design specifications in optimizing quality. Discusses best quality practices for object-oriented development. Discusses prototypes and acceptance testing. Includes a detailed checklist of best practices.MARKET:For software engineers, software project managers, designers, and technical software marketing managers.
1. Attitude Makes the Difference.
2. The Phased Approach.
3. Code and Design Reviews (Structured Reviews).
4. Design Specifications.
5. Object-Oriented Programming and The Project Team.
6. Prototypes, Specifications and Reviews.
8. Acceptance Test.
10. Checklist for Best Practices.
11. Best-in-Breed Survey Results.
Appendix A: Beta Test and Customer Acceptance Test Checklist.
Appendix B: Ambiguity Reviews.