iRise and Automation: The Nuts and
Bolts of the Software Development
Lifecycle
Mike Hughes
Mike
Hughes
iRise, Director of Customer Solutions
1
iRise Company Confidential © 2012 All rights reserved. Session Overview
Creating stunning visualizations is only the tip of the iceberg! Learn about automation solutions for creating simulations, documenting requirements, producing specification documents, estimating effort populating requirements into other platforms generating
effort, populating requirements into other platforms, generating code and test scripts, and monitoring iRise usage. Whatever your role, there is something in the platform that will help you get your
role, there is something in the platform that will help you get your job done more effectively.
2
iRise Company Confidential © 2012 All rights reserved. About Me
•
•
•
•
3
Mike Hughes
Director of Customer Solutions
Director of Customer Solutions
3 years with iRise
14 years IT consulting
14 years IT consulting
iRise Company Confidential © 2012 All rights reserved. The Big Picture
Mission Possible – Advanced Track Breakdown
Workshop Facilitation
Managing the process Preparation
Maximizing Stakeholder Participation
p
Team Based Modeling
Creation and Iteration
Capturing and Managing Feedback
Online and offline techniques
Online and offline techniques
4
iRise Company Confidential © 2012 All rights reserved. Automation
Documents, Code, and Integrations
g
Agenda
• Beyond visualizing requirements
• Solutions
–
–
–
–
Documentation
Generating code
Downstream integrations
What’s coming?
• Q&A
5
iRise Company Confidential © 2012 All rights reserved. Beyond visualizing requirements
Real‐Time, Team‐Based Collaboration
A l t
Analysts
D i
Designers
D l
Developers
Create/Iterate Simulation
Plan/Prepare
A hit t
Architects
QA T
QA Teams
B i
Business Stakeholders
St k h ld
Gather Feedback/Consensus
Generate
Deliverables
A l t d P j t D li
Accelerated Project Delivery
• Project Scenarios
• Reusable Content
• Roles / Roles /
Responsibilities
6
•
•
•
•
Screen Layouts
• Capture Feedback / Data Flow
Iterate
Business Rules
Business Rules
• Review Changes
Review Changes
Capture Requirements • Validate Solution
iRise Company Confidential © 2012 All rights reserved. •
•
•
Documents & Specifications
UI Code
UI Code
Training Content
Documentation - Requirements
What?
•
•
•
•
•
Capture text‐based requirements in iRise document view
document view
Export requirements to CSV format
Import requirements from CSV
Update and add requirements from external
Update and add requirements from external sources
Enrich requirements with other data
How?
Wh ?
Why?
•
•
7
Pass requirements to and from other platforms
q
y
Requirement meta‐data can be seen by iRise modeler and also included in custom reports.
iRise Company Confidential © 2012 All rights reserved. Tip #421: Enrich your iRise text requirements
Tip #421: Enrich your iRise text requirements
You can add other columns of requirement meta data to the exported CSV fil
CSV file so that, after importing, this data is visible in document view. th t ft i
ti
thi d t i i ibl i d
t i
Simply preface column names with rm_
8
iRise Company Confidential © 2012 All rights reserved. Documentation – Custom Report
What?
•
•
•
•
Export your project to XML format
p y
p j
All project data is present
Includes folder of project images
Follows a well defined specification (XSD)
Follows a well defined specification (XSD)
How?
Why?
y
•
•
•
9
XML data is easy to transform
Prepare data for other systems
Create custom specifications/reports
iRise Company Confidential © 2012 All rights reserved. Tip #512: Use an XSLT capable tool
Tip #512: Use an XSLT capable tool
Writing XSLT by hand is cumbersome and error prone. There are many i
inexpensive tools that facilitate the process of creating, running and i t l th t f ilit t th
f
ti
i
d
validating XSLT files. For example, EditiX
10
iRise Company Confidential © 2012 All rights reserved. Tip #571: Start with the end state
Tip #571: Start with the end state
If you wish to build a custom report it is simplest to start with the end state Word document Replace content with placeholders that will be
state Word document. Replace content with placeholders that will be easy to find in the XML. These XML placeholders will be converted to XSLT statements.
Check out: http://www.w3schools.com/xsl/
11
iRise Company Confidential © 2012 All rights reserved. Generating code
What?
•
•
•
•
•
•
Generate code from iRise simulations
F
Focus on front‐end
f t d
Template‐based
Align with your technology standards
Supports virtually any tag‐based UI framework
i
ll
b d f
k
Integrated with Definition Center security
How?
Why?
•
•
12
Reduce time spent coding UI
Enforce UI coding standards
iRise Company Confidential © 2012 All rights reserved. Tip #593: Use CodeGen with iRise asset libraries
Tip #593: Use CodeGen with iRise asset libraries
The best way to use CodeGen is to align CodeGen templates with iRise asset libraries. In this way when reusable content is used to assemble a t lib i I thi
h
bl
t ti
dt
bl
simulation CodeGen already knows how to translate the pages into code.
13
iRise Company Confidential © 2012 All rights reserved. Downstream integrations - Connect
What?
•
Pre‐built integrations to:
–
–
–
•
•
IBM Rational Requirements Composer
IBM
Rational Requirements Composer
HP ALM CaliberRM
How?
Bi‐directional capability
p
y
Synchronize iRise chapters and requirement text
Why?
•
•
•
14
Improve requirement traceability
Assess requirement coverage
Facilitate impact assessment
iRise Company Confidential © 2012 All rights reserved. Tip #478: Bi directional integrations are confusing
Tip #478: Bi‐directional integrations are confusing
While most of our integrations support bi‐directional synchronization it i i l t ti k ith
is simpler to stick with one direction. Generally it makes the most sense di ti
G
ll it
k th
t
to update requirements at the source so if iRise is the source for the requirement, update it in iRise.
requirement, update it in iRise.
15
iRise Company Confidential © 2012 All rights reserved. Downstream integrations - iConnect
What?
•
•
•
•
•
REST‐based web services
OAuth security tied to Definition Center groups
security tied to Definition Center groups
Standards‐based XML and JSON output
Access • Events • Requirements • Users
• iDocs • Project data
Create/Update • Users
• Requirements
• iRise model
How?
• Groups
Why?
•
•
•
16
Easily pull iRise data into other platforms in real‐time
y
Build your own utilities
Analyze iRise usage
iRise Company Confidential © 2012 All rights reserved. What’s coming?
HTML
importer
17
Project estimation
iRise Company Confidential © 2012 All rights reserved. 18
iRise Company Confidential © 2012 All rights reserved.