A new range of technologies has expanded the options for enterprise system architects. These technologies have been developed in response to demands to allow wider usage of systems and more varied interaction with them.

Support for UDDI and B2Bi requires flexible systems with interfaces suitable for both enterprise and consumer use in a diverse range of applications. To cope with these demands, many legacy multi-tier frameworks need to be either augmented or replaced.

The tools and techniques emerging to provide for this variety of interaction includes standards and products such as UDDI, CORBA, MTS (Microsoft Transaction Servers) and J2EE among others. These technologies provide a range of services including support for transactions, security, interoperability and persistence. They are often combined and selecting which to use requires consideration of the skills available, the state of existing legacy systems and requirements for portability, security and flexibility.

Students completing this unit will have an understanding of these technologies from the perspective of a Systems Architect. This task covers high-level aspects of enterprise system development, including project management, system design, development methodologies and tools as well as fundamental problems and technical issues underlying n-tier transaction and Web-based systems.

Students will gain these skills through the staged development of a small enterprise system. This development -- combined with written reviews justifying and evaluating their solution -- provides a solid grounding for both practical concepts and theory in addition to the technical skills acquired.

1. Understand the technical issues underlying distributed enterprise computing
   • Concurrency and transactions
   • Interoperability
   • Scalability
   • Manageability
2. Understand the role of a System Architect in developing these systems
   • Manage system workload and capacity
   • Understand and model required business processes
   • Manage the development and testing of systems

3. Have practical skills in technologies used to develop enterprise systems.
   • Ability to model web-based systems (using UML)
   • Ability to create web applications (servlets, JSP's)
   • Ability to write and deploy EJB applications

This unit looks at the Open Source technologies available for enterprise computing. These technologies include implementations of Sun's J2EE specification (such as JBoss), implementations of Sun's JSP and servlet specifications (such as Tomcat), integration options (such as CORBA) and API's available for the development of XML based web-services. Students will gain practical experience with the issues and technologies related to the development of large scale enterprise systems including: Transactions and distributed transaction processing, interoperability and persistence, scalability and the choices facing enterprise system architects and developers. Students gain experience with Sun's Enterprise Java beans, JSP, commonly used development tools and deployment software as well as learning appropriate design patterns for the creation of maintainable and reliable enterprise systems.

• Douglas, B.P. Real-time UML, 1988. Addison-Wesley. ISBN:0-201-65784-8
• Monson-Haefel, R. Enterprise JavaBeans, 3rd Edition, 2001. O'Reilly. ISBN:0-596-00226-2
• Turner, J. and Bedell, K. STRUTS: Kick Start, 2003, Sams. ISBN: 0-67232-472-5

• Software Title:
• Vendor:
• Version:
• OS: MS Windows XP ( ) and/or LINUX ( )
• License Details: (A valid software license certificate/s or Vendor permission must be available upon request if the software is to be installed for teaching)
• Are we currently licensed: Yes ( ) or No ( ) (If unsure, please check with your local IT support )
• If (Yes), who is the contact person for this software?:
• If (No), will the software license be arranged by: Staff member requesting the software ( ) or Technical Services* ( ) ? *If the latter is selected, please discuss your requirement/s with myself ASAP, prior to finalising your request, as there could be financial or resourcing implications.
• Is the software to be installed and accessed from a: Client/Workstation ( ), or Server ( ) ?
• Type of license: Site License ( ), Freeware ( ), FOSS (Free and Open Source Software) ( ), Shareware ( ), Lab based ( ) # of Licenses needed ____
• In what week will you commence using the software in class? Semester 1 (Week ___ ) and/or Semester 2 (Week ___ ):
• Nominated Staff For Acceptance Testing Software: (Name) (Phone) (Email)
• Additional Information: Special Requirements, Software Configuration/Installation Requirements, etc:

Vendor: Sun Microsystems (java.sun.com) Software Title*: J2EE (SDK) Version*: 1.3.1 OS*: Windows First Semester Week Required : Week 1 License Details*: Freeware Nominated Staff for software testing

Vendor: JBoss (www.jboss.org) Software Title*: JBoss Application Server Version*: 3.2.3 OS*: Windows First Semester Week Required : Week 1 License Details*: Freeware Nominated Staff for software testing

Vendor: Eclipse (eclipse.planetmirror.com) Software Title*: Eclipse Version*: 2.1.3 OS*: Windows First Semester Week Required : Week 1 License Details*: Freeware Nominated Staff for software testing

Vendor: Sourceforge.net (j2eeunit.sourceforge.net) Software Title*: J2EEUnit Version*: latest OS*: Windows First Semester Week Required : Week 1 License Details*: Freeware Nominated Staff for software testing

Vendor: Apache (ant.apache.org) Software Title*: Ant Version*: 1.3 OS*: Windows First Semester Week Required : Week 1 License Details*: Freeware Nominated Staff for software testing

CSE3420 (SFT3200)