How is the site developed?

Question

Programming

Tell me the correct order, and where parallel development is possible, if we are talking about teamwork.

Answer 1

The programming language (or languages) (php, python, java, scala, perl, erlang) is chosen according to the command level. Next, the Architects select:
- application architecture (applications): frontend, backend, databases, caches, message queues, etc., CMS or CMF or framework/frameworks.
And so, we have a team, what, how and what to do.
After that, the Designer makes graphic files and transfers them to the Layout Designer.
At this moment, Programmers can do the main site machinery, write out interaction with databases, frontend / backend, create ORM and queries, make document prototypes and business logic.
As soon as pieces of markup come from layout designers and designers, they are pulled onto the already existing machinery.
At the same time, the testers continuously run functional and load tests in the continius integration mode.
Further stages come the stages of testing and fixing errors by the whole team in a circle.
As soon as the Manager is satisfied with the work, they give it to the Customer. And then - the stages of testing and fixing errors by the whole team in a circle until the Customer is satisfied.
Well, for good, since there are practically no two identical projects, then all the work can be drawn in a Gantt chart . Then it will be immediately clear who is doing what in parallel in this project - infineconomics.blogspot.ru/2014/04/gantt-chart-in-...

Answer 2

Communication with the client, TK + Contract, Prototype, Design - design approval, layout, integration with CMS

Answer 3

habrahabr.ru/post/224655
habrahabr.ru/post/142164

Answer 4

It all starts with an idea, an idea, then a technical specification, a specification, a contract, paper formalities are drawn up ... Then a prototype and design are worked out, final design forms and navigation are drawn, coordinated and given to layout designers. Layout, programming and coding, connection of various libraries, in general, "revitalization" of the site, then its publication and integration. After that, verification, validation, testing, as a result of which shortcomings and errors are corrected. Perhaps the necessary documentation is written during the entire development process.
In general, the software development process, and in particular the site, is usefully described in the ESPD, and in the GOST 34-series.
Very understandable, in the Soviet way, but succinctly and necessary. The life cycle of software in general in different cases may differ from project to project, from complexity and duration.
But the point is this.