Chapter 10 - Database Management

Since this project is very information based, databases will be extremely import for storing and recalling data. First of all, the databases will be stored on the same server as the site content, and will be tied directly to the site. The way that the information is sorted on the databases will be very important.

I assume that the databases would contain specific fields of data. These fields would be: Artist, Albums, Release Dates, Performance dates, and related artists. These categories would have to be very dynamic, and connect to other information in the database. The primary key would most likely be Artist.

I think that it would also be very useful for users to be able to add to the database. For example, if there is a more local artist that a user would like to see on the site, they could input the information themselves. The information could then be appended to the database in the proper form.

Chaper 9 - Communications and Networks

Networking will be an important part of this project. Since the majority of the functionality will be available over the internet, understanding how the process works will be important. The site will be hosted on a server, at a specific location on the Globe (where it's located will depend on pricing/availability/etc.)

When users want to access the site, they will send an http request to the hosted server, and the server will respond by displaying the website's content. This process will follow protocols and network architectures. User's will be able to connect to the site from all around the world, due to the global connectivity of the internet.

The user's that use the desktop application will also tap into the server, but not using the http protocol. The application will most likely request information from the information database, which will be located on the server. In this sense, the information is the same as the web version, but it's acquiring it in a different way.

Chapter 6 - Output

This product would mostly use computer monitors to output information to the user. Any different type of monitor would be sufficient in this case. LCD or CRT monitors would both be able to display the website and/or downloadable software. However, it would be recommended for the monitor to be at least 800x600 to properly display the product's website.

The user could also have the option to print any desired information. Like the monitors, any type of working printer would be sufficient, be it laser, inkjet, etc.

In terms of the smartphone version of the software, the screen output would need to be scaled down greatly from the computer version. This way, the information could be properly viewed on the smaller phone-displays.

Chapter 5 - Input

The software would require two types of user input. The first would be over the web-based product. The user would be able to input information using a basic keyboard. This input technology is found with every laptop/desktop computer, so it wouldn't limit the user's ability to input information to the server.

I intend this product to also be available on smartphones, such as the iPhone. In this case, the input would be from the touch-screen on the phone. Using the onscreen keyboard, the user would be able to enter the band name they are looking to find album information on.

In terms of the plug-in software, the data input would come from the software it is being plugged in to. For example, if using an iTunes plugin, the data would most likely come from XML data straight from iTunes.

Chapter 4- The components of the system unit

Although my product will primarily be a software/web based product, the business will still require hardware. The main component needed would be a server to host the web data on. The server would need to be powerful based on the amount of traffic the site might get. For example, when the product is first released and has a small viewer base, the servers needed would not need as much component power as when the site gets more popular.

The more popular the site gets (more traffic) the more servers we would have to implement. This would also entail using better hardware components, such as faster CPUs and larger amounts of DDR SDRAM.

Iwould intend to implement the site and software for users with all different levels of hardware components. Since the site/software is not hardware intensive, most users would be able to use it with non-powerful computers. A system with the ability to run basic software and a web browser should be able to use the product.

Chapter 3-Application Software

Although this service will be primarily online, I intend to implement downloadable software with similar features to the online service. Ideally, this software could work with other current application software. For example, the product could be a plug-in for iTunes. It could look through the user's music library, and create a listing of album release dates, in a calendar form.

The application software could be more powerful than the online services. Features such as a calendar and pop-up reminders would be incentive for the user to download the software, and not just use the product online. The software could be developed for all major operating systems (Windows, Mac, and Linux).

Like I mentioned above, I feel like a plug-in would be an appropriate form for this software. It could be written for programs such as iTunes and Windows Media Player. The software would ideally converse with the program, and use the artist / album data. It would then search the server for information on upcoming albums, and create a graphical interface for the user to view the desired information. Other features would include email reminders, concert dates, and display other artists the user might enjoy (based on all customer data).

Week 2: Internet and WWW

The internet and eCommerce will play a large part in this project. Being a website, it will be accessed by users over the internet. The majority of the services offered will be based over the internet, thus requiring internet connection to access these services.

eCommerce will also play a large part in the product. Although most services are free, there will be a payed service. For a one time fee, users will be able to download a piece of software that will examine their music library. Once examined, the software will interact with the site's database, and will provide a list of information for the user on album release dates and band information (according the music they have on their computer). The software will warn the user when a new album of their liking is going to be released, and will also include a calendar to mark when these releases are. Since the money transactions will be done over the internet, an Authorize.net account will be needed, as well as all the other necessities of online transactions.

The site will follow effective web site strategies. That is, it will be well designed with technology, content, and management in mind.