代做Accounting Information Systems代写Python语言

Accounting Information Systems

Guidelines for Group Project

(version 2023.09.07)

1. Critical success factors for a Group Project

A good team is one in which every member has a role to play.

Brainstorming is helpful in deriving something innovative and creative.

It is important you enjoy the process of group work on the project while learning something new by yourselves!

2. Topic Identification

This project aims to design a system for a business organization. Example systems include but are not restricted to the following.

Sales System (SS). Purchase System (PS). Enterprise Resources Planning (ERP) system.

Customer Relationship Management (CRM) system. Supply Chain Management (SCM) system.

Human Resource Management (HRM) system. Accounting Information Systems (AIS).

A combination of systems, for example, SS + AIS, or PS + AIS.

A system is of a business purpose for an organization.

Contents to submit should include:

1. The name of your system

2. A brief discussion on the purpose of your system

3. A brief discussion on the functionalities of your system

One representative submits this assignment in a Microsoft Word file.

3. Our Expectations

1. This project expects you to integrate the knowledge you acquired from different chapters of the AIS course into the project. It is assumed that you take the roles of business analyst and system analyst.

2. This project is to facilitate you with some practical experience in writing a system proposal and implementing a system through the system development life cycle (SDLC) of software engineering and project management.

3. This project does not expect a fully developed system and it is impossible for you to do so at this stage. Actual programming codes for functionalities are not required. However, you may add some codes or criteria for input checking in a form. and transition between forms (i.e. in the user interface).

4. You should include system security features and internal control (e.g. business rules) features in your design.

5. You may refer to Chapter 18 which introduces each phase in the systems development life cycle (SDLC). Your proposal should cover the planning, analysis, and design phases. The implementation phase should additionally be included in your project report.

6. We do not confine the software tools you use. You are free to choose any backend tool for the database and front-end tools for the user interface. But you should be able to use them with a reasonable degree of proficiency.

For example, you may use Microsoft Access as a backend as a database and other tools (such as Python) for the front end.

On the other hand, Microsoft Access provides functions for both the backend and front end. Therefore, Microsoft Access alone is enough as development software for your use in the project.

7. As our AIS course covers Microsoft Access, every student should be fairly proficient in using it. Therefore, you have the relevant technical background to work on the project.

4. System Proposal (10%)

Your proposal should cover the following aspects.

(1) Forward

To describe what is the purpose of the system

(2) Legacy system

Assuming that you have a legacy system, what possible problems with the legacy system(s) can you think of?

(3) New System

1. Mission, vision, and objectives of the new system

2. Restrictions, risks, and scope

3. Functionality and data description

What user interfaces are provided by your system?

What reports are to be generated by your system?

Documentation:

1. Use Business Process Modeling Notation (BPMN) for your business system design.

Databases:

a. Draw REA diagrams to describe the file structure for your system

b. Describe table structures (normalized)

c. Show the class relationships by using Unified Modeling Language (UML) or Entity Relationship Diagram (ERD)

Note: We call the relationship diagram in Microsoft Access ERD.

Internal Controls:

Describe the internal controls implemented in your system

Categorize these controls as Obligatory, Prohibited, or Allowed

Types of Business Rules:

• Obligatory. This rule form. states what should occur. For instance, payment should be made in the U.S. dollars.

• Prohibited: This rule form. states what should not occur. For instance, no payments should be made by check.

• Allowed: This rule form. says what is allowed under what conditions. For instance, credit card payments are allowed if the card is American Express.

(4) Feasibility Report

a. All possible solutions

b. Evaluation

c. Cost and benefit analysis of the best solution

(5) Consideration for the new system

Time schedule

Cost estimation

Division of labor (an actual division of labor in your group)

(6)  Recommendation

Whether to proceed with the system development?

In what ways?

(7) Remarks and References

5. Project Report (10%)

1. It should include relevant parts in the proposal

2. Implementation of the system design as described in the proposal

a. Convert class diagrams into Microsoft Access tables. (You will have to make assumptions about the field lengths and types)

b. Implement user interfaces

c. Input sample data

d. Write SQL statements for building reports

e. Generate business reports

Microsoft Access is a simple and relatively easy-to-use database management system (DBMS). It can be used both for the backend as a database (Tables) and the frontend as a user interface (Forms) and reports.

1. Tables: to store data that consists of a series of rows (records) and columns (attributes) connected by relationships (links between tables by foreign keys).

2. Queries: to retrieve and display data stored in the database.

3. Forms: to enter data into tables and view existing records with queries.

4. Reports: to integrate data from one or more queries and tables.

Some remarks:

1. You may include an operation manual. But this is optional.

2. When designing data structures in a database, you can use the data normalization technique and indicate the procedures of your data normalization in your report.

3. Sample data should be input for report generation and demonstration.

6. Group Project Materials

All relevant group project materials should be submitted as evidence of your work.

7. Peer Evaluation Sheet

You need to submit the peer evaluation sheet for evaluating your peer groupmates. Your submission is also an indicator of your level of participation.

8. Presentation (10%)

1. To use PowerPoint slides

2. To demonstrate the operation of your system