Work-Related Project Analysis, Part 2 Paper University of Phoenix Systems Analysis and Design [BSA/376] July 27, 2010 Work-Related Project Analysis, Part 2 Paper This part of the paper focuses on the Systems’ Architecture and process design, in terms of data, processes, interfaces, and networks. Created charts and diagrams represent the activity explained in the following paragraphs. When finished, this part of the paper should display the solution for solving the issue of the accountings systems’ poor tracking of transactions and maintenance repairs.
Poor Tracking and reduction In Maintenance Solution The problem involved poor tracking of transactions and several maintenance repairs. To correct this problem a new design is developed. After testing the system with several types of analysis methods, the following designs for a system proves as the optimal solution. System’s Architecture Every system’s architecture largely permits or prohibits a system’s quality attributes such as performance or reliability.
This Accounting Transaction processing system’s performance will depend heavily on the system’s input/output architecture, data communications architecture, and the efficiency of the system software (Satzinger, 2004). An account transaction processing system’s architecture must support sharing data with many clients, tracking transactions, and most important support the organizational structure of business. Possessing the ability to access daily activity and provide quality service in an efficient way; makes room for good customer service.
Also this newly designed system will eliminate wait time for customers; most requests are processed while the customer waits. With this being the case, this architecture contains scalability to handle high volumes of requests. The Client-Server System is the chosen architecture design for this project. The system allows database functionality to be divided into a request and reply side. This architecture client application takes a load off shared network resources and server machines, and then puts it onto the client computers; this makes room for better performance and application flexibility.
The architecture includes independent, cooperating components (services) that can be allocated around and about an organization’s physical boundaries and security domains, using varying platforms; see figure 1, the architecture design. System Flow Chart In the illustration of Figure 2, the application software illustration identifies the various subsystems and their relationships (Satzinger, 2004). Setting the system in this fashion will let multiple transactions go through with just a minimal chance for delay.
To stay within budget, a system as this is adequate to maintain a mid-size organization’s business operations. If the system needs upgrading/restructuring in the future, this application can start out as a local client/server program, and later be run from anywhere in the world, efficiently accessing a database via the Internet, without costly reimplementation (Base, 2010). Data Flow Chart A flow chart shows the exact sequence of operations performed by a program completing a process (Flow, 2009). The data flow chart to this system illustrates the flow of operations.
The customers are the main driver for this system. Customers purchase product and an order is generated. Next the order is recorded and tracked in the system, and then the customer makes payment. Once complete this transaction is traceable for any after sale activity such as refunds or product returns. If the transaction is not internal then the billing part to the system activates and generates a statement for billing. The statement gets printed and mailed out to the external customer. The following illustration, Figure 3 displays a visual description to this data. Figure 3. Data Flow Diagram
Conclusion Accounting Transaction processing systems are relied upon in the business world. These information systems must accomplish task, provide reports, and maintain records on a regular basis. Through reading several articles, it seems accounting systems make accounting management more manageable (Matthews, 1967). In addition; when implemented correctly; an organization can provide their customers with a quality of excellence. References Base One International Corporation. (2010). Base One’s Service Oriented Architecture Retrieved July 27, 2010 from: http://www. boic. com/dbsoa. tm Flow chart. (2009). In the Hutchinson Unabridged Encyclopedia with Atlas and Weather guide. Retrieved from http://www. credoreference. com/entry/heliconhe/flow_chart Matthews, R. (1967). A Computer Programming Approach to the Design of Accounting systems. Abacus, 3(2), 133-152. Retrieved from Business Source Complete database. Satzinger, J. W. , Jackson, R. B. , & Burd, S. D. (2004). Systems Analysis and Design in A Changing World, Third Edition. Retrieved on July 27, 2010 from https://ecampus. phoenix. edu/content/eBookLibrary2/content/eReader. aspx ———————–
