Organization/Industry Description (approx. 1 page): Describe the products/services sold by the firm. Describe the firm’s industry, primary competitors, etc. Include an organization chart showing the intended major reporting relationships that you will design into your group’s system. Discuss significant industry trends and competitive/operational challenges (e.g., slow growth, new competitors, new regulations, etc.) Cite all sources used (including trade journals, general business publications, Web pages, and primary sources). The project should be properly referenced using an accepted reference technique accompanied by appropriate bibliography and literature review at the end of section 2.1.
2.2 Describe the purpose and key features of each relevant part of the AIS as designed. (approx. 2 pages per sub-system). Describe how each of the proposed AIS sub-systems contributes to organizational goals. On the organization chart, show how the departments in which each AIS sub-system is used relate(s) to the larger organization. Describe each sub-system’s major functions, typical transactions, reports produced, and frequency of transaction and master file updates.
2.3 Discuss how your system addresses the main issues specific to e-business systems: (approx. 2 pages). Identify the main issues that are specific to e-business processes/activities/systems (as opposed to “traditional” business processes/activities/systems). Discuss how your system design addresses these issues.
2.4 Describe how each of your proposed AIS sub-systems will provide data for managerial decisions. (approx. 1 page per sub-system) Describe the typical managerial decisions supported by each of the proposed sub-systems and what other data and/or information is needed for these decisions in addition to that supplied by the system.
2.5 Describe the key features of AIS software chosen (approx. 2 pages). As part of the AIS design process, you will identify suitable software application(s) to support your system design. Normally suitable software application(s) are identified after the system has been designed and system specifications are identified. However it may be possible to integrate the process of application selection and design as an iterative process (i.e. find suitable software, identify its key features and adopt these features into your sub-systems design). Obtain a copy of the chosen AIS software brochure. Read the comments about the accounting software in the brochure in respect to those modules that the group has chosen to report on. Identify and describe the key elements and features that apply to each of the subsystems under review. Describe the computer and network hardware and software that might be used and interfaces with other systems (from which it receives data or sends data). Discuss whether the organisation uses reasonably current technology, and show how the components of the system are arranged. Include such details as hardware brand (e.g., Dell, HP), processor (Intel CDU College of Business and Law Page 5 of 7 Assignment Project Details_ACT506_S2, 2019 Core i7-8700K, AMD FX-8350, etc.), operating system (e.g. MAC OS, Windows 10 — include version numbers), database software (e.g. MS Access, DB2, Oracle), network description (LAN, WAN, or both), and network software used (e.g. Cloud/SaaS, Windows Server 2016, Linux; Apache Web Server). Note whether the software was developed in-house or purchased, and describe the contractual relationship with the software vendor.
2.6 Discuss a few points of similarity/contrast between each relevant part of your AIS design and that described in the relevant chapter (½ page per sub-system). Consider the “standard” description of the system and compare and contrast your system design with the “standard” description. Where significant differences exist suggest reasons for the differences (such as changes to accommodate/compliment controls in other systems, cost effectiveness etc.)
2.7 Document the system using narrative and flowcharts (2 pages) • Prepare a two pages narrative describing the operation of each of the sub-systems under review, it’s data flows, processes, forms, files and reports. Prepare a Level 0 Logical Data Flow Diagram, decisions • Prepare a Document systems flowchart which is consistent with the Level 0 Logical Data Flow Diagram and Narrative
Part 3: Internal Controls Analysis and Documentation, and Recommendations Preparation: Your group should meet once or two times to discuss the controls (or lack of controls) that you designed in your firm’s system, prepare a control matrix describing them, analyse their effectiveness and efficiency. Identify if your system has “built-in” control deficiencies. Then prepare the documents listed below. Detailed description of the requirements for this section and the draft report are as follows: There are no recommended or suggested page lengths for this section. The page lengths are entirely dependent on the elements discussed. However it is expected that you will be relevant, clear and concise in your discussions.
3.1 Partial Control Matrix: include at least 7 existing control plans and any ("missing") control plans for each subsystem examined. These control plans should relate to the “key” or “main” objectives of each of the relevant parts of the client’s sub-system under review. As the case study will have some necessary constraints that will prevent you designing a perfect system, you will need to identify control weaknesses and inefficiencies inherent in your design and what recommendations or design changes you would suggest to improve the efficiency and effectiveness of the AIS, if some or all of the constraints are reduced.
3.2 Control Matrix Explanation: Describe how each control plan helps (or would help) achieve system goals.
3.3 Control Analysis: Discuss the overall adequacy of controls used in each sub-system under review. Discuss the efficiency and effectiveness of controls (if an operations or information system goal has no plan listed under it on your matrix, why not? Does an expensive control support a single goal? Is this appropriate, in your judgment? Are there control deficiencies in your system design due to cost effect constraints, software incompatibility with your preferred system etc.? If so why is this appropriate, in your judgment? Discuss the mix of preventive, detective, and corrective controls. Form a conclusion as to the quality of the controls, based on the system’s environment and user needs.