Team Robo: Difference between revisions
Line 120: | Line 120: | ||
===Final documentation=== | ===Final documentation=== | ||
[https://wiki.itcollege.ee/images/c/c4/Final_RoboTeam_documentation.pdf SRS Documentation (IEEE Std 830-1998)] | |||
==IP Feed-back== | ==IP Feed-back== |
Revision as of 09:41, 4 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:
Things what we plan to do:
- Finalize the documentation
- Meeting with customer at 19:00 today and find out next steps of the Project
Tuesday- 02.04.13
Things what we did that day:
- (Yesterday)Met with the client to get feedback on what has been done so far, and what should we do from here on.
- Finalized the description of the use-cases
- Made changes to the ERD diagram
- Made changes to the system class diagram
- Completed most of the final analysis documentation
- Researched information about possible prototype implementation
Problems what we faced: One of our team members computer malfunctioned
Things what we plan to do:
- Make a presentation for the final client meeting
- Practice presenting the final work
- Finalize the documentation
- Make a prototype of a part of the system (double elimination tree generation)
Results
Summary of what we did and solution what we developed
Final documentation
SRS Documentation (IEEE Std 830-1998)
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.