1 Software Project Lifecycle Collaboration :: The Wiki Way June 25, 2008, 3:00PM – 4:00PM EST Serebrum Corporation 555 US Highway 1 S, Iselin, NJ 08830 www.serebrum.com | [email protected] The Wiki Way
Dec 03, 2014
1
Software Project Lifecycle Collaboration :: The Wiki Way
June 25, 2008, 3:00PM – 4:00PM ESTSerebrum Corporation
555 US Highway 1 S, Iselin, NJ 08830
www.serebrum.com | [email protected]
TheWiki Way
2
Agenda
• Introduction: The Wiki Way Krishna Polineni
• Features Demo Sushil Vegad
• Software Lifecycle Use Cases Sushil Vegad– Project Planning (CMMI)– Requirements Management
• Next Steps
• Q&A
3
Serebrum Profile
• Develop Custom Applications– eBusiness and eGovernment Focus– Enterprise Modernization (Legacy Web)– Portals, Content Management, Collaboration– Web 2.0: High Usability (Ajax), Search
• Axon Enterprise Collaboration Portal– Wiki approach to enterprise collaboration– EASE OF USE: #1 Priority– 100% Ajax, Java EE– On Premise or On Demand
4
NSF SBIR 2006.2 Research GrantProject BrainStormTM – Collaborative Customer Requirements Elicitation for Distributed Software Teams
Investors
DoD Navy SBIR 2006.1 Research GrantA Security Framework for WikisTopic: Cross-Domain Collaboration PortalExplore use in military intelligence capture and sharing
5
6
The Problem• Team Collaboration
– Projects are getting larger – Requirements! Estimates! Issues!– Teams are distributed – across time zones– Current solutions do not empower users!– Email / IM / Blogs: Information Overload!!!
7
The Solution: Empower the User!
Knowledge Management
eLea
rnin
g
Budgeting & Forecasting
Porta
ls
Supply Chain C
ollaboratio
n
Application Lifecycle
Managem
ent
Collab
orat
ion
CMS
8
The Solution: Easy Collaboration
Knowledge Management
eLea
rnin
g
Budgeting & Forecasting
Porta
ls
Supply Chain C
ollaboratio
n
Application Lifecycle
Managem
ent
Collab
orat
ion
CMS
Wiki
9
Wiki-centric Collaboration
Wikipedia.org(MediaWiki)
Stage 1:Proof of Concept
Open Source • Confluence
• PBWiki• MindTouch etc.
Stage 2:Basic Business Wikis
MicrosoftSharePoint
Stage 3:Wiki-embedded
Collaboration Systems
Serebrum Axon Collaboration
Portal
Stage 4:Wiki-centric
Collaboration Systems
10
Enterprise Wiki Checklist
• True WYSIWYG Editing
• Versioning and Rollback
• Topic Hierarchy / Ontology
• Powerful Search• Easy Publishing
• Role-based Access Control
• Data Security• Compatible with
Existing Infrastructure• Extensible via Web
Services
11
Enterprise Usage Scenarios
Functional Area Potential Uses
Across the Enterprise
• Knowledge Management• Project Management and Control
Software Engineering, Consulting
• Requirements Management• Project Management and Control• Collaborative Authoring and Publishing
Finance • Budgeting and Forecasting• Sarbanes-Oxley Compliance
Sales & Marketing • Campaign Development• Collateral Management
Human Resources • Policies and Benefits• eLearning
12
Global Menu
Workspace
Display Area
Workspace
Search
Editable Content
Document Management System
Layout
13
Tree Menu(Create, Cut, Copy, Paste, Delete, Rename)
Topic Tree
Topic Tree
14
WYSIWYG Editor
Editor ToolbarEditor
15
View Topic Version 1
Rollback to Version 1
Version Control and Rollback
16
Link to Schedule
Interlink Topics
17
Switch to topic ‘Schedule’
Interlink Topics
18
Document Management System (DMS)Click Attach
19
Select Copy
Copy Paste Documents
Select Paste
20
WebDAV: Desktop Integration
Document Repository on Windows File System
21
Enter search keyword
Search Results
Search
22
Search Results linking to Topic
Search Window is minimized
Search
23
AxonDocument Assember
xHTML
DOC / TXT
HTML
Editor
Export
RTF
xHTML
eHelp(JavaHelp, HTMLHelp)
Axon Publishing Model
24
Manage Users
Manage Groups
Move to Admin Console
Role Based Access Control (RBAC)
Manage Roles
Manage Spaces
25
26
Project Management
• Initiation
• Planning
• Control
27
Select New Topic
CMMI Level 2 Standards Example
Enter Topic Name
28
New Topic Created
CMMI Level 2 Standards Example
29
Drag n Drop Topics
Export Publish Select Export
DocumentFormats
30
Publish to PDF
Topic Hierarchy
31
Lock the Document
Project Plans
32
Contract Documents
Contract Documents
33
Status Reports
Status Reports
34
Change Order Documents
Workflow Window
Approved
ApprovalPending
Rejected
Approval Workflow: Change Orders
35
Requirements Management
• Business Requirements– Flow Diagrams– Use Cases (Import from Word, Edit)
• Software Requirements– Functional Specs– Requirements Templates– Traceability Matrix – Req – Glossary
36
Business Requirements
Use a requirements definition template specific
to your business
Embed or attach process flow
diagrams. DefineBusiness rules
Easy Editing by Business Users
37
Use Case Example
Import your existing
templates from Word
38
Convert Word Templates to Web-based Collaborative Content
39
Software Requirements
Imported from Word for
Collaborative EditingIEEE Standards
Template
Intra-link
40
Traceability Matrix
Intra-link Requirement # to Relevant Topic
Intra-link
41
42
Next Steps
• Slides will be emailed to all attendees
• Q & A to be emailed as an addendum
• One-on-One Demos
• Onsite Trials
• Webinar: Collaborative Knowledge Management / eLearning– Wednesday, July 30,
2008, 3PM – 4PM
• Krishna Polineni– [email protected]– 1.877.WebSphere
x201
43
Questions & Answers• How do we control unqualified users from contributing meaningless information?
– Axon implemented a robust role-based access control mechanism. Depending on the space manager’s judgment, “Read Only” or “Read-Write” rights can be enforced. Further, a topic can be locked from any future edits once it is at a satisfactory level of information.
• What are your thoughts on user adoption and integration with existing technologies?– Users adopt tools that are easy to use. Axon was designed with this in mind. Axon is
architected to interface with existing repositories such as FileNet, Vignette, Oracle, DB2 or SQLServer.
• How does Axon compare with SharePoint?– Axon delivers what SharePoint delivers. Our feedback from users indicates SharePoint is
being used more as a share drive. It requires programming to do anything meaningful. If it is too difficult to use, users won’t use it. Axon is designed from the ground-up to be used with little or no training.
• What is the Axon architecture?– Axon is based on the Java EE architecture with a 100% Ajax interface. It can run on any
operating system and interface with any database. Axon comes with a self-contained mySQL DB and LDAP so it can operate stand-alone as well.
• What is the licensing model?– Axon is available on-premise on a per CPU or per user basis. We can also host it on a per
user basis.