On 25 Oct 2016, at 12:00, moose-dev-request@list.inf.unibe.ch wrote:Date: Mon, 24 Oct 2016 21:16:57 +0200
From: Tudor Girba <tudor@tudorgirba.com>
To: Moose-related development <moose-dev@list.inf.unibe.ch>
Subject: [Moose-dev] Re: Moose-dev Digest, Vol 122, Issue 16
Message-ID: <72E2F438-2212-401B-B9A2-499146BF05D2@tudorgirba.com>
Content-Type: text/plain; charset=utf-8
Hi,
The current draft of The Moose Book contains an introductory chapter that offers 3 hands-on exercises. I use these for tutorials with professional programmers:
http://themoosebook.org
Cheers,
DoruOn Oct 24, 2016, at 8:45 PM, Offray Vladimir Luna Cárdenas <offray.luna@mutabit.com> wrote:
Thanks Alexandre and Abdelghani. This recent discussions on first approaches to Pharo, Moose and Agile Visualization are pretty interesting and the supporting material is also.
Cheers,
Offray
On 24/10/16 09:05, Alexandre Bergel wrote:Do you have any particular exercise?
Here are some links:
https://www.dropbox.com/s/bimp0wpkwewdksq/02-FirstContactWithMoose.pdf?dl=0
https://www.dropbox.com/s/0dj579b2g5dhlry/03-Pharo.pdf?dl=0
https://www.dropbox.com/s/vadoc20npmfg5c0/04-Roassal.pdf?dl=0
https://www.dropbox.com/s/xqcvnodsfer7c7q/05-Tarea1.pdf?dl=0
I can give you the source using the Keynote file format if you wish. Let me know- What kind of criteria do you as them?
Cross-cutting concern, dependencies, code size are usually easy to spot.- How do you ask them to characterize the architecture and do the software assessment?
05-Tarea1.pdf mentions this.- How do you use visualizations?
04-Roassal.pdf is about that.It would be nice to have the feedback from someone that has already made the experiment ;)
Let me know if this helps
Alexandre
AbdelghaniMessage: 1
Date: Fri, 21 Oct 2016 13:32:25 -0300
From: Alexandre Bergel <alexandre.bergel@me.com>
To: Moose-related development <moose-dev@list.inf.unibe.ch>
Subject: [Moose-dev] Re: Lab exercices with Moose
Message-ID: <85E53AB9-56F0-47A7-8BD5-5CAC4C27095B@me.com>
Content-Type: text/plain; charset=us-ascii
Hi!
I use Moose in Software Quality lecture. At the beginning of the semester, Students do not know Pharo.
They therefore have 1,5 weeks to learn Pharo. I ask them to read the first chapters of Pharo by Example and the chapter I.2 of AgileVisualization (http://agilevisualization.com).
Then they have to read Chapter III.4 of AgileVisualization to have an introduction of Moose. Then comes the time for them to work on a software quality assessment. They pick any Java application and analyze it (e.g., characterize the overall architecture, identify some quality criteria, and do the software assessment).
AlexandreOn Oct 21, 2016, at 2:30 AM, Abdelghani Alidra <alidrandco@yahoo.fr> wrote:
Hi,
For my students, I would like to illustrate some code analysis operations (mainly metrics calculation and some visualisations) with Moose. I was wondering if any one has already made the experiment and if there exist some lab exercices I can base my self on.
Thanks in advance.
Abdelghani
_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
------------------------------
Subject: Digest Footer
_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
------------------------------
End of Moose-dev Digest, Vol 122, Issue 16
******************************************
_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev@list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev
--
www.tudorgirba.com
www.feenk.com
"We can create beautiful models in a vacuum.
But, to get them effective we have to deal with the inconvenience of reality."