1 / 16

BA 372 Midterm

This midterm review explores the intricate dynamics of Marketecture and Tarchitecture, emphasizing the critical influences that shape them, including problem domains and human motivations. It addresses essential factors such as clarity in communication, understanding the other’s perspective, and the significance of a common language, like UML, in project management. Furthermore, it highlights the risks associated with inadequate collaboration and the implications of technical debt, interoperability, and architectural integrity. Finally, the review discusses the need for future support and the importance of incorporating developer feedback.

ranae
Télécharger la présentation

BA 372 Midterm

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BA 372 Midterm Review

  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

More Related