Task Set In Types Of Projects

 Definition of Task Set

      The task set is a collection of software engineering work tasks, milestones, and work products that must be accomplished to complete particular Project.

• Every process model consists of various tasks sets.  Using these tasks sets the software team define, develop or ultimately support computer software.
• There is no single task that is appropriate for all the projects but for developing large, complex projects the set of tasks are required.  Hence every effective software process should define a collection of tasks sets depending upon the type of the Project.
• Using tasks sets the high quality software can be developed and any unnecessary work can be avoided during software development.
• The number of tasks sets will vary depending upon the type of the project.

Various types of projects are enlisted below.

1. Concept Development Project

These are the projects in which new business ideas or the applications based on new techniques are to be developed.

2. New application development Project

These projects are developed for satisfying a specific customer need.

3. Application up gradation project

These are kind of projects in which existing software application needs a major change.  This change can be for performance improvement, or modification within the modules and interfaces.

4. Application maintenance project

These are kind of projects that correct, adapt or extend the existing software applications.

5. Reengineering Projects

These are the projects in which the legacy systems are rebuilt partly or completely.

• Various factors that influence the tasks sets are 

1)     Size of Project,

2)     Project development staff,

3)     Number of user of that project,

4)     Application longevity,

5)     Complexity of application,

6)     Performance constraints,

7)     Use of Technologies.

Task set Example

Consider the concept development type of the project.  Various task sets in this type of project are.

• Defining Scope

This task is for defining the scope, goal or objective of the project.

• Planning

It includes the estimate for schedule, cost and people for completing the desired concept.

• Evaluation of Technology Risks

It evaluates the risk associated with the technology used in the project.

• Concept Implementation

It includes the concept representation in the same manner as expected by the end user.

Software Measurement in Project

Software Measurement

The measurement of Software can be classified into Two Categories :

• Direct Measure
• Indirect Measure

• Direct Measure

Measures cost and effort applied, line of code produced, execution speed and defects.

• Indirect Measure

Measures functionality, quality, reliability, efficiency, maintainability, complexity.

Let us discuss the metrics based on these approaches :

Size Oriented Metrics

This kind of measure is normally based on lines of code of the project.

Function Oriented Metrics

This kind of measure is based on functionality of the application.

Attributes of Effective Software Metrics

The effective software metrics should have following attributes :

1. Simple and Computable

The derivation of metric should be easy to computer and should not be a time consuming activity.

2. Empirically and intuitively persuasive

It should be immediate and can be derived based on observation.

3. Consistent and Objectives

The metric should produce unambiguous results.  Anybody should get the same result by using these metrics when same set of information is used.

4. Consistent in its use of units and dimensions

The mathematical unites and dimensions used for the metric should be consistent.  And there should not be intermixing of units.

5. Programming language independent

The metric should be based on analysis mode, design model and program structure.  It should be independent of programming languages, syntax or semantic of any programming language.

6. Metric should be effective mechanism for high quality feedback

The metric should provide a way to produce high quality software product.

Object Oriented Metrics

Lorenz and Kidd have proposed set of metrics for object oriented projects :

• Number of scenario scripts

The number scenarios can be typically obtained by designing the use cases for the system.  It basically represents the user interaction with the applications.  The total number of scenario is dependent upon size of application and number of test cases.

• Number of Key Classes

In any object oriented design classes are the logical entitles of the system.  Hence total number of key classes ultimately represent the amount of effort required to develop software.

• Number of Support Classes

The support classes are logical entities required to support the key classes.  Thus total number of support classes represent amount of software reusability and total amount of reusability

• Average number of support class per key class

There are more number of support class per key class for the applications with GUI than applications without GUI.  Knowing this aver age number makes the design more simplified.

• Number of Subsystems

Subsystem means aggregation of classes.  To schedule the project systematically it is necessary to identify all the subsystem of the system being developed.