I usually write a Software Requirement Specification (SRS) Document, which mainly has the following sections (functional requirements  as use cases, non-functional requirement and the constraints),, but most of the clients i am meeting with told me that this kind of document should be named as Business Requirement Document (BRD) rather than SRS. So is this right?

Second question i need to include more technical details about my software such as Database diagram, Entity relation diagram, architecture diagram and the user interface ,, so on which document i should provide these technical information ??

 Hi John,

About your first question:

A document containing the specification of system behaviour (either automated or manual or both) to solve problem or realise the business opportunity that document is considered as Solution Requirement Specification.  Use cases can be used to derive the requirements for both business and solution requirements. Sources of both requirements and intention of them are different. BA should have defined Business Requirement Document as early as possible in the project phase. This will assist in many future activities and it is of great assistance when you are following Business Motivation Model.

Your client request of renaming solution requirement document to Business requirement may be due to many reasons:

·          Client might be too technical and they understand clearly what you have documented in SRS

·          Client might working on ROI through your solution document instead through goals/objectives that will be met through executing this solution

Client intention of renaming this document to BRD can only be understood by understanding their intention of renaming.

About your second question:

Solution implementation requires many other artifacts depending on the complexity of the project, business analysis approach planned, solution implementers’ knowledge level on the requirement, etc. These artifacts can be documented in many tools, for example User Interface in PowerPoint slides, Data Flow Diagram and ERD in Rational Rose UML diagram, Process Diagram in Visio. Delivery of these artifacts to different stakeholders including solution implementers depends on communication channel you chose to deliver, that means if the solution requirements needs to understood mainly by reading the solution document then one can include these documents’ references in the Solution Document’s requirement section. If the communication channel is “Consulting model”, which is of more collaborative approach than document analysis then other artifacts can be delivered independently with a sheet of bibliography. Approach is always defined depending on the objectives and planning of the Project Team.