Systems Requirements and User Experience Lecture Overview
Explore the key aspects of systems requirements and user experience in the SRUX course. Learn about user profiles, stakeholder priorities, system requirements, human-centered design process, and more. Enhance your understanding of IT fundamentals for a successful career in the field.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
INFS 1026 Systems Requirements and User Experience - SRUX Lecture 1: Introduction and The Role of Requirements
2 Course Introduction
3 Who? Mrs Michelle Davy Please call me Michelle Course Coordinator Lecturer Michelle.davy@navitas.com Calendly link https://calendly.com/michelle-davy/30min Availability Tuesday Friday after class Other times email for an appointment
4 Systems Requirements and User Experience - SRUX Learning Objectives 1. Given a problem statement, identify the key aspects of the users to construct user profiles and assemble the requirements based on stakeholder priorities 2. Describe the system requirements following appropriate standards 3. Select requirements to construct the use cases 4. Explain a human centred design process 5. Apply a human centred design process to document a user interface
5 Associated courses SRS mandatory co-requisite unless approved If you are not enrolled in both, please speak to me after class IT Fundamentals pre-requisite Design Thinking Studio beneficial Links to programming and database courses Understanding systems requirements is vital to working in any area of IT All projects need to be analysed to understand requirements
6 Student Expectations To pass SRUX Although there is no exam for this course You are assessed on your understanding during the semester Further consolidation in SRS except User Experience theory When you transition to UniSA, understanding is expected Future courses may be difficult without the basic understanding of systems requirements
7 Student Expectations To pass SRUX Individual Learning Attend all classes Complete learning tasks and assessments for every module on time Complete tasks missed due to illness or late enrolment Expect to spend four hours outside of class time Collaborative Learning Work in teams during class to complete tutorial tasks Help others in your team
8 Student Expectations To pass SRUX Ask questions No such thing as a stupid question All questions are valid If you don t understand the first time the answer is given, ask for further details 2. Make sure you follow feedback If a change has been suggested when you submit a draft, please change the content before submitting If assignment feedback identifies how to fix a problem, please follow the instructions If not sure, go to 1 1. a) b) c) a) b) c)
9 Assessments Assessment Learning Outcome 1, 3, 4 Weight Due Date Continuous Assessment Assignment 1 20% Most weeks 2, 3 40% Monday, Week 6, 11:59pm Monday Week 13, 11:59pm Assignment 2 1, 4, 5 40% Extensions are not automatically approved
10 SRUX Website - Communication Class connection Lecturer announcements high visibility Class Discussion Ask questions about the course / assessments Responses from myself or other students Interactive timeline Summary of what the week holds and any assessment due
11 SRUX Website Information Module Information Booklet Information -> Essential Subject Information Information about the course, schedule, due dates Essential readings and resources Resources used throughout the semester Staff contact details and availability Email and Calendly link Student Learning Support Unit Glossary and useful links
12 SRUX Website eResources Textbook referred to in lectures Link to Essential readings and resources Design Collaboration Tools Figma.com Draw.io Assessments Summary Tile for each assessment group
13 SRUX Website Live sessions Zoom link and recordings Select the class link to access past recordings for the semester Welcome Course information Getting to know you task
14 SRUX Website Weekly Resources Weekly resources Prepare My Preparation Topic overview Learning Outcomes for the week Preparation tasks please prepare Reading Readings and link to lecture notes pdf for viewing on any device ppt for viewing in PowerPoint
15 SRUX Website Weekly resources Engage Face to Face My Face to Face requirements Overall schedule Lecture topic and tutorial summary My Lecture Further link to lecture notes Readings or videos My Tutorial Tutorial tasks Links to resources and activities
16 SRUX Website Weekly resources Reflect and Progress My reminders Links to tasks to complete before the next week Weekly review
17 Activity 20 minutes will be allocated to this task Go to My Tutorial Select the lesson titled Where is it? Complete the lesson. Everything has been discussed so far in this session Completion of the activity will contribute to CA1 This activity requires close attention to detail and following instructions Once I see that everyone has completed the activity we will have a break
Terminology Reading: Valacich & George 2016, Chapter 1, pp. 26-30
19 Agenda Background terminology Evolution of Systems Evolution of Systems development Current common systems
20 Terminology System Accept inputs, processed to outputs, used as feedback to change inputs or processes as needed Air conditioning Input air, process of cooling or heating, output processed air, thermostat reads current air temperature (feedback) and changes the processes to keep the temperature in the required range Valacich & George 2016
21 Terminology Information System Generally software built for a purpose May be multiple systems interacting together Share database, web interface Student management system Learning management system Enrolment system Valacich & George 2016
22 Terminology Systems analyst Determine how people, methods and information technology can best be combined to bring about improvements in the organisation (Valacich & George 2016, p. 29) Communication bridge between users and developers Transaction Exchange of items, money or conversation Details of electronic transactions stored and used later to create reports Sales, orders, payments Enrolment, assignment submission Valacich & George 2016
23 Terminology Data and Information Data are raw facts, words, numbers, records stored about a transaction Associate with contents a database eg Student ID, student details Information is processed data such as a report Data organised to make sense and assist with decision making Combine with understanding to create knowledge Demonstrate wisdom when we use knowledge at the right time, under the right circumstances and in the right way Valacich & George 2016
24 History of Systems Development
25 Systems Development Initially thought of as an art, now a science Became structured Understood importance of Good planning Good project management Good documentation Achieved by using systems development methodology A standard process to conduct all the steps necessary to develop and maintain information systems
26 Traditional Systems Development Initially used Systems Development Life Cycle (S D L C) Phases of planning, analysis, design, implementation and maintenance Traditional waterfall model Difficult and costly to go back for changes, often had to wait until the next release Role of system users or customers only narrowly defined if at all Focus on milestones instead of quality Change is inevitable but expensive Modified SDLC Some overlap between phases to allow change Valacich & George 2016
27 SDLC Limitations and Agile Transition to agile methodologies Argument that software development methodologies adapted from engineering generally do not fit with real world software development Agile methodologies require constant user involvement and welcome change The Agile Manifesto / Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Valacich & George 2016
28 Agile Methodology Agile development success dependant on staff attitude Not everyone embraces agile -> project failure Example agile methodology - Scrum UX occurs in Sprint 0 Determine what elements to change Plan for 30 day Sprint Daily scrum Progress discussed and blockages removed Retro / reflection at end of sprint Ideas for experiments
29 Agile Methodology Example: Scrum Stages Requirements Design Implementation Testing Deployment Review Valacich & George 2016
30 Systems Evolution Traditional file based systems Computerised filing cabinets Data not always shared Transition to database systems Current systems Implementation involving three-tier design Database on one server Application on second server Client logic located on user machines Valacich & George 2016
31 Systems Evolution Wireless system components Off the shelf and customisable systems Move from in-house development to cloud systems Save money in development and maintenance Benefit for small to medium business for common systems - Accounting, sales Move towards improved user involvement through consideration of user experience Valacich & George 2016
32 Systems Evolution Developing systems for the Internet, firm s intranets and extranets What Who What Internet Anyone Search / browse, ask questions / chat Intranet Employees Company private network Extranet Access to an intranet by outsiders order, sale Example SAIBT Website Lecturer update course website Student access course materials, enrolments, submit assignments Perform business transactions Valacich & George 2016
Requirements Definition and User Experience Reading: Hartson & Pyla 2019, Chapter 1, pp. 3 - 25
35 User Experience The components of UX (Hartson & Pyla 2019, p. 9) Hartson & Pyla 2019
36 User Experience Components of UX Usability Primary importance of UX but often forgotten Easy to use Efficiency and effectiveness Error avoidance Learnability and retainability Usefulness Ability to get the job done Reason for a product or system Hartson & Pyla 2019
37 User Experience Components of UX Emotional impact How the user feels emotionally when using the product or system Includes user satisfaction, affinity / identifying with the product Users now seek pleasure in product use and aesthetics in product design. (Hartson & Pyla 2019, p. 11) Meaningfulness Meaningfulness comes out of a personal relationship of the product with its human user that endures over time (Hartson & Pyla 2019, p. 16) Consider attachment people can have to a smartphone Hartson & Pyla 2019
38 User-Centred Systems Development Vital to have continual user involvement throughout the system development to enable the best user experience Traditional challenges IT staff belief - users don t know what they want I will know what I want when I see it Users challenged by explaining what they want Result Assumption instead of consultation -> failure When you assume you make an ass out of u and me Example of what can occur if people assume they understand what is being asked of them Hartson & Pyla 2019
39 User-Centred Systems Development Alternative Validate assumptions ASAP - Do you mean . Ask guiding questions Provide visual cues / demonstrations of options Why? User = expert of system functionality Give the user what they want, not what the analyst thinks they want Example: UX: Infinite Scrolling vs. Pagination (Babich 2016) - Choice depends on the function of the system no right or wrong Hartson & Pyla 2019
40 Lean UX Bringing agile development to align with UX According to Kaley (2022) Waterfall: Phases of work flowing in sequence toward project completion Agile: Collaboration and embracing change are more important than following a plan Lean: Maximizing user value through continuous experimentation and removing waste
41 Lean UX Applies agile development values to product design Individuals and interactions over processes and tools Whole team work together to generate ideas from different perspectives Encourage idea exchange debate and decisions to be made quickly Involve stakeholders at every stage of development Working software over comprehensive documentation Big challenge of predicting what will work The speed of delivery of a working system enables evaluation of the most viable solution for the requesting market not always possible during earlier stages of development
42 Lean UX Applies agile development values to product design Customer collaboration over contract negotiation Collaboration creates alignment more effectively than written communication, argument, and elaborate defense. (Gothelf & Seiden 2016, p. 9). Responding to change over following a plan Continuous adjustment of designs based on feedback from the market
43 Next Week Look in more detail at the steps taken with Lean UX Discovery stage discussion
44 References Babich, N 2016, UX: Infinite scrolling vs pagination, UX Planet, viewed 15 June 2021, <https://uxplanet.org/ux-infinite-scrolling-vs-pagination- 1030d29376f1>. Darnit, J 2017, Exact instructions challenge: This is why my kids hate me, video, Youtube, January 27, 3 March 2021, <https://www.youtube.com/watch?v=cDA3_5982h8>. Gothelf, J & Seiden, J 2016, Lean UX: Designing great products with agile teams, O Reilly Media Inc., California USA, ProQuest Ebook Central. Hartson, R & Pyla, P 2019, The UX book: Agile UX design for a quality user experience, 2nd edn, Elsevier Inc, Cambridge, MA, Science Direct. Kaley, A 2022, Lean UX & Agile: Study Guide, Nielsen Normal Group, viewed 7 June 2022, <https://www.nngroup.com/articles/lean-ux-agile-study- guide/>. Norman, D & Nielsen, J 1998, The definition of user experience (UX), Nielsen Normal Group, viewed 15 June 2021, <https://www.nngroup.com/articles/definition-user-experience/>. Valacich, JS & George, JF 2016, Modern systems analysis and design, Global edition, 8th edn, Pearson Education Ltd.
