SOFENG-Reviewer (1).pdf

SOFENG- REVIEWER SOFTWARE PROCESS MODELS - are frameworks for organizing software MODULE 1 development. They define stages, activities, and...

SOFENG- REVIEWER SOFTWARE PROCESS MODELS - are frameworks for organizing software MODULE 1 development. They define stages, activities, and SOFTWARE ENGINEERING: PRINCIPLES AND workflow of software projects PRACTICES The Waterfall Model - Linear sequential SOFTWARE DEVELOPMENT - is the process of approach to software development designing, coding, testing, and maintaining software Consists of distinct phases: requirements, design, implementation, It involves multiple stages and requires testing, maintenance various skills Each phase must be completed before Professional goes beyond just writing the next begins code Software Engineering - is the application of Agile Methodologies - Emphasizes flexibility, engineering principles to software development collaboration, and rapid delivery involves systematic, disciplined, and sprints: Iterative approach with short quantifiable approaches development cycles Aims to create high-quality, reliable, and Focuses on customer feedback and maintainable software adapting to changing requirements Software Engineering Code of Ethics Scrum: An Agile Framework Developed by ACM and IEEE-CS Popular agile framework for managing Emphasizes public interest, client and complex projects employer interests, product quality, and Involves roles like Scrum Master, professional behavior Product Owner, and Development Key Principles of the Software Engineering Team. Uses sprints, daily stand-ups, Code of Ethics and sprint reviews 1. Public - engineers shall act consistently Other Software Process Models with the public interest. To ensure that software does not harm the public or the Spiral Model: Risk-driven approach with environment. multiple iterations 2. Client and Employer - Engineers shall V-Model: Testing is parallel to development act in a manner that is in the best interest stages of their client and employer, consistent Incremental Model: System is developed in with the public interest increments 3. Product - Engineers shall ensure that CORE PROCESS ACTIVITIES their products meet the highest professional standards possible. Requirements Engineering 4. Judgment - Engineers shall maintain integrity and independence in their Process of defining, documenting, and professional judgment. maintaining requirements 5. Management - Managers and leaders Involves elicitation, analysis, shall promote an ethical approach to the specification, and validation management of software development Critical for ensuring the software meets and maintenance. user needs and expectations 6. Profession - Engineers shall advance the integrity and reputation of the profession consistent with the public interest. Design and Implementation 7. Colleagues - Engineers shall be fair and Design: Creating a blueprint for the software supportive of their colleagues. system 8. Self - Engineers shall participate in Implementation: Writing code based on the lifelong learning and promote an ethical design approach to the practice of the profession. Testing and Debugging Testing: Verifying that the software works as expected MODULE 2 Debugging: Identifying and fixing errors in the code SOFTWARE PRODUCT DESIGN: CRAFTING Involves various levels: unit testing, integration USER-CENTERED SOLUTIONS testing, system testing INTRODUCTION TO SOFTWARE PRODUCT Deployment and Maintenance DESIGN Deployment: Releasing the software to users Software Product Design: Maintenance: Updating and improving the Conceptualizing, defining, and planning software post-release software solutions Involves bug fixes, feature updates, and Focuses on solving specific user performance improvements problems Blends UX design, interaction design, and Coping with Change in Software Development software engineering Change is inevitable in software Aims to meet user needs and business development objectives Can be due to evolving requirements, The Importance of User-Centered Design technology updates, or bug discoveries Requires flexible processes and robust Places users at the heart of the design change management process Ensures products are intuitive and meet Version Control Systems real needs Requires tools for managing changes to Increases user satisfaction and adoption source code over time rates Examples include Git, Subversion, and Reduces development costs by Mercurial addressing issues early Allows tracking changes, reverting to Problem Definition: The Foundation previous versions, and collaborative work Clearly articulate the problem the Continuous Integration and Continuous software will solve Deployment (CI/CD) Identify target users and their pain points CI: Regularly merging code changes into Define success criteria and goals a central repository Create a problem statement to guide the CD: Automatically deploying code design process changes to production User Research: Understanding Your Audience Helps detect issues early and speeds up software delivery Conduct interviews, surveys, and observations Embracing Change: Adaptive Software Create user personas and empathy maps Development Analyze user behavior and preferences Focus on quick responses to changing Identify user needs, goals, and requirements frustrations Emphasizes collaboration, learning, and Prototyping: Bringing Ideas to Life continuous improvement Involves short, iterative development Create low-fidelity sketches and cycles wireframes Develop interactive prototypes Future Trends in Software Engineering Test and validate design concepts Increasing use of AI and machine learning Iterate based on user feedback in software development Interaction Design: Crafting User Experiences Growth of low-code and no-code platforms Design user flows and navigation patterns Emphasis on DevOps and cloud-native Create intuitive interactions and gestures development Ensure consistency across the product  Consider accessibility and usability Follow WCAG guidelines for accessibility standards Responsive Design: Adapting to Different User Interface (UI) Design: The Visual Layer Devices Develop a coherent visual style and Design for multiple screen sizes and branding orientations Choose appropriate color schemes and Ensure consistent experiences across typography devices Design icons, buttons, and other UI Optimize layouts for desktop, tablet, and elements mobile Ensure visual hierarchy and readability Design Systems: Ensuring Consistency Information Architecture: Organizing Content Create reusable design components and Structure and categorize information patterns logically Establish design guidelines and Design navigation systems and menus principles Create sitemaps and content hierarchies Ensure visual and functional consistency Ensure users can find information easily Improve efficiency in design and development processes Technical Feasibility: Bridging Design and Development Collaboration in Software Product Design Collaborate with developers to assess Foster communication between technical constraints designers, developers, and stakeholders Consider performance implications of Use collaborative design tools and design decisions version control Ensure designs can be implemented Conduct design reviews and critiques efficiently Align design decisions with business Balance ideal user experience with goals technical realities Measuring Design Success The Iterative Design Process Define key performance indicators (KPIs) Embrace continuous improvement and Analyze user engagement and refinement satisfaction metrics Gather user feedback at each stage Conduct A/B testing to compare design Conduct usability testing and analyze variations results Use analytics to inform future design Make data-driven design decisions decisions Emerging Trends in Software Product Design Artificial Intelligence and Machine Learning integration User Testing: Validating Design Decisions Voice User Interfaces (VUI) and conversational design Conduct usability tests with target users Augmented and Virtual Reality Observe user behavior and gather experiences feedback Personalization and adaptive interfaces Identify pain points and areas for improvement Iterate on designs based on test results Ethical Considerations in Software Design Consider privacy and data protection Accessibility in Software Product Design Design for inclusivity and diversity Design for users with diverse abilities Avoid dark patterns and manipulative Implement keyboard navigation and design screen reader support Promote transparency and user trust Ensure sufficient color contrast and text Career Paths in Software Product Design sizing  UX Designer Group users based on shared Product Designer attributes Interaction Designer Consider demographics, behaviors, or UI Designer needs Information Architect Look for patterns in your assumptions Create distinct user groups Step 4: Visualize the Proto-Persona MODULE 3 Create visual representation for each INTRODUCTION TO PROTO-PERSONAS: proto-persona ACCELERATING USER-CENTERED DESIGN Include key details like goals, Proto-Personas - Quick, assumption-based frustrations, characteristics representations of users Use a consistent format for all proto- personas Created early in the design process Make it visually engaging and easy to Built on internal assumptions and team understand knowledge Visualize users without in-depth research Benefits of Proto-Personas Ideal for fast-paced, agile environments Facilitate early design concepts Why Use Proto-Personas? Gain alignment among team members Provide a shared understanding of Ensures team shares common potential users understanding of potential users Enable quick decision-making in early Serves as a starting point for design stages decisions Foster user-centered thinking from the Allows for immediate design work based start on internal knowledge Keeps product user-focused even at Use Case: Testing Early Design concept stage Concepts Useful when full research isn't feasible Use proto-personas to inform due to time constraints preliminary designs Proto-Personas vs. Full Personas Address assumed user needs in initial concepts Proto-personas: Quick, assumption- Quickly iterate on design ideas based and evolve over time Align design decisions with user goals Full personas: In-depth, research-based Both aim to represent user needs and behaviors Use Case: Gaining Team Alignment Step 1: Identify User Assumptions Offer shared understanding of potential users Gather assumptions from team Align different team perspectives members and stakeholders Create a common target for design Consider users' behaviors, needs, and efforts goals Facilitate communication about user Leverage unique insights from each needs team member Be open to diverse perspectives Step 2: List Hypotheses Formulate hypotheses about users' Limitations of Proto-Personas motivations Built on assumptions, not data-driven Consider potential pain points insights Base on team's beliefs about users Can lead to inaccurate designs if not Remember this need validation later validated Step 3: Segment Users May reinforce existing biases Not a substitute for real user research The Importance of Validation Evolve design strategy based on validated insights User research must confirm or adjust assumptions Best Practices for Proto-Personas Validation turns proto-personas into Involve diverse team members in creation actionable insights Keep them visible and referenced often Helps avoid designing for the wrong user Update regularly with new insights needs Use them to generate empathy, not Essential for creating truly user-centered stereotypes designs Conclusion: The Value of Proto-Personas Iterating Proto-Personas Efficient way to make user assumptions Evolve proto-personas as user research is actionable conducted Bridge gap between no user insight and Update assumptions based on real data full research Continually refine understanding of users Foster user-centered thinking from Transform proto-personas into validated project start personas over time Remember: always validate with real user When to Use Proto-Personas data Early stages of product development Rapid prototyping phases MODULE 4 When time or resources limit full user research CUSTOMER RESEARCH AND JOURNEY To kickstart user-centered thinking in a MAPPING: UNDERSTANDING YOUR project AUDIENCE Creating Effective Proto-Personas Customer Research - Systematic gathering of data about customers and their preferences Keep them simple and focused Include only essential information Essential for informed business decisions Make them easily shareable within the and strategy team Helps understand customer needs, Ensure they're adaptable as new behaviors, and pain points information emerges Why is Customer Research Important? Proto-Personas in Agile UX Design Drives product development and Fit well with iterative development improvement processes Enhances customer satisfaction and Allow for quick starts in sprint planning loyalty Provide a user focus for each Informs marketing strategies and development cycle messaging Can be updated with each sprint Gives businesses a competitive edge Balancing Assumptions and Research Use proto-personas to guide initial design Plan for user research from the beginning Be prepared to challenge and change Types of Customer Research: Qualitative assumptions View proto-personas as starting points, Focus groups: Small group discussions not end results In-depth interviews: One-on-one conversations From Proto-Personas to Full Personas Ethnography: Observing customers in Gradually incorporate real user data their natural environment Refine proto-personas with each Surveys: Structured questionnaires research cycle Analytics: Data from website visits, Identify gaps between assumptions and purchases, etc. reality  Large-scale data collection for statistical Visual representation of a customer's analysis experience with a brand Shows interactions, emotions, and pain Surveys and Questionnaires - Can be points over time conducted online or offline Essential tool for understanding and Use open-ended or closed-ended improving customer experience questions Stages in the Customer Journey Gather large amounts of data efficiently Awareness: Customer becomes aware of Interviews: Diving Deeper a need or problem One-on-one conversations for in- Consideration: Customer researches depth insights potential solutions Can be conducted in person, by Purchase: Customer decides to buy phone, or video call Retention: Customer uses the Allow for follow-up questions and product/service clarifications Advocacy: Customer recommends to Focus Groups: Dynamic Feedback others Components of a Customer Journey Map Small group discussions led by a moderator Stages: Different phases of the Generate ideas through group customer's experience interaction Touchpoints: Where customers interact Observe group dynamics and with the brand consensus formation Emotions: How customers feel at each Observation and Ethnography stage Pain points: Frustrations or obstacles in Study customer behavior in real-life the journey settings Creating Customer Personas Gain insights into subconscious behaviors and habits Fictional characters representing Useful for understanding context of different customer types product/service use Based on research and data about real Analyzing Customer Data customers Include demographics, behaviors, goals, Segment data by demographics, and pain points psychographics, etc. Mapping Customer Actions and Touchpoints Identify patterns and trends in customer behavior Identify what customers do at each stage Create customer personas based on of their journey insights Determine where and how customers Benefits of Customer Research interact with the brand Include both online and offline Informed decision-making for product touchpoints development Improved customer experience and satisfaction Better targeting in marketing efforts Increased customer loyalty and retention Analyzing Emotions and Pain Points Challenges in Customer Research Plot how customers feel at each stage of Time and cost constraints their journey Potential for response bias Identify frustrations, obstacles, or Ethical considerations (e.g., privacy) negative experiences Rapidly changing customer preferences Look for opportunities to improve the Introduction to Customer Journey Maps customer experience Benefits of Customer Journey Mapping Synthesizing insights from empathy phase Identifies gaps and opportunities in the Creating problem statements focused customer experience on user needs Enhances customer engagement and Defining the challenge to be solved loyalty Improves product and service design Ideation: Generating Creative Solutions Aligns teams around customer-centric Brainstorming multiple ideas goals Encouraging out-of-the-box thinking Challenges in Journey Mapping Using various ideation techniques Complexity in mapping diverse customer Prototyping: Bringing Ideas to Life journeys Creating low-fidelity prototypes Keeping journey maps up-to-date as (mock-ups, models) preferences change Rapid visualization of concepts Incorporating omnichannel touchpoints Iterative testing of ideas Translating insights into actionable improvements Testing: Gathering User Feedback The Future of Customer Research and Journey Presenting prototypes to users Mapping Observing user interactions Collecting and analyzing feedback Integration of AI and machine learning for real-time insights Benefits of Design Thinking Increased focus on personalization and Enhances creativity and innovation individual journeys Improves user experience and Greater emphasis on emotional and satisfaction experiential factors Reduces risks through early testing Challenges in Implementing Design Thinking MODULE 5 Resistance to change within DESIGN THINKING AND LEAN UX: organizations INNOVATING WITH USER-CENTERED Requires a mindset shift toward APPROACHES experimentation Design Thinking - Human-centered approach to Time and resource allocation for iterative problem-solving processes Focuses on understanding user needs Introduction to Lean UX and Lean Startup and challenges Methodologies focused on minimizing Iterative process of ideation, prototyping, waste and testing Emphasis on experimentation and Key Principles of Design Thinking feedback Goal: Build successful products quickly Empathy: Understanding users' needs and efficiently and motivations Collaboration: Cross-disciplinary Lean Startup: Key Principles teamwork Build-Measure-Learn Cycle Iteration: Continuous improvement Validated Learning: Testing hypotheses through feedback Minimum Viable Product (MVP) Empathy in Design Thinking Pivot or Persevere decision-making Conducting user research (interviews, Benefits of Lean Startup observations) Reduces time and cost of product Developing empathy maps and personas development Gaining insights into user behavior Focuses on meeting customer needs Provides faster time-to-market Define Phase: Framing the Problem Lean UX: Overview  Design process adapted from Lean Potential for AI and data-driven design Startup processes Focuses on user feedback and iterative testing MODULE 6 Emphasizes cross-functional collaboration INTRODUCTION TO FLOWCHARTS Key Concepts in Lean UX flowchart a visual representation of a process or system that uses standardized symbols and Cross-functional Collaboration shapes to illustrate the steps and decisions MVP Design: Core features only involved in that process. Continuous Feedback loops Rapid Prototyping and Testing tool for depicting processes in a clear and easily understandable manner, Steps in Lean UX Process Flowchart Purposes Hypothesis Creation: Defining assumptions 1. Process Documentation: provide a structured and visual way to document Rapid Prototyping: Building quick, low- the steps, making it easier for individuals fidelity prototypes to understand and follow the process. Continuous Testing: Collecting user 2. Analysis and Optimization: help identify feedback inefficiencies, bottlenecks, or Iterate and Improve: Refining based on redundancies within a process. lead to insights process improvements to make it more Benefits of Lean UX efficient and effective. 3. Communication: effective way to convey Accelerates the design process complex processes to others. used to Focuses on delivering value early and communicate procedures, policies, and often workflows to team members Reduces risks of unusable features 4. Problem-Solving: tools for Challenges in Implementing Lean UX troubleshooting and problem-solving. help pinpoint the source of issues or Requires shift from traditional design errors within a process processes 5. Decision-Making: to represent decision Demands close collaboration across trees and alternative paths within a teams process. assist in making decisions Needs consistent user feedback 6. Standardization: establish and maintain Comparing Lean UX and Traditional UX standardized procedures, ensuring that processes are followed consistently. Traditional UX: Detailed documentation, 7. Training and Onboarding: used as in-depth research training materials for teaching new Lean UX: Iterative, lightweight, quick user employees the steps involved in a validation particular process Lean UX emphasizes speed and early 8. Quality Control: In quality management feedback and manufacturing, flowcharts are used Integrating Design Thinking and Lean UX to outline quality control procedures and standards. Both emphasize user-centered approach 9. Software Development: play a critical Design Thinking can inform initial product role in software engineering to visualize vision algorithms and program logic. help in the Lean UX helps in rapid implementation design and development applications. and validation 10. Project Management: used in project Future of User-Centered Design management to define and illustrate project workflows, timelines, and Increasing focus on user needs and dependencies. experiences Growing importance of rapid iteration and BASIC SYMBOLS USED IN FLOWCHART feedback DESIGNS Terminals are represented by an oval symbol order and logical progression to understand the that indicates the start or end of a process or chart' s structure. flowchart, providing clear entry and exit points. Rules For Creating Flowchart: Input/Output depicted as a parallelogram A flowchart is a graphical representation of an symbol used to represent the interaction algorithm. between a process or system and external entities, such as users, data sources, or other Rule 1: Flowchart opening statement systems. must be ‘start’ keyword. Rule 2: Flowchart ending statement must be ‘end’ keyword. Rule 3: All symbols in the flowchart must be connected with an arrow line. Rule 4: The decision symbol in the The Processing represented as a rectangle. flowchart is associated with the arrow these represents a specific action, task, or line. operation within a process. used to depict a step where data is manipulated, calculations are performed. Decision symbol referred to as a diamond symbol, process where a decision or choice needs to be made. Decision based operations such as yes/no question or true/false. Connector symbol represented by a circle symbol, connects flowchart elements, What is the primary purpose of the Rational indicating process sequence and visual links, Decision-Making Model? * rather than representing specific actions or  To brainstorm ideas visually decisions.  To provide a systematic, logical approach to decision-making  To identify root causes of problems  To evaluate a product's market position What does the 'Product' principle in the Software Engineering Code of Ethics emphasize? Flow lines represented by arrows represent the  Maximizing profits and reducing direction is design to connect symbols and development costs. shapes, illustrating the process's sequential  Meeting the highest professional standards possible   Satisfying only the client's immediate Which of the following is NOT a key principle in needs. the Software Engineering Code of * Ethics?  Following the latest technology trends in  Public interest software development.  Client and employer interests What is the primary purpose of using proto-  Product quality personas in the design process? *  Maximizing code complexity  To replace full user research What is the primary advantage of using the  To accelerate user-centered design Phoenix Checklist? *  To eliminate the need for stakeholder  It's based on visual representations input  It's ideal for remote teams  To finalize product features  It's a question-based CIA method What are proto-personas? *  It focuses on user empathy  Detailed representations of users based Which of the following is NOT a key principle in on extensive research the Software Engineering Code of * Ethics?  Quick, assumption-based  Public interest representations of users  Client and employer interests  Visualizations of user behaviors and  Product quality needs  Maximizing code complexity  In depth analysis of user demographics What is software engineering? * What is a key characteristic of the Incremental Model in software development? *  The design and development of computer hardware.  The system is developed in one large  A set of tools and programming increment languages used to create software.  There is no testing phase  The application of engineering principles  The system is developed in small, to software development. manageable increments  The process of coding and debugging  It follows a strictly linear approach software. What is the recommended approach for What is a potential risk of relying too heavily on balancing assumptions and research when proto-personas without validation? using proto-personas?  Wasting time by collecting too much user  Rely solely on proto-personas throughout data before design begins the project  Ensuring the final product is too flexible  Ignore research that contradicts initial and customizable. assumptions  Reinforcing existing biases and designing  To guide initial design while planning for for the wrong user needs user research  Focusing too much on long-term user  Conduct full user research before behavior rather than immediate needs. creating any proto-personas What is the main focus of Root Cause Analysis? Which of the following is NOT a step in the Design Thinking process? *  Addressing symptoms of problems  Identifying underlying causes  Empathize  Prioritizing tasks  Define  Evaluating market position  Implement  Prototype What are the key principles of the Software Engineering Code of Ethics? * What is the primary advantage of using the Phoenix Checklist? *  Public, Client and Employer, Product, Judgment, Management, Profession,  It's based on visual representations Colleagues, Self  It's ideal for remote teams  Design, Implementation, Testing,  It's a question-based CIA method Maintenance  It focuses on user empathy  Waterfall, Agile, Spiral, Incremental   Requirements Engineering, Design and  They are only used in the final sprint Implementation, Testing and Debugging, What is the purpose of Continuous Integration Deployment and Maintenance and Continuous Deployment (CI/CD)? Which of the following best describes the  Regularly merging code changes into a relationship between problem-solving and central repository decision-making in software product design? *  Automatically deploying code changes to  They are completely separate processes production  Problem-solving always precedes  Detecting issues early and speeding up decision-making software delivery  They often overlap and work together  All of the above  Decision-making is a subset of problem- In the context of software product design, what solving is the main purpose of problem- solving What is the Software Engineering Code of frameworks? Ethics? *  To choose between multiple viable  A set of guidelines for professional alternatives conduct in software engineering  To tackle complex problems  A document that outlines the stages of systematically software development  To evaluate a product's market position  A framework for organizing software  To prioritize tasks based on urgency projects Which framework is particularly useful for  A code that defines the principles of assessing a product's position in the market? software engineering  RICE Matrix What is the primary focus of the Design Thinking  Pareto Analysis framework? *  SWOT Analysis  Identifying root causes  Fishbone Diagram  Emphasizing empathy for users What is the primary benefit of using Mind  Prioritizing tasks based on urgency Mapping in problem-solving? *  Evaluating options based on reach and impact  It helps in identifying root causes  It facilitates visual brainstorming and idea How do proto-personas differ from full organization personas? *  It prioritizes tasks based on urgency o Proto-personas are based on extensive  It evaluates options based on reach and user research, while full personas are impact assumption-based o Proto-personas are quick, assumption- based representations, while full What is the primary goal of software personas are in-depth, research-based maintenance? * o Proto-personas are visualizations of user  To monitor user activities and ensure behaviors, while full personas focus on compliance with terms of service user demographics  To update and improve the software post- What is a key limitation of proto-personas? release  To prevent and correct errors in the  They take too long to create software  They are built on assumptions, not data-  To add new features without changing the driven insights original code  They provide too much detail about users  They can't be used in agile environments Which of the following is NOT a core process activity in software engineering as mentioned in How do proto-personas fit into agile UX design? the presentation?  They slow down the sprint process  Requirements Engineering  They provide a user focus for each  Design and Implementation development cycle  Marketing and Sales  They replace the need for user stories  Testing and Debugging  o Conduct full user research before creating any proto-personas What is the primary purpose of the Rational Decision-Making Model? * Which of the following is NOT a step in the Design Thinking process? * o To brainstorm ideas visually o To provide a systematic, logical approach o Empathize to decision-making o Define o To identify root causes of problems o Implement o To evaluate a product's market position o Prototype What does the 'Product' principle in the Software What is the primary advantage of using the Engineering Code of Ethics emphasize? Phoenix Checklist? * o Maximizing profits and reducing o It's based on visual representations development costs. o It's ideal for remote teams o Meeting the highest professional o It's a question-based CIA method standards possible o It focuses on user empathy o Satisfying only the client's immediate Which of the following is NOT a key principle in needs. the Software Engineering Code of * Ethics? o Following the latest technology trends in software development. o Public interest o Client and employer interests What is the primary purpose of using proto- o Product quality personas in the design process? * o Maximizing code complexity o To replace full user research What is the primary advantage of using the o To accelerate user-centered design Phoenix Checklist? * o To eliminate the need for stakeholder input o It's based on visual representations o To finalize product features o It's ideal for remote teams o It's a question-based CIA method What are proto-personas? * o It focuses on user empathy o Detailed representations of users based Which of the following is NOT a key principle in on extensive research the Software Engineering Code of * Ethics? o Quick, assumption-based representations of users o Public interest o Visualizations of user behaviors and o Client and employer interests needs o Product quality o In depth analysis of user demographics o Maximizing code complexity What is a key characteristic of the Incremental What is software engineering? * Model in software development? * o The design and development of computer o The system is developed in one large hardware. increment o A set of tools and programming o There is no testing phase languages used to create software. o The system is developed in small, o The application of engineering principles manageable increments to software development. o It follows a strictly linear approach o The process of coding and debugging software. What is the recommended approach for balancing assumptions and research when What is a potential risk of relying too heavily on using proto-personas? proto-personas without validation? o Rely solely on proto-personas throughout o Wasting time by collecting too much user the project data before design begins o Ignore research that contradicts initial o Ensuring the final product is too flexible assumptions and customizable. o To guide initial design while planning for o Reinforcing existing biases and designing user research for the wrong user needs  o Focusing too much on long-term user o Proto-personas are quick, assumption- behavior rather than immediate needs. based representations, while full personas are in-depth, research-based What is the main focus of Root Cause Analysis? o Proto-personas are visualizations of user o Addressing symptoms of problems behaviors, while full personas focus on o Identifying underlying causes user demographics o Prioritizing tasks What is a key limitation of proto-personas? o Evaluating market position o They take too long to create What are the key principles of the Software o They are built on assumptions, not data- Engineering Code of Ethics? * driven insights o Public, Client and Employer, Product, o They provide too much detail about users Judgment, Management, Profession, o They can't be used in agile environments Colleagues, Self How do proto-personas fit into agile UX design? o Design, Implementation, Testing, Maintenance o They slow down the sprint process o Waterfall, Agile, Spiral, Incremental o They provide a user focus for each o Requirements Engineering, Design and development cycle Implementation, Testing and Debugging, o They replace the need for user stories Deployment and Maintenance o They are only used in the final sprint Which of the following best describes the What is the purpose of Continuous Integration relationship between problem-solving and and Continuous Deployment (CI/CD)? decision-making in software product design? * o Regularly merging code changes into a o They are completely separate processes central repository o Problem-solving always precedes o Automatically deploying code changes to decision-making production o They often overlap and work together o Detecting issues early and speeding up o Decision-making is a subset of problem- software delivery solving o All of the above What is the Software Engineering Code of In the context of software product design, what Ethics? * is the main purpose of problem- solving frameworks? o A set of guidelines for professional conduct in software engineering o To choose between multiple viable o A document that outlines the stages of alternatives software development o To tackle complex problems o A framework for organizing software systematically projects o To evaluate a product's market position o A code that defines the principles of o To prioritize tasks based on urgency software engineering Which framework is particularly useful for What is the primary focus of the Design Thinking assessing a product's position in the market? framework? * o RICE Matrix o Identifying root causes o Pareto Analysis o Emphasizing empathy for users o SWOT Analysis o Prioritizing tasks based on urgency o Fishbone Diagram o Evaluating options based on reach and What is the primary benefit of using Mind impact Mapping in problem-solving? * How do proto-personas differ from full o It helps in identifying root causes personas? * o It facilitates visual brainstorming and idea o Proto-personas are based on extensive organization user research, while full personas are o It prioritizes tasks based on urgency assumption-based o It evaluates options based on reach and impact What is the primary goal of software maintenance? * o To monitor user activities and ensure compliance with terms of service o To update and improve the software post- release o To prevent and correct errors in the software o To add new features without changing the original code Which of the following is NOT a core process activity in software engineering as mentioned in the presentation? o Requirements Engineering o Design and Implementation o Marketing and Sales o Testing and Debugging