In software industry, are URS and SRS outputs of "collect requirement" process?

Submitted by PMzilla_binh on Fri, 11/05/2010 - 07:54

Hi all,

In software industry, are URS (User Requirement Specs) and SRS (Software Requirement Specs) are considered Requirement Documents that user will use during "verify scope"

However, these 2 documents are usally carried after project planning phase and they make take significant time to process. So they should not be in "collect requirement" which is in Project planning phase.

Can someone advise me on this?

Thanks

Binh

Forums: 
General Discussion
  • Log in to post comments
  • 2371 reads

cuongpt

Fri, 11/05/2010 - 18:55

I first want to ask you a question in order to clarify your idea:

Do you think that those documents should not be in Collect Requirement process bcoz they take significant time to process?
 

PMzilla_binh

Sat, 11/06/2010 - 01:08

Hi Cuongpt, thanks for your reply.

I understand plannning phase can be carried throughout the proj life, so if an activity can take long in planning phase is still ok. However, the collect requirement outputs are the inputs of scope baseline which is usually completed much earlier than that so that other activities like design/prototype/test plan can be carried out.

In my prj experience, mapping with PMI scope management process, after the "collect req" phase, we come out with a blueprint document, which will be be approved and baselined. Then we'll carry out further analysis to come out with URS/SRS.

To this mapping, I'm thinking URS/SRS are more a output of "execution" phase than "planning" phase

Kindly help to advise. Many thanks!

Binh

cuongpt

Sat, 11/06/2010 - 17:44

It's still a little bit complicated in the way you explain.

Tell me, what are the purposes of blueprint document and of URS/SRS?

Who and when they do those documents?

PMzilla_binh

Sun, 11/07/2010 - 10:16

The blueprint document describe business process of the system, high level non-functional.

SRS will break down the each business process in blueprint into use cases  and define detail logic level in each use case.

Taking example in web application, a business process defined in blueprint "system allow to manage user", in SRS, it breaks to some use case like "create user", "update user detail", "delete user", etc. In the "create user", SRS may define how the field will be layout, maximum length of a field, the default value for a text box, etc.

And of course, SRS need the signed-off customer before the system is built.

Hope it clearer

In fact, in software, when we mention about scope, usually it's a high level rather than very detail like URS/SRS. I'm still thinking how to map this with Scope management process in PMI. Thanks

cuongpt

Sun, 11/07/2010 - 16:09

I got it. So SRS is a deliverable. It's defined in WBS and produced in Executing Process Group.

 

PMzilla_binh

Wed, 11/10/2010 - 00:29

Thanks Cuongpt! I'm clear now.

it's also aligned with what I guessed during picking up this