Jak przeprowadzić pełną, poprawną analizę procesów biznesowych dla projektu?
Pełna analiza powinna zawierać informację o:
1. Analizie procesów biznesowych firmy.
2. Analizie procesu, którego tyczy się projekt.
3. Analizie zmiany procesu (zmiany wprowadzonej przez projekt).
4. O tym, jakie narzędzia, metody, techniki powinny zostać wykorzystane.
Poniżej przedstawię kroki, które powinny mieć miejsce podczas takowej analizy. Dorzucam też kilka szczegołów, uwag, komentarzy.
Całość jest w języku angielskim, bo wykorzystuję scenariusz z mojej pracy. Więc do dziela.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
1. Business Analysis
Aim
Business profile
Product scope
Organization structure
External companies cooperation
Company, business mission and startegy
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
2. Process Analysis
Aim - description
Main process (understood as a whole system)
General info
Process components (max 5 (+/-1))
Main process flowchart (Activity Diagram)
Project process (-es)
General info
Product (-s)
Process activities
Process Flowchart (Activity Diagram)
Actors involved in the process
Streamline (ulepszać proces) / Create new Process
Current problematic situation
Cause - event - effect
Proposed solutions, changes
Next steps
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
3. Activity Diagram
Activity diagram usage
Actions, steps flow in process. Scope of the actions shows how to achieve a goal.
Action flow aim: actions order and relations.
Usage: process modeling, use cases, operations, algorithms
Swimlines assigned actions to actors (define actors responsibilities)
Could be created in www.draw.io, www.creately.com
Info: http://brasil.cel.agh.edu.pl/~09sbfraczek/diagram-aktywnosci,1,10.html
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
4. Sequence Diagram
Sequence diagram usage
Statements (interactions) flow included in time frame amongst actors, objects, interfaces of the system, process, use case,
Statements aim: action order, control flow, algorithm template
Scheduled communication exchange amongst actors
Could be created in Power Designer
Info: http://brasil.cel.agh.edu.pl/~09sbfraczek/diagram-sekwencji,1,13.html
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
5. Ishikawa Diagram
Common naming
Cause and effect diagram (Diagram przyczynowo - skutkowy)
Fishbone diagram (Diagram rybiej ości, Diagram ryby)
Diagram jodełkowy
Online
http://www.xmind.net/
http://creately.com/diagram-type/template/g6adlbuz3/fishbone-diagram
Usage
Define, assess cause (root, reason) of the problem, defect
Graphical presentation of all related reasons which lead to the problem
Location, placement of the cause in the factor, process, component
Needed group work (brainstorm) - especially in Detailed Cause Location step
Przyczyna = Cause = Reason, Root
Problem = Skutek = Effect
Top - Down process - from general cause to the detailed root
Definition of root-cause (main cause of the problem)
Process
Problem identification
Definition, description of the problem to be solved, fixed
Define main groups, categories of causes Consequences
Definition of main cause groups
Very common is to use mixed categories not clear factors, processes, components
Detailed causes location
Searching problem causes within factors, processes,components
Getting deeper to the detailed causes
Define percentage probablility of the subcauses (equal to 100% in main cause)
Results analysis
Definition of root-cause (main cause)
Abstraction of main, crucial, the most influential causes (max 4)
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
6. DFD - Data Flow Diagram
Aim
Identify data type, data flow, data transformation within the company, system, process.
Define input, output system, process documents
Determine data transforming processes
Describe data flow graph within processes
Data Flow Analysis
Contextual Diagram - System in the Environment
System Contextual Diagram = Environment Diagram = Level 0 Diagram
General process relation model where our system is settled in the center. All related (to our system) elements (actors, processes, systems) are treated as an external elements.
General relations between our system and other elements - initial data flow informations.
First Level Diagram - Processes in the System
General Decomposition of Contextual Diagram = General System Diagram = Level 1 Diagram
All main processes, actors from our system displayed as a graph with all relations between them.
General data flow witihn processes, actors of our system.
Second Level Diagram - Activities in the Process ID =
Detailed Decomposition of Process = Process Diagram = Level 2 Diagram
All activities from the process displayed as a graph with all relations between them.
Detailed data flow within process activities.
