Process-centered review of object oriented software development methodologies
ACM Computing Surveys (CSUR)
| Hi-index | 0.00 |
From the Publisher:Is the Unified Process the be all and end all standard for developing object-oriented component-based software? Scott Ambler doesn't think so. This book is one in a four-volume series that presents a critical review of the Unified Process designed to present a more robust software process that addresses your development and production needs. The series has been organized to address each of the four phases of the UP Inception, Elaboration, Construction, and Transition. It will: Provide you a balanced perspective of the alternative design methodologies available. Propose a synthesized software process that addresses the scope of your real world. Present materials from the Software Development magazine that will flesh out each of the UP phases. You get the collective wisdom of industry luminaries. Articles by Peter Coad, Larry Constantine, Martin Fowler, David Linthicum, Mary Loomis, Steve Maguire, Steve McConnell, Clemens Szyperski, and Karl Wiegers, and others, provide perspective on the macro issues like: How large-scale, mission critical software is developed and maintained. How each workflow fits into the overall development lifecycle. Tips and techniques to enhance your role (and career). And they address the details of implementing a software process with best practices on such issues as code inspections, configuration management, change control, and architectural modeling of your software organization. Fill the gaps between theory and practice with a plan that includes the nuts and bolts. The Elaboration Phase the second of four chronological phases in the UP focuseson defining, validating, and establishing the baseline architecture for a system. A carefully selected array of articles address the vital elements of this phase. Subjects include developing frameworks, component architectures, designing with interfaces, building large systems, using the Unified Modeling Language (UML) effectively, working with legacy systems, modeling business rules, selecting tools, building your development team, user interface prototyping, testing your requirements, and effectively managing metrics.