Entries for May 2008

9890 Views
2 Likes
1 Comments

In a nutshell, the concept of "stepwise refinement" is to take an object and move it from a general perspective to a precise level of detail. Architects have used such an approach for years, as have engineers building products. But to do so, they realized they cannot simply go from the general to the specific in one felled swoop, but instead, in increments (steps). The number of steps needed to decompose an object into sufficient detail is ultimately based on the inherent nature of the object. To illustrate, for architects designing a building, the typical steps include:

  1. Develop artist rendering (to consider viability).
  2. Design foundation and superstructure.
  3. Design Floor plans.
  4. Design electrical and plumbing diagrams.

Author: Tim Bryce

12450 Views
3 Likes
1 Comments

“The biggest risk to your company is not being able to change fast enough… Business Rules are the answer.” …Ron Ross

I am a great appreciator of Mr. Ross. He has written extensively on the topic of Business Rules, offers excellent training on the subject, and is the keynote speaker at each year’s International Business Rules Forum. I would like to start my own article on Business Rules with an ‘icebreaker’ he used on a seminar I attended.

Consider the sport of American Football. Some aspects of the game are very stable, some less so, and some not necessarily stable at all.

Author: David Wright

7420 Views
2 Likes
2 Comments
Is there a place for business analysts in IT today? Not if their primary function is just to analyze business needs. As the pace of change accelerates, business people want more than analysis; they want workable solutions to their problems. Analysis is only part of the job that needs to be done. It can clarify situations and trends, identify pr...
5544 Views
0 Likes
0 Comments
Most line-of-business execs, project managers and software developers who have worked on application development teams can attest to the importance of good business analysts. In many instances, in fact, today's business analyst can affect the outcome (good or bad) of a software project. "When business analysts aren't able to carry their weight, it...
4635 Views
0 Likes
0 Comments
Software security remains a hot topic. Everyone from grandmothers to Fortune 500 companies has heard the stories of identity theft, data loss, and general mayhem caused by viruses and attackers on the Internet. In the first quarter of 2008 alone, 1,474 different software vulnerabilities were reported with only 64 of them having posted solutions. Th...
5178 Views
0 Likes
1 Comments
Systems and processes are integral to business today but are still difficult to implement successfully. Successful processes and systems are those that meet the business requirements. Businesses utilise these technological and intellectual assets to create value for themselves. Performing analysis upfront ensures the business requirements are m...
7887 Views
0 Likes
0 Comments
How do the professions of project management and business analysis create their work synergies? It’s all about process. The process of successful project execution is reliant upon the business analyst providing the correct inputs to the project that the project manager uses to manage the entire delivery of the project. In short, the business analys...
9861 Views
1 Likes
0 Comments

The short answer: "Because it requires work."

The long answer: People tend to resist gazing into the crystal ball and prefer to react to life as it passes them by. Some people believe planning in today's ever changing world is a waste of time, that you must be more "agile" and accommodate changes as they occur. As anyone who has designed and built anything of substance knows, this is utterly ridiculous. We would not have the many great skyscrapers, bridges, dams, highways, ships, planes, and other sophisticated equipment without the efforts of architects and engineers. Without such planning, our country would look essentially no different than how the pioneers first discovered the continent. Although we must certainly be flexible in our plans, and we will inevitably make some mistakes along the way, little progress would be made if we did not try to plan a course of action and control our destiny.

People often take planning for granted, that someone else will be making plans for us, such as government officials, our corporate management, or even the elders of our families. Consequently we become rather lax about looking into the future. Nor is there any encouragement by anyone to plan our affairs, such as a tax break. Whereas other countries offer incentives to save money for the future, such as Japan, America does not. Therefore, planning is a rather personal activity; we either see the virtue in doing so or we do not.

Author: Tim Bryce

180177 Views
67 Likes
7 Comments

As a software architect and developer I’ve used Enterprise Architect (EA) from Sparx Systems (www.sparxsystems.com) for a number of years. In that time I’ve spent considerable time and energy trying to get our business analysts to do the same. While I’ve had some success I must admit it’s been an uphill battle. I suspect this is partly because EA is often seen as a technical person’s tool. And that’s not altogether surprising.

  • Enterprise Architect – the name itself is completely misleading. EA is not only for people with the title ‘Enterprise Architect’. It’s for the entire project team, from BA’s to Testers and even for Clients.
  • User Interface – for developers the user interface of EA is extremely familiar and intuitive. It looks like a lot of the tools they use already. For non-technical users more familiar with tools like Microsoft Office it is somewhat more intimidating.

So, if you’re a Business Analyst looking for a tool that can help you do your job more effectively then read on.

Author: Andrew Tokeley, Development Manager, Intergen Ltd
You can read Andrew's blog at:
http://andrewtokeley.net

12235 Views
1 Likes
0 Comments

The latest progression in software development methods is the agile approach. Its growing popularity proves how effective it is. But two extreme—and even dangerous—views have arisen about agile development. One is that you don’t do requirements at all when you’re working on an agile project. The other is that you don’t need good requirements practices.

In truth, agile development processes are based on good practices. Most of them are not new but are being reconfigured, along with good product development, engineering, and project management practices. In my work with agile teams, I’ve noticed a number of key practices.

Author: Ellen Gottesdiener, Principal Consultant, EBG Consulting, helps business and technical teams get product requirements right so their projects start smart and deliver the right product at the right time.

7393 Views
1 Likes
0 Comments
A new Forrester report sheds light on this little known, often misunderstood but critical liaison role that can unite the business and IT on enterprise projects, systems development and business strategy. For two decades, the CIO has been viewed as the ultimate broker between the business and technology functions. But while that may be an accurate...
7482 Views
1 Likes
0 Comments
Everyone knows who the business analysts are in their organization, but not everyone knows what they actually do and what they are responsible for during software implementation projects. Anyone who has ever worked on a complex and lengthy software development project knows that the involvement of a business analyst can mean the difference between...






Latest Articles

The Secret is in the Wings
Nov 29, 2020
0 Comments
I could not help but observe in awe the agility of this monstrous wing. My mind could not stop analyzing how an airplanes uses the agility of its wing...





Copyright 2006-2020 by Modern Analyst Media LLC