"The system development model should not be a product or a tool, but it should be a working mode and a variety of tools used in this working mode.
table of Contents
1 System Parts (1) Definition (2) Feature A One System Pack may be a set of code, a set of applications or a set of text templates B package a class of framework, a class of solutions or a class Design Ideas 2 System Parts Development Mode (1) What is Systems Development Mode (2) System Parts Development Mode should be a working mode (3) There are many tools based on this model to be available in these tools. There are also many specific implementations of this model.
text
1 System Parts (1) definition is a special system that has been done, saying it is special because such system templates do not have any specific data characteristics, no personalized information, but have fixed System structure and layout. When we use these system templates as system implementation, we only need to give it specific attribute values, such as specific database information, specific display information, etc. More intuitive, in fact, a system template is similar to a class, a component, and control, but it is the system level, has risen to the system height (2) Features A. A system piece may be a set of code, a set of applications Or a set of text template B A system package encapsulated a class of framework, a class of solutions or a type of design idea 2 Systems development mode (1) What is the system development mode system building model refers to the system around the system This core, a software development process proposed according to the idea of software engineering
The rough ideas are: starting from the demand analysis results, designing what kind of system parts are selected around the system, what kind of database, what kind of database, how to design the database to configure system parts, etc. According to the results of the system design, select the integrated tool based on system-based development mode to complete the system's implementation to obtain the final system!
Compared with the general software development process, the most important difference is that it is based on system components as the main considerations in design, and it is achieved in the integration tool for system parts development mode! According to the selected system parts development mode category, it may involve code, or it may not involve code at all!
(2) The system development model should be a working mode like many software engineers using three-story structural model or distributed architecture model, and component development model thinking is the same. The system development model should develop into a software. Engineers will consider, choose a product construction method, process!
(3) There are many tools that are developing based on this model for use, in these tools, there are many specific implementations of this model.
Just as the current PB, VC / VB, Delphi / C Builder / Kylix, J2EE / EJB and other tools will be integrated into the idea of component / control / component development model, and there will be many integration of systematic development model ideas. Tool of. Just as these tools are different from the implementation methods of the component / control / component development model, the specific implementation methods of system parts development models that integrate system parts development model ideas are also different. But in general, there are two categories: code reuse, binary / text template reuse (system level reuse). Most of everyone's thinking is concentrated on this level of code reuse. In the case of my personal opinion, there may be relationships with the following reasons: 1) Now rapidly developing object-oriented methods, due to the rapid development of object-oriented methods, make it reuse Sexual issues have received a full understanding - because one of the object-oriented core ideas is multiplexed. Because the benefits of multiplexing are so obvious, it also promotes the extreme expansion of object-oriented methods in people's minds. Object-Oriented Methods Now, the most used is mainly in OOP (truly OOA, OOD to make Case is still relatively pleasant), and therefore, when you mention multiplexing problems, you will think of code. Reuse! 2) The current software development is still in the development of language level, studying machine language, assembly, intermediate language, advanced language, business language, non-language development route, our time It is the relatively small, compilation, and business language, the machine language, the non-language is almost unused, both large, two small. Machine language, compilation is almost unused, that is because of thinking, horizontal development It has surpassed this level. And the business language is used, because thinking although this level, the level has not been generally reached this level; the non-language is almost unused, because people's thinking is very small, some people reach this level, Of course, it is not necessary to say levels. Therefore, when people talk about software development, they generally think of the language, code! Here, there is someone mentioning the first six-generation language, I think this will Law and I am not speaking here! According to the Division of Ng (NG N), the business language belongs to the 5th generation, and now is in the period of the third, 4th generation language. I understand The non-language should be a system-level design language, such as business process design, modeling, etc. Actually, the code has been hung up! Because of the above reason, everyone is talking about reuse. Almost all of the code hierarchy!
Of course, from the general thinking mode, this is extremely normal and natural, and as a class of implementation of the system development model, this is also possible. So, in the previous system-developing model, There is a very constructive idea. Typical such as sixth generation languages, etc. also have many ways to think from now on mature products or ideas, such as general programming methods (GP), STL, generic programming, design mode, MFC And in-depth architecture based on these ideas or products such as three-layer (appearance, logic, data), distributed, etc., I can surely say that people think about people based on these profound technologies. If the method is properly, the route is correct, it will definitely make a beautiful tool-based development model, believe in the near future, such a tool will generally be generally generally based on object-oriented development tools! Although there is now The many of the time, efficiency, quality, etc. have questioned, but that is only some of the small episodes on the road, while paying attention, it should not be an insurmountable obstacle. Of course, it is like a road to Kangzhuang Avenue. How to make the system development model becomes a part of the tool that can improve the tools that can improve the efficiency, there are different implementation methods, that is, the binary reuse I said. Binary heavy use this title, More specifically, it should be called system-level reuse. The second-binary heavy use is only to distinguish from the narrow and code reuse, but in more scientific statements, the system is reused more appropriate. Because this type of reuse is not Limited to binary reuse, more importantly, it is not limited to the reuse of the program. The system-level reuse said it is not limited to binary reuse, because in addition to the reuse of the application, it can be reused on the text. A typical Windows application can be designed to be systematic and then used, however, a typical web template (just text) can also be designed to be used for system components. System-level reuse is more important, it should be design ideas, The solution, the experience level, only at these levels, can we say that our reuse is in the system level, has a typical feature of the system development model! Of course, you will definitely think about the code reuse immediately A lot of these ideas, such as design mode! This doubts just reflect the most significant difference between code reuse and system-level reuse: After the code reuse, you must rely on the compiler or interpreter to generate the final application system, and System-level reuse does not depend on any compiler or interpreter, you can directly get the final system! So it is more suitable for system-level reuse! Say system-level reuse to implement system parts development mode, code that you are familiar with you Compared to reusing, it feels a bit unfamiliar. This is as mentioned earlier, now is in the stage of object-oriented development, and now the software development level is in the linguistic period, so when it comes to reuse, it will be from the code Level to think. In fact, the code is reused is only a small instance of reuse. In any industry, anywhere, reusing is happening. Typical, the production process in the manufacturing industry is an excellent reuse - The production process of the product is reused to generate different specifications of products. I have to say that because of the particularity of the software industry, reused in software production is the most prominent - even makes reuse in other industries look Not reused! However, for the software development, when such a very good advantage is only used in the code level, then it is a bit unfortunate. Why can't we expand to other places? Can't let it get more What about the floor? The answer is: Yes! There is therefore a classic reuse of design mode. It is not only reused on the code level, but also reused in design ideas! So why not expand to system level reuse? Answer? Answer Yes: Yes! Therefore, system-level system-based system-based system development model is also possible! Say this, I remember the problem of non-language - sixth generation language. When defining the system development mode, if you want From the code reuse, you can learn from the definition of the object - of course, this is a specific implementation problem! Sarre to say so much, in fact, it is to clear some of the problems in system development model, and finally summed up Let's, or this: "Systems development mode should not be a product or a tool, but it should be a work mode and a variety of tools used in this mode of work." Professional website: Http://systemer.51.net Source: http://systemer.51.net/systemerpattern.htm Posted: http://systemer.51.net/cgi-bin/forums.cgi? Forum = 2
