An Application of TOC on Object-Oriented Project Development

• Main Authors: Bao-Sheng Tseng, 曾寶生
• Other Authors: Ching-En Lee
• Format: Others
• Language: zh-TW
• Published: 2000
• Online Access: http://ndltd.ncl.edu.tw/handle/98715005739828846839

碩士 === 國立交通大學 === 工業工程與管理系 === 88 === Numerous Information systems (IS) are constructed nowadays to help enterprises face the changeable and competitive external environment. However, developing a large-scale IS for an enterprise is not an easy task. Object-oriented (OO) method, a tool using information technology, is used widely to proceed to the IS project development. In addition to development tool, professional knowledge and user requirements are also necessary and important elements. In fact, there are many tools and methods existing which can assist in developing an IS. It seems that everything is ready, but everything goes wrong when the project is proceeding. Many problems occur and intertwine around developers. Those problems often cause project delays or terminations. Many OO projects fall into the same plights, and the developers involved in the projects are at a loss. This thesis applies TOC (Theory of Constraints) on the OO-Project development. TOC is an analytic tool in a system''s view. It provides a complete procedure from analyzing problems to developing solutions. Firstly, the thesis narrows the topic to object development. And then, the thesis clearly explains why and how the problems occur. In the following, a blueprint for object-development by injections is constructed; solutions for every injection are also developed. At last, solutions are mapped to existing tools. By means of TOC, undesirable effects in OO projects are prevented so that the successful development of an OO-Project is expectable. To develop an OO project to meet the enterprise requirements, to clearly define requirements and to make documents are necessary. The thesis strongly shows that these efforts are unavoidable. To conclude that a successful and stable development depends on how many clear and certain requirements a project actually owns.