This article explores one major advantage XP could provide to embedded software developers: the ability to achieve meaningful progress prior to hardware availability. The article also looks at some of the difficulties of applying XP to embedded software development.

It is safe to assume the demand for applications on mobile devices will increase in coming years. Now is a good time to learn eJFace — the open-standards, embedded JFace library — a new technology to build embedded applications. Embedded JFace (eJFace) is a component of the embedded Rich Client Platform (eRCP), which provides an embedded environment for developers to compose user interfaces for embedded applications. Here, we compare eJFace to JFace and show how to develop applications with eJFace. eJFace consists of libraries that allow you to build applications without complex eSWT programming. It provides powerful APIs and introduces a Model-View-Controller (MVC) architecture for implementing and maintaining embedded applications painlessly. In this article, we explain how to develop applications with eJFace, and compare eJFace to JFace. This article will help developers who know JFace understand the differences between eJFace and JFace, and reduce the time needed to develop eJFace applications.

The complexity facing embedded systems architects today is daunting because of added requirements in safety, reliability, and network accessibility. Yet, the tools typically used are often a step behind large-scale software spaces and do not provide the ability to transition smoothly between the detailed device level and a total system view. Learn how to use open source standards such as DITA and PHP and tools such as blob representations to create a system-level environment to address these needs.

It is safe to assume the demand for applications on mobile devices will increase in coming years. Now is a good time to learn eJFace — the open-standards, embedded JFace library — a new technology to build embedded applications. Embedded JFace (eJFace) is a component of the embedded Rich Client Platform (eRCP), which provides an embedded environment for developers to compose user interfaces for embedded applications. Here, we compare eJFace to JFace and show how to develop applications with eJFace. eJFace consists of libraries that allow you to build applications without complex eSWT programming. It provides powerful APIs and introduces a Model-View-Controller (MVC) architecture for implementing and maintaining embedded applications painlessly. In this article, we explain how to develop applications with eJFace, and compare eJFace to JFace. This article will help developers who know JFace understand the differences between eJFace and JFace, and reduce the time needed to develop eJFace applications.

By studying concurrency bug patterns, you both increase your general awareness of concurrency programming and learn to recognize coding idioms that don't, or might not, work. The authors unpack six lesser-known concurrency bugs that threaten the thread-safety and performance of Java™ applications running on multicore systems.

The number of mobile device users is rapidly increasing, but the promise of solutions that leverage networks of connected devices has remained largely unrealized. Some of the pieces needed to build rich, connected experiences were not available until recently. This article explores some of the economic, social, and technology trends that are driving the adoption of mobile devices; describes the different kinds of user experiences that are now becoming possible; and presents an overview of architectural concerns associated with such mobility solutions, at the levels of hardware, software, connectivity, and services capabilities.

When it comes to embedded systems and mobile devices, developers face a very important choice between flat files and an embedded database, as any future change can be very risky and expensive. However, to meet deadlines and satisfy hardware restrictions, many developers build custom solutions from scratch, preferring a quick, simple implementation to a scalable one. As the product line evolves, these solutions can become very complex and difficult to reconcile with new requirements.

This article demonstrates how test-driven development and continuous integration addresses the unique challenges encountered when creating Windows Mobile applications.

When it comes to embedded systems and mobile devices software, developers face a choice between flat file and embedded database, as any future change can be very risky and expensive for their application, in a demanding market where shortcomings can result in failure.

Applications that are occasionally connected have a reputation for being difficult to implement. The challenges are layered, and the heart of the problem is how data is managed. Each occasionally connected client consumes and produces data at random intervals. Islands of data are produced when disconnected, and must be reconciled later when connectivity is restored. Technologies exist to move data to and from the clients, however, only the simplest of data reconciliation tasks are handled without custom code intervening. For example, SQL Replication is a fantastic technology for moving new data from one system to another. But when a record is updated by more than one client, should the last one in always win? Also, what happens when new data entities are created on multiple clients, but they each represent the same unique entity instance? Unfortunately, data models are usually too complex to be handled by generic conflict resolution processes.

This article will discuss how to build your data model to support an occasionally connected application. The data model supports the introduction of a complex conflict resolution process built in .NET. A point-of-service sample application is introduced with steep requirements, including: Web and smart client entry points; smart clients will be occasionally connected; data entities that span multiple tables; and a complex conflict resolution process which includes support for new records that can be created on the Web application and/or smart client application instances.