activity01.txt P. Conrad for CISC474, Spring 2006

Survey of Web Sites and Web Technologies

Introduction

This activity will several goals

It should prompt you to think about ways in which web sites are used to deliver dynamic content.
It should get you started with thinking about what kind of web apps you are interested in building
It should introduce you to the idea of using "stories" which is an important part of the software development methodology known as "eXtreme Programming".
It will help introduce you to some of your classmates, to the wireless laptops, and how PBL works

What you need to do (short version)

Introduce yourself to your fellow team members
Get at least one laptop for your table, and point it at the online version of this web page.
In another web browser window, one group member should log on to WebCT, find the site for CISC474, find the "discussions" link, and go to the discussion marked "A01". Start by making a simple posting with your group number, and the names and userids of the members of your group.
Below, there is a list of web sites along with
- example "stories" for that site (details on what a "story" means are listed below.)
- clues about what technologies are used on that site.
You are asked to add at least two sites to the list along with examples "stories" and if possible some clues about what technologies are used (details below). You'll post your answers on WebCT.

Note that you should periodically check what other groups have posted. If you post a site that some other group has posted "first", then your "later" posting won't count towards your total of two.
Once your group has two new web sites (with stories) with whatever time is remaining (if any), as individuals come up with your own "story" for a web site that you think would be interesting to develop, and post that idea to WebCT. [If we run out of time to do this in class, you'll be asked to do this as homework, sometime between now and 1PM Thursday]. See below for more detail.

Why we are doing this

The web sites you submit will be added to the list on the course web site. We will use this list of web sites throughout the semester to find examples of where and how particular technologies are used.
We will use these web sites as springboards to launch our own ideas about building web sites
We will use these web sites "stories" in ways that will become apparently later (I have to keep "some" mysteries to myself to maintain the sense of drama... ha ha ha...)

Details

The list of web sites is at:

http://www.udel.edu/CIS/474/pconrad/06S/topics/webApplications/exampleWebapps.htm

This list has some example stories, and lists what technologies are used on various sites. The section at the bottom has some advice on keeping the stories short.

Criteria: how will the web site selection and stories be graded?

The web sites you come up with will be graded on originality and clarity: how well you explain the story.

Originiality:

fair (C) a web site that is "just like" one already on the list.
e.g. Delta airlines is on the list, you add USAirways (same story)
good (B) a web site in an existing category, but with a very different story
(e.g. web site that finds current status, location of all "flights in the air".
excellent (A) a web site in a completely different category with a "story" unlike all the others.

For example, the list doesn't currently have any sites about "sports". If you are the first group to post a really good sports site (e.g. for looking up scores?) that would be excellent in terms of originality (well, not so much since I just suggested it, but I'll overlook that.)

Clarity:

fair (C): The story is only vaguely described. Or, the description is clear, but it is either sloppy, or contains spelling, punctuation and/or grammar errors that detract from the clarity.
good (B): The story is mostly clear and described neatly and without errors, but perhaps some point is overlooked; a developer would have to ask more questions, or "read something in" to the story to build a web site from it.
excellent (A): The story is described with enough clarity that a developer could sit down and build a web site from the description that would provide the user with a satisfying experience.

How do you know what technologies are used?

Here are some clues. Don't get too bogged down in this though: I'm more interested in the stories today. I ask you to look for the technologies mainly to get you thinking about the topics we'll cover in this course, and how widely they are used in the "real world."

Clues to Server Side technologies:

If you see .jsp in the URL, then the site probably uses Java Servlets and JSPs on the server side
If you see .asp in the URL, then the site probably users ASP.NET (a Microsoft technology) on the server side
If you see .php in the URL, then the site probably users PHP (a Perl-based technology) on the server side
Finally, some sites tell you what technology they use (e.g., in an "about" link).

Clues to Client Side technologies:

If you view source, and find <script type="text/javascript"> in the source code, then the site is using JavaScript.
If you see <applet> tags, that's a dead giveawy that Java applets are being used. These are pretty rare these days as JavaScript has really taken over a lot of what used to be done with Java applets.
If you view source, and find <script> but no type, then you may have to look at the code. For now, if you aren't sure (and you may not be if you don't already know JavaScript) you can "guess" but label your guess as that.
If you view source and see a <style></style> section then the page is using CSS. Another clue that the site is using CSS is something like this:
```
<link rel="STYLESHEET" type="text/css" href="http://www.example.com/main.css" 
```

Developing your own story

Think of something that interests you, or think of a problem that could be solved with a web site. For example, is there some kind of web site that would help you get through your day more effectively?
Keep your story simple and "high level" for now. You can elaborate on it later.
Don't get bogged down in details such as colors and fonts, how the screen is laid out, or what fields will be in a database. Concentrate on what the website does for the end user, and what the end user's experience is.