team1-requirements

team1-requirements - Team 1 Android Remote CS307 ANDROID...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
Team 1 Android Remote CS307 ANDROID REMOTE TEAM 1 LILI LUO AMY HARLAN NATHAN RADEBAUGH RUDY SEVILE 1
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Team 1 Android Remote CS307 PROBLEM: There is a major hurdle for developers of the Android operating system. Many different hardware sets have been made for Android, and these sets run different versions of the Operating System. A developer needs to run his or her application on many devices to verify that the application is bug proof and runs smoothly. We want to alleviate this problem by creating a system that allows a developer to access a database of connected devices and remotely control and monitor any of those devices. BACKGROUND INFORMATION: There is a strong need for a multi-hardware testing system, as testing software is one of the strongest guarantees that an application works as expected. The financial cost associated with acquiring many devices is high, due to the cost of smartphones and tablets. Also, software updates are frequent and new devices that run the Android operating system come out every month. For those reasons, there is a strong need for a system that allows for quick, remote application testing with ease. For the users of the systems, it will be very important that the system keeps track of which smartphones and tablets are available for testing and knows their brand and model, as well as the firmware version running on the device. Two limitations have been decided to make the project more achievable. Our first limitation is to test the system on our own local router. Using our own router, we do not have to go through the Internet, and thus, we avoid the problem of NAT routing. There are multiple solutions for this problem but implementing a solution that performs well would be a challenge given our time constraints. To reduce the complexity of the project, we will not discuss too much about security. We will assume that each device is ‘public’, and thus everyone can access and test on it. This second limitation goes hand in hand with our first limitation; because the system is developed to work on LAN network and not through the Internet, the danger of having an unknown individual take control of the device is greatly reduced. 2
Background image of page 2
Team 1 Android Remote CS307 ENVIRONMENT AND SYSTEM MODELS: There will be three main components to the system. We will have a client/server architecture at two levels of the system. There will be a main server that communicates with both the client host application, that is the computer that the user will interact with (we will refer to it as “host”), and the multiple smartphones. Each smartphone will also act as a server, allowing an application on the computer, or host, to connect to the smartphone and remotely
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 9

team1-requirements - Team 1 Android Remote CS307 ANDROID...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online