MSF) are with non-?

May 5 posted in Development (RSS), comments.

Often see and hear everyone in the process of argument Agile, RUP and CMM software development process which better or what the process well, have their own reasons, the controversy was in fact ...... joy, there is no perfect process, there is no better process. The key is what kind of process to suit their own (the organization), their fit is the best course of the process. More importantly, the fit of their accumulation process takes time, requires constant practice, the definition of the process has been cut, complement and complete only the most suitable set up their own software development process.

Alistair Cockburn quoted saying that "different projects require different methodology, the best course of a project are the project can afford the minimum process." This shows that for an organization, often has several ways to coexist, while different types of projects, using different methods. Choose an appropriate life cycle model for the success of any software project is vital. Significant delays in a large number of items, product delays in the delivery should not be traced to its root causes are often used with the error-related life cycle model, including the existence of obvious defects in the waterfall model errors caused by, although the 70's over the years made waterfall model has been our software engineering education as a classic to teach, practice falls on the software process model is often led astray. Different is that the new process methodology, regardless of light, heavy, or XP, RUP, or TSP, without exception, have advocated the adoption can significantly reduce the risk of iterative evolutionary life cycle model, emphasis iteration. But too much emphasis on iterative, may overlook the needs analysis and definition, ignore the design, at the late changes constantly, so that the undesirable software development costs (rework, amend defects, etc.) greatly increased, an increase of the cost of doing business.

For example, an increasing number of people in the discussion, highly agile process, Extreme Programming (XP), there is the actual problem is, although the agile process, Extreme Programming Web fit the development of suitable free Web services, the fit Forever Beta version, which also has lot of thought indeed worthy applications, such as continuous integration, reconfiguration, testing emphasis, but there are also other issues, such as colorectal team programming, planning game, code such as collective ownership. Extreme Programming is only suitable for small teams, fit the open-source community, such as, but not suitable for large software enterprises; at the software development process on the overall situation, it is more suitable to adopt Unified Process (RUP), Microsoft Software Development Framework (MSF), and at the local, details, absorbing agile thought. American Friends have told me, XP may be a flash in the pan. Regardless of whether he is right, when the software as a mature industry, would surely not permit exactly like "XP" such a move.

Because of limited space and time, where can be the current popular process model to conduct a comparative analysis of U.S. will be of different strengths and weaknesses of the software process at a glance.

Item	CMM / CMMI	RUP	MSF	XP
Cycle	Spiral model.	Iterative cycle of evolution, the process framework	Waterfall model and spiral model combination	Iterative cycle of evolution. Software development methodology
Core	Process Improvement	Architecture, iterative	Milestone, iterative	To code-centric.
Range	Demand strict and rarely change.	Fit different types of projects	Fit different types of projects	The progress of tight demand Unstable small projects, small-scale distribution and small team
Organize	Personal (PSP), Team (TSP) and organization of three-level, inter-group collaboration, training	Cross-team collaboration	Products emphasize vision, six kinds of the basic role	Team-based, small team, Team member ability to fairly
Technology	Traditional structured methods	Object-Oriented Technology	General Technology	Object-Oriented Technology
Management	Focus on process definition, measurement and improvement. All speak with figures and documents.	From an organizational point of view, focusing on process modeling, deployment.	Business modeling, deployment, process management concepts.	Focus on specific process of the implementation and development of technology, plan design.
Events	Through the process to define the activity domain	The entire team throughout the process focus on quality	Project management, risk management and readiness management	People-oriented, such as 40-hour work week, pair programming
Practice	The different levels of the key practice. Importance of critical infrastructure.	CMM 2-3 class meets the requirements of KPA, which is basically not covered by the KPA class CMM 4-5	Code review, version management, document management, personnel recruitment, re-testing and re-risk management.	Coding and design integration activity, weakening the structure. Use cases, unit testing, iterative development and tiered architecture.
Other	High universality, but the complexity and cost.	Emphasize the risk-driven, so as to safeguard the continuity of available products to deliver the premise of the process to minimize unnecessary work, so that measurement, the smallest of the document to obtain the flexibility and adaptability.	Provide a series of guidelines for planning basic technological infrastructure of enterprises, commercial flow of the operation of the process and to encourage reusability.	Embrace change, emphasize human nature, and easy communication. Try to reduce the document. Individual and cross-over process and tools.

To sum up, does not exist a universal or immutable suitable software development and maintenance of all items of software process model. Software in the organization process, the existence of different corporate culture and business environment, different levels and scales, different types of architecture and products, different resources and capabilities and other factors, required according to different projects, different periods of time to select and use different process model and methods. Continuous process of absorption has been thought, and constantly explore and practice, eventually forming gradually fit their own self-definition process.

Through practice tests and the accumulation of self-definition of the software process is the best process.