BossTalks.com Topic: Project scope: requirements

white on "Project scope: requirements"

white — Sun, 18 Mar 2007 15:30:26 +0000

Do you mean user requirements is a requirements gathered from a client? In this case you are correct, but you missed the original question then. :)

(read more)

melan on "Project scope: requirements"

melan — Sun, 18 Mar 2007 14:08:28 +0000

You are right I was too lazy to find out more types of constrains. Practically I'm not sure that it was obligatory. Main idea of my post related to User requirements. I wanted to point that the type of requirements is the base for any type of software development.

(read more)

white on "Project scope: requirements"

white — Sat, 17 Mar 2007 18:27:13 +0000

I don't know what projects are you working on, but it's strange that you have only so-called User requirements and Constraints, which you see only as a hardware requirements. Where should fit the requirements for OS, support, maintenance, software architecture, deployment procedure, etc?

(read more)

melan on "Project scope: requirements"

melan — Sat, 17 Mar 2007 15:50:24 +0000

The requirements are User requirements... Practically the requirements are the base for the whole development.
So just you need to ask your future customers: Hey guys! What do you want to see in the software when it will be ready?.. Also you need to make analysis of the other same products available on the market and note key features of the products. As the result you will have "user needs".
Another part of the work is to collect constrains. I tried to think out more then 2 of the constraints sources but I have only two: limitations related to physical world like light speed and limitations related to the computer world like speed of CPUs available now

(read more)

white on "Project scope: requirements"

white — Thu, 15 Mar 2007 07:58:47 +0000

You are really wrong in your point. There is nothing abstract in either functional or non-function requirements. These are definitions which are used to be the part of common terminology for years. The functional requirements are requirements which are absolutely required by the project and specify what the project or product should do. The non-functional requirements demonstrate the properties that the project or product should have to do what it must do (in other words to follow the functional part).

I know sometimes people tend to say that it doesn't matter how do you call the thing unless it does its job, but would you imagine if everyone would name the dog in a different way? It leads to chaos and absolute no-way for your career growth. But don't miss my point. There are different statements for what are those requirements, and all of them are coming to a single point. Besides, the standards are really important in the business.

(read more)

krivitsky on "Project scope: requirements"

krivitsky — Thu, 15 Mar 2007 04:47:57 +0000

my experience shows that it doesn't really matter how you call the pieces of requirements as long as you're staying focused on the end users' needs.
if you have your users by your side while moving iteratively and incrementally - eventually you'll have all the *needed* pieces of requirement there.

an excellent activator for us is user stories.
they keep us thinking on the users needs instead of more abstract constraints vs. functional vs. non-functional requirements.

i am not saying one should not care about non-functional requirements or constraints...

(read more)

white on "Project scope: requirements"

white — Wed, 14 Mar 2007 22:12:40 +0000

Speaking about typical project scope of a kind-of-waterfall-model project management strategy, what kind of requirements do you usually gather? Functional and Non-functional requirements sound like a must-have and pretty straight forwarded. But what about General (or global) requirements and Constraints?

I got pretty messed up with some people, trying to distinguish General requirements (which are also called as Constraining requirements) and Constrains. From my experience, I never saw them doing different job.

The General requirements are the ones that describe the highest level of requirements for specific project or system.

The Constrains are named requirements that must met at the top level of every entire project or system.

I do not feel either difference in specification or in idea. Both of them are required to achieve the same goal -- to describe the root and very core requirements of the projects.

Your thoughts and feedback would be highly appreciated.

(read more)