diff --git a/README.md b/README.md
new file mode 100644
index 0000000..ea0873c
--- /dev/null
+++ b/README.md
@@ -0,0 +1,90 @@
+# EdgeCloudSim: An Environment for Performance Evaluation of Edge Computing Systems
+
+EdgeCloudSim provides a simulation environment specific to Edge Computing scenarios where it is possible to conduct experiments that considers both computational and networking resources. EdgeCloudSim is based on CloudSim but adds considerable functionality so that it can be efficiently used for Edge Computing scenarios.
+
+EdgeCloudSim provides a modular architecture to provide support for a variety of crucial functionality such as network modeling specific to WLAN and WAN, device mobility model, realistic and tunable load generator. As depicted in Figure 2, in the current EdgeCloudSim version there are five main modules available, namely: Core Simulation, Networking, Load Generator, Mobility and Edge Orchestrator. To ease fast prototyping efforts, each module contains a default implementation that can be extended easily.
+
+
+ 
+
+ Figure 1: Relationship between EdgeCloudSim modules.
+
+
+
+## Mobility Module
+The mobility module manages the location of edge devices and clients. Since CloudSim focuses on the conventional cloud computing principles, the mobility is not considered in the framework. In our design, each mobile device has x and y coordinates which are updated according to the dynamically managed hash table. By default, we provide a nomadic mobility model but different mobility models can be implemented by extending abstract MobilityModel class.
+
+
+ 
+
+
+## Load Generator Module
+The load generator module is responsible for generating tasks for the given configuration. By default, the tasks are generated according to a Poisson distribution via active/idle task generation pattern. If other task generation pattern is required, abstract LoadGeneratorModel class should be extended.
+
+
+ 
+
+
+## Networking Module
+The networking module particularly handles the transmission delay in the WLAN and WAN by considering both upload and download data. The default implementation of the networking module is based on a single server queue model. Users o EdgeCloudSim can incorporate their own network behavior models by extending abstract NetworkModel class.
+
+
+ 
+
+
+## Edge Orchestrator Module
+The edge orchestrator module is the decision maker of the system. It uses the information collected from the other modules to decide how and where to handle incoming client requests. In the first version, we simply use a probabilistic approach to decide where to handle incoming tasks but more realistic edge orchestrator can be added by extending abstract EdgeOrchestrator class.
+
+
+ 
+
+
+## Core Simulation Module
+The core simulation module is responsible for loading and running the Edge Computing scenarios from the configuration files. In addition, it offers a logging mechanism to save the simulation results into the files. The results are saved in comma-separated value (CSV) data format by default, but it can be changed to any format.
+
+## Extensibility
+EdgeCloudSim uses a factory pattern making easier to integrate new models mentioned above. As shown in Figure 2, EdgeCloudsim requires a scenario factory class which knows the creation logic of the abstract modules. If you want to use different mobility, load generator, networking and edge orchestrator module, you can use your own scenario factory which provides the concrete implementation of your custom modules.
+
+
+ 
+
+ Figure 2: Class Diagram of Important Modules
+
+
+
+## Ease of Use
+At the beginning of our study, we observed that too many parameters are used in the simulations and managing these parameters programmatically is very difficult.
+As a solution, we propose to use configuration files to manage the parameters.
+EdgeCloudSim reads parameters dynamically from the following files:
+- **config.properties:** Simulation settings are managed in configuration file
+- **applications.xml:** Application properties are stored in xml file
+- **edge_devices.xml:** Edge devices (datacenters, hosts, VMs etc.) are defined in xml file
+
+
+ 
+
+
+## Compilation and Running
+To compile sample application, *compile.sh* script which is located in *scripts/sample_application* folder can be used. You can rewrite similar script for your own application by modifying the arguments of javac command in way to declare the java file which includes your main method. Please note that, this script can run on Linux based systems, including Mac OS. You can also use your favorite IDE (eclipse, netbeans etc.) to compile your project.
+
+In order to run multiple sample_application scenarios in parallel, you can use *run_scenarios.sh* script which is located in *scripts/sample_application* folder. To run your own application, you need to modify java command in *runner.sh* script in a way to declare the java class which includes your main method. The details of using this script is explained in [this](/wiki/How-to-run-EdgeCloudSim-application-in-parallel) wiki page.
+
+You can also monitor each process via the output files located under *scripts/sample_application/output/date* folder. For example:
+```
+./run_scenarios.sh 8 10
+tail -f output/date/ite_1.log
+```
+
+## Analyzing the Results
+At the end of each iteration, simulation results will be compressed in the *output/date/ite_n.tgz* files. When you extract these tgz files, you would see lots of log file in csv format. You can find matlab files which can plot graphics by using these files under *scripts/sample_application/matlab* folder. You can also write other scripts (e.g. python scripts) with the same manner of matlab plotter files.
+
+## Example Output of EdgeCloudSim
+You can plot lots of graphics by using the result of EdgeCloudSim. Some examples are given below:
+
+ 
+
+ 
+
+ 
+
+ 