Software EngineeringAgendaNeal AudenaertThe TeamIntroductionSlide 6Problem StatementAn ObservationSlide 9A Possible ApproachPowerPoint PresentationSome ActorsSome Use CasesSlide 14Discussion QuestionsPossible Group StructureSlide 17Slide 18TasksSoftware EngineeringTeam 1 First MeetingAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksNeal AudenaertPhone: (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 VillalpandoIntroductionOur First Assignment – Next FridayUse Cases and Paper PrototypesSo. . . For TodayDevelop a Plan of ActionSchedule a Second MeetingAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksProblem 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 ObservationThat is Hard. Very Hard.There are 66 checkpointse.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.0AgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksA Possible ApproachDevelop a Tool That:Provides Automatic Validation Where PossibleSupports Human Evaluation ElsewhereGoal: Help a Web Development Team Implement a Process that Improves Web Site AccessibilityA Short Story . . .Some ActorsProject ManagerDevelopment Team MemberClientUsability Test Subject/Usability ExpertSome Use CasesStart a New ProjectAutomatically Evaluate a SiteEnter Human Evaluation of a PageTrack Changes to the SiteFind Out How Compliant A Site IsAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksDiscussion QuestionsDecent Approach?Web-Based or Standalone?Programming LanguagePossible Group StructureMainline Development:2 Sections of 4 People EachUser Interface:1 Section of 3 PeopleAnalysis and Testing:1 Section of 3 PeoplePossible Group StructureEach Section has a Documentation LeadEach Section has a Section LeadDivide People by Experience/SkillTeam SecretarySchedule Meetings, Take Meeting Notes, Coordinate DocumentationAgendaIntroductionProject OverviewPossible ApproachDiscussion QuestionsTasksTasksNowSplit Into Groups to Elaborate Use CasesPick a Meeting Time Before Next TimeIf You Haven’t, Read the GuidelinesCome Up With Use CasesThink About GroupsSend Me An Email (skills, experience,
View Full Document