Systems Development LifeCycle in IS

25 Feb

To look at the SLDC from a different perspective I decided to focus on alternative ways of developing systems where the SDLC isnt directly involved.
I am of the opinion that you need to examine it in the following way:

> You first need to examine how you would approach developing the system by asking questions such as what? When? Why? Why not?

> Then you can choose what method you would feel gives the best outcome under the three questions that I mentioned above!

Medium to large mainframe-based systems
1.Structured

2.Formal
1.Time consuming

2.Costly

3.Inflexible

Prototyping
Building an experimental system quickly and cheaply
Unclear user requirements
1.User involvement

2.Fast
1.Poor system quality

2.Lack of standard

Packages
Purchasing programs that have been written and tested
Common system solution
1.Limited technical skills

2.Cost saving

3.Clear expectations
1.Not meeting all needs

2.Customization

End-user Development
Building the system by end-users with little or no formal technical assistance
Personal & small applications
1.No misunderstanding

2.Fast
1.Limited scope

2.Loss of control

Outsourcing
Using an external vendor to develop or operate an organization’s ISs
Mission non-critical applications
1.Reduce costs

2.Predictability
1.Risky

2.Loss of control

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

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: