CSE4939W/4940 CS & E Design Lab I/II CSE4939 CSE4940 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 OV-1.1 Projects and Deliverables Now to Oct 1
CSE4939 CSE4940 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 OV-1.2
Schedule Fall 2015, Spring - TBD CSE4939 CSE4940 Assignment Assigned First Draft Revised Version (if any) Project Proposal Sept. 9
Sept. 12 Sept. 16 High-level Specification Sept. 16 Sept. 23 Sept. 30 Dec. 11 Jan. 27 First Sprint/Scrum Sept. 23
Sept. 30 Oct. 7 Second Sprint/Scrum Nov. 4 Nov. 11 Third Sprint/Scrum Dec. 11 Jan. 27 OV-1.3
CSE4939W Project Proposal Web Links: CSE4939 CSE4940 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 12th by 5pm Feedback by Sept 14th, 12noon Revised Proposal due Sept 16th 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 OV-1.4 CSE4939W High Level Specification
Web Links: CSE4939 CSE4940 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 OV-1.5 Product & Sprint Backlogs Rooms CSE4939 CSE4940
OV-1.6 Product & Sprint Backlogs PHA CSE4939 CSE4940 OV-1.7 CSE4939W Initial Sprint Due Sept. 30 CSE4939 CSE4940
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 OV-1.8 CSE4939W Initial Sprint Requirements Due Sept. 30
CSE4939 CSE4940 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 OV-1.9 Successive Sprint - Requirements CSE4939 CSE4940 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 OV-1.10 Section A. Sprint Backlog For Initial and All Successive Sprints CSE4939 CSE4940
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 OV-1.11
Section A. Sprint Backlog CSE4939 CSE4940 OV-1.12 Section A. Sprint Backlog CSE4939 CSE4940 OV-1.13 Section B: User Stories/Use Cases Initial 5-7, Successive Modify/Add CSE4939
CSE4940 OV-1.14 Section B: User Stories/Use Cases Initial 5-7, Successive Modify/Add CSE4939 CSE4940 OV-1.15 Section C: User Specification/Interfaces Initial 4-6, Successive Modify/Add CSE4939 CSE4940 OV-1.16
Section C: User Specification/Interfaces Initial 4-6, Successive Modify/Add CSE4939 CSE4940 OV-1.17 Section D: Detailed Design Not on Initial Sprint, 10 for Sprint Nov 4 CSE4939 CSE4940 OV-1.18 Section D: Detailed Design Not on Initial Sprint, 10 for Sprint Nov 4 CSE4939 CSE4940
OV-1.19 Section E: Test plans Not on Initial Sprint, 10 for Sprint Nov 4 CSE4939 CSE4940 OV-1.20 Section E: Test plans Not on Initial Sprint, 10 for Sprint Nov 4 CSE4939 CSE4940 OV-1.21 CSE4940 Software Quality Assurance
Due Spring 2016 Web Links: CSE4939 CSE4940 Qualities are:
http://www.engr.uconn.edu/~steve/Cse4939W/ProjSWQ.doc http://www.engr.uconn.edu/~steve/Cse4939W/ProjSWQ.pdf 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 OV-1.22
