DOTNET 2013 IEEE MOBILECOMPUTING PROJECT Model based analysis of wireless system architectures for real-time applications

MODEL-BASED ANALYSIS OF WIRELESS SYSTEM

ARCHITECTURES

FOR REAL-TIME APPLICATIONS

ABSTRACT:

We propose a model-based description and analysis framework for the design of wireless system architectures.

Its aim is to address the shortcomings of existing approaches to system verification and the tracking of

anomalies in safety-critical wireless systems. We use Architecture Analysis and Description Language (AADL)

to describe an analysis-oriented architecture model with highly modular components.

We develop the cooperative tool chains required to analyze the performance of a wireless system by simulation.

We show how this framework can support a detailed and largely automated analysis of a complicated,

networked wireless system using examples from wireless healthcare and video broadcasting.

We proposed a model-based description and analysis framework for the design of wireless system architectures.

Using AADL, the de facto standard formal architecture description language, we have demonstrated how a high

level of modularity can be achieved in simulated wireless network systems. We showed that our framework can

support detailed and largely automated analysis of complicated networked wireless systems.

GLOBALSOFT TECHNOLOGIESIEEE PROJECTS & SOFTWARE DEVELOPMENTS

IEEE FINAL YEAR PROJECTS|IEEE ENGINEERING PROJECTS|IEEE STUDENTS PROJECTS|IEEE

BULK PROJECTS|BE/BTECH/ME/MTECH/MS/MCA PROJECTS|CSE/IT/ECE/EEE PROJECTS

CELL: +91 98495 39085, +91 99662 35788, +91 98495 57908, +91 97014 40401

Visit: www.finalyearprojects.org Mail to:[email protected]

mailto:[email protected]

EXISTING SYSTEM:

In our previous working in a simulation and analysis framework for 3G broadcasting systems to address these

challenges this flexible framework facilitates not only the analysis of individual network and system modules

but also the end-to-end analysis of an entire system for providing multimedia broadcasting services.

PROBLEM DESCRIPTION:

However, the following two problems remain:

1) The description of system models and the behavior of the entire system have not been formally specified

2) The correctness of the input parameters of each module in the system and their compatibility across layers

cannot yet be verified both rigorously and automatically. This leaves the system development process

vulnerable to human errors in specification, simulation, and verification.

PROPOSED SYSTEM:

We propose a model-based description and analysis framework for the design of wireless system architectures.

Its aim is to address the shortcomings of existing approaches to system verification and the tracking of

anomalies in safety-critical wireless systems. We use Architecture Analysis and Description Language (AADL)

to describe an analysis-oriented architecture model with highly modular components.

We develop the cooperative tool chains required to analyze the performance of a wireless system by simulation.

We show how this framework can support a detailed and largely automated analysis of a complicated,

networked wireless system using examples from wireless healthcare and video broadcasting.

AADL provides well-defined models of the hardware and software components used in embedded systems.

These models have common standard semantics that are well understood among the research community,

thereby facilitating the correct interpretation of the models.

Our current analysis does not make use of all the predefined modeling components (processor, memory, and

device) that AADL provides; we expect that the extensibility of AADL models will enable us to expand the

coverage of our analysis to include specific hardware and software implementations in the future.

HARDWARE & SOFTWARE REQUIREMENTS:

HARDWARE REQUIREMENT:

Processor - Pentium –IV

Speed - 1.1 GHz

RAM - 256 MB (min)

Hard Disk - 20 GB

Floppy Drive - 1.44 MB

Key Board - Standard Windows Keyboard

Mouse - Two or Three Button Mouse

Monitor - SVGA

SOFTWARE REQUIREMENTS:

Operating System : Windows XP

Application Server : ASP .NET Web Server

Front End : ASP .NET & C# .NET

Scripts : C# Script.

Database : SQL SERVER 2005

MODULES:

SERVER CLIENT MODULE:

MODEL BASED ANALYSIS:

ANALYSIS OF AADL:

VIDEO APPLICATION MODEL:

PERFORMANCE ANALYSIS:

ARCHITECTURE DIAGRAM:

AADL MODEL DIAGRAM:

SYSTEM DESIGN:

Data Flow Diagram / Use Case Diagram / Flow Diagram

The DFD is also called as bubble chart. It is a simple graphical formalism that can be used to represent a system

in terms of the input data to the system, various processing carried out on these data, and the output data is

generated by the system.

DATAFLOW DIAGRAM:

CLASS DIAGRAM:

ACTIVITY DIAGRAM:

SEQUENCE DIAGRAM:

USE CASE DIAGRAM:

SYSTEM STUDY:

FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put forth with a very

general plan for the project and some cost estimates. During system analysis the feasibility study of the

proposed system is to be carried out. This is to ensure that the proposed system is not a burden to the

company. For feasibility analysis, some understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

ECONOMICAL FEASIBILITY

TECHNICAL FEASIBILITY

SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that the system will have on the organization. The

amount of fund that the company can pour into the research and development of the system is limited. The

expenditures must be justified. Thus the developed system as well within the budget and this was achieved

because most of the technologies used are freely available. Only the customized products had to be purchased.

TECHNICAL FEASIBILITY

This study is carried out to check the technical feasibility, that is, the technical requirements of the system.

Any system developed must not have a high demand on the available technical resources. This will lead to high

demands on the available technical resources. This will lead to high demands being placed on the client. The

developed system must have a modest requirement, as only minimal or null changes are required for

implementing this system.

SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the user. This includes the

process of training the user to use the system efficiently. The user must not feel threatened by the system,

instead must accept it as a necessity. The level of acceptance by the users solely depends on the methods that

are employed to educate the user about the system and to make him familiar with it. His level of confidence

must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final

user of the system.

SYSTEM TESTING

The purpose of testing is to discover errors. Testing is the process of trying to discover every

conceivable fault or weakness in a work product. It provides a way to check the functionality of components,

sub assemblies, assemblies and/or a finished product It is the process of exercising software with the intent of

ensuring that the

Software system meets its requirements and user expectations and does not fail in an unacceptable manner.

There are various types of test. Each test type addresses a specific testing requirement.

TYPES OF TESTS

Unit testing

Unit testing involves the design of test cases that validate that the internal program logic is functioning

properly, and that program inputs produce valid outputs. All decision branches and internal code flow should be

validated. It is the testing of individual software units of the application .it is done after the completion of an

individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is

invasive. Unit tests perform basic tests at component level and test a specific business process, application,

and/or system configuration. Unit tests ensure that each unique path of a business process performs accurately

to the documented specifications and contains clearly defined inputs and expected results.

Integration testing

Integration tests are designed to test integrated software components to determine if they actually run as

one program. Testing is event driven and is more concerned with the basic outcome of screens or fields.

Integration tests demonstrate that although the components were individually satisfaction, as shown by

successfully unit testing, the combination of components is correct and consistent. Integration testing is

specifically aimed at exposing the problems that arise from the combination of components.

Functional test

Functional tests provide systematic demonstrations that functions tested are available as specified by the

business and technical requirements, system documentation, and user manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions, or special test

cases. In addition, systematic coverage pertaining to identify Business process flows; data fields, predefined

processes, and successive processes must be considered for testing. Before functional testing is complete,

additional tests are identified and the effective value of current tests is determined.

System Test

System testing ensures that the entire integrated software system meets requirements. It tests a configuration

to ensure known and predictable results. An example of system testing is the configuration oriented system

integration test. System testing is based on process descriptions and flows, emphasizing pre-driven process links

and integration points.

White Box Testing

White Box Testing is a testing in which in which the software tester has knowledge of the inner workings,

structure and language of the software, or at least its purpose. It is purpose. It is used to test areas that cannot be

reached from a black box level.

Black Box Testing

Black Box Testing is testing the software without any knowledge of the inner workings, structure or

language of the module being tested. Black box tests, as most other kinds of tests, must be written from a

definitive source document, such as specification or requirements document, such as specification or

requirements document. It is a testing in which the software under test is treated, as a black box .you cannot

“see” into it. The test provides inputs and responds to outputs without considering how the software works.

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle,

although it is not uncommon for coding and unit testing to be conducted as two distinct phases.

Test strategy and approach

Field testing will be performed manually and functional tests will be written in detail.

Test objectives

All field entries must work properly.

Pages must be activated from the identified link.

The entry screen, messages and responses must not be delayed.

Features to be tested

Verify that the entries are of the correct format

No duplicate entries should be allowed

All links should take the user to the correct page.

6.2 Integration Testing

Software integration testing is the incremental integration testing of two or more integrated software

components on a single platform to produce failures caused by interface defects.

The task of the integration test is to check that components or software applications, e.g. components in

a software system or – one step up – software applications at the company level – interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

6.3 Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires significant participation by the

end user. It also ensures that the system meets the functional requirements.

Test Results: All the test cases mentioned above passed successfully. No defects encountered.

Software Environment

Features Of .Net

Microsoft .NET is a set of Microsoft software technologies for rapidly building and integrating

XML Web services, Microsoft Windows-based applications, and Web solutions. The .NET Framework is a

language-neutral platform for writing programs that can easily and securely interoperate. There’s no language

barrier with .NET: there are numerous languages available to the developer including Managed C++, C#, Visual

Basic and Java Script. The .NET framework provides the foundation for components to interact seamlessly,

whether locally or remotely on different platforms. It standardizes common data types and communications

protocols so that components created in different languages can easily interoperate.

“.NET” is also the collective name given to various software components built upon the .NET

platform. These will be both products (Visual Studio.NET and Windows.NET Server, for instance) and services

(like Passport, .NET My Services, and so on).

THE .NET FRAMEWORK

The .NET Framework has two main parts:

1. The Common Language Runtime (CLR).

2. A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the environment within which programs

run. The most important features are

Conversion from a low-level assembler-style language, called Intermediate Language (IL), into

code native to the platform being executed on.

Memory management, notably including garbage collection.

Checking and enforcing security restrictions on the running code.

Loading and executing programs, with version control and other such features.

The following features of the .NET framework are also worth description:

Managed Code

The code that targets .NET, and which contains certain extra Information - “metadata” - to describe

itself. Whilst both managed and unmanaged code can run in the runtime, only managed code contains the

information that allows the CLR to guarantee, for instance, safe execution and interoperability.

Managed Data

With Managed Code comes Managed Data. CLR provides memory allocation and Deal location

facilities, and garbage collection. Some .NET languages use Managed Data by default, such as C#, Visual

Basic.NET and JScript.NET, whereas others, namely C++, do not. Targeting CLR can, depending on the

language you’re using, impose certain constraints on the features available. As with managed and unmanaged

code, one can have both managed and unmanaged data in .NET applications - data that doesn’t get garbage

collected but instead is looked after by unmanaged code.

Common Type System

The CLR uses something called the Common Type System (CTS) to strictly enforce type-safety. This

ensures that all classes are compatible with each other, by describing types in a common way. CTS define how

types work within the runtime, which enables types in one language to interoperate with types in another

language, including cross-language exception handling. As well as ensuring that types are only used in

appropriate ways, the runtime also ensures that code doesn’t attempt to access memory that hasn’t been

allocated to it.

Common Language Specification

The CLR provides built-in support for language interoperability. To ensure that you can develop

managed code that can be fully used by developers using any programming language, a set of language features

and rules for using them called the Common Language Specification (CLS) has been defined. Components that

follow these rules and expose only CLS features are considered CLS-compliant.

THE CLASS LIBRARY

.NET provides a single-rooted hierarchy of classes, containing over 7000 types. The root of the

namespace is called System; this contains basic types like Byte, Double, Boolean, and String, as well as Object.

All objects derive from System. Object. As well as objects, there are value types. Value types can be allocated

on the stack, which can provide useful flexibility. There are also efficient means of converting value types to

object types if and when necessary.

The set of classes is pretty comprehensive, providing collections, file, screen, and network I/O,

threading, and so on, as well as XML and database connectivity.

The class library is subdivided into a number of sets (or namespaces), each providing distinct

areas of functionality, with dependencies between the namespaces kept to a minimum.

LANGUAGES SUPPORTED BY .NET

The multi-language capability of the .NET Framework and Visual Studio .NET enables developers to

use their existing programming skills to build all types of applications and XML Web services. The .NET

framework supports new versions of Microsoft’s old favorites Visual Basic and C++ (as VB.NET and Managed

C++), but there are also a number of new additions to the family.

Visual Basic .NET has been updated to include many new and improved language features that

make it a powerful object-oriented programming language. These features include inheritance, interfaces, and

overloading, among others. Visual Basic also now supports structured exception handling, custom attributes and

also supports multi-threading.

Visual Basic .NET is also CLS compliant, which means that any CLS-compliant language can

use the classes, objects, and components you create in Visual Basic .NET.

Managed Extensions for C++ and attributed programming are just some of the enhancements

made to the C++ language. Managed Extensions simplify the task of migrating existing C++ applications to the

new .NET Framework.

C# is Microsoft’s new language. It’s a C-style language that is essentially “C++ for Rapid

Application Development”. Unlike other languages, its specification is just the grammar of the language. It has

no standard library of its own, and instead has been designed with the intention of using the .NET libraries as its

own.

Microsoft Visual J# .NET provides the easiest transition for Java-language developers into the world of

XML Web Services and dramatically improves the interoperability of Java-language programs with existing

software written in a variety of other programming languages.

Active State has created Visual Perl and Visual Python, which enable .NET-aware applications to be

built in either Perl or Python. Both products can be integrated into the Visual Studio .NET environment. Visual

Perl includes support for Active State’s Perl Dev Kit.

Other languages for which .NET compilers are available include

FORTRAN

COBOL

Eiffel

Fig1 .Net Framework

ASP.NET

XML WEB SERVICES

Windows Forms

Base Class Libraries

Common Language Runtime

Operating System

C#.NET is also compliant with CLS (Common Language Specification) and supports structured exception

handling. CLS is set of rules and constructs that are supported by the CLR (Common Language Runtime).

CLR is the runtime environment provided by the .NET Framework; it manages the execution of the code

and also makes the development process easier by providing services.

C#.NET is a CLS-compliant language. Any objects, classes, or components that created in C#.NET can be

used in any other CLS-compliant language. In addition, we can use objects, classes, and components

created in other CLS-compliant languages in C#.NET .The use of CLS ensures complete interoperability

among applications, regardless of the languages used to create the application.

CONSTRUCTORS AND DESTRUCTORS:

Constructors are used to initialize objects, whereas destructors are used to destroy them. In other

words, destructors are used to release the resources allocated to the object. In C#.NET the sub finalize

procedure is available. The sub finalize procedure is used to complete the tasks that must be performed

when an object is destroyed. The sub finalize procedure is called automatically when an object is

destroyed. In addition, the sub finalize procedure can be called only from the class it belongs to or from

derived classes.

GARBAGE COLLECTION

Garbage Collection is another new feature in C#.NET. The .NET Framework monitors allocated resources,

such as objects and variables. In addition, the .NET Framework automatically releases memory for reuse by

destroying objects that are no longer in use.

In C#.NET, the garbage collector checks for the objects that are not currently in use by applications. When

the garbage collector comes across an object that is marked for garbage collection, it releases the memory

occupied by the object.

OVERLOADING

Overloading is another feature in C#. Overloading enables us to define multiple procedures with the same

name, where each procedure has a different set of arguments. Besides using overloading for procedures,

we can use it for constructors and properties in a class.

MULTITHREADING:

C#.NET also supports multithreading. An application that supports multithreading can handle multiple

tasks simultaneously, we can use multithreading to decrease the time taken by an application to respond

to user interaction.

STRUCTURED EXCEPTION HANDLING

C#.NET supports structured handling, which enables us to detect and remove errors at runtime.

In C#.NET, we need to use Try…Catch…Finally statements to create exception handlers. Using Try…Catch…

Finally statements, we can create robust and effective exception handlers to improve the performance of

our application.

THE .NET FRAMEWORK

The .NET Framework is a new computing platform that simplifies application development in the highly

distributed environment of the Internet.

OBJECTIVES OF. NET FRAMEWORK

1. To provide a consistent object-oriented programming environment whether object codes is stored and

executed locally on Internet-distributed, or executed remotely.

2. To provide a code-execution environment to minimizes software deployment and guarantees safe

execution of code.

3. Eliminates the performance problems.

There are different types of application, such as Windows-based applications and Web-based applications.

4.3 Features of SQL-SERVER

The OLAP Services feature available in SQL Server version 7.0 is now called SQL Server 2000

Analysis Services. The term OLAP Services has been replaced with the term Analysis Services. Analysis

Services also includes a new data mining component. The Repository component available in SQL Server

version 7.0 is now called Microsoft SQL Server 2000 Meta Data Services. References to the component now

use the term Meta Data Services. The term repository is used only in reference to the repository engine within

Meta Data Services

SQL-SERVER database consist of six type of objects,

They are,

1. TABLE

2. QUERY

3. FORM

4. REPORT

5. MACRO

TABLE:

A database is a collection of data about a specific topic.

VIEWS OF TABLE:

We can work with a table in two types,

1. Design View

2. Datasheet View

Design View

To build or modify the structure of a table we work in the table design view. We can

specify what kind of data will be hold.

Datasheet View

To add, edit or analyses the data itself we work in tables datasheet view mode.

QUERY:

A query is a question that has to be asked the data. Access gathers data that answers the question from

one or more table. The data that make up the answer is either dynaset (if you edit it) or a snapshot (it cannot be

edited).Each time we run query, we get latest information in the dynaset. Access either displays the dynaset or

snapshot for us to view or perform an action on it, such as deleting or updating.

SAMPLE CODE:

namespace ServerSource1

{

partial class Form1

{

/// <summary>

/// Required designer variable.

/// </summary>

private System.ComponentModel.IContainer components = null;

/// <summary>

/// Clean up any resources being used.

/// </summary>

/// <param name="disposing">true if managed resources should be disposed; otherwise, false.</param>

protected override void Dispose(bool disposing)

{

if (disposing && (components != null))

{

components.Dispose();

}

base.Dispose(disposing);

}

#region Windows Form Designer generated code

/// <summary>

/// Required method for Designer support - do not modify

/// the contents of this method with the code editor.

/// </summary>

private void InitializeComponent()

{

this.openFileDialog1 = new System.Windows.Forms.OpenFileDialog();

this.openFileDialog2 = new System.Windows.Forms.OpenFileDialog();

this.panel2 = new System.Windows.Forms.Panel();

this.groupBox3 = new System.Windows.Forms.GroupBox();


this.label3 = new System.Windows.Forms.Label();

this.txtIp = new System.Windows.Forms.TextBox();


this.pictureBox3 = new System.Windows.Forms.PictureBox();



this.button2 = new System.Windows.Forms.Button();


this.textBox2 = new System.Windows.Forms.TextBox();




this.lblError = new System.Windows.Forms.Label();

this.panel2.SuspendLayout();

this.groupBox3.SuspendLayout();



((System.ComponentModel.ISupportInitialize)(this.pictureBox3)).BeginInit();




this.SuspendLayout();

//

// openFileDialog1

//

this.openFileDialog1.FileName = "openFileDialog1";

//

// openFileDialog2

//

this.openFileDialog2.FileName = "openFileDialog2";

//

// panel2

//

this.panel2.BackColor = System.Drawing.Color.LightSalmon;

this.panel2.BackgroundImageLayout = System.Windows.Forms.ImageLayout.Stretch;

this.panel2.Controls.Add(this.groupBox3);

this.panel2.Controls.Add(this.label4);

this.panel2.Controls.Add(this.label1);

this.panel2.Controls.Add(this.pictureBox6);

this.panel2.Controls.Add(this.lblError);

this.panel2.Location = new System.Drawing.Point(3, 1);

this.panel2.Name = "panel2";

this.panel2.Size = new System.Drawing.Size(925, 668);

this.panel2.TabIndex = 5;

//

// groupBox3

//

this.groupBox3.Controls.Add(this.groupBox2);

this.groupBox3.Controls.Add(this.groupBox1);

this.groupBox3.Location = new System.Drawing.Point(24, 122);

this.groupBox3.Name = "groupBox3";

this.groupBox3.Size = new System.Drawing.Size(514, 464);

this.groupBox3.TabIndex = 8;

this.groupBox3.TabStop = false;

//

// groupBox2

//

this.groupBox2.BackColor = System.Drawing.Color.Transparent;

this.groupBox2.Controls.Add(this.label3);

this.groupBox2.Controls.Add(this.txtIp);

this.groupBox2.Font = new System.Drawing.Font("Lucida Bright", 11.25F,

System.Drawing.FontStyle.Bold, System.Drawing.GraphicsUnit.Point, ((byte)(0)));

this.groupBox2.ForeColor = System.Drawing.Color.Cornsilk;






this.groupBox2.Text = "IPADDRESS";

//

// label3

//

this.label3.AutoSize = true;

this.label3.Font = new System.Drawing.Font("Comic Sans MS", 12F, System.Drawing.FontStyle.Bold,

System.Drawing.GraphicsUnit.Point, ((byte)(0)));

this.label3.ForeColor = System.Drawing.Color.Black;

this.label3.Location = new System.Drawing.Point(15, 25);

this.label3.Name = "label3";

this.label3.Size = new System.Drawing.Size(155, 23);

this.label3.TabIndex = 7;

this.label3.Text = "Enter IpAddress :";

//

// txtIp

//

this.txtIp.BackColor = System.Drawing.Color.Snow;

this.txtIp.Font = new System.Drawing.Font("Rockwell", 13F, System.Drawing.FontStyle.Bold);

this.txtIp.Location = new System.Drawing.Point(194, 24);

this.txtIp.Name = "txtIp";

this.txtIp.Size = new System.Drawing.Size(185, 28);

this.txtIp.TabIndex = 4;

this.txtIp.TextAlign = System.Windows.Forms.HorizontalAlignment.Center;

//

// groupBox1

//

this.groupBox1.BackColor = System.Drawing.Color.Transparent;

this.groupBox1.Controls.Add(this.pictureBox3);



this.groupBox1.Controls.Add(this.button2);

this.groupBox1.Controls.Add(this.label2);

this.groupBox1.Controls.Add(this.textBox2);

this.groupBox1.Font = new System.Drawing.Font("Calibri", 14F, System.Drawing.FontStyle.Italic);

this.groupBox1.ForeColor = System.Drawing.Color.Cornsilk;






this.groupBox1.Text = "file browsing - 1";

//

// pictureBox3

//

this.pictureBox3.Cursor = System.Windows.Forms.Cursors.Hand;

this.pictureBox3.Image = global::ServerSource1.Properties.Resources.sender1;

this.pictureBox3.Location = new System.Drawing.Point(510, 184);

this.pictureBox3.Name = "pictureBox3";

this.pictureBox3.Size = new System.Drawing.Size(102, 141);

this.pictureBox3.SizeMode = System.Windows.Forms.PictureBoxSizeMode.AutoSize;

this.pictureBox3.TabIndex = 24;

this.pictureBox3.TabStop = false;

//

// pictureBox4

//

this.pictureBox4.Image = global::ServerSource1.Properties.Resources.Folder_02_june;




this.pictureBox4.SizeMode = System.Windows.Forms.PictureBoxSizeMode.StretchImage;



this.pictureBox4.Visible = false;

//

// pictureBox5

//

this.pictureBox5.Cursor = System.Windows.Forms.Cursors.Hand;

this.pictureBox5.Image = global::ServerSource1.Properties.Resources._11;




this.pictureBox5.SizeMode = System.Windows.Forms.PictureBoxSizeMode.StretchImage;



this.pictureBox5.Click += new System.EventHandler(this.pictureBox5_Click);

//

// button2

//

this.button2.BackColor = System.Drawing.Color.PeachPuff;

this.button2.Cursor = System.Windows.Forms.Cursors.Hand;

this.button2.Font = new System.Drawing.Font("Rockwell", 12F, ((System.Drawing.FontStyle)

((System.Drawing.FontStyle.Bold | System.Drawing.FontStyle.Italic))), System.Drawing.GraphicsUnit.Point,

((byte)(0)));

this.button2.ForeColor = System.Drawing.Color.Orange;

this.button2.Location = new System.Drawing.Point(290, 23);

this.button2.Name = "button2";

this.button2.Size = new System.Drawing.Size(99, 32);

this.button2.TabIndex = 10;

this.button2.Text = "BROWSE";

this.button2.UseVisualStyleBackColor = false;

this.button2.Click += new System.EventHandler(this.button2_Click);

//

// label2

//


this.label2.Font = new System.Drawing.Font("Cooper Black", 14.25F,

System.Drawing.FontStyle.Regular, System.Drawing.GraphicsUnit.Point, ((byte)(0)));

this.label2.ForeColor = System.Drawing.Color.Black;





this.label2.Text = "Browse a Video rar File :";

//

// textBox2

//

this.textBox2.BackColor = System.Drawing.Color.Snow;

this.textBox2.Font = new System.Drawing.Font("Rockwell", 12F, ((System.Drawing.FontStyle)

((System.Drawing.FontStyle.Bold | System.Drawing.FontStyle.Italic))));

this.textBox2.ForeColor = System.Drawing.SystemColors.WindowText;

this.textBox2.Location = new System.Drawing.Point(29, 61);

this.textBox2.Name = "textBox2";

this.textBox2.ReadOnly = true;

this.textBox2.Size = new System.Drawing.Size(425, 26);

this.textBox2.TabIndex = 4;

//

// label4

//


this.label4.BackColor = System.Drawing.Color.Transparent;

this.label4.Font = new System.Drawing.Font("Jokerman", 18F, System.Drawing.FontStyle.Bold,


this.label4.ForeColor = System.Drawing.Color.DarkGreen;





this.label4.Text = "Wireless Multimedia Sensor Networks";

//

// label1

//


this.label1.BackColor = System.Drawing.Color.Transparent;

this.label1.Font = new System.Drawing.Font("Jokerman", 18F, System.Drawing.FontStyle.Bold,


this.label1.ForeColor = System.Drawing.Color.DarkGreen;





this.label1.Text = "Compressed-Sensing-Enabled Video Streaming for";

//

// pictureBox6

//

this.pictureBox6.BorderStyle = System.Windows.Forms.BorderStyle.Fixed3D;

this.pictureBox6.Image = global::ServerSource1.Properties.Resources.orange_server_md;




this.pictureBox6.SizeMode = System.Windows.Forms.PictureBoxSizeMode.AutoSize;



//

// lblError

//

this.lblError.AutoSize = true;

this.lblError.BackColor = System.Drawing.Color.Transparent;

this.lblError.Font = new System.Drawing.Font("Papyrus", 14.25F, System.Drawing.FontStyle.Bold,


this.lblError.ForeColor = System.Drawing.SystemColors.ControlText;

this.lblError.Location = new System.Drawing.Point(159, 610);

this.lblError.Name = "lblError";

this.lblError.Size = new System.Drawing.Size(66, 30);

this.lblError.TabIndex = 27;

this.lblError.Text = "status";

//

// Form1

//

this.AutoScaleDimensions = new System.Drawing.SizeF(6F, 13F);

this.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font;

this.ClientSize = new System.Drawing.Size(932, 669);

this.Controls.Add(this.panel2);

this.Name = "Form1";

this.Text = "SERVER - 1";

this.Load += new System.EventHandler(this.Form1_Load);

this.panel2.ResumeLayout(false);

this.panel2.PerformLayout();

this.groupBox3.ResumeLayout(false);


this.groupBox2.PerformLayout();


this.groupBox1.PerformLayout();

((System.ComponentModel.ISupportInitialize)(this.pictureBox3)).EndInit();




this.ResumeLayout(false);

}

#endregion

private System.Windows.Forms.Label label3;

private System.Windows.Forms.TextBox txtIp;

private System.Windows.Forms.GroupBox groupBox2;

private System.Windows.Forms.Panel panel2;

private System.Windows.Forms.Label lblError;

private System.Windows.Forms.OpenFileDialog openFileDialog1;

private System.Windows.Forms.OpenFileDialog openFileDialog2;


private System.Windows.Forms.PictureBox pictureBox4;



private System.Windows.Forms.Button button2;


private System.Windows.Forms.TextBox textBox2;





}

}

ROUTER:

using System;

using System.Collections.Generic;

using System.ComponentModel;

using System.Data;

using System.Drawing;

using System.Linq;

using System.Text;

using System.Windows.Forms;

using System.Net.Sockets;

using System.Net;

using System.IO;

namespace RouterSource

{

public partial class Form1 : Form

{

int rnno, rndnumber;

double tcalc;

double tstart;

double tend;

double f, s, cf, cs, wst, wst1;

string f1, f2, f3, f4, f5, f6, f7, f8, f9, f10;

string s1, s2, s3, s4, s5, s6, s7, s8, s9, s10;

public Form1()

{

InitializeComponent();

}

ReceiverCode obj = new ReceiverCode();

ReceiverCode1 obj1 = new ReceiverCode1();

private void Form1_Load(object sender, EventArgs e)

{

backgroundWorker1.RunWorkerAsync();

backgroundWorker2.RunWorkerAsync();

}

//First Vedio File Routing

public void Routing()

{

tstart = Convert.ToDouble(DateTime.Now.Millisecond);

rndnumber = randomnumber();

//rndnumber = 4;

label14.Visible = true;

label14.Text = "Processing...";

if (rndnumber == 2)

{

tend = tstart - Convert.ToDouble(DateTime.Now.Millisecond) / 1000;

tcalc = tend;

f1 = Convert.ToString(tcalc);

label1.Text = "Processing..";

Application.DoEvents();

System.Threading.Thread.Sleep(2000);

pictureBox8.Image = RouterSource.Properties.Resources.greenpacket1;


string rStr = Path.GetRandomFileName();

rStr = rStr.Replace(".", ""); // For Removing the .

label36.Text = rStr;

pictureBox18.Image = RouterSource.Properties.Resources.okicon;

label1.Text = "Success";



label8.Text = Convert.ToString(tcalc) + " (milli seconds)";


tcalc = tend;







string rStr1 = Path.GetRandomFileName();

rStr1 = rStr1.Replace(".", ""); // For Removing the .

label35.Text = rStr1;







tcalc = tend;





pictureBox10.Image = RouterSource.Properties.Resources.redpacket3;

pictureBox20.Image = RouterSource.Properties.Resources.closeicon;

label3.Text = "Failure";



label3.Text = "Reconfigure...";














tcalc = tend;
















tcalc = tend;
























tcalc = tend;
















tcalc = tend;
























tcalc = tend;
















tcalc = tend;
















tcalc = tend;















label14.Text = "FINISH !";



RoutingRefresh();

}

else

{

if (rndnumber == 3)

{


tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
























tcalc = tend;
























tcalc = tend;
















tcalc = tend;
























tcalc = tend;
















tcalc = tend;
















tcalc = tend;


















RoutingRefresh();

}

else

{

if (rndnumber == 1 || rndnumber == 4)

{


tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
























tcalc = tend;
























tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;


















RoutingRefresh();

}

}

}

pictureBox69.Enabled = true;


send();

}

//Second Vedio File Routing

public void Routing1()

{

tstart = Convert.ToDouble(DateTime.Now.Millisecond);

rndnumber = randomnumber1();

//rndnumber = 1;

label15.Visible = true;

label15.Text = "Processing...";

if (rndnumber == 2)

{


tcalc = tend;

s1 = Convert.ToString(tcalc);















tcalc = tend;
















tcalc = tend;
























tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
























tcalc = tend;
















tcalc = tend;
















tcalc = tend;


















RoutingRefresh();

}

else

{

if (rndnumber == 3)

{


tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
























tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;


















RoutingRefresh();

}

else

{

if (rndnumber == 1 || rndnumber == 4)

{


tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
























tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;
















tcalc = tend;


















RoutingRefresh();

}

}

}



send1();

}

public void RoutingRefresh()

{

}

public void RoutingRefresh1()

{

}

//Random Select For File Transaction

public int randomnumber()

{

Random rn = new Random();

rnno = rn.Next(1, 4);

return rnno;

}

//Random Select For File Transaction

public int randomnumber1()

{

Random rn = new Random();

rnno = rn.Next(1, 4);

return rnno;

}

private void backgroundWorker1_DoWork(object sender, DoWorkEventArgs e)

{

obj.StartServer();

}

private void backgroundWorker2_DoWork(object sender, DoWorkEventArgs e)

{

obj1.StartServer1();

}

private void timer1_Tick(object sender, EventArgs e)

{

if (ReceiverCode.Rout == "Start")

{

timer1.Enabled = false;

Routing();

ReceiverCode.Rout = "";

}

}

private void timer2_Tick(object sender, EventArgs e)

{

if (ReceiverCode1.Rout1 == "Start")

{

timer2.Enabled = false;

Routing1();

ReceiverCode1.Rout1 = "";

}

}

public void send()

{

try

{

IPAddress[] ipAddress = Dns.GetHostAddresses(txtIp.Text);

IPEndPoint ipEnd = new IPEndPoint(ipAddress[0], 5656);

Socket clientSock = new Socket(AddressFamily.InterNetwork, SocketType.Stream,

ProtocolType.IP);

clientSock.Connect(ipEnd);

//clientSock.Send(ReceiverCode.send );

clientSock.Send(ReceiverCode.send);


clientSock.Close();

}

catch (Exception ex)

{

if (ex.Message == "A connection attempt failed because the connected party did not properly respond

after a period of time, or established connection failed because connected host has failed to respond")

{

MessageBox.Show("No Such System Available Try other IP");

}

else

{

if (ex.Message == "No connection could be made because the target machine actively refused it")

{

MessageBox.Show("File Sending fail. Because Client not running.");

}

else

{

MessageBox.Show("File Sending fail." + ex.Message);

}

}

}

}

public void send1()

{

try

{

IPAddress[] ipAddress = Dns.GetHostAddresses(txtIp.Text);

IPEndPoint ipEnd1 = new IPEndPoint(ipAddress[0], 5654);

Socket clientSock1 = new Socket(AddressFamily.InterNetwork, SocketType.Stream,

ProtocolType.IP);

clientSock1.Connect(ipEnd1);

//clientSock.Send(ReceiverCode.send );

clientSock1.Send(ReceiverCode1.send1);


clientSock1.Close();

}


{

if (ex.Message == "A connection attempt failed because the connected party did not properly respond

after a period of time, or established connection failed because connected host has failed to respond")

{

MessageBox.Show("No Such System Available Try other IP");

}

else

{

if (ex.Message == "No connection could be made because the target machine actively refused it")

{

MessageBox.Show("File Sending fail. Because Client not running.");

}

else

{

MessageBox.Show("File Sending fail." + ex.Message);

}

}

}

}

//CHART

private void pictureBox70_Click(object sender, EventArgs e)

{

//Routing();

//Routing1();

f = Convert.ToDouble(Convert.ToDouble(f1) + Convert.ToDouble(f2) + Convert.ToDouble(f3) +

Convert.ToDouble(f4) + Convert.ToDouble(f5) + Convert.ToDouble(f6) + Convert.ToDouble(f7) +

Convert.ToDouble(f8) + Convert.ToDouble(f9) + Convert.ToDouble(f10)) / 10;

s = Convert.ToDouble(Convert.ToDouble(s1) + Convert.ToDouble(s2) + Convert.ToDouble(s3) +

Convert.ToDouble(s4) + Convert.ToDouble(s5) + Convert.ToDouble(s6) + Convert.ToDouble(s7) +

Convert.ToDouble(s8) + Convert.ToDouble(s9) + Convert.ToDouble(s10)) / 10;

if (f < s)

{

cs = f;

cf = s;

}

else

{

cs = s;

cf = f;

}

Chart c = new Chart();

c.val = new double[3];

c.val[0] = Convert.ToDouble(cf);

c.val[1] = Convert.ToDouble(cs);

//c.val[2] = Convert.ToDouble(55);

c.txt = new string[2];

c.txt[0] = Convert.ToString("");

c.txt[1] = Convert.ToString("");

//c.txt[2] = "logesh";

c.ShowDialog();

}

//SERVICE TIME

private void pictureBox69_Click(object sender, EventArgs e)

{

f = Convert.ToDouble(Convert.ToDouble(f1) + Convert.ToDouble(f2) + Convert.ToDouble(f3) +

Convert.ToDouble(f4) + Convert.ToDouble(f5) + Convert.ToDouble(f6) + Convert.ToDouble(f7) +

Convert.ToDouble(f8) + Convert.ToDouble(f8) + Convert.ToDouble(f10)) / 10;

s = Convert.ToDouble(Convert.ToDouble(s1) + Convert.ToDouble(s2) + Convert.ToDouble(s3) +

Convert.ToDouble(s4) + Convert.ToDouble(s5) + Convert.ToDouble(s6) + Convert.ToDouble(s7) +

Convert.ToDouble(s8) + Convert.ToDouble(s9) + Convert.ToDouble(s10)) / 10;

wst = (1 / f) * 100;

wst1 = (1 / s) * 100;

ServiceTime st = new ServiceTime(f1, f2, f3, f4, f5, f6, f7, f8, f9, f10, wst, s1, s2, s3, s4, s5, s6, s7, s8,

s9, s10, wst1);

st.ShowDialog();

}

private void panel3_Paint(object sender, PaintEventArgs e)

{

}

}

class ReceiverCode

{

IPEndPoint ipEnd;

Socket sock;

public ReceiverCode()

{

IPHostEntry ipEntry = Dns.GetHostEntry(Environment.MachineName);

IPAddress IpAddr = ipEntry.AddressList[0];

ipEnd = new IPEndPoint(IpAddr, 5655);

sock = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.IP);

sock.Bind(ipEnd);

}

public static string receivedPath;

public static string curMsg = "Stopped";

public static string Rout = "";

public static string FileSize = "";

public static string MsgStatus = "";

public static byte[] send;

public void StartServer()

{

try

{

curMsg = "Starting...";

sock.Listen(100);

curMsg = "Running and waiting to receive file.";

Socket clientSock = sock.Accept();

byte[] clientData = new byte[13000 * 5000];

int receivedBytesLen = clientSock.Receive(clientData);

curMsg = "Receiving data...";

send = new byte[receivedBytesLen];

Array.Copy(clientData, send, receivedBytesLen);

Rout = "Start";

clientSock.Close();

curMsg = "Reeived & Saved file; Server Stopped.";

StartServer();

}


{

curMsg = "File Receving error.";

}

}

}

class ReceiverCode1

{

IPEndPoint ipEnd1;

Socket sock1;

public ReceiverCode1()

{

IPHostEntry ipEntry = Dns.GetHostEntry(Environment.MachineName);

IPAddress IpAddr = ipEntry.AddressList[0];

ipEnd1 = new IPEndPoint(IpAddr, 5659);

sock1 = new Socket(AddressFamily.InterNetwork, SocketType.Stream, ProtocolType.IP);

sock1.Bind(ipEnd1);

}

public static string receivedPath;

public static string curMsg = "Stopped";

public static string Rout1 = "";

public static string FileSize = "";

public static string MsgStatus = "";

public static byte[] send1;

public void StartServer1()

{

try

{

curMsg = "Starting...";

sock1.Listen(100);

curMsg = "Running and waiting to receive file.";

Socket clientSock1 = sock1.Accept();

byte[] clientData1 = new byte[13000 * 5000];

int receivedBytesLen1 = clientSock1.Receive(clientData1);

curMsg = "Receiving data...";

send1 = new byte[receivedBytesLen1];

Array.Copy(clientData1, send1, receivedBytesLen1);

Rout1 = "Start";

clientSock1.Close();

curMsg = "Reeived & Saved file; Server Stopped.";

StartServer1();

}


{

curMsg = "File Receving error.";

}

}

}

}

CONCLUSION:

We proposed a model-based description and analysis framework for the design of wireless system architectures.

Using AADL, the de facto standard formal architecture description language, we have demonstrated how a high

level of modularity can be achieved in simulated wireless network systems. This approach also allows tool

chains for analyzing the performance of wireless systems to be formally derived from the simulated behavior of

the system. By examining example applications of time critical wireless networked systems to healthcare and

video broadcasting services, we showed that our framework can support detailed and largely automated analysis

of complicated networked wireless systems.

REFERENCES:

[1] OPNET Technologies, http://www.opnet.com, 2012.

[2] C. Atici and M.O. Sunay, “High Data-Rate Video Broadcasting over 3G Wireless Systems,” IEEE Trans.

Broadcasting, vol. 53, no. 1, pp. 212-223, Mar. 2007.

[3] N.H. Vaidya, J. Bernhard, V.V. Veeravalli, P.R. Kumar, and R.K.Iyer, “Illinois Wireless Wind Tunnel: A

Testbed for Experimental Evaluation of Wireless Networks,” Proc. ACM SIGCOMM Workshop Experimental

Approaches to Wireless Network Design and Analysis, pp. 64-69, Aug. 2005.

[4] W.J. Jeon, K. Kang, R.H. Campbell, and K. Nahrstedt, “Simulation Framework and Performance Analysis

of Multimedia Broadcasting Service over Wireless Networks,” Proc. Int’l Conf. Distributed Systems (ICDCS

’09), pp. 93-100, June 2009.

[5] N. Medvidovic and R.N. Taylor, “A Classification and Comparison Framework for Software Architecture

Descripton Languages,” IEEE Trans. Software Eng., vol. 26, no. 1, pp. 70-93, Jan.

2000.

[6] SAE International, Standard AS 5506, Architecture Analysis and Design Language (AADL), SAE, Nov.

2004.

[7] P.H. Feiler, B. Lewis, and S. Vestal, “The SAE Architecture Analysis & Design Language (AADL) A

Standard for Engineering Performance Critical Systems,” Proc. IEEE Int’l Symp. Intelligent Control (ISIC ’06),

pp. 1206-1211, Oct. 2006.

[8] N. Bhushan, C. Lott, P. Black, R. Attar, Y.-C. Jou, M. Fan, D. Ghosh, and J. Au, “CDMA2000 1xEV-DO

Revision A: A Physical Layer and MAC Layer Overview,” IEEE Comm. Magazine, vol. 44, no. 2, pp. 37-49,

Feb. 2006.

[9] D.R. Pauluzzi and N.C. Beaulieu, “A Comparison of SNR Estimation Techniques for the AWGN Channel,”

IEEE Trans. Comm., vol. 48, no. 10, pp. 1681-1691, Oct. 2000.

[10] A. Konrad, B.Y. Zhao, A.D. Joseph, and R. Ludwig, “A Markov- Based Channel Model Algorithm for

Wireless Networks,” ACM Wireless Networks, vol. 9, no. 3, pp. 189-199, May 2003.

[11] S.A. Khayam and H. Radha, “Constant-Complexity Models for Wireless Channels,” Proc. IEEE

INFOCOM, pp. 1-11, Apr. 2006.

[12] J. Daemen and V. Rijmen, The Design of Rijndael: AES – The Advanced Encryption Standard. Springer-

Verlag, 2002.

[13] W.J. Ebel and W.H. Tranter, “The Performance of Reed-Solomon Codes on a Bursty-Noise Channel,”

IEEE Trans. Comm., vol. 43, no. 234, pp. 298-306, Feb.-Apr. 1995.

[14] K. Kang, Y. Cho, and H. Shin, “Energy-Efficient MAC-Layer Error Recovery for Mobile Multimedia

Applications in 3GPP2 BCMCS,” IEEE Trans. Broadcasting, vol. 53, no. 1, pp. 338-349, Mar. 2007.

[15] K. Kang and L. Sha, “An Interleaving Structure for Guaranteed QoS in Real-Time Broadcasting Systems,”

IEEE Trans. Computers, vol. 59, no. 5, pp. 666-678, May 2010.

CLOUING

DOMAIN: WIRELESS NETWORK PROJECTS

Technology

DOTNET 2013 IEEE MOBILECOMPUTING PROJECT Model based analysis of wireless system architectures for real-time applications