GitHub is a web-based hosting service for Git repositories that offers both source code management features and additional collaboration tools. Unlike Git, which is command-line based, GitHub provides a graphical web and desktop interface. It allows for access control and features like wikis, task tracking, and bug reporting for each project. Both free and paid plans are offered, with free accounts commonly used for open source projects. As the largest code host, GitHub has over 3.4 million users and has become a staple for open source developers and a replacement for resumes sought by some employers.

2. ABOUT GITHUB
GITHUB is a GIT repository web-based hosting
service which offers all of the distributed revision control
and source code management (SCM) functionality of Git as well
as adding its own features. Unlike Git, which is strictly
a command-line tool, GitHub provides a web-based graphical
interface and desktop as well as mobile integration.
It also provides access control and several collaboration
features such as wikis, task management and bug
tracking and feature requests for every project.
GitHub offers both paid plans for private repositories,
and free accounts, which are usually used to host open source
software projects. As of 2014, GitHub reports having over 3.4
million users, making it the largest code host in the world.
GitHub has become such a staple among the open-source
development community that many developers have begun
considering it a replacement for a conventional resume and some
employers require applicants to provide a link to and have an
active contributing GitHub account in order to qualify for a job.

4.  DATA FLOW DIAGRAM
GITHUB explained in DFD
(Data Flow Diagram). DFD is
a graphical representation of
the “flow” of data through an
information system,
modeling its process aspects.
A DFD is often used as a
preliminary step to create an
overview of the system,
which can later be
elaborated. DFDs can also be
used for the visualization of
data processing.

5. GITHUB explained in Use
Case Diagram. In software
& systems engineering, a use
case is a list of steps,
typically defining
interactions between a role
(known in Unified Modelling
Language (UML) as an
“actor”) & a system, to
achieve a goal. In systems
engineering, use cases are
used at a higher level than
within software engineering,
often representing missions.

7. GITHUB explained in a Class Diagram. In software
engineering, a class diagram in the Unified Modelling
language is a type of static structure diagram that
describes the structure of a system by showing the
system’s classes, their attributes, operations & the
relationships among objects.
The class diagram is the main building block of object
oriented modeling. It is used both for general conceptual
modeling of the systematics of the application, & for
detailed modeling translating the models into
programming code. The classes in the diagram represent
both the main objects, interactions in the application &
the classes to be performed.

9.  SEQUENCE DIAGRAM
GITHUB explained in a sequence diagram. A sequence
diagram is an interaction diagram that shows how processes
operate with 1 another & 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
& classes involved in the scenario & the sequence of messages
exchanged between the objects needed to carry out the
functionality of the scenario.
A sequence diagram shows, as parallel vertical lines, different
processes or objects that live simultaneously, &, as horizontal
arrows, the messages exchanged between them, in the order in
which they occur. This allows the specification of simple
runtime scenarios.

11. ACTIVITY DIAGRAM
GITHUB explained in an activity diagram. Activity
diagrams are a graphical representations of workflows of
stepwise activities and actions with support for choice,
iteration & concurrency. Activity diagrams are constructed
from a limited number of shapes, connected with arrows. The
most important shape types:
• rounded rectangles represent actions
• diamonds represent decisions
•Bars represent the start or end of concurrent activities;
•A black circle represents the start of the workflow;
•An encircled black circle represents the end
Arrows run from the start toward the end and
represent the order in which activities happen. Hence they can
be regarded as a form of flowchart.

13. STATE CHART DIAGRAM
GITHUB explained in a state chart diagram. State chart
diagram is a type of diagram used in computer science &
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. Many
forms of state diagrams exist; which differ slightly & have
different semantics.
State diagrams are used to give an abstract description of the
behavior of a system. Hereby “each diagram usually represents
objects of a single class & track the different states of its
objects through the system”.

15. COLLABORATION DIAGRAM
GITHUB explained in a collaboration diagram. A
collaboration diagram also called a communication diagram
or interaction diagram, is an illustration of the relationships &
interactions among software objects in the UML. A
collaboration diagram resembles a flowchart that portrays the
roles, functionality & behavior of individual objects as well as
the overall operation of the system in real time.
Collaboration diagrams are best suited to the portrayal
of simple interactions among relatively small numbers of
objects. The relationships between the objects are shown in
rectangles. As the number of objects and messages grows, a
collaboration diagram can become difficult to read. Several
vendors offer software for creating & editing collaboration
diagrams.

17. COMPONENT DIAGRAM
GITHUB explained in a component diagram. Component
diagrams are different in terms of nature and behavior. Component
diagrams are used to model physical aspects of a system. Component
diagrams can also be described as a static implementation view of a
system. Static implementation represents the organization of the
components at a particular moment.
A single component diagram cannot represent the entire system
but a collection of diagrams are used to represent the whole. So the
purpose of the component diagram can be summarized as:
•Visualize the components of a system.
•Construct executables by using forward and reverse engineering.
•Describe the organization and relationships of the components.
This diagram is very important because without it the
application cannot be implemented efficiently. A well prepared
component diagram is also important for other aspects like application
performance, maintenance etc.

19. GITHUB explained in a deployment diagram. A deployment
diagram in the UML models is the physical deployment of
artifacts on nodes. To describe a website, for e.g., a deployment
diagram would show what hardware components (“nodes”)
exist (e.g., a web server, an application server, and a database
server), what software components (“artifacts”) run on each
node. A single node in a deployment diagram may conceptually
represent multiple physical nodes, such as a cluster of
database servers. There are 2 types of database servers:
1. Device node
2. Execution environment node
Device nodes are physical computing resources with
processing memory services to execute software, such as
typical computers or mobile phones.

21. GITHUB explained in system architecture diagram. Any real world
system is used by different users. The users can be developers, testers,
business people, analysts and many more. So before designing a system the
architecture is made with different perspectives in mind. The most important
part is to visualize the system from different viewer's perspective. The better
we understand the better we make the system. These perspectives are:
•Design
•Implementation
•Process
•Deployment
UML plays an important role in defining different perspectives of a
system. Architectural model represents the overall framework of the system.
It contains both structural and behavioral elements of the system.
Architectural model can be defined as the blue print of the entire system.
Package diagram comes under architectural modeling. There have been
efforts to formalize languages to describe system architecture, collectively
these are called architecture description languages (ADLs).

24. PRESENTED BY:-
GRACY J. JOSEPH (15)
COLLEGE=
ATHARVA COLLEGE OF ENGINEERING
TE CMPN CLASS-2