Preface |
|
v | |
|
|
|
1 The Systems Analyst and Information Systems Development |
|
|
3 | (34) |
|
|
4 | (2) |
|
|
6 | (1) |
|
|
6 | (1) |
|
|
7 | (1) |
|
The Systems Development Life Cycle |
|
|
8 | (2) |
|
|
10 | (1) |
|
|
11 | (1) |
|
|
12 | (1) |
|
|
12 | (1) |
|
Project Identification and Initiation |
|
|
13 | (2) |
|
|
15 | (1) |
|
Applying the Concepts at DronTeq |
|
|
16 | (3) |
|
|
19 | (1) |
|
|
20 | (1) |
|
|
21 | (6) |
|
Organizational Feasibility |
|
|
27 | (2) |
|
Applying the Concepts at DronTeq |
|
|
29 | (2) |
|
|
31 | (4) |
|
Appendix 1A Detailed Economic Feasibility Analysis for DronTeq |
|
|
35 | (2) |
|
2 Project Selection and Management |
|
|
37 | (34) |
|
|
38 | (1) |
|
|
39 | (1) |
|
Applying the Concepts at DronTeq |
|
|
40 | (1) |
|
Creating the Project Plan |
|
|
41 | (1) |
|
Project Methodology Options |
|
|
42 | (7) |
|
Selecting the Appropriate Development Methodology |
|
|
49 | (3) |
|
|
52 | (1) |
|
|
52 | (3) |
|
Coordinating Project Activities |
|
|
55 | (3) |
|
Managing and Controlling the Project |
|
|
58 | (1) |
|
|
58 | (2) |
|
|
60 | (1) |
|
|
60 | (1) |
|
|
61 | (1) |
|
Applying the Concepts at DronTeq |
|
|
62 | (1) |
|
|
63 | (1) |
|
Coordinating Project Activities |
|
|
64 | (1) |
|
|
65 | (6) |
|
|
|
3 Requirements Determination |
|
|
71 | (40) |
|
|
72 | (1) |
|
|
72 | (2) |
|
Requirements Determination |
|
|
74 | (1) |
|
|
74 | (4) |
|
The Process of Determining Requirements |
|
|
78 | (1) |
|
The Requirements Definition Statement |
|
|
78 | (2) |
|
Requirements Elicitation Techniques |
|
|
80 | (1) |
|
Requirements Elicitation in Practice |
|
|
80 | (1) |
|
|
81 | (7) |
|
Joint Application Development (JAD) |
|
|
88 | (4) |
|
|
92 | (2) |
|
|
94 | (2) |
|
|
96 | (1) |
|
Selecting the Appropriate Techniques |
|
|
96 | (2) |
|
Requirements Analysis Strategies |
|
|
98 | (1) |
|
|
98 | (1) |
|
|
98 | (2) |
|
|
100 | (1) |
|
|
100 | (1) |
|
|
100 | (1) |
|
|
101 | (1) |
|
|
101 | (1) |
|
|
102 | (1) |
|
Comparing Analysis Strategies |
|
|
103 | (1) |
|
Applying the Concepts at DronTeq |
|
|
103 | (1) |
|
Eliciting and Analyzing Requirements |
|
|
103 | (1) |
|
|
104 | (1) |
|
|
104 | (2) |
|
|
106 | (5) |
|
4 Understanding Processes with Use Cases and Process Models |
|
|
111 | (58) |
|
|
112 | (1) |
|
|
113 | (1) |
|
The Use Case Concept in a Nutshell |
|
|
113 | (1) |
|
Use Case Formats and Elements |
|
|
114 | (1) |
|
|
114 | (3) |
|
|
117 | (1) |
|
|
118 | (1) |
|
|
118 | (1) |
|
Use Cases and Functional Requirements |
|
|
119 | (1) |
|
|
119 | (1) |
|
|
120 | (1) |
|
Identify the Major Use Cases |
|
|
120 | (2) |
|
Identify the Major Steps for Each Use Case |
|
|
122 | (3) |
|
Identify Elements within Steps |
|
|
125 | (3) |
|
|
128 | (1) |
|
Revise Functional Requirements Based on Use Cases |
|
|
129 | (1) |
|
Applying the Concepts at DronTeq |
|
|
129 | (1) |
|
Identifying the Major Use Cases |
|
|
129 | (1) |
|
Elaborating on the Use Cases |
|
|
130 | (4) |
|
|
134 | (1) |
|
Reading Data Flow Diagrams |
|
|
134 | (2) |
|
Elements of Data Flow Diagrams |
|
|
136 | (3) |
|
Using Data Flow Diagrams to Define Business Processes |
|
|
139 | (3) |
|
|
142 | (2) |
|
Creating Data Flow Diagrams |
|
|
144 | (1) |
|
Creating the Context Diagram |
|
|
145 | (1) |
|
Creating Data Flow Diagram Fragments |
|
|
146 | (2) |
|
Creating the Level 0 Data Flow Diagram |
|
|
148 | (1) |
|
Creating Level 1 Data Flow Diagrams (and Below) |
|
|
149 | (3) |
|
Validating the Data Flow Diagrams |
|
|
152 | (4) |
|
Applying the Concepts at DronTeq |
|
|
156 | (1) |
|
Developing the Process Model |
|
|
156 | (1) |
|
Creating Data Flow Diagram Fragments |
|
|
156 | (1) |
|
Creating the Level 1 Data Flow Diagram |
|
|
157 | (2) |
|
Creating Level 2 Data Flow Diagrams (and Below) |
|
|
159 | (1) |
|
Validating the Data Flow Diagrams |
|
|
160 | (1) |
|
|
161 | (8) |
|
|
169 | (34) |
|
|
170 | (1) |
|
The Entity Relationship Diagram |
|
|
170 | (1) |
|
Reading an Entity Relationship Diagram |
|
|
171 | (1) |
|
Elements of an Entity Relationship Diagram |
|
|
172 | (5) |
|
The Data Dictionary and Metadata |
|
|
177 | (2) |
|
Creating an Entity Relationship Diagram |
|
|
179 | (1) |
|
Building Entity Relationship Diagrams |
|
|
179 | (3) |
|
|
182 | (2) |
|
Applying the Concepts at DronTeq |
|
|
184 | (4) |
|
Validating an Entity Relationship Diagram |
|
|
188 | (1) |
|
|
188 | (3) |
|
|
191 | (1) |
|
Balancing Entity Relationship Diagrams with Data Flow Diagrams |
|
|
191 | (2) |
|
|
193 | (3) |
|
Appendix 5A Normalizing The Data Model |
|
|
196 | (7) |
|
|
|
|
203 | (19) |
|
|
204 | (1) |
|
Transition from Requirements to Design |
|
|
204 | (2) |
|
System Acquisition Strategies |
|
|
206 | (2) |
|
|
208 | (1) |
|
|
209 | (1) |
|
|
210 | (3) |
|
Influences on the Acquisition Strategy |
|
|
213 | (1) |
|
|
213 | (1) |
|
|
214 | (1) |
|
|
215 | (1) |
|
|
215 | (1) |
|
|
215 | (1) |
|
Selecting an Acquisition Strategy |
|
|
215 | (1) |
|
|
216 | (2) |
|
Applying the Concepts at DronTeq |
|
|
218 | (2) |
|
|
220 | (2) |
|
|
222 | (28) |
|
|
223 | (1) |
|
Elements of an Architecture Design |
|
|
223 | (1) |
|
|
223 | (1) |
|
Client-Server Architectures |
|
|
224 | (1) |
|
|
225 | (2) |
|
Server-Based Architecture |
|
|
227 | (1) |
|
Mobile Application Architecture |
|
|
228 | (1) |
|
Advances in Architecture Configurations |
|
|
229 | (1) |
|
Comparing Architecture Options |
|
|
230 | (1) |
|
Creating an Architecture Design |
|
|
231 | (1) |
|
|
231 | (1) |
|
|
232 | (2) |
|
|
234 | (2) |
|
Access Control Requirements |
|
|
236 | (3) |
|
Cultural and Political Requirements |
|
|
239 | (2) |
|
Designing the Architecture |
|
|
241 | (2) |
|
Hardware and Software Specification |
|
|
243 | (2) |
|
Applying the Concepts at DronTeq |
|
|
245 | (1) |
|
Creating an Architecture Design |
|
|
245 | (1) |
|
Hardware and Software Specification |
|
|
246 | (1) |
|
|
247 | (3) |
|
|
250 | (86) |
|
|
251 | (1) |
|
|
251 | (1) |
|
Principles for User Interface Design |
|
|
252 | (1) |
|
|
252 | (2) |
|
|
254 | (1) |
|
|
255 | (1) |
|
|
255 | (2) |
|
|
257 | (1) |
|
|
258 | (1) |
|
Special Issues of Touch Screen Interface Design |
|
|
258 | (1) |
|
User Interface Design Process |
|
|
259 | (1) |
|
|
260 | (2) |
|
|
262 | (3) |
|
|
265 | (1) |
|
Interface Design Prototyping |
|
|
266 | (2) |
|
Interface Evaluation/Testing |
|
|
268 | (4) |
|
|
272 | (1) |
|
|
272 | (1) |
|
|
273 | (2) |
|
|
275 | (3) |
|
|
278 | (1) |
|
|
278 | (2) |
|
|
280 | (2) |
|
|
282 | (1) |
|
|
282 | (1) |
|
|
282 | (2) |
|
|
284 | (2) |
|
|
286 | (1) |
|
Applying the Concepts at DronTeq |
|
|
287 | (1) |
|
|
287 | (1) |
|
|
288 | (1) |
|
|
289 | (1) |
|
Interface Template Design |
|
|
289 | (5) |
|
|
294 | (1) |
|
Interface Evaluation/Testing |
|
|
295 | (1) |
|
|
295 | (6) |
|
|
301 | (1) |
|
Moving from Logical to Physical Process Models |
|
|
301 | (1) |
|
The Physical Data Flow Diagram |
|
|
301 | (3) |
|
Applying the Concepts at DronTeq |
|
|
304 | (1) |
|
|
305 | (3) |
|
|
308 | (1) |
|
|
309 | (3) |
|
Building the Structure Chart |
|
|
312 | (2) |
|
Applying the Concepts at DronTeq |
|
|
314 | (4) |
|
|
318 | (6) |
|
|
324 | (1) |
|
|
324 | (3) |
|
Applying the Concepts at DronTeq |
|
|
327 | (3) |
|
|
330 | (6) |
|
|
336 | (33) |
|
|
337 | (1) |
|
|
337 | (1) |
|
|
338 | (2) |
|
|
340 | (4) |
|
Selecting a Storage Format |
|
|
344 | (2) |
|
Applying the Concepts at DronTeq |
|
|
346 | (1) |
|
Moving from Logical to Physical Data Models |
|
|
347 | (1) |
|
The Physical Entity Relationship Diagram |
|
|
347 | (3) |
|
Revisiting the CRUD Matrix |
|
|
350 | (1) |
|
Applying the Concepts at DronTeq |
|
|
351 | (1) |
|
|
351 | (3) |
|
Optimizing Storage Efficiency |
|
|
354 | (2) |
|
|
356 | (4) |
|
|
360 | (2) |
|
Applying the Concepts at DronTeq |
|
|
362 | (2) |
|
|
364 | (5) |
|
Part 4 Implementation Phase |
|
|
|
11 Moving into Implementation |
|
|
369 | (22) |
|
|
369 | (1) |
|
Managing the Programming Process |
|
|
370 | (1) |
|
Assigning Programming Tasks |
|
|
370 | (1) |
|
|
371 | (1) |
|
|
372 | (1) |
|
|
372 | (2) |
|
|
374 | (1) |
|
|
374 | (3) |
|
|
377 | (1) |
|
|
377 | (1) |
|
|
377 | (2) |
|
|
379 | (1) |
|
|
380 | (1) |
|
Designing Documentation Structure |
|
|
380 | (2) |
|
Writing Documentation Topics |
|
|
382 | (1) |
|
Identifying Navigation Terms |
|
|
383 | (2) |
|
Applying the Concepts at DronTeq |
|
|
385 | (1) |
|
|
385 | (1) |
|
|
385 | (1) |
|
Developing User Documentation |
|
|
386 | (3) |
|
|
389 | (2) |
|
12 Transition to the New System |
|
|
391 | (27) |
|
|
391 | (1) |
|
Making the Transition to the New System |
|
|
392 | (1) |
|
|
393 | (1) |
|
Selecting the Conversion Strategy |
|
|
394 | (4) |
|
Preparing a Business Contingency Plan |
|
|
398 | (1) |
|
|
399 | (1) |
|
Preparing People for the New System |
|
|
400 | (1) |
|
Understanding Resistance to Change |
|
|
400 | (2) |
|
Revising Management Policies |
|
|
402 | (1) |
|
Assessing Costs and Benefits |
|
|
402 | (3) |
|
|
405 | (1) |
|
Enabling Adoption: Training |
|
|
406 | (3) |
|
Postimplementation Activities |
|
|
409 | (1) |
|
|
409 | (1) |
|
|
410 | (2) |
|
|
412 | (2) |
|
Applying the Concepts at DronTeq |
|
|
414 | (1) |
|
|
414 | (1) |
|
|
414 | (1) |
|
Postimplementation Activities |
|
|
414 | (1) |
|
|
415 | (3) |
|
13 Agile Development Methods |
|
|
418 | |
|
|
418 | (1) |
|
|
419 | (1) |
|
Evolution of Agile Development |
|
|
420 | (1) |
|
Adoption of the Agile Approach |
|
|
421 | (1) |
|
Benefits of Agile Methods |
|
|
421 | (1) |
|
Adoption of Specific Agile Methodologies |
|
|
421 | (1) |
|
|
422 | (1) |
|
|
422 | (2) |
|
|
424 | (1) |
|
|
424 | (2) |
|
|
426 | (4) |
|
|
430 | (4) |
|
|
434 | (1) |
|
Other Types of Agile Methodologies |
|
|
434 | (1) |
|
Crystal Development Methodology |
|
|
434 | (1) |
|
Dynamic Systems Development Methodology |
|
|
435 | (1) |
|
Feature Driven Development |
|
|
435 | (1) |
|
Lean Software Development |
|
|
436 | (1) |
|
Comparing the SDLC with Agile Methodologies |
|
|
436 | (1) |
|
|
437 | |
Index |
|
1 | |