What does the System Architecture section of a User Requirements Document Supposed to have?

[Jabroni]

What am I supposed to put into this section of a User Requirement Document?

Are there any project managers out there who can help me out?

 

[EagleKeeper]

Should contain the overall interaction of the S/W "pieces" which have been indentified and indicate in general how they should fit together. H/W interfaces should also be identified.

This is a high level section to generate and overall idea on how the package will operating.

 

[Argo]

Yup, I second what eagle said.

 

[Jabroni]

Thanks. Should I divide into any sub-sections?

 

[lordex]

Noting that you are preparing a User Requirements document, in the System Architecture section you might want to be identifying the system architecture as part of user requirements, e.g., what are the existing architecture? are you expected to keep them, replace them, or have your new system working with them? etc.

In other words, you might not want to elaborate the architecture of your future system for too much in your user requirements, unless there are something specific from the user that need to be captured.

Just my 2 cents.

 

[EagleKeeper]

My feel is that if you have to create sub-sections (unless required by some external authority), you are putting to much detail into this area.

 

[Jabroni]

Thanks

General is better anyway...