CoolStateLA/Muhammad Lodhi
From CSWiki
Complete requirements definition for CoolStateLA project. Document those requirements as help pages for each web page.
Contents |
[edit] MAY 17, 2008
[edit] ABSTRACT
CoolStateLA is a new vision to develop a CSULA converged newsroom that will consist mainly of the University Times Newspaper, CoolStateLA News Website, CoolStateLA News Web Radio, and CoolStateLA News Webcast. The focus of this analysis is on the process of producing the newspaper and news website from the CoolStateLA Enterprise Information System.The main goal is to create a synergistic environment that allows not only creative input but checks and balances to insure journalistic intregity.The spiral software development process was used to approach the project.Requirements were collected in Use Cases and the functionality was analyzed.We are using an extensive architechural system that incorporates the three main components of information flow.This starts with the client side which consists of the RSS news feeds (Ruetres,CNN,BBC, Etc.). Next it moves onto the STORI workstaff view, Joomla staff and then into CoolStatela's programming.The next components consist of the servers used to construct and pass information along to the consumer.These are made up by the Feed filter Manager (ROME), Stori/Workflow Manager, and then the creation and publication components.The final component in the chain is the Fedora server, Asset manager and finally the delivery of the product to the customer through CoolStateLa's broadcast sytems.The conceptual model was designed through a database schema. Artifacts were iteratively refined by communicating with all of the stakeholders: News Director, technical adviser,and development team members.The results have created a better understanding of the news industry and Fedora's power of compilation.Baseline prototypes were developed for the CoolStateLA website,the asset manager, and workflow manager. Communication and iteration are the keys to analyzing and designing the complex converged newsroom that provides information to change lives.
I am writing the the detail of 2 pages News Budget and Status Report Detail.
[edit] NEWS BUDGET
On the left of the page is the PRIORITY tag and 2nd TITLE. Then comes the DESCRIPTION.
Priority button should be the left most and is a drop down box which should be in numbers only. We are using priority so we don,t need the "Cancel" column. Priority decision is only used by the news director so we don,t need the "Approve" column, as "priority" column is doing the job of both(cancel and approve). The title obviously shows the title of the story and just gives the overview of the story. The "Description" button actually shows the detail of the story. We need the "submit" button on the left of the page in the bottom so that when we click on it we know the story is going to publish. This news budget page is responsible for providing access to all the news. Once we click the "submit" button,this news will automatically upload to the server.
[edit] STATUS REPORT-DETAIL
First of all we need 5 tags: Slug,Sub Slug,Creation Date,Medium and Producer.We don,t need Validity Date,Status Priority Run, Date Story No.,and History. Creation date shows the creation of the news. It shows when news comes to the center. Slug is the caption, for example: "Hillary comes to CSULA". This news comes to section of Slug.Sub. Slug means the events which are supporting to that particular news for examples Sub Slug of the above news can be like this that Hillary address to Engineering students for 2 hours and after that she went to Library and then she did the press conference for 30 minutes.So in other words all these small news items are supporting the big news like "Hillary been to CSULA". Medium shows the section(Radio,Images, Video)that defines which section will be responsible for that particular news item. When we click the "producer" button a drop down pop up button will open which shows the person's personal information. For example: What will be the editor's email address and phone number? It shouldn't be a separate page. It should also come up with detail as a drop down page.
[edit] MAY 10, 2008
I made 2 mock up pages one for general search page and second one i made for advanced search page.In those pages i cleared most of the things which i understood after discussing with Jon.
I sent those pages to sepeideh.
[edit] March 29, 2008
[edit] To do
- Work with Ren on first draft of mock-up.
- Work with Deidre, Ren, Sepideh, and Ishany on DB schema.
[edit] Report
[edit] March 22, 2008
[edit] To do
- Get together with Ren and learn about the overall use cases.
- Revise architecture diagram.
- Revise schema.
[edit] Report
I met with Ren and we discuss use cases, producution report, status report, produce editer and writer. We design some use cases for the above parameters and we meet at the point that the current schema is wroking fine and need no change.
We also came up with some hurdles in the 'beat' which me and Ren are sorting these days and will come up with a solution soon.
