{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

Resource Estimation for Objectory Projects

Resource Estimation for Objectory Projects - Resource...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
Resource Estimation for Objectory Projects Gustav Karner Objective Systems SF AB Torshamnsgatan 39, Box 1128 164 22 Kista email: [email protected] September 17, 1993 Abstract In order to estimate the resources needed to develop a software system with the Objectory process, one would like to have a model which predict the total amount of resources early in the developing process. The model described in this article will help you to do a prediction like that. 1. Introduction Objectory, see Jacobson I., Christerson M., Jonsson P. and Övergaard G. (1992), is a well defined process for developing industrial object oriented applications. The process is built of four different main processes which are: Requirements Analysis Robustness Analysis Construction Testing It would be of great value if a prediction of the resources needed for these processes for a specific project could be done early in the developing process e.g. after the requirements analysis. With such an early estimation, one could more easily plan and predict for the rest of the project. When a project is set up it is very important to know, in advance, how much resources is needed for the project to be completed. This kind of knowledge will help us to estimate the cost and the lead time for the project. It will also help to plan the use of the resources. These estimations should of course be available as soon as possible in the project. This paper will initially survey a model for making early estimations called Function Points. It will then present a model for making early estimations when developing software with the Objectory process. The model is based on the Function Points. 2. Function Points Function Points (FP) is a common model for estimations, proposed by Albrecht (1979). It is useful when you want to estimate man hours in an early phase, when you only have the specifications. The model counts the number and complexity of (in order to estimate the size of the system): 1. Inputs, the number of different commands the software will accept. 2. Outputs, how many types of information it can generate. 3. Inquiries, how many different sorts of question a user can ask the system. 4. Files, how many it can cope with simultaneously. 5. Interfaces, the number of links it can have with other software. Every one of these items are given a value as simple, average or complex with different weights ( W i ). The Unadjusted Function Count (UFC) is: UFC = n i * W i i = 1 5 where n i is the number of items of variety i where i stands for the number of items 1, items 2 etc.. and W i is the weight of i . These are later adjusted with a technical factor which describes the size of the technical complexity involved in the
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
development and implementation of the system. The TCF is computed as: TCF = C 1 + C 2 F i i = 1 n where C 1 = 0.65 C 2 = 0.01 F i is the factors valued from 0 to 5. 0 if it is irrelevant and 5 if it is essential.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

Page1 / 9

Resource Estimation for Objectory Projects - Resource...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon bookmark
Ask a homework question - tutors are online