Boston University CS 633Geographically Distributed Development

Group 2 Team 1Ivan AlencarRobert BeatonScott CromarKris KaufmanKyle SpohnBen Finkel

Agenda

• Project Overview

• Collaboration Technology

• Formal Processes

• Roles and Responsibilities

• Challenges

• Lessons Learned

• Demo / Screenshots

2CS-633 Group 2 Team 1

Project Overview

Professor’s Requirements• It must require several people to build • It must be non-trivial• It must be fairly easy to understand

Team Decisions• Keep it simple• Make it accessible via internet• Use ASP due to developer familiarity• Create contact information database

3CS-633 Group 2 Team 1

Collaborative Technology

• Instantconference.com (Phones)

• Google Code

• Google Groups

• Email

• Instant Messaging

4CS-633 Group 2 Team 1

Team Formal Processes

CS-633 Group 2 Team 1 5

• Biweekly conference calls• Meeting minutes for review• Rough drafts posted on Google Groups• Reviews and comments made• Edits are made by original author• Final Documents uploaded to Google Code• Code repository hosted on Google Code

Roles and Responsibilities

6CS-633 Group 2 Team 1

Member Primary Role Secondary Role Tertiary Role Responsibilities

 Kris Kaufman Team Lead Project  Management Project Admin Meeting Minutes, Team Submissions, SPMP, WBS, 

 Scott Cromar Quality Assurance Analyst Editor Requirements, SDD, Iteration Plans, Test Logs, SQAP

 Kyle Spohn Project Management Quality Assurance Software Testing (Acceptance)

SPMP, WBS, SQAP, STP

 Robert Beaton Application Development

DBA Software Testing (Integration)

Application development and testing

 Ivan Alencar  DBA Application Development

 Software Testing (Unit)

SCMP, SVVP

 Ben Finkel  

 Joshua Cope  Project Sponsor      

 Eric Braude  Project Sponsor      

Challenges

7CS-633 Group 2 Team 1

• Learning curve• Culture differences• Communication related delays• Incompatible work schedules• Missed deadlines• Lack of participation

Lessons Learned

8CS-633 Group 2 Team 1

• Be flexible• Post drafts early• Review and approve• Swift trust but verify• Communicate often• Testing is important• Schedule deployments

Demo – Start Screen

9

Initial Options for Users1. Add an new entry

2. Search for a contact

3. Review contact listCS-633 Group 2 Team 1

1 2 3

Demo – Add an Entry

10

Data entry screen • All fields required• Hit “Publish Entry” to insert a record• Data validation occurs on server and application level• Hit “Reset” to clear fields and start over• Hit “Back” to return to start screen

CS-633 Group 2 Team 1

Demo – Search for Contact

11

1) Fill in at least one parameter

2) Hit “Search” button

3) Wildcard search implemented across fields

4) Records returned can be edited and deleted

5) Use “Reset” button to clear fields

6) Use “Back” to return to start screenCS-633 Group 2 Team 1

Demo – Records Returned

12

1) All records matching parameter(s) are returned

2) All information associated with record is displayed

3) Use “Change Search Parameters” to return to search screen

4) Use “Home” button to return to start screen

5) Use “Open” button to review individual record

CS-633 Group 2 Team 1

Demo – Edit or Delete Record

13

1) All fields become editable

2) Use “Change Entry” button to update fields in database

3) Use “Delete Entry” to remove record from database

4) Use “Reset” button to return fields to previous values

5) Use “Back” button to return to searched list

CS-633 Group 2 Team 1

Demo – Contact List

14

1) All records in the system are displayed

2) Each column of associated data is displayed

3) Use “Back” button to return to start screen

CS-633 Group 2 Team 1

Questions and Answers

15CS-633 Group 2 Team 1