Software architecture is the high- level structure of a software system. It has no concrete definition but can be best described as an organizational.

Slides:



Advertisements
Similar presentations
Implementation of ShipManagement Systems Project Management Prepared by Lana Al-Salem Director of Projects Management SpecTec Ltd.
Advertisements

The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.
Get in touch with Microsoft Dynamics Sure Step Saied Alhamwi, PMP Business Application Manager ACWA Holding
Course: e-Governance Project Lifecycle Day 1
PROGRAM AND PROJECT MANAGEMENT
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
Chapter 20 Introduction to Systems Development and Systems Analysis Copyright © 2012 Pearson Education 20-1.
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
Introduction to Software Engineering Dr. Basem Alkazemi
Software IMprovement using Product LinEs Project Final Presentation Liana Lisboa – PM Project: Starship.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
1 April 2010 TX SET Timeline Project Conceptualization 11 weeks Market Requirements 12 weeks ERCOT Requirements 12 weeks Conceptual Design 6 weeks Detail.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Developing Collaborative Project Managers in IT Presented by: Jane Bachand, PMO Analyst University of Connecticut Amy Baker, Chief Technology Officer West.
SpecFlow & Gherkin Behavior Driven Development. Definitions Behavior Driven Development SpecFlow Structure Gerkin Demo Agenda.
Application Transformation Building Competitive Applications.
Miguel Nunes Information Systems Project Management IS Project Resources.
Project Management Phases Class 6. Initiation & Planning – Agenda Overview of the project management phases Midterm paper details.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 6 Slide 1 Chapter 5 Initiating and Planning Systems Development.
Integrated Capability Maturity Model (CMMI)
From Evidence to Action: Addressing Challenges to Knowledge Translation in RHAs The Need to Know Team Meeting May 30, 2005.
THE ROLE OF PROCESS IN SOFTWARE QUALITY By K.KARTHIKEYAN.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
MyOcean2 First Annual Meeting – April 2013 WP2.3 Service Engineering MyOcean2 First Annual Meeting – Cork /16-17 April 2013.
Moving into Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Copyright © 2002 by The McGraw-Hill Companies, Inc. Information Technology & Management 2 nd Edition, Thompson Cats-Baril Chapter 8 I/S and Organizational.
Management of Post Merger Integration Projects
Rational Unified Process Fundamentals Module 4: Disciplines II.
Chapter 1: Introduction to Systems Analysis and Design
11.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
The Challenge of IT-Business Alignment
Using a Project Model for Assessment of CDIO skills Tomas Svensson, Svante Gunnarsson Linköping University Sweden June
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Software Requirements The starting point of software development “He kept changing the requirements on us” 1 540f07reqelic4sep4.
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
1 מודל ניהול הצוותים של MSF. 2 Causes of failure  Poorly-defined objectives  Insufficient planning  Lack of executive support  Organizational barriers.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
IT Requirements Management Balancing Needs and Expectations.
Chapter 7 IS630. Project Design  Technical Design & Specification Network and System Architecture & Design Software System Architecture & Design  Database.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
Improving engineering productivity APEGGA. Improving Productivity Mega Projects  History  What is needed  How will it be done  Division of Labour.
SOFTWARE SYSTEMS DEVELOPMENT 4: System Design. Simplified view on software product development process 2 Product Planning System Design Project Planning.
Lecture 7: Requirements Engineering
VERMONT COMMUNICATIONS (VCOMM) March 2, 2006.
Apps.  Understand the list of applications or application components that are required, based on the baseline Application Portfolio, what the requirements.
> > > > Prepared for COP-4991 Component-Based Software Development Professor: S. Masoud Sadjadi COP 4991 – Fall 2006 – Term Project Presentation.
1 V /29/12 DOL Shared Service Center Migration NCFLL Briefing.
Requirements Engineering for Web Applications. SR: System Vision Document Written by key stakeholders Written by key stakeholders An executive summary.
Initial Operating Capability Task Force (IOCTF) Status Briefing September 21, 2008.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Computer Science and Engineering - University of Notre Dame Jimmy Neutron CSE 40827/60827 – Ubiquitous Computing December 9, 2009 Project Presentation.
Definitions of GIS Works with geographic information Performs data input, management, manipulation/analysis, and output functions Composed of hardware,
4+1 View Model of Software Architecture
©2012 RAY SVENSON CONSULTING, INC. 1 PHASE 5: IMPLEMENTATION PLANNING Implementation Plan Outline Milestones/Timeline Communication Plan Implementation.
1 SCR756 – Enhancements to the MarkeTrak application –Fondly called - MarkeTrak Phase 3 –ERCOT CEO determined that SCR756 is not necessary prior to the.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
10-1 McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved.
Project Life Cycle and Organization Unit 2. Project Life Cycle Defines the phases that connect the beginning of a project to its end What technical work.
VDM++ Tutorial Architecture.
Fail Fail Poor Communication Lack of Documentation Poor Execution.
Chapter 1: Introduction to Systems Analysis and Design
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Software architecture is the high- level structure of a software system. It has no concrete definition but can be best described as an organizational structure of a system.

 Communicating the high-level design  Reuse of existing design  Extension of a design  Management  Analysis

The architecture process mainly involves two processes, 1)The technical process 2)The organizational process

Initialization committee 2-Architectural Requirement 3-System Structuring 4-Architecture Validation 5-Deployment Technical process Organizational process

o The architecture requirements are a part of system requirements. o These requirements are based on the Architectural application and the business agenda. o The system structure fails if it does not meet the user needs. Hence it is important that we have accurate architecture requirements.

It is the phase where the architecture is created and documented It includes sub-phases like :  Meta architecture  Conceptual Architecture  Logical Architecture  Execution Architecture

Each step in architecture is important, to make sure we are doing the right thing at the right time, we -- Challenging the proposed architecture -- Evaluating it by comparing with the other alternatives

Involves additional people other than those working on the architecture. Architecture will be assessed by experts who look for gaps and weakness based on their experience. A proof is shown that the developed architecture will work.

This process helps by warning us about the project failure factors before it gets too late. It includes two main phases : Initiation and commitment This phase creates a strong support from the management and the sonorous of the project. A communication process is planned.

Deployment This phase follow the technical process. It addresses the needs of the developers who are meant to use the architecture created. This entails consulting, documentation, demos etc…..

Championing Leading and Teaming Communicating and Consulting

 Software Architecture plays a major role in Software engineering  With a perfectly planed and executed software architecture one can be sure of success.