Chapter 7 Problem & Cases

Slides:



Advertisements
Similar presentations
The Web Wizards Guide to Freeware/Shareware Chapter Six Open Source Software.
Advertisements

Chapter 10: Designing Databases
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
WebSphere Diego Leone. Summary Story and birth What is WebSphere?/Goals Main features Advantages/Disadvantages Conclusions.
Overview Define structural components and dynamic interactions
2 Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the differences between requirements activities and design activities.
Chapter 13 Physical Architecture Layer Design
Introduction to z/OS Basics © 2006 IBM Corporation Chapter 8: Designing and developing applications for z/OS.
Lecture 4: Introduction to PHP 3 PHP & MySQL
12 Chapter 12 Client/Server Systems Hachim Haddouti.
Chapter 9: The Client/Server Database Environment
J2EE Java 2 Enterprise Edition. Relevant Topics in The Java Tutorial Topic Web Page JDBC orial/jdbc
Chapter 9: Moving to Design
8 Systems Analysis and Design in a Changing World, Fifth Edition.
Objectives Explain the key role of a systems analyst in business
Chapter 4 - Software – Part 2 Dr. V.T. Raja Oregon State University.
PaperCut NG Chris Dance. Copyright © PaperCut Software Pty. Ltd. 2 Overview Overview of PaperCut NG Why we offer a Mac Version The story of our.
Lecture The Client/Server Database Environment
Web Service Implementation Maitreya, Kishore, Jeff.
The Client/Server Database Environment
Java Pet Store Application. Outline Introduction Introduction Information Layer Information Layer Application Layer Application Layer Infrastructure Layer.
Web-based Software Development - An introduction.
TOPIC 1 – SERVER SIDE APPLICATIONS IFS 234 – SERVER SIDE APPLICATION DEVELOPMENT.
INFO 355Week #61 Systems Analysis II Essentials of design INFO 355 Glenn Booker.
Hands-On Microsoft Windows Server 2008 Chapter 1 Introduction to Windows Server 2008.
BASIC NETWORK CONCEPTS (PART 6). Network Operating Systems NNow that you have a general idea of the network topologies, cable types, and network architectures,
Systems Design. Systems Design Skills People skill (25%) - Listening, understanding others, understanding between two lines, conflict resolution, handling.
6/1/2001 Supplementing Aleph Reports Using The Crystal Reports Web Component Server Presented by Bob Gerrity Head.
2 Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the differences between requirements activities and design activities.
Moving From Business Modeling Requirements to Design
CPTE 209 Software Engineering Summary and Review.
INFO425: Systems Design INFORMATION X Finalizing Scope (functions/level of automation)  Finalizing scope in terms of functions and level of.
Quality Assurance for Component- Based Software Development Cai Xia (Mphil Term1) Supervisor: Prof. Michael R. Lyu 5 May, 2000.
INFO415 An overview of systems development
Remote OMNeT++ v2.0 Introduction What is Remote OMNeT++? Remote environment for OMNeT++ Remote simulation execution Remote data storage.
Networked Application Architecture Design. Application Building Blocks Application Software Data Infrastructure Software Local Area Network Server Desktop.
CIS 375—Web App Dev II Microsoft’s.NET. 2 Introduction to.NET Steve Ballmer (January 2000): Steve Ballmer "Delivering an Internet-based platform of Next.
Introduction To Computer System
1 Documentum 6 Reviews from Early Adopters Technology Services Group, Inc. October 10, 2007.
DWA Example Scenarios This presentation shows a number of the most common scenarios used with the Distributed Websydian Architecture. Note that there are.
Presentation 8: SOAP in a distributed object framework, Application Servers & AXIS SOAP.
Choosing NOS can be a complex and a difficult decision. Every popular NOS has its strengths and weaknesses. NOS may cost thousands of dollars depending.
Computer Emergency Notification System (CENS)
1 Introduction to Middleware. 2 Outline What is middleware? Purpose and origin Why use it? What Middleware does? Technical details Middleware services.
Middleware for FIs Apeego House 4B, Tardeo Rd. Mumbai Tel: Fax:
1 Welcome to CSC 301 Web Programming Charles Frank.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
9 Systems Analysis and Design in a Changing World, Fourth Edition.
Technology Layer. Technology Layer Metamodel Technology Layer Concepts.
6/1/2001 Supplementing Aleph Reports Using The Crystal Reports Web Component Server Presented by Bob Gerrity Head.
An Introduction to Software Engineering (Chapter 1 from the textbook)
Introduction to the new mainframe © Copyright IBM Corp., All rights reserved. Chapter 11 Understanding transaction managers on z/OS.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
ViaSQL Technical Overview. Viaserv, Inc. 2 ViaSQL Support for S/390 n Originally a VSE product n OS/390 version released in 1999 n Identical features.
NJIT 1 Apache Tomcat (Version 6.0) THETOPPERSWAY.COM.
 Understand the concept and scope of IT Infrastructure  Understand with various components and technologies that make up IT Infrastructure  Learn the.
SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright © 1997.
Glink for Java: applet, application and an API for integrating access to Bull, IBM, UNIX and Minitel systems with your Java based e-business applications.
Week 1. Introduction Types of Software Information Systems Information Systems Technologies and Methodologies.
OPERATING SYSTEMS (OS) By the end of this lesson you will be able to explain: 1. What an OS is 2. The relationship between the OS & application programs.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
Systems Analysis and Design in a Changing World, Fifth Edition
Web-based Software Development - An introduction
Systems Analysis – ITEC 3155 Evaluating Alternatives for Requirements, Environment, and Implementation.
Multitier Architecture, MySQL & PHP
ApplinX Rod Carlson Senior Technical Lead.
COMPONENTS – WHY? Object-oriented source-level re-use of code requires same source code language. Object-oriented source-level re-use may require understanding.
UFCEUS-20-2 Web Programming
Presentation transcript:

Chapter 7 Problem & Cases TC 3 Rethinking Rocky Mountain #1, 2

TC 3 Assume that the deployment environment for a high-volume payment processing system consists of the following: DB2 DBMS running under the OS/390 operating system on an IBM S/390 mainframe WebSphere application server running under the Z/OS operating system on an IBM zSeries 900 mainframe CORBA-compliant component-based application software written in Java that will be executed by other internal and external systems What are the key architectural design decisions that must be made for the system? When should the decisions be made and who should make them? Outline the subsequent design tasks that should occur after the key architectural design decisions are made. To what extent can the subsequent steps be performed in parallel?

TC 3 Answer Some key architectural decisions to explore include: the key components and subsystems, where each component will execute and how will all of the pieces interoperate (which requires nailing down how the network, CORBA, and database infrastructure will be configured)? Many of the decisions depend on whether the supporting infrastructure is already in place. If it is, then many of the architectural decisions can be delayed until much code has been written and tested. If not, then the required infrastructure and tools will have to be acquired and configured. Developers will have to be trained, and architectural design will need to occur early to ensure that the developers don’t make any “mistakes” due to lack of fit with the development or deployment environment. Note that an OO development approach is assumed given the nature of the infrastructure and tools

Rocky Mountain Outfitters 1 Various application deployment environments can meet the requirements of RMO’s strategic plan. The staff’s current thinking is to move more toward a Microsoft solution using the latest version of Microsoft Server with Microsoft’s IIS as the Web server. However, Linux with Apache servers is a competing approach. Considering that RMO could also take that approach, do the following: [drawn from SADCW Ch.8] 1. Compare the relative market penetration of Microsoft and Apache/Linux (a good starting place is http://www.netcraft.com)

Rocky Mountain Outfitters 1

Rocky Mountain Outfitters 2 Modify the network diagram in Figure 7-13 to describe a viable architecture using Apache/Linux. What changes, if any, are required for the client workstations and customer PCs? What changes, if any, are required in middleware and communication protocols? Will there be any change in the estimates of required data-communication capacity among client workstations and servers located at the Park City data center? Why or why not? Using UNIX opens the possibility of deploying Java on the clients, which would increase the communication capacity requirements if applets were transmitted to and executed on clients Since Microsoft no longer includes “standard” support for Java in Windows or IE, deployment would be complex since presumably some remote clients and customers would be running Windows. They’d have to install a JVM and probably another browser (e.g., Netscape) or a custom application that mimicked a browser.