Embedded Files
This is a list of main deliverables of each project. It will posted any new deliverable here, if necessary.
General considerations
General considerations
- Project to be developed must have a defined scope (Doesn´t exceed 16 weeks of work).
- It should be taken into account that not all projects to be developed in the course must be of the traditional type, which goes through all stages of the development cycle of a system, due to the duration of the course, which in many cases does not allow the development of a complete system during the 16-week semester.
- The deliverables consist of the software product and corresponding documentation:
- Development process (what was done)
- Document (software models)
- Video or Demo (Technical) and Video or Demo (User´s guide)
- Setting up the environment (Current Settings and Recommended Settings)
- Conclusions and recommendations
- Software artifacts (software products)
- Article written between the teacher and the students
- Development process (what was done)
Weeckly Meeting - Every Wednesday
Weeckly Meeting - Every Wednesday
8:00 am - Control Horas Extra
- Josué, Kevin, Anthony
- External consultant
- Customer: Juan Carlos Rodríguez
8:45 am - Registro Elegibles
- Kenneth, José Antonio, Génesis
- External consultant
- Customer: Juan Carlos Rodríguez
9:30 am - Gestión de Permisos
- Gabriel, Andrés y Cristian
- External consultant
- Customer: Lizeth Rodríguez
10:15 am - Gestión de Resoluciones
- Stewart, Alejandro
- External consultant
- Customer: Lizeth Rodríguez
11:00 pm - Contactos Clientes
- Michael, Freddy
- External consultant
- Customer: Yorleny Badilla
Deadline - (Milestone) - [Description]
Deadline - (Milestone) - [Description]
√ August 1st - (Course introduction) - [General presentation and available projects]
- General Guidelines
- Project asignment
- Read documentation related to the assigned project
√ August 8th - (Environment established) - [Set up the environment for developing the system]
- Write down a document which specifies the software needs
- Rehearse a task distribution
- Set up the development environment
August 15th - (Software Requirements Specification) - [Document which specifies the software needs]
- Document for Software Requirements Specification
- Be prepared for the Kick-Off Meeting
August 22nd - (Kick-off Meeting Minute) - [Minute of the first meeting with the project team and the client of the project]
- Make the arrangements for a meeting with thecnical people
- Kick-Off Meeting
Release 1
Release 1
- September 5th - (Sprint 1 Review) - [A document to convey the status of a project]
- September 19th - (Sprint 2 Review) - [A document to convey the status of a project]
- October 3rd - (Sprint 3 Review) - [A document to convey the status of a project]
Release 2
Release 2
- October 17th - (Sprint 4 Review) - [A document to convey the status of a project]
- October 31st - (Sprint 5 Review) - [A document to convey the status of a project]
- November 14th - (Sprint 6 Review) - [A document to convey the status of a project]
Final Release
Final Release
November 21th - (Final Project progress) - [Final advance has to be shown. Ready final deliverables.]
- It would be expected you all to have completed the documentation.
- Of course, it is necessary to have finished the product development.
Google Sites
Report abuse