Aluna: Fernanda Gomes Silva

Pandu Ranga Rao Masabathula (Senior Developer, International SOS Assistance, Trevose, PA): Software Architecture is an evolving blueprint with artifacts of subsystems/components and the interaction between them and with outside entities/systems. It needs to address the needs of business stakeholders within the organizational, technical and any other constraints to achieve the business, technical or any other goals. It also needs to address software trustworthy characteristics like reliability, availability, maintainability, robustness, safety, security and survivability. A good architecture should continue to support the legacy/current systems and provide a way for enhancements for prospective systems.

Aluna: Jislane Silva Santos de Menezes

Sergio Bogazzi (Consultant, Metaframeworks LLC, Carlstadt NJ USA): "Software Architecture is about the logical relationships, characteristics and behaviors of a software system and its constituent parts which serve as the foundation to a system's design. These architectural attributes (relationships, characteristics, and behaviors) serve as the constraints that drive or alter business decisions, as well as guide the technical documentation, implementation, and maintenance of the system as a whole."

Aluno: PEDRO FELIPE DE LIMA

Joseph Cseh (Director, Technology & Innovation, Siemens Medical Solutions, Malvern, PA, USA): Software Architecture consists of a set of principles, standards, components and reference models applied to a software solution.

Aluno: Diego Armando de Oliveira Meneses 

Nelu Suciu (Solution Architect, ISDC, Cluj, Romania): The core element of any software system is data. Along with data any software system provides the following capabilities: collection, processing, storage, presentation, and distribution of data. Software architecture has a two-fold purpose: first it has to design the balanced mix of capabilities to support the realization of business goals, and second it needs to use an optimal mix of implementation technologies regarding hardware, software, and operations. A good software architecture can be recognized when the business goals are fulfilled by the functionality delivered, within the estimated time and cost.

Aluno:  MICHAEL OLIVEIRA DA CRUZ

Peter Jardine (Principal Engineer, Strategy & Architecture, CIO Infrastructure Services, Hosting & Internet, Telstra Corporation Limited, Brisbane, Qld., Australia): Software Architecture is the documentation and supporting models that describe the aesthetics, functions, performance, structures, components, impacts, and costs of a solution. It provides sufficient detail for a software construction company to build and commission a solution that satisfies the requirements.

Distribuição das definições de arquitetura

Exercício 02

Ler as definições de arquitetura de software

http://www.sei.cmu.edu/architecture/start/community.cfm

Cada aluno (Em ordem alfabética) deve ler 10, em sequência, e escolher uma – a que ele/ela achar melhor

A turma deve fazer uma compilação das definições escolhidas.

Sugestão:

Aluno	Definições	Autores
DIEGO ARMANDO DE OLIVEIRA MENESES	1 a 10	(De Stephan Zehrer até Kanhaiya Choudhary)
FERNANDA GOMES SILVA	11 a 20	(Pandu Ranga Rao Masabathula até Ebenezer Adegbile)
FILLIPE SILVA MARINHO MOTA	21 a 30	(Vijaya Agarwal até Rama Mohan Reddy Ambati)
IGOR PETERSON OLIVEIRA SANTOS	31 a 40	(Arash Amiri até Thomas Behrens)
JISLANE SILVA SANTOS DE MENEZES	41 a 50	(Wouter Beneke até Carlos Canal)
JOSÉ JORGE BARRETO TORRES	51 a 60	(John Carter até David Cuyler)
JOSELENO DIAS MOREIRA DOS SANTOS	61 a 70	(Ramayya Darbhamulla até Kameshwar Eranki)
JOSIMAR DE SOUZA LIMA	71 a 80	(Seckin Fidan até Elan Govan)
MARCUS VINICIUS ANDRADE CORTES	81 a 90	(Matthew Gream até Carl Herbst)
MICHAEL OLIVEIRA DA CRU	91 a 100	(Richard Hubert até Moonesh Kachroo)
PEDRO FELIPE DE LIMA	101 a 110	(Venkata Rao Kadari até Kabir Khanna)
THIAGO COUTO DE ALMEIDA	111 a 120	(Cris Kobryn até Siva Kumar)

OBS: As sugestões podem ser alteradas de acordo com as necessidades da turma.