CSE4939W/4940 CS & E Design Lab I/II

1. 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. Course Goals and Objectives • CSE4939W, CSE 4940: • Year-long sequence of two courses. • Emphasis on Incremental Development via an Agile Approach • Deliver 4-6 Increments – Aim for Final Beta • Extensive Testing Throughout Semester • Final Poster/Presentation at Gampel

3. Student, Instructor, and Supervisor Roles • Student Team Role • You Control Project - “Group Independent Study” • You Make Decisions, Resolve Problems, etc. • You “Apply” your Coursework/Experiences • Instructor’s Role • Provide a Set of Potential Project Topics • Serve as Manager (and Primary Grader), Organize Meetings, Questions, etc. • Supervisor’s Role • Uconn/UCHC Faculty or Industrial Supervisor

4. Philosophy of the Sequence • Demonstrate Ability to Work as a Group with Minimal or No Guidance • Team Organizes, Plans, Designs, Prototypes, and Delivers! • Employ an Agile Approach – see: • www.engr.uconn.edu/~steve/Cse2102/finagile.pptx • scrumreferencecard.com • scrumreferencecard.com/ScrumReferenceCard.pdf • scrumreferencecard.com//ScrumMasterChecklist.pdf • As W course, at least 15 single-spaced pages that go through editorial process

5. What is the Course Approach? • Identify Problem/Proposal • Develop Initial Architecture/Specification • Product Backlog is the list of tasks • Purpose, Objectives, Goals Defines Product • High-Level Architecture Diagram • Revise Architecture/Specification Based on Input • Scrum is a Incremental Approach of Multiple Sprints • Develop Initial Sprint that Contains • Section A. Sprint Backlog • Section B: User Stories/Use Cases • Section C: User Based Specification/Interfaces • Section D: Detailed Design • Section E: Test plans • Sprint is Continuously Updated Throughout Year

6. What is a Sprint? • A Time-Limited (2-4weeks) Complete Increment that has: • Evaluation/Prioritization of to-do-list of tasks • Detailed Requirements • Design & Analysis • Implementation & Developer Testing • QA/Acceptance Testing & Deployment • Sprint Document Organized as • Section A. Sprint Backlog – What to do Next • Section B: User Stories/Use Cases - Functionality • Section C: User Based Specification/Interfaces • Section D: Detailed Design – UML, ER, etc. • Section E: Test plans- White-Box, Black box, etc. • This Document Evolves and Expands Throughout Year

7. Schedule – Fall 2014, Spring - TBD

8. Project Teams/Software Process Models • Team Size: • 4 – 6 Members per Team • With 15 students, Target 5 per Team • OK to Organize Teams Across our two Sections • Supervision • Instructor will Provide Feedback as Primary Grader • Uconn/UCHC Sponsored Project – Faculty Member Involved will Provide Input • Industry Sponsored Project – Expect to work with Industry Personnel

9. Documentation Requirementsand Lab Facilities • All Project Material (Project Proposal, Spec, Sprints, User Manual, etc.) • MS Word, PPT, Excel • All Project Presentations Must be Done Using Powerpoint (PPT) • Submit Only Electronic Versions • Email Instructions for Each Submittal Throughout the Semester • SDP Lab C13 • Windows PCs • 3 iMacs

10. UConn/UCHC Projects • UConn Forestry - MyWoods • UConn Extension - StreetSheetHunger • UConn Plant Science- IPMApp • UConn CommSci/Allied Health- HealthyEating • UConn Natural Resources – Stormwise • UConn Extension – CTGrown 10% • UCHC Occup Environ Med - MoldResponse • Note APP Competition by UConn Extensions CAHNR • $1500 first, $1000 second, $500 third • Due April 1, 2015 • Winners to Regional Competition (TBD)

11. UConn Extension APP Challenge with CAHNRFirst Six UConn Projects • $1500, $1000, $500; Due April 1, 2015 • Winners to Regional Competition (TBD) • www.engr.uconn.edu/~steve/Cse4939W/UConnExtensionAppChallenge.pdf • Significant Interactions with Sponsor as Customer • Pull out requirements • Design Mock-ups and Obtain Approval • Try to Finalize UI by Dec 1, 2014 • Strongly Suggest Android • Ease of use for Input (send apk) • iOS/Apple Very Difficult to Deploy/Distribute • Server/Database usable Cross Platform • Rest APIs • Other Web Services

12. Sample Android Code/App Provided • Provide a Sample App • Splash Screen (with button to leave) • Login Screen • Sample of Various Tabs and use of • Data Entry for Text • Date Pickers • Options with Radio Buttons (Select only 1) • Options with Select Boxes (Select one or more) • See sample.zip for the Android Eclipse zip • Android and Eclipse SDK • Web link developer.android.com/sdk/index.html • Install www.engr.uconn.edu/~steve/Cse4939W/androidinstall.docx

13. Screenshots from sample.apk

14. Screenshots from sample.apk

15. Screenshots from sample.apk

16. Industry Sponsored Projects • To be Defined • Notify as soon as we hear from CSE leadership

17. Today’s Remaining Tasks – CSE4939W • Choosing Teams • Teams of 5 people - Across Our Sections OK • Project Proposal • Assigned 8/27 – Due 9/2 – Revised 9/10 • High-Level Specification • Assigned 9/3– Due 9/10– Revised 9/17, 02/04/2015, 3/25/2015 • First Sprint/Scrum • Assigned 9/3 – Due 9/24 – Revised 10/29 • Second Sprint/Scrum • First Draft Due 10/29 – Revised 12/3 • Third Sprint/Scrum • First Draft Due 12/3 – Revised 01/28/2015