The Difference Between Logical and Physical Network Design
Logical Design
Logical design takes each piece of conceptual design and assigns it to a specific logical role within architecture. For infrastructure projects, the architecture might be a series of block diagrams showing networks, service components, and network connection elements. Application architecture is typically broken down into at least three levels: presentation, business, and data level.
Because this is a migration project, the team should document the existing logical design as well as the logical design of the migrated application or infrastructure component, emphasizing the areas of change. It may be necessary to show how other components outside the scope of the project interact with the subject of the migration.
The Logical Design would be the IP structure of your network. Will you be using a Class A, B or C address scheme? Will you be subnetting your environment? You will need to figure out how many computers you need and what locations they will be in. Then you can design your IP structure based upon the needs of your design. If it is a simple design such as 10 users you can keep it simple.
Physical Design
The physical design of the solution specifies which logical pieces fit into specific physical pieces of architecture. The physical design should include anticipated metrics to assess the performance goals, uptime goals, and milestones of the solution code to be written. For example, the physical design might include metrics for transaction speed performance requirements prior to deployment. Production metrics for the particular deployment scenarios must also be established.
Migration deployment scenarios must do more than describe how the fully migrated technology will exist after the migration is complete. They must also cover how the existing application or infrastructure implementation will be supplanted by the new implementation without violating ongoing service level agreements (SLAs). In other words, the deployment scenarios must
Logical design takes each piece of conceptual design and assigns it to a specific logical role within architecture. For infrastructure projects, the architecture might be a series of block diagrams showing networks, service components, and network connection elements. Application architecture is typically broken down into at least three levels: presentation, business, and data level.
Because this is a migration project, the team should document the existing logical design as well as the logical design of the migrated application or infrastructure component, emphasizing the areas of change. It may be necessary to show how other components outside the scope of the project interact with the subject of the migration.
The Logical Design would be the IP structure of your network. Will you be using a Class A, B or C address scheme? Will you be subnetting your environment? You will need to figure out how many computers you need and what locations they will be in. Then you can design your IP structure based upon the needs of your design. If it is a simple design such as 10 users you can keep it simple.
Physical Design
The physical design of the solution specifies which logical pieces fit into specific physical pieces of architecture. The physical design should include anticipated metrics to assess the performance goals, uptime goals, and milestones of the solution code to be written. For example, the physical design might include metrics for transaction speed performance requirements prior to deployment. Production metrics for the particular deployment scenarios must also be established.
Migration deployment scenarios must do more than describe how the fully migrated technology will exist after the migration is complete. They must also cover how the existing application or infrastructure implementation will be supplanted by the new implementation without violating ongoing service level agreements (SLAs). In other words, the deployment scenarios must