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 all commits
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
63 changes: 56 additions & 7 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,15 +13,64 @@ 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)

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

.Further Information
=== 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 Spain.
|===

=== 2.3 Development Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Development Methodology | The team will follow an agile development methodology.
| Build Tool | The Z build tool will be used for the compilation process.
|===

=== 2.4 Organizational Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Internal Security Policies | Internal security policies of the organization will be adhered to.
|===

=== 2.5 Interoperability Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Communication Standard | The application must be compatible with communication standard ABC.
|===

=== 2.6 Security Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Two-Factor Authentication | Two-factor authentication is mandatory for all users.
|===

=== 2.7 Performance Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Response Time | The application's response time should not exceed 2 seconds.
|===

=== 2.8 Maintenance and Scalability Constraints
[cols="1,1", options="header"]
|===
| Constraint | Description
| Scalability | The application is expected to be scalable to handle a 20% increase in workload.
|===

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

****