Software Engineering for Internet Applications - Student Community

More documents

Recommendations

Info

Interface Guidelines (Apple Computer, Inc.; Addison-Wesley, 1993;full text available online athttp://developer.apple.com/documentation/mac/HIGuidelines/HIGuidelines-2.html). In a Macintosh word processor, for example, you selectone word from the document with a double-click (object). Then fromthe pull-down menus you select an action to apply to this word, e.g.,"put it into italics" (verb). Originality is valorized in contemporarycreative culture but it was not a value for medieval authors and itdoes not help users. The Macintosh was enormously popular tobegin with and its user interface was copied by the developers ofMicrosoft Windows, which spread the object-then-verb idea to tens ofmillions of people. Web publishers can be sure that the vast majorityof their users will be intimately familiar with the "pick the object thenthe verb" style of interface. Sticking with a familiar user interface cutsdown on user time and confusion at a site.These principles are especially easy to apply to user administrationpages, for example. The administrator looks at a list of users andclicks on one to select it. The server produces a new page with a listof possible actions to apply to that user.5.9 Exercise 2: Page FlowStart by sketching the page flow for user registration andadministration. There should be one circle or box for every URL inthe system and one arc for every possible transition from URL A toURL B. If you have a lot of URLs that are form targets and performdatabase updates but redirect to other pages in the system fordisplay, you may want to distinguish those URLs with a light ordashed outline.Ideally this drawing should be scanned and made available amongyour online documentation.Below is an example of the kind of drawing we're looking for.day or two. HTML is simple enough that programmers were able tobuild their first page within 30 minutes and non-programmers weren'tfar behind. In fact, the initial Web standards were so simple thatacademic computer scientists predicted that the system wouldn'twork.Within a decade, however, the Web Consortium was focussing itsefforts on the "Semantic Web" and Resource Description Framework(RDF; see http://www.w3.org/RDF/). Where standards committeemembers once talked about whether or not to facilitate adding acaption to a photograph, you now hear words like "ontology" thrownaround. Web development has thus become as challenging ascracking the Artificial Intelligence problem.Where do SOAP and WSDL sit on this continuum from the simplicityof HTML to the AI-complete problem of a semantic Web? Apparentlythey are closer to RDF than to HTML because it is taking many yearsfor SOAP and WSDL to catch on as opposed to the wildfire-likespread of the human-readable Web.The dynamic world of weblogs has settled on a standard that hasspread very quickly indeed and enabled the construction of quite afew computer programs that aggregate information from multipleweblogs. This standard, pushed forward primarily by Userland's DaveWiner, is known as Really Simple Syndication or RSS and isdocumented at http://blogs.law.harvard.edu/tech/rss.14.10 Exercise 8: What's New Syndication FeedAs a kindness to the thousands of people who run desktop weblogaggregators, create an RSS feed for your content at/services/new-content-rss.xml. The feed should contain justthe title, description, and a globally unique identifier (GUID) for eachitem. You may use and are encouraged to use the fully qualified URLfor the item as its GUID, if it has one.Validate your feed using a rss reader(http://backend.userland.com/directory/167/aggregators) or thevalidator at http://aggregator.userland.com/validator.Template{site name}88261
drawing on the intermodule API that you defined as part of your workon the Software Modularity chapter exercises.14.7 Exercise 6: What's New Web ServiceExpose your procedure to the wider world so that other applicationscan take advantage via remote method invocation. Install a SOAPhandler that accomplishes the following:• handles HTTP requests to /services/new-content andchecks for correct SOAP syntax• pulls the n_items parameter out of the request, if present• executes the procedure call and fetches the results• delivers the results as a valid SOAP response containingzero or more "item" records, with the fields listed in Exercise5 for each item.Your development platform may provide tools that, once you'vemapped the external Web service to the internal procedure call,handle the HTTP and SOAP mechanics transparently. If not, you willneed to skim the examples in the SOAP specification and read theintroductory articles linked below.14.8 Exercise 7: Self-descriptionWrite a WSDL contract that describes the inputs and outputs for yournew-content service. Note that if you are using Microsoft .NET,these WSDL contracts will be automatically generated in most cases.You need only expose them.Your WSDL should be available either by adding a ?WSDL to the URLof the service itself (convenient for Microsoft .NET users) or availableby adding a .wsdl extension to the URL of the service itself.Validate your WSDL contract and SOAP methods by inviting anotherteam to test your service. Do the same for them. Alternatively, lookfor and employ validation tools out on the Web.14.9 The March of ProgressThe initial Web standards, circa 1990, were simple. HTTP is simpleenough that any competent programmer can write a basic server in aFigure ****: Page flow documentation for a standalone birthdayreminder service. Email reminders are sent out either the day of, theday before, or one week before the date each year. For more info onthis application, see Chapter 15 of Philip and Alex's Guide to WebPublishing at http://philip.greenspun.com/panda/. Drawing by MinaReimer.26089
Page 1 and 2:
SoftwareEngineering forInternetAppl
Page 3 and 4:
Signature: ________________________
Page 5 and 6:
end-users. We use every opportunity
Page 7 and 8:
• availability of magnet content
Page 9 and 10:
• we want to see if a student is
Page 11 and 12:
you supply English-language queries
Page 13 and 14:
What to do during lecturesWe try to
Page 15 and 16:
The one-term cram courseWhen teachi
Page 17 and 18:
332• spend a term learning how to
Page 19 and 20:
Once we've taught students how to b
Page 21 and 22:
has permission to perform each task
Page 23 and 24:
UDDIUnixcustomer's credit card. If
Page 25 and 26:
thousands of concurrent users. This
Page 27 and 28:
OraclePerlnamed XYZ" without the pr
Page 29 and 30:
LDAPLinuxbits per color, a vastly s
Page 31 and 32:
FilterFirewallFlat-fileGIF318functi
Page 33 and 34:
when there is an educational dimens
Page 35 and 36:
system. The authors of the core pro
Page 37 and 38: Sign-OffsTry to schedule comprehens
Page 39 and 40: scheduling goals that both you and
Page 41 and 42: Client Tenure In Job (new, mid-term
Page 43 and 44: ReferencesEngagement ManagementSQL*
Page 45 and 46: Decision-makers often bring senior
Page 47 and 48: presentation to a panel of outsider
Page 49 and 50: 300always been written by programme
Page 51 and 52: 17.3 Professionalism in the Softwar
Page 53 and 54: Try to make sure that your audience
Page 55 and 56: Chapter 17WriteupIf I am not for my
Page 57 and 58: Suppose that an RDBMS failure were
Page 59 and 60: analysis programs analyzing standar
Page 61 and 62: at 9 hours 11 minutes 59 seconds pa
Page 63 and 64: found" will result in an access log
Page 65 and 66: 15.18 Time and MotionThe team shoul
Page 67 and 68: select 227, 891, 'algorithm', curre
Page 69 and 70: create table km_object_views (objec
Page 71 and 72: • object-create• object-display
Page 73 and 74: The trees chapter of SQL for Web Ne
Page 75 and 76: );274-- ordering within a form, low
Page 77 and 78: and start the high-level document f
Page 79 and 80: Example Ontology 2: FlyingWe want a
Page 81 and 82: systems. What would a knowledge man
Page 83 and 84: spreadsheet". Other users can comme
Page 85 and 86: Chapter 15Metadata (and Automatic C
Page 87: {site url}{site description}en-usCo
Page 91 and 92: At this point you have something of
Page 93 and 94: • description• URL for a photo
Page 95 and 96: Here's a raw SOAP request/response
Page 97 and 98: Chapter 14Distributed Computing wit
Page 99 and 100: conduct programmer job interviews h
Page 101 and 102: Most admin pages can be excluded fr
Page 103 and 104: content that should distinguish one
Page 105 and 106: Chapter 13Planning ReduxA lot has c
Page 107 and 108: the Internet-specific problem of no
Page 109 and 110: wouldn't see these dirty tricks unl
Page 111 and 112: 12.8 Exercise 4: Big BrotherGeneral
Page 113 and 114: than one call to contains in the sa
Page 115 and 116: A third argument against the split
Page 117 and 118: way 1 1/16One might argue that this
Page 119 and 120: absquatulate 612bedizen 36, 9211cry
Page 121 and 122: What if the user typed multiple wor
Page 123 and 124: Chapter 12S E A R C HRecall from th
Page 125 and 126: long as it is much easier to remove
Page 127 and 128: features that are helpful? What fea
Page 129 and 130: made it in 1938)? Upon reflection,
Page 131 and 132: environment, we identify users by t
Page 133 and 134: those updates by no more than 1 min
Page 135 and 136: Balancer and mod_backhand, a load b
Page 137 and 138: translation had elapsed--the site w
Page 139 and 140:
It seems reasonable to expect that
Page 141 and 142:
11.1.5 Transport-Layer EncryptionWh
Page 143 and 144:
such as ticket bookings would colla
Page 145 and 146:
give their site a unique look and f
Page 147 and 148:
It isn't challenging to throw hardw
Page 149 and 150:
Chapter 11Scaling GracefullyLet's l
Page 151 and 152:
10.15 Beyond VoiceXML: Conversation
Page 153 and 154:
Consider that if you're authenticat
Page 155 and 156:
In this example, we:194• ask the
Page 157 and 158:
As in any XML document, every openi
Page 159 and 160:
(http://www.voicegenie.com). These
Page 161 and 162:
Chapter 10Voice (VoiceXML)questions
Page 163 and 164:
9.15 MoreStandards information:•
Page 165 and 166:
9.14 The FutureIn most countries th
Page 167 and 168:
9.10 Exercise 7: Build a Pulse Page
Page 169 and 170:
9.6 Keypad HyperlinksLet's look at
Page 171 and 172:
text/xml,application/xml,applicatio
Page 173 and 174:
Protocol (IP) routing, a standard H
show all

Software Engineering for Internet Applications - Student Community

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?