Entries for February 2013

21209 Views
33 Likes
11 Comments

Has “Agile” killed “Use Cases”? Let us answer this question in this short article. As you may know, “Use Cases” have been a great way to document the detailed “Functional Requirements” of a system.
 

30275 Views
21 Likes
1 Comments

This article describes the Entity Relationship Diagram that allows you to document the structure of a database in terms of persistent entities and the relationships between them.  The Entity-Relationship Diagram (ERD) provides a way of graphically representing the logical relationships between entities in order to create a database schema to persist those entities.

8380 Views
9 Likes
0 Comments

Three questions regarding breaches of business rules should be addressed by Business Analysts: enforcement level, guidance message, and breach response. The goal is context-dependent, pinpoint reaction to breaches in real-time. Addressing breaches intelligently is key to creating friendly, agile, secure business solutions, ones that can evolve rapidly in day-to-day operation.

16553 Views
21 Likes
5 Comments

This article reviews the complexity of the role of the business analyst (BA) facilitator in obtaining a stakeholder agreement (i.e., a consensus or a compromise) on solution features and/or user requirements. The BA facilitator achieves this agreement by maintaining a neutral posture in guiding the stakeholders though a dialogue in a series of meetings.

7137 Views
1 Likes
0 Comments

Before an organization releases a new piece of software or web feature to all of its customers or the general public, it will generally offer a limited audience a chance to test drive the feature and offer their feedback. This is generally known as a Beta launch...

9349 Views
5 Likes
0 Comments

Many BAs wait until their requirements specification is complete before they present it to some reviewers. Busy developers, testers, project managers, and users have difficulty finding the time to scrutinize a large document on short notice. It’s far more effective to review an evolving document incrementally. Give reviewers just a few pages at a time, preferably soon after an elicitation activity.





Latest Articles

Be the bird in your projects to become a better BA
Aug 11, 2019
0 Comments
The reason why top performing business analysts tend to be so effective in complex projects, even when their domain knowledge is limited, is because o...

Copyright 2006-2019 by Modern Analyst Media LLC