CS427: Software Engineering IAdministrative infoFinal examTopics since midtermCrystal clearSlide 6Crystal clear assumptionsCrystal Clear assumptionsCrystal ClearPeopleOther rolesPoliciesSlide 13Work productsSlide 15Requirements work productsDesign work productsTests and final systemMaking it workRequirementsCommon object modelSummaryNext: Course summary1CS427:Software Engineering IDarko Marinov(slides from Ralph Johnson)CS427 25-2Administrative infoWiki down again If you were affected, you can submit HW5 on Thursday, Dec 7Schedule demo between today and 18?The sooner the better Final report due on Dec 7 or by arrangementAll team members should be present or be able to explain work of the missing membersDefault: Everyone on team gets the same grade for the project, BUT there can be varianceCS427 25-3Final examThu, Dec 14, 7-10pm1310 DCL269 EverittConflict exam: Mon, Dec 11, 1:30-4:30pm3403 SCMore info will be on WikiCS427 25-4Topics since midtermSpecificationsDesignQuality assuranceUser interfaceTwo more processesOpen source (previous lecture)Crystal clear (today)CS427 25-5Crystal clearReading for this lectureCrystal light methods overview http://alistair.cockburn.us/index.php/Crystal_light_methodsA family of processesNamed after crystal terminologyColor and hardnessCrystal Clear: The Simplest Process That Can Work (Applied anthropology)CS427 25-6Crystal clear“Good, small teams have been putting out good software for decades, using thinking, communicating and delivering as their primary tools.”“Good, small teams do not scale up in number, so keep them small, permit them to move fast, do project tracking through their final results, not their intermediate thinking.”CS427 25-7Crystal clear assumptionsPeople are good at looking aroundPeople are not as tidy as abstractions of them make them appearCommunication involves a lot more than the words spoken or writtenSoftware construction is growing understanding of problem and solutionCS427 25-8Crystal Clear assumptionsActual, working processes are Extremely complicatedHard to write downHard to follow Likely to be wrong when written downMethodologists are prone to overcomplicate or embellish thingsCS427 25-9Crystal ClearMake process as simple as you canRely on communication, individual skillSize: 4-6Essential moneys, but not lifeCS427 25-10PeopleSponsorSenior designerUserDesignersCS427 25-11Other rolesCan be separate people, or can be one of the designers, perhaps the senior designerBusiness expertCoordinator TesterWriterCS427 25-12PoliciesUse increments for project staging, tracking by milestones and predicted risks Involve user directlyRequirements are annotated usage scenariosPeer code reviewsCS427 25-13PoliciesCode ownership modelRegression testing framework Code standardUser interface standardCS427 25-14Work productsNot a substitute for understandingUnderstanding is primaryWork products are secondaryA substitute for disciplineA “minimal set”CS427 25-15Work productsMethodologyTeam structureRelease sequenceViewing and release scheduleRisk listProject statusCS427 25-16Requirements work productsMission statementActor-goal pairsAnnotated use casesRequirements fileCS427 25-17Design work productsSystem designCommon object modelScreen draftsDesign sketchesSource codeMigration codeCS427 25-18Tests and final systemTest casesTest resultsPackaged systemUser manualCS427 25-19Making it workHow do you make sure people communicate?How do you decide on an ownership model, coding standard, etc?CS427 25-20RequirementsWhere do requirements come from?How are they recorded?How are they validated?How are they used?CS427 25-21Common object modelHow is the object model recorded?How is the object model created?How is the object model used?CS427 25-22SummaryIs XP just a special case of Crystal Light?Could a RUP project also be a Crystal Light project?Could a Bazaar project be a special case of Crystal Light?CS427 25-23Next: Course summaryLast lecture on Thursday, Dec