CHAPTER 4
DESIGN ENGINEERING
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.
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-step
workflows of components in a system. An activity diagram shows the overall flow of control.
4.1.2 Use Case Diagram
A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their goals (represented
as use cases), and any dependencies between those use cases. The main purpose of a use case
diagram is to show what system functions are performed for which actor. Roles of the actors
in the system can be depicted. Use case diagrams are formally included in two modeling
languages defined by the OMG: the Unified Modeling Language (UML) and the Systems
Modeling Language (SysML). Use case diagrams are behavior diagrams used to describe a set
of actions (use cases) that some system or systems (subject) should or can perform in
collaboration with one or more external users of the system (actors). Each use case should
provide some observable and valuable result to the actors or other stakeholders of the system.
4.1.3 Data Flow Diagram
A data flow diagram (DFD) is a graphical representation of the “flow” of data through
an information system. It differs from the flowchart as it shows the data flow instead of the
control flow of the program. A data flow diagram can also be used for the visualization of
data processing. The DFD is designed to show how a system is divided into smaller portions
and to highlight the flow of data between those parts.
Data Flow Diagram (DFD) is an important technique for modeling a system’s high-level
detail by showing how input data is transformed to output results through a sequence of
functional transformations. DFDs reveal relationships among and between the various
components in a program or system. DFD consists of four major components: entities,
processes, data stores and data flow.
4.1.4Sequence Diagram
A sequence diagram in UML is a kind of interaction diagram that shows how processes
operate with one another and in what order.
A sequence diagram in Unified Modeling Language (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. A sequence diagram shows object interactions
arranged in time sequence. It depicts the objects and classes involved in the scenario and the
sequence of messages exchanged between the objects needed to carry out the functionality of
the scenario. Sequence diagrams typically are associated with use case realizations in the
Logical View of the system under development. Sequence diagrams are sometimes called
event diagrams, event scenarios, and timing diagrams.
4.1.5 Collaboration Diagram
A collaboration diagram show the objects and relationships involved in an interaction, and
the sequence of messages exchanged among the objects during the interaction. The
collaboration diagram can be a decomposition of a class, class diagram, or part of a class
diagram. it can be the decomposition of a use case, use case diagram, or part of a use case
diagram. The collaboration diagram shows messages being sent between classes and object
(instances). A diagram is created for each system operation that relates to the current
development cycle (iteration).A collaboration diagram, also called a communication
diagram or interaction diagram, is an illustration of the relationships and interactions
among software objects in the Unified Modeling Language (UML). The concept is more
than a decade old although it has been refined as modeling paradigms have evolved. A
collaboration diagram resembles a flowchart that portrays the roles, functionality and
behavior of individual objects as well as the overall operation of the system in real time.
Objects are shown as rectangles with naming labels inside. These labels are preceded by
colons and may be underlined. The relationships between the objects are shown as lines
connecting the rectangles. The messages between objects are shown as arrows connecting the
relevant rectangles along with labels that define the message sequencing.
4.1.6 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. In software
engineering, a class diagram in the Unified Modeling Language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes,
their attributes, operations (or methods), and the relationships among the classes. A class
diagram is an illustration of the relationships and source code dependencies among classes in
the Unified Modeling Language (UML). In a class diagram, the classes are arranged in
groups that share common characteristics. A class diagram resembles a flowchart in which
classes are portrayed as boxes, each box having three rectangles inside. The top rectangle
contains the name of the class; the middle rectangle contains the attributes of the class; the
lower rectangle contains the methods, also called operations, of the class. Lines, which may
have arrows at one or both ends, connect the boxes. These lines define the relationships, also
called associations, between the classes.
4.1.7 System Architecture
Architecture diagram shows the relationship between different components of system. This
diagram is very important to understand the overall concept of system. Architecture
diagram is a diagram of a system, in which the principal parts or functions are represented by
blocks connected by lines that show the relationships of the blocks. They are heavily used in
the engineering world in hardware design, electronic design, software design, and process
flow diagrams. This is typically used for a higher level, less detailed description aimed more
at understanding the overall concepts and less at understanding the details of implementation.
Contrast this with the schematic diagram and layout diagram used in the electrical
engineering world, where the schematic diagram shows the details of each electrical
component and the layout diagram show the details of physical construction.
In Authentication module new user going to register their details and registered user login
their account. Because if any user enter their incorrect details in login page then the login
form will terminated. When you give a correct details about user at that time only main form
give access permission otherwise you can’t access this application. Initially, query processing
was made using the closest point. This module describes the server and user communication
process where the client posts the query and the server delivers the result based on the
criteria. So user request the keyword query in URL Page. By using partitioned database, the
search category has been classified based on the user’s search information. The similarity
search proposes the criteria of retrieving the relevant information from the database based on
similar keyword of the subsequent database. This is the process of identifying the records
which are not in the database, and providing the records for future verification. These queries
are displayed to the administrator; thereby he checks the false hits recorded when the users
perform search operation. He then posts the necessary responses to the search database for
future verification. We propose IDAMN, which retrieves distance information from
distributed servers, eliminating those that cannot contribute results. In this project, we discuss
about how we retrieve data in distributed database. In future, we can be extended by
implementing databases on distributed servers and thereby, we can reduce data replication.
4.1.8 Object diagram:
An object diagram in the Unified Modeling Language (UML) is a diagram that shows a
complete or partial view of the structure of a modeled system at a specific time. An Object
diagram focuses on some particular set of object instances and attributes, and the links
between the instances. A correlated set of object diagrams provides insight into how an
arbitrary view of a system is expected to evolve over time. Object diagrams are more
concrete than class diagrams, and are often used to provide examples, or act as test cases for
the class diagrams. Only those aspects of a model that are of current interest need be shown
on an object diagram. An object diagram may be considered a special case of a class
diagram. Object diagrams use a subset of the elements of a class diagram in order to
emphasize the relationship between instances of classes at some point in time. They are
useful in understanding class diagrams. They don’t show anything architecturally different to
class diagrams, but reflect multiplicity and roles.
4.1.9 State Diagram
A state diagram is a type of diagram used in computer science and related fields to describe the
behavior of systems. State diagrams require that the system described is composed of a finite
number of states; sometimes, this is indeed the case, while at other times this is a
reasonable abstraction. There are many forms of state diagrams, which differ slightly and have
different semantics. A state diagram, also called a state machine diagram or state chart diagram, is
an illustration of the states an object can attain as well as the transitions between those states in the
Unified Modeling Language (UML). A state diagram resembles a flowchart in which the initial state
is represented by a large black dot and subsequent states are portrayed as boxes with rounded
corners. There may be one or two horizontal lines through a box, dividing it into stacked sections. In
that case, the upper section contains the name of the state, the middle section (if any) contains the
state variables and the lower section contains the actions performed in that state. If there are no
horizontal lines through a box, only the name of the state is written inside it. External straight lines,
each with an arrow at one end, connect various pairs of boxes. These lines define the transitions
between states. The final state is portrayed as a large black dot with a circle around it. Historical
states are denoted as circles with the letter H inside.
4.1.10. Component Diagram
In the Unified Modeling Language, a component diagram depicts how components are wired
together to form larger components and or software systems. They are used to illustrate the
structure of arbitrarily complex systems.
The Component Diagram helps to model the physical aspect of an Object-Oriented software
system. It illustrates the architectures of the software components and the dependencies
between them. Those software components including run-time components, executable
components also the source code components. A component diagram has a higher level of
abstraction than a Class Diagram - usually a component is implemented by one or more
classes (or objects) at runtime. They are building blocks so a component can eventually
encompass a large portion of a system.
4.1.11 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.
An entity-relationship (ER) diagram is a specialized graphic that illustrates the relationships
between entities in a database. ER diagrams often use symbols to represent three different
types of information. Boxes are commonly used to represent entities. Diamonds are normally
used to represent relationships and ovals are used to represent attributes.
