Sesi 5 Business Modelling

Session 5 Business Modelling and Requirement Determination Dana Indra Sensuse ([email protected]) Indra Budi ([email protected]) Most slides are adopted from the textbook “Systems Analysis and Design with the Unified Modeling Language, Version 2.0” Alan Dennis, Barbara Wixom, and David Tegarden © 2005 and “Managing Software Requirements: A Use Case Approach, Second Edition”, Dean Leffingwell, Don Widrig @2003

Analysis and Design Information System – MTI Fasilkom 2007

Key Ideas  Business

modeling is a problem analysis technique especially suitable for the IS/IT environment.  The business model is used to help define systems and their applications  in terms of business requirements  A business use-case model, consisting of actors and use cases, is a model of the intended functions of the business. Analysis and Design Information System – MTI Fasilkom 2007

The purpose of business modeling   

To understand the structure and dynamics of the existing organization To ensure that customers, end users, and developers have a common understanding of the organization To understand how to deploy new systems to facilitate productivity and which existing systems may be affected by that new system

Business modeling gives the team a logical approach to defining where software applications can improve the productivity of the business and helps determine requirements for those applications. Analysis and Design Information System – MTI Fasilkom 2007

What is a Requirement?  





A statement of what the system must do A statement of characteristics the system must have Focus is on business user needs during analysis phase Requirements will change over time as project moves from analysis to design to implementation

Analysis and Design Information System – MTI Fasilkom 2007

Requirement Types 

Functional Requirements  



A process the system has to perform Information the system must contain

Nonfunctional Requirements 

Behavioral properties the system must have Operational  Performance  Security  Cultural and political 

Analysis and Design Information System – MTI Fasilkom 2007

Functional Requirements

Analysis and Design Information System – MTI Fasilkom 2007

Nonfunctional Requirements

Analysis and Design Information System – MTI Fasilkom 2007

Documenting Requirements 

Requirements definition report  Text

document listing requirements in outline

form  Priorities may be included

Key purpose is to define the project scope: what is and is not to be included.  Using vision document template 

Analysis and Design Information System – MTI Fasilkom 2007

Purposes of a requirements spec documents 

A requirements spec document is used by many different stakeholder for different purposes:     

Customer - part of a formal contract Manager - basis for the project plan Developer - basis for the design and implementation Tester - document to test the system against Maintainer - starting point for understanding the system

Analysis and Design Information System – MTI Fasilkom 2007

Determining Requirements 

Participation by business users/experts and IT analyst is essential  If

done only by IT analyst, may not address true business needs  If done only by business experts, may not take advantage of technology 

Three techniques help users discover their needs for the new system:   

Business Process Automation (BPA) Business Process Improvement (BPI) Business Process Reengineering (BPR)

Analysis and Design Information System – MTI Fasilkom 2007

Basic Process of Analysis (Determining Requirements)    

Understand the “As-Is” system Identify improvement opportunities Develop the “To-Be” system concept Techniques vary in amount of change   



BPA – small change BPI – moderate change BPR – significant change

Additional information gathering techniques are needed as well

Analysis and Design Information System – MTI Fasilkom 2007

Requirement Analysis Techniques

Analysis and Design Information System – MTI Fasilkom 2007

Business Process Automation •Doesn’t change basic operations •Automates some operations Goal: Efficiency for users

Analysis and Design Information System – MTI Fasilkom 2007



Identifying Improvements in As-Is Systems

Problem Analysis 

 



Identify problems with as-is system and to describe how to solve them in the to-be system  Ask users to identify problems and solutions Improvements tend to be small and incremental Rarely finds improvements with significant business value

Root Cause Analysis   

Challenge assumptions about why problem exists Trace symptoms to their causes to discover the “real” problem Identify the root causes of problems rather than symptoms of problems

Analysis and Design Information System – MTI Fasilkom 2007

Root Cause Analysis Example

Analysis and Design Information System – MTI Fasilkom 2007

Business Process Improvement Goal: Efficiency and effectiveness for users

Analysis and Design Information System – MTI Fasilkom 2007

Business process improvement (BPI) changes  

  

How an organization operates Changes operation with new techniques (i.e., take advantage of new opportunities offered by technology) Can improve efficiency (i.e., doing things right) Can improve effectiveness (i.e., doing the right things) More focus on to-be system for improvement (i.e., less on as-is system than BPA)

Analysis and Design Information System – MTI Fasilkom 2007

Duration Analysis    

Calculate time needed for each process step Calculate time needed for overall process Compare the two – a large difference indicates a badly fragmented process Potential solutions:  

Process integration – change the process to use fewer people, each with broader responsibilities Parallelization – change the process so that individual step are performed simultaneously

Analysis and Design Information System – MTI Fasilkom 2007

Activity-Based Costing Calculate cost of each process step  Consider both direct and indirect costs  Identify most costly steps and focus improvement efforts on them 

Analysis and Design Information System – MTI Fasilkom 2007

Benchmarking Studying how other organizations perform the same business process  Informal benchmarking 

Common for customerfacing processes Interact with other business’ processes as if you are a customer Analysis and Design Information System – MTI Fasilkom 2007

Business Process Reengineering (BRP) Changes fundamentally how the organization does certain operations Goal: Radical redesign of business processes

Analysis and Design Information System – MTI Fasilkom 2007

Outcome Analysis Consider desirable outcomes from customers’ perspective  Consider what the organization could enable the customer to do 

Analysis and Design Information System – MTI Fasilkom 2007

Technology Analysis Analysts list important and interesting technologies  Managers list important and interesting technologies  The group identifies how each might be applied to the business and how the business might benefit 

Analysis and Design Information System – MTI Fasilkom 2007

Activity Elimination Identify what would happen if each organizational activity were eliminated  Use “force-fit” to test all possibilities 

Analysis and Design Information System – MTI Fasilkom 2007

Your Turn 

For the plants web system, what type of requirements are those:  Be

accessible to web users  Include the company logo  Provide management reports  Includes pictures of the plants  Print the page  Restricts access to profitability information

Analysis and Design Information System – MTI Fasilkom 2007

Interviews -- Five Basic Steps Selecting interviewees  Designing interview questions  Preparing for the interview  Conducting the interview  Post-interview follow-up 

Analysis and Design Information System – MTI Fasilkom 2007

Selecting Interviewees Based on information needed  Often good to get different perspectives 

 Managers  Users  Ideally,

all key stakeholders

Analysis and Design Information System – MTI Fasilkom 2007

Types of Questions Types of Questions

Examples

Closed-Ended Questions

* * *

Open-Ended Questions

* * *

Probing Questions

* * *

Analysis and Design Information System – MTI Fasilkom 2007

How many telephone orders are received per day? How do customers place orders? What additional information would you like the new system to provide?

What do you think about the current system? What are some of the problems you face on a daily basis? How do you decide what types of marketing campaign to run? Why? Can you give me an example? Can you explain that in a bit more detail?

Designing Interview Questions 

Unstructured interview  



Broad, roughly defined information At the earlier stage of the project

Structured interview  

More specific information At the later stage of the project

Analysis and Design Information System – MTI Fasilkom 2007

Designing Interview Questions : Questioning Strategies

Analysis and Design Information System – MTI Fasilkom 2007

Interview Preparation Steps 

  

Prepare general interview plan  List of question  Anticipated answers and follow-ups Confirm areas of knowledge Set priorities in case of time shortage Prepare the interviewee  Schedule  Inform of reason for interview  Inform of areas of discussion

Analysis and Design Information System – MTI Fasilkom 2007

Conducting the Interview        

Appear professional and unbiased Record all information Check on organizational policy regarding tape recording Be sure you understand all issues and terms Separate facts from opinions Give interviewee time to ask questions Be sure to thank the interviewee End on time

Analysis and Design Information System – MTI Fasilkom 2007

Conducting the Interview Practical Tips      

Don’t worry, be happy Pay attention Summarize key points Be succinct Be honest Watch body language

Analysis and Design Information System – MTI Fasilkom 2007

Post-Interview Follow-Up Prepare interview notes  Prepare interview report  Look for gaps and new questions 

Analysis and Design Information System – MTI Fasilkom 2007

Interview Report INTERVIEW REPORT Interview notes approved by: ____________ Person interviewed Interviewer Date Primary Purpose:

______________ _______________ _______________

Summary of Interview: Open Items: Detailed Notes:

Analysis and Design Information System – MTI Fasilkom 2007

Your Turn 

You are interviewing the director of the PC lab at your school regarding a new program to support keeping track of students’ borrowing software  With a partner, write 5 questions you would ask the PC lab director  Take turns having one pair of students posing the questions to another pair of students  Be sure to take notes and write up the results when you have finished.

Analysis and Design Information System – MTI Fasilkom 2007

JOINT APPLICATION DESIGN (JAD)

Analysis and Design Information System – MTI Fasilkom 2007

JAD Key Ideas Allows project managers, users, and developers to work together  May reduce scope creep by 50%  Avoids requirements being too specific or too vague 

Analysis and Design Information System – MTI Fasilkom 2007

Joint Application Design (JAD) Important Roles Facilitator  Scribe 

Analysis and Design Information System – MTI Fasilkom 2007

Joint Application Design (JAD) Setting U-Shaped seating  Away from distractions  Whiteboard/flip chart  Prototyping tools  e-JAD 

Analysis and Design Information System – MTI Fasilkom 2007

JAD Meeting Room

JPEG Figure 5-5 Goes Here

Analysis and Design Information System – MTI Fasilkom 2007

The JAD Session    



Tend to last 5 to 10 days over a three week period Prepare questions as with interviews Formal agenda and groundrules Facilitator activities  Keep session on track  Help with technical terms and jargon  Record group input  Help resolve issues Post-session follow-up

Analysis and Design Information System – MTI Fasilkom 2007

Managing Problems in JAD Sessions        

Reducing domination Encouraging non-contributors Side discussions Agenda merry-go-round Violent agreement Unresolved conflict True conflict Use humor

Analysis and Design Information System – MTI Fasilkom 2007

QUESTIONNAIRES

Analysis and Design Information System – MTI Fasilkom 2007

Questionnaire Steps 







Selecting participants  Using samples of the population Designing the questionnaire  Careful question selection Administering the questionnaire  Working to get good response rate Questionnaire follow-up  Send results to participants

Analysis and Design Information System – MTI Fasilkom 2007

Good Questionnaire Design Begin with non-threatening and interesting questions Group items into logically coherent sections Do not put important items at the very end of the questionnaire Do not crowd a page with too many items Avoid abbreviations Avoid biased or suggestive items or terms Number questions to avoid confusion Pretest the questionnaire to identify confusing questions Provide anonymity to respondents Analysis and Design Information System – MTI Fasilkom 2007

Document Analysis  

 

Provides clues about existing “as-is” system Typical documents  Forms  Reports  Policy manuals Look for user additions to forms Look for unused form elements

Analysis and Design Information System – MTI Fasilkom 2007

Observation    

Users/managers often don’t remember everything they do Checks validity of information gathered other ways Behaviors change when people are watched Careful not to ignore periodic activities  Weekly … Monthly … Annual

Analysis and Design Information System – MTI Fasilkom 2007

Selecting the Appropriate Techniques Interviews

JAD

Questionnaires

Document Analysis

Observation

Type of Information

As-Is Improve. To-Be

As-Is As-Is Improve. Improve. To-Be

As-Is

As-Is

Depth of Information

High

High

Medium

Low

Low

Breadth of Information

Low

Medium

High

High

Low

Integration of Info.

Low

High

Low

Low

Low

User Medium Involvement

High

Low

Low

Low

Cost

LowMedium

Medium

Low

Analysis and Design Information System – MTI Fasilkom 2007

Low

LowMedium

Business Modelling using UML Concept 





Two key modeling constructs that can be used for this purpose are a business use-case model and a business object model. A business use-case model is a model of the intended functions of the business and is used as an essential input to identify roles and deliverables in the organization The business object model describes the entities and how they interact to deliver the functionality necessary to realize the business use cases

Analysis and Design Information System – MTI Fasilkom 2007

Business Use-case Model 

The business actors   



Users and systems that interact with the business Representing roles external to the business Ex: Customer, Employee, Software developer

The business use cases 

 

Sequences of events through which the actors interact with the business elements to get their jobs done Representing processes Examples: "Deliver electronic pay stub to employee."  "Meet with customer to negotiate contract terms." 

Analysis and Design Information System – MTI Fasilkom 2007

Business Use Case Model Enterprise

Business Actor

Business Use Case

Business UC: pelayanan apa saja yang disediakan oleh organisasi bisnis bagi customers-nya. Analysis and Design Information System – MTI Fasilkom 2007

Contoh: Business UC untuk Sistem Informasi Rumah Sakit Rumah Sakit

Berobat jalan

Melakukan check-up

Pasien

Menjalani rawat inap

DepKes

Memonitor Kinerja RS Memonitor Ketersediaan dan Status Obat

PB Farmasi Analysis and Design Information System – MTI Fasilkom 2007

Business Object Model (BOM) Enterprise

Business Actor

Business Worker

Business Entity

BOM: interaksi antar komponen organisasi dalam rangka melayani cutomers. Analysis and Design Information System – MTI Fasilkom 2007

Contoh: BOM “Berobat Jalan” Rumah Sakit

Kasir

Bukti Berobat

Pasien

Petugas Reservasi

Rekam Medis

Analysis and Design Information System – MTI Fasilkom 2007

Petugas Unit Layanan

Business Process Modeling With Activity Diagrams  

A number of activities support a business process across several departments Activity diagrams model the behavior in a business process  Sophisticated data flow diagrams  Addresses Parallel concurrent activities and complex processes

Analysis and Design Information System – MTI Fasilkom 2007

Basic Elements of Activity Diagrams - Review Initial Node Action 1 Action (node)

Fork

Decision

Action 2

Action 3 Flow/edge

Action 4

Action 5 Action 6

Merge Join Action 7 Final Note Analysis and Design Information System – MTI Fasilkom 2007

Example: Activity Diagrams for Business process modeling – online sales process Initial Node Receive Order Action (node)

Fork

Decision [priority order]

Fill Order

Send Invoice Flow/edge

[else] Overnight Delivery

Regular Delivery Receive Payment

Merge Join

Close Order Final Note Analysis and Design Information System – MTI Fasilkom 2007

Example: Activity Diagram with Partition – Online Order process Actor: System

Actor: Customer select Items [else]

[if regular]

fill shipping info

Display related info present price & shipping info

fill credit card info [if correct] Accept

[else] Override authorise purchase Confirm sale

Analysis and Design Information System – MTI Fasilkom 2007 Swim

lane

Activity Diagram Example - Activity Diagram for Appointment System An Object Node: ■ Is used to represent the flow of information from one activity to another ■ Is labelled by its class name An Object Flow: ■ Shows the flow of an object from one activity (or action) to another Analysis and Design Information System – MTI Fasilkom 2007

Guidelines for Creating Activity Diagrams 1.

2.

3.

4.

5.

Since an activity diagram can be used to model any kind of process, you should set the context or scope of the activity being modeled. Once you have determined the scope, you should give the diagram an appropriate title. You must identify the activities, control flows, and object flows that occur between the activities. You should identify any decisions that are part of the process being modeled. You should attempt to identify any prospects for parallelism in the process. You should draw the activity diagram.

Analysis and Design Information System – MTI Fasilkom 2007

Vision Document Template 

Dokumen yang berisikan business modelling dari suatu aplikasi (software)

Analysis and Design Information System – MTI Fasilkom 2007

Sales Order Problem Statement

Analysis and Design Information System – MTI Fasilkom 2007