Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Interaction between Requirements and Features

Interaction between Requirements and Features

Scheduled Pinned Locked Moved C#
businessquestion
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T Offline
    T Offline
    Tomerland
    wrote on last edited by
    #1

    Dear readers, I'm confused about the interaction between the terms "requirements" and "features". I read a lot about that but I didn't really get the point. There are a lot of statements, as: 1. A feature is built from a group of requirements 2. Traceability (between requirments and implementation) is possible only for features and not for requirements. ...and a lot more... Can somebody provide me some information? Thank's ! !

    C 1 Reply Last reply
    0
    • T Tomerland

      Dear readers, I'm confused about the interaction between the terms "requirements" and "features". I read a lot about that but I didn't really get the point. There are a lot of statements, as: 1. A feature is built from a group of requirements 2. Traceability (between requirments and implementation) is possible only for features and not for requirements. ...and a lot more... Can somebody provide me some information? Thank's ! !

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      Requirements are 'the app needs to do x' Features are 'we added y to the app, and this deals with requirement x' It's probably largely semantic, but I'm sure it keeps some consultants in a job.

      Christian Graus No longer a Microsoft MVP, but still happy to answer your questions.

      T 1 Reply Last reply
      0
      • C Christian Graus

        Requirements are 'the app needs to do x' Features are 'we added y to the app, and this deals with requirement x' It's probably largely semantic, but I'm sure it keeps some consultants in a job.

        Christian Graus No longer a Microsoft MVP, but still happy to answer your questions.

        T Offline
        T Offline
        Tomerland
        wrote on last edited by
        #3

        Thanks's for your answer, but I still are unable to catch the point probably :-))) As I understand you, Requirements are from the user and Features are from the implementation. Am I right? Let me try an example: We have 3 user requirements: R1: Read configdata from file after startup R2: Store configdata to file at closing I have the following implementation (-features) I1: Search file from directory-tree I2: Read config-file I3: Interpret config-file I4: Write config-file This means: R1 is implemented by I1 and I2 and I3 R2 is implemented by I1 and I4. For getting traceability now, I have to check which requirement is implemented by which feature. Is my thinking right in some way? With kind regards

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups