Вы находитесь на странице: 1из 17

Design document

Android based PC Controller


Project Code:
BSEF13E024
Project Advisor:
Sir Bilal Ilyas
Project Manager:
Sir Ilyas
Project Team:
Saleem Sarwar (BSEF13E024)
Usman Manzoor (BSEF13E020)
Submission Date:

10-01-2017
Document Information

Category Information
Customer UOS
Project Android based PC controller
Document Design Document
Document Version 1.0
Identifier BSEF13E02024
Status Draft
Author(s) Saleem sarwar & Usman manzoor
Approver(s) PM
Issue Date 22-12-2016
Document Location D:\project
1. Advisor
Distribution 2. PM
3. Project Office

Definition of Terms, Acronyms and Abbreviations


This section should provide the definitions of all terms, acronyms, and abbreviations required to interpret the terms
used in the document properly.

Term Description
App Application
DC Design Document
PC Personal computer
Contents
1. Introduction .......................................................................................................................................... 4
1.1. Purpose of document.................................................................................................................... 4
1.2. Project overview ................................................................................................................................ 4
1.3 Scope ................................................................................................................................................... 4
2. Design consideration............................................................................................................................. 4
2.1 Assumption and dependencies ..................................................................................................... 4
2.2 Risk and Volatile Area ................................................................................................................... 4
3. System Architecture .............................................................................................................................. 5
3.1 System level Architecture ............................................................................................................. 6
3.2 Sub-System /Component/Module Level Architecture......................... Error! Bookmark not defined.
3.2 Sub-component/Sub-Module Level Architecture (1……n) ................... Error! Bookmark not defined.
4. Design Strategies....................................................................................................................................... 7
InterProcess Communication ................................................................................................................ 7
Socket Programming ............................................................................................................................. 7
Wi-Fi Technology................................................................................................................................... 7
5. Detailed System Design............................................................................................................................. 8
5.1Use case Diagram ................................................................................................................................. 8
5.2 Class diagram ...................................................................................................................................... 9
5.3Activity Diagram ................................................................................................................................. 10
5.4 Sequence Diagram ............................................................................................................................ 11
6. References.............................................................................................................................................. 16
Appendices..................................................................................................... Error! Bookmark not defined.
1. Introduction:

1.1. Purpose of document:


This is design document for android base pc controller. This document is primarily intended to provide
detail design and architecture of the system. The DD will facilitate everyone who wants to precede our
work or want to research on remote desktop sharing controlling devices remotely or using WIFI
technology.

1.2. Project overview:


An android PC controller is an android application project that works like PC mouse. The project controls
pc keyboard functions and mouse operations through an android mobile phone. The problem is that we
cannot interact with our PC in meeting and during lectures. Through this we can interact with our
system in any part of our meeting room. The application is made using android and creates a keypad
buttons similar to the one used in PC. The application when installed and run on an android based
phone shows a keypad settings screen. With the keypad user can even use it for typing it on any word
processor and can operate any application.

1.3 Scope :
This project is named as “Android based pc controller”. The project is limited to two devices having WIFI
technology at both end for sending and receiving. The project includes work on Advance GUI (Graphical
User Interface) Programming for android application and computer application, network programming.
The application should able to controlled computer through android device. The user can provide input
from android device. The computer and device will be paired using WIFI.

2. Design consideration
2.1 Assumption and dependencies
 PC( Personal Computer ) compatible running Windows
 1GB RAM or more is recommended.
 Graphics card 256 or more.
 Processor 3.0 GHz.
 Operate on android device

2.2 Risk and Volatile Area

There is a security risk anyone near to our can track our IP address and control our PC.Performance
depends upon the distance.
3. System Architecture
In this system there is client-server architecture. In which android mobile phone is a client and pc/laptop
is a server. Client send request to the server for connection establishment via wireless communication
(WIFI). Connection is established using handshaking. After connection establishment ports are assign
and sockets are established at both ends for communication.
3.1 System level Architecture
4. Design Strategies

InterProcess Communication
InterProcess Communication (IPC) is a set of methods for the exchange of data among multiple
threads in one or more processes. Processes may be running on one or more computers
connected by a network. IPC methods are divided into methods for message passing,
synchronization, shared memory, and remote procedure calls (RPC).

There are several reasons for providing an environment that allows process cooperation:

 Information sharing
 Computational speedup
 Modularity
 Convenience
 Privilege separation

Socket Programming :
A socket is a bidirectional communication device that can be used to communicate with another
process on the same machine or with a process running on other machines. Sockets are the only
InterProcess Communication that permit communication between processes on different
devices such as here in this project the devices are laptop and android mobile. Normally, a
server runs on a specific computer and has a socket that is bound to a specific port number.

Wi-Fi Technology
To turn ON Wi-Fi on android device Wi-Fi Manager provides the primary API for managing all
aspects of Wi-Fi connectivity. A programmer can get Wi-Fi Manager instance through
Context.getSystemService (Context.WIFI_SERVICE). Wi-Fi Manager is used to find the currently
active Wi-Fi network and change the Wi-Fi state. Android application must be installed on your
android mobile (version 2.2 and above) and the Java application on your laptop respectively.
5. Detailed System Design
5.1Use case Diagram

start apllication

Discovering wifi connection

sent pair request to respective wifi


pc module
Mobile module

reply to wifi request

send file command


create connection
open file system

got remotely access

system

file system

stop application
5.2 Class diagram

socket
address family
attribute

+socket
+bind
+listen
+connect
+accept

client socket server socket


Login
portno() port no()
+userid +create() +create()
+password +connect() +accept()
authenticated() +send data() +recieve data()
+receive data()

implement processor
+pid
+responce()
+process()
5.3Activity Diagram

start application

check for wifi

no
action
yes

open wifi

accept request from


client

recieve data

process data

handle mouse and


keyboard

close application
5.4 Sequence Diagram

client server command command


command command
socket socket proceessor receive
Create request connection()
Send/get desktop
Send request start
application

Accept incoming connection

Receive desktop Receive/start


application image

Connection is established
with the server
5.5 ERD

Client communicates Server

Desktop

keyboard event Mouse event

send key board invoke mouse


invoke key events send mouse events
events events
5.6 Graphical user interface:
5.6.1 Server side:
5.6.2 Client side:
6. References
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&arnumber=5669816&ranges%3D2
009_2014_p_Publication_Year%26queryText%3Dphone+pc
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?tp=&arnumber=4777442&ranges%3D2
009_2014_p_Publication_Year%26queryText%3Dphone+pc

Ref. No. Document Title Date of Release/ Publication Document Source


PGBH01- Project Proposal <Give the path of your
2003- Project repository/Folder>
Proposal
Ref. No. Document Title Date of Release/ Publication Document Source
PGBH01- Functional Specification Oct 20, 2003 <Give the path of your
2003-FS Project repository/Folder>

Вам также может понравиться