Creating a Local Git repository in ubuntu

Agenda :
1) Create a remote repository in local file system
2) Create a workspace
3) Create a empty repository
4) Add Initial file
5) Add remote origin
6) Push the code to remote repo
7) Creation of new branch
8) Pushing the new branch
9) Viewing all branches and Changing branch
10) Merging development branch to Master branch

1) Creation of a local repository
We need to define a location where the git repository will reside.
For this, we will create a local git repo.
To start with the local git repositary setup, first, we have to create a local directory.
I chose the below location for this.

cd /;
sudo mkdir gitrepo;
sudo chmod 777 gitrepo;
cd gitrepo;
mkdir project_1;
cd project_1;
git init –bare;

2) Creation of workspace
To start working, you need a workspace. I chose the below location as workspace

cd ~/;
mkdir workspace;
cd workspace;
mkdir project_1;
cd project_1;

4) Creation of Empty Depositary
Initiate a empty repositary here.

git init;

4) Adding Initial files.
Add your required initial files to the repo.

echo “This repository is to learn creation of local git repos” >>README
git add README;
git commit -m”Initial Commit”

5) Adding Remote origin
Now, we have to specify, where we will store this repository.
Remember?? We have created a local repository at first?
Else, check 1 Creation of a local repository

Now, we are going to use this location as the remote location.

git remote add origin /gitrepo/project_1

6) Pushing the code to remote repo
Now, we can push the code to the remote repo we have added.

git push origin master

The end master indicates, we need to push to the branch called as master in the remote repo.

To test the setup so far.. i.e. to check whether our code is safe at remote repo, lets try the below.

cd ../
rm -rf project_1;

git clone /gitrepo/project_1;
cd project_1;

Now, we should be able to see out previously added file.

7) Creation of new branch
Now, we will create a branch for development..

In the workspace repo, we will create a local branch at first. Then we will push this branch to the remote repo.

git checkout -b devel

git status, should tell that you are in the new branch devel

8) Pushing the new branch to remote :
Once you have added your development code, to push the new branch to the remote repo, follow the below..

git add *;
git commit -m”Adding development code”
git push origin devel

This would push the branch to the remote repo..

9) Viewing all branches and Changing branch
To list all of branches in current repo, run

git branch -a

A start will be present to indicate the active branch.
Remote branches will be preceded with remotes/origin/ in their path.

To change to a particular path, run

git checkout -b branch_name

10) Merging development branch to Master branch

git checkout master
git pull
git merge devel


Stripping and stopping stripping of binaries in RPM Build.

From FedoraProject page :

Normally, if there are binary executables, then debugging symbols are 
stripped from the  normal binary packages and placed into a name-debug
subpackage. If this shouldn't  happen, you can disable the stripping 
and creation of this subpackage by putting this at the top of your 

%global _enable_debug_package 0
%global debug_package %{nil}
%global __os_install_post /usr/lib/rpm/brp-compress %{nil}

If you want to stop stripping any one single binary alone, then you can add this line in the spec file after make..

strip --strip-unneeded binary_name

What is Unified modelling language [UML] and diagrams?

Very very short story

  1. Business process modeling with use cases
  2. Class and object modeling
  3. Behavior modeling
  4. Component modeling
  5. Distribution and deployment modeling
  • User model view,
  •                • Use case Diagram:
  • Structural model view,
  •                •    Class Diagrams:
  •                •    Object Diagrams:
  • Behavioural model view,
  •                •    Sequence diagrams:
  •                •    Collaboration diagrams:
  •                •    State diagrams:
  •                •    Activity diagrams:
  • Implementation model view
  •                •    Component diagrams:
  • Environment model view.
  •                •    Deployment diagrams:

Now, Long story..

Summary :

This post is from here.
If you’re an analyst, developer or architect, the chances are that you have heard of the UML
If you’re not already familiar of using OOA/D design methods such as the UML then there is a fair chance the pressure is on to utilize this standard as part of your analysis and  design process.

To those not familiar with OOAD, either the laymen or seasoned developer alike, the UML can be seen overly comprehensive and daunting to learn.

This article will attempt to provide a fast track introduction for those that need to learn the UML basics and to begin to start understanding UML, so that it can be incorporated into your development project.

  1. I shall begin by clarifying exactly what UML is and is not.
  2. Then question why we should use the UML at all.
  3. Then I will conclude part 1 of this article with a high-level tour of the UML modeling tool-set.
  4. In part 2 of this article I shall continue by applying the models and notation already discussed to a real life business problem with a working example.

What is the UML?
In 1997 the OMG (Object Management Group) developed the UML as a common
architectural framework for modeling object orientated systems & applications.
The UML is derived primarily from the strengths of three notations;

  • Booch OOD (Object-Oriented Design),
  • Rumbaugh OMT (Object Modeling Technique),
  •  Jacobson OOSE (Object-Oriented Software Engineering).

The OMG described UML is a language representing unified best engineering
practices for

  • specifying,
  • visualizing,
  • constructing,and
  • documenting

the elements of business modeling, software and even non-software systems.

•    Specification:
“what” is required of a system, and
“how” a system may be implemented.
It captures the all important
design, and
implementation decisions.
that need to be established during a system development lifecycle.

•    Visualization:
allows the visualization of systems before they are implemented.
shapes with well defined semantics
communicate to a wider audience more succinctly
than a descriptive narrative and
more comprehensively
than what often can be represented by a programming language.

•    Construction:
used to guide and craft the implementation of a complicated system.
its possible to generate OO source code from UML and vice versa.

•    Documenting:
It can capture knowledge and documenting deliverables, such as
requirements documents,
functional specifications,
and test plans.
These are all critical in
measuring, and
a system throughout its life cycle.

These four are modeling applications of UML. Not be confused with a process.
There are many processes available which use the UML;
furthermore there are many tools available on the market that aid the UML and,
in some cases also facilitates the following of a particular process.

Therefore the UML is not:
• A Process:
It is a modeling toolkit with its own notation and syntax.
A process goes further by
describing the steps you take when developing software,
which diagrams are produced and
in which order, who does what and so on.
The premise behind the UML is that it is process-independent,
but enables and facilitates further processes.
•    Visual Programming Language:
It is a visual modeling language frm which programs can be derived
The notation behind UML modeling is comprised of,
a set of specialized shapes        :    used for the construction
of different kinds of diagrams
while the UML syntax specifies    :    how these shapes can be combined.

Therefore further to learning the basics of UML it is recommend that:
• A process or methodology is adopted
• A UML development tool is utilized

UML may be used to support a number of methodologies, such as the
Rational Unified Process.
Some methodologies are more suited to larger enterprise applications
with a large team of architects and developers.
While others are more appropriate for
a single person or small teams working on small embedded systems.

Similarly there are many UML development tools available, such as
Rational Rose (Rational Rose Corporation),
Enterprise Architect (Sparx Systems),
Describe (Embarcadero Technologies) and even
Microsoft Visio.

Why Use UML?
With many of the rapid application development (RAD) tools available
such as Delphi or Visual Basic,
developing an application is fairly easy.

But does this method result in a professional quality application?

Deborh Kurata (1998) states that if an application is to be of a professional
quality, it must:
• meet the needs of the users
• be robust
• be maintainable
• be documented

Many developers using RAD tools will believe it makes sense to develop an
application rapidly.Write a prototype, and then keep adding more code until
the application is complete.

There is however, a fundamental problem to this approach.
The resulting application will lack a well defined architecture
because it would not have been thought out properly.
This will not compromise fundamental object orientated principles and
result in
inefficient and
difficult to maintain code.

the use of UML,
an appropriate UML development tool, and
an applicable process or methodology,

the design and refining of the application is shifted
from the development phase to
an analysis and design phase.

Therefore reducing risks and providing a vehicle for testing the architecture
of a system before it is coding begins.

The analysis and design overhead will eventually pay dividends as the system
has been
user driven,
documented and
generate skeleton code,

that will be
object orientated and
promote re-use.

Sinan Si Alhir (1998) describes the UML as enabling:
the capturing,
and leveraging

and operational knowledge

to facilitate increasing value by

increasing quality,
reducing costs,
and reducing time-to-market

managing risks &
being proactive in regard to
ever-increasing change &

This is a fairly convincing statement in itself, Sinan states that the UML will
increase quality and
reduce development time
while being flexible enough to respond to changing requirements.

Furthermore, the use of UML will help;
• The communication of the desired structure & behavior of a system between
stakeholders and
• The visualization and control of a systems architecture
• Promote a deeper understanding of
the system,
exposing opportunities for
and reuse.
• Manage Risk.

So what are these models?
So what models are available,
what use are they and
how do they link together?

we need to consider the primary modeling purposes of UML.

These are:

  1. Business process modeling with use cases
  2. Class and object modeling
  3. Behavior modeling
  4. Component modeling
  5. Distribution and deployment modeling

Each model is designed to let
developers and
view a system from different perspectives and
with varying levels of abstraction.

Each diagram will fit somewhere into these five architectural views
representing a distinct problem solution space.

These can be described as the;

  1. user  model view,
  2. structural model view,
  3. behavioral model view,
  4. implementation model view and
  5. the environment model view.

The User Model View
The user model view encompasses the models which define a solution to a problem
as understood by the client or stakeholders.This view is often also referred to
as the use case or
scenario view.

•    Use case Diagram:
These models depict
the functionality required by the system and
the interaction of users and other elements (known as actors)
with respect to the specific solution.

The Structural model View :
The structural view encompasses the models which provide the
structural dimensions and
properties of the modeled system.
This view is often also referred to as the static or logical view.

•    Class Diagrams:
These models describe the static structure & contents of a system using
elements such as classes,
packages and
to display relationships such as
inheritance and
•    Object Diagrams:
Depict a class or the static structure of a system
at a particular point in time

The Behavioral Model View:
This model describe the behavioral, dynamic features & methods of the modeled
system. This view is often also referred to as the
concurrent, or
collaborative view.
•    Sequence diagrams:
Describe timing sequence of the objects over a vertical time dimension.
With interactions between objects depicted on a horizontal dimension.
•    Collaboration diagrams:
Describe the interactions and relationships between
objects and
of a system organized in time and space.
Numbers are used to show the sequence of messages.
•    State diagrams:
Describe the sequence, status conditions and appropriate responses or
actions to conditions during the life of the objects within the system.
•    Activity diagrams:
Describe the methods, activities and resulting transitions after
completion of the elements as flows of processing within a system.

The Implementation Model View:
The implementation view combines the structural and behavioral dimensions
of the solutions realization or implementation.
This view is often also referred to as the component or development view.

•    Component diagrams:
These depict the high level organization & dependencies of
source code components,
binary components and
executable components
and whether these components exist at compile, link or run time.

The Environment Model View :
These models describe both the structural and behavioral dimensions of the
domain or environment in which the solution in implemented.
This view is often also referred to as the deployment or physical view.

•    Deployment diagrams:
This models depict & describe
environmental elements &
configuration of runtime processing components,
libraries and
objects that will reside on them.

How do the models fit together?
After a high-level tour of the architectural views and diagrams available,it is
important to remember once again that UML is a not a process, therefore there
is no right or wrong order in which these models should be constructed.

In practice, the only real pre-requisite to a model is a business process model,
use case or a use case diagram. From then on in, a method of refinement on each
model will often be used as many elements of the system will not become obvious
until it is modeled from a different perspective. Therefore the activities of
analysis (what are the objects?) and design (the allocation of behavior) will
be iterative and be a mutually complementary process.

We have taken a look at the origins and definition of the UML to provide a
simplistic understanding of what it is, and what the UML can offer us. We have
also examined how we can benefit from its use on our next development project
and briefly explored the architectural views and models available and how these
can link together. In the concluding part of this article I shall apply the
principles and models discussed and explored in this article to a real life
business problem and development solution using example UML models where

References :
Alhir, Sinan Si. The True Value of the Unified Modeling Language (UML)”. Distributed Computing Magazine. DC Corp. July 1998.
Alhir, Sinan Si. UML in a Nutshell. O’Reilly and Associates, Inc. 1998
Alhir, Sinan Si. Understanding the Unified Modelling Language (UML). Methods & Tools. Martinig & Associates. April 1998.
Kurata, Deborah. Develop a Professional Application. Visual Basic Programmer’s Journal . pp 83-86. March 1998.

Further Reading
UML Tutorial, Sparx Systems:
What is UML, Embarcadero Technologies:
Introduction to OMG’s Unified Modeling Language™. OMG:
Understanding the Unified Modeling Language. Sinan Si Alhir: