Current Search:  Enterprise application integration Computer systems (x)

View All Items

  • CSV Spreadsheet
(1 - 2 of 2)
Patterns for Enterprise Application Design and Development
Title
Patterns for Enterprise Application Design and Development.
Creator
Rubis, Ruslan, Cardei, Ionut E., Florida Atlantic University, College of Engineering and Computer Science, Department of Computer and Electrical Engineering and Computer Science
Abstract/Description
Designing and developing enterprise applications is a complex and resource intensive process, as it often must address thousands of requirements. At the same time, the software architecture of most enterprise applications at their core have many features and structures in common. Designers from different teams do not normally share design elements because of the competitive and proprietary nature of development, and enterprise applications design and development teams end up re-inventing the...
Show moreDesigning and developing enterprise applications is a complex and resource intensive process, as it often must address thousands of requirements. At the same time, the software architecture of most enterprise applications at their core have many features and structures in common. Designers from different teams do not normally share design elements because of the competitive and proprietary nature of development, and enterprise applications design and development teams end up re-inventing the wheel when tackling a new product. My objective is to formulate new design patterns for enterprise application architectures that assist software architects with reusable solutions to improve design quality and productivity. I achieve this by presenting seven patterns, each providing a solution to a specific challenge or a problem that is common to many enterprise applications. The Business Object Pattern provides a generic approach to design extensible Business Objects and their frameworks for enterprise applications. The pattern covers a number of concepts, including the Dynamic business object, the Static business object, constraints for validity, editability, and attribute visibility, as well as the mechanisms for workflow. The Business Object Life Cycle Pattern introduces the concept of stages which comprise a business object’s life cycle, and their relation to the business object’s integrity during that life cycle. The Simple Change History Pattern provides a concept of enforcing record keeping of the owner and date of the last change performed on a given business data object. The Business Data Object Versioning Pattern offers a solution by introducing a new version of a given business data object which allows for preservation of the original data. The Change History Record Pattern defines a solution for cases when there is a need to capture detailed information about the changes performed on a given business object, such as who made the changes, when, and what changes were made. The Permission Based Granular Access Control Pattern offers a basic approach for access control to objects and their attributes. Finally, the Money Object Pattern offers a language neutral approach to internationalization and globalization of business applications which require multi-currency capability. It is hoped that applying these patterns will provide many advantages, ranging from quicker delivery times to a more reliable software, and ultimately help achieve a systematic approach to designing and building complex enterprise applications.
Show less
Date Issued
2017
PURL
http://purl.flvc.org/fau/fd/FA00004976, http://purl.flvc.org/fau/fd/FA00004966
Subject Headings
Dissertations, Academic -- Florida Atlantic University, Enterprise application integration (Computer systems), Software architecture--Development., Software Design., Application software--Design., Patterns.
Format
Document (PDF)
Evolving Legacy Software Systems with a Resource and Performance-Sensitive Autonomic Interaction Manager
Title
Evolving Legacy Software Systems with a Resource and Performance-Sensitive Autonomic Interaction Manager.
Creator
Mulcahy, James J., Huang, Shihong, Florida Atlantic University, College of Engineering and Computer Science, Department of Computer and Electrical Engineering and Computer Science
Abstract/Description
Retaining business value in a legacy commercial enterprise resource planning system today often entails more than just maintaining the software to preserve existing functionality. This type of system tends to represent a significant capital investment that may not be easily scrapped, replaced, or re-engineered without considerable expense. A legacy system may need to be frequently extended to impart new behavior as stakeholder business goals and technical requirements evolve. Legacy ERP...
Show moreRetaining business value in a legacy commercial enterprise resource planning system today often entails more than just maintaining the software to preserve existing functionality. This type of system tends to represent a significant capital investment that may not be easily scrapped, replaced, or re-engineered without considerable expense. A legacy system may need to be frequently extended to impart new behavior as stakeholder business goals and technical requirements evolve. Legacy ERP systems are growing in prevalence and are both expensive to maintain and risky to evolve. Humans are the driving factor behind the expense, from the engineering costs associated with evolving these types of systems to the labor costs required to operate the result. Autonomic computing is one approach that addresses these challenges by imparting self-adaptive behavior into the evolved system. The contribution of this dissertation aims to add to the body of knowledge in software engineering some insight and best practices for development approaches that are normally hidden from academia by the competitive nature of the retail industry. We present a formal architectural pattern that describes an asynchronous, low-complexity, and autonomic approach. We validate the pattern with two real-world commercial case studies and a reengineering simulation to demonstrate that the pattern is repeatable and agnostic with respect to the operating system, programming language, and communication protocols.
Show less
Date Issued
2015
PURL
http://purl.flvc.org/fau/fd/FA00004527, http://purl.flvc.org/fau/fd/FA00004527
Subject Headings
Business logistics -- Automation, Electronic commerce -- Management, Enterprise application integration (Computer systems), Information resources management, Management information systems, Software reengineering
Format
Document (PDF)