The following represents the section headers you should consider for your reasoned document.  Each section should have (at least) two research citations to support your work:

a. Stakeholders.  Who do you think they are and what might their interaction be with the eventual website.    How would you classify them in order of importance for the web site you are designing?

 Hint:  Consider the current stakeholders and perhaps new stakeholders as a result of the web site.

b. What are the events (or scenarios) that the key stakeholders might undertake?

      Hint use a table that breaks down the events into USE case size components as shown in the example below for one scenario (event). 

c. From  here you can model TWO primary USE cases that describe the stakeholder's intereaction with your system design. 

d. You are now in a position to design the site map that describes the system in terms of navigation for primary scenarios  (such as the one described above) .  A site map allows the reader to see the relationship that the pages offer with each other and what the completed system might look like. 

Hint:  Use the SmartArt tools facility in Word that allows an organsiational chart.   You can configure this to reflect your site map.  Just reflect the primary scenarios for your main stakeholders  (roughly no more than 4 levels).

e. Wireframe.  This is a template that shows your client what the layout of each screen will be including various rules and standards.  You can use Word to describe this or a screen in power point.  I do not expect you to draw combo boxes, but to label them ansd let me knopw what the screen components are and how they perform.

f. A story board for ONE scenario.   A story board does not show all the screen detail but just enough to show how ONE  scenario might span part of your site map.

g. How would you test this design to check its suitability