000 | 22448cam a2205245Ii 4500 | ||
---|---|---|---|
001 | 2209 | ||
008 | 150117s2008 mauab b 001 0 eng | ||
020 | _a0073195588q(hardback) | ||
020 |
_a9780073195582 _q(hardback) |
||
040 |
_aTR-IsMEF _beng _erda _cTR-IsMEF |
||
041 | 0 | _aeng | |
049 | _aTR-IsMEF | ||
050 | 0 | 0 |
_aHD30.2 _b.B35 2008 |
100 | 1 |
_aBaltzan, Paige, _eauthor. |
|
245 | 1 | 0 |
_aBusiness driven information systems / _cPaige Baltzan, Daniels College of BUsiness, University of Denver, Amy Phillips, Daniels College of Business, University of Denver. |
264 | 1 |
_aBoston : _bMcGraw-Hill/Irwin, _c2008. |
|
264 | 4 | _a©2008. | |
300 |
_axxix, 489 pages : _billustrations (some color), map ; _c29 cm. + _e2 CD-ROM (4 3/4 in.) |
||
336 |
_atext _2rdacontent |
||
337 |
_aunmediated _2rdamedia |
||
338 |
_avolume _2rdacarrier |
||
500 | _a"McGraw-Hill higher education"--P. 4 of cover. | ||
504 | _aIncludes bibliographical references and index. | ||
538 | _aSystem requirements: Pentium II or higher with minimum 300 MHz processor; Windows 2000/ XP; 128 MB RAM; sound card and speakers or headphones; Internet Explorer 6.0; Adobe Acrobat 5.0 or higher; Windows Media Player 9 or higher | ||
596 | _a1 | ||
650 | 0 |
_aIndustrial management _xData processing |
|
650 | 0 |
_aInformation technology _xManagement |
|
700 | 1 |
_aPhillips, Amy _q(Amy L.), _eauthor. |
|
900 | _aMEF Üniversitesi Kütüphane katalog kayıtları RDA standartlarına uygun olarak üretilmektedir / MEF University Library Catalogue Records are Produced Compatible by RDA Rules | ||
910 | _aÇağlayan. | ||
942 |
_2lcc _cBKS _01 |
||
970 | 1 | 2 |
_tChapter 1 information systems in business, _p1. |
970 | 1 | 2 |
_tOpening case: apple-merging technology, business, and entertainment, _p2. |
970 | 0 | 1 |
_aIntroduction, _p5. |
970 | 1 | 2 |
_tSection 1.1 information systems in business, _p5. |
970 | 1 | 2 |
_tInformation technology's role in business, _p5. |
970 | 1 | 1 |
_tInformation technology's impact on business operations, _p5. |
970 | 1 | 2 |
_tInformation technology basics, _p8. |
970 | 1 | 1 |
_tInformation versus data, _p9. |
970 | 1 | 1 |
_tIT resources, _p9. |
970 | 1 | 1 |
_tIT cultures, _p9. |
970 | 1 | 2 |
_tRoles and responsibilities in information technology, _p10. |
970 | 1 | 1 |
_tThe gap between business personnel and IT personnel, _p12. |
970 | 1 | 2 |
_tMeasuring information technology's success, _p13. |
970 | 1 | 1 |
_tEfficiency and effectiveness metrics, _p13. |
970 | 1 | 1 |
_tBenchmarking-baseline metrics, _p14. |
970 | 1 | 1 |
_tThe interrelationship between efficiency and effectiveness IT metrics, _p14. |
970 | 1 | 2 |
_tSection 1.2 business strategy, _p17. |
970 | 1 | 2 |
_tBusiness strategy, _p17. |
970 | 1 | 2 |
_tThe five forces model-evaluating business segments, _p17. |
970 | 1 | 1 |
_tBuyer power, _p18. |
970 | 1 | 1 |
_tSupplier power, _p18. |
970 | 1 | 1 |
_tThereat of substitute products or services, _p19. |
970 | 1 | 1 |
_tThereat of new entrants, _p19. |
970 | 1 | 1 |
_tRivalry among existing competitors, _p20. |
970 | 1 | 2 |
_tThe three generic strategies-creating a business focus, _p20. |
970 | 1 | 2 |
_tValue chain analysis-targeting business processes, _p21. |
970 | 1 | 1 |
_tValue creation, _p21. |
970 | 0 | 1 |
_aKey terms, _p24. |
970 | 1 | 2 |
_tCase study one: say "charge it" with your cell phone, _p25. |
970 | 1 | 2 |
_tCase study two: innovative business managers, _p26. |
970 | 1 | 2 |
_tCase study three: the world is fiat-Thomas Friedman, _p28. |
970 | 1 | 2 |
_tMaking business decisions, _p29. |
970 | 1 | 2 |
_tChapter 2: strategic decision making, _p31. |
970 | 1 | 2 |
_tOpening case: revving up sales at Harley Davidson, _p32. |
970 | 0 | 1 |
_aIntroduction, _p35. |
970 | 1 | 2 |
_tSection 2.1 decision-making systems, _p35. |
970 | 1 | 2 |
_tDecision making, _p36. |
970 | 1 | 2 |
_tTransaction processing systems, _p36. |
970 | 1 | 2 |
_tDecision support systems, _p38. |
970 | 1 | 2 |
_tExecutive information systems, _p39. |
970 | 1 | 1 |
_tDigital dashboards, _p40. |
970 | 1 | 1 |
_tArtificial intelligence, _p43. |
970 | 1 | 1 |
_tData mining, _p45. |
970 | 1 | 2 |
_tSection 2.2 enterprise systems, _p46. |
970 | 1 | 2 |
_tEnterprise systems, _p46. |
970 | 1 | 2 |
_tSupply chain management, _p46. |
970 | 1 | 2 |
_tCustomer relationship management, _p47. |
970 | 1 | 1 |
_tCRM strategy, _p48. |
970 | 1 | 2 |
_tBusiness process reengineering, _p49. |
970 | 1 | 1 |
_tFinding opportunity using BPR, _p50. |
970 | 1 | 1 |
_tPitfalls of BPR, _p52. |
970 | 1 | 2 |
_tEnterprise resource planning, _p52. |
970 | 1 | 1 |
_tERP software, _p52. |
970 | 1 | 1 |
_tFinding the right ERP solution, _p53. |
970 | 0 | 1 |
_aKey terms, _p54. |
970 | 1 | 2 |
_tClosing case one: conslidating touchpoints for saab, _p50. |
970 | 1 | 2 |
_tClosing case two: made-to-order businesses, _p56. |
970 | 1 | 2 |
_tClosing case three: delta air lines plays catch-up, _p58. |
970 | 1 | 2 |
_tMaking business decisions, _p60. |
970 | 1 | 2 |
_tChapter 3 e-business, _p62. |
970 | 1 | 2 |
_tOpenning case: Amazon.com-not your average bookstore, _p65. |
970 | 0 | 1 |
_aIntroduction, _p65. |
970 | 1 | 2 |
_tSection 3.1 business and the internet, _p65. |
970 | 1 | 2 |
_tDisruptive tehcnology, _p65. |
970 | 1 | 1 |
_tDisruptive versus sustainning technology, _p66. |
970 | 1 | 1 |
_tThe internet-business disruption, _p67. |
970 | 1 | 2 |
_tEvolution of the internet, _p67. |
970 | 1 | 1 |
_tEvolution of the world wide web, _p69. |
970 | 1 | 2 |
_tAccessing internet information, _p72. |
970 | 1 | 1 |
_tIntranet, _p71. |
970 | 1 | 1 |
_tExtranet, _p71. |
970 | 1 | 1 |
_tPortal, _p71. |
970 | 1 | 1 |
_tKiosk, _p72. |
970 | 1 | 2 |
_tProviding internet information, _p72. |
970 | 1 | 1 |
_tInternet service provider, _p72. |
970 | 1 | 1 |
_tOnline service provider, _p74. |
970 | 1 | 1 |
_tApplication service provider, _p74. |
970 | 1 | 2 |
_tSection 3.2 e-business, _p75. |
970 | 1 | 2 |
_tE-business basics, _p75. |
970 | 1 | 2 |
_tE-business models, _p76. |
970 | 1 | 1 |
_tBusiness-to-business (B2B), _p76. |
970 | 1 | 1 |
_tBusiness-to-consumer (B2C), _p78. |
970 | 1 | 1 |
_tConsumer-to-business (C2B), _p79. |
970 | 1 | 1 |
_tConsumer-to-consumer (C2C), _p79. |
970 | 1 | 2 |
_tOrganizational strategies for e-business, _p79. |
970 | 1 | 1 |
_tMarketing/sales, _p80. |
970 | 1 | 1 |
_tFinancial services, _p80. |
970 | 1 | 1 |
_tPurchasing, _p82. |
970 | 1 | 1 |
_tCustomer service, _p83. |
970 | 1 | 1 |
_tIntermediaries, _p85. |
970 | 1 | 2 |
_tMeasuring e-business success, _p85. |
970 | 1 | 1 |
_tWeb site metrics, _p86. |
970 | 1 | 2 |
_tE-business benefits and challenges, _p87. |
970 | 1 | 2 |
_tNew trends in e-business, e-government, and m-commerce, _p91. |
970 | 1 | 1 |
_tM-commerce, _p91. |
970 | 0 | 1 |
_aKey terms, _p93. |
970 | 1 | 2 |
_tCase study one: eBay-the ultimate e-business, _p94. |
970 | 1 | 2 |
_tCase study two: direct groceries, _p97. |
970 | 1 | 2 |
_tCase study three: how do you value friendster?, _p98. |
970 | 1 | 2 |
_tMaking business decisions, _p99. |
970 | 1 | 2 |
_tChapter 4 ethics and information security, _p101. |
970 | 1 | 2 |
_tOpening case: sarbane-oxley: where information technology, finance, and ethics meet, _p102. |
970 | 0 | 1 |
_aIntroduction, _p104. |
970 | 1 | 2 |
_tSection 4.1 ethics, _p104. |
970 | 1 | 2 |
_tEthics, _p104. |
970 | 1 | 2 |
_tInformation ethics, _p105. |
970 | 1 | 1 |
_tInformation has no ethics, _p106. |
970 | 1 | 2 |
_tDeveloping information management policies, _p108. |
970 | 1 | 1 |
_tEthical computer use policy, _p108. |
970 | 1 | 1 |
_tInformation privacy policy, _p109. |
970 | 1 | 1 |
_tAcceptable use policy, _p109. |
970 | 1 | 1 |
_tE-mail privacy policy, _p109. |
970 | 1 | 1 |
_tInternet use policy, _p111. |
970 | 1 | 1 |
_tAnti-spam policy, _p112. |
970 | 1 | 2 |
_tEthics in the workplace, _p113. |
970 | 1 | 1 |
_tMonitoring technologies, _p113. |
970 | 1 | 1 |
_tEmployee monitoring policies, _p114. |
970 | 1 | 2 |
_tSection 4.2 information security, _p115. |
970 | 1 | 2 |
_tProtecting intellectual assets, _p116. |
970 | 1 | 2 |
_tThe first line of defense-people, _p117. |
970 | 1 | 2 |
_tThe second line of defense-technology, _p121. |
970 | 1 | 1 |
_tAuthentication and authorization, _p121. |
970 | 1 | 1 |
_tPrevention and resistance, _p122. |
970 | 1 | 1 |
_tContent filtering, _p123. |
970 | 1 | 1 |
_tEncyrption, _p124. |
970 | 1 | 1 |
_tFirewalls, _p124. |
970 | 1 | 1 |
_tDetection and response, _p125. |
970 | 0 | 1 |
_aKey terms, _p128. |
970 | 1 | 2 |
_tClosing case one: banks banking on security, _p129. |
970 | 1 | 2 |
_tClosing case two: hacker hunters, _p131. |
970 | 1 | 2 |
_tClosing case three: thinking like the enemy, _p133. |
970 | 1 | 2 |
_tMaking business decisions, _p134. |
970 | 1 | 2 |
_tChapter 5 IT Architectures, _p136. |
970 | 1 | 2 |
_tOpening case: electronic breaking points, _p137. |
970 | 0 | 1 |
_aIntroduction, _p140. |
970 | 1 | 2 |
_tSection 5.1 hardware and software basics, _p140. |
970 | 1 | 2 |
_tHardware basics, _p140. |
970 | 1 | 1 |
_tCentral processing unit, _p140. |
970 | 1 | 1 |
_tPrimary storage, _p143. |
970 | 1 | 1 |
_tSecondary storage, _p144. |
970 | 1 | 1 |
_tInput devices, _p145. |
970 | 1 | 1 |
_tOutput devices, _p147. |
970 | 1 | 1 |
_tCommunication devices, _p148. |
970 | 1 | 2 |
_tComputer categories, _p148. |
970 | 1 | 2 |
_tSoftware basics, _p149. |
970 | 1 | 1 |
_tSystem software, _p149. |
970 | 1 | 1 |
_tApplication software, _p151. |
970 | 1 | 2 |
_tSection 5.2 managing enterprise architectures, _p152. |
970 | 1 | 2 |
_tEnterprise architectures, _p152. |
970 | 1 | 2 |
_tInformation architecture, _p154. |
970 | 1 | 1 |
_tBackup and recovery, _p155. |
970 | 1 | 1 |
_tDisaster recovery, _p155. |
970 | 1 | 1 |
_tInformation security, _p157. |
970 | 1 | 2 |
_tInfrastructure architecture, _p158. |
970 | 1 | 2 |
_tEnterprise architectures, _p152. |
970 | 1 | 2 |
_tInformation architectyre, _p154. |
970 | 1 | 1 |
_tFlexibility, _p158. |
970 | 1 | 1 |
_tScalability, _p159. |
970 | 1 | 1 |
_tReliability, _p159. |
970 | 1 | 1 |
_tAvailability, _p159. |
970 | 1 | 1 |
_tPerformance, _p160. |
970 | 1 | 2 |
_tApplication architecture, _p160. |
970 | 1 | 1 |
_tWeb services, _p160. |
970 | 1 | 1 |
_tOpen systems, _p162. |
970 | 0 | 1 |
_aKey terms, _p163. |
970 | 1 | 2 |
_tClosing case one: Chicago tribune's server consolidation a success, _p164. |
970 | 1 | 2 |
_tClosing case two: UPS in the computer repair business, _p166. |
970 | 1 | 2 |
_tClosing case three: fear the penguin, _p167. |
970 | 1 | 1 |
_tMaking business decisions, _p169. |
970 | 1 | 2 |
_tChapter 6 databases and data warehouses, _p171. |
970 | 1 | 2 |
_tOpening case: searching for revenue-google, _p172. |
970 | 0 | 1 |
_aIntroduction, _p176. |
970 | 1 | 2 |
_tSection 6.1 database fundamentals, _p176. |
970 | 1 | 2 |
_tUnderstanding information, _p176. |
970 | 1 | 1 |
_tInformation quality, _p177. |
970 | 1 | 2 |
_tDatabase fundamentals, _p180. |
970 | 1 | 2 |
_tDatabase advantages, _p180. |
970 | 1 | 1 |
_tIncreased flexibility, _p181. |
970 | 1 | 1 |
_tIncreased scalability and performance, _p181. |
970 | 1 | 1 |
_tReduced redundancy, _p181. |
970 | 1 | 1 |
_tIncreased integrity (quality), _p181. |
970 | 1 | 1 |
_tIncreased security, _p182. |
970 | 1 | 2 |
_tRelational database fundamentals, _p182. |
970 | 1 | 1 |
_tEntities, entity classes, and attributes, _p183. |
970 | 1 | 1 |
_tKeys and relationships, _p183. |
970 | 1 | 2 |
_tDatabase management systems, _p183. |
970 | 1 | 1 |
_tData definition component, _p185. |
970 | 1 | 1 |
_tData manipulation component, _p186. |
970 | 1 | 1 |
_tApplication generation and data administration components, _p188. |
970 | 1 | 2 |
_tIntegrating data among multiple databases, _p189. |
970 | 1 | 2 |
_tSection 6.2 data warehouse fundamentals, _p191. |
970 | 1 | 2 |
_tAccessing organizational information, _p191. |
970 | 1 | 2 |
_tHistory of data warehousing, _p191. |
970 | 1 | 2 |
_tData warehouse fundamentals, _p192. |
970 | 1 | 1 |
_tMultidimensional analysis, _p193. |
970 | 1 | 1 |
_tInformation cleansing or scrubbing, _p194. |
970 | 1 | 2 |
_tBusiness intelligence, _p196. |
970 | 1 | 1 |
_tEnabling business intelligence, _p197. |
970 | 1 | 2 |
_tData mining, _p197. |
970 | 1 | 1 |
_tCluster analysis, _p198. |
970 | 1 | 1 |
_tAssociation detection, _p199. |
970 | 1 | 1 |
_tStatistical analysis, _p199. |
970 | 0 | 1 |
_aKey terms, _p202. |
970 | 1 | 2 |
_tClosing case one: fishing for quality, _p203. |
970 | 1 | 2 |
_tClosing case two: mining the data warehouse, _p205. |
970 | 1 | 2 |
_tClosing case three: Harrah's-gambling big on technology, _p207. |
970 | 1 | 2 |
_tMaking business decisions, _p209. |
970 | 1 | 2 |
_tChapter 7 networks, telecommunications, and wireless computing, _p212. |
970 | 1 | 2 |
_tOpening case: the digital hospital, _p213. |
970 | 0 | 1 |
_aIntroduction, _p215. |
970 | 1 | 2 |
_tSection 7.1 networks and telecommunications, _p215. |
970 | 1 | 2 |
_tNetwork basics, _p215. |
970 | 1 | 2 |
_tArchitecture, _p215. |
970 | 1 | 1 |
_tPeer-to-peer networks, _p215. |
970 | 1 | 1 |
_tClient/server networks, _p217. |
970 | 1 | 2 |
_tTopology, _p218. |
970 | 1 | 2 |
_tProtocols, _p220. |
970 | 1 | 1 |
_tEthernet, _p220. |
970 | 1 | 1 |
_tTransmission control protocol/internet protocol, _p221. |
970 | 1 | 2 |
_tMedia, _p223. |
970 | 1 | 1 |
_tWire media, _p223. |
970 | 1 | 1 |
_tWireless media, _p224. |
970 | 1 | 2 |
_tE-business networks, _p225. |
970 | 1 | 2 |
_tSection 7.2 wireless computing, _p226. |
970 | 1 | 2 |
_tWireless fidelity, _p227. |
970 | 1 | 1 |
_tThe value of timely information, _p227. |
970 | 1 | 2 |
_tBusiness drivers for wireless technologies, _p228. |
970 | 1 | 2 |
_tAdvantages of enterprise mobility, _p229. |
970 | 1 | 1 |
_tBluetooth, _p230. |
970 | 1 | 1 |
_tRadio frequency identification (RFID), _p231. |
970 | 1 | 1 |
_tSatelite, _p232. |
970 | 1 | 1 |
_tGlobal positioning system (GPS), _p233. |
970 | 1 | 2 |
_tThe future of wireless, _p234. |
970 | 0 | 1 |
_aKey terms, _p236. |
970 | 1 | 2 |
_tClosing case one: tracking students, _p237. |
970 | 1 | 2 |
_tClosing case two: UPS versus FedEx: head-to-head on wireless, _p238. |
970 | 1 | 2 |
_tClosing case three: watching where you step-prada, _p240. |
970 | 1 | 2 |
_tMaking business decisions, _p241. |
970 | 1 | 2 |
_tChapter 8 supply chain management, _p243. |
970 | 1 | 2 |
_tOpening case: Dell's famous supply chain, _p244. |
970 | 0 | 1 |
_aIntroduction, _p246. |
970 | 1 | 2 |
_tSection 8.1 supply chain fundamentals, _p246. |
970 | 1 | 2 |
_tBasics of supply chain, _p246. |
970 | 1 | 2 |
_tInformation technology's role in the supply chain, _p247. |
970 | 1 | 1 |
_tVisibility, _p250. |
970 | 1 | 1 |
_tConsumer behavior, _p250. |
970 | 1 | 1 |
_tCompetition, _p250. |
970 | 1 | 1 |
_tSpeed, _p251. |
970 | 1 | 2 |
_tSupply chain management success factors, _p251. |
970 | 1 | 1 |
_tMake the sale to suppliers, _p253. |
970 | 1 | 1 |
_tWean employees off traditional business practices, _p253. |
970 | 1 | 1 |
_tEnsure the SCM system supports the organizational goals, _p253. |
970 | 1 | 1 |
_tDeploy in incremental phases and measure and communicate success, _p253. |
970 | 1 | 1 |
_tCommunicate success, _p253. |
970 | 1 | 1 |
_tBe future oriented, _p253. |
970 | 1 | 2 |
_tSCM success stories, _p253. |
970 | 1 | 2 |
_tSection 8.2 applying a supply chain design, _p255. |
970 | 1 | 2 |
_tUsing information technology to drive the supply chain, _p255. |
970 | 1 | 1 |
_tFacilties driver, _p255. |
970 | 1 | 1 |
_tLocation, _p256. |
970 | 1 | 1 |
_tCapacity, _p256. |
970 | 1 | 1 |
_tOperational design, _p257. |
970 | 1 | 2 |
_tInventory driver, _p257. |
970 | 1 | 1 |
_tCycle information, _p257. |
970 | 1 | 1 |
_tSafety information, _p257. |
970 | 1 | 2 |
_tTransportation driver, _p259. |
970 | 1 | 1 |
_tMethod of transportation, _p259. |
970 | 1 | 1 |
_tPush versus pull information strategy, _p260. |
970 | 1 | 2 |
_tApplying a supply chain design, _p261. |
970 | 1 | 2 |
_tFuture supply chain trends, _p261. |
970 | 0 | 1 |
_aKey terms, _p264. |
970 | 1 | 2 |
_tClosing case one: BudNet, _p265. |
970 | 1 | 2 |
_tClosing case two: listerine's journey, _p267. |
970 | 1 | 2 |
_tClosing case three: the ritz-carlton--specializing in customers, _p298. |
970 | 1 | 2 |
_tMaking business decisions, _p299. |
970 | 1 | 2 |
_tChapter 10 enterprise resource planning and collaboration systems, _p301. |
970 | 1 | 2 |
_tOpening case: campus ERP, _p302. |
970 | 0 | 1 |
_aIntroduction, _p304. |
970 | 1 | 2 |
_aSection 10.1 enterprise resource planning, _p304. |
970 | 1 | 2 |
_tEnterprise resource planning, _p304. |
970 | 1 | 2 |
_tCore and extended erp components, _p305. |
970 | 1 | 2 |
_tCore ERP components, _p305. |
970 | 1 | 1 |
_tAccounting and finance ERP components, _p305. |
970 | 1 | 1 |
_tProduction and materials management ERP components, _p306. |
970 | 1 | 1 |
_tHuman resources ERP components, _p307. |
970 | 1 | 2 |
_tExtended ERP components, _p307. |
970 | 1 | 1 |
_tBusiness intelligence components, _p308. |
970 | 1 | 1 |
_tCustomer relationship management components, _p308. |
970 | 1 | 1 |
_tSupply chain management components, _p308. |
970 | 1 | 1 |
_tE-business components, _p308. |
970 | 1 | 2 |
_tERP vendor overview, _p309. |
970 | 1 | 1 |
_tERP software, _p311. |
970 | 1 | 1 |
_tFinding the right ERP solution, _p311. |
970 | 1 | 2 |
_tERP benefits and risks (cost), _p312. |
970 | 1 | 2 |
_tThe connected corporation-integrating SCM, CRM, and ERP, _p312. |
970 | 1 | 2 |
_tThe future of ERP, _p316. |
970 | 1 | 1 |
_tInternet, _p317. |
970 | 1 | 1 |
_tInterface, _p318. |
970 | 1 | 1 |
_tWireless techology, _p318. |
970 | 1 | 2 |
_tSection 10.2 collaboration systems, _p318. |
970 | 1 | 2 |
_tTeams, partnerships, and alliances, _p318. |
970 | 1 | 2 |
_tCollaboration systems, _p320. |
970 | 1 | 2 |
_tKnowledge management, _p322. |
970 | 1 | 1 |
_tKM in business, _p322. |
970 | 1 | 2 |
_tKnowledge management systems, _p322. |
970 | 1 | 1 |
_tExplicit and tacit knowledge, _p323. |
970 | 1 | 1 |
_tKM Technologies, _p324. |
970 | 1 | 1 |
_tKM and social networking, _p325. |
970 | 1 | 2 |
_tContent management systems, _p325. |
970 | 1 | 2 |
_tWorkflow management systems, _p326. |
970 | 1 | 2 |
_tGroupware systems, _p328. |
970 | 0 | 1 |
_aKey terms, _p331. |
970 | 1 | 2 |
_tClosing case one: dreamworks animation collaboration, _p332. |
970 | 1 | 2 |
_tClosing case two: improving highway safety through collaboration, _p334. |
970 | 1 | 2 |
_tClosing case three: saving costs and costco, _p336. |
970 | 1 | 2 |
_tMaking business decisions, _p337. |
970 | 1 | 2 |
_tChapter 11 systems development, _p339. |
970 | 1 | 2 |
_tOpening case: HP's software problems, _p340. |
970 | 0 | 1 |
_aIntroduction, _p342. |
970 | 1 | 2 |
_tSection 11.1 developing enterprise applications, _p342. |
970 | 1 | 2 |
_tDeveloping software, _p342. |
970 | 1 | 2 |
_tThe systems development life cycle (SDLC), _p343. |
970 | 1 | 2 |
_tSoftware development methodologies, _p344. |
970 | 1 | 1 |
_tWaterfall methodology, _p344. |
970 | 1 | 1 |
_tRapid application development methodology (RAD), _p345. |
970 | 1 | 1 |
_tExtreme programming methodology, _p346. |
970 | 1 | 1 |
_tAgile methodology, _p347. |
970 | 1 | 2 |
_tDeveloping succesful software, _p348. |
970 | 1 | 1 |
_tSlash the budget, _p348. |
970 | 1 | 1 |
_tIf it doesn't work, kill it, _p348. |
970 | 1 | 1 |
_tKeep reguirements to a minimum, _p348. |
970 | 1 | 1 |
_tTest and deliver frequently, _p348. |
970 | 1 | 1 |
_tAssign non-IT executives to software projects, _p348. |
970 | 1 | 1 |
_tSection 11.2 the systems development life cycle (SDLC), _p349. |
970 | 1 | 2 |
_tSystems development life cycle, _p349. |
970 | 1 | 2 |
_tPhase 1: planning, _p349. |
970 | 1 | 1 |
_tIdentify and select the system for development, _p350. |
970 | 1 | 1 |
_tAssess project feasibility, _p351. |
970 | 1 | 1 |
_tDevelop the project plan, _p351. |
970 | 1 | 2 |
_tPhase 2: analysis., _p352. |
970 | 1 | 1 |
_tGather business reguirements, _p352. |
970 | 1 | 1 |
_tCreate process diagrams, _p352. |
970 | 1 | 1 |
_tPerform a buy versus build analysis, _p353. |
970 | 1 | 2 |
_tPhase 3: design, _p354. |
970 | 1 | 1 |
_tDesign the IT infrastructure, _p354. |
970 | 1 | 1 |
_tDesign system models, _p354. |
970 | 1 | 2 |
_tPhase 4: development, _p355. |
970 | 1 | 1 |
_tDevelop the IT infrastructure, _p355. |
970 | 1 | 1 |
_tDevelop the database and programs, _p356. |
970 | 1 | 2 |
_tPhase 5: testing, _p357. |
970 | 1 | 1 |
_tWrite in the test conditions, _p357. |
970 | 1 | 1 |
_tPerform the system testing, _p358. |
970 | 1 | 2 |
_tPhase 6: implementation, _p358. |
970 | 1 | 1 |
_tWrite detailed user documentation, _p358. |
970 | 1 | 1 |
_tDetermine implementation method, _p358. |
970 | 1 | 1 |
_tProvide trainning for the system users, _p359. |
970 | 1 | 2 |
_tPhase 7: maintenance, _p359. |
970 | 1 | 1 |
_tBuild a help desk to support the system users, _p359. |
970 | 1 | 1 |
_tPerform system maintenance, _p359. |
970 | 1 | 1 |
_tProvide an environment to support system changes, _p360. |
970 | 1 | 2 |
_tSoftware problems are business problems, _p360. |
970 | 1 | 1 |
_tUnclear or missing business requirements, _p360. |
970 | 1 | 1 |
_tSkipping SDLC phases, _p360. |
970 | 1 | 1 |
_tFailure to manage project scope, _p361. |
970 | 1 | 1 |
_tFailure to manage project plan, _p361. |
970 | 1 | 1 |
_tChanging technology, _p361. |
970 | 0 | 1 |
_aKey terms, _p363. |
970 | 1 | 2 |
_tClosing case one: disaster at denver international airport, _p364. |
970 | 1 | 2 |
_tClosing case two: reducing ambiguity in business reguirements, _p365. |
970 | 1 | 2 |
_tClosing case three: gearing up at REI, _p367. |
970 | 1 | 2 |
_tMaking business decisions, _p369. |
970 | 1 | 2 |
_tChapter 12 project management and outsourcing, _p371. |
970 | 1 | 2 |
_tOpening case: change at toyota, _p372. |
970 | 0 | 1 |
_aIntroduction, _p375. |
970 | 1 | 2 |
_tSection 12.1 project management, _p375. |
970 | 1 | 2 |
_tProject management, _p375. |
970 | 1 | 2 |
_tProject management fundamentals, _p377. |
970 | 1 | 1 |
_tChoosing strategic projects, _p378. |
970 | 1 | 1 |
_tSetting the project scope, _p379. |
970 | 1 | 1 |
_tManaging resources and maintaining the project plan, _p380. |
970 | 1 | 2 |
_tChange management fundamentals, _p381. |
970 | 1 | 1 |
_tPreparing for change, _p383. |
970 | 1 | 2 |
_tRisk management fundamentals, _p383. |
970 | 1 | 1 |
_tMitigating risk, _p384. |
970 | 1 | 1 |
_tSuccesful project management strategies, _p385. |
970 | 1 | 2 |
_tSection 12.2 outsourcing, _p386. |
970 | 1 | 2 |
_tOutsourcing, _p386. |
970 | 1 | 2 |
_tThe outsourcing phenomenon, _p388. |
970 | 1 | 1 |
_tOutsourcing benefits, _p389. |
970 | 1 | 2 |
_tOutsourcing options, _p390. |
970 | 1 | 2 |
_tOffshore outsourcing, _p390. |
970 | 1 | 1 |
_tThe leaders, _p391. |
970 | 1 | 1 |
_tThe up-and-conners, _p393. |
970 | 1 | 1 |
_tThe rookies, _p395. |
970 | 1 | 2 |
_tThe challenges of outsourcing, _p396. |
970 | 1 | 2 |
_tFuture outsourcing trends, _p398. |
970 | 0 | 1 |
_aKey terms, _p399. |
970 | 1 | 2 |
_tClosing case one: staying on track-Toronto transit, _p400. |
970 | 1 | 2 |
_tClosing case two: changing circuits and circuit city, _p401. |
970 | 1 | 2 |
_tClosing case three: outsourcing brew, _p403. |
970 | 1 | 2 |
_tMaking business decisions, _p404. |
970 | 1 | 2 |
_tTechnology plug-in overview, _p406. |
970 | 1 | 2 |
_tApply your knowledge, _p410. |
970 | 0 | 1 |
_aNotes, _p450. |
970 | 0 | 1 |
_aGlossary, _p457. |
970 | 0 | 1 |
_aPhoto credits, _p471. |
970 | 0 | 1 |
_aIndex, _p473. |
999 |
_c11437 _d11437 |
||
003 | KOHA |