Beruflich Dokumente
Kultur Dokumente
Chapter-1 : INTRODUCTION
Chapter-4 APPLICATION
4.1 Introduction
4.2 Programs
CHAPTER 1
INTRODUCTION
Software Life Cycle Model- “Waterfall Model”
The following approach is used to design this system, which is called "Classic
life cycle" or "Waterfall model". This linear sequential model suggests a
sequential, systematic approach to system development that begins at the
system level and progress through the analysis, design, coding, testing and
maintenance. The linear sequential model encompasses the following
activities:
Analysis
Design
Code
Testing
Maintenanc
e
These above phases mark the progress of a system analysis and design effort.
It is an orderly set of activities conducted and planned for each development
project. In most business situations the activities are closely related, usually
inseparable, and even the order may be difficult to determine.
Data flow diagram (DFD) is used to show how data flows through the
system and the processes that transform the input data into output. Data
flow diagrams are a way of expressing system requirements in a
graphical manner. DFD represents one of the most ingenious tools used
for structured analysis. It is also known as a bubble chart.
In the normal convention, logical DFD can be completed using only
four notations.
LEVELS OF DFD:
The input and output data shown should be consistent from one level to the
next.
There are times, as a window network, you would like to control certain
aspects of machine seating remotely, without having to install and trigger an
application on the remote machine that ill communicate with the clients
machine.
Out software provides architecture in which there is one client to control the
remote machine. There is one Sever application (Remote machine).
This Server application will receive all requests from the client application and
send periodically screen and updates to client when requested.
Capturing Desktop.
Mouse Handling.
Keyboard Handling.
Java Programming Language
Simple
Architecture-neutral
Object Oriented
Portable
Distributed
High-performance
Interpreted
Multithreaded
Dynamic
Secure
You can think of java as the machine code instructions for the Java Virtual
Machine (Java VM). Every java interpreter, whether it is a
development tool or a Web browser that can run applets, is an
implementation of the Java VM.
History of Java
Java development began at Sun Microsystems in 1991, the same year the
World Wide Web was conceived. Java’s creator, James Gosling did not design
java for the Internet. His Objective was to create a common development
environment for consumer electronic devices which was easily portable from
one device to another. This effort evolved into a language, code named Oak
and later renamed Java that retains much of the syntax and power of c++,
but is simpler and more platform-independent.
Native code is the code that after you compile it, the compiled code runs on a
specific hardware platform. As a platform-independent environment, the java
platform
can be a bit slower than native code. However, smart compilers, well-tuned
interpreters,
and just-in-time byte code compilers can bring performance close to that of
native
code without threatening portability.
TECHNOLOGY SPECIFICATIONS
Graphical user interface make the usage of the package simpler and
smoother. So here we had used Java Swing to create the GUI. Swing is a part
of Java Foundation Class. Swing is a set of classes that provides more powerful
and flexible component for the GUI. In addition to the familiar components like
buttons, checkboxes, and labels, swing supplies several exciting additions
including tabbed panes, scroll panes, tree and tables. Swing components can
provide a pluggable look and feel, which means that it is easy to substitute
another appearance and behavior for the component. You may even design
your own look and feel. Swings are not implemented by platform specific
code. Instead they are written entirely in Java; therefore they are platform
independent.
CHAPTER 2
SYSTEM ANALYSIS
SYSTEM ANALYSIS
System Analysis works with users to identify goals and build systems to achieve
them. System analysis is an important phase of any system development process.
The system is studied to the minutest details and analyzed. The system analyst
plays
the role of an interrogator and dwells deep in to the working of the present
system.
In analysis, a detailed study of these operations performed by a system and their
relationships within and outside of the system is done. A key question considered
here
is, “what must be done to solve the problem?” One aspect of analysis is defining
the boundaries of the system and determining whether or not the candidate
system
should be considered.
The system is viewed as a whole and the inputs to the system are identified.
The outputs from the system are traced through the various processing that the
input phase through in the organization. During analysis, data are collected on
available files, decision points, and transaction handled by present system. Once
analysis
is completed the analyst has a firm understanding of what is to be done.
Based on analysis a cost/benefit analysis is considered. Here the cost for the
system
is calculated on the basis of the analysis made.
The solutions are given as a proposal. The proposal is presented to the user for
an endorsement by the user. The proposal is reviewed on user requestand
suitable
changes are made. This is a loop that ends as soon as the user is
satisfied with the proposal.After all these proposal becomes a formal agreement
that
paves way for design and implementation.
PRELIMINARY STUDY
Preliminary study is the process of gathering and interpreting facts, using the
information for further studies on the system. It is a problem solving activity that
requires intensive communication between the system users and system
developers.
It does various feasibility studies. In these studies, a rough figure of the system
activities can be obtained, from which the decisions about the strategies to be
followed for effective system study and analysis can be taken. Preliminary study
also identifies the method collection to be followed.
At the preliminary study conducted an initial picture about the system working
was got. From the information got form the study, the data collection methods
are identified. Even in the first investigation itself drawback of the existing system
could be identified.
REQUIREMENT ANALYSIS
Upon evaluating current problems and desired information (input and output),
the analyst begins to synthesize one or more solution. To begin, the data
objects, processing function, and behavior of the system are defined in detail.
Once this information has been established basic architecture of
implementation are considered. A client –server approach would seem to be
appropriate but does the software support this architecture fall within the
scope outlined in the software plan? A database management system would
seem to be required, but is the user/customers need for associating justified?
The process of evaluation and synthesis continues until both analyst and
customer feel confident that software can be adequately specified for
subsequent development steps.
During the evaluation and solution synthesis actually the analyst creates
model of the system in and effort to better understand data and control flow
of functional processing operational behaviors and information contained. The
model servers as a foundation for software design and the basic for the
creation of specifications for the software.
Many different approaches of FAST have been proposed. Each makes use of a
slightly different scenario but all apply variation on the following basic guide
lines.
1. Normal Requirements.
2. Expected Requirements.
3. Exciting Requirements.
PROPOSED SYSYTEM
The proposed system is supposed access the desktop of the remote machine
(Server) to the machine on which it is running (Client).
This system is supposed to have two machines, one as server and the other as
client. The Server will start and wait for a client to establish a connection.
Client requires server machine’s IP address to connect.
These images are sent after every specific time interval and update the client
about the server’s desktop status.
SYSTEM REQUIREMENTS
Hardware Requirements:
Memory: 16 MB RAM
Software Requirements:
From the inception of ideas for a software system, until it is implemented and
delivered to customer and even after that the system undergoes gradual
developments and evaluations.
1. Technical Feasibility:
This is concerned with specifying equipment and software that will
successfully satisfy the use considerably, but might include:
The feasibility to produce output in a given time because system
is fast enough to handle multiple users.
Response time under certain circumstances and ability to process
a certain volume of transaction of a particular speed.
Feasibility to communicate data to distant location.
2. Economical Feasibility:
Economic analysis is the most frequently used technique used for
evaluating the effectiveness of a proposed system. More commonly
known as cost/benefit analysis the procedure is to determine the
benefits and savings that are expected from a proposed system and
compared them with cost. Though the cost of installing the system may
appear high, it is one time investment. The resulting benefit is that
automation results in turn around time. The resulting cost/benefit ratio
is favorable.
3. Operational Feasibility:
It is mainly related to human organizational as social aspects. The points
to be considered are:
Establish
Connection
Operate Remote
Desktop
2nd level DFD of Establish Connection Process
Capture
CONNECTION IMAGE EVENTS
Desktop
Process
Operate
IMAGE EVENTS Remote USES
Desktop SERVE
R
Process
CHAPTER 4
APPLICATIONS
INRODUCTION
Project Virtual network computing(VNC) will be developed in java. Concept of
java
1.Networking
2.MouseEvent handling
3.KeyEvent handling
4.MultiThreading
5.File Handling
import java.io.*;
import java.net.*;
import java.util.*;
public MyServer()
{
try
{
ss= new ServerSocket(10);
while(true)
{
s=ss.accept();
al.add(s);
Runnable r=new MyThread(s,al);
Thread t=new Thread(r);
t.start();
}
}
catch(Exception e){}
}
CLIENT CODE
import java.io.*;
import java.net.*;
String s1;
do
{
s1=br.readLine();
dout.writeUTF(s1);
dout.flush();
}
while(!s1.equals("stop"));
}
OUTPUT:
SERVER
Client1
Client 2
Program for MouseEvent Handler
import java.awt.*;
import java.applet.*;
import java.awt.event.*;
/*<applet code="MouseDemo" width=300 height=100>
</applet>*/
public class MouseDemo extends Applet implements
MouseListener,MouseMotionListener
{
int mx=0;
int my=0;
String msg="";
public void init()
{
addMouseListener(this);
addMouseMotionListener(this);
}
public void mouseClicked(MouseEvent me)
{ mx=20;
my=40;
msg="Mouse Clicked";
repaint();
}
public void mousePressed(MouseEvent me)
{
mx=30;
my=60;
msg="Mouse Pressed";
repaint();
}
public void mouseReleased(MouseEvent me)
{
mx=30;
my=60;
msg="Mouse Released";
repaint();
}
OUTPUT:
Program for KeyEvent Handler.
import java.awt.*;
import java.applet.*;
import java.awt.event.*;
/*<applet code="KeyDemo" width=300 height=300>
</applet>*/
public class KeyDemo extends Applet implements KeyListener
{ String msg="";
int x=10;
int y=20;
public void init()
{
addKeyListener(this);
requestFocus();
}
public void keyPressed(KeyEvent ke)
{
showStatus("key pressed");
int key=ke.getKeyCode();
switch(key)
{
case KeyEvent.VK_SPACE:msg=msg + "<SPACE IS PRESSED
>";
break;
case KeyEvent.VK_SHIFT:msg=msg + "<SHIFT IS PRESSED
>";
break;
case KeyEvent.VK_NUMPAD4:msg=msg + "<4 IS PRESSED
>";
break;
}
repaint();
}
public void keyReleased(KeyEvent ke)
{
showStatus("Key Released");
}
OUTPUT:
Program to implement multithreading
import java.io.*;
import java.lang.*;
import java.awt.*;
import java.awt.event.*;
addWindowListener(
new WindowAdapter()
{
public void windowClosing(WindowEvent e)
{ System.exit(0); }
}
);
}
public void actionPerformed(ActionEvent ae)
{
if(ae.getSource()==b2)
System.exit(0);
}
public void run()
{
try
{
if((lower % 2) != 0)
{
lower = lower + 1;
}
while(lower <= upper)
{
Thread.sleep(1000);
lb2.add(String.valueOf(lower));
lower += 2;
Thread.sleep(500);
}
}catch(Exception e){}
}
OUTPUT:
PROGRAM TO SHOW FILE HANDLING
import java.lang.*;
import java.io.*;
import java.util.*;
class WordCount
{
public static void main(String arg[]) throws Exception
{
int char_count=0;
int word_count=0;
int line_count=0;
String s;
StringTokenizer st;
BufferedReader buf=new BufferedReader(new
InputStreamReader(System.in));
System.out.print("Enter filename : ");
s=buf.readLine();
buf=new BufferedReader(new FileReader(s));
while((s=buf.readLine())!=null)
{
line_count++;
st=new StringTokenizer(s," ,;:.");
while(st.hasMoreTokens())
{
word_count++;
s=st.nextToken();
char_count+=s.length();
}
}
System.out.println("Character Count : "+char_count);
System.out.println("Word Count : "+word_count);
System.out.println("Line Count : "+line_count);
buf.close();
}
}
OUTPUT: