Work on this case study was motivated by an anticipated need of travel agencies to improve their sales by making their products, namely, tours, directly accessible to their client base. Although this application focuses on travel agencies, it could be viewed as one instantiation of a general application framework that handles reservations in general, such as hotel and car reservations.

A software for a travel agency provides reservation facilities for the people who wish to travel on tours by accessing a built-in network at the agency bureau. The application software keeps information on tours. Users can access the system to make a reservation on a tour and to view information about the tours available without having to go through the trouble of asking the employees at the agency. The third option is to cancel a reservation that he/she made. […]

The following is a collection of user requirements, each of which describes the required behavior of a system. Except where otherwise specified for each of the requirements, apply the bridge process to reach a full-fledged design in terms of a use case model, object model, and subsystem model. Apply traceability at all stages.

This part introduces two case studies taken from two different problem domains. The first case study has an internet-based architecture and is an interesting model to apply to applications that deal with reservations; the second deals with web development. This application has a network-based architecture and could also be used as a model to develop similar applications. The bridge process is applied in detail including details of traceability. Both could be viewed as tutorials on applying the bridge process and could be used as such to guide the reader in solving the exercises at the end of the chapters in Part III.

This application focuses on automating the operations of a goods distribution company. The summary of user requirements is appended with all data that may be needed by such applications. Almost all details required by the application are collected from the beginning. The detailed requirements give a useful sample that can be adopted in building similar applications. The activity diagrams depict conditionals and repetitions. Also, the detailed object model is rich with attribute names and associations. The exercises at the end of the chapter lead the user in carrying traceability and other activities that were dropped from this case study.

DVC is a software solution for a given company. This company is a reseller of goods. It obtains its products from a vendor, and resells them to a customer. The basic need of the company is a database to store specific informationconcerning the various vendors, customers, and warehouse,s as well as a product database. In order to make the lives of the employees easier, the software features an easy-to-use interface for the database, which includes interactive forms and graphics. Using the information in the database, the user can access the information in several easy ways, such as browsing and searching.

This case study is about simulating a mechanical robot arm. The design model is obtained as a consequence of applying the bridge process. Similar applications on simulation could be designed in a similar fashion. The user requirements are complemented up front by a glossary of terms, each of which denotes a component of the robot arm, the target of the simulation. In addition a picture is displayed to further clarify the concept. Note that the use case model is simple. It focuses on three activities; two of which, help and test, could be generalized to any application. The third focuses on the core activity of the application. In this sense the initial use case model is a good start to design and later build the application. The scenarios include describing help and test facilities that the application offer. The object model expresses aggregation and inheritance relations, showing how commonalties could be factored out to reach more concise models.

The chapter leaves out the details of derivation to give to the reader the opportunity to apply the bridge process and check the results against the models that are presented. The exercises at the end of the chapter guide the reader in this direction

This part introduces modeling artifacts that are used to express architectures in terms of uses cases and objects. The second chapter introduces the bridge process.