Michael Nielsen has worked at Navision Software since 1987, holding several roles including product manager and director of product development. In 2002, Navision merged with Microsoft and Nielsen became the product unit manager of Microsoft Business Frameworks. He discusses the history of Navision, from its origins in 1985 to its merger with Microsoft in 2002. Navision grew to have local companies in 30 countries and partners in 94 countries by distributing its financial software worldwide. After the merger, Microsoft Business Frameworks was integrated into the Visual Studio development environment to leverage its familiarity and development tools.
1 of 18
Downloaded 19 times
More Related Content
From Navision To Microsoft
1. From Navision To Microsoft February 13, 2004 Michael Nielsen, Product Unit Manager Microsoft Business Framework, Copenhagen
2. Michael Nielsen CV 1986 Master of Science in Engineering (DTU) 1986 UNIX Developer with Knudsen & Johnsen 1987 Joined Navision Software 1987 Developer, Navision 1.x report writer 1989 Developer, AL-Language 1990 Developer, Navision 3.x IDE 1993 Program Manager, Navision Windows client 1995 General Manager of Tools department 1997 Director of Product Development 1998 Director of System Architecture 2000 Director of Navision Research 2002 Product Unit Manager, MBS Frameworks 2003 Product Unit Manager, Visual Studio
10. Navision Financials - Standard UI Windows 95 look and feel Compatible with Microsoft Office Microsoft Access like development tools Microsoft logos
11. Navision Financials 1.0 - Released Product (1995)
12. Navision Around the World Local Navision companies Partners Navision reached companies all over the world. In 2002 Navision had local companies in 30 countries and partners in 94 countries.
16. Moving to Visual Studio (2003) Microsoft Business Framework is part of Visual Studio! Leverages the familiarity of Visual Studio Introduces abstractions related to the application domain Guides the developer (“prescriptive-ness”) Uses the model as a master – not the code Keeps the freedom to code Uses concepts from Intentional & Aspect oriented programming