Preface |
|
xii | |
|
Information System Development |
|
|
1 | (14) |
|
Information systems and IT |
|
|
1 | (2) |
|
Information systems development methodologies |
|
|
3 | (1) |
|
Information systems development life-cycles |
|
|
4 | (7) |
|
|
4 | (1) |
|
Problems with the waterfall life-cycle |
|
|
5 | (2) |
|
|
7 | (1) |
|
|
7 | (1) |
|
Iterative (rapid) application development |
|
|
7 | (2) |
|
|
9 | (1) |
|
|
9 | (1) |
|
|
9 | (2) |
|
Alternative strategies for information systems acquisition |
|
|
11 | (4) |
|
|
11 | (1) |
|
|
11 | (1) |
|
Application service providers |
|
|
11 | (4) |
|
Internet-based Information Systems |
|
|
15 | (14) |
|
|
15 | (3) |
|
|
15 | (1) |
|
From ARP Anet to the Internet |
|
|
16 | (1) |
|
|
16 | (1) |
|
|
17 | (1) |
|
|
18 | (5) |
|
|
18 | (1) |
|
|
19 | (2) |
|
HyperText Markup Language (HTML) |
|
|
21 | (1) |
|
|
22 | (1) |
|
|
22 | (1) |
|
|
23 | (1) |
|
Open source software development |
|
|
23 | (6) |
|
|
24 | (1) |
|
|
25 | (1) |
|
|
26 | (1) |
|
Implications of OSS for IS development |
|
|
26 | (3) |
|
Web IS Development Methodology (WISDM) |
|
|
29 | (12) |
|
|
29 | (1) |
|
WISDM in context: the Multiview approach to IS development |
|
|
29 | (3) |
|
Using the Multiview framework to guide methodology generation |
|
|
31 | (1) |
|
|
32 | (2) |
|
|
32 | (1) |
|
|
33 | (1) |
|
|
33 | (1) |
|
|
33 | (1) |
|
Human computer interface design |
|
|
33 | (1) |
|
Moving around the methods matrix |
|
|
33 | (1) |
|
The role of the analyst: multiple perspectives |
|
|
34 | (2) |
|
WISDM and the IS development life-cycle |
|
|
36 | (1) |
|
Is web IS development different? |
|
|
36 | (5) |
|
|
41 | (20) |
|
|
41 | (2) |
|
|
43 | (1) |
|
Business webs for the theatre industry |
|
|
43 | (12) |
|
|
46 | (3) |
|
|
49 | (2) |
|
|
51 | (2) |
|
|
53 | (2) |
|
|
55 | (1) |
|
Marketspace transformation and relationship capital |
|
|
56 | (5) |
|
|
61 | (18) |
|
|
61 | (1) |
|
|
61 | (2) |
|
Themes in systems thinking |
|
|
63 | (3) |
|
Systems and patterns of organization |
|
|
63 | (2) |
|
Systems and emergent properties |
|
|
65 | (1) |
|
Recursion and system hierarchies |
|
|
65 | (1) |
|
Communication and control |
|
|
65 | (1) |
|
|
66 | (6) |
|
|
68 | (1) |
|
Negative (or balancing) feedback |
|
|
68 | (2) |
|
Positive (or reinforcing) feedback |
|
|
70 | (1) |
|
|
70 | (2) |
|
|
72 | (4) |
|
|
72 | (1) |
|
|
73 | (1) |
|
|
74 | (1) |
|
Success to the successful |
|
|
75 | (1) |
|
|
76 | (3) |
|
|
79 | (20) |
|
|
79 | (1) |
|
Hard and soft systems thinking |
|
|
80 | (2) |
|
|
80 | (1) |
|
|
81 | (1) |
|
|
82 | (13) |
|
Exploring the problem situation |
|
|
83 | (1) |
|
Situation considered problematic [ 1] |
|
|
83 | (1) |
|
Problem situation expressed [ 2] |
|
|
84 | (2) |
|
Below the line: root definitions and conceptual models |
|
|
86 | (1) |
|
Root definition of relevant systems [ 3] |
|
|
86 | (4) |
|
|
90 | (3) |
|
Back above the line: taking action in the problem situation |
|
|
93 | (1) |
|
Comparison of models with real world [ 5] |
|
|
94 | (1) |
|
Evaluating change [ 6] and taking action [ 7] |
|
|
94 | (1) |
|
Beyond the basic form of SSM |
|
|
95 | (4) |
|
Using SSM to support IS Development |
|
|
96 | (3) |
|
Designing for User Satisfaction |
|
|
99 | (24) |
|
|
99 | (2) |
|
Sociotechnical design with ETHICS |
|
|
101 | (8) |
|
|
103 | (1) |
|
|
103 | (2) |
|
Sociotechnical systems design process |
|
|
105 | (4) |
|
The Scandinavian tradition of participative design |
|
|
109 | (3) |
|
Participative design principles |
|
|
110 | (1) |
|
The participative design process |
|
|
111 | (1) |
|
Web site quality -- the customer perspective |
|
|
112 | (11) |
|
|
112 | (1) |
|
|
113 | (1) |
|
|
114 | (1) |
|
Service interaction quality |
|
|
114 | (1) |
|
The application of WebQual to online bookstores |
|
|
115 | (1) |
|
|
116 | (1) |
|
|
117 | (1) |
|
Interpretation of the results |
|
|
118 | (5) |
|
|
123 | (32) |
|
|
123 | (2) |
|
The theatre booking system |
|
|
124 | (1) |
|
Information system modeling |
|
|
125 | (1) |
|
|
125 | (1) |
|
Structured systems analysis and design |
|
|
126 | (1) |
|
Object-oriented analysis and design |
|
|
126 | (1) |
|
The unified modeling language (UML) |
|
|
126 | (4) |
|
Fundamentals of object-orientation |
|
|
127 | (1) |
|
|
127 | (1) |
|
|
128 | (1) |
|
Encapsulation and communication by messages |
|
|
128 | (1) |
|
|
129 | (1) |
|
|
129 | (1) |
|
Requirements gathering and use case diagrams |
|
|
130 | (4) |
|
|
130 | (1) |
|
|
131 | (2) |
|
Extension, inclusion, and generalization |
|
|
133 | (1) |
|
|
133 | (1) |
|
|
133 | (1) |
|
|
133 | (1) |
|
|
134 | (1) |
|
|
134 | (11) |
|
Relationships: associations |
|
|
137 | (1) |
|
|
137 | (1) |
|
Attributes and operations |
|
|
138 | (1) |
|
|
138 | (1) |
|
|
139 | (1) |
|
Relationships: generalization |
|
|
139 | (1) |
|
Relationships: aggregation |
|
|
140 | (1) |
|
The theatre booking system class model |
|
|
141 | (2) |
|
|
143 | (1) |
|
|
143 | (2) |
|
|
145 | (4) |
|
|
146 | (2) |
|
|
148 | (1) |
|
State transition diagrams |
|
|
149 | (2) |
|
|
151 | (4) |
|
|
155 | (32) |
|
|
155 | (1) |
|
Information system design |
|
|
156 | (1) |
|
|
157 | (3) |
|
|
159 | (1) |
|
|
160 | (13) |
|
|
160 | (1) |
|
|
161 | (1) |
|
|
162 | (1) |
|
|
163 | (1) |
|
Moving from UML class model to relational schema |
|
|
164 | (1) |
|
Implementing many-to-many relationships |
|
|
165 | (1) |
|
Implementing supertype and subtype classes |
|
|
166 | (2) |
|
Theatre booking system database design |
|
|
168 | (1) |
|
Entity-relationship model |
|
|
168 | (1) |
|
Entity and attribute list |
|
|
169 | (3) |
|
Object-oriented databases |
|
|
172 | (1) |
|
Object-relational hybrids |
|
|
172 | (1) |
|
|
172 | (1) |
|
|
172 | (1) |
|
|
173 | (5) |
|
|
174 | (1) |
|
|
175 | (1) |
|
|
175 | (1) |
|
Seat reservations -- locking strategy |
|
|
176 | (1) |
|
State transition diagrams |
|
|
177 | (1) |
|
|
178 | (9) |
|
|
179 | (3) |
|
|
182 | (1) |
|
|
183 | (4) |
|
Software System Construction |
|
|
187 | (36) |
|
|
187 | (1) |
|
Software implementation overview |
|
|
188 | (1) |
|
Business data implementation |
|
|
189 | (8) |
|
|
190 | (3) |
|
|
193 | (2) |
|
|
195 | (1) |
|
|
195 | (1) |
|
|
196 | (1) |
|
|
197 | (9) |
|
Using ColdFusion to publish a database on the Internet |
|
|
197 | (2) |
|
Queries and the three ANSI three-level architecture model |
|
|
199 | (1) |
|
Developing Cold Fusion components for the business logic |
|
|
200 | (4) |
|
|
204 | (1) |
|
URL parameters and form fields |
|
|
205 | (1) |
|
|
205 | (1) |
|
|
206 | (1) |
|
|
206 | (1) |
|
Presentation layer -- the user interface |
|
|
206 | (4) |
|
|
207 | (1) |
|
|
208 | (1) |
|
Browser compatibility and bandwidth |
|
|
209 | (1) |
|
Putting it all together -- the complete application |
|
|
210 | (5) |
|
Wireless application protocol (WAP) |
|
|
215 | (3) |
|
Generating wireless content with ColdFusion |
|
|
216 | (2) |
|
|
218 | (5) |
|
|
218 | (1) |
|
|
219 | (1) |
|
Host the site at an Internet Service Provider (ISP) |
|
|
219 | (1) |
|
Co-host a server with an ISP |
|
|
219 | (1) |
|
|
220 | (1) |
|
|
220 | (1) |
|
|
221 | (2) |
|
Web Information Management |
|
|
223 | (22) |
|
|
223 | (1) |
|
eXtensible Markup Language (XML) |
|
|
224 | (10) |
|
|
227 | (2) |
|
Displaying XML in a browser |
|
|
229 | (1) |
|
|
230 | (1) |
|
Business applications of XML |
|
|
231 | (1) |
|
|
231 | (1) |
|
Web automation for business to business transactions |
|
|
231 | (1) |
|
Intranet development and knowledge management |
|
|
231 | (1) |
|
Delivery to different platforms |
|
|
231 | (1) |
|
XML and databases, XML and Java |
|
|
232 | (1) |
|
XML, web services, and .NET |
|
|
233 | (1) |
|
Content management systems |
|
|
234 | (11) |
|
Issues in web content management |
|
|
235 | (1) |
|
Genesis of web content management systems |
|
|
236 | (2) |
|
A web content management systems framework |
|
|
238 | (1) |
|
|
238 | (1) |
|
Organizational integration |
|
|
238 | (1) |
|
|
239 | (1) |
|
CMS illustration: Intranet development |
|
|
240 | (1) |
|
The CMS framework as a diagnostic tool |
|
|
241 | (4) |
|
|
245 | (10) |
|
|
245 | (1) |
|
|
245 | (2) |
|
The client organization in 1998 |
|
|
245 | (1) |
|
The Global Drinks e-commerce project 1999--2001 |
|
|
246 | (1) |
|
Outcomes of the intervention |
|
|
246 | (1) |
|
Web IS Development methods |
|
|
247 | (3) |
|
|
247 | (1) |
|
|
248 | (1) |
|
|
248 | (1) |
|
|
249 | (1) |
|
|
250 | (1) |
|
Methods and methodology in IS development |
|
|
251 | (4) |
Appendix A: Barchester Playhouse Case Study |
|
255 | (8) |
|
|
255 | (2) |
|
A.1.1 The organization of the Playhouse |
|
|
256 | (1) |
|
A.2 Current box office operations |
|
|
257 | (1) |
|
|
257 | (1) |
|
Processes and data supported by the current box office system |
|
|
258 | (1) |
|
Issues with the current box office system |
|
|
258 | (1) |
|
A.3 Motivation for change |
|
|
258 | (1) |
|
A.3.1 Perceptions of the theatre |
|
|
259 | (1) |
|
A.4 Requirements of the theatre booking system |
|
|
259 | (4) |
|
|
259 | (1) |
|
Theatre productions and performances |
|
|
260 | (1) |
|
|
260 | (1) |
|
|
261 | (1) |
|
A.4.1 Roles and attitudes of those involved in the analysis |
|
|
261 | (2) |
Appendix B: Research Student Admissions Case Study |
|
263 | (4) |
|
|
263 | (4) |
Appendix C: Internet Resources |
|
267 | (4) |
|
|
267 | (1) |
|
|
267 | (2) |
|
Tools required for the TicketManager application |
|
|
267 | (1) |
|
Optional tools for the TicketManager application |
|
|
268 | (1) |
|
|
269 | (1) |
|
|
269 | (2) |
Index |
|
271 | |