Applying Methodology to a Design Part 3 — Transcript

Full transcript

1. 0:04identifying customer requirements
2. 0:07this is segment three of applying
3. 0:09methodology
4. 0:10to a design
5. 0:15identifying customer requirements
6. 0:18so this includes assessing the scope
7. 0:22of network design project identifying
8. 0:25required information
9. 0:27extracting initial requirements
10. 0:30gathering network requirements planned
11. 0:34application and network services
12. 0:37organizational goals organizational
13. 0:40constraints
14. 0:42technical goals and technical
15. 0:45constraints
16. 0:48when assessing the scope of a network
17. 0:50design you need to consider the
18. 0:52following
19. 0:53so whether the design is for a new
20. 0:55network
21. 0:56or is a modification of the existing
22. 0:58network
23. 1:00so usually design nowadays are usually
24. 1:03an upgrade
25. 1:04okay so very seldom that we start a
26. 1:07network design or network implementation
27. 1:09from the scratch
28. 1:11so whether the design is for the entire
29. 1:13enterprise network
30. 1:15a subset of the network or a single
31. 1:18segment
32. 1:19or module for example the designer must
33. 1:22ascertain
34. 1:23whether the design is for a set of
35. 1:25campus lens
36. 1:27a one or a remote access network
37. 1:30so whether the design addresses a single
38. 1:32function
39. 1:34or the network's entire functionality
40. 1:38examples of design that would involve
41. 1:40the entire network include
42. 1:42one of which all branch offices
43. 1:45lands are upgraded to support
44. 1:48fast ethernet or giga ethernet and a
45. 1:51migration
46. 1:52from traditional private branch exchange
47. 1:55or pbx
48. 1:56based telephony to an ip telephony
49. 2:00solution
50. 2:01so basically a project
51. 2:05to reduce bottlenecks on a slow one is
52. 2:08an example that would likely affect
53. 2:10only wide area network so
54. 2:14adding wireless mobility okay
55. 2:17or provisioning core redundancy are
56. 2:20designs that would likely affect
57. 2:22only the campus so the open system
58. 2:26interconnect or the osi reference model
59. 2:28is important during the design phase the
60. 2:31network designer
61. 2:33should review the project scope from the
62. 2:36protocol layer perspective
63. 2:38and decide whether the design is needed
64. 2:41for only the network layer or if other
65. 2:44layers are also involved
66. 2:47so for example the network layer
67. 2:49includes
68. 2:50the routing and addressing design the
69. 2:53application layer
70. 2:55includes the design of application data
71. 2:57transport such as
72. 2:59transporting voice the physical and data
73. 3:02link layers
74. 3:04include decisions about the connection
75. 3:06types
76. 3:07and the technologies to be used such as
77. 3:10gigabit
78. 3:10ethernet and other technologies
79. 3:16so the table here exhibits a sample
80. 3:19results
81. 3:20of assessing the scope of design
82. 3:23for a sample enterprise say corporation
83. 3:25x
84. 3:27okay so this includes the scope of
85. 3:30design
86. 3:31the entire network okay the network
87. 3:34layer
88. 3:35or focused on the data link layer only
89. 3:41identifying required information so
90. 3:44determining requirements includes
91. 3:46extracting initial requirements
92. 3:48from the customer and then refining this
93. 3:51with other data that has been collected
94. 3:54from the organization
95. 3:57so extracting initial requirements well
96. 4:00initial design requirements are
97. 4:01typically extracted from
98. 4:03rfp okay or the request for proposal
99. 4:07or request for information or rfi
100. 4:12okay so these are basically coming from
101. 4:15the customers
102. 4:17so an rfp is a formal request of vendors
103. 4:20for proposals that meet the requirements
104. 4:24that the document identifies
105. 4:27an rfid is typically a less formal
106. 4:30document an organization issues to
107. 4:32solicit ideas and information from
108. 4:34vendors about the specific product
109. 4:39so the first step in the design process
110. 4:42should be pre-documenting shifting
111. 4:45processing reordering translating and so
112. 4:48forth
113. 4:49okay so the design requirement and
114. 4:51reviewing them
115. 4:53with the customers for verification and
116. 4:56approval
117. 4:57obtaining the right customers input in
118. 5:00either
119. 5:00oral or written form that's very
120. 5:03important
121. 5:04now the figure here illustrates an
122. 5:06identity approach
123. 5:08to developing the design requirements
124. 5:09document
125. 5:11so the figure illustrates the following
126. 5:13steps here so first
127. 5:16extract the initial customer
128. 5:17requirements from rfp
129. 5:20or rfi okay and then
130. 5:24second query the customer for verbal
131. 5:27description
132. 5:29of the initial requirements and then
133. 5:32third
134. 5:33okay produce a draft document that
135. 5:36describes
136. 5:37the design requirements next would be
137. 5:40fourth verify the design requirements
138. 5:43with the customer
139. 5:44and obtain customer approval
140. 5:48and the last one would be if revise the
141. 5:51document
142. 5:52as necessary to eliminate errors and
143. 5:55omissions
144. 5:56so steps two to five are repeated if the
145. 5:59customers
146. 6:00has additional comments about the draft
147. 6:03document
148. 6:05identifying required information so this
149. 6:07time
150. 6:08gathering network requirements so as
151. 6:10illustrated in the figure
152. 6:12the process of gathering requirements
153. 6:14can be broken down into five steps
154. 6:17right so during these steps which are
155. 6:20sometimes called milestones
156. 6:22the designer discusses the project where
157. 6:24the customer staff
158. 6:26to determine and gather the necessary
159. 6:28data including appropriate documentation
160. 6:31so step one would be identify the
161. 6:34planned network applications and network
162. 6:36services
163. 6:38step two define the organizational goals
164. 6:43three okay so which is
165. 6:46determine the possible organizational
166. 6:48constraints
167. 6:51four determine technical goals
168. 6:54okay and then five determine the
169. 6:58technical constraints
170. 6:59that must be taken into account okay
171. 7:02now these steps provide the designer
172. 7:05with data that must be carefully
173. 7:07interpreted
174. 7:08analyzed and presented to support the
175. 7:11design proposal
176. 7:12so throughout these steps the designer
177. 7:15takes
178. 7:16thorough notes produces documentations
179. 7:18and presents
180. 7:19the findings to the customer for further
181. 7:22discussions
182. 7:27planned application and network services
183. 7:29so the designer must determine which
184. 7:31applications
185. 7:32the customer is planning to use and the
186. 7:35importance
187. 7:36of each of these applications so
188. 7:39using a table here helps organize and
189. 7:41categorize the applications and services
190. 7:44plan
191. 7:45so the table should contain the
192. 7:47following information
193. 7:49so you've got the planned application
194. 7:51types
195. 7:52okay so this includes email
196. 7:56okay groupware tools.8 group work
197. 8:00okay voice networking web browsing
198. 8:04video on demand or the vod databases
199. 8:08file sharing and transfer aided
200. 8:12manufacturing
201. 8:13if applicable okay customer support
202. 8:17and others so applications
203. 8:20specific applications that will be used
204. 8:23such as
205. 8:24microsoft explorer for instance or
206. 8:26microsoft edge
207. 8:28uh the cisco unified meeting place
208. 8:32okay zoom and others
209. 8:35so you also have level of importance
210. 8:39okay so the importance of the
211. 8:41applications
212. 8:42whether critical or important
213. 8:46or not important that should be noted
214. 8:49okay and the last column here
215. 8:53should be your comments additional notes
216. 8:54taken during the data gathering process
217. 9:00now the table here shows an example of
218. 9:02data gathered about the planned
219. 9:03applications
220. 9:04for the sample company and which is the
221. 9:07corporation x
222. 9:08okay so for email application would be
223. 9:11using the microsoft outlook
224. 9:13okay that's important for groupware
225. 9:17something like in this example you've
226. 9:19got the cisco unified
227. 9:21meeting place okay that's important
228. 9:24so some comments for web browsing
229. 9:27you've got the explorer opera netscape
230. 9:30and others
231. 9:31so video on demand databases and
232. 9:34customer support
233. 9:40the planned infrastructure services
234. 9:41table is similar to
235. 9:43the planned application table okay
236. 9:46so it lists infrastructure services that
237. 9:49are planned
238. 9:50for the network and additional comments
239. 9:52about those services
240. 9:55so recall that infrastructure services
241. 9:57includes
242. 9:58security okay quality of service
243. 10:02nm or the network management high
244. 10:05availability
245. 10:07ip telephony and mobility
246. 10:12so software distribution backup
247. 10:14directory services
248. 10:16host naming and other authentication and
249. 10:18authorization
250. 10:20are examples of other services
251. 10:23and solutions that are deployed to
252. 10:25support a typical organization's
253. 10:27many applications
254. 10:30so the table here shows the sample data
255. 10:33that was gathered
256. 10:34about the infrastructure services
257. 10:36planned for our sample
258. 10:39company corporation x so for security
259. 10:43deploys security systematically
260. 10:47okay so firewall technology to protect
261. 10:50internal network
262. 10:51virus scanning applications to check and
263. 10:52damage traffic for viruses
264. 10:55uh intrusion detection and prevention
265. 10:57systems
266. 10:59to protect from and inform about
267. 11:01possible outside intrusions
268. 11:04also on security consider the use of
269. 11:06authentication authorization and
270. 11:07accounting systems
271. 11:09to ensure that only authenticated and
272. 11:12authorized
273. 11:13users have access to specific
274. 11:16services okay so
275. 11:20next would be the quality of service or
276. 11:23the qos
277. 11:24so implementation of qos to prioritize
278. 11:27more important and more delay sensitive
279. 11:30traffic over less important traffic
280. 11:32so that means higher priority for voice
281. 11:35and database traffic while lower
282. 11:37priority for http traffic
283. 11:40okay next would be network management
284. 11:44introduction and installation of
285. 11:47centralized
286. 11:48network management tools such as the hp
287. 11:51openview okay with cisco works
288. 11:54applications for easier and more
289. 11:56efficient
290. 11:58network management you can also use
291. 12:00other network management tools available
292. 12:03okay now for high availability
293. 12:07use redundant path and terminate
294. 12:09connections on different network devices
295. 12:12to eliminate single points of failure so
296. 12:14we have a lot of
297. 12:15a lot of technology being used for high
298. 12:18availability
299. 12:19okay you just have to review your basic
300. 12:23networks
301. 12:24about this uh terms and technologies
302. 12:27being mentioned so next would be
303. 12:31ip telephony okay
304. 12:34the voice okay company wants to migrate
305. 12:38to ip telepony
306. 12:40okay and then for multicast ip multicast
307. 12:44introduction of ip multicast services
308. 12:47needed for the introduction to video
309. 12:49conferencing
310. 12:50and e-learning solutions okay should be
311. 12:53considered
312. 12:55so you also have mobility okay so need
313. 12:58mobility for employees and guest
314. 13:00access for clients so
315. 13:03all of this would be planned application
316. 13:05network services
317. 13:09next would be organizational goals
318. 13:13every design project should begin by
319. 13:15determining the organizational
320. 13:17goals that are to be achieved
321. 13:20okay so the criteria for success must be
322. 13:23determined
323. 13:25and the consequences of failure
324. 13:26understood so network designers
325. 13:30are often eager to start by analyzing
326. 13:32the technical goals
327. 13:34before considering the organizational
328. 13:36goals and constraints
329. 13:37so however detailed attention to
330. 13:40organizational goals and constraints
331. 13:42is important for a project success
332. 13:45so in discussions about organizational
333. 13:48goals
334. 13:49the designer obtains knowledge about the
335. 13:52customer's expectations
336. 13:54of the design positive outcomes for the
337. 13:57organization
338. 13:58so both short and long term should be
339. 14:02identified
340. 14:03okay now this organization-centered
341. 14:06approach
342. 14:07allows the network to become a strategic
343. 14:11asset and competitive weapon for the
344. 14:14customers
345. 14:15so preliminary research of the
346. 14:17organizational
347. 14:18activities products
348. 14:22processes services market suppliers
349. 14:25what else competitive advantages and
350. 14:29structure enhances the positioning of
351. 14:31the technologies and the products to be
352. 14:33used in the network
353. 14:36so this is an opportunity to determine
354. 14:39what is important to the customers
355. 14:42okay so some questions or sample
356. 14:45questions
357. 14:45a designer might ask to help determine
358. 14:48organizational goals includes the
359. 14:50following here so you could ask this to
360. 14:52your
361. 14:53clients okay so what are you trying to
362. 14:56accomplish over this project
363. 15:00what businesses or business challenges
364. 15:03are you currently facing what are the
365. 15:07consequences of not resolving these
366. 15:09issues
367. 15:10so how would you measure the quality or
368. 15:13the quantity success
369. 15:15if you could fix or correct the
370. 15:17identified problems
371. 15:19and issues what applications are most
372. 15:23critical to your organization
373. 15:26what is the major objective of the
374. 15:28project
375. 15:30what is driving the change do you need
376. 15:33to support
377. 15:34any government or safety or legal
378. 15:35mandates
379. 15:37what are your main concerns with
380. 15:39implementation of the new solution
381. 15:42what technologies or services are needed
382. 15:44to support your
383. 15:46objectives okay what other technology
384. 15:50projects and business initiatives will
385. 15:53affect
386. 15:54your group in the next two to
387. 15:57five years for instance okay
388. 16:00so what skill sets does your technical
389. 16:03staff currently have
390. 16:05and what is your goal for return on
391. 16:08investment or the roi
392. 16:11okay so organizational goals differ from
393. 16:15organization to organization okay so the
394. 16:18following are some typical goals that
395. 16:20commercial organization might have
396. 16:24so increase the operations generated
397. 16:26revenue
398. 16:27and profitability
399. 16:30so a design or a new design should
400. 16:32reduce
401. 16:33cost in certain segments and propel
402. 16:35growth in others
403. 16:37so the network designer should discuss
404. 16:40where the customer
405. 16:41and expectations about how the new
406. 16:44network will influence
407. 16:46revenues and profits
408. 16:49next would be short-term development
409. 16:51cycles and enhance productivity
410. 16:54by improving internal data availability
411. 16:57and
412. 16:58inter-departmental communications
413. 17:01you could also improve customer support
414. 17:05and offer additional services that can
415. 17:07expedite reaction to customer needs
416. 17:10and improve customer satisfaction
417. 17:15okay so opened organizations information
418. 17:18infrastructure to all key stakeholders
419. 17:21prospects investors customers
420. 17:26suppliers partners and employees and
421. 17:29build relationships
422. 17:31and information accessibility to a new
423. 17:33level
424. 17:34so take note that similar
425. 17:38though not identical goals are common to
426. 17:41governmental charitable religious and
427. 17:43educational organizations
428. 17:46most of these entities focus on
429. 17:49using available resources effectively to
430. 17:52attain
431. 17:53the organization's goals and objectives
432. 17:57so a not-for-profit organization or
433. 17:59those who are
434. 18:00non-profit okay organization
435. 18:03key measures are typically stated in
436. 18:05terms of
437. 18:06cost constraint or containment
438. 18:10okay service quality service expansion
439. 18:14and resource deployment so this section
440. 18:17emphasizes
441. 18:18the deployment of networks in commercial
442. 18:21organization
443. 18:22as an example of the type of research
444. 18:24required for establishing a network
445. 18:26requirements
446. 18:30so to illustrate the importance of
447. 18:32considering organizational goals in the
448. 18:33network design
449. 18:35so consider two manufacturing
450. 18:37enterprises that are contemplating
451. 18:39network updates
452. 18:41okay so for instance enterprise a
453. 18:44main reason for change is to improve
454. 18:46customer satisfaction
455. 18:48it has received many complaints that
456. 18:50customer information is difficult to
457. 18:52obtain and understand
458. 18:54and there is a need for online ordering
459. 18:56capability
460. 18:58okay now in contrast enterprise b
461. 19:01is given by the end of the system maybe
462. 19:05to reduce cost
463. 19:07okay so this is a mandate from
464. 19:11for instance the ceo so when design
465. 19:14decisions are made
466. 19:16these goals will most likely result in
467. 19:18different outcomes
468. 19:20so for example enterprise a might choose
469. 19:24to implement an integrated product
470. 19:25information database
471. 19:27with e-commerce capability
472. 19:30whereas enterprise b might not see the
473. 19:33value of investing in this technology
474. 19:38okay so following are examples
475. 19:41of the types of data that can be
476. 19:44gathered about some common
477. 19:45organizational goals
478. 19:47okay so this includes increased
479. 19:51competitiveness you have to list
480. 19:53competitive organizations and their
481. 19:55advantages and weaknesses
482. 19:57okay so note possible improvements
483. 20:00that might increase competitiveness or
484. 20:02effectiveness
485. 20:04reduce cost reducing operational costs
486. 20:08can result in increased profitability so
487. 20:10even without a revenue or increase
488. 20:13or increased services with the same
489. 20:15revenue
490. 20:16so list current expenses to help
491. 20:19determine
492. 20:20where cost would be reduced
493. 20:23okay next would be improve customer
494. 20:27support
495. 20:29customer support services help provide a
496. 20:32competitive advantage
497. 20:34so you have to list down current
498. 20:35customer support services
499. 20:38with comments about possible and desired
500. 20:41improvements okay and another thing
501. 20:45would be
502. 20:45add new customer services so you have to
503. 20:48list down
504. 20:49current customer services and not future
505. 20:52and desired or requested services
506. 20:54coming from the customers
507. 20:58now the table here presents data
508. 21:00gathered about organization goals of a
509. 21:02sample company corporate on x
510. 21:06okay so
511. 21:09you've got corporation y corporation z
512. 21:12this is the existing situation you've
513. 21:14got
514. 21:15some comments here right
515. 21:18so reduce cost improve customer support
516. 21:21and add your customer services
517. 21:24okay so document everything
518. 21:29organizational constraints so when
519. 21:32assessing organizational goals it is
520. 21:34important to analyze any organizational
521. 21:36constraints
522. 21:37that might affect the network design so
523. 21:40some
524. 21:42sample questions the designer might ask
525. 21:45to help determine organizational
526. 21:47constraints includes the following so
527. 21:49you could ask this
528. 21:50okay what in your current processes
529. 21:53works well
530. 21:56what is your current processes does not
531. 21:59work well
532. 22:00okay which processes are labor intensive
533. 22:05what are the barriers for implementation
534. 22:07in your organization
535. 22:10what are your major concerns with
536. 22:12implementation
537. 22:13of a new solution okay
538. 22:16so what financial and timing elements
539. 22:18must be considered
540. 22:20what projects already have budget
541. 22:22approval this is very important
542. 22:25okay are other plant technology projects
543. 22:28and business initiatives compatible with
544. 22:30your current
545. 22:30infrastructure and technology solutions
546. 22:34okay what qualifications does your
547. 22:37current staff have
548. 22:39do you plan to hire more staff if so
549. 22:42for what roles do you have budget for
550. 22:46technical development
551. 22:47for your staff and are there any
552. 22:51policies
553. 22:51in place that might affect the project
554. 22:55so you have to ask this on your clients
555. 22:59okay so
556. 23:02assessing organizational constraints so
557. 23:04typical constraints
558. 23:06includes the following so you've got the
559. 23:08budget
560. 23:10reduced budgets or limited resources
561. 23:13often force network designers to
562. 23:16implement an affordable solution
563. 23:18rather than the best technical solution
564. 23:20so take note of that
565. 23:21okay so this usually entails some
566. 23:24compromises in availability
567. 23:28manageability performance and
568. 23:31scalability
569. 23:33okay the budget must include all
570. 23:35equipment purchases
571. 23:37software licenses maintenance agreements
572. 23:41staff training and so on so budget is
573. 23:46often the final decision okay so to
574. 23:51make by the higher ups
575. 23:54okay so budget is often
576. 23:58for design elements selected equipments
577. 24:01and so on so the designer must know how
578. 24:04much
579. 24:04money is available to invest in a solid
580. 24:07design
581. 24:08so it's also useful to know the areas in
582. 24:12which the network can be compromised
583. 24:14to meet budget requirements so as always
584. 24:19budget is a challenge okay
585. 24:22next would be personnel the availability
586. 24:25of
587. 24:26trained personnel within the
588. 24:27organization might be
589. 24:29a design consideration organization
590. 24:32might not have enough trained personnel
591. 24:34or they might not have enough
592. 24:36personal familiarity with both the
593. 24:39equipment
594. 24:40okay and technology speeds deployments
595. 24:43and reduced cost
596. 24:45and trained technicians must be
597. 24:47available to verify
598. 24:49that all network elements are working
599. 24:52so therefore the designer must know the
600. 24:55number of availability of operation
601. 24:57personnel
602. 24:58their expertise and possible training
603. 25:02requirements
604. 25:03okay additional constraints might be
605. 25:06imposed
606. 25:06if the organization is outsourcing
607. 25:09network management
608. 25:10the designer must consider the following
609. 25:12implementation and maintenance
610. 25:14basis which require adequately
611. 25:18trained staff okay you also have to
612. 25:22consider policy
613. 25:24organizations have different policies
614. 25:26about protocols standards vendors and
615. 25:28applications
616. 25:29so to design the network successfully
617. 25:33the designer must understand this
618. 25:35policies
619. 25:36so research is very important data
620. 25:39gathering is very important
621. 25:41so for example the designer should
622. 25:44determine
623. 25:45customer policies related to single
624. 25:47vendor or multi-vendor platforms
625. 25:50an end-to-end single vendor solution
626. 25:53might be a benefit
627. 25:54because compatibility issues do not
628. 25:57restrain
629. 25:58the network so that is a challenge for
630. 26:01the designer okay so as another example
631. 26:05many organizations such as the
632. 26:06government agencies for example
633. 26:08defense departments have strict policies
634. 26:12preventing implementation of proprietary
635. 26:14protocols so take note of that
636. 26:16so as always being a designer i always
637. 26:19emphasize on
638. 26:20using open systems open protocols
639. 26:24okay the good thing about proprietary
640. 26:26protocols is that
641. 26:27these protocols are customized for the
642. 26:31uh for the device for example eigrp is
643. 26:34customized for cisco
644. 26:36okay but ospf is also working fine with
645. 26:38it
646. 26:40all right so those considerations should
647. 26:43be part of
648. 26:44the planning okay next would be
649. 26:47scheduling
650. 26:49the organization's executive management
651. 26:52must discuss and approve the project
652. 26:55schedule to avoid
653. 26:56possible disagreements about deadlines
654. 26:59so for example
655. 27:01the introduction of new network
656. 27:02applications
657. 27:04often drives the network design
658. 27:07the implementation time your time frames
659. 27:11for new applications are often tightly
660. 27:13connected and therefore
661. 27:15influence the available time for the
662. 27:17network design
663. 27:19a lot of considerations needs to be
664. 27:22assessed
665. 27:23needs to be considered
666. 27:28now table here shows an organizational
667. 27:31constraints and accompanying data that
668. 27:33has been collected for
669. 27:34our sample company corporation x here
670. 27:38so the budget okay and the personnel
671. 27:41all with certifications policy
672. 27:45okay the policy should be standardized
673. 27:47protocol so no proprietary protocol to
674. 27:49be used
675. 27:50and of course the scheduling which is
676. 27:52very important in
677. 27:53project implementation
678. 27:58technical goals so the technical goals
679. 28:02of the project must also be determined
680. 28:04before the design starts some sample
681. 28:08questions the designer might
682. 28:09ask to help determine technical goals
683. 28:12includes the following
684. 28:14so what are your technology priorities
685. 28:18how does your technology budgeting
686. 28:20process work
687. 28:23what infrastructure issues exists
688. 28:26or will exist related to your
689. 28:28application rollout
690. 28:30what skill sets does your technical
691. 28:33staff
692. 28:33need to acquire okay
693. 28:36so does your current network have any
694. 28:39performance issues
695. 28:41which portions of your network are
696. 28:43considered mission-critical
697. 28:46or do you have or do you anticipate
698. 28:48significant growth
699. 28:50in the number of network users over the
700. 28:52next few years
701. 28:53so i always give emphasis on this
702. 28:56whenever you design a network
703. 28:58do not design it based on the current
704. 29:01requirement
705. 29:02based on the current criteria you always
706. 29:04have to consider
707. 29:06the future expansion so think five years
708. 29:09or even 10 years from now
709. 29:12okay and then how is your network
710. 29:14managed now
711. 29:18technical goals the following list
712. 29:21describes
713. 29:21common technical goals okay
714. 29:24so improve network performance
715. 29:28an increase in the number of users and
716. 29:31the introduction of new application
717. 29:33might degrade network performance
718. 29:35especially responsiveness
719. 29:38and throughput okay the first goal
720. 29:42of network redesign is usually to
721. 29:44increase performance for example
722. 29:46by upgrading the speed of links
723. 29:49or by partitioning the network into
724. 29:52smaller segments
725. 29:52we call it network segmentation or vlans
726. 29:55all right
727. 29:57so take note performance
728. 30:00is a general term that includes
729. 30:03responsiveness
730. 30:05throughput and also resource utilization
731. 30:09the users of networked applications and
732. 30:11their managers are usually most
733. 30:12sensitive
734. 30:13to responsiveness issues speed
735. 30:17is of the essence so the network systems
736. 30:21managers often look
737. 30:24to throughput as a measure of
738. 30:26effectiveness
739. 30:27in meeting okay the organization's
740. 30:31needs so executives who have capital
741. 30:34budget responsibility tend to evaluate
742. 30:37resource utilization as a measure of
743. 30:40economic efficiency
744. 30:42so it is important to consider the
745. 30:43audience when presenting
746. 30:46performance information so you have to
747. 30:48speak their language
748. 30:50okay so next would be
749. 30:54improve security okay
750. 30:58reliability of mission-critical
751. 31:02applications and data so increased
752. 31:05threats
753. 31:05from both inside and outside the
754. 31:07enterprise network require the most
755. 31:09up-to-date security rules and
756. 31:12technologies to avoid
757. 31:13disruptions of the network operations
758. 31:16okay
759. 31:17next would be decrease expected
760. 31:20downtimes and related expenses
761. 31:23so when a network failure occurs
762. 31:26downtime must be minimal
763. 31:28and the network must respond quickly
764. 31:32to minimize related costs okay
765. 31:35so you also have to modernize outdated
766. 31:39technologies the emergence
767. 31:43of the new network technologies and
768. 31:44application demands
769. 31:46regular updates to and replacement of
770. 31:49outdated equipment and technologies
771. 31:52okay so the lifespan of the equipments
772. 31:55should
773. 31:55always be considered next would be
774. 31:59improve scalability okay
775. 32:03of the network so networks must be
776. 32:06designed
777. 32:07to provide for upgrades and future
778. 32:10growth
779. 32:12simplifying network management that's
780. 32:14also one
781. 32:15simplify network management functions so
782. 32:17that they are
783. 32:18easy to use and easily understood
784. 32:22so using a table helps the designer
785. 32:24identify technical goals
786. 32:26different goals of different levels of
787. 32:28importance
788. 32:29which the customer should determine
789. 32:33okay so one way of expressing the
790. 32:36importance
791. 32:37is with the percentages specific
792. 32:40technical goals
793. 32:41are rated in importance of scale from 1
794. 32:44to 100
795. 32:46so with the sum totaling 100 of course
796. 32:49this
797. 32:49scale provides direction for the
798. 32:53designer
799. 32:53when choosing equipment protocols
800. 32:57features and others
801. 33:01now the table here depicts the desired
802. 33:03technical goals
803. 33:05that were gathered for the sample
804. 33:07company corporation x
805. 33:09along with the importance ratings and
806. 33:11additional comments
807. 33:13so in this example the designer sees
808. 33:15that the customer places great
809. 33:17importance on
810. 33:19availability okay scalability
811. 33:24and performance okay so which is 20.
812. 33:28this suggests that the network design
813. 33:31should include
814. 33:31redundant equipment redundant paths
815. 33:35and use of high-speed links and software
816. 33:39okay so you could check other videos
817. 33:42related to this technical items like
818. 33:45availability the product goals high
819. 33:47availability and others
820. 33:52technical constraints network designers
821. 33:56might face various technical constraints
822. 33:59during the design process
823. 34:01so some sample questions the designer
824. 34:03might ask to help determine technical
825. 34:05constraints
826. 34:06includes the following here okay so
827. 34:09first
828. 34:10how do you determine your technology
829. 34:12priorities
830. 34:14do you have a technology refresh process
831. 34:17if so
832. 34:18is that an obstacle or does it support
833. 34:21the proposed project
834. 34:23what urgent technical problems require
835. 34:26immediate
836. 34:26resolution or mitigation
837. 34:30do you have a plan for technical
838. 34:31development for your staff
839. 34:34in specific areas or
840. 34:37do any applications require specific
841. 34:40network features
842. 34:42like protocols okay routing protocols
843. 34:47um acls and other security
844. 34:50okay now using the table can facilitate
845. 34:54the process
846. 34:55of gathering technical constraints so
847. 34:58the designer
848. 34:58identifies the technical constraints and
849. 35:00notes the current situation and the
850. 35:03necessary changes
851. 35:04that are required to mitigate a certain
852. 35:07constraint so here's the table
853. 35:09okay a good network design addresses
854. 35:12constraints
855. 35:13by identifying possible trade-offs such
856. 35:16as
857. 35:17the following you've got the existing
858. 35:20equipment
859. 35:22the network design process is usually
860. 35:24progressive
861. 35:25legacy equipment must coexist with the
862. 35:28new equipment
863. 35:30okay you also have bandwidth
864. 35:32availability
865. 35:34insufficient bandwidth in parts of the
866. 35:36network where the bandwidth cannot be
867. 35:38increased
868. 35:38because of the technical constraints
869. 35:40must be resolved
870. 35:42by other means okay you also have the
871. 35:45application compatibility
872. 35:47if the new network is not being
873. 35:49introduced at the same time as the new
874. 35:51applications
875. 35:52the design must provide compatibility
876. 35:55with all the applications
877. 35:58okay you also have lack of a qualified
878. 36:01personnel
879. 36:02lack of qualified personal suggests that
880. 36:05the designer
881. 36:06must consider the need for additional
882. 36:08training otherwise
883. 36:10certain features might have to be
884. 36:12dropped
885. 36:13for example if the network proposal
886. 36:16includes the use of ip telephony
887. 36:19but the network administrators are not
888. 36:21proficient in ip telephony
889. 36:23it might be necessary to propose an
890. 36:25iterative solution
891. 36:27okay now the table here presents example
892. 36:31technical constraints gathered
893. 36:32for our corporation x so under existing
894. 36:36equipment
895. 36:37okay the designer knows that the coaxial
896. 36:40cabling
897. 36:41in the land physical cabling plant still
898. 36:44exists
899. 36:44and comments that the twisted pair and
900. 36:47fiber optics should replace it
901. 36:49so there might be or there is a need for
902. 36:52an upgrade on the infrastructure
903. 36:55okay bandwidth availability indicates
904. 36:58that the one service provider does not
905. 37:00have any other available links aside
906. 37:03from 64 kbps one links
907. 37:06so the organization should consider
908. 37:07changing to another service provider
909. 37:09that being the case okay and then
910. 37:13application compatibility suggests that
911. 37:16the designer should take care
912. 37:18when choosing the equipment so this
913. 37:20should support
914. 37:21ipv6 based applications
915. 37:27so to summarize the ppd io approach
916. 37:31reflects the lifecycle phases of a
917. 37:33standard network
918. 37:35the design methodology under ppd io
919. 37:38includes
920. 37:39this processes so first identifying
921. 37:42customer requirements
922. 37:44okay so we cover this characterizing the
923. 37:47existing network and sites
924. 37:49and designing the network topology and
925. 37:51solutions
926. 37:52so take note that each of the pieces has
927. 37:55corresponding deliverables
928. 37:58so key steps in identifying customer
929. 38:00requirements includes
930. 38:01identifying network applications and
931. 38:03services
932. 38:04defining organizational goals and
933. 38:06constraints and
934. 38:08defining technical goals and constraints