Class normalization is a process that can be used to organize the structure of object schema to increase the cohesion of classes while minimizing the coupling between them. This research proposes a method to apply the rule of class normalization to class modeling during the object-oriented systems analysis and design process. A real-world case is presented to illustrate the concepts, application, and the advantages of using the proposed method. Utilizing this method in class modeling can help the system developer ensure the class diagram in third object normal form and thereby enhance the effectiveness of system development.

The system design document can provide maintenance workers a quick understanding of the system operation process and review detail which helps current increasingly complicated information quite a lot, especially the in the aspect of the comprehension of original design concept to system. In addition, the system design document of platform independent can even quickly switch the platform for system without designing system again. It largely increases the operation of information system across platform. Besides the source code, system design document is also one of the most important asset; for instance, when the source code is lost, the designer can quickly duplicate a set of system with the same function under a basis of system design document. Due to the constant revolution of the platform technology to the current software, as well as the prevalent of visualized rapid application development tool, there is no complete design document attached in a set of the developed information system, or the document has been missing. It is necessary to find a way for the source code of system to reversely generate system design document. The study is based on object-oriented technology and object-oriented model to address a concept that platform independent system design document can be reversely generated from the object-oriented source code and to generalize a set of the reverse modeling method from this study. Last, a implemented case would be carried out and verified by the method mentioned above. Through this method, the maintenance workers could therefore quickly transform codes to system design document and then increase the operation efficiency of system maintenance.

Today, modeling the software with unified modeling language (UML), model driven architecture (MDA) concept, and computer-aided software engineering (CASE) tool are the main trend for the objected-oriented systems analysis and design. Furthermore, to enhance the degree of transformation automation and design reuse in the system development process, object constraint language (OCL) is used in UML modeling to specify the navigation, constraint, operation specification, and so forth. However, the guideline for using OCL in class diagram specification and its transformation to JAVA code is lacking. This research presents an approach utilizing the OCL to specify the constraint and operation specification for the class diagram when modeling the platform independent model (PIM), which can then be transformed into the JAVA platform specific model (PSM) and code using a CASE tool. A real-world case using the integrated techniques is presented and a CASE tool is used to illustrate the concepts, application, and the advantages of using the proposed approach. With this approach, the system developer can transform PIM into PSM and code automatically and thereby enhance the efficiency of system development.

No description available.

The presented work deals with analysis and implementation of algorithmic trading applications based on client requirements. Applications developed in this work are supposed to be used to collect and manage data from the stock exchange, to view information about active trading orders, and to send trading orders to the exchange via the API from Interactive Brokers. The first chapter gives an overview of selected books focused on developing applications for C # and analysis. Then the concepts of UML, OOAD, and UP are introduced. In the next chapter, requirements of the customer are defined. In the following chapter, based on the results of literature research and defined client requirements, the initial architectural design is created and cases of use with subsequent specifications are presented. This section is followed by finding analytical classes, creating a domain model, implementation of some use cases using sequence diagrams. The last two chapters describe the implementation details - the language used, the libraries, database schema, and user manual.

處在消費者需求快速變動的時代裏，製造業必須即時取得銷售資訊以掌握消費趨勢，並透過生產的製程調整以因應消費者需求的變動；而快速回應(Quick Response, QR)則被視為能夠藉由資訊科技的使用，降低產業經營成本，並即時回應消費者需求，提升產業競爭優勢的利器。因此，本研究之目的乃是希望在供應鏈成員能夠攜手合作（如透過策略聯盟的方式）的前提下，藉由此製造業快速回應系統架構及模式的引進，達到資訊流垂直整合的目的，並有效地傳遞產銷資訊，使供應鏈成員能針對消費者需求擬定更好的生產及銷售策略，進而達成消費者、零售業、批發業與製造業四贏的局面。 本研究透過文獻探討的方式，提出一個滿足快速回應理念的製造業資訊系統架構，並對其功能加以說明；其次，再透過整合型物件導向系統分析方法，建構出該系統之物件模式，並描述物件間的關係；最後，再以程式語言撰寫資訊垂直整合單元的雛型系統，以驗證本研究之可行性。 本研究的貢獻在於提出一個製造業快速回應系統的架構與物件模式，使製造業可以在建構此類的系統時，有一明確可依循的參考架構，以加速該系統之建置、維護，與修改。 / In the age of rapid changes in customers' needs, the industry must get the sales information on time, and then use this information to adjust its production processes to meet the changes. Quick response systems use information technologies to reduce the operating cost, to respond the customers' needs and changes on time, and to gain the advantages in a business competition. Under the assumption that all members of the supply chain would have cooperated (for example, the members can be cooperated by strategic alliance), the purposes of this research is to develop an architecture and an object model for industrial quick response information systems. Through the usage of this architecture and this model, we hope to meet the purpose of a vertical information integration among the members in the chain; so the members can share their information, and draw up the better production and sales strategies based on the customers' needs. Hence customers, retailers, wholesalers, and manufacturers can reach the win-win situation. Through the literature survey, we first try to propose an architecture for manufacturing information systems with the concept of quick response. Secondly, we use the integrated object-oriented approach to construct an object model for the proposed architecture and to describe the relationships among the objects in the model. Finally, we develop a prototype to show that how vertical information integration can be attained in this architecture. The major contribution of this research is to raise an architecture and an object model for industrial quick response information systems. Manufacturers or manufacturing software industries can use this architecture and this model as a reference to develop their owned systems. We believe that this kind of reference could speed up the time of the system development, maintenance and modification.

傳統會計與決策管理系統受限於現行財務會計報導的架構，並未儲存與財務無關，或不能以金額衡量的資訊，無法對非財務性決策提供有效的幫助。而資訊語意的差異更使得傳統會計與決策管理系統不易與企業內其他資訊系統互通，造成系統整合上的困擾，歷來不斷有學者探討會計與決策管理系統資訊模式建立之方法，以增進會計與決策管理系統資訊模式的有用性。 本研究提出會計與決策管理系統資訊模式建立之框架與方法，強調會計與決策管理系統之建構，應與企業策略發展整體考量，同時導入REA model整合企業整體資訊模式與財會專業資訊模式，並採用UML作為系統發展流程之塑模工具，編製系統發展有關文件，以利後續選擇解決方案的映對程序，確認解決方案符合使用者需求，及增進會計與決策管理系統在企業內的整合性與互通性。 / Traditional accounting and decision management information system cannot support non-financial decision making, because there is only stored financial information without non-financial information due to the current financial accounting reporting structure. The information semantic differences block interoperability between accounting and decision management information system within the organization. And it also has caused the challenge of enterprise information integration. Researchers strive to find viable information modeling process or method to help accounting and decision management information system to be constructed. This thesis presents accounting and decision management information system information modeling framework and process. The framework stresses the construction of accounting and decision management information system must connect with enterprise vision and strategy. It also adopts and expands REA model to integrate accounting information model and enterprise information model at information modeling process. UML is a high-level modeling tool to develop system processes. The goal is to provide a standard method to develop system blueprints beyond tool-specific system solutions and to apply UML modeling documents to map different system solutions and make sure the solution fit with user requirements, and improve the integration and interoperability for accounting and decision management information system design and development.