8.2 Business Analysis and Complicated Modeling Part 2
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *
Already have an account? Sign In »
6 hours 23 minutes
So now what we're gonna do is we're going to do a prideful exercise. I'm not going to go super in depth, but it's kind of show you
how, like maybe online shopping cart might look from a business process model on some of the questions that we might want to ask
during that process. But remember,
this is a complicated problem. This is not a complex problem.
This is a finite number of variables that you can imagine in your head right now, when you're building an online shopping cart,
there's only a certain number of things that people conduce you in order to gain access or to interact with that website, right? So I'm gonna go ahead and go over to visual Designer. This is because it's for the Mac.
There is video, which is the most common one for a window of based computers,
but they all worked relatively similar. So what I've got here is I've got some serious of shapes,
some of the shapes, some places. Have you no specific rules for about the shapes and tail like, for example, this is often used as like a termination process. The final notice what it says right here,
another agencies. And so I don't have rules. The only really hard and fast rule that I have seen enforced across all different organizations
is that the diamond usually indicates some sort of decision tree. Right. So I've got these four objects in front of me.
I know that my input is going to be accessed the website, and that's pretty much gonna be it. Like there's really no way to access any of the Web site functionality, necessarily without first accessing the Web site. So whenever possible, when you're doing complicated business process modeling,
if you can create a single input,
a single output
Well, actually, don't worry so much about the output, but a single input
input process output. Right. So your input there's a series of things that can happen.
Make sure you tie all those together. You don't have any hanging out there, and then you have your output. So I'm gonna go ahead and click the little
connector button here and I'm gonna say Okay, So when I accessed the website, I have the option to Loggins.
Maybe I have another option two shot by category
and another option is shot by item so you might think of these is like menu items on top of a particular website.
Now, if I choose the logging option, let's just say I'm gonna have another process I'm gonna drag out over here,
and I'm gonna say, Okay, if you log in that I need to present
Oh, are prompt for a user name and password.
So that's what I'm gonna basically tell the programmer when, uh when and if this business process model is approved,
don't lie. I thought, Let me do an enter.
There it goes. We'll see if that makes it better.
Right? Well, it's good enough for now.
Um, so I'm gonna promise for a user name and password, so if my user clicks log in,
then I do that, and you can even put in here. Usually they let your type text
No, I didn't like that. Okay.
So I would put right here a little yes option and say okay, if if this action is undertaken, then prompt for a user name and password.
Okay. Well, that's good. Then what do I do? Well, now, this is gonna lead to another process or even possibly a decision. Tree
So when I prom for a user name and password,
that website somehow gonna have to communicate with the database and determine whether that user name and password is valid.
So let me just use a decision box for now, because it will be easier. And I could go back and change this, obviously, if I needed to.
Um, So the question is, is it valid? So it's gonna ping back to the database, and it's gonna prompt,
and it's gonna basically try toe authenticate that user
user name and password, determine whether it's valid. Okay, If it's not valid,
then I need to do something else. Right. So I'm gonna show
invalid dot a S p X. That's just gonna be a Web page that says that they their username and password is not valid.
And what do I do if it is valid? If it is valid, I'm gonna take them to my account page. Okay,
so I'll bring that over here.
I'm going to say redirect to my account. That s
and again, I'm just making this up on the fly. This is not any kind of real specific to any one individual upside, but it's kind of pretty standard across most websites. This is basically how they kind of flow out.
So I'm gonna redirect. Okay, Great
on. And then again in here, I'd want to put a text box if I could get again. No, I just have to figure out a put text boxes on the lines. But, uh, once I put the text box in there, that would say yes.
And the other one would say no. Okay.
Now, is that the end of that process? Not necessarily what we can get to that later.
So then I got my shot by category options so they haven't logged in, but they want a shot by category. So if they click that button, what am I going to do? So I'm gonna go to category
I think I spelled it wrong,
but basically, I'm just gonna have them go to that web page. And then and then I'm going to have another process flow that's going to exist either on another document or later on this document
That's going to specify what options are available to them when they go to category. Uhm so then you've got long in shop by category shot by item. You might have a key word search
so you could d'oh! Keyword search
that could have its own Siri's of functionality based on that.
Now, the key thing about this business process modeling, and I like to use flow diagrams because, well, twofold. One.
Very few people, in my experience once sit there and read hundreds and hundreds of pages of requirements documentation that just tends to Ben. And then they zone out and they don't get it.
Whereas a picture kind of tell that that picture's picture's worth 1000 words, it really shows you what's going to happen with this new system that you built.
For example, the biggest flow diagram that I did.
I was in 12.5 using busy Oh, nothing
super big. I mean, actual objects were fairly small, but when we printed it out on a slaughter paper, it took up like a 16 by eight foot wall, 16 feet wide, eight feet tall.
But what made it really interesting and cool to have that level of business process analysis done via flow chart?
any given point during our discussions in our meeting, somebody could walk up to the wall point to the specific process or decision box that we were talking about
and really flow it all the way out to the very end of the process.
um, that's why I like I like the visual aid of this type of thing.
The second thing I like about this is as a
I t person or programmer developer, we're gonna call it.
What I conducive with this is look for what's called open loops.
So any time that I can go from just to this to this and I don't have like, for example, under this diamond, I don't have to,
uh, guess And no option I haven't opened loop. So, for example, right now, this logging has an open loop.
If you click the log in, it does this. If you don't click log in, you know, then what else? What could do? So any time you have an open loop,
what? You open yourself up to our holding your process and therefore holes in your program. So if somebody, for example, goes to category I s P X, and you don't
allow them to then log in during the select a category, select a product at it to my car. Check out.
You got sort of a noble oot there because at no point did you redirect them back to this log in functionality.
So using ah video were a flow chart type document for business process. Analysis is a really good way to also spot those open loops. And as you can see from my sample, we do have some open loops. And, of course, if I was doing this for Riel,
I would make sure I connect. For example, all of these would have to be connected because if they don't choose long in,
then did they choose shot by category. If they didn't you shot by category. So it's on.
So they have to do something. I have to close all those loops and have some sort of functionality that's going to prevent them from finding a hole in my online shopping cart.
That's a very brief
exercise, but it's kind of give you an idea of what business process smiling looks like. And again, that's for complicated problems. You cannot model via busy Oh, how hurricane forms or how a school of fish is going to interact with water and change directions. Right? That's just too many variables.
But for things with a finite number of variables,
business process modeling is a great way to get everybody on the same page. And it's definitely one of the things that,
um, we really have learned and taken
Frederick Winslow Taylor's findings the heart and really improve the efficiency of almost every organization in the last 100 150 years.
So in summary,
we went over business analysis today, and we also went over a complicated process. Modeling
next lesson will go over a complex process modeling.
I want to thank you for your time and have a great day.