Software Engineering for Internet Applications - Student Community

More documents

Recommendations

Info

This says that the quotations element must contain at least oneoccurrence of onequote but may contain more than one. Now wehave to say what constitutes a legal onequote element:This says that the sub-elements, such as quotation_id must eachappear exactly once and in the specified order. Now we have todefine an XML element that actually contains something other thanother XML elements:This says that whatever falls between and is to be interpreted as raw characters rather than ascontaining further tags (PCDATA stands for "parsed character data").Here's our complete DTD:You will find this extremely useful... Hey, actually you won't find thisDTD useful at all for completing this part of the problem set. The onlyreasons that DTDs are ever useful is for feeding to XML parsersbecause then they can automatically tokenize an XML document. Forimplementing your quotations-xml page, you will only need to look atthe informal example.The meat of this exercise: Write a script that queries the quotationstable, produces an XML document in the preceding form, and returnsit to the client with a MIME type of "application/xml". Place this in fileCapabilities for Site-Wide Administrator. For this as for other userclass items, list those features that are needed first (must-have tolaunch the service in any form), next (what you'd do if you had a littlebit of extra time and effort available), and nice-to-have. One examplefor the site-wide administrator user class is the following:First = publish / manage contentNext = spam members with news/offersNice = track activity at individual registereduser levelDesign Preferences. If your organization has an existing Web site orsites you can probably infer their design style. If they suggest Flash,frames, a lot of JavaScript you've got a potential problem and mightwant to point out that Google, Amazon, eBay, and the othersuccessful Internet applications stick to a plain fast-loading easilyunderstood design.Performance Requirements/ Expectations. Start by suggestingyour own standards of loading times in seconds for the index pageand more complex pages on the site. Let the client react to thesesuggestions. If everyone agrees on sub-second page loading timesthat will make it a lot easier to kick out the worst user interface ideas,such as Flash introductions.Technical Infrastructure Constraints. A small or medium-sizedorganization will generally only have expertise and staff appropriatefor maintaining one kind of server. If you're not building the project ontop of that server you're implicitly asking the organization to spend$100,000 per year to bring in additional maintenance staff and/orpush the new service out to a contract hosting organization. It is bestto be clear up front about what will need to happen when it comestime to move the system into production.Application Maintenance Plans / Resources. Who's going to lookafter what you deliver? How experienced is this person?Budget. What is the total budget for hardware, software, integration,launch (including populating with content), training, andmaintenance?Deadlines. You'll probably use other tools to keep a detailedschedule. Use this worksheet to keep track of some high-level40309
Client Tenure In Job (new, mid-term, leaving)Client Technical Knowledge (none, some, lots)About the ApplicationYou want to document at a high level what the client wants, what youthink the client should want (if different), and if there are differences,what the plan for persuading the client to follow your lead is. Some ofthese items are confusing and they are explained below.TopicCapabilities for Site-Wide AdministratorCapabilities forRegisteredCommunity MemberCapabilities forUnregistered CasualVisitorCapabilities for UserClass NDesign PreferencesPerformanceRequirementsTechnicalInfrastructureConstraintsApplicationMaintenance Plans /ResourcesBudget ThroughFirst YearDeadlinesWhat the ClientWantsFirst, Next, NiceFirst, Next, NiceFirst, Next, NiceFirst, Next, NicePage loadingtimesSoft launch, fullrollout, firstbusiness benefitWhat WeThinkPersuasionPlan*system at /basics/quotations-xml, so that other users can retrieve thedata by visiting that agreed-upon URL.Exercise 11: Importing XMLWrite a program to import the quotations from another student's XMLoutput page. Your program must• Grab /basics/quotations-xml from another student's server• Parse the resulting XML structure into records and thenparse the records into fields.• If a quote from the foreign server has identical author andcontent as a quote in your own database, ignore it;otherwise, insert it into your database with a newquotation_id. (You don't want keys from the foreign serverconflicting with what is already in your database.)Hint: You can set up a temporary table using create tablequotations_temp as select * from quotations and then drop it afteryou're done debugging, so that you don't mess up your ownquotations database.You are not expected to write an XML parser as part of this exercise.You will either use a general-purpose XML parser or your TAs willgive you a simple program that is capable only of parsing thisparticular format. If you aren't getting any help from your TAs andyou're using Oracle, keeping in mind that the Oracle RDBMS hasextensive built-in support for processing XML. Read the Oracledocumentation, notable the Oracle9i XML Database Developer'sGuide - Oracle XML DB or visit http://otn.oracle.com. If you're usingJava or Perl there are plenty of free open-source XML parsersavailable. The Microsoft .NET Framework Class Library contains aclasses that provide a full set of XML tools.Exercise 12: Taking CreditPlease go through your source code files. Make sure that there is aheader at the top explaining (1) who wrote the code, (2) on what dateit was written, and (3) what problem it is trying to solve. Please gothrough your Web pages. Make sure that at the bottom of each pagethere is a mailto: link to your permanent email address.It is your professional obligation to other programmers to takeresponsibility for your source code. It is your professional obligation30841
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: scheduling goals that both you and
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 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?