Microsoft Word - [2017SMA][T8]OOPT_Stage_2040 ver2.docx

Similar documents
Ver 1.0 마감하루전 Category Partitioning Testing Tool Project Team T1 Date Team Information 김강욱 김진욱 김동권

Microsoft Word - [2017SMA][T8]OOPT_Stage_1000 ver2.docx

Microsoft Word - [2017SMA][T8]OOPT_Stage_1000_ docx

Microsoft Word - OOPT stage 2040 ver2.docx

PowerPoint 프레젠테이션

Contents Activity Define Real s Activity Define Reports UI, and Storyboards Activity Refine System Architecture Activity Defin

1.5 Issue TrafficCard Management Activity 2142 Define Reports, UI, and Storyboards window Window Windo

Index Activity Refine System Architecture Activity Define Design Class Diagrams Activity 2141, 2142, 2144 Design Real Use Case + Define Re

Ver. 4.0 OOPT Stage 1000 <Plan and Elaboration> Version 4.0 Project Team T7 Team Date Team Information 오세욱 임현유

A NEW CSE ATM OOPT Stage 1000 Project Team T3 Date Team Information 이원오 이재규

A NEW CSE ATM OOPT Stage 1000 Project Team T3 Date Team Information 이원오 이재규

OOO Paint

PowerPoint 프레젠테이션

OOO Paint

Contents. Phase Revise Plan --- Phase Synchronize Artifacts --- Phase 2130 Analyze Activity2131. Define Essential Use Cases --- Activity21

소프트웨어개발방법론

매뉴얼_웹용

PowerPoint 프레젠테이션

화판_미용성형시술 정보집.0305

UML

Software Modeling & Analysis Global ATM System Project Team 1 Team Date Team Information 엄현식 최정헌 전다윤

OSP Stage 2040 <Plan & Elaboration> 유아를위한주제별영어학습놀이프로그램 T 김도희 박수민 + 김태현 1

Software Modeling & Analysis Global ATM System Project Team 1 Team Date Team Information 엄현식 최정헌 전다윤 목차 Activ

텀블러514

Ver1.0

IT현황리포트 내지 완

Microsoft Word - [TP_3][T1]UTP.docx

자식농사웹완


표1.4출력

003-p.ps

중앙도서관소식지겨울내지33

양성내지b72뼈訪?303逞


표1~4


chungo_story_2013.pdf

*중1부

2

Çѱ¹ÀÇ ¼º°øº¥Ã³µµÅ¥

...._


전반부-pdf

<4D F736F F F696E74202D20312E20B0E6C1A6C0FCB8C15F3136B3E2C7CFB9DDB1E25F325FC6ED28C0BA292E >

_

12월월간보고서내지편집3

에너지포커스 2007년 가을호


01_당선자공약_서울

인권문예대회_작품집4-2




목차

A°ø¸ðÀü ³»Áö1-¼öÁ¤

±¹³»°æÁ¦ º¹»ç1

¿¡³ÊÁö ÀÚ¿ø-Âü°í ³»Áö.PDF

전반부-pdf

뉴스레터6호

Microsoft PowerPoint 하반기 크레딧 전망_V3.pptx

50차 본문 최종

³»Áöc03âš

fsb9¿ù³»ÁöÃÖÁ¾Ãâ

¾ç¼º-¾÷¹«Æí¶÷-³»¿ëÃà¼Ò4

전도대회자료집

< DBAB4B9ABC3BB5FBAB9B9ABB0FCB8AEB8C5B4BABEF32D33B1C72E706466>

<3344C7C1B8B0C6C320BFE4BEE02D E706466>

µ¶ÀÏÅëÀÏÁý1~2Æíq36£02Ð


ORANGE FOR ORACLE V4.0 INSTALLATION GUIDE (Online Upgrade) ORANGE CONFIGURATION ADMIN O

Ver 2.2 마감하루전 Category Partitioning Testing Tool Project Team T1 Date Team Information 김강욱 김진욱 김동권

Software Modeling & Analysis Global ATM System Project Team 1 Team Date Team Information 엄현식 최정헌 전다윤

슬라이드 1

#KM560

example code are examined in this stage The low pressure pressurizer reactor trip module of the Plant Protection System was programmed as subject for

Orcad Capture 9.x

OOO Paint

푸른21탄소중립행사내지확정

?털恬묵

<Software Modeling & Analysis> OSP Stage 2040 < Design > Ver 3 Team 2 김민우 김재엽 최하나 /05/23 1

PowerPoint 프레젠테이션

OOO Paint

<C0D3C7F6BCFA2E687770>

#한국사문제7회4급

OOO Paint

Software Verification 1 st Testing System Test Team 고예은 김수현 김아름 1

13 Who am I? R&D, Product Development Manager / Smart Worker Visualization SW SW KAIST Software Engineering Computer Engineering 3

Software Modeling < < OOAD Stage 김정태 최정명 이낙원 송준현

Print

thesis

05Çѱ۳»Áö11

Manufacturing6

감정원-0506

소프트웨어공학 Tutorial #2: StarUML Eun Man Choi

03.Agile.key

Something that can be seen, touched or otherwise sensed

슬라이드 제목 없음

Ver. DS-2012.T3.DWS.STR-1.0 System Test Report for Digital Watch System Test Cases Specification Test Summary Report Project Team 이동아 Latest update on



Transcription:

OOPT Stage 2040 - Design Feesual CPT Tool Project Team T8 Date 2017-05-24 T8 Team Information 201211347 박성근 201211376 임제현 201411270 김태홍 2017 Team 8 1

Table of Contents 1. Activity 2041. Design Real Use Cases 2. Activity 2042. Define Reports, UI, and Storyboards 3. Activity 2044. Define Interaction Diagrams 4. Activity 2045. Define Design Class Diagrams 5. Activity 2046. Design Traceabillity Analysis 2017 Team 8 2

1. Activity 2041. Design Real Use Cases 1.1. UI <Window-1> <Window-2> 2017 Team 8 3

1.2. Use Case Set Table Actors User Purpose Analyze에서사용할값을입력받는다. Overview Analyze에사용하기위해 User가 Table에값들을입력한다. Type Primary and Essential Cross References Functions : N/A Use Cases : N/A Pre_Requisites N/A UI Widgets Window-1 Typical Courses of Events (A) : Actor, (S) : System 1. (A) Category Partitioning Test를진행하기위한정보를 A ~ H 까지입력한다. 2. (S) 입력한정보를 Table에저장한다. 3. (S) 더이상입력할공간이없으면입력할수있는한행을추가한다. 3. (A) 고려할조건에맞는 I ~ K 체크박스를체크한다. 4. (S) 체크박스의정보가 Table에저장된다. Alternative Courses of Events N/A Exceptional Courses of Events N/A 2017 Team 8 4

Use Case Analyze Actors User Purpose 입력받은값들로시스템에분석을요청한다. Overview 입력받은값들로 Test Case들을생성하고, Feedback을분석하기를시스템에요청한다. Type Primary and Essential Cross References Functions : R2.1, R2.2 Use Cases : Mk Feedback, Mk Test Case Pre_Requisites 정상적으로 Test case들을생성하기위해서 Table에올바른값들이저장되어있어야한다. UI Widgets Window-1, Window-2 Typical Courses of Events (A) : Actor, (S) : System 1. (A) Window-1-L버튼을눌러 feedback을요청한다. 2. (S) issuccessful을이용하여 Test case를정상적으로생성할수있는지확인한다. 3. (S) issuccessful이 true이면 Feedback을 Window-2-A에출력하고, TestCaseList를요청하여 Window-1-M에출력한다. 4. (S) issuccessful이 false이면이면 Feedback을 Window-2- A에출력한다. Alternative Courses of Events N/A Exceptional Courses of Events N/A 2017 Team 8 5

Use Case Mk Feedback Actors N/A Purpose 상황에알맞은 feedback을분석한다. Overview User가 Analyze를요청했을때, 상황에알맞은 feedback을 분석하여알려준다. Type Primary and Essential Cross References Functions : R2 Use Cases : Analyze Pre_Requisites Analyze 가요청을보내야한다. UI Widgets N/A Typical Courses of Events (A) : Actor, (S) : System 1. (S - A) User의 Analyze요청을받은시스템이 feedback 분석요청을한다. 2. (S) JTable에한행에어느곳이라도값이들어있으면 Ref#, Category, Sub-Category, Sub-Category Detail의값이 모두들어있는지확인한다. 3. (S) 값이모두들어있으면 issuccessful은 true가된다. 4. (S) property가있으면 if열에해당값이있는지확인하 고, if가있으면 property열에해당값이있는지확인한다. 5. (S) TestcaseList의수가제약조건이없을경우보다 20% 이하인지확인한다. 6. (S) Feedback을 User의 Analyze요청을받은시스템에넘 겨준다. 7. (S - A) User의 Analyze요청을 받은 시스템이 issuccessful 검사를요청을한다. 8. (S) 위의결과를 User의 Analyze요청을받은시스템에 넘겨준다. Alternative Courses of Events N/A Exceptional Courses of Events N/A 2017 Team 8 6

Use Case Mk Test Case Actors N/A Purpose Table에설정된값에맞추어 Test case를생성한다. Overview User가 Analyze를요청했을때, Table에설정된값에맞추어 Test case를생성하여알려준다. Type Primary and Essential Cross References Functions : R2 Use Cases : Analyze Pre_Requisites Analyze 가요청을보내야한다. Table에정상적인값이저장되어있어야한다. UI Widgets N/A Typical Courses of Events (A) : Actor, (S) : System 1. (S - A) User의 Analyze요청을받은시스템에서 issuccessful을확인하여 true일경우 Test case 생성요청을한다. 2. (S) Table의 if, single, error 값을확인하여해당항목의 subcategory를제외한나머지 subcategory를서로다른 category에대해 1개씩뽑아서조합한다. 그뒤 if항목에각각알맞은 property를조합한다. 3. (S) Test case List 요청을받으면 TestcaseList를넘겨준다. Alternative Courses of Events N/A Exceptional Courses of Events Table에정상적인값이저장되어있지않을경우, Test Case를생성하지않는다. 2017 Team 8 7

Use Case Test case Desc Actors User Purpose Test Case의 Description을보여준다. Overview User가 Test Case를선택하면해당 Test Case의 Description 을한개씩보여준다. Type Primary and Essential Cross References Functions : N/A Use Cases : N/A Pre_Requisites 정상적으로 Test Case들이생성되어있는상태여야한다. UI Widgets Window-1 Typical Courses of Events (A) : Actor, (S) : System 1. (A) Window-1-M에서원하는 Test Case를선택한다. 2. (S) 해당되는 testcaselist의 singletclist에서첫인덱스에저장된 Description을 Window-1-N에출력한다. 3. (A) Window-1-O버튼을누른다. 4. (S) 이전의 Description이존재하는경우 singletclist에서이전인덱스에저장된 Description을 Window-1-N에출력한다. 5. (A) Window-1-P버튼을누른다. 6. (S) 이후의 Description이존재하는경우 singletclist에서이전인덱스에저장된 Description을 Window-1-N에출력한다. Alternative Courses of Events N/A Exceptional Courses of Events Test Case들이생성되어있지않은경우, User에게알려준다. 2017 Team 8 8

Use Case Save File Actors User Purpose Table과 Test Case를 txt 파일로저장한다. Overview 설정한 Table과생성된 Test Case들을 txt 파일로저장한다. Type Primary and Essential Cross References Functions : N/A Use Cases : N/A Pre_Requisites 정상적으로 Test Case들이생성되어있는상태여야한다. UI Widgets Window-1 Typical Courses of Events (A) : Actor, (S) : System 1. (A) Window-1-Q버튼을누른다. 2. (S) txt파일의저장을요청한다. 3. (S) Table에저장된값들과생성된 testcaselist를 txt 파일로저장한다. 4. (S) 저장성공여부를 Window-2-A에띄워 User에게알린다. Alternative Courses of Events N/A Exceptional Courses of Events Test Case들이생성되어있지않은경우, User에게알려준다. 2017 Team 8 9

2. Activity 2042. Define Reports, UI, and Storyboards < 기본화면 > 2017 Team 8 10

< 정상적인실행 > 2017 Team 8 11

< 피드백예시 > 2017 Team 8 12

3. Activity 2044. Define Interaction Diagrams 2017 Team 8 13

2017 Team 8 14

4. Activity 2045. Define Design Class Diagrams 5. Activity 2046. Design Traceability Analysis 2017 Team 8 15