Tool for describing business processes in order to prepare technical specifications for programmers

Question

ERP

We have a medium-sized organization (or even a large one by the standards of the local market) that sells household appliances.

1C 8.1 UT is now used as ERP. ERP was sharpened for us back in 2007. And we have outgrown it. Some business processes need to be changed, some have already changed and the question arose of creating an ERP (most likely based on 1C 8.2), tailored for already different business processes.

It is necessary to describe the business processes of the enterprise, which would then smoothly flow into the technical specification and be automated (to the extent possible to automate them, of course) by third-party programmers.

Question. What tool (program, programs) would be more convenient / better to use to prepare the ERP structure, describe the business processes of an enterprise and prepare technical specifications for 1C programmers?

We tried it on Business Studio, but something didn't work out. And even after this, programmers need to figure it all out.

Anyone with experience in this area or any suggestions would be greatly appreciated.

Answer 1

>> for 1C
programmers >> for 1C programmers
>> for 1C programmers
>> for 1C programmers
v8.1c.ru/metod/fileworkshopdownload.htm

Answer 2

First you need to determine how your business processes are best represented. Business process modeling model. Well, then find the best tool for her.
I would advise UML + any drawing tool that can do it. Programmers are accustomed to UML, it will piss them off the least.
Magicdraw, Visio... most of the good drawing apps are paid, but there are often free viewers for them, so programmers don't have to buy another hundred expensive licenses.
Also, it is convenient for programmers to think in terms of individual features and blocks, while it is more convenient for managers to draw the whole process in one huge monolithic diagram. If you're designing a process model from scratch, there are two other things you can try to keep in mind: the division into subtasks, and the prioritization of those subtasks for implementation. It can be great to reduce the risk when the programmers themselves begin to breakdown what they haven't figured out yet ;)

Answer 3

BPwin+ERwin (ancient thing), MS Visio, BPMN+BPMS.

Answer 4

Our company used MS Visio to describe the PSU. BPWin and other Erwin they are quite difficult to perceive by the programmer's brain, they were tested in practice.
Visio used an extended mechanism for describing the process through flowcharts.

Answer 5

Bizagi - free, in Russian. Supports BPMN notation. Details here casepress.org/bizagi-process-modeler-sreda-dlya-modelirovaniya-biznes-protsessov-na-russkom-besplatnaya/
BPMN is well suited for process drawing. For some implementation projects.
If you need to describe the processes so that employees can then work on them, so that employees can be trained on them, so that they are useful and so that they can stabilize the quality of the results, then process diagrams in BPMN notation can be put in the toilet for wiping back seat. Nobody ever reads them. They are put on the shelves and arrived.
In this case, the usual description of processes in human language in the form of instructions works better. This is what people read, they are ready to learn from them, and it is easy to bring the implementation project to a result using them. Tested on many projects. There is a description of an example solution here casepress.org/?portfolio=kompleksnaya-model-description-protsessov

Answer 6

You can draw a process diagram in the cloud, at https://storm.bpmn2.ru