Are there languages to describe the technical specifications for the formation of complex reports in a tabular form?

Database reports are generated in large quantity. Reports from small to large. "Terms of reference" for the rules to calculate cell values may take 50 pages or more. Tasks are written, almost formal (for strings.. that counts ... details of same, to such conditions, exceptions-such,...). To write an automatic parser is impossible due to the formal approach in the description of the conditions. I think so, not to reinvent the wheel that already exist methods or languages for writing such tasks, which then are built in the automatic mode queries. Could you tell me the direction where to look? Because when you come to a "job" like that, takes a lot of time to study, it is difficult to understand what has changed that added.
June 3rd 19 at 19:38
4 answers
June 3rd 19 at 19:40
SQL
The problem is that TK is lowered from Moscow to the regions in an abstract form. In Moscow there are no bases, there is only compose of the condition groups table. In the regions it's different for everyone. This pure SQL is out. - rico23 commented on June 3rd 19 at 19:43
June 3rd 19 at 19:42
SQL was originally invented for the managers.
Not for programmers.

There is also a graphical query builders SQL.
It is suitable to use the most that neither is ordinary users.

https://www.quora.com/What-are-some-good-visual-SQ...
They are actually very, very much...

But then the question arises -
and whether users have to formally approach the problem,
to all these formal tools automatically use.

I believe that it is easier to blame it all on programmers.
Graphically I think it will be very difficult, TK TK takes dozens of pages. The question is to offer some kind of formalized approach to the description of the complex TK. - rico23 commented on June 3rd 19 at 19:45
that they still manually process.
Well, for example Rational RequisitePro - rico23 commented on June 3rd 19 at 19:48
June 3rd 19 at 19:44
In addition that you will need to find and negotiate the use of some markup, will need to train Directors in the use of this language. This second task can be much more unmanageable than first.

With regard to languages for describing/modeling and reporting forms, the well-known standards. Everything is always bound to a specific BI tool and built into its graphical IDE with which these reports are: MS SSRS, Crystal Reports, Cogons BI, Oracle BI, etc.

In simple cases it would be possible to do the usual UML with the addition of OCL, but do you will that be enough?

If you try to solve another problem - to see the changes in the TOR of the reporting form, you do not need a language, a tool for managing requirements (or ALM system).
June 3rd 19 at 19:46
Strange job. Seems a bit implausible.

Before to fence in the languages, try formationat itself your problem.

# Version control

Vsevolod Vladimirov be sure to pay attention to the last phrase, "istakes a lot of time to study, it is difficult to understand what has changed, added". Most likely, you have a problem with task/bug tracker. It is not. As there is no storage system tasks and versioning solutions. Therefore, you can trace the history of changes and the main structural load on the formal structure and algorithms. From this it follows that the description of one much uses

# Data structures

Describing working structures, you would have a brief and succinct definition that could be used in the job. For example, lists, trees, temporary tables, sampling static sampling, stacks, links. For data structures, you can always apply

# Algorithms

What's easier to point to the "last cut"? Never had residue on "end of period"? Unique. Search of duplicates. Find the first occurrence. Sort.

# Classification

You need to constantly classify of reports and their structuring with the use of at least a basic taxonomic principles. Structure and hierarchy allows you to quickly search similar, which in General may in itself be a solution to the problem, because to replace the condition not the same as to query the DB again.

# Increase the level of abstraction

After each (or each group) in the development cycle, the report would not be bad to increase (try to do) level of abstraction description of the problem. Ultimately, your goal in automation. And what could be nicer than a precise answer to the query: "Give the most active customers of each of the first quarter in 10 years."

It turns out that the best tool the pencil again.

Find more questions by tags SpreadsheetsPreparation of technical assignment