create a UML case-diagram

iPublisher is a partnership of publishers that publishes books on wide-ranging topics. iPublisher has its head office in London Ontario and has branch offices in Toronto, Ottawa, Vancouver and Montreal. Each branch office is equipped with a few computers. Each of these branch offices functions as an independent publishing unit where the entire publishing process is handled by a team of 15 people. A publishing unit is comprised of a manager, a publisher, senior editors, and typographers. In addition, each publishing unit corresponds with the authors in its respective region and maintains records of all the contracts, the authors, and the titles written by the authors in a relational database server. The unit also maintains a record of the revenues generated from the sales of the books and the individual book profit margins. The database servers maintained at each publishing unit are synchronized with the publishing server located at the branch offices and the head office. To facilitate and centralize the management of the publishing units, iPublisher is headed by a president who is aided by managers. The top management located at the head office performs semi-annual as well as annual reviews of the business conducted at each publishing unit. iPublisher has recently formed an alliance with other publishers. As a result, many new branch offices have been opened recently. For instance, a branch office has been opened in Waterloo. These new branch offices have very few computers. In addition, to provide users information about the books published by iPublisher, Web site has been created to provide the required information over the Internet. Users can access this information by registering with the company's Web site. Imagine that you are a team member in a project to develop an integrated software system that automates all business processes for iPublisher mentioned above. In the requirements analysis phase, the team interviewed the publishers of the various branch offices and the officials at the head office. From its discussions and analysis, the team identified that: 1. Each branch office needs to maintain and update data related to publishers, authors, discounts, sales, and titles. 2. From time to time, the local management needs to generate reports based on current data. Some of the reports generated include publications per business year, titles published so far in the current quarter, and titles written by each author. 3. In addition, only the publisher views the report. This implied that the report need not be shared with the remaining employees at the branch office. 4. The results of these reports need not be published in the Web site of iPublisher. 5. The modification of author details is the most frequently performed task. As a result, this functionality needs to be created and rolled out on a priority basis. 6. Each publisher unit would like to maintain record of the revenues that can be generated from the sales of the books and the defined profit margin for each book. 7. The newly added branch offices have a few machines that cannot run standalone applications due to software and hardware inadequacy. Therefore, there is a need for these branches to manage their business processes using Web-based application that is directly connected to their web server. 8. iPublishers also wants to share the generated reports across branch offices and the head office. However, these reports cannot be put on the Internet because they contain sensitive information. As an alternative, it was decided that these data can be read from a remote JSON file and display the reports. 9. The top management at iPublisher performs semiannual as well as annual reviews of the business conducted at each branch office. Apart from the profits generated by each branch office, the management reviews the titles published and the sales per title. 10. iPublisher have a Web site that provides information about books published by the company. To access the information, a user has to register with the company's Web site