CSS is a language used to define the look and structure of HTML pages. In this Application, you will add CSS to your website. You will create a CSS file that specifies various parameters about the look of your website and then update two individual webpages to reference that CSS file. Remember, if a change is made to the CSS file, it will affect the look of every page on your website that references that CSS file.

Perform the following steps:

Create two HTML pages that will be added to your website created in the previous week. Name the new pages week3a.html and week3b.html.

Create a CSS file by using a text editor. You may use TextEdit or Notepad, if you are using a Windows computer, or TextEdit, if you are using a Mac system.
 

The CSS file should contain at least three styles and two classes. Try to make these styles and classes easily visible and distinguishable from plain text and from each other.
 

On a Windows computer, select “Save as type: All Files” when saving your Notepad files, and save the files with the “.css” extension.

On a Mac system, save the TextEdit document with the “.css” extension.
 

Update week3a.html and week3b.html to reference the CSS file and use all the styles and classes defined therein.

Provide a link from your homepage, index.html, to both of the newly created HTML files: week3a.html and week3b.html.

Finally, publish your work by uploading the new and modified files to your web host.

Validate your pages by pasting the CSS codes into http://jigsaw.w3.org/css-validator/ to ensure that no CSS syntax errors are detected. Take screenshots of the validation results and paste them into an MS Word document. In the MS Word document, include your explanations of what functionality you have coded in the CSS, how it is being applied to the week3a.html and week3b.html pages, and thoughts about what CSS file(s) could be appropriate to develop to make the website of Week 2 attractive with a uniform look.

Finally, publish your work by uploading the Week 3 pages and CSS file to your web host; be sure that the CSS file is properly referenced in each of the Week 3 pages and include the valid URL to the location of your website index.html home page on the web hosting server. (Remember that the index.html page needs to be updated to enable navigation to the Week 3 webpages.)

Compile your website files into a single .zip file, including the MS Word document, and submit the .zip file as your deliverable. Name the .zip file.

I PowerPoint Presentation

Review different available BI tools and choose one to investigate in detail.

• Create a PowerPoint Presentation summarizing the tool and include the following details:
  • What is the purpose of the tool?
  • What features does the tool have?
  • What industries benefit most from this type of tool?
  • What similar tools are available from competing BI solution provides?
• The rubric for this assignment can be viewed when clicking on the assignment link.

Video:

Watch VideoWhat is a Key Performance Indicator (KPI)?Duration: (4:32)
User: CreativeLive – Added: 8/12/13 

Businesses today are extremely reliant on large amounts of data for making intelligent business decisions. Likewise, the data warehouses are often structured in a manner that optimizes processing large amounts of data.

Write a two to three (6-7) page paper in which you:

1. Outline the main differences between the structure of a relational database optimized for online transactions versus a data warehouse optimized for processing and summarizing large amounts of data.
2. Outline the main differences between database requirements for operational data and for decision support data.
3. Describe four (4) examples in which databases could be used to support decision making in a large organizational environment.
4. Describe four (4) examples in which data warehouses and data mining could be used to support data processing and trend analysis in large organizational environment.
5. Use at least five (5) quality resources in this assignment. Note: Wikipedia and similar Websites do not qualify as quality resources.

The assignment must follow these formatting requirements:

• Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA. 
• Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length. 

 I need a Broadcasting chat server Project in Java

1. Proposal/Requirements document–The proposal document shall clearly describe the planned final project’s end product. This document shall be produced using Microsoft Word (it should contain graphics, images, or tables produced using other applications). It must be written using complete English sentences and have been spell- and grammar-checked. The document must unambiguously describe what the proposed system will do (in other words, its requirements). Any performance requirements (e.g., response time to a keypress) must be documented in the proposal document. The document must also include the following topics: Working title of project, purpose of the project, platform (e.g., Windows, Mac, iOS), intended customer/user (that is, who is the program for?), source of the idea for the project, development environment and/or tools to be used, development language(s), limitations or risks anticipated, schedule (built around the course milestones), estimated number of lines of code, documentation, user training, delivery/installation plan. The document should also include anything not mentioned above that will be relevant or helpful when evaluating the proposal. Use the checklist in section 3.4 of the text (checklist begins on p. 42) as you prepare your requirements; you MUST cover all of these items in your document. A typical proposal/requirements document will be 5-10 pages in length.

Checklist: Requirements

The requirements checklist contains a list of questions to ask yourself about

your project’s requirements. This book doesn’t tell you how to do good requirements

development, and the list won’t tell you how to do one either. Use the list

as a sanity check at construction time to determine how solid the ground that

you’re standing on is—where you are on the requirements Richter scale.

Not all of the checklist questions will apply to your project. If you’re working on

an informal project, you’ll find some that you don’t even need to think about.

You’ll find others that you need to think about but don’t need to answer formally.

If you’re working on a large, formal project, however, you may need to

consider every one.

Specific Functional Requirements

❑ Are all the inputs to the system specified, including their source, accuracy,

range of values, and frequency?

❑ Are all the outputs from the system specified, including their destination,

accuracy, range of values, frequency, and format?

❑ Are all output formats specified for Web pages, reports, and so on?

❑ Are all the external hardware and software interfaces specified?

❑ Are all the external communication interfaces specified, including handshaking,

error-checking, and communication protocols?

❑ Are all the tasks the user wants to perform specified?

❑ Is the data used in each task and the data resulting from each task specified?

Specific Nonfunctional (Quality) Requirements

❑ Is the expected response time, from the user’s point of view, specified for

all necessary operations?

❑ Are other timing considerations specified, such as processing time, datatransfer

rate, and system throughput?

❑ Is the level of security specified?

❑ Is the reliability specified, including the consequences of software failure,

the vital information that needs to be protected from failure, and the strategy

for error detection and recovery?

❑ Are minimum machine memory and free disk space specified?

❑ Is the maintainability of the system specified, including its ability to adapt

to changes in specific functionality, changes in the operating environment,

and changes in its interfaces with other software?

❑ Is the definition of success included? Of failure?

Requirements Quality

❑ Are the requirements written in the user’s language? Do the users think

so?

❑ Does each requirement avoid conflicts with other requirements?

❑ Are acceptable tradeoffs between competing attributes specified—for

example, between robustness and correctness?

❑ Do the requirements avoid specifying the design?

❑ Are the requirements at a fairly consistent level of detail? Should any

requirement be specified in more detail? Should any requirement be specified

in less detail?

❑ Are the requirements clear enough to be turned over to an independent

group for construction and still be understood? Do the developers think

so?

❑ Is each item relevant to the problem and its solution? Can each item be

traced to its origin in the problem environment?

❑ Is each requirement testable? Will it be possible for independent testing to

determine whether each requirement has been satisfied?

❑ Are all possible changes to the requirements specified, including the likelihood

of each change?

Requirements Completeness

❑ Where information isn’t available before development begins, are the

areas of incompleteness specified?

❑ Are the requirements complete in the sense that if the product satisfies

every requirement, it will be acceptable?

❑ Are you comfortable with all the requirements? Have you eliminated

requirements that are impossible to implement and included just to

appease your customer or your boss?

video link:

pages content:

first paragraph:  Introduction (definition of Occam’s Razor).

second paragraph: summarize the movie

third paragraph: the relationship between Occam’s Razor and Data Mining.

fourth paragraph: What do you notice from the movie! (three points)

References.

2 pages exclude student name page and references page

– font(times new roman(12))