Systems Architecture and Integration – Case Study Example

Application Architecture Number) February 12, (Faculty Application Architecture Introduction Most people hardly reach an agreement when it comes to the definition of architecture. Applications architecture happens to be the building block of enterprise architecture in information systems. Application architecture could be used to discuss various applications useful in a business organization. The architectural uniqueness is based on business requirements. The large organization in the United States suggests the need for a centralized data management system with the ability to effectively manage networked offices. This study purposes to address the architectural, technological and ethical issues involved in the construction of a payroll program for a large organization. One important thing that is usually involved in enterprise applications or programs as the one required by the US Company is persistent data. Fowler (2003) affirms that “The data is persistent because it needs to be around between multiple runs of the program...”
Architecture
System architecture should be used in the new software application. This is due to its ability to translate the logical design of the desired information system into physical structure that entails network support, software, and hardware and most importantly secured processing methods (Northwestern University 2004). The management of complex environments can greatly be simplified by system architecture. Processing is conducted in such a way that the after collecting and reviewing the time sheet of an employee, it is engaged into the system architecture. The sheet is further saved in computer hardware for processing purposes. Due to the presence of the computer network the computed information is displayed across the network system so that it is visible to authorized personnel including the employees. This is an instance of simple functionality achievable through implementation of system architecture.
Involved Technology
The necessary technology suitable for system architecture range from web based transactional applications to complex systems that meet the enterprise strategy. The involved technological types can be identified as Service Oriented Architecture (SOA), Enterprise Application Integration (EAI), and Enterprise Service Bus (ESB) technologies (Dev Technology Group 2007). With the Service Oriented Architecture put in place, there will be ability in integration of business data, processes and the knowledge of the entire organization. In this case interfaces are platform-independent. SOA therefore enables a client using any operating system embedded in any machine to be serviced in any language. Secondly, the Enterprise Application Integration will enable the business to share data as well as business processes all over the networked applications within the system.
EAI can further be subdivided into four major categories which include; database linking, application linking, data warehousing, and common virtual system. Finally, Enterprise Service Bus technology can be attributed to an open standards-based distributed asynchronous messaging middleware. Its prime role is the provision of interoperability between enterprise applications through web service interfaces and XML. ESB also handles standardized rules built on routing documents. We can also identify the ESB technology as an earlier form of middleware which is simply EAI.
Graphical Representation
Graphical representation of the system in one form of software visualization aimed at demystifying the complexities behind development of the program. The diagram 1 bellow has been designed by dia, alternative software to Microsoft Visio.
Diagram 1
Ethical Issues
Should there be chances that the payroll system might get you into trouble with the law then it is considerate to change it. Therefor the potential issue likely to arise here is failure to get into good terms with the law. However most people go beyond the law based on their own definition of ethics. The application architecture can dawn a series of decisions based on wide range of factors. Each decision can have considerable impact on the maintenance ability, performance as well as quality. The proposed system introduces change into the company, an issue which might get some people offended. To some workers within the company it may sound very unethical being locked out of the company due to failure in knowing how to use the new system. Furthermore, aspects of business ethics can be related to “damage control” (Jasper 2006), or simply keeping off trouble. Another way we think of business ethics is in terms of “mission control” (Jasper 2006). This means doing something positive while attempting to create a greater culture in the company.
Conclusion
several software design architecture are not covered in this study. A preferred architecture is highly dependent on the type of software being developed as well as the preferred developer’s style. Service environment can be improved by endorsed system architecture. Many organizations are faced with the challenges of implementing new technologies into their systems. As much as every organization strives to better its services, some people as well as other organizations seem to show discontent.
References
Dev Technology Group. (2007, April). Systems Architecture and Integration. Retrieved from http://devtechnology.com/systems-architecture-and-integration/
Fowler, M. (2003). Patterns of Enterprice Application Architecture. New York, NY: Pearson Education, Inc..
Jasper, M. (2015, January). Ethical Issues With a New Payroll System? Retrieved from http://ethix.org/2006/10/01/ethical-issues-with-a-new-payroll-system
Northwestern University, .. (2004, January). System Architecture Primer. Information Technology, Revision. 1.01(543277-67), 1-7.