Skip to document
Welcome to StudocuSign in to access the best study resources
Guest user
0followers
HomeMy LibraryAsk AI
  • You don't have any recent items yet.
My Library
  • You don't have any courses yet.
  • You don't have any books yet.
  • You don't have any Studylists yet.

The application composition model

Discussion about The application composition model
Course

Software Engineering (CS391)

174 Documents
Students shared 174 documents in this course
Academic year: 2022/2023
Uploaded by:
Anonymous Student
This document has been uploaded by a student, just like you, who decided to remain anonymous.
Fayoum University

Comments

Please sign in or register to post comments.

Students also viewed

Related documents

Preview text

The application composition model

The application composition model is a new feature that was added to COCOMO II to assist with the assessment of the amount of work that is necessary for prototyping projects as well as projects in which the software is produced by composing existing components. It is calculated using an estimate of weighted application points, which are also referred to as object points on occasion. This figure is then divided by a standard estimate of application point productivity (B. W. Boehm et al. The number of application points in a programme can be derived from four simpler estimates, which are: 1) the number of separate screens or web pages that are displayed; 2) the number of reports that are produced; 3) the number of modules in imperative programming languages (such as Java); and 4) the number of lines of scripting language or database programming code.

The accuracy of this estimate is then determined by the degree of complexity associated with the creation of each application point. The expertise and skill of the developer are important factors in determining productivity, but so are the features and capabilities of the software tools (ICASE) that are used to support development. The levels of application-point productivity that were indicated by the architects of the COCOMO model are displayed in Figure 23.

The process of composing an application typically involves customising application systems and reusing already developed software. So, the implementation of some of the system's application points will involve the use of components that can be reused. As a consequence of this, you will need to modify the estimate so that it takes into account the anticipated proportion of reuse. As a result, the following is the ultimate formula for computing the amount of effort required for system prototypes:

PM 5 (NAP 3 (1 2%reuse/100)) / PROD PM: the estimated amount of work needed in person-months

NAP stands for "total number of application points" in the system that has been delivered.

%reuse is an estimation of the proportion of the development that consisted of reusing existing code.

As shown in Figure 23, PROD refers to the productivity of the application point.

Was this document helpful?

The application composition model

Course: Software Engineering (CS391)

174 Documents
Students shared 174 documents in this course

University: Fayoum University

Was this document helpful?
The application composition model
The application composition model is a new feature that was added to COCOMO
II to assist with the assessment of the amount of work that is necessary for
prototyping projects as well as projects in which the software is produced by
composing existing components. It is calculated using an estimate of weighted
application points, which are also referred to as object points on occasion. This
figure is then divided by a standard estimate of application point productivity (B.
W. Boehm et al. The number of application points in a programme can be derived
from four simpler estimates, which are: 1) the number of separate screens or web
pages that are displayed; 2) the number of reports that are produced; 3) the number
of modules in imperative programming languages (such as Java); and 4) the
number of lines of scripting language or database programming code.
The accuracy of this estimate is then determined by the degree of complexity
associated with the creation of each application point. The expertise and skill of the
developer are important factors in determining productivity, but so are the features
and capabilities of the software tools (ICASE) that are used to support
development. The levels of application-point productivity that were indicated by
the architects of the COCOMO model are displayed in Figure 23.11.
The process of composing an application typically involves customising
application systems and reusing already developed software. So, the
implementation of some of the system's application points will involve the use of
components that can be reused. As a consequence of this, you will need to modify
the estimate so that it takes into account the anticipated proportion of reuse. As a
result, the following is the ultimate formula for computing the amount of effort
required for system prototypes:

Students also viewed

Related documents