Software Engineering

1
Software Engineering

• Team 1 First Meeting

2
Agenda

• Introduction
• Project Overview
• Possible Approach
• Discussion Questions
• Tasks

3
Neal Audenaert

• Phone
• [phone] (w)
• [phone] (m)
• Email
• neal_at_csdl.tamu.edu
• Web Site
• http//www.csdl.tamu.edu/neal/

4
The Team

• Caleb Bell
• Paul Bilnoski
• Jeffrey Carollo
• Thomas Garner
• Esam Mlaih
• Loi Nguyen
• Jesse Plymale

• Payton Quackenbush
• Pradeep Sarvepalli
• Mahbub Siddique
• Bhargavi Srivathsan
• Chunhua Tang
• Nathanael Taylor
• Ryan Villalpando

5
Introduction

• Our First Assignment Next Friday
• Use Cases and Paper Prototypes
• So. . . For Today
• Develop a Plan of Action
• Schedule a Second Meeting

6
Agenda

• Introduction
• Project Overview
• Possible Approach
• Discussion Questions
• Tasks

7
Problem Statement

• Develop a tool for evaluating Web sites. The tool
  will check for compliance against a set of
  guidelines, in this case the Web Content
  Accessibility Guidelines 1.0.

8
An Observation

• That is Hard. Very Hard.
• There are 66 checkpoints
• e.g. Checkpoint 14.1
• Use the clearest and simplest language
  appropriate for a sites content.

Source Checklist of Checkpoints for Web Content
Accessibility Guidelines 1.0
9
Agenda

• Introduction
• Project Overview
• Possible Approach
• Discussion Questions
• Tasks

10
A Possible Approach

• Develop a Tool That
• Provides Automatic Validation Where Possible
• Supports Human Evaluation Elsewhere
• Goal Help a Web Development Team Implement a
  Process that Improves Web Site Accessibility

11
A Short Story . . .
12
Some Actors

• Project Manager
• Development Team Member
• Client
• Usability Test Subject/Usability Expert

13
Some Use Cases

• Start a New Project
• Automatically Evaluate a Site
• Enter Human Evaluation of a Page
• Track Changes to the Site
• Find Out How Compliant A Site Is

14
Agenda

• Introduction
• Project Overview
• Possible Approach
• Discussion Questions
• Tasks

15
Discussion Questions

• Decent Approach?
• Web-Based or Standalone?
• Programming Language

16
Possible Group Structure

• Mainline Development
• 2 Sections of 4 People Each
• User Interface
• 1 Section of 3 People
• Analysis and Testing
• 1 Section of 3 People

17
Possible Group Structure

• Each Section has a Documentation Lead
• Each Section has a Section Lead
• Divide People by Experience/Skill
• Team Secretary
• Schedule Meetings, Take Meeting Notes, Coordinate
  Documentation

18
Agenda

• Introduction
• Project Overview
• Possible Approach
• Discussion Questions
• Tasks

19
Tasks

• Now
• Split Into Groups to Elaborate Use Cases
• Pick a Meeting Time
• Before Next Time
• If You Havent, Read the Guidelines
• Come Up With Use Cases
• Think About Groups
• Send Me An Email (skills, experience, etc)