Unformatted text preview:

Software EngineeringAgendaNeal AudenaertThe TeamIntroductionSlide 6Problem StatementAn ObservationSlide 9A Possible ApproachPowerPoint PresentationSome ActorsSome Use CasesSlide 14Discussion QuestionsPossible Group StructureSlide 17Slide 18TasksSoftware EngineeringTeam 1 First MeetingAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksNeal AudenaertPhone: (979) 845-4924 (w)(979) 739-5636 (m)Email:[email protected]Web Site:http://www.csdl.tamu.edu/~neal/The TeamCaleb BellPaul BilnoskiJeffrey CarolloThomas GarnerEsam MlaihLoi NguyenJesse PlymalePayton QuackenbushPradeep SarvepalliMahbub SiddiqueBhargavi SrivathsanChunhua TangNathanael TaylorRyan VillalpandoIntroductionOur First Assignment – Next FridayUse Cases and Paper PrototypesSo. . . For TodayDevelop a Plan of ActionSchedule a Second MeetingAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksProblem StatementDevelop 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.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 site’s content.”Source: Checklist of Checkpoints for Web Content Accessibility Guidelines 1.0AgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksA 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 AccessibilityA Short Story . . .Some ActorsProject ManagerDevelopment Team MemberClientUsability Test Subject/Usability ExpertSome 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 IsAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksDiscussion QuestionsDecent Approach?Web-Based or Standalone?Programming LanguagePossible Group StructureMainline Development:2 Sections of 4 People EachUser Interface:1 Section of 3 PeopleAnalysis and Testing:1 Section of 3 PeoplePossible 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 DocumentationAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksTasksNowSplit Into Groups to Elaborate Use CasesPick a Meeting Time Before Next TimeIf You Haven’t, Read the GuidelinesCome Up With Use CasesThink About GroupsSend Me An Email (skills, experience,


View Full Document

TAMU CSCE 606 - mtg1

Documents in this Course
Load more
Download mtg1
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view mtg1 and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view mtg1 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?