Apr 26 2013
Months after a successful dimensional data mart deployment, I was informed end users were unhappy. The users were apparently dissatisfied with the slowly changing dimension component of the solution. Improper product names continued to appear on reports because those products were named incorrectly when they were sold. End users wanted the products sold to reflect the proper product names rather than some earlier erroneous version of the product names.
Apr 26 2013
If any of the following are true of your unit tests, you might not be following some simple guidelines for effective unit testing:
- I can't test that because it is static/void/private.
- My unit tests take too long to run.
- My test fails if the database/webservice/system is down.
- My unit test's Spring configuration file is out of sync with production.
Unit testing can be fairly simple to implement with immeasurable value for both the customer and the implementing team. Unfortunately more often than not, basic principles and tools that can help prevent these problems are not being applied.
What follows are proven guiding principles to successful unit testing.
Apr 25 2013
When the first brick and mortar bank was created, bankers had just one customer touch point – the branch. Then came direct mail, the phone, ATM, online, and mobile channels. The new channels have created a scattering effect that is rippling across the industry: “In 2012, consumers in the US who opened financial products reported that they opened 37% of those products online, 2% by mobile, and 40% in a branch. Online sales have increased seven percentage points since 2010.”  General adoption rates for mobile were above 40% in 2012 and is expected to increase to 50% by 2015.
Apr 22 2013
We’re up in Reston at the No Fluff, Just Stuff conference from April 19-21 learning about a myriad of open source technologies, design patterns, architecture techniques, and just about everything else that a bunch of IT geeks would want in a tech-heavy weekend. We’ll be following up on the cool seminars, speakers, and topics in the coming weeks, but we want to single out a few really interesting ideas and concepts covered each day while they’re fresh on our minds.
We’ll be covering a list of highlights that seemed most impactful, valuable, or interesting each day. Don’t expect anything too comprehensive; if you’re intrigued, feel free to research more on your own, or look out for detailed blog posts on some of these topics as our group has a chance to further digest and follow-up on everything learned.
Here are the highlights from Day 2:
Apr 20 2013
I’ve spent the past several years as a business systems analyst on multiple SharePoint projects for clients across numerous industries. A wide range of functionality is made available to users simply by installing SharePoint. Understanding what the platform can deliver right out of the box will really help an analyst during enterprise analysis, solution assessment and validation, elicitation, and requirements analysis activities. However, gaining that subject matter knowledge can be real a challenge.