<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.fritscher.ch/hec/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel>
        <title>HEC 4 ALL</title>
        <description></description>
        <link>http://www.fritscher.ch/hec/</link>
        <lastBuildDate>Sat, 04 Feb 2012 21:58:29 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
        <image>
            <url>http://www.fritscher.ch/hec/lib/tpl/arctic/images/favicon.ico</url>
            <title>HEC 4 ALL</title>
            <link>http://www.fritscher.ch/hec/</link>
        </image>
        <item>
            <title>Business Model Designer From Sticky Note To Screen Interaction</title>
            <link>http://www.fritscher.ch/hec/tm/business_model_designer_from_sticky_note_to_screen_interaction?rev=1232390982&amp;do=diff</link>
            <description>Master of Science in Information Systems

Boris Fritscher

Supervised by Prof. Yves Pigneur and by Prof. Thibault Estier

December 2008

Abstract

Business model innovation is getting more and more traction and there are new methodologies to help identify new business models, unfortunately tools to assist in this task are scarce. The difficulty is to have an application which respects all the constraints imposed by the methodology, without infringing onto the creative thought process. This proje…</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Mon, 19 Jan 2009 19:49:42 +0100</pubDate>
        </item>
        <item>
            <title>tm:sidebar</title>
            <link>http://www.fritscher.ch/hec/tm/sidebar?rev=1232136409&amp;do=diff</link>
            <description>*  Business Model Designer From Sticky Note To Screen Interaction

----------

	* Chapter 1  Introduction

----------

	*  Chapter 2  Business Model Ontology Refinement and Visualization

----------

	*  Chapter 3  Design of The Prototype

----------

	*  Chapter 4  The Technology Behind</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Fri, 16 Jan 2009 21:06:49 +0100</pubDate>
        </item>
        <item>
            <title>Appendix A  User Guide to The Final Prototype</title>
            <link>http://www.fritscher.ch/hec/tm/appendixa?rev=1232125161&amp;do=diff</link>
            <description>Chapter 7  Conclusion

A.1  Quick Reference

Figure A.1: Design screen with main actions highlighted 



A.2  Terminology

Users can have a view or an edit right on a model.

A model can have a normal or a snapshot state.

A snapshot is a picture of a model taken at a specific time.</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Fri, 16 Jan 2009 17:59:21 +0100</pubDate>
        </item>
        <item>
            <title>Appendix C  Technical Supplements</title>
            <link>http://www.fritscher.ch/hec/tm/appendixc?rev=1232123997&amp;do=diff</link>
            <description>Appendix B  Sample Business Models

C.1  Prototype 2 Server Domain Classes

 Figure C1 shows the class diagram of the domain objects representing the business model ontology. There is no class representing the building blocks instead there exists a class for each element of a building block. These classes all inherit their common attributes from a common element parent class. Elements have all at least one layer. Some subclasses of element have additional custom attributes, while others do not. …</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Fri, 16 Jan 2009 17:39:57 +0100</pubDate>
        </item>
        <item>
            <title>Appendix B  Sample Business Models</title>
            <link>http://www.fritscher.ch/hec/tm/appendixb?rev=1232123689&amp;do=diff</link>
            <description>Appendix A  User Guide to The Final Prototype

Figures B.1 and B.2 show two real world examples of models entered into the prototype. Images are exported from de report generation feature. Business models courtesy of Arvetica.

Figure B.1: Amazon: classic and S3 services</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Fri, 16 Jan 2009 17:34:49 +0100</pubDate>
        </item>
        <item>
            <title>Chapter 7  Conclusion</title>
            <link>http://www.fritscher.ch/hec/tm/chapter7?rev=1232123577&amp;do=diff</link>
            <description>Chapter 6  Further Research

The prototype that was created and studied has proven that it is possible to take a very unrestrictive paper based approach to business model innovation and support it with a digital application. The prototype in its first version does not solve more problems that the paper based version, but acts as a platform on which new functions can bring new opportunities. Some have been tried out, like annotations to keep better track of the reflexions which guided the choices…</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Fri, 16 Jan 2009 17:32:57 +0100</pubDate>
        </item>
        <item>
            <title>Chapter 6  Further Research</title>
            <link>http://www.fritscher.ch/hec/tm/chapter6?rev=1232123548&amp;do=diff</link>
            <description>Chapter 5  Validating The Prototype



What is next? Certainly the next iteration of the prototype will mainly focus on fixing the identified usability issues and implement some of the proposed features, which can be integrated into the current code base, without too many changes. But where to go after this is still open.</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Fri, 16 Jan 2009 17:32:28 +0100</pubDate>
        </item>
        <item>
            <title>Chapter 5  Validating The Prototype</title>
            <link>http://www.fritscher.ch/hec/tm/chapter5?rev=1232123409&amp;do=diff</link>
            <description>Chapter 4  The Technology Behind

For a couple of reasons, user interaction and feedback during development of the application was not very extensive. Naturally, there were time constrains, but the priority was also set on doing quick iterations to allow testing of new features. In addition, to be able to use the application a prior knowledge of the model is required. Therefore, for the first version only feedback from experts was possible. Even if the interactions are heavily inspired by the ph…</description>
            <author>boris</author>
        <category>tm</category>
            <pubDate>Fri, 16 Jan 2009 17:30:09 +0100</pubDate>
        </item>
    </channel>
</rss>

