.NET vs. J2EE Architecture

Slides:



Advertisements
Similar presentations
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
Advertisements

8.
IS6112 Application Modelling and Design Introduction.
ECEN5053 SW Eng of Dist Systems, Arch Des Part 2, Univ of Colorado, Boulder1 Architectural Design of Distributed Systems, Part 2 ECEN5053 SW.
Satzinger, Jackson, and Burd Object-Orieneted Analysis & Design
CS 432 Object-Oriented Analysis and Design
The Architecture of Transaction Processing Systems
J2EE vs..NET Tom Tong. Enterprise Application 1 distributed 2 multiple-platform 3 critical 4 performance 5 security 6 multiple-data sources.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 12 Slide 1 Distributed Systems Design 1.
Client/Server Architectures
February Semantion Privately owned, founded in 2000 First commercial implementation of OASIS ebXML Registry and Repository.
© Drexel University Software Engineering Research Group (SERG) 1 Based on the paper by Philippe Kruchten from Rational Software.
LAYING OUT THE FOUNDATIONS. OUTLINE Analyze the project from a technical point of view Analyze and choose the architecture for your application Decide.
What is Architecture  Architecture is a subjective thing, a shared understanding of a system’s design by the expert developers on a project  In the.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 13Slide 1 Architectural Design u Establishing the overall structure of a software system.
An Introduction to Software Architecture
Enterprise JavaBeans. What is EJB? l An EJB is a specialized, non-visual JavaBean that runs on a server. l EJB technology supports application development.
© 2006 IBM Corporation IBM WebSphere Portlet Factory Architecture.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Architectural Design l Establishing the overall structure of a software system.
1 Another group of Patterns Architectural Patterns.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
XML Registries Source: Java TM API for XML Registries Specification.
Information System Development Courses Figure: ISD Course Structure.
Architectural Design lecture 10. Topics covered Architectural design decisions System organisation Control styles Reference architectures.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Architectural Patterns Support Lecture. Software Architecture l Architecture is OVERLOADED System architecture Application architecture l Architecture.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
NA-MIC National Alliance for Medical Image Computing UCSD: Engineering Core 2 Portal and Grid Infrastructure.
Enterprise Java Beans. Model 1 J2EE – Web View Model/View/Controller Model View Control Data base Web Server Model One Architecture HTTP Request HTTP.
CSC480 Software Engineering Lecture 10 September 25, 2002.
Information Technology Division Executive Office for Administration and Finance Service Oriented Architecture An Enterprise Approach to Enabling the Business.
Java EE Patterns Dan Bugariu.  What is Java EE ?  What is a Pattern ?
DESIGN OF SOFTWARE ARCHITECTURE
© FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 JSP Application Models.
SEA Side – Extreme Programming 1 SEA Side Software Engineering Annotations Architectural Patterns Professor Sara Stoecklin Director of Software Engineering-
Lecture VIII: Software Architecture
CSC 480 Software Engineering Lecture 17 Nov 4, 2002.
J2EE Platform Overview (Application Architecture)
Method – Notation 8 Hours.
PLM, Document and Workflow Management
N-Tier Architecture.
Chapter 2 Database System Concepts and Architecture
OO Methodology OO Architecture.
Distribution and components
Part 3 Design What does design mean in different fields?
Enterprise Computing Collaboration System Example
POOL persistency framework for LHC
CSC 480 Software Engineering
EIN 6133 Enterprise Engineering
Introduction to J2EE Architecture
#01 Client/Server Computing
Graduation Project Kick-off presentation - SET
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
VSA Integration with Apache
Service-centric Software Engineering
Leigh Grundhoefer Indiana University
Ada – 1983 History’s largest design effort
Lecture 1: Multi-tier Architecture Overview
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Evaluating Compuware OptimalJ as an MDA tool
Software Architecture
An Introduction to Software Architecture
What is Software? Software is: (1) instructions (computer programs) that when executed provide desired features, function, and performance; (2) data structures.
Developing and testing enterprise Java applications
Design Yaodong Bi.
Overview Activities from additional UP disciplines are needed to bring a system into being Implementation Testing Deployment Configuration and change management.
Design.
Software Development Process Using UML Recap
#01 Client/Server Computing
Presentation transcript:

.NET vs. J2EE Architecture .NET and J2EE both provide distributed and concurrent solutions Sacramento Java User Group Chris Scheuble

Technology Stacks

.NET Architecture

J2EE Architecture

WebSphere Deployment

Enterprise Layers Database Persistence Business Presentation

Migration Efforts Domain Identities Data Inputs & Outputs A datum is an element of information that is transferred from an connector, or received by a service, via a connector. Services A service is an abstract unit of software instructions and internal state that provides a transformation of data via its connector. Interfaces An connector is an abstract mechanism that mediates communication, coordination, or cooperation among services. Technical Dependencies A dependency is a immutable condition that mandates cohesion to external hardware or software or embedding in an environment or other domain.

Migration Efforts Domain Identities Technical dependencies are further split into divided domains unless the effort to split the domain dependency out weighs the cost to maintain the dependency.

Migration Efforts Distributed System Interfaces Split the code base into multiple executables Decouple the message data Relax the binding between development teams Publish “client code” executables

Migration Efforts Unified Version Control Formalize the code base into code sets based upon the identified domains Automate all code set build and deploy procedures Includes database schemas Includes run-time, work station, server and client environments

Migration Efforts Synthesize the business Architect a business model not the features Abstract out data dependencies not switch statements Abstract out hierarchical dependencies not crusty concrete inheritances Design the framework not the details of how it is implemented Design unanimously not a methodology campaign

Migration Efforts Teamwork and Focus Team meetings Unified effort Encyclopedia Note book wiki Personal growth Sharing of objective findings Win as a team

Functional Architecture ORM Connectors Workflow Engines Legacy Middleware Systems Data Publishing & Caching Engines Business Rules Engines Session State Engines EDI / HTML Handlers Internal Support Tools

.NET vs. J2EE Architecture Questions… Sacramento Java User Group Chris Scheuble