ࡱ> oqn#` /bjbj\.\. e`>D>D%$ <%<%<%P%L%t :@X&D(*)*)*)*), -???????$AhLD?/*)*)//?*)*)?]2]2]2/d*)*)?]2/?]2]22;.=*)L& ?PP<%/|E=.= @0:@s=.Do0D\=D=T`.>.,]2.$.`.`.`.??2X`.`.`.:@//// dpd$d p$     SUBJECT \* MERGEFORMAT   TITLE \* MERGEFORMAT Software Architecture Document Version <1.0> [Note: Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and shall be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).] [To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9. This must be done separately for Headers and Footers. Alt-F9 will toggle between displaying the field names and the field contents. See Word help for more information on working with fields.] Revision History DateVersionDescriptionAuthor

 Table of Contents  TOC \o "1-3" 1. Introduction  PAGEREF _Toc151297363 \h 4 1.1 Purpose  PAGEREF _Toc151297364 \h 4 1.2 Scope  PAGEREF _Toc151297365 \h 4 1.3 Definitions, Acronyms, and Abbreviations  PAGEREF _Toc151297366 \h 4 1.4 References  PAGEREF _Toc151297367 \h 4 2. Architectural Goals and Constraints  PAGEREF _Toc151297368 \h 4 3. High-level Architectural Overview  PAGEREF _Toc151297369 \h 4 3.1 Dependencies on other Systems  PAGEREF _Toc151297370 \h 4 3.2 Dependencies on Data stores  PAGEREF _Toc151297371 \h 4 4. Use-Case View  PAGEREF _Toc151297372 \h 5 4.1 Overview  PAGEREF _Toc151297373 \h 5 4.2 Use-Case Realizations  PAGEREF _Toc151297374 \h 5 5. Logical View  PAGEREF _Toc151297375 \h 5 5.1 Overview  PAGEREF _Toc151297376 \h 5 5.2 Analysis Model  PAGEREF _Toc151297377 \h 5 5.3 Significant Packages or Subsystems or Layers or Tiers  PAGEREF _Toc151297378 \h 5 6. Process View  PAGEREF _Toc151297379 \h 5 6.1 Overview  PAGEREF _Toc151297380 \h 5 6.2 Interprocess Communication Mechanisms  PAGEREF _Toc151297381 \h 5 7. Deployment View  PAGEREF _Toc151297382 \h 5 7.1 Overview  PAGEREF _Toc151297383 \h 5 7.2 Deployment Policies  PAGEREF _Toc151297384 \h 6 8. Data View  PAGEREF _Toc151297385 \h 6 8.1 Overview  PAGEREF _Toc151297386 \h 6 8.2 Data Access Mechanisms  PAGEREF _Toc151297387 \h 6 9. Size and Performance  PAGEREF _Toc151297388 \h 6 10. Quality  PAGEREF _Toc151297389 \h 6 11. Common Patterns and Mechanisms  PAGEREF _Toc151297390 \h 6   TITLE \* MERGEFORMAT Software Architecture Document Introduction Purpose This document provides a comprehensive architectural overview of the system, using a number of different architectural views to depict different aspects of the system. It is intended to capture and convey the significant architectural decisions that have been made on the system. This document may be used to communicate significant architectural decisions to the technical leads to ensure that design is consistent throughout the project. The architectural views will stabilize very early in Elaboration, but the patterns and guidelines sections of the document will continue to evolve through early Construction. Scope This document describes high level views of the architecture to indicate the overall structure of the project and its relationship to the enterprise architecture. In addition, the document will include patterns and guidelines created by the architect for the design teams to use. These patterns and guidelines will ensure consistency in the design of the project. Reasons for significant architectural decisions will be included along with alternates considered. This will provide a record in case questions arise later in the project or during maintenance of the system. If the reasons for the decisions change, this documentation will provide a basis for revisiting those architectural decisions. Team Members and Roles [This section lists each team member and tells the responsibilities of each member of the team.] Definitions, Acronyms, and Abbreviations [This section provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Software Architecture Document. This information may be provided by reference to the projects Glossary.] References [This section provides a complete list of all documents referenced elsewhere in the Software Architecture Document. Identify each document by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.] Bureau of Grant Applications Project Proposal November 15, 2006 Architectural Goals and Constraints [This section describes the software requirements and objectives that have some significant impact on the architecture; for example, safety, security, privacy, use of an off-the-shelf product, portability, distribution, and reuse. It also captures the special constraints that may apply: design and implementation strategy, development tools, team structure, schedule, legacy code, and so on.] High-level Architectural Overview Dependencies on other Systems [This section describes (typically using a diagram) the relationships that this project has with other systems and projects in the Enterprise.] Dependencies on Data stores [This section describes (typically using a diagram) the relationships that this project has with persistent data stores in the Enterprise.] Use-Case View Overview [This section lists use cases or scenarios from the use-case model if they represent some significant, central functionality of the final system, or if they have a large architectural coveragethey exercise many architectural elements or if they stress or illustrate a specific, delicate point of the architecture. This is typically a use case diagram for the project.] Use-Case Realizations [This section illustrates how the software actually works by giving a few selected use-case (or scenario) realizations, and explains how the various design model elements contribute to their functionality. This would be sequence diagrams for project level use cases.] Logical View Overview [This section describes the overall decomposition of the design model in terms of its package hierarchy and layers. This is typically a diagram of the packages or subsystems of the project.] Analysis Model [This section describes the runtime data of the system, especially data that is shared between components or processes. This is typically a class diagram.] Significant Packages or Subsystems or Layers or Tiers [For each significant package or subsystem or layer or tier, include a subsection with its name, its brief description, and a diagram showing the responsibilities of the package or subsystem. The responsibilities may be shown with project level use cases, interfaces, package contents (classes and nested packages), or subsystem operations.] Process View Overview [This section describes the significant processes and threads of the project, along with their relationships. Each process or thread will include an interface showing the responsibilities of the process or thread. This is typically a component diagram.] Interprocess Communication Mechanisms [Describe the main modes of communication between processes, such as message passing, interrupts, and rendezvous. This may be text or patterns described by class and sequence diagrams.] Deployment View Overview [This section describes one or more physical network (hardware) configurations on which the software is deployed and run. This is typically a deployment diagram. At a minimum for each configuration it should indicate the physical nodes (computers, CPUs) that execute the software and their interconnections (bus, LAN, point-to-point, and so on.) For a small project, you may choose to combine the Process View and Deployment View onto one diagram.] Deployment Policies [List the significant policies or requirements affecting the deployment view. This may include items such as maintenance down-times, backup and recovery schemes, and any required mirroring or hot-backups.] Data View Overview [This subsection describes the persistent data of the system. This is typically a data model, either an ER diagram or a class diagram.] Data Access Mechanisms [Describe the mechanisms by which the components of the system access the data. For example, is this by direct SQL calls to the database, or through an object layer? This description may be text or patterns described by class and sequence diagrams.] Size and Performance [A description of the major dimensioning characteristics of the software that impact the architecture, as well as the target performance constraints.] Quality [A description of how the software architecture contributes to all capabilities (other than functionality) of the system: extensibility, reliability, portability, and so on. If these characteristics have special significance, such as safety, security or privacy implications, they must be clearly delineated.] Common Patterns and Mechanisms [A description of architectural mechanisms to be used in the project( that are not documented in other sections of the SAD), including at least a class diagram with a text description of how to use the mechanism. You may also include a sequence diagram showing the use of the mechanism. These mechanisms may include, for example, error handling, data logging, or access control.]      DOCPROPERTY "Company" \* MERGEFORMAT  PAGE   SUBJECT \* MERGEFORMAT  Version: <1.0> TITLE \* MERGEFORMAT Software Architecture Document Date:
 Confidential( DOCPROPERTY "Company" \* MERGEFORMAT ,  DATE \@ "yyyy" 2006Page  PAGE 2 of  NUMPAGES \* MERGEFORMAT 6 )*+,CDbces -  e f t u w x γ΢γγΑγγ΀ jhjUmHnHu j3hjUmHnHu jhjUmHnHujhMUmHnHuhMCJaJmHnHuhMmHnHu h^:5h&h^:5 hM5 h^:CJhMh^:jh^:U2+destu    $$Ifa$.gd&.$a$-/  * 0 : A lffff$Ifkd$$Ifl\ $  04 laA B C D E F lffff$Ifkd$$Ifl\ $  04 laF G H I J K lffff$Ifkd|$$Ifl\ $  04 laK L M N O P lffff$Ifkd:$$Ifl\ $  04 laP Q R e H w ljhb\\\\bb  kd$$Ifl\ $  04 la ( ) C D E F G H K L W X r s t u v w y z %&@ABCD j!hjUmHnHu jhjUmHnHu j'hjUmHnHu jhjUmHnHu j-hjUmHnHuhMCJaJmHnHuhMmHnHujhMUmHnHu5EMz7dFs?^gdHE `  DEHIef -.HIJKLMP j hjUmHnHu j hjUmHnHu jhjUmHnHu jhjUmHnHu jhjUmHnHujhMUmHnHuhMmHnHuhMCJaJmHnHu4PQZ[uvwxyz}~  234567:;DE_`abcdgh j hjUmHnHu j hjUmHnHu j hjUmHnHu j hjUmHnHu j hjUmHnHujhMUmHnHuhMmHnHuhMCJaJmHnHu4     &'ABCDEFHISTnopqrsvw jthjUmHnHu j hjUmHnHu jz hjUmHnHu j hjUmHnHuhMCJaJmHnHu j hjUmHnHuhMmHnHujhMUmHnHu4 :;<=>?BCbc}~غةؘ؇{h^:jh^:U jhjUmHnHu jhhjUmHnHu jhjUmHnHu jnhjUmHnHuhMCJaJmHnHuhMmHnHujhMUmHnHu jhjUmHnHu0:;Auv145\jrs !!$!!!!!!""""""""D#$"$-$1$N%O%%&&"&#&&&}'''((((((())žžžڷڷ hN_hN_ hE|hE|hE| h`ih`ih`i h^:0J0hN_ hMhM hHEhHEhHEhMjh^:Uh^:H;Av~5Z$\jsgdE|.gdHEgdHEgdHEgd`i..gdMgdMgdHE^gdHE!!!!!""$"$+$)%O% &&#&''(((b)y)s** +)+.gdN_.gdW^gdN_gdE|..gdE|))`)b)r*s*^,_,s,,,-------...... .0.1.?.@.A.B.D.E.K.L.M.O.P.i.j.x.y....... / / /4/Ц jh&hMjh&U h&0Jjh&0JUh&hM5CJ$OJQJh&5CJ$OJQJjh&5CJ$OJQJU h&CJhjjhjU hW^hW^hW^ hN_hN_hN_hE|h^:3)+_,~,-----.......A.B.C.D.M.N.O.z.$Ifh]h&`#$ $&dPa$ $dN.gdN_gdW^.z.....||$Iflkdb$$Ifl0$k 04 la oD($If]D......20.Ykd$$Ifl$V%04 la$Iflkd$$Ifl0$k 04 la. /^/////////ca_]_a_kd$$IflF H$Z Z Z 0    4 la $$Ifa$ $$Ifa$ h$If]h 4/5/C/D/F/G/W/X/\/]/c/d/j/k/l/m/q/r//////// hW^hW^hjhM0JmHnHu h&0Jjh&0JUhMmHnHuh&hMjh&U///.gdN_20&P/ =!"#$%0 /0:&P/ =!"#$% $$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4$$If!vh5 555 #v #v#v#v :V l05 555 4}DyK _Toc151297363}DyK _Toc151297364}DyK _Toc151297365}DyK _Toc151297366}DyK _Toc151297367}DyK _Toc151297368}DyK _Toc151297369}DyK _Toc151297370}DyK _Toc151297371}DyK _Toc151297372}DyK _Toc151297373}DyK _Toc151297374}DyK _Toc151297375}DyK _Toc151297376}DyK _Toc151297377}DyK _Toc151297378}DyK _Toc151297379}DyK _Toc151297380}DyK _Toc151297381}DyK _Toc151297382}DyK _Toc151297383}DyK _Toc151297384}DyK _Toc151297385}DyK _Toc151297386}DyK _Toc151297387}DyK _Toc151297388}DyK _Toc151297389}DyK _Toc151297390$$If!vh55k #v#vk :V l055k 4$$If!vh55k #v#vk :V l055k 4z$$If!vh5V%#vV%:V l05V%4$$If!vh5Z 5Z 5Z #vZ :V l05Z / 42B@B Normal 1$d_HmH sH tH d@d Heading 1'$ & F0x<@&^`05CJOJQJ<@< Heading 2  & F@&CJB@B Heading 3  & F@& 56CJ@@@ Heading 4  & F@&5CJL@L Heading 5 & F@ <@&^@ CJP@P Heading 6 & F@ <@&^@ 6CJH@H Heading 7 & F@ <@&^@ L@L Heading 8 & F@ <@&^@ 6R @R Heading 9 & F@ <@&^@ 56CJDA@D Default Paragraph FontVi@V  Table Normal :V 44 la (k@(No List POP Paragraph2$P^a$B*mH sH uB>@B Title$da$5CJ$OJQJPJ@P Subtitle $<a$6CJ$OJQJmH sH uF@"F Normal Indent|^`|>@> TOC 1 $<]>@> TOC 2 $]^:@: TOC 3 $`^`4@b4 Header  !4 @r4 Footer  !.)@. Page NumberO Bullet1p & FP>T?^`PO Bullet2p & F>Th?^`B* 6O6 Tabletext $x>B@> Body Text$x^@Y@  Document Map-D OJQJD&@D Footnote ReferenceCJH*f@f  Footnote Text&$$h((&d^h` CJOJQJXOX Main Title $d<a$5CJ KHOJQJ@O@ Paragraph1!$dPa$HO"H Paragraph3"$dP^a$HO2H Paragraph4#$dP^a$.@. TOC 4 $X^X.@. TOC 5 % ^ .@. TOC 6 &^.@. TOC 7 '^.@. TOC 8 (x^x.@. TOC 9 )@^@8P@8 Body Text 2*6B*NC@N Body Text Indent +^ 6>*B*HOH Body,$dx1$a$OJQJtH ubOb Bullet4-$ & FQ hdx1$]h^a$OJQJDOD InfoBlue.x^ 6B*ph0U@0 Hyperlink>*B*(W@( Strong5FV@F FollowedHyperlink >*B* ph'`4` '@0v @0v  @00m '@0t @0t  @00m+destu *0:ABCDEFGHIJKLMNOPQReHwEMz7d F s  ? ; A v~5Z$\js"+)O # b!y!s"" #)#_$~$%%%%%&&&&&&&A&B&C&D&M&N&O&z&&&&&&&&&& '^''''''''''0000.0.0.0.00000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0000000000000000000000000000000 0 0 0 0 0  0 0<  0 .0 0 .0w 0 .00 0.06 0 0.0 0.0 0 0]].0k 0]].0 0 0.0 0.0 0.0 0 0.0# 0.0* 0 0  .0 0  .0 0 0 .0  0 .0c! 0.0t" 0 .0!# 0 .0.0h00h00h00h00h00h00h00h00@0@0@0@0@0h0 0 h0 0 h0 0 h0 0 @0 @0 @0 @0 @0 @0 @0 @0 @0h00@0 @0 @0 @0 @0h00h00h00h00h00h00l  '@0x @0x  @00m JUUUUU DP)4// "#$%&). A F K P )+z...//!'(*+,-//)+Cbet(DFWsu%ACe-IKZvx35D`b & B D S o q    ; = b ~ ' %%%%%%%%%%%%%%%%%%%%%%%%%%%%6EJQUo~:IL]biprwU!UT!! _Toc456598586 _Toc151297363 _Toc456598587 _Toc151297364 _Toc456598588 _Toc151297365 _Toc456598589 _Toc151297366 _Toc456598590 _Toc151297367 _Toc151297368 _Toc151297369 _Toc151297370 _Toc151297371 _Toc151297372 _Toc151297373 _Toc151297374 _Toc151297375 _Toc151297376 _Toc151297377 _Toc151297378 _Toc151297379 _Toc151297380 _Toc151297381 _Toc151297382 _Toc151297383 _Toc151297384 _Toc151297385 _Toc151297386 _Toc151297387 _Toc151297388 _Toc151297389 _Toc151297390 ; A v~~5\j")  b!s" #_$'  @ @ X#ir *N" x!"'#}$'c|e?Bd|e? Be|e?pf|e?A6OO'YY'9*urn:schemas-microsoft-com:office:smarttagsplace8*urn:schemas-microsoft-com:office:smarttagsCity ()5%%%%%%%&&&&&''"#$$%%%%%%%&&&&&''333*+c||e u} _$s$$$%%%%%%%%&&&&&&@&O&y&&&&& 'D'F']'c'm'q'''''''%%%%%%%&&&&&'' SG" p  m :D" NcK- E,1 Q+2 Hu3}tqT6 {B pI +sdO NsR F}/m *q 6t Pau 4{ @.@.@..@...@ ....@ .....@ ......@ .......@ ........* hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo( hh^h`OJQJo(Hu34{NsR+sdO,kSG"Paup qT6Q+26tE,1m*qpI:D"{BkNcK-F}/m8k @h ^`OJQJo(k @h 8^8`OJQJo(Qe' pHW^`iY|jN_bME|&^:HE *0:ABCDEFGHIJKLMNOPQ ;  !r"%%%&&N&z&&&&&&&&& '^''''33333@mmmm'@UnknownGz Times New Roman5Symbol3& z Arial?5 z Courier New5& zaTahoma;& z HelveticaABook Antiqua"htFtFO DO D$4d%%2qHX ?M2Software Architecture Document<Project Name>GeriGeri\               Oh+'04 DP p |   Software Architecture DocumentGeri$Software Architecture Document2.dotGeri1Microsoft Office Word@G@@>eP@9PO ՜.+,D՜.+,h$ px  BD% Software Architecture Document Titlex(AI] Company Name Objectives_Toc430444386  !"#$%&'()*+,-./023456789:<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]_`abcdeghijklmpRoot Entry FpRPrData 11Table;:EWordDocumente`SummaryInformation(^DocumentSummaryInformation8fCompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q