I need basic website Programming Assignment Help

there is fail attached is describing everything

completing my project under this proposal:

Hurricanes inflict billions of dollars in economic damages throughout the United States. The potential for long-term effects becomes evident in various cases throughout the United States history dealing with such damaging effects caused from hurricanes. Such economic tolls display storm surges throughout the Atlantic coast while wreaking a havoc of tourism and agriculture industries being hit the hardest (Smith III, T. J., 2009). These hurricanes damage a lot more properties from the flooding that is left behind. Coastline storms are of the greatest hurricane occurrences and thus, causes the most economic damages done to the surrounding and impacted economies (Smith III, T. J., 2009). Hurricanes are feared along the Atlantic coasts, such as surrounding areas of Florida, while Florida has been hit the hardest from the most damaging and recent hurricane occurrences.

Physical harm in family units, business premises, and open framework will cost the US monetary state up to $30 billion. A few structures have been pulverized and additionally streets, rails, and sewage and water frameworks. Control blackouts have additionally been far reaching in affected regions because of devastation of electrical cables (Sinigalliano, C. D., 2007). To decrease the tropical storm’s negative effect, Americans are encouraged to take preventive measures against physical harms. They should guarantee that they know their environment. For instance, they should distinguish close-by dams and levees that may represent a peril and move things to more secure spots. Individuals are likewise asked to know the rise level of their property with a specific end goal to keep things at danger of harm in safe spots (Sinigalliano, C. D., 2007).

For a considerable length of time financial analysts have talked about whether ruinous tempests are even terrible for a nation’s economy. To a non-financial expert, the evil impacts of a tempest may appear to be natural, however market analysts have a talent for finding conceivable irrational clarifications. With regards to a noteworthy cataclysmic event, they had four contending speculations: Such a debacle may forever set a nation back; it may briefly crash development just to get back on course not far off; it may prompt much more prominent development, as new venture pours into supplant demolished resources; or, perhaps, it may yet far and away superior, invigorating development as well as freeing the nation of whatever obsolete framework was keeping it down (Sinigalliano, C. D., 2007).

References

Smith III, T. J., Anderson, G. H., Balentine, K., Tiling, G., Ward, G. A., & Whelan, K. R. (2009). Cumulative impacts of hurricanes on Florida mangrove ecosystems: sediment deposition, storm surges and vegetation. Wetlands, 29(1), 24-34.

Sinigalliano, C. D., Gidley, M. L., Shibata, T., Whitman, D., Dixon, T. H., Laws, E., … & Gast, R. J. (2007). Impacts of Hurricanes Katrina and Rita on the microbial landscape of the New Orleans area. Proceedings of the National Academy of Sciences, 104(21), 9029-9034.

For our purposes, Reading Responses are focused responses to the assigned reading. These responses are the most important means for practicing and developing your ability to read and think critically. You will generally write one response each week. These responses should be typed, double-spaced, and at least one page in length. These are like journal entries relating how students respond to their reading.

How did the reading make you think and feel? Of what did the reading remind you? How can you relate the reading to your other classes? Or your current life situations? Or history? Try to make these relatively informal but still academic. Do not give me summaries! Some of the response may quote excerpts of the reading, but keep the quotes short. And make sure to use proper formatting for quotes.

Good Luck!

Based on your team’s Week Four Learning Team Collaborative discussion, write the Access Control Policy section of the Information Security Policy. Include the following:

• User enrollment
• Identification
• Authentication
• Privileged and special account access
• Remote access

Format according to APA guidelines. I fully expect that this and all assignments related to the creation of the Security Policy document will be fully researched with all references cited with proper APA formating. I fully expect to see a reference section with an indication that you researched the information for this section.

I will attach the first two assignments. They all need to flow together and be coherent. The company is Apple

See the Resources area for links to resources that you will use for this assignment:

• You will complete this assignment using the DAA Template.
• Read the SPSS Data Analysis Report Guidelines for a more complete understanding of the DAA Template and how to format and organize your assignment.
• Refer to the IBM SPSS Step-By-Step Guide: t Tests for additional information on using SPSS for this assignment.
• If necessary, review the Copy/Export Output Instructions to refresh your memory on how to perform these tasks. As with your previous assignments, your submission should be in narrative format with supporting statistical output (table and graphs) integrated into the narrative in the appropriate places (not all at the end of the document).

You will analyze the following variables in the grades.sav data set:

• gender
• gpa

Step 1: Write Section 1 of the DAA.

• Provide the context of the grades.sav data set.
• Include a definition of the specified variables (predictor, outcome) and corresponding scales of measurement.
• Specify the sample size of the data set.

Step 2: Write Section 2 of the DAA.

• Analyze the assumptions of the t test.
• Paste the SPSS histogram output for gpa and discuss your visual interpretations.
• Paste SPSS descriptives output showing skewness and kurtosis values for gpa and interpret them.
• Paste SPSS output for the Shapiro-Wilk test of gpa and interpret it.
• Report the results of the Levene test and interpret it.
• Summarize whether or not the assumptions of the t test are met.

Step 3: Write Section 3 of the DAA.

• Specify a research question related to gender and gpa.
• Articulate the null hypothesis and alternative hypothesis.
• Specify the alpha level.

Step 4: Write Section 4 of the DAA.

• Paste the SPSS output of the t test.
• Report the results of the SPSS output using proper APA guidelines (refer to the Unit 8 Introduction and the “Results” example from the Warner text in Chapter 5). Include the following:
  • t.
  • Degrees of freedom.
  • p value.
  • Effect size.
  • Interpretation of effect size.
  • Means and standard deviations for each group.
  • Mean difference.
  • 95% confidence interval of the difference of sample means.
• Interpret the results against the null hypothesis.

Step 5: Write Section 5 of the DAA.

• Discuss the implications of this t test as it relates to the research question.
• Conclude with an analysis of the strengths and limitations of the t test.

Submit your DAA Template as an attached Word document in the assignment area

Using Microsoft PowerPoint, create a timeline, beginning in the 1960s, to demonstrate the specific changes that led to today’s paradigm of local policing. The timeline should include the following:

• A description of the significant changes that occurred in local policing strategy, including the years in which these developments took place.
• A description of crime conditions that led to such changes.
• An explanation of other factors that increased the perceived need for those changes in law enforcement strategy. For instance, the cultural workforce, technology, social issues, etc.
• An analysis of how the present state of police and law enforcement will impact the future of law enforcement. In what ways do you think community policing can be made more effective?
• What other changes are required in law enforcement to prevent and reduce crime?
• In what ways do you predict policing will change in the near future? Support your prediction.

Psychologists have identified five main personality traits, often called the “Big Five” or the five-trait model. Think about the “Big Five” personality traits we studied in class. Then select a real or fictional character from literature, film, television, or public life. How could the “Big Five” model be used to understand the character’s personality?

In a multi-paragraph essay, explain what is meant by a “personality trait” according to the “Big Five” model, define each of the “Big Five” traits, and describe the character’s personality using the “Big Five” traits. For each trait, be sure to provide evidence from the character’s thoughts, emotions, and behavior. Include details from class materials, readings, and research on personality to support your discussion.

Mutex Locks or Semaphores in Shared Memory
Last one of the semester. Let’s combine what we did in program #4 and program #5 and show, and then prevent, a race condition between processes rather than threads. Start with your code from program #5 but instead of simply putting an integer in shared memory, use a structure like the one that you used in program #4 to represent a 2-dimensional Cartesian point having two integer coordinates called x and y. Instead of communicating between parent and child by simply updating the integer with a user supplied value (as you did in program #5), update the racePoint coordinates as we did in program #4 (no user interaction necessary), which will create critical sections and then,as in program #4, use a stupidly placed sleep(1) call to simulate a random preemption causing a genuine race condition. Here, of course, we’ll have a race condition between two processes (over a shared resource in shared memory) rather than between two threads of the same process. Finally, just as in program #4, add entry and exit sections with a synchronization mechanism (semaphore, binary semaphore or mutex lock, whatever worked for you previously) to protect your critical sections and prevent the race condition.
Couple of notes:
A. Since both the parent and the child process obviously (I sure hope it’s obvious by now) need to use the same semaphore or mutex lock, it too will have to be in shared memory, no? Now I suppose you could just create a second shared memory segment for that; but that seems to me pretty inefficient. Instead, since a structure in C can contain other structures, why not put both the racePoint and the semaphore/mutex that will protect it inside a single structure and then create the shared memory to hold the “outer” structure containing the two “inner” structures your processes need to share access to; that way you don’t need an extra shmget, shmat, etc.
B. Remember that semaphores, mutex locks, and such like have to be initialized before they can be used. In program #4, where the semaphore or mutex lock was simply declared as a global variable, that initialization could be done in the declaration itself and many of you did. I myself, for example, used the following line to declare and initialize a POSIX mutex lock named demoLock:
pthread_mutex_t demoLock = PTHREAD_MUTEX_INITIALIZER;
where PTHREAD_MUTEX_INITIALIZER is #defined in one of the header files as as a set of the appropriate constants inside squiggly brackets, e.g., { …, …} That wouldn’t work here, since the the memory for the synchronization structure is being obtained dynamically (via the shmget) rather than by a simple compile-time declaration, as in my example just above. So here in this program, you’ll need to use some additional system service calls from the pthread library to initialize your mutex lock correctly.
Conceptually there’s not much new here. Aside from the half a dozen extra lines or so to get the mutx lock initialized properly, there’s not much new code to be written; you’re just mixing and matching stuff from programs #4 and #5 with a couple of fairly minor changes. But the changes involve handling pointers to components of structures inside dynamically allocated structures, which requires careful coding, so I think this program, as do most interesting programs, really begs for “build-a-little, test-a-little”. You’re obviously not required to proceed via the same sequence of stepwise refinements that I used (from the requirements engineering standpoint, that’s not a testable requirement 😉 but here’s roughly how I did it (compiling and executing after each step):
1. Start from program #5 (the process program, not the thread one) but change the integer in shared memory to the racePoint structure from program #4 and do the spinning/communicating on just the x component, ignoring the y component completely here in the beginning (we’ll use it later though). This step just ensures our code can create and properly access a dynamically allocated C structure (not just an integer) located in shared memory.

a. In program #4, the structure, racePoint, was simply a global variable of an anonymous structured type:
struct { int x, y; } racePoint={0,0};
Here, of course, it has to be placed in shared memory so you’ll need to give the structure definition a name, vis struct point { int x, y; }; so that you can refer to sizeof(struct point) when requesting your shared memory from shmget.

b. Note that I removed the variable declaration for racePoint. Here, we don’t want to allocate storage for racePoint when we define struct point; we just want to define the struct point data type so that storage for the one we need can be dynamically allocated later, during execution, with a shmget call. If you also declare a variable at this point in your code (the compiler wouldn’t care, now would it?), you might easily get confused later and refer to it (the totally unnecessary local variable) rather than the dynamically created one in shared memory, with the result that you’ll manipulate the wrong variable and your code won’t work as intended.

2. After attaching to the shared memory as we did in program #5, set both the x and y coordinates of the shared point to 0 Note that we’ll have to refer to the coordinates by pointer rather than by the name of the structure; e.g., racePointPtr->x, rather than racePoint.x, where racePointPtr contains the address we get when we do the shmat.

3. fork() a child process.

a. In the code executed by the parent process after the fork():
i. Take out the code from program #4 that requests user input and then spins until the child resets the integer.

ii. Replace it with the code for a critical section by copying the 3 lines from the critical section of the main thread of program #4 (suitably modified, as per item #2, above):

1. First, set the x coordinate to 1.

2. Then make a call to sleep(1) to simulate random preemption of the process.

3. Then set the y coordinate to 1 (modifying the copied code to refer to both x and y by pointer).

iii. Last thing in the parent code (after the critical section), print out the values of x and y so we can see if we got the race condition.

b. In the child code, insert a line that spins while the x coordinate is 0 — so the child doesn’t try to enter its critical section too soon, before the parent process even executes after the fork (At this point, we’re trying to force a race condition and if the child gets completely through its critical sectrion before the parent even enters its, we won’t get one.) Next (still in the child code) put in the two line critical section that sets the x and y coordinates to 2.

At this point, when you compile and execute your code you should see the simulated race condition: x will end up 2 while y will be 1.

4. Put the definition of the race point structure inside an outer structure of some sort, called something stunningly original like sharedData or whatever name your sense of programming style deems appropriate:
struct sharedData
{
struct point
{
int x, y;
} racePoint;
};
This outer structure is where, in the next step, we’ll also place the mutex mechanism we’ll need, but for now (build-a-little, test-a-little) just make the necessary modifications to show that your code can still access x and y properly now that they’re inside an inner structure that’s inside an outer structure — and remember to alter your shmget to request enough storage for the outer structure, e.g., sizeof(struct sharedData), or whatever you name your outer structure

 Helpful hint: If you saved the address returned by the shmat in a variable named, say, sharedMemoryPtr, you’d now need to refer to the x coordinate as (sharedMemoryPtr->racePoint).x sharedMemoryPtr points to the outer structure; sharedMemoryPtr->racePoint designates the component of the outer structure named racePoint, which is itself a structure. So (sharedMemoryPtr->racePoint).x refers to the x component of the inner structure.

 Irrelevant aside on programming style: (sharedMemoryPtr->racePoint).x can be written without the parentheses as sharedMemoryPtr->racePoint.x and the compiler will do the right thing, but I think that’s poor style. It forces you or your readers to think explicitly about the precedence or association order of the operators involved. Better to use parentheses and make your intentions clear.

 Note that I had to put the name racePoint back in when I defined struct point, but here it’s not the name of a variable being declared (as it was in program #4) but the name of a structured component in the definition of the structured sharedData type. Components or fields have to have names, no?

Anyway, compile and execute again; you should still see the race condition. Save this version of code somewhere; it’s one of two versions you’ll turn in for this assignment.

5. Now put your definition of your synchronization structure inside the definition of the outer structure and add your call to initialize it somewhere before the fork(). I found it helpful to save and check the value returned by the initialization call (see my examples on using perror or strerror) since it’s all too easy at this point to write code that the compiler accepts but still have the OS nonetheless reject the system service call since it didn’t like the address you sent it. You can waste a lot of time trying to figure out why your program doesn’t work if you assume that just because the compiler buys off on the data types you use as arguments to system service calls and your program executes without blowing up that therefore the OS is actually doing what you are asking it to. That’s why system service calls return success/failure values and what perror is for. Compile and execute again to make sure you haven’t screwed anything up; although you still won’t have fixed the race condition yet.

 Programming hint: While it’s never a good idea to ignore warnings from the compiler (as opposed to errors, which, of course, can’t be ignored), when working with complex pointer accesses it is particularly vital to not ignore warnings. If the compiler thinks you’re pointing to the wrong type of thing, even though that’s only a warning, not an error, it is very unlikely that your system service calls will work correctly even though they may not notice an error. When you tell a system service call to initialize something, for example, all it knows is the address of the