Achieving Designs that Satisfy Stakeholders Through Better Requirements

00:49:10
https://www.youtube.com/watch?v=YVtchkhpDFE

Résumé

TLDRTammy Katz, en systemingeniørekspert, præsenterer om betydningen af at udvikle bedre krav ved at forstå interessenternes behov. Hun diskuterer, hvordan man gennem en struktureret tilgang til behovsudvikling bedre kan valideres systemer, så de faktisk opfylder nødvendige stakeholder behov og ikke blot formelle krav. Hun fremhæver vigtigheden af at sætte større fokus på behov frem for umiddelbar kravudvikling for at opnå bedre systemintegritet og stakeholder tilfredsstillelse. Katz introducerer en ny manual fra INCOSE, der beskriver disse koncepter nærmere, og opfordrer til at tage en datadrevet tilgang i systemudvikling. Desuden opfordrer hun til feedback på denne manual fra de praktiserende ingeniører, som vil blive nyttiggjort ved fremtidige opdateringer.

A retenir

  • 🛠️ Fokus på behov før krav fører til bedre systemdesign.
  • 💼 INCOSE manualer og vejledninger er tilgængelige for medlemmer.
  • 🔄 Verifikation og validering af systemer sker gennem hele livscyklussen.
  • 🎯 Betydningen af en datadrevet tilgang til systemudvikling.
  • 📚 Den nye manual giver en dybdegående guide til behovs- og kravstyring.
  • 🤝 Samarbejde mellem interessenter er vigtigt for succesfuldt design.
  • 🗂️ Sammenkoblede data sikrer præcise systemkonstruktioner.
  • 🚀 Systemer valideres imod interessenters reelle behov.
  • 🌍 Tilpasning og forståelse af kontekst er kritisk under kravsudvikling.
  • 🔍 Aktualisering af materialer i systemingeniørpraksis.

Chronologie

  • 00:00:00 - 00:05:00

    Mød Tammy Katz, en beundringsværdig kvinde med dyb interesse i kravfastlæggelse og mission arkitektur. Hun præsenterer om at opnå design, der tilfredsstiller interessenter gennem bedre kravfastsættelse. Formålet er at belyse vigtigheden af at forstå og udvikle interessenternes behov som grundlag for gode krav.

  • 00:05:00 - 00:10:00

    Materialet fra INCOSE Requirements Working Group hjælper systemudviklere med at opnå systemvalidering gennem en bedre forståelse af behov og krav. Det omfatter en ny manual til behov og krav samt vejledninger til anvendelse, der dækker forskellige industridomæner.

  • 00:10:00 - 00:15:00

    Indsatsen for at afklare de forvirrende termer i systemkravudvikling fremhæves, herunder forskelle mellem behov og krav og vigtigheden af behovsidentifikation for at sikre validering. Tilpasninger forventes i næste udgave af SE håndbogen for at afklare misforståelser.

  • 00:15:00 - 00:20:00

    Fokusering på behov i systemudviklingen kan føre til bedre overensstemmelse med interessenternes ønsker og validering. Verifikation og validering skal behandles i sammenhæng med livscyklusprocesser. En datacentrisk fremgangsmåde opfordres for at forbedre integration.

  • 00:20:00 - 00:25:00

    Verifikation og validering bør ikke forveksles, da de er essentielle men forskellige processer i systemudviklingen. De sikrer, at produktet opfylder både krav og behov gennem hele sin livscyklus.

  • 00:25:00 - 00:30:00

    Introduktion til processen for at etablere et integreret sæt af behov gennem mission, mål og interessenter, samt hvordan disse oversættes til krav. Datacentrisk tilgang foreslås for bedre at forbinde udviklingsdokumentation.

  • 00:30:00 - 00:35:00

    Brugen af et integreret sæt af behov kan udføres selv ved lavere samlingsniveauer og ikke blot på kundens eller brugerens krav. Dette hjælper med at sikre, at alle interessenter, herunder interne, er repræsenteret i behovsanalyse.

  • 00:35:00 - 00:40:00

    Alle systeminteressenter bidrager til et integreret sæt af behov, som senere transformationer til systemkrav. Dette hjælper med at sikre, at udviklede systemer opfylder de forventede funktioner og præstationer.

  • 00:40:00 - 00:49:10

    Behov og krav transformation i kontekst – vigtigheden af datacentrisk praksis og modellering for systemudvikling og validering. Understreger interkoblede data og spredning af kraften i dataanalyse i udviklingsprocessen.

Afficher plus

Carte mentale

Mind Map

Questions fréquemment posées

  • Hvem er aftenens taler?

    Aftenens taler er Tammy Katz, en kvinde med stor faglighed inden for systemingeniørfeltet.

  • Hvad er den primære fokus for Tammy Katz's præsentation?

    Fokus for præsentationen er at opnå systemdesign, der tilfredsstiller interessenter gennem bedre forståelse af behov og krav.

  • Hvad diskuterer Tammy omkring systemdesign og krav?

    Hun diskuterer hvordan et system kan opfyldes interessenternes behov ved korrekt viden om og håndtering af krav.

  • Hvilken organisation er Tammy Katz en del af?

    Tammy Katz er en del af INCOSE (International Council on Systems Engineering).

  • Hvad er et væsentligt udbytte af at fokusere på behov før krav?

    Ved at fokusere på behov før krav kan man skabe et system der validerer de oprindelige interessentbehov og ikke kun opfylder formelle krav.

  • Hvornår skal en system validering finde sted ifølge præsentationen?

    Systemet skal valideres mod interessenternes behov gennem hele dets livscyklus.

  • Hvad er en vigtig opfattelse i kravspecificeringsprocessen ifølge Tammy Katz?

    At forene interessenternes reelle behov med de krav der udvikles til systemdesignet.

  • Hvilken opdatering er udgivet i januar 2023, som Tammy Katz nævner?

    En ny manual om behov og krav fra INCOSE's requirements working group.

  • Hvad opfordrer Tammy deltagerne til at gøre efter præsentationen?

    Hun opfordrer deltagerne til at bruge og give feedback på den nye manual og dens indhold.

Voir plus de résumés vidéo

Accédez instantanément à des résumés vidéo gratuits sur YouTube grâce à l'IA !
Sous-titres
en
Défilement automatique:
  • 00:00:00
    and now what we've all been waiting for
  • 00:00:02
    tonight's speaker meeting
  • 00:00:05
    tammy katz is is a um
  • 00:00:09
    a woman of wonder she's an esep
  • 00:00:11
    she's a phd
  • 00:00:13
    she's chair of the cozy uh requirements
  • 00:00:15
    working group
  • 00:00:16
    she's a chief engineer she does mission
  • 00:00:19
    architecture studies
  • 00:00:20
    don't know where you find the time tammy
  • 00:00:22
    but um i i appreciate people like you
  • 00:00:25
    who are interested in these topics and
  • 00:00:28
    and willing to share your knowledge with
  • 00:00:30
    us
  • 00:00:31
    and she has lots of things to share with
  • 00:00:32
    us this evening
  • 00:00:35
    um several needs and requirements um
  • 00:00:38
    specifics are in that guide
  • 00:00:41
    uh there's a white paper on
  • 00:00:43
    integrated data
  • 00:00:45
    a guide on verification and validation
  • 00:00:48
    one to write requirements and of course
  • 00:00:50
    she also contributes to the sc handbook
  • 00:00:52
    and the systems engineering
  • 00:00:54
    body of knowledge so she provides
  • 00:00:56
    guidance across um the the boundaries of
  • 00:01:00
    all areas of emposi
  • 00:01:02
    we are very happy to have tammy um with
  • 00:01:05
    us today and i'm proud to call her one
  • 00:01:07
    of our own in the inclusi organization
  • 00:01:11
    so without further ado i'm gonna stop
  • 00:01:13
    sharing tana would you like to share or
  • 00:01:15
    would you like me to
  • 00:01:16
    flip your slides
  • 00:01:18
    i'll go ahead and share i've got them
  • 00:01:20
    set up on the screen
  • 00:01:21
    so i'm gonna
  • 00:01:23
    get this going hopefully we get the
  • 00:01:24
    right screen
  • 00:01:27
    please confirm if you see my slides
  • 00:01:31
    confirm
  • 00:01:33
    excellent thank you and thank you for
  • 00:01:35
    that very nice introduction i really
  • 00:01:37
    appreciate it um so the title of my talk
  • 00:01:40
    today is achieving designs that satisfy
  • 00:01:42
    stakeholders through better requirements
  • 00:01:45
    and it doesn't say it boldly in here but
  • 00:01:48
    really what i'm going to be talking
  • 00:01:50
    about is developing our needs and
  • 00:01:52
    understanding the needs because that's
  • 00:01:54
    the foundation of establishing good
  • 00:01:56
    requirements that satisfy our
  • 00:01:58
    stakeholders and i'm going to give a lot
  • 00:02:00
    of credit to my fellow members of our
  • 00:02:03
    requirements working group here in a
  • 00:02:04
    minute so i'm going to introduce us
  • 00:02:06
    as a group
  • 00:02:07
    so i'm going to show how our material
  • 00:02:10
    through the in cozy requirements working
  • 00:02:11
    group
  • 00:02:12
    can help develop system developers
  • 00:02:16
    get an effort that really satisfies
  • 00:02:18
    their stakeholders ultimately achieving
  • 00:02:20
    system validation we're going to
  • 00:02:22
    highlight our new needs and requirements
  • 00:02:24
    manual and and just talk about examples
  • 00:02:26
    of how someone could apply it and some
  • 00:02:28
    some key lessons i hope you take away
  • 00:02:30
    from that manual
  • 00:02:33
    so our requirements working group has
  • 00:02:35
    been around for some time
  • 00:02:37
    and everyone
  • 00:02:38
    who's an cozy member is welcome to join
  • 00:02:41
    we uh really are just trying to advance
  • 00:02:43
    the practice of how to apply
  • 00:02:46
    requirements development management in
  • 00:02:48
    our various industries as systems
  • 00:02:50
    engineers and now we've also
  • 00:02:52
    incorporated the idea of needs and
  • 00:02:54
    requirements development and after my
  • 00:02:56
    talk today i hope you understand why
  • 00:02:58
    and we're really a group for
  • 00:02:59
    practitioners although we have quite a
  • 00:03:01
    diverse array of both
  • 00:03:04
    experienced industry folks
  • 00:03:07
    academic
  • 00:03:08
    participants and everyone in between so
  • 00:03:11
    we've got folks who've just started
  • 00:03:13
    their journey as systems engineers and
  • 00:03:15
    and folks like lou that you just met
  • 00:03:17
    who've been practicing it for for a few
  • 00:03:19
    decades now
  • 00:03:21
    this is the leadership here of our group
  • 00:03:24
    um i've been the chair for about three
  • 00:03:25
    years before me uh lou wecraft was the
  • 00:03:28
    chair and he's now kindly agreed to
  • 00:03:30
    support me as a co-chair
  • 00:03:32
    we've got mike ryan who just retired he
  • 00:03:35
    works out in australia and he's been a
  • 00:03:38
    co-chair for a while and we have raymond
  • 00:03:40
    wolfgang who works out in sandia
  • 00:03:42
    national labs
  • 00:03:43
    and besides the the four of us we have
  • 00:03:46
    400 plus members and that sounds uh
  • 00:03:49
    pretty impressive uh it's quite the
  • 00:03:51
    diverse large group of uh working group
  • 00:03:54
    members that we've got
  • 00:03:56
    it's one of our largest in and cozy and
  • 00:03:58
    what we really enjoy is being able to
  • 00:04:00
    get together frequently and having
  • 00:04:02
    dialogues of what's challenging folks
  • 00:04:05
    you know what are the issues that people
  • 00:04:07
    are seeing that we can try to solve as a
  • 00:04:10
    group
  • 00:04:11
    we have several resources i'm going to
  • 00:04:12
    point you to and i'll bring them up
  • 00:04:14
    later again if you'd like to see them
  • 00:04:15
    and the slides will be made available so
  • 00:04:17
    you can get to our sites but we have an
  • 00:04:19
    external site where we publish a lot of
  • 00:04:22
    our upcoming
  • 00:04:24
    i guess meetings and and presentations
  • 00:04:27
    and we have a youtube channel so if
  • 00:04:29
    you're actually to go on
  • 00:04:30
    the youtube uh
  • 00:04:32
    if you go on youtube and search for in
  • 00:04:34
    cozy requirements working group or in
  • 00:04:36
    cozy rwg you'll find our channel and we
  • 00:04:39
    put a lot of information about our
  • 00:04:41
    material there including our guest
  • 00:04:43
    speakers and our workshop
  • 00:04:45
    sessions
  • 00:04:47
    now you saw earlier a form of our
  • 00:04:49
    products this is actually our product
  • 00:04:51
    tree
  • 00:04:52
    and we are very responsive to the in
  • 00:04:54
    cozy system engineering handbook so you
  • 00:04:57
    see that up here we've supplied inputs
  • 00:04:59
    to version 5 and that really forms how
  • 00:05:03
    we generate our material which is
  • 00:05:05
    practical guidance in support of that
  • 00:05:07
    material and i'm going to hit some of
  • 00:05:10
    how we also respond to
  • 00:05:12
    the 15 288 standard as well here
  • 00:05:15
    um we also try to align very closely
  • 00:05:17
    with the cboc which has a lot of uh i
  • 00:05:20
    would say more living material
  • 00:05:22
    associated with systems engineering
  • 00:05:23
    practices
  • 00:05:25
    our document that we just put out this
  • 00:05:27
    year is called the needs and
  • 00:05:28
    requirements manual and i'm going to
  • 00:05:29
    share a bit about it with you and i'm
  • 00:05:31
    going to show you excerpts from it today
  • 00:05:34
    but before we publish that we had
  • 00:05:35
    published a white paper a few years ago
  • 00:05:38
    called
  • 00:05:40
    integrated data as a foundation of
  • 00:05:41
    systems engineering and it's really
  • 00:05:43
    about a data centric practice of systems
  • 00:05:45
    engineering and how that intertwines a
  • 00:05:47
    lot of requirements with our other
  • 00:05:50
    artifacts of development and how
  • 00:05:52
    important that is that that all talks to
  • 00:05:54
    each other and i'm going to bring up
  • 00:05:55
    elements of that today as well because
  • 00:05:57
    that also worked its way into our manual
  • 00:06:00
    and uh that was also one of the uh in
  • 00:06:03
    cozy technical operation uh like best
  • 00:06:06
    paper awards a few years ago from a
  • 00:06:09
    working group
  • 00:06:10
    we have practitioner guides though so
  • 00:06:12
    the manual itself
  • 00:06:14
    pretty large has a lot of information
  • 00:06:18
    we realize some people want the easy
  • 00:06:20
    option so we put together a handful of
  • 00:06:22
    guides that give practical application
  • 00:06:25
    guidance and examples so they speak to
  • 00:06:27
    the material but in a little simpler
  • 00:06:29
    form
  • 00:06:30
    the shorter
  • 00:06:32
    and and then the like i said have
  • 00:06:33
    examples so we have the guide to needs
  • 00:06:35
    and requirements we have the guide to
  • 00:06:37
    verification and validation and then we
  • 00:06:39
    also have the guide to writing
  • 00:06:40
    requirements which has been around for a
  • 00:06:41
    while and we're going to go ahead and do
  • 00:06:43
    a refresh on that uh over this next few
  • 00:06:45
    years with even more characteristics and
  • 00:06:48
    examples
  • 00:06:50
    and we have work with other working
  • 00:06:52
    groups to provide more domain specific
  • 00:06:55
    guides since we work across many
  • 00:06:56
    industries we find some industries think
  • 00:06:59
    about security or aerospace perhaps
  • 00:07:02
    might want to focus in on some guidance
  • 00:07:04
    just for domains that are very
  • 00:07:07
    specialized
  • 00:07:10
    and i certainly encourage everyone to go
  • 00:07:11
    to the store the cozy store has all this
  • 00:07:14
    material you can you know here's
  • 00:07:15
    screenshots of where you can find it
  • 00:07:18
    we know this material is pretty uh
  • 00:07:21
    low cost if you're not a member but if
  • 00:07:23
    you are a member it's even lower it's
  • 00:07:25
    free to download so
  • 00:07:27
    uh i hope you get an opportunity to go
  • 00:07:30
    to the cozy store and check out our
  • 00:07:32
    needs and requirements requirements
  • 00:07:34
    manual and some of our guides
  • 00:07:36
    and we are going to put this plea at the
  • 00:07:38
    end and i'll start off now saying we
  • 00:07:40
    welcome your feedback we put this
  • 00:07:41
    material together over several years
  • 00:07:43
    with a lot of peer reviews and user
  • 00:07:46
    inputs and the best thing that we can
  • 00:07:48
    hear is folks who have been using it
  • 00:07:50
    with recommendations on how to improve
  • 00:07:51
    it and make it even better
  • 00:07:55
    so i'm going to go in and talk a little
  • 00:07:57
    bit about why
  • 00:07:58
    we're trying to solve certain problems
  • 00:08:00
    what what is it we saw needed to be
  • 00:08:02
    addressed what are some of the confusing
  • 00:08:05
    things out there in the practice of
  • 00:08:07
    developing requirements and what we
  • 00:08:10
    believe could be a way to approach it
  • 00:08:13
    that could be a little bit more
  • 00:08:14
    beneficial a little more effective
  • 00:08:17
    so i'm going to start by talking about
  • 00:08:18
    the current system engineering technical
  • 00:08:20
    processes themselves
  • 00:08:23
    and i'm sure many of you are aware of
  • 00:08:25
    5288 and it's a technical standard for
  • 00:08:27
    systems engineering in general right so
  • 00:08:30
    it covers uh processes across many
  • 00:08:32
    lifecycle stages not just requirements
  • 00:08:35
    obviously but it is in there
  • 00:08:37
    they also put together a 29148
  • 00:08:41
    standard in 2018 and it is very focused
  • 00:08:44
    on requirements engineering and it tries
  • 00:08:46
    to get a little bit more focused in
  • 00:08:48
    terms of terminology concepts
  • 00:08:51
    my opinion a little less user-friendly
  • 00:08:53
    in terms of practical application so
  • 00:08:57
    what we saw then is in the cozy systems
  • 00:08:59
    engineering handbook it expands also on
  • 00:09:01
    15 288 and does define a little bit more
  • 00:09:06
    on how some of these technical processes
  • 00:09:08
    could be done
  • 00:09:10
    but what the requirement working group
  • 00:09:11
    did is decide to take that
  • 00:09:14
    and write more material that can help
  • 00:09:16
    the users with very specific sets of
  • 00:09:19
    those technical processes
  • 00:09:21
    and if you're not familiar haven't read
  • 00:09:23
    it recently these are the overview of
  • 00:09:25
    the 15 288 processes that we're talking
  • 00:09:27
    about and specific the technical
  • 00:09:29
    processes are really um
  • 00:09:32
    probably the the most
  • 00:09:33
    that people think about when they think
  • 00:09:34
    about developing a product right they're
  • 00:09:36
    certainly the ones people think about
  • 00:09:38
    when they think about developing your
  • 00:09:40
    requirements developing verification
  • 00:09:42
    understanding you know your transition
  • 00:09:44
    and and your designs so these are the
  • 00:09:47
    ones a lot of the engineers think of
  • 00:09:49
    when they're developing a product and
  • 00:09:52
    if you read 15 288 and the sc handbook
  • 00:09:54
    you'll recognize they're done
  • 00:09:56
    iteratively and recursively and this is
  • 00:09:58
    one of the areas that some folks tend to
  • 00:10:00
    miss is some of these
  • 00:10:02
    don't necessarily happen in order or
  • 00:10:04
    they can go back and we can mature them
  • 00:10:06
    further as we go through a development
  • 00:10:08
    life cycle so we're going to talk a
  • 00:10:10
    little bit how that can work with some
  • 00:10:12
    of the examples i'm going to give today
  • 00:10:15
    now obviously how these processes are
  • 00:10:17
    implemented can greatly affect the
  • 00:10:19
    outcome of a product
  • 00:10:21
    one of the things i'm going to focus on
  • 00:10:22
    are the first three
  • 00:10:24
    um so the technical process is here i'm
  • 00:10:27
    going to give a little bit more
  • 00:10:28
    attention to the first three of this
  • 00:10:30
    group
  • 00:10:33
    now this material i'm presenting now is
  • 00:10:36
    your as is state so when you see updates
  • 00:10:39
    to uh the sc handbook in my next summer
  • 00:10:42
    when it's published much of this is
  • 00:10:44
    going to go away and i'm going to talk a
  • 00:10:46
    little bit about why it's going to go
  • 00:10:47
    away but if you were to look at the
  • 00:10:49
    system engineering handbook now this is
  • 00:10:51
    what you would see
  • 00:10:52
    and it's what a lot of people try to put
  • 00:10:53
    into practice today so i'm going to just
  • 00:10:55
    go ahead and expand on it and then talk
  • 00:10:57
    about some of the
  • 00:10:59
    more evolved material that we're we're
  • 00:11:01
    putting out
  • 00:11:02
    so when you think about
  • 00:11:04
    your technical process for business and
  • 00:11:06
    mission analysis one of the things
  • 00:11:08
    you're thinking about here
  • 00:11:10
    is your preliminary life cycle concepts
  • 00:11:13
    and your business needs and what is
  • 00:11:15
    what is it you're trying to do when
  • 00:11:18
    where are you trying to solve a problem
  • 00:11:19
    or an opportunity where are you going to
  • 00:11:21
    put your money what market are you going
  • 00:11:23
    for
  • 00:11:24
    and as you look on it it kind of gets
  • 00:11:26
    into the part where you're starting to
  • 00:11:28
    just skim the surface of what are we
  • 00:11:31
    aiming for
  • 00:11:32
    the concept here is you then get from
  • 00:11:35
    you know this initial concept to a set
  • 00:11:37
    of business requirements
  • 00:11:38
    and they could be published in some sort
  • 00:11:41
    of business requirement specification
  • 00:11:44
    now i don't know about you i've never
  • 00:11:46
    seen or written a business requirement
  • 00:11:48
    specification
  • 00:11:49
    however this idea of starting with your
  • 00:11:51
    problem statement or what opportunity
  • 00:11:53
    you're solving that's real right i mean
  • 00:11:56
    we do do that as various companies
  • 00:12:00
    and then the next process is called the
  • 00:12:02
    stakeholder needs and requirements
  • 00:12:05
    technical process so it has has both
  • 00:12:06
    those terms in there
  • 00:12:08
    and it's really about
  • 00:12:10
    understanding then
  • 00:12:12
    what stakeholders are out there
  • 00:12:15
    for that problem or opportunity what are
  • 00:12:17
    you solving and what is it they need and
  • 00:12:19
    they inform it in terms of requirement
  • 00:12:22
    statements from the stakeholder
  • 00:12:23
    perspective
  • 00:12:24
    and
  • 00:12:25
    the
  • 00:12:26
    the requirements standard actually goes
  • 00:12:28
    quite a bit into this process as well
  • 00:12:31
    but when you're done with this step it's
  • 00:12:32
    expected that you will have some sort of
  • 00:12:35
    stakeholder requirement specification
  • 00:12:38
    and
  • 00:12:39
    you see here on this figure
  • 00:12:41
    the strs is the outcome of this process
  • 00:12:45
    and there is a transformation step
  • 00:12:47
    within this technical process where you
  • 00:12:49
    take your stakeholder needs as after you
  • 00:12:51
    acquire them and you kind of transform
  • 00:12:54
    them into requirement statements from a
  • 00:12:56
    stakeholder perspective
  • 00:12:58
    and then you enter your next technical
  • 00:13:00
    process called system requirements
  • 00:13:02
    and this is where you get through to
  • 00:13:05
    what is the system of interest supposed
  • 00:13:06
    to do to meet those stakeholder needs
  • 00:13:09
    and requirements and when you exit this
  • 00:13:12
    process you get to your system
  • 00:13:13
    requirement specification
  • 00:13:16
    and that ultimately captures what the
  • 00:13:17
    system needs to do how well it needs to
  • 00:13:20
    do it under what conditions many of us
  • 00:13:22
    are very familiar with this particular
  • 00:13:25
    form of requirements
  • 00:13:27
    now this is very interesting to me to
  • 00:13:29
    see all the steps that go into that
  • 00:13:31
    because in my practice as an engineer
  • 00:13:34
    i've often not seen those other steps
  • 00:13:36
    this is actually
  • 00:13:37
    where i've spent a bulk of my time
  • 00:13:40
    and i find as i talk to other peers
  • 00:13:43
    that's where a lot of other folks tend
  • 00:13:45
    to focus as well
  • 00:13:47
    so then that gets into the challenges
  • 00:13:49
    what what are the actual challenges with
  • 00:13:52
    these approaches in these technical
  • 00:13:53
    processes and what can we do to kind of
  • 00:13:55
    put a spin on it to help make them more
  • 00:13:57
    effective
  • 00:14:01
    so first i'd like to highlight that
  • 00:14:03
    second process stakeholders needs and
  • 00:14:05
    development it's very critical and when
  • 00:14:07
    you think about the definition of
  • 00:14:09
    validation in the system engineering
  • 00:14:11
    handbook one of the things you'll see is
  • 00:14:13
    that actually this the system is
  • 00:14:15
    actually validated against these the
  • 00:14:17
    stakeholder needs and requirements
  • 00:14:20
    and
  • 00:14:21
    it's very important then to understand
  • 00:14:23
    them very well
  • 00:14:26
    however
  • 00:14:28
    you know in practice we've noticed that
  • 00:14:30
    the approach to capture our stakeholder
  • 00:14:32
    requirements and system requirements
  • 00:14:34
    they tend to be combined people tend to
  • 00:14:37
    shortcut it and go right to the system
  • 00:14:39
    set of requirements
  • 00:14:41
    and they focus more on it and and
  • 00:14:43
    sometimes what you hear is why do that
  • 00:14:45
    double work you know ultimately we want
  • 00:14:48
    the system requirements
  • 00:14:49
    um there's also additional confusion in
  • 00:14:52
    my opinion from iso 29148 which refers
  • 00:14:56
    to stakeholder owned system requirements
  • 00:14:59
    so okay is that a stakeholder
  • 00:15:01
    requirement let's get a system
  • 00:15:02
    requirement right
  • 00:15:04
    so
  • 00:15:05
    it really comes down to this is a very
  • 00:15:07
    important step understanding the
  • 00:15:09
    stakeholder needs is a very critical
  • 00:15:11
    step to achieving system validation
  • 00:15:13
    because ultimately we want to show we
  • 00:15:15
    built the right thing
  • 00:15:16
    and missing that stakeholder needs and
  • 00:15:18
    requirements process can result in a
  • 00:15:20
    system that really conforms to your
  • 00:15:22
    requirements it's fully verified
  • 00:15:24
    but it doesn't address the needs of the
  • 00:15:25
    stakeholders it's not validated
  • 00:15:30
    and then we get down to the other thing
  • 00:15:32
    we've noticed a confusion of is it a
  • 00:15:34
    need or is it a requirement now we have
  • 00:15:37
    here
  • 00:15:38
    the definitions obviously the terms are
  • 00:15:40
    defined differently but when we think
  • 00:15:42
    about it in terms of the technical
  • 00:15:43
    processes uh they are very different uh
  • 00:15:46
    statements right so needs are more in
  • 00:15:50
    the um view sorry i'm gonna move that
  • 00:15:53
    right there
  • 00:15:54
    capabilities or things that are lacking
  • 00:15:57
    but wanted or desired by one or more
  • 00:15:59
    stakeholders and they're often in the
  • 00:16:00
    viewpoint of the stakeholders
  • 00:16:03
    so you know i really want
  • 00:16:07
    the ability to image something i really
  • 00:16:10
    need to be able to take pictures right
  • 00:16:12
    and that ultimately can be decomposed to
  • 00:16:14
    a series of requirements around a system
  • 00:16:16
    that can do those things and have those
  • 00:16:18
    capabilities
  • 00:16:19
    so
  • 00:16:21
    researching many publications and
  • 00:16:23
    courses what we see is a lot of emphasis
  • 00:16:25
    on developing the requirements which are
  • 00:16:28
    those formal structured statements that
  • 00:16:30
    can be verified and we'll say validated
  • 00:16:33
    now and i'll give you a little insight
  • 00:16:35
    later what we mean when we say and
  • 00:16:36
    they're validated
  • 00:16:37
    there may be more than one requirement
  • 00:16:39
    defined for each need so you have this
  • 00:16:41
    capability concept from a stakeholder
  • 00:16:43
    perspective in form of a need but most
  • 00:16:45
    of the training that we've seen most of
  • 00:16:47
    the guidance most of the published
  • 00:16:49
    material really focuses right on the
  • 00:16:51
    requirements that formal structured
  • 00:16:54
    almost contractual set of terms on what
  • 00:16:57
    a thing needs to do
  • 00:16:59
    and so what we're finding is uh
  • 00:17:02
    less focus on needs in terms of
  • 00:17:04
    education in terms of practice
  • 00:17:07
    now i took this from the system
  • 00:17:09
    engineering handbook very specifically i
  • 00:17:11
    see many flavors of the system
  • 00:17:13
    engineering be
  • 00:17:14
    and some of them do start with the
  • 00:17:17
    capture of needs and the you know what
  • 00:17:19
    is it our business is trying to do
  • 00:17:22
    many of them start right here with the
  • 00:17:23
    system the system viewpoint system
  • 00:17:26
    requirements and a lot of system
  • 00:17:28
    engineers are almost trained from the
  • 00:17:31
    get-go that the very top of that v is
  • 00:17:33
    our system and then we go down and
  • 00:17:35
    decompose to a lower level like a
  • 00:17:38
    subsystem and maybe a component and that
  • 00:17:40
    really just again reinforces this idea
  • 00:17:43
    we go right to the system requirements
  • 00:17:46
    but where do those requirements come
  • 00:17:47
    from right what is the thing that really
  • 00:17:49
    prompts those requirements and that's
  • 00:17:51
    really where we want to get focused on a
  • 00:17:52
    little bit more
  • 00:17:55
    so nomenclature challenges this is not
  • 00:17:57
    my favorite figure and i know that uh
  • 00:18:00
    you know some of some of my peers helped
  • 00:18:02
    develop it so i hope you know i can say
  • 00:18:04
    that and not get in trouble but the idea
  • 00:18:06
    is it's a nomenclature challenge
  • 00:18:09
    i think of myself as a technical person
  • 00:18:11
    and a systems engineer and i see this
  • 00:18:14
    statement of business operations and my
  • 00:18:16
    head immediately goes to oh those other
  • 00:18:18
    people you know the folks that manage
  • 00:18:21
    the business side of things not
  • 00:18:22
    necessarily the technical side of things
  • 00:18:24
    that's not really true in this
  • 00:18:25
    particular technical process it's a very
  • 00:18:28
    critical step where they're taking
  • 00:18:29
    stakeholder needs and transforming them
  • 00:18:31
    to stakeholder requirements which
  • 00:18:33
    ultimately feed system requirements it's
  • 00:18:35
    a very critical step but a lot of folks
  • 00:18:38
    get turned off by the name of business
  • 00:18:39
    operations so again it takes a little
  • 00:18:41
    less importance then
  • 00:18:44
    of getting on to the idea of what your
  • 00:18:46
    needs are for the system of interest
  • 00:18:48
    that you're developing in the framework
  • 00:18:50
    of those who are going to use that
  • 00:18:51
    system or are impacted by that system
  • 00:18:54
    so we just find that's a misleading
  • 00:18:56
    nomenclature and one thing you will
  • 00:18:58
    learn is a lot of this material is going
  • 00:19:00
    to be updated in the next revision of
  • 00:19:02
    the system engineering handbook but this
  • 00:19:04
    is what's out there today
  • 00:19:06
    um we also like to remind you that this
  • 00:19:08
    15288 processes they are iterative and
  • 00:19:11
    recursive right so this needs
  • 00:19:12
    development don't just happen one time
  • 00:19:14
    at the very beginning they can happen
  • 00:19:17
    throughout the levels of abstraction so
  • 00:19:19
    as you go down to the subsystem level
  • 00:19:21
    there are stakeholders there right and
  • 00:19:23
    they they definitely have some needs and
  • 00:19:25
    viewpoints of that lower level uh that's
  • 00:19:27
    being developed and then you get to
  • 00:19:29
    maybe the component level and there are
  • 00:19:30
    stakeholders there as well so this
  • 00:19:32
    process does happen
  • 00:19:34
    uh multiple times throughout the life
  • 00:19:36
    cycle of a system of interest
  • 00:19:37
    development
  • 00:19:41
    so
  • 00:19:42
    got through a lot of terms that were
  • 00:19:43
    confusing and concepts that were being
  • 00:19:45
    missed and so now i'm going to highlight
  • 00:19:47
    some thoughts from the cozy requirements
  • 00:19:49
    working group on material we put
  • 00:19:51
    together we think might help
  • 00:19:53
    um make things a little more clear when
  • 00:19:56
    we're developing our requirement set and
  • 00:19:58
    how to actually ensure we're getting all
  • 00:20:00
    of the requirements and we're getting
  • 00:20:02
    them from the right perspectives and it
  • 00:20:04
    really will ultimately address the
  • 00:20:06
    problem that's being solved or the
  • 00:20:08
    opportunity that's trying to be realized
  • 00:20:11
    so
  • 00:20:11
    the requirements uh needs and
  • 00:20:13
    requirements manual is actually rather
  • 00:20:15
    large and there's a lot of concepts in
  • 00:20:17
    it and i certainly can't do justice in
  • 00:20:19
    the time i have today on all of it but
  • 00:20:21
    if you take away three things today
  • 00:20:23
    these are the three things that i would
  • 00:20:25
    love for you to see as effective ways to
  • 00:20:28
    improve requirements development efforts
  • 00:20:31
    one is focus more on the needs right and
  • 00:20:34
    i have charts on all of these but
  • 00:20:36
    particularly when you focus more on the
  • 00:20:37
    needs we're going to give you a methods
  • 00:20:39
    for establishing what we call the
  • 00:20:41
    integrated set of needs
  • 00:20:43
    and by moving more emphasis to what's
  • 00:20:45
    really needed before the development of
  • 00:20:47
    your system requirements
  • 00:20:49
    we believe that you ultimately get a
  • 00:20:51
    system that's
  • 00:20:52
    achieving system validation it's going
  • 00:20:54
    to be meeting your stakeholder needs
  • 00:20:56
    it's it's really ultimately going to be
  • 00:20:58
    the right thing
  • 00:21:00
    the other thing that we would like you
  • 00:21:02
    to take away is verification and
  • 00:21:04
    validation is really based on context so
  • 00:21:06
    i'm going to give examples of this but
  • 00:21:08
    the vnv terms
  • 00:21:09
    when we say vnv get interchanged a lot
  • 00:21:12
    right verification and validation do
  • 00:21:14
    absolutely mean different things
  • 00:21:16
    and based on where you are in your life
  • 00:21:18
    cycle and the thing you're trying to
  • 00:21:20
    verify or the thing you're trying to
  • 00:21:22
    validate those are different activities
  • 00:21:24
    so i'm going to talk a little bit about
  • 00:21:26
    what that means in relationship then to
  • 00:21:28
    also our needs and our requirements
  • 00:21:30
    and then the third takeaway which i
  • 00:21:32
    think is just huge and fundamental and
  • 00:21:35
    many many people are are dealing with
  • 00:21:38
    this beyond just the requirements aspect
  • 00:21:40
    is dealing with more of a data centric
  • 00:21:42
    approach we're going beyond a
  • 00:21:44
    document-centric viewpoint where we just
  • 00:21:46
    think about isolated documents while
  • 00:21:49
    we're developing a system a a spec a b
  • 00:21:52
    spec an icd an environment spec you know
  • 00:21:55
    these things are just no longer
  • 00:21:57
    stovepiped individual documents what
  • 00:21:59
    we're really dealing with is a set of
  • 00:22:01
    needs and requirements data that are
  • 00:22:04
    intertwined with all your other
  • 00:22:06
    system development artifacts
  • 00:22:08
    so i'm going to talk a little bit more
  • 00:22:10
    about that as we go through as well
  • 00:22:14
    and the last thing is um
  • 00:22:17
    okay i thought i would just look at the
  • 00:22:18
    chat briefly um we will address
  • 00:22:20
    questions of course but i just want to
  • 00:22:22
    make sure there was no you know
  • 00:22:23
    immediate question
  • 00:22:25
    let me talk a little bit about what we
  • 00:22:26
    mean when we say focus more on the needs
  • 00:22:29
    let's define it right needs represent a
  • 00:22:31
    stakeholder and customer or acquire view
  • 00:22:34
    of the system of interest so we'll say
  • 00:22:36
    system of interest or soi here this
  • 00:22:38
    could be a mission of some nature it
  • 00:22:41
    could be a medical device
  • 00:22:43
    it could be you know anything that's
  • 00:22:45
    being developed to solve a problem
  • 00:22:47
    and it could be a lower level of
  • 00:22:49
    something and so you know something part
  • 00:22:52
    of a bigger system
  • 00:22:53
    but needs represent the stakeholder and
  • 00:22:55
    customer require view of that what do
  • 00:22:57
    they need it to do to result in their
  • 00:22:59
    problem being resolved or their
  • 00:23:00
    opportunity being realized and of course
  • 00:23:03
    there are some defined constraints
  • 00:23:04
    associated with that
  • 00:23:06
    needs communicate what the stakeholders
  • 00:23:08
    expect the end state to be
  • 00:23:10
    once we get the system of interest
  • 00:23:12
    developed
  • 00:23:13
    and delivered
  • 00:23:14
    what will satisfy the stakeholder but
  • 00:23:16
    the other aspect of it the stakeholders
  • 00:23:19
    could also be part of the development
  • 00:23:20
    process it could be other members of the
  • 00:23:22
    team
  • 00:23:23
    that need something during the
  • 00:23:25
    development or verification activities
  • 00:23:27
    or or production right so they're not
  • 00:23:30
    just limited to the customer or the end
  • 00:23:32
    user they could be reflected of those
  • 00:23:34
    impacted by the system in some way even
  • 00:23:36
    including internal stakeholders
  • 00:23:38
    and ultimately your system of interest
  • 00:23:40
    is going to be validated against your
  • 00:23:42
    integrated set of needs and i'm going to
  • 00:23:44
    give examples of that shortly so you can
  • 00:23:46
    see what integrated needs are versus
  • 00:23:48
    this other thing we're calling
  • 00:23:49
    requirements
  • 00:23:51
    and requirements are your technical
  • 00:23:53
    developer view of the system of interest
  • 00:23:55
    so what must the soi do what must the
  • 00:23:58
    system do in order to meet those needs
  • 00:24:00
    it's an input to the design process
  • 00:24:02
    right so to think about then we're going
  • 00:24:05
    from needs to requirements to ultimately
  • 00:24:08
    a design solution
  • 00:24:10
    both the design and the realized system
  • 00:24:12
    the produced system will be verified
  • 00:24:15
    against the requirements so validated
  • 00:24:17
    against the integrated set of needs
  • 00:24:19
    verified against the requirements
  • 00:24:23
    so integrated needs again represent the
  • 00:24:25
    stakeholder needs that were transformed
  • 00:24:27
    from what we call the life cycle
  • 00:24:29
    concepts for the system of interest the
  • 00:24:31
    set of needs communicate all of the
  • 00:24:33
    stakeholder perspectives
  • 00:24:35
    concerning their expectations
  • 00:24:37
    and because needs are not requirements
  • 00:24:39
    they don't contain the word child so
  • 00:24:41
    we'll give some examples shortly
  • 00:24:43
    and then we're going to add a little
  • 00:24:45
    modifier to the word requirements
  • 00:24:47
    because remember earlier we were talking
  • 00:24:49
    about things called stakeholder
  • 00:24:51
    requirements and system requirements but
  • 00:24:53
    we're actually going to view it a little
  • 00:24:54
    more simply than that i'm just going to
  • 00:24:56
    call it design input requirements you
  • 00:24:58
    could still say requirements for short
  • 00:25:00
    because i would like you to recognize
  • 00:25:02
    that sometimes this can be a mouthful
  • 00:25:04
    but think about it in terms of design
  • 00:25:06
    input requirements they represent those
  • 00:25:09
    technical requirements that were
  • 00:25:11
    transformed from your baselines out of
  • 00:25:13
    integrated needs
  • 00:25:14
    or the system of interest their inputs
  • 00:25:16
    into the architecture and design
  • 00:25:17
    definition process they're written in a
  • 00:25:20
    structured
  • 00:25:21
    natural language as textual shell
  • 00:25:23
    statements
  • 00:25:24
    yeah they could actually be written in
  • 00:25:26
    terms of models too i think that in the
  • 00:25:28
    needs requirements manual we do say
  • 00:25:30
    there's a room for both right this is
  • 00:25:32
    the structured shell
  • 00:25:34
    so it's you're being measured against it
  • 00:25:37
    and and we do have rule sets for good
  • 00:25:39
    characteristics of writing requirements
  • 00:25:41
    that these are bounced against
  • 00:25:43
    so i will have you know there's a little
  • 00:25:45
    less emphasis on this word called
  • 00:25:47
    stakeholder requirements
  • 00:25:49
    our intent is to mitigate the confusion
  • 00:25:51
    of terms between stakeholder
  • 00:25:52
    requirements with stakeholder wants and
  • 00:25:54
    system requirements what the system is
  • 00:25:56
    expected to do we're trying to just keep
  • 00:25:58
    things a little more simple your
  • 00:25:59
    integrated set of needs
  • 00:26:01
    and then that feeds your design input
  • 00:26:04
    requirements
  • 00:26:07
    so this is what it visually could look
  • 00:26:09
    like then when you're developing your
  • 00:26:10
    integrated set of needs and we even
  • 00:26:12
    formulate a series of steps that could
  • 00:26:14
    be useful so you know you can think
  • 00:26:16
    about
  • 00:26:17
    everything holistically and you don't
  • 00:26:19
    miss major inputs
  • 00:26:21
    so
  • 00:26:22
    you know real highlight here
  • 00:26:24
    first you define the why what problem
  • 00:26:26
    are you trying to solve or your you know
  • 00:26:29
    opportunity that you're trying to
  • 00:26:30
    realize and you often to think about in
  • 00:26:32
    terms of mission
  • 00:26:34
    goals objectives and measures
  • 00:26:36
    mgos right and this idea is um you're
  • 00:26:40
    thinking about your problem or your
  • 00:26:42
    opportunity your mission goals
  • 00:26:43
    objectives and that'll start formulating
  • 00:26:47
    this idea that will eventually take the
  • 00:26:49
    form of life cycle concepts so your
  • 00:26:51
    initial architecture your initial
  • 00:26:53
    mission your initial set of use cases
  • 00:26:56
    but what is it you're trying to do let's
  • 00:26:58
    solve what thing are you trying to solve
  • 00:27:00
    and then
  • 00:27:01
    who's impacted define the who
  • 00:27:04
    you've got a lot of stakeholders that
  • 00:27:05
    could either be an acquirer or a
  • 00:27:07
    customer
  • 00:27:08
    you've got stakeholders that could be
  • 00:27:09
    users testers builders coders you've got
  • 00:27:14
    users who could be regulatory
  • 00:27:16
    they could be certifying they could be
  • 00:27:18
    safety
  • 00:27:19
    so you've got a lot of stakeholders that
  • 00:27:22
    ultimately will relate to your system in
  • 00:27:24
    some way look at things from their
  • 00:27:26
    viewpoint so then start defining what is
  • 00:27:28
    needed from their viewpoint right by
  • 00:27:30
    eliciting needs from those stakeholders
  • 00:27:32
    and there will be some prioritization
  • 00:27:35
    scheme you'll need to work out because
  • 00:27:36
    not everyone gets an equal vote and
  • 00:27:38
    there might be some conflicts between
  • 00:27:40
    what different stakeholders want but
  • 00:27:42
    you'll work through those
  • 00:27:44
    prioritizations some stakeholders get a
  • 00:27:46
    a bigger vote so to speak
  • 00:27:48
    um as you then go through that you're
  • 00:27:50
    going to think about your constraints
  • 00:27:51
    right you've got boundaries you've got
  • 00:27:53
    drivers things that will enable and
  • 00:27:55
    you've got constraints things you've got
  • 00:27:57
    to make sure you're within
  • 00:27:59
    operational environments as an example
  • 00:28:02
    um you will also have risks right
  • 00:28:04
    there's things out there that could be
  • 00:28:06
    your risk to success you need cyber
  • 00:28:08
    security potentially you know something
  • 00:28:09
    like that that could be a threat or a
  • 00:28:11
    risk to success like not enough money
  • 00:28:13
    not enough enough schedule and you'll
  • 00:28:15
    start working through those and
  • 00:28:16
    understand how they can influence your
  • 00:28:18
    system
  • 00:28:19
    and they might have needs that come out
  • 00:28:21
    from that
  • 00:28:22
    and then you go through some life cycle
  • 00:28:25
    concepts right and you think about your
  • 00:28:26
    life cycle concepts from several
  • 00:28:28
    perspectives so your life cycle concepts
  • 00:28:31
    analysis and maturation will ultimately
  • 00:28:33
    go look at use cases activities this is
  • 00:28:37
    where your model based systems
  • 00:28:38
    engineering really can help
  • 00:28:40
    as you start crafting out what the
  • 00:28:42
    system would do and start thinking about
  • 00:28:44
    then all your inputs your risks your
  • 00:28:47
    regulations your existing systems your
  • 00:28:49
    costs and ultimately through all of that
  • 00:28:52
    you'll develop an integrated set of
  • 00:28:54
    needs
  • 00:28:55
    now i have heard
  • 00:28:57
    that some folks would say but i have a
  • 00:28:58
    customer specification i don't need to
  • 00:29:00
    do all this well the example i'm going
  • 00:29:03
    to share with you today is actually
  • 00:29:04
    going to show what happens when you may
  • 00:29:06
    be at a lower level of assembly and you
  • 00:29:08
    have a customer specification and some
  • 00:29:11
    of this could still apply
  • 00:29:13
    so just because you might be at the end
  • 00:29:15
    of a contract where you're a producing
  • 00:29:18
    something for someone else doesn't mean
  • 00:29:20
    you don't get to do some subset of this
  • 00:29:22
    and likewise we would like to put more
  • 00:29:24
    emphasis on those who acquire systems to
  • 00:29:27
    make sure they do full justice to this
  • 00:29:30
    they think about truly what it is
  • 00:29:31
    they're trying to solve for many
  • 00:29:33
    viewpoints so when they do put the
  • 00:29:35
    requirements together for some sort of
  • 00:29:37
    you know acquisition contract it's a
  • 00:29:39
    complete set of requirements and looked
  • 00:29:41
    at from multiple perspectives
  • 00:29:46
    so
  • 00:29:47
    requirements come from the integrated
  • 00:29:49
    set of needs
  • 00:29:50
    the efforts described on the prior
  • 00:29:52
    slides ultimately talk about this
  • 00:29:55
    and it's the set of needs that will be
  • 00:29:57
    transformed to the set of requirements
  • 00:29:59
    which the system of interest is going to
  • 00:30:01
    be generated against
  • 00:30:03
    the approach in iso 1528 is to develop
  • 00:30:06
    stakeholder needs and requirements and
  • 00:30:09
    we recommend you actually instead think
  • 00:30:11
    about it in terms of an integrated set
  • 00:30:13
    of needs so we're not going to rewrite
  • 00:30:15
    15 to 88 those terms are still going to
  • 00:30:17
    be there but when you're actually
  • 00:30:19
    applying these concepts we believe
  • 00:30:22
    you'll look at all the different
  • 00:30:24
    influencers into what it is you're
  • 00:30:26
    developing come up with the integrated
  • 00:30:28
    set of needs and ensure that your
  • 00:30:30
    requirements stem from that
  • 00:30:32
    for the iterative and recursive concepts
  • 00:30:34
    here the set of needs is unique for each
  • 00:30:37
    level in the hierarchy and the system of
  • 00:30:38
    interest and this is actually worked at
  • 00:30:40
    each level and again my example will go
  • 00:30:42
    through a much lower level effort show
  • 00:30:44
    you how that can be done
  • 00:30:47
    but before i go to my example i want to
  • 00:30:48
    talk about our second recommendation
  • 00:30:50
    which is verification and validation in
  • 00:30:52
    context
  • 00:30:53
    those terms don't mean the same thing
  • 00:30:55
    they are distinctly different depending
  • 00:30:57
    on how they're used
  • 00:30:59
    unfortunately they're often used
  • 00:31:00
    interchangeably
  • 00:31:01
    and
  • 00:31:03
    unless we're clear on the context of use
  • 00:31:06
    uh people may think that they're
  • 00:31:08
    validating something when they're really
  • 00:31:10
    verifying something right and so what
  • 00:31:12
    what does that mean
  • 00:31:13
    this idea of needs verification and
  • 00:31:15
    needs validation well we can talk about
  • 00:31:18
    that but that's that idea of you're
  • 00:31:21
    dealing with your need expressions are
  • 00:31:23
    they correct and are they right
  • 00:31:25
    and are they high quality are they
  • 00:31:27
    written well and are they the right
  • 00:31:29
    needs you get to your requirement
  • 00:31:31
    verification and validation are they
  • 00:31:32
    correct are they right
  • 00:31:34
    your design
  • 00:31:36
    and your system so these all these
  • 00:31:37
    different aspects and so there's visuals
  • 00:31:39
    that go along with this one because it
  • 00:31:41
    can be quite a lot to to think about so
  • 00:31:43
    this is a figure and it's actually
  • 00:31:45
    already out of date because the system
  • 00:31:47
    engineering handbook is still in
  • 00:31:48
    development but this is a figure
  • 00:31:50
    that we have that's going into version
  • 00:31:53
    five of the system engineering handbook
  • 00:31:55
    it tries to put the idea of verification
  • 00:31:57
    and validation in context so again we
  • 00:32:00
    start real here with the stakeholder
  • 00:32:02
    real world expectations and they get
  • 00:32:03
    transformed to
  • 00:32:05
    integrated set of needs or in the 15 to
  • 00:32:08
    88 words stakeholder needs and
  • 00:32:10
    requirements
  • 00:32:12
    and they are validated against that
  • 00:32:15
    ultimate concept of what the
  • 00:32:17
    stakeholders wanted right
  • 00:32:19
    and you get to your system requirements
  • 00:32:21
    then and they are validated against well
  • 00:32:24
    those integrated set of needs you
  • 00:32:25
    developed then and so on so we're going
  • 00:32:28
    to talk a little bit about what should
  • 00:32:29
    each of these lines mean shortly but the
  • 00:32:32
    idea is verification and validation
  • 00:32:34
    happens throughout your life cycle and
  • 00:32:36
    it happens against different things
  • 00:32:39
    so key concept then what i just said
  • 00:32:43
    each stage of the life cycle addresses
  • 00:32:44
    quality and content of your development
  • 00:32:46
    artifacts validation is more important
  • 00:32:49
    than verification we're going to state
  • 00:32:50
    that boldly it's better to build the
  • 00:32:52
    right thing
  • 00:32:53
    than to build the wrong thing right
  • 00:32:55
    right so validation is against a set of
  • 00:32:57
    needs that represent key stakeholders
  • 00:33:00
    and not just the customer
  • 00:33:02
    and needs requirements verification and
  • 00:33:04
    validation are the common threads that
  • 00:33:05
    tie all the system engineering
  • 00:33:06
    activities together so we see this
  • 00:33:08
    interwoven throughout the entire
  • 00:33:10
    development life cycle
  • 00:33:13
    so when you think about requirements
  • 00:33:15
    verification then you think about the
  • 00:33:17
    term
  • 00:33:18
    verification of the requirement
  • 00:33:20
    statements
  • 00:33:21
    and that ultimately is against are they
  • 00:33:24
    right are they um defined correctly
  • 00:33:27
    right um are they is the math right you
  • 00:33:30
    know did we use good conventions
  • 00:33:32
    um
  • 00:33:35
    your design verification is against best
  • 00:33:37
    practices and requirements in other
  • 00:33:39
    words we also make sure conforms to the
  • 00:33:42
    requirements and we make sure we use the
  • 00:33:44
    best practices for design for our
  • 00:33:46
    organization or industry
  • 00:33:50
    system verification against the design
  • 00:33:52
    artifacts
  • 00:33:54
    did we build the right system i mean in
  • 00:33:55
    terms of is it built right
  • 00:33:58
    and we look at it against the
  • 00:33:59
    requirements so it's built correctly and
  • 00:34:02
    satisfies the requirements
  • 00:34:05
    needs validation is against that
  • 00:34:07
    stakeholder set of original inputs
  • 00:34:10
    but after that everything is against
  • 00:34:12
    those needs
  • 00:34:13
    system requirements are checked against
  • 00:34:15
    the needs that's how they're validated
  • 00:34:17
    to be the right requirements
  • 00:34:19
    your design is checked against the needs
  • 00:34:22
    that's how we know we've got the right
  • 00:34:24
    design because it's against what the
  • 00:34:27
    stakeholders needed
  • 00:34:29
    and you realize system of interest is
  • 00:34:31
    checked against the needs
  • 00:34:35
    so i'm going to go on our third concept
  • 00:34:37
    and then i'm going to go into an example
  • 00:34:39
    because this is a lot that i've gone
  • 00:34:40
    through and again it's not the entire
  • 00:34:42
    set of information we'd like to relay
  • 00:34:44
    from our needs and requirements manual
  • 00:34:46
    but i think these are the three
  • 00:34:47
    takeaways i'd love for you to have
  • 00:34:49
    so the last takeaway of course is the
  • 00:34:50
    thing that enables all of this to work
  • 00:34:52
    together which is the data centric
  • 00:34:54
    approach
  • 00:34:55
    here's an artifact from our needs and
  • 00:34:57
    requirements manual it's a slight update
  • 00:34:59
    from the figure we had in the integrated
  • 00:35:01
    data as a foundation of system
  • 00:35:02
    engineering white paper
  • 00:35:04
    and
  • 00:35:05
    what you see here is a lot of your
  • 00:35:08
    artifacts so to speak are all really
  • 00:35:10
    part of an integrated or federated
  • 00:35:12
    shareable set of data now this could be
  • 00:35:14
    a uber tool or it could be a set of many
  • 00:35:17
    different tools but there's a single
  • 00:35:19
    source of truth and it is based on the
  • 00:35:20
    data that's there and you can leverage
  • 00:35:23
    data instead of just
  • 00:35:26
    duplicating it manually through a series
  • 00:35:28
    of documents and this is where the world
  • 00:35:30
    is going through the lot of our digital
  • 00:35:32
    engineering work that you see happening
  • 00:35:34
    and so the idea is you get the right
  • 00:35:36
    tool sets uh going on in your
  • 00:35:38
    organization and they all talk to each
  • 00:35:41
    other so you can have your needs and
  • 00:35:42
    requirements talk to your design
  • 00:35:44
    artifacts
  • 00:35:46
    talk to your test or you know build
  • 00:35:49
    artifacts and ultimately you can produce
  • 00:35:52
    reports
  • 00:35:53
    metrics other artifacts things that can
  • 00:35:56
    satisfy uh your your contract so this
  • 00:35:59
    data centric practice versus a document
  • 00:36:02
    century practice really enables that
  • 00:36:03
    single source of truth and it ultimately
  • 00:36:06
    enables you to get your system um
  • 00:36:09
    validation through all these artifacts
  • 00:36:11
    that intertwine we think it's just an
  • 00:36:13
    enabler
  • 00:36:14
    could you do a system without being data
  • 00:36:17
    centric yes and they have for many years
  • 00:36:20
    but it is an enabler and perhaps even a
  • 00:36:22
    little bit more precise if you do have
  • 00:36:25
    that data centric capability
  • 00:36:29
    so again then you get your data
  • 00:36:31
    traceability you would ultimately have
  • 00:36:34
    all the threads to get your validation
  • 00:36:36
    and your verification
  • 00:36:38
    addressed so your different parts your
  • 00:36:39
    life cycle
  • 00:36:42
    so i'd like to give you an example
  • 00:36:43
    application particularly with this
  • 00:36:45
    aspect of developing an integrated set
  • 00:36:46
    of needs at a lower level because most
  • 00:36:49
    people i have talked to you think this
  • 00:36:50
    is the reason you don't do it you have a
  • 00:36:53
    contract you're just going to deal with
  • 00:36:54
    that spec
  • 00:36:55
    why would you try to develop an
  • 00:36:57
    integrated set of needs
  • 00:37:00
    so let's talk about in a sample
  • 00:37:03
    problem right
  • 00:37:04
    so we've got this
  • 00:37:07
    company you know fictitious company
  • 00:37:10
    with a potential customer um and they've
  • 00:37:12
    given them a spec a specification an
  • 00:37:14
    operational concept
  • 00:37:16
    and this this company has a project
  • 00:37:18
    proposal team who then just develops
  • 00:37:20
    this concept the system of interest
  • 00:37:22
    concept that complies with those those
  • 00:37:24
    operational concepts and the
  • 00:37:26
    specification so it basically looks like
  • 00:37:28
    it'll do the job
  • 00:37:30
    and they model it how will it do the job
  • 00:37:32
    right you know what are the activities
  • 00:37:33
    and use cases that show can handle those
  • 00:37:35
    concepts
  • 00:37:36
    and then they start looking at their
  • 00:37:38
    their view of internal external
  • 00:37:41
    stakeholders okay who beyond the
  • 00:37:43
    customer will interface with the system
  • 00:37:46
    right does it need to be regulated
  • 00:37:48
    licensed um is there safety you know
  • 00:37:50
    implications
  • 00:37:52
    how is it going to be produced how is it
  • 00:37:53
    going to be tested how it's going to be
  • 00:37:55
    certified you know there's all these
  • 00:37:57
    different concepts of where we're going
  • 00:37:58
    to build it right and they start
  • 00:38:00
    thinking about all of this
  • 00:38:02
    and not all of that specified in a
  • 00:38:03
    customer stack right that's really their
  • 00:38:06
    own way to develop their product a lot
  • 00:38:08
    of it is very unique to them
  • 00:38:10
    so they're going to generate an
  • 00:38:12
    integrated set of needs by capturing
  • 00:38:14
    these life cycle concepts their use
  • 00:38:16
    cases
  • 00:38:17
    throughout both perhaps build and
  • 00:38:20
    operations maybe disposal
  • 00:38:23
    they'll look at expected functions this
  • 00:38:25
    is where you start getting into your
  • 00:38:26
    functional analysis they start looking
  • 00:38:29
    at performance they'll start looking at
  • 00:38:31
    constraints
  • 00:38:32
    and through that then they'll get an
  • 00:38:34
    integrated set of needs that are traced
  • 00:38:36
    to different stakeholders to different
  • 00:38:37
    customer documentation like conops
  • 00:38:40
    statement of work online items and
  • 00:38:42
    they'll get a system model where they'll
  • 00:38:44
    build this traceability model then of
  • 00:38:47
    this integrated set of needs to both the
  • 00:38:49
    sources of where they come from and how
  • 00:38:51
    they're going to be implemented in the
  • 00:38:53
    system of interest
  • 00:38:55
    and during their concept design
  • 00:38:56
    development the team will also ensure
  • 00:38:58
    the system of interest concepts just
  • 00:39:00
    address the need uh those needs as well
  • 00:39:02
    as the customers back right so they're
  • 00:39:04
    gonna look at it in both terms
  • 00:39:05
    contractual compliance and also does it
  • 00:39:08
    really solve the problem that's trying
  • 00:39:10
    to be solved and can we produce it can
  • 00:39:12
    we test it right is this thing
  • 00:39:14
    achievable
  • 00:39:16
    as they go then they look at the
  • 00:39:17
    integrated set of needs they're going to
  • 00:39:18
    put attributes against them and they may
  • 00:39:20
    be simple but little things like
  • 00:39:22
    criticality priority right risk because
  • 00:39:26
    some of these needs might be really more
  • 00:39:28
    important in terms of system validation
  • 00:39:31
    than others
  • 00:39:32
    right um and and the system acceptance
  • 00:39:36
    uh might be based on a few of the needs
  • 00:39:38
    compared to all of them so they're going
  • 00:39:39
    to prioritize them they're going to mark
  • 00:39:41
    them somehow and then they'll develop
  • 00:39:43
    their validation plans against the shall
  • 00:39:45
    we say highly critical highly
  • 00:39:46
    prioritized set of needs
  • 00:39:49
    they could choose all of them but you
  • 00:39:51
    know maybe it's really more important to
  • 00:39:53
    spend their time on the bang for the
  • 00:39:56
    buck type of needs where they know these
  • 00:39:58
    are the most important the system can be
  • 00:39:59
    validated when these are addressed these
  • 00:40:01
    others are enablers to ensure the system
  • 00:40:04
    will really work well
  • 00:40:07
    so some examples right of some set of
  • 00:40:10
    needs they uncover as they go through
  • 00:40:11
    and look at all their different
  • 00:40:13
    stakeholders and these are based on
  • 00:40:16
    functional decomposition and analysis
  • 00:40:17
    from their life cycle concepts they're
  • 00:40:19
    based on their stakeholder inputs and
  • 00:40:21
    reviews
  • 00:40:22
    but their customer needs their system
  • 00:40:24
    operational by 2026 right that's kind of
  • 00:40:27
    a constraint that got put in place so
  • 00:40:29
    they don't have forever to develop this
  • 00:40:31
    thing
  • 00:40:32
    customer needs a system to support
  • 00:40:34
    activities
  • 00:40:35
    and the operational concepts provided in
  • 00:40:37
    the request for proposal right so
  • 00:40:39
    there's very specific life cycle
  • 00:40:41
    concepts and and mission type concepts
  • 00:40:43
    that need to be addressed so that's a
  • 00:40:45
    source of their derived functions they
  • 00:40:46
    should start working use cases and
  • 00:40:48
    activities for those
  • 00:40:50
    the system of interest operators need a
  • 00:40:52
    method to upload new configurable
  • 00:40:54
    parameters during the mission and that's
  • 00:40:56
    actually a derived function they come
  • 00:40:57
    out as they start working through those
  • 00:40:58
    lifecycle concepts and they realize you
  • 00:41:01
    know as it's being used from the user
  • 00:41:02
    perspective they need to be able to
  • 00:41:04
    upload something real time
  • 00:41:07
    customer needs to leverage existing
  • 00:41:09
    operation infrastructure and software
  • 00:41:10
    well there's an interface constraint
  • 00:41:12
    right so all of a sudden our solution
  • 00:41:14
    space whittles down a little bit because
  • 00:41:15
    of this need from the customer
  • 00:41:18
    and that gets into that that boundaries
  • 00:41:20
    those drivers and constraints
  • 00:41:23
    the company's production team needs to
  • 00:41:25
    be able to transport the system within
  • 00:41:27
    their facilities right so we got to be
  • 00:41:29
    able to pick it up move it around right
  • 00:41:31
    and all of a sudden that gets into a
  • 00:41:32
    little bit of design
  • 00:41:34
    you know characteristics that need to
  • 00:41:36
    exist maybe they need some lifting and
  • 00:41:38
    handling features maybe they need to
  • 00:41:39
    develop some support equipment or use
  • 00:41:41
    some existing ones
  • 00:41:43
    the project test team needs to be able
  • 00:41:45
    to connect their test equipment to the
  • 00:41:46
    system to provide power upload software
  • 00:41:49
    send commands obtain telemetry inputs
  • 00:41:51
    all of a sudden now maybe you need test
  • 00:41:52
    ports right and compatible software now
  • 00:41:55
    this isn't something your customer is
  • 00:41:57
    necessarily going to put in a
  • 00:41:58
    specification right this is something
  • 00:41:59
    you'll develop at your level and realize
  • 00:42:01
    oh we need to think about how we're
  • 00:42:03
    going to do these activities even before
  • 00:42:05
    we deliver it
  • 00:42:06
    and then of course company leadership
  • 00:42:08
    strategically needs to leverage work
  • 00:42:10
    done on a prior effort right so all of a
  • 00:42:13
    sudden it's like i would like to reuse
  • 00:42:15
    stuff instead of reinvent stuff because
  • 00:42:17
    that's a better use of our resources and
  • 00:42:19
    it might drive down our costs on this
  • 00:42:21
    product
  • 00:42:22
    so that becomes a bit of a design
  • 00:42:24
    constraint because now we're kind of
  • 00:42:26
    forced into using an existing thing
  • 00:42:28
    versus a big open you know field of
  • 00:42:30
    design work so you see all of a sudden
  • 00:42:33
    these integrated set of needs aren't
  • 00:42:34
    necessarily dictated from the customer
  • 00:42:36
    some of them are but some of them are
  • 00:42:38
    very internal to this company at that
  • 00:42:40
    level of assembly
  • 00:42:42
    so then what would that look like when
  • 00:42:44
    we start thinking about our requirement
  • 00:42:45
    space
  • 00:42:47
    so after contract award this team
  • 00:42:49
    captures this final customer
  • 00:42:51
    specification right in the in their
  • 00:42:53
    requirements tool so we're getting a
  • 00:42:54
    data centric practice and they refine
  • 00:42:57
    their concept model based on final
  • 00:42:58
    agreement with the uh customer
  • 00:43:01
    and then they scrub their integrated set
  • 00:43:02
    of needs for any additional needs to
  • 00:43:05
    ensure that they're still the right
  • 00:43:06
    needs you know they didn't miss any
  • 00:43:07
    stakeholders they're still accurate per
  • 00:43:09
    the contract
  • 00:43:11
    and they start to build their
  • 00:43:12
    traceability model you know they've got
  • 00:43:14
    their needs that they've derived and
  • 00:43:16
    they're integrated and they've got this
  • 00:43:17
    customer contractual specification
  • 00:43:20
    and they start thinking about all those
  • 00:43:22
    other contract documents you know maybe
  • 00:43:24
    there's some standards they have to meet
  • 00:43:25
    some icds that are placed in front of
  • 00:43:27
    them and they start to capture those in
  • 00:43:29
    their data model as well kind of make
  • 00:43:32
    this holistic set of requirements then
  • 00:43:34
    into this middle layer called the system
  • 00:43:36
    of interest requirements
  • 00:43:38
    you could bypass that level and if your
  • 00:43:41
    data is centric you could still look at
  • 00:43:42
    all of this holistically up here in the
  • 00:43:44
    top but sometimes people like to see a
  • 00:43:47
    compartmentalized holistic set of system
  • 00:43:50
    of interest requirements that come from
  • 00:43:51
    both your customer so you're going to be
  • 00:43:54
    contractually compliant
  • 00:43:56
    and your integrated set of needs all
  • 00:43:58
    those derived functions all those
  • 00:44:00
    capabilities all those constraints
  • 00:44:02
    and
  • 00:44:03
    ultimately that's what's going to be
  • 00:44:05
    translated then into your lower level
  • 00:44:08
    set of design input requirements for
  • 00:44:11
    your teams this could be your internal
  • 00:44:13
    design teams or at some point you may
  • 00:44:15
    spin off a specification that goes into
  • 00:44:18
    another contract to another supplier who
  • 00:44:21
    then might do the same exercise at their
  • 00:44:23
    level as they start building the thing
  • 00:44:25
    that will help feed your system of
  • 00:44:26
    interest
  • 00:44:28
    now every one of those system of
  • 00:44:29
    interest requirements is traceable to a
  • 00:44:31
    customer requirement or a derived or
  • 00:44:33
    integrated set of need um there's a
  • 00:44:36
    source there right
  • 00:44:37
    and the system of interest requirements
  • 00:44:40
    they could be allocated out or perhaps
  • 00:44:42
    that is the level you're designing to
  • 00:44:45
    um and then you know you start thinking
  • 00:44:48
    about what would we verify against and
  • 00:44:50
    what would we validate against so we're
  • 00:44:52
    going to get to that but first you start
  • 00:44:54
    thinking about all my data is now
  • 00:44:55
    connected i've got my needs i've got my
  • 00:44:58
    requirements now i'm going to start
  • 00:44:59
    building my design i've got verification
  • 00:45:01
    plans i've got test plans and this is
  • 00:45:04
    where you start building and
  • 00:45:05
    interconnecting your models maybe you've
  • 00:45:07
    got some mbse models for your various
  • 00:45:11
    parts of your architecture and your
  • 00:45:13
    functions and your behaviors you might
  • 00:45:15
    have some mathematical models that are
  • 00:45:17
    connected in there so your data is all
  • 00:45:20
    integrated together and now you're able
  • 00:45:21
    to show progress and compliance towards
  • 00:45:24
    those requirements and those needs
  • 00:45:28
    and then as you
  • 00:45:30
    build your system of interest whether
  • 00:45:33
    it's a product a hardware software or a
  • 00:45:36
    service
  • 00:45:37
    you're able to ultimately verify
  • 00:45:40
    against your system of interest
  • 00:45:42
    requirements
  • 00:45:43
    and you're able to validate against that
  • 00:45:45
    integrated set of needs that ultimately
  • 00:45:47
    showed you built the right thing
  • 00:45:50
    and you achieved your stakeholder
  • 00:45:52
    expectations
  • 00:45:55
    now i'm going to talk a little bit about
  • 00:45:56
    where to learn more and then i'm more
  • 00:45:58
    than happy to take questions and i know
  • 00:45:59
    lou will as well
  • 00:46:01
    um so this is the needs and requirements
  • 00:46:03
    manual
  • 00:46:04
    and it was
  • 00:46:06
    originally released in january we did a
  • 00:46:07
    minor update to it in may
  • 00:46:10
    it does align with what's coming out in
  • 00:46:12
    the in cozy system engineering handbook
  • 00:46:14
    version 5 which will be released next
  • 00:46:16
    summer
  • 00:46:19
    we have an external website and we do uh
  • 00:46:22
    put a lot of links on there as well and
  • 00:46:24
    we also highlight upcoming events so we
  • 00:46:26
    have monthly meetings in the
  • 00:46:27
    requirements working group we spend a
  • 00:46:29
    lot of time maybe talking about this
  • 00:46:30
    topic or we'll talk about uh things
  • 00:46:33
    we're doing with other groups like uh
  • 00:46:35
    coming up here in
  • 00:46:37
    august 24th we've got an exchange cafe
  • 00:46:40
    with beth wilson we're going to talk
  • 00:46:41
    about system of system
  • 00:46:44
    versus you know how we can handle the
  • 00:46:46
    needs and requirements manual and apply
  • 00:46:48
    it to a system of systems
  • 00:46:50
    so we're definitely happy to have people
  • 00:46:52
    even lurk if you don't want to join the
  • 00:46:54
    requirements working group but you just
  • 00:46:56
    want to pay attention maybe join some of
  • 00:46:58
    our cafes or some of our presentations
  • 00:47:00
    this is where you can learn about what's
  • 00:47:02
    coming up however you're also welcome to
  • 00:47:05
    join it's it's we don't bother anybody
  • 00:47:06
    we just send regular information and
  • 00:47:08
    communication and you do that on your
  • 00:47:10
    cozy member profile by joining a
  • 00:47:12
    committee you can join a requirements
  • 00:47:13
    working group or any other working group
  • 00:47:17
    and then the youtube channel um you
  • 00:47:19
    don't even need to be in and cozy to
  • 00:47:21
    watch the youtube channel but we put a
  • 00:47:22
    lot of information on here like this
  • 00:47:24
    talk today many resources from lou and
  • 00:47:27
    others
  • 00:47:28
    that help people on all things related
  • 00:47:31
    to requirements or needs and
  • 00:47:32
    requirements
  • 00:47:34
    and then just some some thoughts before
  • 00:47:36
    we go into any questions which is
  • 00:47:39
    we believe a larger focus on the
  • 00:47:41
    integrated set of needs during the
  • 00:47:42
    stakeholder needs and requirements
  • 00:47:44
    definition technical process
  • 00:47:47
    combined with this use of data-centric
  • 00:47:49
    approach towards developing this this
  • 00:47:51
    material enables a system development
  • 00:47:53
    effort that ultimately will satisfy your
  • 00:47:55
    stakeholders
  • 00:47:56
    system engineers
  • 00:47:58
    all of you
  • 00:47:59
    are encouraged to download and start
  • 00:48:01
    using this material you can get the
  • 00:48:03
    manual you can get the guides start
  • 00:48:05
    using it start looking at the examples
  • 00:48:07
    and and really what we're also looking
  • 00:48:09
    for is feedback we would love to see
  • 00:48:12
    practical application of this material
  • 00:48:15
    and we want to hear from the users on
  • 00:48:17
    what works well what may have missed the
  • 00:48:19
    mark what may have not been clear
  • 00:48:22
    maybe even some other examples would be
  • 00:48:24
    great to include
  • 00:48:25
    um
  • 00:48:27
    so
  • 00:48:27
    you can send information to me
  • 00:48:30
    and as the chair and and we'll make sure
  • 00:48:32
    it gets distributed for our next round
  • 00:48:34
    of updates louie craft is also happy to
  • 00:48:37
    take uh input um but this is definitely
  • 00:48:40
    something where encourage those of you
  • 00:48:42
    here uh listening to this material just
  • 00:48:44
    start using the material and give us
  • 00:48:46
    feedback on it there are forms i guess
  • 00:48:48
    that you could fill out and give us
  • 00:48:50
    comments or you could just email us
  • 00:48:51
    directly redlines or comments as well
  • 00:48:54
    and with that being said i haven't paid
  • 00:48:56
    too much attention to the chat but i'm
  • 00:48:58
    certainly welcome
  • 00:48:59
    anything that
  • 00:49:01
    someone may want to comment on or ask
  • 00:49:02
    questions on and and lou as well i think
  • 00:49:05
    is on and he can also weigh in
Tags
  • systemdesign
  • krav
  • behov
  • INCOSE
  • validering
  • interessenter
  • datadrevet
  • vejledning
  • manuelle
  • ingeniør