Project Meeting - in.tum.de file•Need documentation to present concepts in advance of...

31
Project Meeting 20 Nov 2002

Transcript of Project Meeting - in.tum.de file•Need documentation to present concepts in advance of...

Page 1: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

Project Meeting

20 Nov 2002

Page 2: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 2

Today’s Outline

• Status (70 minutes)– Showcase Tutorial (20 min)

Planning and Producing a Product Showcase– CASE Tools Tutorial (40 min)

Computer-Aided Software Engineering: UsingTogether Control Center

– Dev Team Status (15 min)– Schedule (5 min)

• Discuss (50 minutes)– Volunteers & Process for System Design Review– Coding Standards and Testing Tutorial (Build Team)– Work Breakdown Structure

Page 3: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

Showcase and Demo Engineering

We Shoot They Buy

Page 4: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - Showcase and Demo Engineering 4

Problem

• Need to be able to tell people about system ineasy way

• Also understandable to non-technical people

• Need documentation to present concepts inadvance of implementation - even beforeprototypes can be produced.

Page 5: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - Showcase and Demo Engineering 5

Solution

• Filmed product showcase and demos

• Non - technical stuff can go side-by-side withtechnical details.

• Nontechnical people can be introduced gently tothe subject matter.

• Archivable

• Not dependent on implementation

Page 6: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - Showcase and Demo Engineering 6

Film Support forRequirements Elicitation

Page 7: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - Showcase and Demo Engineering 7

Showcase

• Project Presentation: How we did what we did

• Product Presentation: What came out

Page 8: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - Showcase and Demo Engineering 8

Project Presentation

• Participants

• Organization

• Process

Page 9: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - Showcase and Demo Engineering 9

Product Presentation

• Scenario

• Functional, Object and Dynamic Model

• Finished Product

Page 10: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - Showcase and Demo Engineering 10

• This page intentionally left blank

Page 11: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

CASE Tools Tutorial

Computer Aided Software Engineering

Michael Nagel

Page 12: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - CASE Tools 12

Tutorial outline

• Motivation

• Together Control Center

• Project Builder

• Live Demo and Exercises

Page 13: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - CASE Tools 13

Problem

• Lots of routine work for programmers

• Many tasks can be automated

• Several different tools in the developmentprocess (compiler, debugger, modeler)

• Forward/Reverse/Roundtrip Engineering

Page 14: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - CASE Tools 14

Solution

• Integrated Development Environments– Editor– Compiler– Debugger– UI Builder

• Automated code generation• Modeling capabilities• Roundtrip Engineering• Version Control

Page 15: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - CASE Tools 15

Together Control Center

• C++/Java applications, J2EE, Web Services,JSP frontends

• UML modeling

• Roundtrip Engineering

• UI Builder

• Debugger

• Testing framework

• Software Audits and Metrics

• Automated documentation

Page 16: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - CASE Tools 16

Project Builder

• Included with Mac OS X

• Wide variety of project types supported

• Cocoa, Carbon, AppleScript applications

• Debugger

• No modeling capabilities

Page 17: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 ARENA Tutorial - CASE Tools 17

Live Demo

• How to create a Project Builder project

• How to create a Together project

• Roundtrip engineering example

• Together project for all ARENA classes

• Running the Oscillator example

Page 18: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 18

Today’s Outline

• Status (70 minutes)– Showcase Tutorial (20 min)

Planning and Producing a Product Showcase– CASE Tools Tutorial (40 min)

Computer-Aided Software Engineering: UsingTogether Control Center

– Dev Team Status (15 min)– Schedule (5 min)

• Discuss (50 minutes)– Volunteers & Process for System Design Review– Coding Standards and Testing Tutorial (Build Team)– Work Breakdown Structure

Page 19: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 19

Dev Team Status

• Volunteer Minute Taker, please?

• Dev HCI

• Dev Network

• Dev FRAG

• Dev SWORD-Engine

• Dev Algorithm

Page 20: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 20

Today’s Outline

• Status (70 minutes)– Showcase Tutorial (20 min)

Planning and Producing a Product Showcase– CASE Tools Tutorial (40 min)

Computer-Aided Software Engineering: UsingTogether Control Center

– Dev Team Status (15 min)– Schedule (5 min)

• Discuss (50 minutes)– Volunteers & Process for System Design Review– Coding Standards and Testing Tutorial (Build Team)– Work Breakdown Structure

Page 21: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 21

Schedule

Mon Tue Wed Thu Fri11 12 13 14 15

18 19 today 21 22

25 26 27 28 29SystemDesignReview

internal reviewinternal review

SDD v.1

Subsystemdecom-position

SDRSDRdry-rundry-run

SDD v.2

Page 22: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 22

Schedule Details

• Subsystem decomposition (by 09:09 on Thu, 21Nov 2002)– some minor additions and corrections

– FRAG Team is responsible editor

• SDD template complete (by 11:11 on Thu, 21Nov 2002)– section subsystem decomposition is extended

– new .tex files will be generated and assigned todevelopment teams for further editing

– Documentation Team is responsible for this task

Page 23: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 23

Schedule Details - 2

• SDD v.1 (by 23:23 on Fri, 22 Nov 2002)– all sections are complete

– status in XROADS is updated

– Documentation Team is responsible

• SDD v.2 (by 23:23 on Tue, 26 Nov 2002)– reviewed by cross-functional teams

– ready to be printed

– Documentation Team is responsible

• SDD printed by 15:00 on Wed, 27 Nov 2002

Page 24: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 24

Schedule Details - 3

• SD Review requires:– presentation slides– presenters (3 max.) (responsible for slides)– film setup

• SDD presentation v.1 (dry-run at 16:00 on Mon,25 Nov)– design goals– subsystem decomposition– hardware/software mapping– boundary conditions

• SDD presentation v.2 (by 23:23 on Tue, 26 Nov)

Page 25: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 25

Today’s Outline

• Status (70 minutes)– Showcase Tutorial (20 min)

Planning and Producing a Product Showcase– CASE Tools Tutorial (40 min)

Computer-Aided Software Engineering: UsingTogether Control Center

– Dev Team Status (15 min)– Schedule (5 min)

• Discuss (50 minutes)– Volunteers & Process for System Design Review– Coding Standards and Testing Tutorial (Build Team)– Work Breakdown Structure

Page 26: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 26

Volunteers forSystem Design Review

• Volunteer 1:

• Volunteer 2:

• Volunteer 3:

Page 27: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

Coding Standards andTesting Tutorial

Build Team

Page 28: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 28

Today’s Outline

• Status (70 minutes)– Showcase Tutorial (20 min)

Planning and Producing a Product Showcase– CASE Tools Tutorial (40 min)

Computer-Aided Software Engineering: UsingTogether Control Center

– Dev Team Status (15 min)– Schedule (5 min)

• Discuss (50 minutes)– Volunteers & Process for System Design Review– Coding Standards and Testing Tutorial (Build Team)– Work Breakdown Structure

Page 29: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 29

Work Breakdown Structure

• 6 Work Areas have been identified:– Input

– Output

– Network

– Environment

– FRAG Objects

– SWORD Engine

• Within the work areas, there are tasks that aredone by the “ARENA Dev *” teams

Page 30: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 30

$Id: WorkBreakdownStructure.graffle,v 1.2 2002/11/12 18:35:54 creighto Exp $

Page 31: Project Meeting - in.tum.de file•Need documentation to present concepts in advance of implementation - even before prototypes can be produced. 8. Februar 2003 ARENA Tutorial - Showcase

8. Februar 2003 Project Meeting 31

Developer Team Assignments

• Dev HCI: HCI Design (Input and Output)

• Dev Network: Peer Discovery

• Dev FRAG: Object Drawing, World Drawing

• Dev SWORD-Engine: FRAG Object Classes

• Dev Algorithm: World Generation Algorithm,Mission Model