Systems Analysis and Design

2. Project Planning
Course Outline

1.Introduction

2.ProjectPlanning

3.SystemAnalysis

4.SystemDesign

5.SystemImplementation
Recap
• The systems analyst is a key person analyzing the business,
identifying opportunities for improvement, and designing
information systems to implement these ideas
• The Systems Development Lifecycle consists of four stages:
Planning, Analysis, Design, and Implementation
• The major development methodologies:
1. Structured Design
1. Waterfall method
2. Parallel development
2. Rapid Application Development
1. Phased Development
2. Prototyping
3. Throw-away Prototyping
3. Agile Development
1. Extreme Programming
2. Scrum
3
SDLC and Deliverables
Planning
(System Proposal)

Implementation Analysis
(New System) (System Specification)

Design
(System Specification)

4
2. Project Planning
2.1 Identifying Business Value (System Request)
2.2 Feasibility Analysis
2.3 Project Size Estimation

5
2.1 Identifying Business Value
(System Request)

6
When Do Projects Begin?
• When someone sees an opportunity to
create business value from using
information technology
• Then he or she creates a system request
• Feasibility analysis is used to aid in the
decision of whether or not to proceed
with the project
• Project estimation is important activity
which aims to estimating the size of
software project
7
Planning (System Proposal)

8
Elements of a System Request
1. Project Name
• The name of project
2. Project sponsor
• Primary point of contact for the project
3. Business Need
• Reason prompting the project
• Why the project should be funded
4. Business Requirements
• Business features and capabilities the system will need to have
• Can be replaced by Use Case Diagram
5. Business Value
• Benefits the organization can expect from the project
• Tangible value (a quantiable value) and intangible value (intuitive believe)
6. Special issues
• Anything else that should be considered
• Budget constraints, deadline, Legal requirements

9
 System Request
Elemen Deskripsi Contoh
Business The business-related Increase sales
Need reason for initiating the Improve market share
software development Improve access to information
project Improve customer service
Decrease product defects
Streamline supply acquisition processes

Business The business capabilities Provide onIine access to information

Requirements that software will Capture customer demographic information
provide Include product search capabilities
Produce management reports
Include online user support

Business The benefits that the 3% increase in sales

Value software will create for % increase in market share
the organization 10% operational cost reduction
$200,000 cost savings from decreased supply costs
$150,000 savings from removal of existing system

10
 Sofware Quality?

• Software quality is (IEEE, 1991):

1. The degree to which a
system, component, or
process meets specified
requirements
2. The degree to which a
system, component, or
process meets customer or
user needs or expectations
(benefits)

• Quality means conformance

to requirements (Crosby, 1979)
11
System Request: CD Selection Project
Project Sponsor: Margaret Mooney, Vice President of Marketing
Business Needs: This project has been initiated to reach new Internet customers and to better serve
existing customers using Internet sales support

Business Requirements:
Using the Web, customers should be able to search for products and identify the brick-and-mortar stores that
have them in stock. They should be able to put items on hold at a store location or place an order for items
that are not carried or not in stock. The functionality that the system should have is listed below:
1. Search through the CD Selections’ inventory of products
2. Identify the retail stores that have the product in stock
3. Put a product on hold at a retail store and schedule a time to pick up the product
4. Place an order for products not currently in stock or not carried by CD Selections
5. Receive confirmation that an order can be placed and when it will be in stock

Business Value:
Intangible Value:
 Improve customer satisfaction
 Increase brand recognition due to its Internet presence
Tangible Value:
 Increase sales by reducing lost sales due to out-of-stock or nonstocked items and by reaching out to
new customers through its Internet presence
• $750,000 in increased sales from new customers
• $1,875,000 in increased sales from existing customers
 Reduce customer complaints, primarily because 50 percent of all customer complaints stem from
out of stocks or nonstocked items
• $50,000 yearly reduction in customer service calls

12
System Request: CD Selection Project
Project Sponsor: Margaret Mooney, Vice President of Marketing
Business Needs: Project ini dibangun untuk:
1. Mendapatkan pelanggan baru lewat Internet

2. Memberikan layanan pendukung dengan menggunakan internet

Business Requirements:
CD Selection project adalah sistem yang mendukung penjualan CD lewat internet. Fitur-fitur
yang harus ada di sistem ini adalah sebagai berikut:
1. Fitur Pencarian Produk
2. Fitur Pencarian Toko yang Menyediakan Stok Produk
3. Fitur Pemesanan Produk Melalui Toko yang Menyediakan
4. Fitur Pembayaran dengan Berbagai Pilihan Pembayaran

Business Value:
Intangible Value:
 Meningkatkan kepuasan pelanggan
 Meningkatkan brand recognition tentang perusahaan di dunia Internet
Tangible Value:
1. Meningkatkan penjualan dari pelanggan baru lewat Internet:
• Rp.400.000.000,- peningkatan penjualan dari pelanggan baru dan
Rp. 600.000.000,- dari pelanggan lama
2. Mengurangi biaya operasional untuk menangani komplain dari pelanggan
• Rp.100.000.000,- pengurangan tahunan biaya telepon untuk menangani pelanggan

13
Exercise: Membuat System Request
1. Lihat contoh System Request untuk
Internet Order Project (CD Selection)
2. Pikirkan suatu sistem* yang saat ini
dibutuhkan oleh perusahaan atau
organisasi anda
3. Buat System Request dari sistem
tersebut

* System request yang anda buat akan menjadi

studi kasus dari pembelajaran kita selama course
berlangsung
14
2.2 Feasibility Analysis

15
Feasibility Analysis

1. Technical feasibility: Can we build it?

2. Economic feasibility: Should we build it?

3. Organizational feasibility: If we build it, will

they come?

16
 Feasibility Analysis Template
Technical Feasibility: Can We Build It?
1. Familiarity with Application: Less familiarity generates more risk
2. Familiarity with Technology: Less familiarity generates more risk
3. Project Size: Large projects have more risk
4. Compatibility: The harder it is to integrate the system with the company’s
existing technology, the higher the risk

Economic Feasibility: Should We Build It?

1. Return on Investment (ROI) over 3 years
2. Break-even Point (BEP)
3. Total benefit after 3 years

Organizational Feasibility: If We Build It, Will They Come?

1. Project champion(s)
2. Senior management
3. Users
4. Other stakeholders
5. Is the project strategically aligned with the business?

17
 Technical Feasibility

Familiarity with • Knowledge of business domain

application • Need to understand improvements
• Need to recognize pitfalls and bad ideas
Familiarity with • Is technology new to this organization?
technology • Is this a brand new technology?
• Extension of existing firm technologies
Project size • Number of people, time, and features
Compatibility • Systems are not built in a vacuum
• Needs to integrate with current systems and data

18
Economic Feasiblity – Cost Benefit Analysis

• Project costs and benefits over several years

(3-5 years)
• Use normal growth rates for sales etc.
• Total added to determine
• Overall Benefits = Total Benefits – Total Costs
• Higher number is better

19
Economic Feasiblity – Definition and Formula

20
Cash Flow Plan

21
Present Value (PV)

• The amount of an investment today compared

to the same amount n years in the future
• Taking into account inflation and time

Amount
PV =
(1 + Interest Rate)n

22
Net Present Value

537,201
1  0.035

 463,395

23
Net Present Value (NPV)
The present value of benefit less the
present value of cost

NPV = PV Benefits – PV Costs

24
NPV Calculation

3,204,752  2,575,331
 629,421



25
Return on Investment (ROI)
The amount of revenue or cost savings
results from a given investment

Total Benefits – Total Costs

ROI = Total Costs

26
ROI Calculation

3,204,752  2,575,331
2,575,331
 0.2444

27
Break Even Point (BEP)
The point in time when the costs of the
project equal the value it has delivered

BEP = Yearly NPV* – Cumulative NPV

Yearly* NPV
* Use the yearly NPV amount from the first year in which
project has positive cash flow

28
Break Even Point (BEP)

29
Organizational Feasibility
• Strategic Alignment
• How well does the project match up with the business
strategy?

• Stakeholder analysis considers

• Project champion
• High-level non-IS executive
• Shepherds project to completion
• It's good to have more than one
• Organizational management
• Need this support to sell system to organization
• System users
• In the loop so end system meets needs

30
Planning (System Proposal)

31
System Request: CD Selection Project
Project Sponsor: Margaret Mooney, Vice President of Marketing
Business Needs: Project ini dibangun untuk:
1. Mendapatkan pelanggan baru lewat Internet

2. Memberikan layanan pendukung dengan menggunakan internet

Business Requirements:
CD Selection project adalah sistem yang mendukung penjualan CD lewat internet. Fitur-fitur
yang harus ada di sistem ini adalah sebagai berikut:
1. Fitur Pencarian Produk
2. Fitur Pencarian Toko yang Menyediakan Stok Produk
3. Fitur Pemesanan Produk Melalui Toko yang Menyediakan
4. Fitur Pembayaran dengan Berbagai Pilihan Pembayaran

Business Value:
Intangible Value:
 Meningkatkan kepuasan pelanggan
 Meningkatkan brand recognition tentang perusahaan di dunia Internet
Tangible Value:
1. Meningkatkan penjualan dari pelanggan baru lewat Internet:
• Rp.400.000.000,- peningkatan penjualan dari pelanggan baru dan
Rp.600.000.000,- dari pelanggan lama
2. Mengurangi biaya operasional untuk menangani komplain dari pelanggan
• Rp.100.000.000,- pengurangan tahunan biaya telepon untuk menangani pelanggan

32
 Feasibility Analysis Template
Technical Feasibility: Can We Build It?
1. Familiarity with Application: Less familiarity generates more risk
2. Familiarity with Technology: Less familiarity generates more risk
3. Project Size: Large projects have more risk
4. Compatibility: The harder it is to integrate the system with the company’s
existing technology, the higher the risk

Economic Feasibility: Should We Build It?

1. Return on Investment (ROI) over 3 years
2. Break-even Point (BEP)
3. Total benefit after 3 years

Organizational Feasibility: If We Build It, Will They Come?

1. Project champion(s)
2. Senior management
3. Users
4. Other stakeholders
5. Is the project strategically aligned with the business?

33
CD Selection Internet Order Feasibility Analysis Executive Summary
Margaret Mooney and Alec Adams created the following feasibility analysis for the CD Selections Internet
Order System Project. The System Proposal is attached, along with the detailed feasibility study

Technical Feasibility
The Internet Order System is feasible technically, although there is some risk.

CD Selections’ risk regarding familiarity with the application is high

• The Marketing Department has little experience with Internet-based marketing and sales
• The IT Department has strong knowledge of the company’s existing order systems; however, it has
not worked with Web-enabled order systems
CD Selections’ risk regarding familiarity with the technology is medium
• The IT Department has relied on external consultants and an Information Service Provider to
develop its existing Web environment
• The IT Department has learned about Web technology by maintaining the corporate site
• Development tools and products for commercial Web application development are available in the
marketplace, although the IT department has little experience with them
The project size is considered medium risk
• The project team likely will include less than ten people
• Business user involvement will be required
• The project timeframe cannot exceed a year because of the Christmas holiday season
implementation deadline, and it should be much shorter
The compatibility with CD Selections’ existing technical infrastructure should be good
• The current Order System is a client-server system built using open standards. An interface with
the Web should be possible
• Retail stores already place and maintain orders electronically
• An Internet infrastructure already is in place at retail stores and at the corporate headquarters

34
Economic Feasibility
A cost–benefit analysis was performed; see attached spreadsheet for details. A conservative
approach shows that the Internet Order System has a good chance of adding to the bottom line
of the company significantly.
• Return on Investment (ROI) over 3 years: 229 percent
• Break-even point (BEP): after 1.7 years
• Total benefit after three years: $3.5 million (adjusted for present value)
Intangible Costs and Benefits
• Improved customer satisfaction
• Greater brand recognition

Organizational Feasibility
• From an organizational perspective, this project has low risk. The objective of the system,
which is to increase sales, is aligned well with the senior management’s goal of increasing
sales for the company. The move to the Internet also aligns with Marketing’s goal to become
more savvy in Internet marketing and sales.
• The project has a project champion, Margaret Mooney, Vice President of Marketing.
Margaret is well positioned to sponsor this project and to educate the rest of the senior
management team when necessary. To date, much of senior management is aware of and
supports the initiative.
• The users of the system, Internet consumers, are expected to appreciate the benefits of CD
Selections’ Web presence. And, management in the retail stores should be willing to accept
the system, given the possibility of increased sales at the store level.

35
 2003 2004 2005 Total
Increased sales from new customers 0 750,000 772,500  
Increased sales from existing customers 0 1,875,000 1,931,250  
Reduction in customer complaint calls 0 50,000 50,000  
Total Benefits: 0 2,675,000 2,753,750  
PV of Benefits: System Request 0 2,521,444 2,520,071 5,041,515
PV of All Benefits: (Business Value) 0 2,521,444 5,041,515  
Labor: Analysis, Design and Implementation 162,000 0 0  
Consultant Fees 50,000 0 0  
Office Space and Equipment 7,000 0 0  
Software and Hardware 35,000 0 0  
Total Development Costs: 254,000 0 0  
Labor: Webmaster 85,000 87,550 90,177  
Labor: Network Technician 60,000 61,800 63,654  
Labor: Computer Operations 50,000 51,500 53,045  
Labor: Business Manager 60,000 61,800 63,654  
Labor: Assistant Manager 45,000 46,350 47,741  
Labor: 3 Staff 90,000 92,700 95,481  
Software upgrades and licenses 4,000 1,000 1,000  
Hardware upgrades 5,000 3,000 3,000  
User training 2,000 1,000 1,000  
Communications charges 20,000 20,000 20,000  
Marketing expenses 25,000 25,000 25,000  
Total Operational Costs: 446,000 452,700 464,751  
Total Costs: 700,000 452,700 464,751  
PV of Costs: 679,612 426,713 425,313 1,531,638
PV of all Costs: 679,612 1,106,325 1,531,638  
Total Project Costs Less Benefits: (700,000) 2,222,300 2,288,999  
Yearly NPV: (679,612) 2,094,731 2,094,758 3,509,878
Cumulative NPV: (679,612) 1,415,119 3,509,878  
Return on Investment (ROI): (3,509,878/1,531,638)   = 229.16%
Break-even Point (BEP): BEP in Year 2 = 1 + ( (2,094,731 – 1,415,119)/ 2,094,731 = 1.32 years
36
 Studi Kelayakan Sistem Penjualan CD
Margaret Mooney dan Alec Adams membuat studi kelayakan untuk pengembangan
Sistem Penjualan CD
Kelayakan Teknis
Sistem Penjualan CD layak secara teknis, meskipun memiliki beberapa risiko.
Risiko Berhubungan dengan Kefamilieran dengan Aplikasi: Resiko Tinggi
• Divisi Marketing tidak memiliki pengalaman menggunakan sistem penjualan online
• Divisi IT memiliki pemahaman yang baik tentang sistem penjualan CD, akan tetapi tidak
berpengalaman mengembangkan sistem penjualan CD berbasis web (online)
Risiko Berhubungan dengan Kefamilieran dengan Teknologi: Resiko Sedang
• Divisi IT tidak menguasai masalah infrastruktur dan ISP, tetapi akan menyewa konsultan
• Divisi IT cukup familier dengan framework dan IDE yang akan digunakan
• Divisi Marketing tidak memiliki pengalaman menggunakan teknologi Web
Risiko berhubungan dengan Ukuran Project: Risiko Rendah
• Perusahaan memiliki total 30 orang pengembang
• Project dikerjakan oleh 5 orang pengembang dengan estimasi waktu 6 bulan
Kompatibilitas dengan sistem dan infrastruktur yang ada: Risiko Rendah
• Sistem pemesanan yang ada sekarang menggunakan open standard, jadi sangat
kompatibel dengan sistem penjualan berbasis web yang akan dibangun

37
Kelayakan Ekonomi
Cost benefit analysis telah dilakukan. Sistem Penjualan CD memiliki peluang yang baik
untuk bisa meningkatkan pendapatan perusahaan.
• Return on Investment (ROI) setelah 3 tahun: 26.2%
• Break-even point (BEP): 2.28 tahun
• Total keuntungan setelah 3 tahun: Rp.429.878.356,-

Keuntungan Intangible
• Meningkatkan kepuasaan pelanggan
• Meningkatkan branding perusahaan

Kelayakan Organisasi
• Secara organisasi, resikonya rendah. Tujuan dari pengembangan sistem penjualan
CD adalah meningkatkan penjualan perusahaan. Dan ini selaras dengan KPI divisi
marketing yang ke arah peningkatan kuantitas penjualan
• Project champion dari pengembangan Sistem Penjualan CD ini adalah Margaret
Mooney, Vice President of Marketing

38
  2016 2017 2018
Peningkatan penjualan dari pelanggan baru 0 400,000,000 500,000,000
Peningkatan penjualan dari pelanggan lama 0 600,000,000 700,000,000
Pengurangan biaya operasional dan telepon 0 100,000,000 100,000,000
Total Benefits: 0 1,100,000,000 1,300,000,000
PV of Benefits: System Request 0 978,996,084 1,091,505,068
PV of All Benefits: (Business Value) 0 978,996,084 2,070,501,152
Honor Tim (Analysis, Design and Implementation) 360,000,000 0 0
Honor Konsultan 90,000,000 0 0
Total Development Costs: 450,000,000 0 0
Honor Pengelola Web 60,000,000 70,000,000 80,000,000
Biaya Lisensi Software 50,000,000 60,000,000 70,000,000
Hardware upgrades 100,000,000 100,000,000 100,000,000
Biaya Komunikasi 20,000,000 30,000,000 40,000,000
Biaya Marketing 100,000,000 200,000,000 300,000,000
Total Operational Costs: 330,000,000 460,000,000 590,000,000
Total Costs: 780,000,000 460,000,000 590,000,000
PV of Costs: 735,849,057 409,398,362 495,375,377
PV of all Costs: 735,849,057 1,145,247,419 1,640,622,796
Total Project Costs Less Benefits: -780,000,000 640,000,000 710,000,000
Yearly NPV: -735,849,057 569,597,722 596,129,691
Cumulative NPV: -735,849,057 -166,251,335 429,878,356
Return on Investment (ROI) di Tahun 3: 26.2% 429,878,356/1,640,622,796 0.262021445
2 + (596,129,691-429,878,356)/
Break-even Point (BEP): 2.28 tahun 2.278884507
596,129,691
39
Exercise: Membuat Feasibility Analysis

1. Lihat contoh Feasibility Analysis untuk Internet

Order Project
2. Perhatikan kembali System Request yang
sebelumnya sudah kita buat
3. Buat Feasibility Analysis dari system yang akan
kita buat tersebut
4. Kirim file System Request (PPT) dan Economic
Feasibility (XLS) ke [email protected]

40
2.3 Project Size Estimation

41
 “Size” of Software Systems

Source: Wikipedia

42
“Size” of Software Systems

Caper Jones, The Economic of

Software Quality (2012)

43
 Software Effort Estimation Methods

1. SimplyMethod 2.FunctionPoint 3.UseCase Point

(IndustryStdPercentages) (Allen Albrecht, 1979) (GustavKarner, 1993)

• Use the time spent for • Estimate System Size • Estimate System Size (Use
planning (Function Point) Case Points)
• Along with industry • EstimateEffortRequired(Pe • Estimate Effort Required
standard percentages rson-Month) (Person-Month)
• Estimate the overall time • EstimateTimeRequired(Mo • Estimate Time Required
for the project nth) (Month)

44
1. Simply Method

45
Simply Method

46
Time Spent for Each Phase

We are given that

Planning time  0.15  Overall time
so
Planning time
Overall time 
0.15

Planning time
Analysis time  0.2 
0.15

47
Estimate the Overall Time

Planning Analysis Design Implementation

Industry
Standard
For Web 15% 20% 35% 30%
Applications

Effort
Required 4 5.33 9.33 8
in Time (month)

4
Example: Analysis 0.2 month  5.33
0.15

48
2. Function Point

49
Function Point Approach

(Allen Albrecht, 1979)

50
A. Function Points Estimation
-- Step One (TUFP)

Complexity

Description Low Medium High Total

Inputs __x 3 __x 4 __x 6 ____

Outputs __x 4 __x 5 __x 7 ____

Queries __x 3 __x 4 __x 6 ____

Files __x 7 __x 10 __x 15 ____

Program __x 5 __x 7 __x 10 ____

Interfaces

TOTAL UNADJUSTED FUNCTION POINTS ____

51
Example: CD Selection System

52
Function Points Estimation
-- Step Two (Processing Complexity)
Scale of 0 to 3

Data Communications _____

Heavy Use Configuration _____
Transaction Rate _____
End-User efficiency _____
Complex Processing _____
Installation Ease _____
Multiple sites _____
Performance _____
Distributed functions _____
On-line data entry _____
On-line update _____
Reusability _____
Operational Ease _____
Extensibility _____

Processing Complexity (PC) _____

53
Example: CD Selection System

54
Function Point Estimation
-- Step Three (TAFP)

Processing Complexity (PC) = 7

(From Step Two)

Adjusted Processing
Complexity (PCA) = 0.65 + (0.01 * 7 ) = 0.72
Total Adjusted
Function Points (TAFP): 338 * 0.72 = 243
(From Step One)

55
Adjusted Processing Complexity

Choose standard Adjusted Project

Complexity (PCA) from the range:
1. 0.65 Simple systems
2. 1.0 "Normal" systems
3. 1.35 Complex systems

56
Converting Function Points to Lines of Code

Language LOC/Function Point

C 130
COBOL 110
JAVA 55
C++ 50
Turbo Pascal 50
Visual Basic 30
PowerBuilder 15
HTML 15
Packages 10-40
(e.g., Access, Excel)

Source: Capers Jones, Software Productivity Research

57
58
Lines of Codes (LOC)

Line of Codes (LOC) = TAFP * LOC/TAFP

Example:

If TAFP = 243 Then we build the software using Java

LOC = (243 * 55) = 13365 line of codes

59
Contoh Jenis Aplikasi dan FP

Caper Jones, The Economic of

Software Quality (2012)

60
B. Estimating Effort

Effort = 1.4 * thousands-of- lines-of-code

(in Person- Months)

Example:

If LOC = 13365 Then...

Effort = (1.4 * 13.365) = 18.711 Person Months

61
C. Estimating Time

Time = 3.0 * person-months1/3

(in Months)

Example:

If LOC = 13365 Then...

Effort = (1.4 * 13.365) = 18.711 person-months
Time = 3.0 * 18.711 1/3 = 7.9 month

Boehm’s Third Law (1981):

62
Boehm’s Third Law (1981)

Development effort is a non-linear

function of product size

63
DeMarco-Glass Law (1982)

Most cost estimates tend

to be too low

64
 Hitung Size dari Sistem dengan Function Point (TUFP
– TAFP – LOC – PM – M)
• Sebuah perusahaan membutuhkan sistem job seeker untuk pencari
kerja dan perusahaan pembuka lowongan pekerjaan
• Sistem memungkinkan pencari kerja untuk menginput data curriculum
vitae. Di sisi lain, perusahan pembuka lowongan kerja bisa menginput
data perusahaan dan lowongan pekerjaan yang disediakan
• Pencari kerja dapat melakukan pencarian (query) tentang lowongan
pekerjaan apa saja yang tersedia, sedangkan pembuka lowongan kerja
mencari tentang siapa saja yang sudah mendaftar di suatu lowongan
pekerjaan
• Sistem mampu memproduksi laporan statistik lengkap tentang pencari
kerja, perusahaan, jenis lowongan pekerjaan dan tren lowongan kerja
yang sedang populer
• Laporan statistik akan disajikan dalam bentuk infografik dan juga
tersedia dalam bentuk file pdf yang bisa didownload
• Sistem akan dikembangkan dengan menggunakan bahasa Java
65
TUFP
Complexity

Description Low Medium High Total

Inputs __x 3 __x 4 __x 6 ____

Outputs __x 4 __x 5 __x 7 ____

Queries __x 3 __x 4 __x 6 ____

Files __x 7 __x 10 __x 15 ____

Program __x 5 __x 7 __x 10 ____

Interfaces

TOTAL UNADJUSTED FUNCTION POINTS ____

67
 TUFP
Fungsi Bobot (Low) Total
Input 3 3 9
Output 4 4 16
Queries 2 3 6
File 2 7 14
Program Interface 5 5 25

TUFP 70

68
Processing Complexity
• Data Communications1
• Heavy Use Configuration 0
• Transaction Rate 0
• End-User efficiency 0
• Complex Processing 0
• Installation Ease 0
• Multiple sites 0
• Performance 0
• Distributed functions 0
• On-line data entry 2
• On-line update 2
• Reusability 0
• Operational Ease 1
• Extensibility 0
TOTAL 6
69
TAFP
• Processing Complexity (PC) = 6

• Adjusted Processing
Complexity (PCA) = 0.65 + (0.01 * 6 ) = 0.71

• Total Adjusted
Function Points (TAFP): 70 * 0.71 = 49.7

70
LOC  Effort (ManMonth) Time (Month)

1. LOC = 55*49.7 = 2733.5

2. Effort = 1.4*2.7335 = 3.83 MM

3. Time = 3.0 * 3.83 (1/3) = 4.6 M

71
Example: Schedule
Fase M PM Cost
1 Planning 1 3 10
2 Analysis 2 3 40
3 Design 2 5 20
4 Implementation 4 6 90
160jt

72
Exercise: Software Size Estimation dengan
Function Point Approach

• Kembali ke System Request yang sudah kita

buat

• Lakukan Software Size Estimation dengan

menggunakan Function Point Approach
untuk System Request yang sudah kita buat

73
3. Use Case Point

74
 Use Case Points
Unadjusted Actor Weighting (UAW)
Actor Type Description Weighting Factor
Simple External System with well-defined API 1
Average External System using a protocol- 2
based
interface, e.g., HTTP, TCT/IP, SQL
Complex Human 3

Unadjusted Use Case Weighting (UUCW)

Use-Case Type Description Weighting Factor
Simple 1-3 transactions 5
Average 4-7 transactions 10
Complex More than 7 transactions 15

Unadjusted Use Case Points (UUCP) = UAW + UUCW

75
 Sistem AT M Sistem AT M

Sistem ATM – Use Case Diagram

uc UCD - Sistem ATM Memasukkan PIN
Memasukkan Kartu Memasukkan PIN
Memasukkan Kartu
«include» «include»
Sistem AT M
Sistem AT M

Memasukkan Kartu Memasukkan PIN

Human = 3
Memasukkan KartuMengecek Saldo
«include»
Memasukkan PIN
Mengecek Saldo
«include»

Transaction = ?
Pengguna
Mentransfer Uang Mengecek Saldo Uang
Mentransfer
Mengecek Saldo

Pengguna
Mentransfer Uang
Melakukan
Mentransfer
LogoutUang Melakukan Logout
Mengambil Uang Mengambil Uang

Melakukan Logout Mengambil Uang

ukan Logout Mengambil Uang

76
Activity Diagram: Mengirim Uang
act 5 AD Mengirim Uang

Nasabah Sistem ATM Sistem Inti Perbankan

Mulai
Transaction=3
Pilih Kirim Uang Tampilkan Menu
di Menu Utama Pengiriman Uang

Masukan No Request Validasi No Validasi No Rekening

Rekening Tuj uan Rekening Tuj uan Tuj uan

tidak No Rekening Valid?

Tampilkan Error No
Rekening Tidak Valid

ya
Masukan Jumlah Tampilkan Isian
Uang Jumlah Uang

tidak

Request Cek Cek Kecukupan Saldo

Kecukupan Saldo

Saldo Cukup?

ya

Tampilkan Pesan Proses Pengiriman

Uang Berhasil Dikirim Uang

Selesai
77
 Sequence Diagram: Mengirim Uang
sd 5 SD Mengirim Uang

:Nasabah
MenuUtama MenuPengirimanUang Manaj erPengirimanUang Account Pengirim:Balance Penerima:Balance

pilihKirimUang()

Transaction=3
tampilkan()

masukanAccountTujuan()
validasiAccount()
getID()
tampilkan(hasil)

masukanJumlahUang()

cekKecukupan Saldo(id)
getSaldo()

alt Saldo Cukup?

[tidak] tampilkan(pesanKesalahan)

[ya]
kirimUang(idPengirim, idPenerima, jumlah)

setSaldo(saldo)

setSaldo(saldo)

78
Technical Complexity Factors (TCF)
Factor Description Weight
Number
T1 Distributed system 2.0
T2 Response time or throughput performance 1.0
objectives
T3 End-user online efficiency 1.0
T4 Complex internal processing 1.0
T5 Reusability of code 1.0
T6 Easy to install 0.5
T7 Ease of use 0.5
T8 Portability 2.0
T9 Ease of change 1.0

TCF = 0.6 + (0.01 * TFactor)

79
Environmental Complexity Factors (ECF)

Factor Description Weight

Number
E1 Familiarity with system development process in use 1.5
E2 Application experience 0.5
E3 Object-oriented experience 1.0
E4 Lead analyst capability 0.5
E5 Motivation 1.0
E6 Requirements stability 2.0
E7 Part time staff -1.0
E8 Difficulty of programming language -1.0

ECF = 1.4 + (-0.03 * EFactor)

80
Computing Use Case Points

• Adjusted Use Case Points (UCP) = UUCP * TCF * ECF

• Effort in Person Hours = UCP * PHM

81
 Person Hour Multiplier (PHM)

Let F1 = Number of ECF1 to ECF6 that are < 3

Let F2 = Number of ECF7 and ECF8 that are > 3

If F1 + F2 <= 2
PHM = 20
Else if F1 + F2 = 3 or 4
PHM = 28
Else
Scrap the project

82
Computing Use Case Points with Sparx EA

83
84
85
Use Case Points in Sparx EA

86
87
Estimation Factors

88
Estimation Factors (Environment)

89
Estimation Factors (Technical)

90
Example: Sistem ATM
UCP = 33
PHM = 20
PH = 20*33 = 660 PH
28*33 = 924

PM = 660/8/22 = 3.75 PM
= 924/8/22 = 5.25 PM

TIME (M)= 3.0 * PM 1/3

TIME (M) = 3.0 * 3.75 1/3 = 4.6 M
= 3.0 * 5.25 1/3 = 5.21 M
91
Example: Sistem ATM
UCP = 42
PHM = 20
PH = 20*42 = 860 PH

PM = 860/8/22 = 4.8 PM
= 660/10/26 = 2.5 PM (LEMBUR)
TIME (M)= 3.0 * PM 1/3
TIME (M) = 3.0 * 4.8 1/3 = 5.1 M
= 3.0 * 2.5 1/3 = 4 M (LEMBUR)

92
Example: Schedule
Fase M PM Cost
1 Planning 1 2 10
2 Analysis 2 2 40
3 Design 2 4 20
4 Implementation 4 8 90
160jt

93
Example: Sistem ERP
UCP = 662
PHM = 20
PH = 20*662 = 13240
PM = 13240/8/22 = 75
PM = 13240/10/26 = 50

TIME (M)= 3.0 * PM 1/3

TIME (M) = 3.0 * 75 1/3 = 12.65
TIME (M) = 3.0 * 50 1/3 = 11.05

94
Example: Sistem Service Desk
UCP = 106
PHM = 20
PH = 20*106 = 2120
PM = 2120/10/26 = 8.2

TIME (M)= 3.0 * PM 1/3

TIME (M) = 3.0 * 8.2 1/3 = 6.03

95
Exercise: Selesaikan Fase Planning

1. Selesaikan seluruh tahapan planning

(system request, feasibility analysis, cost-
benefit analysis, project size estimation)
untuk sistem yang kita akan kembangkan

2. Kirimkan via email seluruh dokumen yang

telah dibuat: system request, feasibility
analysis, project size estimation (pptx),
cost-benefit analysis (xlsx)

96
Summary
1. Project initiation involves creating and assessing
goals and expectations for a new system
2. Identifying the business value of the new project is
a key to success
3. The system request describes an overview of the
proposed system.
4. The feasibility study is concerned with insuring that
technical, economic, and organizational benefits
outweigh costs and risks
5. Project estimation methods: simply method,
function point and use case point

97
References
1. Alan Dennis et al, Systems Analysis and Design with UML 4th Edition,
John Wiley and Sons, 2013
2. Kenneth E. Kendall and Julie E Kendall, Systems Analysis and Design 8th
Edition, Prentice Hall, 2010
3. John W. Satzinge, Robert B. Jackson, Stephen D. Burd, Systems Analysis
and Design in a Changing World 6th Edition, Course Technology, 2012
4. Hassan Gomaa, Software Modeling and Design: UML, Use Cases,
Patterns, and Software Architectures, Cambridge University Press,
2011
5. Gary B. Shelly and Harry J. Rosenblatt, Systems Analysis and Design 9th
Edition, Course Technology, 2011
6. Howard Podeswa, UML for the IT Business Analyst 2nd Edition, Course
Technology, 2009
7. Jeffrey A. Hoffer et al, Modern Systems Analysis and Design 6th Edition,
Prentice Hall, 2010

98