A software development framework for hardware centric applications: an architectural perspective

Throughout the history of Software Engineering, software development has been looked at from various perspectives, in terms of: usability, suitability for proposed problem, speed of development, relevance to real world scenarios, as well as in terms of the hardware that it needs to manifest itself in the real world. This paper delves deeper into the aspect of the actual core concept in software engineering: that of mapping software onto hardware[1], focused specifically on Hardware Centric systems (HCS), (systems where the hardware dictates to an influential level, the actual nature of the software); examining the various frameworks and concepts that exist for displaying this mapping from an architecture point of view, so as to establish if there is a need for a more complete and/or effective framework. It also proposes a roadmap proposal for a base architecture framework for the development of Hardware Centric applications, which will then be employed to determine if a suitable framework already exists.peer-reviewe

Integration and Deployment Techniques in Combination with Development Methodologies

Efficient and inefficient pairings of software development methodologies and software integration and deployment techniques exist. Often times the automation of code integration and deployment is chosen but the full benefit of these technologies are throttled by the incorporation of a development methodology. It can be hypothesized that the evolution of software development created this situation along with the latency of implementing development methodologies. This work examines four scenarios comprised of traditional and conventional development methodologies with manual and automated software integration and deployment techniques. Similar web-based software applications were selected from waterfall (traditional) and agile (conventional) run project development teams. The four scenarios were quantitatively analyzed through the use of a subjective component which took into account the common characteristics of each scenario. It was thought that the use of automation within an agile development methodology would show clear distinction when compared to the other three evaluation scenarios. However as discussed in the analysis, automated integration and deployment technologies benefited both waterfall and agile methodologies. Though due to agile\u27s foundational characteristics of small iterations with constant integration and deployments, the automation of both practices had more of a realized value and benefit

An Event Monitor and Response Framework Based on the WSLogA Architecture

Web services provide organizations with a powerful infrastructure by which information and products may be distributed, but the task of supporting Web service systems can be difficult due to the complex nature of environment configuration and operation. Tools are needed to monitor and analyze such Enterprise environments so that appropriate engineering, quality control, or business activities can be pursued. This investigation resulted in the development of a software development kit, the WSLogA Framework, which is inspired by the vision of Cruz et al. (2003, 2004). The WSLogA Framework provides distributed Enterprise systems with a platform for comprehensive information capture and environment management. Five component groups are intended for employment to enable integrated workflows addressing monitoring and response activities, but these components may also be used individually to facilitate the phased integration of the WSLogA Framework into existing environments. The WSLogA Framework\u27s design is portable across technology platforms (e.g., Java and .NET) and a variety of technologies may be substituted for the provided implementations to address unique system architectures. The WSLogA Framework supersedes existing logging and monitoring solutions in terms of both capability and intent. Applications based on the WSLogA Framework have an internal, real-time view of their operation and may adjust their environment based on the information provided by events related to their or system activities. The WSLogA Framework is intended as a software development kit around which system functionality may be organized and implemented, which makes the WSLogA Framework an architectural peer or complement to traditional application frameworks such as Spring\u27s Web module. WSLogA Framework based systems should be envisioned as information appliance elements rather than traditionally scoped applications or services