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

Slides:



Advertisements
Similar presentations
Invoice Management Software Developed by Morbadevi Softwares Morbadevi Softwares®2014, All Rights Reserved.
Advertisements

Preliminary Design: Smart Scheduling Client: Dr. Robert Yoder.
An On-line bookstore Software Engineering II CS616 Software Engineering II Team 4:Jing Fu Hai Huang Xiao-Rong Wang Lijun Yuan.
Web Servers How do our requests for resources on the Internet get handled? Can they be located anywhere? Global?
Generic Simulator for Users' Movements and Behavior in Collaborative Systems A Application D Design D Document Alex Surguch, Niv Saar, Mattan Margalith,
Progress Report 11/1/01 Matt Bridges. Overview Data collection and analysis tool for web site traffic Lets website administrators know who is on their.
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
Architect Presentation POST System K14T01 – Team 02.
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
Members: Trần Huy Thường Trần Mạnh Cường Đào Anh Thư Nguyễn Duy Tiến
IS 4506 Database Connectivity.  Overview Two and Three-Tier C/S Architecture ASP Database Connection ODBC - Connection to DBMS Overview of transaction.
Team assignment 13 TEAM 3 – K15T1 Hanh Luong – Leader – T Hao Tran – T Huy Nguyen – T Hieu Le – T Quang Nguyen – T
Copyright © 2004 Pearson Education, Inc.. Chapter 25 Distributed Databases and Client–Server Architectures.
CaDSR Software Development Update Denise Warzel Semantic Infrastructure Operations Team Presented to caDSR Content team November 2012.
Irwin/McGraw-Hill Copyright © 2004 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS6th Edition.
Greg Andolshek Alex Koch Michael McCormick Team Lasso.
Copyright © 2006 Pilothouse Consulting Inc. All rights reserved. Overview Scale out architecture Servers, services, and topology in Central Administration.
CS480 Computer Science Seminar Introduction to Microsoft Solutions Framework (MSF)
Session 26 Modeling the Static View: The Deployment Diagram Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 27, 2011 Presented.
Project Dragon Small Business Website Content Management System.
SOFTWARE ARCHITECT – DESIGN.  Introduction  Architecture Drivers  POS System Architecture  Mapping Between Perspective  Evaluate Architecture  Project.
3TC Company e-Restaurant Project management plan lick to add Title 2 Contents Introduction add Title 1 Requirement Specifications 3 Design Description.
An application architecture specifies the technologies to be used to implement one or more (and possibly all) information systems in terms of DATA, PROCESS,
CEN Advanced Software Engineering
LOGO Team Assignment 1 Software Architectures. LOGO K15T2- Group21 Contents Introduce to Sale system 1 Architecture Drivers 2 Minimal Acceptable Delivery.
Sale system Expected system: Web-base, Software Application, 2 tiers Application – data, Stand alone database for client, Database engine for Server, Client.
ArcGIS Server for Administrators
Documenting Software Architectures 1.Uses and Audiences for Architecture Documentation Architecture documentation serves as a means of education Architecture.
KFC VIETNAM ORDER SYSTEM HTC TEAM. AGENDA 1.TEAM INTRODUCTION 2.PROJECT OVERVIEW 3.PLAN 4.PRODUCT ARCHITECTURE 5.DATABASE DESIGN 6.TEST PLAN & TEST REPORT.
Group Members Krishna C Kandala Guruprasad Ramachandra Shweta Satish.
LOGO FINAL STATUS REPORT ORDER FOOD ONLINE PROJECT Copy right by © Team 3 – K15T1.
UOFS Information System Version 0.9 Yaodong Bi Copyright 2009, Yaodong Bi.
GOAL User Interactive Web Interface Update Pages by Club Officers Two Level of Authentication.
Introduction Database integral part of our day to day life Collection of related database Database Management System : software managing and controlling.
Three Layer Architecture Why Bother with the Middle Layer?
I Copyright © 2007, Oracle. All rights reserved. Module i: Siebel 8.0 Essentials Training Siebel 8.0 Essentials.
CAPSTONE PROJECT OPEN-ONES PROJECT MANAGEMENT SYSTEM INSTRUCTOR. LÊ NGỌC THẠCH (MR) TEAM MEMBERS. NGÔ ĐỨC DUY MẠNH HOÀNG TR ƯƠ NG PHẠM NGUYỄN TR Ư ỜNG.
Company LOGO Team assignment 03 Team 04 K15T02. Members… 1.Hoàng Thị Kim Dâng 2.Thái Thanh Nhã 3.Trần Thị Mộng Hà 4.Trần Tiễn Hưng 5.Chu Thị Thu Hương.
Adaptive Book Mark-up Repository Service. Team 10 Prof. Malu Rolden Joshua Shorrock Tammy Huynh Yuan Zhang Karun Veligeti.
Petals SAP Point Of Sale System Second Project Presentation M.Tech Team SE 15 (Saturday) Team Aug-2008.
Members: Trần Huy Thường Trần Mạnh Cường Đào Anh Thư Nguyễn Duy Tiến.
INTERNET PROTOCOLS. Microsoft’s Internet Information Server Home Page Figure IT2031 UNIT-3.
Petals SAP Point Of Sale System Second Project Presentation M.Tech Team SE 15 (Saturday) Team Aug-2008.
Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang.
Team assignment 13 TEAM 3 – K15T1 Hanh Luong – Leader – T Hao Tran – T Huy Nguyen – T Hieu Le – T Quang Nguyen – T
Overview  Types of Web Applications There are three main types of web applications:  Customer-facing applications are known as ecommerce or  Employee-facing.
Team 4 Software Architecture and Design Final Project.
Scheduler CSE 403 Project SDS Presentation. What is our project? We are building a web application to manage user’s time online User comes to our webpage.
Statistics Monitor of SPMSII -High level and detailed design Warrior Team Pu Su Heng Tan Kening Zhang.
Software Architect and Design Final Project– K15T2 – Team 04.
LOGO Accounting Module In ERP Supervisor: Mr. Nguyễn Hồng Kỳ Students: Hoàng Phương Thảo Tạ Trung Kiên Nguyễn Tấn Trí Lưu Hằng My Nguyễn Văn Tiệp.
Supervisor: Tran Dinh Tri Group Members: Duong Ngoc Nhat-NhatDN01687 Nguyen Quang Minh-MinhNQ01717 Nguyen Quang Minh-MinhNQ01717 Duong Hoang Nam-NamDH01552.
LOGO e-Citizen. Phan Nhật Minh Phạm Thị Dinh Vũ Xuân Đông Phạm Thị Huyền Nguyễn Thùy Trang
Project Dragon Small Business Website Content Management System.
Blood Bank Phạm Tiến Lập – SE02683 Nguyễn Sơn Hải – SE02879
Designing software applications
ONLINE SHOP MANAGEMENT SYSTEM
Relational database and SQL MySQL LAMP SQL queries
6/25/2018.
Smart Tendering System
About Us JICO Journey Business Requirements Consolidated Solution Hosting Challenges Oracle Cloud Solution Solution Success Summary Q&A.
Data, Databases, and DBMSs
Web-based Console for Controlling a Wireless Sensor Network (WeConWSN)
A Web-based Integrated Console for Controlling a Set of Networks
File Operations Access Permissions.
Database Systems Instructor Name: Lecture-2.
Visual Studio 2005 Tools For Office: Creating A Multi-tier Application
Database Architecture
Team 21: Project Design Team Members: Nathan Staley Steven Murray
What’s new ArcGIS 10.1 for Server The Server Framework
Presentation transcript:

SOFTWARE ARCHITECTURE AND DESIGN TEAM 3 – K15T1 Hanh Luong – Leader – T Hao Tran – T Huy Nguyen – T Hieu Le – T Quang Nguyen – T TEAM ASSGIMENT 2 1

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

System overview 1. Functionality 3

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

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

Module view - Decomposition style 1.Primary presentation 6

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

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

Module view- Layered style combine use style 9

Module view – Data model 10

11

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

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

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

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

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

C&C view – Multi tier 17

Allocation view 1.Deployment view 18

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

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

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)

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

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

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

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

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)

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)]

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)]

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));

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

Thanks for listening 32