Use cases

K. Sycara, "Using Case-Based Reasoning for Plan Adaptation and Repair," in Proceedings of the DARPA Workshop on Case-Based Reasoning, Morgan... 

Give time for understanding to be absorbed. Use case studies and current problems to get the message across. 

The wellbore, drill string and drilling fluid data from the previous example are used. Casing depth is 4,000 ft. Assuming a drill pipe length of 5,000 ft and a drill collar length of 500 ft, find the friction pressure losses. 

The applicability of such VS in combination with tools available include situations where portions of any molecule need replacement with bioisosteric fragments. In this regard, BROOD software [105] and MOE [222] provide automated tools for fragment removal, replacement, and minimization to relieve any strain in the molecular assembly step and provide a database of fragments(isosteres) that could be enhanced in custom fashion by an enterprise as well. These software allow facile FBVS in 3D. Since this software has become available within the last 2 years, there seem to be a dearth of use cases in the published literature. However, anecdotal reports indicate that these are being used regularly in industry and the Websites of these two vendors provide adequate information for the inquisitive reader. 

For the investigation of logistic questions or for the design of pipeless plants, like in the presented use-case, PPSiM offers a suitable solution. The comparison between the two plant concepts showed that the developed pipeless plant configuration leads to 20 % shorter processing times for similar investments, due to the higher utilization of the plant equipment. 

Case-based reasoning has earlier been used for instance for equipment design. Koiranen and Hurme (1997) have used case-based reasoning for fluid mixer design and for the selection of shell-and-tube heat exchangers. They have included an estimation of design quality for the case retrieval beside technical factors. 

For object-oriented design Clear, use case driven techniques for transforming from a business model to 00 code, with an interface-centric approach and high quality assurance. 

Catalysis has been central to the component-specification standards defined by Texas Instruments and Microsoft, the CBD-96 standards from Tl/Sterling, and services and products from Platinum Technology it has been adopted by several companies as their standard approach for UML-based development. It fits the needs of Java, JavaBeans, COM+, and CORBA development and supports the approach of RM-ODP. It also supports systematic development based on use cases. 

Abstract joint actions come from Disco [Kurki-Suonio90], the OBJ tradition [Goguen90], and database transactions as well as from the general notion of the Objec-tory use case. 

One is that there may be significant replication of information between the components in a distributed system, for both performance and reliability reasons. A component generally works with others (including people) to support a particular business-level action (or use case), an object generally represents a business concept. These two process-biased and object-biased views give rise to separate tiers in many designs. 

Chapter 4, Interaction Models Use Cases, Actions, and Collaborations, describes modeling of interactions among a group of objects. 

Actions can be joint (use cases) They abstract multiple interactions and specific protocols for information exchange, and describe the net effect on all participants and the summary of information exchanged. 

At the business level, it takes a sequence of interactions between client and seminar company, including enquire, schedule, deliver, follow-up, and pay, to together constitute an abstract purchaseCourse action. This sequence has a net effect on both client and seminar company not only has the seminar company delivered a service and gained some revenue, but also the client has paid some fees and gained knowledge. In software, it may take a sequence of low-level operations via the user interfaces (UIs) of multiple applications and databases to complete a scheduleCourse operation. Such a joint action, also called a use case, is the subject of Chapter 4. 

Use cases, actions, and collaborations abstract the interactions among a group of objects above the level of an individual OOP message send. These interaction models let you separate abstract multiparty behaviors, joint or localized responsibilities, and actual interfaces and interaction protocols. 

Section 4.1 provides an overview of the design of object collaborations. Section 4.2 begins with examples of object interactions to show that many variations in interaction protocols achieve the same net effect and so motivate the need for abstract actions. Section 4.3 introduces use cases and relates them to actions and refinement. Section 4.4 explains how actions and effects are related to abstract actions. Section 4.5 describes concurrency between actions and explains how to specify these constraints. 

In a joint action, some of the parameters may be distinguished as participants and drawn linked to the use case pictorially, whereas other parameters are written in text style. For example, in Figure 4.5, buyer and vendor are participants, whereas item is a parameter. In business analysis, the difference is a matter of convenience and is analogous to the equivalence of the associations and attributes of object types. In a software design, the participants can be used to represent objects that we know will definitely exist in the final code and that will, between them, take responsibility for executing the action. The list of parameters, on the other hand, represents information transferred between them whose implementation is yet to be determined. 

Our use case template permits these additional distinctions to be made ... 

The analysis idea of a use case is a joint action specification at the business or user level. When describing a use case, you may prefer a diagram view without the type mod-... 

It is also useful to document informally the performance requirements of a use case. Such requirements include whether it is considered a primary or secondary use case (alternatively, priority levels), the frequency with which it is expected to take place, and its concurrency with other use cases. 

---