Download chatroom android app and more Study Guides, Projects, Research Communication in PDF only on Docsity!
ABSTRACT
Smart phones have really changed the way of communications. Smart phones are the most used communication tools today. But they are not just limited to communication purposes. Most of us use their smart phone every day, to surf the internet and social media platforms, check emails, read the news, to make phone calls, write text messages, chatting (using Snapchat, whatsapp etc). Despite the presence of messaging apps like WhatsApp and Snapchat, you can’t really do without sending SMS or text messages and these remain one of the messengers with mostly required features on Smartphone. Unfortunately, most stock texting apps are found lacking in some more needy features by the users of Smartphone.
So AOU chatroom is a messaging app that is developed for the Smartphone. This messaging app supports multiple features which are not present in the other messaging app. These features are multiple themes support, night mode, reply to messages without leaving the current app, block message of a particular contact, schedule message sending, Wi-Fi chatting etc. e.g.: if you are in exam it reply your sender automatically that I am in exam and many others. students use this messaging app to make their communication more efficiently and more effectively they can view all the questions of other students and their reply for this question.
Abstract
Epaigham 1
Table of Contents
- Chapter ABSTRACT v - INTRODUCTION - 1 CHAPTER 1-INTRODUCTION
- 1.1 Introduction:
- 1.2 Existing System
- 1.3 Discrepancies of existing system:
- 1.4 Proposed System:
- 1.5 Merits of Proposed System
- 1.6 Project Scope:
- 1.7 Objective of Project - CHAPTER - REQUIREMENT ANALYSIS - 2 CHAPTER 2 – REQUIREMENT ANALYSIS
- 2.1 Requirement Analysis
- 2.2 Functional Requirements
- 2.2.1 Change Theme
- 2.2.2 Manage Message
- 2.2.3 Manage Chat
- 2.3 Non Functional Requirements
- 2.3.1 Appearance
- 2.3.2 Availability
- 2.3.3 Safety
- 2.3.4 Usability
- 2.3.5 Performance
- 2.3.6 Modifiability
- 2.4 Use Cases
- 2.4.1 Actor
- 2.4.2 Use Case Diagram
- 2.4.3 Use case description: - 3 CHAPTER 3 – SYSTEM DESIGN
- 3.1 SYSTEM DESIGN
- 3.2 ACTIVITY DIAGRAMS:
- 3.2.1 Manage Message Activity Diagram:
- 3.2.2 Send Message Activity
- 3.3 Sequence diagrams
- 3.3.1 Change Theme Sequence
- 3.3.2 Block Massage Sequence
- 3.3.3 Send message Sequence Diagram:
- 3.3.4 Wi-Fi Chat Sequence Diagram:
- 3.4 Class diagrams:
- Chapter
- 4 CHAPTER 4 – IMPLEMENTATION
- 4.1 Introduction
- 4.2 Tools and Technologies
- 4.2.1 Microsoft Office Word
- 4.2.2 Software Ideas Modular
- 4.2.3 Microsoft Office Word
- 4.2.4 Android studio
- 4.3 Software Components
- 4.3.1 Application Interface
- 4.3.2 Database
- 4.3.3 Major Methods - 5 CHAPTER 5 – TESTING
- 5.1 Introduction:
- 5.2 Software Testing Axioms:
- 5.3 Verification and validation:
- 5.4 Block Box Testing
- 5.5 White Box Testing
- 5.6 Grey Box Testing
- 5.7 Levels of testing:
- 5.8 Test cases
- 5.9 A sample testing cycle:
- 5.9.1 Requirements Analysis:
- 5.9.2 Test Planning:
- 5.9.3 Test Development:
- 5.9.4 Test Execution:
- 5.9.5 Test Reporting:
- 5.10 Retesting the Defects Test Cases
- 5.10.1 Change Theme:
- 5.10.2 Manage Message:
- 5.10.3 Send Message:
- 5.10.4 Block Message:
- 5.10.5 Send and receive messages
- 6.1 Conclusion
- 6.2 The Software at its Best
- 6.3 Software Requirements:
- 6.4 Hardware Requirements: - User Manual - References
- Figure 2.1: Use Case Diagram TABLE OF FIGURES
- Figure 3.1: Manage Message Activity Diagram
- Figure 3.2: Manage Wi-Fi Communication Activity Diagram
- Figure 3.3: Change Theme Sequence Diagram
- Figure 3.4: Block Message Sequence Diagram
- Figure 3.5: Send message Sequence Diagram
- Figure 3.6: Class Diagram
- Figure 7.1: login Interface
- Figure 7.2: Setting Interface
- Figure 7.3: Register Notification
- Figure 7.4: Block Interface
- Figure 7.5:Others interface
▲ Block Message ▲ Not showing the recent messaging ▲ There are a private messages no need here because they make some problem with privacy
Proposed System:
The proposed system is a chatroom app for Android application which is being developed on android studio. This messaging application allows user to change Multiple Themes according to their preference, Night Mode When you have to read or send messages by a dim light. The Night Mode prevents your eyes from being irritated by the screen of your device. Reply to messages without leaving the current app, Texting can be difficult sometimes. When you're browsing the web or playing a game on your smart phone and need to respond to text message real quick, you have to exit your current app to do so. This messaging app allows you to reply to sms you received without leaving the current app. This messaging app allow you Schedule message sending,. This chatroom app allows you Block Message of someone who sending harassing or annoying text messages, you can
block them directly from this message app. This messaging app allows you to send single Message to a multiple numbers. This messaging app allows Wi-Fi chatting. Student can send question in chatroom and anyone can reply to this question and help all students..also you can view all recent question even if u delete the app and reinstall it after period.
Merits of Proposed System
Following are the merits of the proposed system: ▲ New Features will be added i.e. Wi-Fi Chatting, Night Mode, Auto message sending, contact all recent discussion, Send message without leaving current app ▲ Audio call through Wi-Fi ▲ Contact all recent discussion. ▲ Block Messages ▲ Multiple Theme Support
Chapter 1 Introduction
Aou chatroom 7
Project Scope:
Following is the scope of the project:
▲ Allow user to send message without leaving current app. ▲ Allow user to Block massage of someone. ▲ Allow user to change Multiple Theme. ▲ Allow user to view recent discussion anytime even if they have deleted the app.
Objective of Project
The objective of this chatroom app is to provide multiple features in a single app. Students can found all the reply of frequent questions related to our university no need to consult another website or application. All which are needed for the chatroom application are provided in this application.
Chapter 1
INTRODUCTION
Aou chatroom 8
CHAPTER 2 – REQUIREMENT ANALYSIS
Requirement Analysis
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. System requirements determine what criteria a system or modified system must meet. Requirements Analysis and Definition is the first stage in the systems engineering and software development process. This stage breaks down functional and non-functional requirements to a basic design view to provide a clear system development process framework.
Requirements analysis is a team effort that demands a combination of hardware, software and human factors engineering expertise as well as skills in dealing with people.
Functional Requirements
Functional requirements describe what the system should do, what functionalities are provided by the system. These are following:
▲ Change Theme
▲ Manage Message
- Send Message
- Send schedule Message
- Chat heads
- Send Auto Message
- Send Message on Multiple numbers
- Receive Message
- Listen Message
- Delete Message
- Read Message
- Block Message
▲ Manage Wi-Fi Chat
- Send or Receive message through Wi-Fi
Change Theme
Change theme module allows the user to change the theme of the application according to their preferences and allow user to change look and feel of their application.
Manage Message
Manage Message module manages the following functionalities of the application.
▲ Manage Message
- Send Message
- Send schedule Message
- Chat heads
- Send Auto Message
- Receive Message
- Listen Message
- Delete Message
- (^) Read Message
- Block Message
Manage Wi-Fi Chat
Manage Wi-Fi Chat module manages the following functionalities of the application.
▲ Manage Wi-Fi Chat
Actors represent classes of users, organizations, and external systems that interact with your system.
Use Case Diagram This is use case diagram of our project. This use case diagram shows the actual features of our project and functionality of our project which can perform by the users.
ACTIVITY DIAGRAMS:
Activity diagrams are graphical representations of workflows of stepwise activities and actions. Activity diagram shows the flow of overall control and how actions are taken place and how objects are flow in order object and interactions between the actions []. In particular, it shows the objects participating in the interaction, and the flow of overall system. Activity diagram is another important diagram in UML to describe dynamic aspects of the system.
Figure 3.1: Activity Diagram
Sequence diagrams
UML provides different types of diagrams to translate system requirements to system responsibilities sequence diagrams are used here to represent the dynamic view of the whole system. A Sequence diagram is an interaction diagram that shows how objects operate with one another and in what order. A sequence diagram shows object interactions arranged in time sequence [5].
It depicts the objects and classes involved in the scenario and the sequence of messages exchanged between the objects needed to carry out the functionality of the scenario. Sequence diagrams are typically associated with use case realizations in the Logical View of the system under development. Sequence diagrams are sometimes called event diagrams or event scenarios. The functionality of use cases is described using sequence diagrams.
Change Theme Sequence
This is the sequence diagram of the change theme of the application. User can start the application and load theme. User select theme from the list and change theme of the application.
Block Message Sequence
This is the sequence diagram of the block message. User can start the application and select a contact from the contact list. User blocks messages of the provided number.
Figure 3.4: Block Message Sequence Diagram
Send message Sequence Diagram:
This is the sequence diagram of the send message. User can start the application and compose message and select a contact from the contact. Application sends messages to the provided number.
Figure 3.5: Send message Sequence Diagram
Class diagrams:
The class diagram is a static diagram. It represents the static view of an application. Class diagram is not only used for visualizing, describing and documenting different aspects of a system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the constraints imposed on the system. The class diagrams are widely used in the modeling of object oriented systems because they are the only UML diagrams which can be mapped directly with object oriented languages [1].
The class diagram shows a collection of classes, interfaces, associations, collaborations and constraints. It is also known as a structural diagram.
