Chapter 1 – Analyzing Business Goals and Constraints.docx

5 Pages
Unlock Document

Ryerson University
Information Technology Management
ITM 600
Robert Hudyma

Chapter 1Analyzing Business Goals and ConstraintsUsing a TopDown Network Design MethodologyA network created with this complexity often doesnt perform as well as excepted doesnt scale as the need for growth arises and doesnt match a customers requirementsoHard to make upgrades patch updates modifications to a networkoSolution use a streamlined systematic methodology in which the network or upgrade is designed in a topdown fashionRequirementsoAvailability Scalability Affordability Security and ManageabilityDesign tools and methodologies in use the connect the dots network design methodologyoCan be used when customers expect a quick response and the requirements are well knownGood network design must recognize that a customers requirements embody many business and technical goals Including requirements for availability scalability affordability security and manageabilityService Level customers want to specify a required level of network performanceTop down network design is a methodology for designer networks that begins at the upper layers of the OSI reference model before moving to the lower layersoIt focuses on applications sessions and data transportoIs it also iterativeoIncludes exploring organizational and group structures to find the people for whom the network will provide services and from whom the designer should get valuable information to make the design succeedUnexpected scalability and performance problems appear as the number of network users increasesUsing a Structured Network Design ProcessStructured systems analysis has the following characteristicsoThe system is designed in a topdown sequenceoDetermine new user requirements and propose a structure for the future systemoA focus is placed on data flow data types and processes that access or change the dataoA focus is placed on understanding the location and needs of user communities that access or change data and processesoThe logical model represents the basic building blocks divided by function and the structure of the systemoThe physical model represents devices and specific technologies and implementationsoSpecifications are derived from the requirements gathering at the beginning of the topdown sequenceoLarge network design projects should be split functionally to make the project more manageable oSAFESecure Architecture for EnterprisesoECNMEnterprise Composite Network ModeloSystems development lifecycles from a systems analysis contextWant to develop a system that exists runs well but evolves through upgrades and changes over the course of its lifetimeSystem Development Life CyclesMany system analysis books use the acronym SDLC to refer to the systems life cycle which might sound stage to older networking students who know SDLC as Synchronous
More Less

Related notes for ITM 600

Log In


Don't have an account?

Join OneClass

Access over 10 million pages of study
documents for 1.3 million courses.

Sign up

Join to view


By registering, I agree to the Terms and Privacy Policies
Already have an account?
Just a few more details

So we can recommend you notes for your school.

Reset Password

Please enter below the email address you registered with and we will send you a link to reset your password.

Add your courses

Get notes from the top students in your class.