Successful Software Development (2nd Edition)
Scott E. Donaldson
Format: PDF / Kindle (mobi) / ePub
In the age of the Internet, where software is more mission-critical than ever, it is no longer enough for your development projects to succeed some of the time. You need to deliver excellence, consistently - and you must do it faster than ever.
development disciplines and the product assurance disciplines perceive project progress from different viewpoints. Developers tend to look for solutions that “work” but often do not worry how the solutions “will not work.” Product assurance tends to look at developer solutions from the view of how the solutions “work” and “will not work.” This second look both helps to ensure that the customer’s needs are being satisfied and increases the likelihood of a good return on the development investment.
buy-in to the changes that ADPE implementation implies? ♦ How does a seller involve the customer in the ADPE development and implementation? ♦ How does a seller extend the cultural change activity associated with ADPE implementation beyond the seller’s environment into the customer’s environment? ♦ How can seller senior management support be orchestrated to facilitate ADPE implementation? ♦ How frequently should promulgated ADPE elements be updated to tune their effectiveness without disrupting
Programs CONFIGURATION MANAGEMENT Baseline Project Plan . . . Baseline Project Plan . . . Baseline Design Plan, Records . . . Update Plans . . . Baseline Development Plan, Databases . . .Update Plans . . . Baseline Implementation Plan, Tables, Pgms. . . .Update Plans . . . Baseline Retirement Plan, Catalog and Archive Products CUSTOMER/ SELLER INTERACTION Management $ $ CCB Development Product Assurance The Change Control Board (CCB) is a CUSTOMER/SELLER forum convened periodically
or idea. As the project unfolds, the products take shape. For example, a requirements document evolves from a topic outline, to an annotated outline, to a detailed specification. As the requirements specification takes shape, the computer code also takes shape. Early in the project, there is a concept of what the computer code will do and how it may be organized. As the requirements specification evolves to a design specification, the computer code takes on additional shape. Equally important is
process. 148 Chapter 3 • Software Systems Development Process Subsequently, if appropriate, the program manager may decide additional training or mentoring is needed within the organization. Perhaps when the program manager is convinced that project managers understand what to do, the final approval authority for certain products may be delegated to the project managers. Figure 3–13 shows an example tracking form linked to our example organizational software systems development process. To