You are on page 1of 2

ACCY225 Tutorial 4 – Systems Development Life Cycle

User -> System -> Issue -> Acquire New System via SDLC

Accounting System
Functions:
Store acctg data
Analyze
Safeguard

Three Keys
When developing new system
People
 System Analysts
Processes
 SDLC
o Plan
o Analuse
o Design
o Build or buy
o Install
o Deploy
Plan and analyse – fix user problems
Install – training users and providing documentation
Deploying it – repairs, maintenance

Define each step and describe what happens in each step


Go through each step and analyse whether it has been completed
comprehensively

Link this all back to whether user’s initial problem is fixed


Technology
 Software
 Hardware
 Networks

Part 1
- Format answer around SDLC steps
- Plan
o Katie didn’t interview users affected
o Should have conducted interviews with current users to determine
current issues, what they need for decision making and
informational needs
- Analytical
o Should have thought about capabilities of new system and generate
discussion around new system
- Design
o Ensure system is suited to user needs rather than copy off old
system (user focused)
- Build/Buy
o No review of changes to modules
o No authorisation of changes
o Changes should be reviewed
o Should have consulted depts. affected by changes
o Should have tested changes more thoroughly rather than
concerned with labour savings prior to implementation
- Install
o Should have given more complete instructions
o Should complete training of users on new system
o Usage of backup procedures
- Deploy/In General
o John and Katie should have worked out the informational needs of
users and established a schedule on the reports that users needed

Q2
Internal controls were not changed, co-ordinated or properly developed or
evaluated in any way.
Backup procedures were lacking
Systems, programming, documentation were behind schedule
Segregarion of duties issue: inventory and purchasing control allowed to prepare
journal entries or produce purchase orders etc.

Q3
Weakness Recommendation
Plan and analyse No systems analysis - Perform systems analysis
(copied and pasted from
previous system and did
not ascertain users’ needs)
Build/Buy Systems testing and All modules need to be
reviews not conducted tested, reviewed thoroughly
prior to implementation for effectiveness
Little/no user involvement Participate in planning
phase (interviews and
brainstorms)
Participate in testing and
final implementation
Install No Training Doc should have been
Lack of documentation prepared prior to
installation and everyone
trained

You might also like