Systems Analysis and Design: System Analysis

Presentasi berjudul: "Systems Analysis and Design: System Analysis"— Transcript presentasi:

1 Systems Analysis and Design: System Analysis
Romi Satria Wahono

2 Romi Satria Wahono SD Sompok Semarang (1987) SMPN 8 Semarang (1990)
SMA Taruna Nusantara, Magelang (1993) S1, S2 dan S3 (on-leave) Department of Computer Sciences Saitama University, Japan ( ) Research Interests: Software Engineering, Intelligent Systems Founder dan Koordinator IlmuKomputer.Com Peneliti LIPI ( ) Founder dan CEO PT Brainmatics Cipta Informatika

3 Contents Introduction Project Planning System Analysis System Design System Implementation

4 Recap Identifying the business value of the new project is a key to success The system request describes an overview of the proposed system. The feasibility study is concerned with insuring that technical, economic, and organizational benefits outweigh costs and risks Project estimation methods: simply method, function point and use case point

5 3. SYSTEM ANALYSIS romi@romisatriawahono.net
Object-Oriented Programming 3. SYSTEM ANALYSIS

6 Learning Objectives Understand how to create a requirements definition
Become familiar with requirements analysis techniques Understand when to use each requirements analysis technique Understand how to gather requirements using interviews, JAD sessions, questionnaires, document analysis, and observation Understand when to use each requirements-gathering technique Understand the business process modeling

7 SDLC and Deliverables Planning Analysis (System Specification)
Object-Oriented Programming SDLC and Deliverables Planning (System Proposal) Analysis (System Specification) Design (System Specification) Implementation (New System)

8 System Analysis and Design with UML
Business Process Identification Use Case Diagram Business Process Modeling Activity Diagram or Business Process Modeling Notation (BPMN) Business Process Realization Sequence Diagram (Buat untuk setiap use case dengan menggunakan pola Boundary-Control-Entity) System Design Program Design Class Diagram (Gabungkan Boundary-Control-Entity Class dan susun story dari sistem yang dibangun) Package Diagram (Gabungan class yang sesuai, boleh menggunakan pola B-C-E) Deployment Diagram (arsitektur software dari sistem yang dibangun) User Interface Design (Buat UI design dari Boundary Class) Entity-Relationship Model (Buat ER diagram dari Entity Class)

9 Requirement Gathering

10 What is a Requirement Business Requirement
Statement of what the system must do Focus on what the system must do, not how to do it There are 2 kinds of requirements Functional Nonfunctional

11 Functional Requirement
Defines the functions of the system must carry out Specifies the process that must be performed Examples: Diagrams: Activity Diagrams Use Case Diagrams Problem Statements: Must search for inventory Must perform these calculations Must produce a specific report

12 Nonfunctional Requirements
Deals with how the system behaves: Operational – Physical/technical environment Performance – Speed and reliability Security – Who can use the system Cultural & Political – Company policies, legal issues

13

14 Requirement Gathering Methods
Document Analysis Interviews Joint Application Design (JAD) Questionnaires Observation

15 1. Document Analysis Provides clues about the "formal" existing As-Is system Typical documents Forms Reports Policy manuals Look for user additions to forms Look for unused form elements Do document analysis before interviews

16 2. Interviews Most commonly used technique Very natural
If you need to know something, you ask someone Five basic steps: Selecting interviewees Designing interview questions Preparing for the interview Conducting the interview Post-interview follow-up

17 3. Joint Application Design (JAD)
Allows project managers, users, and developers to work together May reduce scope creep by 50% Avoids requirements being too specific or too vague Include 10 to 20 users Tend to last 5 to 10 days over a three week period

18 JAD Meeting Room JPEG Figure 5-5 Goes Here

19 4. Questionnaire Selecting participants Designing the questionnaire
Using samples of the population Designing the questionnaire More important than interview questions Prioritize questions to grab attention Distinguish between Fact-oriented questions (specific answers) Opinion questions (agree – disagree scale) Test the questionnaire on colleagues

20 4. Questionnaire Questionnaire follow-up
Administering the questionnaire Need to get good response rate Explain its importance & how it will be used Give expected response date Follow up on late returns Have supervisors follow up Promise to report results Questionnaire follow-up Send results to participants

21 5. Observation Users/managers often don’t remember everything they do
Validates info gathered in other ways Behaviors change when people are watched Keep low profile, don’t change the process Careful not to ignore periodic activities Weekly … Monthly … Annual

22 Selecting the Appropriate Techniques
Interviews JAD Questionnaires Document Observation Analysis Type of As-Is As-Is As-Is As-Is As-Is Information Improve Improve. Improve. To-Be To-Be Depth of High High Medium Low Low Information Breadth of Low Medium High High Low Integration Low High Low Low Low of Info. User Medium High Low Low Low Involvement Cost Medium Low Low Low Low- Medium Medium

23 Business Process Analysis

24 Business Process Analysis Steps

25 Business Process Analysis Strategies
BPA (Business Process Automation) BPI (Business Process Improvement) BPR (Business Process Reengineering)

26 Business Process Automation
Makes almost no changes to business processes Just makes them more efficient Improves efficiency by automating the business processes Least impact on users They do the same things, just more efficiently

27 Business Process Improvement
Goal is to improve the business processes Change what the users do, not just how efficiently they do it Changes to business process must be decided first Decisions to change the business processes cannot be made by the analyst

28 Business Process Reengineering
“Fundamental rethinking and radical redesign of business processes to achieve dramatic improvements…” Throw away everything Start with a blank page Appealing, but very expensive and risky

29 Automation Improvement Reeingineering
Strategy Comparation Business Business Business Process Process Process Automation Improvement Reeingineering Potential Business Low-Moderate Moderate High Value Project Cost Low Low-Moderate High Breadth of Analysis Narrow Narrow-Moderate Very Broad Risk Low Low-Moderate Very High

30 Business Process Identification

31 System Analysis and Design with UML
Business Process Identification Use Case Diagram Business Process Modeling Activity Diagram or Business Process Modeling Notation (BPMN) Business Process Realization Sequence Diagram (Buat untuk setiap use case dengan menggunakan pola Boundary-Control-Entity) System Design Program Design Class Diagram (Gabungkan Boundary-Control-Entity Class dan susun story dari sistem yang dibangun) Package Diagram (Gabungan class yang sesuai, boleh menggunakan pola B-C-E) Deployment Diagram (arsitektur software dari sistem yang dibangun) User Interface Design (Buat UI design dari Boundary Class) Entity-Relationship Model (Buat ER diagram dari Entity Class)

32 Use Case Diagram

33 Use Case Diagrams Summarized into a single picture
All of the use cases for the part of the system being modeled Use case represents the discrete activities performed by the user Use Case Diagram tells what the system will do Good for communicating with users

34 Syntax for an Use Case Diagram
Actor person or system that derives benefit from and is external to the subject Use Case Represents a major piece of system functionality Association Relationship Include Relationship Extend Relationship Generalization Relationship <<includes>> <<extends>>

35 Use Case Use Case A major piece of system functionality
Can extend other Use Cases Placed inside system boundary Labeled with descriptive verb - noun phrase Use Case

36 System Boundary Boundary
Includes the name of the system inside or on top Represents the scope of the system Actors are outside the scope of the system Boundary

37 Actor A person or another system that interacts with the current system A role, not a specific user Provides input, receives output, or both actor Actor/Role

38 Association Relationship
Links actor and the Use Case Shows two-way communication If one-way, arrows are used * is for "multiplicity of the Association" * *

39 extend Extends Relationship
Extends Use Case to include Optional behavior Arrow points from the extension Use Case to the base Use Case extend extend Make Appointment Make Payment Arrangement

40 include Include Relationship
Include one Use Case from within another Arrow points from base Use Case to the included Use Case include include Make New Patient Appointment Create New Patient

41 Generalization Relationship
A specialized Use Case to a more generalized Use Case Arrow points from specialized to general Use Case Make Old Appointment Make Appointment

42 Use Case Diagram for Appointment System

43 Use Case Diagram with Specialized Actor

44 Extend and Include Relationships

45 Studi Kasus: ATM System

46 ATM System

47 ATM System Layar Kotak Uang Kotak Kartu Kotak Kuitansi
Object-Oriented Programming ATM System Layar Kotak Uang Kotak Kartu Kotak Kuitansi

48 Masukkan PIN: Kotak Uang Kotak Kartu Kotak Kuitansi
Object-Oriented Programming Masukkan PIN: Kotak Uang Kotak Kartu Kotak Kuitansi

49 Menu Utama Melihat Saldo Mentransfer Uang Mengambil Uang Logout
Object-Oriented Programming Menu Utama Melihat Saldo Mentransfer Uang Mengambil Uang Logout Kotak Uang Kotak Kartu Kotak Kuitansi

50 Saldo anda adalah …. Menu Melihat Saldo Kotak Uang Kotak Kartu
Object-Oriented Programming Menu Melihat Saldo Saldo anda adalah …. Kotak Uang Kotak Kartu Kotak Kuitansi

51 No Account Penerima: Menu Mentransfer Uang Kotak Uang Kotak Kartu
Object-Oriented Programming Menu Mentransfer Uang No Account Penerima: Kotak Uang Kotak Kartu Kotak Kuitansi

52 Jumlah uang yang dikirim:
Object-Oriented Programming Menu Mentransfer Uang Jumlah uang yang dikirim: Kotak Uang Kotak Kartu Kotak Kuitansi

53 Uang berhasil terkirim
Object-Oriented Programming Menu Mentransfer Uang Uang berhasil terkirim Kotak Uang Kotak Kartu Kotak Kuitansi

54 Jumlah uang yang diambil:
Object-Oriented Programming Menu Mengambil Uang Jumlah uang yang diambil: Kotak Uang Kotak Kartu Kotak Kuitansi

55 Uang berhasil diambil Menu Mengambil Uang Kotak Uang Kotak Kartu
Object-Oriented Programming Menu Mengambil Uang Uang berhasil diambil Kotak Uang Kotak Kartu Kotak Kuitansi

56 Use Case Diagram

57 Use Case Diagram (Alternatif)

58 Exercise: Business Process Identification
Lihat kembali System Request yang sudah anda buat Lakukan business process identification dengan membuatkan Use Case Diagram untuk System Request tersebut

59 Exercise: Systems Analysis and Design
Object-Oriented Programming Exercise: Systems Analysis and Design Lakukan sistem analysis and design yang menghasilkan diagram: Use Case Diagram Pilih salah satu aplikasi di bawah: Aplikasi Rental Mobil Aplikasi Pengelolaan Klinik Aplikasi Pengelolaan Apotik Aplikasi Pengelolaan Service Mobil Aplikasi Penjualan Motor Aplikasi Pengelolaan Perpustakaan Aplikasi Penjualan Buku Online Aplikasi Penjualan Tiket Kereta Online Aplikasi Manajemen Universitas Online Aplikasi Penjualan Laptop Online Aplikasi Perpustakaan Digital Aplikasi Pengelolaan Project Software

60 Business Process Modeling
Object-Oriented Programming Business Process Modeling

61 System Analysis and Design with UML
Business Process Identification Use Case Diagram Business Process Modeling Activity Diagram or Business Process Modeling Notation (BPMN) Business Process Realization Sequence Diagram (Buat untuk setiap use case dengan menggunakan pola Boundary-Control-Entity) System Design Program Design Class Diagram (Gabungkan Boundary-Control-Entity Class dan susun story dari sistem yang dibangun) Package Diagram (Gabungan class yang sesuai, boleh menggunakan pola B-C-E) Deployment Diagram (arsitektur software dari sistem yang dibangun) User Interface Design (Buat UI design dari Boundary Class) Entity-Relationship Model (Buat ER diagram dari Entity Class)

62 Business Process Modeling with Activity Diagrams
Elements of an Activity Diagram Guidelines for Creating Activity Diagrams

63 BPM With Activity Diagrams
A number of activities support a business process across several departments Activity diagrams model the behavior in a business process

64 Syntax for an Activity Diagram

65 Activity Diagram Example

66 Creating Activity Diagrams
Set the context or scope of the activity being modeled Identify the activities and control/object flows between activities Identify any decisions made Look for opportunities for parallelism Draw the diagram

67 Business Process Modeling with BPMN

68

69

70

71

72 Credit Application

73 Purchase Request

74 Shipment Process of a Hardware Retailer

75 The Pizza Collaboration

76 Order Fulfillment and Procurement

77 Studi Kasus: ATM System

78 Activity Diagram: Memasukkan Kartu

79 Activity Diagram: Memasukkan PIN

80 Activity Diagram: Mengecek Saldo

81 Activity Diagram: Mentransfer Uang

82 Activity Diagram: Mengambil Uang

83 Activity Diagram: Melakukan Logout

84 Exercise: Business Process Modeling
Lihat kembali System Request dan Use Case Diagram yang sudah anda buat Lakukan business process modeling dengan membuatkan Activity Diagram untuk setiap Use Case yang dibuat

85 Exercise: Systems Analysis and Design
Object-Oriented Programming Exercise: Systems Analysis and Design Lakukan sistem analysis and design yang menghasilkan diagram: Use Case Diagram Activity Diagram Pilih salah satu aplikasi di bawah: Aplikasi Rental Mobil Aplikasi Pengelolaan Klinik Aplikasi Pengelolaan Apotik Aplikasi Pengelolaan Service Mobil Aplikasi Penjualan Motor Aplikasi Pengelolaan Perpustakaan Aplikasi Penjualan Buku Online Aplikasi Penjualan Tiket Kereta Online Aplikasi Manajemen Universitas Online Aplikasi Penjualan Laptop Online Aplikasi Perpustakaan Digital Aplikasi Pengelolaan Project Software

86 Business Process Realization
Object-Oriented Programming Business Process Realization

87 System Analysis and Design with UML
Business Process Identification Use Case Diagram Business Process Modeling Activity Diagram or Business Process Modeling Notation (BPMN) Business Process Realization Sequence Diagram (Buat untuk setiap use case dengan menggunakan pola Boundary-Control-Entity) System Design Program Design Class Diagram (Gabungkan Boundary-Control-Entity Class dan susun story dari sistem yang dibangun) Package Diagram (Gabungan class yang sesuai, boleh menggunakan pola B-C-E) Deployment Diagram (arsitektur software dari sistem yang dibangun) User Interface Design (Buat UI design dari Boundary Class) Entity-Relationship Model (Buat ER diagram dari Entity Class)

88 Sequence Diagram

89 Sequence Diagrams Illustrate the objects that participate in a use case Show the messages that pass between objects for a particular use-case over time

90 Sequence Diagram Syntax
AN ACTOR AN OBJECT A LIFELINE A FOCUS OF CONTROL A MESSAGE OBJECT DESTRUCTION anObject:aClass aMessage() x

91 Sequence Diagram Susun Sequence Diagram untuk setiap Use Case yang dibuat Mulai dari menarik Actor yang ada di Use Case Diagram, lanjutkan dengan membuat sequence detail dari berjalannya Use Case Catatan: Objek dari Lifeline di Sequence Diagram akan menjadi kandidat Class

92 Jenis Class Boundary Class: Control Class: Entity Class:
Class yang berinteraksi dengan aktor langsung (user interface) Form, input, UI ini masuk di sini Control Class: Class yang berhubungan dengan pemrosesan, penghitungan, kalkulasi, komputasi, query, dst Entity Class: Class yang berhubungan dengan data, penyimpanan data/file

93 Studi Kasus: ATM System

94 Sequence Diagram: Memasukkan Kartu

95 Sequence Diagram: Memasukkan PIN

96 Sequence Diagram: Mengecek Saldo

97 Sequence Diagram: Mentransfer Uang

98 Sequence Diagram: Mengambil Uang

99 Sequence Diagram: Melakukan Logout

100 Exercise: Sequence Diagram
Lihat kembali System Request, Use Case Diagram, dan Activity Diagram yang sudah anda buat Lengkapi diagram tersebut dengan Sequence Diagram untuk setiap Use Case yang dibuat

101 Exercise: Systems Analysis and Design
Object-Oriented Programming Exercise: Systems Analysis and Design Lakukan sistem analysis and design yang menghasilkan diagram: Use Case Diagram Activity Diagram Sequence Diagram Pilih salah satu aplikasi di bawah: Aplikasi Rental Mobil Aplikasi Pengelolaan Klinik Aplikasi Pengelolaan Apotik Aplikasi Pengelolaan Service Mobil Aplikasi Penjualan Motor Aplikasi Pengelolaan Perpustakaan Aplikasi Penjualan Buku Online Aplikasi Penjualan Tiket Kereta Online Aplikasi Manajemen Universitas Online Aplikasi Penjualan Laptop Online Aplikasi Perpustakaan Digital Aplikasi Pengelolaan Project Software

102 Collaboration Diagram

103 Collaboration Diagrams
Essentially an object diagram that shows Message passing relationships Instead associations Emphasize The flow of messages among objects Rather than timing and ordering of messages

104 Collaboration Diagram Syntax
AN ACTOR AN OBJECT AN ASSOCIATION A MESSAGE anObject:aClass aMessage()

105 Example Collaboration Diagram

106 State Machine Diagram

107 Behavioral State Machines
Some objects may change states often Some may change state and never change back Patient: new  current  former This is seen in the cells of the CRUD matrix

108 Behavioral State Machines
The behavioral state machine is a dynamic model that shows this The behavioral state machine shows The different states of an object The events That cause the object to change from one state to another

109 Components of Statechart Diagrams
States Determined by the values of the attributes Events Changes the state of an object e.g. changes the values of attributes

110 Components of Statechart Diagrams
Transitions Movement of an object from one state to another Often has a guard condition Actions Atomic process, takes "zero time" Activities Non-atomic, take a long time, can be started and stopped

111 Statechart Diagram Syntax
A STATE AN INITIAL STATE A FINAL STATE AN EVENT A TRANSITION aState anEvent

112 Example Behavioral State Machine Diagram

113 Building Behavioral State Machine Diagrams
Set the context Identify Initial state Final state All stable states Determine the order in which the object will pass through stable states Identify the events, actions, and guard conditions associated with the transitions Validate the diagram

114 Estimating Project Size with Use Case Points
Gustav Karner (1993)

115 Actor and Use Case Weighting Tables
Unadjusted Actor Weighting (UAW) Actor Type Description Weighting Factor Simple External System with well-defined API 1 Average External System using a protocol-based interface, e.g., HTTP, TCT/IP, SQL 2 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

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

117 Environmental Complexity Factors
Factor Number Description Weight 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 E5 Motivation E6 Requirements stability 2.0 E7 Part time staff -1.0 E8 Difficulty of programming language Environmental Factor (ECF) = (-0.03 * EFactor)

118 Computing Use Case Points
Adjusted Use Case Points (UCP) = UUCP * TCF * ECF Effort in Person Hours = UCP * PHM

119 Person Hour Multiplier (PHM)
If the sum of (number of Efactors ECF1 through ECF6 assigned value < 3) and (number of Efactors ECF7 and ECF8 assigned value > 3) ≤ 2 PHM = 20 Else If the sum of (number of Efactors ECF1 through ECF6 assigned value < 3) and (number of Efactors ECF7 and ECF8 assigned value > 3) = 3 or 4 PHM 28 Else Rethink project; it has too high of a risk for failure

120 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

121 Use Case Points in EA

122

123 Effort Estimation from PM Defined
Effort Estimation of Sistem ATM UCP = 30 PHM = 20 PH = 20*30 = 600 PM = 600/8/22 = 3.4 TIME (M) = 3.0 * PM 1/3 TIME (M) = 3.0 * 3.4 1/3 TIME (M) = 4.5

124 Budget (Custom Software)
Pekerjaan Man-Month Month Budget Total Planning 2 1 Analysis Design Implementation 4 Training

125 Budget (Generic Software)
Product Total LMS Teleconference Chatting eLibrary

126 Exercise: Project Size Estimation
Lihat kembali Use Case Diagram, dan Sequence Diagram yang telah anda buat Estimasi Project Size, Effort dan Time dengan menggunakan Use Case Point

127 Exercise: System Analysis untuk System Request
Lihat kembali System Request yang sudah anda buat Lakukan system analysis dengan membuat diagram di bawah: Use Case Diagram Activity Diagram Sequence Diagram Buat project baru di Sparx EA, buat 3 package dengan nama sama dengan 3 diagram di atas

128 Object-Oriented Programming Referensi Alan Dennis et al, Systems Analysis and Design with UML 4th Edition, John Wiley and Sons, 2013 Kenneth E. Kendall and Julie E Kendall, Systems Analysis and Design 8th Edition, Prentice Hall, 2010 Hassan Gomaa, Software Modeling and Design: UML, Use Cases, Patterns, and Software Architectures, Cambridge University Press, 2011 Gary B. Shelly and Harry J. Rosenblatt, Systems Analysis and Design 9th Edition, Course Technology, 2011 Howard Podeswa, UML for the IT Business Analyst 2nd Edition, Course Technology, 2009 Jeffrey A. Hoffer et al, Modern Systems Analysis and Design 6th Edition, Prentice Hall, 2012