-
Notifications
You must be signed in to change notification settings - Fork 46
Deliverables
Jared Smith edited this page Jan 22, 2015
·
4 revisions
###List of Deliverables
- Team Creation
- VM/ VCS & Bug Tracking tool setup
- Project Requirements document
- Design Document
- Release 1
- Team reflection
- Beta release
- Release 2
- Post mortem
- I do not care which one you use, however I would advise not spending much time selecting one, or setting one up yourself.
- One good one you may use can be found here.
- For submission, you may place a link with the necessary login information into the dropbox. You may place this in a text file
- You will have the appropriate VM supplied to you.
- Play around with the VM and put some simple hello world files on there.
- Make sure everything is squared away and your team has access to all the files.
- As far as a version control system goes, I am more than happy to create a SVN account for you on the SE machines. - However, I do realize not everyone loves SVN. If you have your own Version Control System (VCS) that you would rather utilize, feel free to do so. A word of warning: any issues with your VCS are yours to deal with, and the customer will not be happy with project delays due to issues with your VCS.
- These should be kept up to date as the term progresses.
- These are borrowed from 261. Feel free to tweak as you see fit. You may also borrow ideas off the web.
-
Requirements Document which should include (but not limited to):
- Sequence diagrams
- Include all wireframes try this
- If you choose to use MVC, make sure to go into details
-
Design Document
- Test Plan
- Class Diagram
- Proper development & “production”environment setup.
- Virtual machines
- Deployment process
- Bug Tracking
- Version control system
- Main page setup
- Facebook tie in
- You may leave all of your source code in your Version Control System. There is no need to submit.
- Small .pdf document containing:
- Your version control system link & any appropriate logins
- Links to your production and staging applications (which are properly tagged as R1)
- Stock ticker (Retrieve information from existing external API’s)
- Updated documentation (design & requirements).
- Your staging & production environments should be mirrors of each other.
- Create a virtual directory for the release titled R1.
- This means that the release should be http://vm549-x.se.rit.edu/R1/
- Make sure that your website is publicly accessible to the outside world. This is required for the 1st deliverable and I encourage you to test your application early & often.
- “Final” deliverable is on the production website.
- Other items as will be defined by customer,
Presentation guidelines can be found here
Post Mortem guidelines can be found here
- Two main additions for functionality include:
- Stock ticker (Storing information)
- Calendar
- Other items as will be defined by customer,
- Updated documentation.
- Small .pdf document containing:
- Your version control system link & any appropriate logins
- Links to your production and staging applications (which are properly tagged as R1)
- Analytics feature for customer. You will need to elicit the precise details with the customer.
- Something like Google Analytics here is fine.
- A fully implemented system with good usability.
- Your staging & production environments should be mirrors of each other
- “Final” deliverable is on the production website.
- Chat feature.
- Chat & save chat history
- Presentation adheres to several guidelines as what was done for R1.
- Create a virtual directory for the release titled R2.
- This means that the release should be http://vm549-x.se.rit.edu/R2/
- You may leave all of your source code in your Version Control System. There is no need to submit.
- All data should be stored in your MSSQL database. Do not plan on storing anything in local files (IE .csv or .xml files)
- Everything should be as functional as possible. Additionally, the application should be much more aesthetically pleasing.
- Be sure that the database is properly setup. This includes:
- Schema
- Propagation mechanism
- Functionality
- Security (you can discuss this with customer)
- Application should work in:
- Various versions of Internet Explorer
- Various versions of FireFox
- Various versions of Chrome
- Mobile devices (Iphone, Ipad, Android)
Presentation guidelines can be found here
Post Mortem guidelines can be found here