| <?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_basic\guidances\templates\architecture.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: architecture.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,__JXkoCk8EduLGM8dfVsrKg CRC: 1822983426 -->Architecture<!-- END:presentationName,__JXkoCk8EduLGM8dfVsrKg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,__JXkoCk8EduLGM8dfVsrKg CRC: 2701263748 -->Templates for representing the architecture work product.<!-- END:briefDescription,__JXkoCk8EduLGM8dfVsrKg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-1Lm8-0FY-QIC56u5t2SC9w CRC: 2598173112 --><p> |
| Here are some templates for representing the architecture. Architecture can be represented in a variety of ways, |
| according to the needs of the project team. See <a class="elementLink" |
| href="./../../../openup_basic/workproducts/architecture,_0XAf0MlgEdmt3adZL5Dmdw.html" |
| guid="_0XAf0MlgEdmt3adZL5Dmdw">Architecture</a> for more information. |
| </p> |
| <p> |
| Feel free to use one or more of these templates or create your own. |
| </p> |
| <p> |
| The <a class="elementLink" href="./../../../openup_basic/roles/architect,_0X9iEMlgEdmt3adZL5Dmdw.html" |
| guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a> should decide what views are useful for describing the system under |
| consideration. |
| </p> |
| <p> |
| Consider one or more relevant views of the architecture and document each one using the provided template for the |
| architectural view. If needed, document information that applies to more than one view using the template provided for |
| the Software Architecture Document to get an integrated representation of the architecture instead of just snapshots |
| taken from different angles. |
| </p> |
| <p> |
| The structuring of the documents must support the needs of the intended audience. For example, instead of a document |
| for the implementation view developers may find more useful alternative forms for the project directory structure like |
| the template provided for the project startup kit. |
| </p> |
| <p> |
| Keep documentation up-to-date but to an essential minimum. When the architecture is under development, decisions are |
| reconsidered frequently so constant revision of the documentation is an unnecessary expense. Determine points in |
| the development lifecycle when documentation should be updated. |
| </p><!-- END:mainDescription,-1Lm8-0FY-QIC56u5t2SC9w --> |
| </body> |
| </html> |
