Software Engineering for Internet Applications - Student Community

More documents

Recommendations

Info

With Java Server Pages...The following is Jin S. Choi's recommendation for storing andaccessing configuration parameters when using Java Server Pages.Specify Parameter tags within the Context specification for yourapplication in conf/server.xml. Example:You can also specify the parameter in the WEB-INF/web.xml file foryour application:companyNameMy Company, Inc.The "override" attribute in the first example specifies that you do notwant this value to be overridden by a context-param tag in theweb.xml file. The default value is "true" (allow overrides).To retrieve parameters from a servlet or JSP, you can call:Related links:• VoiceXML Forum (http://www.voicexml.org/)• Voice articles at developer.com(http://www.developer.com/voice/)• Voice Extensible Markup Language (VoiceXML)Specification Version 2.0(http://www.w3.org/TR/voicexml20/)• Speech Recognition Grammar Specification Version 1.0(http://www.w3.org/TR/grammar-spec/)• VoiceXML: letting people talk to your HTTP server throughthe telephone (http://eveandersson.com/arsdigita/asj/vxml;includes source code and case studies)10.17 Time and MotionEach member of the team should work through the basics, Exercises1-4, individually and expend to spend 2 to 3 hours.The team should plan to spend one to two hours together designingthe voice interface, but may divide the work of prototyping andrefining the voice interface plus Exercises 5 and 6. A reasonablescope is 8 to 12 programmer-hours.The time required for client signoff will vary depending on the client'slevel of interest. Plan spend at least 30 minutes on the signoff.getServletContext().getInitParameter("companyName");More:• documentation for Context:http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/context.html• javadoc for ServletContext:http://jakarta.apache.org/tomcat/tomcat-4.0-doc/servletapi/javax/servlet/ServletContext.html7.7 Exercise 1Create a /doc/ directory on your team server. Create an index pagein this directory that links to a development standards document150199
10.15 Beyond VoiceXML: Conversational SpeechWill all voice applications be VoiceXML applications? The currentsyntax of VoiceXML is geared at producing a user experience ofnavigating through hierarchical menus. State-of-the-art research ismoving beyond this towards conversational systems in which anyutterance makes sense at any time and where context is carried fromexchange to exchange. For example, you can call the MIT Laboratoryfor Computer Science's server at 1-888-573-8255:198• You: Will it rain tomorrow in Boston?• JUPITER: To my knowledge, the forecast calls for no raintomorrow in Boston.• You: What about Detroit?• JUPITER: To my knowledge, the forecast calls for no raintomorrow in Detroit.• You: Are there any floods in the United States?• JUPITER: Flood warnings have been issued for Louisianaand Mississippi.• You: Will it be sunny in Phoenix?...Notice how the system, more fully described athttp://www.sls.lcs.mit.edu/sls/whatwedo/applications/jupiter.html,assumed that you were still interested in rain when asking aboutDetroit, context carried over from the Boston question.In the long run, as these more natural conversational technologiesare perfected, the syntax of VoiceXML will have to grow toaccommodate the full power of speech interpreters or be eclipsed byanother standard.10.16 MoreVoiceXML gateways:• Tellme (http://studio.tellme.com/)• VoiceGenie (http://developer.voicegenie.com/)• Voxeo (http://www.voxeo.com/)• BeVocal Cafe (http://cafe.bevocal.com/)• HeyAnita Freespeech (http://freespeech.heyanita.com/)(/doc/development-standards would be a reasonable URL butyou can use whatever you like so long as it is clearly linked from/doc/).In this development standards document, cover at least the followingissues:1. naming of URLs: abstract versus non-abstract (bleah),dashes versus underscores (hard for many users to read),spelled out or abbreviated2. naming of URLs used in forms and form processing--willthese be at the same URL or will a user working through asequence of forms proceed /foo/bar, /foo/bar-1,/foo/bar-2, etc.3. RDBMS used4. computer languages used for Web scripts and proceduralcode within the RDBMS5. means of connecting to the RDBMS (libraries, bindvariables, etc.)6. variable naming conventions7. how to document a module8. how to document an shared procedure9. how to document a Web script (author, valid inputs)10. how Web form inputs are validated by scripts11. templating strategy chosen (if any)12. how to add a configuration variable and how to name it sothat at least all parameters associated with a particularmodule can be identified quicklyStep back from your document before moving on to the nextexercise. Ask yourself "If a new programmer joined this projecttomorrow, and I asked her to build a surveys module, would she beable to be an effective consistent developer in my environmentwithout talking to me?" Remember that a surveys module will requirean extensive administrative interface for creation of surveys,questions, and possible answers, both admin and user interfaces forlooking at results, and a user interface for answering surveys. If theanswer to the question is "Gee, this new programmer would have toask me a lot of questions", go back and make your developmentstandards document more explicit and add some more examples.7.8 Exercise 2Document your team's intermodule API within the /doc/ directory,perhaps at /doc/intermodule-API, linked from the doc index151
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 and 88:
{site url}{site description}en-usCo
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: Chapter 11Scaling GracefullyLet's l
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?