Breaking traditional software development ideas, build new application software

xiaoxiao2021-03-06  119

Breaking traditional software development ideas, build new application software

- Learn OO from the perspective of easy to learn

Heavy rainpoint August 16, 2004

reader:

This article applies to executable application developers having a year of working age.

If you do MIS, you don't have to read this article, because this article introduces the content, basically you have done it!

statement:

Often in the Internet, I have learned a lot of knowledge. The network is a very good platform for us to learn, and I have a very good platform to learn. I always learn someone else's things, how much is a little guilty, so I have written a few words in my scalp today. Let everyone laugh. The content involved in this article is purely personal view, and it may be ugly in front of those high people, but I am very confident to improve my design capabilities, so I can accept everyone's valuable advice. I will always do the strong point of the article than those who don't write :)

Preface:

Software Development This industry has been a long period of time, but compared with traditional industries, the software industry is also a baby, in the rapid growth period; at the same time, software is a human-oriented industry, our products are our thoughts, this One point and traditional industries are very different, so our ideas are directly related to the birth, growth, mature, aging until the whole life cycle of death, but more important phases is the system design phase before the birth of the software, due to The influence of each person's character, education, experience, we will also have a lot difference on the idea of ​​designing software. This article recommends a general development idea to provide you with the healthy growth of software developed. basis.

text:

When we developed software before, we are usually new standard form-> drag and drop controls -> Writing code -> Beautify interface -> Test release, especially in most people in 2000, of course, including me, if If you don't include you, you may get in touch with Oo than I have long! There is also a possibility that you are sitting in the desk, write homework, writing a book, haha; but after later, after the system enters the maintenance stage, the problem brought by this development is exposed one by one, 1. Maintenance difficulties, modify one BUG, causing the possibility of new bugs; 2. Since the peers are frequent, it is often difficult to maintain the program, the code is not easy to read; 3. Sometimes the customer proposes, modify the contents of a label on the interface, etc. The way to make a small revision requires recompilation; so how to solve such problems? "Listen" I will come slowly!

In recent years, UML has been popular in China. Most companies have improved the situation I have encountered above, but I found that companies that truly play OO thinking is not a lot, this reason is much, for example, 1. The company's designer is very thoroughly understood by OO thinking, but the company must not invest in the development of software libraries that have not yet customers have, and designers only understand half of OO. The company is designed by the design person. At this time, although the company's products have a certain degree of progress, the advancement of OO thinking cannot be fully played.

Because OO thinking is relatively large, it is not the focus of this article, this article is not explained in detail. Here we only introduce knowledge of OO packages on the interface from a practical perspective;

System requirements: Due to the characteristics of software interface layers directly and user interaction, the change is also very frequent. Now the user proposes interface content (ie, the user can pass the computer screen) can be modified, customized, or even added, deleted (of course It is within a certain condition);

Systematic analysis: First we analyze what users can see on the screen? For applications, all controls consisting of one by one window, a number of controls placed on the window: edit box, buttons, radio, check, list box, tree structure, table, etc., especially table The content is most complicated; to achieve user customization of the above content, the above information must be saved to achieve custom function; so we divide it into three categories: 1, window; 2, normal control; 3, complex control; The control is divided into 1, tree control; 2, table control; 3, reserved expansion interface;

System implementation:

There are several types of data, 1, saved to the server database (slow access speed, add additional network traffic, but the program is simple); 2. Save to the server database (can be combined with hard disk buffer), read when the program starts In-memory (fast access, but occupying a large amount of memory, program is relatively troubles); 3. Save to local library files (access speed, no additional memory, program writing relatively trouble); here, due to each interface every interface These data need to be accessed, so use local data files are relatively reasonably, save memory, speed medium, although it is a bit reduced system efficiency, but because each interface is displayed in the case of manual operation, the automatic system The compared number of times is much less, so the reduced system efficiency user is able to bear, but when there is a problem, if the data modified in the client A is updated to the client B, this is. . . Or give you a chance to think, haha. OK, the data storage method is determined, let's consider the software structure implementation, we use the object-oriented design point of view, to derive our own, and the user can modify the class content (excluding interface control) class BASFORM, which class Provide the user to customize the window style, including: size, title, style, etc .; read from the data file type when the window is created, the interface is displayed to the user to set the window content to the user, in user modification After the interface content is saved to the data file, OK, one can be out of the basic class that can be customized by the user end user; Similarly, we are derived from BASFORM to provide user custom interface standard control, commonly used, such as tags , Buttons, etc., after derived BASFORMControlSupper, provide customization functions for complex interface controls, including tree controls, table controls, etc., provide addition, modification, deletion of tree controls; provide column headings for table controls, column Display, display format, etc .; this is the most basic class library to establish success; the following can be expanded according to our needs.

For example, the user needs to add a button on the interface. Of course, this is relatively simple, the problem is to add this button to dry? Of course, there must be an execution code support, so we need to expand a code resolution, which is to let the end user can write a statement like us. Of course, if this job is made, the user is definitely unwilling, because this requirement for users Too high, so this work should be handed over to our technical support, don't say that technical support will not be! And we haven't provided print support, don't forget, the print function is the most common; so we can also derive the print function at the end;

At the end: This article is just a brick, according to the actual needs of the reader, can explore the design idea more depth, apply to your development, improve. . . . . .

About the Author:

The year "Shimen" graduated from the year of Macao returned. . . . . .

Zhongguancun entered the day of the trough to Beijing. . . . . .

It is still always working with the teachers and sisters. . . . . .

Depressed. . . . . .

Proficiency in Delphi, CBuilder, JBuilder, VC6 kernel telecommunications industry development

Email: hryyx@163.com

-------------------------------------------------- - Full text -------------------------------------------- ------------

转载请注明原文地址:https://www.9cbs.com/read-126273.html

New Post(0)