F07_SEA_Kreiser_en < F07_Studium

Sie sind hier: Foswiki>F07_Studium Web>F07_SEA_Kreiser_en (Revision 3) (Quelltext-Ansicht)
<!--
   * Set USERSTYLEURL = %PUBURLPATH%/%WEB%/DokumentFormat/fonts.css
-->
---+!! Course %FORMFIELD{"Bezeichnung"}%


%TOC{depth="3"}%
%STARTSECTION{"no_toc"}%
---
*Responsible:* Prof.Dr. Kreiser

---++ Course
---+++ Meets requirements of following modules(MID)
   * in active programs
      * [[BaET2012_SE]]
      * [[BaET2010_SEA]]

---+++ Course Organization
<sticky>
  <table border="0">
    <tr valign="top">
      <td>
        <table border="1" cellpadding="2" cellspacing="0">
          <th colspan="2">Version</th>
          <tr>
            <td>created</td>
            <td>2013-06-06</td>
          </tr>
          <tr>
            <td>VID</td>
            <td>1</td>
          </tr>
          <tr>
            <td>valid from</td>
            <td>WS 2012/13</td>
          </tr>
          <tr>
            <td>valid to</td>
            <td/>
          </tr>
        </table>
      </td>
      <td>         </td>
      <td>
        <table border="1" cellpadding="2" cellspacing="0">
          <th colspan="2">Course identifiers</th>
          <tr>
            <td>Long name</td>
            <td>%FORMFIELD{"Bezeichnung"}%</td>
          </tr>
          <tr>
            <td>CID</td>
            <td>F07_SEA_Kreiser</td>
          </tr>
          <tr>
            <td>CEID (exam identifier)</td>
            <td/>
          </tr>
        </table>
      </td>
    </tr>
  </table>
</sticky><sticky>
  <table border="0">
    <tr valign="top">
      <td>
        <table border="1" cellpadding="2" cellspacing="0">
          <th colspan="2">Contact hours per week (SWS)</th>
          <tr>
            <td>Lecture</td>
            <td>%FORMFIELD{"VorlesungSWS"}%</td>
          </tr>
          <tr>
            <td>Exercise (unsplit)</td>
            <td>%FORMFIELD{"UebungGanzSWS"}%</td>
          </tr>
          <tr>
            <td>Exercise (split)</td>
            <td>%FORMFIELD{"UebungHalbSWS"}%</td>
          </tr>
          <tr>
            <td>Lab</td>
            <td>%FORMFIELD{"PraktikumSWS"}%</td>
          </tr>
          <tr>
            <td>Project</td>
            <td>%FORMFIELD{"ProjektSWS"}%</td>
          </tr>
          <tr>
            <td>Seminar</td>
            <td>%FORMFIELD{"SeminarSWS"}%</td>
          </tr>
          <tr>
            <td>Tutorial(voluntary)</td>
            <td>%FORMFIELD{"TutoriumSWS"}%</td>
          </tr>
        </table>
      </td>
      <td>    </td>
      <td>
        <table border="1" cellpadding="2" cellspacing="0">
          <th colspan="2">Total contact hours</th>
          <tr>
            <td>Lecture</td>
            <td>%FORMFIELD{"VorlesungPZ"}%</td>
          </tr>
          <tr>
            <td>Exercise (unsplit)</td>
            <td>%FORMFIELD{"UebungGanzPZ"}%</td>
          </tr>
          <tr>
            <td>Exercise (split)</td>
            <td>%FORMFIELD{"UebungHalbPZ"}%</td>
          </tr>
          <tr>
            <td>Lab</td>
            <td>%FORMFIELD{"PraktikumPZ"}%</td>
          </tr>
          <tr>
            <td>Project</td>
            <td>%FORMFIELD{"ProjektPZ"}%</td>
          </tr>
          <tr>
            <td>Seminar</td>
            <td>%FORMFIELD{"SeminarPZ"}%</td>
          </tr>
          <tr>
            <td>Tutorial (voluntary)</td>
            <td>%FORMFIELD{"TutoriumPZ"}%</td>
          </tr>
        </table>
      </td>
      <td>    </td>
      <td>
        <table border="1" cellpadding="2" cellspacing="0">
          <th colspan="2">Max. capacity</th>
          <tr>
            <td>Exercise (unsplit)</td>
            <td>%FORMFIELD{"UebungGanzTeilnehmer"}%</td>
          </tr>
          <tr>
            <td>Exercise (split)</td>
            <td>%FORMFIELD{"UebungHalbTeilnehmer"}%</td>
          </tr>
          <tr>
            <td>Lab</td>
            <td>%FORMFIELD{"PraktikumTeilnehmer"}%</td>
          </tr>
          <tr>
            <td>Project</td>
            <td>%FORMFIELD{"ProjektTeilnehmer"}%</td>
          </tr>
          <tr>
            <td>Seminar</td>
            <td>%FORMFIELD{"SeminarTeilnehmer"}%</td>
          </tr>
        </table>
      </td>
    </tr>
  </table>
</sticky>

*Total effort (hours):* %FORMFIELD{"Gesamtaufwand"}%

---++++ Instruction language
   * German, 70%
   * English, 30%

---++++ Study Level
   * %FORMFIELD{"Niveau"}%
---++++ Prerequisites
   * basic skills in modeling of technical system behavior (e.g. State Charts, Petri Nets)  
   * basic skills in project management

---++++ Textbooks, Recommended Reading
   * I. Sommerville: Software Engineering (Addison-Wesley / Pearson Studium)
   * H. Balzert et.al.: Lehrbuch der Softwaretechnik (Spektrum Akademischer Verlag)
      * Basiskonzepte und Req.Eng.
      * Softwaremanagement
   * G.E. Thaller: Software- und Systementwicklung (Heise Verlag)
   * Bernd Oestereich: Analyse und Design mit UML 2.3 (Oldenbourg)
   * Gamma et.al.: Design Patterns, (Addison-Wesley)
   * OMG Unified Modeling Language Spec., www.omg.org/uml
   * K. Beck: eXtreme Programming (Addison-Wesley Professional)
   * Ken Schwaber: Agiles Projektmanagement mit Scrum (Microsoft Press)
   * H.D. Litke: Projektmanagement (Hanser)

---++++ Instructors
   * Prof.Dr.Kreiser



---++++ Supporting Scientific Staff
   * Dipl.-Ing. Kellersohn

---++++ Transcipt Entry
Software Engineering for Automation

---+++ Assessment
<sticky>
  <table border="1" cellpadding="2" cellspacing="0">
    <th colspan="2">Type</th>
    <tr>
      <td>oE</td>
      <td>normal case (except on large numbers of assessments: wE</td>
    </tr>
  </table>
</sticky>

<sticky>
  <table border="1" cellpadding="2" cellspacing="0">
    <th colspan="2">Total effort [hours]</th>
    <tr>
      <td>oE</td>
      <td>10</td>
    </tr>
  </table>
</sticky>

*Frequency:* 2-3/year

-----
---++ Course components

%STARTSECTION{"Vorlesung / Übung"}%
---+++ <u>Lecture/Exercise</u>

---++++ Objectives 
---+++++ Contents
   * terms
      * software system
      * software produkt
      * software quality
      * complexity in software systems
   * modeling object oriented software systems using UML
      * domain model
         * structure
         * behavior
         * interfaces
      * architectural model
      * implementation model
      * model transformation
      * modeling tools
   * software development life cycle
      * linear process models
         * phase model
         * V-Modell
      * evolutionary process models
         * spiral model
         * eXtreme Programming
         * Scrum
         * Timebox
      * quality management
         * SOPs
   * requirements analysis
      * requirements engineering
      * design-input-requirements
      * legal, regulatory and organisational requirements and constraints
   * product risk analysis
      * FMEA
      * FTA
   * concept and design
      * design principles
      * feasibility analysis
      * system specification (Pflichtenheft)
      * software specifications
   * development
      * chosing suitable programming languages
      * coding standards, coding conventions
      * team development, distributed teams
      * developer controlled testing
      * system integration
      * system launch
      * development tools
   * verification &amp; valididation
      * formalized software testing
         * dynamic testing
         * static testing / reviews
      * field evaluation
      * field monitoring / site monitoring
   * management activities
      * document management
      * configuration management
         * version management
         * build management
      * test management
      * change management

---+++++ Acquired Skills
   * analyse technical software systems
      * methodically retrieve, consolidate and prioritize system requirements
      * construct a formalized design-input-requirements specification
   * model technical software systems
      * unified modeling language, using various diagram types to model simple software systems
         * structural notations
            * class diagram
            * package diagram
            * component diagram
            * deployment diagram
         * behavioral notations
            * use-case diagram
            * activity diagram and concept of actions
            * state machine diagram and variants
            * sequence diagram
      * role based hierachical modeling
         * domain model (customers view)
            * system entity model
            * system interface model
            * system behavioral model
         * software model (devlopers view)
            * class model (technical)
            * detailed behavioral model
            * design principles
            * basic software architecture
      * derive context, interfaces, tasks, behavior and structure of simple software systems out of technical documents
         * understand compact technical documents in detail
         * realize implicit specifications
         * realize and resolve inconsistant specifications
         * realize missing specifications, resolve gaps by own deduction and/or customer interview 
      * modeling software systems using UML2.x
         * iteratively develop simple domain models
            * develop entity model
            * develop context and use-case-models (customers view)
            * specify use-cases
               * evaluate and describe standard scenario and essential alternative scenarios
               * refine and formalize as activity diagram
         * iteratively develop simple software models
            * refactor and detail entity model (developers view)
            * detail behavioral models (developers view)
               * model structural based bahavior by state machines
               * refine activites down to the actions layer
               * link actions to class methods
      * efficently use a professional UML2 development tool
      * verify models
         * define evaluation criteria
            * compliance to modeling guides and standards und to design principles
            * completeness vs. unnecessary complexity
            * quality regarding to specific, customer originated criteria
         * define test cases
         * conduct and document model reviews
            * by own
            * with a peer
            * in a group
         * capture and specify model defects
      * refactor models (correct and optimize based on evaluation results)
   * design technical software systems
      * analyse product risks, define suitable mitigation methods and specify an appropriate design 
      * find suitable design principles to reach given quality criteria, motivate their usage and apply them to the software design
      * find and apply a suitable system and software architecture
      * explain software development methods with respect to distributed teams and make use of suitable methods
      * explain software test methods with respect to distributed teams and make use of suitable methods
   * develop technical software systems
      * describe, compare and exemplarily make use of process models
      * derive information from international regulatory standards on software development (german/english)


---++++ Additional Component Assessment 
<sticky>
  <table border="1" cellpadding="2" cellspacing="0">
    <th colspan="2">Type</th>
    <tr>
      <td>fPS</td>
      <td>excercise (on course and self study)</td>
    </tr>
  </table>
</sticky>

<sticky>
  <table border="1" cellpadding="2" cellspacing="0">
    <th colspan="2">Contribution to course grade</th>
    <tr>
      <td>fPS</td>
      <td>not rated</td>
    </tr>
  </table>
</sticky>

*Frequency:* 1/year

%ENDSECTION{"Vorlesung / Übung"}%



%STARTSECTION{"Praktikum"}%
---+++ <u>Lab</u>

---++++ Objectives 
---+++++ Acquired Skills
   * analyse larger technical software systems
      * read and understand comprehensive technical documents, especially in english language
      * analyse comprehensive system requirements
   * model larger technical software systems
      * separate model layers
         * domain model (customers view)
         * software model (developers view)
      * systematically use model notations to describe software systems
      * iteratively develop behavioral and structural models using UML2
      * efficently use a professional UML2 development tool
      * verify and evaluate models, correct model defects and optimize models
   * design larger technical software systems
      * use design principles to reach specific quality criteria
      * use a suitable system and software architecture
      * conduct development and test in a project team
      * handling program code
         * analyze given program code fragments
         * use an object oriented programming language (C++)
   * develop larger technical software systems
      * use an evolutionary process model
      * derive information from international regulatory standards on software development (german/english)
      * make a compact presentation of the teams work results to a given target audience in english language

---+++++ Operational Competences
   * model real world systems
      * decomposition
         * evaluate and take account of system borders and system interfaces
         * evaluate and take account of system structure
         * evaluate and take account of system behavior
      * composition
         * design structural and behavioral models
         * integrate models
         * verify and evaluate decomposed and integral models
   * manage complex tasks as a team
      * plan and control small projects
      * meet agreements and deadlines
      * plan and conduct reviews
   * make use of model transformations (round trip engineering)
      * revert model elements from given C++ code or code fragments
      * manually verify and complete reverted model elements by analyzing code fragments
      * model system extensions and enhancements based on new requirement specification
      * generate code out of a model and manually add or complete not generatable code fragments
      * debug code and systematically verify software units on the target system


---++++ Additional Component Assessment 
<sticky>
  <table border="1" cellpadding="2" cellspacing="0">
    <th colspan="2">Type</th>
    <tr>
      <td>fSC</td>
      <td>lab experiment (4h)</td>
    </tr>
    <tr>
      <td>fTP</td>
      <td>2 lab experiments (each 4h) per project team</td>
    </tr>
    <tr>
      <td>oR</td>
      <td>presentation on fTP (20min per project team)</td>
    </tr>
  </table>
</sticky>

<sticky>
  <table border="1" cellpadding="2" cellspacing="0">
    <th colspan="2">Contribution to course grade</th>
    <tr>
      <td>fSC</td>
      <td>Attestation</td>
    </tr>
    <tr>
      <td>fTP</td>
      <td>Attestation</td>
    </tr>
    <tr>
      <td>oR</td>
      <td>prerequisite to course exam</td>
    </tr>
  </table>
</sticky>

*Frequency:* 1/year

%ENDSECTION{"Praktikum"}%




%ENDSECTION{"no_toc"}%
Topic-Revision: r3 - 11 Jan 2016, GeneratedContent
F07_Studium
Einloggen oder Registrieren
Webs
F07_Studium
System
Das Urheberrecht © liegt bei den mitwirkenden Autoren. Alle Inhalte dieser Kollaborations-Plattform sind Eigentum der Autoren.
Ideen, Anfragen oder Probleme bezüglich Foswiki? Feedback senden