The Basic Model

After reading advanced papers on MSF (notably the Project Management Discipline), I put some thought on the relationship between MSF and COCOMO. MSF has reference to COCOMO, but does not particularly address the relationship between the two.

Starting from COCOMO, they have the basic equation of Effort = a * (KSLOC ^ b). The closest thing to MSF is the KSLOC variable. I would need to find the parameters to complete the following equation: KSLOC = ? (MSF attributes).

Looking at MSF track and cycles, the earliest item that MSF has would be Vision, Persona, Scenario, and Quality of Service Requirement. Judging from quantitative relationship, the above equation would be something that looks like: KSLOC = (c * number of Persona) + (d * number of Scenario) + (e * number of QoS Requirement).

My first impression, c, d, and e constants are to be generated emprically. But this approach would require a lot of data and the data itself has to come from the same source (that means, all Scenario has to be of the same scope, etc.) The problem lies in researching for the data, and normalizing the data itself. We'll see how this will evolve in the future.

Definition: Solution

-From MSF Process Model v.3.1-

A solution is simply a strategy or method to solve a problem. In MSF term, solution is coordinated delivery of the elements needed to successfully respond to a unique customer's business problem. The elements are technologies, documentation, training, and support. A solution, therefore, can contain more than one product.

The paper expressed that MSF is focused on custom solution for a specific customer.

The difference between solution and product is as follows:

Products

  • Designed for the needs of a mass market.
  • Delivered as a packaged goods or "bits".

    MSF Solution

  • Designer or tailored to fit individual customer needs.
  • Delivered as a project.
  • Paper: MSF v3.0 Overview

    Summary:
    MSF is an adaptable framework for delivering solutions on time and within budget. MSF is flexible and scalable, so that it is adaptable to any project. MSF is more about managing "people and process", one of the key elements in technology projects. Based on the paper, failures causes are not just technology, but also lack of communication. To address that problem, organizations will need to change their behaviour, and it requires dedication, commitment, and leadership. MSF is built from experience, thus is affected by industry standards like SEI CMMI, Agile Methodologies, and ISO 9000 family.

    Relation with research:
    This paper provide background information about Microsoft Solutions Framework key concept and goals. As written on the paper, the goal of MSF is to deliver successful, high-quality, business-driven technology solutions. This is aligned with the goal of this research, to reduce failures in software projects.

    Notes:
    more information should be taken from more advanced papers on MSF, notably the Process Model, Project Management Discipline, and Risk Management Discipline.

    Paper: The Chaos Report

    Summary:
    The Chaos Report is published by The Standish Group, a research firm. The Chaos Report focuses on software project failures, identifying the scope of failures, factors that cause failures, and factors that reduces failures. The subject of the research were U.S. companies that has an MIS department. In this report, they found that the average cost overruns was 189% of the original estimation. The bigger the company, the higher it's chances of having a failure.

    Relation with research:
    This paper provides the starting point for identifying problems with cost estimation. With a high level of cost overruns, there should be a better way to estimate the project cost. This is where software cost models like COCOMO take part. Better estimation of project cost will encourage better Executive Management Support, one of the factors that reduces failures.

    Notes:
    provide a firm reasoning between better estimation of project cost and better executive management support. Also link to 2004 Chaos Report that moves Executive Management Support to number one factor that reduces failure rate.

    Reference Textbooks

    These are the list of books I'm going to read the following week to establish a base knowledge between project metrics and cost model.

    The Mythical Man-Month
    Frederick P. Brooks
    Paperback: 322 pages
    Publisher: Addison-Wesley Professional; 1st edition (August 2, 1995)

    Software Engineering Economics
    Barry Boehm
    Paperback: 767 pages
    Publisher: Prentice Hall PTR (October 22, 1981)

    I've found Boehm's at the library, and still looking for Brooks'. Hopefully both are available to borrow.