Software System EngineeringSlide 2Slide 3RECOMMENDATIONS FOR DOCUMENTING PROCESSESESSENTIAL OO PROCESS ELEMENTSINTEGRATED GRAPHICAL/ TEXTUAL DOCUMENTATION RECOMMENDEDLESSONS LEARNED FROM PROCESS DEVELOPMENTOO DEVELOPMENT PROCESS SUMMARYProcess Documentation – Template & ExampleProcess Documentation – Symbolic NotationSlide 11Process Documentation – Symbolic Notation - ExampleDiscussion QuestionsQuestions for the Next LectureTasks for Next Lecture 1998-06 FayadSJSU -- CmpESoftware System EngineeringDr. M.E. Fayad, ProfessorComputer Engineering Department, Room #283I College of EngineeringSan José State UniversityOne Washington SquareSan José, CA 95192-0180 http://www.engr.sjsu.edu/~fayad, [email protected] 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S2 Doc. Processes2Lecture 2c:Documenting SoftwareProcesses - 2 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S3 Doc. Processes Lesson ObjectivesObjectives3Understand the recommendations for documenting process. Discuss the essential process elements Understand how to document S/W processes Template Symbolic notation UML – activity diagram 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S4 Doc. ProcessesRECOMMENDATIONS FOR DOCUMENTING PROCESSESConcentrate on tracing inputs to outputs–encapsulate creative processingIdentify all reviews–define products required–approval authorityIdentify where CM occursConsistently specify all roles involved –developers–SQA–testers–customersConcentrate on tracing inputs to outputs–encapsulate creative processingIdentify all reviews–define products required–approval authorityIdentify where CM occursConsistently specify all roles involved –developers–SQA–testers–customers4 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S5 Doc. ProcessesESSENTIAL OO PROCESS ELEMENTSMap method products to each software activity–graphics–tables–repositoriesIdentify what/when from CASE toolsIdentify appropriate OO notation for your documentationSpecify what level of coordination must exist betw een objectsMap method products to each software activity–graphics–tables–repositoriesIdentify what/when from CASE toolsIdentify appropriate OO notation for your documentationSpecify what level of coordination must exist between objects5 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S6 Doc. ProcessesINTEGRATED GRAPHICAL/ TEXTUAL DOCUMENTATION RECOMMENDEDgraphics maximize communicationtext expands detailgraphics maximize communicationtext expands detailSQAReviewerReaderDesignerPreliminaryDesignReviewerModeratorS/W TechLeadReworkPerform furt her r ework of th edeta iled design. Prese nt minorrewor k to SQA Reviewer andmajor rework to S/ W T ech Lea d.Are allminor defectsreworked?Are al lmajor defectsreworked ?Follow-UpInfo rm de signer that de taileddesign passed in spection.Add specificat io n units int ocurr ent CM S libr ary.YesYesNoNoSoftware Inspection ProcessRolesTime3.2.2 Follow-Up3.2.1 Rework6 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S7 Doc. ProcessesLESSONS LEARNED FROM PROCESS DEVELOPMENTIngrain metrics collection directly into processesDevelopment team should “own” processesDevelopment team should “enforce” processesProcess assessment should be part of processIngrain metrics collection directly into processesDevelopment team should “own” processesDevelopment team should “enforce” processesProcess assessment should be part of process7 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S8 Doc. ProcessesOO DEVELOPMENT PROCESS SUMMARY1. Processes map software methods from the classroom to the computer room–translate theory to action2. Processes especially important for new OO development teams–maximizes individual contributions3. Processes must be tuned for specific projects–tuned for specific attributes4. Integrated graphics and text provide effective documentation format–eases communication and maintenance1. Processes map software methods from the classroom to the computer room–translate theory to action2. Processes especially important for new OO development teams–maximizes individual contributions3. Processes must be tuned for specific projects–tuned for specific attributes4. Integrated graphics and text provide effective documentation format–eases communication and maintenance8 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S9 Doc. ProcessesProcess Documentation TemplateMicro-Development Process – Software Inspection9Process Documentation – Template & Example 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S10 Doc. Processes10Process Documentation – Symbolic NotationInput description -- Process inputsi,e. tools & informationTransition ArrowRole 1Role 2Role NParticipants ChartOutput description -- Process outputsi,e. tools, manual, & informationProcess Step NameRoles 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S11 Doc. Processes11Process Documentation – Symbolic NotationDecisionDiamondYesNoFilled Process BoxParallelogram shows concurrencyParallelProcessStepParallelProcessStep 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S12 Doc. Processes12Process Documentation – Symbolic Notation - Example 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S13 Doc. ProcessesName the roles in the following software processes–Spiral Model–Requirement Engineering–Software Testing–Software Review–Interaction Diagram–Class Diagram–Software development planning13 Discussion Questions 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S14 Doc. ProcessesActivity Diagram14Questions for the Next Lecture 1998-06 FayadSJSU -- CmpE M.E. Fayad L2c-S15 Doc. ProcessesTask 1: Read Appendix A – Fayad’s Book & any materials on UML – Activity DiagramsPlease note that all deliverables must be submitted electronically as MS Word format.15 Tasks for Next