CPSC 875 John D. McGregor C23 - Architecture evolution/organization/safety analysis and product lines.

Slides:



Advertisements
Similar presentations
National Association for Regulatory Administration September 13, 2011 IT’s NOT Like Building a House Mark Parker (800)
Advertisements

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Software Process Models
Chapter 2 Modeling the Process and Life Cycle Shari L. Pfleeger
Unit 2. Software Lifecycle
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
29 September Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will.
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Feature Driven Development
GAJAH ANNUAL REPORT 2015 | 1 Business Process Management Meghan Atkins Lohith Bangalore Omprakash John Doyle Rebecca Mazur.
CS 5150 Software Engineering
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CPSC 871 John D. McGregor Processes – a first iteration Module 1 Session 1.
Standards John D. McGregor. But first… SECIE-Safety-in-Software-and-Human- Intensive-Systems-Leveson-brief.pdf.
CPSC 871 John D. McGregor MSumS2 Summary – technical issues in software engineering.
CPSC 871 John D. McGregor Module 7 Session 2 Agile Software Development.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
RUP Implementation and Testing
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
Software Engineering Environment  A quality focus: constant incremental improvement  Process: framework to organize development activities  Methods:
CS CS 5150 Software Engineering Lecture 3 Software Processes 2.
CPSC 372 John D. McGregor Process Module 1 Session 1.
CpSc 875 John D. McGregor AADL. Point of sale system.
Jump to first page (c) 1999, A. Lakhotia 1 Software engineering? Arun Lakhotia University of Louisiana at Lafayette Po Box Lafayette, LA 70504, USA.
.com Software Testing Tutorials “Basics for beginners. Fundamentals for everyone.” Welcome to Day 4. We will start at 4:35 PM PST. Software Testing Tutorials.
CPSC 871 John D. McGregor M9S1 Next Steps. Challenges Relating Requirements and Architectures Moving to Evidence-based Practice Engineering Scalability.
An Introduction to Software Engineering
Software Engineering II Lecture 3 Fakhar Lodhi. Software Life-Cycle Steps Life-cycle model (formerly, process model) –Requirements phase –Specification.
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
CSC 354 – System Development Life Cycles & Processes, Spring 2015 March 2015 Dr. Dale Parson.
Stand Up Comedy Project/Product Management
1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Software Testing Process
CPSC 871 John D. McGregor Module 8 Session 3 Assignment.
Software Engineering, 8th edition. Chapter 4 1 Courtesy: ©Ian Sommerville 2006 FEB 13 th, 2009 Lecture # 5 Software Processes.
CS223: Software Engineering Lecture 16: The Agile Methodology.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
CPSC 872 John D. McGregor Session 13 Process. Specification and design problem solution specification implementation specification.
Chapter 4 & Chapter 5 Important Concepts
Requirements Engineering Lecture 4
John D. McGregor Process Module 1 Session 1
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
The Web Application Development Process Models
Software Life Cycle “What happens in the ‘life’ of software”
V-Shaped SDLC Model Lecture-6.
Software Process Models
Software Processes.
Prescriptive Process Models
Introduction to Software Engineering
Documentation in Continuous Delivery Model and DevOps
CPSC 372 John D. McGregor MSemat.
Tools and Techniques for Agile Project Management
Introduction to Software Process Models
CS 577b: Software Engineering II
Basic SDLC Models SDLC  System Development Life Cycle.
CSE 403, Software Engineering Lecture 2
CSC 354 – System Development Life Cycles & Processes, Fall 2013
Baisc Of Software Testing
SOFTWARE LIFE-CYCLES Beyond the Waterfall.
Strategy for development of new software
SDLC (Software Development Life Cycle)
Agile Development.
John D. McGregor Session 11 Adv Design Patterns
Systems Architecture and Engineering
Presentation transcript:

CPSC 875 John D. McGregor C23 - Architecture evolution/organization/safety analysis and product lines

Creating a metric Goal – manage the evolution of an architecture Question – How much has changed? How fast is it changing? Metric – velocity = ; acceleration =

Velocity/Aceleration of Evolution

Safety analysis Problem – what is static and what is dynamic? What is knowable when? IaaS,PaaS,SaaS

Self-organizing network What is fixed, what is constrained, what is dynamic?

Safety analysis and product lines Composition of error propagations

domain Engineering Mature Scientific Technology Emerging Business Exploratory

Development process style Agile Spiral Iterative Incremental Waterfall

Team structure Strict hierarchy Matrix Self-organizing team requirements coding architecture testing

ASM—Acquisition Strategy Meeting CDR—Critical Design Review CERR—Critical Events Readiness Review DR—Decommissioning Review FAD—Formulation Authorization Document FRR—Flight Readiness Review KDP—Key Decision Point LRR—Launch Readiness Review MRR—Mission Readiness Review ORR—Operational Readiness Review PCA—Program Commitment Agreement PDR—Preliminary Design Review PFAR—Post-Flight Assessment Review PIR—Program Implementation Review PLAR—Post-Launch Assessment Review SARSystem Acceptance Review SDR—System Definition Review SIR—System Integration Review SMSR—Safety and Mission Success Review SRB—Standing Review Board SRR—System Requirements Review

Single person Chief architect model Team model ----------------- Their emphasis Technical Business

Program manager Product manager Project manager Team manager Software architect

Here’s what you are going to do Assemble a package of everything. Write a summary about your project and the process of creating it. Use metrics to argue why your architecture is “good”. Submit everything by 11:59pm Monday , April 11th