A PARTLY READ-ONLY, PORTABLE WEB SITE
Introduction. One of the features of 6.033 is that we discuss real systems, both successful and unsuccessful. To get beyond discussion and give you some direct experience with designing systems we also assign two design projects. As in the real world, these projects have (we hope) a simple high-level problem statement but when you get into the system design you will find that there are hard choices to make. And, as in the real world, it is your job to explore, understand, and explain what the best choices are, how to reconcile sometimes conflicting goals, and how to keep the complexity of your design under control.This term, the first of these design projects relates to naming and the World-Wide Web.
The problem. A friend, an Egyptologist, has constructed a web site that consists of about 1,000 distinct web pages holding text, drawings, and photographs of archeological sites--pyramids, monuments, tombs, mummies, and that sort of thing. One of the characteristics of these pages is that they are highly interlinked with cross-references, but they contain no links out to other sites.
Your friend travels to Egypt frequently, with a laptop computer, and would like to carry the content of his web site along when he is in the field. The reason for carrying a copy along is that Internet connectivity in Egypt ranges from weak to non-existent, depending on the location. This year's laptops come with CD readers, and the idea of copying the contents of the web site onto a CD-ROM is very attractive--CD-ROM's are durable even when dropped in the sand, CD writers have recently become cheap and work well, the CD-ROM can easily be placed in any computer in addition to the laptop, and any web browser that happens to be available on the computer provides a convenient user interface. There is even a standard way of writing a complete file system onto a CD-ROM in such a way that it can be mounted on practically any computer system, much like the file system on a floppy disk can be mounted on a PC. A single CD-ROM can hold 650 Megabytes of data, so there is plenty of room on it to hold the 400 Megabytes of stuff currently in the web site.
The problem with this idea is that once written, a CD-ROM is unchangeable. Your friend considers an important virtue of the web organization for his materials to be that he can update individual pages or add new pages as fast as he discovers new things. So there is a need to provide some form of update despite the fact that a CD-ROM is read-only. The option of carrying a CD-ROM writer to Egypt is not attractive, because writing CD-ROM's requires a carefully controlled environment. Your job is to come up with a scheme that your friend can use that has the following features:
Your job is to analyze the situation based on what you what you have learned in 6.033 and its prerequisites about the World-Wide Web, naming systems, and general computer system design issues--modularity, complexity, and so forth. Then develop a complete design that caters to your friend's requirements.
The design project. Propose a design of something (you get to decide what) that solves the problem, while at the same time introducing a minimum of new problems. You do NOT have to implement the design.
Before jumping to the design stage, you should do some more reading:
Another possible source of information is to invoke Alta Vista and look for Web pages that have the word "CD-ROM" or "portable" in them. Unfortunately, there are about 500,000 such Web page for each of those queries. But maybe you can come up with a more helpful query. ("Egyptology" will lead you to some fascinating stuff, but since your friend is on the leading edge of technology you probably won't find this problem already solved there.)
Some things to think about...
There are at least three fundamentally different ways to approach this problem, each with its own merits and disadvantages. It may be very difficult to completely achieve all of the properties that you consider desirable at the same time. In most system designs, trade-off and compromise is required, so you have to decide how important each desirable property is in relation to the others.
Your report. Your paper should be 8 to 10 pages in length. You should start by explaining to your intended audience the background of the problem in terms that audience can understand. Next, describe what you have decided are desirable properties of a solution. Then give your solution and explain how well it achieves (or fails to achieve) the desirable properties. Throughout the paper you should justify each of your design decisions, especially in relation to alternative decisions that you could have made. You will be more convincing if you say not just why your idea is good, but why it is better than the alternatives. (For example, if another approach would meet all of the objectives perfectly, but the cost would be 100 times higher, then you should mention that as a reason for choosing your less-general but cheaper approach.)
Write for an audience consisting of colleagues who took 6.033 five years ago. That is, they understand the underlying system, network, and naming concepts and have a fair amount of experience applying them in various situations, but they have not thought carefully about the particular problem you are dealing with. Assume that your paper will also be used to convince your friend's computer guru that you have the right idea. Finally, give enough detail that he can turn the project over to that guru for implementation with some confidence that you won't surprised by the result.
When evaluating your report, your instructor will be looking at both content and writing.
You can find other helpful suggestions on writing this kind of report in the M.I.T. Writing Program's on-line guide to writing Design and Feasibility Reports.
Phase Two writing considerations: If you are enrolled in the 6.033 writing practicum, you don't need to do anything special; your practicum instructor will explain how the report will get you credit for the Phase II writing requirement. If you are not enrolled in the practicum, AND you want us to forward your design project report to the writing program as your phase II writing project, please say so on the cover page, and make sure that your report is at least 8 pages long. Note also that the writing program has a rule that they will accept only reports that earn a B or better from the class in which they originate. Finally, be aware that the second design project will probably be a team project, and thus much more difficult to tailor to the needs of the writing program than this one.
Collaboration: This project is an individual effort. You are welcome to discuss the problem and ideas for solution with your friends, but if you include any of their ideas in your solution you should explicitly give them credit, and you should be the sole author of your report.
Schedule: Your report is due in recitation Thursday, March 20, 1997.