Requirement description

Initial requirements discussion

Moderator: seaton

Requirement description

Postby peter_gullberg » Sun Sep 23, 2007 9:03 pm

I'm used to work with a concept description that defines:

1. A short description on the aim of this project (more detailed than what I have seen)

2. Business rules/requirements, a description that defines what the product should do, and what values these brings, in simple words, what adds value to this product aimed to a person that will use this product:

3. Functional requirements: Technical definition on what functions and what features the product should have.

4. Non-functional requirements (quality/performance/size): Issues that are important to cover in order for the product to work correctly, or be attractive.


I'm interested to participate, have expertise in most areas of product development, s/w, h/w, mech, production, product management, and now also 1yr interest in photography :)

In order for me to participate, I would prefer to have someone in charge of the (V1) project scope (technical lead), to manage things such as a concept description, including a project leader, that could distribute tasks.

Cheers
\Peter
peter_gullberg
 
Posts: 4
Joined: Sun Sep 23, 2007 8:34 pm
Location: Gothenburg, Sweden

I agree

Postby Thonord » Sun Sep 23, 2007 10:06 pm

I,m with you Peter.

A project is:
A clearly defined goal
At a defined cost
Within a given timeframe.

But, while we wait, lets continue brainstorming.

Tom
Ppl who agree need normally not reply, those who disagree or have questions do.
Or - just ignore me.
Thonord
 
Posts: 50
Joined: Fri Sep 21, 2007 2:32 pm
Location: Norway


Return to Requirements

Who is online

Users browsing this forum: No registered users and 1 guest

cron