Showing posts with label behaviour. Show all posts
Showing posts with label behaviour. Show all posts

Tuesday, 15 September 2020

Final Project Guidelines and Rubric

UK assignment helper

 






IT 412: Final Project Guidelines and Rubric 

Overview There are two components to the final project for this course. The first component is a risk analysis paper. The second component is a risk mitigation plan presentation to stakeholders that illustrates an organization’s regulatory position related to a given scenario. This project is divided into two milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final submissions. These milestones will be submitted in Modules Three and Five. The final product will be submitted in Module Seven. 

 

In this assignment, you will demonstrate your mastery of the following course outcomes: 

 

 Evaluate federal, regional, and state cyberlaws and ethics regulations for their impact on organizations’ IT and computing policies and operations  Assess personal and professional ethical violations for the extent to which they impact IT and computing within organizations  Recommend policies and strategies that align with cyberlaw and ethics guidelines for facilitating compliance and addressing non-adherence  Utilize cyberlaw and ethics guidelines in creating IT-specific codes of ethics for mitigating stakeholder and organizational risk 

 

Scenario ABC Healthcare is a startup company with 50 employees. The company’s computer network is shown in Figure 1 below. The healthcare data server contains the company's records, including copies of patient health records with personally identifiable data, patient billing, company financials, and forms. 

 

You have been hired as the IT network security officer, reporting directly to the chief information officer (CIO). Currently, there is a network administrator who has very limited experience and worked as a desktop technician prior to joining ABC. This network administrator helped set up the existing network. In addition, ABC plans to hire a desktop technician and a website developer/programmer who will report directly to the CIO. 

 

There are no policies or guidelines for employees’ usage of the computers and network. Network setup was done by various vendors, and all of the programs use default usernames and passwords. Wireless access has been set up for staff using wireless laptops. The same wireless access point also provides clients access to the internet. Some staff members bring in their own computers and connect them to the network. Employees use the work systems for personal web browsing and to check personal email accounts. 

 

As part of network security, management set up a video monitoring system throughout the office. Employees are not notified of any monitoring. 

There is a copier/printer in the front office that is used by employees. Currently, all unused copies are left next to the copier for recycling. 


 

 

 

 

Figure 1 

 

The administration office room uses an open cubicle structure for its staff. Figure 2 depicts the cubicles and seating of its sta f. Staff members sometimes complain that they can hear each other during the work day. 


 

 

 

Figure 2 

 

 

Prompt Create a comprehensive risk analysis narrative in which you assess ABC Healthcare’s information systems for ethics violations and cyberlaw compliance, and research the framework for creating an acceptable use-of-technology policy and code of ethics. 

 

Next, using PowerPoint, Google Presentation, or Prezi, create a presentation in which you recommend appropriate strategies for remediating the instances of ethics violations and cyberlaw noncompliance you identified in your risk analysis. Propose an organizational code of ethics related to information technology that prevents future violations and noncompliance, and propose an acceptable use-of-technology policy that addresses non-adherence. 


 

 

Specifically, the following critical elements must be addressed: 

 

I. Risk Analysis Paper 1. Describe the information technology structure of the organization in the given scenario. 2. Identify specific cyberlaws and ethics regulations that pertain to the organization and its computing operations in the scenario. 3. Organizational ethics violations i. Classify unethical behaviors with respect to whether they are personal or professional in nature, being sure to support your position with specific examples. ii. Assess the impact of the unethical behaviors on IT and computing within the organization. 4. Cyberlaw noncompliance i. Identify instances of cyberlaw noncompliance, being sure to cite the specific regulation(s) being violated. ii. Assess the impact of the noncompliance on IT and computing within the organization. 5. Acceptable use-of-technology policies research i. Compare and contrast acceptable use-of-technology policies from various organizations. You can find suggested organizations below or use policies of your own choosing. ii. Select aspects of the acceptable use-of-technology policies you have researched that you feel could be adapted to meet the needs of the organization, and explain how you would adapt them. 6. Codes of ethics research i. Compare and contrast IT-specific codes of ethics from various organizations. You can find suggested organizations below or use codes of ethics of your own choosing. ii. Select aspects of the codes of ethics you have researched that you feel could be adapted to meet the needs of the organization, and explain how you would adapt them. 

 

IT Acceptable Use Policies 

 

There are many areas within the field of IT, and each area’s policies may vary based on specialization. IT does not have one rule-making body as other professions do. IT does, however, have many professional organizations that represent different specializations, such as security, operations management, and computing technology. 

 

SANS Institute Acceptable Use Policy ISSA Acceptable Use Policy Pennsylvania College of Technology IT Acceptable Use Policy AT&T Acceptable Use Policy 


 

 

IT Codes of Ethics 

 

Professional organizations provide codes of ethics that may vary slightly, depending on specialization. A code of ethics may also be provided by a business or educational organization. 

 

SANS Institute IT Code of Ethics ISSA Code of Ethics  K-State Information Technology Employee Code of Ethics 

 

Business Codes of Ethics 

 

AT&T Code of Ethics Microsoft Standards of Business Conduct 

 

 

II. Risk Mitigation Plan Presentation: Based on your research, you will create a multimedia presentation (suggested length of 5–10 slides) using a tool of your choice (for example, PowerPoint, Google Presentation, or Prezi). Your audience for this presentation is the organization’s management. This presentation will provide a brief overview of the issues you identified in your risk analysis and present your recommendations for addressing the problems identified in your analysis. The presentation must include the following elements: 

 

o Provide an overview of the issues you identified in your risk analysis. In other words, what were the unethical behaviors and instances of cyberlaw noncompliance? o Propose appropriate strategies that remediate the identified ethics violations and cyberlaw noncompliance. What can the organization do now to address the issues you have identified? o Recommend, based on your research, a brief list of appropriate policy statements that address acceptable use in facilitating future compliance and addressing non-adherence. In other words, how can the organization prevent the same or similar problem(s) in the future? o Recommend, based on your research, a brief IT-specific code of ethics that mitigates the risk of future instances of violation and noncompliance. In other words, how can the organization prevent the same or similar problem(s) in the future? 

 

Guidelines for Presentation: Your final presentation can be submitted in PowerPoint, Google Presentation, or Prezi format. 

 

 You can find various template designs on the internet for your presentation. Prior to selecting a specific style, consider your presentation from the perspective of your audience. Avoid distractions. Be consistent with the style of text, bullets, and sub-points to support a powerful presentation that allows your content to be the focus. 


 

 

 Each slide should include your key point(s). Do not place large blocks of text on the visuals. Add more extensive information in the presenter notes section.  Use clip art, AutoShapes, pictures, charts, tables, and diagrams to enhance, but not overwhelm, your content.  Be mindful of your intended audience. 

 

Below are links that offer helpful tips and examples for developing your presentation: 

 

 Making PowerPoint Slides  Beyond Bullet Points: The Better Way to Use PowerPoint  Really Bad PowerPoint and How to Avoid It 

 

 

 

Milestone One: Draft of Risk Analysis Paper, Sections 1–3 

Milestones 

In Module Three, you will submit a draft of Section 1: Information Technology Structure, Section 2: Cyberlaws and Ethic Regulations, and Section 3: Ethics Violations. This milestone will be graded using the Milestone One Rubric. 

 

Milestone Two: Draft of Risk Analysis Paper, Sections 4–5 In Module Five, you will submit a draft of Section 4: Cyberlaw Noncompliance and Section 5: Acceptable Use Policies of the risk analysis paper. This milestone will be graded using the Milestone Two Rubric. 

 

Final Submission: Risk Analysis Paper and Risk Mitigation Plan Presentation In Module Seven, you will submit the final risk analysis paper and the risk mitigation plan presentation. These should be complete, polished artifacts containing  all of the critical elements of the final product. They should reflect the incorporation of feedback gained throughout the course. This submission will be graded using the Final Project Rubric. 


 

 

Final Project Rubric Guidelines for Submission: Written components of this project must follow these formatting guidelines: double spacing, 12-point Times New Roman font, one- inch margins, and discipline-appropriate citations. The risk analysis paper should be 10–15 pages in length, and the risk mitigation presentation should have 5–10 slides. 

 

 

Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value Paper: Information Technology Structure Meets “Proficient” criteria and uses industry-specific language to establish expertise Comprehensively describes the information technology structure of the organization in the scenario Describes the information technology structure of the organization in the scenario, but description is inaccurate or lacks detail Does not describe the information technology structure of the organization in the scenario 5 Paper: Cyberlaws and Ethics Regulations Meets “Proficient” criteria and provides specific examples from similar organizations encountered during research Identifies specific cyberlaws and ethics regulations that pertain to the organization and its computing operations Identifies specific cyberlaws and ethics regulations but does not connect them to the organization and its computing operations Does not identify specific cyberlaws and ethics regulations 7 Paper: Ethics Violations: Personal or Professional Meets “Proficient” criteria, and examination includes harm caused by unethical behaviors Accurately classifies unethical behaviors as personal or professional in nature and supports position with specific examples Classifies unethical behaviors inaccurately, or does not support position with specific examples Does not classify unethical behaviors as personal or professional in nature 7 Paper: Ethics Violations: Impact Meets “Proficient” criteria and expands on the impact beyond immediate internal stakeholders Assesses the impact of unethical behaviors on IT and computing within the organization Assesses the impact of unethical behaviors but does not connect them to the organization, or discussion lacks detail Does not assess the impact of unethical behaviors on IT and computing within the organization 7 Paper: Cyberlaw Noncompliance: Regulation(s) Meets “Proficient” criteria, and examination includes harm caused by noncompliance Accurately identifies instances of cyberlaw noncompliance and cites specific regulation(s) being violated Identifies instances of cyberlaw noncompliance inaccurately, or does not cite specific regulation(s) being violated Does not identify instances of cyberlaw noncompliance 7 

Paper: Cyberlaw Noncompliance: Impact 

Meets “Proficient” criteria and expands on the impact beyond immediate internal stakeholders 

Assesses the impact of cyberlaw noncompliance on IT and computing within the organization 

Assesses the impact of cyberlaw noncompliance but does not connect it to the organization, or discussion lacks detail 

Does not assess the impact of cyberlaw noncompliance on IT and computing within the organization 


 

 

Paper: Acceptable Use Policies: Comparing and Contrasting 

Meets “Proficient” criteria, and examples are drawn from a broad range of resources 

Comprehensively compares and contrasts acceptable use-of- technology policies 

Compares and contrasts acceptable use-of-technology policies, but discussion lacks detail or is inaccurate 

Does not compare and contrast acceptable use-of-technology policies 

Paper: Acceptable Use Policies: Adaptation 

Meets “Proficient” criteria and provides detailed examples of how the adaptation will support the organization 

Selects aspects of the policies that could be adapted to meet the needs of the organization and explains how they would be adapted 

Selects aspects of the policies that could be adapted to meet the needs of the organization, but does not explain how they would be adapted 

Does not select aspects of the policies that could be adapted to meet the needs of the organization 

Paper: Codes of Ethics: Comparing and Contrasting 

Meets “Proficient” criteria, and examples are drawn from a broad range of resources 

Comprehensively compares and contrasts IT-specific codes of ethics 

Compares and contrasts codes of ethics, but codes are not IT- specific, or discussion lacks detail or is inaccurate 

Does not compare and contrast IT-specific codes of ethics 

Paper: Codes of Ethics: Adaptation 

Meets “Proficient” criteria and provides detailed examples of how the adaptations will support the organization 

Selects aspects of codes of ethics that could be adapted to meet the needs of the organization and explains how they could be adapted 

Selects aspects of codes of ethics that could be adapted to meet the needs of the organization, but does not explain how they would be adapted, or explanation is not accurate 

Does not select aspects of the codes of ethics that could be adapted to meet the needs of the organization 

Presentation: Overview 

Meets “Proficient” criteria and uses industry-specific language to establish expertise 

Provides a comprehensive overview of the issues identified in the risk analysis 

Provides an overview of the issues identified in the risk analysis, but the overview lacks detail 

Does not provide an overview of the issues identified in the risk analysis 

Presentation: Strategies 

Meets “Proficient” criteria and provides detailed examples of how the proposed strategies will remediate the identified issues 

Proposes appropriate strategies that remediate the identified ethics violations and cyberlaw noncompliance 

Proposes strategies that remediate the identified ethics violations or cyberlaw noncompliance, but not both, or the proposed strategies are inappropriate 

Does not propose appropriate strategies that remediate the identified ethics violations and cyberlaw noncompliance 

Presentation: Policy Statements 

Meets “Proficient” criteria and provides detailed examples of how the proposed policy statements will facilitate noncompliance and address non- adherence 

Recommends appropriate policy statements that address acceptable use in facilitating compliance and addressing non- adherence 

Recommends policy statements that address acceptable use in facilitating compliance or addressing non-adherence, but not both, or recommended policy statements are inappropriate 

Does not recommend policy statements that address acceptable use in facilitating compliance and addressing non- adherence 


 

 

Presentation: Code of Ethics 

Meets “Proficient” criteria and provides detailed examples of how the proposed code of ethics will mitigate the risk from the identified issues 

Recommends appropriate code of ethics that mitigates the risk of future instances of violation and noncompliance 

Recommends code of ethics that mitigates risk of future instances of violation or noncompliance, but not both, or the recommended code of ethics is inappropriate 

Does not recommend code of ethics that mitigates risk of future instances of violation and noncompliance 

Articulation of Response 

Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy-to-read format 

Submission has no major errors related to citations, grammar, spelling, syntax, or organization 

Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas 

Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas 

Earned Total 100% 

 

Monday, 14 September 2020

Short Paper Guidelines and Rubric

UK assignment helper





 IT 415 Short Paper Guidelines and Rubric

Short papers offer additional opportunities for analysis of the system design process. In the first short paper, you will discuss a sample system design

document, and in the second short paper, you will summarize each document that will be included in your detailed design.

You are required to write two short papers.

Guidelines for Submission: Submit assignment as a Word document with double spacing, 12-point Times New Roman font, and one-inch margins.

Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value

Content Demonstrates strong or Demonstrates knowledge with Demonstrates knowledge but Fails to demonstrate knowledge 20

adequate knowledge of the some errors or omissions with major errors or omissions of the materials

materials

Critical Analysis Provides a strong critical analysis Provides analysis and Provides analysis and Fails to provide critical analysis 20

and interpretation of the design interpretation of design interpretation of design and interpretation of the design

document document with some errors or document but with major errors document

omissions or omissions

Sources/Examples Sources or examples meet Sources or examples meet Sources or examples meet Source or example selection and 20

required criteria and are well required criteria but are less required criteria but are poorly integration of knowledge from

chosen to provide substance than adequately chosen to chosen to provide substance the course is clearly deficient

and perspectives on the issue provide substance and and perspectives on the issue

under examination perspectives on the issue under under examination

examination

Writing (Mechanics) Paper is clearly organized, well Paper is fairly well organized and Paper is poorly organized with Paper is not organized or well 20

written, and in proper format written, and is in proper format inconsistent and inadequate written; work is of poor quality

with strong sentence and with reasonably good sentence sentence and paragraph and unacceptable in terms of

paragraph structure and few and paragraph structure, but development, and numerous grammar and spelling

errors in grammar and spelling significant number of errors in errors in grammar and spelling

grammar and spelling

Writing (APA) Paper contains proper APA Paper contains few errors in APA Paper contains significant errors Paper contains more than five 20

formatting with no more than formatting in APA formatting significant errors in APA

one significant error formatting

Earned Total 100%

Thursday, 10 September 2020

Case Study Analysis Guidelines and Rubric

UK assignment helper

  




IT 380 Module Three Case Study Analysis Guidelines and Rubric

Overview: This case study analysis will help you analyze a cybersecurity scenario and identify which principles were violated. Each skill in this paper is an essential part of the final project and accompanying milestones in this course.

Prompt: Use the articles from the Module Three required resources to analyze the cyber security occurrence, determine which principles were violated, and recommend appropriate policies to prevent recurrence.

Scenario: In February 2015, as many as 80 million customers of the nation’s second‐largest health insurance company, Anthem Inc., had their account information stolen. This compromise affected customers in at least 14 different states where Anthem provided services.

The hackers gained access to Anthem’s computer system and got information including names, birthdays, medical IDs, Social Security numbers, street addresses, email addresses, and employment information including income data. Both current and former customers were exposed during this breach.

So, while this was an attack against a medical provider and it resulted in a massive data breach, regulatory requirements were not sufficient to help prevent this breach. Because no actual medical information appears to have been stolen, the breach would not come under Health Insurance Portability and Accountability Act (HIPAA) rules, which govern the confidentiality and security of medical information.

Based on the Test Out sections from this module and the additional module resources you have reviewed, your paper should address the following critical elements:

 Identification of cyber security principles that were violated and rationale of cause

 Analysis of cryptography that would have helped prevent this breach

 Recommendation of additional policies that would have been useful to mitigate the breach or even prevent the breach


Rubric

Guidelines for Submission: Your paper should be submitted as a 2‐ to 3‐page (in addition to the cover and reference pages) Microsoft Word document with double spacing, 12‐point Times New Roman font, and one‐inch margins. All sources must be cited in APA format.

Critical Elements

Exemplary (100%)

Proficient (90%)

Needs Improvement (70%)

Not Evident (0%)

Value

Identification of Cybersecurity Principles That Were Violated

Meets “Proficient” criteria and correctly identifies which principles were violated with empirical supporting examples

Correctly identifies which principles were violated with supporting examples

Identifies which principles were violated but supporting examples have gaps

Does not identify a single principle

30

Analysis of Cryptography and Prevention

Meets “Proficient” criteria and analysis demonstrates keen insight of cryptography and prevention methods

Analysis demonstrates accurate knowledge of cryptography and prevention methods

Analysis demonstrates knowledge of cryptography but needs additional information to support prevention ideas

Does not analyze the cryptography and prevention methods

30

Policy Recommendation

Meets “Proficient” criteria and recommendation demonstrates understanding of policies that would remedy the situation appropriately

Recommends policies to ensure proper resolution of scenario

Recommends a single policy to remedy situation but recommendation has gaps in strategic implementation

Does not recommend any policies

30

Proper Use of Writing, Mechanics, and Grammar

Paper is free of errors in organization and grammar with applicable sources cited

Paper is mostly free of errors of organization and grammar; errors are marginal and rarely interrupt the flow; cites applicable sources

Paper contains errors of organization and grammar but errors are limited enough so that assignments can be understood; cites applicable sources

Paper contains errors of organization and grammar making the content difficult to understand

10

Total

100%

Wednesday, 9 September 2020

Ethical Case Study

UK assignment helper

 





Ethical Case Study Project Guidelines

Overview

You write a case study based on your own experience related to an ethical issue within an organization; or you may choose to write about an emerging ethical issue within your current or planned industry. The case study can be fully anonymous to protect those within your organization, and you may choose to identify your role in the case study or not. Your case study will be submitted for a grade in parts throughout the term with the entire final document as the last deliverable. Please review these general tips and guidelines. How to approach writing your case:

• Assume you are one of the leaders in the organization. Write with clarity and confidence on the topic based on what you have learned prior to and during this course.

• Pretend that the audience reading this case study knows nothing about the situation or ethical philosophy, decision-making, etc. Provide enough detail to give readers enough information to draw conclusions, but remain succinct.

• Explain, as needed, the context, evaluate the evidence, and make a decision concerning the appropriate course of action, and support your conclusion through arguments and counter-arguments.

• Take a clear and decisive position – What would you do in this case? What ethical decision-making framework did you use? What most influenced your decision?

Formatting Requirements

The formatting of this document should be as follows:

• Use consistent formatting throughout (12 pt font, Times New Roman, single-spaced).

• Do review your paper thoroughly for grammatical issues and typographical errors!

• Use cover page and references

• Cite your sources (do not use Wikipedia or Blog, etc.) and list them in a reference page per APA style.

• At minimum 5 resources that are published no more than five years ago. Choose scholarly resources (i.e., peer-reviewed journal, sources from your industry/organization, and (sparingly) the textbook.

• 9-12 body pages (single-spaced, not including cover page and references).

Project Timeline

• Week 3: Choose an ethical issue and a topic. See the assignment for details.

• Week 4: Part 1 and Outline of Case

• Week 5: Part 2

• Week 6: Part 3

• Week 7: Final Document

• Week 8: Final Presentation

Ethical Case Outline

Part 1: Describe the case (3-4 pages):

• Identify the parties involved, their rights, their responsibilities

• Identify the salient ethical and/or legal issues of the case

• Identify the relevant factual issues, conceptual issues, social constraints, and any additional information necessary for an accurate understanding of the case.

• If needed, conduct research about the issue from multiple perspectives and include relevant ethical theory, legal requirements, and technical details about the case to ensure that the case can be solved.

• See OWL Sample Outlines for formatting information.

Part 2: Critically analyze the case (3-4 pages):

• Identify the primary “ethical dilemma (or question)” in the case.

• Formulate possible courses of action.

• Discuss any role that information technology or context played in creating the special circumstances of the case.

• Evaluate the strengths and weaknesses of those actions.

• Analyze different courses of action, are they based on a consequential or non-consequential approach? Are these courses of action ethical?

• Weigh the pros and cons of each action.

Part 3: Solve the case (3-4 pages):

• Indicate which course of action you would choose, and why. If you were personally involved in the scenario, you can detail what you DID do compared to what you WOULD do given what you have learned in this course.

• Provide your own opinions: do not rephrase the opinions of others, create your own, unique viewpoint based on your ethical philosophy, ethical decision-making framework, and the context and scenario of the case.

• Clearly demonstrate and explain how the pros of your solution outweigh the cons.

• Use the facts of the case and supporting resources to convince your readers of the soundness of your ethical point of view

Final Document

• All parts due as one cohesive document.

• Be sure to have addressed any issues or concerns that were brought to your attention from each individual part.

Final Presentation

• Create a 8-10 minute narrated presentation that is limited to 10 slides

Monday, 7 September 2020

Six Case Study Analysis Guidelines and Rubric

UK assignment helper

 





IT 380 Module Six Case Study Analysis Guidelines and Rubric 

 

Overview: This case study will help you analyze a cyber security scenario and identify which tenets were violated. Each skill in this paper is an essential part of the final project and accompanying milestones in this course. 

 

Prompt: Choose either the Home Depot security breach or Target security breach from the articles below. Use the information provided to analyze the cyber security occurrence, determine which principles were violated, and recommend appropriate policies to prevent recurrence. Review the Module Six resources to complete this assignment. 

 

After reviewing the details surrounding these two major breaches and the information from Test Out from this module, answer the following questions. Select either the Home Depot breach or Target breach as your exemplar. 

 

 Which tenets of cyber security were violated in the breach? How were those attacks executed to bypass network defenses?  What elements of network defense would have helped mitigate or prevent the breach?  What elements of data defense would have helped mitigate or prevent the breach?  What best practices would you recommend going forward to better secure the organization—both for overall defense and also to provide better detection? 

 

Based on the Test Out sections from this module and the additional module resource articles that you reviewed, your paper should address the following critical elements: 

 

 Identification of cyber security tenets that were violated and rationale of cause  Analysis of data defense that would have helped mitigate or prevent this breach  Recommendation of best practices to secure organization going forward 

 

  


 

 

Rubric 

 

Guidelines for Submission: Your paper should be submitted as a 2‐ to 3‐page (in addition to the cover and reference pages) Microsoft Word document with double spacing, 12‐point Times New Roman font, and one‐inch margins. All sources must be cited in APA format. 

 

Critical Elements Exemplary (100%) Proficient (90%) Needs Improvement (70%) Not Evident (0%) Value Identification of Violated Cybersecurity Tenets Meets “Proficient” criteria and correctly identifies which tenets were violated, with empirical supporting examples Correctly identifies which tenets were violated with supporting examples Identifies which tenets were violated but supporting examples have gaps Does not identify which tenets were violated 30 Analysis of Data Defense Meets “Proficient” criteria and analysis demonstrates keen insight of data defense and prevention methods Analysis demonstrates accurate knowledge of data defense and prevention methods Analysis demonstrates knowledge of data defense methods but needs additional information to support prevention ideas Does not analyze the data defense and prevention methods 30 Best Practices Recommendation Meets “Proficient” criteria and recommendation demonstrates understanding of industry best practices that would remedy the situation appropriately Recommends industry best practices to ensure proper resolution of scenario Recommends a single best practice to remedy situation but recommendation has gaps in strategic implementation Does not recommend any industry best practices 30 Proper Use of Writing, Mechanics, and Grammar Paper is free of errors in organization and grammar with applicable sources cited Paper is mostly free of errors of organization and grammar; errors are marginal and rarely interrupt the flow; cites applicable sources Paper contains errors of organization and grammar but errors are limited enough so that assignments can be understood; cites applicable sources Paper contains errors of organization and grammar making the content difficult to understand 10 Total 100% 

Thursday, 3 September 2020

DATABASE ARCHITECTURE AND DESIGN

UK assignment helper





IT 8100 DATABASE ARCHITECTURE IT 8100 

 DATABASE ARCHITECTURE AND DESIGN


 Group Activity 1 “Whole Sale Food Market” Group Activity 

“Whole Sale Food Market”

3

Department Department Department

Product

Code Code

Aisle

Number Number

Price Price

Unit of Unit of Unit of Measure Measure

Produce Produce Produce

4081

1

0.35

lb

Produce Produce Produce

4027

1

0.90

ea

Produce Produce Produce

4108

1

1.99

lb

Butcher Butcher

331100

5

1.50

lb

Butcher Butcher

331105

5

2.40

lb

Butcher Butcher

332110

5

5.00

lb

Freezer Freezer

411100

6

1.00

ea

Freezer Freezer

521101

6

1.00

ea

Freezer Freezer

866503

6

5.00

ea

Freezer Freezer

866504

6

5.00

ea

Whole Sale Food Market Whole Sale Food Market Whole Sale Food Market Whole Sale Food Market Whole Sale Food MarketWhole Sale Food Market Whole Sale Food Market

User View 1 User View 1 User View 1 User View 1 User View 1 User View 1 User View 1 -Price Update List Price Update List Price Update List Price Update List


5

Normalize User Views and Create a Final 3NF Normalize User Views and Create a Final 3NF Normalize User Views and Create a Final 3NF Normalize User Views and Create a Final 3NF Normalize User Views and Create a Final 3NF Normalize User Views and Create a Final 3NF Normalize User Views and Create a Final 3NF solution

UNF

1NF

2NF

3NF

CHALLENGES CHALLENGES

Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market” Group Activity 1 “Whole Sale Food Market”

Monday, 31 August 2020

F1 Championship

UK assignment helper



Reassessment/Deferred Assignment: F1 Championship

About this assessment

This reassessment/deferred assignment 100% towards the total module mark (capped as it is a resit).

It is an individual piece of work.


Objectives

The objective of this assessment is for you to demonstrate your ability to design and implement an

OO system consisting of a set of Java classes and a client program. In particular:

1. To design and implement classes with suitable fields, constructors, accessor methods, and

modifier methods.

2. To conform to the standard conventions of Java.

3. To implement classes that are associated by inheritance, delegation, composition and

aggregation.

4. To write a client application that uses your classes to show that they function correctly.

Submission

When you have completed the assignment, submit one .zip Archive File called imat5101F1.zip

via Blackboard consisting of your (Eclipse) project folder and associated source code.

Late Submission

Late submissions will be processed in accordance with current University regulations which state:

“the time period during which a student may submit a piece of work late without authorisation and have the

work capped at 50% if passed is 14 calendar days. Work submitted unauthorised more than 14 calendar

days after the original submission date will receive a mark of 0%. These regulations apply to a student’s

first attempt at coursework. Work submitted late without authorisation which constitutes reassessment of a

previously failed piece of coursework will always receive a mark of 0%.”

Academic Offences and Bad Academic Practices

These include plagiarism, cheating, collusion, copying work and reuse of your own work, poor

referencing or the passing off of somebody else's ideas as your own. If you are in any doubt about

what constitutes an academic offence or bad academic practice you must check with your tutor.

Further information is available at:

http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-support-office/academicoffences.

aspx and http://www.dmu.ac.uk/dmu-students/the-student-gateway/academic-supportoffice/

bad-academic-practice.aspx

IMAT5101 OO Programming

la/2018 Page 2 of 5

Your Scenario: Formula 1 Championship System

Foreword: You are required to build a Java application that provides a basis for storing and

processing details related to a Formula 1 Championship. Although there may be similarities to a real

Formula 1 Championship, and therefore it is logical that you may draw inspiration from this to

assist your understanding, this scenario is intended to be both hypothetical and fictional. To this

extent, this specification should be strictly followed and a submission that does not resemble the

provided specification will not receive any credit, where it does not meet the intended design or

programming logic.

The Scenario: A Formula 1 Championship comprises of several teams. Each team has two drivers

and many mechanics. Drivers and mechanics are both team members and therefore have a common

set of details (name and address) about them stored, as well as their annual salary.

A mechanic has a particular role within the team, e.g. basic engineer, data strategist, driver support,

etc. They also are either based back at the factory or travel to races. A driver has a number of points,

based upon their race results. This said, races and results are beyond the scope of the current system

release and therefore hypothetical points may be added to a driver at any time.

As well as having two drivers and a list of mechanics on their records, a team will also have a

number of points, based upon the sum of the points of their two drivers, e.g. driver 1 has 20 points

and driver 2 has 76 points then the team has 96 points. A team should be able to calculate their

points at any time. The size of a team is based on the number of mechanics, as well as their 2

drivers.

A championship should be ordered based on teams and the points they hold, with the team in 1st

position being the one that holds the most points.

Technical Information: The UML class diagram (overleaf) specifies all required classes, interfaces

and their relationships. It also lists all fields, constructors and methods that you are required to

implement. You should strictly follow this specification.

Note that classes Championship and Team both implement the Iterable interface, whilst class Team

implements the Comparable interface. The compareTo(…) method in the Team class should

compare two teams based on their points – this will assist with sorting teams in the Championship

class. It is important to ensure that both teams’ points are calculated prior to comparing them. The

equals(…) methods you are required to override in the TeamMember and Details classes, should

compare each field within those respective classes. A toString() method should be present in each

class and output the current value stored in each of the fields.

Use Cases: You should have a test class, with a main method, that should complete the following

use cases for the “Formula 1 Championship System” to show it works:

1. Create 5 teams, each populated with 2 drivers and a minimum of 4 mechanics.

2. Add these 5 teams to a championship, calculate each team’s points and order them on this.

3. Output in order the championship standings including team name, and points, as well as the

full name of each driver within the team and their respective points.

4. Calculate the total combined salary for all mechanics and drivers belonging to the current

championship leading team, and output this figure, along with the number of team members.

IMAT5101 OO Programming

la/2018 Page 3 of 5





2

* *

IMAT5101 OO Programming

la/2018 Page 4 of 5

IMAT5101 Assignment 3 Assessment Indicators

Grade indicators

55%: Classes without dependencies have been implemented meeting standard basic conventions.

Test programs exist for these classes. At least one Inheritance, one Composition and one

Aggregation association have each been attempted. The data model has been populated (probably

by hard-coding). At least one use-case has been attempted. Basic tasks have been carried out

independently during the lab test.

65%: As for 55% above. Most classes in the design have been implemented to meet standard

conventions and documentation standards. Test program has identified the limitations of a class.

The data model has been suitably populated. Classes implement appropriate interfaces (e.g.

Comparable, Iterable). Use-cases have been simulated with moderate success. Most tasks have been

completed in the lab test and successfully demonstrate the essential functionality of the system.

75%+: As for 65% above. Additionally: a coherent data model has been designed and

implemented, with appropriate levels of abstraction. The integrity of attributes has been a

consideration and mostly maintained. All use-cases have been implemented with high levels of

success. Documentation is at the appropriate level to support maintainable code. All the lab test

activities have been completed successfully and demonstrate the correctness and quality of the

system.

Please Turn Over for a Checklist of Assessment Indicators.

IMAT5101 OO Programming

la/2018 Page 5 of 5

Checklist

These indicators will be used as a basis for the assessment mark and will form your feedback.

(67% Model) Class documentation, design and implementation.

 Javadoc class headers, method and constructor description.

 Javadoc @param and @return tag description.

 Details class fields, constructors and standard methods.

 Details class equals method.

 TeamMember class fields, constructors and standard methods.

 TeamMember class equals method.

 Driver class fields, constructors and standard methods.

 Mechanic class fields, constructors and standard methods.

 Team class fields and constructors and standard methods.

 Team class delegated aggregate methods.

 Team class compareTo and getPoints methods.

 Iterable implemented by Team and Championship classes.

 Championship class fields, constructors and standard methods.

 Championship class delegated aggregate methods.

 Championship class sortTeamsOnPoints method.

(30% Testing) Use Case success.

 Use Case 1 has been achieved appropriately.

 Use Case 2 has been achieved appropriately.

 Use Case 3 has been achieved appropriately.

 Use Case 4 has been achieved appropriately.

 Overall quality of test data and output.