UML:
Perspective of UML
- – Conceptual: the diagrams are interpreted as describing things in a situation of real word or domain of interest.
- – Specification: Diagrams describe the software abstraction or components with no commitment to particular implementation
- – Implementation: Diagrams describe software implementation in a particular technology.
History:
- 1960s and 1970s: Emergence of OO Programming languages i.e. Simula, Smalltalk
- 1982: OOD Emerged, Grady Booch wrote the first OOD paper [Booch82]
- 1988: Meyer published early influential book “Object Oriented Software Construction”
- 1990: Wifs-Brock and others described the responsibility driven design approach to OOA/D
Unified Process:
- Agile practices such as Agile Modeling are key to applying the UML in an effective way
- Iterative and evolutionary development—contrasted with a sequential or “waterfall” lifecycle
- Involves early programming and testing of a partial system, in repeating cycles
- We rely on short quick development steps, feedback, and adaptation to clarify the requirements and design
- Emerged as a popular iterative software development process for building object oriented systems
- UP is very flexible and open, and encourages including skillful practices e.g.
- – XP (TDD, Refactoring, Continuous integration),
- – SCRUM,
- – Iterative lifecycle
- – Risk-driven development, into a cohesive and welldocumented process description
- The UP is an iterative process
No comments:
Post a Comment