معماری سیستم های با مقیاس بزرگ
اسلاید 1: 1آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)معماری سيستمهای با مقياس بزرگآزمايشگاه سيستمهای هوشمندزمستان 1385
اسلاید 2: 2آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)مشخصات سيستمهایLSکارکرد پيچيده و گسترده.انتظارات سطح بالا در مورد نيازمنديهای غير کارکردی.نياز به اطلاعات گسترده.توزيع شدگی پردازش کارايي و يا اطلاعات.يکپارچگی سخت افزارها و نرم افزارها و سيستمهای ارتباطی مختلف.
اسلاید 3: 3آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)لزوم داشتن يک LSبرای يکپارچه سازی سيستمهای مختلف به منظورنيل به:اقتصادی ساختن سيستم از نظر توسعه و پشتيبانی از طريق استفاده مجدد..فروش يکباره ←رضايت مشتریبرای حل مشکل سيستم های جديد(green field)برای رسيدن به نيازهای بازار و کسب وکاربرای رسيدن به اهداف استراتژيک سازمانیمحافظت از سرمايه
اسلاید 4: 4آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)نمونه هايي از سيستمهایLSسيستم رزرواسيون بليط سيستمهای مالياتیسيستمهای بانکیسيستمهای بازار بورس و سهامسيستمهای انبارداریonline و توزيع شده.سيستمهای خدماتی onlineسيستمهای جامع و يکپارچه سازمانیسيستمهای کنترل و اندازه گيری از را دور بلادرنگ.سيستمهای مخابراتی.
اسلاید 5: 5آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)متغييرهای موجود در LSSمحتوا← کاراييکيفيت ← نيازمنديهای غير کارکردی و ديگر محدودژت ها مانند محدوديت های تکنولژيکیزمانبندی ← زمان مورد نياز برای تکميل LSSهزينه ← سرمايه، فراساختار و هزينه منابع انسانی.
اسلاید 6: 6آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)متغييرهای موجود در LSS Content CostSchedule Quality
اسلاید 7: 7آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)موارد مورد توجه در LSSتقسيم وظايف در توسعه LSS(زمينه های مورد توجه)افراد مختلفمسوليت های متفاوتتخصصهای مختلفهر زمينه دارای مسائل مختلف و روشهايي جهت حل مشکلات می باشد.هر روش ديدگاههای متفاوتی در مواجهه با مساله دارد.ديدگاه تيم طراحیديدگاه مديريت پروژهديدگاه کسب و کار.
اسلاید 8: 8آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Software Development For Large-Scale Systems
اسلاید 9: 9آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Software Architecture for LSSAgendaWhatWhy an LSSViewsArchitecture description
اسلاید 10: 10آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)What is software architectureSoftware architecture is an abstraction (generalized model) of systemsSoftware Architecture is composed of sub-systems or components (possibly nested)Components have properties ,e.g attributes and behaviorThe sub-Systems or componenets have relationship between themNon-runtimeE.g located within the same directory, layer or packageRuntime, e.g coupling (10 types)
اسلاید 11: 11آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)IntroductionLarge-Scale Software Architecture
اسلاید 12: 12آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)What is Software ArchitectureThere of dozens of books talk about software architectureThe definitions used in this book are closely aligned IEEE 1417
اسلاید 13: 13آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Key Terms (1)SystemIs a set of components that accomplishes a specific function or set of functions.ArchitectureIs the fundamental organization of a system embodied in its components, their relationships to each, and to the environment, and the principles guiding its design and evolution.
اسلاید 14: 14آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Key Terms (2)Architectural DescriptionA set of products that document the architectureArchitectural ViewA representation of a particular system or part of a system from a particular perspectiveArchitectural ViewpointA template that describes how to creat and use an architectural viewIncludes a name, stakeholders, concerns addressed by the viewpoint and the modeling and analytic conventions.
اسلاید 15: 15آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)SoftwareArchitectureRefers to analysis, design, documentation, review, approval, and other related activities concerned with the definition and management of the software architectureArchitectural viewsProvide representations of the architectureUsed to guide construction, manage, explore, train personnel, test and perform other engineering tasks related to creation and maintenance of software system
اسلاید 16: 16آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Uses of viewsCapturing the design decisions both early on and as enhancements are madeCapturing information about the runtime enviroment for softwareProviding constrains on the lower-level design and implementationProviding input to the structure of the development organizationDesigning the system to meet the software reliability, availability, maintainability, and performance requirementsFacilitating communication among the project teamsCommunicating software capabilities and constraints to varios developers, testers, and others
اسلاید 17: 17آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Other way for thinkingTypical questions answered by views of the architectureWhat 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 systemWhat development teams are impacted by a change to this interface?How much effort is involves in the development of this functionality?
اسلاید 18: 18آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)What software architecture is notHardware, network, physical plant architectureHardware model number, hardware configuration, routers, LANShould not duplicate information on other sourcesAppropriate level of detailLow level implementation details should not included in the software architecture
اسلاید 19: 19آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Attributes of software architecture(1/2)Cultural adaptabilitySecurityData integrityMaintainability characteristicsPortabilityChangeabilityFragilityRigidityDuplicationUnderstandabilityDebugging supportTestabilityusability
اسلاید 20: 20آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Attributes of software architecture(2/2)Operational system aspectsAvailabilityManageabilityUpgradeabilityReliabilityRecoverabilityPerformanceResponseScalabilityCapacity/throughputsafety
اسلاید 21: 21آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)PointsMembers of the architecture team need to constantly evaluate the software architecture to determine if it meets the desire goal with respect to these characteristicsArchitects must constantly prioritize and manage the trade-off between these attributes for a given projects
اسلاید 22: 22آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)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 designersIt is a place to capture early design decitionsProvide constraints on the lower level design and implementationProvide the organizational structure for the development teamThis goal is that a well defined architecture will produce a system that will be easier to design, develop and maintain
اسلاید 23: 23آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Uses of software architectureTraining for the new team membersMaking modificationTesters need to understand the systemEnsuring architectural attributesVerification of requirementsProject managementOperating systems
اسلاید 24: 24آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Architectural viewpoint summaryViewpoint are built by applying the various UML diagram types to specific architecture development tasksEach viewpoint has specific modeling goals and stakeholders
اسلاید 25: 25آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)IEEE 1471 viewpointsConceptual and analysis viewpointLogical design viewpointEnvironment/physical viewpoint
اسلاید 26: 26آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)UML: Unified Modeling Language
اسلاید 27: 27آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Conceptual and analysis viewpoint
اسلاید 28: 28آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Logical design viewpoints
اسلاید 29: 29آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Environment/physical viewpoint
اسلاید 30: 30آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Roles of Software Architect
اسلاید 31: 31آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)OutlineRoles of software architect and relation with other rolesSkills required for software architectKey approaches to lead software architecture teamTraps and pitfalls associate with software architect
اسلاید 32: 32آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Importance of software architectLack of goof software architect is a part of the lack of good leadership in projectsSoftware architect defines a large part of shared vision of softwareThe idea of the development team about what the final product will be, the effect the software will have and the goals of organizationThe final architecture will balance the conflicting interest of the various stakeholders
اسلاید 33: 33آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Activities for defining shared visionAnalysis the problem domainRisk managementRequirement managementInterface designTechnology roadmap managementDetermination of implementation approachesDefinition of an architecture that meets the system requirements, goal of organization, project budget and scheduleOversight of the mapping from the architecture to the design and implementationCommunication of software architecture to technical and non-technical audienceMaintenance of software architecture during system life cycle
اسلاید 34: 34آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Other software architecture approaches4+1 viewsRM-ODP viewpointsBass architectural structuresHofmeister software architecture views
اسلاید 35: 35آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)RM-ODP viewpointsReferenced Model for Open Distributed Processing (RM-ODP)An ISO standardProvides a framework for the development of standards related distributed processingDefines the important properties of distributed systems; openness, integration, flexibility, modularity, federation, manageability, provisioning of quality services, security, and transparency
اسلاید 36: 36آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)RM-ODP viewpointsEnterprise viewpointInformation viewpointComputational viewpointEngineering viewpoint
اسلاید 37: 37آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Bass architectural structuresDoes not use UMLStructuresModule structureConceptualProcessPhysicalUsesCallsData flowsControl flowClass structure
اسلاید 38: 38آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Hofmeister viewsConceptual viewModule viewExecution viewCode view
اسلاید 39: 39آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Stages of designHigh level designHigh level data structureArchitectureLow level design-code designAlgorithmsLow level data structuresExecutable designVery lower level of detail
اسلاید 40: 40آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Types of designData designArchitectural designExternal interface designAlgorithmic design
اسلاید 41: 41آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Design techniquesRequire some sort of decompositionModular decompositionData oriented decompositionEvent oriented decompositionOutside in designObject oriented design
اسلاید 42: 42آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Architectural view -2Which structure are used, and why?Common view includeModuleProcessUsesClassData flowClassphysical
اسلاید 43: 43آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Typical roles and responsibilitiesRequirementsTechnical riskAnalysis of problem domainDesign of overall softwareReviewer and approver of deliverablesMentoring of design and developersIntegration and test supportImplementation supportTeam leadLaison to project management
اسلاید 44: 44آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key rolesProject managementResponsibilitiesProgram planning, subcontract management, supplier management, software estimation, release management, operation managementRelation to software architectSoftware architect works with project management in definition of release contents and prioritization of features included or omitted from a release
اسلاید 45: 45آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)Development team managersResponsibilitiesManaging individual development teamsRelation to software architectThese managers should clearly understand the interface they provide and consume to other development teams and external entitiesHigh level aspects (COTS tools for interfaces, complexity of development, modification of each interface)
اسلاید 46: 46آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)System architect/ chief engineerResponsibilitiesOverall system design and deliveryTechnical leadership pf the systems engineering, software development, hardware design, network design, even test organizationsRelation to software architectInterfaces between development teams, external interfaces, requirements related issuesIdentify and resolve significant technical issues
اسلاید 47: 47آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)Chief software engineeringResponsibilitiesEnsures the process is followed thoroughout the development life cycle.Relation to software architectTo make sure the delivered software meets the requirements and the interface and port definitions match by those defined by software architect team.
اسلاید 48: 48آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)Hardware architectResponsibilitiesSelecting and configuring of hardwareRelation to software architectSoftware architect provides low level requirements for selecting hardwareHardware architect informs hardware restriction to provide requirementsSoftware architect makes sure the software architecture id defined within the constraints of the hardware.
اسلاید 49: 49آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)Network architectResponsibilitiesDefining the LAN and WAN design and configurationRelation to software architectCommunicate for defining network requirementsDefines constraints implies by network back to software architect
اسلاید 50: 50آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)Technical leads of each releaseResponsibilitiesDeliver each major releaseRelation to software architectCommunicate for technical issuesSoftware architect deliver a set of architecture views to the technical leadCommunication and interfaces with previous release
اسلاید 51: 51آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)Data architectResponsibilitiesDefinition, development and documentation of the data architect.Relation to software architectA member of architecture team.Software architect have final approval of the data architecture.
اسلاید 52: 52آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)System engineering leadsResponsibilitiesResponsible for delivering the system requirementsRelation to software architectSoftware architect review these requirements to make sure they can be deliveredGiven the project constraintsProvide feedback to the system engineer
اسلاید 53: 53آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Relation to other key roles (con)Software system engineering leadResponsibilitiesTranslates and maps the requirements from higher level system group into lower level requirementsRelation to software architectSoftware architecture will often be provided th the organizationSSE team will evolve the software architecture in translating requirements
اسلاید 54: 54آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Skills and background for the architectExtensive software design and developmentTechnical leadershipTeam facilitation skillsCommunication skillsTechnical skillsKnowledge of component communication mechanismsKnowledge of domainAbstraction skills
اسلاید 55: 55آزمايشگاه سيستم های هوشمند (http://ce.aut.ac.ir/islab)Traps and pitfallsClear definition of leadershipReporting structure for the software architectGeographical location of software architect and technical leadsArchitecture team size and compositionSoftware architect lifecycle participatio
نقد و بررسی ها
هیچ نظری برای این پاورپوینت نوشته نشده است.