PUBLISHING SYSTEM
PUBLISHING SYSTEM
represents the different diagrams that appear in the book regardless of format; a figure is a table,
diagram, picture, or chart. The Section class contains a figureReference attribute in addition to
other identifying factors that may be linked directly to a diagram in an eBook or PDF, or a
specially formatted reference (bold or colored) in printed books. Nearly all of the objects in the
system have a revisionDate as an attribute to help track the latest version of the books elements.
The domain class diagram appears below with associations and multiplicity.
Domain Class Diagram
PUBLISHING SYSTEM
is to store the objects directly in the database using BLOB types. The data type CLOB may also
be used to store large text-based objects if they exceed the 4k limit of varchar2. The second
approach is to implement a file server and use XML objects in the database that reference the
storage location of a particular object required. XML reference objects could be useful for
objects that exceed 2 GB such as a completed book object and the other media types. The table
below lists the data types needed.
Data Type
BLOB
XML
Varchar2
Date
Number
CLOB
Description
Binary Large Object 4 gigabyte block size up to 8 TB
A system-defined type for storing binary XML data
Variable length string maximum length 4000 bytes
Valid date range
For numbers including precision and scale
Character Large Object 4 gigabyte block size up to 8 TB
PUBLISHING SYSTEM
employees will be accessing content remotely. Remote connections by any employ require SSL
via Secure Hypertext Transport Protocol (HTTPS). The company will need to register a digital
certificate with a certifying authority for the purposes of data encryption between the internal
system and outside connections by independent contractors. Finally, the massive amount of
digital data stored in the database mandates a strong redundancy, backup, and recovery plan.
Group Contributions
Three members of group A contributed to the assignment for this weeks class, (1) Ervin
Windham, (2) Lee Wendel, and (3) Aaron Hall. I provided the initial post for the group outlining
work for the week. I also created two versions of the Domain Class Diagram, one preliminary
rough diagram and the final diagram for the group. Included in the creation of the diagram was
multiple posts to discuss classes, attributes, and how to store the data in the database. Lee posted
the first response to the questions for the group. Lees suggestion of a Media superclass became
part of the final diagram as well as his thoughts about treating each portion of the book as its
own class. Lee also suggested the use of the XML data type to help manage the content and the
use of a file server for larger objects. He also outlined the primary controls needed for integrity
and security which became the core of the final plan. Ervin provided feedback and suggestions
at every step of the process for classes and the creation of the diagram. Both Lee and Ervin
provided integral support for all aspects of the project this week.
PUBLISHING SYSTEM
References
Satzinger, J., Jackson, R., & Burd, S. (2012). Systems analysis and design in a changing world
(6th ed.). Boston, MA: Course Technology, Cengage Learning.
SS64.com. (2014). Oracle Datatypes. Retrieved from http://ss64.com/ora/syntax-datatypes.html.