|
|
|
|
|---|---|---|
|
Sep 22 |
slides |
The software development process can be looked at from various angles. Though the starting points may be different (assuring high product quality - managing a project - addressing software development as an engineering discipline), the same issues come come up in the various viewpoints. In this talk I will give an overview of the various subtopics embraced by the term software engineering and will show how these topics relate to each other. |
|
Sep 27 |
slides: part1, part2 (for printing disable "black&white") |
UML (Unified Modeling Language) is the object-oriented modeling technique
that evolved from modeling languages used in methods like Booch, OMT (Rumbaugh)
and OOSE (Jacobson). It has been adopted by OMG, is now widely used in
many companies, and is an integral part of many software development methods.
This series of lectures will give an in depth introduction into UML,
covering most yet not all of its elements. Prior knowledge about object-oriented
concepts (classes, objects, inheritance) is assumed, and knowing basic
entity-relationship modeling is helpful.
Part one: Introduction into semi-formal modelling, Actors, Use Cases |
|
Sep 29 |
|
Part two: Class diagrams |
|
Oct 4 |
|
Part three: Dynamic Diagrams |
|
Oct 6 |
|
Taks/workflows and different methodologies, watersluice methodology as an in depth example ? (Ron Burback ?) or Cost Estimation (Stoica?) |
|
Oct 11 |
slides: part1, part2, part3 (for printing disable "black&white") |
Part four: Processes for UML, Rational Unified Process, use-case driven development, risk-driven iterative development |
|
Oct 13 |
|
|
|
Oct 18 |
|
|
|
Oct 20 |
|
By architecture, I mean the components of a large distributed software system and their interfaces, methods of communication, and behavior. This talk will give an overview of typical architecture patterns, and will survey several architecture examples with a more detailed discussion of DADL. |
|
Oct 25 |
|
|
|
Oct 27 |
|
|
|
Nov 1 |
Component based development , Reuse , Reuse Organization | |
|
Nov 3 |
Modeling for Reuse | |
|
Nov 8 |
Modeling for Reuse, Interaction diagrams (SEAM) and Abstraction Levels, Frameworks (db or external) | |
|
Nov 10 |
slides |
Requirements engineering: content of a requirements document, activities to determine requirements (requirements analysis, validation, evolution), taking into account multiple viewpoints in the requirements engineering process. |
|
Nov 15 |
slides, see Requirements Engineering |
When, how and why and what for to use prototyping. Various kinds of prototyping. |
| week 9: | ||
|
|
slides |
We will look at the content and role of various elements of qualitity assurance like reviews, code inspection, metrics, QA-group, QA-standards, metrics and code inspection tools (e.g. Logiscope) etc. |
|
|
|
General principle of software cost estimation. Metrics for software
size. Some estimation approaches:
|
|
|
slides |
How could automated composition of large, distributed, heterogenous (also concerning the protocol like CORBA, RMI, DCE, DCOM) and automonous software modules look like? The CHAIMS project has the goal to investigate and develop a language and a system for the high-level composition of such modules. |
|
|
(Anthony I. Wasserman, Principal of Software Methods & Tools) slides |
This talk describes both the technical and market forces in the software
tools industry.
Key topics of tool integration and environment architectures are traced to their historical roots. Different forms of tool integration are discussed, including data integration through a shared repository. Future directions include speculations about the use of Java, the activities of the dominant vendors, the emergence of tool suites, and the role of the Internet. |
|
|
|