보다스마트한협업개발을위한 IBM Collaborative Lifecycle Management … · 2012-08-20 · Application Lifecycle Management (ALM) Manages the flow of people, process and

1

보다 스마트한 협업 개발을 위한IBM Collaborative Lifecycle Management Solution

DongYoung Kim ([email protected])

Rational Software, IBM Korea

© 2012 IBM Corporation2

The Premier Event for Software and Systems Innovation

혁신은 소프트웨어에 의해 주도되고 있습니다

Source: Mobile banking: A catalyst for improving bank performance, Deloitte, 2010;and This Car Runs on Code, Robert Charette, IEEE Spectrum, 2009.

Mobile banking will bethe most widely used bankingchannel by 2020, if not sooner

The average 2010 automobile contains more lines of software

code than a fighter jet



Source: Numerous sources

2010 Spending in U.S. on governance, risk and compliance was $29.8 billion

IncreasingMandates

62% of projects fail to meet intended schedule

Unpredictability in Software Delivery

50% of outsourced projects are expected to under perform

Globally Distributed Softwareand Product Supply Chains

Complex, Multi-platformSystems and Applications

62% of companies have agile projects requiring integration with legacy systems

30% of project costs are due to rework and poor execution of requirements

Changing Requirementsand Time to Market

CostReduction

70% budget locked in maintenance and37% of projects go over budget

2010 Spending in U.S. on governance, risk and compliance was $29.8 billion

IncreasingMandates

62% of projects fail to meet intended schedule

Unpredictability in Software Delivery

50% of outsourced projects are expected to under perform

Globally Distributed Softwareand Product Supply Chains

Complex, Multi-platformSystems and Applications

62% of companies have agile projects requiring integration with legacy systems

30% of project costs are due to rework and poor execution of requirements

Changing Requirementsand Time to Market

CostReduction

70% budget locked in maintenance and37% of projects go over budget

그러나 소프트웨어 개발 현실은 녹록하지 않습니다Complexities in software delivery compounded by market pressures



그리고 효과적인 소프트웨어 개발을 가로막는 system들이 있습니다Anytime, for any team, silos create barriers to effective software delivery

2. Development

1. Business

3. Operations

“At some point, you take a step back, and you realize you have an awful lot of siloed systems that are limiting transparency across strategic projects.”

- Development DirectorTemenos, Inc.



해결책은 개발자간의 협업 및 정보를 공유할 수 있는 Application Lifecycle Management 솔루션

1. Business

2. Development 3. Operations

ALM manages the flow of:PeopleProcessInformation

ALM manages the flow of:PeopleProcessInformation



소프트웨어 개발은 다양한 역할 간의 효과적인 협업을 필요로 합니다

ApplicationLifecycle Management (ALM)

Manages the flow of people, process and information in an iterative cycle of software delivery activities

Analysts Quality Professionals

Release EngineersDevelopers

Architects

Project Managers



IBM Collaborative Lifecycle Management 솔루션

Optimize your team’s productivity

Collaborate across teams and create deep integrations across the lifecycle

Extend with role-based licensing

Unify infrastructure and protect current investments with a single, open, extensible platform

Support heterogeneous development across multiple platforms and technologies

RationalRequirements

ComposerRational

Team ConcertRationalQuality

Manager

RationalRhapsody

Design Manager

Rational Software Architect Design

Manager

Collaborative Lifecycle Management

Collaborative Design Management

Architect

Analyst

Developer

QualityProfessional

DeploymentEngineer

Engineer



What is required to deliver end-to-end visibility across teams, tools and projects?



IBM Jazz 기반 CLM 솔루션을 이용한생산성 향상과 스마트한 협업 개발

1. 스마트한 협업

2. 스마트한 계획

3. 스마트한 라이프 사이클 추적성

4. 스마트한 프로젝트 진척사항 파악

5. 스마트한 개발 프로세스 개선



스마트한 협업을 위해 고려해야 할 점Can your team…

…bring new team members up-to-speed quickly?

…overcome the barriers of multiple time zones when working with outsourced and distributed team members?

…find all the information related to a specific task?

…quickly grasp the “who, what, when and why” of team activities?



필요한 정보의 스마트한 공유를 통한 협업이 생산성을 향상시킴

Empower teams to collaborate on and review software development artifacts so they can incorporate feedback early and often aligning delivery with stakeholders’ vision

Provide a single source of truth hosted in a shared repository so that team members can collaborate effectively around the globe to build a collective intelligence

Make information immediately accessible to all team members in the context of their work



릴리즈 요구사항 정의 및 분석에 대한 협업

요구사항에 대한 토론최근 토론이 추가된 요구사항 하이라이트



릴리즈 요구사항 정의 및 분석에 대한 협업시 컨텍스트를 제공

요구사항 주석을 클릭하면 주석이 달린 요구사항을 알려줌



팀원과의 협의 및 피드백을 통해 완성함으로써 재 작업 감소시킴

테스트 케이스에대한 리뷰 및 승인

요구사항에 대한리뷰 및 승인

개발업무 처리결과에 대한 리뷰

및 승인

Reviews & approvals ensures artifacts are reviewed and/or approved by key team members and capture compliance requirements.



개발팀원은 자신의 작업 결과물인 Change Set를 팀원과 공유함

파일수정 후 체크인 , 전달 , 작업항목 연관 등 형상관리 작업을 수행합니다.

DeveloperWorkspace

Change Set

TeamStream

WindowsExplorer



“Defect” 항목에 처리 결과 “Change Set”을 증거로 연계함

“Defect”를 해결하기 위해 Source code를 수정합니다.

수정한 Source code를 Check in합니다 – Change set.

Change set과 “Defect”를 연계합니다.

Change Set

“Defect”



“Defect”에 대한 “Code Review” 프로세스를 강화함

Review 전 Review 후

PrjDevStream Developer

Workspace

Code Review : Accept

Change Set

“Defect”



개발팀의 개발 결과를 Continuous Build - Build break 여부를 파악하고 Build breaker에 메일을 통보함

PrjDevStream Developer

Workspace

BuildWorkspace

Change Set

“Defect”



개발팀의 빌드 결과를 검증팀에서 확인할 수 있음

Continually make the right things easy to find



빌드 결과를 통해 수정 및 해결된 사항 파악이 용이함- Build Compare 기능

Build 간 Source Code 변경 사항을 Build Compare를 통해 확인합니다.











스마트한 계획을 위해 고려해야 할 점Does your team…

…plan across the entire team?

…manually collect and report status?

…instantly see the impact of a change in project scope or resources?

…integrate planning with execution?

…plan for waterfall, iterative and agile environments?



실시간 정보를 바탕으로 한 계획을 통해 의사결정을 신속히 함– 소프트웨어 출시를 가속화함

Provides a single plan that spans requirements, development, and test, ensuring the whole team understands the overall scope of a project

Integrates planning with execution ensuring the entire team understands the true project status

Allows everyone to participate in keeping the plan current and accurate

Helps teams respond to the unexpected in a timely manner ensuring the team stays on schedule

DeploymentEngineer

Project Lead

Analyst Developer

Architect QualityProfessional

Planningand Execution



요구사항에 근거한 릴리즈 계획을 수립함

Collections focus team for:ReviewsSnapshotsImplementation



릴리즈 개발 계획을 요구사항 계획 및 테스트 계획과 연계함

릴리즈요구사항 Collection

릴리즈 개발 계획

릴리즈테스트 계획

라이프사이클 “릴리즈 계획” 연계

요구사항

개발항목

테스트케이스요구사항

개발항목

테스트케이스

Linked to Requirement Collection

Linked to Test Plan



개발 계획 업무에 대한 랭킹 정보를 공유하고 협업Team clearly understand the goals

Priorities are good.

Rankings are better!



개발 계획 및 진행 파악시 목적별 다양한 뷰를 활용함

22

33

11



개발에 필요한 정보를 제공해 줌Everyone participates in planning

Whole team sees dependencies

Stories decomposed into cross-discipline tasksPlans include all work



계획의 실행 결과를 공유함Deliverables and work products show results

Progress & Status are good indicators of execution.

Change Sets & Attachments are better !



필요한 정보를 곧바로 업데이트함Part of everyday work activities In place updates to status

automatically appear in the plan











Are we readyto release?

Are we aligned with the business?

Can we passan audit?

What defects were resolved in this release?

Which requirements are addressed in this iteration?

Are all of therequirements

tested?What defects are affecting

which requirements?

Project ManagerAnalyst

스마트한 라이프 사이클 추적성을 위해 고려할 점Can your team answer…

Quality ProfessionalRelease EngineerDeveloper

What is the quality of the build?

What is ready for me to test?

What defects have been addressed since the last

build?

How can I standardize when teams use different tools?

Where are the bottlenecksin our processes?

How can I speed up my builds?

Are build timesgetting longer

or shorter?

What requirementsam I implementing?

What testuncovered this defect,

on which environment and what build?

What changes occurred overnight?

Are there reusable components we can

leverage?

Can we implement in a way that supports maintainability?

Which requirements impact the design?

Architect



스마트한 라이프 사이클 추적성을 통해 품질을 향상시킴

Establish relationships between software artifacts

Identify and close artifact gaps, ensuring coverage across disciplines

Provide visibility into the completeness of planned items by inspecting all related artifacts

Provide easy access to related artifacts ensuring everyone shares the same view

Deliver transparency which enables everyone to make fully informed decisions based business priorities

Customer FinalProduct

BuildArtifacts

Environment Supporting Systems

Requirements Management

Initial Idea

Instant access to details from any point in development process



협업이 필요한 업무간의 추적성을 제공

릴리즈요구사항Collection

릴리즈 개발 계획

릴리즈테스트 계획

협업 업무간의 추적성

요구항목 테스트 항목

개발 항목(스토리)



Proactively respond to gaps (in red) as they surface throughout the project

Issues are quickly highlighted and resolved (in yellow)

추적성의 가시화를 통해 커버리지 및 완성도를 처리함



추적성 커버리지 및 관련 문제점을 하이라이트함

Link Type : value



요구사항, 구현, 테스트 작업에 대한 스마트한 협업을 통해품질 향상 및 관련 작업에 대한 예상이 높아짐

Developers understand the requirements, test criteria and test results

Developers understand the requirements, test criteria and test results

Testers define and execute tests cases with a clear understanding of requirements

Testers define and execute tests cases with a clear understanding of requirements

Teams collaborate and clarify the details of requirements

Teams collaborate and clarify the details of requirements

Creating a shared vision delivers what the stakeholders want

Whole team buy-in improves team trust, efficiency and focus

Everyone knows what work is needed by whom and when.

Traceability provides insight to knowing when you are DONE!

http://pokgsa.ibm.com/home/j/i/jinli/web/public/html/arch_ken.html



For the Developer

Rich Hoversprovides insight at your finger tips reducing time to value.

Clickable linksprovides valuable information on requirement

개발자 입장에서 구현 관련된 요구사항에 대한 정보를 제공함



테스트 작업의 결과가 즉시 개발자에 공유됨

Developers can see the exact test failure without having to ask and remediate it

Developers can see the exact test failure without having to ask and remediate it

Testers execute tests and submit defectsTesters execute tests and submit defects4-clicks to submit a defect

automatically linked to impacted artifacts

Test results are recorded and linked to test cases, and associated requirements

Test results can be linked to software builds

Everyone has visibility into the defects, their impact, and the action taken to resolve them



테스터가 제출한 결함에서 개발자는 보다 자세한 정보를 파악함

All roles can view the links on their artifacts.

Each user has their own perspective and user interface for viewing links.

Create, delete, navigate links on artifacts

Example: Developer sees the relationships on a defect

Traceability links on defects are automatically created



라이프 사이클 질의문 작성을 통해 손쉽게 정보를 파악함Answer the hard questions

Provides cross-discipline visibility of issues effecting delivery











스마트한 프로젝트 진척 파악을 위해 고려할 점Can your team…

…track desired improvements with metrics?

…minimize administrative overhead by relying on your environment to capture metrics?

…provide one view of project health at multiple levels?

…make steering decisions based on facts rather “guesstimates”?



스마트한 프로젝트 정보 파악을 통해 프로젝트 향방에 대한 예측력을 높임

Enable fact-based decision making (to communicate status, monitor progress, diagnose problems, identify corrective actions)

Steer projects and programs to deliver on-time

Apply Business Intelligence techniques to software and systems development

Weak measurement practice Strong measurement practice

Cancelled

Late

On-time

15%

5%

40%

20%

45%

75%

Measurement Practices Impact Project Success

Sources: Capers Jones, Measurement, Metrics and Industry Leadership, Copyright © 2002-2007 by Capers Jones LLCCapers Jones, Software Engineering Best Practices, Copyright © 2010 McGraw-Hill



대시보드에서 제공하는 정보를 바탕으로 프로젝트를 파악하고 진단함



자신에 맞는 정보를 구성할 수 있음Ensures the team has steering data from all disciplines

Mashup dashboards with information across silos

Easy to add viewlets to assist steering to completion



의사결정에 필요한 정보 파악이 용이함Easily answer steering questions

Click thru on the viewlet to drill into information

Take corrective action in-place



팀원도 자신의 대시보드를 구성할 수 있음

Customized by the practitioner

Mini-dashboards: available on any page











스마트한 개발 프로세스의 끊임없는 개선을 위해 고려할 점Can your team…

…allow team leads to determine how strict or lax the “rules of the road” should be?

…modify process enforcement over the life of a project, to encourage early-stage experimentation and end-game stability?

…leverage out-of-the-box templates that support traditional and agile workflows?

…change process “on the fly” as part of a continuous feedback loop?



끊임없는 개발 프로세스 개선으로 불필요한 비용을 절감함Improve software delivery through the ongoing adoption of best practices and automation to reduce manual, non-creative and error prone tasks

Promote incremental improvement of a project when needed

Enable breakthrough improvement by capturing best practices and reusing across teams

Allow everyone to participate with easy to adopt best practices at your fingertips.

Assess

SteerAct



프로세스 개선 항목을 통해 개선 영역을 파악함

Tracking Retrospectives help team members to collaborate on improvements

– Ranking of process improvements help to focus on where the team feels the biggest pain



개선 활동 협업을 수행하고 수행결과를 기록함

Team tracks the work of implementing an improvement



개선 결과를 Template으로 작성하고 차기 프로젝트에 활용함Support breakthrough improvement

Use and reuse of project templates is an example of breakthrough improvement

• Modify to match your organization’s process



라이프사이클 Template을 기반으로 “프로젝트” 구성함

분석가

“요구사항”프로젝트

개발자

“형상/변경 관리”프로젝트

품질 전문가(테스터)

“품질 관리”프로젝트

협업 기반 라이프사이클 “프로젝트” 구성 라이프사이클프로젝트 Template



프로세스 개선 활용 예 - 형상관리 정책 설정 유연성 활용형상관리 policy 정책 설정의 유연성을 제공합니다.

– Ex, QA 단계에서는 Defect와 연계되지 않는 소스의 반입을 허용하지 않음

– Ex, 새로 참여한 개발자의 경우, 동료의 검토를 받지 않는 bug fix의 반입을 허용하지 않음











IBM CLM 솔루션의 효율적인 협업을 통해 재작업 시간을 감소시킴

Require-ments Design Develop Test

Requirements ChurnChanging Requirements

Quality ChurnPersistent Defects


Planning, Change, Configuration &

Build Management

Quality Management

Rational Requirements

Composer

Rational Team Concert

Rational Quality Manager



IBM CLM 솔루션의 투명성과 추적성을 통해 개발 생산성 및 소프트웨어품질을 향상함

Rational Requirements Composer


Rational Quality Manager 3.0


QualityDevelopmentRequirements



IBM CLM 솔루션의 구성


Planning, Change, Configuration & Build

Management

Quality Management


Composer



22

3311



IBM Rational Requirements Composer 4.0 세부 기능Requirements Management for the Development Lifecycle

DefinitionRich-text documentsDiagrams: Process, Use CaseStoryboards, UI sketching & flowProject glossariesTemplates (formal/agile)

CollaborationReview & Approval DiscussionsEmail Notification

VisibilityCustomizable dashboardsProject dashboardsAnalysis viewsCollectionsMilestone tracking & status

ManagementStructure, Attributes/TypesTraceability, Suspect Link Filtering, Change HistoryTags, Reuse, Baselines, Reporting Metrics & Doc.

PlanningIntegrated planningEffort estimationTask management


Composer



11



SCMComponent based SCM enables

reuse across projectsComponent level baselinesChange set based for easy

addition or removal of featuresServer-based sandboxesUse RTC SCM or SVN, Git,

ClearCase or Synergy

Work ItemsDefects, enhancements

and conversationsView and share query resultsSupport for approvals and

discussionsQuery editor interfaceConnects to ClearQuest or Change

BuildAutomated Work item and change

set traceabilityBuild definitions for team

and personal buildsLocal or remote build serversMulti-level continuous integrationSupports Ant and command

line toolsCan integrate with Build Forge

PlanningIntegrated release/iteration planningEffort estimation & progress tracking taskboardsOut of the box process templates: formal or agile

Project TransparencyCustomizable web based dashboardsReal time metrics and reportsProject milestone tracking and status

IBM Rational Team Concert 4.0 세부 기능Planning Change, Configuration and Release Management


Composer



22



IBM Rational Quality Manager 4.0 세부 기능Requirements Management for the Development Lifecycle

Test PlanningComprehensive test planShared objectivesScope, Timeline, ResourcesRisk assessment

Test ConstructionRequirement driven testingTest environments coverageManual test authoringTest lab management

Test ExecutionManual test executionUse test automation toolsRecord test resultsSubmit & track defects

Reporting & DashboardStatus and progress trackingCustomizable live dashboardReal-time metrics and reportsCompliance and quality audit

Team CollaborationProcess enactment and enforcementReview and approvalTask managementRapid team member on-boarding


Composer



33



Product Owner

Defines & links requirements and defect to influence the development plan

Developers

Plan the iteration from requirementsDevelop & deliver changes Tester

Validate requirementsSubmit defectsTest the iteration

Plan Requirements

Find & Fix Defects

Requirements driven testingRequirements Management

Planning, Change, Configuration &

Build Management

Quality Management

IBM CLM 솔루션의 기능 요약


Composer



22

3311



Automation

Monitoring

IBM CLM – Jazz 기반의 솔루션의 특징


Composer



22

3311

• Simplified Licensing• Unified Administration• Integrated Installation & Setup• Flexible Deployment • Automated traceability link creation

Jazz 기반의 솔루션의 특징• Mashup/Personal/Mini dashboards • Cross-application reporting• Cross-application traceability views and queries• Linked plans with gap analysis



Developer productivity

Automated testing

Heterogeneous connectivity

Systems development

Business-role extensions

Mobile development

Build and deploy

IBM CLM - OSLC 기반의 솔루션의 특징 : 확장성 및 개방성 제공

External tool integrations• Git• Jira• HPQC



Summary : IBM Collaborative Lifecycle Management 솔루션

Optimize your team’s productivity

Collaborate across teams and create deep integrations across the lifecycle

Extend with role-based licensing

Unify infrastructure and protect current investments with a single, open, extensible platform

Support heterogeneous development across multiple platforms and technologies

RationalRequirements

ComposerRational

Team ConcertRationalQuality

Manager

RationalRhapsody

Design Manager

Rational Software Architect Design

Manager

Collaborative Lifecycle Management

Collaborative Design Management

Architect

Analyst

Developer

QualityProfessional

DeploymentEngineer

Engineer



www.ibm.com/software/rational

http://www.ibm.com/software/rational




참고 : IBM Jazz 및 OSLC의 커뮤니티 사이트

IBM Jazz 커뮤니티 사이트/ jazz.net OSLC 커뮤니티 사이트/ open-services.net



© Copyright IBM Corporation 2012. 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 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. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic 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.

www.ibm.com/software/rational



Documents

보다스마트한협업개발을위한 IBM Collaborative Lifecycle Management … · 2012-08-20 · Application Lifecycle Management (ALM) Manages the flow of people, process and