SQM – Function Point Method. The function point method  The Function point approach for software sizing was invented by Allan Albrecht in 1979  The.

Slides:



Advertisements
Presentasi serupa
Pertemuan 2 Pengantar Pengembangan Sistem
Advertisements

CHAPTER 7 Pengembangan Sistem
INTERAKSI MANUSIA DAN KOMPUTER
Tahapan information engineering
ARTIFICIAL INTELLIGENCE
PROJECT MANAGEMENT MANPRO-M5 : PERENCANAAN PROYEK LANJUT am/page : 1 of 20 PERENCANAAN PROYEK LANJUT SESI : 5 BY ARISM,SKOM,MMSI.
ANALISIS DAN PERANCANGAN SISTEM
KONTROL ALUR EKSEKUSI PROGRAM
Bahan Ajar disusun oleh Budi Susanto, S.Kom,MT
Struktur Organisasi *Studi Kasus: Restrukturisasi Dinkes
Information Systems, Organizations, and Strategy
Managing Software Requirements (manajemen kebutuhan perangkat lunak)
ORGANISASI YANGEFEKTIF, BERKEMBANG DAN MAPAN
Software Measurement FUNCTION POINT.
Training, Learning, and Development Strategy
Software Project Planning Departemen Ilmu Komputer IPB 2009.
1 Pertemuan 1 Introduction Matakuliah: sistem Operasi Tahun: 2010.
Learning Outcomes Pada akhir pertemuan ini, diharapkan mahasiswa akan mampu : Mahasiswa dapat membuat diagram / skema untuk assessment setiap tahap pengembangan.
Game Theory Purdianta, ST., MT..
KONSEP STRATEGI BISNIS DAN IMPLIKASINYA PADA STRATEGI IS/IT
WaterfallPrototyping RAD Incremental Prototyping Pendekatan SDLC.
Presented By : Group 2. A solution of an equation in two variables of the form. Ax + By = C and Ax + By + C = 0 A and B are not both zero, is an ordered.
ANALISA PERANCANGAN SISTEM
Bina Nusantara Model Simulasi Peretemuan 23 (Off Clas) Mata kuliah: K0194-Pemodelan Matematika Terapan Tahun: 2008.
Testing Implementasi Sistem Oleh :Rifiana Arief, SKom, MMSI
Constructive Cost Model
Inventory Management. Introduction Basic definitions ? An inventory is an accumulation of a commodity that will be used to satisfy some future demand.
Oleh: SARIPUDIN Jurusan SISTEM INFORMASI
© 2009 Fakultas Teknologi Informasi Universitas Budi Luhur Jl. Ciledug Raya Petukangan Utara Jakarta Selatan Website:
Rekayasa Perangkat Lunak (Software Engineering)
Organisasi dan arsitektur komputer
Perencanaan Proyek Software
a.k.a structural testing WHITE BOX TESTING clear box testing
Phase III Rapid Prototyping and Demonstration Prototype
1 Pertemuan 21 Function Matakuliah: M0086/Analisis dan Perancangan Sistem Informasi Tahun: 2005 Versi: 5.
1 Pertemuan 22 Analisis Studi Kasus 2 Matakuliah: H0204/ Rekayasa Sistem Komputer Tahun: 2005 Versi: v0 / Revisi 1.
1 Pertemuan 6 Hubungan WCA dan Sistem Informasi Matakuliah: H0472 / Konsep Sistem Informasi Tahun: 2006 Versi: 1.
1 Pertemuan 11 Function dari System Matakuliah: M0446/Analisa dan Perancangan Sistem Informasi Tahun: 2005 Versi: 0/0.
Materi. Introduction In this discussion the appliaction of maintainability to the design process is addressed. The maintainability design process is similar.
9.3 Geometric Sequences and Series. Objective To find specified terms and the common ratio in a geometric sequence. To find the partial sum of a geometric.
1 INTRODUCTION Pertemuan 1 s.d 2 Matakuliah: A0554/Analisa dan Perancangan Sistem Informasi Akuntansi Tahun: 2006.
Iwan Abadi, Ir., M. M.  11.  Tatap Muka  Tugas  Studi kasus  Diskusi  22.
Introduction.  Proses manajemen untuk mengidentifikasi, mengantisipasi dan memuaskan kebutuhan pelanggan secara menguntungkan  Pemasaran adalah proses.
Software Engineering Process
Chapter 6 Foundations of Business Intelligence: Databases and Information Management.
Functional Requirements vs Non Functional Requirements
Pert. 16. Menyimak lingkungan IS/IT saat ini
Rekayasa Perangkat Lunak
5. Proses Perangkat Lunak dan Metrik Proyek
Rekayasa Perangkat Lunak
Software Measurement FUNCTION POINT.
PERENCANAAN PROYEK LANJUT
IMPLEMENTASI FMS.
Information Technologies
Analisis dan Perancangan Sistem Informasi Erik Kurniadi
Rekayasa Perangkat Lunak (Software Engineering)
Organizational Environment Analysis
REKAYASA PERANGKAT LUNAK
REAL NUMBERS EKSPONENT NUMBERS.
INTERAKSI MANUSIA DAN KOMPUTER
Phase III Rapid Prototyping and Demonstration Prototype
ANALISIS & DESAIN SISTEM
Dasar-Dasar Sistem Informasi
Rekayasa Perangkat Lunak Part-5
Master data Management
System Development Life Cycle
BAB 9 TEORI PRODUKSI. 2 Introduction Our focus is the supply side. The theory of the firm will address: How a firm makes cost-minimizing production decisions.
SISTEM PENUNJANG KEPUTUSAN UNTUK SISTEM INFORMASI MANAJEMEN.
BY : LUTFIANI RATNA DEWANTI LILIS SINARSIH Action Research.
A SHORT ESSAY OF CIVIL ENGINEERING BY : ALFATIHATU RAHMI CIVIL ENGINEERING ENGINEERING FACULTY ANDALAS UNIVERSITY PADANG.
Transcript presentasi:

SQM – Function Point Method

The function point method  The Function point approach for software sizing was invented by Allan Albrecht in 1979  The measure of Albrecht - Function Point Analysis (FPA) - is well known because of its great advantages: Independent of programming language and technology. Comprehensible for client and user. Applicable at early phase of software life cycle.

Function Point ??  Function Point adalah sebuah sebuh teknik terstruktur dalam memecahkan masalah dengan cara memecah sistem menjadi komponen yang lebih kecil dan menetapkan beberapa karakteristik dari sebuah software sehingga dapat lebih mudah dipahami dan dianalisis.

Function Point ?? Cont..  Function Point mengukur dari perspektif Functional dari software yang akan dibangun, terlepas dari bahasa programaan, metode development atau platform perangkat keras yang digunakan,

Function Point ?? Cont..  Function Point harus dilakukan oleh orang terlatih dan berpengalaman dalam development software, karena dalam memberikan nilai-nilai dari setiap komponen Function point bersifat subyektif, dan akan wajar apabila hasil perhitungan function point seseorang akan berbeda dengan yang lain

Function Point ?? Cont..  Hasil dari pengukuran menggunakan Function Point dapat digunakan untuk mengestimasi biaya dan effort yang diperlukan dalam development perangkat lunak.

The function point method The function point estimation process:  Stage 1 : Compute crude function points (CFP).  Stage 2 : Compute the relative complexity adjustment factor (RCAF) for the project. RCAF varies between 0 and 70.  Stage 3 : Compute the number of function points (FP): FP = CFP x ( x RCAF)

Crude Function Point??  Crude Function Points (CFP) adalah untuk menghitung bobot nilai dari komponen- komponen Function Point yang dikaitkan dengan software yang akan dibuat.

Calculation of crude function points (CFP) The method relates to the following five types of software system components: ■ Number of user inputs – distinct input applications, not including inputs for online queries.  Berkaitan dengan interface yang dilakukan pengguna/user dalam memasukan data pada aplikasi. ■ Number of user outputs – distinct output applications such as batch processed reports, lists, customer invoices and error messages (not including online queries). ■ Number of user online queries – distinct online applications, where output may be in the form of a printout or screen display. ■ Number of logical files – files that deal with a distinct type of data and may be grouped in a database. ■ Number of external interfaces – computer–readable output or inputs transmitted through data communication, on CD, diskette, etc. The function point method applies weight factors to each component according to its complexity. 9

Software system components Complexity level Total CFP Simpleaveragecomplex Count Weight Factor PointsCount Weight Factor PointsCount Weight Factor Points AB C= AxB DE F= DxE GH I= GxH User inputs User outputs User online queries Logical files External interfaces Total CFP

Calculating the relative complexity adjustment factor (RCAF)  RCAF digunakan untuk menghitung bobot kompleksitas dari software berdasarkan 14 karakteristik.  The relative complexity adjustment factor (RCAF) summarizes the complexity characteristics of the software system and varies between 0 and 70.  Assign grades (0 to 5) to the 14 subjects that substantially affect the required development efforts (Extent of distributed processing, performance requirements …).  RCAF is the sum of grades regarding the 14 subjects. 11

NoSubjectGrade 1 Requirement for reliable backup and recovery Requirement for data communication Extent of distributed processing Performance requirements Expected operational environment Extent of online data entries Extent of multi-screen or multi-operation online data input Extent of online updating of master files Extent of complex inputs, outputs, online queries and files Extent of complex data processing Extent that currently developed code can be designed for reuse Extent of conversion and installation included in the design Extent of multiple installations in an organization and variety of customer organizations Extent of change and focus on ease of use Total = RCAF

Function Point Method An example: The Attend Master 13

Attend Master Software System  Attend-Master is a basic employee attendance system that is planned to serve small to medium-sized businesses employing 10–100 employees.  The system is planned to have interfaces to the company’s other software packages: Human- Master, which serves human resources units, and Wage-Master, which serves the wages units.  Attend-Master is planned to produce several reports and online queries. 14

Calculation of CFP Crude Function Points Analysis of the software system as presented in the DFD summarizes the number of the various components: ■ Number of user inputs – 2 ■ Number of user outputs – 3 ■ Number of user online queries – 3 ■ Number of logical files – 2 ■ Number of external interfaces – 2. The degree of complexity (simple, average or complex) was evaluated for each component. 16

Software system components Complexity level Total CFP Simpleaveragecomplex Count Weight Factor PointsCount Weight Factor PointsCount Weight Factor Points AB C= AxB DE F= DxE GH I= GxH User inputs User outputs User online queries Logical files External interfaces Total CFP 81

Calculation of RCAF Relative Complexity Adjustment Factor

NoSubjectGrade 1 Requirement for reliable backup and recovery Requirement for data communication Extent of distributed processing Performance requirements Expected operational environment Extent of online data entries Extent of multi-screen or multi-operation online data input Extent of online updating of master files Extent of complex inputs, outputs, online queries and files Extent of complex data processing Extent that currently developed code can be designed for reuse Extent of conversion and installation included in the design Extent of multiple installations in an organization and variety of customer organizations Extent of change and focus on ease of use Total = RCAF 41

The ATTEND MASTER – function points calculation FP = CFP x ( x RCAF) FP = 81 x ( x 41) = 85.86

Converting NFP 2 KLOC  The estimates for the average number of lines of code (LOC) required for programming a function point are the following: 21 For C++: KLOC = (85.86 * 64)/1000 = KLOC