quarta-feira, 15 de outubro de 2014

Caso de Sucesso - Linha de Produtos

Aluno: Pedro Felipe de Lima


Unnamed

Description: Legal expert systems

Cited Improvements: 
- Increased modifiability, testability, usability (through uniform behavior), and adaptability.

References: C. Fritsch & B. Renz. "Four Mechanisms for Adaptable Systems: A Meta-Level Approach to Building a Software Product Line," R. Nord (ed.), Proceedings SPLC3, Lecture Notes in Computer Science 0302-9743, vol. 3154. Springer, 2004. Page: 34-50. Boston. ISBN: 3540229183. Revised and extended in Software Process Improvement and Practice, v 10, n 2, April-June 2005, 103-24, ISSN: 1077-4866 CODEN: SPIPFL. Wiley, UK. 



terça-feira, 14 de outubro de 2014

Caso de Sucesso - Linha de Produtos


Aluna: Fernanda Gomes Silva


LG Industrial Systems

Description


Elevator control systems


Cited Improvements


  • Decreased complexity of software base; functions reduced by half
  • Reduced cost of making changes


Reference


Klaus Pohl, Günter Böckle, & Frank van der Linden. Software Product Line Engineering, Springer 2005, ch. 21.



Caso de Sucesso - Linha de Produtos

Aluno: Diego Armando de Oliveira Meneses 


Salion, Inc. is a member of the Product Line Hall of Fame.
Description: Revenue acquisition management systems
Cited Improvements:
- Time to market;
- Scalability of product portfolio;

Catálogo de Casos de Sucesso - Linhas de Produto


http://www.sei.cmu.edu/productlines/casestudies/catalog/index.cfm

Cada aluno deve ler e escolher um item de caso de sucesso no uso de linhas de produto, explicar o motivo da escolha de forma sucinta.

quarta-feira, 1 de outubro de 2014

Aluno: Josimar de Souza Lima

Sampathgiri Gopalakrishna (Director, Bigtec, Bangalore, India): Software Architecture is a set of answers to the following questions: 

(1) What are the key design decisions that makes it possible to meet the current business requirements? 
(2) What are the key design decisions that makes it possible to overcome the current constraints imposed on the system? 
(3) How does the key design decisions take care of the known future business requirements? 
(4) How does the key design decisions take care of business agility in general to handle unknown future requirements? 
(5) What are the constraints imposed by the software system on business?

quarta-feira, 24 de setembro de 2014

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."