Firefighting Communication System
Brainstorming phase

People involved: Fire Fighters, Department supervisors, Software company, Victims of fire, emergency personnel.

Risks: System doesn’t work between firefighters – firefighters can coordinate movements to help each other during the fire leading to complications and dangers. System doesn’t work between supervisors and firefighters – firefighters can’t communicate anything to their bosses so they can’t make important decisions when its most important. System doesn’t work between firefighters and medical personnel – firefighters can speak to each other, but the medical personnel are in the dark about what’s happening. System works during the test but not in the field – something about the openness of the test makes the system work but in confined buildings at different elevations the systems just can’t connect properly and lag or don’t work at all. System isn’t fireproof – works in testing but in the actual firefight it melts making communication impossible or exploding/ setting on fire making the problem worse and possibly killing firefighters.

Benefits: Better communication between everyone involved.

Possible Actions: continue testing the system, release the system to the fire department, scrap the system all together if the testing doesn’t go well and we can’t fix it. Release a flawed System.

Analysis phase
Responsibilities: deciding if the product is ready to be released. Making sure the product has no bugs or risks. Testing the product thoroughly enough to prove that it is ready for use.

Stakeholder rights: right to refuse purchase, right to test the system themselves, right to buy but not use the system, right to buy and use the system.

Impact: Risks – if the system fails at all it could lead to a stall during the firefight and, at worst, cost someone or many people their lives.

Benefits – If the system works as intended, instructions and protocol can be passed much easier to all parties involved, allowing for a faster firefight and quicker response from all personnel involved.

Action category: continue testing – obligatory. Release the system – acceptable. Scrap the system with further issues – obligatory. Release flawed – Prohibited.

Ethical Dilemma
Is it ethical to release the system when you are not sure whether it's ready or not?

Solution PreviewSolution Preview

This material may consist of step-by-step explanations on how to solve a problem or examples of proper writing, including the use of citations, references, bibliographies, and formatting. This material is made available for the sole purpose of studying and learning - misuse is strictly forbidden.

If we judge the scenario using the Utilitarianism current, then the consequences of releasing the system immediately cannot be predicted entirely. We are aware the existing risks might transform the release into a horrible outcome which might have even legal implications....
$5.00 for this solution

PayPal, G Pay, ApplePay, Amazon Pay, and all major credit cards accepted.

Find A Tutor

View available Computer Science - Other Tutors

Get College Homework Help.

Are you sure you don't want to upload any files?

Fast tutor response requires as much info as possible.

Upload a file
Continue without uploading

We couldn't find that subject.
Please select the best match from the list below.

We'll send you an email right away. If it's not in your inbox, check your spam folder.

  • 1
  • 2
  • 3
Live Chats