Lessons from Integrating Functionalities Fred C. Martin WA Dept. Natural Resources Olympia, WA Open-FVS: Lessons from Integrating Functionalities into.

Slides:



Advertisements
Similar presentations
Object Oriented Analysis And Design-IT0207 iiI Semester
Advertisements

Business Development Suit Presented by Thomas Mathews.
System Development Life Cycle (SDLC)
DETAILED DESIGN, IMPLEMENTATIONA AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
© 2005 Prentice Hall6-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Algorithms and Problem Solving-1 Algorithms and Problem Solving.
Algorithms and Problem Solving. Learn about problem solving skills Explore the algorithmic approach for problem solving Learn about algorithm development.
Software Development Process. Process Improvement Using the Shewhart Cycle 1.PLAN - Plan a change aimed at improvement, collect data, and establish a.
1 Building with Assurance CSSE 490 Computer Security Mark Ardis, Rose-Hulman Institute May 10, 2004.
Software Engineering CSE470: Requirements Analysis 1 Requirements Analysis Defining the WHAT.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 2 Introduction to Database Development.
Introduction to Database Development. 2-2 Outline  Context for database development  Goals of database development  Phases of database development.
About the Presentations The presentations cover the objectives found in the opening of each chapter. All chapter objectives are listed in the beginning.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
Baker/McGreevy Day 1 How many beamlines have eqpmt not able to support present software? Certain experiments can’t be done now, but in future? What does.
Introduction to the Enterprise Library. Sounds familiar? Writing a component to encapsulate data access Building a component that allows you to log errors.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Home, school & community partnerships Leadership & co-ordination Strategies & targets Monitoring & assessment Classroom teaching strategies Professional.
Object Oriented Analysis and Design Introduction.
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
9 Chapter Nine Compiled Web Server Programs. 9 Chapter Objectives Learn about Common Gateway Interface (CGI) Create CGI programs that generate dynamic.
4/16/2004MSE Presentation II1 ESTMD System -- A Web-based EST Model Database System Yinghua Dong.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
________________________________________________________ Write Your Quality Story June 26, VanQ. Daniel Zrymiak Our Quality professionals have many.
Scalable Game Development William Roberts Senior Game Engineer
Cooperative FVS ! Functional Requirements for a Shared Library Version of FVS, or Calling FVS from R! Nicholas L. Crookston Rocky Mountain Research Station.
Approaching a Problem Where do we start? How do we proceed?
SIMO SIMulation and Optimization ”New generation forest planning system” Antti Mäkinen Dept. of Forest Resource Management / University of Helsinki.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Data Structures Using C++1 Chapter 1 Software Engineering Principles and C++ Classes.
Software Development Life Cycle by A.Surasit Samaisut Copyrights : All Rights Reserved.
MBTI and Decision Making: The Z Model (
SIMO SIMulation and Optimization ”New generation forest planning system” Antti Mäkinen & Jussi Rasinmäki Dept. of Forest Resource Management.
Effort.vs. Software Product “Quality” Effort Product “Quality” Which curve? - linear? - logarithmic? - exponential?
Oregon Department of Forestry Kevin Birch Planning Coordinator Use of Criteria & Indicators and Sustainable Forest Management at Different Scales Oregon.
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
1 1 ECHO Extended Services February 15, Agenda Review of Extended Services Policy and Governance ECHO’s Service Domain Model How to…
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
“Architecture” The outcome of top-level design, reflecting principal design decisions Can (and should) be modified and updated Analogous to architecture.
Chapter 1 Software Engineering Principles. Problem analysis Requirements elicitation Software specification High- and low-level design Implementation.
Software Quality Assurance and Testing Fazal Rehman Shamil.
EE694v - Verification - Lect Lect 12,13,14 – 762 Testbenches Lets look at the EE 762 testbenches Look at stimulus generation techniques Look at response.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Issues in Curriculum and Instruction. IDEA requirements IEP—often thought of as the curriculum for kids in sped 1997 – focus on strengths – Strong parent.
GEOSS Common Infrastructure (GCI) The GEOSS Common Infrastructure allows Earth Observations users to search, access and use the data, information, tools.
Dillon: CSE470: ANALYSIS1 Requirements l Specify functionality »model objects and resources »model behavior l Specify data interfaces »type, quantity,
ILO Public web site guided tour. WEBDEV Page 2 The way we were...  The ILO web presence is composed of about 150 different sites  On top of them there.
Portlet Development Konrad Rokicki (SAIC) Manav Kher (SemanticBits) Joshua Phillips (SemanticBits) Arch/VCDE F2F November 28, 2008.
Principles of Programming & Software Engineering
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Algorithms and Problem Solving
Integration Testing.
Review for Final, Fall 2010 Close book, Close notes
Systems Thinking Why is the whole less than the sum of its parts?
Streamlined publishing through the cloud with HTML5
IS442 Information Systems Engineering
Chapter 20 Object-Oriented Analysis and Design
Data Model.
Systems Engineering for Mission-Driven Modeling
Chapter 7 Software Engineering.
Algorithms and Problem Solving
Chapter 13: Construction
Shared Reading Four Blocks Literacy Framework.
Case Study 1 By : Shweta Agarwal Nikhil Walecha Amit Goyal
Chapter 11: Integration- and System Testing
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Lab 2: Information Retrieval
Presentation transcript:

Lessons from Integrating Functionalities Fred C. Martin WA Dept. Natural Resources Olympia, WA Open-FVS: Lessons from Integrating Functionalities into A Multi-Developer Framework

"The art of research [is] the art of making difficult problems soluble by devising means of getting at them." Sir Peter Medawar. Open participation structure - expand contributor base USFS Forest Mgmt. Service Center Universities Consultants Other Agencies Pros: larger community. Cons: larger community. Lessons from Integrating Functionalities

"With some glee and considerable professional acclaim, we seem to keep at least one jump ahead of the man- agers' comprehension of our methods." Albert R. Stage. Framework for potential additions & extensions Habitat classification Optimizer Climate changes interactions: pests, cover, etc. Alternative growth engines – Organon, Forest BGC, etc. Pros: API for extending functionality. Cons: loss of independence. Lessons from Integrating Functionalities

“To know what I think, I need to read what I've written.” Unknown. Documentation standards - consistency & availability Users manuals WIKIs Internal code documentation, spctrn.f SVN commit comments Suppose Outputs/results – reports, database, visualization, etc. Pros: central hosting. Cons: multiple points of reference, coordination effort. Lessons from Integrating Functionalities

“Give me a fruitful error any time, full of seeds, bursting with its own corrections. You can keep your sterile truths for yourself." Vilfredo Pareto. Testing – incorporate into building process Protects existing content Functionality testing, black box testing Internal testing, white box testing Test driven development – unit tests Pros: continuous quality assurance. Cons: can double development time. Lessons from Integrating Functionalities

"We do think in language, and so the quality of our thoughts and ideas can only be as good as the quality of our language." George Carlin. Programming standards & architecture – code consistency Procedural versus object oriented, spaghetti code Structure, style - camel notation, comments, linkages Variable & method naming Pros: guides design, common patterns, aids understanding. Cons: constrains progress. Lessons from Integrating Functionalities

"All science is the search for unity in hidden likenesses." J. Bronowski. Integration implications – logical behavior among entities Database connectivity - file versus database outputs Timing issues – simulation periods, end of period versus beginning of period Harvest in first period versus activities later in a cycle Start and stop operations and retrieval of state Pros: affirms expected interactions, extends solution space. Cons: constrains creativity. Lessons from Integrating Functionalities

"They didn't want it good, they wanted it Wednesday." Robert Heinlein. It’s a framework not a panacea – it ain’t easy & it takes time System is large Inherits limitations from the past Need to work as a team Longer learning curve Pros: contributes to larger good. Cons: higher tolerance level. Lessons from Integrating Functionalities

"Don't analyze constraints; we ignore them until we get caught, so just tell us how good it could be if we didn't have any." Local forest manager. ECON Extension integration – linkages between programs Keyword input Individual tree and log volumes Controlling harvest implementation via PRETEND Event Monitor actions Publish results Lessons from Integrating Functionalities

FVS Keyword Entry Initiate Trees Grow Trees Burn, Infect, Infest Publish Outcomes Harvest Trees Regeneration ECON Pass Keywords Get Tree/Log Volumes Get Harvests Get Events Value Harvest & Events Pass Results

Summarizing: "Entities should not be multiplied unnecessarily," "law of parsimony" or "law of succinctness." Franciscan friar William of Ockham. "Art is never finished, only abandoned." Leonardo da Vinci. "You cannot predict the future because it depends on how you react to it." George Soros. Lessons from Integrating Functionalities