1 / 11

SAIP 19 - Software Architecture in the Future

SAIP 19 - Software Architecture in the Future. The book says …. ABC Revisited Architecture and Legacy Systems Achieving an Architecture From Architecture to System. ABC Revisted. Different kinds of ABCs require different ways of thinking, different processes Book missed open source

bandele
Download Presentation

SAIP 19 - Software Architecture in the Future

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. SAIP 19 - Software Architecture in the Future

  2. The book says … • ABC Revisited • Architecture and Legacy Systems • Achieving an Architecture • From Architecture to System

  3. ABC Revisted • Different kinds of ABCs require different ways of thinking, different processes • Book missed • open source • Microsoft marketplace

  4. Architecture and Legacy Systems • Reverse engineering • Reengineering and migration • Book emphasizes tool support • Better techniques also important • Refactoring

  5. Achieving an Architecture • Understanding quality attributes • The effect of patterns on software arch. • Creating or selecting an architecture • Application generator technology Object-oriented frameworks Reusable architecture Parameterized components Pure Application generators Ad hoc Partial System generators Component libraries Styles kit

  6. Achieving an Architecture We need to: • Make case studies on architectures and architectural styles • Develop taxonomy of • problem spaces (problem frames) • context space (pattern languages) • solution space (patterns)

  7. From Architecture to System • Better development processes • ADL • Practical verification • Prediction: Ideas from ADLs will be integrated into other languages and ADLs will never be widely used

  8. How to Become an Architect • SAIP, LSSA, and POSA have a list of ideas • This list can serve as a guide and a test • This list will not teach you how to be an architect • If you make sure you learn the things on the list then you will become a good architect

  9. How to Learn an Architectural Pattern • Study the pattern • Find a system that uses the pattern • Work with the system, work with the pattern • Design a new system that uses the pattern, or put it in an existing system • If the pattern makes perfect sense then you probably understand it

  10. How to Learn an Architectural Quality • Find a system that exhibits that quality and work with it • Read books that tell how to achieve the quality • Build a system (or three) that must achieve the quality • The first time you build a system with a desired quality, work under an expert

  11. Summary • Architecture is a booming field. There is a big demand for architects, and there is a lot of research that needs to be done. • A good software architect has 10-15 years of experience as a developer. Don’t expect to become a software architect overnight.

More Related