|
|
1 | (20) |
|
|
2 | (2) |
|
Just What Is a Complex Project? |
|
|
4 | (14) |
|
|
7 | (2) |
|
|
9 | (1) |
|
|
9 | (9) |
|
|
18 | (3) |
Part I Determining Needs |
|
|
2 Assessing Business Requirements |
|
|
21 | (16) |
|
The Tiers of Software Development |
|
|
21 | (7) |
|
|
21 | (1) |
|
|
22 | (1) |
|
Productivity Through Automation |
|
|
22 | (1) |
|
|
22 | (2) |
|
Establishing User Interfaces |
|
|
24 | (1) |
|
Forming an Interview Approach |
|
|
25 | (2) |
|
Dealing with Political Factions |
|
|
27 | (1) |
|
Categories and Levels of Users |
|
|
28 | (8) |
|
Joint Application Development (JAD) |
|
|
31 | (5) |
|
|
36 | (1) |
|
|
37 | (12) |
|
|
42 | (5) |
|
The Supporter Side of Buying |
|
|
43 | (1) |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
46 | (1) |
|
|
47 | (1) |
|
|
47 | (1) |
|
|
48 | (1) |
|
4 Establishing Requirements Using a Request for Proposal (RFP) and a Request for Information (RFI) |
|
|
49 | (22) |
|
|
49 | (5) |
|
|
54 | (15) |
|
|
54 | (15) |
|
|
69 | (2) |
|
5 Searching for Solutions |
|
|
71 | (10) |
|
Selecting the Management Team |
|
|
71 | (1) |
|
The Process of Due Diligence |
|
|
72 | (4) |
|
Performing Reference Checks |
|
|
73 | (1) |
|
Reviewing Financial Statements |
|
|
73 | (1) |
|
|
74 | (1) |
|
Scheduling On-Site Demonstrations |
|
|
74 | (1) |
|
Scheduling On-Site Review at Vendor Site(s) |
|
|
75 | (1) |
|
Reviewing Vendor Training Capabilities |
|
|
75 | (1) |
|
Understanding the Product Upgrade Process |
|
|
75 | (1) |
|
|
76 | (1) |
|
Understanding the Vendor Ownership |
|
|
76 | (1) |
|
Reviewing the Product's Architecture and Design |
|
|
76 | (1) |
|
|
77 | (1) |
|
|
78 | (1) |
|
|
79 | (1) |
|
|
79 | (1) |
|
|
79 | (2) |
|
6 Controlling Costs and Realistic Budgeting |
|
|
81 | (18) |
|
|
89 | (1) |
|
Hardware and Infrastructure |
|
|
89 | (1) |
|
|
90 | (1) |
|
|
91 | (1) |
|
|
91 | (1) |
|
The Balanced Scorecard as a Budget Tool |
|
|
92 | (5) |
|
|
97 | (1) |
|
|
97 | (2) |
|
7 Analysis Methods and Tools |
|
|
99 | (18) |
|
The Concept of the Logical Equivalent |
|
|
99 | (4) |
|
Tools of Structured Analysis |
|
|
103 | (1) |
|
Making Changes and Modifications |
|
|
104 | (6) |
|
|
104 | (2) |
|
|
106 | (1) |
|
|
106 | (2) |
|
|
108 | (2) |
|
|
110 | (2) |
|
|
112 | (5) |
Part II Development Architecture |
|
|
8 Creating Requirements Documents Using Analysis Tools |
|
|
117 | (28) |
|
|
117 | (5) |
|
|
122 | (1) |
|
|
122 | (1) |
|
|
123 | (1) |
|
|
123 | (1) |
|
|
124 | (2) |
|
Sequence of Implementation |
|
|
126 | (1) |
|
|
127 | (4) |
|
|
127 | (1) |
|
|
127 | (1) |
|
Either/Or with Option Separator ([ /]) |
|
|
127 | (1) |
|
|
128 | (1) |
|
|
128 | (1) |
|
|
128 | (3) |
|
|
131 | (6) |
|
|
131 | (2) |
|
|
133 | (1) |
|
|
134 | (1) |
|
|
135 | (2) |
|
State Transition Diagrams |
|
|
137 | (4) |
|
Entity Relationship Diagrams |
|
|
141 | (1) |
|
|
142 | (1) |
|
|
143 | (1) |
|
|
144 | (1) |
|
|
145 | (34) |
|
Introduction to Databases |
|
|
145 | (1) |
|
|
145 | (2) |
|
Logic Data Modeling Procedures |
|
|
147 | (11) |
|
|
147 | (2) |
|
|
149 | (9) |
|
Limitations of Normalization |
|
|
158 | (18) |
|
The Supertype/Subtype Model |
|
|
160 | (5) |
|
|
165 | (4) |
|
|
169 | (2) |
|
Integration with Existing Data Models |
|
|
171 | (2) |
|
Determining Domains and Triggering Operations |
|
|
173 | (2) |
|
|
175 | (1) |
|
|
176 | (1) |
|
|
176 | (1) |
|
|
177 | (1) |
|
|
178 | (1) |
|
10 Legacy Systems and Integration |
|
|
179 | (36) |
|
|
179 | (1) |
|
|
180 | (1) |
|
Third-Generation Language Legacy System Integration |
|
|
181 | (2) |
|
Replacing Third-Generation Legacy Systems |
|
|
183 | (1) |
|
Approaches to Logic Reconstruction |
|
|
183 | (1) |
|
Enhancing Third-Generation Legacy Systems |
|
|
184 | (7) |
|
Data Element Enhancements |
|
|
186 | (1) |
|
|
187 | (4) |
|
"Leaving As Is": Third-Generation Legacy Systems |
|
|
191 | (1) |
|
Fourth-Generation Language Legacy System Integration |
|
|
192 | (1) |
|
Replacing Fourth-Generation Legacy Systems |
|
|
192 | (1) |
|
Approaches to Logic Reconstruction |
|
|
192 | (2) |
|
Enhancing Fourth-Generation Legacy Systems |
|
|
194 | (1) |
|
"Leaving As Is": Fourth-Generation Legacy Systems |
|
|
195 | (1) |
|
Hybrid Methods: The Gateway Approach |
|
|
196 | (1) |
|
Incremental Application Integration |
|
|
197 | (1) |
|
Incremental Data Integration |
|
|
198 | (4) |
|
Converting Legacy Character-Based Screens |
|
|
202 | (1) |
|
The Challenge with Encoded Legacy Screen Values |
|
|
203 | (1) |
|
Legacy Migration Methodology |
|
|
204 | (9) |
|
Step 1: Analyze the Existing Legacy Systems |
|
|
205 | (1) |
|
Step 2: Decompose Legacy Systems to Determine Schedules of Migration and Linkage Strategies |
|
|
206 | (1) |
|
Step 3: Design "As Is" Links |
|
|
207 | (1) |
|
Step 4: Design Legacy Enhancements |
|
|
207 | (1) |
|
Step 5: Design Legacy Replacements |
|
|
208 | (1) |
|
Step 6: Design and Integrate New Databases |
|
|
208 | (1) |
|
Step 7: Determine New Infrastructure and Environment, Including Gateways |
|
|
209 | (1) |
|
Step 8: Implement Enhancements |
|
|
210 | (1) |
|
|
210 | (1) |
|
Step 10: Migrate Legacy Databases |
|
|
211 | (1) |
|
Step 11: Migrate Replacement Legacy Applications |
|
|
211 | (1) |
|
Step 12: Incrementally Cutover to New Systems |
|
|
212 | (1) |
|
|
213 | (1) |
|
|
213 | (2) |
|
11 Business Process Reengineering |
|
|
215 | (12) |
|
Analyzing Legacy Systems for Replacement |
|
|
215 | (1) |
|
|
216 | (1) |
|
|
217 | (1) |
|
Combining Structured and Object Techniques |
|
|
217 | (2) |
|
|
219 | (2) |
|
Information Systems Issues |
|
|
221 | (1) |
|
System Development Life Cycle (SDLC) |
|
|
222 | (1) |
|
|
223 | (1) |
|
Downsizing System Components |
|
|
224 | (1) |
|
Transactions vs. Data Warehousing |
|
|
225 | (1) |
|
|
226 | (1) |
|
12 Digital Transformation and Consumer Requirements |
|
|
227 | (24) |
|
Requirements Without Users and Without Input |
|
|
229 | (5) |
|
Concepts of the S-Curve and Digital Transformation Analysis and Design |
|
|
233 | (1) |
|
Analysis and Design and the S-Curve |
|
|
234 | (1) |
|
|
235 | (9) |
|
|
244 | (2) |
|
The Role of the Analyst in Change Management for IT Organizations |
|
|
246 | (3) |
|
The Analyst in the Digital Transformation Era |
|
|
248 | (1) |
|
|
249 | (1) |
|
|
250 | (1) |
|
13 Data Analytics and Data Warehouses |
|
|
251 | (40) |
|
|
251 | (1) |
|
Data Warehousing Concepts |
|
|
252 | (1) |
|
Performance Benefits of Data Warehouses |
|
|
253 | (2) |
|
Concept of Multiple Dimensions |
|
|
255 | (3) |
|
Data Warehouse Architecture |
|
|
258 | (3) |
|
Extracting Data from the Source |
|
|
258 | (2) |
|
Staging the Extracted Data |
|
|
260 | (1) |
|
|
260 | (1) |
|
|
261 | (1) |
|
Types of Data Warehouse Architecture |
|
|
261 | (2) |
|
The Packaged Software Decision Support Life Cycle |
|
|
263 | (21) |
|
|
264 | (1) |
|
Phase 2: Gathering Data Requirements and Modeling |
|
|
265 | (4) |
|
Phase 3: Physical Database Design and Development |
|
|
269 | (4) |
|
Phase 4: Data Mapping and Transformation |
|
|
273 | (3) |
|
Phase 5: Populating the Data Warehouse |
|
|
276 | (2) |
|
Phase 6: Automating Data Management Procedures |
|
|
278 | (1) |
|
Phase 7: Application Development and Reporting |
|
|
278 | (5) |
|
Phase 8: Data Validation and Testing |
|
|
283 | (1) |
|
|
283 | (1) |
|
|
283 | (1) |
|
|
284 | (1) |
|
Considerations for Using Big Data |
|
|
284 | (3) |
|
Data Visualization and Design |
|
|
287 | (1) |
|
|
288 | (1) |
|
|
288 | (1) |
|
|
289 | (2) |
|
14 Documentation and Acceptance Testing |
|
|
291 | (10) |
|
|
292 | (1) |
|
|
292 | (1) |
|
Cannot Test 100% of Everything |
|
|
292 | (1) |
|
More Efficient Development |
|
|
293 | (2) |
|
|
295 | (1) |
|
|
295 | (1) |
|
|
295 | (1) |
|
|
296 | (1) |
|
|
297 | (1) |
|
|
297 | (4) |
Part III How to Implement |
|
|
|
301 | (24) |
|
|
301 | (3) |
|
|
304 | (1) |
|
|
304 | (1) |
|
|
305 | (1) |
|
Determining the Scope of the Project |
|
|
306 | (1) |
|
|
307 | (1) |
|
|
308 | (2) |
|
|
310 | (3) |
|
|
313 | (1) |
|
Set Rules and Guidelines for Communication |
|
|
313 | (1) |
|
|
313 | (2) |
|
Working with User Resources |
|
|
315 | (1) |
|
|
315 | (1) |
|
Planning and Process Development |
|
|
315 | (4) |
|
|
319 | (2) |
|
Defining Technical Development Requirements |
|
|
319 | (1) |
|
|
320 | (1) |
|
Project Management and Communication |
|
|
321 | (1) |
|
|
322 | (1) |
|
|
323 | (1) |
|
|
323 | (2) |
|
16 Virtual Teams and Outsourcing |
|
|
325 | (16) |
|
|
327 | (1) |
|
Project Management Challenges |
|
|
327 | (1) |
|
Dealing with Multiple Locations |
|
|
327 | (4) |
|
|
331 | (1) |
|
|
331 | (1) |
|
|
331 | (1) |
|
|
331 | (1) |
|
Externalization Virtual Project Management |
|
|
332 | (1) |
|
Internalization Virtual Project Management |
|
|
332 | (1) |
|
Combination Virtual Project Management |
|
|
332 | (1) |
|
|
333 | (1) |
|
Dealing with Multiple Locations and Outsourcing |
|
|
334 | (2) |
|
Social Discourse in Virtual Project Management |
|
|
336 | (1) |
|
|
336 | (1) |
|
|
337 | (1) |
|
|
337 | (2) |
|
|
339 | (1) |
|
|
339 | (2) |
|
17 Cyber Security, ISO 9000, and the Software Development Life Cycle |
|
|
341 | (14) |
|
Cyber Security in Analysis and Design |
|
|
341 | (1) |
|
Cyber Security Risk in the S-Curve |
|
|
342 | (1) |
|
Decomposition in Cyber Security Analysis |
|
|
343 | (1) |
|
|
344 | (1) |
|
Developing a System of Procedures |
|
|
345 | (9) |
|
|
346 | (1) |
|
How to Incorporate ISO 9000 into Existing Software Life Cycles |
|
|
347 | (3) |
|
|
350 | (2) |
|
|
352 | (2) |
|
|
354 | (1) |
|
|
354 | (1) |
|
18 Vendor Contract Considerations |
|
|
355 | (24) |
|
|
356 | (1) |
|
Legal Protections and Coverage |
|
|
357 | (1) |
|
|
358 | (2) |
|
Deliverables and Performance |
|
|
360 | (16) |
|
Contract Considerations in a Global Economy |
|
|
376 | (2) |
|
|
378 | (1) |
|
19 Going Live and Conclusions |
|
|
379 | (6) |
|
|
379 | (1) |
|
|
380 | (1) |
|
|
381 | (4) |
Appendix A Case Study: The Rainforest Book Company Problem |
|
385 | (4) |
Appendix B Case Study: Northwest General Practitioner's Office |
|
389 | (2) |
Appendix C Case Study: University Student Enrollment Database |
|
391 | (2) |
Further Reading |
|
393 | (2) |
Glossary |
|
395 | (4) |
Index |
|
399 | |