Informatics business

Website:	website containing additional information
Course code:	INFOIB
Credits:	7.5 ECTS (=5.25 old credit points)
Period:	periode 2 (week 46 t/m 5, dwz 14-11-2005 t/m 3-2-2006; herkansing week 12)
Timeslot:	D
Participants:	up till now 58 subscriptions
Schedule:	Dit is een oud rooster! form group time week room teacher college   wo 13-15 46-51,2-4 BBL-106 Sjaak Brinkkemper Slinger Jansen     vr 11-13 46-51,2-4 BBL-106 werkcollege   vr 09-17 48-51,2-4 BBL-465 groep 1 wo 15-17 46-51,2-4 BBL-468 vr 09-11 46-51,2-4 BBL-468 vr 13-17 46-51,2-4 BBL-468 groep 2 wo 15-17 46-51,2-4 BBL-461 vr 09-11 46-51,2-4 BBL-461 vr 13-17 46-51,2-4 BBL-461 groep 3 wo 15-17 46-51,2-4 BBL-412 vr 09-11 46-51,2-4 BBL-412 vr 13-15 46-51,2-4 BBL-520 BBL-574 vr 13-17 48-51,2-4 BBL-416 vr 15-17 46-51,2-4 BBL-412
Contents:	After this course the student should: know what developing a software product entails be able to work with the scientific theories of product software be able to start an own software enterprise A software product is defined as a packaged configuration of software components or a software-based service with auxiliary materials, which is released for and traded in a specific market. In this course the creation, production and organization of product software will be discussed and elaborated in depth: Requirements management: functional categorization, prioritization for releases (QFD, AHP), tracing en tracking, scope management Architecture and design: application genericity and typologies, variability, product architectures, internationalization, platforms, localization and customization Development methods: prototyping, realization and maintenance, testing, configuration management, delivery; development teams Knowledge management: web-based knowledge infrastructures, quality improvement programs (CMM, SPI) Protection of intellectual property: ©, ™, NDA, Software Patents Organization of a product software company: business functions, financing, venture capital, partnering, business plan, product/service trade-off, diversification This course is explicitly meant for students Information Science and Computer Science. Pre-arranged or mixed teams are are no problem, it is the product idea what matters. After the course the students can continue working on the product in the Utrecht student software incubator, called Netherware, see www.netherware.nl. Netherware provides product and business coaching, access to the financial network, and the possibility to perform a master thesis project on your own product.
Literature:	Micheal Cusumano: The Business of Software, Free Press, ISBN: 074321580X. Available from A-eskwadraat, and the regular bookshops.
Course form:	This course is run in the virtual software company, called Netherware (see www.netherware.nl). The students form teams around their own product idea, and produce a design and a prototype of the product or service. The students also play a horizontal role in Netherware: Finance, Project Office, Human Resource Management, Technology, Marketing, and Investor Relations. The Netherware company is running during 12 hours of the week; 4 on Wednesday and 8 on Friday. In this time the following activities take place: Work on deliverables, product, or service Workshop with participatory knowledge transfer Progress meetings of the product teams Horizontal role activities Reporting to the Netherware management Presentations of Netherlands entrepreneurs in product software
Exam form:	The course is run as a project, where several deliverables have to be produced. The course grade is a weighted average of the grades for the deliverables and the presentation. Any activity graded below 6 is to be repeated.
Minimum effort to qualify for 2nd chance exam:	Om aan de aanvullende toets te mogen meedoen is ontbreken van ten hoogte 1 toetsactiviteit toegestaan.
Description:	Several documents have to be produced during the course: Project plan Product definition Product architecture Product design or prototype Business plan These documents are reviewed and feedback is given, partly by the horizontal teams. At the end the product vision, prototype and business plan are presented to an external Board of Supervisors, which will judge the proposals for business feasibility.