1) The document discusses improving decision making support by linking database results to simulations.
2) Currently, decision making involves disjointed tools like spreadsheets and simulations that do not interoperate.
3) The author proposes a new language called SimQL, similar to SQL, that would allow querying and linking simulations in the same way databases are currently used.
4) This would help merge the disciplines of databases and simulations to better support decision making by providing access to simulations and future predictions from within database systems.
This document contains summaries of topics discussed in a CS207 class on software valuation and intellectual property:
1) The first section outlines topics to be covered in the class, including why software should be valued, principles of valuation, market value of software companies, intellectual capital/property, patents/copyrights/trade secrets, open source software, the life cycle of innovations, and business models.
2) Later sections summarize discussions on open source software licensing obligations, recognition of trade secrets under federal law, examples of corporate structures using offshore holdings, and long-term effects of shifting capital and intellectual property to tax havens.
3) Key concepts covered are tax benefits of jurisdictions like Bermuda and the Cayman
1) The document discusses improving decision making support by linking database results to simulations.
2) Currently, decision making involves disjointed tools like spreadsheets and simulations that do not interoperate.
3) The author proposes a new language called SimQL, similar to SQL, that would allow querying and linking simulations in the same way databases are currently used.
4) This would help merge the disciplines of databases and simulations to better support decision making by providing access to simulations and future predictions from within database systems.
This document contains summaries of topics discussed in a CS207 class on software valuation and intellectual property:
1) The first section outlines topics to be covered in the class, including why software should be valued, principles of valuation, market value of software companies, intellectual capital/property, patents/copyrights/trade secrets, open source software, the life cycle of innovations, and business models.
2) Later sections summarize discussions on open source software licensing obligations, recognition of trade secrets under federal law, examples of corporate structures using offshore holdings, and long-term effects of shifting capital and intellectual property to tax havens.
3) Key concepts covered are tax benefits of jurisdictions like Bermuda and the Cayman
This document summarizes a class on software valuation taught by Gio Wiederhold. The syllabus covers topics like why software should be valued, principles of valuation, open source software, market value of software companies, intellectual property, the life and lag of software innovation, sales expectations, business models, patents, copyrights, trade secrets, and risks of outsourcing. It discusses concepts like intellectual capital, patent bundles, setting licensing fees, and using internal sales and offshore entities to flexibly move intellectual property for tax purposes.
1. The document provides instructions for a directed reading course, including defining a topic of study, signing up under the instructor's course section, and draft/feedback deadlines of November 19th and 25th respectively, with a final report due December 2nd.
2. The syllabus outlines topics for the software valuation course, including why software should be valued, open source software, principles of valuation, market value of software companies, intellectual property, and risks of outsourcing.
3. The review discusses how understanding software value allows for rational design and business decisions, and could improve software education by considering quality over quantity in assignments.
This document contains notes from a class on valuing software intellectual property. It discusses several topics:
1. Software growth models including linear growth models and Erlang sales curves. Linear growth is a reasonable assumption but software cannot grow exponentially.
2. Factors that affect the value of software IP over its lifetime such as size, life, diminution, and lag period. The value of software IP decreases as the code base grows in size over multiple versions.
3. Methods for estimating the value of software IP including calculating total income based on price and sales volume, and discounting future cash flows to get the net present value.
4. An example valuation calculation that combines factors like software version
This document contains a syllabus for a course on software valuation and intellectual property. It discusses topics like why software should be valued, principles of valuation, open source software, market value of software companies, intellectual capital, the life cycle of software innovation, sales expectations, business models, patents and more. The document also contains slides on offshoring, transferring intellectual property rights to foreign companies, selling those rights, types of foreign entities, knowledge as the link between companies and workers, transferring tangibles versus intangibles, and a hypothetical sequence of cases to illustrate these concepts.
This document contains notes from a CS207 class on software valuation taught by Gio Wiederhold on October 14, 2012. The notes cover several topics related to software valuation including:
1. Parameters needed to value intellectual property like the life of the IP and how it diminishes over time.
2. Assumptions made in quantitative valuation models like intellectual property content being proportional to software size.
3. Factors that influence software growth patterns and total income like price, sales volume over the product lifetime, and discounting future income.
4. How companies allocate income between routine operations, intellectual property generating expenses, and dividends/interest payments.
This document contains notes from a CS207 class on software valuation taught by Gio Wiederhold. It includes:
1. Announcements about new sign-up sheets and the option to write a report to make up a missed class.
2. An example spreadsheet model that calculates the discounted income from selling software over multiple versions, showing that income is approximately $1 million, not the initially expected $25 million.
3. A discussion of alternative business models for software, including charging for ongoing maintenance rather than just the initial sale.
This document contains notes from a CS207 class on intellectual property valuation of software. The syllabus covers topics like why software should be valued, open source software, intellectual capital, principles of valuation, business models, and risks of outsourcing. The notes discuss how personnel are the largest cost for tech companies and represent intellectual capital. Software is the primary intellectual property that is generated by people and embedded in products and services.
Gio Wiederhold proposes linking database results to simulations to better support decision-making. Currently, databases provide information about the past while decision-makers consider future possibilities using separate tools. Wiederhold suggests databases and simulations be integrated using a language called SimQL, similar to SQL, to estimate future outcomes. This would allow seamless access to simulations from databases, merging past data with predicted futures to improve decisions. Several research questions around language design and managing uncertainty over time remain.
This document contains the syllabus for a class on software valuation. The syllabus lists 13 topics to be covered, including why software should be valued, open source software models, principles of valuation, the role of intellectual property, risks of outsourcing, and the effects of tax havens on housing intellectual property. It also provides examples and graphs about software development lags and the timing of expenses and revenues in the software development process.
This document summarizes a lecture on valuing software and intellectual property protection. It discusses why software should be valued, principles of valuation, open source software, market value of software companies, intellectual capital, the life cycle of software innovation, business models, patents, copyrights, trade secrets, risks of outsourcing, effects of tax havens, and protecting trade secrets. Methods of intellectual property protection include patents, copyrights, and trade secrets. Trade secrets must be defended through agreements and prosecuted when violated.
This document provides an overview of the CS207 course on software economics taught by Professor Gio Wiederhold. The course will cover topics related to valuing software, including open source software, principles of valuation, intellectual property, and business models. It lists the main topics to be covered in the 12 lectures. The class meets weekly on Fridays and involves a short written report. 際際滷s and materials from past years are available online. The goal of the course is to help students understand how to maximize the economic benefits of software.
This document outlines the syllabus for a course on software economics. It covers topics such as valuing software, intellectual property, different business models, licensing, and taxation. The course is divided into three parts, with each part covering several topics related to software economics. It emphasizes that software is different from other assets because it requires ongoing maintenance to retain value over its lifetime. Proper valuation of software should account for expected future income from sales and maintenance fees, discounted to reflect present value and risk.