Big Chemical Encyclopedia

Chemical substances, components, reactions, process design ...

Articles Figures Tables About

Logic business

Zhang, T.Y. (2006) Process Chemistry The Science, Business, Logic, and Logistics. Chemical Reviews, 106,2583-2595. [Pg.189]

Application architecture The major components, how they partition the business logic, and how they interact, defined primarily with collaborations and types. [Pg.234]

Server components typically implement significant business functions and mn on a server. In a multitier architecture, most business logic in an application runs on dedicated servers... [Pg.423]

In practice, it is useful to distinguish the application architecture—how the business logic is split across components and how they interact—from the technical architecture all the infrastructure and other domain-independent pieces that support that collaboration. The four-tier Web-enabled architecture presents a typical case for making this distinction. [Pg.505]

Use a three-tier client-server architecture. All business logic must be in the middle tier, presentation and dialog on the client, and data services on the server. In this way you can scale the application server processing independently of persistent storage. [Pg.506]

Use Model-View-Controller with an explicit ApplicationModel object to connect any UI to the business logic and objects. [Pg.506]

Logical Components, connectors How business logic is logically partitioned in software how parts collaborate... [Pg.508]

The application architecture A package structure and collaborations. This implements the business logic itself as a collection of collaborating components, with the original specification types now split across different components. The components can range from custom-built to common off-the shelf components, such as spreadsheets, calendars, and contact managers, to purchased domain-specific components such as factory-floor schedulers. This application architecture lives atop, and uses, the technical architecture. [Pg.542]

Pattern 16.7, Implement Technical Architecture Define major technical components of your design as an architectural collaboration. These components might be GUI, business logic, persistence (database or file system), communications, and other middleware elements. [Pg.553]

Note that the model represents the state of the whole system from its external users point of view — not just the business logic, and not just the software hardware may be included too. So if a display shows the result of some calculation, and that display is part of the boundary the system, then that value can be an attribute in the model, even if the software forgets it immediately after sending it to the display. It s the system context model that sets this boundary. [Pg.619]

Separate the GUI (and other layers that interface externally) from the core business logic. [Pg.663]

The GUI involves more than one class—usually several classes for every kind of shape and display and every displayed business object. So we are talking here about another substantial component. Considerations that apply to the user interface also apply to interfaces to other external objects, so an interface to a separate component would also use a fagade. Once these fagades have been separated out, we are left with a core component in the middle that reflects the business types and represents the business logic in its code. [Pg.663]

Each of the components has its own model of objects it is interested in. They include static types and reified actions (use cases). Examples are an object controlling the interaction with a user or, in the business logic, a long-term action such as loan. [Pg.663]

Integration of disparate systems involves a lot of infrastructure support communication, coordinating distributed transactions, load distribution, and shared resource management. The costs of developing infrastructure components of high quality would dominate a typical large business project compared with that of the actual business logic involved. [Pg.667]

As a market saturation point is approached, limiting growth, a company may enter a third phase, in which the company searches for new but related bundles of products and services to serve as the basis for the next round of growth. Consider The Home Depot as an example. The Home Depot s first business logic was evidenced in its well-known... [Pg.278]

We have described our growth model, presented in Figure 14.1, in a linear fashion, suggesting that the development of the business logic... [Pg.280]


See other pages where Logic business is mentioned: [Pg.750]    [Pg.376]    [Pg.424]    [Pg.433]    [Pg.519]    [Pg.519]    [Pg.548]    [Pg.559]    [Pg.663]    [Pg.669]    [Pg.272]    [Pg.273]    [Pg.274]    [Pg.274]    [Pg.274]    [Pg.275]    [Pg.275]    [Pg.275]    [Pg.276]    [Pg.276]    [Pg.277]    [Pg.277]    [Pg.277]    [Pg.278]    [Pg.279]    [Pg.279]    [Pg.280]    [Pg.280]    [Pg.280]    [Pg.281]    [Pg.281]    [Pg.282]   
See also in sourсe #XX -- [ Pg.273 , Pg.275 , Pg.277 , Pg.278 ]

See also in sourсe #XX -- [ Pg.39 , Pg.41 , Pg.65 , Pg.132 ]




SEARCH



© 2024 chempedia.info