Additional than prototyping and incremental delivery, are there other steps that can be taken during software development that may help predict changes and make the program more resistant to change?

It's feasible that the software development process's metric use may be elucidated. Everything has to be handled with extreme care.

How important are concepts such as coherence and connection when it comes to the design of software? How can we expedite the construction of high-quality programs by providing instructions that are crystal clear and step-by-step in nature?