-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Notes of 24th Jan:
Looking for something in the middle of myFuture and myCourses Co-op progress - Tracking all the documentation, steps,.looking at co-op as a course, Co-op have 2-3 credits, A linear timeline Forms?? Acceptance forms, evaluation forms, should be pdf's because it's easier to sign Problematic - Missing deadlines, No need to implement penalties 4 co-ops. A semester each The web will have a richer application than Android 75 students in the 1st batch, few hundred later. Co-op admin, group statistics, How many students are done with co-ops and so on ... Academics Program Manager, Report which courses helped you in the co-op and which didn't The co-op needs to be approved. Student can provide a list of courses they have taken until now and then report usefulness. Example: 10 students from Ericsson, 3 academic managers. 3 reports from the students, 1st within 2 weeks, and the last 2 in the last 2 weeks. We can make safe assumptions without contradicting given requirements.
Notes of 27th Jan:
To Do:
Sign up for Poll. Set up Deadline. Contact other groups.
Deadlines:
Finish Deliverable 1 by Friday, February 8th.
Finish 1. Requirements Model today Sunday, January 27th. Finish 2. Domain Model by Wednesday, January 30th.
Questions,
Should the student add co-op courses on mycourses? What courses? During the co-op term, they need to submit technical reports to myCourses? What does No.3 mean, backlog? What is the project wiki?
Notes of 29th Jan:
To Do:
Finish requirements model today, January 29th. Finish Domain Model by Tomorrow, 30th Jan.
TA Comments from meeting on 29th Jan:
Use only shall or may. Don't use should. What instead of how? The system shall be able to authenticate users. Remove the box part. Inform the student of his progress. No UI requirements. Remove multiple submissions.
2, 3 are more functional. Reword them to be non-functional.
- Project Discussion
- Detailed look at student viewpoint
- Understanding of functional and non-functional requirements
- First Draft of Requirements
- Noted down questions and confusing parts to ask the TA, customer and prof
- Finalized requirements
- Draft of User Case Diagram
- Discussion of Domain Model and all team members were told to review Domain Modelling slides
- Created Domain Model
- Team members split up work to focus on different parts of the deliverable (Domain Modelling and Persistence Layer)
- Finalizing Domain model
- Begin coding persistence layer
- Begin documentation part of deliverable
- Debugging issues in testing of the persistence layer
- Finalize documentation
- Finalize all aspects of sprint 1 for submission