CSE 4939 CSE 4939 CSE Design Laboratory Prof. Aggelos Kiayias Computer Science & Engineering Department The University of Connecticut 371 Fairfield Way,

Slides:



Advertisements
Similar presentations
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Advertisements

Static Structure: Process Description
Unified Modeling Language
Introduction To System Analysis and Design
OV-1.1 CSE4100 CSE4100 Programming Language Translation Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
January 2007 CSE 293 CS & E Design Laboratory Prof. Alexander A. Shvartsman Computer Science & Engineering Department The University of Connecticut 371.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
SE 470 Software Development Processes James Nowotarski 21 April 2003.
OV-1.1 CSE4939 CSE4939 CS & E Design Laboratory Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut.
General information CSE 230 : Introduction to Software Engineering
CSE 4939 CSE 4939 (293) CSE Design Laboratory Prof. Alexander A. Shvartsman Computer Science & Engineering Department The University of Connecticut 371.
1 UML Component and Deployment Diagrams. Models, Views, and Diagrams Use Case Diagrams Use Case Diagrams Use Case Diagrams Scenario Diagrams Scenario.
OV-1.1 CSE244 CSE244 Programming Language Translation Aggelos Kiayias Computer Science & Engineering Department The University of Connecticut 371 Fairfield.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
IT 499 Bachelor Capstone Week 9.
Introduction to Information System Development.
Introduction to Interactive Media 02. The Interactive Media Development Process.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 1: Best Practices of Software Engineering.
230EA.1 CSE 2102 CSE2102 Exam Advice and Hints Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 271.
Paul Bourke DT211/3 & DT228/3 Team Project Paul Bourke Module Web Page:
OV-1.1 CSE2102 CSE2102 Intro to Software Engineering Prof. Steven A. Demurjian, Sr. Director, CS&E Graduate Program Computer Science & Engineering Department.
Tablet PC Capstone CSE 481b Richard Anderson Craig Prince.
IT 499 Bachelor Capstone Week 8. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary.
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.
Object Oriented Programming (OOP) Design Lecture 1 : Course Overview Bong-Soo Sohn Associate Professor School of Computer Science and Engineering Chung-Ang.
Spring 2011 CIS 4911 Senior Project Catalog Description: Students work on faculty supervised projects in teams of up to 5 members to design and implement.
Teaching an Object-Oriented Software Development Lifecycle in Undergraduate Software Engineering Education February 27, 2002 Professor Brian Blake Georgetown.
Prof. Barbara Bernal NEW Office in J 126 Office Hours: M 4pm - 5:30 PM Class Lecture: M 6 PM - 8:30 in J133 Weekly Web Lecture between Tuesday to Sunday.
Introduction To System Analysis and Design
11 Partnership for Performance How to hear this lecture Click on the icon: to hear the narration for each slide.
Requirements Analysis Visual Modeling] Lab 02 Visual Modeling (from Visual Modeling with Rational Rose and UML) A way of thinking about problems using.
BUS 1040 Project Management Week 10 Let’s get a sense of direction Presented by Professor Fred Pentney.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 121 Software Design I Lecture 10.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
TAL7011 – Lecture 4 UML for Architecture Modeling.
2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Systems Analysis and Design in a Changing World, Thursday, Feb 15.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
ECE791 Senior Design Experience Project Requirements and Timeline.
Commission on Teacher Credentialing Ensuring Educator Excellence 1 Program Assessment Technical Assistance Meetings December 2009.
® IBM Software Group © 2007 IBM Corporation Module 1: Getting Started with Rational Software Architect Essentials of Modeling with IBM Rational Software.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Fall 2007 Week 9: UML Overview MSIS 670: Object-Oriented Software Engineering.
1 Architectural Blueprints—The “4+1” View Model of Software Architecture (
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
OV-1.1 CSE262 CSE293 CSE262 Software Engineering Laboratory CSE293 CS & E Design Laboratory Prof. Steven A. Demurjian, Sr. Computer Science & Engineering.
OV-1.1 CSE230 CSE230 Introduction to Databases Prof. Steven A. Demurjian, Sr. Computer Science & Engineering Department The University of Connecticut 371.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
Working in Groups in Canvas
ECE361 Engineering Practice
Object-Oriented Analysis and Design
Unified Modeling Language
Introduction to Unified Modeling Language (UML)
Informatics 121 Software Design I
CSE4939W/4940 CS & E Design Lab I/II
Unified Modeling Language
Software Design Lecture : 15.
Uml diagrams In ooad.
CSE4939W/4940 CS & E Design Lab I/II
Presentation transcript:

CSE 4939 CSE 4939 CSE Design Laboratory Prof. Aggelos Kiayias Computer Science & Engineering Department The University of Connecticut 371 Fairfield Way, Unit 2155 Storrs, CT (860) Course material credits : Professors Shvartsman, Demurjian, Huang, and the instructor.

CSE 4939 Course Goals  CSE 4939: The “Second” Project Based Course  Follows CSE 261, 262, 263, 265, 268, 269  Similar Goals and Objectives but…  You control project - “Group Independent Study”  You make decisions, resolve problems, etc.  You apply your coursework and experiences  What is the Instructor’s Role?  Guide teams on potential project topics  Provide structural framework for the course  Present requirements for specifications, provide templates  Facilitate/organize meetings, respond to questions, etc.

CSE 4939 CSE 4939 Course Philosophy  CSE 4939: senior-level, team-based, design-oriented, writing-intensive, implementation-heavy course  Demonstrate ability  to work as a group  with minimal or no guidance  Team organizes, plans, specifies, designs, prototypes, implements, tests, reports, delivers!  Periodic updates  Using the web for delivery of material.

CSE 4939 Course Process and Overview  Identify Problem  Develop Specifications  Interactions and Feedback  Explore Design Alternatives  Detailed Design and Testing  Implementation & Integration  Team Interactions and Dynamics  Setting and Meeting Milestones  Evaluating Success/Failure  CSE Lab 1 (40XX / 26X)  First time through  Lots of guidance  Suggestions & advice  Instructor as manager  CSE 4939  Second Time  Minimal Guidance  Instructor as mentor, facilitator, coordinator  Major design experience - Implement / evaluate

CSE 4939 Texts and Class Materials  Primarily project-specific – gathered by the team  CSE 4939 web site.   Assignments and auxiliary documents  Legacy CSE 293 web site at   Older course materials made available on-line

CSE Semester Schedule  Milestone I: Teams formation and preliminary project idea – (due Jan. 26 th in forum).  Milestone II: Functional Specification – (due Feb. 9 th in forum and class).  Revised Specification – (due Feb 16 th in forum)  Milestone III : High Level Design – (due Feb. 23 rd in forum and class)  Detailed Design Extract – (due March 2 nd in forum)  Milestone IV : Development/Mgmt. Plan – (due March 16 th in forum and class).  Deliverable on Realistic Issues for product development – (due March 23 rd in forum).  Release 1 / Report – due March 30 th in forum.  Release 2 / Report and Presentation – due April 6 th in forum and class.  Release 3 / Report and Presentation – due April 27 th in forum and class.  Final Report/User Manual – due May 3 rd in forum.

CSE Specification!  Typical discussion  User to developer: “The system is not operating as specified!”  Developer to user: “No, the system is behaving exactly as specified!”  How can they both be right?  How to avoid this?

Lateness  Late submissions will not be allowed.  Teams that deliver late will have a penalty in their deliverable grade that may affect their final grade. Penalties accrue with every day a deliverable is late. CSE

Example: Using UML  Typical project will be UML Based  UML is a Language for Specifying, Visualizing, Constructing, and Documenting Software Artifacts  What Does a Modeling Language Provide?  Model Elements: Concepts and Semantics  Notation: Visual Rendering of Model Elements  Guidelines: Hints and Suggestions for Using Elements in Notation  References and Resources  Web:  “The Unified Modeling Language Reference Manual”, Addison-Wesley.

CSE UML Modeling Constructs/Diagrams Static vs. Dynamic Perspectives  A Diagram is a View Into a Model  Presented From the Aspect of a Particular Stakeholder  Provides a Partial Representation of the System  Is Semantically Consistent With Other Views  In the UML, There Are Nine Standard Diagrams  Static Views: Use Case, Class, Object, Component, Deployment  Dynamic Views: Sequence, Collaboration, Statechart, Activity

CSE 4939 UML Modeling Constructs/Diagrams Classification by Capability/Timeline  Use-Case Diagrams  Class and Object Diagrams  Behavior Diagrams  Statechart Diagrams  Activity Diagrams  Interaction Diagrams  Sequence Diagram  Collaboration Diagram  Implementation Diagrams  Component Diagram  Deployment Diagram

CSE Relationship Between Models and Diagrams Use Case Diagrams Use Case Diagrams Use Case Diagrams Scenario Diagrams Scenario Diagrams Collaboration Diagrams State Diagrams State Diagrams Component Diagrams Component Diagrams Component Diagrams Deployment Diagrams State Diagrams State Diagrams Object Diagrams Scenario Diagrams Scenario Diagrams Statechart Diagrams Use Case Diagrams Use Case Diagrams Sequence Diagrams State Diagrams State Diagrams Class Diagrams Activity Diagrams Models

CSE 4939 Semester Requirements  Summary  Teams of 3 to 5 students  “W” course means 15 pages/team member  Revisions cycles count towards page total  Submission to forum for all materials  Use of IDE or equivalent (e.g., Visual Studio, Eclipse, etc.)  Source Code Control (Subversion or equivalent)  Team and Individual Contributions

CSE 4939 Documentation Packages/Requirements  All Written Documents and Specifications must be submitted in PDF format  All Project Presentations Must be Done Using Powerpoint (PPT)  Where multiple files are involved / needed submit zipped files.

CSE 4939 Projects Considered in the Past  Social/professional networking  Car dealership infosystem  Peoplesoft replacement  Online Poker package with statistics  Marklin Digital Trains  Atari 800 Renovation  Web-Based Journal Editor  Heating System Design and Engineering

CSE 4939 Project/Team Documentation  Each Team will use the class forum for presenting their project. Each team will have its own “board” and in this board all material will be posted.  The board’s threads will be augmented with all the design Documents.  Take advantage of any documentation functionality.  Documentation of Java with Java Doc  Utilize Together Architect.  Utilize an IDE.

CSE 4939 First Class: Tasks  Choosing Teams: 3-5 people  Self-Organized Teams  Instructor Approves Teams  Meet & Brainstorming  Remainder of Class  Exchange and Phone Numbers  Discuss Project Ideas  Visit Prior Web Pages  First task Due January 26 th – Expect Feedback by Friday of that week (through the forum).  First Project Presentation February 9 th  20 to 30 minutes per team  Copy of Slides/Create & Post on forum