|
Scheme
1
Scheme
2
Scheme 1
In
all of the scenarios Heather has to log on to the system. Screen
1 displays the initial page of the system that is provided to the
user when they start the CMS program. This screen allows the user
to log in. Then Heather sees a list of choices.
In
scenario 1, In screen 2 she chooses add or modify document.
She then sees screen 3. She chooses the appropriate category from
the list for press releases (Screen 3). Then she comes to screen
4 where she enters the title for the press release and clicks submit.
Then Heather comes to screen 5 where she can enter the press release
and submit it to the system. Next she is taken to screen 6 where
she can choose the graphics and/or style sheets for the document
she added (defaults apply if nothing is selected). Finally, Heather
exits the system.
In
scenario 2 she wants to update the content. This task can be
done following the same sequence mentioned above. The only difference
being that in screen 4, Heather has to select the appropriate existing
document.
In
scenario 3, Heather wants to add a graphic. In screen 2, Heather
selects the add graphics button. She is then taken to screen 3b
where she selects the type of graphic to be added. Then she can
browse her files to find the file for uploading. When the file has
been found she clicks submit. Finally, she exits the system.
In
scenario 4, Heather wants to edit an existing style sheet. In
screen 2, the selects the add or modify style sheet button. Then
in screen 3c she is given a list of style sheets and she selects
the desired sheet and hits submit. Then she sees screen 4c where
the style sheet is presented in the DEM. She edits the style sheet
and hits submit. Then she can exit the system.
In
scenario 5, Dave
needs to review the press release that Heather submitted. Dave logs
on to the system in screen 1. In screen 2 he selects editors console.
He is then presented with screen 3d. In screen 3d he sees a list
of content that has been modified and is waiting for approval. He
selects the press release from the list. Then he sees screen 4d
where the press release is presented in the DEM and the style sheet
and graphic are listed below. He can make modifications and then
submit the content to go live. He can then exit the system.
In
scenario 6, Mekki needs to delete a document. He logs on to
the system in screen 1. Then in screen 2 he selects delete document.
He then sees screen 7a where he selects the category of the document.
Then in screen 7b he selects the document he wants to delete. He
then exits the system.
 
 
 
 
 
Scheme
2
Again,
In
all of the scenarios Heather has to log on to the system. Screen
1 displays the initial page of the system that is provided to the
user when they start the CMS program. This screen allows the user
to log in. Then Heather sees a list of choices.
In
scenario 1, In screen 2 she chooses 'add a document file'. She
then sees screen 3. She chooses the document whose content she would
like to add to the CMS. Also on Screen 3, she selects the appropriate
category to add the press release to. She clicks 'add to CMS' and
then recieves a confirmation screen (Screen 4) so she knows her
content was successfully added. Next she clicks 'ok' to go back
to Screen 2 where she can exit the system. Default graphics and
backgrounds are set with the chosen category for the content. Finally,
Heather exits the system.
In
scenario 2, she wants to update the content. Heather logs in
and selects 'change a document' in screen 2. Heather has to select
the appropriate existing document at Screen 7. SHe clicks 'submit'
and is taken to Screen 8. Here, the document appears in the DEM
and edits can be made to the content. She clicks 'change' and Screen
9 appears to confirm that the changes were made. Next she clicks
'ok' to go back to Screen 2 where she exits the system.
In
scenario 3, Heather wants to add a graphic. In screen 2, Heather
selects 'add a graphic'. She is then taken to screen 12, where she
selects the graphic file to be added and the category to add the
graphic file to. She then clicks 'add', which takes her to Screen
13, where Heather recieves confirmation that the graphic was added
to the system. She clicks 'ok', goes back to Screen 2, and exits
the system.
In
scenario 4, Heather wants to edit an existing style sheet. In
screen 2, she selects 'change a style sheet' and clicks 'submit'.
This works much like changing a document (content). A screen such
as Screen 7 displays a choice of style sheets. Heather chooses the
press release style sheet and clicks 'submit'. Screen 8 presents
the style sheet in the DEM so that changes can be made. Heather
changes the color of the hyperlinks and then clicks 'change'. Screen
9 appears to confirm that the changes were made. Next she clicks
'ok' to go back to Screen 2 where she exits the system.
In
scenario 5, Dave
needs to review the press release that Heather submitted. Dave logs
on to the system in screen 1. In screen 2 he selects editors console.
He is then presented with Screen 14. In screen 14, he sees a list
of content that has been modified and is waiting for approval. He
selects the press release from the list which he recognizes from
the title. After clicking 'review', he sees screen 15, where the
press release is presented in the DEM. He then makes modifications
if he feels they are necessary and then submits the content to go
live by clicking 'submit'. He is taken back to Screen 14, the editor's
console, and clicks 'main' to go back to Screen 2, where he exits
the system.
In
scenario 6, Mekki needs to delete a document. He logs on to
the system in screen 1. In screen 2, he selects 'delete a document
file'. He then sees screen 5, where he selects the document from
the appropriate category for deletion. He clicks 'delete' and is
taken to Screen 6, his confirmation that the selected document was
in fact deleted. He clicks 'ok' to return to Screen 2 and exits
the system by clicking 'exit'.
|