Scenario Analysis Activities
§ It is expected of the all the students in this class to apply the ACM Code of Ethics and Professional Conduct.
§ Students are to go beyond a checklist analysis and perform their own analysis based on their comprehension of the intent of the codes provided in the Additional Course Resources provided under Course Information in Blackboard.
§ Students are to focus on identifying the stakeholders[1], their respective stakes, the essential issues, and the problem being analyzed.
§ There are many frameworks for analysis provided on the web. Students are encouraged to use any of them which they deem appropriate for the problem domain they use.
§ A code of Ethics is a moral and professional obligation that computer professionals, society, and businesses came to an agreement to produce.
§ It would be a good idea if the students exchange their views with other computer professionals, society and any businesspeople to model their own analysis.
§ At the end of the semester, each student must write a final paper to write about what they have learned from reading the scenarios.
§ Scenarios will be posted on blackboard biweekly and it will have the due dates for each assignment.
Grading your analysis
§ All papers must conform to the following requirements:
· 1” Margins all around
· Must have a title, and your name
· Bibliography page for your references
· 12 points font
· Use either Ariel or Times New Roman
· Single Space your article
· Use proper indentations “e.g. press Tab when you start in a new paragraph”
· No grammar or spelling errors will be accepted
· Your article must be at least 500 words
§ When you write your article, you are to:
· Identify stakeholders, stakes, and responsibilities of the computer professional involved with respect to each stakeholder.
· Isolate the ethical issues involved.
· Identify relevant principles of the ACM Code of Ethics and Professional Conduct or any other Code of Ethics provided in your Additional Course Resources file.
· Discuss various courses of action including alternatives in addition to the obvious extreme positions.
· Recommend and justify course of action.
· Offer suggestions for preventing a recurrence (e.g. policy changes) and discuss immediate and long-term consequences.
[1] Anyone that has some direct or indirect influence on systems requirements is a stakeholder. End-users who use the system, Engineers who maintain and develop the system, Business Managers, Domain Experts, may also be system stakeholders.