Cocomo Model (Software Engineering)

I. Introduction
A. Scope and Purpose of Document
The equipment management plan in seaport is purposed and describes the
planning about amount of equipment which is supposed operate to handle some
of container in seaport for one time. There are several equipment like rubber tyred
gantry (RTG), quay crane, head truck, top loader, etc. which are need to be
managed in order to operate according to the amount and time specified to make
more efficient and reduce operating costs.
The equipment management plan in seaport is purposed and describes the
planning about amount of equipment which is supposed operate to handle some
of container in seaport for one time. There are several equipment like rubber tyred
gantry (RTG), quay crane, head truck, top loader, etc. which are need to be
managed in order to operate according to the amount and time specified to make
more efficient and reduce operating costs.
B. Project Objectives
A. Objectives
The objectives for this project equipment management plan is determine the
number of equipment in order to operate in ideal, it means when operate the
equipment is not excessive and nor deficiencies in handling containers at a time
and the amount of equipment will continue to change according to the number of
containers that arrive at the port.

Figure 1. Involve Factors in XP

In this project using Extreme Programming (XP) method. Extreme Programming
(XP) is a software development methodology which is intended to improve
software quality and responsiveness to changing customer requirements, as a
type of agile software development, it advocates frequent releases in short
development cycles, which is intended to improve productivity and introduce
1

Cocomo Model (Software Engineering)

checkpoints at which new customer requirements can be adopted. Other elements
of extreme programming include: programming in pairs or doing extensive code
review, unit testing of all code, avoiding programming of features until they are
actually needed, a flat management structure, simplicity and clarity in code,
expecting changes in the customer's requirements as time passes and the
problem is better understood, and frequent communication with the customer and
among programmers. Change-control boards are a sign that there are potential
conflicts in project objectives and constraints between multiple users. XP's
expedited methods are somewhat dependent on programmers being able to
assume a unified client viewpoint so the programmer can concentrate on coding,
rather than documentation of compromise objectives and constraints. This also
applies when multiple programming organizations are involved, particularly
organizations which compete for shares of projects.
B. Historical Data Used for Estimates
Historical data will become important especially for effective budgeting and
estimation and needed for any form of consistent estimation. The problem with
historical data is that gathering the data requires effort, time or money. The
following is historical data used for estimates in software development of
information equipment management, which are: effort, duration, staffing, cost,
capabilities (describe the level of competency of the team), size (is measure of
the end project delivered by the project), context (is the story of the project
including whether anything out of the norm that happened) and project
demographics.
C. Estimation Techniques
In this project, the estimation techniques in software development of equipment
management is using the Constructive Cost Model (COCOMO) which is an
algorithmic software cost estimation model with uses a basic regression formula
and parameters that are derived from historical project data and current as well as
future project characteristic. COCOMO consist of a hierarchy of three increasingly
detailed and accurate forms, the first level, basic COCOMO is good for quick,
early, rough order of magnitude estimates of software costs, but its accuracy is
limited due to its lack of factors to account for difference in project attributes (cost
drivers), intermediate COCOMO takes these cost drivers into account and

Cocomo Model (Software Engineering)

detailed COCOMO additionally accounts for the influence of individual project
phases, and for cost estimation process shows by figure 2 below.

Figure 2. Cost Estimation Process

The basic COCOMO equation can be described:

Effort Applied ( E )=a b ( KLOC )b [ personmonth ]

b

db

Development Time ( D )=c b ( Effort Applied) [ months ]

People required ( P ) =

Effort Applied
[ count ]
Developement Time

Output
[bit]
128
160
224

Input
[bit]
512
512
512

No. of
rounds
64
80
64

Collisions
found
yes
not yet
no

SHA-256

256

512

64

no

SHA-384
SHA-512

384
512

1024
1024

80
80

no
no

Algorithm
MD5
SHA-1
SHA-224
SHA -2