Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Adding new requirements in SRS
Previous Previous
 
Next Next
New Post 2/4/2013 12:31 AM
User is offline Chaans
2 posts
No Ranking


Adding new requirements in SRS 

Hi,

I am a newbie in BA field and recently joined an IT company as BA.  Writing SRSs are part of my job role sometimes there will be new requirements to be added into the exisitng SRSs.  Now Iam making another new document with new requirements and adding reference of the old SRS document.  I would need an advise on how to add new requirements into old SRS documents or the way iam doing will do.  Please suggest.

Regards,

CS

 
New Post 2/8/2013 1:42 PM
User is offline Chris Adams
323 posts
5th Level Poster






Re: Adding new requirements in SRS 

CS,

There's probably 10 different ways you could think of to manage new or updated requirements to a system requirements specification document. However, placing all of your new requirements in a separate document hasn't worked well from my experience.

It's typically difficult for a reader of the new and separate document to get a full understanding of the new requirements without the full context of the current spec and surrounding information. Jumping back and forth between documents to get this context is difficult.

If you are using MS Word for your documentation, consider using track changes and simply updating your documentation. Of course, it's always a good idea to have a revision history table where a summation of thew new changes along with who made them and when can be tracked even after the newly tracked changes have been accepted.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Adding new requirements in SRS

Community Blog - Latest Posts

A business analysis checklist helps you stay organized while you work through projects. It includes questions that will help you identify problems in your current processes, and suggest improvements for future projects. Understand the Problem Before you start writing code, you need to understand what problem you're solving. This means u...
I’ve heard “The End is Near!” for Business Analysts for almost 20 years.  Waterfall project management, with its need for formal requirements, is dead…a dinosaur…so 1990’s.  To be honest, that’s mostly true.  With the publishing of the Agile Manifesto in 2001 there was no need for a 2-inch-...
Business analysis is used to identify and articulate the need for change in how organizations work, and to facilitate that change. As business analysts, we identify and define the solutions that will maximize the value delivered by an organization to its stakeholders. We look for opportunities for new business models and new ways to work together. ...

 






 

Copyright 2006-2022 by Modern Analyst Media LLC