Distinguish between the use of methods designed for repetitive tasks

[sujonkumar6300]

Manufacturing and methods designed for creative tasks (e.g., creating software). Computers are well suited to performing repetitive, mechanical tasks, and so computerized process automation in modern physical product manufacturing has a prominent place in the contemporary factory. Humans are required to design such an automated factory, but increasingly less so to act as machines within it; good factory design avoids placing humans in repetitive, mechanical tasks. Likewise, humans are required to design a software factory, but good design also avoids placing humans in repetitive azerbaijan phone number data mechanical tasks. The effective end product in software is the productive execution of instructions given to the end user's computer, and the factory for that end product is the operating system itself. The manufacturing blueprints for that end product are the executable artifacts that are copied to such computers when a release is made. In other words, what a programmer does is design the construction blueprints that will be taken by the software factory, ie, the operating system, to build the final product each time it is executed on the user's computer.

Consider methods centered on the premise that source code is the design. As a direct implication of the previous point, a realistic approach to quality in software development revolves the methodological effort around the design of the best possible construction plans for the software, because there, in these plans, and in the properties that emerge from them, every requirement, every specification, every testing effort, every analysis of both the problem and the solution, and, in short, every realistic methodology, must be specified. Otherwise, efforts that do not have a relationship with these plans, with that form of technical documents also called "source code", remain unmaterialized. Therefore, in the methodological exercise it is convenient to distinguish between methods that help to achieve better source code from those that are only focused on other types of non-executable documentation.