[LINK] Low-code and no-code development .. but .. security?

David Lochrin dlochrin at aussiebb.com.au
Fri Nov 27 11:11:33 AEDT 2020


On 2020-11-25 08:54, Tom Worthington wrote:

> Shayne Flint and others who developed the program, wrote a paper about it: https://ieeexplore.ieee.org/document/7942964
> Here is a later paper on my bit out it: https://doi.org/10.1109/TALE48000.2019.9225921

Thanks for those links, which I shall read with interest.

I wrote a 45-page student guide for the UTS Software Engineering course before it was restructured to include elements of agile development, and was involved in internal discussions concerning those changes.  However a death in my family suddenly, though indirectly, ended my association there, hence my interest.

The project Groups were encouraged to think of themselves as a small software-development company.  Although the University reserved some rights, each Group could go on to commercialise packages they developed and some were very professional indeed.  The pre-agile course was highly structured, very comprehensive, and quite intensive, and marking Group  "deliverables" each semester was not something tutors would anticipate with pleasure.  Each group was then given a bucket of marks which they had to distribute among their members.

I won't go on, but I think I can extract the following from one Group's "Reflection", for which they received top marks.

The standout, major issue in this second phase was the complexity of our solution to the business problem.  The System Construction document will go into more depth into the technical issues we encountered. The first issue was choosing the Java framework XXX.
This had a number of adverse effects:
-     Longer setup time
-     Not all group members understood XXX
-     Complex – Could not rotate a group member in or out if they had free time to help

We believed we could combat these issues by:
-     Having really good programmers

1)   A complex solution is a complex solution regardless of the quality of the programmers
2)   Scope Creep always ends in tears
David Lochrin

More information about the Link mailing list