Moral Decisions

Important: Resources Ready for Audit 3:

• Audit 3 slide

• Prototype

• Front End website: https://moralfrontend.azurewebsites.net/en

• Front End GitHub Repository: https://github.com/24-S1-2-C-Moral-Decisions/moral-front-end

• Survey website: https://24-s1-2-c-moral-decisions.github.io/moral-survey/

• Survey GitHub Repository: https://github.com/24-S1-2-C-Moral-Decisions/moral-survey

• Deployable Docker File: https://github.com/24-S1-2-C-Moral-Decisions/moral_moments

• Jira Username: vincenttttwu@gmail.com password: MoralTeam

• Meeting Logs

• Meeting Minutes Files

• Risk Logs

• Decision Logs

• Decision Log files

• Reflection Logs

• UI Issues

Table of Contents

• Project Description

  • Project Description
  • Team Members and Roles
  • Statement of Work

• Project Management

  • Project Management
  • Risk Management
  • Conflict Resolution Protocol

• Meeting

  • Records and schedules
  • Meeting Minutes
  • Client Meeting
  • Team Meeting
  • Tutorial Meeting

• Project Logs

  • Decision Log
  • Reflection Log
  • Risk Log
  • Issue Log

• Project Documentations

  • Design Documentation
  • Develoing Document
  • WorkFlow
  • Getting Start
  • Installation
  • Weekly Update

• Connection

• Other Resources

Moral Moment Project Resources

• How to use multi thread in node.js: https://www.digitalocean.com/community/tutorials/how-to-use-multithreading-in-node-js#
• survey(Dev Mode): https://24-s1-2-c-moral-decisions.github.io/moral-survey/moral-survey-2/index.html
• survey backend: https://moralmomentapi.azurewebsites.net/api
• Related presentations: presentations
• UI design:
  • Figma: https://www.figma.com/file/6PINXpuynOE8HFpRz3wDtn/Moral-Moment?type=design&node-id=141%3A9123&mode=design&t=277SwbMjeEaPBOdb-1
• website frontend: https://github.com/24-S1-2-C-Moral-Decisions/moral-front-end
• Repo:
  • Main Survey: https://github.com/24-S1-2-C-Moral-Decisions/moral-survey
  • Survey 1: https://github.com/24-S1-2-C-Moral-Decisions/moral-survey-1
  • Survey 2: https://github.com/24-S1-2-C-Moral-Decisions/moral-survey-2
• AI Model:
  • https://huggingface.co/joshnguyen/mformer-authority
  • https://huggingface.co/joshnguyen/mformer-care
  • https://huggingface.co/joshnguyen/mformer-fairness
  • https://huggingface.co/joshnguyen/mformer-loyalty
  • https://huggingface.co/joshnguyen/mformer-sanctity
• Jira: Moral

Project Description

• Developers: COMP8715 Computing Project, Australian National University, Australia

• Background: In recent years, the intersection of artificial intelligence (AI) and ethics has emerged as a critical area of research. Projects such as Ask Delphi and the Moral Machine Experiment have made significant strides in understanding how AI can be aligned with human moral values. However, these projects often focus on idealized or extreme moral dilemmas, such as the trolley problem, which may not fully capture the complexity of everyday moral decision-making.

• Objective: The "AI + Human Exploration of Daily Moral Decisions" project aims to bridge this gap by focusing on the nuances of everyday moral dilemmas. By leveraging AI and human collaboration, the project seeks to provide a more comprehensive understanding of how people navigate moral decisions in their daily lives. The project will involve the development of an interactive Moral Profile Website, which will assist humans in appreciating the rich and nuanced aspects of moral life, and a large-scale Opinion Survey Website, including exploring whether individuals are willing to change their opinions under the influence of others.

• Tech Stack: Tech Stack Documentation

• Stakeholders: Stakerholders analysis

Team Members and Roles

Project Management

In managing our web API development project, we faced challenges such as increasing complexity, the need for consistency in development environments, version control requirements, and time and resource constraints. To address these, we made the following decisions:

• Use Git as our version control system to facilitate collaboration and prevent conflicts.
• Utilize development environments like Visual Studio and WebStorm to ensure uniformity across the team and prevent inconsistencies.
• Use Postman for testing to ensure the code's reliability and effectiveness.
• Chose Jira for task management, the Jira Kanban workflow, and the Jira timeline for our development process, aiming for seamless integration, simplicity, cost-effectiveness, and enhanced collaboration within the team.
  • You can use account: vincenttttwu@gmail.com and password MoralTeam to access the Jira
• Chose Jira for task management, aiming for seamless integration, simplicity, cost-effectiveness, and enhanced collaboration within the team.
• Use agile project management as well as agile development methods. We expect to set a weekly development cycle. Synchronization of tasks and progress at each stage of the development cycle will be determined through frequently scheduled stand-ups meeting, and tasks for the next stage or cycle will be decided.
• We meet with our clients once a week at a set time to synchronize current project progress and to consult with them on issues. The meeting agenda is sent to the client in advance of the meeting.

By focusing on integration, simplicity, and collaboration, we've positioned our team to work with greater agility and transparency, aligning our tooling and workflows with the specific needs and goals of our project. The full decision log can be accessed here.

Risk Management

Risk Identification

Make the most of every team station meeting, synchronized meetings with clients, and meetings with tutors to communicate positively. Encourage team members to actively raise possible risks.

Risk Evaluation

Utilize weekly station meetings to perform qualitative and quantitative assessments of identified risks, including assessing the probability and impact level of the risk. Risks are prioritized based on their level of impact.

Risk Response

Develop response strategies for each risk, including avoidance, transfer, mitigation, and acceptance. Ensure that the response strategy is aligned with project objectives and stakeholder expectations.

Incorporate risk response strategies into project plans and implementation. Ensure that team members have the skills and resources to address the corresponding risks.

Documentation and records

Document all identified risks, assessments, response strategies, and implementation processes.

Conflict Resolution Protocol

• Purpose:

  The purpose of this document is to outline a well-defined protocol for handling conflicts within our development team. This protocol is intended to ensure that disagreements and issues are resolved efficiently and effectively, allowing us to maintain a healthy and collaborative work environment while focusing on the completion of our APP design and testing tasks.

• Protocol:

  • Identifying the Conflict:

    Team members should openly and respectfully communicate any concerns or disagreements that arise during the course of the project. This may be done in-person, through video calls, or other appropriate communication channels. Conflicts should be brought up as soon as possible to prevent escalation and to ensure timely resolution.

  • Open Discussion:

    Once a conflict has been identified, all parties involved should engage in an open discussion to better understand the root cause of the issue.

    Each team member involved should have the opportunity to express their perspective and concerns without interruption. Have group meeting twice a week on Wednesday(on-campus) and Sunday(on-line).

    Active listening should be practiced by all participants, ensuring that everyone's viewpoint is heard and understood.

  • Brainstorming Solutions:

    After all parties have had a chance to express their concerns, the group should brainstorm potential solutions to the conflict.

    Team members are encouraged to offer suggestions and ideas, no matter how unconventional they may seem.

    The team should aim for a consensus-based solution, where all parties involved are in agreement.

Project Documentation

Design Documentation

The design documentation for our project, including logos and web design prototypes, can be found in the "Designs" folder within our project repository. This documentation provides a comprehensive overview of the visual and interaction design aspects of our project.

Location: Designs Folder

Develoing Document

Getting Start

See the online documentation for references we referenced in the project.

We use GitHub Discussions as our forum, and Microsoft Teams for chat. These are great places to ask questions and advice from the community or to discuss projects.

For bugs and feature requests, please raise an issue and follow the templates there.

Installation

Getting deployment

1. First, install docker

2. clone and init repo

   
   # clone repo
   git clone git@github.com:24-S1-2-C-Moral-Decisions/moral_moments.git

init submodules

git submodule update --init --recursive

update submodules(when needed)

git submodule update --recursive --remote

3. build and publish survey
```bash
# build and publish survey
./build-survey.sh

4. set up database environment

   1. create a directory for environment files (e.g. enveroments)
   2. create a file named .database.env in the directory
   3. set the database connection string in the file

   DATABASE_CONN_STRING=mongodb://127.0.0.1:27017/testdb

5. build docker images

   docker-compose up -d --build

Connection

We use GitHub Discussions and Github Issues as our forum, and Microsoft Teams for chat. These are great places to ask questions and advice from the community or to discuss projects.