2. WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010. They may not show up well on other PowerPoint versions. You can download PowerPoint 2010 viewer from here.here These slides contain a lot of animations. For optimal results, watch in slideshow mode.

3. Pre-lecture exercise [can do in pairs] : Imagine you are building an online system called TeamFormer. Specify the vision, scope, user types, and the workflow of TeamFormer. Specify requirements of TeamFormer as a list of User Stories. TeamFormer is a system for helping CS2103 students during team forming period. It lets students record who is in which team. Students can use the system to find teams short of members and students looking for teams, easing the team forming process. Note that the system is not meant as a platform for students to communicate with each other to find team members. Students are supposed to talk to each other and form teams outside the system, as they do now. TeamFormer simply helps students to see the team forming status of the class (e.g., who has teams and who don’t) and record their own team after forming a team. It is also meant to ease the team-forming-related workload of instructors. If you didn’t do this earlier, try it now.

4. Pre-lecture exercise [can do in pairs] : Imagine you are building an online system called TeamFormer. Specify the vision, scope, user types, and the workflow of TeamFormer. Specify requirements of TeamFormer as a list of User Stories. TeamFormer is a system for helping CS2103 students during team forming period. It lets students record who is in which team. Students can use the system to find teams short of members and students looking for teams, easing the team forming process. Note that the system is not meant as a platform for students to communicate with each other to find team members. Students are supposed to talk to each other and form teams outside the system, as they do now. TeamFormer simply helps students to see the team forming status of the class (e.g., who has teams and who don’t) and record their own team after forming a team. It is also meant to ease the team-forming-related workload of instructors.

5. admin?, team? Pre-lecture exercise [do in pairs] : Imagine you are building an online system called TeamFormer. Specify the vision, scope, user types, and the workflow of TeamFormer. Specify requirements of TeamFormer as a list of User Stories. TeamFormer is a system for helping CS2103 students during team forming period. It lets students record who is in which team. Students can use the system to find teams short of members and students looking for teams, easing the team forming process. Note that the system is not meant as a platform for students to communicate with each other to find team members. Students are supposed to talk to each other and form teams outside the system, as they do now. TeamFormer simply helps students to see the team forming status of the class (e.g., who has teams and who don’t) and record their own team after forming a team. It is also meant to ease the team-forming-related workload of instructors. Vision: Scope: for CS2103? for NUS? for any school? for the world? for capturing team forming status ? to form teams using system? Users: instructor, student, Workflow: (a) Any student can create/join/leave any team? (b) Instructor creates slots and leader sign up for slots? To make team forming easier

6. User stories:? As a _______I can _______So that_______ userloginI can access actions available to me logoutothers don’t perform actions using my identity instructorSpecify a team forming period Team forming happens in a limited period Specify which students take part Only the relevant students take part student without a team find others looking for teammates find potential team members Let others know own profile To increase chances of being approached by a matching team

7. User stories:? As a _______I can _______So that_______ userloginI can access actions available to me logoutonly my actions are identified as mine instructorSpecify a team forming period Team forming happens in a limited period Specify which students take part Only the relevant students take part student without a team find others looking for teammates find potential team members Let others know own profile To increase chances of being approached by a matching team

8. User stories:? As a _______I can _______So that_______ student without a team find others looking for teammates find potential team members specify own profileTo increase chances of being approached by a matching team

9. User stories:? As a _______I can _______So that_______ student without a team find others looking for teammates find potential team members specify own profileTo increase chances of being approached by a matching team a rep of a partial team specify count and nature of vacancies others matching the vacancies can approach a rep of a teamcan remove a member to indicate student is no longer with the team a student in a teamcan remove self from the team to indicate no longer with that team And more… a representative of a team can register the team to let others know we have a team

10. Use case: add student to team Actor: Instructor Pre-condition: Logged in MSS: 1. Instructor chooses student to add 2. System shows teams that can take the student 3. Instructor indicates which team to add 4. System applies the change and updates the view Use case ends Extensions 3a Instructor chooses to add student to a new team 3a.1 System request for new team id 3a.2 Instructor provide a new team id Use case resumes at step 4. 4a Instructor chooses to undo 4a.1 System undo the change and updates view Use case ends. Interactions, not UI design Can be different from yours

13. Students without teams Team 1 Team 2 Team 3 move UI prototype:? Student Jake moved to Team 1 [undo]

14. Students without teams Team 1 Team 2 Team 3 move UI prototype:? Student Jake moved to Team 1 [undo] Glossary TFS: team forming session team (not group) Loner: student without a team Supplementary Authentication done by IVLE. The session is linked to IVLE module. Only one session at a time. Only one instructor. No messaging, notifications done via the system. No max/min team size. All student actions are logged.

15. GREAT SOFTWARE

17. Label groups Side-by-side views Drag-and- drop Issue nesting HubTurbo [Pre release]

18. Which of these is least likely to be in the supplementary requirements category? a) Admin users can delete any other account. b) The code should be open source. c) The product should actively prevent it being used for illegal purposes. d) A customer may not have more than one overdrawn account. supp {a|b|c|d} e.g. supp c supp {a|b|c|d} e.g. supp c 77577 OR tinyurl.com/answerpost

21. V0.0 = User Guide

27. 1.value to user, not you 2.minimize work for user 3.match user intent 4.less is more 5.don’t force to RTFM 6.don’t make users feel stupid 7.benefits, not features 8.be everything to somebody 9.visualize usage 10.care

28. 1.value to user, not you 2.minimize work for user 3.match user intent 4.less is more 5.don’t force to RTFM 6.don’t make users feel stupid 7.benefits, not features 8.be everything to somebody 9.visualize usage 10.care reschedule | editdate

29. 1.value to user, not you 2.minimize work for user 3.match user intent 4.less is more 5.don’t force to RTFM 6.don’t make users feel stupid 7.benefits, not features 8.be everything to somebody 9.visualize usage 10.care Error messages + instructions

30. value to user, not you minimize work for user match user intent less is more don’t force to RTFM don’t make users feel stupid benefits, not features be everything to somebody visualize usage care Yes we can!

31. CS2103 project CS2103 exam CS2103

32. CS2103 project CS3106 project CS2103 exam internship Interviews First job Thematic project FYP CS2103 is for life!

33. CS2103 is for life!

34. CS2103 is for life! Behavior, Practices, Mindset

35. CS2103 is for life!

36. http://doanie.wordpress.com/2010/02/23/mean-professor-tells-student/

41. Small things matter in the industry }

42. Small things matter NOW! NOC Grades FYP allocation Tutor appointment Recommendation letters Joining teams …

43. Small things matter.

44. Do them right. Participation points will take care of themselves Small things matter. Industry survival tip

45. Individual basic coding competencies. Conceptualizing a product to solve a problem. L4 Theme: Let’s split work and start building this thing.

46. Software Engineer (for real)

47. 1.value to user, not you 2.minimize work for user 3.match user intent 4.less is more 5.don’t force to RTFM 6.don’t make users feel stupid 7.benefits, not features 8.be everything to somebody 9.visualize usage Forgive spelling mistakse spelling {number} e.g. spelling 3 spelling {number} e.g. spelling 3 77577 Which observation is most related to this feature?