Analysis, design, and implementation of a Smart City Management Application

System features:

A smart city has a number of smart buildings and smart streets. The users of the system have different roles and different privileges.

The system components in addition to the different users, their roles and responsibilities are presented in the next paragraphs.

Smart Buildings:

• Each building has a number of floors and each floor consists of a number of apartments.
• A building is characterized by its ID, type (residential, institutional, business, industrial), the smart street where it is located, in addition to the number of residents.
• Smart buildings integrate renewable energy sources (solar and/or wind) in order to power the building.
• Apartments in each building have IDs.
• Each apartment is equipped with a sensor node.
• These nodes contain the following components:
  • Motion sensor
  • Temperature sensor
  • Humidity sensor
  • Microcontroller
  • Communication module
• Apartments also contain different smart appliances. Each appliance is connected to a switch in addition to smart meter to monitor the power consumption. The smart appliances allowed in each apartment are: heater, AC, washing machine, dryer, TV, and fridge. Other non-smart appliances can be added but will not be part of the system.
• Each building has a control room that contains a network gateway responsible for the gathering and visualization of the data received from the different sensor nodes in all the apartments. The gateway contains a microcontroller and a communication module.

Smart Streets:

• A smart street has a name and an ID.
• Streets are also equipped with sensor nodes consisting of the following components:
  • Microcontroller
  • Temperature sensor
  • Smart meter for the streetlights power consumption monitoring
• Each street has a general control room where we can find data about the street itself along with data regarding the different buildings located in that street.

The system has two main users:

General Admin:

The general admin manages the entire city. His privileges include:

• Adding smart buildings to the system
• Adding smart streets to the system
• Adding apartments to the buildings on the system
• Adding sensor nodes to the apartments and streets on the system
• Viewing data related to the different sensor nodes deployed.
• Manages profiles/accounts for the residents
  • Create account
  • Delete account
  • Update account

In order to have access to these privileges, the general admin has to login using a username and a password. A general admin has an ID, full name, email, and phone number. In addition to the privileges mentioned previously, the general admin can manage his own account. The general admis also takes care of the different report given by the residents. These reports are given to the corresponding organisations offline.

Resident

Residents have ID, name, phone number, email, age, profession, and address (street, building, and apartment). Residents have access to the different sensor nodes that are deployed in their apartments. They can view the data given by the sensors and the status of the appliances; they can also control the appliances (turn on/off). In addition to that, residents can report any problems related to their smart appliances or the sensor nodes deployed in their apartments. These reports and requests are handled by the general admin who contacts the responsible parties to take care of the problems. Residents have access to the system through their accounts (login and password). They can manage their accounts by changing passwords and usernames.

What To Submit:

1. UML class diagram that models the entire system. The diagram should contain the methods and attributes of all the classes in addition to the relationships between them.
2. Java project that contains all the classes modeled in the UML diagram. Each class should implement all the methods mentioned in the requirements. Make sure you implement a Graphical User Interface that allows the user to use the features of the system. Include the necessary exceptions, use the appropriate data structures and enumerations.

Report where you present your work and justify your design and implementation decisions