Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Rhapsody Eclipse

•Download as PPT, PDF•
•
Bill Duncan
Bill Duncan

The document discusses embedded software development for Eclipse. It provides an overview of Eclipse and how it offers a customizable development platform through a plug-in architecture. Model-driven development approaches are described that can help reduce development costs by catching defects earlier through visual modeling and design-level debugging integrated within the Eclipse environment. Team collaboration is also facilitated through Eclipse and Rational Team Concert plug-ins.

1 of 17
Embedded software development for Eclipse Paul Urban, IBM
Eclipse overview Eclipse started as an open source development platform by IBM Highly customizable generic features for specific domain solutions Customization through open plug-in architecture The Eclipse platform integrates multiple development tools for software development It allows tools to be added through the use of plug-ins Eclipse offers several advanced C/C++ coding environments Features appealing to the “coder” persona Both open source [C/C++ development tools (CDT)] and proprietary Realtime operating system (RTOS) vendors offer Eclipse-based environments Integrates with configuration management and product management tools
Challenges facing embedded developers Increasing complexity and accelerating changes Unrelenting financial pressures and need to better manage risk Compliance with key engineering and design processes Effectiveness of organizationally and geographically distributed teams Building more innovative products to grow the business Aerospace & Defense Automotive Telecom/ Datacom Consumer Electronics Medical Devices
Traditional software development An optimal approach would be to fix errors as they are introduced, thereby reducing your cost of development! Requirements Design Implementation Test Costs of design changes Time Induced errors
Goal of a Telelogic ® Rhapsody ® Model-Driven Development ™ approach Helping you catch defects as they are introduced, reducing costs of development Costs of design changes Time Induced errors
Model-driven development Model-driven development (MDD) enables developers to capture the design using graphical models Visualizing design concepts increases understandability Use Object Management Group (OMG) Unified Modeling Language (UML) or a domain-specific language (DSL) Achieving the full benefits of MDD requires model and code synchronization
Benefits of modeling Modeling gives us the ability to visualize the system clearly Modeling simplifies the problem through abstraction Executable models enable early prototyping
Rhapsody integration with Eclipse Integrated MDD within Eclipse environment Enable synchronized model or code development workflow Leverage Eclipse to tailor the environment for your needs Eclipse code editor Rhapsody diagram editors
Integrated design and debug environment Natural workflow for code-centric developers Perform design- or code-level debugging in single environment Leverage Eclipse tools with Rhapsody data, such as team collaboration Use Eclipse Intellisense View build errors View Rhapsody diagrams View model information
Collaborative development with Eclipse Collaborative platform facilitating: Online collaboration of project artifacts Integrate work items management Online project tracking dashboards Real-time project presence and messaging Rhapsody eclipse plug-ins inter operate with the Rational Team Concert plug-ins Leverages Jazz and Eclipse technologies Connecting modeling project with change streams Associating changes with work-items Automatic merging of trivial changes Activate diff-merge for non-trivial changes
Integrated team collaboration with RTC User 1 – adds a new class Change gets listed in pending changes list
Deliver completed work Associate changes to work item and deliver it to RTC
Team is notified of changes User 2 – is notified of the incoming changes and can accept them
Demo Demo Time
Rhapsody and Eclipse integration Discover defects earlier with design-level debugging Visualize existing Eclipse code A picture is worth a thousand words Documents undocumented code using customizable formats View structure and architecture of the current design Tailored development environment Customize perspectives for your needs Work in the model or Eclipse editor with changes synchronized Automates tedious coding tasks Leverage Eclipse tools such as team collaboration capabilities Automated documentation for your application
For more information To learn more, please visit: www.telelogic.com Learn about IBM Rational ® software at: IBM Rational software IBM Rational Software Delivery Platform Process and portfolio management Change and release management Quality management Architecture management Rational trial downloads Leading Innovation Web site developerWorks ® Rational IBM Rational TV IBM Business Partners IBM Rational case studies
Copyright information © Copyright IBM Corporation 2008 IBM Corporation Software Group Route 100 Somers, NY 10589 U.S.A. Produced in the United States of America October 2008 All Rights Reserved IBM, the IBM logo, ibm.com, Rational, and Telelogic are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at ibm.com/legal/copytrade.shtml Other company, product, or service names may be trademarks or service marks of others. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. References in this publication to IBM products and services do not imply that IBM intends to make them available in all countries in which IBM operates. The information contained in this documentation is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this documentation, it is provided “as is” without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this documentation or any other documentation. Nothing contained in this documentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM (or its suppliers or licensors), or altering the terms and conditions of the applicable license agreement governing the use of IBM software. RAP14028-USEN-00

More Related Content

Rhapsody Eclipse

  • 1. Embedded software development for Eclipse Paul Urban, IBM
  • 2. Eclipse overview Eclipse started as an open source development platform by IBM Highly customizable generic features for specific domain solutions Customization through open plug-in architecture The Eclipse platform integrates multiple development tools for software development It allows tools to be added through the use of plug-ins Eclipse offers several advanced C/C++ coding environments Features appealing to the “coder” persona Both open source [C/C++ development tools (CDT)] and proprietary Realtime operating system (RTOS) vendors offer Eclipse-based environments Integrates with configuration management and product management tools
  • 3. Challenges facing embedded developers Increasing complexity and accelerating changes Unrelenting financial pressures and need to better manage risk Compliance with key engineering and design processes Effectiveness of organizationally and geographically distributed teams Building more innovative products to grow the business Aerospace & Defense Automotive Telecom/ Datacom Consumer Electronics Medical Devices
  • 4. Traditional software development An optimal approach would be to fix errors as they are introduced, thereby reducing your cost of development! Requirements Design Implementation Test Costs of design changes Time Induced errors
  • 5. Goal of a Telelogic ® Rhapsody ® Model-Driven Development ™ approach Helping you catch defects as they are introduced, reducing costs of development Costs of design changes Time Induced errors
  • 6. Model-driven development Model-driven development (MDD) enables developers to capture the design using graphical models Visualizing design concepts increases understandability Use Object Management Group (OMG) Unified Modeling Language (UML) or a domain-specific language (DSL) Achieving the full benefits of MDD requires model and code synchronization
  • 7. Benefits of modeling Modeling gives us the ability to visualize the system clearly Modeling simplifies the problem through abstraction Executable models enable early prototyping
  • 8. Rhapsody integration with Eclipse Integrated MDD within Eclipse environment Enable synchronized model or code development workflow Leverage Eclipse to tailor the environment for your needs Eclipse code editor Rhapsody diagram editors
  • 9. Integrated design and debug environment Natural workflow for code-centric developers Perform design- or code-level debugging in single environment Leverage Eclipse tools with Rhapsody data, such as team collaboration Use Eclipse Intellisense View build errors View Rhapsody diagrams View model information
  • 10. Collaborative development with Eclipse Collaborative platform facilitating: Online collaboration of project artifacts Integrate work items management Online project tracking dashboards Real-time project presence and messaging Rhapsody eclipse plug-ins inter operate with the Rational Team Concert plug-ins Leverages Jazz and Eclipse technologies Connecting modeling project with change streams Associating changes with work-items Automatic merging of trivial changes Activate diff-merge for non-trivial changes
  • 11. Integrated team collaboration with RTC User 1 – adds a new class Change gets listed in pending changes list
  • 12. Deliver completed work Associate changes to work item and deliver it to RTC
  • 13. Team is notified of changes User 2 – is notified of the incoming changes and can accept them
  • 15. Rhapsody and Eclipse integration Discover defects earlier with design-level debugging Visualize existing Eclipse code A picture is worth a thousand words Documents undocumented code using customizable formats View structure and architecture of the current design Tailored development environment Customize perspectives for your needs Work in the model or Eclipse editor with changes synchronized Automates tedious coding tasks Leverage Eclipse tools such as team collaboration capabilities Automated documentation for your application
  • 16. For more information To learn more, please visit: www.telelogic.com Learn about IBM Rational ® software at: IBM Rational software IBM Rational Software Delivery Platform Process and portfolio management Change and release management Quality management Architecture management Rational trial downloads Leading Innovation Web site developerWorks ® Rational IBM Rational TV IBM Business Partners IBM Rational case studies
  • 17. Copyright information © Copyright IBM Corporation 2008 IBM Corporation Software Group Route 100 Somers, NY 10589 U.S.A. Produced in the United States of America October 2008 All Rights Reserved IBM, the IBM logo, ibm.com, Rational, and Telelogic are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at ibm.com/legal/copytrade.shtml Other company, product, or service names may be trademarks or service marks of others. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. References in this publication to IBM products and services do not imply that IBM intends to make them available in all countries in which IBM operates. The information contained in this documentation is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this documentation, it is provided “as is” without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this documentation or any other documentation. Nothing contained in this documentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM (or its suppliers or licensors), or altering the terms and conditions of the applicable license agreement governing the use of IBM software. RAP14028-USEN-00