Microsoft Solutions Framework: Difference between revisions

Revision as of 22:54, 30 January 2007

Revision as of 21:41, 12 March 2007

Line 9:

The Microsoft Solution Framework version 4.0 is a combination of a metamodel which can be used as a base for prescriptive software engineering processes, and two customizable and scalable software engineering processes. The MSF metamodel consists of foundational principles, a team model and cycles and iterations.

MSF 4.0 provides a higher-level framework of guidance and principles which can be mapped to a variety of prescriptive process templates. It is structured in both [[Prescription and description|descriptive and prescriptive]] [[Methodology|methodologies]]. The descriptive component is called the MSF 4.0 [[metamodel]], which is a theoretical description of the SDLC best practices for creating SDLC methodologies. Microsoft is of the opinion that organizations have diverging dynamics and contrarilycontrary priorities during their [[software development]]; some organizations need a responsivelyresponsive and adaptable software development environment, ifwhile others need a standardized, repeatable and more controlled environment. To fulfil these needs, Microsoft represent the metamodel of MSF 4.0 in two prescriptive methodology templates that provide specific process guidance, named Microsoft Solutions Framework for Agile Software Development (MSF4ASD) and Microsoft Solutions Framework for Capability Maturity Model Integration Process Improvement (MSF4CMMI). Note that these software engineering processes can be modified and customized to the preferences of organization, customer and project team.

The MSF philosophy holds that there is no single structure or process that optimally applies to the requirements and environments for all sorts of projects. Therefore MSF supports multiple process approaches, so it can be adapted to support any project, regardless of size or complexity. This flexibility means that it can support a wide degree of variation in the implementation of software engineering processes while retaining a set of core principles and mindsets.