1 / 19

Using Collaboration Tools to Improve Artifact Consistency in CS577 Projects

Using Collaboration Tools to Improve Artifact Consistency in CS577 Projects. Allen Kou. Motivation. Concurrent engineering can lead to inconsistent artifacts Finding and fixing inconsistencies is time consuming and tedious It’s easy for minor inconsistencies to go unnoticed.

cullen
Download Presentation

Using Collaboration Tools to Improve Artifact Consistency in CS577 Projects

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Collaboration Tools to Improve Artifact Consistency in CS577 Projects Allen Kou

  2. Motivation Concurrent engineering can lead to inconsistent artifacts Finding and fixing inconsistencies is time consuming and tedious It’s easy for minor inconsistencies to go unnoticed

  3. Sharing Artifacts • Common Approach: Email and Team Website

  4. Problems • Availability • Referencing out of date documents • Intermediate versions may not be available • Everyone may not have same versions • Does not promote collaboration • Only focus on your own document • Ignore other documents • Documents are large • Tedious to search individually

  5. Examples of Inconsistency 1 SSAD Use Case

  6. Examples of Inconsistency 1 SSAD Use Case SSRD Requirement 6

  7. Examples of Inconsistency 2 FED Evaluation Summary SSAD Styles, Patterns, Frameworks

  8. Examples of Inconsistency 2 FED Evaluation Summary SSAD Styles, Patterns, Frameworks ASP.NET MVC 3 requires Visual Studio 2010! 8

  9. Collaboration Tools • 3 extremely popular tools • 1) Google Docs • 2) SharePoint • 3) Zoho

  10. Google Docs – Features 1 • Search collections • Collections • Sharing Settings • Version Management

  11. Google Docs – Features 2 • Concurrency control • See who else is viewing the document • Chat with others viewing the document • Concurrent edits appear in real time

  12. Google Docs – Pros and Cons • Pros • Intuitive & easy to use • Search entire documents • Access & concurrency control • Cons • Messes up 577 template header / footer format • Error converting CS 577 documents • No version management for doc? • Users are polarized • Requires internet access • 1 MB single file upload limit?

  13. SharePoint Features • Collaborative Document Management • Checkout documents • View revisions • Access control • Integration with Office • Build collaboration environment • Etc …

  14. SharePoint… Imagefromhttp://blog.pentalogic.net/2010/11/how-much-does-sharepoint-cost/

  15. Zoho – Features Same main features provided by Google Docs

  16. Zoho – Features 2 • Offline mode • Install a plugin • Access documents while offline

  17. Zoho – Features 3 • Microsoft Office plugin • Access and edit Zoho documents using Office • Windows only

  18. How do collaboration tools help? • If we change Requirement CR-38 (based on the earlier example) • Search all documents to see what references CR-38 • Modify other documents as necessary • Every member can easily access the most up to date document • Easier to track progress and share information • Search all documents

  19. Conclusion • Many effective tools for collaborative document management • Each have strengths and weaknesses • Superior to only using emails and the team website • Fixing inconsistencies in artifacts is tedious and difficult • Document management tools can reduce the number of inconsistencies

More Related