Case "Designing a web service for booking tickets." Business analysis. Description of existing business processes (AS-IS)
After it became clear what situation we are in and who are the main agents, it is necessary to describe the business processes that require automation or change. This will help to understand what is happening and in what sequence, as applied to this case - how is the ticket purchase and booking generally performed?
In the form of diagrams, a business process can be described using various notations: ARIS - VAD and EPC , IDEF0, BPMN, etc. There are many notations, each has its own advantages and disadvantages, this topic is not covered in this article.
The main advantage of using diagrams is visibility. The main disadvantages are that it is difficult to depict all possible branching variants and make long changes.
')
Another way of documenting business processes is a structured text description. As a description format, an approach was taken to writing business and system options for using the system ( use cases ) proposed by A. Kobern .
The main argument in favor of such a textual description of business processes is the speed and convenience of creating, editing and making changes. A significant disadvantage is the complexity of perception for unprepared readers.
In conclusion, I would like to say that the following recommendation is valid: if there are not very many processes, then it is better to use a graphical description format, and if there are many processes, then it makes sense to depict the most important ones using diagrams, and describe the rest in text form.
[Contents of a series of articles]
Iii. Process description in graphic form
In the form of diagrams, a business process can be described using various notations: ARIS - VAD and EPC , IDEF0, BPMN, etc. There are many notations, each has its own advantages and disadvantages, this topic is not covered in this article.
The main advantage of using diagrams is visibility. The main disadvantages are that it is difficult to depict all possible branching variants and make long changes.
')
Visiting the cinema without pre-booking tickets (in VAD notation)
Visits to the cinema with reservation (in VAD notation)
Detailed description of both cinema visitation options (in EPC notation)
Iv. Description of processes in the form of text scripts
Another way of documenting business processes is a structured text description. As a description format, an approach was taken to writing business and system options for using the system ( use cases ) proposed by A. Kobern .
The main argument in favor of such a textual description of business processes is the speed and convenience of creating, editing and making changes. A significant disadvantage is the complexity of perception for unprepared readers.
In conclusion, I would like to say that the following recommendation is valid: if there are not very many processes, then it is better to use a graphical description format, and if there are many processes, then it makes sense to depict the most important ones using diagrams, and describe the rest in text form.
[Contents of a series of articles]
Source: https://habr.com/ru/post/107908/
All Articles