7. Analisis Kebutuhan - 1 (System Actors & System Use Cases ) SIF15001 Analisis dan Perancangan Sistem Informasi Agi Putra Kharisma, S.T., M.T. Genap 2014/2015
Desain slide ini dadaptasi dari University of San Fransisco
Pemodelan Bisnis
Analisis Kebutuhan
Unified Process
Di sini
Bagaimana kebutuhan sistem direpresentasikan?
Dalam perkuliahan ini, kebutuhan direpresentasikan dengan menggunakan teknik berbasis use-case.
High Level System Use Case
The system use case is an individual process that is identified from the business activities. High-level (or brief) system use cases* represent the more general functional requirements of a system.
*) high-level system use cases akan didetailkan pada expanded use case di tahap berikutnya.
Pendekatan – Pendekatan Yang Dapat Digunakan Untuk Menemukan Use Case 1. Create a list of functional requirements, and then identify use cases associated with them. 2. Create a set of use cases, and then extract the functional requirements from them. 3. Consider that use cases are requirements. The brief version
of the use cases corresponds to high-level requirements and the expanded use cases correspond to the complete set
of requirements. Pendekatan yang digunakan pada perkuliahan ini.
System Use Case
System Use Case system use cases are often executed in a short period of time, usually minutes. must be performed without interruptions. normally performed by a few (sometimes just one) human actors
Business Use Case business actors may spend days or even weeks performing a business use case. May be performed with interruption. Usually performed by many human actors
Bagaimana System Use Case Yang Baik?
1. 2. 3. 4. 5. 6.
Single Session Interactive Consistent result Essential Brief System Boundary
1. Single Session
“it should begin and finish without interruption”
Mengikuti ide EBP (Elementary Business Process) (Larman, 2004), yang menyatakan: “a task performed by one person in one place at one time, in response to a business event, which adds measurable business value and leaves the data in a consistent state.”
Contoh System Use Case (1)
PERINGATAN: Hindari Fragment! Processes that can only happen in the context of other processes are just fragments, not use cases.
2. Interactive
“an actor must exist to interact with the system”
3. Consistent Result
“only a complete process is a system use case” • This excludes from the use case definition fragments
•
That also excludes operations such as Login (It may be just part of one or more use cases)
Independent use cases that may be related
In practice, at this point, any association between use cases such as extend or include should be avoided in the diagram because they usually add no useful information for the Inception phase.
4. Essential
“During requirements elicitation and analysis, system use cases are considered requirements, not design.” Two styles for writing use cases may be identified: • Essential use cases, which do not mention interface technology. • Concrete (or real) use cases, which are specifically written for a given interface technology.
5. Brief
“they are described just by their name or, in some cases, by one or two sentences”
6. System Boundary
Here (in system use case diagram), system boundary represents the limits of a computational system. *in business use case diagrams, the system boundary represents the limits of the organization (company, department, etc.).
Bagaimana menemukan system use cases?
1. Temukan aktor – aktornya (dengan melihat business use case diagram) 2. Kemudian periksa activity diagram dan state diagram pada pemodelan bisnis untuk menemukan aktivitas mana yang dapat dijadikan system use cases.
Menentukan aktor
Menemukan Use Case Dari Activity Diagram
Menemukan Use Case Dari State Diagram
Next
Requirements
Referensi
Raul Sidnei Wazlawick - Object-Oriented Analysis and Design for Information Systems
Tugas
Buatlah system use case pada “Kantin PTIIK” sesuai dengan pemodelan bisnis yang telah saudara buat di tugas sebelumnya.
