系統分析與設計方法之研究－建構以職務概念為核心之資訊系統

Abstract

隨著網際網路興起，使得資訊傳遞已跨越時空的限制。使用者透過網路接觸到的資訊多如牛毛，過去資訊不足的問題，已轉為資訊過多，企業主管及組織內部人員對於如何取得有用的資訊都充滿著無力感。除此之外，企業中的員工因人事的變動而升遷或離職，使得所建立的資訊常會隨之煙消雲散或不易再被利用，且甚至會造成下一個接棒的人需要一段很長的摸索期，方能順利地進入工作狀況，而這些資訊往往是前人工作累積所得之經驗智慧。 由此得知，企業內各人員職務所隱含的資訊，是非常重要的。它不只是企業有價的無形資產，更是企業競爭力的泉源。因此，企業資訊系統的發展將勢必以「人員職務概念為核心」觀點來進行，以使得組織的人員可適時適地取得所需的資訊，來協助達成企業的目標。 因此，本研究試圖提出一套系統分析與設計方法，以提供企業做為其建置以職務概念為核心之資訊系統的參考指引。同時，採用了目前最新一代物件導向(Object-oriented)技術－統一塑模語言(Unified Modeling Language，UML)，做各階段資訊表達工具。而此套系統分析與設計方法共分成三個階段，第一個階段，需求分析，主要的目的在找出使用者的需求，也就是要確立出建置的範圍，並建構出使用案例。第二個階段，系統分析，則是分析出職務與工作間、工作與系統功能間及系統功能與元件間的關係，以便進行系統設計的工作。第三個階段，系統設計，則是進行系統功能及職務系統功能集的設計。

Due to the thriving development of the Internet, the circulation of information is no longer bound by distance and time. The information we may access on the Internet nowadays is actually excessive compared to the insufficiency used to happen in the past. The executives and staff in some corporations have troubles retrieving useful information. Besides, the established information might be irretrievable or unusable because of the employment changes, such as being promoted or leaving the post. And the consequences of this matter may result in the time-consuming replacement efforts. What makes this kind of information so important is that it is the accumulation of working experiences and wisdom. The information stays behind the employees is fairly important. It is not only invisible valuable assets, but also the foundation of competitiveness for corporations. Therefore, the development of a corporation information system should be based on “Role Concept” of the employees. So that the employees would be able to retrieve the information they need efficiently and accomplish the objective for the corporation. This thesis is intended to propose a system analysis and design methodology, which is the guideline for a corporation establishing an information system based on “Role Concept”. The object-oriented technology, UML (Uniform Modeling Language), is adopted as the tool for presenting the information of various phases. The system analysis and design methodology demonstrated here has three phases. The first phase, requirements analysis, is to find out all the requirements from users, determine the scope of the system, and then create usage examples. Secondly, before developers proceed with the system design, the phase of system analysis is supposed to analyze all the relationships between roles and jobs, jobs and system functions, and system functions and components. The last phase, system designing, is to implement the system functions and system function sets of role.