search

dewv / project-management-pomodoro

MIT License
0 stars 1 forks source link

Risk: too much or too little design definition #10

Open smattingly opened 6 years ago

smattingly commented 6 years ago

10 Issue by smattingly,

At one extreme, a pure waterfall process expects to fully define all design entities and map them to requirements before pursuing other activities. IEEE and other standards provide guidance and outlines for Software Design Description documents.

For many projects, a more realistic approach to design definition might be a combination of pseudocode, entity-relationship diagrams, UML diagrams, and/or screen mock-ups.

abed12345 commented 6 years ago
  1. must finish timer page
  2. connect timer page to GitHub.
  3. build a view for the teacher to see all the pomodoros in one place.
  4. build a database to store pomodoros information.
smattingly commented 6 years ago

I would suggest spelling out the design in terms of MVC services. I think we have a good handle on it but it needs to be captured in written documentation (can be very brief).

abed12345 commented 6 years ago

model: MySQL database that tracks pomodoros. views: timeclock webpage and gethub issue page. controllers: github api

JStanley19 commented 6 years ago

reviewed

JStanley19 commented 6 years ago

reviewed

JStanley19 commented 6 years ago

reviewed

JStanley19 commented 6 years ago

reviewed, continues to be high risk.

JStanley19 commented 6 years ago

reviewed, continues to be high risk, especially with new MVEC redesign.