90 likes | 220 Vues
Explore the journey of developing a mobile worker application under tight deadlines and challenging technical requirements. This case study illustrates how a team approached the task of creating a prototype in just 5 days, despite having no initial requirements and only one developer available. The application needed to operate under rough conditions, connect to existing architectures, and provide reliable communication over various networks. Discover the technology stack used, including J2EE, Eclipse RCP, and broadband wireless, and the lessons learned from this fast-paced project.
E N D
Mobilizing the Enterprise N. Lee Faus Enterprise Architect Railinc
Where We Began • Can you build me a wireless application? • Sure… • Can you do it in 3 months? • How many developers… • Where are the requirements… • One, not hired yet. Requirements don’t exist yet. We need a prototype in 5 days.
So We Gathered Requirements • Mobile Worker Application • Able to handle rough conditions • Connect to current application that was architected 3 years ago • Intermittent data connection • Go live date 12/31/2004 • 1 developer
Devices • Standard Slate • XP Tablet 2005 • Hardened Webpad • XP Embedded • “Hummer” Tablet • XP Tablet 2005 • PocketPC • CE.NET Derivative
System Architecture • Communication Via • 1xRTT • CDMA • Broadband Wireless (EDGE, EVDO) • Satellite • WiFi • LAN • J2EE application deployed on Tomcat • JMS Backbone for B2B communication
Technologies Off The Shelf • Client • Eclipse RCP • Communications • Broadbeam ExpressQ • Mobile IP • Wireless Matrix • Infrastructure • Websphere 5.0.2 • MQ 5.3