| <?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-Mm7s8vlK5CaZZ_Msx8reCQ" name="new_concept,_HlRqANpbEdyP58ppo1Ieaw" guid="-Mm7s8vlK5CaZZ_Msx8reCQ" version="7.2.0"> |
| <mainDescription><p>
 |
| Architectural goals provide the motivation and rationale&nbsp;for decisions. These goals are&nbsp;often driven
 |
| by&nbsp;the software requirements, particularly system-wide requirements [<a class="elementLinkWithUserText"
 |
| href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html"
 |
| guid="_9ToeIB83Edqsvps02rpOOg">ALL02</a>].
 |
| </p>
 |
| <p>
 |
| Architectural goals define how the system needs to respond to change over time. Architectural goals tend to address the
 |
| following questions:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| What is the expected lifespan of the system?
 |
| </li>
 |
| <li>
 |
| Will the system need to respond to technological changes over that time, such as new versions of middleware or
 |
| other products?
 |
| </li>
 |
| <li>
 |
| How&nbsp;frequently is&nbsp;the system&nbsp;expected to adapt to change?
 |
| </li>
 |
| <li>
 |
| What changes can we anticipate in the future, and how can we make them easier to accommodate?
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| These considerations will have a significant effect on the structure of the system.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
