Cosmic 4z3zd

Cosmic Full Function Point

Submitted By: Vivek Chavan(231173) Pallav Sharma(231096) Sreyasi Bandyopadhyay(08346) Rahul Jain(231111) Gaurav Makkar(231058) Shikha Arora(231142)

Introduction  The

COSMIC method is an internationally standardized software sizing method.

 It is a method of measuring a ‘functional size’

of software. ‘COSMIC’ stands for the Common Software Measurement International Consortium, a grouping of software measurement experts from around the world who, in 1998, saw the need to improve on traditional function point methods.

Cosmic method The COSMIC method can be used:  To provide a measure of the size of a software development or enhancement project’s work-output that may be used to derive performance measures such as  productivity = size/effort  As the size measure depends only on the required functionality and is independent of any technology used, such measures can be used to compare performance across projects using different technologies for use as the primary input to methods for estimating project effort.  The ability to measure a software size from its requirements is especially valuable early in the life of a software project.

COSMIC Concepts

The Functional Requirements (FUR) specify ’s needs and

procedures that the software should fulfill. The FUR are analyzed to identify the functional processes. A Functional Process is an elementary component of a set of FUR. It is triggered by one or more events in the world of the of the software being measured. The process is complete when it has executed all that is required to be done in response to the triggering event. Each functional process consists of a set of sub processes that are either movements or manipulations of data. Since no‐one knows how to measure data manipulation, and since the aim is to measure ‘data movement‐rich’ software, the simplifying assumption is made that each functional process consists of a set of data movements. A Data Movement moves one Data Group. A Data Group is a unique cohesive set of data (attributes) specifying an ‘object of interest’ (i.e. some thing that is of interest’ to the . Each Data Movement is counted as one CFP (COSMIC function point).

COSMIC representation of functional requirements within a piece of software.

Source: http://www.ittoday.info/Articles/COSMIC_FPP/COSMIC_FPP.

COSMIC FFP Software Model

Sorce: http://www.ittoday.info/Articles/COSMIC_FPP/COSMIC_FPP.htm Accessed on 26/05/15

Data Movements Exit Read Entry moves moves moves data from data from data from the persistent outside process to storage to into the the the process outside process world

Write moves data from the process to persistent storage.

MIS

Data Movement Process Flow

Source: http://galorath.com/wpcontent/s/2014/08/cosmic_fun ctional_size_measurement_method

MIS Example Invoices should be made as part of the financial settlement of week

40. These invoices relate to customer product deliveries in week 40. For the invoice all deliveries of week 40 will be collected. The invoice is kept in data storage to write off customer’s payments. The customer receives a hard copy of the invoice. Identified data movements: E week number R read deliveries R read customer data W store invoice E print customer data E print customer related deliveries E print invoice totals E message handling The Functional Process consists of a set of 8 data movements; the size is 8 CFP.

Real‐time Example A domestic oven allows the to set a

target temperature and then press ‘start’ for the oven to heat up and maintain the temperature. The first functional process has the following data movements: E Start this functional process from menu E Set target temperature X Display target temperature W Store target temperature

Real time Example Contd.. Total size: 4 CFP The second functional process has E Start clock which repeats every 10 secs E Obtain current oven temperature R Retrieve target temperature X Set heater on/off, depending on temp X Display current temperature X Sound audible signal when target temperature is first reached Total size: 6 CFP

Benefits  It is based on fundamental software

engineering principles, so ‘future‐proof’.  It s realistic scheduling and budgeting;  It is simple to learn and easy to use.  s communication between principal, and supplier.  It is applicable in most software domains.  It is applicable for complete applications and for components, in any layer.

THANK YOU