1

BA 372 MIDTERMReview

2

Marketecture / Tarchitecture

Influences Problem Domain Ilities

Marketecture and Tarchitecture Collide Technology Base

Human Influences on This Results now while considering the long run

Future Support Needs Architecting for a Class of Needs

Harnessing Feedback Include Developers

Risks Associated w/ This

3

Marketecture / Tarchitecture (2)

Clarity in Communication Both Must Understand the Problem Domain

Worse if Markitect doesn't understand it Each benefits from understanding the other Agreement on Project Management Common Language (e.g. UML) Make Data Available

4

SQL Queries

Project Action SELECT

Join Action FROM

Select Action WHERE

5

Portability

Supposed vs. Real Motivations Real Motivations

It is Cool Early Customer Requests

Costly Doesn't Compensate for a Poor Product Matrix of Pain

6

INTEROPERABILITY

7

SOA Webservices

REST Easy to Access Parameters in URL Not Well Defined

SOAP Machine Readable More Complex Inputs Well Defined Bloated (XML adds data)

8

XML

Formats a.k.a. Schemas MATHML MUSICML

Well Formed

9

UML

Use Case Diagram Shows Scope

Static Class Diagram ERD Shows Entities and Relationships

Sequence Diagram Process Shows Flow of Methods

10

Human Motivations

Resumé Driven Design Sense of Wholeness Giving In To Great Architectures

11

Good Architecture

Encapsulation Loose Coupling High Cohesion Interfaces Parameterization Deferring Uncertain Decisions

12

Success breed failure

Market Pressure w/ No Architectural Support Technical Debt Entropy Entropy Reduction

13

TECHNOLOGICAL CURRENCY

14

Rational 4+1

Logical View Development View Process View Physical View

15

HTTP

Request Request Line

Method Address Http Version

Headers Body

Response Response Line

Version Status Code Status Description

Headers Body

16

HTTP (2)

Stateless