Unified Modeling Language. software design methodology

1. Unified modeling language

2. History of UML

3. Why UML
 As the strategic value of software increases for
many companies, the industry looks for
techniques to automate the production of
software and to improve quality and reduce cost
and time-to-market. These techniques include
component technology, visual programming,
patterns and frameworks. Businesses also seek
techniques to manage the complexity of systems
as they increase in scope and scale.

4. Object-Oriented Design in UML
 Provide users with a ready-to-use, expressive visual modeling language so
they can develop and exchange meaningful models.
 Provide extensibility and specialization mechanisms to extend the core
concepts.
 Be independent of particular programming languages and development
processes.
 Provide a formal basis for understanding the modeling language.
 Encourage the growth of the OO tools market.
 Support higher-level development concepts such as collaborations,
frameworks, patterns and components.
 Integrate best practices.

5. A software development will have many
stakeholders
 Analysts
 Designers
 Coders
 Testers
 QA
 The Customer
 Technical Authors

6. Class diagram

7. Object diagram

8. Component diagram

9. Deployment diagram

10. Package diagram

11. Use case diagram

12. Activity diagram

13. State machine diagram

14. Sequence diagram

15. Traditional Methods of Gathering
Information
 Interviews
 Questioning
 Questionnaires
 Observation
 Study of existing organizational documents, forms and reports

16. Modern Methods of Gathering
Information
 JAD
 RAD
 Prototyping

17. Joint Application Development - JAD
A modern method of requirements
gathering that involves one or more
workshops that bring together all of the
stakeholders in one location.

18. Rapid Application Development - RAD
An Object Orientated approach to
software development that includes a
method of development as well as
software tools (Kendall and Kendall,
2002). The primary purpose of a RAD
is to speed up the systems
development process.

19. Prototyping
An approach to software development
that requires developers to construct a
working representation of the system.

20. Find actors and use case
Actor – External parties that interact
with the system(Human, Timers, Other
systems)
User case – A sequence of actions
that the system performs that yields an
observable result of value to an actor.