now just a quick reminder of the software development life cycle. And this says for the cloud, That's true. But it's still the software development life cycle, right? Just may be slightly different considerations. So we start with planning requirements, analysis. All business requirements should be defined and risks should be identified.
This might be where we're working with a cloud broker
that can kind of help us understand what we're really trying to accomplish. Help us convey there's needs to the Cloud Service provider
because ultimately, like I said, they're many kind of out of the box implementations that every organization has their own specific needs and requirements. Service level agreements. What are the risks that we're concerned with? So that's the first piece planning in requirements analysis.
The second piece is, let's take kind of these lofty ideas what our needs are, and let's map them too specific,
attainable requirements, things that can be measured, things that can be documented and tracked and accounted for.
We from their move into designing. And this is where your cloud service provider comes back to us with the solution. As a matter of fact, a lot of times you might hear the 1st 2 phases being as the problem space
and then designing and developing. It's the solution space, meaning the customer provides the plans. You know, here the planning and requirements analysis. Here's what we need. And then they trains like that make it clear what they need. But from the design, that's how we're going to solve the problem that the customer came to us with.
So designing where to take the hardware in the system requirements and figure out what architecture
is going to be necessary to implement in order to meet customers needs.
Now in the developing piece. This is where the work is divided up the specific modules of functionality or sign. And this is where we get to work
I think it was Winston Churchill. Don't quote me on this, But he said, No matter how brilliant your planning,
you should probably still conduct tests now. I think that's very wise idea. So this is where the penetration, testing, the vulnerability assessments and 10 testing happened. This is where really we would go through the technical evaluations off the security features of the environment to make sure that, um
uh the application's gonna meet our needs.
We want to think about, um, use your acceptance testing. Can our users access and provide? Does the application provide the service? Is that the user's need? So at the end of this piece is really where the testing happens on all aspects resiliency, testing, integration, testing all those pieces.
And then we come into maintenance.
Ah, just ongoing monitoring. Making sense, sure that we continue to monitor the environment so that we're making sure that our agreements are met.