CS 350, slide set 10ACM Speaker: Frank ByrumReadingWhat’s due when?CommentsTopicsComments on team designDesign completion detailsDesign standardsLevels of designDesign goalsDesign script - 1Design script - 2Design script - 3StandardsIMP script - 1IMP script - 2IMP script - 3Some goals/guidelinesCS 350, slide set 10M. OverstreetOld Dominion UniversitySpring 2005ACM Speaker: Frank ByrumDate: Wednesday, April 20, 2005Time: 12:00-1:00pmLocation: 1st Floor Auditorium, E&CS Building Come and find out about the ACM and the computer science department! Refreshments will be servedReadingTSP text, omit Ch. 6; central part of CS 410; the NASA document provides one concrete example.TSP text: Ch. 7, 8, 9, 10, App. B (config. mgmt) will be discussed in classTSP text: Read Ch. 16 (Managing yourself), Ch. 17 (Being on a team), & Ch. 18 (Teamwork)What’s due when?See class web site, link under “checklists,” “Required forms checklist, due dates”Mail completed components to userid cs350The grader will check for them thereCommentsThere’s a spreadsheetTakes time to learn, use is optionalMake sure you know what data you will need to report so it will take less time to provide it!Look over the forms NOW!You set your own schedulesBut we will be checking on what you submit & prompting for things!Project is about TSPi, not codingEval. biased on determining if you followed TSPi!•Did you make reasonable plans (time, sizes, req. tasks)?•Were you able to handle the inevitable surprises?•Did you set goals, design, inspect, test, record errors, log time, etc.?•Did you measure your performance against your goals?•Did you support your team?TopicsDesigning in teamsDesign scriptImplementationImplementation scriptComments on team designNot easily done by large groupSome believe all good designs are done either by one individual or at most by a very small teamDesign can start with brain-storming sessionAll team members have input and contribute idealsThen 1 or 2 people create the designDesign completion detailsGoal: Inspection team can determine correctness of designProgrammers can produce the intended implementation directly from the design and their background knowledgeSometimes reference materials may be neededAnd domain knowledgeDesign standardsNaming conventionsInterface formatsSystem and error messagesDesign representation notationsLevels of designCommon levels:SystemSubsystemProductComponentModuleFor GCS, you only needSystem (mostly done)Module (for each selected module)Design goalsReuseDepends in part on standard documentationUsabilityNeed to review design from perspective of all people who will use the softwareTestabilityMay choose one design over anotherDesign script - 1Step Activity Description1 Design process reviewReview design process Review sample design How design inspection is performed2 High-level designDevelop manager leads design team Define program structure Name program components Identify design tasks to be completed and documented3 Design standardsQuality/process manager leads the effort to produce the name glossary and design standards4 Design tasksThe development manager leads the team through Outlining the SDS and the work to produce it.5 Task allocationThe team leader help allocate task among team members Also obtains commitments from membersDesign script - 2Step Activity Description6 Design specificationEach team member Produces and reviews his/her portions of the SDS documentProvides these to development managerDevelopment manager produces composite SDS draft7 Integration test planDevelopment manager leads team in producing and reviewing integration test plan8 Design & int. plan inspectionQuality/process manager leads team through inspecting the SDS draft and integration test plan Design is complete and correct Integration test plan is adequate Each problem is recorded and fix responsibility decidedInspection is documented in form INS, defects recorded in LOGDDesign script - 3Step Activity Description9 Design updateDevelopment manager SDS obtains sections and Combines them into final SDS Verifies traceability to the SRS10 Update baselineSupport manager baselines the SDSStandardsDesign standardsLet's assume pseudocode is good enough•Use another if you preferCoding standardsWhat we have is good enoughSize standardsMax size of a single component?Defect standardsWhat we have is good enoughStandards need to be reviewed and changed if they don't workBut not this semesterIMP script - 1Step Activity Description1 Imple- mentationprocess overviewInstructor has described Importance of quality implementation Need for coding standards Strategy for handling poor-quality components2 Imple- mentation planningDevelopment manager leads work to Define and plan implementation task (SUMP & SUMQ)3 Task allocationTeam leader helps allocate tasks to team members Obtains commitments for when they will complete tasks4 Detailed designProgrammers produce detailed designs They do individual thorough design reviews They complete LOGD and LOGT forms5 Unit test planTester produces unit test plansIMP script - 2Step Activity Description6 Test develop-mentTesters follow script UT to produce unit test plans,test procedures, and test data for each component7Test inspect.Quality/process manager leads team in inspection of test cases, procedures and data (use INS script and forms INS and LOGD) for each component8 Detailed design inspect.Quality/process manager leads team in inspection of DLD of each component (script INS and forms INS and LOGD)9 Code Programmers produce component source code Do a code review using personalized checklist Compile and fix the code until it compiles Complete LOGD and LOGT forms10 Code inspect.Quality/process manager leads team in code inspection of each component (script INS and INS and LOGD forms)IMP script - 3StepActivity Description11 Unit test Programmers, following script UT Conduct the unit tests and complete forms LOGD and LOGT12 Component quality reviewQuality/process manager reviews each component's data to determine if component quality meets establish team criteria If so, component is accepted for integration testing If not, quality/process mangers recommends either: the product be reworked and