Some of the next focus focuses on the development of the information system.
In order to achieve the improvement and improvement of the quality of development and product (ie information system), many organizations choose to use a development framework [framework], such as Capability Maturity Model. (* Note: High-performance mature model? I don't know what to How to translate into Chinese ... :()
To look at the definition: The Capability Maturity Model (CMM) is a framework to assess the maturity level of an organization's infomation system development and management processes and products, It consists of five levels of development maturity.
CMM is a framework for assessing information systems development and management maturity and complete horizontal, which consists of 5 levels.
Level 1 --- The initial [Initial]: This is a low level, the project group does not have any pre-standard development processes, and each member in the development team adopts its own development tool and development method. Success or failure is completely determined by the experience and ability of the project team. The process of this development is unpredictable and inerable. The project developed will encounter a lot of trouble, often exceeding the budget and cannot be completed on time. None of any documents can be used as a reference, must be maintained and resolved by the initial developers. This level shows that it is very low-level or even difference, but all organizations start from this level.
Level 2 - Reusable [REPEATABLE]: The management of special projects has been established in development, and they are responsible for project costs, processes, and functions. Therefore, development is reusable, but because management is only for the project itself, there is no unified method, which has a large difference in different projects. And success or failure is still completely determined by the experience and ability of the project team. Although this level is not as good as a place, it has begun to pay attention to and strive to make the project reuse and success. Therefore, high efficiency has become the basis for the standardization of the next level of management practices.
Level 3 --defined [defined]: At this level, standard system development process (usually a methodology) has been established and developed, and uses it to integrate information systems in the organization and its services. All items use this unified development process to develop and maintain. Since all items use unified and standard development processes, each item can be constructed from high quality documents and partially distributable and reused parts. The entire development process is stable, predictable and reused.
Level 4 --- Management [Managed]: At this level, the measurement of the product and quality is established. During the various details standards in the development process of information system, it is measured and stored in the database. Then, based on these collected data to improve the management of the project. Therefore, in management, there are more predictable and strain capabilities that encounter problems (time, budget, etc.) encountered, even if it encounters some unpredictable issues and events, the development process can quickly quantify these problems. And make appropriate adjustments to adapt to solve problems. The entire development process is predictable.
Level 5 - Optimized [Optimized]: In the previous level, ie Level 4, the quantitative data is established, monitors and use it as a basis for improving the system and development. At this level, this standard system development continues and strengthened, making it uninterrupted, sustained process, thus making the system more performance and more adaptability. In the maintenance of the system, the system has continuously improved the improvement and performance of the system. The above levels of CMM are briefly introduced, and each level is the foundation of its next level according to the order from low to high.
Normally, we need at least the third level [level 3], that is, the defined [defined]. That is to say, in the development process, we need to use a standard, a methodology.
Defined methodology for Information System Development: A systems development methodology is a very formal and precise system development process that defines (as in CMM Level 3) a set of activities, methods, best practices, deliverables, and automated tools for system developers and project Managers to use to we we exvelate and maintain Most OR All Infomation Systems and Software.
Let's first take a look at the general principles in some development before introducing the specific development methodology:
Principle 1: Let the system all this and system users participate in [Get Owners And Users Involved]
Principle 2: The focus is to use a specific method to solve the actual problem [Use a problem-solid approach]
Principle 3: Divide which activities are made into various phases [Establish Phases and Activities]]
Principle 4: Building a variety of activities and matters (such as document, quality, development tools, development technology, etc.) [Establish Standards]
Principle 5: To handle development systems as a capital investment (system analyst needs to analyze and find multiple possible solutions and calculate and measure the feasibility and possible results of each program) [Justify System As Capital Investments ]
Principle 6: Don't be afraid to cancel the result and re-coming [Don't be afraid to cancel or revise scope]
Principle 7: Divide the problem and overcome [Divide and Conquer]
Principle 8: Design the system into changing and upgraded [Design Systems for Growth and Change]
The above is some things we need to remember in mind, and the principle of meeting the basis of meeting and abide by the time when we analyze and deal with the problem. With these principles, we can continue to discuss the methodology of development. :)
Then, in the next section, the methodology will continue to be explained on the methodology of information system development. :)
