├── .gitignore ├── LICENSE ├── README.md ├── images ├── OOAD.png ├── TM.png ├── appendixA.png ├── appendixB.png ├── appendixC.png ├── appendixD.png ├── appendixE.png ├── appendixF.png ├── core_layer.png ├── define_module.png ├── deployment.png ├── deployment_sequence.png ├── deployment_view.png ├── module.png ├── module_view.png ├── refine_module.png ├── requirement.png ├── system_definition.png ├── template.png ├── threadA.png ├── threadA_sequence.png └── validate_module.png ├── pom.xml └── src └── main └── java └── com └── bosornd └── example ├── core ├── TM.java └── TP.java ├── logic ├── TA.java ├── TB.java └── TC.java └── ui └── TU.java /.gitignore: -------------------------------------------------------------------------------- 1 | # Compiled class files 2 | *.class 3 | 4 | # Log files 5 | *.log 6 | 7 | # BlueJ files 8 | *.ctxt 9 | 10 | # Mobile Tools for Java (J2ME) 11 | .mtj.tmp/ 12 | 13 | # Package Files # 14 | *.jar 15 | *.war 16 | *.nar 17 | *.ear 18 | *.zip 19 | *.tar.gz 20 | *.rar 21 | 22 | # Virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml 23 | hs_err_pid* 24 | 25 | # Maven specific files 26 | target/ 27 | pom.xml.tag 28 | pom.xml.releaseBackup 29 | pom.xml.versionsBackup 30 | pom.xml.next 31 | release.properties 32 | 33 | # Eclipse specific files 34 | .project 35 | .classpath 36 | .settings/ 37 | bin/ 38 | 39 | # IntelliJ IDEA specific files 40 | .idea/ 41 | *.iml 42 | *.iws 43 | out/ 44 | 45 | # NetBeans specific files 46 | nbproject/private/ 47 | build/ 48 | nbbuild/ 49 | dist/ 50 | nbdist/ 51 | .nb-gradle/ 52 | 53 | # VS Code specific files 54 | .vscode/ -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | This is a simple project that demonstrates the module design process and architecture documentation. This project implements the designed architecture in Java. This helps to understand concept of S/W elements - components, modules and their mappings to code. 2 | 3 | ### Object-Oriented Analysis & Design 4 | The basic object-oriented analysis & design (OOAD) process is as shown in the figure below. Module design has same process and follows object-oriented design principles. 5 | 6 | ![OOAD process](images/OOAD.png) 7 | 8 | ### Module design 9 | #### Step 1. Identify Object / Component 10 | ![Deployment View](images/deployment_view.png) 11 | Assume that it is designed as shown in the deployment view in terms of execution. It's a multi-threaded system composed of 3 threads. 12 | - Thread A is composed of components U and A. U gets input from the user and requests A to process it. A processes the input and requests thread B to do more. 13 | - Thread B is composed of components M1 and B. M1 gets a request from thread A and requests B to process it. B processes the requested and requests thread C to do more. 14 | - Thread C is composed of components M2 and C. M2 gets a request from thread B and requests C to process it. C processes the requested to the user. 15 | 16 | #### Step 2. Define Class / Module 17 | ![Module Defined](images/define_module.png) 18 | In basic, components can be mapped to modules. Components U, A, B and C are mapped to modules TU, TA, TB and TC. However, components M1 and M2 have almost identical behavior of getting requests from the other thread and requesting to the internal component to handle them. Components M1 and M2 are mapped to module TM, which means one module TM is instantiated to 2 different components M1 and M2. 19 | 20 | #### Step 3. Refine Class / Module 21 | ![Module Refined](images/refine_module.png) 22 | 5 modules TU, TM, TA, TB and TC defined in step 2 should be implemented. Module architecture should be refined to enhance maintainability. 23 | - Modules TA, TB and TC are programs that implement request processing. Here, the common part is extracted into a separate module TP, which is extended to implement modules TA, TB and TC. 24 | - Modules TM and TP are core and independent of business logic. They can be grouped into core layer, which is the lowest layer. 25 | - TU is a module related to the user interface. Because the user interface changes frequently, it is placed at the top layer, the UI layer. 26 | - Modules TA, TB and TC which implement business logic can be grouped into logic layer. 27 | - The final module architecture is a three-layer architecture composed of UI, logic and core layers. 28 | 29 | The designed module architecture needs validation. 30 | - In the deployment view (left), component M1 uses component B(red arrow), but module TM must not depend on module TB in the module view (right). 31 | - In the module view (right), module TB extends module TP, which module TM is allowed to use. So, component B instantiated in module TB is injected into component M1 as an instance of TP (dependency injection). M1 doesn't need to know TB. M1 only uses TP instances. Module TM doesn't depend on module TB. 32 | - Same with components M2 and C. 33 | 34 | ![Module Validation](images/validate_module.png) 35 | 36 | ### Architecture Documentation 37 | The SW Architecture document consists of the following table of contents. 38 | ![Architecture Document](images/template.png) 39 | 40 | #### Chapter 1. Overview 41 | In this chapter, the system should be defined clearly. The system is specified as a black box. Internal components are not in the system definition. 42 | 43 | System Definition 44 | 45 | #### Chapter 2. Requirements 46 | In this chapter, the more detail requirement should be specified. It's better to specify what the system should do with the request. 47 | 48 | Requirements 49 | 50 | #### Chapter 3. Architecture 51 | In this chapter, the designed architecture in terms of execution (as shown in the below view) should be explained - how the system works. 52 | 53 | ![Deployment View](images/deployment_view.png) 54 | 55 | When describing an architecture which is complex, it is better to first describe an abstracted high-level one. In terms of execution, deployment view can be first. 56 | 57 | The architecture designed in terms of execution is a multi-threaded system with 3 threads - threads TA, TB and TC. 58 | 59 | Deployment View 60 | 61 | The more detail system behavior can be described using a sequence diagram as shown below. 62 | 63 | Sequence Diagram 64 | 65 | ##### 3.1 thread TA 66 | 67 | In section 3.1, the internals of thread TA can be described. Thread TA is composed of components U and A. 68 | 69 | Thread TA 70 | 71 | Component U gets input from the user and requests component A to handle it. Component A processes the request and requests thread B to do more. The detail flow can be described using a sequence diagram as shown below. 72 | 73 | Sequence Diagram 74 | 75 | In the same way, the internals of threads TB and TC can be explained in sections 3.2 and 3.3. 76 | 77 | #### Chapter 4. Module 78 | In this chapter, the designed architecture in terms of development should be explained - how the system should be implemented. 79 | 80 | It is better to first describe the top level view (layered view) instead of the complex overall module view. 81 | 82 | Layered Architecture 83 | 84 | The designed architecture in terms of development is 3 layered architecture, which is composed of UI, logic and core layer. 85 | - UI layer is allowed to use (depend on) logic and core layer. 86 | - Logic layer is allowed to use core layer but not to use UI layer. 87 | - Core layer is not allowed to use UI and logic layer. 88 | 89 | ##### 4.1 Core layer 90 | In section 4.1, the internals of core layer can be described. Core layer is composed of modules TM and TP. 91 | 92 | Core Layer 93 | 94 | ###### 4.1.1 TM 95 | In section 4.1.1, module TM can be described using providing / required interfaces. Module TM should provide interface InterfaceTM. 96 | 97 | Module TM 98 | 99 | In the same way, the internals of other layers can be described in Sections 4.2 and 3.3. 100 | 101 | #### Appendix 102 | The appendix helps the reader to understand how to approach architectural design. It should answer important questions to the reader. 103 | 104 | #### Question 1. rationale to design the final architecture 105 | What made you design the final architecture? The reader wants to know the top-level views in terms of execution (chapter 3) and development (chapter 4). 106 | 107 | ![Appendix F](images/appendixF.png) 108 | 109 | Appendix F describes the rationale for designing the top-level architecture. In the architectural design process, the final architecture was incorporated from selected candidate architectures. They can be rationales to design the final architecture. 110 | 111 | #### Question 2. rationale for architectural decisions 112 | What made you decide on the architectural decision (candidate architecture)? The reader wants to know why you choose the design over alternatives. 113 | 114 | ![Appendix E](images/appendixE.png) 115 | 116 | Appendix E describes the rationale for deciding architectural decisions. In the architectural design process, candidate architectures were evaluated according to quality requirements and selected from the evaluation. They can be rationales for architectural decisions. 117 | 118 | #### Question 3. proof of optimal architecture 119 | Is the designed architecture optimal? The reader wants to know how much close the designed architecture is to the optimal. 120 | 121 | Appendix D 122 | 123 | Appendix D describes the proof of optimal architecture design - how to approach to design candidate architectures from quality requirements. What are architectural concerns to enhance quality requirement? What are candidate architectural decisions to address them? What are mitigating solutions for the weakness of the candidate architectures? How much considered to get the optimal architecture design needs to be explained. 124 | 125 | Domain model is a conceptual architecture for providing functional requirements, which doesn't reflect quality requirements. The analysis of quality requirements and the design of candidate architectures in appendix D are based on the domain model. Appendix A describes the domain model. 126 | 127 | Appendix A 128 | 129 | #### Question 4. rationale for quality requirements 130 | What made you determine quality requirements? 131 | - high-priority quality attributes 132 | - low-priority quality attributes 133 | - non-functional requirements 134 | - ignored quality scenarios 135 | 136 | Appendix C 137 | 138 | Appendix C describes the rationale for quality requirements. Quality requirements were determined based on analysis of quality scenarios according to importance and difficulty. They should be aligned with business drivers. Ultimately, they are determined by stakeholders. 139 | 140 | #### Question 5. rationale for missing quality requirements 141 | Why did you miss quality requirements? The reader wants to know how to create quality scenarios. 142 | 143 | Appendix B 144 | 145 | Appendix B describes the way how to create quality scenarios. 146 | - scenario generation in utility tree (top-down approach) 147 | - brainstorming with stakeholders (bottom-up approach) 148 | - quality attribute workshop 149 | -------------------------------------------------------------------------------- /images/OOAD.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/OOAD.png -------------------------------------------------------------------------------- /images/TM.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/TM.png -------------------------------------------------------------------------------- /images/appendixA.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/appendixA.png -------------------------------------------------------------------------------- /images/appendixB.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/appendixB.png -------------------------------------------------------------------------------- /images/appendixC.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/appendixC.png -------------------------------------------------------------------------------- /images/appendixD.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/appendixD.png -------------------------------------------------------------------------------- /images/appendixE.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/appendixE.png -------------------------------------------------------------------------------- /images/appendixF.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/appendixF.png -------------------------------------------------------------------------------- /images/core_layer.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/core_layer.png -------------------------------------------------------------------------------- /images/define_module.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/define_module.png -------------------------------------------------------------------------------- /images/deployment.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/deployment.png -------------------------------------------------------------------------------- /images/deployment_sequence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/deployment_sequence.png -------------------------------------------------------------------------------- /images/deployment_view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/deployment_view.png -------------------------------------------------------------------------------- /images/module.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/module.png -------------------------------------------------------------------------------- /images/module_view.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/module_view.png -------------------------------------------------------------------------------- /images/refine_module.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/refine_module.png -------------------------------------------------------------------------------- /images/requirement.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/requirement.png -------------------------------------------------------------------------------- /images/system_definition.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/system_definition.png -------------------------------------------------------------------------------- /images/template.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/template.png -------------------------------------------------------------------------------- /images/threadA.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/threadA.png -------------------------------------------------------------------------------- /images/threadA_sequence.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/threadA_sequence.png -------------------------------------------------------------------------------- /images/validate_module.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/bosornd/example-module-design/84e38bb2541e446d480e3670bed0178a8affab5a/images/validate_module.png -------------------------------------------------------------------------------- /pom.xml: -------------------------------------------------------------------------------- 1 | 3 | 4.0.0 4 | 5 | com.bosornd.example 6 | example-module-design 7 | 1.0-SNAPSHOT 8 | jar 9 | 10 | 11 | 21 12 | 21 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | org.apache.maven.plugins 23 | maven-compiler-plugin 24 | 3.8.1 25 | 26 | ${maven.compiler.source} 27 | ${maven.compiler.target} 28 | 29 | 30 | 31 | 32 | -------------------------------------------------------------------------------- /src/main/java/com/bosornd/example/core/TM.java: -------------------------------------------------------------------------------- 1 | package com.bosornd.example.core; 2 | 3 | public class TM extends Thread { 4 | Boolean requested = false; 5 | int number; 6 | TP p; 7 | 8 | public TM(TP p) { 9 | this.p = p; 10 | } 11 | 12 | public void request(int number) { 13 | this.number = number; 14 | requested = true; 15 | } 16 | 17 | public void run() { 18 | while(!requested) { 19 | try { 20 | Thread.sleep(100); 21 | } catch (InterruptedException e) { 22 | e.printStackTrace(); 23 | } 24 | } 25 | 26 | p.process(number); 27 | } 28 | } -------------------------------------------------------------------------------- /src/main/java/com/bosornd/example/core/TP.java: -------------------------------------------------------------------------------- 1 | package com.bosornd.example.core; 2 | 3 | public abstract class TP { 4 | public abstract void process(int number); 5 | } -------------------------------------------------------------------------------- /src/main/java/com/bosornd/example/logic/TA.java: -------------------------------------------------------------------------------- 1 | package com.bosornd.example.logic; 2 | 3 | import com.bosornd.example.core.TM; 4 | import com.bosornd.example.core.TP; 5 | 6 | public class TA extends TP { 7 | TM m; 8 | 9 | public TA(TM m) { 10 | this.m = m; 11 | } 12 | 13 | public void process(int number) { 14 | System.out.println("TA.process: " + number); 15 | 16 | // request to m 17 | m.request(number + 1); 18 | } 19 | } -------------------------------------------------------------------------------- /src/main/java/com/bosornd/example/logic/TB.java: -------------------------------------------------------------------------------- 1 | package com.bosornd.example.logic; 2 | 3 | import com.bosornd.example.core.TM; 4 | import com.bosornd.example.core.TP; 5 | 6 | public class TB extends TP { 7 | TM m; 8 | 9 | public TB(TM m) { 10 | this.m = m; 11 | } 12 | 13 | public void process(int number) { 14 | System.out.println("TB.process: " + number); 15 | 16 | // request to m 17 | m.request(number + 1); 18 | } 19 | } -------------------------------------------------------------------------------- /src/main/java/com/bosornd/example/logic/TC.java: -------------------------------------------------------------------------------- 1 | package com.bosornd.example.logic; 2 | 3 | import com.bosornd.example.core.TP; 4 | 5 | public class TC extends TP { 6 | public void process(int number) { 7 | System.out.println("TC.process: " + number); 8 | } 9 | } -------------------------------------------------------------------------------- /src/main/java/com/bosornd/example/ui/TU.java: -------------------------------------------------------------------------------- 1 | package com.bosornd.example.ui; 2 | 3 | import java.util.Scanner; 4 | 5 | import com.bosornd.example.core.*; 6 | import com.bosornd.example.logic.*; 7 | 8 | public class TU { 9 | TP p; 10 | 11 | public TU(TP p) { 12 | this.p = p; 13 | } 14 | 15 | public void process() { 16 | Scanner in = new Scanner(System.in); 17 | p.process(in.nextInt()); 18 | in.close(); 19 | } 20 | 21 | public static void main(String[] args) { 22 | TC c = new TC(); 23 | TM m2 = new TM(c); // thread TC 24 | m2.start(); 25 | 26 | TB b = new TB(m2); 27 | TM m1 = new TM(b); // thread TB, connected to TC 28 | m1.start(); 29 | 30 | TA a = new TA(m1); 31 | TU u = new TU(a); // main thread(TA), connected to TB 32 | 33 | u.process(); 34 | 35 | try { 36 | m1.join(); 37 | m2.join(); 38 | } catch (InterruptedException e) { 39 | e.printStackTrace(); 40 | } 41 | } 42 | } --------------------------------------------------------------------------------