Business Analyst Community & Resources | Modern Analyst

The Community Blog for Business Analysts

Systems Analysis

NO Image:

Dahlia Biazid

The Need for a Recipe

Everyone knows what use cases are and their use in the software requirements process. We all know there are many ways to write them: logical, physical, to describe a manual procedure or an automated procedure. The purpose of State Diagrams is well-known to everyone in the field. They help us define the transitional lifecycle of an object moving and...

1 Responses

This entry was published on Sep 13, 2012 / Dahlia Biazid. Posted in Use Cases, Systems Analysis, Business Analysis, Getting Started as a Business Systems Analyst, Technical Topics. Bookmark the Permalink or E-mail it to a friend.

Seilevel

Challenges with User Stories

A Promise to have a Conversation I’ve been writing user stories for a couple of years now, and the best way I’ve heard how to describe them is that they are a promise to have a conversation. Enough information should be written down to give the reader an idea of what the gist of the story is (and to be able to roughly estimate a story point ...

1 Responses

This entry was published on Nov 22, 2010 / Seilevel. Posted in Business Rules, Systems Analysis, Business Analysis, Agile Methods. Bookmark the Permalink or E-mail it to a friend.

Craig Brown

Abandon the use of Non Functional Requirements

This model is provided by Don Firesmith of SEI. Note the lack of an NFR category. More

4 Responses

This entry was published on Sep 24, 2009 / Craig Brown. Posted in Requirements Analysis (BABOK KA) , Functional Specifications, Systems Analysis, Business Analysis, Structured Systems Analysis (DFDs, ERDs, etc.). Bookmark the Permalink or E-mail it to a friend.

Gil

Agile Business Analysis using UML

Following the lead of another forum, where the question was asked about the use of UML by Business Analysts, I would like to ask the same question when we come to Agile Analysis. The answer is NOT simple and like all professional questions needs analysis. This means, I shall post a series of these blog pages, expanding one point at a time. I will ...

1 Responses

This entry was published on Feb 26, 2009 / Gil. Posted in Unified Modeling Language (UML), Systems Analysis, Business Analysis, Agile Methods. Bookmark the Permalink or E-mail it to a friend.

Craig Brown

Invest in User Stories

User stories have a place in modern requirements management. They may not be going to replace use cases but you shoulod know how to write them well. Invest In Good User Stories View SlideShare presentation or Upload your own. (tags: agile scrum)

0 Responses

This entry was published on Jan 09, 2009 / Craig Brown. Posted in Requirements Management and Communication (BABOK KA), Functional Specifications, Systems Analysis, Agile Methods. Bookmark the Permalink or E-mail it to a friend.

Craig Brown

How to write Entity Relationship Diagrams

E R Diagram View SlideShare presentation or Upload your own. (tags: er diagram)

0 Responses

This entry was published on Aug 29, 2008 / Craig Brown. Posted in Data Analysis & Modeling, Systems Analysis, Business Analysis, Domain Modeling. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade - that's all 13 Principles of mine: do you have any? win a free copy of my book.

Thirteen is all you need, at least in this point in time. I may add to them as time goes by, but I would also like to hear from readers if they have any suggestions or thoughts or their very own principles for IT Projects success. Pleae offer them and maybe we can get them into the second edition of the book...which you all remember is available at...

0 Responses

This entry was published on Jun 17, 2008 / David Wright. Posted in Systems Analysis, Business Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 15 - Principle #13: Use Architecture to Manage and Integrate the Deliverables

13. Given many medium to small software Deliverables, use Architecture to manage and integrate the Deliverables into a complete system. This is a more specific statement of Principle #3; in Cascade, an Information System Architecture is used to integrate the two week deliverables, until a complete deliverable (component, sub-system) is assemble...

0 Responses

This entry was published on Jun 13, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 14 - Principle #12: Parcel work into two-week periods

12. Within the three month phase, parcel work into two-week periods; analyze for 2 weeks, then design and develop for 2 weeks (two developers), and then test for 2 weeks. When the first 2 weeks of analysis is done, start the next two weeks of analysis in parallel to the design/development; carry on in cascading 2 week periods until the entire proje...

0 Responses

This entry was published on Jun 09, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 13 - Principle #11: Partition large projects into 3 month phases, that is the longest period you can plan for without the chance of significant change

#11. Partition large projects into 3 month phases, that is the longest period you can plan for without the chance of significant change to priorities, resourcing, etc. I was lucky to learn this early in the 90's as Project Management was getting a higher profile, accompanied by the increased use of Microsoft Project. Other PM tools wer...

0 Responses

This entry was published on Jun 05, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

Page 2 of 4

First Previous 1 [2] 3 4 Next Last

Modern Analyst Blog Latests

Jarett Hailes

Three Audacious Goals for Business Analysts in 2013

As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...

Howard Podeswa

Hey IIBA, What’s Up With That?

Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...

Adrian M.

BA ABCs: “C” is for Class Diagram

Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN