1. Software Design

2. A well-known phenomenon

3. You will learn…. –Thinking "object oriented“ –Define requirements and analyze the problem domain. –Design of a solution Patterns (GRASP) Problem-solving ideas / principles –Assigning of responsibilities to objects –Architecture –Java implementation Unified Process Iterative development General OOA / OOD topics –UML notation Project management

4. Analysis - "WHAT" Analysis –Investigation of the problem domain and identifying system requirements. Is there a basis for developing a system ? –OO-analysis Use-cases (requirements) –Not object oriented Domaine model –Conceptual concepts in the problem domain

5. Design – “How” A conceptual solution –Not implementation A general database schema –OO-design Defining software objects and their relationships Allocation of the methods in the classes Architecture User Interface

6. Software problems Symptoms –Users needs are not met –The requirements are changing –Modules do not match –The problems are discovered late –Poor quality –Difficult to extend the system –Difficult to maintain –Time and resource estimate is not correct Causes –incomplete requirements –Inadequate communication –changing conditions –Great complexity –Undetected inconsistencies Incomplete test –uncontrolled changes –Bad architecture –subjective evaluations –Poor management of risk UP is trying to solve these problems