Software Engineering 2

Taught at the Universidad Carlos III Madrid (bilingual courses)

 Lecture – summer 2005/2006



Lecturer: Michał Śmiałek

Objectives

The main objective of the course is to teach proper organization of the software engineering (SE) process for building software applications.

This objective is realized through teaching of four SE disciplines:

-   user requirements elicitation (UR)

-   software requirements formulation (SR)

-   architectural design (AD)

-   detailed design (DD)

These disciplines are taught as parts of the overall software engineering methodology based on an iterative lifecycle.

 

Introduction and regulations

Lecture 1

Lecture 2

Lecture 3

Lecture 4

Lecture 5

Lecture 6

Lecture 7

Lecture 8

Example model

 

 Literature

Main literature

1. ESA Board for Software Standardisation and Control (BSSC). ESA Software Engineering Standards. European Space Agency, February 1991.

2. Braude, E. Software Engineering. An Object-Oriented Perspective. John Wiley & Sons, 2001.

3. Leffingwell, D., Widrig, D. Managing Software Requirements. A Unified Approach. Addison-Wesley, 2000.

 

Supplementary literature

1. Jim Arlow, Ila Neustadt. UML and the Unified Process. Practical Object-Oriented Analysis & Design. Addison-Wesley, 2002.

2. Martin Fowler, Kendall Scott. UML Distilled, A Brief Guide to the Standard Object Modeling Language. Addison-Wesley, 2000.

3. Perdita Stevens, Rob Pooley. Using UML, Software Engineering with Objects and Components. Addison-Wesley, 2000.

4. Grady Booch, James Rumbaugh, Ivar Jacobson. The Unified Modeling Language User Guide. Addison-Wesley, 1999.

5. Ivar Jacobson, Grady Booch, James Rumbaugh. The Unified Software Development Process. Addison-Wesley, 1999.

6. James Rumbaugh, Ivar Jacobson, Grady Booch. The Unified Modeling Language Reference Manual. Addison-Wesley, 1998.

7. Object Management Group. Unified Modeling Language Specification. Version 2.0, 2005 (http://www.omg.org/).