Navigation

• Main Page

• Random Page
• Create a new Page
• All Pages
• Categories

• Administration
• File Management

• Login/Logout
• Language Selection
• Your Profile
• Create Account

Quick Search

Advanced Search »

This document inventory is for the Smart Meeting Manager.


Smart Meeting Manager Proposal (given in class)
Questions About The Smart Meeting Manager (given in class)

1. Assignment 1 Deliverables
2. Vision and Scope Document (VSD Template)
3. Operational Concept Document (OCD Template)
4. Business Rules
5. Actors For The Use Cases
6. Use Cases for SMM (UCT Template)
   • Book A Meeting
   • Book A Room For The Meeting
   • Define A Time For The Meeting
7. Event Action Lists for SMM (EAL Template)
   • EAL Book A Meeting
   • EAL Book A Room For The Meeting
   • EAL Define A Time For The Meeting
8. Assignment 2 Deliverables
9. Software Requirements Specification (SRS Template)

Edit

Why I've Used Wiki For This Assignment

I have selected Wiki environment to keep track of prepared documents for the SMM project. In Wiki, it is easy to edit documents and the changes will be recorded with the editor’s name. Users can browse to older versions and see who is changed what. This is useful if you work in a team and documents are created with collaboration of others.

There are many Wiki applications available as open source written with different languages on internet. I have used FlexWiki before but this site upgraded to ScrewTurn wiki now.

Because the documents are web based and published from a web server, sharing is easy amongst the team. Any member of the team can login to web site and browse and/or amend the documents. And changes will be attributed to the logged-in user.

Linking and referencing is very easy. Users can link to a document by referring its name only e.g. BusinessRules. If there is a summary written for this document, it will be visible when user hover the mouse pointer on to the link. This functionality increases the understanding of the document read.

It is good as an assignment delivery style. When I am writing for this assignment, I never printed a copy; I think, I have protected lots of trees. Also in an office environment or in a project group there is no need to print documents unless it is really necessary. Once you print, the version control capability and the originality of the document are lost. Even reviews can be done on wiki pages and comments can be added with your login name. A document manager should make the templates ready for the team to use and structure them like in an SDLC style. So that every team member will be aware of what documents to create and when. Also new starters can learn the system by reading the wiki documents.

Once the documents are ready, user can link them with the source control (modules, specific projects) to create a configuration management environment. Anyone can trace back to specific customer requirements from code. I am working on a small project at home to link Subversion, WebSVN, and FlexWiki to combine documents with code. I think this key point could convert a coder to a developer and finally to an analyst developer.