原文標題：New-type information system

New-type information system
（By Russ Finney）
The business of building systems has changed. A time once existed when computer literacy, technical know-how, and programming skills were all it took to become a successful information systems professional. In many companies, this is still the case. But slowly, yet steadily, a new breed of systems professional is beginning to emerge. Technical skills are no longer enough. Business knowledge, communication ability, and a client centered perspective are becoming more and more important. With computer systems playing an ever increasing role in the management and the competitiveness of companies of all sizes, the information systems professional no longer just serves the company, in many case he or she has a major influence on the way business is conducted.
What does this mean for today's systems professional? It means the burden of keeping up is even more challenging than ever! Systems professionals must increasingly view themselves as business problem solvers and business enablers, not just technicians. Computing power has become a part of corporate strategy, and the system builders are charged with creating the business information systems "vision" and making it a reality. Add to this the vast array of technical platforms, programming languages, databases, and system building methodologies which are available in today's marketplace, and the job becomes somewhat overwhelming! So how should the computing professional approach these challenges?
First, today's system builder must adopt a more business centered philosophy, and second, he or she must exercise discipline and flexibility as the company moves through the system building lifecycle. But which lifecycle? Traditional System Building Approaches, Information Engineering, Object Oriented Design, Rapid Application Development, and a host of others all possess inherent strengths and weaknesses. Which one is best? How should these approach decisions be made?
Unfortunately, no easy answers exist to these questions. Depending on circumstances and experience, one approach may be preferable over another. In other situations, a sampling of techniques and methods from one or more of the current approaches may be appropriate. What follows within this web site is a mix. Some of the strengths from the traditional lifecycle are still present, the foundation of structured analysis is present, many of the advantages of information engineering have been incorporated, and the new paradigms of object-oriented analysis, design and programming are included.
The main criteria for discussion here is one of practicality. What are the approaches which make most sense in today's business climate, and which will yield the greatest productivity results given the ever increasing quality demands of the business clients. The other consideration for inclusion here is that the selected philosophies and approaches are proven and they work. They have been developed from actual IS implementation and support experiences.

譯文標題：新型信息系統

新型信息系統
（翻譯yanrj）
系統建造這一工作（業務）已經變了！曾經一度時間，計算機素養、技術細節、 編程技巧是成為一個成功信息系統專業人士的全部。（事實上，）在很多公司里，目前 仍然是這樣。但是，慢慢地，新一代的信息系統專業人員正在穩步開始出現。僅有技術 上的技巧已經不夠，業務知識、溝通能力、以客戶為中心的觀點變得越來越重要。隨著 計算機系統在各種（或所有）大大小小的公司中的管理和競爭能力方面起的作用越來越 重要，信息系統專業人員不再僅僅是為公司服務，在很多情況下他或她對業務運作的方 式有著關鍵的影響。
那么對于今天的系統專業人員來說，這意味著什么呢？ 意味著（系統）維護的 擔子比以前更具有挑戰性！系統專業人員必須進一步把自己當作業務問題的解決者和 業務使能者，而不僅僅是技術人員。現在，計算能力已成為公司策略的一部分，而系 統開發人員則負責創造業務信息系統的“愿景”，并將它變成現實。加上目前大量在 市場上可獲得的技術平臺、編程語言、數據庫和系統開發方法，這項工作一定程度上 說勢在必行！那么，計算業人員應如何面對這些挑戰？
首先，今天的系統建造人員必須采納更加以業務為中心的哲學；其次，隨公司沿著 系統建造生命周期的推進，他或她必須訓練自己的紀律性和靈活性。然而是哪個生命周期？ 傳統的系統建造方法，信息工程、面向對象設計、快速應用開發，以及其它方法都具有其固 有的優點和缺點。哪個是最好的？應當如何進行這些方法的決策？
不幸的是，對于這些問題不存在簡單的回答。在特定的環境和經驗下，一種方法可能要 比其它方法好。然而在其它的環境下，從現有方法中提取的一些技術和方法可能更加合適。 這個網站構造就是一個(這種方法的)混合體。傳統生命周期的部分優點依舊存在，結構化分 析的基礎依舊存在，而很多信息工程的優點已經被結合，包括面向對象分析、設計、編程等 新方法。
這里討論的主要準則是實用性。在今天的商業氣候中最起作用的方法是什么，哪種方法 能面對商業客戶不斷增長的質量需要而產生最大的收益。這里，另一需要考慮的是被選體系 和方法應當是被證實的，并能工作的。它們是在實際的信息系統實施和支持實踐中形成的。