Objectives and Types of System Development

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
or

Already have an account? Sign In »

Time
5 hours 58 minutes
Difficulty
Intermediate
CEU/CPE
6
Video Transcription
00:00
>> Welcome back to Cybrary ISP,
00:00
of course, I'm your instructor Brad Rhodes.
00:00
Let's jump into Module 8,
00:00
the system development life cycle.
00:00
Where are we on our ISP journey?
00:00
Well, we just finished Module 7, the ISSE process,
00:00
which took and applied hopefully for you all of
00:00
the different things we've talked about
00:00
in the ISP domains.
00:00
Now, we're into the system development lifecycle.
00:00
Module 8, where we're going to talk through
00:00
how systems engineer's from
00:00
a NIST perspective actually
00:00
develop and build their creations if you will.
00:00
Then we'll follow on and talk very specifically about
00:00
key NIST standards you need to
00:00
know for the ISP exam in Module 9.
00:00
In this video, we're going to cover
00:00
our module objectives briefly,
00:00
and then we're going to review real quick
00:00
the types of development because that's going to
00:00
be important in our discussions
00:00
of the system development life cycle.
00:00
Our module objectives here are pretty straightforward.
00:00
We're going to real quickly adjust [LAUGHTER] the slide,
00:00
we're going to review those development types.
00:00
You want to have those in the back of your head
00:00
when you think about the SDLC.
00:00
Then we're going to investigate
00:00
the five phases of the system development life cycle,
00:00
which is the standard now.
00:00
It's actually about to change into something else,
00:00
which we'll talk about in our NIST standards.
00:00
Remember there are four development capabilities
00:00
or development processes we've talked about.
00:00
The first one we talked about was waterfall.
00:00
That's cascade of processes, it's very linear,
00:00
created in the 1970s,
00:00
and very hard to change as you went through the process.
00:00
Sometimes from a systems
00:00
engineering perspective with waterfall,
00:00
you get to the very end and you don't have the product
00:00
that you quite expected you were going to
00:00
get and that's the danger of waterfall.
00:00
The next developed in the 1980s
00:00
was the systems engineering VEE.
00:00
That's where we go from concept development
00:00
all the way to transition, operations,
00:00
and maintenance after we've
00:00
tested, and in this case here,
00:00
this is where we really saw the terms
00:00
of verification and validation.
00:00
Where verification is determining
00:00
whether we met requirements
00:00
and validation it does the product,
00:00
the security control,
00:00
the system, the capability, whatever.
00:00
Does it meet the mission or business needs?
00:00
As we talked about multiple times,
00:00
it is possible to verify a product but not validate it.
00:00
Of course, in the 1990s,
00:00
we saw the beginnings of something called spiral.
00:00
This is one of the first processes where we
00:00
saw iterative process to product development.
00:00
That's where we saw prototyping.
00:00
This is the first introduction of prototyping.
00:00
What was nice about that one in specific to
00:00
spiral is that now if a prototype didn't quite work,
00:00
you could go back
00:00
reprototype and move forward. That was nice.
00:00
Then, of course, the CUDA Graal,
00:00
if you will, of development cycles,
00:00
is the Agile process.
00:00
[NOISE] Agile itself is
00:00
a widely-used process across
00:00
multiple industry verticals now,
00:00
not just security, not just information systems in IT,
00:00
but all over the place you see Agile apply.
00:00
Because Agile conceptually is
00:00
a great way to get all products out the door.
00:00
Agile is the other product type or
00:00
product development cycle that we've talked about.
00:00
In this video, what did we cover?
00:00
We reviewed our module objectives,
00:00
and we briefly walked
00:00
through development models because
00:00
you need to have them in
00:00
your head for a quick portion of
00:00
the system development life cycle that we're
00:00
going to talk about. We'll see you next time.
Up Next