• State of practice in software architecture - e.g., views from Microsoft, Netscape, JavaSoft, OMG/ODP, and the software architecture R&D community.
• Characterizing the problem.  What do large application developers and enterprise software architects want? How do they avoid building more unmaintainable legacy applications? How do they build applications with fifteen year life cycles on middleware products that change annually? How do they architect systems so that both functionality and architectural -ilities can be upgraded over the application's life cycle?  Approaches to evolution of software.
• Architectural properties.  What are ilities, i.e.,  some property added to a system that is independent of the functionality of that system.  How to insert them into component software architectures?  Say you had a system doing something.  How would it look different if ility X was added or removed?  Is there some kind of architectural level where the boundary between the visibility/hiddeness of the ility changes?  What is needed in the architecture in order to add ilities?
• Scaling component software architectures.  Frameworks, patterns, configurations, inter component protocols.  Examples of composition involving heterogeneous data sources.   Federation - do we have to federate the services when we have ORBs on 40,000,000 desktops?  what can we say about the federation pattern? end-to-end, top-to-bottom ilities like optimization, QoS, security, ...
• Adaptivity of component software architectures.  Tailorability, evolvability, assured services and graceful degradation, survivability.
• Web object models, metadata and registry/repository in Internet/Web.  How do DOM, XML, PICS-NG, RDF, and the many metadata proposals relate to object and agent definition languages?
• Convergence of ORB and Web architectures.  (Why) are both camps doing the same things differently? How to avoid recreating the same set of services like versioning on both architectures.
• Theoretical models and foundations for coordination: component composition, concurrency, mobility, dynamic aspects of coordination, emergent behavior.
• Specification, refinement, and analysis of software architectures: patterns and styles, verification of functional and non-functional properties.
• Coordination, architectural, and interface definition languages: implementation, interoperability, heterogeneity.
• Multi-agent systems and coordination: models, languages, infrastructures.
• Dynamic software architectures: mobile code and agents, configuration, reconfiguration, self-organization.
• Industrial relevance of coordination and software architectures: programming in the large, domain-specific software architectures and coordination models, case studies.
• Interdisciplinary aspects of coordination
• Software Architecture Modeling and Analysis Methods and Tools
• State-of-the-Art and State-of-Practice in Software Architecture
• Software Architecture Support for Software Qualities
• Relationship of Enterprise, System, and Software Architecture
• Architectural Patterns and Styles (including particularly SOA)
• Architecture Description Languages and Model Driven Architecture
• Software Architecture of Large or Very Small systems
• Software Architectures for Emerging Systems
• Software Architecture Discovery and Recovery
• Software Architects' Roles and Responsibilities
• Software Architecture for Legacy Systems and Systems Integration
• Product-Line Architectures
• Cultural, Economical and Managerial Aspects of Software Architecture
• Training, Education, and Certification of Software Architects
• Architecture description languages and meta-models,
• Architectural models, patterns and styles,
• Architecture analysis, validation and verification,
• Architecture transformation and refinement,
• Architecture-based synthesis, code generation,
• Architecture-based support for reconfigurable,   adaptive or mobile applications, 
  requirements engineering and software architectures,
• Quality attributes and software architectures,
• Architecture reengineering, recovery,
• Architecture conformance, run-time monitoring,
• Aspect-oriented software architectures,
• Service-oriented architectures,
• Web services: composition, orchestration, choreography,
• Ontology-based approaches for component and architecture description,
• Process and management of architectural decisions,
• Process models and frameworks for architecture-centric software engineering,
• Architecture-centric model driven engineering,
• Architectural features of Model Driven Architecture (MDA),
• Software tools and environments for architecture-centric software engineering,
• Architectural styles and models for applications based on mature and emerging technologies (Web Services, Java/J2EE, .Net, ...)
• Architectural concerns of autonomic systems,
• Component-based models, middleware, component-based deployment,
• Technology of components and component-based frameworks,
• Industrial applications, case studies, best practices and   experience reports on software architecture,
• dependability modeling in software architectures;
• verification and validation of dependable software architectures;
• adaptable architectures for achieving dependability;
• architectural support for self-healing and self-repairing systems
• run-time checks of dependable architectural model;
• dependability evaluation in software architectures;
• architectural patterns for dependable systems;
• exception handling for software architectures;
• redundancy and diversity at the level of architectures;
• dependable architecture and implementation.

Modeling Software Architectures 
• Visual Modeling of Software Architectures 
• Software Architecture Views 
• Software Architecture Description Languages 
• Architecture Styles and Patterns 
• Documenting Software Architectures

Software Architecture Design Process 
• Architectural Requirements Analysis 
• Role of domain analysis in architecture design 
• Mapping Architecture to Design 
• Architecture Implementation Alternatives

Reuse 
• Software Components and  Reuse 
• Software Product Line Architectures 
• Domain Engineering 
• Application Engineering

Analysis and evaluation of Software Architectures 
• Evolving Software Architecture 
• Evaluating Software Architectures 
• Quality Models for Software Architectures 
• Simulation of Software Architectures 
• Experimenting with Software Architectures

Component and platform architectures 
• Model-Driven Architectures  
• Object-Oriented Application Frameworks  
• Interface-oriented development 
• Service-Oriented Architectures

Tools 
• Tools for Software Software Architecture Design Modeling 
• Tools for supporting Software Architecture Design Method 
• Tools for Evaluating Software Architectures

Industrial Applications and Experiences 
• Software Architecture in practice 
• Experiences in educating software architectures 
• Architecture-centered software development/project management

• Architectural styles, frameworks, and designs in practice

Special Architectures

• Adoptive software architecture
• Domain specific software architecture (DSSA)
• Secure software architecture
• Self-repairing software architecture
• Dynamic software architecture
• Distributed software architecture
• Quality oriented Software architecture