Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentacion Apartado 2 #10

Merged
merged 2 commits into from
Feb 5, 2024
Merged

Documentacion Apartado 2 #10

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ae2fdee
Plantilla docuemntacion
UO290054 Feb 5, 2024
399f658
Adaptacion de la pantilla
UO290054 Feb 5, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Adaptacion de la pantilla
  • Loading branch information
@UO290054
UO290054 committed Feb 5, 2024
commit 399f6587379709207fb2df6ed3bba9ddebab7da8
24 changes: 2 additions & 22 deletions docs/src/02_architecture_constraints.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,31 +13,20 @@ Any requirement that constraints software architects in their freedom of design
Architects should know exactly where they are free in their design decisions and where they must adhere to constraints.
Constraints must always be dealt with; they may be negotiable, though.

.Form
Simple tables of constraints with explanations.
If needed you can subdivide them into
technical constraints, organizational and political constraints and
conventions (e.g. programming or versioning guidelines, documentation or naming conventions)


.Further Information

See https://docs.arc42.org/section-2/[Architecture Constraints] in the arc42 documentation.


=== 2.1 Technical Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Application Server Version | Usage of version X.X of the application server is required.
| Compatibility with Operating Systems | The application must be compatible with Windows and Linux operating systems.
| Compatibility with Operating Systems | The application must be compatible with Windows .
|===

=== 2.2 Legal and Regulatory Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Compliance with Privacy Regulations | The application must comply with privacy regulations in country Y.
| Compliance with Privacy Regulations | The application must comply with privacy regulations in country Spain.
|===

=== 2.3 Development Constraints
Expand Down Expand Up @@ -83,14 +72,5 @@ See https://docs.arc42.org/section-2/[Architecture Constraints] in the arc42 doc
| Scalability | The application is expected to be scalable to handle a 20% increase in workload.
|===

=== 2.9 Other Relevant Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| [Add any additional constraint here] | [Description of the additional constraint]
|===

=== 2.10 Impact on Design Decisions
These constraints will influence the selection of design patterns, technologies, and implementation approaches. It is crucial to consider these limitations when making design decisions, although some constraints may be negotiable.

****