What is the difference? They all are business management solutions. They do the same? Some sort of different editions? Do they use same platform?
Dynamics NAV
Microsoft Dynamics NAV 2009 is a
comprehensive business management
solution that helps people work faster
and smarter, and gives your business
the flexibility to adapt to new
opportunities and growth.
Dynamics AX
Microsoft Dynamics AX 2009 is a
comprehensive business management
solution for mid-sized and larger
organizations that works like and with
familiar Microsoft software to help
your people improve productivity.
Dynamics GP
Microsoft Dynamics GP is a richly
featured business management solution
that allows you to use familiar,
powerful software to operate and grow
your business.
Dynamics SL
Microsoft Dynamics SL is a business
management solution specialized to
help project-driven midsize
organizations obtain reports and
business analysis, while helping
increase efficiency, accuracy, and
customer satisfaction.
Generally speaking each of these products were purchased separately, and Microsoft is kind of trying to put them into a general business, but has not actually integrated them into a common ERP platform (yet anyway). For example, NAV was formerly Navision, GP was formerly Great Plains. I think AX was also part of the Navision purchase, but was a different product that Navision had themselves purchased.
Each has a separate accounting implementation that it came with, so there is a lot of overlap in the non-differentiators like accounting.
Basically they are targeted at different types of businesses. SL is for a service oriented business (like a software consulting firm). NAV would be more targeted at an inventory based operation.
I didn't investigate all of their options in depth to know all of the similarities and differences, but in a former job I had to look into NAV, AX and GP and that is what I recall it being all about.
I agree with Dave Markle, the marketing is engineered to create the maximum possible confusion. The executive suite buys these things and then marketing has to break its head to figure out how to sell and differentiate each one. As you can see, they didn't do a great job.
The marketing-ese is in full effect with the Dynamics products. All these packages were acquisitions by Microsoft, and they are making an effort to bring them to market under one brandname: Dynamics. They are aiming at the SMB market. It's not positioned to compete with SAP. Both are client-server apps.
I've worked with Dynamics SL (previously named Solomon). It's an accounting suite, with modules for Accounts Payable + Receivable, Inventory, General Ledger, Purchasing, Reporting, Cost Accounting, Purchase Orders, etc.
It's all VBA goodness. The database underlying would make your blood curdle. It's denormalized like you wouldn't believe. I guess saying 'denormalized' would indicate that it previously normalized. I got the feeling it was never normalized. Full of technical debt.
Foreign keys are an unknown entity in SL. DBAs would have trouble taking the architecture seriously (e.g. columns actually named like User1 and User2 to indicate a custom field on the User Interface).
Dynamics GP is more oriented towards payroll. I cannot comment on its inner architecture.
They all run on the same platform. Client executables connecting to SQL Server. The forms design is like the Win95 and sometimes Win3.1 paradigm. Don't let the Outlook-like main screen fool you in the screenshot; it's the only one getting the upgrade treatment.
The licensing model is a killer, and so my previous encounter with Solomon had everyone running the same EXE from the network share. It was notoriously slow, and rarely a compliment from users on its responsiveness.
Entire consultancy businesses are built around these products. Supply and demand allow those consultants to charge a substantial amount, relative to the web-app and other line-of-business consultants.
On their "How To Buy" form, there is a "Contact Us"
and I'm completely certain that if you contacted one of the sales reps, they would go into great detail and great length about the strengths and weaknesses of each product.
Keep in mind, they'll be highlighting more strengths than weaknesses, and they'll be highlighting the weaknesses of the lesser priced products. But the sales reps are guaranteed to know the products inside out.
Also, Wikipedia has little write-ups on each of them.
They are mostly similar (sometimes identical) to the blurb on the MS website, but there's also some extra information there.
Related
I want to power a very simple shopping-cart where I will be selling software. I've checked a bunch of them already and still can't find what I need. Most of shopping-carts don't have "virtual product" functionality. Among those that have this feature are PrestaShop and Magento.
Presta doesn't have this feature implemented very well. I don't remember details about what I didn't like in Presta but as far as I remember the feature was not very well implemented: no ability to disable shipping, not possible to specify that people must be able to buy one item only (which is software license), no ability to set endless quantity for the products, etc.
Then I checked Magento, it has this feature implemented almost perfectly (still have to figure out how to disable quantity). However I heard that Magento is rather slow and frankly speaking this software looks like overkill. It has huge number of features and there are many many lines of code while I simply need the ability to register users, let them log in to the customer area and provide them with either download link to the already purchased software or the "buy now" link.
Do you by chances know of such software?
decided to use zen cart after all
I am assessing some tools to manage software develpment projects. Dotproject seems a good one, but i would like to learn of other's experinces using it for software development.
Thanks.
I've been using Assembla for a small team and loving it. The web interface is very elegant, and it gives me power and simplicity at the same time.
My favorite feature is the strong ticketing system which allows me to create tickets on the web, assign them to developers, associate them with other tickets, estimate the time it takes to close the ticket, and aggregate those times graphically. It really shines, though, with its version control and ticket integration. Being able to specify that this commit is related to ticket #45, fixes bug #78, and closes ticket #32 is very nice.
They offer version control hosting for multiple version control systems - including SVN and GIT.
They offer free and paid packages.
For more information, check out their usage videos here.
Oh, and do let us know what you decide and why :)
An old post, I know...
I used to be a core member of the dotproject team and used it for years and set up many organizations on it... ranging from small non-profits and software shops to major government projects. It tended to work relatively well. Unfortunately, due to the crawl of development, half the dotproject team split to form web2project and we've been there almost two years.
At present, we (web2project) does a quarterly release and have done major work on the code. We've closed ~100+ bugs, added dozens of features like iCal feeds, and improved performance by 95% and cut about 1/3 of the code overall. And yes, we have an upgrade path from dotProject.
I've noticed an increasing number of jobs that are asking for experience with data mining and business intelligence technologies. This sounds like an incredibly broad topic but where would one go if they wanted to develop at least a partial understanding of this stuff if it were to come up in an interview?
A very good book with practical examples is the
Programming Collective Intelligence: Building Smart Web 2.0 Applications by Toby Segaran.
Go read Data Mining: Practical Machine Learning Tools and Techniques (Second Edition).
Then use Weka on a pet project. Despite the name, this is a good book, and the Weka package has several levels of entry into the data-m... er machine-learning world.
Consider reading Ralph Kimball's books for an introduction to Business Intelligence.
Also, try to not stick to one technolgy-vendor, every company has its own biased vision of BI, you'll need a 360 overview.
Maybe you can also try to work with real BI - it is almost impossible to get in contact with data-filled and running SAS, MS, Oracle etc. I work in a team which integrates BI BellaDati for enterprises. For try-out and personal purposes it is free with some datastore limitations ( http://www.trgiman.eu/en/belladati/product/personal ).
BellaDati is also used as a learning tool on technical universities focused on practical application of data mining and analysis. The final manager-level dashboards examples of BellaDati can be seen at http://mercato.belladati.com/bi/mercato/show/worldexchanges
You can work here with SQL datasources, flat files, web services and play. From my own experience - to show real samples of market analysis practise (like case study etc.) is good for an interview.
I wish you luck,
Peter
Are there any online repositories of completed real-world projects with their timescales that I can use to callibrate my own development time estimates?
If such a repository existed, how would you expect to correlate your project to find matches?
To expand; every software development project has unique aspects - particularly with regard to project participants - and will therefore have unique dynamics that affect estimates, possibly by orders of magnitude.
To apply past project metrics to future projects and hope they hold up you would need to assume a few things;
Developers are interchangeable (they
aren't)
Building software is like building a house or a brick wall (it isn't)
Project risks are negligible (maybe you'll get lucky?)
Finally, if all you need is a ball-park number then isn't "calibration" overkill? Just ask your most experienced developer how long they think - they are usually in the ball park.
I don't think relating your project to a set of generic other projects to determine a time est. would be hugely beneficial. You can compare to other projects for defect rates - here's a good starting point for that: http://www.scribd.com/doc/7758538/Capers-Jones-Software-Quality-in-2008
My suggestion would be to look at prior projects in your company with the same relative technology and resources and develop a table (via function points) and then a continual resync. If there is no prior info and/or the technology is new and/or the resources are different - then it's best to use the team's prior experience from prior jobs.
Here's a good book: Software Estimation: Demystifying the Black Art
Do you use a wiki in your company? Who uses it and what for. Do you share information between projects / teams / departments or not?
We use ours to store
Coding Style docs
Setup and Deployment procedures for web servers and sites
Network diagrams (what are all the servers in Dev, Staging, QA and Production called etc.)
Project docs (pdfs, visios, excel, docs, etc.) are stored in SVN. For the non-techies we have links to those docs in the wiki that point to an up-to-date share on my box. (tip: some wikis provide source control integration but ours doesn't)
Installation and Setup procedures for development tools
Howto's on things like using our bug tracking system, our unit testing philosophy
When doing research on a topic I often capture the important information in a wiki page for others to learn from
I've seen them used to keep seating charts in medium to large size organizations for the new people
At my previous company all of the emergency contacts and procedures for handling a critical outage where available on the front page of the wiki
The best part about a wiki is that it's searchable. Some wiki's support searching inside uploaded or linked docs as well.
If you setup a wiki and encourage or even require people to use it the amount of information that will accumulate can be amazing. It's definately worth the effort especially if you have someone in IT with some spare time on their hands to set it up.
Do you use a wiki in your company?
= We use it for the purpose of a Knowlede Based. Basically it is a wiki but many more functionalities intagrated.
Who uses it and what for
= Employees. Knowledge Sharing, Preparation of collaborative-documents, etc.
Do you share information between projects / teams / departments or not?
= Depends on the requirements. It is possible to set permissions between users.
We use a wiki, for documenting our systems. It's updated gradually as things update and evolve. It should go without saying that there's benefit in that, however whether you use a wiki or other methods is worth thinking about.
A wiki is great for collarborative editing. The information shouldn't go stale in theory, because as people use the systems they have the opportunity to keep it up to date.
However we have found in our organisation that people struggle a little with wiki markup. Especially tables. I think a solution that has wysiwyg editing would be better if you have non-highly-technical people editing it. Sharepoint springs to mind, but it's expensive.
I use a wiki as my virtual "story wall" for agile development. All of my stories are written and organized in the wiki. While my customers are reasonably local (we can have face-to-face meetings), they aren't co-located. To enable better customer interaction I've resorted to a wiki instead of a wall-based story tracking mechanism. It also works a little better for me due to the fact that I often have multiple, concurrent projects and limited wall space in my cube. In a larger team with more focused projects and more wall area, I'm not sure I'd make the same choice.
My company uses a wiki for project-planing but also for storing documentation and ideas.
I have found that a wiki is a great way to link the programmers in the company with the business-people.
When someone who are not on the programming-team comes up with an idea or finds a bug, it's a loot simpler to let that person document it in the wiki.
I think it's an important aspect for a small company like mine to easily synchronize the business-team with the development-team. A wiki helps with that, since it gives the feeling of being a part of the development process, instead of having to ask the programmer directly about every little detail.
we have MediaWiki to store technical information that is not ready to be published in other formats - specification drafts, diagrams (via GraphViz extension), results of short investigations, etc.
I also think this question is a wiki too :)