2.GNU DDD is the visual graphic front end of command line debugger, such as GDB, DBX, WDB, Radberg, JDB, XDB, Perl debugger or Python debugger. Its unique graphic data display function can graphically display the data structure. DDD originated from the VSL structured language written by Andreas Zeller at 1990. Later, with the efforts of some programmers, it evolved into what it is today. DDD is very powerful and can debug programs written in C\C, Ada, Fortran, Pascal, Modula-2 and Modula-3. You can browse the source code in hypertext mode; Ability to set breakpoints, backtrack debugging and edit history; Have the simulation window of the program running in the terminal and the ability to debug on the remote host; Graphical data display is one of the original intentions of creating a debugger, which can display the relationship between various data structures and display the data structures in a graphical form. Command line interface with GDB/DBX/XDB, including complete text editing, history and search engine.
3. "DDD" Author: Naisu きのこ (all 2 volumes)
Introduction:
The full name of "DDD" is "withdrawal from addiction", which roughly tells the story that a strange disease called "agitation" is spreading rapidly. Patients infected with this disease will not only be insane, but even their bodies will be deformed-also known as "demon possession." The place where the stone staff of the young man who lost his left arm is located, and the young man who has a dark special prosthesis and lies in a big bed with a bedstead cover all day, are wonderful stories around these two people. ...
Nai Su's novel, after The Realm of the Empty, was published in the third issue of Faust (March 2004). The focus of the magazine's new biography series planning is the integration of reality and unreality on the extension line. Cartography was done by こやまひろかず (Yamashita Hiroshi).
The theme of this book is the devil, so the religious view is based on the monotheistic view of the Christian system, but there are still many ideas that subvert common sense.
Four volumes are expected, and two volumes have been sold so far.
4. Limited daily dose
5.DDD (domain-driven design)
In 2004, Eric Evans, a famous modeling expert, published his most influential and famous book: Domain-Driven Design-Solving the Complexity of Software Core (Chinese translation: Tsinghua Publishing House in March 2006, or Domain-Driven Design Architecture [Evans DDD]). Nowadays, DDD development frameworks emerge one after another (such as RoR, RIFE, JdonFramework, etc.). ), and the software package structure of our project becomes like this: the concepts of xxx.modelxxx.service and DDD can be said to be everywhere. DDD tells us how to do a good job in the business layer! Domain modeling is an artistic technology, not a mathematical technology, and it is a solution to solve complex software and quickly respond to changes.
The production process of software is: analysis, design, programming, testing and deployment. In the past, the fields of analysis and software design were divided, and analysts collected basic concepts from the fields; The design must indicate a set of components that can be built by adaptive programming tools in the project. These components must be able to execute effectively in the target environment and solve the problems in the application correctly. Model-driven design abandons the practice of splitting analysis model and design, and uses a single model to meet these two requirements. This is a domain model. A single domain model satisfies both analysis prototype and software design. If a model is not practical to implement, then look for a new model. If the model does not faithfully express the key concepts of the domain, it must also find a new model. Modeling and design become an iterative cycle. Closely link domain model with design. Therefore, modeling experts must know how to design and program.
According to Eric's theory, the business layer will be subdivided into two levels: application layer and domain layer. Application layer: define what software can do, command domain objects with rich meanings to solve problems, and keep it simple; The state that does not include business rules or knowledge and has no business situation; Domain layer: the information and business rules that represent business concepts and business states are the core of business software. Each layer must be clearly separated, and each layer is cohesive and only depends on its lower layer.
Eric pointed out in particular that the quick UI method of handing over business logic to business interface is a detour. I hope that software development can be done by dragging graphics intuitively like C/S structure, which is a wrong direction, with fast development speed and difficult maintenance and expansion. Although J2EE technology is used, it is actually a pseudo multi-layer technology. It is recommended to buy a translation book "Domain-Driven Design" to learn.
In the life cycle of domain objects, there are three modes to maintain the integrity of objects: aggregation of clearly defined ownership and boundaries, making the model more compact and avoiding the interwoven object relationship network; Factory and assembly. At the beginning of the object life cycle, factories and combinations are used to provide methods to access and control model objects. Establishing an aggregation model and adding factories and combinations to the design can enable us to manage model objects systematically. Aggregation circles a range within which an object remains unchanged regardless of its life cycle.
MF (martin fowler) once put forward a famous anemia model or blood loss model. He thinks that there are only weak behavior setter and getter methods in the solid model objects, and there is no real behavior, such as ischemic people, which is not harmonious. Eric believes that in DDD, some concepts in the domain cannot be regarded as objects in the model. If these functional concepts are forcibly added to entity objects and value objects, the definition of objects in the model will be destroyed. All our DDD projects exist in the form of blood loss models, so Eric appeals that modeling experts must know how to realize and understand software technology.