WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 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.

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 doesn’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 try this exercise earlier, try it now. If you have any questions, come down and talk to me now.

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 doesn’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 try this exercise earlier, try it now. If you have any questions, come down and talk to me now.

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 doesn’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

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 I can try to form a team with them let others know my profile I increase chances of being approached by a matching team

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 see others looking for teammates I know who are potential team members specify my profileothers know the value they get if they take me as a team member

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 see others looking for teammates I know who are potential team members specify my profileothers know the value they get if they take me as a team member

User stories:? As a _______I can _______So that_______ student without a team see others looking for teammates I know who are potential team members specify my profileothers know the value they get if they take me as a team member rep of a partial team specify count and nature of vacancies others matching the vacancies can approach rep of a teamremove a memberothers know he/she is no longer with the team student in a teamremove self from the team others know that I am no longer with that team And more… representative of a team register the teamothers know we have a team

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

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

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.

GREAT SOFTWARE

Filter issues Select to view HubTurbo [Pre release]

Side-by-side views Keyboard shortcuts 1.Saves time 2.Helps developers 3.Can contribute 4.Learn from it HubTurbo [Pre release] Similar, but different Done well, not done well

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

Which of these is not a non-functional requirement? 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. func {a|b|c|d} e.g. func b func {a|b|c|d} e.g. func b OR tinyurl.com/answerpost

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 Which observation is most related to this feature?