1. SYS2003/SYS2403: Professional Practice in Information Systems

2. SYS2403 (4 points) 4 hrs classes per week 4 hrs assignment per week Exam 60% Three assignments

3. SYS2003 (6 points) 4 hrs classes per week 8 hrs assignment per week Exam 60% Four assignments

4. Subject Administration Subject leader: Barry Atkinson E-mail barry.atkinson@sims.monash.edu.au Web page www3.sims.monash.edu.au/subjects/ sys2003.nsf

5. Subject Administration Lectures: Monday, 4-6pm Tutorials: Monday, 6-8pm No tutes in first week Course materials: Available on subject web site from next week

6. Texts (highly recommended) Judith DWYER: Communication for Business. (previously “The Business Communication Handbook”) Prentice Hall (any edition) Galvin, Prescott & Huseman: Business Communication: strategies and skills. Holt, Rinehart & Winston Copies available in library not compulsory BUT … don’t expect lectures and tutorials to give you all you need to know – this is University not school

7. The Nature of Systems: A Reminder Multiple components Integrated/inter-related components Whole greater than sum of parts People are essential components

8. Professional Practice in IS? Professional? Practice Is -On time -On budget -Happy users enough?

9. This unit Exploring the demands on the IT professional “IT professional” means all IT jobs, not just Systems Analysts Looks at the - knowledge -skills -attitudes demanded by the marketplace for IS professionals

10. This unit (cont) Increased skills (especially analytic and communications skills) Skill mix (the broad variety of skills currently required by IS professionals) Offers an opportunity to broaden your skills through study and practical tutorial work

11. Attendance Miss tutorial sessions at your peril! This unit has a practical component designed to broaden your skills, which includes group project management (which will be part of unit assessment) Take the opportunity to test your skills before your job requires them Tutorial attendance is not compulsory, nor will it be recorded – so its up to you!

12. Workload Lectures Background study Four/five assignments Group project management REQUIRES Planning Organization Consistent work practices THIS UNIT IS DESIGNED TO MAKE “NIGHT BEFORE DUE DATE” EFFORTS IMPOSSIBLE

13. People vs Machines as System Components Machines Definable limited functionality; limited adaptability Standardised operation Externally controlled/directed/driven Totally unresponsive to external stimuli; consistent performance within standard operating environment Not subject to emotions - embarrassment/hurt/anger/fear/humiliation/etc

14. People Adaptable Unique Individually controlled/directed/driven Responsive to external stimuli Inconsistent performance Subject to emotions - embarrassment/hurt/anger/fear/humiliation/etc Their input and usage and good will necessary to make machines do the job they are designed to do

15. The Problem You have been trained to lead the technical development of machine-based systems How would you cope with a technical environment where every machine was different? ….. So how will you cope with a system environment where every person involved is different? different beliefs, different experience more than you/less than you

16. Coping Strategies 1. Pretend it’s not an issue: “Computing is only about technical issues” “Working with IT is just common sense” “Everyone knows that” 2. Treat People Like Machines: “He/she/they should be able to do that” “He/she/they shouldn’t feel/think like that” “He/she/they should be able to just follow instructions” “He/she/they should do what they are told”

17. Coping Strategies (cntd) 3. Pass the Problem to Someone Else: “It’s a management/organisational issue. I’m just here to do the technical stuff” “Someone else on the development team can do that better than me” “The users will have to sort it out for themselves” “I don’t know who should do it, but it’s not my area of responsibility”

18. Issues to be Addressed Communication Negotiation/conflict resolution Ethics Professionalism WHY? Because we are designing and building systems to be used Because we can adapt the machine components of the system to better use if we want to Because we have power to harm Because we want to do the whole job, not just part

19. SYS2003/2403: Professional Practice in IS The Changing Role of the IS Professional

20. The IS Professional’s Role: Reasons for Change The increasing capabilities of technology The increasing spread and accessibility of technology The increasing business reliance on technology The increasing expectations of technology The changing patterns in development practice The increasing globalization of business environment

21. Some Roles for IS Professionals: The Technician Responsibilities Buying and installing the technology Making the technology work Supporting the users Audiences Other technicians Other technical professionals Equipment vendors Users

22. Some Roles for IS Professionals: The Programmer Responsibilities Developing code which meets functional specifications Making the code maintainable, supportable, etc Customising packages or systems to meet specifications or changed circumstances Audiences Other programmers Other technical professionals Users

23. Some Roles for IS Professionals: The Analyst Responsibilities Determining system needs Negotiating with system users and operators Liaising with suppliers of packaged systems Preparing system specifications Audiences Other analysts Programmers and other technical professionals Operators and users of the system Vendors of packaged systems

24. Some Roles for IS Professionals: The Business Systems Analyst Responsibilities Identifying opportunities for improving business operations Monitoring industry trends in business practice Preparing the ‘business case’ for system development or change Preparing system specifications Audiences Business and industry experts Managers Equipment vendors Technical professionals of all kinds

25. Some Roles for IS Professionals: The Team or Project Leader Responsibilities Planning and organising the project Liaising with all parties involved Monitoring, controlling and reporting on progress Taking or advising on remedial action Audiences Senior business managers Equipment and package vendors Consultants and contractors Technical professionals and Users Etc etc etc - everyone!

26. Roles for IS Professionals: Specialisation and Multi-skilling Broad categories do not cover the extent of the roles required Roles and work responsibilities often cannot be ‘pigeon-holed’; multi-skilling is often needed Degree of specialisation and multi-skilling needed depends on organisation and project team structures Range and type of skills required has changed dramatically over the years and is continuing to change rapidly

27. The IS Professional’s Role: What Next? Consider some recent trends and developments: - the power of desktop machines - the capabilities of packaged software - the development of the Internet and Web - the pressure for increased business efficiency - the growth of e-commerce - the trend to inter-organisational systems and globalisation - the popularity of outsourcing Predictions anyone?

28. The IS Professional’s Role: Implications for Communication Different types of communication relevant to different roles Different audiences who must be effectively communicated with The need for an extensive variety of tools, ‘technologies’ and techniques for communication written oral and wordless