Competent development of a new project, components?

Question

Software design

Hello everyone
Interested in your opinion on the process of developing a new project:
1) Business task - is formed by the customer
2) System analyst - analyzes the area and forms the TOR. In fact, System Analyst = Team Lead? Product manager (!not Project)
3) Architect (CTO) - deep knowledge of IT - Creates a database structure (DBA), sets deep technical requirements for Programmers (Using Frame, programming language, using a technology stack), including participating in planning and the timing of the project.
4) Programmers (Front, Back) - take the TK-Documentation compiled by the System Analyst + Architect, and clearly run according to the plan without wasting time thinking about how to do it and what to use
5) Is the documentation for the code still written by the programmer himself or by a technical writer? after all, there should be uniformity of documentation
6) Q&A
7) Product release
Interface design (UI UX) deliberately omitted I
have a number of questions here
validates this scheme, with the study of deeper issues (Scheme of bases, solutions used, requirements for programmers how to do it)
In fact, SA + Architect - work in a single bundle - and the result of their activity is the Product Construction Project.
2) In fact, if the development of a software product follows a well-planned project plan, then the Project Manager is not actually needed. The architect will drive the prepared project into Jira Protfolio and the programmers run along it, summing up the results of the sprints weekly. I don't understand the meaning of Project Manager(!Not a product).
3) In fact, the Architect should do code review of completed tasks like this?
4) Documenting the code - It's still not clear, if the programmer who wrote the code does this, then how do they bring the documentation to the unity of the format? Should the technical writer then moderate the documented code?
5) Store documentation is good in Jira Confluence. But to generate documentation for the Rest API and the DB Structure, which tools are better?
Thank you!

Answer 1

between paragraphs 1 and 2 there is also a business analyst who translates the "task" of the Customer into a really understandable task. For often the Customer's task sounds like "I want everyone to be well", and only with the help of a business analyst it becomes something like "reduce the average invoice processing time to 1 minute 30 seconds".