| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-EytH4BCNGiHF6pZrp8ISCw" |
| name="new_concept,_eFElAOK2EdqHEo0wLIc5jg" guid="-EytH4BCNGiHF6pZrp8ISCw" authors="Mark Dickson" |
| changeDate="2006-07-07T04:53:04.786-0700" changeDescription="First Draft" version="1.0"> |
| <mainDescription><p>
 |
| Not all requirements have equal significance in the architecture.&nbsp;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&nbsp;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&nbsp;demand&nbsp;to validated account holders with sufficient cleared funds.
 |
| </li>
 |
| </ul><br /></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
