Software Engineering for Internet Applications - Student Community

More documents

Recommendations

Info

If your interest in this book stems from the desire to build astraightforward ecommerce site, don't despair. It turns out that themost successful ecommerce and collaborative commerce sitesare, at their core, actually online communities. Amazon is the bestknown example. In 1995 there were dozens of online bookstoreswith comprehensive catalogs. Amazon had a catalog but, with itsreader review facility, Amazon also had a mechanism for users tocommunicate with each other. Thus did the programmers atAmazon crush their competition.As you work through this book, you're going to build an onlinelearning community. Along the way you'll pick up all the importantprinciples, skills, and technologies for building desktop Web, mobileWeb, and voice applications of all types.More• on GPRS: "Emerging Technology: Clear Signals for GeneralPacket Radio Service" by Peter Rysavy in the December2000 issue of Network Magazine, available athttp://www.rysavy.com/Articles/GPRS2/gprs2.html• on the state-of-the-art in easy-to-build Voice applications:Chapter 10 on VoiceXML (stands by itself reasonably well)results and whether the numbers could have been predictedfrom the page flow and HTML designs.• Week 6, Meeting 2: Students present their refineddiscussion forum systems. Class time devoted topresentation of the refined systems. Close with anexhortation that students spend the weekend starting theMobile and VoiceXML problems in parallel so that if they arestuck with the tools they'll have an early warning.• Week 7, Meeting 1: Students complete all exercises inMobile chapter. Class time devoted to presentations anddiscussion of the wireless interfaces to the applications.• Week 7, Meeting 2: Students complete all exercises inthe VoiceXML chapter. Class devoted to presentations anddiscussion. It would be very helpful to have an amplifiedtelephone system so that the entire class can hearinteractions between a team's system and a user.• Week 8, Meeting 1: Students complete all exercises inScaling Gracefully chapter. Take-home mid-term examhanded out (an individual rather than a team project).Class discussion of scaling exercises, ideally starting witheach answer being presented by a separate team.• Week 8, Meeting 2: Exercises 1 and 2 from Search due.Discussion of team designs for full-text search.• Week 9, Meeting 1: Mid-term exam due. All exercisesfrom the Search chapter due. Class time devoted todiscussion of exam questions, answers, and implications.• Week 9, Meeting 2: Planning Redux exercises due. Notethat the instructors must interview the clients as part of thischapter. Team presentations of their work and plans forpublic launch.What to put on examsYou might think that exams are unnecessary in a project-orientedcourse such as this one. We give exams for the following reasons:• we want to make sure that a student isn't being carried byhis or her teammates• we want to make sure that students are reading and rereadingthe principles outlined in this textbook• we want to make sure that students understand datamodeling and concurrency10339
you supply English-language queries that they'll have totranslate into SQL against their tables and columns. A groupcan be one project team or two project teams workingtogether. Ideally the classroom will have many separateblackboards. The instructors walk around answeringquestions and coaching the groups. After 30-40 minutes youask two or three of the best groups to present their work.After each presentation you moderate a discussion of themerits of the data model and how much work the RDBMSwill have to do in answering the queries. You close themeeting time by introducing the B-tree index and explaininghow to add indices to a data model to improve queryperformance.• Week 3, Meeting 1: Students turn in their work on UserRegistration and Management. Class time is devoted topresentation and discussion of different teams' approachesto the user registration chapter problems. At least a coupleof teams will have been successful in meeting with theirclients and drafting solutions to the Planning chapter.Devote 5-10 minutes of class time to discussing the work ofthe farthest-along teams in this area as a way of inspiringthe rest of the class.• Week 3, Meeting 2: Students turn in their work onPlanning and Exercises 1 through 3 in ContentManagement (up to but not including the skeletalimplementation). Class time is devoted to presentation anddiscussion of teams' approaches to content managementdata models. Consider breaking up into teams to take asingle-table data model and put it into 3rd Normal Form.• Week 4, Meeting 1: Devoted to look and feel criticism ofpublic Internet applications and the more advanced teams.• Week 4, Meeting 2: Students complete all exercises inContent Management, including client sign-off. Classtime devoted to team presentations of work so far and plansfor immediate future.• Week 5, Meeting 1: Students complete all exercises inSoftware Modularity. Class time devoted to teampresentations of their design decisions and documentation.• Week 5, Meeting 2: Students complete exercises inDiscussion chapter up to but not including the usabilitytest.• Week 6, Meeting 1: Students complete all exercises inDiscussion chapter except execution of the refinementplan. Class time devoted to discussion of usability testChapter 2B a s i cIn this chapter you'll learn how to evaluate Internet applicationdevelopment environments. Then you'll pick one. Then you'll learnhow to use it.You're also going to learn about the stateless and anonymousprotocol that makes Web development different from classical intercomputerapplication development. You'll learn why the relationaldatabase management system is key to controlling the concurrencyproblem that arises from multiple simultaneous users. You'll developsoftware to read and write Extensible Markup Language (XML).2.1 Old-style Communications ProtocolsIn a traditional communications protocol Computer Program A opensa connection to Computer Program B. Both programs runcontinuously for the duration of the communication. This makes iteasy for Program B to remember what Program A has said already.Program B can build up state in its memory. The memory can in factcontain a complete log of everything that has come over the wirefrom Program A.**** insert figure here ****Figure 1: In a traditional stateful communications protocol, twoprograms running on two separate computers establish a connectionand proceed to use that connection for as long as necessary,typically until one of the programs terminates.2.2 HTTP: stateless and anonymousHyperText Transfer Protocol (HTTP) is the fundamental means ofexchanging information and requesting services on the Web. HTTP isalso used when developing text services for mobile phone users and,with VoiceXML, also used to implement voice-controlled applications.The most important thing to know about HTTP is that it is stateless. Ifyou view 10 Web pages, your browser makes 10 independent HTTPrequests of the publisher's Web server. At any time in between thoserequests, you are free to restart your browser program. At any time inbetween those requests, the publisher is free to restart its serverprogram.33811
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: • we want to see if a student is
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 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?