2 Replies - 1074 Views - Last Post: 11 May 2010 - 11:47 AM

#1 lex3   User is offline

  • New D.I.C Head

Reputation: 0
  • View blog
  • Posts: 2
  • Joined: 08-May 10

problem in Requirement Analysis

Posted 08 May 2010 - 07:42 AM

Hi everyone. I need help in doing my assignment.
My assignment is about a company who sales and rents video, music and games. Im having problem in Requirement Analysis topic. I understand what is requirement Analysis but the problem is that i dont know how to work it out.

Here is the Question:
Requirement Analysis

Describe the principle of requirement engineering activities and their relationships. Explain the technique used for requirement elicitation, analysis and requirement validation.



Please Guide me on this topic.
Thanks.

Is This A Good Question/Topic? 0
  • +

Replies To: problem in Requirement Analysis

#2 MentalFloss   User is offline

  • .
  • member icon

Reputation: 619
  • View blog
  • Posts: 1,590
  • Joined: 02-September 09

Re: problem in Requirement Analysis

Posted 10 May 2010 - 10:53 AM

Try to at least provide a little effort on this. If it's wrong, it's wrong but give it a try first.
Was This Post Helpful? 0
  • +
  • -

#3 NickDMax   User is offline

  • Can grep dead trees!
  • member icon

Reputation: 2255
  • View blog
  • Posts: 9,245
  • Joined: 18-February 07

Re: problem in Requirement Analysis

Posted 11 May 2010 - 11:47 AM

Start big -- move towards details.

Requirements are probably the most important part of software design. One needs to know what we are building before we can build it.

Start with the big picture. Identify basic areas and then begin to narrow down to line items.

For example your application will definetly have requirements regarding -- a database, user interface.

For the database as yourself questions like:

What kind of data will they need to keep track of?
Will there be a need for reporting/analysis?
How much data will there be?
Is the database external (MySql, Oralce etc,) or integrated?
Is there are need for archiving?
and on and on.

These can each be broken up to define in more detail what is meant. For example under reporting you might have:
Need the ability to view a report of weekly/monthly/quarterly earnings.
Need the ability to rank item's popularity by sales.

remember requirements are about the business needs not (normally) the implementation details. IF you find yourself talking about buttons, and fields, graphics, particular object or functions etc. you are probably going into too much detail.
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1