CSE4939W/4940 CS & E Design Lab I/II

1. CSE4939W/4940 CS & E Design Lab I/II Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 191 Auditorium Road, Box U-155 Storrs, CT 06269-3155 steve@engr.uconn.edu http://www.engr.uconn.edu/~steve (860) 486 - 4818

2. Course Goals and Objectives • Fall 2012, Year-Long Capstone Design Project • CSE4939W: First Project Based Course • Concentration on Design/Documentation • Analysis of Specification/Project Scope • Three Mini-Demonstrations in First 7 Weeks • Two Prototypes in Week 10 and 14 • Final Project Materials Set up for CSE490X • CSE4940: Follow-On Project Based Course • Emphasis on Incremental Development • Deliver 5 Increments – Aim for Final Beta • Extensive Testing Throughout Semester • Final Presentation at Gampel

3. Student, Instructor, and Supervisor Roles • Student’s 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 • CSE Faculty or Industrial Supervisor

4. CSE4939W: Course Philosophy • Demonstrate Ability to Work as a Group with Minimal or No Guidance • Develop Specification,, Design, and other Documents Throughout Semester • Team Organizes, Plans, Designs, Prototypes, and Delivers! • Periodic Updates and “Current” Web Repositories • As W course, at least 15 single-spaced pages that go through editorial process

5. CSE4940: Course Philosophy • Transition into a Strong Development and Testing Process with Prototype and Management Plan • Maintain an Updated Design – Key Requirement in Commercial Develop • Evaluate Realistic Issues • Plan Five Prototypes over the Course of Semester • Weeks 5, 8, 10, 12, and 14 • Update/Revise PT/Mgmt Plan • Each Prototyped by Testing: • Unit/White Box, User Interface, Black Box Testing, General Performance Testing, SWQ Assessment

6. Identify Problem Develop Detailed Specification Interactions and Feedback Explore Design Alternatives Detailed Design and Testing Implementation and Integration Team Interactions and Dynamics Setting and Meeting Milestones Evaluating Success/Failure CSE4939W First Time Guidance/Oversight Instructor Hands-On Manager and Troubleshooter Coordinate Major Design Experience Evaluate Results CSE4940 Continuation Mostly Team Driven Instructor as Mentor Course Process and Overview

7. CSE4939W Deliverables • Detailed Written Specification • Assessment Of Software Qualities • Detailed Documented Design • Design Patterns, UML and ER Diagrams • Prototyping and Management Plan • Proof of Concept Prototyping (Weeks 9, 11 and 14) • Project Management via Process Model and github • Final Documentation

8. CSE4940 Deliverables • Revised Documented Design • Design Patterns, UML and ER Diagrams • Weeks 2, 8, and 14 • Prototyping and Management Plan • Week 2 – for five increments • Revisions Weeks 5, 8, 10, 12, and 14 • Realistic Issues: • Week 4 • Proof of Concept Prototyping • Weeks 5, 8, 10, 12, and 14 • Project Management via Process Model and github • Final Documentation and SDP Demo (Gampel)

9. Project Teams/Software Process Models • Team Size: • 4 to 6 Members per Team • Last Fall 5 per Team • OK to Organize Teams Across Sections • Supervision • Instructor will Provide Feedback as Primary Grader • CSE Sponsored Project – Faculty Member Involved will Provide Input • Industry Sponsored Project – Expect to work with Industry Personnel

10. Project Management Requirements • Documentation/Source Code • http://about.github.uconn.edu/ • Teams A, B, C, D, E, F, G, H • Instructor/Supervisor have Access • Software Development Model (SDM) • Team Chooses their Own Model • Recommend: Spiral, Agile, Unified Process • Notes: • Deadlines for Various Documents are Same Regardless of SDM • SDM will have more Impact on Prototyping • W Requirements and Standards for Documentation Dictate Deadlines

11. CSE4939W DeadlinesSubject to Change

12. CSE4939W DeadlinesSubject to Change

13. CSE4939W DeadlinesSubject to Change

14. CSE4940 DeadlinesSubject to Change

15. CSE4940 DeadlinesSubject to Change

16. Documentation Requirementsand Lab Facilities • All Project Specifications (Written Documents) Must be Done using: • MS Word • All Project Presentations Must be Done Using Powerpoint (PPT) • Utilize Samples on Web Page for Spring 2012 • Submit Only Electronic Versions • Email Instructions for Each Submittal Throughout the Semester • SDP Lab C13 • Windows PCs • 3 New iMacs

17. Potential Projects • Homer Babbage Library Projects: DOC and  PDF • SpoonfedMD Med Student Education App: DOCand  PDF • TestProFun Theatre Game/App: DOCand  PDF • medadherene.com Tablet Application: PDF • NOTE: Apple Project students need Apple PCs or Laptops

18. Today’s Remaining Tasks – CSE4939W • Review of Project Proposal and Project Specification • Present Project Proposals • Sponsor Presentations • Exchange Email and Phone Numbers • Discuss Project Ideas • Choosing Teams - Teams of 4-6 people • First Project Due – 3 days after first class at 9am - Expect Feedback by End of Day • First Project Presentation – 2nd class • 5 to 10 minutes per team • Copy of Slides/Create & Post on Web Page

19. 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 at 9am 3 days after first class by email. • 5 Slide Presentation at 2nd class (Sept 10th) • See St Francis Patient Mobile App Example • Course Web Page • Submissions, Grading, Revisions • Most Documents Covered

20. CSE4939W Project Specification(Week 3, Original; Week 5 Revised) • Web Links: • http://www.engr.uconn.edu/~steve/Cse4939W/ProjSpec.doc • http://www.engr.uconn.edu/~steve/Cse4939W/ProjSpec.pdf • At most 8 pages (Single spaced, 12 pt, 1 in margs) • Focus on: • Purpose, Objective, Goals • http://www.engr.uconn.edu/~steve/Cse4939W/specif.pdf • High-Level Software Architecture • http://www.engr.uconn.edu/%7Esteve/Cse4939W/SWArchExs.ppt • User-Based Specification – Screen Mockups • Use, Number, and Cite Figures • Explain Figures with Accompanying Text • Each Student Clearly Identifies their Section • Due on Monday, September 17 (Week 3)

21. CSE4939W Software Quality Assurance (Week 4, Original; Week 6 Revised) • 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

22. Today’s Remaining Tasks – CSE4940 • Quick Demos of all Projects (5 mins each) • Reaffirm Teams and Teammates • Limited Switching Allowed • Want to Maintain 5 person Teams if Possible • Week 2 Deliverable • Revised Design • Suggest Reverse Engineering • Code to UML Diagrams • DB to Create Statements or ER Diagram • Week 4 Deliverable – Realistic Issues • Talking About Testing

23. Talking About Testing– CSE4940 • Test Across all Five Increments • Week 5: Module Testing with JUnit • Week 8: GUI/User Interface Testing with Scenarios, Scripts, and Outputs • Week 10: Black Box – Teams test other Teams Software • Week 12: General Performance Testing (Stress testing, algorithm performance, load, #users, etc.) • Week 14: Demonstrating SWQualities – Maintainability, Evolvability, and User Friendly • Each Team Member in Charge of One Testing • All Team Members Particpate