generated from Arquisoft/wiq_0
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
922fae8
commit c47f552
Showing
2 changed files
with
13 additions
and
54 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,73 +1,32 @@ | ||
ifndef::imagesdir[:imagesdir: ../images] | ||
|
||
[[section-concepts]] | ||
== Cross-cutting Concepts | ||
== Conceptos Transversales | ||
Estos conceptos todavia no han sido aprobados ni implemenmtados pero dan una idea general al proyecto. | ||
|
||
=== Modelo de Dominio | ||
Esta es una primera version del modelo del dominio muy simple para hacerse una idea como funcionara la aplicacion. | ||
|
||
[role="arc42help"] | ||
**** | ||
.Content | ||
This section describes overall, principal regulations and solution ideas that are relevant in multiple parts (= cross-cutting) of your system. | ||
Such concepts are often related to multiple building blocks. | ||
They can include many different topics, such as | ||
|
||
* models, especially domain models | ||
* architecture or design patterns | ||
* rules for using specific technology | ||
* principal, often technical decisions of an overarching (= cross-cutting) nature | ||
* implementation rules | ||
|
||
=== Experiencia de Usuario | ||
|
||
.Motivation | ||
Concepts form the basis for _conceptual integrity_ (consistency, homogeneity) of the architecture. | ||
Thus, they are an important contribution to achieve inner qualities of your system. | ||
El usuario sera capaz de interactura con una aplicacion web donde se podra registrar y jugar al juego de manera sencilla. | ||
|
||
Some of these concepts cannot be assigned to individual building blocks, e.g. security or safety. | ||
image::08_diagrama_modelo_dominio.png["Modelo de dominio simple provisional"] | ||
|
||
.Form | ||
The form can be varied: | ||
* concept papers with any kind of structure | ||
* cross-cutting model excerpts or scenarios using notations of the architecture views | ||
* sample implementations, especially for technical concepts | ||
* reference to typical usage of standard frameworks (e.g. using Hibernate for object/relational mapping) | ||
.Structure | ||
A potential (but not mandatory) structure for this section could be: | ||
* Domain concepts | ||
* User Experience concepts (UX) | ||
* Safety and security concepts | ||
* Architecture and design patterns | ||
* "Under-the-hood" | ||
* development concepts | ||
* operational concepts | ||
Note: it might be difficult to assign individual concepts to one specific topic | ||
on this list. | ||
image::08-Crosscutting-Concepts-Structure-EN.png["Possible topics for crosscutting concepts"] | ||
.Further Information | ||
See https://docs.arc42.org/section-8/[Concepts] in the arc42 documentation. | ||
**** | ||
|
||
|
||
=== _<Concept 1>_ | ||
=== Seguridad | ||
|
||
_<explanation>_ | ||
|
||
=== Arquitectura y Patrones de Diseño | ||
|
||
_<explanation>_ | ||
|
||
=== _<Concept 2>_ | ||
=== Desarrollo | ||
|
||
_<explanation>_ | ||
|
||
... | ||
|
||
=== _<Concept n>_ | ||
=== Operaciones | ||
|
||
_<explanation>_ | ||
_<explanation>_ |