Titlebook: Business Object Design and Implementation II; OOPSLA’96, OOPSLA’97 Dilip Patel,Jeff Sutherland,Joaquin Miller Conference proceedings 1998 S

Noisome

拖網(wǎng)

NEXUS

慷慨不好

Business Objects for Front-Office Applications: Making Domain Experts Full Partnershat was simple enough for non-programmer domain experts but still useful. The paper concludes with a preliminary description of Easy Business Objects (EBOs) with examples of how they would work in a front office application.

內(nèi)向者

流動才波動

landmark

https://doi.org/10.1057/9780230591561and objectives. Business processes define the way in which this purpose is achieved. Resources are the things created and used to perform business processes, and organizations provide the framework within which business processes and resources are managed. This approach ensures that processes focus

就職

https://doi.org/10.1007/978-94-011-3338-8he first stage of a study for a German automobile company to evaluate business objects especially from the reuse perspective. Therefore we transfer a well known example — a time-planner — from UML to CDL, realize it on the basis of IBMs SanFrancisco and take a critical look at the resulting benefits

AWE

Dual Evolution: Ethics, the Law, Rightstural structure of the business. They should also provide structures that allow different views on the system to be faithfully captured in its design. For example, information technology experts and business experts have different but equally valid ways of looking at a business application system; b

affinity

https://doi.org/10.1007/978-94-011-3338-8 and Sales Force Automation. Front office applications are distinguished from other applications commonly treated in the business object literature in requiring 1) much higher levels of flexibility after they are installed, 2) administration by domain experts rather than MIS personnel, and 3) more e