How are complex large projects implemented?

Question

Programming

Where can I read competently about the creation of large complex technical projects? How are such projects done? How technical specifications are compiled, architecture, plan, delegation of authority, etc. are made. etc.?

Answer 1

If about methodologies, then google Scrum, Agile and so on.
If about architecture, then google Fowler, "Rapid software development. Principles, examples, practice" and so on.
No way. Seriously. 2-4 people sit down and code for days. If it is possible to separate the authorities, they will allocate funds and space for the project. If not, then either it is completed at night, or its own LLC and the search for investments / customers.

Answer 2

Complex large projects are usually grown : first a prototype is made, then iteratively completed, gradually absorbing new features and new users, and then you see, oh, it has become large and complex.
And a large and complex project of the next generation or on a similar topic is done by analogy with an already done project, such as Habr → GeekTimes, Megamind, Toaster. Having gained experience, the authors of such projects no longer ask questions on the Internet.

Answer 3

We read about Scrum / Kanban and XP (google in the context of agile). Separately, it is worth reading about BDD. There you will have both how to lead and do the specification for the project, and how to plan ...
As for the architecture itself, there are heaps of things, like Service-oriented architecture, hexagonal architecture (which goes well with SOA), you can read about DDD ... In a word, you can read Martin Fowler, Eric Evans and other cool dudes.
In any case ... the first pancake is lumpy if there is no one nearby for whom this is not the first pancake. Well, again, everyone has a different concept of "big project".

Answer 4

:) Are you talking about a business card site? Not?! OK. We take classmates and imagine that each individual function is a separate site. The size of such a function site will turn out to be the size of a business card site. That is, we make a lot of business card sites and combine them into one structure.
It turns out the method of eating an elephant: if you can not eat the whole elephant, eat it in parts :).