Download presentation
Presentation is loading. Please wait.
Published byBonnie O’Brien’ Modified over 9 years ago
1
S556 Systems Analysis & Design Week 14: December 2, 2008
2
S556-Fall2008 2 Evaluation Team member evaluation Course evaluation http://www.indiana.edu/~best/ go to QuizSite (Students)
3
S556-Fall2008 3 Final Project Presentation 20 minutes each Every member of the team should be involved You are welcome to invite your clients
4
S556-Fall2008 4 Final Specification Document The deadline is 5pm on Friday, December 12 Your team needs to submit both a hard copy and an electronic copy to Oncourse Oncourse Include contact information of clients (name, physical address, & e-mail)
5
S556-Fall2008 5 Design Ideas (Verganti, 2006) Functionality vs. form Design change the experience, though $159.00 a piece
6
S556-Fall2008 6 Go Beyond Your Imagination When you design... Web 3.0 (Roush, 2006)
7
S556-Fall2008 7 Risk-payoff Analysis (Yen & Davis, 1999) Area 3: advance immediately Area 4: do nothing until resources or the expected payoff increases Area 1: wait until additional analysis reduces the risk Area 2: stop immediately payoffs risks Area 1 high payoff high risk Area 3 high payoff low risk Area 2 low payoff high risk Area 4 low payoff low risk
8
S556-Fall2008 8 Organizational Change Designing information systems for end users is as much about changing the behavior of users as it is about the technology itself (Regan & O’Connor, 1994)
9
S556-Fall2008 9 Planned Organizational Change Information analysts needs to be technical experts as well as effective change agents Planned change has both: a technical and a social aspect
10
S556-Fall2008 10 Understanding Resistance to Change Social uncertainty Limited perspectives Lack of understanding Resistance to technical personnel Perception that costs outweigh benefits Fear of failure or inadequacy Loss of control Feelings of insecurity Threat of economic loss
11
S556-Fall2008 11 Overcoming Resistance to Change (HWW, Ch 16) Water drop method Make your project visible ROI Defining requirements Time to code Customer response Develop success stories
12
S556-Fall2008 12 Adoption Adopter (Rogers, 1995; 2003) Innovators Early adopters Early majority Late majority Laggards
13
S556-Fall2008 13 Adoption Adopter stage (Dormant, 1986) Awareness Self concern Mental tryout Hands on trial Adoption Air-car by Tata Motors
14
S556-Fall2008 14 Involving Top Management in IT Projects (Simonsen, 2007) Participatory design Problem/ Need CausesConsequencesSuggestions for solution Not able to contact SLIS graduates No up-to-date contact information of SLIS graduates Difficult to network ??? Contact IU Alumni Association Provide systems for SLIS graduates’ information Use existing SNS
15
S556-Fall2008 15 Lessons learned? Are there any lessons learned in this class that you’d like to share?
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.