Close the gap between analysis and design
392244
Get robust Book extract, part 3 To get from use cases to detailed design (and then to code), you need to link your use cases to objects. The technique we describe in this chapter, robustness analysis, helps you to bridge the gap from analysis to design by doing exactly that.â¦
189931
Experts in a field can benefit from an outsiderâs perspective.
40560
Editors: Shlomo Reifman and Samantha N. Wong Researchers: Joshua Brandt, Fei Mei Chan,  Andrew T. Gillies, Soo Jeong, Edward Knudsen,  Artie Kwok, John Ray and Jody Yen Programmer: Carl Subick
477249
Find out how one analyst contradicts himself in his report.
455848
By Anonymous  COMBINING WEATHER FACTORS
362483
(Source: Tibco)  So you have a few analysis-savvy experts but a lot of business users needing to solve both repeatable and unpredictable problems. What do you do to scale properly? Using Guided Analytics, expert business professionals can use powerful and easy-to-use data analysis applications to easily and quickly create analysis templates and recommended workflows, thus effectively transferring their best-practice analytics to general corporate users, without IT intervention! That speeds up decision-making by automating common analysis tasks, capturing best practices and providing a framework for distribution of analysis applications to meet the ever-changing needs of their organization.
508803
With the iPhone on deck, it's finally time to see if Apple's vaunted designers have come up with another winner. But first: A pause to focus on developers.
559757
The company needs to focus on its core brand rather than launching new products.
87348
New methods need new measures, and the old ones get new uses.
765964
Delivering the capabilities of traditional EAI products within a light-footprint, standards-based infrastructure supporting incremental integration
270172
Blog: Glaskowsky explains the difference between design flaws and defects.
433593
(Source: Symphoniq) You can't manage what you can't measure.  Learn why traditional performance tools can't deliver the visibility and control required to manage today's complex architectures.  Also learn about key requirements an optimal solution should provide.  View this 5-Minute solution preview.
769015
Felix Geisendorfer shares, in this new post to the ThinkingPHP blog, some of his experiences with writing his code using test driven development.   So far I've had tons of fun trying to create php code using test driven development. It caused my code to become a lot more structured/consistent because writing the tests shows you interfaces problems right away. This is because the process of writing the test forces you to think a lot more about *how* you want to use some class / piece of code vs. your traditional "how can I get task x done"-thinking.   He also points out another benefit - it makes refactoring the code even easier (so there's more of a likelyhood that you'll use it again and again). He talks specifics about a library that he's been working on and the processes he's gone through to make things work with the testing versus his normal development cycle.
389639
There is an interesting post on OnLamp.com that mentions the search for a good wiki system. Read the post to find out why the author thinks that the wiki world "needs the kind of vision that will make the product more accessible, more polished, less prone to abandonment or neglect...", and the several comments that follow.
490298
Nobody writes software entirely in-house anymore. Almost everyone relies upon libraries and frameworks written by someone else. This allows programmers to concentrate on the actual logic of the application and shortens the development time. By Tim Boudreau, Jaroslav (Yarda) Tulach and Geertjan Wielenga. 0611
88066
Making what could happen less of a guess In broad terms there are three key elements to consider in the development of any new application â or any new product, for that matter. The obvious one, certainly from a software point of view, is the technology to be used â the language, the target platform and operating system, and the rest.â¦
184722
On his blog, Nick Halstead shares a few tips he's worked up to help developers that might be having a hard time with coding issues - a few steps towards solving programming problems.   Early on in most people's programming careers problem solving is a large part of your day to day job. As you become more experienced you find that many programming patterns that you have used before can be reapplied. You then start working on larger and larger projects and the problems tend to be more about solving architectural problems rather than logic related ones.   Included in his list are things like "Talking it through", "Brainstorming", "Breaking it down" and "Research". This last one can be one of the most important and can save tons of time in the long run. With tools like Google and other sites, there's no reason to check before you start a project to see if there's someone out there that might have already done it (and it might be more well developed).