Fluent Essays

Attached are needed corrections for asignments you have helped me with, the needed corrections are in highlighted in yellow next to the corresponding picture. Please correct , last paper is due soon but these correction must be submitted prior to moving to the last phase. week5ct.docx week6ct.docx Unformatted Attachment Preview Running Head: MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS Module 5: Option #2: Phase 2: Mamma Mia Accounts Payable – Data Flow Analysis James Byrd MIS 350 – Information Systems Analysis and Design Colorado State University – Global Campus Dr. William Willette December 15, 2019 1 MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS 2 Mamma Mia Accounts Payable – Data Flow Analysis Background of the case The business in this context involves the creation of two large systems that will be integrated into a more comprehensive information solution. The business has encountered a challenge in supplier management and payment to the vendors. In this context, the use of the current model has created a gap in the achievement of the desired level of performance in the long run. However, the business operates under a set of systems that help it to achieve its day to day goals. One of the main issues that the company has focused on is financial management. The current systems allow the company to deliver services under minimum levels of defects and downtime. The business does not see the need for using a cloud-based system because of the associated security issues. Also, the business does not want to use cloud systems because the current architecture offers a platform for improved service delivery. However, regardless of the idea that the business is achieving better performance, the element of supplier and invoice processing is a problem. The company does not have an automated system to perform supplier and invoice management activities. Therefore, this section discusses the elements of the creation and integration of an account payables system into interior architecture. This integration will help the business to achieve maximum growth in the long run based on the idea that it will focus on the delivery of quality services as well as efficient management of invoice and payment processes. However, the integration of the desired system calls for the company to first understand the primary needs and requirements of the selected module. The flow chart provided previously MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS 3 shows the interactions amongst the three leading players as far as the account payable system is concerned. Understanding these needs will help in the formulation of a reliable architecture for the creation of an efficient database that will foster better performance (Degroeve et al., 2014). The selected system Account payable system aids in the management of bills that an organization incurs logically and efficiently. The primary aim that the system focuses on achieving is efficiency as far as the management of finances of a company is concerned. Timely payments to vendors have been a significant problem for the company in the context. Further, the business claims that it had encountered a significant problem in the creation of a reliable payment prediction mechanism since it relies on a lengthy process of invoice and vendor management activities. Creation of the proposed system will help the company to form a foundation for improved efficiency and insight into future trends as far as invoice payments are considered. The inputs for the system are payment receipts, goods received, deposits, credit memos and but not limited to the vendor invoice. The outputs for the system are in the form of reports such as cheques, payment vouchers, vendor credit memos, analysis reports and but not limited to edit reports. These reports can be downloaded for future reference or viewed using the web-viewer interface. Context diagram The first element to address as far as the design and visualization of the proposed system is the context diagram. This representation is also referred to as a level 0 data flow diagram (Repa, 2013). A context diagram shows the ultimate boundaries that a system exhibits and its relationships with the external entities. The external entities in this context are the suppliers or vendors. The other entity that interacts with the system is the accounting department of the MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS company. Therefore, the proposed accounts payable system will be interacting with both suppliers and accounts department for the firm in the management of invoices as well as payments for the vendors. The context diagram for the accounts payable system is as shown below. The correct term is: Accounts Payable All charts, tables, and figures must have a label, a number, a title, and if necessary, a proper citation and reference. Accounts Payable Level 1 data flow diagram Adding just a data sink is not sufficient decomposition. Also some process flows in the context DFD have been eliminated. Each entity should only be listed once per DFD. 4 MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS 5 As opposed to the level 0 contest diagrams, level 1 offers a platform for exploring the interactions of the system based on the main sub-processes. The context diagram above shows the interactions of the system with the external players. On the other hand, level 1 diagram in this context will show the interactions of the main processes and their roles to the creation of a conventional system. The level 2 diagram is as shown below. This section outlines two of the main processes that make up the system and their interactions through the two levels 1 diagram. All charts, tables, and figures must have a label, a number, a title, and if necessary, a proper citation and reference. Is there no link between Payables and Pruchases Orders and Reports? Then how does Purchase Orders and Report access the data sink Purchases Order that is connect to Payables? Level 1 data flow diagram This diagram shows the interactions of the processes in a more detailed structure. The advantage of using this model is that it offers a platform for the exploration of the possible connections that the central system exhibits with the primary players and stakeholders. The leading players in this context are the purchases department, the receiving department, and the vendors. The vendors are the main point of focus for the company and system in this context. On MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS 6 the same note, the main reports that the system releases in this context are received goods, purchases orders, invoices and the status of the account payables. Level 2 data flow diagram Who starts these processes? Surely the vendors do not start the invoice approvals process. There should only be one Vendors entity in any DFD. Level 2 data flow diagram is an exploded view of level 1. This diagram shows more details that a given system exhibits (Tiwari, Tripathi, Sharma & Dubey, 2012). For instance, the diagram, in this case, shows the connection amongst the various subprocesses which make up the entire system. Interactions of these systems help the creation of a platform for improved connection and understanding of the working of the proposed system. The processes shown in this context offer a platform for understanding the overall makeup of the entire system and the associated records. Each of the records, in this case, form a foundation for capturing the overall components and records that the system will interact with. The diagrams above and below show MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS the makeup of the system outlining the records, data stores and significant processes that the resulting solution will exhibit. Level 2 data flow diagram All charts, tables, and figures must have a label, a number, a title, and if necessary, a proper citation and reference. Which level 1 process is being decomposed? Why is process 03 not connected to the other process? How does it start? Why would Mamma Mia generate an invoice in process 02? Why would the vendor send a payment to process 02? Why would invoice records be stored in process 02? 7 MAMMA MIA ACCOUNTS PAYABLE – DATA FLOW ANALYSIS References Degroeve, B., Petroons, J., Hanan, C. C., Bailey, A. G., Gupta, S. D., Mellyn, K. L., ... & Mondschein, C. (2014). U.S. Patent No. 8,712,887. Washington, DC: U.S. Patent and Trademark Office. Repa, V. (2013). Object-Oriented Analysis with Data Flow Diagram. In Information Systems Development (pp. 419-430). Springer, New York, NY. Tiwari, K., Tripathi, A., Sharma, S., & Dubey, V. (2012). Merging of Data Flow Diagram with Unified Modeling. International Journal of Scientific and Research Publications, 403. 8 Running Head: ENTITY-RELATIONSHIPS AND DATABASE DESIGN Module 6: Option #2: Phase 3: Mamma Mia Accounts Payable – Entity-Relationships and Database Design James Byrd MIS 350 – Information Systems Analysis and Design Colorado State University – Global Campus Dr. William Willette December 22, 2019 1 ENTITY-RELATIONSHIPS AND DATABASE DESIGN 2 Accounts Payable – Entity-Relationships and Database Design Introduction The previous submission looked at the basic building blocks of the two main subsystems that will be included in the central architecture. The business operates under a system that needs improvement as far as the management of suppliers and accounts is concerned. In this context, the company needs to create a reliable system that will aid in the improvement of operations carried out on the day to day basis. The previous submission looked at the UML modelling of the proposed solutions. This submission, on the other hand, looks at the database modelling of the proposed system (Elmasri & Navathe, 2017). The selected option is the creation of a database model for the account payables subsystem. The creation of such models will help in improving the level of insight into the final database that the company should implement into the company. There are two main models and approaches which can be used include the logical and physical designs. Logical data model The consistent model offers a platform for viewing the general and structural makeup of the database of the proposed system (Thalheim, 2013). The figure below shows the entity relationships diagram for the proposed system for Mama Mia. ENTITY-RELATIONSHIPS AND DATABASE DESIGN Figure 1: ER Diagrams Entities missing attributes, including primary and foreign keys. Cardinality is not represented at both ends of the relationship lines. No textual explanation provided. Physical data model The physical model shows a complex and expanded view of the design of the database. This design contains the definition of data and the respective tables. The figure below shows the database tables and the data definitions. 3 ENTITY-RELATIONSHIPS AND DATABASE DESIGN Figure 2: Physical database model Missing data types and field sizes. Cardinality is not represented at both ends of the relationship lines. No textual explanation provided. Payment Entry entity shows more than one PK. Entities Acc_PayBill, Advance, BillItem, and PaymentDetails show the same PK, which is not allowed in relational databases. 4 ENTITY-RELATIONSHIPS AND DATABASE DESIGN References Elmasri, R., & Navathe, S. (2017). Fundamentals of database systems. Pearson. Thalheim, B. (2013). Entity-relationship modelling: foundations of database technology. Springer Science & Business Media. 5 ... Purchase answer to see full attachment