Www.mef.net Euro16 LSO Hackathon Guidelines for Project Participation.

Slides:



Advertisements
Similar presentations
Applicatieplatform congres 12 & 13 maart. Modeling that works with code Preview VSTS Architect edition 2010 Marcel de Vries IT- Architect Info Support.
Advertisements

Mastering Object-Oriented Analysis and Design with UML Module 4: Analysis and Design Overview.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
Design and Programming Patterns Associated with Java Networking by Margaret Toews cs843, Spring 2003.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5.
Architecture, Deployment Diagrams, Web Modeling Elizabeth Bigelow CS-15499C October 6, 2000.
SwE 313 Introduction to Rational Unified Process (RUP)
UML - Development Process 1 Software Development Process Using UML (2)
Business Requirements Using Unified Modeling Language Eric H. Castain, SVP Internet Services Group, Architecture Wells Fargo March 2005.
*All other brands and names are the property of their respective owners. Slide 1 ® UDIG Driver Test Suite Rob Mills Barry Feild
Unified Modeling Language, Version 2.0
Role-Based Guide to the RUP Architect. 2 Mission of an Architect A software architect leads and coordinates technical activities and artifacts throughout.
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Modelling Class T16: Conceptual Modelling – Architecture Image from
Object Oriented Analysis and Design using the UML CIS 520 Advanced Object-Oriented Design.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
Accelerating Java Development with the UML Greg Schottland General Manager, Application Development Tools Embarcadero Technologies,Inc.
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
TAL7011 – Lecture 4 UML for Architecture Modeling.
June 15, 2009GITB Open Meeting, Brussels1 GITB Alternative Architectures and Business Models CEN/ISSS eBIF Global eBusiness Interoperability Test Bed Methodologies.
CS 772: Global Knowledge Networks V. “Juggy” Jagannathan CSEE, West Virginia University.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
CSC480 Software Engineering Lecture 8-9 September 20, 2002.
CONTENT 1.Software Process 2.Object Technology 3.UML 4.UML For Java.
GEN15 LSO Hackathon. Session Topics LSO Hackathon vision (GEN15 and beyond) GEN15 LSO/CE 2.0 oriented scope (review of the diagram) and defined outputs.
UML Diagrams for Caradon developers Daniel DG Moth Core Development Group, Research Student University of Brighton, MSc Object Oriented Software Technology.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
A Well Designed Web Application The Benefits of Object Oriented Analysis and Design Simone Becker
Bhuvan Unhelkar, PhD, FACS Phone: +61(0) ; & Prof. Brian Henderson-Sellers Modelling Spaces and.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Computer Science 340 Software Design & Testing Software Architecture.
United Nations Economic Commission for Europe Statistical Division International Collaboration to Modernise Official Statistics Steven Vale UNECE
Charles Eckel, Cisco DevNet WELCOME TO THE Agenda and Code Contributions.
04 - OOD Intro.CSC4071 Software Design ‘Requirements’ defines –The goals the system needs to satisfy. ‘Specification’ defines –The externally-observable.
Executive Overview. Software modeling is essential, because it is the map that guides your developers. Additionally: Modeling Software  Visual information.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
1 IBM Software Group ® Mastering Object-Oriented Analysis and Design with UML 2.0 Module 4: Analysis and Design Overview.
Use Case, Component and Deployment Diagrams University of Sunderland.
Lab Results Interface Pilots WG Kick-Off August 1, 2011.
1 Model Driven Health Tools Design and Implementation of CDA Templates Dave Carlson Contractor to CHIO
SWE 214 (071) Introduction to UML Slide 1 Introduction to UML.
Using Git with collaboration, code review, and code management for open source and private projects. & Using Terminal to create, and push commits to repositories.
MEF Modeling Activities
UML Diagrams By Daniel Damaris Novarianto S..
MEF Modeling Activities
MEF Q2, April Frankfurt, Germany
Systems Analysis and Design With UML 2
Documentation Guidelines
Chapter 6: Structured Vs. Object Oriented Analysis and Design.
Chapter 1 OBJECT-ORIENTED ANALYSIS AND DESIGN
LSO Hackathon Summary Charles Eckel, Cisco DevNet.
for Display Antique and Art Object Information
IMTC SIP Interconnect and SuperOp
UML Diagrams Jung Woo.
API Documentation Guidelines
MEF API Development Approach
Rational Worldwide Software Symposium
Product Life cycle (RUP)
Rational Worldwide Software Symposium
12/26/2018 1:44 AM © Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN.
Software Design Lecture : 14.
Strategy for development of new software
Rational Worldwide Software Symposium
Uml diagrams In ooad.
from Lutz Dietrich and Hans Kluge
CSCI 360 Final Review Dr. X.
Presentation transcript:

Euro16 LSO Hackathon Guidelines for Project Participation

Euro16 LSO Hackathon April 27-29, 2016 A.ROMA Hotel, Rome Co-located with MEF Quarterly Meeting

What’s a Hackathon? People collaborate intensively Hack + Marathon

Get feedback from the market Validate Use Cases Accelerate the development of artifacts

Business Use Cases LSO RA Interface Point Implementation Use Cases Developer’s Guide & Supporting Materials SDK + Development Environment

Wednesday 27 th Thursday 28 th Friday 29th Workshop/SetupDevelop Wrap up and share

Select Biz Use Cases Identify LSO RA Interface Points Identify Candidate Projects Specify Implementation Use Cases Begin Publishing Supporting Materials (for developers)* Publish SDK & Development Environment Specs. Publish Developer’s Guide Setup Deployment Environment (Hackathon Starts) Support Developers Retrospective 12/11/15 1/28/163/1/164/12/16 4/27/164/27/16 to 4/29/16 5/6/16

(Rome) Serviceability & Ordering (Remote ) Serviceability & Ordering

Keys to a Successful Participation

Review and sign Code Contribution Agreement

Articulate benefits of Euro16 LSO Hackathon How’s the project going to benefit from participating in the Hackahton? How are participants going to benefit from working on the project during the Hackathon?

Describe participant’s profile and expectations What skillset and background will guarantee a successful participation during the Hackathon? Software developer? What programming environment and languages are participants expected to know? Linux? Java? Python? GitHub? Software architect? What programming environment and architectural patterns are participants expected to be familiar with? What network virtualization technologies are participants expected to be familiar with? Network engineer/architect? What network virtualization technologies are participants expected to be familiar with? Business Analyst? What processes are participants expected to be familiar with? Other?

Specify implementation Use Cases Specify the use cases participants will implement during the Euro16 LSO Hackathon Use UML Use Case or Sequence Diagrams Add Use cases to the LSO Hackathon wiki

Commit to develop and publish SDK and supporting materials by 12-April-2016 A successful project participation is the direct result of the artifacts produced by the team. Use MEF’s GitHub to publish the SDK participants will need to implement the use cases you’ve proposed API specs code snippets & any other artifact developers will use during the hackathon Specify and publish the development environment participants will use during the Hackathon Provide a Participant’s Guide

Commit to Euro16 LSO Hackathon timeline/milestones 4/12/2016 – Publish SDKs 4/12/2016 – Publish Participants’ guide 4/27/2016-4/29/2016 – Euro16 LSO Hackathon in Rome

Mind your logistics