Course资讯系统的规划与开发

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

2、程n確定組織狀況的描述架構n確定目前的組織狀況與資源n預測環境因素的未來變化n確定所期待的未來組織狀況n確定規劃模式n作出計劃資訊管理 / Course 35資訊系統規劃的意義n資訊系統規劃的工作n預期變化、可能產生的問題、目標n預先考慮資訊科技的整合問題、資訊科技架構n訂定各項配合工作的 schedule、人力與財力n誰來做資訊系統的規劃？n資訊部門主管資訊部門主管n資訊部門專職規劃人員n資訊部門組成臨時規劃小組n各部門派表表組成臨時規劃小組實際擔任規劃的人員資訊管理 / Course 36資訊系統規劃的內涵n目的n描繪組織如何使用資訊科技來創造價值，並作為資源分配及控制之基礎n分類n長程規

3、劃：指出大方針n短程規劃：研擬作業項目及績效衡量方法n產出nMIS 主計劃資訊管理 / Course 37管理資訊系統主計劃n資訊系統的總目標、細部目標、資訊科技架構總目標：指引資訊系統的走向細部目標：考核資訊系統績效的依據n現有資源的分析n預測未來資訊科技環境的發展科技產品的生命週期 (出現、矯正、成長、早期成熟、成熟、改進、衰退) * Moore Law預測資訊科技時應注意的科技 (目前)n細項計劃n主計劃的更新資訊管理 / Course 38資訊系統規劃理論n組織資訊系統規劃重點n資訊科技基礎建設 () 的建構 n企業策略與資訊科技策略間的調準 (alignment)n策略與資訊科技必須

4、適合相同的經營模式nStrategic Alignment 相關概念nVictor et al. 產品流程變化矩陣 ：找出企業經營模式nHenderson 的策略調準模型：內外部的適配程度nMcFarlan-McKenney策略方格：判定企業應用資訊科技目前的定位與未來的走向資訊管理 / Course 39產品流程變化矩陣大量客製化大量生產發 明持續改良關 係任 務自動化增補化產品改變流 程 改 變穩 定動 態穩定動態資訊管理 / Course 310Henderson 調準模型n外在領域n企業在資訊科技市場的地位n企業競爭的範圍n內在領域n資訊科技基礎建設 & 流程的組態及管理n管理

5、結構、關鍵企業流程的再設計、人力資源技能的取得及發展資訊管理 / Course 311Henderson 調準模型 (cont.)n企業策略驅動企業變革n策略執行觀點n技術轉型觀點n資訊科技推動企業變革n競爭潛力觀點n服務等級觀點資訊管理 / Course 312策略方格支援型(Support)工廠型(Factory)扭轉型(Turnarround)策略型(Strategic)規劃中資訊系統對策略的影響目前資訊系統對策略的影響低高低高 支援傳統資料處理應用和公司整體計劃幾無關連 影響企業活動的運作 著重現有資訊科技基礎建設 影響現有和未來的競爭策略 公司規劃和資訊系統規劃整合 與策略型大致類似

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

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

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

9、 CSF 的作法n列出企業策略目標n決定達成策略目的關鍵因素n決定衡量關鍵因素的績效比率資訊管理 / Course 320資源分配n比較與成本效益n以投資報酬率評估n應用系統組合n將各個子系統視為一個整體進行評估n依風險與策略性方向n內部計價n將資訊系統成本分攤給使用者n指導委員會決定資訊管理 / Course 321資訊系統規劃的關鍵議題n集中或分散n小型化n企業流程改造n陳舊系統的管理n浮現中新技術的管理n跨組織資訊系統、使用者自建系統n電子商務資訊管理 / Course 322資訊系統開發的過程n初步設計 (可行性分析)n分析經濟可行性、技術可行性、作業可行性n系統分析n規範系統需求 (

10、資訊、組織、控制、機器設備)n系統設計n定義系統規格 (程式規格 + 作業程序規格)n系統發展n編寫電腦程式與設計人工作業程序 + 程式測試n系統推行資訊管理 / Course 323資訊系統開發的概念與技術n50 70 年代n使用結構化系統設計方法n著重在系統開發的初期工作n80 年代n使用 4GL 之雛型系統 (prototype) 設計方法n使用者自建系統n90 年代n物件導向技術 (Object-Oriented)n網際網路應用系統開發工具n強調快速的資訊系統開發方法n大型整合應用系統資訊管理 / 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 物件導向式的資訊物件導向式的資訊系統開發系統開發n模型是將一個系統從特定角度來作完整的

32、描繪模型是將一個系統從特定角度來作完整的描繪Use CaseDiagramsUse CaseDiagramsUse CaseDiagramsScenarioDiagramsScenarioDiagramsCollaborationDiagramsStateDiagramsStateDiagramsComponentDiagramsComponentDiagramsComponentDiagramsDeploymentDiagramsStateDiagramsStateDiagramsObjectDiagramsScenarioDiagramsScenarioDiagramsStatechart

33、DiagramsUse CaseDiagramsUse CaseDiagramsSequenceDiagramsStateDiagramsStateDiagramsClassDiagramsActivityDiagramsModels資訊管理 / Course 351Class Diagramn描繪系統的系統信息之傳遞Object Diagramn描繪物件及其關聯Component Diagramn描繪實際建置的實體結構Use Case Diagramn以使用者角度來描繪系功能Deployment Diagramn描繪系統硬體架構的拓樸資訊管理 / Course 352Sequence Dia

34、gramn描繪動態隨機的行為 (時程導向)Collaboration Diagramn描繪動態隨機的行為 (訊息導向)Statechart Diagramn描繪動態隨機的行為(事件導向)Activity Diagramn描繪動態隨機的行為(活動導向)資訊管理 / 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