The Software Architecture research line studies and generates new knowledge on the decisions, models, and verification techniques that shape robust and adaptable software systems, spanning structural design, quality attributes, large-scale systems, architectural modeling, and verification.
The Software Architecture research line studies and generates new knowledge — methods, models, techniques, and empirical evidence — on the different aspects that define the architecture of software systems. Recognizing architecture as a fundamental pillar for ensuring the quality, evolution, and adaptability of software systems in modern environments, our research spans a broad spectrum of key topics in the field. This line bridges theoretical research with real-world software development practices, combining conceptual and empirical work with the development of methods, models, and tools that support architects in making informed, well-founded design decisions.
Each thematic axis is a component; connectors show how knowledge flows between them. Click a component to see its subtopics.
Axis 1Architectural styles and patterns, and the decisions involved in discovering, selecting, and combining them, to shape the structural organization of software systems.
Axis 2Architectural tactics and patterns, and the decisions involved in discovering, selecting, and applying them, to achieve specific quality attributes — such as performance, scalability, security, reliability, availability, maintainability, and sustainability — and shape the non-functional behavior of software systems.
Axis 3Architectural design principles for building software systems that handle high complexity in terms of structural size, distribution, concurrency, and critical quality scenarios.
Axis 4Use of architectural models and representations to design, analyze, and generate software architectures, enabling automation, consistency, and early verification of architectural design decisions.
Axis 5Techniques and tools to analyze whether software architectures comply with functional and non-functional requirements, and to verify architectural conformance in the early stages of design, before system implementation.
Email
Academic Information System
Libraries
Job Openings
U.N. Identity
Jeisson Andrés Vergara Vargas