Please enable JavaScript.
Coggle requires JavaScript to display documents.
Mindmap 3 - Business Modeling - Coggle Diagram
Mindmap 3 - Business Modeling
UML
standard modeling language, not a software development process, suitable for use case driven, iterative & incremental development processes
Current version 2.5 (June 2015)
describe, specify, design & document existing or new business processes, structure and behavior or artifacts of software systems.
Set of tools to document the analysis & design of software system:
Things: primary elements of UML
Structural things: classes, interfaces, use cases,...
Behavioral things
Describe how things work: interactions and state machines
Group things --> define boundaries
Annotational things: notes to the diagrams
Relationships
Behavioral: used in behavioral, relationships: communicates, includes, extends, generalizes
Structural: tie things together in structural diagrams, show inheritance: dependencies, aggregations, associations, generalizations
Diagrams
Structural diagrams: describe relation between classes, show static structure of the system: Class diagrams, Object Diagram,...
Behavioral diagrams: describe interactions between people(actors) and a use case(how actors use the system): UseCase Diagrams, Activity Diagram, State Machine Diagram,..
Commonly used: Use case diagram: how system is used, use case scenario, activity diagram: overall flow of activities, sequence diagram: sequence of activities and class relationship, class diagram, state chart diagram
Business Analysis Model
defines internal business workers and business entities need to be related and how they need to collaborate
structural organization --> independent units & how they interact
-> realize behavior in business use cases
purpose: describe how business use cases are performed
defines external business services invoked by business actors in the performance of business use cases
Business Use-Case Model
purpose: describes the direction and the intent of the business, the added value and means of interaction with the stakeholders and customers
used by: stakeholders, business-process analyst, business designers --> understand & improve the way business interacts with its environement
systems analyst & software architects -->. context for software development
model of business goals and intended functions, describes what happens between business actors and the business, essential input to identify roles and deliverables in the organization
Business Modeling
Scope of business modeling: tung ung voi các level cua yêu cau
scenario 3: 1 business many systems
scenario 4: generic business model(business improvement)
scenario 2: domain modeling
scenario 5: new business(business creation)
Scenario 1: organization chart
scenario 6: revamp(business reengineering)
supports the discovery of system requirements, consists of studying & understanding the organization and its processes --> result: business analysis model & business use-case model
Business use-case diagram
Object
Business boundary: rectangle with subjects name, use cases inside it and business actors outside
Business actor: a role played by a person or system external to the modeled business & interacting with the business. Represent sth outside modeled business & involved with <= 1 use case.
Business use-case
business function, process, activity in modeled business. defines what happen in the business when the use case is requested by business actor
understand the purpose --> need step-by-step outline of the workflow
interaction between business and business actors, significant business events
Relationships
Actor & use-case: Association: interact by sending & receive messages, both can take the initiative to interact.
Use-case & use-case
Include: partition out parts of a workflow when use case depends on the result not the method
Extend: add a flow to use case that already complete itself
Generalization: show workflows share structure, purpose & behaviors.
Actor & actor: Generalization: some actor play same role in a business use case --> shared one is an abstract actor, inherited by original ones
illustrate the structure of BS use-case model, behavioral diagram
Business Modeling process
Business Use-case analysis
Find business actors & use-cases
Find business actors: individual, group, organization, company,... interact with system
Find business use-case
consider what value business actor receive from the system, services expect from the system
categories: core(external-facing business use cases provide value-chain), management(internal use case coordinate value chain), support(internal use case support value chain)
Define business system context: determine system development boundary: find entities outside system, entities inside organization but outside system
Creating business use case model: business system boundary, business actor, business use-cases, relationships (actor-actor, use case-actor, use case-use case), complete & accurate model
Capture business vocabulary: Role: business-process analyst, describe how to define common set of business terms --> common vocal to use in all textual descriptions of business
Find business workers & business entities
Assets Target Organization
Role: Business-Process Analyst, Output: Target-Organization Assessment. Only necessary when engineer business, if only building chart don't need
Describe current status of organization, why the target must be engineered, identify stakeholders to business modeling effort
Initiate an assessment -> identify stakeholder -> describe structure of target organization -> identify key persons -> assess business idea & business strategy -> benchmark -> measure target organization -> identify underlying reasons for change -> estimate capacity for change -> identify problem -> draw conclusions -> make recommendations
Business Use-Case Analysis
Writing business use case
Capture business use-case scenarios: instance of use-case, give each scenario a name, list name of flows in the scenario
Collect additional requirements
Outline the flow of events: Basic flow, alternative flow
Business Use-case Realization
describe how system, business worker, business entities, business event collaborate to perform business use-case
role: business designer, output: activity diagram, class diagram, communication diagram,...
Business worker report used by people interested in business analysis model
brief description -> responsibilities-> relationships -> operations -> attributes -> competence requirements -> diagrams
Business entities
piece of info manipulated by business actors and business workers, not initiate interactions on their own
ensure the info created and required by the organization is present in the business analysis model
Business workers
collaborate with each other to manipulate business entities to perform responsibilities
represent a role human, system, software,.. play within the organization
confirms responsibilities and interactions of the business workers correctly how work is performed or should be performed
Activity diagram
represent a flow of business use-case provide the value of the served business actor requires
often consists of a basic flow and 1 or more alternative flows
order of task to acomplish business goals satisfy commitments between external business actors and internal business workers
Sequence diagram
depicts the detail of interactions between business workers, business actors & how business entities are accessed of a use-case
notations: actor, object, lifeline, execution occurrence, message, guard condition, frame,...
Communication diagram
identical to sequence but focus on objects, present the subset of objects relevant to the affected working sequence(links, messages, message sequences)
notations: actor, object, association, message, guard condition, frame
Class diagram
generic structure in business domain model, part of the documentation of a business use-case realization
shows associations, aggregations & generalization between business workers & business entities
Behavioral state machine diagram
illustrate which state a business workers or a business entity can have
events cause transitions from state to state, actions result from state change
notations: state, initial state, final state, event, transition, frame