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.

Slides:



Advertisements
Similar presentations
Project Analysis Course ( ) Final Project Report Overview.
Advertisements

1 CS Tutorial 2 Architecture Document Tutorial.
Guidelines for honors theses for Computer Science, Computer Systems Engineering, and Informatics March 2013.
Introduction to CS 491 / 2 Senior Design Project I / II Prof. Dr. H. Altay Güvenir.
FE.1 CSE 4701 CSE4701 Final Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
OV-1.1 CSE4701 CSE4701 Introduction to Databases Prof. Steven A. Demurjian Computer Science & Engineering Department The University of Connecticut 371.
OV-1.1 CSE4100 CSE4100 Programming Language Translation Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
Team READ THIS SLIDE CAREFULLY Beta Demonstrations will be given by each team at our all-hands meeting on the dates listed at All-Hands Meeting Agendas.All-Hands.
OV-1.1 CSE4939 CSE4939 CS & E Design Laboratory Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
READ THIS SLIDE CAREFULLY The intent of this presentation is to provide an “Executive Summary” of your project to Design Day attendees and judging panel.
7. Team Project Schedules September 22, 2004 Wayne Dyksen Brian Loomis Department of Computer Science and Engineering Michigan State University Fall 2004.
Technical Specification / Schedule Department of Computer Science and Engineering Michigan State University Spring 2007 Team : CSE 498, Collaborative Design.
General information CSE 230 : Introduction to Software Engineering
1 CS 425 / CS 625 Software Engineering Fall 2007 Course Syllabus August 27, 2007.
Online Peer Evaluation System Team Green Apple Team Members Ada Tse Amber Bahl Tom Nichols Matt Anderson Faculty Mentor Prof. M Lutz Project Sponsor Richard.
CSE 322: Software Reliability Engineering Topics covered: Course outline and schedule Introduction, Motivation and Basic Concepts.
Computer Science ABET Visit Update November 8, 2003.
Slide 1 Instructor: Dr. Hong Jiang Teaching Assistant: Mr. Sheng Zhang Department of Computer Science & Engineering University of Nebraska-Lincoln Classroom:
Department of Computer Science Requirements Analysis for Complex Software Systems Vereistenanalyse voor complexe softwaresystemen.
S9k Preventive Maintenance & Equipment Inventory.
DESIGN REVIEW DECEMBER 11, 2009 Databases and Innovative Systems for the community 1.
Project Requirements COP 4331 OO Processes for Software Development © Dr. David A. Workman School of EE and CS University of Central Florida March 22,
230EA.1 CSE 2102 CSE2102 Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 271.
Project Analysis Course ( ) Final Project Report Overview Prepared by: Sijali Petro Korojelo (Course Assistant)
OV-1.1 CSE2102 CSE2102 Intro to Software Engineering Prof. Steven A. Demurjian, Sr. Director, CS&E Graduate Program Computer Science & Engineering Department.
Introduction to Information and Computer Science Information Systems Lecture b This material (Comp4_Unit9b) was developed by OHSU, funded by the Department.
Web Trnsport – Beta Testing and Implementation TUG Roundtable Discussion Elizabeth Rodgers Info Tech, Inc. October 9, 2007.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
OV-1.1 CSE4939 CSE4940 CSE4939W/4940 CS & E Design Lab I/II Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of.
Course Introduction Software Engineering
Dr. John Lowther, Associate Professor of CS Adjunct Associate Prof. of Cognitive and Learning Sciences Computer Graphics:
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
FP OntoGrid: Paving the way for Knowledgeable Grid Services and Systems Communication in the consortium Review meeting Delft,
OV-1.1 CSE4939 CSE4940 Reviewing Concepts  The Agile Methodology   scrumreferencecard.com/ScrumReferenceCard.pdf.
Geographic Information Systems GEO481/506, Fall 2012 Tu Th 2:30-3:20pm, NSC 210 The course is offered three times a year.
Introduction to CS Senior Design Project I / II Prof. Dr. H. Altay Güvenir.
Lab Course / Praktikum: S ummer Semester 2012 Project Management and Software Development for Medical Applications Computer Aided Medical Procedures (CAMP),
Computer Science and Software Engineering© 2014 Project Lead The Way, Inc. Software Design Process.
Final Exam Review Session 14 LBSC 790 / INFM 718B Building the Human-Computer Interface.
Fall 2011 Course Syllabus Instructor: Sergiu Dascalu Department of Computer Science and Engineering August 30,
CSE 436—Software Development Models Ron K. Cytron 10 October 2005.
Senior Projects Meeting 7 September 9, Agile Development Process The players are Product owner: sets priorities, owns in the sense of is responsible.
Fall 2012 Professor C. Van Loan Introduction to CSE Using Matlab GUIs CS 1115.
Meghe Group of Institutions Department for Technology Enhanced Learning 1.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Client Senior Design Electrical and Computer Engineering Iowa State University Introduction Abstract Architectural plans are currently being developed.
Project Management Requirements Prof. Ralph Locurcio, PE Dr. Troy Nguyen, PE.
CSE 403, Spring 2008, Alverson CSE 403 Software Engineering Pragmatic Programmer Tip: Care about Your Craft Why spend your life developing software unless.
OV-1.1 CSE262 CSE293 CSE262 Software Engineering Laboratory CSE293 CS & E Design Laboratory Prof. Steven A. Demurjian, Sr. Computer Science & Engineering.
10 Aug 2010 ECE/BENG-492 SENIOR ADVANCED DESIGN PROJECT Meeting #6.
OV-1.1 CSE230 CSE230 Introduction to Databases Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 371.
DigitalHC-1 CSE 5810 Digital Healthcare Security Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Exam 0 review CS 360 Lecture 8.
<workgroup name>
Introduction to CS Senior Design Project I / II
Software Support Framework
CSE4102 Team Project Prof. Steven A. Demurjian
Introduction to CS Senior Design Project I / II
Introduction to CS Senior Design Project I / II
Computer Networks CNT5106C
CSE255 Final Exam Advice and Hints
CSE4939W/4940 CS & E Design Lab I/II
Team [Team Name] Beta Presentation
Bourke properties Houston, Whitney relocation info 23/02/2019.
Read Me (Delete this slide.) (1 of 2)
Introduction to CS Senior Design Project I / II
Team [Team Name] Beta Presentation
CSE4939W/4940 CS & E Design Lab I/II
Presentation transcript:

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

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

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

OV-1.4 CSE4939 CSE4940 CSE4939W Project Proposal  Web Links:    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  Team D: Rooms  Team G: Personal Health Assistant

OV-1.5 CSE4939 CSE4940 CSE4939W High Level Specification  Web Links:    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   High-Level Software Architecture   Each Student Clearly Identifies their Section  Due on September 23; Revised September 30  Again – Samples for Teams A, D, and G

OV-1.6 CSE4939 CSE4940 Product & Sprint Backlogs – Rooms

OV-1.7 CSE4939 CSE4940 Product & Sprint Backlogs – PHA

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:

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

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

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

OV-1.12 CSE4939 CSE4940 Section A. Sprint Backlog

OV-1.13 CSE4939 CSE4940 Section A. Sprint Backlog

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

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

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

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

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

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

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

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

OV-1.22 CSE4939 CSE4940 CSE4940 Software Quality Assurance Due Spring 2016  Web Links:    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