logging in or signing up PF chungbuk Raimondo Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 112 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: April 08, 2008 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... By: kallolchowdhury (15 month(s) ago) How interesting and amazing this post is! It is useful and helpful for me that I like it very much,and I am looking forward to hearing from your next. I have seen such kind of blog in another site. i.e. Architect Pavilion. You can take a tour in architect pavilion. I think it will help you to express your views. It is very usefull site for sw Architect , developers etc. The link is : http://www.architectpavilion.com/vb/content/ Saving..... Post Reply Close Saving..... Edit Comment Close Premium member Presentation Transcript Bridging Enterprise Architectures and System Architectures Using NFR Framework: Bridging Enterprise Architectures and System Architectures Using NFR Framework Dr. Subramanian(UT), Dr. Lawrence Chung(UTD), Dr. Yeong-Tae Song Dept. of Comp.& Info Sciences Towson University U.S.A.Enterprise Architecture (1/2): Enterprise Architecture (1/2) Def1: A means for describing business structure and processes that connect business structure Def2: Enterprise architecture is used to manage and align an organization’s business processes, IT, underlying networks, people, operations and projects with their strategic plan.Enterprise Architecture (2/2): Enterprise Architecture (2/2) May be defined by the constituent architectures (domains): Business architecture Application/Software architecture Technology/Infrastructure architecture Information architecture They are all interrelated to meet the enterprise-wide concerns (business needs)Some Requirements for Enterprise Architecture: Some Requirements for Enterprise Architecture Meeting the stakeholders’ needs Choosing the right IT to support business processes Must be secure and efficient Seamless integration of various architectures for the sharing of efficient and consistent data, information and knowledge Avoid redundancy while making it dependableRole of Enterprise Architecture: Role of Enterprise Architecture Help build IT architecture for the entire organization Standardizes hardware, software, and network technology for an organization Serves as the starting point for all IT projects in an organization Relationship of EA to Business Goals: Relationship of EA to Business Goals Strategic Enterprise Plan (SEP) captures the short-term (3 to 5 years) business goals Strategic Information Systems Plan (SISP), derived from SEP, prioritizes (approves) the development of IS in the short term EA should reflect SEPSystem Architecture: System Architecture Each IS developed in an organization should be based on System architecture developed during requirements analysis Considers the allocation of requirements to hardware, software, and networking components The quality of SA is crucial to the quality of the final system Requirements Hardware Software Networks System architecture Allocated toRelationship between Plans and Architectures: Relationship between Plans and Architectures Strategic Enterprise Plan (SEP) Strategic Information Systems Plan (SISP) Enterprise Architecture Requirements elicitation and analysis Initial phases of an approved IS Approves IS System Architecture Based on Derived from Should meet the goals of Should be Traceable to Derived from Should satisfy Business goals/ objectives Captures IS needs Goals, constraints, guidelines of IS Enterprise strategic direction and IT: Enterprise strategic direction and IT Enterprise’s strategic planning seeks to generate its values -> EA Enterprise’s strategic decisions drive IT planning and strategy to support the business IT planning and strategy prioritize IS projects Each planned IS’s requirements are applied to SA SA should be aligned with EATraceability Between SA and EA (1/2): Traceability Between SA and EA (1/2) Ensures that the SA meets the strategic goals Ensures that the SA satisfies requirements Can be used for technical feasibility analysisTraceability Between SA and EA (2/2): System Architectures should be traceable to the Enterprise Architectures Ensures that all the systems are developed by using pre-approved technologies Helps easy deployment of relevant development personnel across projects within an organization Helps make information systems more manageable Traceability Between SA and EA (2/2)Techniques to Ensure Traceability between SA and EA: Techniques to Ensure Traceability between SA and EA Strategic Alignment Method: Identifies four cross-domain perspectives Does not help determine the perspectives Does not take into account the requirements for the new system Information Economics uses ten factors to determine which system should be funded next Does not provide a way to capture justification for the ratingsSlide13: cross-domain perspectives Business Strategy Business scope Distinctive competencies Business governance IT strategy Technology scope Systemic competencies IT governance Organizational Infrastructure and Processes Administrative structure Processes skills IT Infrastructure and Processes IT architecture Processes Skills Techniques to Ensure Traceability between SA and EA: Techniques to Ensure Traceability between SA and EA Business IT Alignment Method: Uses 12 steps to establish mappings between SA and EA Does not provide a means to capture rationales for decisions Seems to lack an ability to quickly adapt to changed business goals Our approach: Propagatory FrameworkNFR Framework (1/3): NFR Framework (1/3) Non-functional requirements: Describe quality factors and/or constraints of the software system E.g. –ilities, -ness: maintainability, interoperability, understandability, reliability, reusability, completeness, modularity Assumes that decisions taken during dev. process contribute only partially Hard to say “accomplished” or “satisfying” Expect to satisfy given NFRs within acceptable limitsNFR Framework (2/3): NFR Framework (2/3) Each NFR is called softgoal and each element in system architecture or enterprise architecture is called an operationalizing softgoal The rationale for various decisions is captured by another softgoal – the claim softgoalNFR Framework (3/3): NFR Framework (3/3) NFR Framework requires the following iterative steps: Develop NFR goals and their decomposition Develop alternative maintenance models Develop model tradeoffs and rationale Develop goal criticalities Evaluation and analysis The resulting graph is called Softgoal Interdependency Graph (SIG)Partial ontology of NFR Framework: Partial ontology of NFR Framework NFR softgoal Operationalizing softgoal Claim softgoal ++ Strongly Positively Satisficing (MAKE contribution) + Positively Satisficing (HELP contribution) - Negatively Satisficing (HURT contribution) -- Strongly Negatively Satisficing (BREAK contribution) AND contribution OR contribution ! Criticality Used by SIGPropagatory Framework: Propagatory Framework Based on the NFR Framework Applies the propagation rules of the NFR Framework to determine the traceability Uses the notion of softgoals to captures requirements and architectures Uses the notion of contributions to determine the satificability or deniability Develops Softgoal Interdependency Graph to determine traceabilitySlide20: Standardization [Software] Standardization [Interface Technology] Standardization [Application] Standardization [Programming Language] Internet Explorer ++ ++ VS.Net ++ ++ VB.Net C# Java ++ ++ ++ SIG example Steps of the Propagatory Framework: Steps of the Propagatory Framework Decompose the goals of the EA Decompose the requirements for the new system Decompose the candidate system architectures Determine the contributions Propagate the contributions Determine the contributions made by the satisfactory system architectures to the EA decomposition hierarchy. Propagate the contributions of the system architectures up the EA decomposition hierarchy and evaluate the propagations to determine the achievement or lack thereof of the EA’s goals.Application of PF: Application of PF Application illustrated using Home Appliance Control System (HACS) Helps to remotely control home appliances wirelessly over the internet Expected to be a standard feature of future homesHome Appliance Control System: Home Appliance Control SystemSystem Requirements: System RequirementsCandidate System Architectures: Candidate System ArchitecturesEnterprise Architecture: Enterprise ArchitectureSIG for EA’s Goals - PF Step 1: SIG for EA’s Goals - PF Step 1Slide28: Req. [HACS] FR [HACS] NFR [HACS] Extensible [HACS] Security [HACS] Performance [HACS] Reliable [HACS] Control [Appliance] Configure [Appliance] Access [Appliance Status] Modifiable [HACS] Updatable [HACS] Reconfigurable [HACS] Fast Response [HACS] User Authentication [HACS] Appliance C# Classes Network [HACS] Hardware [HACS] Software [HACS] Wireless Arch. [HACS] MS SQL DB Controller -- + Compiled, Faster than Java ++ Classes Not easily Updatable ++ Contributions of a system architecture to the requirements decomposition …..SIG for Contribution of SA’s to Requirements: SIG for Contribution of SA’s to RequirementsSIG for Traceability Between SA and EA: SIG for Traceability Between SA and EAResults of Application of PF: Results of Application of PFAdvantages of PF: Advantages of PF Ensures SA meets Business Goals Ensures SA meets System Requirements Ensures SA is traceable to EA Ensures SA is technically feasibleFuture Work: Future Work Application of Propagatory Framework to Software Architecture determining right software architecture for given requirements Make given requirements traceable to resulting software architecture Automate the process of application of Propagatory Framework to enterprise architecture Develop systematic interface to existing traceability methodology You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
PF chungbuk Raimondo Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 112 Category: Education License: All Rights Reserved Like it (0) Dislike it (0) Added: April 08, 2008 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... By: kallolchowdhury (15 month(s) ago) How interesting and amazing this post is! It is useful and helpful for me that I like it very much,and I am looking forward to hearing from your next. I have seen such kind of blog in another site. i.e. Architect Pavilion. You can take a tour in architect pavilion. I think it will help you to express your views. It is very usefull site for sw Architect , developers etc. The link is : http://www.architectpavilion.com/vb/content/ Saving..... Post Reply Close Saving..... Edit Comment Close Premium member Presentation Transcript Bridging Enterprise Architectures and System Architectures Using NFR Framework: Bridging Enterprise Architectures and System Architectures Using NFR Framework Dr. Subramanian(UT), Dr. Lawrence Chung(UTD), Dr. Yeong-Tae Song Dept. of Comp.& Info Sciences Towson University U.S.A.Enterprise Architecture (1/2): Enterprise Architecture (1/2) Def1: A means for describing business structure and processes that connect business structure Def2: Enterprise architecture is used to manage and align an organization’s business processes, IT, underlying networks, people, operations and projects with their strategic plan.Enterprise Architecture (2/2): Enterprise Architecture (2/2) May be defined by the constituent architectures (domains): Business architecture Application/Software architecture Technology/Infrastructure architecture Information architecture They are all interrelated to meet the enterprise-wide concerns (business needs)Some Requirements for Enterprise Architecture: Some Requirements for Enterprise Architecture Meeting the stakeholders’ needs Choosing the right IT to support business processes Must be secure and efficient Seamless integration of various architectures for the sharing of efficient and consistent data, information and knowledge Avoid redundancy while making it dependableRole of Enterprise Architecture: Role of Enterprise Architecture Help build IT architecture for the entire organization Standardizes hardware, software, and network technology for an organization Serves as the starting point for all IT projects in an organization Relationship of EA to Business Goals: Relationship of EA to Business Goals Strategic Enterprise Plan (SEP) captures the short-term (3 to 5 years) business goals Strategic Information Systems Plan (SISP), derived from SEP, prioritizes (approves) the development of IS in the short term EA should reflect SEPSystem Architecture: System Architecture Each IS developed in an organization should be based on System architecture developed during requirements analysis Considers the allocation of requirements to hardware, software, and networking components The quality of SA is crucial to the quality of the final system Requirements Hardware Software Networks System architecture Allocated toRelationship between Plans and Architectures: Relationship between Plans and Architectures Strategic Enterprise Plan (SEP) Strategic Information Systems Plan (SISP) Enterprise Architecture Requirements elicitation and analysis Initial phases of an approved IS Approves IS System Architecture Based on Derived from Should meet the goals of Should be Traceable to Derived from Should satisfy Business goals/ objectives Captures IS needs Goals, constraints, guidelines of IS Enterprise strategic direction and IT: Enterprise strategic direction and IT Enterprise’s strategic planning seeks to generate its values -> EA Enterprise’s strategic decisions drive IT planning and strategy to support the business IT planning and strategy prioritize IS projects Each planned IS’s requirements are applied to SA SA should be aligned with EATraceability Between SA and EA (1/2): Traceability Between SA and EA (1/2) Ensures that the SA meets the strategic goals Ensures that the SA satisfies requirements Can be used for technical feasibility analysisTraceability Between SA and EA (2/2): System Architectures should be traceable to the Enterprise Architectures Ensures that all the systems are developed by using pre-approved technologies Helps easy deployment of relevant development personnel across projects within an organization Helps make information systems more manageable Traceability Between SA and EA (2/2)Techniques to Ensure Traceability between SA and EA: Techniques to Ensure Traceability between SA and EA Strategic Alignment Method: Identifies four cross-domain perspectives Does not help determine the perspectives Does not take into account the requirements for the new system Information Economics uses ten factors to determine which system should be funded next Does not provide a way to capture justification for the ratingsSlide13: cross-domain perspectives Business Strategy Business scope Distinctive competencies Business governance IT strategy Technology scope Systemic competencies IT governance Organizational Infrastructure and Processes Administrative structure Processes skills IT Infrastructure and Processes IT architecture Processes Skills Techniques to Ensure Traceability between SA and EA: Techniques to Ensure Traceability between SA and EA Business IT Alignment Method: Uses 12 steps to establish mappings between SA and EA Does not provide a means to capture rationales for decisions Seems to lack an ability to quickly adapt to changed business goals Our approach: Propagatory FrameworkNFR Framework (1/3): NFR Framework (1/3) Non-functional requirements: Describe quality factors and/or constraints of the software system E.g. –ilities, -ness: maintainability, interoperability, understandability, reliability, reusability, completeness, modularity Assumes that decisions taken during dev. process contribute only partially Hard to say “accomplished” or “satisfying” Expect to satisfy given NFRs within acceptable limitsNFR Framework (2/3): NFR Framework (2/3) Each NFR is called softgoal and each element in system architecture or enterprise architecture is called an operationalizing softgoal The rationale for various decisions is captured by another softgoal – the claim softgoalNFR Framework (3/3): NFR Framework (3/3) NFR Framework requires the following iterative steps: Develop NFR goals and their decomposition Develop alternative maintenance models Develop model tradeoffs and rationale Develop goal criticalities Evaluation and analysis The resulting graph is called Softgoal Interdependency Graph (SIG)Partial ontology of NFR Framework: Partial ontology of NFR Framework NFR softgoal Operationalizing softgoal Claim softgoal ++ Strongly Positively Satisficing (MAKE contribution) + Positively Satisficing (HELP contribution) - Negatively Satisficing (HURT contribution) -- Strongly Negatively Satisficing (BREAK contribution) AND contribution OR contribution ! Criticality Used by SIGPropagatory Framework: Propagatory Framework Based on the NFR Framework Applies the propagation rules of the NFR Framework to determine the traceability Uses the notion of softgoals to captures requirements and architectures Uses the notion of contributions to determine the satificability or deniability Develops Softgoal Interdependency Graph to determine traceabilitySlide20: Standardization [Software] Standardization [Interface Technology] Standardization [Application] Standardization [Programming Language] Internet Explorer ++ ++ VS.Net ++ ++ VB.Net C# Java ++ ++ ++ SIG example Steps of the Propagatory Framework: Steps of the Propagatory Framework Decompose the goals of the EA Decompose the requirements for the new system Decompose the candidate system architectures Determine the contributions Propagate the contributions Determine the contributions made by the satisfactory system architectures to the EA decomposition hierarchy. Propagate the contributions of the system architectures up the EA decomposition hierarchy and evaluate the propagations to determine the achievement or lack thereof of the EA’s goals.Application of PF: Application of PF Application illustrated using Home Appliance Control System (HACS) Helps to remotely control home appliances wirelessly over the internet Expected to be a standard feature of future homesHome Appliance Control System: Home Appliance Control SystemSystem Requirements: System RequirementsCandidate System Architectures: Candidate System ArchitecturesEnterprise Architecture: Enterprise ArchitectureSIG for EA’s Goals - PF Step 1: SIG for EA’s Goals - PF Step 1Slide28: Req. [HACS] FR [HACS] NFR [HACS] Extensible [HACS] Security [HACS] Performance [HACS] Reliable [HACS] Control [Appliance] Configure [Appliance] Access [Appliance Status] Modifiable [HACS] Updatable [HACS] Reconfigurable [HACS] Fast Response [HACS] User Authentication [HACS] Appliance C# Classes Network [HACS] Hardware [HACS] Software [HACS] Wireless Arch. [HACS] MS SQL DB Controller -- + Compiled, Faster than Java ++ Classes Not easily Updatable ++ Contributions of a system architecture to the requirements decomposition …..SIG for Contribution of SA’s to Requirements: SIG for Contribution of SA’s to RequirementsSIG for Traceability Between SA and EA: SIG for Traceability Between SA and EAResults of Application of PF: Results of Application of PFAdvantages of PF: Advantages of PF Ensures SA meets Business Goals Ensures SA meets System Requirements Ensures SA is traceable to EA Ensures SA is technically feasibleFuture Work: Future Work Application of Propagatory Framework to Software Architecture determining right software architecture for given requirements Make given requirements traceable to resulting software architecture Automate the process of application of Propagatory Framework to enterprise architecture Develop systematic interface to existing traceability methodology