Login

Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering and documentation of out of the box requirements
Previous Previous
 
Next Next
New Post 3/2/2011 10:00 AM
User is offline piya
1 posts
No Ranking


Gathering and documentation of out of the box requirements 
Modified By piya on 6/30/2011 1:37:11 PM)

 
 
New Post 3/2/2011 5:39 PM
User is offline KJ
243 posts
6th Level Poster


Re: Gathering and documentation of out of the box requirements 

 

Priyat,
Mmmh, Sharepoint: a piece of software for in-house web and content management stuff (not verbatim). Do you really need requirements? No, because you know what the software can do, right?  “We know what we want” and “the software features are well documented” are some of the reasons for not documenting requirements. Let’s extrapolate this to a large ERP where the features are well documented. And lots of these large ERP implementations go belly up. And one of the main reasons for failure is “None or inadequate requirements”.
 
So, the short answer is, you still need formal requirements, defining WHAT the business needs. For example, lets say you’re a Government Agency and you still publish a booklet of jobs (a monthly gazette) and you also publish the same information on the web. You may need to provide:
  1. High-level processes (eg. defining content, approval, creation, version management and publication).
  2. Use-Cases (defining how the user will interact with the system)
  3. Functional requirements (the system shall … phrases)
    1. Non-Functional Requirements (Reliability, the system shall be available 24 x7, except Sunday morning 00:01-04:00 for maintenance)
 
For non-functional requirements (see FURPS at http://en.wikipedia.org/wiki/FURPS). Also cast you eye over these FURPS+ requirements from IBM (see http://www.ibm.com/developerworks/rational/library/4706.html).
 
Warm regards,
K

 
 
 Page 1 of 1
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Gathering and documentation of out of the box requirements

Community Blog - Latest Posts

Jayaram.K
Jayaram.K

DOR & DOD: The BA’s Compass in Agile Delivery

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
Jayaram.K
Jayaram.K

The Business Analyst's Superpower: Bridging the Gap Between Business and IT

In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
Bekka Ball
Bekka Ball

Recipe Redesign: There Is No Box, Only Possibilities

I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 



Upcoming Live Webinars




 

brought to you by Modern Analyst Media LLC enabling practitioners & organizations to achieve their goals using:

Copyright 2006-2025 by Modern Analyst Media LLC