Automatic Software Design

 

 

In 1973, Peter Freeman, an AmericanArticleAutomation software design has the assumption that, if there is such a machine, when we tell it what software we need, it will immediately meet our requirements and automatically generate what we needProgram.

From the user's point of view, the automatic software design divides software procurement into two steps: provide demand and receive software products. From the perspective of software developers, automatic software design divides software provision into two steps: obtaining requirements and submitting software products.

Based on the assumption of automatic software design, software developers are compared to printers, and user needs are compared to a document. The content of the document may be a speech, a work report, or a beautiful picture. The printer prints the content without any deviation based on the document layout, style, and color requirements. The user gets the expected results.

Therefore, the user's requirements, as the input information of software products developed by software developers, play a decisive role and influence on whether the software products can meet the user's needs.

The degree of clarity, timeliness, accuracy, completeness, and meticulousness of the user's business description are all factors that directly affect the product. Users' business is the focus of both users and software developers.

Due to the limitation and continuity of people's understanding, coupled with the changes in the customer's business environment, the design and software delivery cannot be completed at one time. In order to ultimately meet the customer's business needs, the demand must be continuously improved.

To achieve continuous improvement and reduce the impact of demand changes, modeling is usually used. Describe services and interactions between users and systems using abstract and independent models.

UML, MDA, and SOA are all languages, tools, standards, methods, and processes that target your business.

During model implementation, you can adopt a policy of encapsulation changes to encapsulate the changing business functions. When the business needs change, you only need to modify or replace the changed parts to meet the business needs.