Specific, Measurable, Assignable, Realistic, Time-related 1 THEORACTICE Applying Contextual Design to Studio Project Team Name : THEORACTICE KangWoon Hong.

Slides:



Advertisements
Similar presentations
Fraunhofer FOKUS Competence Center MOTION FOKUS VIEW ON MODEL-BASED TEST DESCRIPTION LANGUAGES (TDLS) Alain-G. Vouffo Feudjio.
Advertisements

TTCN-3 & Conformance Testing Anitha Krishnamoorthy.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
Methods: Deciding What to Design In-Young Ko iko.AT. icu.ac.kr Information and Communications University (ICU) iko.AT. icu.ac.kr Fall 2005 ICE0575 Lecture.
Specific, Measurable, Assignable, Realistic, Time-related 1 THEORACTICE TTA Studio Project Kim, HyungChoul Han, SangJin Hong, KangWoon DEC. 09, 2005.
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Consolidation Reading: CD Ch.s 8, 9, & 10 Modeling & Interpretation.
PRESENTED BY USHA GHIMIRE. Introduction-The need for MBSE MBSE now and present shortcomings A view of MBSE in the future Key advantages and disadvantages.
A Brief Introduction. Acknowledgements  The material in this tutorial is based in part on: Concurrency: State Models & Java Programming, by Jeff Magee.
Building Models Part 1: Models good for defining system and user requirements –Affinity diagrams –Flow model –Cultural model –Sequence model –Physical.
ISBN Chapter 3 Describing Syntax and Semantics.
Unified Modeling Language
Hong, KangWoon (TTA team) Master of Software Engineering, ICU&CMU 1 Requirements Analysis for TTA studio project Hong, KangWoon SEP 13, 2005.
Software Testing and Quality Assurance
1 Introduction to Software Engineering Lecture 42 – Communication Skills.
Contextual Design. Purpose for us An example A term often used, with varying levels of precision.
SwE 313 Introduction to Rational Unified Process (RUP)
Sharif University of Technology1 Design and Use-case Realization Software Engineering Laboratory Fall 2006.
Describing Syntax and Semantics
BUSINESS PROCESS MODELING By Raghavi Jayaprakash.
Software Testing and QA Theory and Practice (Chapter 10: Test Generation from FSM Models) © Naik & Tripathy 1 Software Testing and Quality Assurance Theory.
ACM/JETT Workshop - August 4-5, 2005 UML Modeling using MagicDraw UML for Java Programmers.
- Chaitanya Krishna Pappala Enterprise Architect- a tool for Business process modelling.
10th TTCN-3 User Conference, 7-9 June 2011, Bled, Slovenia AUTOSAR Conformance Tests - Feedback on their development and utilization Alain Feudjio-Vouffo,
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
Managing IT/IS Projects Across Borders: Opportunities and Challenges for Hong Kong Joseph Lee.
Chapter 8 Architecture Analysis. 8 – Architecture Analysis 8.1 Analysis Techniques 8.2 Quantitative Analysis  Performance Views  Performance.
4 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
Investigating System Requirements
Interaction Modeling Interaction model describes how objects interact to produce useful results. Interactions can be modeled at different levels of abstraction:
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
Object-Oriented Analysis and Design An Introduction.
Object Diagram Notation Lecture Oo11 Object Visibility.
TTCN Protocol Testing on Steroids! IEEE P WPAN Meeting March 6-10, 2000 Albuquerque, NM USA 802 Plenary Meeting Matthew Graney Telelogic North America.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
CSE 403, Software Engineering Lecture 4 Gathering user requirements.
Object-Oriented Analysis and Design Fall 2009.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
Department of Informatics, UC Irvine SDCL Collaboration Laboratory Software Design and sdcl.ics.uci.edu 1 Informatics 43 Introduction to Software Engineering.
Online Shopping e-Business ITCS451/951 Group Assignment Online Shopping e-Business Team Members: 1. Elmabourk Benlamma Dhany Setia Purnama
TTCN-3 MOST Challenges Maria Teodorescu
Software Testing and Quality Assurance Software Quality Assurance 1.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
ObjectivesObjectives 1.A definition of organization cultures 2.An understanding of the importance of organizations culture in building organizational.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
Automatic Testing of Neighbor Discovery Protocol Based on FSM and TTCN Zhiliang Wang, Xia Yin, Haibin Wang, Jianping Wu Department of Computer Science.
TTCN-3 and ASN.1 interworking Analysis of backward compatibility in ASN.1 Géza Horváth TTCN-3 User Conference – 9 June 2011.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Assignment Help From Requirements Elicitation to Elicitation.
Minkyoon Kim, Sangjin Han1 Querying in Highly Mobile Distributed Environments T.Imielinski and B. R. Badrinath Minkyoon Kim Sangjin Han.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
TTCN-3 Testing and Test Control Notation Version 3.
Object Oriented Analysis & Design By Rashid Mahmood.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
Object-Oriented Techniques
Thank You! For More Details Visit us at Mobile Phone Accessories Market.pptx Follow Us On.
Programming in Perl Introduction
دانشگاه شهیدرجایی تهران
تعهدات مشتری در کنوانسیون بیع بین المللی
UseR-CENTRIC DESIGN ...and how We’d Benefit From Using IT
بسمه تعالی کارگاه ارزشیابی پیشرفت تحصیلی
G suite Customer Service Phone Number.
Overview of the ETSI Test Description Language
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Presentation transcript:

Specific, Measurable, Assignable, Realistic, Time-related 1 THEORACTICE Applying Contextual Design to Studio Project Team Name : THEORACTICE KangWoon Hong HyungChoul Kim SangJin Han

Specific, Measurable, Assignable, Realistic, Time-related 2 THEORACTICE Terminology  TTCN – The Tree and Tabular Combined Notation  TTCN is the language used to write detailed test specification and specifies tests for many kinds of applications including mobile communication protocols (GSM, 3G, TETRA)  TTCN assures testing and highquality  ATS – Abstract Test Suite  ETS – Executable Test Suite  CCG – C Code Generation

Specific, Measurable, Assignable, Realistic, Time-related 3 THEORACTICE Individual Flow Model

Specific, Measurable, Assignable, Realistic, Time-related 4 THEORACTICE Consolidated Flow Model

Specific, Measurable, Assignable, Realistic, Time-related 5 THEORACTICE Individual Sequence Model

Specific, Measurable, Assignable, Realistic, Time-related 6 THEORACTICE Consolidated Sequence Model

Specific, Measurable, Assignable, Realistic, Time-related 7 THEORACTICE Individual Artifact Model

Specific, Measurable, Assignable, Realistic, Time-related 8 THEORACTICE Consolidated Artifact Model

Specific, Measurable, Assignable, Realistic, Time-related 9 THEORACTICE Individual Cultural Model

Specific, Measurable, Assignable, Realistic, Time-related 10 THEORACTICE Consolidated Cultural Model

Specific, Measurable, Assignable, Realistic, Time-related 11 THEORACTICE Individual Physical Model

Specific, Measurable, Assignable, Realistic, Time-related 12 THEORACTICE Consolidated Physical Model

Specific, Measurable, Assignable, Realistic, Time-related 13 THEORACTICE Vision Drawing

Specific, Measurable, Assignable, Realistic, Time-related 14 THEORACTICE Storyboard - 1

Specific, Measurable, Assignable, Realistic, Time-related 15 THEORACTICE Storyboard - 2

Specific, Measurable, Assignable, Realistic, Time-related 16 THEORACTICE User Environment Design

Specific, Measurable, Assignable, Realistic, Time-related 17 THEORACTICE What we learn  Know what our users actually do  Recognize work  Express work about even subtleties  Contextual Design is more helpful if various customers exist

Specific, Measurable, Assignable, Realistic, Time-related 18 THEORACTICE Question  Thank you for your attention!