Posted by charlotteb on October 20, 2011 – 10:55 am
There has always been major controversy about how businesses should conduct themselves amongst employees, clients, and the public. Society is constantly changing and manifesting what they consider to be acceptable business practices. And through these ever-changing opinions, we change our views on the types of companies we want to do business with. And one of the more forward thinking ideas is that a business strategy and structure should be transparent, or naked to the public.
Transparency by definition means capable of transmitting light so that objects or images can be seen as if there were no intervening material. So fine in texture that it can be seen through. (http://www.thefreedictionary.com/transparent)
This nakedness/transparency when applied to business allows the public, clients and potential clients to get a very clear understanding of the business they are choosing to partner with, employ or engage. If a business is transparent studies have begun to show that it increases productivity and enhances the ethical workplace culture. One Study by Deloitte in October 2008 published: Read More »
Let’s say you are a key system user or maybe a business subject matter expert. What would you typically tell someone when you explain what you do to accomplish a specific task? How about if you were to sit down train a new employee on a computer system. What information would you give to that new employee so that the employee can better learn how to do the job that needed to be done?
Just like training a new employee for a job, gathering information for software development projects requires a great deal of diligence. Not enough training, or giving a new employee the wrong information, could have a dramatic effect on how that new employee performs their tasks. Gathering the wrong requirements for a software project would have a dramatic effect on the delivery of a valid solution. Due diligence is required for software project requirements information gathering – making sure that the right solution is created for the right reasons. Read More »
Effectively communicating the same message to the many types of stakeholders in a software development project can be a challenge. Semantics used in a communication, such as that of a software requirement for example, can be received and interpreted differently from one person to the next. Often times each recipient will receive a communication however not everyone will have the same common understanding of what is being said.
There are many methodologies, models, and templates that attempt to provide a more cohesive understanding of a software solution design. The 4 + 1 View Model is one such way of describing a software system. Developed by Philippe Kruchten , currently a professor of software engineering at the University of British Columbia, the 4 + 1 View Model is a framework for presenting a consistent look at the design of a software system.
Read More »
