13 Physical Architecture Design

Physical architecture components

- Software components : Data Storage(DM layer의 object persistence), Data Access Logic(DM layer의 data access과 manipulation), Application logic(Problem domain layer에 위치), Presentation logic(human-computer interaction layer에 위치,  사용자에 정보 제시 & 사용자 명령 수용(UI)

- Hardware components : Client computers, servers, connecting network

 

Physical Architectures

① server-based

client(terminal)

server의 기능 : Presentation logic, Application logic, Data Access Logic, Data Storage 

② client-based

- thin client/ fat server : 

client : terminal 보다 조금 나음

server : 모든 과정 

- fat client/ thin server : 

client : Presentation logic, Application logic, Data Access Logic / 모든 과정

server : data storage

③ client server

- 2-Tiered Architecture 클라이언트가 서버에 요청, 서버가 클라이언트에 응

client : Presentation logic, Application logic

server : Data Access Logic, Data Storage

- 3-Tiered Architecture

client : Presentation logic

application server : Application logic

database server : Data Access Logic, Data Storage

 

 

deployment diagram 

- node : 모델에 hw 구성요소

- artifact : 정보 시스템(sw, db..) 구성요소 

- communication path

 

network model

- The network model is a diagram that shows the major components of the information
system (e.g., servers, communication lines, networks) and their geographic locations throughout
the organization. 네트워크 모델은 정보 시스템의 주요 구성 요소(예: 서버, 통신 라인, 네트워크)와 그들의 조직 내 지리적 위치를 보여주는 다이어그램입니다.

 

- high-level diagrams

it shows the locations of the components needed to support the application 애플리케이션을 지원하기 위해 필요한 구성 요소의 위치를 보여줍니다.

- low-level diagrams

for each of the locations shown on the high-level diagram.

 

 

Nonfunctional requirements

1) Operational Requirements

 Technical Environment : type of hardware and software

     HW and SW specification

 System Integration : interaction with other systems

 Portability : response to changing environments

 Maintainability : expected business requirement changes

2) Performance Requirements

 Speed : response time of the system, transaction update time

 Capacity : number of users, volume of data

 Availability and Reliability : specify available times, permissible failure rate 시스템이 사용자에게 제공될 가용성의 정도와 오류로 인한 허용 가능한 장애율입니다.

3) Security Requirements

 System value estimates : business value of the system and data

 Access control : access limitations of users

 Encryption and Authentication : data encryption, and user logging

 Virus control : check for uploading and saving files

4) Cultural and Political Requirements

 Multilingual : English, French, Chinese, and more

 Customization : country-specific information (ex, phone number )

 Making unstated norms explicit : stating assumption (ex, MM-DD-YY form)

 Legal requirements : laws and regulations for personal information