Table of Contents

Acknowledgments. Preface. PART I. THE PROBLEM. 1. Familiar Passages. The Industrial Viewpoint. The Practitioner Viewpoint. The Example. 2. Recognizing the Problem. The Example (Continued). Territories, Maps, and Bridges. PART II. THE APPROACH. 3. Just--In--Time Philosophy and Strategy. Plan, Plan, Then Re--Plan. Identify Risks Early. Develop in Parallel. 4. More on Software Risk Management and Just--In--Time. Risk Management Perspectives. Strategic Risk Management. Operational Risk Management. 5. Elements of Software Risk. Technical Risk. Cost Risk. Schedule Risk. Risk Management Activities. Risk Identification. Risk Strategy and Planning. Risk Assessment. Risk Mitigation/Avoidance. Risk Reporting. Risk Prediction. 6. Software Risk Factors. Organization. Estimation. Monitoring. Development Methodology. Tools. Risk Culture. Usability. Correctness. Reliability. Personnel. 7. Software Risk Metrics. Organization. Estimation. Monitoring. Development Methodology. Tools. Risk Culture. Usability. Correctness. Reliability. Personnel. 8. Just--In--Time Method by Development Phase. Pre--Requirements and QFD. Requirements: Written and Executable. Design: Wide Then Deep. Code: Start Early! Test: Accepting In Steps. Delivery and Maintenance: Old Code Never Dies. PART III: THE APPLICATION. 9. Applying Just--In--Time. Making Choices. The Model's Design. The Model's Equations. A SERIM Example. Interpreting SERIM's Results. Using SERIM for Predicting Risks. JIT Software: The Whole Picture. 10. Just--In--Time Examples. PC Software Project. Embedded Software Application Project. QFD Application. PERT Application. SERIM Application. Interpreting the Results: PC Project. Interpreting the Results: Embedded Project. Interpreting the Results: Both Projects. Executable Requirements. Design Strategies. Coding. Testing and Delivery. Dreaming About Maintenance. Closing Thoughts. Glossary. References. Index. About the Author.

About the Author

Karl Karolak is currently a Design Engineering Manager at TRW Automotive Electronics Group. He received the BS degree in computer science from Central Michigan University, the PhD degree in software engineering from Union Institute in Cincinnati, Ohio, and the MBA degree from the University of Phoenix. His research interests include software engineering management, software process development, software architectures, and software verification/validation. Karolak is a member of the IEEE Computer Society and the ACM. He has published papers for IEEE, ACM, SERF, and NSIA and has a patent pending on a Software Architecture for a Communications (Network) Management System.