Date: March 10, 2016
Time: 1:30--3:00 PM ET
CEU's available upon request
About the Virtual Event
For two decades, the SEI has been instrumental in the creation and development of the field of software engineering known as software architecture. An architect
whose skills and capabilities match a project's needs is more likely to be successful. So what are those skills?
Join SEI researchers and an industry colleague in a live-streamed discussion on
What Makes a Good Software Architect?
Topics to be covered
- John Klein and Andrew Kotov on
Skills and Knowledge of Successful Architects
- Ipek Ozkaya and Michael Keeling on
Architects Design Trade-off Toolbox: Balancing Agility and Technical Debt
What attendees will learn
- How the technical skills needed by a software architect change throughout a system's lifecycle and how this influences the architect's success
- How architects should be the champions of product quality while making the right (and timely) design trade-offs
Who Should Attend?
- Architects
- CTOs
- Developers
- Engineers
- Testers
- Business Analysts
- Technical and Product Managers
About the Speakers
John Klein is a Senior Member of Technical Staff at the Carnegie Mellon Software Engineering Institute (SEI), where he does research and consulting in enterprise and system architecture, working with commercial and government customers in domains
that include healthcare, analytics, financial trading, and command and control.
Andrew Kotov has recently joined the Software Engineering Institute as a Senior Member of the Technical Staff. He works with government customers to evaluate and improve their architectural solutions. Prior to joining SEI, he worked as a software
engineer and architect in various domains, such as reliability engineering, supply chain management, rule-based systems, finance, and healthcare.
Ipek Ozkaya is a Senior Member of the Technical Staff at the Software Engineering Institute at Carnegie Mellon University. She works with government and industry organizations to improve their software architecture practices, focusing on research
and development of software economics, Agile development, architectural trade-off and technical debt practices.
Michael Keeling is a senior software engineer at IBM, where he develops and maintains IBM's Watson Explorer and Watson platforms. Michael is an experienced software architect, Agile practitioner, and programmer, having worked on projects ranging
from combat systems to search to web apps.
Please share with interested colleagues
|