Migration of a Chosen Architectural Pattern to Service Oriented ...

More documents

Recommendations

Info

Chapter 5. Guidelines 128Software Architecture DocumentationThe overview of the architecture of TRWAM project is presented in the figure5.16: Content (according to available documentation) of particular elements ofthe architecture is following:1. View – contains packages representing graphical part of the system. PackageAssets (SrodkiTrwale) is responsible for proper representation of assets onGraphical Usage Interface. Package Commons (Wspolne) contains classesresponsible for common parts of Graphical User Interface.2. Controller – here also two packages are available. Package Assets (SrodkiTrwale)contains classes associated with service of assets. Package Commons(Wspolne) contains classes common for the whole application like classesmanaging printing.3. Model – represents classes responsible for persistence of data in database.Package Assets (SrodkiTrwale) contains classes responsible for persistence ofassets. Package Commons (Wspolne) contains classes used by other classes.Package Data (Dane) contains classes persisted in database.4. javax.swing – this is a core package of Java language containing classesresponsible for displaying GUI.5. java.sql – this is a core package of Java language containing classes responsiblefor establishing connection to a database. The package allows sendingdata to previously connected database.6. javax.print – this is a core package of Java language. The package providesprint-relate functionality that allows discovering and selecting printers, setpage format and submit documents to selected printer.Rules and Limitations The rules and limitations presented in TRWAM projectare divided into two types:1. Business rules – document contain sixteen business rules. An example rule:An asset can be lent only if the manager of unit gave permission.2. Domain constrains – document presents only five domain constrains. Anexample constraint: System can use both PLN and Euro currency.GlossaryThe glossary defines basic vocabulary used to describe domain of the system.
Chapter 5. Guidelines 129UsecasesThe system shall implement following usecases:1. Add a vendor information2. Add an asset3. Add / remove spare parts for internal filing system4. Generate asset’s documentation5. Revise asset’s information6. Remove a vendor information7. Remove an asset8. Lend an asset9. Search an asset vendor information10. Search for an asset11. Change asset’s configuration12. Return an assetOverview of available usecasees is presented on figure 5.175.3.5 ImplementationTRWAM is a desktop application. Users invokes functionality of the system usingSwing GUI ( see figure 5.18).The system has several use cases, only one asset related CRUD operation wascompletely implemented - add an asset. The code has only several classes andno unit testing. The only comments that exists in the code are the commentsauto generated by Integrated Development Environment (IDE). The project isnot large, but it is sufficient to show how to implement guidelines.5.4 Application of the guidelines1. Convert MVC into LayersApplied SOA pattern: Service LayersApplication: MVC architectural pattern consists of only three componentsand dependencies between them. Components of MVC are translated into
Page 1 and 2:
Master ThesisSoftware EngineeringTh
Page 3 and 4:
AbstractContext: Several examples o
Page 5 and 6:
List of Figures1.1 Research methodo
Page 7 and 8:
List of Tables3.1 Summary of archit
Page 9 and 10:
3.3.1 Definition of Pattern Languag
Page 11 and 12:
Chapter 1Introduction1.1 Background
Page 13 and 14:
Chapter 1. Introduction 3technique
Page 15 and 16:
Chapter 1. Introduction 5was notice
Page 17 and 18:
Chapter 1. Introduction 7do not pro
Page 19 and 20:
Chapter 1. Introduction 9Chapter 4
Page 21 and 22:
Chapter 2. Related Work 11This chap
Page 23 and 24:
Chapter 2. Related Work 13(b) Chara
Page 25 and 26:
Chapter 2. Related Work 15Figure 2.
Page 27 and 28:
Chapter 2. Related Work 17Drawbacks
Page 29 and 30:
Chapter 2. Related Work 19Figure 2.
Page 31 and 32:
Chapter 2. Related Work 21Advantage
Page 33 and 34:
Chapter 2. Related Work 23between a
Page 35 and 36:
Chapter 2. Related Work 252. Applic
Page 37 and 38:
Chapter 2. Related Work 274. Mediat
Page 39 and 40:
Chapter 2. Related Work 292.3 Summa
Page 41 and 42:
Chapter 3. Architectural Patterns 3
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Chapter 4. Service Oriented Archite
Page 87 and 88: Chapter 4. Service Oriented Archite
Page 113 and 114: Chapter 5. Guidelines 1035.1 Patter
Page 115 and 116: Chapter 5. Guidelines 105Descriptio
Page 117 and 118: Chapter 5. Guidelines 107Result Con
Page 119 and 120: Chapter 5. Guidelines 109ContextAn
Page 121 and 122: Chapter 5. Guidelines 111Result Con
Page 123 and 124: Chapter 5. Guidelines 113System’s
Page 125 and 126: Chapter 5. Guidelines 115ViewSchema
Page 127 and 128: Chapter 5. Guidelines 117ViewViewCo
Page 129 and 130: Chapter 5. Guidelines 119ViewViewCo
Page 131 and 132: Chapter 5. Guidelines 121ViewViewPr
Page 133 and 134: Chapter 5. Guidelines 123FrontendFr
Page 135 and 136: Chapter 5. Guidelines 125complicati
Page 137: Chapter 5. Guidelines 127Concluding
Page 141 and 142: Chapter 5. Guidelines 131puter (ext
Page 143 and 144: Chapter 5. Guidelines 133Group 3 ma
Page 145 and 146: Chapter 5. Guidelines 135Output: Du
Page 147 and 148: Chapter 5. Guidelines 137generation
Page 149 and 150: Chapter 5. Guidelines 139(a) Fronte
Page 151 and 152: Chapter 5. Guidelines 141Figure 5.1
Page 153 and 154: Chapter 5. Guidelines 143Figure 5.1
Page 155 and 156: Chapter 5. Guidelines 145FrontendSc
Page 157 and 158: Chapter 6. Conclusion 147There are
Page 159 and 160: Chapter 6. Conclusion 149RQ.6 How t
Page 161 and 162: References[1] http://www.soa-manife
Page 163 and 164: References 153[22] Frank Buschmann,
Page 165 and 166: References 155[46] Dirk Krafzig, Ka
Page 167 and 168: References 157[67] Xiaohong Qiu. Bu
show all

Migration of a Chosen Architectural Pattern to Service Oriented ...

Create successful ePaper yourself

Delete template?

Save as template?