SYSTEMS PLANNING,

DESIGN AND
IMPLEMENTATION
6.53

Febrina Handayani 2221031008

Friscilya Sembiring
Pipin Apriani
Siti Aisyah 2221031018
INTRODUCTION
Information systems (IS) are developed for different purposes, largely
depending on human and business needs.These are merely a sample of
questions managers may explore with key stakeholders and with systems
analysts. To address some of these questions this chapters examines AIS
system development approaches. Systems analysts systematically assess how
users interact with existing or new business technologies while identifying
specific functions, for example, accounting and user needs to gather and
process data to support the organisational strategy. In this chapter, we
examine the systems development lifecycle to identify how it guides the
design, planning and implementation of AIS.

2
ACCOUNTING INFORMATION SYSTEMS
(AIS)
AIS is defined as a specialised subset of an AIS are designed to facilitate
organisational information system that both financial and non-financial
accumulates, classifies, processes, analyses and analysis and reporting by
communicates relevant financial transaction supporting various accounting
information to internal and external parties and tasks
supports management in decision making tasks.

AIS have three basic functions:

1. Efficient and effective collection and storage of financial
data and activities;
2. Ensure controls are in place to accurately record and
process data.
3. Supply accurate and timely information to support
decisions through various reports and financial statements

3
 ALIGNING PEOPLE, PROCESSES
AND TECHNOLOGY
Factors which influence the success of AIS

There are three key factors to the success of AIS to drive organisational
strategy: people, processes and technology. AIS researchers often examine
how accounting and IT systems are designed (technology) to support
strategic and operational decision needs (people) that are necessary for the
implementation of an organisation’s strategy (processes) (Macintosh and
Quattrone, 2010; Hall, 2012).

7/1/20XX Pitch deck title 4

 AIS BUSINESS PROCESSES
A business process can be described as a
structured set of activities designed to
achieve a specific business goal or
objective
Understanding how the AIS brings about
improved structures and procedures to
execute key processes allows a business to
enjoy improved efficiencies, transparency,
visibility, audibility and overall improved
business performance
7/1/20XX
Defining how specific processes align
with a business strategy to deliver a
required organisational output is a key
factor for the implementation of AIS
Understanding how the technology can support business
processes requires technical knowledge on how the
technology capabilities are tailored to achieve business
goals and non-technical knowledge on the success and
credibility of technical solutions from case studies or
testimonials that support evidence of successful
implementation
Pitch deck title 5
 AIS APPLICATION LAYERS
At an abstract level, the logical architecture view illustrated in
Figure 4.2, indicates a set of cooperating services grouped into
the three key layers of the AIS:
1. Presentation: comprising the user interface
components to deliver user-orientated services,
which enables user interaction with a system. This
layer acts as a bridge to the core business services.
2. Business: comprising the business workflows,
business components, business entities to
implement the core functionality of the system and
execute key business processes.
3. Data: comprising data access components, data
utilities, service agents which are accessed to
support the business layer typically access through
defined business services.

6
 AIS APPLICATION LAYERS

Simple and quick to Creates spaces for Reduces carbon

build community footprint
interactions

7/1/20XX Pitch deck title 7

DEVELOPING AIS WITHIN A SYSTEM
DEVELOPMENT LIFECYCLE
In recent years, organisations have increasingly adopted cloud-
based AIS to enjoy the benefits
of reduced cost and improved accessibility. In other cases,
organisations will seek system analysts
to design, plan and implement bespoke AIS. This requires a
systems analyst to develop an understanding
of the organisation and identify what the ideal configuration of
the system components
are to align with an organisation’s operations. This requires the
analyst to undertake a number
of key steps (Figure 4.3) within the system development
lifecycle (SDLC).

8
The SDLC Framework Defines Steps Within The Software Development Process.
As Illustrated In Figure 4.3, The SDLC Comprises The Following Key Stages To Develop
AIS:

1. Planning and requirement analysis

Gathering and analysing requirements is considered to be the most important

stage of the SDLC as it provides the very foundation that the entire AIS project will
be based on. This phase requiresinput from senior stakeholders, market analysis and
a feasibility study to determine the scopeof a project.

2. Defining requirements

Having gathered information from key stakeholders during the requirements

analysis process, it is critical that the systems analysis begins to define and
document the AIS requirements. Through the identification of common themes and
the prioritisation of key stakeholder requirements, the analysts will record
requirements on a Software Requirements Specification document. This document
will list all requirements that must be met in the design and development stages of
the SDLC.

9
3. Designing the AIS architecture

The Software Requirements Specification document acts

as a vital reference source to guide the AIS product architects
on the most suitable solution for the client.
To confirm that therequirements align with the
4. Building or developing the AIS
organisation’s needs, the Design Document Specification is
reviewed by key stakeholders to ensure that the project is
The fourth stage focuses on how the AIS is
within budget, can be delivered on-time, the system is robust,
built and emphasises the importance of having a
the system does not present any risks to existing business
quality Design Specification Document to
operations and that the design is acceptable and meets their
reference and guide the development process.
expectations.

7/1/20XX Pitch deck title 10

5. Testing the AIS

Testing is a critical process throughout each of

the key phases of the SDLC. Within this specific
phase requires testing on various AIS defects
through tracking, reporting, fixing and retesting in
accordance with software quality standards.

6. Deployment in the market and maintenance of the AIS

When the testing phase of the AIS is complete, it can be

deployed and released in the market in accordance with the
organisational strategy. This may be achieved by targeting a
specific segment of the market to gather feedback through user-
acceptance testing.

11
 AIS SOFTWARE PROTOTYPING
Software prototyping refers to building software application prototypes that provide the functionality of the product
under development, although it does not present the sophistication or exact logic of the planned AIS.

There are different software prototyping types widely used, such as:
1. Throwaway/rapid prototyping: this requires minimum effort to establish customer requirements whereby the
developer launches into building a prototype.
2. Evolutionary prototyping: developing prototypes with minimal functionality to allow requirements be well
understood and evolved throughout the development process.
3. Incremental prototyping: developing numerous functional prototypes of the sub-systems and integrating the
prototypes to develop a finished system solution.
4. Extreme prototyping: typically conducted within the web development domain using HTML format, simulating
data processing, implementing services and integrating all components into a final prototype.

7/1/20XX Pitch deck title 12

 SUMMARY

7/1/20XX Pitch deck title 13

 THANK YOU

7/1/20XX Pitch deck title 14