1. OV-1.1 CSE262 CSE293 CSE262 Software Engineering Laboratory CSE293 CS & E Design Laboratory 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. OV-1.2 CSE262 CSE293 Course Goals  CSE262: The “First” Project Based Course  Team-Oriented Software Development  Presentations, Reports, Walkthroughs  Exploring and Harnessing New Technologies  Simulate “Real-World” Project  CSE293: 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/Experiences

3. OV-1.3 CSE262 CSE293 Course Philosophy  CSE262:Apply the Software Engineering Process  First Time Through the Process  Guidance, Suggestion, Feedback  Preparation for CSE293  CSE293:  Demonstrate Ability to Work as a Group with Minimal or No Guidance  Team Organizes, Plans, Designs, Prototypes, and Delivers!  Periodic Updates and “Current” Web Repositories

4. OV-1.4 CSE262 CSE293 Course Process and Overview  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  CSE262  First Time Through  Lots of Guidance  Suggestions/Advice  Instructor as “Hands- On” Manager  CSE293  Second Time  Minimal Guidance  Instructor  Mentor and Troubleshooter  Coordinate Major Design Experience  Evaluate Results

5. OV-1.5 CSE262 CSE293 Textbooks and Class Materials  UConn COOP has One Required Text …  The Unified Modeling Language User Guide, Booch, et al., Addison-Wesley, 1999  Recommend “Java Text”  CSE262 Web Site at …  www.engr.uconn.edu/~steve/Cse262/cse262.html  All Course Materials Available On-Line  CSE293 Web Site at …  www.engr.uconn.edu/~steve/Cse293/cse293.html  All Course Materials Available On-Line  Other Important Class Materials  Software Download - Ghostview/Ghostscript  Together Control Center - UML Tool

6. OV-1.6 CSE262 CSE293 Percentages Breakdown for Milestones and Deliverables  300 pts Project Design  75 pts Project 2  125 pts Project 3  100 pts Project 4  300 pts Project Implementation  25 pts PT and Management - Project 5 Plan  20 pts PT Reports  55 pts Project Final Report  100 pts Working PT/Meetings Objectives  100 pts Team Effort and Cohesiveness  100 pts Individual Points/Design Implementation  CSE293 To Be Developed During the Semester!

7. OV-1.7 CSE262 CSE293 Course Projects Using UML and Together CC  CSE262 and CSE293 will both 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: www.rational.com/uml/ documentation.html  “The Unified Modeling Language Reference Manual”, Addison-Wesley, 1999.

8. OV-1.8 CSE262 CSE293 Representing System Architecture ConceptualPhysical Logical View End-user Functionality Implementation View Programmers Software management Process View Performance Scalability Throughput System integrators Deployment View System topology Delivery, installation Communication System engineering Use Case View

9. OV-1.9 CSE262 CSE293 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

10. OV-1.10 CSE262 CSE293  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 UML Modeling Constructs/Diagrams Classification by Capability/Timeline

11. OV-1.11 CSE262 CSE293 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

12. OV-1.12 CSE262 CSE293 Course Projects Using UML and Together CC  Utilize the Together Control Center UML Tool  www.togethersoft.com  Go to Download Page and Register  Download TCC for Win or Unix  Send email to steve@engr.uconn.edu  Name, Address, Phone, email  Course #, Graduation Date (expected)  Receive key (TG) file by email - place in c:\Together4.2\bin directory  Key Changes WhiteBoard to Full Version  Provides Full UML Plus ER and Business Process

13. OV-1.13 CSE262 CSE293 Documentation Packages/Requirements  All Project Specifications (Written Documents) Must be Done using:  MS Word or Latex  For Latex, Generate Postscript (or PDF) from DVI File  All Project Presentations Must be Done Using Powerpoint (PPT)  Utilize Samples on Web Page for UML and CT Insurance Dept. Link for Guide  Submit Both Hard Copy and Electronic Versions  Hard Copy Produced on Laser Printer  Electronic as a Directory zipped  TeamNameProjX.zip

14. OV-1.14 CSE262 CSE293 Project/Team Web Page/Documentation  Each Team MUST Develop a Web Page for their Project  See Links for Spring 2000 Projects as Example  Use To Post On-Going Documents  Augment Web Page with Detailed Design Documents  Together CC Generates Documentation  Frame Based HTML Resembles Java Doc  Make Sure you Select “All” Diagrams  Documentation of Java with Java Doc  Utilize Together CC  Utilize Sun’s Forte or Other Tool

15. OV-1.15 CSE262 CSE293 CSE262 Course Schedule Week ---- Topic and Objectives One Organization - Overview, Choosing Teams, Team Dynamics Two Project 1 and Presentation Project 2 Distributed (Write Specification) Project 2 Distributed (Write Specification) Three Project 2 Due Project 3 Distributed Project 2 Graded with Comments Project 2 Graded with Comments Four Project 3, Parts I/II Due, Graded, and Returned Project 3, Part III Discussed - Design (UML and ERs) Project 3, Part III Discussed - Design (UML and ERs) Five Project 3, Part III - Presentation/Walkthrough Project 3 Graded with Comments Project 3 Graded with Comments Six Project 3, Part III - Revisions - 2nd Walkthrough Project 4 Distributed (UML Class/Packages) Project 4 Distributed (UML Class/Packages) Seven Project 4 Presentation/Walkthrough Project 5 - Distributed - Scheduling, Management Project 5 - Distributed - Scheduling, Management Eight Project 5 Presentation - Management/Prototyping Plan Nine Spring Break Week Ten to At least 3 separate Prototypes/Demos by Each Team Fifteen Final Presentation/Report Due on Thursday 5/3/01

16. OV-1.16 CSE262 CSE293 CSE293 Course Schedule Week ---- Topic and Objectives One Organization - Overview, Choosing Teams, Team Dynamics Two Project 1 and Presentation Four Specification and Progress Report Six Design/Prototyping and Progress Report Eight Design/Prototyping and Progress Report Nine Spring Break Week Eleven Design/Prototyping and Progress Report Thirteen Design/Prototyping and Progress Report FifteenFinal Presentation/Report - 5/8/01

17. OV-1.17 CSE262 CSE293 Defining Semester Project  CSE262: Team Defines and Quantifies Project Based on Their Own Interests  Identify/Define “Significant” Project Which can be Partitioned into Components  “Too” Large for One Semester  Project 1: 1 Page Proposal for Feedback  CSE293: Team Defines Project or Instructor offers Suggestions from his/her Research Program  Can be Follow-up Project from 26X Course  Project Must Allow Application of Learned Skills from CSE Curriculum  Submit 1 Page Proposal for Feedback

18. OV-1.18 CSE262 CSE293 Today’s Tasks CSE262 and CSE293  Choosing Teams  4 Teams of 5-6 people  Self-Organized Teams  Instructor Sets Teams  Meet & Brainstorming  Remainder of Class  Exchange Email and Phone Numbers  Discuss Project Ideas  Visit Prior Web Pages  Choosing Teams  3 Teams of 3-4 people  Self-Organized Teams  Instructor Sets Teams  Meet & Brainstorming  Remainder of Class  Exchange Email and Phone Numbers  Discuss Project Ideas  Visit Prior Web Pages  First Project Due - January 29th, 9am - Expect Feedback by End of Day  First Project Presentation - February 1, 4-6pm  5 to 10 minutes per team  Copy of Slides/Create & Post on Web Page