to Siskel Certified Design Associate. C T G A
I'm your instructor wing.
In a previous video, we introduced this Cisco Desire in Life Psycho.
From this video, we will begin to introduce identifying the existing network reassessment question
which to design methodology staffs to relate to, at least in part
to the implementation phase over the p p t i o process. Choose two from the following a verifying the never the determining customer department see establishing the organization. No requirements The testing design
e characterizing the existing network have collected customer refinement
The high level design a low level design from those options here.
Um, anything related requirements will be out of a scope.
we'll be out of a scope, right? So let's look at a and the d verifying the network and a task in this I will tell you they are all related to the implementation face
Sofer. Hey, Level and the lower level design there Also something related. That desire is now Larry implementation face. So
that confirmed that a nd that cracked the answer.
So in this video, we talked, but I didn't find the exact existing network will give up revolver. Be about the design and methodology on the stand, stabs and identifying customer requirements. Includes. Identify current and planned applications.
Determine the importance of each application.
Gather plan Infrastructure service These organizational goes so on so forth. Okay, I started
desire methodology. There are three steps. Threats. Step one. Decision makers identify requirements and, uh,
conceptual architectural have proposed this steps This step ultra sing this strategy and announces process over the PBM plan. Face stab to the network is assessed on Get Up announces a performance to determine the infrastructure necessary
all the requirements. The network is a sized on function performance and the quality this Stab all cars in the assassin in the process of the PBM plan face
on day and Step three. The network with apologies design to meet a requirement. Close the never gaps identified in the previous steps right, a detailed designed to all communities have prepared doing the space design solutions include a network infrastructure voice over i p void,
on intelligent that research sees right this set hawkers in the design process of the ppm desire face.
Then we move out two steps in identifying customer requirements. There are, in total five steps, right step one. Identify current and plan implications on that determine the importance of each application. For example, is email as important as a customer support
is actually travel being deployed?
High availability and a hype in with implications need to be identified for the decision to accommodate their memory requirements. Right,
this all happened in these. I'll tap one on Dad. Step two. I'll get additional ghosts, right? So identify whether the companies go is to improve the customer support on at a new customer. Surveys increased competitive in this or reduce costs. Right
Step three off organizational costumes,
budgets, personnel policy and a schedule is all talk about you know the limitations. Right step for technical goes support to the organization's objectives and of the support of the implications includes improving the network's response times through boot
decreases never feelers on downtime. High availability, right?
A. Simply find network management in proving that our security improve. Ah, reliability of a mission. Critical applications modernize outdated technologies, technology refresh, for example, right. A improve the never to scale ability.
This is all happening in step four, right? This is all I get. Ah, Technical ghost
A Step five Never design Mad Beacon Constant by parameters that let me do this. Lucious, for example, Right Existing wiring does not support new technology being with men. All support new applications. The network and I asked the support Existing legacy equipment
Legacy implications must be supported.
Application compatibility should write all those early technical constants after five stacks done. Although collected information needs to be documented properly. Right?
Which three atoms are part of the process? ***. A vast siskel, for one Does nice choose free, you know, cure desires Cute. You might write a characterized an existing network B I analyze customer requirements. See configure deployed. A service is
Want apology E open cases with Cisco that structure down going Never performance. See show F customer survey about a critical application performance. Okay, that started. Explain one by one Her eyes the existing network A parent is right
to characterize the existing network
full of desire Be I always customer requiring this apparently is right Because we need to do the analyzation after the Carmen being collected, right? See configure No, we don't need a computer configure and not a part of that desire, right?
The design. A new 1 12 year off course e and 1/2
opened attack case. Non related costume serving. No, now related. So obviously answer our A B in the deep, right? Hopefully you get this right. Let's move on to another question.
Question number two What three customers supported. Details. Identifies memory requirements based on a ppd io design emoto to three. A ghost be bucket. See User needs the location. E policies have tasks,
GMR, mental requirements.
I hate politics. Gave the three answers right there. A BNC right goes budgets, user name. But talking about it goes We're talking about a cost Reince budget. One of them we're talking about A user needs part of the design model, right? So a B and C u of u the cracker.
Hopefully you get this right,
OK, in today's brief luxury disgust, design methodology, stabs and identifying customer requirements.
Any questions? Send the email.
I'll see you in the next video. Bye bye. Fiona