System Analysis Example Essay

1984 Words 8 Pages
University of Tartu

ePublishing Information System

Group: | | | | | | Instructor: | |


Table of Contents 1. Overview 4 Advantages of ePublishing system 4 Which problem needs to be solved? 4 Where is the problem? 4 Whose problem is it? 4 Why does it need solving? 5 How does the problem manifest itself? 5 When does it need solving? 5 What might prevent us solving it? 5 2. Strategic dependency model 6 3. Strategic rationale model 6 4. Use cases diagram 7 5. Use cases 8 6. Class diagram 10 7. Sequence diagrams 11 8. State diagram 13 9. Security analysis 14 9.1. Context and assets identification 14 9.2. Determination of security objectives 14 9.3. Risk analysis and
…show more content…
When books are not reviewed on devices it might happen just so that they might not look and feel as expected.
When does it need solving?
UI and inner logic development can be started on Friday 19. november 2010. Working previewing application should be ready on 28. february 2011.
What might prevent us solving it?
Delays with the development of network API-s that provides necessary services and data to the editor application.

2. Strategic dependency model
This strategic dependency model gives an overview of the dependencies of the ePublishing system in general. In this context ePublishing system consists of software for preparing the book for publishing (editor, converter) , web services and media server.

Figure 1. Strategic dependency model.
3. Strategic rationale model
Strategic rationale model gives also an overview of ePublishing system. In this case author’s goal is to prepare books for publishing, so that clients could buy them. In order to achieve it, author can use different parts of ePublishing system: software, web services and servers. When book is finished and formatted into ePu format, the book is forwarded to vendors, which offer this book to clients.

Figure 2. Strategic rationale model.

4. Use cases diagram
This diagram shows all the actors of the ePublishing system. This document concentrates on the Author’s “Preview a book” usecase.

Figure 3. Use case diagram.

5. Use cases

Related Documents