Statement of Work (SOW)

Sow describes all work products that will be produced and a list of people who will perform that work. It has a detailed description of all of the work products that will be created over the course of the project. A list of features that will be developed. A description of each intermediate deliverable or work product that will be built. 

COCOMO MODEL

The constructive Cost model (COCOMO) is an empirical estimation model i.e. the model uses a theoretically derived formula to predict cost related factors. This model was created by “Barry Boehm”. The COCOMO model consists of three models:-

(1) The Basic COCOMO Model: It computes the effort & related cost applied on the software development process as a function of program size expressed in terms of estimated lines of code (LOC or KLOC).

(2) The Intermediate COCOMO Model: It computes the software development effort as a function of – Program size and A set of cost drivers that include subjective assessments of product, hardware, personnel, and project attributes.

(3) The Advanced COCOMO Model: It incorporates all the characteristic of the intermediate version along with an assessment of cost driver’s impact on each step of software engineering process.

The COCOMO Model is defined for three classes of software projects stated as follows:-

(1) Organic Projects: These are relatively small and simple software projects which require small team structure having good application experiences.

(2) Semi-detached projects: These are medium size projects with a mix of rigid and less than rigid requirements level.

(3) Embedded Projects: These are large projects that have a very rigid requirement level. Here the 

hardware, software and operational constraints are of prime importance.

In below we will discuss only the Basic & intermediate COCOMO Models:

To Download: http://www.megaupload.com/?d=4GHKC51V

Waterfall Model

It is a simplest model, which states that the Phases are organized in a linear order. The model was originally proposed by “Royce”.

The various phases in this model are shown below:-

(1) Analysis Phase: It consists of planning and requirements definition activities. The end products of planning are – (a) System definition (b) project plan

(a) System definition – It is typically expressed in English. It incorporates charts, figure, graphs, tables and equation of various kinds.

(b) Project plan – It contains the life cycle model to be used, the preliminary development schedule, preliminary cost estimates and resources estimates, tools & technique to be used.

(2) Design Phase: This phase is concerned with – (a) identifying software components like functions, data streams and data stores, (b) Specifying software structures, (c) Maintaining a record of design decisions and providing blue prints for the implementation phase.

(3) Implementation Phase: It involves the translation of the design specifications into source code. It also involves activities like debugging, documentation and unit testing of the source code. In this stage various styles of programming can be followed like built-in and user defined data types, secure type checking, flexible scope rules, exception handling, concurrency constructs etc.

(4) System Testing Phase: It involves three kinds of activities: - (a) Unit testing (b) Integration testing (c) Acceptance testing

(a) Unit testing - Unit testing focuses on the smallest unit of software design i.e. the software component or module. Using the component-level design description as a guide, important control paths are tested to uncover errors within the boundary of the module. The unit test is white box oriented. Selective testing of execution paths is an essential task during the unit test. Boundary testing is the last and one of the most important tasks of the unit.

(b) Integration testing - Integration testing is a systematic technique for constructing the program structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested components and build a program structure strictly as per design. The program is constructed and tested in small increments, where errors are easier to isolate and correct.

(c) Acceptance testing – Acceptance testing involves Planning & Execution of various types of tests in order to demonstrate that the implemented software system satisfies the requirements stated in the requirements document.

(5) Maintenance Phase: In this phase the activities include (a) Enhancement of Capabilities (b) Adaption of software to new processing environments and (c) Correction of software design. 

To Download: http://www.megaupload.com/?d=LXR3CR73

Pert

Pert is stand for “Project Evaluation Review Technique”. It is a technique of representing activities of project in its proper sequence & timing. Pert is methodology developed by the U.S. Navy in the 1950s to manage the Polaris submarine missile program.

Terminologies used in PERT

(1) Pert Event: It is a point that marks the start or completion of one or more tasks. It consumes no time & uses no resources.

(2) Predecessor Event: An event that immediately precedes some other event without any intermediate events.

(3) Successor Event: An event that immediately follows some other event without any intermediate events.

(4) Pert Activity: It’s an actual performance of a task. It consumes time, it require resources (such as labors, materials, space, machinery etc).

(5) Optimistic time: The minimum possible time required to accomplish a task assuming nothing goes wrong.

(6) Pessimistic time: The maximum possible time required to accomplish a task assuming everything goes wrong.

(7) Most likely time: The best estimate of the time required to accomplish a task assuming everything goes normal.

Advantages of PERT:

(1) It helps us to estimate expected project completion time.

(2) It helps us to identify the critical path activities that directly impact the completion time.

(3) The start & end dates of the activities can be determined.

(4) The activities with slack time can be identified.

To Download: http://www.megaupload.com/?d=SIWNFU32

Project Charter

Project Charter will serve as an internal document that captures high level planning information (scope, deliverables, assumptions, etc.) about the Project. Its purpose is to recognize the existence of the project and to begin the planning process required to accomplish the Project goals.

Purpose of Project Charter

(1) Define project infrastructure (2) Summarize details of project plan

(3) Define roles and responsibilities (4) Show explicit commitment to project

(5) Set out project control mechanisms

Establish the project Charter:

(1) Vision: Write a concise vision statement that summarizes the purpose and intent of the project and describes what the world will be like when the project is completed. The vision statement should reflect a balanced view that will satisfy the needs of diverse customers as well as those of the developing organization.

(2) Objectives: Describe the important business objectives of the product in a way that is quantitative and measurable. These could include revenue increase, cost savings, return on investment, or target release dates. Determine how success will be defined and measured on this project.

(3) Scope: In Scope is what the project will include to meet the requirements of the Project goals. Out of Scope excludes responsibilities, activities, deliverables or other areas that are not part of the Project.

(4) Deliverables: Provide a high level list of “what” needs to be done in order to reach the goals of the project.  Each deliverable should be sufficiently detailed so that the Project Team will understand what needs to be accomplished.

 (5) Risks: Summarize the major risks associated with project, such as marketplace competition, timing issues, user acceptance, implementation issues, or possible negative impacts on the business.

Benefits of creating a charter include:

(1) Giving authority to project teams to commence work with official documented approval.

(2) Allowing senior management to set boundaries for the project scope.

(3) Formalizing partnerships.

(4) Helping project teams identify and plan for risks, increasing the chance of project success.

To Download: http://www.megaupload.com/?d=68GVZ8E1

Work breakdown structure (WBS)

A work breakdown structure (WBS) is a hierarchic decomposition or breakdown of a project or major activity into successive levels in which each level is a finer breakdown of the preceding one.

Major features of WBS: The major features of WBS is shown below:-

(1) Structure

   • WBS diagram is drawn like the organization chart.

   • Different desktop applications offer functionalities to easily create this kind of diagram.

(2) Classifications

There are two main classifications: (a) Product Hierarchy (b) Process Hierarchy

 (a) Product Hierarchy: It identifies the product components and indicates the manner in which the components are interconnected.

(b) Process Hierarchy: It identifies the work activities and the relationship between them.

(3) Description

• Each WBS element should be described with a title.

• The meaning of each title should be clear.

(4) Coding

• One of the main features of WBS is the ability to uniquely code the different elements of the work.

• The coding system can be alphabetic, numeric or alphanumeric.

(5) Depth

• The recommended depth of a WBS diagram is three to four levels.

                                                                                                              

Use of WBS: The potential uses of WBS include:-

• For dividing the project into phases.

• For dividing the project into responsibility areas within the organization.

• For dividing the schedule of the project into sub-schedule whose interrelation are known.

• For giving hierarchical outlining and coding for the work to be done.

To Download: http://www.megaupload.com/?d=4NZZTCYQ

Critical Path Method (CPM)

CPM uses activity oriented network which consist of a number of well recognized jobs, tasks or activities. Each task/activity is represented by arrow and the activities are joined together by events. CPM is generally used for simple, repetitive types of projects for which the activities time & costs are certainly and precisely known. Projects like construction of a building, road, bridge, physical verification of store can be handled by CPM. Thus it is Deterministic rather than Probabilistic model. 

Steps in CPM technique:

Step 1: Specify the individual activities                                                                                                          

A listing of all the activities in the project is made from the WBS (work breakdown structure).

Step 2: Determine the sequence of those activities

Some activities depend on others for their completion. They need to be identified.

Step 3: Draw a Network diagram

Once the activities & their sequencing have been defined the CPM diagram can be drawn.

Step 4: Estimate the completion time for each Activity

For each activity the completion time need to be estimated. This can be done on the basis of past experience.

Step 5: Identify the Critical path

The critical path is the longest duration path through the network where no activity is slack. The critical path can be identified by determining the following four parameters for each activity:

(a) Earliest start time (ES) – Earliest time at which the activity can start given that its previous activities must be completed first.

(b) Earliest finish time (EF) – It is equal to the earliest start time for the activity plus the time required to complete the activity.

(c) Latest finish time – The latest time at which the activity can be completed without delaying the project.

(d) Latest start time – It is equal to the latest finish time minus the time required to complete the activity.

Advantages of CPM:

(1) The activities & their outcomes can be shown as a network.

(2) It displays dependencies to help scheduling.

(3) It determines slack time.

(4) It evaluates which activities can run parallel to each other.

(5) It determines the project duration which optimizes both direct & indirect costs.

(6) If properly developed & applied CPM can encourage a team feeling.

(7) They are useful in new project managers.

(8) It is widely used in industry.

Disadvantage of CPM:

(1) The critical path is not always clear & needs to be calculated carefully.

(2) Estimating the completion of an activity can be difficult.


To Download: http://www.megaupload.com/?d=O57CQ2FV