1 / 15

معماری سيستمهای با مقياس بزرگ

معماری سيستمهای با مقياس بزرگ. آزمايشگاه سيستمهای هوشمند زمستان 1385. Uses of views. Capturing the design decisions both early on and as enhancements are made Capturing information about the runtime enviroment for software Providing constrains on the lower-level design and implementation

julie
Download Presentation

معماری سيستمهای با مقياس بزرگ

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. معماری سيستمهای با مقياس بزرگ آزمايشگاه سيستمهای هوشمند زمستان 1385 آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  2. Uses of views • Capturing the design decisions both early on and as enhancements are made • Capturing information about the runtime enviroment for software • Providing constrains on the lower-level design and implementation • Providing input to the structure of the development organization • Designing the system to meet the software reliability, availability, maintainability, and performance requirements • Facilitating communication among the project teams • Communicating software capabilities and constraints to varios developers, testers, and others آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  3. Other way for thinking • Typical questions answered by views of the architecture • What are subsystems or components of the software? • What are responsibilities of the components? • What are the interfaces provided, consumed by these components? • What subsystems or components are impact by a change to the software? • How much retesting is required if we change this component? • When components are involved in installing this change? • How are part of system to be physically distributed? • How will a change impact the performance of the system • What development teams are impacted by a change to this interface? • How much effort is involves in the development of this functionality? آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  4. What software architecture is not • Hardware, network, physical plant architecture • Hardware model number, hardware configuration, routers, LAN • Should not duplicate information on other sources • Appropriate level of detail • Low level implementation details should not included in the software architecture آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  5. Attributes of software architecture(1/2) • Cultural adaptability • Security • Data integrity • Maintainability characteristics • Portability • Changeability • Fragility • Rigidity • Duplication • Understandability • Debugging support • Testability • usability آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  6. Attributes of software architecture(2/2) • Operational system aspects • Availability • Manageability • Upgradeability • Reliability • Recoverability • Performance • Response • Scalability • Capacity/throughput • safety آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  7. Points • Members of the architecture team need to constantly evaluate the software architecture to determine if it meets the desire goal with respect to these characteristics • Architects must constantly prioritize and manage the trade-off between these attributes for a given projects آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  8. Why architect? • Architecting simply recognized the need to focus on the bigger picture of the software design and to provide guidance to the development team designers • It is a place to capture early design decitions • Provide constraints on the lower level design and implementation • Provide the organizational structure for the development team • This goal is that a well defined architecture will produce a system that will be easier to design, develop and maintain آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  9. Uses of software architecture • Training for the new team members • Making modification • Testers need to understand the system • Ensuring architectural attributes • Verification of requirements • Project management • Operating systems آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  10. Architectural viewpoint summary • Viewpoint are built by applying the various UML diagram types to specific architecture development tasks • Each viewpoint has specific modeling goals and stakeholders آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  11. IEEE 1471 viewpoints • Conceptual and analysis viewpoint • Logical design viewpoint • Environment/physical viewpoint آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  12. UML: Unified Modeling Language آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  13. Conceptual and analysis viewpoint آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  14. Logical design viewpoints آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

  15. Environment/physical viewpoint آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)

More Related