1 22-03-25 Taraxacum Anne Jon Schoonhoven Magdalena Jurić Final Prototype
Dec 28, 2015
123-04-19
Taraxacum
Anne Jon SchoonhovenMagdalena Jurić
Final Prototype
• Make sharing of learning materials easy– Teachers can view, add, remove and edit
shared resources
• E-learning environment– Students can view, browse and
comment/discuss resources shared with them
223-04-19
Project Recap
323-04-19
Today’s Hats
Customer
Project Manager System Architect
423-04-19
Today’s Outline
• Project Metrics
• Project Experiences– Communication– Work Deviation– Project Result
523-04-19
Project Metrics
• Deliverables– On time and fulfilled
• Features– Implemented 66 out of 72
• Dropped 2 customer requirements• Dropped 4 additional requirements
623-04-19
Project Metrics
• Communication– Weekly Team meetings– Daily IM / Skype– Documentation– Redmine (project management software)
723-04-19
Project Metrics
Spend Hours - Ratio
823-04-19
Project Metrics
Spend Hours – Time Line
923-04-19
Project Metrics
1023-04-19
Project Taraxacum
1. Fresh Start– Focus on Process
2. Productive– Focus on Development
3. Challenging– Focus into Oblivion
1123-04-19
Project Taraxacum
• 3rd Iteration went worser than planned.– Blame the Project Manager
• Other suspects– Communication– Holidays
1223-04-19
Communication
• Distance of Communication– Culture– Medium
• (F2F, Skype, Mail, IM, • Redmine, SVN)
1323-04-19
Case
“ Create an simple WYSIWYG editor for the plaintext resource.As an attachment you will find a custom version of TinyMCE editor [..] “
Cultural Differences
Type of Communication Mostly DigitalTowards Shallow (!)
Notion Of Time “Finish by Sunday”
Type of Thinking Task Minded & Goal Minded
1423-04-19
1523-04-19
Product Status
• Shift of context use– Hierarchical – Community
• Product is “in between”
1623-04-19
Initial Requirements
• Teacher– Browse – Manage courses and
topics – Share resources– Create exercises– Search
• Student– Browse shared
materials– Take and print notes– Share flashcards– Practice exercises and
get results– Ask questions– Signal errors– Search
1723-04-19
Design decisions
• Domain Driven Development
• Separation of concerns
• Layered architecture (MVC)
Good• it was easier to extend system• independent development of layers
Bad• initially time consuming
1823-04-19
Solution structure
1923-04-19
Backend design
• Data access layer– Repository– Unit of Work– EF mapping to DB
• Model layer – POCO classes
• Service layer– Implements functionalities– Hides details
2023-04-19
Backend design - Model
2104/19/23
Frontend design
• Controller– Using service functions– Data provider for views
• View– Razor views (HTML + CS code)– Used to preview pages
2204/19/23
Integration with other tools
• TinyMCE– Javascript WYSIWYG text editor
• Disqus– Comments community platform
2323-04-19
System Demo
– Registration of new user– Create Course– Create Exercise– Perform Exercise– Kudo Course– Comment– Perform Search
2423-04-19
System Demo
http://ec2-184-73-21-178.compute-1.amazonaws.com/
http://dsd.skoonhoven.net/mvc/
2523-04-19
System Demo
• Plan B – Video
2623-04-19
System Demo
• Plan C – Screenshots
2723-04-19
What’s Next?
Strengths
•Well documented•Flexible in features
Weaknesses
•Red Code•Performance
Opportunities•Niche Market
Threads•Not the only player on the market
2823-04-19
Conclusion
• Requirements Struggling
• Level of Knowledge Different
• Effort Consuming
2923-04-19
Discussion
• Target minded or Process minded– Running Late– Efficiency
• Task explanation vs execution
3023-04-19
Discussion
• What was the biggest gap in the project?– Knowledge– Distance– Culture