1 / 16

Future Work: Gap analysis and Roadmapping

Future Work: Gap analysis and Roadmapping. Plans for further work Arne J. Berre, SINTEF. The CBSEnet Roadmapping process. CBSE Classification Model Concepts Process Roles Business Product. Landscape Domains Common Business Finance Telecom COTS Simulation GIS …embedded

elton-fulton
Download Presentation

Future Work: Gap analysis and Roadmapping

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Future Work: Gap analysis and Roadmapping Plans for further work Arne J. Berre, SINTEF

  2. The CBSEnet Roadmapping process • CBSE • Classification • Model • Concepts • Process • Roles • Business • Product • Landscape • Domains • Common • Business • Finance • Telecom • COTS • Simulation • GIS • …embedded • Web services • MDA • Landscape documents • Domain • Visions • CBSE practice • CBSE stds/tec • CBSE research, IST • Issues/Gaps • practice, stds/tec, research • 7. Roadmap recommendations • practice, stds/tec, research • CBSE Survey • State of • the practice

  3. Gap Analysis activities Research Gap A research gap is a fundamental absence of knowledge. Technology Gap A technology gap is an absence of technology or the integration of technologies. Research results are available (i.e. from IST projects), but has not yet been manifested in products. Standards Gap A standards gap is the absence of Standard components , concepts/infrastructure, process, …

  4. Roadmapping • Whilst gap analysis identifies missing research, technology, and standards, the process of creating a roadmap is concerned with actions to close the gap. Generally, this process of creating a roadmap is called roadmapping. Roadmapping was originally developed to help organizations anticipate and clarify resource and performance requirements and to plan and systematically manage and integrate complex projects. Currently roadmapping is used within organizations to facilitate technology planning and communication.

  5. Different types of Roadmaps • A. Science and Technology Roadmaps • B. Industry Technology Roadmaps • C. Corporate or Product-Technology Roadmaps • D. Product or Portfolio Management Roadmaps

  6. Taxonomy of roadmaps

  7. Have Want Interpretation 1 1 What can be done with existing RTS[1] to achieve a particular goal 1 0 What should be avoided to do with existing RTS 0 1 A particular goal should be achieved, but there is insufficient RTS 0 0 What should be avoided to do and there should be no activity to develop RTS Roadmapping logic [1] RTS = Research, Technology, Standards

  8. Gap Analysis Roadmap Process Research Gap Actions to close Research Gap Technology Gap Actions to close Technology Gap Standards Gap Actions to close Standards Gap Gap analysis vs Roadmap process

  9. Time horizon T1 0-2 years T2 2-5 years T3 5-10 years Roadmapping time horizon

  10. Priority P0 Irrelevant P1 Relevant P2 Important P3 Essential Roadmapping priorities

  11. The CBSEnet Roadmapping process • CBSE • Classification • Model • Concepts • Process • Roles • Business • Product • Landscape • Domains • Common • Business • Finance • Telecom • COTS • Simulation • GIS • …embedded • Web services • MDA • Landscape documents • Domain • Visions • CBSE practice • CBSE stds/tec • CBSE research, IST • Issues/Gaps • practice, stds/tec, research • 7. Roadmap recommendations • practice, stds/tec, research • CBSE Survey • State of • the practice

  12. Next steps • Finish Landscape documents for Business, Telecom and COTS – by Mid-May, 2003 • Analyse differences/similarities between the domains/sectors – horizontal versus vertical structuring of topics/issues • Initiate Landscape documents for new important domains: Embedded (Aerospace, Automotive, Command and Control, Process Control), – Identify new associate partners/contributors • Write up benefits/experiences of the use of CBSE – not only inhibitors – Marketing the vision of CBSE +(CBSE-based Services/MDA) • Further population of CBSE portal, - in particular the results of IST project research item analysis

  13. 3rd CBSEnet Workshop, CBSE – What next ?(Gap analysis and roadmapping) • OSLO, Norway • 25-26 September, 2003 • Focus: CBSE Future challenges – Gap analysis – Identify and clarify the work to be done

  14. Initial target focus for Gap analysis and Roadmaps • Business (Finance) • Telecom • COTS • Web Services vs Components • Updated Landscape documents by Mid-May 2003 • Further work until September 2003 on other domains: • Embedded, GIS, Simulation, Finance, … other ? • MDA technologies and issues

  15. CBSE at ECOOP’2003 • Input to Workshop on Component-based Programming, Darmstadt, July 2003 • CBSEnet experiences

  16. Discussion on the structure and content of the 3rd CBSEnet workshop in Oslo • Structure: Presentations, • Position statements to be submitted ? • Content: Components and Services, • Model Driven Architecture, … Trusted components, … ??? • Oslo workshop - September 25th-26th. • By SINTEF and Telenor, Oslo, Norway

More Related