Scribd
Upload
8 views

UNCG-CSC100-F17-LAB2-PairProgramming

The document outlines the structure and objectives of Lab 2 for CSC 100 at UNC Greensboro, focusing on software engineering principles and pair programming. It discusses the traditional Waterfall Model and the Agile Development approach, emphasizing the importance of peer reviews and collaborative coding. Additionally, it provides guidelines for pair programming activities, including roles, partner interactions, and submission procedures for lab work.

Uploaded by

ssneel
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

UNCG-CSC100-F17-LAB2-PairProgramming

The document outlines the structure and objectives of Lab 2 for CSC 100 at UNC Greensboro, focusing on software engineering principles and pair programming. It discusses the traditional Waterfall Model and the Agile Development approach, emphasizing the importance of peer reviews and collaborative coding. Additionally, it provides guidelines for pair programming activities, including roles, partner interactions, and submission procedures for lab work.

Uploaded by

ssneel
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Lab 2: Intro Material

Software Engineering and Pair Programming

Notes for CSC 100 - The Beauty and Joy of Computing


The University of North Carolina at Greensboro
Question to think about….

In these labs you are writing programs

How does this relate to professional software development?


Software Engineering
How to control the complex process of creating software

Traditional “software lifecycle” has well defined phases that feed into
each other one-way - called the “Waterfall Model”
Requirements
definition and
analysis
This is what we do in labs.
System
design

Implementation

Testing
In reality it never really works this
way - early stages change even Operations
when working on later stages. and
maintenance
Software Engineering
How to control the complex process of creating software

Traditional “software lifecycle” has well defined phases that feed into
each other one-way - called the “Waterfall Model”
Requirements Recent trend: “Agile Development”
definition and
Among other things, testing done
analysis
concurrently with development.
System Idea: Faster error identification and
design correction - higher quality software?

Implementation

Testing
In reality it never really works this
way - early stages change even Operations
when working on later stages. and
maintenance
Peer Reviews and Pair Programming
Two ideas for software development...

Peer Reviews: At regular intervals, a


developer presents and explains their code to
co-workers, who critically review code.
Similar to a writer going over drafts with an
editor.

Pair Programming: Development is


actually a collaborative activity -
pushes “review” so far back that it is
simultaneous with development!
Pair Programming for Learning
Plug: Don’t forget our
From August 2013 Communications of the ACM: UNCG ACM chapter!

Surprise!

We don’t do pair programming


because we like to torture you and
stick you with terrible partners.

We do it because it helps people


learn!
Pair Programming: What to do
Really simple concept:
● Two students, one computer
○ Roles: “Driver” and “Navigator”
○ Driver has keyboard/mouse, but navigator describes how to build
solution
● Both students always active
○ Not “Driver” and “Sleepy passenger”
● Switch roles regularly
○ At least once per lab activity, if not more often
● Be open and respectful
○ If you don’t like a proposed solution, your job is to either explain why
it’s not a good solution or to make the case for a better one - don’t just
dismiss it!

Handout: “Fun with Pair Programming!”


Details of Pair Programming in CSC 100
At the beginning of lab:
● Check partner/workstation information sheet posted on lab door
● Find your workstation
● If you don’t know your partner, introduce yourself!
● Only one of you will log in to the workstation - decide which one
(maybe first to sit down?) and log in to Snap! Cloud account
● If your partner is a no-show by 10:02, let the instructor or lab
assistant know

Submitting your work:


● Submit activities as usual through “The G”
● One of you logs in to Canvas and enters names that worked
together
● Everyone still does the quiz individually (before the next class)

You might also like