Software Estimation Data Model

Status

This page is obsolete. The data model will be expressed using RDF instead of an Entity-Relationship model. Using RDF aligns it with other OSLC specifications. Refer to EMS 1.0 Part 1: Resources and REST API for the normative specification of the RDF data model.

Introduction

The purpose of this model is to identify the main entities and relations that describe software metrics, estimates, and their relation to projects. This model will define our vocabulary and inform the development of REST services, XML resource representations, tool object models, and database schemas. The model itself is non-normative.

About the Data Model

The data model is an Entity-Relationship (ER) model.

This model has been developed using Telelogic System Architect. The model has been published as a website. The website has also been zipped so you can download it and view it offline.

The text below gives a high-level narrative of the model. Eventually the entities and relations described in the text will be linked to the model website.

External Entities

This model extends the base software development model. We assume the following entities are part of the base model.

CREATOR Entity

A CREATOR represents a person or team that performs some work on a project. The main work roles we are concerned with here are modeller, measurer, and estimator.

MANAGER Entity

A MANAGER is a person that manages projects.

PROJECT Entity

A PROJECT represents a software project, i.e. a time-bounded work effort that produces a unique product.

• Each PROJECT is managed by some MANAGER.
• Each PROJECT has additional attributes such as name, description, planned start date, planned finish date, etc.

SCM_RESOURCE Entity

An SCM_RESOURCE represents a folder or file in a software configuration management (SCM) system. These resources are what is produced by the software project.

• Each SCM_RESOURCE is part of an SCM_COMPONENT tree. Folders contain other folders and files. Files are leaves of the tree.

CM_COMPONENT Entity

A CM_COMPONENT represents a component in a change management (CM) system. Defects are tagged as being found in specific components. Features are tagged as being enhancements to specific components. A component is implemented by a collection of source files and other resources. However, there is often no direct mapping between the CM system and the SCM system.

• Each CM_COMPONENT is part of a CM_COMPONENT tree.

Main Estimation Entities

See Entity Relation model.

Comments

Add your comments here.