Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Vamshi Krishna (Vamshi_Kassety)
Infosys
AU
Vamshi_Kassety Member since 2013 4 posts
Posted: Feb 15, 2016
Last activity: Feb 17, 2016
Posted: 15 Feb 2016 22:49 EST
Last activity: 17 Feb 2016 14:59 EST
Closed

Best Practise to capture Specifications for Second Application built on a Frame Work

Hi,

We are trying to understand what is best practise to capture specifications for a impl layer? Given we have an FW Layer and specs associated with them. Impl Layer would reuse most of the functionality from FWLayer and specialise a limited functionality.

 

In this scenario, what is the approach should be followed?

 

1. Pull all specifications from FWLayer to IMPLLayer?

2. Pull only the specifications which are supposed to be specialised?

3. Any other way to do this?

 

Also, when should we capture Reporting requirements, is this as part of Inception sessions or during eloborations?

 

We are following PegaSCRUM methodlogy.

 

Thanks and Regards,

-Vamshi

To see attachments, please log in.

Posted: 8 years ago
Posted: 16 Feb 2016 4:07 EST
Phani Sahukaru (sahup1)
Pegasystems Inc.
Phani Sahukaru
Pegasystems Inc.
IN

Pulling only the specifications which are supposed to be specialised makes sense? please share your thoughts/comments, Thank you!

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice