1. OV-1.1 CSE4939 CSE4940 CSE4939W/4940 CS & E Design Lab I/II Profs. Steven A. Demurjian and Swapna Gokhale Computer Science & Engineering Department The University of Connecticut 191 Auditorium Road, Box U-155 Storrs, CT 06269-3155 {steve,ssg}@engr.uconn.edu http://www.engr.uconn.edu/~steve/Cse4939W/cse4939W.html

2. OV-1.2 CSE4939 CSE4940 Projects and Deliverables – Now to Oct 1  CSE4939W: First Project Based Course  Concentration on Architecture, Specification, and Design  Emphasis on Incremental Development via an Agile Approach  Deliver 2 Increments  CSE4940: Continuation of the Project  Emphasis on Incremental Development  Deliver 3 Increments – Aim for Final Beta  Extensive Testing Throughout Semester  Final Poster/Presentation at Gampel

3. OV-1.3 CSE4939 CSE4940 Schedule – Fall 2015, Spring - TBD AssignmentAssignedFirst DraftRevised Version (if any) Project ProposalSept. 9Sept. 12Sept. 16 High-level SpecificationSept. 16Sept. 23Sept. 30 Dec. 11 Jan. 27 First Sprint/ScrumSept. 23Sept. 30Oct. 7 Second Sprint/ScrumNov. 4Nov. 11 Third Sprint/ScrumDec. 11Jan. 27

4. OV-1.4 CSE4939 CSE4940 CSE4939W Project Proposal  Web Links:  http://www.engr.uconn.edu/~steve/Cse4939W/ProjProp.doc  http://www.engr.uconn.edu/~steve/Cse4939W/ProjProp.pdf  1 to 2 page proposal due Sept 12 th by 5pm  Feedback by Sept 14 th, 12noon  Revised Proposal due Sept 16 th  See Three Examples on Web Page  Team A: Drones http://www.engr.uconn.edu/~steve/Cse4939W/TeamAProposal.docx  Team D: Rooms http://www.engr.uconn.edu/~steve/Cse4939W/TeamDProposal.docx  Team G: Personal Health Assistant http://www.engr.uconn.edu/~steve/Cse4939W/TeamGProposal.docx

5. OV-1.5 CSE4939 CSE4940 CSE4939W High Level Specification  Web Links:  http://www.engr.uconn.edu/~steve/Cse4939W/ProjArchSpec.doc  http://www.engr.uconn.edu/~steve/Cse4939W/ProjArchSpec.pdf  6-8 pages (Single spaced, 12 pt, 1 in margs)  Product Backlog – See Next Two Slide  Purpose, Objective, Goals  Introduction, Glossary, Operating Environment  Information, Performance, Security  http://www.engr.uconn.edu/~steve/Cse4939W/specif.pdf  High-Level Software Architecture  http://www.engr.uconn.edu/~steve/Cse4939W/SWArchExs.ppt  Each Student Clearly Identifies their Section  Due on September 23; Revised September 30  Again – Samples for Teams A, D, and G

6. OV-1.6 CSE4939 CSE4940 Product & Sprint Backlogs – Rooms

7. OV-1.7 CSE4939 CSE4940 Product & Sprint Backlogs – PHA

8. OV-1.8 CSE4939 CSE4940 CSE4939W Initial Sprint Due Sept. 30  Contains Six Sections:  Section A. Sprint Backlog  Section B: User Stories/Use Cases  Section C: User Based Specification/Interfaces  Section D: Detailed Design  Section E: Test plans  Section F: Product Backlog Items (PBI) (see slides 6/7)  Focus on the RED HIGHLIGHTED sections only  Samples on web page: http://www.engr.uconn.edu/~steve/Cse4939W/TeamAInitSprint.docx http://www.engr.uconn.edu/~steve/Cse4939W/TeamDInitSprint.docx http://www.engr.uconn.edu/~steve/Cse4939W/TeamGInitSprint.docx

9. OV-1.9 CSE4939 CSE4940 CSE4939W Initial Sprint – Requirements Due Sept. 30  Section A. Sprint Backlog  Section B: User Stories/Use Cases  5 to 7 use cases with actors  Section C: User Based Specification/Interfaces  4 to 6 GUI Mockups  Section D: Detailed Design  Add 5 new Diagrams per Sprint  Section E: Test plans  Section F: Product Backlog Items (PBI) (see slides 6/7)  Update with Changes at end of Sprint  Used to Generate New Sprint Backlog

10. OV-1.10 CSE4939 CSE4940 Successive Sprint - Requirements  Section A. Sprint Backlog  Section B: User Stories/Use Cases  5 to 7 use cases with actors  Section C: User Based Specification/Interfaces  4 to 6 GUI Mockups  Section D: Detailed Design  Version Due November 10: Initial 10 Diagrams  Subsequent Versions – Update Existing and Add 5 Diagrams  Section E: Test plans  Section F: Product Backlog Items (PBI)  Update with Changes at end of Sprint  Used to Generate New Sprint Backlog

11. OV-1.11 CSE4939 CSE4940 Section A. Sprint Backlog For Initial and All Successive Sprints   For each sprint item, there is:  Primary and secondary individual in charge of the item (initials)  The different task for the PBI in the sprint.  Effort in hours for weeks 1, 2, 3, and 4   For Each Week  Each member has 10 hours  50 hours effort per team   For Entire Sprint  Each member has 40 hours  200 hours effort per team

12. OV-1.12 CSE4939 CSE4940 Section A. Sprint Backlog

13. OV-1.13 CSE4939 CSE4940 Section A. Sprint Backlog

14. OV-1.14 CSE4939 CSE4940 Section B: User Stories/Use Cases Initial 5-7, Successive Modify/Add

15. OV-1.15 CSE4939 CSE4940 Section B: User Stories/Use Cases Initial 5-7, Successive Modify/Add

16. OV-1.16 CSE4939 CSE4940 Section C: User Specification/Interfaces Initial 4-6, Successive Modify/Add

17. OV-1.17 CSE4939 CSE4940 Section C: User Specification/Interfaces Initial 4-6, Successive Modify/Add

18. OV-1.18 CSE4939 CSE4940 Section D: Detailed Design Not on Initial Sprint, 10 for Sprint Nov 4

19. OV-1.19 CSE4939 CSE4940 Section D: Detailed Design Not on Initial Sprint, 10 for Sprint Nov 4

20. OV-1.20 CSE4939 CSE4940 Section E: Test plans Not on Initial Sprint, 10 for Sprint Nov 4

21. OV-1.21 CSE4939 CSE4940 Section E: Test plans Not on Initial Sprint, 10 for Sprint Nov 4

22. OV-1.22 CSE4939 CSE4940 CSE4940 Software Quality Assurance Due Spring 2016  Web Links:  http://www.engr.uconn.edu/~steve/Cse4939W/ProjSWQ.doc  http://www.engr.uconn.edu/~steve/Cse4939W/ProjSWQ.pdf  Qualities are:  Performance Portability  Understandability Productivity  Reliability User Friendliness  Robustness Repairability  Reusability Maintainability  Interoperability Evolvability  Each Team Member Does 2 Qualities  Importance and Relevance  Attainment of Quality in your Specifacation  ½ page, 12 pt, single spaced per Quality