Instructions: For this assignment, create an original post addressing the topics below prior to midnight ET on Wednesday. Continue to follow your classmates' posts for the remainder of the week and post at two follow-up messages to your classmates' posts prior to midnight ET on Sunday. Your follow-up posts can add additional insight to a classmate's opinions or can challenge their opinions. Use examples from the readings, or from your own research, to support your views, as appropriate. Be sure to read the follow-up posts to your own posts and reply to any questions or requests for clarification. By the way, include the name of the person's post you are replying to. Thanks!Case Study:Layla just got hired as the Web developer for a small business called Axe Grinders, which sells and repairs guitars and amps. The aging rock 'n' rollers who own Axe Grinders were taking care of business by phone and mail, but they just don't have too much time on their hands for this anymore. They decided they need a Web site so they could start processing orders more efficiently, spend their time on guitars, and get the business back in black.These guys know music inside and out, but their guitars gently weep when it comes to Web sites. They don't need no education about the Web, so they hired Layla to do the job for them.Layla's new bosses are same as her old boss. Part of the reason they hired her was because they thought it would be nice to have a pretty woman around the office. Layla doesn't want to be paranoid, but she is determined to prove that she's got brains and she knows how to use them.On her first day, the owners tell Layla that they'd like their site to have some high-voltage effects. And because they have sold guitars to several celebrity musicians, they want a feature that can list their customers along with the guitar types they bought — users could either select a specific customer or guitar, or they could list 'em all. The owners have seen some other sites do something like this, so they know it is possible, but they wonder if she can make it happen. They tell her it is okay if she can't handle this task — it's just another brick in the wall. They could get satisfaction with just a plain HTML site instead, even though it would have to be updated constantly.As she's climbing the stairway to her office, Layla realizes that scripting the Customer List feature will require more than the usual predefined JavaScript objects. And she knows that the code for the Customer List feature will include a lot of repetition. She is determined to make these features work as requested. Layla knows she's got to ramble. Because even though the owners said it would be ok to have a simpler site, she would really like to impress them.Discussion Points:Consider this scenario and answer the following questions.How can Layla use JavaScript custom objects to create the Customer List feature for the Web site?How do custom objects help Web developers with repetitive programming tasks such as the ones in the Customer List feature?What other advantages do custom objects offer to Layla in this situation?What are the first steps Layla should take in creating a custom object for this feature? Forum Rubric: Rubric for Learner PostsPointsSynthesis of concepts in 250 or more words (critical to class performance)30Applications of personal experience20Writing standards10Response to two or more students 150 words or More40Timeliness: (deduction) Optional10 Downloadable Rubric DescriptionPlease use APA formatting and intext cititation Please No Plagiarism

Database case study A school district has three schools. •Each school has its own system to manage records. •The district office wants to centralize record keeping to provide students and parents with access to teacher and student information. •Phased approach: –Phase 1: Teacher contact and Course Assignment information (Note: Course Assignment means homework assignments for a course.) –Phase 2: TBD•Make high level assumptions and come up with the relational tables for Phase 1 •Draw a Conceptual Data Base Model using the notation in slide title “Conceptual Data Base Model” (see slide 24 for an example) •Define the Logical Data Base Model (see slide 25 for an example) •You may omit the Physical Data Base Model

Utilizing the attached Project Requirements, Template and Security Baseline Document. I need a minimum 6 pages to meet the requirements of the rubric below. System Security PlanExcellentOutstandingAcceptableNeeds ImprovementNeeds Significant ImprovementMissing or UnacceptableSections 1 - 8 (System Identification)10 pointsSections 1 - 8 present a thorough and complete identification of the system (Field Office General IT Support), the responsible individuals, and the system status. Key personnel (Section 5) roster contains three or more appropriate designated officials.8.5 pointsSections 1 - 8 identify the system (Field Office General IT Support), the responsible individuals, and the system status. Information was adapted from the Case Study. Key personnel (Section 5) roster contains at least two appropriate designated officials.7 pointsSections 1 - 8 were completed using information from the Case Study. Key personnel (Section 5) roster contains at least one appropriate designated official.6 pointsEntered information for 6 or more sections. Information was incomplete or incorrect.4 pointsCompleted less than 50% of the required information for sections 1-8. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Section 9: System Description / Purpose10 pointsProvided an excellent description of the Field Office General IT Support System. Integrated case study information to describe the business operations supported by the hardware, software, and networks which comprise the "General IT Support" system. Included information about the types and sensitivity of information processed by this system. Described the "smart home" and "Internet of Things" capabilities which are supported by the field office IT systems.8.5 pointsProvided an outstanding description of the Field Office General IT Support System. Integrated case study information to describe the business operations including mention of the types and sensitivity of information processed by this system. Mentioned the "smart home" and "Internet of Things" capabilities which are supported by the field office IT systems.7 pointsProvided an acceptable description of the Field Office General IT Support System. Integrated case study information to describe the business operations, mentioned the types of information processed, and the "smart home" / "Internet of Things" capabilities incorporated into the field offices.6 pointsDescribed the field office business operations supported by the Field Office General IT Support System. The description lacked details.4 pointsAttempted to describe a General IT Support System. Did not integrate information from the case study. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Section 10: System Environment10 pointsProvided an excellent description of the enterprise architecture for the Field Office General IT Support System. Integrated case study information to clearly and accurately describe the hardware, software, and networks which comprise the "General IT Support" system. Included information about the devices and controllers used for the "smart home" and "Internet of Things" capabilities which are used by the field office.8.5 pointsProvided an outstanding description of the enterprise architecture for the Field Office General IT Support System. Integrated case study information to describe the hardware, software, and networks which comprise the "General IT Support" system. Included information about the devices and controllers used for the "smart home" and "Internet of Things" capabilities which are used by the field office.7 pointsProvided an acceptable description of the Field Office General IT Support System. Integrated case study information to describe the business operations, mentioned the types of information processed, and the "smart home" / "Internet of Things" capabilities incorporated into the field offices.6 pointsDescribed the field office business operations supported by the Field Office General IT Support System. The description lacked details.4 pointsAttempted to describe a General IT Support System. Did not integrate information from the case study. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Section 11: System Interconnections / Information Sharing10 pointsUsed information from the case study to identify (name) 5 or more interconnected systems and networks (including the LAN/WAN network connections between the field office and the operations center). Provided an excellent description for each that included the types and sensitivity levels of information transmitted over the connection (e.g. company proprietary information, customer information, public Internet information). Named the "owning" organization and responsible ISSO.8.5 pointsUsed information from the case study to identify (name) 4 or more interconnected systems and networks (including the LAN/WAN network connections between the field office and the operations center). Provided an outstanding description for each that included the types and sensitivity levels of information transmitted over the connection (e.g. company proprietary information, customer information, public Internet information). Named the "owning" organization and responsible ISSO.7 pointsUsed information from the case study to identify (name) 3 or more interconnected systems and networks (including the LAN/WAN network connections between the field office and the operations center). Provided an acceptable description for each. Named the "owning" organization.6 pointsSection identified interconnected systems including the LAN / WAN network connections. Provided some information about the systems and networks.4 pointsSection named LAN / WAN network connections but provided no other information. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Section 12: Related Laws / Regulations / Policies10 pointsProvided an excellent overview of laws, regulations, and policies which establish specific requirements for the confidentiality, integrity, and availability of the data collected, processed, and/or stored in the Field Office General IT Support System. Named and described the applicability of 5 or more federal or state laws and regulations. Identified and described at least one internal policy which applies to the use of this system.8.5 pointsProvided an outstanding overview of laws, regulations, and policies which establish specific requirements for the confidentiality, integrity, and availability of the data collected, processed, and/or stored in the Field Office General IT Support System. Named and described the applicability of 4 or more federal or state laws and regulations. Identified and described at least one internal policy which applies to the use of this system.7 pointsProvided an acceptable list of laws, regulations, and policies which establish specific requirements for the confidentiality, integrity, and availability of the data collected, processed, and/or stored in the Field Office General IT Support System. Named and described the applicability of 3 or more federal or state laws and regulations. Identified and described at least one internal policy which applies to the use of this system.6 pointsNamed and described at least three legal (laws), regulatory (regulations or "rules"), and/or policy sources for security requirements which apply to the Field Office IT General Support System.4 pointsNamed at least two laws, regulations, and/or policies as sources of security requirements for the Field Office IT General Support System. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Section 13: Introduction for Minimum Security Controls5 pointsProvided an excellent introduction for Section 13: Minimum Security Controls. Discussed the differences between management, operational, and technical categories of security controls. Used information from the case study and NIST SP 800-53.4 pointsProvided an outstanding introduction for Section 13: Minimum security controls. Discussed the use of management, operational, and technical categories of security controls. Used information from the case study and NIST SP 800-53.3 pointsProvided an acceptable introduction for Section 13: Minimum Security Controls. Mentioned the three categories (management, operational, technical). Used information from the case study and NIST SP 800-53.2 pointsProvided an introduction for Section 13: Minimum Security Controls. Introduction used information from the case study but lacked important details.1 pointProvided an introduction for section 13. Did not customize the introduction for the case study. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Section 13 (a) Minimum Security Controls: Management Controls Category10 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. CA) listed under the "management controls" category (in the baseline) using information from NIST SP 800-53. For each "family" listed in the baseline under this category, identified (listed) the specific controls (e.g. CA-1) and provided a excellent description of how the controls in each family work together to mitigate threats and vulnerabilities.8.5 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. CA) listed under the "management controls" category (in the baseline) using information from NIST SP 800-53. For each "family" listed in the baseline under this category, identified (listed) the specific controls (e.g. CA-1) and provided an outstanding description of how the controls in each family work together to mitigate threats and vulnerabilities.7 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. CA) listed under the "management controls" category (in the baseline) using information from NIST SP 800-53. Provided a brief description of how the controls in each family work together to mitigate threats and vulnerabilities.6 pointsListed and described three or more management controls (from NIST SP 800-53) which should be implemented for the Field Office IT General Support System.4 pointsListed and described one or more management controls (from NIST SP 800-53) which should be implemented for the Field Office IT General Support System.0 pointsInsufficient, missing, or no work submitted.Section 13 (b) Minimum Security Controls: Operational Controls Category10 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. AT) listed under the "operational controls" category (in the baseline) using information from NIST SP 800-53. For each "family" listed in the baseline under this category, identified (listed) the specific controls (e.g. AT-1) and provided a excellent description of how the controls in each family work together to mitigate threats and vulnerabilities.8.5 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. AT) listed under the "operational controls" category (in the baseline) using information from NIST SP 800-53. For each "family" listed in the baseline under this category, identified (listed) the specific controls (e.g. AT-1) and provided an outstanding description of how the controls in each family work together to mitigate threats and vulnerabilities.7 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. AT) listed under the "operational controls" category (in the baseline) using information from NIST SP 800-53. Provided a brief description of how the controls in each family work together to mitigate threats and vulnerabilities.6 pointsListed and described three or more operational controls (from NIST SP 800-53) which should be implemented for the Field Office IT General Support System.4 pointsListed and described one or more operational controls (from NIST SP 800-53) which should be implemented for the Field Office IT General Support System. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Section 13 (c) Minimum Security Controls: Technical Controls Category10 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. AC) listed under the "technical controls" category (in the baseline) using information from NIST SP 800-53. For each "family" listed in the baseline under this category, identified (listed) the specific controls (e.g. AC-1) and provided a excellent description of how the controls in each family work together to mitigate threats and vulnerabilities.8.5 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. AC) listed under the "technical controls" category (in the baseline) using information from NIST SP 800-53. For each "family" listed in the baseline under this category, identified (listed) the specific controls (e.g. AC-1) and provided an outstanding description of how the controls in each family work together to mitigate threats and vulnerabilities.7 pointsUsed the provided security controls baseline for the case study company. Named and described each of the required control families (e.g. AC) listed under the "technical controls" category (in the baseline) using information from NIST SP 800-53. Provided a brief description of how the controls in each family work together to mitigate threats and vulnerabilities.6 pointsListed and described three or more technical controls (from NIST SP 800-53) which should be implemented for the Field Office IT General Support System.4 pointsListed and described one or more technical controls (from NIST SP 800-53) which should be implemented for the Field Office IT General Support System. (Or, inappropriate or excessive copying from other authors' work.)0 pointsInsufficient, missing, or no work submitted.Sections 14-15: Completion & Approval Dates5 pointsIncluded both sections from the template file (14 & 15) and entered the completion date for the plan.3 pointsIncluded section 14 from the template file and entered a completion date for the plan.0 pointsN/A0 pointsN/A0 pointsN/A0 pointsInsufficient, missing, or no work submitted.ProfessionalismExcellentOutstandingAcceptableNeeds ImprovementNeeds Significant ImprovementMissing or UnacceptableExecution10 pointsWork is professional in appearance and organization (appropriate and consistent use of fonts, headings, color). No word usage, grammar, spelling, or punctuation errors. All quotations (copied text) are properly marked and cited using a professional format (APA format recommended but not required.)8.5 pointsWork is professional in appearance and organization (appropriate and consistent use of fonts, headings, color). Work contains minor errors in word usage,grammar, spelling or punctuation which do not significantly impact professional appearance. All quotations (copied text) are properly marked and cited using a professional format (APA format recommended but not required.)7 pointsWork is professional in appearance and organization (minor issues allowable but overall the work contains appropriate and consistent use of fonts, headings, color). Errors in word usage, spelling, grammar, or punctuation which detract from professional appearance of the submitted work. All quotations (copied text) are properly marked and cited using a professional format (APA format recommended but not required.)6 pointsSubmitted work has numerous errors in formatting, organization, word usage, spelling, grammar, or punctuation which detract from readability and professional appearance. Punctuation errors may include failure to properly mark quoted or copied material (an attempt to name original source is required).4 pointsSubmitted work is difficult to read / understand and has significant errors in formatting, appearance / organization, spelling, grammar, punctuation, or word usage. Significant errors in presentation of copied text (lacks proper punctuation and failed to attribute material to original source).0 pointsNo work submitted. OR, work contains significant instances of cut-and-paste without proper citing / attribution to the original work or author.Overall ScoreExcellent90 or moreOutstanding80 or moreAcceptable70 or moreNeeds Improvement56 or moreNeeds Significant Improvement36 or moreMissing or Unacceptable Work0 or more