Andrew Stopford's Weblog

poobah

Sponsors

News

Articles

Family

Old Blogs

Functional specs

If you have used a methodology like the V-Model then the concept of functional specs and SRS (Software Requirements Specification) documents you may know. I have seen a few posts that ask, do we need them and can visual interface lead design be a better approach. I could be missing the point but an SRS in the scheme of the V-model is critical, high level design leads low level design. Create the use cases, realize the objects and the object flow. Know this information going into your high level design and let your testing mirror your levels. Using this methodology depends on you, its a tool and you use the best tool for the job. User interface lead design I would consider in the agile world/RAD world. I disagree that functional specs are the for big companies, they are useable in medium to small project teams, it really depends if you want to know where your going before you get there.

Comments

Jeffrey Palermo said:

"User interface lead design I would consider in the agile world/RAD world."

Are you a RAD coder and an agile coder? I don't understand how you can make that comment? In agile, if you have a UI mockup but no user stories or specs, how can you develop a system?

As far as RAD goes, there are no rules. Get it out fast, period.

For CMM, the SRS is king. Nothing gets done without it. The SRS can be a big, bloated bunch of no value in the hands of the wrong project manager, or it can be used effectively with agile methodologies if it is trim and to the point and includes the relavent user stories.
# March 28, 2005 1:20 PM

Andrew Stopford said:

"Are you a RAD coder and an agile coder?"

I do them all thanks. However I am commenting on the world of BPUF/CMM.

"In agile, if you have a UI mockup but no user stories or specs"

At what point did I say anything about no stories or specs. I know full well that UI mockup in the world of agile is as important as any other methodology.

# March 29, 2005 12:41 PM