Software Architecture for Managers delivered to you by Matthew Bass, a member of the core faculty of Carnegie Mellon’s Master of Software Engineering programs. As you might know, Carnegie Mellon is one of the best software engineering schools in the world, and Matt is one of our program’s long-standing and much-appreciated facilitators.
Prior to joining Carnegie Mellon, Matthew was a member of the technical staff for the Software Architecture group of Siemens Corporate Research. In this role, he taught software architecture classes, mentored Siemens operating companies in software architecture practices, conducted software architecture reviews for critical projects, and acted as a software architect for multiple domains including automotive, medical, building automation, and power distribution. Matthew has been a practicing software engineer for greater than 17 years, working with Fortune 500 companies across a variety of industry domains.
This 4-day course teaches a structured approach for realizing a system that supports the intended business goals. While realizing the intended functionality is important, it is often the extent to which the system supports or inhibits additional properties such as scalability, reliability, modifiability, and security that make the difference between success and failure. Traditional approaches miss this fact, paying only cursory attention to these properties resulting in systems that are brittle or unstable, lack the desired performance or throughput, or are difficult and expensive to evolve and maintain.
The organization must be set up in a way that:
– Understands what kinds of requirements are architecturally significant
– Recognizes the architectural requirements implied by the business objectives
– Articulates these requirements in a way that is actionable and in some sense “testable”
– Understands the relationship between technical decisions and these requirements
– Be able to determine the business impact of technical tradeoffs
– Refines both business objectives and technical decisions as needed to maintain alignment
– Appropriately documents architectural decisions and rationale in order to maintain traceability
Knowledge of particular aspects of technical activities allows management to adequately plan, coordinate, and monitor technical activities in order to maintain alignment between the business objectives and the system throughout the lifecycle.
By the end of this course attendees should be able to:
– Recognize architecturally significant requirements
– Specify actionable architectural requirements
– Plan architectural activities
– Execute the architectural plan in a way that maintains alignment between the strategic objectives and the system that is being built
To request detailed information about the course, please send a message to Anastasiya Markuts or MSс in Technology Management.
Additional contact: 067 215 4848, email@example.com, skype: anastasiya.markuts