Skip to main content
summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'plugins/org.eclipse.osee.support.admin/eclipseCon/2008')
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt.svn-base116
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/The_Cure_for_Your_Disconnected_Toolset_Headache.txt.svn-base108
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/presentation_planning.txt.svn-base162
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt116
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/The_Cure_for_Your_Disconnected_Toolset_Headache.txt108
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/presentation_planning.txt162
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/.svn/text-base/OSEE - An Integrated Solution.txt.svn-base16
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/OSEE - An Integrated Solution.txt16
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/.svn/text-base/agenda.txt.svn-base38
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/agenda.txt38
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/.svn/text-base/Top 10 deployment secrets they don't want you to know.txt.svn-base80
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/Top 10 deployment secrets they don't want you to know.txt80
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/API Design Workshop.txt.svn-base10
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/Practical testing of Eclipse plugins and OSGi bundles.txt.svn-base10
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/API Design Workshop.txt10
-rw-r--r--plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/Practical testing of Eclipse plugins and OSGi bundles.txt10
16 files changed, 540 insertions, 540 deletions
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt.svn-base
index c2c5397f24..b50199f597 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt.svn-base
@@ -1,58 +1,58 @@
-Authors/Presenters: Ryan and Don
-Category: Industry Vertical
-Name: Going Vertical: An Experience from the Aerospace Industry
-
-Abstract:
-
-If you are interested in collaborating on the current effort to apply the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) to Aerospace and Automotive industries or in learning how OSEE might be applied to your industry, then this talk is for you.
-
-Industries that build complex, mission-critical systems typically work with many suppliers in order to create a single integrated product. These products often have long development lifecycles and have stringent requirements for verification, traceability, and document deliverables. In order to effectively manage this complexity, these industries are required to assemble a wide array of tools that provide only piecemeal capabilities. Often, the resulting toolset provides disconnected access to partially redundant data and may carry with it multi-million dollar software licensing, customization, and maintenance costs.
-
-OSEE is being developed to provide an integrated solution to these challenges. At the heart of OSEE is an Application Framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to all OSEE applications. Two such applications, that are widely applicable, have already been created: a powerful requirements and document management solution, OSEE Define, and a full featured change management system, OSEE ATS.
-
-The OSEE Eclipse project provides tremendous opportunities to collaborate on industry wide solutions and build upon lessons already learned.
-
-
---
-
-A significant source of waste when developing complex systems is handing off work between separate functional disciplines and the associated knowledge loss. Someone who knows this first hand is Jonathan Ive, head of design at Apple, who stated that "The historical way of developing products just doesn't work when you're as ambitious as we are. When the challenges are that complex, you have to develop a product in a more collaborative, integrated way." Engineering a product in a more collaborative and integrated way requires an engineering environment that is itself tightly integrated.
-
-
-A solution that is developed by all the players in the vertical enables each competitor to become more attractive in the corresponding market. A smaller cost of collaboration in an open source solution yields a long term gain for all involved. This is in contrary to the proprietary competitors whose main focus is on hording the specific functionality that all need to succeed. As Mike Mil?? stated, "We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform."
-
-Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is designed to maintain the extensibility of the Eclipse platform and give the added benefit of sharing data between the applications built upon.
-
---
-
-Intended audience: Engineers in industry verticals that are looking for a platform to provide their solution. We hope to let these people see that OSEE can be that platform.
-
-Ideas:
- - OSEE scales from simple application development to complex mission-critical software and systems engineering
- - delivery of tool and DB, not documents
- - get US Government on board and everyone's using OSEE
- - collaboration can provide for easier plug-in-play software between companies; eg: Rockwell could sell their ARC-210 radio requirements, code, test to Boeing
- - collaboration between competitors happens anyway, why not make it direct
- - indirect collaboration happens when a company provides a solution to requirements Mgmt, they then sell to Boeing who asks for enhancements and customization, company makes improvements which they then sell to the next customer
-
-_________________________________________________________________________________
-
-Industry Vertical presentations:
-The industry vertical track is looking for short talks and panel submissions related to the use of Eclipse technology within specific industry verticals such as Automotive, Healthcare or Finance. Topics can be either of a technical or business nature and could cover emerging domain specific platforms or other solutions for the vertical.
-
-
-2007 Industry Vertical Talks
----
-
-Eclipse and Industry Verticals: The healthcare experience:
-Within Eclipse there is growing interest in vertical industry projects. Currently the only full vertical industry Eclipse project is the Open Healthcare Framework (OHF), which intends to provide extensible frameworks, tools and run-time components based on a coherent secure Eclipse based architecture. OHF - and other industry verticals - a somewhat different from other eclipse projects. This presentation will review the history and current status of the OHF project. OHF's various deliverables and interests will be reviewed, and the relationship between OHF and the general Eclipse community and roadmap will be considered. In addition, the presentation will consider the requirements for a successful industry vertical, including the kind of relationships that are needed in the industry, and the relationships that will be needed within eclipse when more than one vertical industry project exists.
-
-Building the next generation weather platform in Eclipse
-In 2005, NOAA contracted Raytheon to develop the National Weather Service's next generation platform for Advanced Weather Information Processing System (AWIPS). AWIPS is currently deployed at 122 forecast offices nation-wide, in addition to many national labs and centers. It is the primary tool for National Weather Service forecasters. Instead of the typical contractor closed-source and proprietary approach, we are developing the system using completely open-source and free technologies. At the foundation of the weather workstation is the Eclipse Rich Client Platform, which will allow far more flexibility and extendability than the existing UNIX-platform dependent system.
-
-The CAVE (Common AWIPS Visualization Environment) will bring together a variety of disparate user interfaces into a common environment. A technology demo of the system will be given showing:
-
- * CAVE's OpenGL-based rendering system
- * Core capabilities such as GIS visualization, collaboration and editing
- * A quick look at the Eclipse extension points developed to build the platform
-
-Prerequisites: A general understanding of Eclipse RCP
+Authors/Presenters: Ryan and Don
+Category: Industry Vertical
+Name: Going Vertical: An Experience from the Aerospace Industry
+
+Abstract:
+
+If you are interested in collaborating on the current effort to apply the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) to Aerospace and Automotive industries or in learning how OSEE might be applied to your industry, then this talk is for you.
+
+Industries that build complex, mission-critical systems typically work with many suppliers in order to create a single integrated product. These products often have long development lifecycles and have stringent requirements for verification, traceability, and document deliverables. In order to effectively manage this complexity, these industries are required to assemble a wide array of tools that provide only piecemeal capabilities. Often, the resulting toolset provides disconnected access to partially redundant data and may carry with it multi-million dollar software licensing, customization, and maintenance costs.
+
+OSEE is being developed to provide an integrated solution to these challenges. At the heart of OSEE is an Application Framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to all OSEE applications. Two such applications, that are widely applicable, have already been created: a powerful requirements and document management solution, OSEE Define, and a full featured change management system, OSEE ATS.
+
+The OSEE Eclipse project provides tremendous opportunities to collaborate on industry wide solutions and build upon lessons already learned.
+
+
+--
+
+A significant source of waste when developing complex systems is handing off work between separate functional disciplines and the associated knowledge loss. Someone who knows this first hand is Jonathan Ive, head of design at Apple, who stated that "The historical way of developing products just doesn't work when you're as ambitious as we are. When the challenges are that complex, you have to develop a product in a more collaborative, integrated way." Engineering a product in a more collaborative and integrated way requires an engineering environment that is itself tightly integrated.
+
+
+A solution that is developed by all the players in the vertical enables each competitor to become more attractive in the corresponding market. A smaller cost of collaboration in an open source solution yields a long term gain for all involved. This is in contrary to the proprietary competitors whose main focus is on hording the specific functionality that all need to succeed. As Mike Mil?? stated, "We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform."
+
+Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is designed to maintain the extensibility of the Eclipse platform and give the added benefit of sharing data between the applications built upon.
+
+--
+
+Intended audience: Engineers in industry verticals that are looking for a platform to provide their solution. We hope to let these people see that OSEE can be that platform.
+
+Ideas:
+ - OSEE scales from simple application development to complex mission-critical software and systems engineering
+ - delivery of tool and DB, not documents
+ - get US Government on board and everyone's using OSEE
+ - collaboration can provide for easier plug-in-play software between companies; eg: Rockwell could sell their ARC-210 radio requirements, code, test to Boeing
+ - collaboration between competitors happens anyway, why not make it direct
+ - indirect collaboration happens when a company provides a solution to requirements Mgmt, they then sell to Boeing who asks for enhancements and customization, company makes improvements which they then sell to the next customer
+
+_________________________________________________________________________________
+
+Industry Vertical presentations:
+The industry vertical track is looking for short talks and panel submissions related to the use of Eclipse technology within specific industry verticals such as Automotive, Healthcare or Finance. Topics can be either of a technical or business nature and could cover emerging domain specific platforms or other solutions for the vertical.
+
+
+2007 Industry Vertical Talks
+---
+
+Eclipse and Industry Verticals: The healthcare experience:
+Within Eclipse there is growing interest in vertical industry projects. Currently the only full vertical industry Eclipse project is the Open Healthcare Framework (OHF), which intends to provide extensible frameworks, tools and run-time components based on a coherent secure Eclipse based architecture. OHF - and other industry verticals - a somewhat different from other eclipse projects. This presentation will review the history and current status of the OHF project. OHF's various deliverables and interests will be reviewed, and the relationship between OHF and the general Eclipse community and roadmap will be considered. In addition, the presentation will consider the requirements for a successful industry vertical, including the kind of relationships that are needed in the industry, and the relationships that will be needed within eclipse when more than one vertical industry project exists.
+
+Building the next generation weather platform in Eclipse
+In 2005, NOAA contracted Raytheon to develop the National Weather Service's next generation platform for Advanced Weather Information Processing System (AWIPS). AWIPS is currently deployed at 122 forecast offices nation-wide, in addition to many national labs and centers. It is the primary tool for National Weather Service forecasters. Instead of the typical contractor closed-source and proprietary approach, we are developing the system using completely open-source and free technologies. At the foundation of the weather workstation is the Eclipse Rich Client Platform, which will allow far more flexibility and extendability than the existing UNIX-platform dependent system.
+
+The CAVE (Common AWIPS Visualization Environment) will bring together a variety of disparate user interfaces into a common environment. A technology demo of the system will be given showing:
+
+ * CAVE's OpenGL-based rendering system
+ * Core capabilities such as GIS visualization, collaboration and editing
+ * A quick look at the Eclipse extension points developed to build the platform
+
+Prerequisites: A general understanding of Eclipse RCP
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/The_Cure_for_Your_Disconnected_Toolset_Headache.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/The_Cure_for_Your_Disconnected_Toolset_Headache.txt.svn-base
index 9c534a3f2c..47766dafa0 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/The_Cure_for_Your_Disconnected_Toolset_Headache.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/The_Cure_for_Your_Disconnected_Toolset_Headache.txt.svn-base
@@ -1,54 +1,54 @@
-Authors/Presenters: Ryan, Don and Jeff
-Name: The Cure for Your Disconnected Toolset Headache
-Abstract:
-
-If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. Many organizations loosely integrate tools using point-to-point data synchronization. This is costly to create, impedes the flow of information through the development lifecycle and is difficult to maintain. Applying a data-centric approach yields a more tightly integrated toolset.
-
-The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) builds upon this by providing a common mechanism for the integration of applications at the data level. At the core of OSEE is an application framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
-
-This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS), a full featured change management system, and Define, a powerful requirements and document management solution. While these applications are already available in OSEE, new applications can be developed to share the same data model.
-
---
-
-If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and Open System Engineering Environment (OSEE) provides a common mechanism for the integration of applications at the data level. Many organizations loosely integrate tools using point-to-point data synchronization and this impedes the flow of information through the development lifecycle. Where as, applying a data-centric approach yields a much more tightly integrated toolset. Architected around this insight, the OSEE Application Framework provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
-
-OSEE is an open source project under the Eclipse Technology Project being developed by Boeing and other large system integrators in both the avionics and automotive industries. This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS) and Define which is a requirements and process management solution.
-
-
--- Details
-
-Each program or business that develops systems and software is currently required to assemble a wide array of software products to provide piecemeal capabilities necessary for completing different stages of the engineering lifecycle. Once installed, the daunting task of configuring and gluing them together begins. After years of effort, the program may have a toolset that is adequate for its current needs, but is ill-suited for growth and is far from optimized. In addition, the resulting tools are disconnected, sporadically maintained, and use an overwhelming array of disjointed user interfaces to access partially redundant data. Additionally, in the case of large programs or document-demanding customers like the US Government, such a toolset can often carry with it multi-million dollar software licensing, customization, configuration, and maintenance costs.
-
-Eclipse has solved half of this problem by presented the capability to purchase and develop a set of tools that can be plugged in to a common framework. This framwork gives many common services to both the developer and the end user. It is now easier than ever to "integrate" a set of tools. But, if the desire is true integration that provides cost savings, the problem of the data must be addressed.
-
-Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is being developed with a strong focus on the data. At the core of OSEE is an Application Framework that includes a powerful version controlled, object database that enables applications to persist their data in a simple model of only three main objects: Artifacts, Attributes and Relations. This enables applications to share not only the user interface, but the data. Software design created in a modeling application can be stored and related directly to the system and subsystem requirements which are stored and related to the source code that implements it and the test cases that verify it.
-
---
-Audience
- Tool developers, Tech-leads and project managers or anyone who uses to large tools suites
-
-
-Thoughts to be considered:
-Delivery of open source DB and OSEE to customer instead of documents
-OSEE provides to data what Eclipse provides to UI
-
-- History of Apache program at Boeing
-- Reasearch into DBs
-- Tight integration / vs loose
-- Delivery of open source DB and OSEE to customer instead of documents
-- Simplicity of Data (Artifact, Relation, Attribute, Branch)
-- Dynamic object db versus static relational
-- Version controlled
-- Configuration Managed
-- Generic Editors / Viewers (cause generic data model)
-- Extensible enought to create Specific editors /viewers (ATS)
-- Eclipse based
-- OSEE is open source - collaboration (Universities / etc)
-- Scalability - Small to Enterprise use
-- Demo
- - Architecture diagram
- - ATS Workflow
- - Skywalker
- - Artifact Editor
- - ATS Editor
- - Artifact Explorer
+Authors/Presenters: Ryan, Don and Jeff
+Name: The Cure for Your Disconnected Toolset Headache
+Abstract:
+
+If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. Many organizations loosely integrate tools using point-to-point data synchronization. This is costly to create, impedes the flow of information through the development lifecycle and is difficult to maintain. Applying a data-centric approach yields a more tightly integrated toolset.
+
+The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) builds upon this by providing a common mechanism for the integration of applications at the data level. At the core of OSEE is an application framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
+
+This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS), a full featured change management system, and Define, a powerful requirements and document management solution. While these applications are already available in OSEE, new applications can be developed to share the same data model.
+
+--
+
+If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and Open System Engineering Environment (OSEE) provides a common mechanism for the integration of applications at the data level. Many organizations loosely integrate tools using point-to-point data synchronization and this impedes the flow of information through the development lifecycle. Where as, applying a data-centric approach yields a much more tightly integrated toolset. Architected around this insight, the OSEE Application Framework provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
+
+OSEE is an open source project under the Eclipse Technology Project being developed by Boeing and other large system integrators in both the avionics and automotive industries. This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS) and Define which is a requirements and process management solution.
+
+
+-- Details
+
+Each program or business that develops systems and software is currently required to assemble a wide array of software products to provide piecemeal capabilities necessary for completing different stages of the engineering lifecycle. Once installed, the daunting task of configuring and gluing them together begins. After years of effort, the program may have a toolset that is adequate for its current needs, but is ill-suited for growth and is far from optimized. In addition, the resulting tools are disconnected, sporadically maintained, and use an overwhelming array of disjointed user interfaces to access partially redundant data. Additionally, in the case of large programs or document-demanding customers like the US Government, such a toolset can often carry with it multi-million dollar software licensing, customization, configuration, and maintenance costs.
+
+Eclipse has solved half of this problem by presented the capability to purchase and develop a set of tools that can be plugged in to a common framework. This framwork gives many common services to both the developer and the end user. It is now easier than ever to "integrate" a set of tools. But, if the desire is true integration that provides cost savings, the problem of the data must be addressed.
+
+Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is being developed with a strong focus on the data. At the core of OSEE is an Application Framework that includes a powerful version controlled, object database that enables applications to persist their data in a simple model of only three main objects: Artifacts, Attributes and Relations. This enables applications to share not only the user interface, but the data. Software design created in a modeling application can be stored and related directly to the system and subsystem requirements which are stored and related to the source code that implements it and the test cases that verify it.
+
+--
+Audience
+ Tool developers, Tech-leads and project managers or anyone who uses to large tools suites
+
+
+Thoughts to be considered:
+Delivery of open source DB and OSEE to customer instead of documents
+OSEE provides to data what Eclipse provides to UI
+
+- History of Apache program at Boeing
+- Reasearch into DBs
+- Tight integration / vs loose
+- Delivery of open source DB and OSEE to customer instead of documents
+- Simplicity of Data (Artifact, Relation, Attribute, Branch)
+- Dynamic object db versus static relational
+- Version controlled
+- Configuration Managed
+- Generic Editors / Viewers (cause generic data model)
+- Extensible enought to create Specific editors /viewers (ATS)
+- Eclipse based
+- OSEE is open source - collaboration (Universities / etc)
+- Scalability - Small to Enterprise use
+- Demo
+ - Architecture diagram
+ - ATS Workflow
+ - Skywalker
+ - Artifact Editor
+ - ATS Editor
+ - Artifact Explorer
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/presentation_planning.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/presentation_planning.txt.svn-base
index 987f5612d6..7e4b6c3521 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/presentation_planning.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/.svn/text-base/presentation_planning.txt.svn-base
@@ -1,81 +1,81 @@
-See ../EclipseCon 2008.txt for more information
-
-jeff.c.phillips@boeing.com
-donald.g.dunne@boeing.com
-andrew.m.finkbeiner@boeing.com
-<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a>
-
-422 submittions
-
-"Long Talk" is 50 minutes
-"Short Talk" is 10 minutes
-
-competitors, as Mike noted:
-
- You need to step out of your comfort zone as to what Eclipse is. It's no longer just about development tools. Eclipse now houses a wide range of "runtime" projects like application frameworks (service-oriented architecture (SOA) frameworks, etc.) or things one would expect to find in a Java application server.
-
- We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform.
-
- Importantly, we're not just talking about enterprise software. In fact, Eclipse is now the standard for C/C++ development in the embedded/mobile market (the only real-time operating system company that hasn't standardized on Eclipse is Green Hills). So, in the mobile/embedded space we have Symbian, QNX, Wind River, Nokia, and others working together on common platforms, then aggressively competing on the products they build on top of these platforms.
-
-Submission Guidelines http://wiki.eclipse.org/EclipseCon_Submission_Guidelines
-Selection Guidelines http://wiki.eclipse.org/EclipseCon_Selection_Guidelines
-Talk Types http://www.eclipsecon.org/2008/?page=submissions/submissionspage2
-Category of Presentation http://www.eclipsecon.org/2008/?page=submissions/submissionspage3
-
-Engineering Environment [Industry Vertical]
-"Long Talk" - Don and Ryan
- integrated, open source
- saves millions on license fees
- unlike many proprietary competitors
-
-The Intrapreneural Spirit [Business]
-"Long Talk" - Don and Ryan
- how to get an open source project through a large corporation
- work with Eclipse foundation to find partners (GM)
- Earned value
- The education of an acedential C.E.O.
- integration around the data
- lean - deep integration
-
-Open System Engineering Environment: An Integrated Solution [Emerging Technologies]
-"Short Talk" - Jeff and Andy
- share BLAMs operations,
- GUI is auto-generated
- construct workflow from discovered operations
- put data from web and store in artifacts
-
-The Cure for Your Disconnected Toolset Headache [Tools]
-"Long Talk" - Don and Jeff
- eliminate redundant data entry
- Change Management
- OSEE Application Framework including Object-Oriented Persistence Layer
-
-Take Courage and Arm Yourself With The Right Tooling To Embrace Change [Tools]
-"Long Talk" - Jeff and Ryan
- scales from small project to enterprise level
- navigate traceability using skywalker (graphical aid in understanding the architecture)
- pre-configured database (our demo database)
- advanced searching
- import
- how to customize and extend (that opens their minds to possibilities)
- data versus document delivery (give the customer the tool with the data)
- Publishing
-
- individual requirement artifacts with fine grained (version, tracability)
- mention eclipse open source
- way to interact with audience
-
- Connectivity
-
-
-Top 10 Deployment Secrets They Don't Want You To Know [Other]
-"Long Talk" - Don and Andy
- supporting large number of users
- User experience and usability (HCI)
- lesson about non-sw developers using an eclipse based product
- general purpose is more complicated for the user than a limited scope tool
- Escape from processes
- (build workflow into the tool)
- how do you encourage adoption of new tool
- don't deploy and then leave for EclipseCon
+See ../EclipseCon 2008.txt for more information
+
+jeff.c.phillips@boeing.com
+donald.g.dunne@boeing.com
+andrew.m.finkbeiner@boeing.com
+<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a>
+
+422 submittions
+
+"Long Talk" is 50 minutes
+"Short Talk" is 10 minutes
+
+competitors, as Mike noted:
+
+ You need to step out of your comfort zone as to what Eclipse is. It's no longer just about development tools. Eclipse now houses a wide range of "runtime" projects like application frameworks (service-oriented architecture (SOA) frameworks, etc.) or things one would expect to find in a Java application server.
+
+ We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform.
+
+ Importantly, we're not just talking about enterprise software. In fact, Eclipse is now the standard for C/C++ development in the embedded/mobile market (the only real-time operating system company that hasn't standardized on Eclipse is Green Hills). So, in the mobile/embedded space we have Symbian, QNX, Wind River, Nokia, and others working together on common platforms, then aggressively competing on the products they build on top of these platforms.
+
+Submission Guidelines http://wiki.eclipse.org/EclipseCon_Submission_Guidelines
+Selection Guidelines http://wiki.eclipse.org/EclipseCon_Selection_Guidelines
+Talk Types http://www.eclipsecon.org/2008/?page=submissions/submissionspage2
+Category of Presentation http://www.eclipsecon.org/2008/?page=submissions/submissionspage3
+
+Engineering Environment [Industry Vertical]
+"Long Talk" - Don and Ryan
+ integrated, open source
+ saves millions on license fees
+ unlike many proprietary competitors
+
+The Intrapreneural Spirit [Business]
+"Long Talk" - Don and Ryan
+ how to get an open source project through a large corporation
+ work with Eclipse foundation to find partners (GM)
+ Earned value
+ The education of an acedential C.E.O.
+ integration around the data
+ lean - deep integration
+
+Open System Engineering Environment: An Integrated Solution [Emerging Technologies]
+"Short Talk" - Jeff and Andy
+ share BLAMs operations,
+ GUI is auto-generated
+ construct workflow from discovered operations
+ put data from web and store in artifacts
+
+The Cure for Your Disconnected Toolset Headache [Tools]
+"Long Talk" - Don and Jeff
+ eliminate redundant data entry
+ Change Management
+ OSEE Application Framework including Object-Oriented Persistence Layer
+
+Take Courage and Arm Yourself With The Right Tooling To Embrace Change [Tools]
+"Long Talk" - Jeff and Ryan
+ scales from small project to enterprise level
+ navigate traceability using skywalker (graphical aid in understanding the architecture)
+ pre-configured database (our demo database)
+ advanced searching
+ import
+ how to customize and extend (that opens their minds to possibilities)
+ data versus document delivery (give the customer the tool with the data)
+ Publishing
+
+ individual requirement artifacts with fine grained (version, tracability)
+ mention eclipse open source
+ way to interact with audience
+
+ Connectivity
+
+
+Top 10 Deployment Secrets They Don't Want You To Know [Other]
+"Long Talk" - Don and Andy
+ supporting large number of users
+ User experience and usability (HCI)
+ lesson about non-sw developers using an eclipse based product
+ general purpose is more complicated for the user than a limited scope tool
+ Escape from processes
+ (build workflow into the tool)
+ how do you encourage adoption of new tool
+ don't deploy and then leave for EclipseCon
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt
index c2c5397f24..b50199f597 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/Going_Vertical_An_Experience_from_the_Aerospace_Industry.txt
@@ -1,58 +1,58 @@
-Authors/Presenters: Ryan and Don
-Category: Industry Vertical
-Name: Going Vertical: An Experience from the Aerospace Industry
-
-Abstract:
-
-If you are interested in collaborating on the current effort to apply the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) to Aerospace and Automotive industries or in learning how OSEE might be applied to your industry, then this talk is for you.
-
-Industries that build complex, mission-critical systems typically work with many suppliers in order to create a single integrated product. These products often have long development lifecycles and have stringent requirements for verification, traceability, and document deliverables. In order to effectively manage this complexity, these industries are required to assemble a wide array of tools that provide only piecemeal capabilities. Often, the resulting toolset provides disconnected access to partially redundant data and may carry with it multi-million dollar software licensing, customization, and maintenance costs.
-
-OSEE is being developed to provide an integrated solution to these challenges. At the heart of OSEE is an Application Framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to all OSEE applications. Two such applications, that are widely applicable, have already been created: a powerful requirements and document management solution, OSEE Define, and a full featured change management system, OSEE ATS.
-
-The OSEE Eclipse project provides tremendous opportunities to collaborate on industry wide solutions and build upon lessons already learned.
-
-
---
-
-A significant source of waste when developing complex systems is handing off work between separate functional disciplines and the associated knowledge loss. Someone who knows this first hand is Jonathan Ive, head of design at Apple, who stated that "The historical way of developing products just doesn't work when you're as ambitious as we are. When the challenges are that complex, you have to develop a product in a more collaborative, integrated way." Engineering a product in a more collaborative and integrated way requires an engineering environment that is itself tightly integrated.
-
-
-A solution that is developed by all the players in the vertical enables each competitor to become more attractive in the corresponding market. A smaller cost of collaboration in an open source solution yields a long term gain for all involved. This is in contrary to the proprietary competitors whose main focus is on hording the specific functionality that all need to succeed. As Mike Mil?? stated, "We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform."
-
-Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is designed to maintain the extensibility of the Eclipse platform and give the added benefit of sharing data between the applications built upon.
-
---
-
-Intended audience: Engineers in industry verticals that are looking for a platform to provide their solution. We hope to let these people see that OSEE can be that platform.
-
-Ideas:
- - OSEE scales from simple application development to complex mission-critical software and systems engineering
- - delivery of tool and DB, not documents
- - get US Government on board and everyone's using OSEE
- - collaboration can provide for easier plug-in-play software between companies; eg: Rockwell could sell their ARC-210 radio requirements, code, test to Boeing
- - collaboration between competitors happens anyway, why not make it direct
- - indirect collaboration happens when a company provides a solution to requirements Mgmt, they then sell to Boeing who asks for enhancements and customization, company makes improvements which they then sell to the next customer
-
-_________________________________________________________________________________
-
-Industry Vertical presentations:
-The industry vertical track is looking for short talks and panel submissions related to the use of Eclipse technology within specific industry verticals such as Automotive, Healthcare or Finance. Topics can be either of a technical or business nature and could cover emerging domain specific platforms or other solutions for the vertical.
-
-
-2007 Industry Vertical Talks
----
-
-Eclipse and Industry Verticals: The healthcare experience:
-Within Eclipse there is growing interest in vertical industry projects. Currently the only full vertical industry Eclipse project is the Open Healthcare Framework (OHF), which intends to provide extensible frameworks, tools and run-time components based on a coherent secure Eclipse based architecture. OHF - and other industry verticals - a somewhat different from other eclipse projects. This presentation will review the history and current status of the OHF project. OHF's various deliverables and interests will be reviewed, and the relationship between OHF and the general Eclipse community and roadmap will be considered. In addition, the presentation will consider the requirements for a successful industry vertical, including the kind of relationships that are needed in the industry, and the relationships that will be needed within eclipse when more than one vertical industry project exists.
-
-Building the next generation weather platform in Eclipse
-In 2005, NOAA contracted Raytheon to develop the National Weather Service's next generation platform for Advanced Weather Information Processing System (AWIPS). AWIPS is currently deployed at 122 forecast offices nation-wide, in addition to many national labs and centers. It is the primary tool for National Weather Service forecasters. Instead of the typical contractor closed-source and proprietary approach, we are developing the system using completely open-source and free technologies. At the foundation of the weather workstation is the Eclipse Rich Client Platform, which will allow far more flexibility and extendability than the existing UNIX-platform dependent system.
-
-The CAVE (Common AWIPS Visualization Environment) will bring together a variety of disparate user interfaces into a common environment. A technology demo of the system will be given showing:
-
- * CAVE's OpenGL-based rendering system
- * Core capabilities such as GIS visualization, collaboration and editing
- * A quick look at the Eclipse extension points developed to build the platform
-
-Prerequisites: A general understanding of Eclipse RCP
+Authors/Presenters: Ryan and Don
+Category: Industry Vertical
+Name: Going Vertical: An Experience from the Aerospace Industry
+
+Abstract:
+
+If you are interested in collaborating on the current effort to apply the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) to Aerospace and Automotive industries or in learning how OSEE might be applied to your industry, then this talk is for you.
+
+Industries that build complex, mission-critical systems typically work with many suppliers in order to create a single integrated product. These products often have long development lifecycles and have stringent requirements for verification, traceability, and document deliverables. In order to effectively manage this complexity, these industries are required to assemble a wide array of tools that provide only piecemeal capabilities. Often, the resulting toolset provides disconnected access to partially redundant data and may carry with it multi-million dollar software licensing, customization, and maintenance costs.
+
+OSEE is being developed to provide an integrated solution to these challenges. At the heart of OSEE is an Application Framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to all OSEE applications. Two such applications, that are widely applicable, have already been created: a powerful requirements and document management solution, OSEE Define, and a full featured change management system, OSEE ATS.
+
+The OSEE Eclipse project provides tremendous opportunities to collaborate on industry wide solutions and build upon lessons already learned.
+
+
+--
+
+A significant source of waste when developing complex systems is handing off work between separate functional disciplines and the associated knowledge loss. Someone who knows this first hand is Jonathan Ive, head of design at Apple, who stated that "The historical way of developing products just doesn't work when you're as ambitious as we are. When the challenges are that complex, you have to develop a product in a more collaborative, integrated way." Engineering a product in a more collaborative and integrated way requires an engineering environment that is itself tightly integrated.
+
+
+A solution that is developed by all the players in the vertical enables each competitor to become more attractive in the corresponding market. A smaller cost of collaboration in an open source solution yields a long term gain for all involved. This is in contrary to the proprietary competitors whose main focus is on hording the specific functionality that all need to succeed. As Mike Mil?? stated, "We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform."
+
+Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is designed to maintain the extensibility of the Eclipse platform and give the added benefit of sharing data between the applications built upon.
+
+--
+
+Intended audience: Engineers in industry verticals that are looking for a platform to provide their solution. We hope to let these people see that OSEE can be that platform.
+
+Ideas:
+ - OSEE scales from simple application development to complex mission-critical software and systems engineering
+ - delivery of tool and DB, not documents
+ - get US Government on board and everyone's using OSEE
+ - collaboration can provide for easier plug-in-play software between companies; eg: Rockwell could sell their ARC-210 radio requirements, code, test to Boeing
+ - collaboration between competitors happens anyway, why not make it direct
+ - indirect collaboration happens when a company provides a solution to requirements Mgmt, they then sell to Boeing who asks for enhancements and customization, company makes improvements which they then sell to the next customer
+
+_________________________________________________________________________________
+
+Industry Vertical presentations:
+The industry vertical track is looking for short talks and panel submissions related to the use of Eclipse technology within specific industry verticals such as Automotive, Healthcare or Finance. Topics can be either of a technical or business nature and could cover emerging domain specific platforms or other solutions for the vertical.
+
+
+2007 Industry Vertical Talks
+---
+
+Eclipse and Industry Verticals: The healthcare experience:
+Within Eclipse there is growing interest in vertical industry projects. Currently the only full vertical industry Eclipse project is the Open Healthcare Framework (OHF), which intends to provide extensible frameworks, tools and run-time components based on a coherent secure Eclipse based architecture. OHF - and other industry verticals - a somewhat different from other eclipse projects. This presentation will review the history and current status of the OHF project. OHF's various deliverables and interests will be reviewed, and the relationship between OHF and the general Eclipse community and roadmap will be considered. In addition, the presentation will consider the requirements for a successful industry vertical, including the kind of relationships that are needed in the industry, and the relationships that will be needed within eclipse when more than one vertical industry project exists.
+
+Building the next generation weather platform in Eclipse
+In 2005, NOAA contracted Raytheon to develop the National Weather Service's next generation platform for Advanced Weather Information Processing System (AWIPS). AWIPS is currently deployed at 122 forecast offices nation-wide, in addition to many national labs and centers. It is the primary tool for National Weather Service forecasters. Instead of the typical contractor closed-source and proprietary approach, we are developing the system using completely open-source and free technologies. At the foundation of the weather workstation is the Eclipse Rich Client Platform, which will allow far more flexibility and extendability than the existing UNIX-platform dependent system.
+
+The CAVE (Common AWIPS Visualization Environment) will bring together a variety of disparate user interfaces into a common environment. A technology demo of the system will be given showing:
+
+ * CAVE's OpenGL-based rendering system
+ * Core capabilities such as GIS visualization, collaboration and editing
+ * A quick look at the Eclipse extension points developed to build the platform
+
+Prerequisites: A general understanding of Eclipse RCP
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/The_Cure_for_Your_Disconnected_Toolset_Headache.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/The_Cure_for_Your_Disconnected_Toolset_Headache.txt
index 9c534a3f2c..47766dafa0 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/The_Cure_for_Your_Disconnected_Toolset_Headache.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/The_Cure_for_Your_Disconnected_Toolset_Headache.txt
@@ -1,54 +1,54 @@
-Authors/Presenters: Ryan, Don and Jeff
-Name: The Cure for Your Disconnected Toolset Headache
-Abstract:
-
-If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. Many organizations loosely integrate tools using point-to-point data synchronization. This is costly to create, impedes the flow of information through the development lifecycle and is difficult to maintain. Applying a data-centric approach yields a more tightly integrated toolset.
-
-The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) builds upon this by providing a common mechanism for the integration of applications at the data level. At the core of OSEE is an application framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
-
-This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS), a full featured change management system, and Define, a powerful requirements and document management solution. While these applications are already available in OSEE, new applications can be developed to share the same data model.
-
---
-
-If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and Open System Engineering Environment (OSEE) provides a common mechanism for the integration of applications at the data level. Many organizations loosely integrate tools using point-to-point data synchronization and this impedes the flow of information through the development lifecycle. Where as, applying a data-centric approach yields a much more tightly integrated toolset. Architected around this insight, the OSEE Application Framework provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
-
-OSEE is an open source project under the Eclipse Technology Project being developed by Boeing and other large system integrators in both the avionics and automotive industries. This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS) and Define which is a requirements and process management solution.
-
-
--- Details
-
-Each program or business that develops systems and software is currently required to assemble a wide array of software products to provide piecemeal capabilities necessary for completing different stages of the engineering lifecycle. Once installed, the daunting task of configuring and gluing them together begins. After years of effort, the program may have a toolset that is adequate for its current needs, but is ill-suited for growth and is far from optimized. In addition, the resulting tools are disconnected, sporadically maintained, and use an overwhelming array of disjointed user interfaces to access partially redundant data. Additionally, in the case of large programs or document-demanding customers like the US Government, such a toolset can often carry with it multi-million dollar software licensing, customization, configuration, and maintenance costs.
-
-Eclipse has solved half of this problem by presented the capability to purchase and develop a set of tools that can be plugged in to a common framework. This framwork gives many common services to both the developer and the end user. It is now easier than ever to "integrate" a set of tools. But, if the desire is true integration that provides cost savings, the problem of the data must be addressed.
-
-Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is being developed with a strong focus on the data. At the core of OSEE is an Application Framework that includes a powerful version controlled, object database that enables applications to persist their data in a simple model of only three main objects: Artifacts, Attributes and Relations. This enables applications to share not only the user interface, but the data. Software design created in a modeling application can be stored and related directly to the system and subsystem requirements which are stored and related to the source code that implements it and the test cases that verify it.
-
---
-Audience
- Tool developers, Tech-leads and project managers or anyone who uses to large tools suites
-
-
-Thoughts to be considered:
-Delivery of open source DB and OSEE to customer instead of documents
-OSEE provides to data what Eclipse provides to UI
-
-- History of Apache program at Boeing
-- Reasearch into DBs
-- Tight integration / vs loose
-- Delivery of open source DB and OSEE to customer instead of documents
-- Simplicity of Data (Artifact, Relation, Attribute, Branch)
-- Dynamic object db versus static relational
-- Version controlled
-- Configuration Managed
-- Generic Editors / Viewers (cause generic data model)
-- Extensible enought to create Specific editors /viewers (ATS)
-- Eclipse based
-- OSEE is open source - collaboration (Universities / etc)
-- Scalability - Small to Enterprise use
-- Demo
- - Architecture diagram
- - ATS Workflow
- - Skywalker
- - Artifact Editor
- - ATS Editor
- - Artifact Explorer
+Authors/Presenters: Ryan, Don and Jeff
+Name: The Cure for Your Disconnected Toolset Headache
+Abstract:
+
+If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. Many organizations loosely integrate tools using point-to-point data synchronization. This is costly to create, impedes the flow of information through the development lifecycle and is difficult to maintain. Applying a data-centric approach yields a more tightly integrated toolset.
+
+The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and the <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) builds upon this by providing a common mechanism for the integration of applications at the data level. At the core of OSEE is an application framework which provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
+
+This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS), a full featured change management system, and Define, a powerful requirements and document management solution. While these applications are already available in OSEE, new applications can be developed to share the same data model.
+
+--
+
+If you are a tool developer, project lead, or anyone who works with a sprawling toolset then this talk is for you. The Eclipse workbench provides a common mechanism for the integration of applications at the user interface level and Open System Engineering Environment (OSEE) provides a common mechanism for the integration of applications at the data level. Many organizations loosely integrate tools using point-to-point data synchronization and this impedes the flow of information through the development lifecycle. Where as, applying a data-centric approach yields a much more tightly integrated toolset. Architected around this insight, the OSEE Application Framework provides a powerful persistence layer allowing applications to utilize a common data model that is accessible to the entire toolset.
+
+OSEE is an open source project under the Eclipse Technology Project being developed by Boeing and other large system integrators in both the avionics and automotive industries. This tightly integrated environment includes applications built on the OSEE Application Framework such as the Action Tracking System (ATS) and Define which is a requirements and process management solution.
+
+
+-- Details
+
+Each program or business that develops systems and software is currently required to assemble a wide array of software products to provide piecemeal capabilities necessary for completing different stages of the engineering lifecycle. Once installed, the daunting task of configuring and gluing them together begins. After years of effort, the program may have a toolset that is adequate for its current needs, but is ill-suited for growth and is far from optimized. In addition, the resulting tools are disconnected, sporadically maintained, and use an overwhelming array of disjointed user interfaces to access partially redundant data. Additionally, in the case of large programs or document-demanding customers like the US Government, such a toolset can often carry with it multi-million dollar software licensing, customization, configuration, and maintenance costs.
+
+Eclipse has solved half of this problem by presented the capability to purchase and develop a set of tools that can be plugged in to a common framework. This framwork gives many common services to both the developer and the end user. It is now easier than ever to "integrate" a set of tools. But, if the desire is true integration that provides cost savings, the problem of the data must be addressed.
+
+Recently submitted and approved as an Eclipse project, The Open System Engineering Environment (OSEE) is being developed with a strong focus on the data. At the core of OSEE is an Application Framework that includes a powerful version controlled, object database that enables applications to persist their data in a simple model of only three main objects: Artifacts, Attributes and Relations. This enables applications to share not only the user interface, but the data. Software design created in a modeling application can be stored and related directly to the system and subsystem requirements which are stored and related to the source code that implements it and the test cases that verify it.
+
+--
+Audience
+ Tool developers, Tech-leads and project managers or anyone who uses to large tools suites
+
+
+Thoughts to be considered:
+Delivery of open source DB and OSEE to customer instead of documents
+OSEE provides to data what Eclipse provides to UI
+
+- History of Apache program at Boeing
+- Reasearch into DBs
+- Tight integration / vs loose
+- Delivery of open source DB and OSEE to customer instead of documents
+- Simplicity of Data (Artifact, Relation, Attribute, Branch)
+- Dynamic object db versus static relational
+- Version controlled
+- Configuration Managed
+- Generic Editors / Viewers (cause generic data model)
+- Extensible enought to create Specific editors /viewers (ATS)
+- Eclipse based
+- OSEE is open source - collaboration (Universities / etc)
+- Scalability - Small to Enterprise use
+- Demo
+ - Architecture diagram
+ - ATS Workflow
+ - Skywalker
+ - Artifact Editor
+ - ATS Editor
+ - Artifact Explorer
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/presentation_planning.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/presentation_planning.txt
index 987f5612d6..7e4b6c3521 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/presentation_planning.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Abstracts/presentation_planning.txt
@@ -1,81 +1,81 @@
-See ../EclipseCon 2008.txt for more information
-
-jeff.c.phillips@boeing.com
-donald.g.dunne@boeing.com
-andrew.m.finkbeiner@boeing.com
-<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a>
-
-422 submittions
-
-"Long Talk" is 50 minutes
-"Short Talk" is 10 minutes
-
-competitors, as Mike noted:
-
- You need to step out of your comfort zone as to what Eclipse is. It's no longer just about development tools. Eclipse now houses a wide range of "runtime" projects like application frameworks (service-oriented architecture (SOA) frameworks, etc.) or things one would expect to find in a Java application server.
-
- We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform.
-
- Importantly, we're not just talking about enterprise software. In fact, Eclipse is now the standard for C/C++ development in the embedded/mobile market (the only real-time operating system company that hasn't standardized on Eclipse is Green Hills). So, in the mobile/embedded space we have Symbian, QNX, Wind River, Nokia, and others working together on common platforms, then aggressively competing on the products they build on top of these platforms.
-
-Submission Guidelines http://wiki.eclipse.org/EclipseCon_Submission_Guidelines
-Selection Guidelines http://wiki.eclipse.org/EclipseCon_Selection_Guidelines
-Talk Types http://www.eclipsecon.org/2008/?page=submissions/submissionspage2
-Category of Presentation http://www.eclipsecon.org/2008/?page=submissions/submissionspage3
-
-Engineering Environment [Industry Vertical]
-"Long Talk" - Don and Ryan
- integrated, open source
- saves millions on license fees
- unlike many proprietary competitors
-
-The Intrapreneural Spirit [Business]
-"Long Talk" - Don and Ryan
- how to get an open source project through a large corporation
- work with Eclipse foundation to find partners (GM)
- Earned value
- The education of an acedential C.E.O.
- integration around the data
- lean - deep integration
-
-Open System Engineering Environment: An Integrated Solution [Emerging Technologies]
-"Short Talk" - Jeff and Andy
- share BLAMs operations,
- GUI is auto-generated
- construct workflow from discovered operations
- put data from web and store in artifacts
-
-The Cure for Your Disconnected Toolset Headache [Tools]
-"Long Talk" - Don and Jeff
- eliminate redundant data entry
- Change Management
- OSEE Application Framework including Object-Oriented Persistence Layer
-
-Take Courage and Arm Yourself With The Right Tooling To Embrace Change [Tools]
-"Long Talk" - Jeff and Ryan
- scales from small project to enterprise level
- navigate traceability using skywalker (graphical aid in understanding the architecture)
- pre-configured database (our demo database)
- advanced searching
- import
- how to customize and extend (that opens their minds to possibilities)
- data versus document delivery (give the customer the tool with the data)
- Publishing
-
- individual requirement artifacts with fine grained (version, tracability)
- mention eclipse open source
- way to interact with audience
-
- Connectivity
-
-
-Top 10 Deployment Secrets They Don't Want You To Know [Other]
-"Long Talk" - Don and Andy
- supporting large number of users
- User experience and usability (HCI)
- lesson about non-sw developers using an eclipse based product
- general purpose is more complicated for the user than a limited scope tool
- Escape from processes
- (build workflow into the tool)
- how do you encourage adoption of new tool
- don't deploy and then leave for EclipseCon
+See ../EclipseCon 2008.txt for more information
+
+jeff.c.phillips@boeing.com
+donald.g.dunne@boeing.com
+andrew.m.finkbeiner@boeing.com
+<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a>
+
+422 submittions
+
+"Long Talk" is 50 minutes
+"Short Talk" is 10 minutes
+
+competitors, as Mike noted:
+
+ You need to step out of your comfort zone as to what Eclipse is. It's no longer just about development tools. Eclipse now houses a wide range of "runtime" projects like application frameworks (service-oriented architecture (SOA) frameworks, etc.) or things one would expect to find in a Java application server.
+
+ We've come up with a way to help multiple companies - including direct competitors - to work together on a level playing field to build next-generation platforms and then compete with the applications they build on top of this platform. In other words, they use Eclipse to collaborate on a platform and then compete on the products that run on the platform.
+
+ Importantly, we're not just talking about enterprise software. In fact, Eclipse is now the standard for C/C++ development in the embedded/mobile market (the only real-time operating system company that hasn't standardized on Eclipse is Green Hills). So, in the mobile/embedded space we have Symbian, QNX, Wind River, Nokia, and others working together on common platforms, then aggressively competing on the products they build on top of these platforms.
+
+Submission Guidelines http://wiki.eclipse.org/EclipseCon_Submission_Guidelines
+Selection Guidelines http://wiki.eclipse.org/EclipseCon_Selection_Guidelines
+Talk Types http://www.eclipsecon.org/2008/?page=submissions/submissionspage2
+Category of Presentation http://www.eclipsecon.org/2008/?page=submissions/submissionspage3
+
+Engineering Environment [Industry Vertical]
+"Long Talk" - Don and Ryan
+ integrated, open source
+ saves millions on license fees
+ unlike many proprietary competitors
+
+The Intrapreneural Spirit [Business]
+"Long Talk" - Don and Ryan
+ how to get an open source project through a large corporation
+ work with Eclipse foundation to find partners (GM)
+ Earned value
+ The education of an acedential C.E.O.
+ integration around the data
+ lean - deep integration
+
+Open System Engineering Environment: An Integrated Solution [Emerging Technologies]
+"Short Talk" - Jeff and Andy
+ share BLAMs operations,
+ GUI is auto-generated
+ construct workflow from discovered operations
+ put data from web and store in artifacts
+
+The Cure for Your Disconnected Toolset Headache [Tools]
+"Long Talk" - Don and Jeff
+ eliminate redundant data entry
+ Change Management
+ OSEE Application Framework including Object-Oriented Persistence Layer
+
+Take Courage and Arm Yourself With The Right Tooling To Embrace Change [Tools]
+"Long Talk" - Jeff and Ryan
+ scales from small project to enterprise level
+ navigate traceability using skywalker (graphical aid in understanding the architecture)
+ pre-configured database (our demo database)
+ advanced searching
+ import
+ how to customize and extend (that opens their minds to possibilities)
+ data versus document delivery (give the customer the tool with the data)
+ Publishing
+
+ individual requirement artifacts with fine grained (version, tracability)
+ mention eclipse open source
+ way to interact with audience
+
+ Connectivity
+
+
+Top 10 Deployment Secrets They Don't Want You To Know [Other]
+"Long Talk" - Don and Andy
+ supporting large number of users
+ User experience and usability (HCI)
+ lesson about non-sw developers using an eclipse based product
+ general purpose is more complicated for the user than a limited scope tool
+ Escape from processes
+ (build workflow into the tool)
+ how do you encourage adoption of new tool
+ don't deploy and then leave for EclipseCon
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/.svn/text-base/OSEE - An Integrated Solution.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/.svn/text-base/OSEE - An Integrated Solution.txt.svn-base
index 56162dad34..b50adf2eca 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/.svn/text-base/OSEE - An Integrated Solution.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/.svn/text-base/OSEE - An Integrated Solution.txt.svn-base
@@ -1,8 +1,8 @@
-Open System Engineering Environment: An Integrated Solution
-Presenters: Ryan and Don
-
-The <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) eclipse project supports lean engineering across
-the full product life-cycle by providing an integrated and data-centric application framework. At its core is a persistence layer that provides a
-dynamic data model, advanced version control capabilities, and powerful search capabilities. This talk provides an overview of the OSEE Application
-Framework and tools that extend it, including; a powerful requirements and document management solution, OSEE Define, and a full featured change
-management system, OSEE ATS.
+Open System Engineering Environment: An Integrated Solution
+Presenters: Ryan and Don
+
+The <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) eclipse project supports lean engineering across
+the full product life-cycle by providing an integrated and data-centric application framework. At its core is a persistence layer that provides a
+dynamic data model, advanced version control capabilities, and powerful search capabilities. This talk provides an overview of the OSEE Application
+Framework and tools that extend it, including; a powerful requirements and document management solution, OSEE Define, and a full featured change
+management system, OSEE ATS.
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/OSEE - An Integrated Solution.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/OSEE - An Integrated Solution.txt
index 56162dad34..b50adf2eca 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/OSEE - An Integrated Solution.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/OSEE - An Integrated Solution/OSEE - An Integrated Solution.txt
@@ -1,8 +1,8 @@
-Open System Engineering Environment: An Integrated Solution
-Presenters: Ryan and Don
-
-The <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) eclipse project supports lean engineering across
-the full product life-cycle by providing an integrated and data-centric application framework. At its core is a persistence layer that provides a
-dynamic data model, advanced version control capabilities, and powerful search capabilities. This talk provides an overview of the OSEE Application
-Framework and tools that extend it, including; a powerful requirements and document management solution, OSEE Define, and a full featured change
-management system, OSEE ATS.
+Open System Engineering Environment: An Integrated Solution
+Presenters: Ryan and Don
+
+The <a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE) eclipse project supports lean engineering across
+the full product life-cycle by providing an integrated and data-centric application framework. At its core is a persistence layer that provides a
+dynamic data model, advanced version control capabilities, and powerful search capabilities. This talk provides an overview of the OSEE Application
+Framework and tools that extend it, including; a powerful requirements and document management solution, OSEE Define, and a full featured change
+management system, OSEE ATS.
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/.svn/text-base/agenda.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/.svn/text-base/agenda.txt.svn-base
index ac7c17792a..3b743e2de6 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/.svn/text-base/agenda.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/.svn/text-base/agenda.txt.svn-base
@@ -1,20 +1,20 @@
-title slide
-
-
-traceability
-tight integration (around the data)
-baselining / product lines / variant control
-V diagram
-systems engineering
-arhcitecture diagram
-collaboration
-
-
-show credability - include screen shots and demo
-zest viewer
-
-worklfow/ process integration
-maturity / status
-future plans
-lean
+title slide
+
+
+traceability
+tight integration (around the data)
+baselining / product lines / variant control
+V diagram
+systems engineering
+arhcitecture diagram
+collaboration
+
+
+show credability - include screen shots and demo
+zest viewer
+
+worklfow/ process integration
+maturity / status
+future plans
+lean
beyond vertical \ No newline at end of file
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/agenda.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/agenda.txt
index ac7c17792a..3b743e2de6 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/agenda.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/The Cure for Your Disconnected Toolset Headache/agenda.txt
@@ -1,20 +1,20 @@
-title slide
-
-
-traceability
-tight integration (around the data)
-baselining / product lines / variant control
-V diagram
-systems engineering
-arhcitecture diagram
-collaboration
-
-
-show credability - include screen shots and demo
-zest viewer
-
-worklfow/ process integration
-maturity / status
-future plans
-lean
+title slide
+
+
+traceability
+tight integration (around the data)
+baselining / product lines / variant control
+V diagram
+systems engineering
+arhcitecture diagram
+collaboration
+
+
+show credability - include screen shots and demo
+zest viewer
+
+worklfow/ process integration
+maturity / status
+future plans
+lean
beyond vertical \ No newline at end of file
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/.svn/text-base/Top 10 deployment secrets they don't want you to know.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/.svn/text-base/Top 10 deployment secrets they don't want you to know.txt.svn-base
index 73ed24825f..c45d93e66f 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/.svn/text-base/Top 10 deployment secrets they don't want you to know.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/.svn/text-base/Top 10 deployment secrets they don't want you to know.txt.svn-base
@@ -1,40 +1,40 @@
-Authors/Presenters: Don and Andy
-Name: Top 10 deployment secrets they don't want you to know
-Abstract:
-
-If you are an application developer and think the hardest thing you have to do is develop the application, this talk is for you. Determining requirements, architecting, developing and testing applications all have their obstacles and pitfalls, but they're nothing compared to some of the challenges that you will have with deployment and support. This talk will focus on lessons learned from deploying OSEE to over 300 users in development of the Boeing Longbow Apache AH-64 Attack Helicopter.
-
-<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE), is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share a common data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
-
----
-
-15. Don't deploy then leave for EclipseCon - Don't be the one left behind
-1. Eclipse update site for quick turn-around releases - It wasn't meant for sprial development
-2. Multi-layered system of FAQ, Help, Presentations and Screencasts - You're users still won't be happy
-3. Training - Screencasts, Hands On and Mentoring
-4. ATS everything, then sort it out
-5. Users Group Meeting
-6. Prioritization Meeting
-7. Release cycle 3-1-1 (3 wks of work, 1 wk of integ/test, 1 wk of test)
-8. Key Users == Happy Users
-9. Use what you develop
-10. Branching and Merging
-11. After >3 of same user reported problems, code the problem away
-12. Build the workflow into the application (process free)
-13. General purpose over specific
-14. Selling the concept/tool
-16. Non-eclipse users using and eclipse based integrated environment
-
-The Open System Engineering Environment (OSEE), an Eclipse project, is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share the data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
-
-Top 10 deployment secrets they don't want you to know [Other]
-"Long Talk" - Don and Andy
- supporting large number of users
- User experience and usability (HCI)
- lesson about non-sw developers using an eclipse based product
- general purpose is more complicated for the user than a limited scope tool
- Escape from processes
- (build workflow into the tool)
- how do you encourage adoption of new tool
- don't deploy and then leave for EclipseCon
-
+Authors/Presenters: Don and Andy
+Name: Top 10 deployment secrets they don't want you to know
+Abstract:
+
+If you are an application developer and think the hardest thing you have to do is develop the application, this talk is for you. Determining requirements, architecting, developing and testing applications all have their obstacles and pitfalls, but they're nothing compared to some of the challenges that you will have with deployment and support. This talk will focus on lessons learned from deploying OSEE to over 300 users in development of the Boeing Longbow Apache AH-64 Attack Helicopter.
+
+<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE), is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share a common data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
+
+---
+
+15. Don't deploy then leave for EclipseCon - Don't be the one left behind
+1. Eclipse update site for quick turn-around releases - It wasn't meant for sprial development
+2. Multi-layered system of FAQ, Help, Presentations and Screencasts - You're users still won't be happy
+3. Training - Screencasts, Hands On and Mentoring
+4. ATS everything, then sort it out
+5. Users Group Meeting
+6. Prioritization Meeting
+7. Release cycle 3-1-1 (3 wks of work, 1 wk of integ/test, 1 wk of test)
+8. Key Users == Happy Users
+9. Use what you develop
+10. Branching and Merging
+11. After >3 of same user reported problems, code the problem away
+12. Build the workflow into the application (process free)
+13. General purpose over specific
+14. Selling the concept/tool
+16. Non-eclipse users using and eclipse based integrated environment
+
+The Open System Engineering Environment (OSEE), an Eclipse project, is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share the data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
+
+Top 10 deployment secrets they don't want you to know [Other]
+"Long Talk" - Don and Andy
+ supporting large number of users
+ User experience and usability (HCI)
+ lesson about non-sw developers using an eclipse based product
+ general purpose is more complicated for the user than a limited scope tool
+ Escape from processes
+ (build workflow into the tool)
+ how do you encourage adoption of new tool
+ don't deploy and then leave for EclipseCon
+
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/Top 10 deployment secrets they don't want you to know.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/Top 10 deployment secrets they don't want you to know.txt
index 73ed24825f..c45d93e66f 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/Top 10 deployment secrets they don't want you to know.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/Top 10 Deployment Secrets/Top 10 deployment secrets they don't want you to know.txt
@@ -1,40 +1,40 @@
-Authors/Presenters: Don and Andy
-Name: Top 10 deployment secrets they don't want you to know
-Abstract:
-
-If you are an application developer and think the hardest thing you have to do is develop the application, this talk is for you. Determining requirements, architecting, developing and testing applications all have their obstacles and pitfalls, but they're nothing compared to some of the challenges that you will have with deployment and support. This talk will focus on lessons learned from deploying OSEE to over 300 users in development of the Boeing Longbow Apache AH-64 Attack Helicopter.
-
-<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE), is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share a common data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
-
----
-
-15. Don't deploy then leave for EclipseCon - Don't be the one left behind
-1. Eclipse update site for quick turn-around releases - It wasn't meant for sprial development
-2. Multi-layered system of FAQ, Help, Presentations and Screencasts - You're users still won't be happy
-3. Training - Screencasts, Hands On and Mentoring
-4. ATS everything, then sort it out
-5. Users Group Meeting
-6. Prioritization Meeting
-7. Release cycle 3-1-1 (3 wks of work, 1 wk of integ/test, 1 wk of test)
-8. Key Users == Happy Users
-9. Use what you develop
-10. Branching and Merging
-11. After >3 of same user reported problems, code the problem away
-12. Build the workflow into the application (process free)
-13. General purpose over specific
-14. Selling the concept/tool
-16. Non-eclipse users using and eclipse based integrated environment
-
-The Open System Engineering Environment (OSEE), an Eclipse project, is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share the data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
-
-Top 10 deployment secrets they don't want you to know [Other]
-"Long Talk" - Don and Andy
- supporting large number of users
- User experience and usability (HCI)
- lesson about non-sw developers using an eclipse based product
- general purpose is more complicated for the user than a limited scope tool
- Escape from processes
- (build workflow into the tool)
- how do you encourage adoption of new tool
- don't deploy and then leave for EclipseCon
-
+Authors/Presenters: Don and Andy
+Name: Top 10 deployment secrets they don't want you to know
+Abstract:
+
+If you are an application developer and think the hardest thing you have to do is develop the application, this talk is for you. Determining requirements, architecting, developing and testing applications all have their obstacles and pitfalls, but they're nothing compared to some of the challenges that you will have with deployment and support. This talk will focus on lessons learned from deploying OSEE to over 300 users in development of the Boeing Longbow Apache AH-64 Attack Helicopter.
+
+<a href="http://www.eclipse.org/osee">Open System Engineering Environment</a> (OSEE), is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share a common data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
+
+---
+
+15. Don't deploy then leave for EclipseCon - Don't be the one left behind
+1. Eclipse update site for quick turn-around releases - It wasn't meant for sprial development
+2. Multi-layered system of FAQ, Help, Presentations and Screencasts - You're users still won't be happy
+3. Training - Screencasts, Hands On and Mentoring
+4. ATS everything, then sort it out
+5. Users Group Meeting
+6. Prioritization Meeting
+7. Release cycle 3-1-1 (3 wks of work, 1 wk of integ/test, 1 wk of test)
+8. Key Users == Happy Users
+9. Use what you develop
+10. Branching and Merging
+11. After >3 of same user reported problems, code the problem away
+12. Build the workflow into the application (process free)
+13. General purpose over specific
+14. Selling the concept/tool
+16. Non-eclipse users using and eclipse based integrated environment
+
+The Open System Engineering Environment (OSEE), an Eclipse project, is built on the OSEE Application Framework that was developed as a data-centric complement to the Eclipse platform and allows applications that extend Eclipse to go one step further and share the data model. On this framework was built two main applications, Define, a requirements and document management solution, and the Action Tracking System, a tightly-integrated problem change request system.
+
+Top 10 deployment secrets they don't want you to know [Other]
+"Long Talk" - Don and Andy
+ supporting large number of users
+ User experience and usability (HCI)
+ lesson about non-sw developers using an eclipse based product
+ general purpose is more complicated for the user than a limited scope tool
+ Escape from processes
+ (build workflow into the tool)
+ how do you encourage adoption of new tool
+ don't deploy and then leave for EclipseCon
+
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/API Design Workshop.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/API Design Workshop.txt.svn-base
index 9caaf41a79..3c39c87b17 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/API Design Workshop.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/API Design Workshop.txt.svn-base
@@ -1,5 +1,5 @@
-Read through the presentation slides at http://www.eclipsecon.org/2008/?page=sub/&id=65
-very good slides (look at the slides on listeners)
-
-if you care about compatibility, do not have subclasses extend interfaces rather use abstract classes
-this means extension points should require abstract classes and not interfaces
+Read through the presentation slides at http://www.eclipsecon.org/2008/?page=sub/&id=65
+very good slides (look at the slides on listeners)
+
+if you care about compatibility, do not have subclasses extend interfaces rather use abstract classes
+this means extension points should require abstract classes and not interfaces
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/Practical testing of Eclipse plugins and OSGi bundles.txt.svn-base b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/Practical testing of Eclipse plugins and OSGi bundles.txt.svn-base
index d399447775..80be4d4d50 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/Practical testing of Eclipse plugins and OSGi bundles.txt.svn-base
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/.svn/text-base/Practical testing of Eclipse plugins and OSGi bundles.txt.svn-base
@@ -1,6 +1,6 @@
-
-create test bundles as fragments (same class loader, separates code and test)
-Run an application: [No Application]
-Use test suite (helps with command line test running)
-in the test launch: clear the workspace and clear configuration area
+
+create test bundles as fragments (same class loader, separates code and test)
+Run an application: [No Application]
+Use test suite (helps with command line test running)
+in the test launch: clear the workspace and clear configuration area
use RCP Robot \ No newline at end of file
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/API Design Workshop.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/API Design Workshop.txt
index 9caaf41a79..3c39c87b17 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/API Design Workshop.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/API Design Workshop.txt
@@ -1,5 +1,5 @@
-Read through the presentation slides at http://www.eclipsecon.org/2008/?page=sub/&id=65
-very good slides (look at the slides on listeners)
-
-if you care about compatibility, do not have subclasses extend interfaces rather use abstract classes
-this means extension points should require abstract classes and not interfaces
+Read through the presentation slides at http://www.eclipsecon.org/2008/?page=sub/&id=65
+very good slides (look at the slides on listeners)
+
+if you care about compatibility, do not have subclasses extend interfaces rather use abstract classes
+this means extension points should require abstract classes and not interfaces
diff --git a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/Practical testing of Eclipse plugins and OSGi bundles.txt b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/Practical testing of Eclipse plugins and OSGi bundles.txt
index d399447775..80be4d4d50 100644
--- a/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/Practical testing of Eclipse plugins and OSGi bundles.txt
+++ b/plugins/org.eclipse.osee.support.admin/eclipseCon/2008/tutorials/Practical testing of Eclipse plugins and OSGi bundles.txt
@@ -1,6 +1,6 @@
-
-create test bundles as fragments (same class loader, separates code and test)
-Run an application: [No Application]
-Use test suite (helps with command line test running)
-in the test launch: clear the workspace and clear configuration area
+
+create test bundles as fragments (same class loader, separates code and test)
+Run an application: [No Application]
+Use test suite (helps with command line test running)
+in the test launch: clear the workspace and clear configuration area
use RCP Robot \ No newline at end of file

Back to the top