Sobre a disciplina

• Objetivos

Professor

• Jacques Philippe Sauvé
• Podem aparecer na minha sala (CN 216) a qualquer momento para conversar.
  

Monitor

• Guilherme Germoglio
  
• Podem aparecer na sala CN 203 a qualquer momento.

Plano de Aulas 

16/10 - Fundamentos Design de Software - Responsável: João Arthur

    Conceitos básicos, diferenças entre design de alto nível e baixo nível, enabling techniques

    Bibliografia:

• D. Budgen, Software Design (2nd Edition).    Addison Wesley, May 2003.
• E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design Patterns.    Addison-Wesley Professional, January 1995. 
• F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, M. Stal, P. Sommerlad, and M. Stal, Pattern-Oriented Software Architecture, Volume 1: A System of Patterns.    John Wiley & Sons, August 1996.
• C. Larman, Applying UML and Patterns : An Introduction to Object-Oriented Analysis and Design and Iterative Development (3rd Edition).    Prentice Hall PTR, October 2004.
• G. Booch, R. A. Maksimchuk, M. W. Engel, B. J. Young, J. Conallen, and K. A. Houston, Object-Oriented Analysis and Design with Applications (3rd Edition).    Addison-Wesley Professional, April 2007.
• B. Adelson and E. Soloway, "The role of domain experience in software design," Software Engineering, IEEE Transactions on, vol. SE-11, no. 11, pp. 1351-1360, 1985.
• R. J. Wirfs-Brock, "Connecting design with code," Software, IEEE, vol. 25, no. 2, pp. 20-21, 2008. 
• R. N. Taylor and A. van der Hoek, "Software design and architecture the once and future focus of software engineering," in FOSE '07: 2007 Future of Software Engineering.    Washington, DC, USA: IEEE Computer Society, 2007, pp. 226-243. 
• E. W. Dijkstra, "The structure of the “THE”-multiprogramming system," Commun. ACM, vol. 11, no. 5, pp. 341-346, 1968.
• B. W. Lampson, "Hints for computer system design," in SOSP '83: Proceedings of the ninth ACM symposium on Operating systems principles, vol. 17, no. 5.    New York, NY, USA: ACM Press, October 1983, pp. 33-48. 
• G. F. Smith and G. J. Browne, "Conceptual foundations of design problem solving," Systems, Man and Cybernetics, IEEE Transactions on, vol. 23, no. 5, pp. 1209-1219, 1993.
• D. L. Parnas, "On the criteria to be used in decomposing systems into modules," Classics in Software Engineering, pp. 139-150, 1979. 
• J. Kramer, "Is abstraction the key to computing?" Commun. ACM, vol. 50, no. 4, pp. 36-42, 2007.   

21/10, 23/10 - Fundamentos de Arquitetura de Software - Responsável: Jemerson Damásio

    Conceitos básicos, características, benefícios  

     Bibliografia:

• F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, M. Stal, P. Sommerlad, and M. Stal, Pattern-Oriented Software Architecture, Volume 1: A System of Patterns.    John Wiley & Sons, August 1996.
• I. Gorton, Essential Software Architecture.    Springer, June 2006.
• L. Hohmann, Beyond Software Architecture: Creating and Sustaining Winning Solutions.    Addison-Wesley Professional, January 2003.
• C. Hofmeister, R. Nord, and D. Soni, Applied Software Architecture.    Addison-Wesley Professional, November 1999.
• K. Smolander, "Four metaphors of architecture in software organizations: Finding out the meaning of architecture in practice," in ISESE '02: Proceedings of the 2002 International Symposium on Empirical Software Engineering.    Washington, DC, USA: IEEE Computer Society, 2002.
• Eden, A.H.; Kazman, R., "Architecture, design, implementation," Software Engineering, 2003. Proceedings. 25th International Conference on , vol., no., pp. 149-159, 3-10 May 2003
• T. Ball and S. G. Eick, "Software visualization in the large," Computer, vol. 29, no. 4, pp. 33-43, 1996.
• L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, Second Edition.    Addison-Wesley Professional, April 2003.
• M. Shaw and D. Garlan, Software Architecture: Perspectives on an Emerging Discipline.    Prentice Hall, April 1996. 
• J. Reekie and R. Mcadam, A Software Architecture Primer.    Angophora Press, March 2006. 
• N. Rozanski and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives.    Addison-Wesley Professional, April 2005.

28/10 - Situando a arquitetura no processo de desenvolvimento/O arquiteto - Responsável: Sabrina de F. Souto

    Como/quando a arquitetura acontece em RUP, XP, outros

    O papel do arquiteto no ciclo de vida do software

    Bibliografia:

• P. Kruchten, The Rational Unified Process: An Introduction, Third Edition.    Addison-Wesley Professional, December 2003
• K. Beck and C. Andres, Extreme Programming Explained : Embrace Change (2nd Edition).    Addison-Wesley Professional, November 2004.
• P. Kruchten, "The software architect-and the software architecture team," Software Architecture; TC2 First Working IFIP Conference on Software Architecture (WICSA1), vol. 2, pp. 565-583.
• M. R. Mcbride, "The software architect: essence, intuition, and guiding principles," in OOPSLA '04: Companion to the 19th annual ACM SIGPLAN conference on Object-oriented programming systems, languages, and applications.    ACM Press, 2004, pp. 230-235.
• M. Fowler, "Design - who needs an architect?" Software, IEEE, vol. 20, no. 5, pp. 11-13, 2003
• L. Hohmann, Beyond Software Architecture: Creating and Sustaining Winning Solutions.    Addison-Wesley Professional, January 2003.

30/10 - Stakeholders - Responsável: Camila

    Quem são e como se relacionam com a arquitetura de um sistema, como se relacionam entre si

• I. Gorton, Essential Software Architecture.    Springer, June 2006.
• N. Rozanski and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives.    Addison-Wesley Professional, April 2005.
• L. Hohmann, Beyond Software Architecture: Creating and Sustaining Winning Solutions.    Addison-Wesley Professional, January 2003.
• P. Clements, F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architectures: Views and Beyond.    Addison-Wesley Professional, September 2002.
  

Requisitos não-funcionais (atributos de qualidade)

    O que são e como influenciam a arquitetura de um sistema, métricas

4/11 - Como alcançar alto desempenho e escalabilidade? - Responsável: Thiago Manel

6/11   - Como alcançar alta disponibilidade? - Responsável: Giovanni

11/11   - Como alcançar segurança? - Responsável: Larissa

13/11 - Como melhor lidar com mudanças? - Responsável: Fabrício Lélis

    Bibliografia:

• N. Rozanski and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives.    Addison-Wesley Professional, April 2005.
• F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, M. Stal, P. Sommerlad, and M. Stal, Pattern-Oriented Software Architecture, Volume 1: A System of Patterns.    John Wiley & Sons, August 1996.
• M. Kircher and P. Jain, Pattern-Oriented Software Architecture Volume 3: Patterns for Resource Management.    Wiley, June 2004.  
• D. Schmidt, M. Stal, H. Rohnert, and F. Buschmann, Pattern-Oriented Software Architecture, Volume 2, Patterns for Concurrent and Networked Objects.    John Wiley & Sons, September 2000.
•  E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design Patterns.    Addison-Wesley Professional, January 1995.  
• A. Oram and G. Wilson, Beautiful Code: Leading Programmers Explain How They Think (Theory in Practice (O'Reilly)).    O'Reilly Media, Inc., June 2007.
• John Engates, 7 Stages of Scaling Web Applications http://www.slideshare.net/davemitz/7-stages-of-scaling-web-applications
• K. S. Ahluwalia, "Scalability design patterns," in 14th Conference on Patterns Languages of Programs, Monticello, IL, USA, September 2007.

Padrões/Estilos arquiteturais

18/11 - Layers, Pipes and Filters, Blackboard - Responsável: Anne Caroline

20/11 - MVC, Presentation-Abstraction-Controller - Responsável: Alan Cruz

25/11 - Message Bus, Publish-Subscribe, Broker - Responsável: Bruno Coitinho

27/11 - Microkernel, Reflection - Responsável: Rodrigo Rocha

    Bibliografia:

• F. Buschmann, R. Meunier, H. Rohnert, P. Sommerlad, M. Stal, P. Sommerlad, and M. Stal, Pattern-Oriented Software Architecture, Volume 1: A System of Patterns.    John Wiley & Sons, August 1996.
• E. Gamma, R. Helm, R. Johnson, and J. Vlissides, Design Patterns.    Addison-Wesley Professional, January 1995. 
• N. Rozanski and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives.    Addison-Wesley Professional, April 2005.
• M. Fowler, Patterns of Enterprise Application Architecture.    Addison-Wesley Professional, November 2002. 
  

2/12, 4/12 - Documentação de arquitetura - 2 Responsáveis: Helder Fernando e Maria de Lourdes

    Visões, Pontos-de-vista, conjuntos de visões clássicos (4+1, SEI)

    Bibliografia:

• IEEE and ISO/IEC, "Systems and software engineering - recommended practice for architectural description of software-intensive systems," ISO/IEC 42010 IEEE Std 1471-2000 First edition 2007-07-15, pp. c1-24, July 2007.
• P. Clements, F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford, Documenting Software Architectures: Views and Beyond.    Addison-Wesley Professional, September 2002.
• P. B. Kruchten, "The 4+1 view model of architecture," Software, IEEE, vol. 12, no. 6, pp. 42-50, 1995.
• N. Rozanski and E. Woods, Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives.    Addison-Wesley Professional, April 2005.

9/12 - Diferenças entre Arquitetura e Código - Responsável: Andreza Vieira

    Bibliografia:

• Lindvall, M. and Muthig, D. 2008. Bridging the Software Architecture Gap. Computer 41, 6 (Jun. 2008), 98-101. DOI= http://dx.doi.org/10.1109/MC.2008.176 
• Garlan, D.; Allen, R.; Ockerbloom, J., "Architectural mismatch: why reuse is so hard," Software, IEEE , vol.12, no.6, pp.17-26, Nov 1995
• Garlan, D., Allen, R., and Ockerbloom, J. 1995. Architectural mismatch or why it's hard to build systems out of existing parts. In Proceedings of the 17th international Conference on Software Engineering (Seattle, Washington, United States, April 24 - 28, 1995). ICSE '95. ACM Press, New York, NY, 179-185.  
• Murphy, G. C., Notkin, D., and Sullivan, K. 1995. Software reflexion models: bridging the gap between source and high-level models. In Proceedings of the 3rd ACM SIGSOFT Symposium on Foundations of Software Engineering (Washington, D.C., United States, October 12 - 15, 1995). G. E. Kaiser, Ed. SIGSOFT '95. ACM Press, New York, NY, 18-28.
• Murphy, G.C.; Notkin, D.; Sullivan, K.J., "Software reflexion models: bridging the gap between design and implementation," Software Engineering, IEEE Transactions on , vol.27, no.4, pp.364-380, Apr 2001
• Aldrich, J., Chambers, C., and Notkin, D. 2002. ArchJava: connecting software architecture to implementation. In Proceedings of the 24th international Conference on Software Engineering (Orlando, Florida, May 19 - 25, 2002). ICSE '02. ACM Press, New York, NY, 187-197. 

(a definir) Recuperação estrutural da arquitetura de um sistema - Responsável: Roberto Bittencourt  

Draft do livro Software Architecture for Experts-to-be (link)

Avaliação

A avaliação será feita através de minitestes e um projeto. 

Os minitestes pode ocorrer a qualquer momento e de forma não anunciada. Alunos podem faltar a até 25% dos mini-testes, sem prejuízo.

O projeto deve ser entregue via e-mail para Guilherme, até a meia-noite do dia de entrega

Notas dos minitestes e projetos aqui.

Datas Importantes

• Aulas: terça-feira/18:00-20:00, quinta-feira/18:00-20:00, sala Mario Hattori
  

• Calendário da Universidade