What is System Architecture and Design?
This course (SEAD 6102) includes an introduction to system architecture; the strategic role of architectures; an architecture metaphor; technology, business, and organizational trends that are increasing system complexity; and the importance of architecture to system integrators.
It provides a review of SE fundamentals, reviewing the systems engineering process from customer needs to system requirements; benefits of a disciplined systems engineering process; introduction of the hands-on case study which students will model during the class.
Presented material provides instruction on developing the functional architecture and object oriented architecture (using SysML). It includes an overview of the architecture process and developing a logical architecture; scenario tracing. Also covered is a module on functional architecture trade-offs, extending the decomposition process; architectural considerations and trade-offs. Prerequisite: SEFS 6102 Fundamentals of Systems Engineering.
Why take this course?
Every system has an architecture – whether it is by accident, or by design. No customer would consider constructing a new building without an architect. Yet, companies are designing complex systems, drilling rigs, weapons systems, automobiles, etc. without the aid of a systems architect, or even knowledge of architectural thinking. This course informs the systems engineer on the critical considerations when architecting a complex system. What does separation of concerns mean to a system? What does it mean to be loosely coupled or tightly coupled? What is the value of black box/white box views of the system architecture? And finally, how can model-based systems engineering (MBSE) inform the systems architecture? How does a systems architect create a black box architect? When should an engineering team use functional decomposition and when should they use an object-oriented approach? This course is designed to address many of these critical issues.
Who should take this course?
Systems engineers, and potential system architects who need to better understand the value of abstraction and decomposition to systems architecting. Engineers that must do a better job of tracing the systems architecture back to the systems requirements, as well as being able to allocate systems requirements to significant subsystems. SEAD6102 is a continuation of principles learned in SEFS6102 (which is a pre-requisite).
- Dates 2020 TBC
The courses are organized as intensive one-week courses each with 5 days of lectures. During this week, the lectures last from 0830 to 1630 each day. The courses are a mixture of lectures and work in groups. Masterstudents and others taking courses for credit will work on a written assignment which is due 10 weeks after the end of the course. A completed course with approved written assignment will give 7.5 studypoints.
The price for attending a course depends on whether you take the course for credit or not. To get credit for the course, you need to hand in a written assignment.
- Alternative 1: Attendance only kr. 16.000,-
- Alternative 2: Attendance and written assignment kr. 21.000,-
The price includes course material, coffee and lunch during the course. For alternative 2, the price also includes supervision and grading of the written assignment.
The registration deadline for each course is 2 weeks before course starts.
We accept registrations also after the deadline, provided there are available seats. Each course has a limited number of seats, so please sign up early. We reserve the right to cancel courses with too low participation.