SYSTEM DESIGN

4.1 GENERAL

Design Engineering deals with the various UML

[Unified Modeling language] diagrams for the implementation of project.
Design is a meaningful engineering representation of a thing that is to be
built. Software design is a process through which the requirements are
translated into representation of the software. Design is the place where
quality is rendered in software engineering. Design is the means to
accurately translate customer requirements into finished product.

4.1.1 ACTIVITY DIAGRAM

Activity diagram are a loosely defined diagram to show workflows

of stepwise activities and actions, with support for choice, iteration and
concurrency. UML, activity diagrams can be used to describe the business
and operational step-by-step workflows of components in a system. UML
activity diagrams could potentially model the internal logic of a complex
operation. In many ways UML activity diagrams are the object-oriented
equivalent of flow charts and data flow diagrams (DFDs) from structural
development.
4.1.2 USE CASE DIAGRAM
A use case diagram is a type of behavioral
diagram created from a Use-case analysis. The purpose of use case is to
present overview of the functionality provided by the system in terms of
actors, their goals and any dependencies between those use cases.
4.1. 3. SEQUENCE DIAGRAM

A sequence diagram in UML is a kind of interaction diagram

that shows how processes operate with one another and in what order. It
is a construct of a message sequence chart. Sequence diagrams are
sometimes called Event-trace diagrams, event scenarios, and timing
diagrams.
4.1.4. CLASS DIAGRAM

A class diagram in the UML is a type of static structure

diagram that describes the structure of a system by showing the system’s
classes, their attributes, and the relationships between the classes. Private
visibility hides information from anything outside the class partition.
Public visibility allows all other classes to view the marked information.
Protected visibility allows child classes to access information they
inherited from a parent class.
4.1.5. E-R DIAGRAM

In software engineering, an entity-relationship model (ERM) is an

abstract and conceptual representation of data. Entity-relationship
modeling is a database modeling method, used to produce a type
of conceptual schema or semantic data model of a system, often
a relational database, and its requirements in a top-down fashion.
Diagrams created by this process are called entity-relationship
diagrams, ER diagrams, or ERDs.
4.1.7. SYSTEM ARCHITECTURE

The users or nodes involved in our projects are

Sender, Intermediate and Receiver. In order to send file, the sender has to
find out the list of nodes which are connected with the sender. From that
available list he can choose receiver. Then the sender has to analyze the
performance of each and every node which is connected with the sender.
The performance analysis list will return the priority based result so that
sender can choose the intermediate to send the file. The Intermediate will
receive the file from sender then it will analyze the performance so that it
can send data to another intermediate or receiver. In the receiver side, the
receiver has to select the file path to receive the file from sender or
intermediate. Then the receiver can view the file received file.