1. SOFTWARE ARCHITECTURE AND DESIGN TEAM 3 – K15T1 Hanh Luong – Leader – T095095 Hao Tran – T094442 Huy Nguyen – T094016 Hieu Le – T093798 Quang Nguyen – T094193 TEAM ASSGIMENT 2 1

2. Content 1.System overview 2.Module view 3.C&C View 4.Allocation view 5.Mapping 2

3. System overview 1. Functionality 3

4. System overview 1. Quality attribute requirement Quality attributeUse caseID Performance UC2.1 View list memberQP01 UC2.4 View detail member informationQP02 UC3.1 Manage saleQP03 UC6.0 StatisticQP04 UC10.1 Update info from POST server to Head office serverQP05 UC10.2 Update info from Head office server to POST office serverQP06 UC11.1 Manage company statisticQP07 Availability UC3.1 Manage saleQA01 UC6.0 Store StatisticQA02 UC11.1 Manage company statisticQA03 Usability UC1.2 Change passQU01 UC2.1 View list memberQU02 UC2.3 Modify member informationQU03 UC4.3 Modify user group informationQU07 UC4.7 View detail account informationQU10 UC4.9 Reset passQU11 UC4.11 Modify account informationQU12 UC5.3 Modify store’s products informationQU15 UC7.1 View list productQU17 UC7.3 View detail productQU18 UC7.4 Modify productQU19 UC7.6 Deliver productQU20 UC11.1 Manage company statisticQU27 4

5. Module view 1.Decomposition style 2.Layered style combine use style 3.Data model 5

6. Module view - Decomposition style 1.Primary presentation 6

7. Module view - Decomposition style 2. Context diagram Context diagram Store 7

8. Module view - Decomposition style 2. Context diagram Context diagram Head office 8

9. Module view- Layered style combine use style 9

10. Module view – Data model 10

11. 11

12. C&C view 1.Share data combine Client – server 2.Multi tier 12

13. C&C view - Share data combine Client – server Packet 1: Manage sale (UC3.1) 13

14. C&C view - Share data combine Client – server Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1) 14

15. C&C view - Share data combine Client – server Packet 3: Manage member information (UC2.0  UC2.5) 15

16. C&C view - Share data combine Client – server Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3) 16

17. C&C view – Multi tier 17

18. Allocation view 1.Deployment view 18

19. Mapping 1.Mapping between views 1.Mapping between C&C view and Module view 2.Mapping between C&C view and Allocation view 2.Mapping requirement to architecture 19

20. Mapping - Mapping between views 1.Mapping between C&C view and Module view 20 SharedShared data combine client- serverDataData model Statistic UICompanyStatistic Store statisticStoreStatistic Add member UI, Edit member UIPermission Edit member UIAccountGroupDetail Add member UI, Edit member UIAccountGroup Add member UI, Edit member UI, Enable/Disable member UI Member CalculationInvoice Store statisticStoreStatisticDetail N/AAccount N/ABranch Edit retail price UIRetailPrice CalculationDetailInvoice N/AStoreProduct Add product UI, Edit product infor UI, Delete product UI Product Add product type UI, Edit product type UI, Delete product type UI ProductType

21. Mapping - Mapping between views 1.Mapping between C&C view and Module view 21 Decomposition ViewShared data combine Client-Server Submodule: Manage sale, UpdateInfoToHeadOffice Packet 1: Manage sale (UC3.1) Submodule: StoreStatistic, CompanyStatistic, UpdateInfoToHeadOffice Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1) Submodule: ManageMember, UpdateInfoToPOST Packet 3: Manage member information (UC2.0  UC2.5) Submodule: ManageProduct, ManageProductType, ManageStoreProduct, UpdateInfoToPOST Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3)

22. Mapping - Mapping between views 1.Mapping between C&C view and Module view 22 Multi-tierLayerLayer style Manage system UIManageAccountUI Catalog UI ManageProductTypeUI Catalog UI ManageProductUI Catalog UI ManageStoreProductUI Catalog UI ManageBranchUI Business UI ManageSaleUI Business UI ManageMemberUI Business UI CompanyStatisticUI Business UI StoreStatisticUI Manage account ManageAccountBL Manage product type ManageProductTypeBL Manage product ManageProductBL Manage store product ManageStoreProductBL Manage branch ManageBranchBL Manage member ManageMemberBL

23. Mapping - Mapping between views 1.Mapping between C&C view and Module view 23 Multi-tierLayerLayer style Manage sale ManageSaleBL Company statistic CompanyStatisticBL Store statistic StoreStatisticBL UpdateToPOST UpdateInfoToPOSTBL UpdateToHeadOffice UpdateInfoToHeadOfficeBL Manage account ManageAccountDA Manage product type ManageProductTypeDA Manage product ManageProductDA Manage store product ManageStoreProductDA Manage branch ManageBranchDA Manage sale ManageSaleDA Manage member ManageMemberDA Store statistic StoreStatisticDA Company statistic CompanyStatisticDA UpdateToHeadOffice UpdateInfoToHeadOfficeDA UpdateToPOST UpdateInfoToPOSTDA

24. Mapping - Mapping between views 1.Mapping between C&C view and Module view 24 MultiMulti - tierData model Web browserN/A Main (HTML)N/A Manage system UI (HTML)N/A Business UI (HTML)N/A Catalog UI (HTML)N/A Manage accountPermission, AccountGroupDetail, AccountGroup, Account Manage sale Invoice, DetailInvoice, StoreProduct, Product, ProductType, Branch, Member Manage member Invoice, DetailInvoice, StoreProduct, Product, ProductType, Branch, Member Store statistic StoreStatistic, StoreStatisticDetail, Invoice, DetailInvoice, StoreProduct, Product, ProductType, Branch, Member Company statistic CompanyStatistic, StoreStatistic, StoreStatisticDetail, Invoice, DetailInvoice, StoreProduct, Product, ProductType, Branch, Member Manage product typeProductType Manage productProduct, ProductType Manage store productStoreProduct, Product, ProductType, Branch Manage branchBranch UpdatetoPOST Permission, AccountGroupDetail, AccountGroup, Account, Product, ProductType, Invoice, DetailInvoice, StoreProduct,, Branch, Member UpdatetoHeadOffice Invoice, DetailInvoice, StoreProduct, Product, ProductType, Branch, Member, StoreStatistic, StoreStatisticDetail Main databaseN/A Backup databaseN/A

25. Mapping - Mapping between views 1.Mapping between C&C view and Allocation view 25 Shared data combine Client-ServerDeployment View Web server Web Server (Store) Head Office Web server Web Server (Head Office) Local DB Database server (Store), Backup server (Store) Head Office DB Database server (Head Office), Backup server (Head Office) Packet 1: Manage sale (UC3.1) Cashier machines Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1) Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3) Store manager machine Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3) Product manager machine Packet 3: Manage member information (UC2.0  UC2.5) Member manager machine Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1) Company manager machine

26. Mapping - Mapping between views 1.Mapping between C&C view and Allocation view 26 MultiMulti - tierDeployment View Web browser User machine of Store manager, Cashier, Head office administrator, Member manager and Company manager, Product manager. Main (HTML)Web server (at store) Manage system UI (HTML)Web server (at Head office) Business UI (HTML)Web server (at store) Catalog UI (HTML)Web server (at store) Manage accountHead office administrator (User machine) Manage saleCashier (User machine) Manage memberMember manager (User machine) Store statisticStore manager (User machine) Company statisticCompany manager (User machine) Manage product typeProduct manager (User machine) Manage productProduct manager (User machine) Manage store productStore manager (User machine) Manage branchCompany manager (User machine) UpdatetoPOSTN/A UpdatetoHeadOfficeN/A Main databaseDatabase server (Head office and store) Backup databaseBack up server (Head office and store)

27. Mapping - Mapping requirement to architecture 27 RequirementArchitecture UC1.1Module View (Data Model) UC1.2Module View (Data Model) UC1.3Module View (Data Model) UC2.0 C&C view [shared data combine client-server (Packet 3: Manage member information(UC2.0  UC2.5)); Multi-tier style] Allocation view [deployment view (Member manager works at Head office)] Module View (Data Model), Module View (layered style combine use style) UC3.1 Module View (Data Model), Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 3: Manage member information (UC2.0  UC2.5)); Multi-tier style] Allocation view [deployment view (Store manager and cashier work at store)] UC4.0 Module View (Data Model), Module View (layered style combine use style) Allocation view [deployment view (Head office administrator works at Head office)] C&C view [Multi-tier style] UC5.0 Module View (Data Model), Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3));Multi-tier style] Allocation view [deployment view (Store manager works at store)] UC6.0Module View (Data Model), Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1)); Multi-tier style] Allocation view [deployment view (Store manager works at store)]

28. Mapping - Mapping requirement to architecture 28 RequirementArchitecture UC7.0 Module View (Data Model), Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3)); Multi-tier style] Allocation view [deployment view (Product manager work at Head office)] UC8.0 Module View (Data Model), Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3)); Multi-tier style] Allocation view [deployment view (Product manager work at Head office)] UC9.0 Module View (Data Model), Module View (layered style combine use style) C&C view [Multi-tier style] Allocation view [deployment view (Company manager work at Head office)] UC10.1 Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 3: Manage member information (UC2.0  UC2.5) ; Packet 1: Manage sale (UC3.1); Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1));Multi-tier style] UC10.2 Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 3: Manage member information (UC2.0  UC2.5); Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3)); Multi-tier style] UC11.1Module View (Data Model), Module View (layered style combine use style) C&C view [shared data combine client-server (Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1)); Multi-tier style] Allocation view [deployment view (Company manager work at Head office)]

29. Mapping - Mapping requirement to architecture 29 RequirementArchitecture QP01 C&C view [shared data combine client-server (Packet 3: Manage member information (UC2.0  UC2.5)] QP02 C&C view [shared data combine client-server (Packet 3: Manage member information (UC2.0  UC2.5)] QP03C&C view [shared data combine client-server (Packet 1: Manage sale (UC3.1)] QP04 C&C view [shared data combine client-server (Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1))] QP05 C&C view [shared data combine client-server (Packet 3: Manage member information (UC2.0  UC2.5) ; Packet 1: Manage sale (UC3.1); Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1)) QP06C&C view [shared data combine client-server (Packet 3: Manage member information (UC2.0  UC2.5); Packet 4: Manage product (UC7.0  UC7.6), manage product type (UC8.0  UC8.5) and manage store’s product (UC5.0  UC5.3));

30. Mapping - Mapping requirement to architecture 30 RequirementArchitecture QP07 C&C view [shared data combine client-server (Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1))] QA01 C&C view [shared data combine client-server (Packet 1: Manage sale (UC3.1)] Allocation view [deployment view (Backup server at each store and Head office)] QA02 C&C view [shared data combine client-server Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1))] Allocation view [deployment view (Backup server at each store)] QA03C&C view [shared data combine client-server Packet 2: Manage store statistic (UC6.0  UC6.2), Manage company statistic (UC11.1))] Allocation view [deployment view (Backup server at each store and Head office)]

31. ??? 31

32. Thanks for listening 32