Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Software Architecture in Agile Development

No description

Diego Mantilla

on 11 February 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Software Architecture in Agile Development

Sashimi approach Concentric approach Software Architecture in Agile Development Technical vision of the solution: Conceptual baseline.
Module decomposition: Coherent separation of responsibility.
Layers and Tiers: Varying levels of abstraction (layers) and describe a structure for separating responsibilities according to their volatility (tiers).
Components: Packaged pieces of software whose very specific responsibilities are defined by their interfaces.
Classes: Object-oriented level. Developers can fully use the language that they share with the stakeholders. The focus is more on the API level of the infrastructure, and not the actual implementation.
As iterations progress, the actual implementation is incrementally completed, following the needs of the functional part of the application. Cesar Adrián Florez Acacio
Diego Fernando Mantilla Vega
Carlos Andrés Palma Suarez
Tania Katiuska Upegui Chaparro "The best architectures, requirements and designs emerge from self-organizing teams" Emergent and
iterative design Shared Responsibility Dynamic architecture agile teams Multidisciplinary team Quality-attribute requirements must be managed as part of the product backlog and implemented incrementally.
Considering the quality attribute as a user goal.

The metrics for each quality-attribute requirement should be integrated with the continuous build process. Quality Attributes AGILE DEVELOPMENT
TEAM Main focus of Agile:
emergent design and iterative production. TYPES
OF TECHNIQUES SASHIMI CONCENTRIC Architect is not the one who “defines” the design of a solution, the Architecture is performed by the whole team, someone contributes with a perspective and the whole team participates and takes the design decisions. Construction minimum amount of code Focused Infrastructure API. Full incrementally High-level Technical Vision Modules decomposition Layers and Tiers Specific components Object - Oriented "http://www.youtube.com/watch?v=jjHD2lsoqDc" Construction minimum amount of code Not in the actual implementation Team members fully understand the consequences of selected alternatives, remain aware of their initial assumptions, and raise concerns when their validity is affected. It's very important for other members to participate! Even the less experienced team members can provide a somewhat naïve perspective to some discussion. "http://www.youtube.com/watch?v=iFbBzGRuycc" Techniques and
technologies ¿How can we apply agile
to the architectural space? Regular Test Tools
and Frameworks Specific checking tools
over quality attributes Deployment configuration tools
for different staging environments Flexibility and mantenibility
metric tools
Full transcript