Answered Questions

  • Mar 29 2007
    09:04 PM
    7458
    9

    How do you come up with non-functional requirement?
    • hasan

    Star Read Best Answer

    Editorial / Best Answer

    amarchis  

    • Member Since Jun-2007 | Jun 9th, 2007

    There are a variety of methods to elicit non-functional requirements.  One method that I use is to identify upfront (before the project even starts) the main categories of non-functional requirements as well as a standard set of questions to ask for each type of non-functional requirements.

    Here are some key categories of non-functional requirements:
    1. GUI look and feel requirements
    2. Performance requirements
    3. Availability requirements
    4. Security requirements
    5. Capacity requirements
    6. Exception Handling requirements
    7. Logging requirements
    8. Extensibility requirements
    9. Data Retention requirements
    etc.

    Then for each type of non-functional requirement you could develop standard questions or just as more general questions such as: "Data Retention: do you have any requirements related to how long data (or certain types of data) should be retained by the system?"

    Hope this helps!
    - Adrian

    sandhya001

    • Sep 3rd, 2007

    The simple method is:Functional Requirements are MUST TO HAVE (The system will not function without these requirements)Non-Functional Requirements are NICE TO HAVE (The system will work however, NFR will increase the usability or performance related issues.)

  • Mar 27 2007
    02:03 AM
    3355
    9

    what are the contents that go into the object model and domain model during GAP analysis. how are the AS-IS and To-BE system documentation prepared
    • garfield

    sandhya

    • Sep 3rd, 2007

    When I did GAP analysis I have considered some of the following criteria to show the gap between AS-IS and TO-BE:1. Technical (technology ex. language and database etc)2. Functional (all major functio...