Apps.  Understand the list of applications or application components that are required, based on the baseline Application Portfolio, what the requirements.

Slides:



Advertisements
Similar presentations
Doc.:October 2009 Slide 1 Architecture for Smart Grid IT Interoperability (1) Purpose –Understand and model Smart Grid IT and its interoperability needs.
Advertisements

Component-Based Software Engineering Main issues: assemble systems out of (reusable) components compatibility of components.
Deployment Diagrams Depicts a static view of the run-time configuration of Nodes.
Connecting People With Information DoD Net-Centric Services Strategy Frank Petroski October 31, 2006.
Data (What) Function (How) Network (Where) People (Who) Time (When) Motivation (Why) Objectives/ Scope List of things important to the enterprise List.
Conquering Complex and Changing Systems Object-Oriented Software Engineering TJSS System Design Lecture 12 Päivi Ovaska.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
SWE Introduction to Software Engineering
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
1 Software Testing and Quality Assurance Lecture 35 – Software Quality Assurance.
University of California, Irvine ITAG Face-to-Face -10/18/2010 Marina Arseniev.
Course Instructor: Aisha Azeem
Enterprise Architecture 2013 ITAG – Managing Enterprise Architecture Assets April 5 th 2013.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Enterprise Architecture
Chapter 6: The Traditional Approach to Requirements
Effective Methods for Software and Systems Integration
Developing Enterprise Architecture
The Design Discipline.
UML - Development Process 1 Software Development Process Using UML (2)
RUP Fundamentals - Instructor Notes
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Copyright © The Open Group 2011 Your Name Your title 44 Montgomery Street Suite 960 San Francisco, CA USA Tel
An Introduction to Software Architecture
The Challenge of IT-Business Alignment
Software Engineering Chapter 8 Fall Analysis Extension of use cases, use cases are converted into a more formal description of the system.Extension.
RUP Design RUP Artifacts and Deliverables
Software Requirements Engineering CSE 305 Lecture-2.
4/2/03I-1 © 2001 T. Horton CS 494 Object-Oriented Analysis & Design Software Architecture and Design Readings: Ambler, Chap. 7 (Sections to start.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 11 Subsystem Design.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
Chapter 6 – Architectural Design CSE-411, Dr. Shamim H Ripon.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Design Analysis builds a logical model that delivers the functionality. Design fully specifies how this functionality will be delivered. Design looks from.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
5 Levels of MDM Maturity.
Unified Modeling Language. Object Oriented Methods ► What are object-oriented (OO) methods?  OO methods provide a set of techniques for analyzing, decomposing,
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
Software Development A Proposed Process and Methodology.
Introduction to OOAD & Rational Rose cyt. 2 Outline RUP OOAD Rational Rose.
Enterprise Engineering Directorate (EE)
UML (Unified Modeling Language)
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Title 24 Report Generator Robert Scott R ASENT Solutions Nov. 20, 2012.
Simplifying Algebraic Expressions. 1. Evaluate each expression using the given values of the variables (similar to p.72 #37-49)
4+1 View Model of Software Architecture
CS223: Software Engineering Lecture 14: Architectural Patterns.
1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.
Rational Rose For System Design What is Rational Rose? Rational Rose is the visual modeling software solution that lets you create, analyze, design,
From Use Cases to Implementation 1. Structural and Behavioral Aspects of Collaborations  Two aspects of Collaborations Structural – specifies the static.
1 SYS366 Week 2 - Lecture 2 Visual Modeling & UML.
Software architecture is the high- level structure of a software system. It has no concrete definition but can be best described as an organizational.
From Use Cases to Implementation 1. Mapping Requirements Directly to Design and Code  For many, if not most, of our requirements it is relatively easy.
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
EIN 6133 Enterprise Engineering
The Open Group Architecture Framework (TOGAF)
Rational Unified Process
Geospatial Service Architecture Viewpoints
EA Framework TOGAF is a framework - a detailed method and a set of supporting tools - for developing an enterprise architecture.
Computer Services Business challenge
(Software) reuse, is the use of (Software) knowledge, to build new (something) software.
Presentation transcript:

Apps

 Understand the list of applications or application components that are required, based on the baseline Application Portfolio, what the requirements are, and the business architecture scope  Simplify complicated applications by decomposing them into two or more applications

 Ensure that the set of application definitions is internally consistent, by removing duplicate functionality as far as possible, and combining similar applications into one  Identify logical applications and the most appropriate physical applications

 Application Communication diagram  Application and User Location diagram  Enterprise Manageability diagram  Process/Application Realization diagram  Application Migration diagram  Software Distribution diagram  Software Engineering diagram  Application Use-Case diagram

 Select standards for each of the building blocks, re-using as much as possible from the reference models selected from the Architecture Repository  Fully document each building block