Transcript Slide show January 17, 2007

CSE 293
CS & E Design Laboratory
Prof. Alexander A. Shvartsman
Computer Science & Engineering Department
The University of Connecticut
371 Fairfield Way, Unit 2155
Storrs, CT 06269
[email protected]
http://www.engr.uconn.edu/~aas
(860) 486-2672
Acknowledgment: Based on a presentation by Prof. S. A. Demurjian, Jr.
January 2007
Course Goals
 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
 What is the Instructor’s Role?

Provide a set of potential project topics

Serve as a manager - organize meetings, available for
questions, etc.

January 2007
Course Philosophy
 CSE293:



January 2007
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
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
January 2007
 CSE26X
 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
Texts and Class Materials
 Primarily project-specific – gathered by the team
 CSE293 web site at
www.engr.uconn.edu/~steve/Cse293/cse293.html
 Course materials made available on-line
 Other examples of class materials/texts
 Software Download - Ghostview/Ghostscript
 Together Control Center - UML Tool
 UML Explained, K. Scott, Addison Wesley

January 2007
Milestones with Dates
(Initial Schedule Subject to Change)











Project 1: Project Proposal – 3 days after 1st class
Project 2: Initial Specification – 3rd Class
Project 3: Part I - Revised Specification – 4th class
Project 3: Part II – Initial Design – 5th class
Project 3: Part III - Revised Design – 6th class
Project 4: Prototyping/Mgmt. Plan – 6th class
Project 4: Proto/Dev-t Report 1/Presentation – 9th class
Project 4: Proto/Dev-t Report 2/Presentation – 11th class
Project 4: Proto/Dev-t Report 3/Presentation –13th class
Project 4: Final Report/User Manual – End of Semester
Project 4: Final Student Assessment – End of Semester
January 2007
6
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?
January 2007
7
Course Projects Using UML and
Together CC
 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: www.rational.com/uml/documentation.html

“The Unified Modeling Language Reference Manual”,
Addison-Wesley, 1999.
January 2007
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

January 2007
9
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

January 2007
Relationship Between
Models and Diagrams
Use Case
Use Case
Diagrams
Sequence
Diagrams
Diagrams
Scenario
Scenario
Diagrams
Collaboration
Diagrams
Diagrams
Scenario
Scenario
Diagrams
Statechart
Diagrams
Diagrams
January 2007
Use Case
Use Case
Diagrams
Use Case
Diagrams
Diagrams
State
State
Diagrams
Class
Diagrams
Diagrams
State
State
Diagrams
Object
Diagrams
Diagrams
State
State
Diagrams
Component
Diagrams
Diagrams
Models
Component
Component
Diagrams
Deployment
Diagrams
Activity
Diagrams
Diagrams
11
Semester Requirements
 See cse293requirements.pdf on web page
 Summary







January 2007
Teams of 5 or 6 students
W course means 15 pages/team member
Revisions cycles count towards page total
Web-Page for each Team with all materials
BLOG for each team member
Use of IDE (e.g., Visual Studio, Eclipse, etc.)
Source Code Control (Subversion)
Course Projects Using UML and
Together Architect 1.0 or EclipseUML
 Information on Both Forthcoming 

January 2007
www.togethersoft.com
www.eclipse.org
Documentation
Packages/Requirements
 All Project Specifications (Written Documents) Must be Done
using:

MS Word (unless there is an acceptable reason not to)
 All Project Presentations Must be Done Using Powerpoint (PPT)

Help yourselves: 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
January 2007
Projects Considered in the Past






Marklin Digital Trains
Atari 800 Renovation
PDFA and/or Cell Phones
Web-Based Journal Editor
Auditory Perception of Alphabet Letters
Heating System Design and Engineering
January 2007
Additional Project Ideas
 Simple atomic read/write data service for dunamic
networks
 Talk to me
 Use experimental IDE for the (new) Tempo language to
model and simulate Internet Supercomputing
 Talk to me
 Web Auction System
 Talk to Prof. Kiayias
January 2007
16
Project: Web Auction System
 Design an online community-based auction-type web-portal
based on a novel price discrimination technology that

enables considerably better discount opportunities for buyers as well as

maximization of profit margin for sellers.
 The methodology is new, different from E-bay, Priceline, etc.

It was developed recently by a Prof. Kiayias in collaboration with RSA
Security and is currently considered for commercialization.
 The system will be web-based and include

(1) front end for sellers and buyers,

(2) reputation system,

(3) market coordination.
 Some knowledge of computer security is a plus.

Talk to Prof. Kiayias

January 2007
17
Project/Team Web
Page/Documentation
 Each Team MUST Develop a Web Page for their Project
See Links for Former Projects as Examples

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 Architect

Utilize IDE

January 2007
Today’s Tasks
 Choosing Teams - 3 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
 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
January 2007
