SRS for RUP

[Dilshan Edirisuriya]

I am in a process of creating a SRS and I follow up the RUP process. I have following issues regarding the creation of SRS.

1) Do I need to add traditional diagrams like context, DFD and ER. If so what are the needed diagrams I should add.

2) What are the UML diagrams I should add in the SRS.

3) When writing use case descriptions does it require to describe the design level factors such as forms, interfaces, links, buttons etc. in the use case description.

There are plenty of SRS templates in the internet but I could not find a standard one. The structure varies from one to another. Please I need a proper/standard SRS template to achieve my requirement.

Thank you

[Jeanne Boyarsky]

What does SRS stand for?

[Dilshan Edirisuriya]

I know what SRS stands for. But these days SRS get messy. People add things based as they wanted without considering about the structure, format or its intended use. These are some areas I have identified in SRSs. Some of the areas have above diagrams but some do not have.
To stay in a specific accepted format I would like to get feed back on above points.

Jeanne Thank you for reply.

[Ilja Preuss]

I assume that it means Software Requirements Specification in this case.

[Dilshan Edirisuriya]

Originally posted by Ilja Preuss:
I assume that it means Software Requirements Specification in this case.

Me too. But most of them do not. As an example try this link. It contains various diagrams.

http://www.cim.mcgill.ca/~limh/Ta321/SRS_Slide.ppt

So please I need your feed back.

[Jeanne Boyarsky]

Originally posted by Dilshan Edirisuriya:
I know what SRS stands for.

I know you do. That's why I asked in this thread. Also, I can't open the link. PowerPoint Reader says it is a macro-enabled PowerPoint document file and just prompts me to save it. And I'm not inclined to spend time fiddling with a tool to figure out what you are asking. This is really a tip to you: make it easy for people to answer your question by providing the information they will need to understand it. Now granted I likely don't know the answer, but others who do could be deterred.

Ilja: Thanks for expanding the acronym.

[Ilja Preuss]

Who is asking you to write that specification, and with what goal?

[Dilshan Edirisuriya]

Sorry for not expanding the word. Initially I figured out it as a sarcastic statement.

Back to the thread. The intended System Requirement Specification is for a student registration system.
[ November 15, 2008: Message edited by: Dilshan Edirisuriya ]

[Don Solomon]

I thought we were talking about a Safety Restraint System. That is what it says on my Toyota steering wheel (SRS).

Glad we got that cleared up.

[Ilja Preuss]

And who is asking you to write that specification, and with what goal?

[Gabriel Claramunt]

If you're required to follow explicitly RUP, you should use the template provided. Usually, an appropriate set of UML diagrams will do the job.
Although I agree with Ilja: what are you trying to communicate and to who? That will determine the content of the SRS.

[Dilshan Edirisuriya]

Thank you for your reply.
I am focusing on a student registration system and it will for a university. So I am trying to communicate the benefits or features of automated registration system comparing to the manual process. To clarify that process I am bit confused about the content I should add. I was stuck on following issues.

[Ilja Preuss]

OK, to show the *benefits* of the system, I don't think you need a requirements specification. What you need is a very high level *vision* of the system, and a rough Return Of Investement analysis.

[Don Solomon]

Sounds like to me you need to perform a Workflow analysis and not the details of software development. More importantly, a manual process is going to be replaced with automation. What you are taking about is the possible elimination of jobs in the registrar. Most of the time this is not well received by employees or even management. You can make lots of enemies very fast. Just be sure that this is something that has been requested from upper management and not just some brainstorm you had.

[Dilshan Edirisuriya]

Client requested a System Requirement Specification. So I have to come up with a SRS. So I need to clarify above issues.

[Gabriel Claramunt]

If the client requested it, ask them to provide a template or at least what they expect on it.
In RUP, usually the SRS is replaced with the Vision document and the Use case specification. (Some time ago, I posted some samples in my blog)

[Dilshan Edirisuriya]

Thanks Gabriel.
Well well. That sounds interesting. So does it mean that the Software Requirement Specification is totally replaced by the Vision document when it comes to RUP?

Need others feedback as well......