Microsoft Visual Studio and Microsoft Access Desktop App Worksheet

Using Microsoft Visual Studio and Microsoft Access, develop a desktop application:

COMPOLICE ST™is your personal mobile app community policing app that is intended to aid police services in the region in gathering data about various hot spots within each territory.

• The app should have the ability to move from country to country. Once you are in that country, any data that should be uploaded is uploaded to that country’s database.
• The app should be able to support picture/video upload; for each upload, there should be appropriate data and metadata.
• The app should allow the user to report a community disturbance.
• The app should be able to list each police station in the country you are in.
• The app should provide at least four (4) information pages, such as a page containing a list of emergency numbers etc.

You must determine the data that is to be collected. This is a simple application to generate data to provide data to the police. The concept can be viewed as giving the local community police ‘eyes on the ground’.

A compiled C# desktop application showcasing all areas previously covered. Your project is intended to draw on the previous assignments.

You are to provide:

• A folder named DEVELOPMENT with all your development resources. This must include all development assets.
• A folder named DEPLOY with all relevant files compiled to run your application, such as existing *.dll files, *.bat files, *.ocx files or other file types.
• A file named Documentation.doc(x) which provides for documentation of your project.

COMPOLICE ST™ Application:
Requirements Gathering:
As per the project description, the main features and functionalities of the app are:
1. Users can create and submit a report including a title, description, and location.
2. Users can view all submitted reports and filter them by status (i.e., open or closed).
3. Admins can view all reports and update their status (i.e., open or closed).
4. Police stations can view all reports assigned to them and update their status.
5. Users can sign up and log in to the app.
6. The app should have a user-friendly interface and be accessible to users with disabilities.
Additional requirements or specifications needed to fulfill the project objectives may include:
1. The app should have a search function to allow users to search for specific reports.
2. The app should have a notification system to alert users when their report status has been
updated.
3. The app should be optimized for both mobile and desktop devices.
4. The app should have proper authentication and authorization to ensure data security and
privacy.
5. The app should be developed using a scalable architecture to accommodate future
updates and features.
Class Diagram:
Here’s a sample class diagram for our COMPOLICE ST™ community policing app:
The class diagram includes four entities: User, PoliceStation, Report, and HotSpot.
The User entity represents the app’s users, including their userID, username, password, and
email. The PoliceStation entity represents the police stations in the area, including their
stationID, stationName, location, and contactNo.
The Report entity represents the user-generated reports about community disturbances, including
their reportID, description, image, date, and the userID of the user who submitted the report. The
HotSpot entity represents the areas of interest identified by the police or users, including their
hotSpotID, hotSpotName, location, description, and the userID of the user who submitted the
hotspot.
Use case Diagram:
Here are three example Use Case diagrams for the COMPOLICE ST™ community policing app:
Use Case Diagram for Reporting a Disturbance:
Actors:
•
User
Use Cases:
•
Report Disturbance
•
Attach Picture/Video
•
Add Metadata
•
Submit Report
Use Case Diagram for Viewing Police Stations:
Actors:
•
User
Use Cases:
•
View Police Stations
•
Search Police Stations by Location
Use Case Diagram for Accessing Information Pages:
Actors:
•
User
Use Cases:
•
View Emergency Numbers Page
•
View Crime Prevention Tips Page
•
View FAQ Page
•
View About Page
Sequence Diagram:
Here are three example sequence diagrams for the COMPOLICE ST™ community policing app:
User Reports a Community Disturbance
This sequence diagram shows how a user can report a community disturbance through the app.
The user selects the “Report Disturb” option from the app’s menu, creates a new report, and
sends it to the police station. The police station receives the report, notifies the user that the
report was received, and takes appropriate action.
User Views List of Police Stations
This sequence diagram shows how a user can view a list of police stations in their area. The user
selects the “Police Stations” option from the app’s menu, which triggers a query to retrieve the
list of stations from the database. The app displays the list to the user.
Police Station Receives and Processes a Report
Database Creation:
Here’s an example of how the tables could be structured:
Table: User
•
UserID (PK)
•
Username
•
Password
•
Email
•
FirstName
•
LastName
Table: Report
•
ReportID (PK)
•
UserID (FK)
•
Timestamp
•
Description
•
Location
•
Media
Table: PoliceStation
•
StationID (PK)
•
StationName
•
Address
•
City
•
State
•
ZipCode
Table: EmergencyNumber
•
NumberID (PK)
•
NumberType
•
PhoneNumber
Table: InformationPage
•
PageID (PK)
•
PageTitle
•
PageContent
The relationships between the tables could be structured as follows:
•
The User table has a one-to-many relationship with the Report table, as each user can
create multiple reports.
•
The Report table has a many-to-one relationship with the PoliceStation table, as each
report is associated with one police station but each police station may receive multiple
reports.
•
The EmergencyNumber and InformationPage tables are not directly related to any other
tables, but they provide additional information for the app.
And the following are the table design of database of the system.
Screen Design:
For the purpose of this exercise, we will provide a high-level mockup of five screens each for the
web and mobile versions of the app. Please note that these designs are not final and are subject to
change based on user feedback and further testing.
Web Screens:
1. Home Screen
•
This screen provides an overview of the app’s features and allows users to sign in
or register.
•
Navigation: The navigation menu is located at the top of the screen and includes
links to the app’s main features.
•
User Assistance/Help System: The app includes a help button at the top right
corner of the screen that users can click for assistance.
2. Report Screen
•
This screen allows users to report a community disturbance by uploading pictures
or videos and providing relevant data and metadata.
•
Navigation: The navigation menu is located at the top of the screen and includes
links to the app’s main features.
•
User Assistance/Help System: The app includes a help button at the top right
corner of the screen that users can click for assistance.
3. Police Station List Screen
•
This screen displays a list of police stations in the user’s current location.
•
Navigation: The navigation menu is located at the top of the screen and includes
links to the app’s main features.
•
User Assistance/Help System: The app includes a help button at the top right
corner of the screen that users can click for assistance.
4. Information Screen
•
This screen displays information about emergency numbers and other relevant
information.
•
Navigation: The navigation menu is located at the top of the screen and includes
links to the app’s main features.
•
User Assistance/Help System: The app includes a help button at the top right
corner of the screen that users can click for assistance.
5. Profile Screen
•
This screen displays the user’s profile information and allows them to edit their
information.
•
Navigation: The navigation menu is located at the top of the screen and includes
links to the app’s main features.
•
User Assistance/Help System: The app includes a help button at the top right
corner of the screen that users can click for assistance.
Mobile Screens:
1. Home Screen
•
This screen provides an overview of the app’s features and allows users to sign in
or register.
•
Navigation: The navigation menu is accessible by clicking the hamburger icon in
the top left corner of the screen.
•
User Assistance/Help System: The app includes a help button at the bottom of the
screen that users can click for assistance.
2. Report Screen
•
This screen allows users to report a community disturbance by uploading pictures
or videos and providing relevant data and metadata.
•
Navigation: The navigation menu is accessible by clicking the hamburger icon in
the top left corner of the screen.
•
User Assistance/Help System: The app includes a help button at the bottom of the
screen that users can click for assistance.
3. Police Station List Screen
•
This screen displays a list of police stations in the user’s current location.
•
Navigation: The navigation menu is accessible by clicking the hamburger icon in
the top left corner of the screen.
•
User Assistance/Help System: The app includes a help button at the bottom of the
screen that users can click for assistance.
4. Information Screen
•
This screen displays information about emergency numbers and other relevant
information.
•
Navigation: The navigation menu is accessible by clicking the hamburger icon in
the top left corner of the screen.
•
User Assistance/Help System: The app includes a help button at the bottom of the
screen that users can click for assistance.
5. Profile Screen
•
This screen displays the user’s profile information and allows them to edit their
information.
The following are some of the visuals of the website the screen design of website would look
like.
Admin dashboard:
Employee Dashboard:
All the cases page:
User Dashboard:
User Login Dashboard:
About page of the Crime Investigation website:
Home page/Index page of the crime reporting system website:
Navigational Map:
Here’s a sample navigational map for both the web and mobile applications:
Web Application Navigational Map: Home -> Login -> Dashboard -> Report -> Submit Report > Confirmation -> Logout
Mobile Application Navigational Map: Login -> Dashboard -> Report -> Submit Report ->
Confirmation -> Menu -> Logout
In the web application, the user starts on the home page, then logs in to access the dashboard.
From the dashboard, they can choose to create a new report, which takes them to the report
submission page. After submitting the report, the user sees a confirmation page before returning
to the dashboard. From the dashboard, they can choose to log out.
In the mobile application, the user starts on the login page and then goes to the dashboard. From
the dashboard, they can choose to create a new report, which takes them to the report submission
page. After submitting the report, the user sees a confirmation page and then can access the menu
to log out.
Application Structure:
If the application is intended to be delivered as a native or hybrid mobile application only, the
basic application structure can be organized as follows:
1. Main menu: The main menu is the first screen that the user sees when they open the
application. It provides access to all the main features of the application, such as
reporting a disturbance, viewing emergency numbers, and accessing the list of police
stations.
2. Report disturbance screen: This screen allows the user to report a disturbance by
providing details such as the location of the disturbance, the type of disturbance, and any
additional comments.
3. Emergency numbers screen: This screen displays a list of emergency numbers, including
the police, ambulance, and fire department.
4. List of police stations screen: This screen provides a list of police stations within the
user’s location, including their contact information and location on a map.
5. Settings screen: This screen allows the user to customize the application, such as
changing the language or notification settings.
The application can be structured using a navigation drawer, which allows the user to access all
the main features of the application from a single menu. Additionally, the application can have a
floating action button that is always present on the screen, allowing the user to quickly report a
disturbance from anywhere in the application.
Desktop Application Design:
For the desktop application, we can consider the following screens:
1. Home Screen: This screen should provide an overview of the app and allow users to
navigate to other sections of the app. It can include options to report a community
disturbance, view police station locations, and access emergency numbers.
2. Report Screen: This screen should allow users to report a community disturbance by
uploading a picture or video and providing relevant data and metadata. The screen should
have clear instructions and options for submitting the report.
3. Police Stations Screen: This screen should provide a list of police stations in the user’s
country, along with their contact information and location. It should allow users to search
for police stations by name or location.
4. Emergency Numbers Screen: This screen should provide a list of emergency numbers,
such as ambulance, fire department, and poison control. It should also include
instructions on what to do in different emergency situations.
5. User Profile Screen: This screen should allow users to view and edit their personal
information, such as their name and contact details. It should also provide options for
changing their password or deleting their account.
For menu/navigation, we can consider using a navigation bar at the top of the screen or a side
menu that expands when the user clicks on a hamburger icon. The navigation should be intuitive
and allow users to quickly access the different sections of the app.
For user assistance/help system, we can consider including tooltips or pop-up windows that
provide additional information or instructions when the user hovers over or clicks on certain
elements of the screen. We can also provide a help section that includes FAQs and
troubleshooting tips. Additionally, we can include a feedback form or contact information for
users who need further assistance.
Platform Recommendation:
Based on market trends and user demographics, we recommend developing a hybrid mobile
application for this project.
According to a report by Statista, the number of mobile phone users worldwide is expected to
reach 7.33 billion by 2023. Additionally, the report states that the majority of mobile phone users
(72.6%) are expected to access the internet via their mobile devices by 2025. Therefore,
developing a mobile application would allow the app to reach a wider audience.
Furthermore, a hybrid mobile application can be developed for both Android and iOS platforms,
which would increase the app’s reach even further. This is especially important as Android and
iOS are the dominant mobile operating systems globally.
In terms of technical requirements, a hybrid mobile application can be developed using popular
frameworks such as React Native or Ionic. These frameworks offer several benefits such as code
reusability, easy maintenance, and access to native features, making it easier to develop a highquality app.
Moreover, a hybrid mobile application can provide a seamless user experience by allowing users
to access the app even when offline, which is not possible with a web application. This is
particularly important in areas where internet connectivity may be unreliable.
In conclusion, developing a hybrid mobile application would allow the app to reach a wider
audience, offer a seamless user experience, and provide access to native features.