Software Architecture Design, Spring 2019

Introduction

We will review the concept of software architecture and practice software architecture design. We also use architecture design tools, if needed. In addition, we review the latest trends in standards and industry.

  • Lecturer: Seonah Lee
  • Class Time: Wednesday 19:00-21:50
  • Class Rome: No. 202 (or 204)

Objectives

  • Students will be able to explain the concept of software architecture.
  • Students will be able to document software architecture.
  • Students will be able to discuss the latest trends in standards and industry.

References

Tool Installation

  • You can download UML Rhapsody from here. The version is Rhapsody Architect for Software v8.2.
  • You can then set up the license as the following steps:
    1. Set up the value of the system environment variable TELELOGIC_LICENSE_FILE. (Please, ask the value to the instructor Seonah Lee, Hint: 9X3).
    2. Find HKEY_CURRENT_USER\Software\FLEXlm License Manager in window registry, and set up the  value of TELELOGIC_LICENSE_FILE.
  • You can find the tool already installed in Room 202.

Evaluation

Proposal 10% FACE Presentation 20%
Mid-term Presentation 25% Attendance and Discussion, etc. 10% 
Final Presentation 35%    

*. You can replace your attendance by summarizing each book chapter and submit your summary to e-campus. If you want to replace your attendance with your summary, please email to saleese@gnu.ac.kr. 

*. You have to submit your 6 assignments to e-campus.

Schedule

Week

Date

Content

Submission

1

Mar. 13
  • Course Introduction
  • Definition of Software Architecture
  • Architecture Drivers
  

2

Mar. 20
  • UML Introduction
  • Rhapsody Tutorial
  • 1-page project proposal
    • Design Topic
    • Context Diagram

3

Apr. 3

Proposal Presentation

  • Architecture Design Strategy
  • Architecture View, Veiw-points, View-types
  • Proposal Presentation
    • Topic
    • Context Diagram
    • Functional Reqs
      • Use Case Diagram
      • Use Scenarios
    • Quality Reqs
      • Quality Scenarios
    • Constraints

4

Apr. 10

 
  • Interim Report (1-page)
    • Architectural Strategies
    • Identified Components 

5

Apr. 24

Mid-term Presentation 
  •  Mid-term Presentation
    • Topic
    • Functional Reqs (Scenarios)
    • Quality Reqs (Scenarios)
    • Constraints
    • Architectural Strategies
    • Module View
    • C&C View
 

May 1

 Architecture Documentation

  • Arcadia (Teles in France)
  • Siemens' approach 
  

6

May 8

   Architecture Evaluation
  • SAAM, ATAM, CBAM
  

7

May 15
  • FACE Presentation I, II
  • FACE Presentation III, IV
  

9

Jun 12

Final Presentation 

   Mid-term Presentation
  • Topic
  • Context Diagram
  • Functional Reqs (Scenarios)
  • Quality Reqs (Scenarios)
  • Constraints
  • Architectural Strategies
  • Siemens View or Teles View
    • e.g.,Conceptual View
    • e.g.,Module View
    • e.g.,Execution View
    • e.g.,Code View
  • ATAM Table
  • Reflection


 *. The schedule, lecture materials, and assignments can be changed and updated just before each class.

Project

You can choose any software project that you have done, you are doing, or your plan to do. In this class, you will perform software architecture design activities for the project.

FACE Presentation

You can download the FACE pdf from here. If you want to get an overview of FACE, please refer to the presentation slides.

  • FACE Presentation I    OS Segment                                                                p.16-44 (29 pages) 이건표
  • FACE Presentation II   IO Segment/Platform-specific Services Segment         p.45-57 (13 pages) 안찬주
  • FACE Presentation III  Transport Services Segment,                                       p.57-80 (24 pages) 조희태
  • FACE Presentation IV   Data Architecture/Portable Component Segment       p.81-88 (10 pages) 이현권
  • FACE Presentation V    Graphic Services/LCM Services                                  p.95-112 (17 pages)