Presentation is loading. Please wait.

Presentation is loading. Please wait.

 1998-05 Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San.

Similar presentations


Presentation on theme: " 1998-05 Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San."— Presentation transcript:

1  1998-05 Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San José State University One Washington Square San José, CA 95192-0180 http://www.engr.sjsu.edu/~fayad, m.fayad@sjsu.edu

2 L2c-S2 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad 2 Lecture 2c: Documenting Software Processes - 2

3 L2c-S3 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad Lesson Objectives 3 Understand the recommendations for documenting process. Discuss the essential process elements Understand how to document S/W processes Template Symbolic notation UML – activity diagram

4 L2c-S4 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad RECOMMENDATIONS 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 –customers 4

5 L2c-S5 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad E SSENTIAL OO P ROCESS E LEMENTS 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 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 objects 5

6 L2c-S6 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad INTEGRATED GRAPHICAL/ TEXTUAL DOCUMENTATION RECOMMENDED graphics maximize communication text expands detail graphics maximize communication text expands detail 6

7 L2c-S7 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad LESSONS 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 process 7

8 L2c-S8 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad OO DEVELOPMENT PROCESS SUMMARY 1. Processes map software methods from the classroom to the computer room –translate theory to action 2.Processes especially important for new OO development teams –maximizes individual contributions 3.Processes must be tuned for specific projects –tuned for specific attributes 4.Integrated graphics and text provide effective documentation format –eases communication and maintenance 1. Processes map software methods from the classroom to the computer room –translate theory to action 2.Processes especially important for new OO development teams –maximizes individual contributions 3.Processes must be tuned for specific projects –tuned for specific attributes 4.Integrated graphics and text provide effective documentation format –eases communication and maintenance 8

9 L2c-S9 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad Process Documentation Template Micro-Development Process – Software Inspection 9 Process Documentation – Template & Example

10 L2c-S10 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad 10 Process Documentation – Symbolic Notation Input description -- Process inputs i,e. tools & information Transition Arrow Role 1 Role 2 Role N Participants Chart Output description -- Process outputs i,e. tools, manual, & information Process Step Name Roles

11 L2c-S11 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad 11 Process Documentation – Symbolic Notation Decision Diamond Yes No Filled Process Box Parallelogram shows concurrency Parallel Process Step Parallel Process Step

12 L2c-S12 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad 12 Process Documentation – Symbolic Notation - Example

13 L2c-S13 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad Name the roles in the following software processes –Spiral Model –Requirement Engineering –Software Testing –Software Review –Interaction Diagram –Class Diagram –Software development planning 13 Discussion Questions

14 L2c-S14 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad Activity Diagram 14 Questions for the Next Lecture

15 L2c-S15 Doc. Processes  1998-05 Fayad SJSU -- CmpE M.E. Fayad Task 1: Read Appendix A – Fayad’s Book & any materials on UML – Activity Diagrams Please note that all deliverables must be submitted electronically as MS Word format. 15 Tasks for Next Lecture


Download ppt " 1998-05 Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San."

Similar presentations


Ads by Google