Software Engineering for Internet Applications - Student Community

More documents

Recommendations

Info

Not a user|VNeed Email Verification Rejected (via anyNeed Admin Approval pre-authorization| state)||Need admin approvalNeed email verification| || |-------------->Authorized
{site url}{site description}en-usCopyright {dates}{rfc822 date}{your emailaddr}{rfc822 date}{item1 title}{description foritem1}{guid for item1}{rfc822 date for when item1went live}262item2}went live}{item2 title}{description for{guid for item2}{rfc822 date for when item2Remember to escape any markup in your titles and descriptions, sothat, for example, Whoa! becomesWhoa!.14.11 More• http://www.soapware.org/bdg -- A Busy Developer's Guideto SOAP• http://www-106.ibm.com/developerworks/library/wssoap/?dwzone=components#2-- Using WSDL in SOAPApplications (An introduction to WSDL for SOAPprogrammers)SOAP implementations:• Apache SOAP (in Java) at http://xml.apache.org/soap/• PHP: NuSOAP (http://dietrich.ganx4.com/nusoap/) andPEAR::SOAP(http://www.phppatterns.com/index.php/article/articleview/39)5.8 Multi-Page Design and FlowThis book defers discussion of individual page design until theContent Management chapter but we need to think about page flowdesign right now. Why? The bad design of a single page will offend auser; the bad design of the page-to-page flow of a site will defeat auser.One of the things that users love about the Web is the way in whichcomputation is discretized. A desktop application is generally acomplex miasma in which the state of the project is only partiallyvisible. Despite software vendors having added multiple-level Undocommands to many popular desktop programs, the state of thoseprograms remains opaque to users.The first general principle of multi-page design is therefore Don'tbreak the browser's Back button. Users should be able to goforward and back at any time in their session with a site. Forexample, consider the following flow of pages on a shopping site:• choose a book• enter shipping address• enter credit card number• confirm• thank-youA user who notices a typo in the shipping address on the confirmpage should be able to return to the shipping address entry form withthe Back button or the "click right" menu attached to the Back button,correct the address and proceed from there. See the "Choosingbetween GET and POST" section later in this chapter.A second general principle is Have users pick the object first andthen the verb. For example, consider the customer service area ofan ecommerce site. Assume that Jane Consumer has alreadyidentified herself to the server. The merchant can show Jane a list ofall the items that she has ever purchased. Jane clicks on an item(picking the object) and gets a page with a list of choices, e.g.,"return for refund" or "exchange". Jane clicks on "exchange" (pickingthe verb) and gets a page with instructions on how to schedule apickup of the unwanted item and pages offering replacement goods.How original is this principle? It is lifted straight from the AppleMacintosh circa 1984 and is explicated clearly in Macintosh Human87
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: Chapter 15Metadata (and Automatic C
Page 89 and 90: drawing on the intermodule API that
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

Create successful ePaper yourself

Delete template?

Save as template?