Revisión arquitectura

**1.Introduction and Goal** |
1.1 Requirements Overview | realizado |  
1.2 Quality Goals | realizado |  
1.3 Stakeholders | realizado |  
**2.Architecture Constraints** |
**3.System Scope and Context** |
3.1 Business Context | realizado con comentarios |
- _A context diagram should be included at this point. This diagram shows in a glance external systems_
3.2 Technical Context | realizado con comentarios |

- _A module digaram should be included at this point.This diagram shows main system modules_

**4.Solution Strategy** |

- _Mistake: two introductions section  included. Only one should be. Decisions are ok_

**5.Building Block View** | 
5.1 WitheBox Overall System | realizado con comentarios |

- _Maps system should be included_

5.2 Level 2 | realizado |  
5.3 Level 3. | no realizado |  

**6.RuntimeViewer**
6.1 Runtime Scenario 1 | realizado con comentarios |

- _A sequence diagram should be. Include to know who generate the actions described in this section_

6.2 Runtime Scenario 2 | no realizado |  
**7.Deployment View** |
7.1 Infraestructura Level 1 | realizado con comentarios |

- _This section should contains the technical infrastructure used to execute your system, not interface_

7.2 Infraestructura Level 2 | no realizado |  
**8.Cross-cutting Concepts** |
8.1 Conceptos | realizado con comentarios |

- _Concepts should be improved in next  iteration. Not include general description, but how is going to be used in your project_

**9.Design Decisions** |

- _Nothing about google maps api, rdflib…_

**10. Quality Requirements** |
10.1 Quality Tree | realizado |  
10.2 Quality Scenarios | realizado con comentarios |

- _Should be more concrete_

11. Risk and Terchnical Debts | no realizado |  
12. Glossary | realizado |  

Use issue #32 as a checklist for the architecture documentation, starting with the sections marked incomplete or containing reviewer comments. Locate the document covering the numbered sections, then address the requested context, module, map, sequence, infrastructure, concepts, decisions, quality, risk, and technical-debt content. Done means the listed gaps and comments are resolved and the architecture review is complete.

Written by the indexing model from the issue text.