Lecture

Identifying & Evaluating Business Opportunities

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

Description

This lecture covers the core elements of new venture creation, focusing on business opportunities as the foundation for shaping a firm's identity. It discusses the roadmap for opportunity exploitation, the importance of technological fungibility, and market opportunities. The instructor emphasizes the evaluation and testing of potential target markets through prototyping, research, cost estimation, pricing, and customer outreach.

In MOOC

Launching New Ventures

Sharpen your “entrepreneurial mindset”. Launching New Ventures, a course about Entrepreneurship & Strategy for Technology-Driven Startups, is designed for professionals, entrepreneurs, and students who want to learn about how to successfully launch a new business. Through short, animated lectures, inspiring interviews with successful entrepreneurs from around the world, quizzes and suggested readings, students will gain a broad overview of entrepreneurship strategy with insights they can apply to their ven

Official source

Ontological neighbourhood

Computer engineering

Software development: Software development process

Related concepts (32)

Software testing

Software testing is the act of examining the artifacts and the behavior of the software under test by validation and verification. Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not necessarily limited to: analyzing the product requirements for completeness and correctness in various contexts like industry perspective, business perspective, feasibility and viability of implementation, usability, performance, security, infrastructure considerations, etc.

Acceptance testing

In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve chemical tests, physical tests, or performance tests. In systems engineering, it may involve black-box testing performed on a system (for example: a piece of software, lots of manufactured mechanical parts, or batches of chemical products) prior to its delivery.

Unit testing

In computer programming, unit testing is a software testing method by which individual units of source code—sets of one or more computer program modules together with associated control data, usage procedures, and operating procedures—are tested to determine whether they are fit for use. It is a standard step in development and implementation approaches such as Agile. Before unit testing, capture and replay testing tools were the norm. In 1997, Kent Beck and Erich Gamma developed and released JUnit, a unit test framework that became popular with Java developers.

Integration testing

Integration testing (sometimes called integration and testing, abbreviated I&T) is the phase in software testing in which the whole software module is tested or if it consists of multiple software modules they are combined and then tested as a group. Integration testing is conducted to evaluate the compliance of a system or component with specified functional requirements. It occurs after unit testing and before system testing.

System testing

System testing is testing conducted on a complete integrated system to evaluate the system's compliance with its specified requirements. System testing takes, as its input, all of the integrated components that have passed integration testing. The purpose of integration testing is to detect any inconsistencies between the units that are integrated together (called assemblages). System testing seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.

Related lectures (64)

Design Thinking and Business Models

Covers design thinking, innovation process, business models, and value creation in a modern context.

Testing Actor Systems

Explores testing actor systems, covering principles, Akka's Test Kit, dependencies, interaction with the parent, and actor hierarchies.

Software Quality: Managing Defects and Testing Strategies

Explores managing defects, testing strategies, and challenges in software quality, with real-world examples and case studies.

GoogleTest, Pytest, Git Submodule/Subtree, Python os.path

Covers Google Test, Pytest, Git submodule/subtree, and Python file manipulation.

Concept Selection and Tradespace Exploration