Team Robo: Difference between revisions
From ICO wiki
Jump to navigationJump to search
| Line 73: | Line 73: | ||
* Finalized the use-case diagrams | * Finalized the use-case diagrams | ||
* Completed the first draft of the class diagram | * Completed the first draft of the class diagram | ||
* | * Design the ERD diagram | ||
* Started creating the final analysis documentation | * Started creating the final analysis documentation | ||
| Line 83: | Line 83: | ||
* Finalize the class diagram | * Finalize the class diagram | ||
* Finalize the first draft of final documentation as a deliverable for our client meeting | * Finalize the first draft of final documentation as a deliverable for our client meeting | ||
===Monday - 01.04.13=== | |||
Things what we did that day: | |||
*Finalized the system class diagram | |||
*Completed the ERD diagram | |||
*Continue creating the final analysis documentation | |||
*Start creating mockups with mock up builder tool for each one of use cases | |||
Problems what we faced: | |||
*The documentation was more complicated than we expected | |||
Things what we plan to do: | |||
Finalize the documentation | |||
==Results== | ==Results== | ||
Revision as of 15:38, 1 April 2013
Team page for Deploying IT Infrastructure Solutions.
Team Members
- Veiko Vainu, IT College
- Andreas Plado, IT College
- Giorgos Ioannidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
- Konstantinos Michailidis, T.E.I. of Crete, Department Of Applied Informatics And Multimedia
Goal
- System design description, including:
- Component diagram
- Database diagram
- Sequence diagram
- Suggestion on database, programming language and reusable components.
- Creating a project time plan with at least two scenarios:
- Full scope
- Minimum scope
- BONUS:
- Prototype solution covering some part of the system.
Activity
Monday - 25.03.13
Things what we did that day
- Participate in lectures
- Learn
- We get to know each other through the exercises.
Tuesday - 26.03.13
Things what we did that day
- Composed a set of questions for the client.
- Started making a draft scenario for the client.
- Researched similar systems.
Problems what we faced:
- Lack of project details
Things what we plan to do:
- Client meeting
Wednesday - 27.03.13
Things what we did that day
- Met with the client
- Clarified project details
- We made the activity chart
- We divided roles
Problems what we faced:
- We didn't have problems today
Questions and answers from client:
- We asked the basic structure of the outcome
The outcome supposed to be the analysis part of the software.
Things what we plan to do:
- Continiue with undertaking the subtasks of the project
- Tasks List.pdf
Thursday - 28.03.13
Things what we did that day
- Analyse the whole scenario
- Started making the use-case diagram
Problems what we faced:
- We didn´t expect the scenario to be so complicated
Things what we plan to do:
- Finish the use-case diagram
- Start with class-diagram
Friday - 29.03.13
Things what we did that day
- Finalized the use-case diagrams
- Completed the first draft of the class diagram
- Design the ERD diagram
- Started creating the final analysis documentation
Problems what we faced:
- The database was more complicated than we expected
Things what we plan to do:
- Finalize the class diagram
- Finalize the first draft of final documentation as a deliverable for our client meeting
Monday - 01.04.13
Things what we did that day:
- Finalized the system class diagram
- Completed the ERD diagram
- Continue creating the final analysis documentation
- Start creating mockups with mock up builder tool for each one of use cases
Problems what we faced:
- The documentation was more complicated than we expected
Things what we plan to do: Finalize the documentation
Results
Summary of what we did and solution what we developed
Final documentation
Analysis
Solution
IP Feed-back
Konstantinos Michailidis
I liked this and that. Didn't like.
Giorgos Ioannidis
I liked this and that.
Andreas Plado
I liked this and that. Didn't like.
Veiko Vainu
I liked this and that.
