ARYA College of Engineering

And
Research Centre

2018-2019

Synopsis On
Elevator System
Submitted To: Submitted By:
Er. Pradeep Jha Pankaj Naruka
Head of Department (16EAYCS059)
Computer Science & Rohit Yadav
Engineering (16EAYCS072)
Sankalp Ahuja
(16EAYCS076)
 CERTIFICATE
This to certify that the work, which is being presented in the
project entitled ELEVATOR SYSTEM submitted by
SANKALP AHUJA, ROHIT YADAV & PANKAJ NARUKA
student of 3rd year (6th sem.) B.tech in Computer Science and
Engineering in partial fulfilment for the award of degree of
Bachelor of Technology is a record of the student's work carried
out and found satisfactory for submission.

EXTERNAL EXAMINER HEAD OF DEPARTMENT

 INTRODUCTION
OBJECTIVE-
The objective of the project is for students to design the software (using LabVIEW)
and hardware interfacing electronics for the simulated elevator control system such
that it mimics the operation of a typical elevator. This paper provides a detailed listing
of the engineering requirements for the system and the functional test procedure for
verifying proper operation of the system. Examples of student work are provided,
along with a project assessment. This project is also linked to several ABET criteria
and can be used for assessment of the same. Recommendations are provided to help
ensure student success on the project. This project has been found to effectively
integrate both hardware and software design,while utilizing information covered from
many prerequisite courses. Due to the slow response Characteristics of this system,
this PC-based control project lends itself well to this application.

SCOPE-
In more recent years, elevator relay control systems have gone to solid state. “We
used to drive high-speed elevators with DC; we converted the building’s AC to DC
using motor-generator sets. Today, it’s all done with solid-state devices.
Machine-room-less elevators incorporate machinery and equipment into the hoistway
or closets, eliminating the need for a separate machine room. “The machine-room-less
elevator is becoming very common.
Destination-oriented elevators eliminate control buttons in elevator cars; instead,
passengers enter the elevator-lobby area and select a floor. Based upon the floor
they’re visiting, they’re assigned an elevator car. “It’s a faster way of moving people.
CASE TOOLS-
In this paper software development and testing tool for distributed elevator systems
(DES) is described. The motivation for making this tool grew out of the problems that
have arisen in the process of designing, testing and servicing of the elevator control
processor (referred to as lift-processor), and the entire elevator system. The problems
are largely a consequence of the impossibility of viewing all the functional
requirements or changes to these requirements during the design phase or exploitation.
It should be noted that the liftprocessor must meet the basic requirement that is placed
in front of such a system, related to the high security of the whole system. In fact,
despite the availability of a wide range of tools for designing reliable hardware and
software, a lack of such tools that closely covers specific problems related to the
proposed lift-processor architecture is evident. Also, this device could
achieve much faster response to the new functional demands of the market.
 UML DIAGRAM
USE CASE DIAGRAM
A use case is a methodology used in system analysis to
identify, clarify, and organize system requirements; a use case
diagram is a graphic depiction.

USE CASE DIAGRAM OF ELEVATOR SYSTEM

CLASS DIAGRAM
A class diagram is an illustration of the relationships and source
code dependencies among classes in the Unified Modelling
Language (UML). In this context, a class defines the methods
and variables in an object, which is a specific entity in a
program or the unit of code representing that entity. Class
diagrams are useful in all forms of object-oriented programming
(OOP). The concept is several years old but has been refined as
OOP modelling paradigms have evolved.
CLASS DIAGRAM OF ELEVATOR SYSTEM
Object Diagram
Object diagrams can be described as an instance of class diagram. Thus, these
diagrams are more close to real-life scenarios where we implement a system. Object
diagrams are a set of objects and their relationship is just like class diagrams. They
also represent the static view of the system. The usage of object diagrams is similar
to class diagrams but they are used to build prototype of a system from a practical
perspective.
OBJECT DIAGRAM OF ELEVATOR SYSTEM
Statechart Diagram-
The name of the diagram itself clarifies the purpose of the diagram and other details.
It describes different states of a component in a system. The states are specific to a
component/object of a system.
A Statechart diagram describes a state machine. State machine can be defined as a
machine which defines different states of an object and these states are controlled by
external or internal events.
STATECHART DIAGRAM OF ELEVATOR SYSTEM
Sequence Diagram –
A sequence diagram simply depicts interaction between objects in a sequential order
i.e. the order in which these interactions take place. We can also use the terms event
diagrams or event scenarios to refer to a sequence diagram. Sequence diagrams
describe how and in what order the objects in a system function. These diagrams are
widely used by businessmen and software developers to document and understand
requirements for new and existing systems.

SEQUENCE DIAGRAM OF ELEVATOR SYSTEM

Activity Diagram
Activity diagram describes the flow of control in a system. It consists of activities
and links. The flow can be sequential, concurrent, or branched. Activities are nothing
but the functions of a system. Numbers of activity diagrams are prepared to capture
the entire flow in a system. Activity diagrams are used to visualize the flow of
controls in a system. This is prepared to have an idea of how the system will work
when executed.
ACTIVITY DIAGRAM OF ELEVATOR SYSTEM
Collaboration Diagram
Collaboration diagram is another form of interaction diagram. It represents the
structural organization of a system and the messages sent/received. Structural
organization consists of objects and links.
The purpose of collaboration diagram is similar to sequence diagram. However, the
specific purpose of collaboration diagram is to visualize the organization of objects
and their interaction.

COLLABORATION DIAGRAM OF ELEVATOR

SYSTEM
Component Diagram
Component diagrams represent a set of components and their relationships. These
components consist of classes, interfaces, or collaborations. Component diagrams
represent the implementation view of a system.
During the design phase, software artifacts (classes, interfaces, etc.) of a system are
arranged in different groups depending upon their relationship. Now, these groups
are known as components.
COMPONENT DIAGRAM OF ELEVATOR SYSTEM
Deployment Diagram
Deployment diagrams are a set of nodes and their relationships. These nodes are
physical entities where the components are deployed.
Deployment diagrams are used for visualizing the deployment view of a system. This
is generally used by the deployment team.
DEPLOYMENT DIAGRAM OF ELEVATOR SYSTEM
Conclusion
In this report, a detailed UML documentation for a simulated elevator control system
is given.
The UML diagrams used in this documentation are Use Case Diagram, Class
Diagram, Object Diagram,Sequence Diagram,State Chart Diagram,Activity
Diagram,Collaboration Diagram,Component Diagram and Deployment Diagram.
Throughout the process of working on the class project, how can UML be used in real
time systems are paid great attention to, the successful results of our project can be a
good answer for the question.
Given the popularity and notational robustness of the current version of UML, OO
technology can be reasonably exploited in real time developments. Current object-
oriented analysis and design methods focus solely on the software of a system, which
is not quite acceptable to real time systems, which are demanding a more pragmatic
and comprehensive approach to system development, rather than just software. There
are some aspects of real-time systems that need to be addressed:
• Definition of hardware elements and their characteristics;
• Definition of task and task communication;
• Time constraints;
• Modeling of the network.
UML, however, if used properly with attention paid to the real-time features of a
system and
combination of different notes, helps a lot the design and analysis of real-time system
and can to some extend address above real-time system aspects.
To describe the hardware elements and model the network, we use three different
views to model the structure of the system: the object construction and the software
structure view focus on the software architecture of the system, while the system
architecture view gives out an sketch of the system hardware and the communication
method among system components. To describe the time constraints, UML supplies
sequence diagrams and collaboration diagrams, which are able to specify the real-time
feature of the system by way of marking time constraints aside by the names
of message and object.