Preview of the IIBA Toronto Chapter Members Area - Feature Article

NOTE

This is a special preview page showing typical content that is available to Members of the Toronto Chapter. For more information on how you can join the Chapter and gain access to the live version of this functionality, click here.

Click the Red Carpet to return to the Preview Main Page

by Jason Questor, Toronto Chapter President
© 2007 Jason Questor

Modeling of business information systems has come a long way in the last sixty years, not all of it smooth. From the original scribbles of 1940's logic flows, through 1974's big bang in structured design, and later the evolution of the Unified Modeling Language and Business Process Modeling Notation, modeling remains an area of great debate. In some cases, there is almost religious fervor  attached to syntax by adherents to a particular modeling technique. The only thing most business and systems professionals agree on is the importance of modeling. Sadly, when you say model to many people, they immediately think only of diagrams. An effective model is a lot more than a diagram. It is a synthetic detailing of something that currently may be only an idea or abstraction. An effective model is a critical communication tool that allows us to share a vision, establish a common goal and manage expectations. This article covers the typical components you should include in your models.

Join today to read the entire article.

by John Slater, Vice President Membership Services

The Problem

Those of us who have worked as Business Analyst, System Analyst, Business Systems Analyst or any other version of these terms for different companies have come across a number of different ways to label requirements.  There are Business Requirements, User Requirements, System Requirements, High Level Requirements, Detailed Requirements, Software Requirements, Functional Requirements, Non Functional Requirements, Technical Requirements, Specifications, Customer Requirements and other similar terms.  There are also a number of other labels to identify “Requirement Like” items such as Business Rules, Constraints and Success Criteria.

 Join today to read the entire article.