http://agilemanifesto.org/

We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on
the right, we value the items on the left more.

Kent Beck Mike Beedle Arie van Bennekum Alistair Cockburn Ward Cunningham Martin Fowler

James Grenning Jim Highsmith Andrew Hunt Ron Jeffries Jon Kern Brian Marick

Robert C. Martin Steve Mellor Ken Schwaber Jeff Sutherland Dave Thomas

Client Passion

We focus on our clients, always thinking in terms of what is best for each client. We offer only solutions that are workable, pragmatic and prudent—solutions that add value and become an intrinsic part of a client’s business.

Professional Excellence

Our solutions come from industry-specific knowledge, best practices and accumulated expertise. As a true industry leader, we constantly explore new services and expand our knowledge and skill sets. We invest in people who are passionate about achieving excellence, and who are measured by tangible results and client satisfaction.

Power of Diversity

As a global organization, we are diverse by definition. We share a culture of mutual respect for each individual’s capabilities, achievements, and heritage. We recognize how diversity adds value to our clients – and to each other – by amassing individuals’ capabilities into a unique collection of knowledge.

Collaboration and Collegiality

We work as a team, both enterprise-wide and at the engagement level, with our clients and with each other. We overcome complex challenges together, and welcome new challenges.

Global Perspective

We absorb best practices from around the world as our own, while respecting local value systems and cultures. This worldwide network enables us to deliver benefits that are specific to each client’s industry, objectives, and geography.

 

UML 2.0 has 13 types of diagrams that can be categorized hierarchically as shown in the following Class diagram:

Structure diagrams emphasize what things must be in the system being modeled:

• Class diagram
• Component diagram
• Composite structure diagram (added in UML 2.x)
• Deployment diagram
• Object diagram
• Package diagram

Behavior diagrams emphasize what must happen in the system being modeled:

• Activity diagram
• State Machine diagram
• Use case diagram

Interaction diagrams, a subset of behavior diagrams, emphasize the flow of control and data among the things in the system being modeled:

• Communication diagram
• Interaction overview diagram (added in UML 2.x)
• Sequence diagram
• Timing diagram (added in UML 2.x)

The Protocol State Machine is a sub-variant of the State Machine. It may be used to model network communication protocols.

UML does not restrict UML element types to a certain diagram type. In general, every UML element may appear on almost all types of diagrams. This flexibility has been partially restricted in UML 2.0.

In keeping with the tradition of engineering drawings, a comment or note explaining usage, constraint, or intent is always allowed in a UML diagram.