COIT20258 Assignment 3

Disaster Response System - Enhanced Version

Project Type: Team-based Software Development

Team Size: 2-4 Students

Weighting: 45% of Final Grade

Due Date: Sunday, 15 June 2025, 11:59 PM AEST

This assignment represents the culmination of your software development journey in this unit. You will work collaboratively to enhance an existing disaster response system, demonstrating both technical competence and effective teamwork.

Learning Objectives

This assignment assesses your ability to:

Key Focus: This assignment emphasizes both technical excellence and professional collaboration skills essential for software development careers.

Assignment Overview

The Three-Stage Development Process

Previous Stages (Completed)

  • Stage 1: Requirements analysis and system design (Individual)
  • Stage 2: Initial prototype development - DRS-Initial (Individual)

Current Stage (Assignment 3)

  • Stage 3: Enhanced system development - DRS-Enhanced (Team)
  • Extend and improve existing functionality
  • Add two new domain-specific features

You will select the most promising DRS-Initial from your team members and collaboratively enhance it into a comprehensive disaster response system.

Team Formation and Initial Steps

Step 1: Establish Your Development Team

Step 2: Project Foundation Selection

Step 3: Project Infrastructure

Technical Architecture Requirements

System Architecture Components

Frontend Layer

  • JavaFX-based graphical interface
  • Scene Builder for UI design
  • User-friendly interaction design

Middle Layer

  • Multi-threaded server implementation
  • Business logic processing
  • Client-server communication

Backend Layer

  • MySQL database integration
  • Data persistence and retrieval
  • Database security measures

Design Pattern

  • Model-View-Controller (MVC) or
  • Model-View-Presenter (MVP)
  • Clear separation of concerns

Important: Your application must demonstrate proper three-tier architecture with clear separation between presentation, business logic, and data layers.

Core System Functionality

Essential Disaster Response Capabilities

1. Disaster Reporting Module

Enable users to report various disaster types including hurricanes, fires, earthquakes, and other emergency situations with detailed incident information.

2. Assessment and Prioritization System

Provide automated assessment capabilities to evaluate reported disasters and establish response priorities based on severity, location, and available resources.

3. Department Coordination Interface

Facilitate communication and coordination between emergency services, hospitals, utilities, transportation, and other relevant organizations.

4. Two Additional Domain-Specific Features

Implement two innovative features that enhance the disaster response capabilities, such as resource allocation, evacuation planning, or real-time status tracking.

Recommended Development Timeline

8-Week Implementation Schedule

Week 1: Project Initiation

Team formation, repository setup, foundation selection, and initial planning

Weeks 2-3: Design and Architecture

Create UML diagrams, design new features, establish database schema, and finalize technical specifications

Weeks 4-5: Implementation Phase

Develop enhanced features, implement multi-threaded server, integrate database functionality

Weeks 6-7: Testing and Refinement

Conduct comprehensive testing, resolve identified issues, optimize performance, and finalize documentation

Week 8: Final Preparation

Complete reports, conduct final testing, prepare submission materials, and ensure all requirements are met

Assignment Deliverables

Part 1: Team Submission (40 marks)

Group Report Components:

  • Requirements specification
  • UML diagrams (use cases, classes, sequences)
  • Database Entity-Relationship Diagram
  • Comprehensive test plan with results
  • Evidence of automated testing

Software Deliverables:

  • Complete DRS-Enhanced implementation
  • Executable application files
  • Database creation and population scripts
  • Installation and execution instructions

Part 2: Individual Submission (5 marks)

Teamwork Reflection Report:

  • Team formation and role descriptions
  • Technical challenges and solutions
  • Collaborative problem-solving experiences
  • Success factors for effective teamwork
  • Communication skills development

Note: Individual reports must reflect personal experiences and cannot be shared between team members.

Strategies for Success

Technical Excellence

  • Begin with database design and architecture
  • Implement core functionality before advanced features
  • Conduct regular integration testing
  • Maintain clean, well-documented code
  • Ensure application compilation and execution

Project Management

  • Establish clear task assignments and deadlines
  • Conduct regular team meetings and progress reviews
  • Maintain detailed project documentation
  • Create backup plans for potential challenges

Collaboration Excellence

  • Communicate openly and frequently
  • Document all decisions and problem resolutions
  • Support team members facing difficulties
  • Maintain professional working relationships
  • Take screenshots of collaborative achievements

Critical Success Factor: Start early and maintain consistent progress throughout the development period.

Remember: This assignment evaluates both technical competence and professional collaboration skills. Focus on delivering a functional, well-tested system while demonstrating effective teamwork.

Assessment Criteria and Grade Distribution

Part 1: Team Submission (40 marks)

Requirements Specification (6 marks)

  • Functional requirements clarity (1 mark)
  • Non-functional requirements (1 mark)
  • System requirements (1 mark)
  • User requirements with screenshots (1 mark)
  • Two additional features (2 marks)

Design Specifications (14 marks)

  • System architecture (1 mark)
  • UML diagrams (4 marks)
  • Test plan and evidence (6 marks)
  • GitHub repository management (3 marks)

Software Implementation (20 marks)

  • Complete NetBeans project (5 marks)
  • Compilation and execution (5 marks)
  • MVC/MVP pattern implementation (2 marks)
  • User interface design (3 marks)
  • Additional features implementation (5 marks)

Critical: 50% penalty applies if project fails to compile or execute properly.

Part 2: Individual Teamwork Report (5 marks)

Each component worth 1 mark: team formation description, technical problem solutions, collaborative challenge resolution, teamwork success factors, and communication skills development.

1 / 10