1 of 43

INFORMATICS 113:�REQUIREMENTS ANALYSIS �& ENGINEERING

What is this course about?

How do we work effectively as a team?

Lecture 1

2 of 43

Today’s Lecture – What is this course about? How do we work effectively as a team?

  • Course basics/syllabus
  • Teamwork

Text questions to (562) 684-8307

2

3 of 43

Today’s Lecture – What is this course about? How do we work effectively as a team?

  • Course basics/syllabus
  • Teamwork

Text questions to (562) 684-8307

3

4 of 43

Teaching Staff

  • Professor
    • Emily Navarro
  • Teaching assistants
    • Rafed Yasir
    • Shilong Li
    • Leyu Lyu
  • Reader
    • Diya Saha

Text questions to (562) 684-8307

4

5 of 43

Class Structure

    • Lectures
    • T Th: 9:30-10:50am
  • Discussions
    • Mondays
  • 3 Exams
    • Every other Tuesday (~weeks 4, 7, finals)
  • 7 Team Homework Assignments

5

Text questions to (562) 684-8307

6 of 43

Office Hours

  • Emily: T 1:30-2:30pm on Zoom
  • TAs/Readers: During discussion, or by appointment
  • Office hours start in week 2

6

Text questions to (562) 684-8307

7 of 43

Schedule

  • See Website

Text questions to (562) 684-8307

7

8 of 43

What is this course about?

​

​

The hardest part of software engineering is building the right thing.

Text questions to (562) 684-8307

8

9 of 43

What is this course about? (1 of 2)

  • Equipping YOU to develop software systems through requirements analysis and engineering techniques
  • Becoming familiar with a systematic process of developing requirements through cooperative problem analysis, representation, and validation

Text questions to (562) 684-8307

9

10 of 43

What is this course about? (2 of 2)

  • Specifying what a proposed software system should do, why and for whom the system is needed
    • Not how the system should do it
  • Both technical and non-technical approaches to the requirements problem

Text questions to (562) 684-8307

10

11 of 43

Learning Objectives

  • Work as a productive member of a team to:
    • analyze a proposed software system
    • create and validate various requirements artifacts
      • product vision (goals and scope)
      • stakeholder model
      • elicitation questions
      • user stories
      • use cases
  • Understand and describe the following non-technical requirements-related aspects:
    • team dynamics (in the context of software engineering)
    • principles of RE
    • RE processes
    • requirements management
    • tools/standards for RE
    • RE for AI-based software

​

Text questions to (562) 684-8307

11

12 of 43

Rules of the Game: Be Involved…

  • Attend lecture
    • Class material is core part of assignments and quizzes
    • Exercises in class
    • Official place for announcements
  • Attend discussion
    • Week 2: Team formation
    • All other weeks: Elicitation with customer (TA), possibly other activities TBD
  • Visit Canvas website on a regular basis
  • Read e-mail frequently
  • Do not ignore Canvas announcements!
  • Ask questions

Text questions to (562) 684-8307

12

13 of 43

Retrieval Practice

  • We will do semi-frequent retrieval practice in lecture (through Canvas quizzes)
  • Unless otherwise stated, these Canvas quizzes are ungraded for right/wrong answers; you get participation points for completing them
  • More info: https://www.retrievalpractice.org

​

13

https://www.youtube.com/watch?v=ZO8abw3DHxs&t=2s

14 of 43

Cheating

  • DON’T DO IT!
  • All assignments are checked thoroughly for plagiarism
  • Collaborating with someone else during a weekly quiz is considered cheating
  • Plagiarism/cheating consequences
    • Fail the assignment
    • Offense recorded with the Office of Academic Integrity & Student Conduct

Text questions to (562) 684-8307

14

15 of 43

Assessment

  • Homework (55%)
    1. Product Vision (Goals and Scope) (5%) - teamwork
    2. Stakeholder Model (5%) - teamwork
    3. Elicitation (5%) – teamwork
    4. User Stories (15%) – teamwork
    5. Use Cases (15%) – individual + teamwork
    6. AI Requirements (5%) – teamwork
    7. Validation (5%) – teamwork
  • Class Attendance and Participation (10%)
  • Exams (35%)
    • Lowest one dropped

15

16 of 43

Class Attendance/Participation

  • Canvas participation quizzes
    • ~1-2 per lecture
  • Lecture pre-work quizzes
    • At most 1 per lecture
    • Assigned at the end of a lecture, due by the start of the next lecture
    • Short thought questions to get you thinking about the upcoming lecture content
  • Lowest 5 dropped

Text questions to (562) 684-8307

16

17 of 43

Illness

    • Do not come to class if you are sick!
    • You can miss about 3 lectures with no penalty in participation points

17

Text questions to (562) 684-8307

18 of 43

Peer Evals

  • After the grading of each assignment is finalized, scores on team assignments may be modified based on peer evals and Google Drive revision history
  • Unless everyone on your team contributes equally throughout the semester, you will not all receive the same scores on these team assignments

Text questions to (562) 684-8307

18

19 of 43

Grading

  • Performed by TA/reader
  • Double-checked by professor
  • Disagreements
    • Resolve with TA/reader first, then with professor
    • If you believe a mistake has been made prepare the following before arranging a meeting with the TA/reader
      • What is the mistake?
      • Why is it a mistake?
      • Support that demonstrates your arguments
    • You have one week from the time the grade is posted to request a regrade

Text questions to (562) 684-8307

19

20 of 43

Specifications Grading

  • Each assignment will include a detailed rubric with requirements for each category
  • Each rubric item is "all or nothing" scoring
  • For Homeworks 1-6, every team will be allowed to revise and resubmit every homework once

​

​

20

21 of 43

Late Work

  • My general policy is that I do not accept late work
  • Talk to me if you have a situation

Text questions to (562) 684-8307

21

22 of 43

Questions

  • Use Ed Discussion
    • Access through Canvas
  • E-mail questions
  • Questions may not be answered very close to the due date
    • so plan ahead

Text questions to (562) 684-8307

22

23 of 43

Letters of Recommendation

  • If you want one (now or in the future), make sure you make an impression on me!
    • Participate in class
    • Come to office hours
    • Do well in the class
  • The more I know you, the better the letter
  • Ask me early!

Text questions to (562) 684-8307

23

24 of 43

Questions?

Text questions to (562) 684-8307

24

25 of 43

Canvas Quiz

​

​

​

Lecture 1: Syllabus Quiz

Text questions to (562) 684-8307

25

26 of 43

Today’s Lecture – What is this course about? How do we work effectively as a team?

  • Course basics/syllabus
  • Teamwork

Text questions to (562) 684-8307

26

27 of 43

Think…

  1. About your best team experience and what made it the best
  2. About your worst team experience and what made it the worst

Text questions to (562) 684-8307

27

28 of 43

28

29 of 43

Why teamwork?

  • Central to this course and to a SE career
  • You can conquer complex and challenging projects that you could not accomplish on your own
  • Conflict management skills
  • Multiple perspectives
  • Accountability
  • You learn from all aspects of teamwork, even the bad

​

Text questions to (562) 684-8307

29

30 of 43

What makes a team?

  • Members
    • share a common purpose
    • recognize they belong to the team
    • are interdependent on each other
    • agree on norms or values that regulate their behavior

Text questions to (562) 684-8307

30

This usually has to develop … teams aren’t born with it!

31 of 43

Moxon’s Theory of Team Formation

31

Stage

Description

What members ask themselves

1. Forming

Initial awareness

Why are we here? �Will I be accepted?

2. Storming

Sorting-out process

Who has what kind of control and power? �Will I be respected?

3. Norming

Self-organization

How are we going to work together? �How can I help this group?

4. Performing

Maturity

How can we do better?

Peter Moxon: Building a Better Team (Ashgate 1998)

32 of 43

Stage 1:  Forming

  • Introductions, socializing
  • Team tries to come to a consensus on their purpose
  • Generally, people are on their best behavior
  • Cliques may form
  • A team leader may emerge

​

Text questions to (562) 684-8307

32

33 of 43

Stage 1:  Recommendations

  • Discuss team expectations
    • Establish ground rules
    • Be as specific as possible
    • Hold each other (and yourself) accountable
  • Define team roles and responsibilities
    • Facilitator
      • Help team organize, focus, participate, be productive
    • Recorder
      • Maintains and distributes team record (actions, decisions)
    • Participants (all)
      • Generate ideas, complete tasks

​

Text questions to (562) 684-8307

33

34 of 43

Stage 2:  Storming

  • The most painful, but most important stage 
  • Role negotiation is the undercurrent
  • Competition/conflicts/battles/challenges

34

35 of 43

Stage 2:  Recommendations

  • Communicate! Make sure everyone stays in the loop.
    • Write things down
  • A goal to aim for:  everyone is doing effective things, not destructive things
    • Refer to the ground rules
  • There is no cookbook strategy for getting through this phase -- it's difficult, and each group is unique

​

Text questions to (562) 684-8307

35

If you avoid, rather than confront conflict, you will never reap the cognitive benefits of functioning collaboratively!

36 of 43

Stage 3:  Norming

  • Members collaborate rather than compete
  • Creativity increases
  • Leaders becomes facilitators
  • Teammates have roles but role boundaries are fluid
  • Teammates tolerate and compensate for each others’ weaknesses
  • A team spirit is developed

​

Text questions to (562) 684-8307

36

37 of 43

Stage 3:  Norming

  • active listening "What I hear you saying is ..."
  • check what you hear with others, not just the speaker
  • if you disagree, say so
  • no interrupting
  • if you don't understand, ask questions then
  • allow everyone to participate
  • honesty and self-disclosure
  • look for facts in complaints; always bring it back to a technical discussion
  • keep criticism constructive
  • decide what to do with each criticism (don't leave it hanging)
  • accept/act on at least some of the feedback you are given
  • validate others’ contributions
  • ask quiet ones what they think
  • politely cut off domineering ones
  • find and follow systematic ways of working
  • see conflicts as mutual problems to be resolved

Effective interpersonal behaviors emerge:

37

38 of 43

Stage 3: Recommendations

  • Keep up the good practices from this and previous stages

​

Text questions to (562) 684-8307

38

39 of 43

Stage 4:  Performing

  • The effective patterns of behavior are now the norm
  • The team achieves more than the sum of what its members could do individually
  • The team has the ability to prevent or work through team problems

​

Text questions to (562) 684-8307

39

40 of 43

Teamwork skills to focus on and develop this quarter

  • Provide and receive constructive feedback
    • Use feedback received to improve your work without taking it personally
  • Show appreciation for the work of others
  • Actively listen
  • Work ethic
    • Professionalism
    • Respectfulness
    • Dependability
    • Positive attitude
    • Provide honest, accurate schedule estimates and dependably deliver on them

Text questions to (562) 684-8307

40

41 of 43

Finally…

  • If you are having a problem in your team
    • Try resolving it on your own
    • If that doesn’t work, come to one of the teaching staff ASAP and/or proceed with “firing” procedure (see syllabus)

​

Text questions to (562) 684-8307

41

42 of 43

Team Formation

  • During discussion Monday
  • Teams are about 4 people and all must be in same discussion section

Text questions to (562) 684-8307

42

43 of 43

For Next Time

  • Complete Lecture 2 Pre-Work: Why RE?

43