Course資訊系統(tǒng)的規(guī)劃與開發(fā)

1、資訊管理 / Course 31Course 3資訊系統(tǒng)的規(guī)劃與開發(fā)資訊系統(tǒng)的規(guī)劃與開發(fā)李鍾斌資訊管理 / Course 32Outlinen何謂規(guī)劃活動(dòng)？n資訊系統(tǒng)規(guī)劃n內(nèi)涵n規(guī)劃理論n過程、方法與關(guān)鍵議題n資訊系統(tǒng)發(fā)展n資訊系統(tǒng)開發(fā)過程n資訊系統(tǒng)開發(fā)的概念與技術(shù)n資訊系統(tǒng)開發(fā)的管理問題資訊管理 / Course 33規(guī)劃活動(dòng)的基本概念組織狀況(目前)目前)組織狀況組織狀況組織狀況(目前+1)(目前+2)組織狀況(目前+3)(期待)(期待)活動(dòng) 1資源 1活動(dòng) 2資源 2活動(dòng) 3資源 3活動(dòng) n資源 n3未來導(dǎo)向資源分配導(dǎo)向隨時(shí)修正環(huán)境影響具操作困難性資訊管理 / Course 34規(guī)劃的過

2、程n確定組織狀況的描述架構(gòu)n確定目前的組織狀況與資源n預(yù)測環(huán)境因素的未來變化n確定所期待的未來組織狀況n確定規(guī)劃模式n作出計(jì)劃資訊管理 / Course 35資訊系統(tǒng)規(guī)劃的意義n資訊系統(tǒng)規(guī)劃的工作n預(yù)期變化、可能產(chǎn)生的問題、目標(biāo)n預(yù)先考慮資訊科技的整合問題、資訊科技架構(gòu)n訂定各項(xiàng)配合工作的 schedule、人力與財(cái)力n誰來做資訊系統(tǒng)的規(guī)劃？n資訊部門主管資訊部門主管n資訊部門專職規(guī)劃人員n資訊部門組成臨時(shí)規(guī)劃小組n各部門派表表組成臨時(shí)規(guī)劃小組實(shí)際擔(dān)任規(guī)劃的人員資訊管理 / Course 36資訊系統(tǒng)規(guī)劃的內(nèi)涵n目的n描繪組織如何使用資訊科技來創(chuàng)造價(jià)值，並作為資源分配及控制之基礎(chǔ)n分類n長程規(guī)

3、劃：指出大方針n短程規(guī)劃：研擬作業(yè)項(xiàng)目及績效衡量方法n產(chǎn)出nMIS 主計(jì)劃資訊管理 / Course 37管理資訊系統(tǒng)主計(jì)劃n資訊系統(tǒng)的總目標(biāo)、細(xì)部目標(biāo)、資訊科技架構(gòu)總目標(biāo)：指引資訊系統(tǒng)的走向細(xì)部目標(biāo)：考核資訊系統(tǒng)績效的依據(jù)n現(xiàn)有資源的分析n預(yù)測未來資訊科技環(huán)境的發(fā)展科技產(chǎn)品的生命週期 (出現(xiàn)、矯正、成長、早期成熟、成熟、改進(jìn)、衰退) * Moore Law預(yù)測資訊科技時(shí)應(yīng)注意的科技 (目前)n細(xì)項(xiàng)計(jì)劃n主計(jì)劃的更新資訊管理 / Course 38資訊系統(tǒng)規(guī)劃理論n組織資訊系統(tǒng)規(guī)劃重點(diǎn)n資訊科技基礎(chǔ)建設(shè) () 的建構(gòu) n企業(yè)策略與資訊科技策略間的調(diào)準(zhǔn) (alignment)n策略與資訊科技必須

4、適合相同的經(jīng)營模式nStrategic Alignment 相關(guān)概念nVictor et al. 產(chǎn)品流程變化矩陣 ：找出企業(yè)經(jīng)營模式nHenderson 的策略調(diào)準(zhǔn)模型：內(nèi)外部的適配程度nMcFarlan-McKenney策略方格：判定企業(yè)應(yīng)用資訊科技目前的定位與未來的走向資訊管理 / Course 39產(chǎn)品流程變化矩陣大量客製化大量生產(chǎn)發(fā) 明持續(xù)改良關(guān) 係任 務(wù)自動(dòng)化增補(bǔ)化產(chǎn)品改變流 程 改 變穩(wěn) 定動(dòng) 態(tài)穩(wěn)定動(dòng)態(tài)資訊管理 / Course 310Henderson 調(diào)準(zhǔn)模型n外在領(lǐng)域n企業(yè)在資訊科技市場的地位n企業(yè)競爭的範(fàn)圍n內(nèi)在領(lǐng)域n資訊科技基礎(chǔ)建設(shè) & 流程的組態(tài)及管理n管理

5、結(jié)構(gòu)、關(guān)鍵企業(yè)流程的再設(shè)計(jì)、人力資源技能的取得及發(fā)展資訊管理 / Course 311Henderson 調(diào)準(zhǔn)模型 (cont.)n企業(yè)策略驅(qū)動(dòng)企業(yè)變革n策略執(zhí)行觀點(diǎn)n技術(shù)轉(zhuǎn)型觀點(diǎn)n資訊科技推動(dòng)企業(yè)變革n競爭潛力觀點(diǎn)n服務(wù)等級(jí)觀點(diǎn)資訊管理 / Course 312策略方格支援型(Support)工廠型(Factory)扭轉(zhuǎn)型(Turnarround)策略型(Strategic)規(guī)劃中資訊系統(tǒng)對策略的影響目前資訊系統(tǒng)對策略的影響低高低高 支援傳統(tǒng)資料處理應(yīng)用和公司整體計(jì)劃幾無關(guān)連 影響企業(yè)活動(dòng)的運(yùn)作 著重現(xiàn)有資訊科技基礎(chǔ)建設(shè) 影響現(xiàn)有和未來的競爭策略 公司規(guī)劃和資訊系統(tǒng)規(guī)劃整合 與策略型大致類似

6、 高階主管參與較少資訊管理 / Course 313資訊系統(tǒng)規(guī)劃的過程與方法規(guī)劃活動(dòng)規(guī)劃活動(dòng)三階段三階段策略規(guī)劃組織資訊需求分析資源分配 先驅(qū)型公司 穩(wěn)健型公司 追隨型公司 資訊科技規(guī)劃方法 BSP ISP CSF 比較成本 / 利益 應(yīng)用系統(tǒng)組合 內(nèi)部計(jì)價(jià) 指導(dǎo)委員會(huì)評(píng)價(jià)方方法法SIP資訊管理 / Course 314策略規(guī)劃先驅(qū)型公司n塑造科技創(chuàng)新的組織文化n以資訊科技當(dāng)作競爭的武器n資訊科技策略與企業(yè)策略密切結(jié)合n設(shè)立推動(dòng)先進(jìn)科技小組n尋找達(dá)成目標(biāo)與解決問題的科技n企業(yè)高階主管 + 資訊管理專業(yè)人員n關(guān)係經(jīng)理n促使資訊部門和事業(yè)部門改善溝通並增加合作資訊管理 / Course 315策略

7、規(guī)劃穩(wěn)健型 & 追隨型公司n穩(wěn)健型n重視企業(yè)策略和資訊科技策的調(diào)準(zhǔn) (alignment)n策略規(guī)劃委員會(huì)n資訊部門 & 事業(yè)單位n共同制定資訊科技政n追隨型n以支援組織策略為主n依組織計(jì)劃中的目標(biāo)和策略訂定資訊科技的目標(biāo)和策略資訊管理 / Course 316策略規(guī)劃規(guī)劃方法n套用組織策略規(guī)劃方法n產(chǎn)業(yè)環(huán)境分析 Porter 五力競爭模式n目前的挑戰(zhàn)n資訊科技實(shí)力的分析n形成策略方案nHenderson & Rockart 策略資料模式與策略資訊系統(tǒng)規(guī)劃方法nWiseman 策略選擇產(chǎn)生器資訊管理 / Course 317資訊需求分析企業(yè)系統(tǒng)規(guī)劃(BSP)定義企業(yè)目標(biāo)

8、定義企業(yè)流程定義企業(yè)資料定義資訊架構(gòu)以企業(yè)流程為主軸找出企業(yè)的資訊需求 找出企業(yè)產(chǎn)品/服務(wù)及相關(guān)資源 定義產(chǎn)品/服務(wù)和資源相關(guān)的作業(yè)流程 找出管理流程 (規(guī)劃控制流程)資訊管理 / Course 318資訊需求分析策略資訊規(guī)劃(SIP)n(Martin)n將願(yuàn)景套入資訊系統(tǒng)，進(jìn)行策略規(guī)劃和分析n將分析的結(jié)果以個(gè)體關(guān)係模式表達(dá)n加入資訊科技，分析其對業(yè)務(wù)的影響n進(jìn)行關(guān)鍵成功因素之分析n分析問題與目的的因果關(guān)係n重新定義企業(yè)個(gè)體關(guān)係模式資訊管理 / Course 319資訊需求分析關(guān)鍵成功因素(CSF)nCritical Success Factor的來源n產(chǎn)業(yè)本身、環(huán)境、公司本身和組織因素n定義

9、 CSF 的作法n列出企業(yè)策略目標(biāo)n決定達(dá)成策略目的關(guān)鍵因素n決定衡量關(guān)鍵因素的績效比率資訊管理 / Course 320資源分配n比較與成本效益n以投資報(bào)酬率評(píng)估n應(yīng)用系統(tǒng)組合n將各個(gè)子系統(tǒng)視為一個(gè)整體進(jìn)行評(píng)估n依風(fēng)險(xiǎn)與策略性方向n內(nèi)部計(jì)價(jià)n將資訊系統(tǒng)成本分?jǐn)偨o使用者n指導(dǎo)委員會(huì)決定資訊管理 / Course 321資訊系統(tǒng)規(guī)劃的關(guān)鍵議題n集中或分散n小型化n企業(yè)流程改造n陳舊系統(tǒng)的管理n浮現(xiàn)中新技術(shù)的管理n跨組織資訊系統(tǒng)、使用者自建系統(tǒng)n電子商務(wù)資訊管理 / Course 322資訊系統(tǒng)開發(fā)的過程n初步設(shè)計(jì) (可行性分析)n分析經(jīng)濟(jì)可行性、技術(shù)可行性、作業(yè)可行性n系統(tǒng)分析n規(guī)範(fàn)系統(tǒng)需求 (

10、資訊、組織、控制、機(jī)器設(shè)備)n系統(tǒng)設(shè)計(jì)n定義系統(tǒng)規(guī)格 (程式規(guī)格 + 作業(yè)程序規(guī)格)n系統(tǒng)發(fā)展n編寫電腦程式與設(shè)計(jì)人工作業(yè)程序 + 程式測試n系統(tǒng)推行資訊管理 / Course 323資訊系統(tǒng)開發(fā)的概念與技術(shù)n50 70 年代n使用結(jié)構(gòu)化系統(tǒng)設(shè)計(jì)方法n著重在系統(tǒng)開發(fā)的初期工作n80 年代n使用 4GL 之雛型系統(tǒng) (prototype) 設(shè)計(jì)方法n使用者自建系統(tǒng)n90 年代n物件導(dǎo)向技術(shù) (Object-Oriented)n網(wǎng)際網(wǎng)路應(yīng)用系統(tǒng)開發(fā)工具n強(qiáng)調(diào)快速的資訊系統(tǒng)開發(fā)方法n大型整合應(yīng)用系統(tǒng)資訊管理 / Course 324THE SYSTEMS APPROACHnJohn Dewey id

11、entified three series of judgments involved in adequately resolving a controversynRecognize the controversynWeigh alternative claimsnForm a judgmentnDuring the late 1960s/early 1970s, interest in systematic problem solving strengthenednManagement scientists and information specialists produced a rec

12、ommended framework that became known as the systems approacha series of problem-solving steps that ensure the problem is first understood, alternative solutions are considered, and the selected solution works (Figure 7.1)資訊管理 / Course 325資訊管理 / Course 326The Systems Approach (cont.)nIf a manager can

13、 also regard the levels of management as subsystems, the importance of information flows becomes clearnA problem trigger a signal that things are going better/worse than planned usually stimulates a definition effort nA top-down analysis then begins of the system for which the manager is responsible

14、 nAs the manager studies each system level, the system elements are analyzed in sequence (Figure 7.3)資訊管理 / Course 327資訊管理 / Course 328資訊管理 / Course 329Steps towards a SolutionnIdentify Alternative SolutionsnEvaluate the Alternative SolutionsnSelecting the Best Solution Involves:nAnalysisnJudgment n

15、Bargaining nImplement the Solution nFollow Up to Ensure That the Solution Is Effective 資訊管理 / Course 330THE SYSTEMS DEVELOPMENT LIFE CYCLEnThe system development life cycle (SDLC) is an application of the systems approach methodology to the development of an information system 資訊管理 / Course 331THE T

16、RADITIONAL SDLCnIt didnt take the first system developers long to recognize a sequence if the project was to have the best chance of success:nPlanningnAnalysisnDesignnImplementationnUsenFigure 7.4 illustrates how the life cycle phases can fit into a circular pattern over time 資訊管理 / Course 332資訊管理 /

17、 Course 333PROTOTYPINGnA prototype is a version of a potential system that provides the developers and potential users with an idea of how the system will function when completednIn prototyping, a prototype is produced as quickly as possible, perhaps overnight, to obtain user feedback that will enab

18、le the prototype to be improvednFigure 7.5 shows the four steps involved in developing an evolutionary prototypenFigure 7.6 shows the steps involved in developing a requirements prototype nAs prototyping has proven to be one of the most successful methodologies, it would be difficult to find a devel

19、opment project that didnt use it to some degree 資訊管理 / Course 334資訊管理 / Course 335資訊管理 / Course 336RAPID APPLICATION DEVELOPMENTnRapid Application Development (RAD), is a term coined by James Martin. It refers to a development life cycle intended to produce systems quickly without sacrificing qualit

20、ynInformation engineering is the name that Martin gave to his overall approach to system development, which treats it as a firm-wide activity, while the term enterprise is used to describe the entire firmnFigure 7.7 illustrates the top-down nature of information engineering, involving both data (the

21、 left face of the pyramid) and activities (the right face) 資訊管理 / Course 337資訊管理 / Course 338RAD (cont.)nRAD requires four essential ingredients:nManagement nPeople nMethodologies nToolsnOf all the components of information engineering, RAD has probably enjoyed the greatest support 資訊管理 / Course 339

22、PHASED DEVELOPMENTnThis is an approach for developing information systems that consists of six stages: nPreliminary investigationnAnalysis nDesign nPreliminary constructionnFinal constructionnSystem test and installation nThe analysis, design, and preliminary construction stages are taken for each s

23、ystem modulenThe six phased development stages are illustrated in Figure 7.8 nFigure 7.9 illustrates how the module phases are integrated into the system development 資訊管理 / Course 340資訊管理 / Course 341資訊管理 / Course 342BUSINESS PROCESS REDESIGNnThe process of reworking the systems has been called reen

24、gineering or business process redesign (BPR) nBPR affects the firms IT operation in two ways:nIT can apply BPR to the redesign of legacy systems that can no longer be kept alive by ordinary maintenance nWhen a firm applies BPR to its major operations, the effort invariably has a ripple effect that r

25、esults in the redesign of information systems nIT has devised reverse engineering, restructuring, and reengineering that can be applied separately or in combination for applying BPR資訊管理 / Course 343Three Techniques for Applying BPR nAs used in computing, reverse engineering is the process of analyzi

26、ng an existing system to identify its elements and their interrelationships, as well as to create documentation in a higher level of abstraction than currently exists.nRestructuring is the transformation of a system into another form without changing its functionalitynReengineering is the complete r

27、edesign of a system with the objective of changing its functionality nThe proper mix depends on the current state of the system in terms of its functional and technical quality. Figure 7.10 is a diagram that shows these two influences資訊管理 / Course 344資訊管理 / Course 345PUTTING THE TRADITIONAL SDLC, PR

28、OTOTYPING, RAD, PHASEDDEVELOPMENT, AND BPR IN PERSPECTIVEnThe traditional SDLC, prototyping, RAD, and BPR are methodologies that are recommended ways of developing an information systemnCurrently, firms are revamping many systems that were implemented with computer technology that is now obsolete nT

29、he name BPR is used for this. Prototyping, RAD, and phased development can be utilized in a BPR project to meet users needs in a responsive way 資訊管理 / Course 346Process ModelingnAs developers perform analysis and design, they model the system data, processes, and objects nA data flow diagram (DFD) i

30、s a graphic representation of a system that uses four symbol shapes representing: (1) environmental elements with which the system interfaces, (2) processes, (3) data flows, and (4) storage of data to illustrate how data flows through interconnected processesnFigure 7.11 illustrates a DFD system tha

31、t a firm might use to compute commissions for its sales representativesnFigure 7.12 is a context diagram of the sales commission systemnFigure 7.13 shows a Figure 4 diagram 資訊管理 / Course 347資訊管理 / Course 348資訊管理 / Course 349資訊管理 / Course 350Object-Oriented 物件導(dǎo)向式的資訊物件導(dǎo)向式的資訊系統(tǒng)開發(fā)系統(tǒng)開發(fā)n模型是將一個(gè)系統(tǒng)從特定角度來作完整的

32、描繪模型是將一個(gè)系統(tǒng)從特定角度來作完整的描繪Use CaseDiagramsUse CaseDiagramsUse CaseDiagramsScenarioDiagramsScenarioDiagramsCollaborationDiagramsStateDiagramsStateDiagramsComponentDiagramsComponentDiagramsComponentDiagramsDeploymentDiagramsStateDiagramsStateDiagramsObjectDiagramsScenarioDiagramsScenarioDiagramsStatechart

33、DiagramsUse CaseDiagramsUse CaseDiagramsSequenceDiagramsStateDiagramsStateDiagramsClassDiagramsActivityDiagramsModels資訊管理 / Course 351Class Diagramn描繪系統(tǒng)的系統(tǒng)信息之傳遞Object Diagramn描繪物件及其關(guān)聯(lián)Component Diagramn描繪實(shí)際建置的實(shí)體結(jié)構(gòu)Use Case Diagramn以使用者角度來描繪系功能Deployment Diagramn描繪系統(tǒng)硬體架構(gòu)的拓樸資訊管理 / Course 352Sequence Dia

34、gramn描繪動(dòng)態(tài)隨機(jī)的行為 (時(shí)程導(dǎo)向)Collaboration Diagramn描繪動(dòng)態(tài)隨機(jī)的行為 (訊息導(dǎo)向)Statechart Diagramn描繪動(dòng)態(tài)隨機(jī)的行為(事件導(dǎo)向)Activity Diagramn描繪動(dòng)態(tài)隨機(jī)的行為(活動(dòng)導(dǎo)向)資訊管理 / Course 353nToday, it is possible for life cycle management to span several organizational levels and involve managers outside of IT nFigure 7.16 shows the hierarchical

35、nature of project management nIn this example, there are five development projects going at the same time, all managed by the MIS steering committee PROJECT MANAGEMENT資訊管理 / Course 354資訊管理 / Course 355The MIS Steering Committee nThe MIS Steering Committee performs three main functions:nIt establishes policies that ensure computer support for achieving the strategic objectives of the firmnIt provides fiscal control by