Discussion on software factory

The software factory is an industrial software development methodology, just as the factory is different from the Research Institute-the factory focuses on tool applications, the Research Institute focuses on the same theoretical practice-software factory and agile development theory are also basically opposite: it does not emphasize the continuous improvement of systems and processes, it emphasizes a highly-divided team-Work Model and provides the resources required during the development cycle (for exampleCodeComponents, tools, practical references, documents, and standardized activities) to ensure the quality of the final product and improve development efficiency.

Prerequisites for the software factory

A large number of practical theories (Mode) And productization tools (Reusable frameworks, development tools and testing tools).

Taking the dependency injection model as an example, the basic idea of dependency injection is to implement a more flexible and scalable system architecture by changing the dependency between components. The Unity block provided by Microsoft is implemented based on this idea. This is a tool component provided for us to implement dependency injection.

For example, Asp. net membership implements role-based access control, Asp. net MVC framework implements the Model-View-controller separation principle, ADO. NET Entity Framework implements object-relation-mapping data access modes and so on. It is a development framework based on a series of practical modes. These frameworks, coupled with development tools, testing tools (nunit, xunit, and so on), provide a mature environment for the emergence of software factories.

Abundant Resources

As described in the above section, a large number of software development design patterns exist in the software factory in the form of tools, virtually providing developers with excellentArchitecture and design application modes.

Two developers, one skilled in using ASP. net mvc framework to build Web ApplicationsProgramThe other one is skilled in creating web applications based on the MVC model. In fact, you cannot determine whether they use their respective strengths to create the final product design.

Practical reference and documentation, Quick Start GuideIt can solve common technical problems in the development process.

Design and Code GeneratorUsed to control the code and application system hierarchy.

TemplateContains a large amount of reusable code.

Standardized development activities

In the software factory, we operate a series of templates to complete the existing functions in the current step to create an application. For every developer, the degree of freedom of development activities will be greatly reduced, but for the entire development process, collaboration and division of labor are more clear and controllable. See the process of creating a multi-layer Web Application in Web client software factory:

 

 

Highly divided

Because the software factory standardizes development activities, we can give the development team a clearer division of labor. For example, a senior engineer can operate the designer to generate the basic code while breaking down the function. Another engineer is responsible for writing the implementation code in the generated file using the development tool. Because these different tools are integrated in the software factory to serve solution files, rather than interacting with documents, Visio graphics, or UML as in previous projects.

Challenges brought by the software factory

Software factories and agile development do not have the problem of superior or inferior performance. The industrial production has brought about higher requirements for management and technology classification. For the factory itself, continuous improvement and thinking are also required. The ultimate goal is only one: the final product achieves the perfect unity of efficiency and quality, and achieves higher output value for the development team.