View
221
Download
2
Category
Preview:
Citation preview
Z556 Systems Analysis & DesignSession 13
ILS
Z5
56
1
Final Project Presentation
• 15-20 minutes each• Every member of the team should be
involved• Follow the outline of the final
document, but include a report on feedback from the client/users
• You are welcome to invite your clients
ILS
Z5
56
2
Final Specification Document• The deadline is 5pm on Wednesday,
April 29. Your team needs to submit both a hard copy and an electronic copy to Oncourse
ILS
Z5
56
3
Tips for Writing the Final Specification Document• Executive summary should be a separate
document• can use the drafts you’ve previously submitted
for this semester• Should include work models in the documents & explain these models in the text.• If models are peripheral or too much details to be
included in the text (in other words, that would distract the readers from seeing the problems/current situation, include them in Appendices (but make sure to point them in the text).
ILS
Z5
56
4
Tips for Writing the Final Specification Document• Include data you’ve collected to demonstrate
current problems (e.g., quotes and examples) in order to either demonstrate the problems or justify the salutation (or both)
• Data collection methods can be included in the appendix if the client request it
• Conclusion in the final specification document should encourage the client to pursue the solutions you suggested
ILS
Z5
56
5
Design Ideas (Verganti, 2006)
• Functionality vs. form
• Design change the experience though $169.00 a piece
ILS
Z5
56
6
Verganti, R. (2006). Innovating through design. Harvard Business Review. 84(12), 114-122.
Exeprience Design vs. Interface Design (Buxton, 2007)
• Even $400 a piece
• The “difference did not come by accident”
ILS
Z5
56
7
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)
ILS
Z5
56
8
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
ILS
Z5
56
9
Business Analyst Manifesto (Brandenburg, 2010)
Out of chaos, we create orderOut of disagreement, we create alignmentOut of ambiguity, we create clarityBut most of all, we create positive change for the organizations we serve
ILS
Z5
56
10Brandenburg, L. (2010). How to start a business analyst career: A roadmap to startAn IT career in business analysis or find entry-level business analyst jobs. CreateSpace.
The 10 Golden Rules of Systems Analysis (Gibson, et al., 2007)
• Rule 1: there always a client• Rule 2: your client does not understand his/her
own problem• Rule 3: the original problem statement is too
specific: you must generalize the problem to give it contextual integrity
• Rule 4: the client does not understand the concept of the index of performance
ILS
Z5
56
11
The 10 Golden Rules of Systems Analysis (Gibson, et al., 2007)
• Rule 5: you are the analyst, not the decision-maker• Rule 6: meet the time deadline and the cost budget• Rule 7: take a goal-centered approach to the problem,
not a technology-centered or chronological approach• Rule 8: nonusers must be considered in the analysis and
in the final recommendations• Rule 9: the universal computer model is a fantasy• Rule 10: the role of decision-maker in public systems is
often a confused one
ILS
Z5
56
12
Agile
• Agile – based on the 12 original principle: Agile Manifesto
ILS
Z5
56
13
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
ILS
Z5
56
14
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
ILS
Z5
56
15
Adoption
• Adopter (Rogers, 1995; 2003)
ILS
Z5
56
16
InnovatorsEarly
adoptersEarly
majorityLate
majorityLaggards
Adoption
• Adopter stage (Dormant, 1986)• Awareness• Self concern• Mental tryout• Hands on trial• Adoption
ILS
Z5
56
17
Air-car byTata Motors
Being A System Analyst
• Solve business problems• Work models• Final specification document
• Manage projects/teams• Communicate solutions to
programmers• UML
• Flow model ~= use case diagram• Sequence model ~= activity diagram• ER diagram ~= class diagram
ILS
Z5
56
18
Beyond the Organizational ‘Container’ (Winter, et al., 2014)• Organizational container, i.e., boundary• Sociotechnical work• Net-STS premises:
• 1. Work system are encapsulated within one or more, potentially overlapping STS
• 2. Work systems have interrelated, possibly complimentary, redundant, competing, or conflicting, social and technical elements that may co-exist without every being fully reconciled
ILS
Z5
56
19
Beyond the Organizational ‘Container’ (Winter, et al., 2014)• Net-STS premises:
• 3. Work systems can derive purpose, meaning, and structure from the multiple contexts
• 4. Creation and continued existence of work systems involves simultaneous support for both performance of work and ongoing negotiation of goals, values, and meaning.
• What would be your reaction if you revisited the organization 3 years from now and found out that the organization followed exactly what you had suggested in this class?
ILS
Z5
56
20
Lessons learned?• Are there any
lessons learned in this class that you’d like to share?
ILS
Z5
56
21
Evaluation
• Team member evaluation
• Course evaluation
ILS
Z5
56
22
Recommended