Systems Development LifeCycle in IS

26 Feb

Continuing on from where I commenced yesterday, today I will list the threats that this change to IS can cause:

• Fire
• Power failure
• Hardware malfunction
• Software errors
• User errors
• Computer crime, hackers & viruses
• Computer abuse

Therefore the company can have controls in place: these can bethe specific technology, policies, and manual procedures for protecting assets, accuracy, and reliability of the IS

1)Hardware>>>> eg: restrict access preventative maintainance
2)Software>>> EG: Activity logs, Restrict access
3)Data security>>> eg: Password, Restriction Access and Encryption
4)Operations>>> eg:
5)Systems Development>>> eg:
Management review & audit

Documentation

6)Management>>> eg:
Formal written policies & procedure

Division of labor

Supervision

Accountability

7)Application

8)Input>>> eg:
Authorization/validation

Control totals, e.g., record counts

Edit checks, e.g, format check, existence check

Error correction

9)Processing>>> eg:
Edit checks, e.g., check digit

Control totals, e.g., hash totals

10)Output>>>

eg:Control totals

User feedback

Authorization

Reference: https://www.uky.edu/~dsianita/320/ch4.html

One Response to “Systems Development LifeCycle in IS”

  1. sad112540853 March 11, 2013 at 10:47 am #

    Great blog once againg😀 I really like the way you have lined all your blogs together😀 The layout of your blogs are really well done and they are easy to read and understand😀 Your blogs have a lot of great information on them which are really relevant for the exams😀

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: