Relevance for Software Engineering
Since each aspect of the case studies pertains to some problem in software engineering and its solution, relevance is evident; we chose the cases based on utility. One of the most accelerated ways to illustrate such points is the use of case studies [Linn and Clancy92]. Table 16.1 presents the structure of the chapter.
| Software Management | Software Development Paradigm | General Principles |
|---|---|---|
| Case 1: Overtime | Case 5: Specifying | Case 9: The Recycling Principle |
| Case 2: Schedule | Case 6: Designing | Case 10: Multiple Representations |
| Case 3: Getting New Business | Case 7: Coding | Case 11: Alternative Tasks |
| Case 4: Discovering Information | Case 8: Testing | Case 12: Reflection Case 13: Fingerprints Case 14: Divide and Conquer Case 15: Persecution Complex Case 16: Literacy |
EAN: 2147483647
Pages: 242
- Structures, Processes and Relational Mechanisms for IT Governance
- An Emerging Strategy for E-Business IT Governance
- Linking the IT Balanced Scorecard to the Business Objectives at a Major Canadian Financial Group
- A View on Knowledge Management: Utilizing a Balanced Scorecard Methodology for Analyzing Knowledge Metrics
- Governance Structures for IT in the Health Care Industry