Exam Information: * Worth 60% of final mark (There will be a general discussion question on architecture!!) * Consists of two 30 mark questions and one 40 mark question * When listing techniques, make sure you know all the disadvantages and advantages for them, and when to use them (e.g. requirements gathering, requirements and stakeholder analysis) * Apply study material to real life scenarios, AND INCLUDE EXAMPLES * Main topics that will be covered: Weeks 2, 3, 8, 9, 10
Week 2 Notes – Projects and Stakeholder management * A system analyst creates value for a business and is required to have the following skills: * Technical knowledge e.g. cost-benefit analysts * Business knowledge e.g. organisational structure and business concerns * Analytical skills * Interpersonal/people skills e.g. listening empathetically, adapting systems to users * and ethical skills e.g. privacy and sensitive information * A system analyst can act as a “change agent” who identifies the improvements needed, designs systems to implement those changes and trains/motivates others to use these systems * Projects are driven by business needs to create value (tangible or intangible e.g. improved customer service) * Ways in which IS can add value: * Reduced costs * Improved services * Better performance * Support for new products and services * More information provided * Stronger controls * The success of projects is measured with cost, scheduling and performance/functionality * Manage your project through milestones * The term “business case” refers to the reasons/justification for a new proposal (feasibility)
* Stakeholders are people who can affect or are affected by the system and can make or break your business * Get stakeholders on your side e.g. bring everyone together (meetings) and co-create * Tools for stakeholder