Informatics 122 Alex Baker

Slides:



Advertisements
Similar presentations
INTRODUCTION TO SIMULATION WITH OMNET++ José Daniel García Sánchez ARCOS Group – University Carlos III of Madrid.
Advertisements

Technieken van de Software Architectuur, VUB ‘98-’99, Part 21 Part 2: Component and Framework Reuse Technieken van de Software Architectuur.
Applied IT Architecture Introduction Reference IT architecture & Standards Applied Reference Architecture Governance model Governance process Problems.
Search in Source Code Based on Identifying Popular Fragments Eduard Kuric and Mária Bieliková Faculty of Informatics and Information.
Optimizing single thread performance Dependence Loop transformations.
Software Architectural Design Software Components Instructor Dr. Lawrence Chung.
Main issues: • Why is reuse so difficult • How to realize reuse
(c) 2009 University of California, Irvine – André van der Hoek1April 20, 2015 – 00:59:05 Informatics 122 Software Design II Lecture 11 André van der Hoek.
Multi Card Problem Which card do I use when I am at a point of sale to maximize rewards? Choose Randomly ? Build & Solve a complex equation to choose the.
Applying Concepts of Software Reuse to the Implementation of Data Warehouse ETL Systems Jiayang Zhou November 2001.
Quotes from The Teaching Gap Stigler & Hiebert, 1999
May 2011 Milestone Materials Atmosphere-ocean design document Updated target interoperability table Adoption status table NUOPC Layer software prototype.
UML Static diagrams. Static View: UML Component Diagram Component diagrams show the organization and dependencies among software components. Component:
Where Do the 7 layers “fit”? Or, where is the dividing line between hdw & s/w? ? ?
© 2009 University of California, Irvine – André van der Hoek1June 13, 2015 – 18:19:12 Informatics 122 Software Design II Lecture 5 André van der Hoek &
Software Engineering. How many lines of code? Average CS1004 assignment: 200 lines Average CS4115 project: 5000 lines Corporate e-commerce project: 80,000.
© 2010 University of California, Irvine – André van der Hoek1June 14, 2015 – 15:24:35 Informatics 121 Software Design I Lecture 11 André van der Hoek &
Software Engineering.
My view of challenges faced by Open64 Xiaoming Li University of Delaware.
© 2010 University of California, Irvine – André van der Hoek1June 26, 2015 – 00:06:40 Informatics 122 Software Design II Lecture 6 André van der Hoek &
Testing Components in the Context of a System CMSC 737 Fall 2006 Sharath Srinivas.
The Re-engineering and Reuse of Software
CH07: Writing the Programs Does not teach you how to program, but point out some software engineering practices that you should should keep in mind as.
LAYING OUT THE FOUNDATIONS. OUTLINE Analyze the project from a technical point of view Analyze and choose the architecture for your application Decide.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Design.
CSE 303 – Software Design and Architecture
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Codeigniter is an open source web application. It occupies a very small amount of space in the memory and is most useful for developers who aim to develop.
SOFTWARE REUSABILITY AJAYINDER SINGH CSC What is Software Reuse Software reuse is the process of implementing or updating software systems using.
SE: CHAPTER 7 Writing The Program
Eurostat Expression language (EL) in Eurostat SDMX - TWG Luxembourg, 5 Jun 2013 Adam Wroński.
The “Joy of Automation” Barry Baker & Mo Shannon Test Automation Centre (TAC) BT.
Figure 5.1 Hardware development process and information usage. © 2003 Crnkovic, Asklund, Persson Dahlqvist, ”Implementing and Integrating Product Data.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
2D/3D Integration Challenges: Dynamic Reconfiguration and Design for Reuse.
Lab 5 CPIT 250 System Analysis and Design.
ICIST 2011 Mar , Nanjing, China Visualization in Software Architecture Helen Wu 1 Let’s Enforce a Simple Rule in Software Architecture Helen.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 15. Review Interaction-Oriented Software Architectures – MVC.
How to develop a program CSE 160 University of Washington 1.
Conception Scoping the project Investigating the work Determining the product Defining requirements How do we know when to move from one stage to the.
04 - OOD Intro.CSC4071 Software Design ‘Requirements’ defines –The goals the system needs to satisfy. ‘Specification’ defines –The externally-observable.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Nigel Baker UWE & CERN/EP-CMA Design Patterns for Integrating Product and Process Models The C.R.I.S.T.A.L. Project ( C ooperative R epositories & I nformation.
+ Informatics 122 Software Design II Lecture 13 Emily Navarro Duplication of course material for any commercial purpose without the explicit written permission.
By Ramesh Mannava.  Overview  Introduction  10 secure software engineering topics  Agile development with security development activities  Conclusion.
Detailing your features for your second client meeting What to put on your Google Group for them to review!
Chapter 7 Lecture 1 Design and Implementation. Design and implementation Software design and implementation is the stage in the software engineering process.
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
Off-Site SEO to Improve Your Website’s Page Rank Straight Up Marketing.
Washington, D.C., U.S.A May Some concepts of systems architectures Industrialization of statistics and software architecture Study cases.
Introduction to Android Programming. Features of Android.
How to develop a program
Software Configuration Management
Environment Assessment
Introduction Software is becoming very expensive:
Informatics 122 Software Design II
Informatics 121 Software Design I
Design Tips.
How to develop a program
Informatics 121 Software Design I
1 To go to the next slide, click this button instead. A random slide will come up.
Authors: Barry Smyth, Mark T. Keane, Padraig Cunningham
PRICING YOUR SERVICE.
Informatics 122 Software Design II
Digital Designs – What does it take
FRAMEWORKS AND REUSE What is “Framework”?
Informatics 122 Alex Baker
(Software) reuse, is the use of (Software) knowledge, to build new (something) software.
Presentation transcript:

Informatics 122 Alex Baker Components Recap Informatics 122 Alex Baker

Was this difficult? 1 . 10

Using components Someone hands you this component Use it instead of building the functionality?

Using components Someone hands you this component Use it instead of building the functionality? Was it worth the trouble of finding it?

Using components Someone hands you this component Use it instead of building the functionality? Was it worth the trouble of finding it? What if you could use a random component among those you looked at?

What made a component useful?

What made a component useful? Fitness of concept Effectiveness Features Clear code Flexible execution Documentation A clear initial description

What made a component useful? Did any components require architectural changes?

What made a component useful? Did you rank a less fitting component higher because of understandability?

Designing for reuse