iSixSigma

How to identify System Requirements

Six Sigma – iSixSigma Forums Old Forums General How to identify System Requirements

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #29598

    Taylor
    Member

    Recently started to do more IT related six sigma projects, wondering if anyone has a tip or template that I could use during a mapping session to drive out enough detail to capture system requirements.

    0
    #76185

    Norrin Radd
    Participant

    Todd,
    Could you please be more specific as to what “system” means here.
    Thanks

    0
    #76189

    Ex MBB
    Participant

    Hi Todd,
    Several years ago, the medical device community took a stab at this under a mandate from the FDA to validate their computer systems.  The catchy phrase within the community was Computer System Validation (CSV).  Most programs included within the CSV a definition of the system, including what they referred to as generating a Statement of Requirements.  This is dated information, but there may be some lingering references.
    You may also want to see what references exist to prepare folks for the ASQ Certified Software Quality Engineer exam.  These may also help.
    One last reference — if you looking at systems in general, Systems Engineering and Analysis by Blanchard and Fabrycky is a great resource.

    0
    #76190

    Taylor
    Member

    By system requirements I mean funtional requirements of an IT system and business rules that govern them.
    Thank you Silver Surfer!

    0
    #76196

    Norrin Radd
    Participant

    Todd,
    I have used two approaches in the past.
    Approach one identify business functions of IT
    Maintenance, Risk Management, Development, and Project initiaitves.
    Approach two: identify the different individual components of IT work:
    Desktop(Hardware and OS), Desktop Software, LAN-Data Com, WAN-Data Com, Servers(Hardware and OS), Enterprise Software, IT Support Software, Supplier Contracts.
    Hope this helps

    0
    #76249

    R. Wheeler
    Participant

    Todd,for the last 8 years I personally have used Use Cases as a means to capture software and hardware system (both functional and non-functional) requirements. But remember, a Use Case is not a Use Case without the end user’s (a.k.a. your customer) involvement. You will have to facilitate meeting(s) as part of a Requirements Gathering Workshop or Use Case Workshop session(s) with your users (a.k.a. customers).I am currently in the process of experimenting the use of Use Cases within the context of the Six Sigma DFSS (Design For Six Sigma ) methodology and believe them to be yet another tool that I can incorporate into DFSS when applying Six Sigma to the IT industry.A great book for identifying and capturing Use Cases along with a template for their documentation can be found in Alistair Cockburn’s “Writing Effective Use Cases”.All the best.Regards,
    Roy.

    0
Viewing 6 posts - 1 through 6 (of 6 total)

The forum ‘General’ is closed to new topics and replies.