Search In This Website
Menampilkan postingan yang diurutkan menurut relevansi untuk kueri use case. Urutkan menurut tanggal Tampilkan semua postingan
Menampilkan postingan yang diurutkan menurut relevansi untuk kueri use case. Urutkan menurut tanggal Tampilkan semua postingan

Jumat, 11 April 2025

Tabel Identifikasi Use Case Dalam AsciiDoctor

1. Buka AsciiDoctor editor.
2. Ketik file AsciiDoctor di bawah ini ke dalam AsciiDoctor editor:
= Tabel Identifikasi Use Case
:author: -
:co-author: Tutor Course and After School Course
:revnumber: 1.0
:revdate: -
:doctype: article
:toc:
:icons:
:lang: id
.Identifikasi Use Case
[%header]
|===

|ID|Nama +
Use Case|Deskripsi|Aktor

|UC01
|Login
|Use Case ini menggambarkan +
kegiatan memasukkan data id user +
dan password untuk dapat +
masuk ke dalam sistem.
a|. Admin Inventory
. Admin Pembelian
. Manajer

|UC02
|Update Profil
|Use case ini menggambarkan +
kegiatan memperbaharui atau +
mengubah biodata user seperti +
nama lengkap, nomor telepon, +
e-mail, dan foto profil.
a|. Admin Inventory
. Admin Pembelian
. Manajer

|UC03
|Ubah Password
|Use case ini menggambarkan +
kegiatan mengubah password +
lama menjadi password baru
a|. Admin Inventory
. Admin Pembelian
. Manajer

|UC04
|Manajemen Barang
|Use case ini menggambarkan +
kegiatan melihat data barang, +
menambahkan data barang, +
mengubah data barang dan +
menghapus data.
a|Admin Inventory
|===
3. Simpan dengan nama file TabelIdentifikasiUseCase.asciidoc
4. Jalankan preview atau save as HTML atau PDF.
5. Buka HTML di browser atau PDF di PDF reader.

Notes

Jika Asciidoctor Editor berjalan dengan baik maka akan menghasilkan file output HTML seperti di bawah ini:
<!DOCTYPE html>
<html>
<head><title>Tabel Identifikasi Use Case</title></head>
<body>
<h1>Tabel Identifikasi Use Case</h1>
<table border="1">
<caption>Table 1. Identifikasi Use Case</caption>
<colgroup>
<col style="width: 25%;">
<col style="width: 25%;">
<col style="width: 25%;">
<col style="width: 25%;">
</colgroup>
<thead>
<tr>
<th>ID</th>
<th>Nama<br>
Use Case</th>
<th>Deskripsi</th>
<th>Aktor</th>
</tr>
</thead>
<tbody>
<tr>
<td>UC01</td>
<td>Login</td>
<td>Use Case ini menggambarkan<br>
kegiatan memasukkan data id user<br>
dan password untuk dapat<br>
masuk ke dalam sistem.</td>
<td>
<ol>
<li>
Admin Inventory
</li>
<li>
Admin Pembelian
</li>
<li>
Manajer
</li>
</ol>
</td>
</tr>
<tr>
<td>UC02</td>
<td>Update Profil</td>
<td>Use case ini menggambarkan<br>
kegiatan memperbaharui atau<br>
mengubah biodata user seperti<br>
nama lengkap, nomor telepon,<br>
e-mail, dan foto profil.</td>
<td>
<ol>
<li>
Admin Inventory
</li>
<li>
Admin Pembelian
</li>
<li>
Manajer
</li>
</ol>
</td>
</tr>
<tr>
<td>UC03</td>
<td>Ubah Password</td>
<td>Use case ini menggambarkan<br>
kegiatan mengubah password<br>
lama menjadi password baru</td>
<td>
<ol>
<li>
Admin Inventory
</li>
<li>
Admin Pembelian
</li>
<li>
Manajer
</li>
</ol>
</td>
</tr>
<tr>
<td>UC04</td>
<td>Manajemen Barang</td>
<td>Use case ini menggambarkan<br>
kegiatan melihat data barang,<br>
menambahkan data barang,<br>
mengubah data barang dan<br>
menghapus data.</td>
<td>
Admin Inventory
</td>
</tr>
</tbody>
</table>
</body>
</html>

Output

Tabel Identifikasi Use Case

Table 1. Identifikasi Use Case
ID Nama
Use Case		 Deskripsi Aktor
UC01 Login Use Case ini menggambarkan
kegiatan memasukkan data id user
dan password untuk dapat
masuk ke dalam sistem.
  1. Admin Inventory
  2. Admin Pembelian
  3. Manajer
UC02 Update Profil Use case ini menggambarkan
kegiatan memperbaharui atau
mengubah biodata user seperti
nama lengkap, nomor telepon,
e-mail, dan foto profil.
  1. Admin Inventory
  2. Admin Pembelian
  3. Manajer
UC03 Ubah Password Use case ini menggambarkan
kegiatan mengubah password
lama menjadi password baru
  1. Admin Inventory
  2. Admin Pembelian
  3. Manajer
UC04 Manajemen Barang Use case ini menggambarkan
kegiatan melihat data barang,
menambahkan data barang,
mengubah data barang dan
menghapus data.		 Admin Inventory

document header, document metadata, document attributes, document structure, low-code application development, software requirement specification document, srs document


Bibliography

Software Engineering;R.S. Pressman et. al.
Analisis Dan Desain Sistem Informasi;Jogiyanto
https://books.google.com/
https://www.researchgate.net/
https://www.scribd.com/
di Tidak ada komentar:
Label:

Rabu, 18 Desember 2024

Study About UML Diagram

  • UML Diagram List
    UML Class Diagram, UML Component (Structure) Diagram, UML Deployment Diagram
  • Most Common UML Notation
    Study about Notes and Stereotypes
  • UML Vocabulary List
  • Apa Itu UML Diagram
    Mempelajari tipe-tipe diagram UML, Class Diagram, Package Diagram, Object Diagram, Component Diagram, Composite Structure Diagram, Deployment Diagram, Activity Diagram, Sequence Diagram, Use Case Diagram, State Diagram / Statechart Diagram / State Machine Diagram, Communication Diagram / Collaboration Diagram, Interaction Overview Diagram, Timing Diagram, dan manfaat UML Diagram.

Use Case Diagram:

Class Diagram and Object Diagram:

Other Structure Diagrams:

Business Process



unified modeling language, uml chart, software engineer, software developer,

Related Post

di Tidak ada komentar:
Label:

Senin, 09 Juni 2025

Apa Itu UML Diagram

Apa itu Diagram UML?

UML  (Unified Modelling Language) adalah cara memvisualisasikan software program menggunakan kumpulan diagram. Notasi ini telah berkembang untuk digunakan pada desain object oriented, tetapi sejak itu telah diperluas untuk mencakup berbagai macam proyek software engineering. Saat ini, UML diterima oleh Object Management Group (OMG) sebagai standar untuk pemodelan pengembangan software.

Tipe-Tipe Diagram UML

Standar UML saat ini menyerukan 13 jenis diagram yang berbeda:

class diagram, activity diagram, object diagram, use case diagram, sequence diagram, package diagram, state diagram, component diagram, communication diagram, composite structure diagram, interaction overview diagram, timing diagram, and deployment diagram.

Diagram ini diorganisasikan menjadi dua kelompok berbeda: Structural Diagram dan Behavioral Diagram.

  • Structural UML diagrams
    • Class diagram
    • Package diagram
    • Object diagram
    • Component diagram
    • Composite structure diagram
    • Deployment diagram
  • Behavioral UML diagrams
    • Activity diagram
    • Sequence diagram
    • Use case diagram
    • State diagram
    • Communication diagram
    • Interaction overview diagram
    • Timing diagram.

Class Diagram

  • Class Diagram adalah tulang punggung hampir setiap metode object oriented, termasuk UML.
  • Class Diagram menggambarkan static structure suatu sistem.
  • Class diagram atau diagram kelas merupakan suatu diagram yang digunakan untuk menampilkan kelas-kelas berupa paket-paket (packets) untuk memenuhi salah satu kebutuhan paket yang akan digunakan nantinya.
  • Namun, pada Class diagram desain modelnya dibagi menjadi 2 bagian.
    • Class diagram yang pertama merupakan penjabaran dari domain model yang merupakan abstraksi dari basis data.
    • Class diagram yang kedua merupakan bagian dari modul program, contohnya metode pemrograman MVC pattern (Model View Controller), dimana terdapat boundary presentation class sebagai class interface, class control sebagai tempat ditemukannya algoritma, dan class entity sebagai tabel dalam basis data dan query program.

Package Diagram

  • Package Diagram bagian dari class diagram, tetapi pengembang terkadang memperlakukannya sebagai teknik terpisah.
  • Package Diagram hadir sebagai solusi untuk memudahkan organisasi dan pemetaan elemen-elemen dalam sistem tersebut.
  • Package Diagram mengatur elemen-elemen suatu sistem ke dalam kelompok-kelompok terkait  dalam unit yang lebih kecil untuk meminimalkan ketergantungan antar package.

Object Diagram

  • Object Diagram digunakan untuk menggambarkan sebagian atau seluruh static structure diagram ( UML  structural diagram ) dari suatu sistem pada waktu tertentu. Object Diagram dapat digunakan untuk menguji kelengkapan dan keakuratan class diagram.
  • Object Diagram menggambarkan hubungan dan struktur objek pada waktu tertentu, contoh selama eksekusi.
  • Object Diagram ini dapat memudahkan tim memahami perilaku dan interaksi objek yang terlibat, baik selama pengembangan maupun analisis masalah.
  • Object Diagram biasanya digunakan untuk mengidentifikasi informasi mengenai elemen model tertentu untuk menunjukkan contoh spesifik dari pengklasifikasikan yang diperlukan.

Component diagram

  • Component Diagram menjelaskan organisasi software component fisik, termasuk source code, run-time (biner)  code, interface yang tersedia, port dengan hubungan di antaranya dan file yang dapat dieksekusi.
  • Component Diagram ini biasa digunakan dalam pengembangan perangkat lunak untuk menggambarkan struktur ( UML structural diagram ) dan hubungan antar komponen dalam sistem agar lebih mudah dianalisis.
  • Component Diagram membantu dalam visualisasi, spesifikasi, dan dokumentasi sistem berbasis komponen juga membangun sistem yang dapat dieksekusi melalui forward engineering dan reverse engineering.

Composite Structure Diagram

  • Composite Structure Diagrammerupakan bagian dari structural Unified Modeling Language (UML) diagram untuk menunjukkan bagian dalam kelas atau komponen.
  • Composite Structure Diagram ini berguna untuk memvisualisasikan interaksi antara objek dan elemen internal dari suatu kelas, terutama ketika elemen tersebut memiliki peran yang berbeda dalam komunikasi.
  • Composite Structure Diagram dapat mendokumentasikan dan memvisualisasikan hubungan internal yang tidak terlihat pada diagram kelas, dengan menggunakan elemen, seperti objek, port, dan konektor untuk menunjukkan komunikasi antar objek.

Deployment Diagram

  • Deployment Diagram menggambarkan sumber daya fisik dalam suatu sistem, termasuk node, component, dan koneksi.
  • Deployment diagram menjadi salah satu jenis UML diagram yang memainkan peran penting dalam mendeskripsikan bagaimana komponen software saling berinteraksi dengan komponen lainnya.
  • Deployment diagram adalah diagram yang berfungsi untuk menggambarkan penempatan (deployment) komponen software dalam perangkat keras.

Activity Diagram

  • Activity Diagram menggambarkan sifat dinamis suatu sistem dengan memodelkan aliran control dari satu activity ke activity lainnya.
  • Suatu activity mewakili suatu operasi atau proses pada beberapa class dalam sistem yang mengakibatkan perubahan pada state sistem. Biasanya, aktivitas dari activity diagram digunakan untuk memodelkan workflow atau proses bisnis dan operasi internal.
  • Seperti layaknya runtutan proses berjalannya suatu sistem dan digambarkan secara vertikal.
  • Activity diagram adalah salah satu contoh diagram dari behavioral UML dalam pengembangan dari Use Case.

Sequence Diagram

  • Sequence Diagram menggambarkan interaction antar class atau objek dalam hal pertukaran message dari time ke time atau berdasarkan urutan waktu.
  • Sequence dapat menggambarkan urutan atau tahapan yang harus dilakukan untuk dapat menghasilkan sesuatu, seperti yang tertera pada Use Case diagram.

Use Case Diagram

  • Use Case Diagram adalah satu jenis dari diagram UML (Unified Modelling Language).
  • Use Case Diagram memodelkan fungsionalitas suatu sistem menggunakan actor dan use case.
  • Use Case Diagram menggambarkan hubungan interaksi antara sistem dan aktor/pengguna.

State Diagram / Statechart Diagram / State Machine Diagram

  • Statechart Diagram, yang sekarang dikenal sebagai State Machine Diagram dan State Diagram, menggambarkan behavior dinamis suatu sistem dalam menanggapi rangsangan external. State Diagram terutama berguna dalam pemodelan objek reaktif yang statenya dipicu oleh event tertentu.
  • Statemachine yaitu salah satu jenis diagram pada UML yang berfungsi untuk menggambarkan transisi serta perubahan pada suatu objek pada sistem.

Communication Diagram / Collaboration Diagram

  • Communication Diagram memodelkan interaction antara object secara sequence.
  • Communication Diagram menggambarkan static structure dan behavior dinamis suatu sistem. Dalam banyak hal, Communication Diagram adalah versi sederhana dari collaboration diagram yang diperkenalkan dalam UML 2.0.
  • Communication Diagram memodelkan kolaborasi antara object-object atau peranan yang mengirimkan fungsionalitas dari use cases dan operasi-operasinya.
  • Mekanisme Model Communication Diagram dalam architectural design dari suatu system.

Interaction Overview Diagram

  • Interaction Overview Diagram merupakan kombinasi activity diagram dan sequence diagram. 
  • Interaction Overview Diagram memodelkan serangkaian actiondan memungkinkan Anda mendekonstruksi interaction yang lebih kompleks menjadi kejadian yang dapat dikelola. Anda harus menggunakan notasi yang sama pada Interaction Overview Diagram seperti yang Anda lihat pada activity diagram.
  • Interaction Overview Diagram dapat memungkinkan analisis interaksi antar objek atau elemen , mengidentifikasi masalah potensial, dan memiliki fungsi sebagai alat komunikasi untuk pemangku kepentingan (stakeholder) non-teknis.

Timing Diagram

  • Timing Diagram adalah jenis diagram UML behavior atau interaction yang berfokus pada proses yang terjadi selama periode time tertentu.
  • Timing Diagram adalah contoh khusus dari sequence diagram, kecuali time ditunjukkan meningkat dari kiri ke kanan, bukan dari atas ke bawah.

Manfaat UML Diagram

Berikut adalah beberapa manfaat membuat UML diagram:
  1. Membantu Pengambilan Keputusan: Dengan membuat UML diagram, tim pengembang dan perancang software dapat menentukan jenis infrastruktur fisik mengenai apa yang dibutuhkan, seperti apakah sistem harus di-hosting di cloud, server fisik, atau di keduanya.
  2. Memudahkan Pengembangan Dan Pemeliharaan: UML diagram juga dapat memudahkan dalam memahami bagaimana komponen dalam software saling berinteraksi, sehingga pengembang dapat lebih mudah memecahkan masalah saat sistem berkembang.
  3. Meminimalisir Resiko Kesalahan: Dengan penggambaran visual yang tepat, tim pengembang dapat menghindari kesalahan dalam penempatan komponen produk atau kesalahan konfigurasi yang dapat menyebabkan downtime.
  4. Memudahkan Pemahaman Fungsi Komponen Atau Elemen: Tiap-tiap komponen dalam diagram memiliki tugas tertentu dalam sistem, pada aspek ini UML diagram dapat membantu memperjelas tanggung jawab masing-masing komponen sehingga lebih mudah memahami peran mereka dalam sistem secara menyeluruh.
  5. Dapat memberikan bahasa pemodelan visual atau gambar kepada para pengguna dari berbagai macam pemrograman maupun proses umum rekayasa.
  6. Menyatukan informasi-informasi terbaik yang ada dalam pemodelan.
  7. Memberikan suatu gambaran model atau sebagai bahasa pemodelan visual yang ekspresif dalam pengembangan sistem.
  8. Tidak hanya menggambarkan model sistem software saja, namun dapat memodelkan sistem lain, seperti sistem berorientasi objek.
  9. Mempermudah pengguna untuk membaca suatu sistem.
  10. Berguna sebagai blueprint, jelas ini nantinya menjelaskan informasi yang lebih detail dalam perancangan berupa coding suatu program.
  11. Panduan Implementasi: UML diagram dapat membantu pengembang saat membangun dan menguji suatu sistem, serta memberikan pedoman dalam representasi sistem pada kode. 
  12. Dukungan Pengujian Integrasi: Memiliki fasilitas pengujian integrasi dengan memvisualisasikan hubungan antar-objek dalam sistem dan memastikan sebuah komponen dapat bekerja secara efektif.
  13. Validasi Kode: Pengembangan dapat menggunakan diagram ini untuk memastikan sebuah konsistensi antara kode dan sebuah desain. 
  14. Ilustrasi Skenario: Diagram objek dapat menggambarkan sebuah skenario atau kasus penggunaan, serta memvisualkan perilaku sistem dalam berbagai keadaan.
  15. Mengelola Kompleksitas: Dengan membagi sistem besar menjadi unit yang lebih kecil, analisis dan desain bisa lebih disederhanakan.
  16. Komunikasi yang Lebih Efektif: UML Diagram ini mempermudah tim untuk memahami komponen mana saja yang terkait dan bagaimana relasi antar paket berlangsung.



technical interview, coding qna, most technology question and answer, concept, managerial theory

Bibliography

https://www.conceptdraw.com/
https://www.dicoding.com/
https://www.lawencon.com/
https://www.smartdraw.com/
https://www.sjsu.edu/ ( university )
https://www.visual-paradigm.com/
di Tidak ada komentar:
Label:

Kamis, 13 April 2023

Use Case Diagram Notation 1

The most used of Use Case Diagram Notation on the following list:

  • System Boundary ( rectangle )
  • System Boundary Subject ( in this example: Clinic Appointment Receptionist System )
  • Actor ( stick figure actor )
  • Actor Role
  • Use Case
  • Association

Example:
Use Case Context Diagram Notation

NOTES: From above example, only to introduce about Notation of Use Case Context Diagram.
di Tidak ada komentar:
Label:

Sabtu, 07 Juni 2025

Dimensions And Outcome Of Rational Unified Process

Rational Unified Process

Four Horizontal Axis Dimensions or Four Consecutive Phases Of Rational Unified Process:

  • Inception Phase.
  • Elaboration Phase.
  • Construction Phase.
  • Transition Phase.
  • Production Phase.

Vertical Axis Dimension or  Of Rational Unified Process:

  • Core Process Workflows:
    • Business Modeling Workflow.
    • Requirements Workflow.
    • Analysis & Design Workflow
    • Implementation Workflow.
    • Test Workflow.
    • Deployment Workflow.
  • Core Supporting Workflows:
    • Project Management Workflow.
    • Configuration And Change Management Workflow.
    • Environment Workflow.
The outcome Of Rational Unfied Process
  • The outcome of the Inception Phase is establish the business case for the system and delimit the project scope. At minimum, it consists of:
    • A vision document is a general vision of the core project’s requirements, key features, and main constraints.
    • An initial use-case model (10%-20% complete).
    • An initial project glossary (may optionally be partially expressed as a domain model).
    • An initial business case, which includes business context, success criteria (revenue projection, market recognition, and so on), and financial forecast.
    • An initial risk assessment.
    • A project plan, showing phases and iterations.
    • A business model, if necessary.
    • One or several prototypes.
  • The outcome of the Elaboration Phase is to analyze the problem domain for an organization. At minimum, it consists of:
    • A use-case model (at least 80% complete) — all use cases and actors have been identified, and most use-case descriptions have been developed.
    • Supplementary requirements capturing the non functional requirements and any requirements that are not associated with a specific use case.
    • A Software Architecture Description.
    • An executable architectural prototype.
    • A revised risk list and a revised business case.
    • A development plan for the overall project, including the coarse-grained project plan, showing iterations” and evaluation criteria for each iteration.
    • An updated development case specifying the process to be used.
    • A preliminary user manual (optional).
  • The outcome of the Construction Phase is a product ready to put in hands of its end-users. At minimum, it consists of:
    • The software product integrated on the adequate platforms.
    • The user manuals.
    • A description of the current release.
  • The outcome of Transition Phase is entered when a baseline is mature enough to be deployed in the end-user domain. At minimum, it consists of:
    • “beta testing” to validate the new system against user expectations.
    • parallel operation with a legacy system that it is replacing.
    • conversion of operational databases.
    • training of users and maintainers.
    • roll-out the product to the marketing, distribution, and sales teams.

Enterprise Unified Process

Four Horizontal Axis Dimensions or Four Consecutive Phases Of Enterprise Unified Process:

  • Inception Phase.
  • Elaboration Phase.
  • Construction Phase.
  • Transition Phase.
  • Production Phase.
  • Retirement Phase.

Vertical Axis Dimension or  Core Process Engineering Workflows Of Enterprise Unified Process:

  • Project Disciplines:
    • Business Modeling Disciplines.
    • Requirements Disciplines.
    • Analysis And Design Disciplines.
    • implementation Disciplines.
    • Test Disciplines.
    • Deployment Disciplines.
    • Configuration andalso Change Management Disciplines.
    • Project Management Disciplines.
    • Environment Disciplines.
    • Operations And Support Disciplines.
  • Enterprise Disciplines:
    • Solution Delivery Disciplines.
    • Operations & Support Disciplines.
    • Enterprise Business Modeling Disciplines.
    • Portfolio Management Disciplines.
    • Enterprise Architecture Disciplines.
    • Strategic Reuse Disciplines.
    • People Management Disciplines.
    • Enterprise Administration Disciplines.
    • Deployment Disciplines.
    • Software Process Improvement.

<< back to Study About UML Diagram

Bibliography

https://wikipedia.org/
https://www.ku.edu/ ( university )
https://www.uccs.edu/ ( university )
The Unified Process Series;Addison Wesley Longman
UML Series;Addison Wesley Longman
di Tidak ada komentar:
Label:

Jumat, 06 Oktober 2023

Use Case Diagram ( uml )

System: Draw your system's boundaries using a Rectangle that contains use cases. Place actors outside the System's Boundaries.


Use Case: Draw use cases using Ovals. Label with ovals with verbs that represent the system's Functions.


Actors: Actors are the Users of a system. When one system is the actor of Another System, label the actor system with the actor Stereotype.


Next  Use Case Diagram ( UML ) 2 >


Unified Modelling Language ( UML ), chart, diagram, hierarchy, program design, software design, application design, program analyst

Related Post:

di Tidak ada komentar:
Label:

Senin, 15 April 2024

Use Case Diagram 2 ( UML )

Use Case Diagram: shows the interaction between the system and the system users.

Diagram Name: Use Case Diagram

Element Names: Actor, Relationship Link / Relationship Line

Element Names for most common relationship is:  ...

question: Fill in the blank !

the answer is in the comment of this post.

Bibliography:

Java For Dummies by Barry Burd.

Spring Boot 2 by Jens Boje.

Head First Java by Kathy Sierra, et al.

Java for Aliens by Claudio De Sio Cesari, et al.

UML 2 For Dummies by Michael Jesse.

Uml: A Beginner's Guide by Jason Roff, et al.

Database management systems by K. Laxmi Narayanamma.

https://www.ibm.com/

unified modelling language ( uml ), program design, software design, application design

Related Post:

di 1 komentar:
Label:

Selasa, 03 Juni 2025

A Kind Of Process Model In Technology

The Concurrent Model Activity

  • Inactive
  • Under Development
  • Awaiting Changes
  • Under Revision
  • Under Review
  • Baselined
  • Done

The Prototyping Paradigm

  • Communication
  • Quick Plan
  • Modeling Quick Design
  • Construction Of Prototype
  • Deployment, Delivery and Feedback

Spiral Model

  • Communication
    • Project initiation
    • Requirements gathering.
  • Planning
    • Estimating
    • Scheduling
    • Risk Analysis
  • Modelling
    • Analysis
    • Design
  • Construction
    • Code
    • Test
  • Deployment
    • Delivery
    • Feedback

The Unified Process ( UP ) or Rational Unified Process ( RUP )

  • Inception Phase:
    • Communication Activities.
    • Planning Activities.
  • Elaboration Phase:
    • Planning Activities.
    • Modelling Activities.
  • Construction Phase:
    • Construction Activities.
    • Deployment Activities.
  • Transition Phase:
    • Construction Activities.
    • Deployment Activities.
  • Production Phase:
    • Deployment Activities.
    • Software Release.

The Dependencies Between Models Of The Unified Process

  • Use Case Model Specified By Analysis Model.
  • Use Case Model Realized By Design Model.
  • Use Case Model Distributed By Deployment Model.
  • Use Case Model Implemented By Implementation Model.
  • Use Case Model Verified By Test Model.

The Waterfall Model

  • Communication
    • Project initiation
    • Requirements gathering.
  • Planning
    • Estimating
    • Scheduling Tracking
  • Modelling
    • Analysis
    • Design
  • Construction
    • Code
    • Test
  • Deployment
    • Delivery
    • Support
    • Feedback

<<back to Study About UML Diagram

technical interview, coding qna, most technology question and answer, concept, managerial theory

Bibliography

https://binus.ac.id/ ( university )
https://ioc.ee/ ( university )
https://www.ku.edu/ ( university )
Business Process Modelling Series;CRC Press
Business Process Modelling Series;Pearson
Business Process Modelling Series;Routledge
Business Process Modelling Series;SpringerLink

di Tidak ada komentar:
Label:

Rabu, 10 Juli 2024

UML Vocabulary List

These are UML ( Unified Modelling Language ) Vocabulary List:

  • Basic Components:
    • Structure
      • Use Case
      • Class
      • Active Class
      • Interface
      • Component
      • Collaboration
      • Node
    • Component
      • Interaction Diagram
      • State Machine Diagram
    • Group
      • Model Geographic Boundaries ( Activity Partition )
      • Worker Responsibilities ( Swim Lanes )
      • Complex Transactions ( State Chart / State Chart Machine Diagram )
      • Package
      • Model
      • Sub system
      • Framework
    • Annotation
      • Notes
  • Relations:
    • Dependencies
    • Associations
    • Generalisation
  • Diagrams
  • Extention Mechanisms
unified modelling language, business process modelling

Related Post

di Tidak ada komentar:
Label:

Selasa, 04 Juni 2024

Use Case Diagram ( UML ) 2

Use case
Actor
Extension
Stereotypes

di Tidak ada komentar:
Label:

Selasa, 31 Oktober 2023

UML Diagram List

UML Diagram Hierarchy:

  • Structure Diagrams:
    • Class Diagram
    • Component (Structure) Diagram
    • Deployment Diagram
    • Object Diagram
    • Package Diagram
    • Profile Diagram
    • Composite Structure Diagram
  • Behavioral Diagrams:
    • Use Case Diagram
    • Activity Diagram
    • State Machine Diagram
    • Interaction Diagram:
      • Sequence Diagram,  
      • Communication Diagram
      • Interaction Overview Diagram:
      • Timing Diagram
to learn more about Use Case Diagram (UML) click 
to learn more about Sequence Diagram (UML) click 

Bibliography:

https://www.ibm.com/
https://www.visual-paradigm.com/
https://www.researchgate.net/
https://www.uu.se/ ( university )

Unified Modelling Language ( UML ), uml modelling, uml diagram, uml chart, program design, software design, application design

di Tidak ada komentar:
Label:

Selasa, 12 Agustus 2025

Visual Studio Code Extension 5

These are Useful Extension for Visual Studio Code Editor:

  • adammaras.overtype = Provides insert/overtype mode.
  • aflov.todogenerator = Boilerplate TODO .txt file generator.
  • aiekick.plantuml-switcher = Switch PlantUML elements (relations, links, ...).
  • alexcvzz.vscode-sqlite = Explore and query SQLite databases.
  • AlekseyNagovitsyn.autocomplete-line = Auto complete lines by grepping the project.
  • alpinebuster.vscode-latex-table-editor = An Open Source WYSIWYG table editor that exports to multiples languages including LaTeX, ConTeXt, Plain TeX, CSV, HTML, BBCode, Eplain, PreTeXt, MediaWiki, Markdown and WML.
  • antfu.browse-lite = Embedded browser in VS Code.
  • asciidoctor.asciidoctor-vscode = Provides rich language support for AsciiDoc.
  • barankilic.beamer = Beamer snippets for Visual Studio Code.
  • betterthantomorrow.paste-replaced = Paste text replaced using regular expressions that you configure, optionally simulating that you are typing it. Works anywhere in VS Code, not just the editors. E.g. good for fast typing canned text in your presentations and a lot of other cases.
  • bierner.markdown-mermaid = Adds Mermaid diagram and flowchart support to VS Code's builtin markdown preview.
  • Cardinal90.multi-cursor-case-preserve = Preserves case when editing with multiple cursors.
  • claudiobartoli.latex-songs = Syntax highlighting for LaTeX songs package.
  • cmoog.sqlnotebook = Open SQL files in the VS Code Notebook interface. Execute query blocks and view output interactively.
  • davraamides.todotxt-mode = Commands and decorators for managing todo.txt files.
  • efoerster.texlab = LaTeX and BibTeX language support for Visual Studio Code.
  • fabiospampinato.vscode-todo-plus = Manage todo lists with ease. Powerful, easy to use and customizable.
  • hari64boli64.latexlint = Linter for LaTeX with useful commands for academic writing.
  • HuYigong.vscode-latex-commands = Usefull commands for LaTeX.
  • isawu.partial-autocomplete = Adds common substrings to suggested completions list for partial auto-completion.
  • JaimeOlivares.yuml = UML diagramming tool based on the yUML syntax.
  • James-Yu.latex-workshop = Boost LaTeX typesetting efficiency with preview, compile, autocomplete, colorize, and more.
  • jebbs.plantuml = Rich PlantUML support for Visual Studio Code.
  • JeffersonQin.latex-snippets-jeff = Useful Snippets for LaTeX.
  • johnguo.columnpaste = Copy/Paste a column text.
  • JZWenxuan.spread-selection = Spread the selected text for every line in the clipboard.
  • k-kuroguro.csv2latex = VSCode extension for converting CSV or Excel table to LaTeX tabular.
  • kilacoda.code2latex = TeXify Your Code.
  • konstantin.wrapSelection = wrap selection with combination of symbols or your custom pattern.
  • lhl2617.latex-js-preview = Provides preview of LaTeX.js in VSCode.
  • ltex-plus.vscode-ltex-plus = Grammar/spell checker using LanguageTool with support for LaTeX, Markdown, and others.
  • lucax88x.codeacejumper = Visual Studio Code Ace Jump.
  • Lw-lonely.latex-table-helper = Latex Table Helper provides an easy way to generate table.
  • maptz.camelcasenavigation = Provides Camel Case cursor navigation for the Visual Studio Code editor.
  • marclipovsky.string-manipulation = Format strings to camelize, dasherize, etc.
  • mathematic.vscode-latex = LaTeX language support for Visual Studio Code.
  • mjpvs.latex-previewer = Preview a typeset LaTeX document in VS Code.
  • NadavGold.tex-matrix = An extension provides user snippets for latex which allows creating matrix up to 12x12.
  • nhawkes.selection-overtype = Typing with a selection active overtypes with matching case.
  • oijaz.unicode-latex = Insert unicode symbols for latex names.
  • pinglewareapps.pingleware-access-db-viewer = A Visual Studio Code extension to view Microsoft Access databases.
  • qwtel.sqlite-viewer = SQLite Viewer for VS Code.
  • rarnoldmobile.todo-txt = Todo.txt file management.
  • sabertazimi.latex-snippets = Powerful LaTeX Snippets for CS Paper Writing.
  • SaptarshiDey.latex-viewer = A simple LaTeX previewer for VsCode.
  • skyer.vscode-markdown-diagram = Adds Mermaid PlantUML DOT and ditaa support to VS Code's builtin markdown preview.
  • tecosaur.latex-utilities = An add-on to LaTeX Workshop that provides some fancy features that are less vital to the basic experience editing a LaTeX document, but can be rather nice to have.
  • TheUMLetTeam.umlet = Free UML Tool for Fast UML Diagrams.
  • tomoyukim.vscode-mermaid-editor = Live editor for mermaid.js in Visual Studio Code.
  • torn4dom4n.latex-support = LaTeX language support for Visual Studio Code.
  • usernamehw.todo-md = Todo tracking based on `todo.txt` format. Todo-md extension does NOT conform to the todo.txt spec.
  • vomout.latex-syntax = Rich LaTeX syntax highlighting (for use with Texlab).
  • vvlvm.paste-in-selected-case = 「Paste in Selected Case」は、クリップボードのテキストを選択したケース（Camel Case、Snake Case、Upper Case など）に変換して貼り付ける Visual Studio Code 拡張機能です。複数カーソルや複数行のテキストにも対応しています。
  • wmaurer.change-case = Quickly change the case (camelCase, SCREAMING_CASE or CONSTANT_CASE, PascalCase or TitleCase, dot.case, snake_case, kebab-case or param-case, slash/case, lowercase, UPPERCASE, space case or no case, Sentence case, Upperfirst, etc) of the current selection or current word.
  • wware.plain-text-diagrams = Syntax Highlighting and formatting for .ptd (Plain Text Diagram) files.
  • wxhenry.latex-begin-end-auto-rename = Automatically modify the other when editing either begin or end in LaTeX.
  • Yongke.latex-wordcount = Count the tex words by TexCount.



di Tidak ada komentar:
Label:

Senin, 21 Oktober 2024

Case Tools

Components of CASE Tools

  • Central Repository CASE Tools: A central repository is required by the tools to serve as a common source of integrated and consistent information. The central place of storage consisting of specifications of product, documents requirement, diagrams and reports and information about the management is a central repository.  The central repository also acts as a data dictionary.
  • Upper CASE Tools ( U-Case Tools ): Planning, requirement analysis, system modelling and high-level designing of different stages ( early stages ) of the software development life cycle can be performed using upper case. Examples of U-CASE tools include IBM Rational Rose, Sparx Systems Enterprise Architect, and Microsoft Visio.
    • Requirements Modeling Tools for capturing, organizing, and visualizing software requirements using techniques like :
      • Use Case Diagrams;
      • Entity-Relationship Diagrams
    • Diagramming Support for creating various diagrams, including :
      • Data Flow Diagrams, 
      • Entity-Relationship Diagrams,
      • State Transition Diagrams.
    • Modeling Languages: U-CASE tools often support modeling languages such as Unified Modeling Language (UML) for system modeling and design.
  • Lower CASE Tools ( L-Case Tools ): Implementation, testing, and maintenance ( later stages ) can be performed using lower case. Examples of L-CASE tools include Microsoft Visual Studio, JetBrains IntelliJ IDEA, and Git for version control.
    • Code Generation or Source Code Editor or IDE ( Integrated Development Environmet ) or Rapid Application Development Tools : Tools that automatically generate code based on design specifications or models, reducing manual coding efforts.
    • Source Code Management: Support for version control, change tracking, and collaborative development by multiple developers.
    • Debugging and Testing: Tools that aid in code debugging, unit testing, and code quality analysis.
  • Integrated: All the stages of the software development life cycle right from the gathering of requirements for testing and documentation can be performed using integrated tools.
  • CASE Management Tools:
    CASE management tools focus on project management aspects, including scheduling, resource allocation, version control, and documentation management. They help teams coordinate their efforts and ensure that projects are delivered on time and within budget. Key functionalities of CASE management tools include:
    • Project Planning: Tools for creating project plans, defining tasks, estimating resource requirements, and setting project milestones.
    • Document Management: Features for managing project documentation, including version control, document tracking, and access control.
    • Workflow Automation: Automation of workflow processes, such as code reviews, approvals, and change management.
    • Examples of CASE management tools include Microsoft Project, Atlassian Jira, and Redmine.
Top 13 Types of CASE Tools
  1. Diagram Tools:
    The components of the system, data flow, control flow and the structure of the system can be represented in graphical form using diagram tools.
  2. Process Modeling:
    The software process model can be created using process modelling tools for software development. The managers can choose a process model using process modelling tools or make modifications depending upon the software product requirements.
  3. Project Management
    Planning of the project, estimation of cost and efforts, scheduling of project and organizing of resources can be done using project management tools.
  4. Documentation Tools
    Before the beginning of software process, documentation of the software project must begin. This documentation must cover the all the software development life cycle phases and the completion of the software development phase as well. The documents are generated by the documentation tools for both technical and end users. The in-house professionals in the development team who refer the manual maintained for the system, manual maintained for reference, manual for training, manuals for installation etc. is described in the technical users documents. The functioning of the system and how system works is described in the end user documents.
  5. Analysis
    Requirements gathering, inconsistency checks, diagrams inaccuracy, redundancies in the data etc. can be checked using analysis.
  6. Design
    The block structure of the software can be designed by the software designers using design tools which are again broken down into smaller modules using techniques of refinement. The detailing of every module and the interconnections between the modules can be done using this.
  7. Configuration Management Tools
    Whenever one version of software instance is released, configuration management tools deals with the following:
    • Management of revision and version.
    • Configuration management of baseline.
    • Change control management.
    Automatic tracking, management of version, and management of release can be done with the help of configuration management.
  8. Change Control
    Change Control are a part of configuration management. The changes that occur in the software after fixing its baseline or after the first release of the software are dealt by change control tools. Tracking the changes, management of files, management of codes etc. can be automated using change control. The change policy of the organization can be enforced by using change control.
  9. Programming
    The programming environments like integrated development environment , library consisting of in built modules, simulation are all included in programming tools. The development of software product is aided by these and simulation and testing features are included.
  10. Prototyping
    The simulated version of the software product to be built is called a prototype in software. The look and feel of the product is provided by the prototype and several aspects of the actual product can be simulated using prototyping. Graphical libraries are contained in the prototyping tools. User interfaces and design that are hardware independent can be created using prototyping. Rapid prototypes can be built using prototyping based on the existing information. The software prototype can be simulated using prototyping tools.
  11. Web Development
    The web pages like forms, text, script, graphic etc. can be designed using web development tools. The web page that is being developed can be previewed to see how it looks after completion using web development.
  12. Quality Assurance
    Monitoring the engineering process and methods used for software development to ensure the quality is as per the standards of the organization can be performed using quality assurance tools. The configuration change control and software testing tools come under the category of QA tools.
  13. Maintenance
    If there are any modifications after the delivery of the software product can be done through software maintenance tools. Techniques for automatically logging, error reporting, generation of error tickets automatically and root cause analysis are used in the maintenance phase of the software development life cycle to help the software organizations.


Related Post

di Tidak ada komentar:
Label:

Rabu, 26 Juni 2024

Most Common UML Notation

Notes

  • Notes allow you to enter additional comments that are not captured in your diagrams. You can write anything you want in a note to explain your diagram, similar to a comment in code. 
  • Notes are pictured with the folded rectangle notation.

Stereotypes

  • Stereotypes signify a special use or intent and can be applied to almost any element of UML notation.
  • Stereotypes modify the meaning of an element and describe the element's role within your model.
  • A stereotype sometimes has an associated icon, such as stick-figure actor symbol.
  • The stereotype is shown using guillemots at either end of the stereotype name, as in «stereotype_name». However, because guillemots require an extended character set, you can substitute them for angle brackets, as in <<stereotype_name>>.
  • There is no limit to the number of stereotypes with which an element can be associated; sometimes you may end up specifying more than one stereotype.
  • The UML specification defines a set of "standard" or predefined stereotypes. Some of the more useful standard stereotypes include:
    • utility: Represents a class that provides utility services through static methods, just as Java's Math class.
    • service: A stateless, functional component that computes a value; could be used to represent a web service.
    • subsystem: A large component that is actually a subordinate system of a larger system.



Unified Modelling Language ( UML ), uml modelling, uml diagram, uml chart, program design, software design, application design

Related Post

di Tidak ada komentar:
Label:

Jumat, 11 April 2025

Tabel Identifikasi Aktor Use Case Dalam Markdown

Persiapan: Markdown Editor dan Markdown Reader yang mendukung markdown-it parser dan markdown-it-table-captions plugin (Table caption plugin for markdown-it markdown parser).

1. Buka Markdown Editor.
2. Ketik dokumen markdown di bawah ini pada markdown editor:
<meta name="description" content="Author: Tutor Course and After School Course, Description: menampilkan tabel Identifikasi Aktor Use Case UML (Unified Modelling Language), Rev-Number: 1.0, Language: id">

|ID|Aktor|Deskripsi|
|---|---|---|
|AC01|Admin _Inventory_|Aktor yang dapat mengelola data barang, mengelola data pemasok, mengelola data pelanggan, mengelola data barang masuk, mengelola data barang keluar, mengelola data persediaan barang, dan mengelola data permintaan barang.|
|AC02|Admin Pembelian|Aktor yang dapat melihat dan menyetujui permohonan permintaan barang|
|AC03|Admin Penjualan|Aktor yang dapat melihat dan menyetujui permohonan penjualan barang|
|AC04|Manajer|Aktor yang dapat membuat _user_ baru, memiliki hak akses untuk mengedit dan menghapus _user_, melihat laporan barang masuk, laporan barang keluar, laporan daftar barang, laporan persediaan barang, laporan permintaan barang, dan laporan penjualan barang.|

Table: Identifikasi Aktor
3. Simpan dengan nama file tabelIdentifikasiAktor.md.
4. Jalankan preview  atau save as HTML atau PDF.
5. Buka HTML di browser atau PDF di PDF reader.

Notes

Jika Markdown Editor dan Markdown Converter atau Markdown Compiler untuk parsing Markdown berjalan dengan baik maka akan menghasilkan file output HTML seperti di bawah ini:
<!DOCTYPE html>
<head>
<meta name="description" content="Author: Tutor Course and After School Course, Description: menampilkan tabel Identifikasi Aktor Use Case UML (Unified Modelling Language), Rev-Number: 1.0, Language: id">
</head>
<body>
<table>
<caption>Table: Identifikasi Aktor</caption>
<thead>
<tr>
<th>ID</th>
<th>Aktor</th>
<th>Deskripsi</th>
</tr>
</thead>
<tbody>
<tr>
<td>AC01</td>
<td>Admin <em>Inventory</em></td>
<td>Aktor yang dapat mengelola data barang, mengelola data pemasok, mengelola data pelanggan, mengelola data barang masuk, mengelola data barang keluar, mengelola data persediaan barang, dan mengelola data permintaan barang.</td>
</tr>
<tr>
<td>AC02</td>
<td>Admin Pembelian</td>
<td>Aktor yang dapat melihat dan menyetujui permohonan permintaan barang</td>
</tr>
<tr>
<td>AC03</td>
<td>Admin Penjualan</td>
<td>Aktor yang dapat melihat dan menyetujui permohonan penjualan barang</td>
</tr>
<tr>
<td>AC04</td>
<td>Manajer</td>
<td>Aktor yang dapat membuat <em>user</em> baru, memiliki hak akses untuk mengedit dan menghapus <em>user</em>, melihat laporan barang masuk, laporan barang keluar, laporan daftar barang, laporan persediaan barang, laporan permintaan barang, dan laporan penjualan barang.</td>
</tr>
</tbody>
</table>
</body>
</html>

Output

Table: Identifikasi Aktor
ID Aktor Deskripsi
AC01 Admin Inventory Aktor yang dapat mengelola data barang, mengelola data pemasok, mengelola data pelanggan, mengelola data barang masuk, mengelola data barang keluar, mengelola data persediaan barang, dan mengelola data permintaan barang.
AC02 Admin Pembelian Aktor yang dapat melihat dan menyetujui permohonan permintaan barang
AC03 Admin Penjualan Aktor yang dapat melihat dan menyetujui permohonan penjualan barang
AC04 Manajer Aktor yang dapat membuat user baru, memiliki hak akses untuk mengedit dan menghapus user, melihat laporan barang masuk, laporan barang keluar, laporan daftar barang, laporan persediaan barang, laporan permintaan barang, dan laporan penjualan barang.


lightweight markup syntax, lightweight markup document, lightweight markup language


Bibliography

https://daringfireball.net/projects/markdown/
https://developers.google.com/
https://github.com/
http://stackoverflow.com/
https://www.tutorialspoint.com/

di Tidak ada komentar:
Label:

Sabtu, 25 Januari 2025

Customizing Latex Font Style

Settings Document Font Sizes

\documentclass[options]{class}
For example, the article class supports 10pt, 11pt and 12pt for the main document text:
\documentclass[11pt]{article}

Customizing Latex Heading / Section Font Style And Body Font Family Style / Font Face Style / Font Type Style

You can set up the use of sans font as a default in a LaTeX document by using the command:

\renewcommand{\familydefault}{\sfdefault}

Similarly, for using roman font / serif font as a default:

\renewcommand{\familydefault}{\rmdefault}

Similarly, for using typewriter font / monospace font as a default:

\renewcommand{\familydefault}{\ttdefault}

Type the above command in preamble before \begin{document}.

Customizing Latex Font Family Style / Font Face Style / Font Type Style

\renewcommand\bfdefault{bc}
\renewcommand\rmdefault{garamondx}
\renewcommand\mddefault{mc}
\renewcommand\sfdefault{phv}

Type the above command in preamble before \begin{document} to use one of the font family from the font family list below as a default font in a LaTeX document .

Font Family List
pag = Avant Garde
fvs = Bitstream Vera Sans
pbk = Bookman
bch = Charter
ccr = Computer Concrete
cmr = Computer Modern = Serif
cmss = Computer Modern Sans Serif = Sans Serif
cmtt = Computer Modern Typewriter = Typewriter / Monospace
pcr = Courier = Typewriter / Monospace
phv = Helvetica = Sans Serif
fi4 = Inconsolata
lmr = Latin Modern
lmss = Latin Modern Sans
lmtt = Latin Modern Typewriter
pnc = New Century Schoolbook
ppl = Palatino
ptm = Times
uncl = Uncial
put = Utopia
pzc = Zapf Chancery

Format Font Style In Bold For Entire Document

\renewcommand{\seriesdefault}{bx}

Format Font To Standard Main Document Font

\textnormal{text normal}
or
{\normalfont text normal}

Format Font For A Part Of Our Document 1

If we need to use a certain font family only for a part of our document, we can write it in a text command.
\textrm{Serif Font Family}
\textsf{Sans Serif Font Family}
\texttt{Monospaced Font Family}

Format Font For A Part Of Our Document 2

If we need to use a certain font family only for a part of our document, we can write it in a text declaration form/text switches, which is often useful. This form takes no arguments, as in {\rmfamily text}. The scope of the declaration form lasts until the next type style command or the end of the current group.
\rmfamily
Serif Font Family

\sffamily
Sans Serif Font Family

\ttfamily
Monospaced Font Family

or you can use like this following foms:
{\rmfamily Serif Font Family}

{\sffamily Sans Serif Font Family}

{\ttfamily Monospaced Font Family}

Format Font Shape For A Part Of Our Document

for italic shape
\textit{Italic} 
or
{\itshape Italic}
for slanted shape
\textsl{Slanted}
or
{\slshape Slanted}

Format Font Weight For A Part Of Our Document

to print in bold characters
\textbf{Bold}
or
\bfseries

Format Font Emphasizing For A Part Of Our Document

 to print in emphasize or italic characters
\emph{emphasised text}

Changing Letter Case

LaTeX provides the option to change the letter case of a piece of text to lower or upper case: \lowercase and \uppercase are the commands for the job. 
\uppercase{text}

\lowercase{TEXT}

Changing Underline 

to print in underline characters using underline command 
\underline{text}

Changing SuperScript And SubScript

to print in subscript and superscript characters using subscript and superscript command 
\textsubscript{text}
\textsuperscript{th}

Notes

Notice that in the sans serif font family, italic and slanted fonts are the same. Some font families don’t have a format or some font shape form. If that is the case, these previous commands produce the form that is available.


typography, low-level font commands

Bibliography

https://latexref.xyz/
https://latex-tutorial.com/
https://www.dickinson.edu/ ( university )
https://www.overleaf.com/
https://www.scijournal.org/
https://tug.org/

Related Post

di Tidak ada komentar:
Label:
Langganan: Postingan (Atom)
  • Study About Google Docs Suite
    About Google Docs You can create, view and edit Google documents, Spreadsheet, Presentation as well as Microsoft Office Word®, Microsoft Off...
  • Chinese Stroke Order + Unicode
    A set of Chinese characters representing strokes used in writing Han Characters were added at 31C0..31E3 in Unicode Characters. The names o...
  • Number Line In Latex 6
    1. type this following latex code in Latex editor for drawing a number line: % !TEX TS-program = pdflatex % !TEX encoding = UTF-8 Unicode % ...
  • Customizing Latex Font Style 3
    < Previous  Customizing Latex Font Style 2 Serif Fonts This following Latex font suggest to minimal study on the screen only ( because mo...
  • Istilah Matematika 3
    Akar kuadrat adalah salah satu dari dua faktor yang sama dari suatu bilangan. Contoh: 9 = 3 karena 3 2 = 9 Anggota Himpunan adalah suatu o...