In this part of the project, you will be required to explain your solution. A solution consists of many components.In general, you should describe the original problem, the general architecture of the system you are building and then the details of the specific parts of the system. For example, if you are building a database for selling books you can talk about the following issues:

• System issues:
• which databases you are going to access [such Amazon or BarnesandNoble];
• are you going to access them online when a user asks a query, or offline by loading the data periodically from the servers;
• how the data loading process is going to work, how are you going to create wrappers for accessing these sources, automatically, manually or by some adaptive process;
• what are the various tools you are going to use to access the sources [backend databases, CGI scripts, etc.]
• what type of an interface and query options are you going to provide to the users; etc.
• Theoretical issues:
• how are you going to solve mismatches between different systems;
• in terms of queries, you might be able to ask for ISBN in one source but only title and author in another one;
• in terms of answers, one source might return as author "Fedor Dostoyevski" as opposed to "Fyodor Dostoyevski" in another, how will you decide the two are the same;
• in terms of information, one source may only give you a part of the information you want, how will you use this information to decide which sources to access;
• if you have a backend database that stores a warehouse of all books, what is your unified data model, where do you store the sources and the prices for these sources;
• in the backend data model, what are the rules for removing a book or changing its price in the warehouse if this book does not appear in a database temporarily;