Effective Requirement Definition and Management in … · 2009-07-21 · 1970 - 1980 1980 - Present...

®

IBM Rational Solutions Day 2009

© 2009 IBM Corporation

Effective Requirement Definition and Management in Collaborative Environment

Reduce Rework, Speed up Development Process

Kwon, Oh Sung

2


Agenda

� Customer Challenges

� Solutions

� Case Studies

� Customer Value

3


Electronics

Aerospace and Defense

� 35% increased value of in-vehicle electronics & software by 2010

� 90% of innovation is based on electronics & embedded software

� 50% of warranty costs are SW & electronics related

� Need for product differentiation is driving increasing amount of software into products

� NPI delays are impacting profits

� Warranty costs are skyrocketing

� Need for cost reduction/ increased innovation is resulting in extensive focus on SW and collaborative product development

� Quality, configuration & change are top priorities

Automotive

Competition and Customer Demand are the Driving Force Behind the Transformation of Product Development

Changes are being driven across the entire supply chain - even to commodity parts that now require sophisticated software & best practices

Tier 1 Suppliers

4


� Aerospace Agency

$1 billion prototype rocket self-destructed 40 seconds after takeoff. due to a bug in on-board guidance software

� Automobile OEM

Software bug forced recall of 75k cars that stalled at high speeds

� Medical Equipment Manufacturer

Recalled 42K defibrillator devices due to poor software

Software & Integrated Product Failures Still Plague CompaniesDespite their investment on PLM

5


No clear product differentiation

Pricing

Product quality

Poor commercialization / promotion

Late to market/missed demand

Product missed customer needs

19%

23%

24%

26%

33%

46%

49%

Poor communication and collaboration (handling change)

Increase visibility into status of requirements

Increase ability to predict system behavior prior to testing

Implement or alter new product development processes for a multi-disciplinary approach

Increase real time visibility of product Bill of Materials (BOM)throughout the development process

71%

46%

39%

43%

Source: Aberdeen Group, 2008

What’s Behind These Failures and Increasing Costs?

Source: AMR Research, 2006

Business View

Engineering View

6


� Increased focus on software engineering

� Full traceability of requirements throughout product lifecycle

� Holistic system design and interaction

� 3D CAD

� PDM focus on mechanical BOM

� Organization & process improvement

� 2D CAD

� Ad-hoc data management

� No organization / process change

Product

Development

Tool-Assisted Design

Reengineering

Innovation

The Product Development Landscape is Evolving From Focusing on Cost - to Focusing on Innovation

Present & Beyond1980 - Present1970 - 1980

Globalization of suppliers, workforce & markets

New technology for reduced cost & time, increased flexibility

Productivity improvement through automation

BusinessDrivers

Business Value

Rapid innovation with software as major differentiator

Time and cost reduction

Improved production with higher quality

7


� Over 75 percent of CEOs indicated that collaboration and partnering is very important to innovation

� Extensive collaborators outperformed the competition in terms of both revenue growth and average operating margin

Importance versus extent of collaboration and partnering

(% of CEO respondents)

Source: IBM CEO Survey, 2006

Design Collaboration is a Key Enabler of InnovationAcross Departmental, Functional, Enterprise & Geographic Boundaries

100

50

0

Collaboration gap

Collaboration of great importance

Collaborated toa large extent

CEOs stressed the overwhelming importance of collaborative innovation – particularly beyond company walls

8


None Some Most All

Proportion of Products That Are Mechatronic

Laggard

Average

Best InClass

30% 30% 40%

25% 31% 19% 25%

8% 38% 30% 24%

0% 100%50%

Best in Class Products Rely More on Integration of Mechanical, Electrical and Software

Mechatronic product development has added a new level of complexity to product development as companies strive to integrate mechanical, electrical

and software components into their products.

Aberdeen Group, The Mechatronics System Design Benchmark Report, Chad K. Jackson, August, 2006

Aberdeen Group, System Design: New Product Development for Mechatronics, Michelle Boucher, David Houlihan, January, 2008

9


� Mature from processes to practices; tools to platforms

� Invest the same focus on the software domain as in mechanical

Best Practices Adopted By Leading CompaniesEstablishing Discipline & Governance in Key Product Development Areas

� Mature from managing requirements in isolated disciplines to managing them across the whole product—software, mechanical, electronics

� Invest the same focus and rigor on managing requirements as in managing mechanical bill of materials

� Establish core discipline of systems engineering and mature into practices

� Transition from a paper-based to a model-based approach

� Manage change through the full-lifecycle and across all disciplines

Systems Engineering

Requirements Engineering

Software Delivery

BestPractices

10


How IBM Can Help?

모델모델모델모델지향지향지향지향시스템시스템시스템시스템개발개발개발개발및및및및공학공학공학공학요구요구요구요구공학공학공학공학

통합통합통합통합제품제품제품제품변경변경변경변경관리관리관리관리 소프트웨어소프트웨어소프트웨어소프트웨어및및및및시스템시스템시스템시스템딜리버리딜리버리딜리버리딜리버리플랫폼플랫폼플랫폼플랫폼

Solution: Telelogic DOORS, eXchange

“전사에서 제품 요구사항의 단일뷰를 제공한다면, 우리의

개발주기가 더욱 효율적이고, 비용은 절감되며, 올바른 제품을

딜리버리가 가능할 텐데...”

Solutions: Telelogic DOORS, Telelogic Synergy & Change, and integrations with key PLM ISVs : PTC, Siemens, Dassault, and Agile.

“전자 부품의 변경이 소프트웨어또는 하드웨어의 변경에 영향을미친다. 올바른 제품을 딜리버리

하기 위해서 모든 도메인과공급자간에 변경을 조정할

필요성이 있다.”

Solutions: Rational Systems Developer, Telelogic Rhapsody, Telelogic System Architect, Rational Asset Manager, Telelogic DOORS

“우리 제품이 이전보다 더욱복잡해서, 모든 컴포넌트가

어떻게 관련 있는지를 이해하고설계의 복잡도를 관리하기

위해서는 보다 체계적인 방법이필요할 텐데….”

Solution: Rational Software & Systems Delivery Platform

“제품의 소프트웨어가 복잡하다. 고품질의 소프트웨어를 정의,

모델링, 구현, 테스팅 및 이관하기위해서는 통합적인 개발

플랫폼이 필요하다.”

11


Requirement Chain Management (RCM)

OEM

Tier #n

R & D Production QA/QC ��

Partners

Tier #1

1.그룹간그룹간그룹간그룹간프로세스프로세스프로세스프로세스및및및및기술을기술을기술을기술을표준화하여표준화하여표준화하여표준화하여복잡도복잡도복잡도복잡도관리관리관리관리

2.그룹간그룹간그룹간그룹간의사소통의사소통의사소통의사소통및및및및협업협업협업협업개선개선개선개선및및및및재사용재사용재사용재사용프랙티스프랙티스프랙티스프랙티스개선개선개선개선

목표목표목표목표 :

Review,

ApproveElicit,

Define

Vision, Goals, Use cases, Needs, Compliance, Risks, Constraints, etc

Requirements, Specifications, Technical Solutions, Test cases, etc

Specification, Design, Components, Sub-components, Test cases, etc

SW/HW/Mecha SW/HW/Mecha Reliability/Validation

“양방향양방향양방향양방향(수평적수평적수평적수평적,수직적수직적수직적수직적) 요구요구요구요구 관리관리관리관리”

Review,

ApproveElicit,

Define

12


A Typical Requirements Process

Input Requirements

Analyse & Model

Derive Requirements

and Acceptance Strategy

Agree with

customer

Results

Acceptance StrategyOutput Requirements

Request Change

Acceptance Strategy

Agree with

supplier

Request Change

Request Change

Input Requirements

Analyse & Model

Derive Requirements


Agree with

customer

Results


Request Change

Acceptance Strategy

Agree with

supplier

Request Change

Request Change

Input Requirements

Analyse & Model

Derive Requirements


Agree with

customer

Results


Request Change

Acceptance Strategy

Agree with

supplier

Request Change

Request Change

Negotiation process at each level of requirements

13


Collaboration Process

� Main work-stages:

�Preparation and agree specifications

�Share specification with suppliers

�Supplier provides a response against the Customer specification

�Customer negotiates and validates Suppliers‘ response

Preparation ofSpecification

Share Specification

Customer Agreement

Supplier Response

Customer needs to enhance collaboration and improve relationships with suppliers

14


요구공학솔루션개요

개요개요개요개요

•제품생명주기기간동안요구사항의정의/관리하기위해요구정의및관리모범사례및지원도구활용

• Telelogic DOORS, DWA, DOORS/eXchange

•제품개발, 양산, 유지보수및단종기간동안고객니즈수집, 연결, 추적, 분석및관리함

•모든설계도메인에적용가능 (전자, 소프트웨어, 기구/하드웨어)

• PLM ISP 비즈니스파트너솔루션일부와연동가능 (PTC, Dassault, Siemens)


•제품생명주기기간동안요구사항의정의/관리하기위해요구정의및관리모범사례및지원도구활용

• Telelogic DOORS, DWA, DOORS/eXchange

•제품개발, 양산, 유지보수및단종기간동안고객니즈수집, 연결, 추적, 분석및관리함

•모든설계도메인에적용가능 (전자, 소프트웨어, 기구/하드웨어)

• PLM ISP 비즈니스파트너솔루션일부와연동가능 (PTC, Dassault, Siemens)

차별화차별화차별화차별화요소요소요소요소

•분산개발팀을포함한대규모/복잡한시스템개발프로젝트지원 - Requirement Chain Management (RCM)

•설계파트너, 공급자, ISV를포함한프로젝트에서필요로하는보안제공

•변경의영향에대한이해및분석기능제공

• Telelogic 변경관리솔루션, Change와연동


•분산개발팀을포함한대규모/복잡한시스템개발프로젝트지원 - Requirement Chain Management (RCM)

•설계파트너, 공급자, ISV를포함한프로젝트에서필요로하는보안제공

•변경의영향에대한이해및분석기능제공

• Telelogic 변경관리솔루션, Change와연동

Centralized

management

of customer needs and

design

requirements

Sales

Market Analysts Customer Support

Competitors

MarketingSuppliers

Development

Customers

Customer Need/Req

Functional Req.

Design Req.

Test Req.

15


차별화차별화차별화차별화 요소요소요소요소

� 종합적인문서및스프레드시트뷰제공

� 단일뷰를통해제품생명주기영향및포괄도분석

� 관련정보에집중할수있는동적인뷰제공

� 지역적및조직적으로분산된요구관리지원

� 요구사항변경영향도분석및다중추적성제공

기대효과기대효과기대효과기대효과

� 요구사항수집, 명세, 추적성을중앙에서컨트롤

� 제품개발관련정보가시성및관련그룹간협업

개선

� 고객니즈및관련산업계또는정부규정에대한

정합성보장

“Since using DOORS in our development process, we’ve significantly reduced our systems engineering interval, which positively impacts our business.”

Director of Systems Engineering, Global Communications Network Provider

User Requirements

Technical Requirements

Test

Requirements

수평적요구관리 : Telelogic DOORS

16


Sharing DOORS Data with Suppliers

OEM database

Supplier database

Transfer

Transfer set

Export

? ? ?

Package

? ? ?

Transfer set

Unpackage

Import

Configured for Exchange

Configured for Exchange

17



� 관련그룹간에문서의일부보내기및변경사항

불러오기가능

� Away 조직으로의문서복제및지속적인문서

Update

� Home 및 Away 조직간의문서의여러버전간의

Synchronize

� 지역적지역적지역적지역적, 조직적조직적조직적조직적분산분산분산분산요구요구요구요구관리관리관리관리


� 분산그룹간공통데이터상호교환프로세스표준화

� 공급자프로세스모니터링및감사지원

� 분산그룹간요구사항정보협업및변경관리

프로세스개선

“DOORS eXchange facilitate efficient collaboration of requirement development between OEM and suppliers so that it helps managing increasing complexity of specs.”

HIS, German Automotives

Home side Away sides

Results

eXchange

Data synchronization

수직적요구관리 : Telelogic DOORS eXchange (Add-on)

18


수직적요구관리 : Telelogic DOORS eXchange (Add-on)

Home module XA in Acquirer database X

Manufacturer attributes (editable) Supplier attributes (read-only)

Away module XA in Supplier database Y

Manufacturer attributes (read-only) Supplier attributes (editable)

All exchanged

attributes are

initially created in

the home module

Values of

dedicated

attributes can

be edited in the

away module

19


수직적요구관리 : DOORS RIF eXchange

<?xml version="1.0" encoding="UTF-8" ?>

<TITLE>Test data RIF00</TITLE>

<COMMENT>RiF exchange file with

administrative data but no attribute types and

specification objects.</COMMENT>

<AUTHOR>Stefan Hendrata</AUTHOR>

<VERSION>0.1</VERSION>

<CREATION-TIME>2005-05-23T12:00:00+02:00</CREATION-TIME>

<COUNTRY-CODE>DE</COUNTRY-CODE>

<SOURCE-TOOL-ID>Manually

written</SOURCE-TOOL-ID>

<IDENTIFIER>ID_RIF_File</IDENTIFIER>

</RIF>

RIF

� Allows users to select DOORS specifications for data transfer using RIF (requirements interchange format)

�Exchange data with other RM projects or tools

�Collaborate on requirements with external vendors or suppliers

�Reliably update your data from specifications derived in parallel

20


수평적 & 수직적요구관리 : DOORS Web Access (DWA)

� Requirements analysts / Systems / Electronic / Mechanical Engineers author requirements using rich desktop client (DOORS)

RequirementsDatabase

� Manufacturing/ QA / Suppliers / Stakeholders review and comment on requirements through web browser (DOORS Web Access)

21


수평적 & 수직적요구관리 : DOORS Discussions

22


통합제품변경관리솔루션개요


•모든설계도메인에서양방향변경워크플로우자동화를할수있도록도메인특정변경관리, 요구관리, ISP PLM 도구간연동제공

• Telelogic DOORS및 Telelogic Change / Synergy및

PLM 벤더와통합 (Dassault, PTC, Oracle 및 Siemens)

•하나의설계도메인에서발생된변경과소프트웨어, 전자, 하드웨어를포함한모든도메인에서의변경간의추적성제공


•모든설계도메인에서양방향변경워크플로우자동화를할수있도록도메인특정변경관리, 요구관리, ISP PLM 도구간연동제공

• Telelogic DOORS및 Telelogic Change / Synergy및

PLM 벤더와통합 (Dassault, PTC, Oracle 및 Siemens)

•하나의설계도메인에서발생된변경과소프트웨어, 전자, 하드웨어를포함한모든도메인에서의변경간의추적성제공


•기업전사솔루션으로확장가능

•도메인특정니즈에맞게조정가능

•점진적또는하나의완성된적용솔루션으로적용가능

• PDIF SOA 기반프레임워크를포함한 PLM 솔루션을구현할수있는 IBM의광범위한자산및서비스제공


•기업전사솔루션으로확장가능

•도메인특정니즈에맞게조정가능

•점진적또는하나의완성된적용솔루션으로적용가능

• PDIF SOA 기반프레임워크를포함한 PLM 솔루션을구현할수있는 IBM의광범위한자산및서비스제공


SOFTWARE MECHANICAL ELECTRONIC

Systems Engineering Process

Integrated product change management

Qualitymanagement

Requirementsmanagement

Change & release management

Architecture management

Process & product management


SOFTWARE MECHANICAL ELECTRONIC

Systems Engineering Process

Integrated product change management

Qualitymanagement





Qualitymanagement





Qualitymanagement





Telelogic DOORS

고객고객고객고객적용적용적용적용방법방법방법방법

•제한된도메인또는 PDM 벤더와의통합에관심있는고객은기존 point to point 통합으로시작. 변형가능한 PDIF 기반솔루션으로향후확장제공

•보다포괄적인솔루션을찾는고객에게는 PDIF 기반솔루션으로시작

고객고객고객고객적용적용적용적용방법방법방법방법

•제한된도메인또는 PDM 벤더와의통합에관심있는고객은기존 point to point 통합으로시작. 변형가능한 PDIF 기반솔루션으로향후확장제공

•보다포괄적인솔루션을찾는고객에게는 PDIF 기반솔루션으로시작

Telelogic Synergy/Change

23


“Having Telelogic Change with proper workflow and

processes in place has significantly improved the

quality of development at Volkswagen..”

- Volkswagen

통합요구변경관리 : Telelogic Change


• 조직및개발생명주기동안변경워크플로우관리

• 모든유형및크기의조직전반에일관성있는변경관리, 사용편의성, 적용실패가낮은 out-of-

the-box 솔루션제공

• 유연성있고다이나믹한보고기능제공


• 변경에신속한응답

• 지속가능한정합성성취

• 조직전반및지역적으로분산된조직에서변경사항의효과적인의사소통과협업

• 조직적용및조정이쉬움

24


통합요구변경관리 – DOORS/Change empowers Requirements Change Request Process

� Predefined, customizable Lifecycles, allowing assignment, multiple reviewers, electronic signatures

�Web-based submission, transitions, analysis history, reporting

�Work on the Requirements is carried out inside DOORS

Changes are proposed against

requirements

Proposed Changes

are assessed and approved

Proposed Changes

are applied

Important information is

captured, displayed and traceability is

maintained

25


Telecommunications: Samsung Electronics, LG Electronics, AT&T, Vodafone, Verizon, Alcatel,

Bell South, British Telecom, Ericsson, L3 Comm, Lucent, Nokia, Worldcom, Motorola, Nortel, Tellabs, Zyray Wireless, Symbian

Automotive: HKMC, CARNES, AutoNet, Mando, S&T Daewoo, Continental, BMW, Audi, Chrysler Daimler-

Benz , Ford, GM, Bosch, Visteon, Porsche, Volkswagen, Toyoda, Honda, Hella, Delphi

Financial/Insurance: SC First Bank,Citibank, Experian, Freddie Mac, Mastercard, Nations Bank,

NASD/NASDAQ/ASE, Prudential, State Farm, UNUM, USAA, VISA, Wells Fargo, Swedish Bank

Government: CND, FDA, FAA, MoD, NIMA, NASA, NSA, DISA, IRS, DOD

Healthcare/Medical: Abbott Labs, Beckman Instruments, CVS, GE Medical, HP Medical,

Kaiser Permanente, Siemens Medical

IT Serivce : Booz Allen, CSC, EDS, Ernst & Young, IBM, Litton/PRC, Mitre, SAIC, TRW, Unisys

E-business: AOL, Charles Schwab, eGreetings, Hire.com, homegain.com, logistics.com,

mail2000.com, Netnanny.com, Opus360.com, phone.com, Stockback.com

Defense/Aerospace: ADD, Samsung Thales, KAI, Samsung Techwin, Korean Air, Next1, STX,

ROTEM, Boeing, JPL, Lockheed Martin, Raytheon, Rolls Royce, BAE SYSTEM, DASSAULT, Honeywell,

HUGHES, THALES, TRW

Equipment Manufacturing: Cadence, Carrier, Tata, Cisco Systems, Hewlett Packard,

Kodak, Otis Elevator, Pitney Bowes, Xerox, Ricoh, ENEA, Valley Lab

주요 Telelogic 고객

26


독일 OEM의공급자와의요구사항상호교환및관리방법사례

배경배경배경배경:

� 자동차의통합적인기능에따라소프트웨어의규모가

성장함에따라복잡도의관리점차어려워짐. 이에따라파트너와의요구사항정보의상호교환의필요성이점차

대두됨. OEM은보다구조적이고효과적으로공급자와협업할수있는방법및공급자의감사프로세스를개선할

수있는방법을찾게됨

상황상황상황상황:

� OEM은공급자와충분치않은협업을통해공급자에게요구사항을정의하는것을요구하고, 심지어양산단계에서빈번한엔지니어링변경요청을공급자에게

요청하여왔다. 이에따라공급자는 OEM에게자동차품질을개선하고비용을절감하기위해서는요구사항및

스펙의정의가중요하다는것을지속적으로설득하였고, 이에 OEM이공급자의설득을수용함 !

솔루션솔루션솔루션솔루션:

� 독일 OEM은분산요구관리와요구공학프로세스및요구상호교환프로세스를표준화하기위해

DOORS/eXchange을 선정하였다.HIS는 Requirement Interchange Format (RIF)를표준화하였고, Telelogic DOORS®는모든수준의요구사항을상호교환할수있도록 RIF를지원한다.

비경쟁소프트웨어에대해서(products 및 processes) 독일자동차생산업체는 (Audi, BMW Group, Daimler AG, Porsche and Volkswagen) HIS (Herstellerinitative Software)를설립하였고협업을통해아래와같은영역에서 Joint 표준을수립하고있음.

� Standard software modules

� Software test

� Flash programming of electronic control units

� Process assessments

� Simulation and tools

27


제품개발에서요구사항 Chain 구현사례 – Automotive

배경배경배경배경 :

독일의슈트가르트에있는다임러크라이슬러는

세계적이자동차제조업체로메르세데스벤츠, 크라이슬러, 지프, 다지, 등의브랜드를보유한자동차

회사

상황상황상황상황 :

각다임러크라이슬러브랜드는보통워드프로세스

프로그램을사용하여요구사항을관리하였음. 요구사항과변경간의의존관계를추적하기어려웠음. 다임러는지역적으로분산된개발팀이다양한브랜드

간에공통스펙을공유하기를원함

솔루션솔루션솔루션솔루션 :

다임러는개발된시스템의신뢰성및고품질을

보장하고, 전자부품의요구명세를전세계에제공/ 분산적인요구관리를위해요구관리솔루션인

Telelogic DOORS/eXchange를선택하였음. DOORS를통해현재지역적으로분산된개발팀이브랜드간에공통스펙을공유할수있음.

“Our Freightliner truck, set for release in 2007, has more than 200 features with complex requirements for each one. Tracing all of these features back to the requirements, and re-using them for common components, would be extremely difficult to do without DOORS.”

Arno von Querfurth, Manager of specifications and Software Systems,

DaimlerChrysler

28


제품개발에서요구사항및변경관리통합구현사례 – A&D

배경배경배경배경 :

�호주의 Leading 국방및항공회사

상황상황상황상황:

�다양한요구관리솔루션을사용하여

개발자가요구사항및변경을추적하기

어렵고, 비효율적인협업, 중복된공수를

야기함

솔루션솔루션솔루션솔루션 :

�요구사항및변경지향개발을할수있도록

BAE는 Telelogic DOORS®및 Telelogic Change™를선정함.

“DOORS gives us the traceability we need. Now, we can maximize reuse of requirements, better understand the scope of a project, and estimate delivery times more accurately.”

Werner Kolze, Engineering Tools Manager, BAE Systems Australia

29


고객에게주는솔루션의가치

� 프로세스의 “지연”을제거하여비용비용비용비용절감절감절감절감 (e.g. 보증도는칩 re-spin 비용) 및시장시장시장시장출시출시출시출시단축단축단축단축

� 고객의고객의고객의고객의니즈를니즈를니즈를니즈를충족시키는충족시키는충족시키는충족시키는제품

딜리버리보증

� 복잡도복잡도복잡도복잡도관리관리관리관리및변경의신속한

대응

� 제품의출시연기및고장을

야기하는제품제품제품제품문제문제문제문제해결해결해결해결지연지연지연지연

단출단출단출단출

� 소프트웨어및시스템품질품질품질품질개선

� OEM과의과의과의과의의사소통의사소통의사소통의사소통및및및및협업협업협업협업개선개선개선개선

� 요구사항구현가시성확보

� 명확한프로젝트목표및요구사항정의

� 개발개발개발개발공수및및및및비용비용비용비용감소감소감소감소

� 요구사항재사용프랙티스활용촉진

� 프로세스프로세스프로세스프로세스정확성정확성정확성정확성확인확인확인확인용이용이용이용이

� 변경에신속히대응할수있는엔지니어링 ‘agility’

확보

Value to OEM

Value to Suppliers

30


© Copyright IBM Corporation 2008. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product plans, release dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. All statements regarding IBM future direction or intent are subject to change or withdrawal without notice and represent goals and objectives only. IBM, the IBM logo, the on-demand business logo, Rational, the Rational logo, and other IBM products and services are trademarks of the International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

Contact Point : Oh Sung KwonEmail : [email protected] : 010-5399-7674

Effective Requirement Definition and Management in … · 2009-07-21 · 1970 - 1980 1980 - Present...

Documents

Transcript of Effective Requirement Definition and Management in … · 2009-07-21 · 1970 - 1980 1980 - Present...