Department of Computer Sciences and Information

Technology
University of Sargodha

Project Title:

Session:

Submitted By:

Acknowledgment

This project consumed huge amount of work, research and dedication. We have taken efforts in this
project. However, it would not have been possible without the kind support and help of many
individuals. We would like to extend our sincere thanks to all of them.

We are highly indebted to Mr. Hassan Rauf for their guidance and constant supervision as well as for
providing necessary information regarding the project & also for their support in completing the
project. We are thankful for his aspiring guidance, invaluably constructive criticism and friendly
advice during the project work. We are sincerely grateful to him for sharing his truthful and
illuminating views on a number of issues related to the project.

We would like to express our gratitude towards our HOD “Mr. Umer Shahzad” for their kind co-
operation and encouragement which help us in completion of this project.
TABLE OF CONTENTS
CHAPTER 1: FINAL PROJECT PROPOSAL

Contents
CHAPTER 1: FINAL PROJECT PROPOSAL ......................................................................... 6
1.1: INTRODUCTION: ................................................................................................................ 6
1.2: PROJECT TITLE: ..............................................................Error! Bookmark not defined.
News aggregator application Error! Bookmark not defined.
1.3. Project Overview statement: ...............................................Error! Bookmark not defined.
Project Overview Statement Template Error! Bookmark not defined.
1.4. Project Goals & Objectives:................................................Error! Bookmark not defined.
1.5. High-level system components: ..........................................Error! Bookmark not defined.
1.6. List of optional functional units: .........................................Error! Bookmark not defined.
1.7. Application Architecture:....................................................Error! Bookmark not defined.
1.8. Gantt chart:..........................................................................Error! Bookmark not defined.
1.9. Hardware and Software Specification: ...............................Error! Bookmark not defined.
1.9.1: Hardware Requirements Error! Bookmark not defined.
1.9.2: Software Requirements Error! Bookmark not defined.
1.10. Tools and technologies used with reasoning: ...................Error! Bookmark not defined.
1.11. Exclusion: .........................................................................Error! Bookmark not defined.
CHAPTER 2: COST AND RISK ASSESSMENT .... ERROR! BOOKMARK NOT DEFINED.
 2.1. Introduction .........................................................................Error! Bookmark not defined.
2.2: Project Feasibility Report ...................................................Error! Bookmark not defined.
2.2.1: Technical Feasibility Error! Bookmark not defined.
2.2.2: Operational Feasibility Error! Bookmark not defined.
2.2.3: Economic Feasibility Error! Bookmark not defined.
2.2.4: Schedule Feasibility Error! Bookmark not defined.
2.2.5: Specification Feasibility Error! Bookmark not defined.
2.2.6: Information Feasibility Error! Bookmark not defined.
2.2.7: Motivational Feasibility Error! Bookmark not defined.
2.2.8: Legal & Ethical Feasibility Error! Bookmark not defined.
2.3: Project Scope ......................................................................Error! Bookmark not defined.
2.4: Extended Features ...............................................................Error! Bookmark not defined.
2.5: Project Costing....................................................................Error! Bookmark not defined.
Project Cost Estimation by Function Point Analysis ................................................................ 13
2.6: Project Cost Estimation by using COCOMO (Constructive Cost Model)Error! Bookmark not define
2.7: Task Dependency Table......................................................Error! Bookmark not defined.
2.8: CPM - Critical Path Method ...............................................Error! Bookmark not defined.
2.9: Introduction to Team member and their skill set: ...............Error! Bookmark not defined.
2.10: Tools and Technology with reasoning ..............................Error! Bookmark not defined.
2.10.1: Reasoning Error! Bookmark not defined.
2.11: Gantt Chart:.......................................................................Error! Bookmark not defined.
2.12: Vision Document ..............................................................Error! Bookmark not defined.
2.13: Risk List ............................................................................Error! Bookmark not defined.
2.13.1: Requirement Risks Error! Bookmark not defined.
2.13.2: Construction Risks Error! Bookmark not defined.
2.13.3: Design Risks 16
2.13.4: Business Risks 16
2.13.5: Technical Risks 16
2.13.6: Operational Risks 17
2.13.7: Project Management Risks 17
2.13.8: Product Features/ Product Decomposition: 17
CHAPTER 3: SECOND DELIVERABLE FOR OBJECT ORIENTED APPROACH ...... 18
3.1: Introduction ........................................................................................................................ 18
3.2: Systems Specifications ...................................................................................................... 18
3.2.1: Introduction 18
3.2.2: Existing System 19
 3.2.3: Scope of the System 19
3.3: Identifying External Entities: ............................................................................................. 19
3.4: Capture Shall Statements and Requirement Allocation :................................................... 19
FUNCTIONALITY...................................................... ERROR! BOOKMARK NOT DEFINED.
3.4.1: Functional Requirements Error! Bookmark not defined.
3.5: Use Cases ............................................................................Error! Bookmark not defined.
3.5.1: Login Error! Bookmark not defined.
3.5.2: Login via Facebook Error! Bookmark not defined.
3.5.3: Sign up 22
3.5.4: Sign up Via Facebook Error! Bookmark not defined.
3.5.5: Logout Error! Bookmark not defined.
3.5.6: ViewError! Bookmark not defined.
3.5.7: Follow a topic Error! Bookmark not defined.
3.5.8: News Article Error! Bookmark not defined.
3.5.9: Comment on a News Article Error! Bookmark not defined.
3.5.10: Modify Notifications Error! Bookmark not defined.
3.5.11: Search Error! Bookmark not defined.
3.5.12: Share Error! Bookmark not defined.
3.5.13: Edit Error! Bookmark not defined.
3.5.14: Change Picture Error! Bookmark not defined.
3.6: Admin Tasks .......................................................................Error! Bookmark not defined.
3.6.1: Add news sources to a topic Error! Bookmark not defined.
3.6.2: Remove a user Error! Bookmark not defined.
CHAPTER 4: OBJECT ORIENTED APPROACH . ERROR! BOOKMARK NOT DEFINED.
4.1: Sequence Diagram ..............................................................Error! Bookmark not defined.
4.2: Activity Diagram: ...............................................................Error! Bookmark not defined.
4.3: Collaboration Diagram .......................................................Error! Bookmark not defined.
4.4: Class Diagram: ....................................................................Error! Bookmark not defined.
CHAPTER 5: ................................................................ ERROR! BOOKMARK NOT DEFINED.
5.1. Introduction: ........................................................................Error! Bookmark not defined.
5.2Entity Relationship Diagram: ...............................................Error! Bookmark not defined.
5.3. Data flow diagram (Functional Model) ..............................Error! Bookmark not defined.
5.4: State Transition Diagram ....................................................Error! Bookmark not defined.
CHAPTER 6: (USER INTERFACE DESIGN) ........ ERROR! BOOKMARK NOT DEFINED.
6.1. Introduction .........................................................................Error! Bookmark not defined.
6.2: Logo ....................................................................................Error! Bookmark not defined.
 6.3: Splash ..................................................................................Error! Bookmark not defined.
6.4: Home...................................................................................Error! Bookmark not defined.
6.5: Login ...................................................................................Error! Bookmark not defined.
6.6: Sign up ................................................................................Error! Bookmark not defined.
6.7: Successful Sign up ..............................................................Error! Bookmark not defined.
6.8: Profile..................................................................................Error! Bookmark not defined.
6.9: Drawer ................................................................................Error! Bookmark not defined.
6.10: Categories .........................................................................Error! Bookmark not defined.
6.11: News Details .....................................................................Error! Bookmark not defined.
CHAPTER 7: (SOFTWARE TESTING) .................. ERROR! BOOKMARK NOT DEFINED.
7.1 Introduction: .........................................................................Error! Bookmark not defined.
7.2 Purpose of Testing ...............................................................Error! Bookmark not defined.
7.3 Product Testing ....................................................................Error! Bookmark not defined.
7.4 Process of Testing ................................................................Error! Bookmark not defined.
7.5 Testing Techniques ..............................................................Error! Bookmark not defined.
7.5.1 Black box testing Error! Bookmark not defined.
7.5.2 White box testing Error! Bookmark not defined.
7.6 Implementation of Testing ...................................................Error! Bookmark not defined.
7.6.1 User Login Error! Bookmark not defined.
7.6.2 User Registration Error! Bookmark not defined.
7.6.3Sign Up Error! Bookmark not defined.
7.6.4Categories Selection Error! Bookmark not defined.
7.6.5 Edit Profile Error! Bookmark not defined.
Chapter 1: Final Project Proposal

1.1: INTRODUCTION:

It's the way the 21st century communicates now. Social networking is the grouping of
individuals into specific groups, like small rural communities or a neighbourhood
subdivision.
In this project, we are going to build a social media app with a purpose to enable users to
create and share content or to participate in social networking. Social media is the collective
of online communications channels dedicated to community-based input, interaction, content-
sharing and collaboration. We are making an app that will allow user to share their content
with other user using a network. This app will improve the user experience of the connecting
with other users and share their content.
It have different features like user will be able to post their pictures with other user, user
aggregate their thoughts with other with posting their status, user can like and comment on
other users post, user can find and send friend request to other users and chat with them and
user and maintain their profile with singing up with the app.

1.2: Project Title

1.3: Project Overview Statement

This project centres on building a social media app that will allow user to share their content over a
channel to communicate with different people and make new friends online.
Social media app project itself is a huge project comprising various features like profile
updating, friend’s list organization, chat and various other applications to enhance the overall
look and feel of the app. However, in this project we are basically working on four essential
features or modules Profile Management, Friend Organization, Chat box and Posting.

Profile Management:
This module maintains the profile of a user like name, like, dislikes, username, password,
pictures and status.

Friends Organization:
This module maintains the friend list, handles requests, sends request to the other user,
handles request acceptance and request decline.

Chat Box:
This Module allows users to chat with other users and also maintain the chats of the users.

Posting:
This module allows users to post their pictures and status and share with other users. It also
maintains the like and comments of the different users on a particular post.

Project Overview Statement Template

Project Title:

Project Manager:
Project Members:
Name Registration # Email Address Signature

Project Goal: Our ultimate goal is to come up with an optimal social media app for mobile phone that help
user to find new friends and share their content with different people and have chat with them.

Objectives:
1 Allow users to sing up with the app
2 Allow users to make their profile
3 Allow users to maintain their profile
4 Posting
5 Friends list organization
6 Allow user to send friend request
7 Allow users to chat with friends
 8 Allow users to see posts of other users
Project Success criteria:
1. Content Posting
2. Friend Request send
3. Friend Request Received
4. Chat
5. Profile Editing

Type of project:
1. Development
Target End users:
2. Android Users
3. Developers.
4. Evaluation Panel.
5. Supervisors.
Development Technology:
1. Object Oriented
Platform:
1. Distributed
2. Android

Approved By:
Date:

1.4. Project Goal & Objectives:

Our ultimate goal is to come up with an optimal social media app for mobile phone that help
user to find new friends and share their content with different people and have chat with
them. And our Objectives are as follow;

1. Allow users to sing up with the app

2. Allow users to make their profile
3. Allow users to maintain their profile
4. Posting and sharing
5. Friends list organization
6. Allow user to send friend request
7. Allow users to chat with other users
8. Allow users to see posts of other users

1.5. High-level System Components:

1. Internet connection
2. Database availability and accessibility
3. Server performance and availability

1.6. List of Optional Functional Units

1.6.1 System shall allow the user to sign up and create profile
1. User shall be able to sign up via email.
1.6.2 System shall allow the user to maintain his/her profile.

1. User shall be able to edit his/her personal profile.

2. User shall be able to change his/her picture.
1.6.3 System shall automatically sign in current users
1. System shall maintain the log in session of current user
2. System shall automatically sign in the current user
1.6.4 System shall maintain user like and dislikes
1. System shall maintain users likes and dislikes
1.6.5 System shall maintain friends list
1. System shall maintain user friends list
1.6.6 System shall allow users to see other user’s profiles
1. User shall be able to see other users profile
1.7. Application Architecture:
1.8. Gantt Chart:
1.9. Hardware and Software Specification:
Following are the software and hardware requirements that are necessary to develop and deploy
this web application

1.9.1: Hardware Requirements

1. Android running Smartphone for android app
1.9.2 Software Requirements
2. Android 4.2 or higher

1.10. Tools and technologies used with reasoning:

The application tools, which are to be used on front and back end of the system to be
developed, are listed below. The reasons for these tools are also enlisted.

3. JAVA: Programming language for coding

4. XML: for front-end development
5. Firebase: database
6. Genymotion: for app debugging
7. Android Studio: IDE for development
8. MS Word: for documentation
9. Ms Project: for project scheduling
10. Ms Visio: for UML diagrams
11. Ms power Point: for presentation slides preparation
1.11 Exclusion:
1. We are developing an android app and not a web based application
2. We are not going to work on sentiments here; our full focus is on semantics.

Chapter 2: Cost and Risk Assessment

2.1. Introduction
In this chapter we will discuss Project Feasibility report of final project. We will discuss
Project Feasibility, Project Scope, Project Costing, Task Dependency Table, Critical Path
Method Analysis (CPM Analysis), Gantt chart, Introduction to team members, Tasks and
member assignment table, Tools and Technologies, Vision Document, Risk List and Product
Features.

2.2: Project Feasibility Report

2.2.1: Technical Feasibility

2.2.1.1: Technology
1. We are using JAVA technology for developing the back-end of the app because
JAVA is an open source technology and we have technical expertise to work on it

2. We are using SQL to manipulate data in database because it is easy to handle and
understand.
3. We are using XML for developing the front-end of the application because it provides
better GUI components and give better User interface experience.
2.2.1.2: Tools
1. We are using android studio for coding purpose because it is open source and easily
available and also provide better integration with JAVA.
2. We are using Google Firebase to store data of the application because it is an online
database so data sharing among different copies of the application comes handy.
3. We are using Adobe Photoshop CC2014 for designing purpose.
4. Gennymotion for debugging

2.2.2: Operational Feasibility

1. We have a team of expert’s members in designing and android development. So we
are able to do work on this project in effective and efficient manner.

2. We are proposing a social media network based system which allows it’s user to
communicate with different people and post their content on it so other user can see it,
like it, and make comments on it.

2.2.3: Economic Feasibility

1. Benefit Estimation
1. Tangible:
1. App will maintain the firebase authentication.
2. App will manage the record of the previous and new users.
3. App will provide the facility to manage profile.
2. Intangible:
1. App increases data usability.
2. Improved response.
3. App stores previous chats and post.

2.2.4: Schedule Feasibility

1. Requirement Gathering:
20 days required for gathering requirements and whole group involved in this activity.
2. Documentation:
30 days required for documentation of the project and all members are involved in
documentation.
3. Graphical User Interface (GUI):
15 days required for designing of user interface and all members are involved in
designing user interface.
4. Coding:
30 days required for coding and all members are involved in coding.
5. Testing:
 15 days required for testing of app and all members as well as end users are involved
in testing process.

2.2.5: Specification Feasibility

1. We have done very well requirement elicitation through research about the general
requirements for this project so the requirements are very well define and clear, there
is no ambiguity in them.
2. Scope of the Socio covers these; it allow user to sign up with the app and maintain
his/her profile, allow user to make posts, allow user to send friend requests, accept
friend request , decline friend request, chat with friends, change his/her profile picture
and username.

2.2.6: Information Feasibility

1. Information is complete and consistent.
2. There is no redundancy of the information.
3. Information is easily understandable.
4. All the information in the system is meaningful.

2.2.7: Motivational Feasibility

1. App fulfils all the requirements that are given.
2. All group members complete their tasks precisely and accurately that were assign to
them.

2.2.8: Legal & Ethical Feasibility

1. We will provide data privacy to users.
2. There are no copy right issues.

2.3: Project Scope

App will do following tasks:

1. It will allow users to sing up with app and create their profile. It will allow users to
upload their display picture (DP) and allow them to pick their usernames.
2. Sing in will be password protected and only profile owner can know it. Password will
be stored in Google Firebase’s auth. After password verification users will be
navigate to main/home screen.
3. After login to the app users can post their content, user can post a picture and text as
well.
4. User can view his/her posts.
5. User can like the post.
6. User unlike his/her post.
7. User can make comment on his/her post (Images and text).
8. Other user can view the post.
9. Other users can like the post.
10. Other users can unlike the post.
11. Other Users can make comments on any post (Images and text).
12. Users can view the list of all the users.
13. Users can send friend request to any other user.
14. Users can view all pending friend requests.
15. Users can accept the friend request.
16. User can decline friend request.
17. Users can view all the posts of his/her friends.
18. Users can chat with his friends only.
19. App will provide a chat box in which both text and pictures can be sent or received.
20. App will keep the previous chat conversations.
21. Users can view other user’s profiles.
22. Users can edit their profile (DP and users).
23. App will automatically update the friend list.
24. App will keep current user logged in.

2.5: Project Costing

Project Cost Estimation by Function Point Analysis

2.6: Project Cost Estimation by using COCOMO (Constructive Cost

Model)

2.7: Task Dependency Table

2.7.1: List of activities in table

Seri Activity Name Task No.
al
No.

1 Proposal T1

2 Project overview T2

3 Goals and Objectives T3

4 Requirements gathering T4

5 Feasibility report T5

6 Project scope T6

7 Project cost estimation by functional T7

point analysis
 8 Project cost estimation by using COCOMO T8

9 List of activities in project T9

10 Task dependency table T10

11 Gantt Chart T11

12 Task and member assignment table T12

13 Introduction to Team member and their T13

skill set

14 Risk List T14

15 Use case diagrams T15

16 Use cases description T16

17 Sequence and collaboration diagrams T17

18 Activity diagrams T18

19 Class diagram T19

20 ERD T20

21 Prototype T21

2.7.2: Task Dependency Table

Task Dependencies Task Dependencies

No. No.

T1 T4 T11 T10

T2 T1,T4 T12 None

T3 T4 T13 None

T4 None T14 T2,T13

T5 T4,T3 T15 T4

T6 T4,T3 T16 T15

T7 T,T T17 T4,T15

T8 T21 T18 T4,T15

T9 T4 T19 T20
 T10 T9 T20 T15

2.8: CPM – Critical Path Method

2.9: Introduction to Team Members and Their Skill Set:

Member# Member Name Skills

M1 Ahsan Tanveer Android Developer and Web Designer

M2 Abdul Ghaffar Android Developer and Web Developer

2.10: Tools and Technologies with reasoning

25. JAVA: Programming language for coding
26. XML: for front-end development
27. Firebase: database
28. Genymotion: for app debugging
29. Android Studio: IDE for development
30. MS Word: for documentation
31. Ms Project: for project scheduling
32. Ms Visio: for UML diagrams
33. Ms power Point: for presentation slides preparation

2.10.1: Reasoning
Our Project is a android based project. For designing the design of application we are
using Adobe Photoshop. For coding we like to use android studio. For testing we use
GennyMotion. Android application is basically based on JAVA programming. We are
using MS Project for making Gantt chart. For documentation we are using MS Office and
Notepad++ is being used as code editor.

2.11: Gantt chart:

2.12: Vision Document
The purpose of this document is to collect, analyze and define the high-level needs and
features of the Socio. It focuses on facilitating the users by news aggregating app. The project
is being developed for University of Sargodha and target Pakistani users and can also be use
in different countries. The details of what all are the needs Socio fulfills these needs are
detailed in the use-case and supplementary specifications.
The purpose of this document is to describe the external behavior of Socio. The Vision
Document captures very high-level requirements and design constraints, which gives the
reader an understanding of Socio to be developed. Requirements Specification defines and
describes the operations, interfaces, performance, and quality assurance requirements of the
Socio. The document also describes the nonfunctional requirements such as the user
interfaces. It also describes the design constraints that are to be considered when the system is
to be designed.
Socio is a social media app and will help users to communicate with other users through
single channel and allow them to post their content over the network.

2.13: Risk List

2.13.1: Requirement Risk

1. The requirements must be clear and precise. Wrong perceptions may lead to failure of
the project or unnecessary results.

2. Do not start the project without incomplete requirements. All requirements must be
complete at the beginning of the project if any requirement is missed, it will affect the
system later.

3. All members are inexperienced so requirement phase may take more time that will
disturb overall project.

2.13.2: Construction Risks

1. Unidentified utility features not covered that may will affect the system in future.

2. Requirement may change during design or development that will affect the
construction phase and hence disturb the overall scheduling.
3. Use of unfamiliar tools and tactics will affect the system.

2.13.3: Design Risks

1. Incomplete quantitative estimation will affect the system design.
2. There would be some difficulties for user if design is complex.
3. Wrong assumptions during requirement phase will affect the system’s design.
4. Inadequate and wrong design will create problems in development phase.

2.13.4: Business Risks

1. Organizational revenue will be affected by the system, this directly related to use of
software.
2. If software does not meet all organizational requirements it will affect recruitment
process.
3. Changes in requirement will change the cost of the system.

2.13.5: Technical Risks

1. All team members are not expert so there may arise some technical issues.
2. No software tools are used for software analysis and requirement analysis for this
time due to short deadline.
3. There will be some quality attributes in software but no plan have been made to
collect complete quality metrics, so there may be some quality issues later in
software.
4. No software tools are used for software testing due to existing deadline so there may
be a little bit technical issues in testing point of view.

2.13.6: Operational Risks

1. The requirements for this project are little bit flexible but a bigger change will affect
the whole operation and it will cause delay in project deployment.
2. All work is done by a single team but team members are inexperienced so there may
be some problems occur in communication and integration of work.

2.13.7: Project Management Risks

1. Tasks were assigned to different team members if their tasks are not synchronous that
will affect the whole project and project scheduling.
2. Infect the whole project was pre-planned but due to poor project tracking the project
planning may disturb and cause delay in deployment.

2.13.8: Product Features/ Product Decomposition:

Functional requirements capture the intended behaviour of the system. This behaviour may
be expressed as services, tasks or functions the system is required to perform.
Chapter 3: Second Deliverable For Object Oriented Approach

3.1: Introduction
In this chapter we will discuss about requirement specification regarding our project. We will
discuss capture shall statement use cases, development of requirement traceability matrix,
allocation of requirements, and data flow diagram.

3.2: Systems Specifications

The following are the clauses that must be included while describing the system specifications.

3.2.1: Introduction
This project centers on building of a social media app for mobile devices. In this project we
are proposing a system that allows individuals to construct a public profile within a bounded
system, articulate a list of other users with whom they share a connection, and view and
traverse their list of connections and those made by others within the system. It isn't just a
social media site used to socialize with your friends but also, represents a huge pool of
information from day to day living. A social networking service is an online service,
platform, or site that focuses on facilitating the building of social networks or social relations
among people who, for example, share interests, activities, backgrounds, or real-life
connections.
3.2.2: Existing System
Many apps have appeared that provide a social network which allow user to share and post
their content on it and chat with other users but usually they required a Gmail or other
mailing server’s authentication but Socio will provide them its own login and authentication,
so everyone can easy create his/her profile easily.

3.2.3: Scope of the System

The scope of the system is to manage and providing the facility of a social network use an
android app. System is targeting the Gujranwala community but it can be used in any other
city or country.

3.3: Identifying External Entities:

1. Local person
2. All Community members

3.4: Capture Shall Statements and Requirement Allocation:

3.4.1: Functional Requirements
3.4.1.1 System shall allow the user to sign up and create profile
1. User shall be able to sign up via any email
3.4.1.2 System shall allow the user to login to his/her existing profile.
1. There should be opening activity which allow user to login.
2. Login activity should provide a text field to enter email and a one more text field to
enter password.
3. There should be button to login to profile.
3.4.1.3 User shall be able to post a picture and text as well.

1. When user click on float button of the main activity’s first tab posting activity should
open.
2. A button shall allow user to add picture in the post.
3. A text field shall allow user to enter text about the post.
4. A posting button shall allow user to post the content on the home screen.

3.4.1.4 User can view his/her posts.

1. When user click on the post picture it will open in new activity and user can zoom in
it.

3.4.1.5 User can like the post.

1. When user click on the like icon there should be a increment in the likes count.

3.4.1.6 User unlike his/her post.

1. When user clicks again on the like icon it should decrease the likes count.
3.4.1.7 User can make comment on his/her post (Images and text).

1. When user clicks on the comment button a new commenting activity should be
opened.
2. There should be a text field where user writes the comments.
3. There should be button to allow user to add picture in the comment.
4. There should be button to post the comment.

3.4.1.9 Users can view the list of all the users.

1. There should be tab of the users in which all the users of the application are viewable.
2. When user clicks any other user image or username it should open its profile.

3.4.1.10 Users can send friend request to any other user.

1. When user opens other user profile page there should be a button to send friend
request.

3.4.1.11 Users can view all pending friend requests.

1. There should be floating button on the Users tab to open pending requests activity
screen.

3.4.1.12 Users can accept the friend request.

2. When user clicks on the pending requests button (floating button in users tab) list of
all pending request should open.
3. When user clicks on a request a new activity should open.
4. There should be a button of accept the request.

3.4.1.13 User can decline friend request.

1. When user clicks on the pending requests button (floating button in users tab) list of
all pending request should open.
2. When user clicks on a request a new activity should open.
3. There should be a button of decline the request.

3.4.1.14 Users can view all the posts of his/her friends.

1. When user clicks on the profile of its friends there should be a button to see all his/her
posts.

3.4.1.15 App will provide a chat box.

1. There should be tab named chats on the home activity.

2. When user clicks on the tab all the chats should be appeared there.

3.4.1.16 Users can view his profiles.

1. There should be tab on the home screen named profile.

 2. When user clicks on the tab it should be able to view his profile.

3.4.1.17 Users can view other user’s profiles.

1. Users shall be able to view the other users profile by clicking on their picture or
username.

3.4.1.18 User can edit his/her profile (DP and users).

1. There should be button to edit the user profile on profile tab.

2. When user clicks on the button a new dialog box should be opened.
3. It should display the existing picture and the username.
4. By clicking on the picture a new dialog box should be opened, there should be to
buttons, one for take image from camera and other for taking picture from gallery.
5. By clicking username it should turn into the editing filed.
6. There should be a button to done editing.

3.4.1.19 App will automatically update the friend list.

1. When a new user signs up with the app its profile should be placed in the users list
automatically.

3.4.1.20 System shall allow user to logout.

1. There should be button in profile tab to logout from the current profile.

3.5: Use Cases

3.5.1: Sign up

Name: Sign up

Actors: User

Summary: The user will sign up with username or email id and password to use
the product
Pre-Conditions Application start up

Successful Post- User will successfully sign up to the application

Conditions
Typical Course of Events

Actor Action System Response

1 User enters a valid user name or email id

2 User will enter a valid password

3 User set its display picture

4 User will tap sign up button 4 System will create the profile
of the user and redirect the
user to main/home activity
screen.

Alternative Course System Response

A-1 user left the username field System displays an error message.
empty.

A-2 User left password field System shall display a error alert.
empty.
A-3 User left profile picture box System shall prompt to a error.
empty.

3.5.2: Login

Name: Login

Actors: User

Summary: The user will login with user name or email id and password to use
the product
Pre-Conditions User must sign up

Successful Post- User will successfully login on to the home page

Conditions
Typical Course of Events

Actor Action System Response

1 User enters a valid user name or email id

2 User will enter a valid password

3 User will tap login button 4 System will authenticate,

identify user and redirect user
to particular home page.

Alternative Course System Response

A-1 user enters invalid user System displays an error message.
name or email

A-2 User enters invalid System shall prompt if the password is incorrect
password
A-2 User clicks forgot password System shall prompt to enter email

3.5.3: Posting

Name: Posting

Actors: User

Summary: The user will post the content by clicking on posting button.
Pre-Conditions User must logged in.

Successful Post- Posting done successfully.

Conditions
Typical Course of Events

Actor Action System Response

1 User clicks on the post button Opens posting activity

2 User add picture to post by click the add picture section Opens dialog box to add
picture

3 User selects the image from gallery or camera System set the image on the
picture section on the posting
activity.

4 User enter the post title or text in the text field on the
posting activity

5 User will tap submit post button 4 System done posting on the
home activity screen.

Alternative Course System Response

A-1 User forget to add the System displays an error message.
picture in the posting section

3.5.4: View Posts

Name: View Posts

Actors: User
Summary: The user sees the post in full view.

Pre-Conditions User must Logged in

Successful Post- User will successfully view the post in full view.
Conditions
Typical Course of Events

Actor Action System Response

1 User clicks on the post picture System opens a activity and
show picture on it.

Alternative Course System Response

A-1 Internet connection lost System displays black screen.

3.5.5: Like Posts

Name: Like Posts

Actors: User

Summary: The user will like the posts of the other users.

Pre-Conditions User must Logged in

Successful Post- User successfully liked the posts

Conditions
Typical Course of Events

Actor Action System Response

1 User clicks on the like icon System changes the icon into
blue and increase the like
count.

Alternative Course System Response

A-1 No internet connection System makes the like count pending until the internet
connection restored.
 3.5.6: Unlike the Posts

Name: Unlike the Posts

Actors: User

Summary: The user will unlike the Post that he/she liked before

Pre-Conditions User must logged in

Successful Post- User will successfully unlike the post

Conditions
Typical Course of Events

Actor Action System Response

1 User clicks on the blue like icon System change icon into
hollow like icon and decrease
the like count.

Alternative Course System Response

A-1 No internet connection System makes the unlike request pending until internet
connection restored.

3.5.7: Commenting
Name: Commenting

Actors: User

Summary: The user comments on the posts

Pre-Conditions User must logged in

Successful Post- User will successfully make comment on the post

Conditions
Typical Course of Events

Actor Action System Response

1 User clicks on the comment icon System opens commenting
activity screen.

2 User enter the commenting text in the field

3 User clicks the plus icon in lower right corner System opens a dialog box to
add picture in the comment

4 User select the picture from camera or gallery System make the comment

5 User tap on the send button System make the comment

Alternative Course System Response

A-1 user left the text field System displays an error message.
empty

A-2 internet connection failed System cancel the commenting request

3.5.8:

3.5.9: View Users List

Name: View Users List

Actors: User

Summary: The user will view the list of all the users who signed up with the app.
Pre-Conditions User must logged in

Successful Post- User will successfully view the list of the users
Conditions
Typical Course of Events

Actor Action System Response

1 User clicks on the users tab System opens the users list

Alternative Course System Response

A-1 internet connection failed System failed to load the list of the users and show blank activity
screen.

3.5.10: Send Friend request

Name: Send Request

Actors: User

Summary: The user Will send the friend request to other users

Pre-Conditions User must logged in

Successful Post- User will successfully send the friend request

Conditions
Typical Course of Events

Actor Action System Response

1 User clicks the other user’s profile image or System opens that
username particular user’s profile

2 User clicks the send request button System sends the request to
particular user and change
the button to cancel
request.

Alternative Course System Response

A-1 internet connection System displays an error message.
failed
 3.5.11: View Pending Requests

Name: View pending Requests

Actors: User

Summary: The user will view the pending request he received or sent.

Pre-Conditions Friend Request sent

Successful Post- User will successfully view the pending requests

Conditions
Typical Course of Events

Actor Action System Response

1 User taps on the pending requests button in the users System opens new activity of
tab the pending requests

2 User clicks the particular requests System opens the particular

pending request in new
activity.

3 User accept or decline the request System changes the view

accordingly.

Alternative Course System Response

- -

3.5.12: Decline Friend Request

Name: Decline request

Actors: User

Summary: The user will decline the request of the other user
Pre-Conditions Friend request sent

Successful Post- User will successfully decline the request

Conditions
Typical Course of Events

Actor Action System Response

1 User Click the pending requests button System opens pending request
activity screen.

2 User clicks the particular request System opens particular

request

3 User tap the decline button 4 System will delete the friend
request

Alternative Course System Response

A-1 Internet Connection failed System will not fulfil the declining request

3.5.13: Accepting Request

Name: accepting request

Actors: User

Summary: The user will accept the request of the other user

Pre-Conditions Friend request sent

Successful Post- User will successfully accept the request

Conditions
Typical Course of Events

Actor Action System Response

1 User Click the pending requests button System opens pending request
activity screen.

2 User clicks the particular request System opens particular

request
3 User tap the accept request button 4 System will add the friend

Alternative Course System Response

A-1 Internet Connection failed System will not fulfil the declining request

3.5.14: Viewing Friend Posts

Name: Viewing friends posts

Actors: User

Summary: The user will see all the post made by the particular friend

Pre-Conditions Post made by friends

User logged in

Successful Post- User will successfully view the particular friend posts
Conditions
Typical Course of Events

Actor Action System Response

1 User Clicks the friend list in his/her profile System opens friends list.

2 User clicks the particular friend System opens particular

profile

3 User tap floating button System shows all posts made

by the particular friend

Alternative Course System Response

A-1 internet connection failed System will not load the posts and show blank activity
 3.5.15: chat

Name: Chat

Actors: User
Friend
Summary: The user will have chat with his/her friends

Pre-Conditions Other user must be the friend

User must be logged in

Successful Post- User will successfully chat with his/her friend

Conditions
Typical Course of Events

Actor Action System Response

1 User Click chat tab System opens chat tab and
show all the chats

2 User clicks the new chat floating button System opens friends list

3 User tap on the particular friend 4 System opens chat activity

4 User enter the text in text field to communicate

5 User clicks the “+” button to send the image System opens image selecting
dialog box

6 User select the image from the camera or gallery System sends the image

7 User taps the send button System sends the message

Alternative Course System Response

A-1 Internet connection failed System will not send the message
 3.5.16: Profile Viewing

Name: Profile viewing

Actors: User

Summary: The user will view his/her profile

Pre-Conditions User must be logged in

Successful Post- User will successfully view his/her profile

Conditions
Typical Course of Events

Actor Action System Response

1 User Clicks the profile tab System opens user profile

Alternative Course System Response

- -

3.5.17: Other users profiles viewing

Name: Other users profile viewing

Actors: User

Summary: The user will see the other user’s profiles either he/she is friend or
not.
Pre-Conditions User must logged in

Successful Post- User will successfully view the other users profiles
Conditions
Typical Course of Events

Actor Action System Response

1 User taps the picture or user name of the other user on System opens that particular
his/her post user profile

2 User taps the users tab and clicks the user image or System opens particular user
username profile

Alternative Course System Response

A-1 Internet Connection failed System will show the profile

3.5.18: Edit Profile

Name: Edit Profile

Actors: User

Summary: The user will edit his/her profile

Pre-Conditions User must logged in

Successful Post- User will successfully Edit his/her profile

Conditions
Typical Course of Events

Actor Action System Response

1 User taps the profile tab System opens user profile

2 User taps the edit profile button System opens profile editing
dialog box

3 User tap on the existing picture System open image selecting

dialog box
4 User selects new image from camera or gallery System sets the new picture in
the image view area

5 User enter the new username in the username text field

6 User enter the new phone number in phone number

text field

7 User tap the update profile System changes the picture,

username and phone number
in user’s profile.

Alternative Course System Response

A-1 User left name field empty System will prompt please enter name
A-2 User left phone number System will prompt please enter phone number
empty
A3 User left both field empty System will show the error

3.5.19: Logout

Name: Logout

Actors: User

Summary: The user will logged out from the app’s current profile.

Pre-Conditions User must logged in

Successful Post- User will successfully logged out

Conditions
Typical Course of Events

Actor Action System Response

1 User taps the profile tab System opens the user profile

2 User taps logout button in upper right corner System will logout the user
Alternative Course System Response
- -