Use Case Scenarios-CAO


Collaborative Authoring and Officing Suites Home Page 

Potential Product List

Use Case Scenarios

Collaborative Authoring Product Breakdown



Scenario 1: 

Community group coming together to help plan building a local park


     Kathleen is the head of Project Park Build and has recently been placed in touch with 25 active members in her community. Initially, she sends out a mass email to see who is interested in tackling this project. As she hears from those who want to be involved, she adds their name to a digital spreadsheet and shares the spreadsheet with those members. She uses another online tool to schedule a face-to-face meeting, before which she shares all files relating to Project Park Build through the virtual collaboration tool where the spreadsheet is located. The automated email that the team members received has a link to the files and a personal note from Kathleen saying, “I am thrilled you’re interested in helping our neighborhood park be built! Please look over the files, print them off or bring your laptop to the meeting. Each person is responsible to have the information in front of them during the meeting.” Over the weeks between sharing the files and holding the meeting, Kathleen is able to make edits to the files and add the new drawings she received from the contractor. At the meeting, Kathleen is able to flow through each point on the agenda since each member was able to come prepared. From that meeting, a board is established, and Tom volunteers to be in charge of the collaboration tool. He quickly learns to add and edit files that need to be in the online folder. Everything from PDF files, sound files of the meeting, and external links for possible landscapers can be added to the folder and shared with the team. 


Scenario 2:

Team of journalists using a wide variety of reference material to collaboratively write a book about modern US Presidential election history


     Jack, Mike, and Alexis are a group of political news journalists that work for three different leading newspaper outlets. Recently they came together and brainstormed an idea to co-author a new title called “Political Winds: 25 Years of Presidential Election Trends” which will hope to tie in two and a half decades of quantitative and quantitative information. The book will focus on the trends, news stories, and hot button issues that have shaped the Presidential landscape going back to the election of President Reagan. The team hopes to answer big questions like why the notion of a one-term president is so uncommon in the modern era, what underpinnings affect which candidates end up making it through primaries, and much more.

     The team of journalists wants to complete their project in a year or less, and one of the major challenges facing them is having to work in separated parts of the country. Jack resides in New York; Mike works out of San Diego; and Alexis works down in Dallas. In addition to their newfound book project, the trio has a normal day-job workload to manage involving keeping up with political news for their respective newspapers.

     Their book project is going to rely very heavily on previously published news and print material, so source reference cutting and citing will be critical to the book’s focus. The team hopes to set up centrally shared repositories of poll data, editorials, and other reference materials that can be used by any team member needing information for their respective areas of the book. Whatever software solution they decide to use needs to have integrated commenting and markup capability, along with versioning control so that a digital draft of the book can be edited and added to in real time.


Scenario 3:

Virtual Programmers


     There is a team of virtual programmers who are working from different offices around the world. They want to use a collaborative authoring and communication tool that could help them to share their documents from different places at the same time since they cannot meet in person. Also, they want the collaborative tool enables them to chat with each other, share their experiences in software development field and review the written codes, comments, drawing while others are writing. Furthermore, each developer will be able to invite any other developers to their space. By using a collaborative tool, the developer could email team members when he makes changes to the document that they are creating. Developers are also looking for drawing features in the tool that allow them to draw a UML design model.