Group Members and Contributions s1

Epoch Proxy Laptop

Section 1:

Group Members and Contributions:

Samuel Asakiewicz – Transparent Box Functional Diagram

Jan Cruz – Function-Means Diagram

Rodrigo Gualberto – Project Overview

Gregory Stormes – Project Justification, Additional Project Details

Section 2:

Project Overview:

The goal of our project is to design and build a portable, light-weight device with the capabilities of using Remote Desktop software efficiently. The current name of the product is “Epoch Proxy Laptop”. Portability is an absolute necessity and as such, the device must be small. It will resemble the design of a Netbook computer, which will allow it to be easily carried and stored in a variety of locations. Reasonable to high performance speed is also necessary so that the intended running applications will not appear to stall or crash. With that requirement in mind, the operating system implemented will be stripped down to its most basic of functions. That is not to say that the device will be unappealing but rather more suited to its specific function.

With the proposed underlying hardware and software structure, a Remote Desktop program can be created or installed onto the device. In its simplest form, the device will simply act as a terminal with which to access other devices. Access to certain devices will be granted, assuming the correct username and password combination is given. This information will either be stored in a database separate from the terminal computer (intermediary server that is involved in accessing a remote computer). This aspect may not be included as it may affect performance depending on how much information is to be stored in the database, but on the other hand it is important for security purposes.

The device itself will come with its own lightweight remote desktop software with basic features like similar current products. It will be streamlined to function specifically with the hardware and its design will be similar to that of an embedded system. Additionally, if the user so desires, the device will also allow a third-party application to be installed. This gives users the option to customize or use programs they have already become familiar with.

Project Justification:

The moment the user leaves the desktop they have limited compute capabilities and access to information. Applications are not duplicated across devices and storage capabilities are very limited in some cases. Media captured or created while remote will need to be synchronized at some point if the user wants to aggregate the files in a single location. The effect is that even though portable devices are connected they are still islands of computing capabilities.

§  Multiple platforms are “islands” of computing power

o  Multiple CPU platforms (desktop, laptop, smart phone, tablet, etc.), besides mobility, and some redundancy, there is little additive benefit to having multiple platforms. While one is being used the others are usually dormant.

o  While Media standardization and web access have allowed for better access to files the actual compute functions are still mostly stand alone.

§  Average user has limited mobile computing power

o  Desktop computers (at home or at work) continue to be more powerful and capable than remote solutions.

o  Mobile devices have become increasingly more powerful but still lack the storage, interfaces, memory and CPU power of the desktop

§  Solutions exist to remotely access computers but are not robust

o  Power users may utilize tools like Remote Desktop but not the avg. user

o  Lag time and interface limitations prevent a fully emulated desktop experience.

The areas of deficiency identified create an opportunity for advancement and improvements to enable better access to data, reduce over-all cost of computing ownership and provide for other enhancements such as security and reliability.

§  Improve Mobile Users Access to Data and Applications

§  Reduce Cost Associated with Multiple Platforms

§  Potentially :

o  Improve Remote Access Network Issues

o  Address Network Latency and Reliability Issues

o  Add a Layer of Security

§  Remote clients would have encryption and authentication

§  Data is actually securely locked in a central location and can’t be lost or stolen if a device is lost

Additional Project Details:

The major aspect of the project is the creation and utilization of a Remote Desktop program created specifically for use within this product. This may be done completely by the group or previously developed, public software can be adapted for usage in this project. The second option is most likely except that it involves potential copyright requirements before the software can be utilized. Since a large amount of Remote Desktop software exists with varying costs and capabilities, it is quite possible to obtain one of these for usage in this project. A full list of these and a comparison of their properties is available at: http://en.wikipedia.org/wiki/Comparison_of_remote_desktop_software . The software chosen will also change the performance metrics of the overall product. This is because of the varying capabilities of the Remote Desktop software. One important aspect is the potential inclusion of a downgrading inherent in the software. The remote computer may be running at higher resolution with various display settings that would lead to a larger message being necessary to provide all the information to the terminal computer. For example, the size of the transmission of the desktop of a remote computer to the Epoch Proxy Laptop can be reduced by ignoring the fact that the remote computer is using Windows Aero rather than a classic theme. However, this can be considered a reduction in capability from the remote computer to the terminal computer which conflicts with the intentions of the project. The final product should be a terminal computer which performs as if the remote computer existed in front of the user instead.

Another important aspect of this project is the security inherently necessary for the success of a product such as this. The Epoch Proxy Laptop could potentially be used to access any computer. For certain secure locations to permit remote access to their computers (such as businesses with sensitive information) some security is required. This will involve a database that is separate from the terminal computers and accessed each time a remote connection is attempted. This database, known as the “Remote Desktop Database”, would likely be necessary at multiple locations as the product becomes more successful across the world. It would be maintained by employees and would probably include a Help Desk to answer questions involving any problems users encounter. However, it will only be required when initially accessing a remote computer so that there is no additional travel time for transmissions between the remote and terminal computers. The database will contain log on information for the users as well as the remote computers these users are permitted to access. If this security is insufficient for certain situations, then it can be improved upon. Some amount of base security will also be necessary since the transmissions between remote and terminal computers could contain data that could be reconstructed into sensitive information. This is especially problematic when connecting through wireless since it is inherently more insecure. However, the problem is difficult to solve by our own project since it involves the improvement of wireless security wherever it is present. The hope is that as this product becomes popular various businesses would be inclined to improve their wireless security to accommodate users.

Function-Means Diagram Description:

The above diagram describes the functions of the Epoch Proxy Laptop and the means through which these functions are performed. Functions are denoted by a blue trapezoid surrounding the box. They are also easily identifiable due to the usage of verbs within each square. As indicated in the basic descriptions about the product, the Epoch Proxy Laptop’s primary function is to access a remote computer. This not only entails connecting to the other computer, but also transmitting user inputs to the computer. The terminal (or local) computer must also receive updates from the remote computer and change its display accordingly. These aspects are indicated through the “Process User Inputs” and “Display Outputs” functions and their associated means. This is performed while retaining the capabilities of typical laptops (such as the “Connect to Internet/Peripherals” function and its associated mean). All transmissions between the local and remote computer occur utilizing the “Internet” means which also involves necessary “Security” for safe transmission and the required means to utilize Internet connections.

Transparent Box Functional Diagram:

Transparent Box Diagram Description:

This transparent box diagram details the remote desktop PC, Proxy laptop, and the connection between the two. The remote side of the chart must be setup beforehand, in that the desktop must be running, connected to the internet, and prepared to accept remote connection. During the entire time the desktop is waiting for a remote connection it will be using power and generating heat despite being mostly idle. The local laptop, by contrast, can be turned off or disconnected when not in use and the due to the bare boned capabilities of the laptop it will have low energy consumption. Another difference that is not apparent from the diagram is the bandwidth usage. The desktop will mainly upload data; even if the display data is highly compressed it will still require a decent upload capacity. The laptop’s bandwidth will mainly go to downloading, requiring very minimal uploading capacities. This block diagram is heavily simplified in regard he internet and LAN section. For the sake of a simple readable graph other machines such as router or servers are left out due to their minimal importance in the scope of our project.