OOA and software multiplexing
Author: gnicky URL: http://blog.9cbs.net/loconfuse
Keywords: OOA, Reuse, Supporting for Reuse, Supporting with Reuse, SUPPORTING
Software multiplexing is to construct an existing software component to construct a new software system. The existing software ingredients can be, extracted, extracted, or commercialized components, Reusable Component.
Software multiplexing and component sharing and software transplant are easily confused, everyone should pay attention to the difference. Software multiplexing is not only for program reuse, including reuse of finished products generated by any activity in software production, such as project plan, feasibility report, demand definition, analysis model, design model, detailed description, source Program, test plan, test case, etc.
Formally proposing software reuse is in 1968. Re-use significantly has a lot of advantages, and put forward the concept of software reuse in a very early stage, and people have still been interested in software reuse, which means that people have given it a hopes. The most direct benefit of software reuse is to improve software production efficiency, thereby reducing the cost of software production, allowing enterprises to achieve high interest rates. Humans have been in the industrialized society, and the growth of material wealth has grown rapidly. One of the reasons is to replicate similar products in large quantities, which is a reuse of design and production processes. Although the object-oriented software has arrived in the industrialization stage, the reuse away from the industrialization, and the cost of the software needs to pay and the reuse of industrial production cannot be synonymous. Industrial production is plus consumption and software reuse. Discover that can be reused, developing a reconfimate component is more than two to four times more than the software ingredients used in one system. The second obvious advantage of software reuse is to improve software quality, because the quality assurance of the reused components is generally more stringent and sufficient, especially commercial components than the quality assurance of non-multiplexes. In addition, when the component is used in a large amount of use, it has been repeatedly tested, and its error will be discovered earlier and excluded.
Other benefits: the system uses the same components to reflect consistency to the user, reflecting readers to program readers, reflecting maintainability to maintaread, reflecting better interoperability; promoting standardization, so that software The architecture, algorithm is consistent, and the development process is aggravated, and rapid prototyping is supported because the component is the basis for rapid prototyping.
Software multiplexed factors:
Technology, people, management, education, law
