Karteikarten
Architectural design
Karten in diesem Stapel (13)
- 1Client-server, master slave, distributed are ________ architecturePhysical architecture
- 2Client-server+ Easy to extend
+ Secure
- Bottleneck: network - 3Master-slave+ Dedicated processes (slave)
+ Great for real-time systems
- Not so extensible/secure - 4Distributed+ Allows system designer to delay decisions on when/how services are provided
+ Flexible/scalable/extensible
- Complex - 5Layered model architecture and model-view are examples of ____ architectureLogical architecture
- 6Layered model architecture+ Used to model interacting subsystems
+ Support reuse -> changes in one layer does not affect others, layers can be merged/split
+ Organizes system into set of layers -> each layer provides only a set of services
- Too simple
-- Performance -> needs to bypass layers - 7Model-view controller+ Separates presentation/interaction/data
-> data can change independently of its representation, allows presenting some data in multiple ways
-Too simple -> might involve extra coding, requires to adapt the logical architecture - 8Thin-client+ Simple client (browser, app)
+ Security
- Server/traffic load
Client: presentation
Server: database, data management, application processing - 9Fat-client+ Less server load
- Need to install client
- Bad security (raw data)
Client: presentation, application processing
Server: database, data management - 10Physical 3-tier architecture+ Scalable
+ Best of both worlds
- Double network delays
-Complex
Clients/tier 1: Processing
Web server/tier 2: App processing and data management
DB server/tier 3: database processing - 11Reuse process1. Requirement outline - what the system should do
-> Find candidate items (1 and 2)
2. Modified requirements - new
architecture
-> Select/adapt items (2 and 3)
3. Compose system - 12Re-engineeringMeans making fundamental changes
- porting = program modified to work in new hardware
- translation = programs translated from legacy language to contemporary ones
-migration = programs converted from legacy language to new dialect - 13RefactoringChanges in code without changing behavior
- remove dead code
-renaming variables
- modularize program
Informationen
- Beschreibung
- Information Technology Karteikarten am Architectural design, erstellt von Johan Isaksson am 20/10/2018.
- Erstellt von
- Johan Isaksson
- Aufrufe
- 6
- Bewertung