Link to home
Start Free TrialLog in
Avatar of yjchong514
yjchong514Flag for United States of America

asked on

During software requirement gathering phase

Dear EE members,

I am talking about User Requirement Gathering phase in software development life cycle.

As usual, the end-user will request a lot of requirements to convert the current manual system to a computerised
system.

As a fresh software developer, how to know what type of user requirement can be accepted and what type of user requirement is impossible to implement?


Rgds,

yjchong514
SOLUTION
Avatar of BigRat
BigRat
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Mike McCracken
Mike McCracken

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of yjchong514

ASKER

@proffric
Can you give an example for:
For every "shall" statement, write a corresponding test in a Systems Test Document that will fully verify the correctness of the "shall" statement. If unable to figure out how to test this statement, then remove the requirement.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Dear EE members,
ALL of you have given me the BEST opinion.
I appreciated your kindness.
Thank you!

Regards,

yjchong514