Running head: LAB II – JOURNALHUB PROTOTYPE PRODUCT SPECIFICATION
Lab II – JournalHub
Prototype Product Specification
Adam Lawson
Purple Team
Old Dominion University
CS411
Janet Brunelle
April 15, 2016
Version 1
1
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
Table of Contents
1 Introduction…………………………………………………………………………………3
1.1
Purpose………………………………………………………………………..3
1.2
Scope………………………………………………………………………….4
1.3
Definitions, Acronyms, and Abbreviations…………………………………...6
1.4
References…………………………………………………………………….7
1.5
Overview……………………………………………………………………...7
2 General Description…………………………………………………………………………7
2.1
Prototype Architecture Description…………………………………………...8
2.2
Prototype Functional Description……………………………………………..9
2.3
External Interfaces………………………………………………………….....9
Figures and Tables
Figure 1………………………………………………………………………………………..8
2
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
3
1 Introduction
As people go about their lives, they rely on media in all its forms to stay abreast of
current events and topics of interest. In particular, newspaper organizations provide critical,
time-sensitive content to readers both online and in print. To carry out this mission, these
organizations, such as the Virginian Pilot, rely on their reporters to find relevant information and
compile it into useful, comprehensive stories within tight deadlines. Unfortunately, the current
systems for managing existing and upcoming content are inadequate, potentially requiring the
staff to sift through obnoxious amounts of irrelevant data. Worse, the information is rarely in the
same location and is often spread amongst disparate management systems.
Without a centralized, coordinating tool to store, review, and retrieve relevant stories and
information, the process as it stands is wasteful in both time and energy. Most organizations
acknowledge that proper management of resources is important for maximizing their potential
(Semore, 2014). Despite this, over 35% of businesses lack a central project information
repository, costing additional time and money (Burger, 2014). The solution for many
organizations is a normal Content Management System, or CMS. The solution for news
organizations is JournalHub.
1.1 Purpose
With more and more people now seeking fast, responsive information about current
events and topics online, the pace of reporting has increased. To keep up with the demands of the
modern consumer, news organizations must publish timely, correct new stories as they break. In
order to help meet these needs of the modern newsroom, a more effective interface for content
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
4
must be available. JournalHub will fulfill this requirement and ease the creation of new content
while allowing staff to stay fully informed.
News organizations need an intuitive, and comprehensive tool for their work. One from
which accessing and searching old stories or checking to see what stories are active and where is
just a few clicks away, whether via a computer or mobile device. JournalHub will meet this
specification and more, providing a centralized, all-in-one interface for stories old and new,
complete with tracking information and notifications.
1.2 Scope
JournalHub will be a user-friendly interface between newsroom staff and the database on
which the content will be stored. Since it is being purposed solely for the use of journalistic
news organizations, JournalHub will eliminate unnecessary clutter and provide quick easy access
to critical components like searches, calendars, and upcoming events. A user will be able to log
in and immediately begin work, whether they need to retrieve an archived story, create a new
one, or check on an active story’s progress. Authorization will be managed by one-or-more
administrators who may grant new users access and customized group-based roles. Modifiable
notifications can be set for important events or dates, which can be sent either via email or popup message. Additionally, a budgeting system will be implemented to allow staff to modify the
appearance and layout of stories for publication.
With distinct tabs for functions such as tasks, documents, a calendar, and more, users of
JournalHub will always know where to begin, no matter the immediate goal. By minimizing the
number of tabs and making all of them available from a single page, JournalHub will be
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
responsive to the rapidly changing needs of staff members working in the modern news
enterprise.
5
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
6
1.3 Definitions, Acronyms, and Abbreviations
Content Management System (CMS): Software that implements publishing, editing and
modifying functions for various types of content
Database: A structured set of data stored by a computer that can be accessed from another
machine
MySQL: An open-source database management system
PHP: An open-source scripting language commonly used for web development, since it may be
embedded in HTML
Feng Office: A free, open-source project management tool
ODU: Old Dominion University
Budgeting: In journalism, determining the placement and size allotment for stories and articles
within a publication
Slug: In journalism, a unique identifier for a story. It is used to clearly identify a story and is
likely to contain a keyword or words. Often includes a reference to the author’s name or initials
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
7
1.4 References
Burger, R. (2014, July 7). 14 Surprising Project Management Statistics. Retrieved October 21,
2015, from http://blog.capterra.com/surprising-project-management-statistics
Puscasu, A. (2015, April 26). Project Management Statistics. Retrieved October 21, 2015, from
http://apepm.co.uk/project-management-statistics/
Semore, B. (2014, October 20). Project Management Success: Part 1, Know Your Stakeholders –
Pinnacle. Retrieved October 21, 2015, from http://pbsnow.com/pinnacle-point/projectmanagement-success-know-your-stakeholders/
1.5 Overview
This product specification details the fundamental hardware and software design,
interfaces, and features of JournalHub. The following sections will describe the elements in
detail, including a diagram of the JournalHub components. A discussion of features and outputs
will also be incorporated.
2.0 General Description
The JournalHub prototype will be implemented on a web server provided by one of the
team members. It will incorporate multiple database tables such as stories, files, and staff, each
with their own storied information content. The database entries will be created and managed
through a MySQL database. The primary functionality of the system will be achieved through a
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
8
modified version of Feng Office, also installed on the web server. The major functional
components for JournalHub are illustrated below in Figure 1. JournalHub will be accessible via
most modern web browsers, whether via PC or mobile device. The JournalHub system will be
fully operated from a remote web and database server, and will be interacted with via a local
ODU or personal machine.
2.1 Prototype Architecture Description
Figure 1. Major Functional Components Diagram
JournalHub will be accessible over the internet from a modern web browser. It will
maintain and access a MySQL database which will store all relevant story and archival
information. Once a user is authenticated by entering their credentials, including their username
and password, they will have access to the JournalHub file system, and will be able to perform
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
9
tasks according their user group’s designated roles. Users may send notifications or reminders to
themselves and/or others using the notification system. JournalHub can be configured to either
send mails, making use of an email client, or generate pop-up messages to satisfy the notification
requirements.
2.2 Prototype Functional Description
The prototype will allow users to be added to the system with their own unique
credentials and granted roles on either an individual or group basis. The group roles will be
customizable by administrators with proper authorization. The prototype will be accessed from a
modern web browser on a personal or ODU machine. A user, once authenticated, will be able to
create new tasks as well as manage and manipulate existing tasks. They may also search for and
retrieve existing stories and documents based on information such as date, author, or slug from
within the file system’s database. Users may set up notifications with two mediums to choose
from: pop-up message or email. Additionally, a calendar displaying relevant upcoming events
and tasks will be available. A budgeting system for assigning space to stories for print
publication will be accessible.
2.3 External Interfaces
Use of JournalHub will require a web browser. The browser should be up-to-date, and
installed on a personal computer. Some mobile devices may also be able to access JournalHub
through their own web browsers.
LAB II – JOURNALHUB PROTOTYPE PRODUCT DESCRIPTION
10
2.3.1 Hardware Interfaces
The JournalHub prototype will be hosted on a private remote server. The database and
Feng Office will be held and accessed on this machine. The user will require an internet
connection and web browser.
2.3.2 Software Interfaces
The JournalHub prototype software will be based on a modified installation of Feng
Office. The hosting machine will require this customized Feng Office to operate properly. A
MySQL database installation will also be present on the hosting machine. A user will need a
modern web browser to connect to and make use of JournalHub.
2.3.3 User Interfaces
Users will need keyboard and mouse to make use of JournalHub. Both will required to
properly manipulate all elements of the application. The keyboard will be used for text entries,
such as titles, dates, and other information. The mouse will be used to select and access the
various graphical elements that represent JournalHub’s tabs and functions. Within each tab, the
mouse will be used to select and manipulate the involved sub-elements.