Should each software enterprise have its own development platform?

I have been busy with enterprise development platform-related matters for some time, so I want to discuss with you whether an enterprise needs to have its own development platform;

We act. NET programmers basically develop some business information systems. They all have many application systems in an application industry. Therefore, I have thought about developing a system development platform that can be used by the company;

In fact, I think this is necessary. I 'd like to give you some ideas about my opinion. [Wang qingpei is copyrighted. Please give a signature for reprinting.]

The company is engaged in the development of information systems in the pharmaceutical industry. Some big business models are basically fixed and rarely changed. Therefore, I want to abstract the main business logic for encapsulation; in addition, our company's staff flow is fast, and it is difficult for new employees to get started with business development. Therefore, the company often organizes training for new employees, but the effect is not obvious; the company's business system processes all the drug transaction data across the country, so the data is very important and there is no small error; but there are still program errors due to unfamiliar business logic;

I think this has also happened in other companies, so is the company willing to invest in developing such a framework at a certain cost? The general implementation idea is this, and there may be deficiencies;

1: find an old employee or a person with familiar business logic to extract the business logic and abstract the core business framework. This framework is crucial. Whenever business needs change, the code here can only be modified by people who are familiar with it, which can prevent major errors caused by changes of people who are not familiar with the business;

2: Re-split the current company's systems, that is, re-layered. Try to use plug-in-type development methods for development, and strictly differentiate the functional points for development, high cohesion, and low coupling call conventions; in this way, we can easily change the system when there are functional changes rather than business changes. If you are interested, please refer to your ".. NET briefly introduces the component system development model;

3: Try to abstract the UI Layer as much as possible. The advantage is that new employees who just graduated have something to do. When they are not familiar with business functions, they can gradually familiarize themselves with the general interface process to get familiar with the system;

The above are some of my general ideas. But such a system is either big or small. It depends on the company's business. If the company is a large enterprise, the investment may be relatively high, but in the long term, it is still necessary to develop a project. We will calculate an account, which is calculated from the company's perspective, it may be unfair to new employees;

From the company's perspective, if such a platform can be successfully developed, it will reduce the company's investment in technical training for new employees, new employees do not need to carry out complex technical training. They only need to conduct business training for new employees, which saves a lot of energy to study their business. This is what the company thinks; as long as the company's core business code is focused on some senior programmers, System Architects, or the company's core technical team, I think this company can save a lot of energy; when a company deletes data, it is unfamiliar with the business logic, causing serious consequences. Such a loss is very huge, therefore, I think that enterprises with business-dominated and core businesses can consider developing such a platform. [Wang qingpei is copyrighted. Please give a signature for reprinting.]

This article is from the pattern driven the world blog, please be sure to keep this source http://wangqingpei557.blog.51cto.com/1009349/602639