| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>openup&#92;guidances&#92;concepts&#92;&#92;architecturally_significant_requirements.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: architecturally_significant_requirements.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_HrZGIA4MEduibvKwrGxWxA CRC: 1611319007 -->Architecturally Significant Requirements<!-- END:presentationName,_HrZGIA4MEduibvKwrGxWxA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_HrZGIA4MEduibvKwrGxWxA CRC: 1638410698 -->Some requirements have a profound impact on the architecture of the solution and require special attention.<!-- END:briefDescription,_HrZGIA4MEduibvKwrGxWxA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-EytH4BCNGiHF6pZrp8ISCw CRC: 3597024231 --><p> |
| Not all requirements have equal significance in the architecture. Some play an important role in determining the |
| architecture of the system, but others do not. |
| </p> |
| <p> |
| Deciding whether a specific requirement is architecturally significant is often a matter of judgment. Typically, these |
| are requirements that are technically challenging, technically constraining, or central to the system's purpose. |
| </p> |
| <p> |
| These are good examples of Architecturally Significant Requirements: |
| </p> |
| <ul> |
| <li> |
| The system must record every modification to customer records for audit purposes. |
| </li> |
| <li> |
| The system must respond within 5 seconds. |
| </li> |
| <li> |
| The system must deploy on Microsoft Windows XP and Linux. |
| </li> |
| <li> |
| The system must encrypt all network traffic. |
| </li> |
| <li> |
| The ATM system must dispense cash on demand to validated account holders with sufficient cleared funds. |
| </li> |
| </ul><br /><!-- END:mainDescription,-EytH4BCNGiHF6pZrp8ISCw --> |
| </body> |
| </html> |
