Sidebar Menu

Projects

  • Dashboard
  • Research Project
  • Milestones
  • Repository
  • Tasks
  • Time Tracking
  • Designs
  • Forum
  • Users
  • Activities

Login

  • Login
  • Webmail
  • Admin
  • Downloads
  • Research

Twitter

Posts by stumathews
Stuart Mathews
  • Home
  • Blog
  • Code
  • Running
  • Gaming
  • Research
  • About
    • Portfolio
    • Info

Agile and Model Driven Development

Details
Category: Blog
By Stuart Mathews
Stuart Mathews
14.Jun
14 June 2020
Last Updated: 14 June 2020
Hits: 3514

Model driven development (MDD) primarily focuses on developing conceptual models during the Software Development Lifecycle with a secondary emphasis on the code by “shifting from programming to the creation of models and transformations between them” ({xbref tag="0" title="Shin, 2019" desctext="Shin, S.-S., 2019. Empirical study on the effectiveness and efficiency of model-driven architecture techniques. Software & Systems Modeling 18, 3083–3096. https://doi.org/10.1007/s10270-018-00711-y" }Shin15{/xbref}, 2019).

Agile focuses on project delivery practises and techniques which manage the effects of change during a project by focusing on the people, communication, collaboration, feedback and working software ({xbref tag="0" title="Cockburn et al, 2001" desctext="Cockburn, A., Highsmith, J., 2001. Agile software development, the people factor. Computer 34, 131–133. https://doi.org/10.1109/2.963450" }Cockburn et al, 200115{/xbref}).

MDD and agile are both concerned about the successful delivery of artefacts during the SDLC.

Incorporating the benefits of agile, which focuses on managing project delivery in the face of change, has been shown to be successful in projects focused on developing models as their primary artefact - where the various agile principles and methodologies have been mapped to their MDD counterparts such as Continuous modelling to Continuous Integration, Test-Driven Modelling to Test Driven Development, Automated batch mode simulation to Automated test regression and other related activities . ({xbref tag="0" title="Zhang, 2001" desctext="Yuefeng Zhang, Patel, S., 2011. Agile Model-Driven Development in Practice. IEEE Software 28, 84–91. https://doi.org/10.1109/MS.2010.85" }Zhang, 200115{/xbref})

Among other benefits of agile, is its focus on feedback and collaboration which “reduces the cost of moving information between people” and helps reduce the elapsed time between making a decision to seeing the consequences of that decision” (Cockburn et al, 200115)  – which can only help make development teams more efficient and models more effective.

MDD and in particular, The Unified Modelling Language (UML) have been shown to be effective in contributing to requirement elicitation, producing “well-defined semantics and an elegant graphic syntax for expressing rich business requirements” (Shin15, 2019).

Furthermore, MDD focuses on design abstractions which helps, “alleviating the complexity of platforms and express domain concepts effectively” {xbref tag="0" title="Schmidt, 2006" desctext="C. Schmidt, 'Guest Editor's Introduction: Model-Driven Engineering,' in Computer, vol. 39, no. 2, pp. 25-31, Feb. 2006, doi: 10.1109/MC.2006.58. https://ieeexplore-ieee-org.libezproxy.open.ac.uk/document/1597083" }(Schmidt, 2006)15{/xbref}, contributing to both the design and analysis phases of the SDLC.

However, one study has shown it less effectiveness in transforming these model to accurate code representations, in particular MDD’s “round-trip engineering” phase which is the synchronization of code and models, “was not perceived as effective or efficient” by the study (Shin15, 2019) and echoes much earlier concerns raised by Schmidt and Ambler in prior years.

That prior study also highlighted the difficulty of defining Object Constraint Language (OCL) expressions, even within relatively simple scenarios and how Query/View/Transformation (QVT) is a relatively complex specification, contributing to perhaps its perceived effectiveness.

Cockburn et al, advocates that agile development “excels in exploratory problem domains” and “high-change environments” and as such the analysis phase is an incremental iterative and dynamic endeavour which might not be “suited for everyone” suggesting there are limitations.

Research has shown that introducing new people “increased defects in new ASD teams” (Agile Software Development) and conversely when they move away, “Lack of knowledge retention” is an increased risk.

This research also identified the accumulation of “technical debt” which is the result from compromises made by technical teams where the “pressure of delivering in short time-boxed iterations cycles made them take short cuts to speed up delivery.  ({xbref tag="0" title="Elbanna et al, 2006" desctext="Elbanna, A., Sarker, S., 2016. The Risks of Agile Software Development: Learning from Adopters. IEEE Software 33, 72–79. https://doi.org/10.1109/MS.2015.150" }Elbanna et al, 200615{/xbref})

Both ideas rely on incorporating the problem space into the correct design for working software.

 

Rails, Euclid and Generating Mazes

Details
Category: Blog
By Stuart Mathews
Stuart Mathews
31.May
31 May 2020
Last Updated: 31 May 2020
Hits: 5809
  • Running
  • Math
  • Digital Signal Processing and Audio Programming
  • Ruby

Since Set Theory, Ruby and Upgrades, I've been focusing on learning new technologies recently{xbref tag="0" title="Changed jobs" desctext="I now work at VMware" } [Changed jobs] 15{/xbref}. The primary focus of the new platform under development is on centralizing the view of your current separate clouds{xbref tag="0" title="Multi clouds" desctext="AWS, Azure, GCP(Google), Alibaba etc" } [Multi clouds] 15{/xbref} and managing them from single operational, governance, security and cost management perspective.

The platform is based on Ruby on Rails and it is a completely new and another level of learning which centres around a platform that provides the tools to develop online or cloud-based systems. There is a striking resemblance to ASP.net MVC and Spring MVC however the added twist of needing to use ruby makes it an interesting proposition, not to mention's provision for metaprogramming.

I've been in the thick of learning about RSpec, FactoryGirl and the base Rails platform documentation. I've also been watching a lot of Plural Sight videos which has been quite a time-consuming process however an interesting diversion at times. I'm not even nearly made a dent in the materials.

I recently decided to write a simple game called Ruby Mazer entirely in Ruby over the May bank holiday weekend. This was really fun and got me conversational with ruby. I used a gem called Gosu to help with the drawing and input. The premise of the game is that you need to reach a point in the autogenerated maze without touching the maze walls in getting there. Once you get to the exit point, you are teleported to a new maze which is slightly more difficult. I used Prims Algorithm to generate and solve the models that make up the level generation routines. You can read up on the implementation in Ruby Mazer.

I've had to dial back on my recent reads{xbref tag="0" title="Recent reads" desctext="DirectX and Maths" } [Recent reads] 15{/xbref} as priorities have changed and I'm re-focusing on other things{xbref tag="0" title="Re-focus" desctext="Ruby and Ruby and rails being one, and some of the onbording training being the other" } [Re-focus] 15{/xbref}, however as my learning curve goes down, I'll probably continue with them. This has also been the case with my running over the last two weeks.

Having said that I went for a run yesterday as described in Hot weather running. I just about survived. I also earned two new(3 actually) blisters for my efforts. I played my specifically created Spotify playlist. A particular good running tune is Micheal Jackson - The way you make me feel and Dance Monkey.

In other news, I've recently started focusing on Euclid. It's fairly slow going, however 'slow and steady wins the race'... It's quite nice to see how common rules like how the angles under at the base of an isosceles triangle are equal - is actually solved in an actual proof so as to show/explain/prove where/how this rationale came from{xbref tag="0" title="Proposition 5, Book 1" desctext="This is the actual proposition by Euclid" } [Proposition 5, Book 1] 15{/xbref}. 

The other thing I like about the proofs is that they build upon each other. Initially, if you look at the rationale of a proposition, particularly the starting diagram{xbref tag="0" title="Proposition 3, Book 1" desctext="Given two unequal straight lines, to cut off from the greater a straight line equal to the less" } [Proposition 3, Book 1] 15{/xbref} it's not entirely clear however that it proceeds from the previous Proposition{xbref tag="0" title="Proposition 2, Book 1" desctext="To place at a given point[as an extermity] a straight line equal to a given straight line" } [Proposition 2, Book 1] 15{/xbref}.  This is sometimes a pain however I do think the mental realization of connecting where the previous proposition left off and where this one derives from it perhaps is a necessary mental step. The first 7 triangle propositions have been an interesting diversion over the last couple of weeks.

I've also been heavily customizing my editor recently for my new workflow - see it here complete with split screens and git integration! 

Now, I must not forget to sleep and must run more. Sleep and run, sleep and run and program in the middle (7 hours) 

Set Theory, Ruby and Upgrades

Details
Category: Blog
By Stuart Mathews
Stuart Mathews
25.Apr
25 April 2020
Last Updated: 30 April 2020
Hits: 5340
  • holiday
  • Game development
  • C++
  • Investing
  • Asp.Net Core
  • Math
  • .Net Core
  • Functional programming
  • DirectX
  • Ruby
  • MonoGame

Since Time shifting, CS algorithms and Game Architecture, I've been exploring trivial set theory to gain insights into the theory of what defines a function from a purely mathematical standpoint, which as it happens, is the product of two sets. For example, let C represents a function in terms of a set \( C \subset A \times B \) such that it produces a set where \( \{(a,b): a \in A, b \in B\}\) and which references all the possible inputs and outputs of the function where \( C = A \mapsto B \).

Usually the nomenclature of a function is usually represented as \( F = X \mapsto Y\) and alternatively \( f(x) = y : x \in X \ y \in Y \). Obviously, if you spend some time going through the theory of functions as expressed on a graph such as a linear equation, the relationship between the dependant variable \(y\) and independent variable \(x\) has a clear relationship. In programming, this is generally interpreted as the running of a function's code as opposed to the evaluation of an equation or expression to realise the dependant variable's value.

The theory of sets is pretty interesting in its own right however its particularly interesting in the context of functional programming, particularly pure functions which are programming constructs which are trying to model the mathematical ideals of functions. A pure function represents a bijective mapping (both injective and surjective) of the product of the two sets (domain \(X\) and codomain \(Y\)). This means nothing else exists that influences \(y\) other than \(x\) (it's a direct mapping). This is a key consideration of pure functions in functional programming and immutability.

The reason its key is because this makes \(f(x)=y\) absolutely reliable because if you know \(x\), then you know \(y\). These ideas have implications for real-time processing environments like games because they usually rely on highly concurrent and often parallel execution of tasks, where reasoning about functions within a threading context requires predictability. This is among some of the research I'm doing at the moment.

Parallel executing tasks usually lock critical sections of shared state and these tasks (functions really) themselves are prone to producing non-deterministic results due to the very fact that they don't exhibit a bijective nature between their domain and codomains. Executing environments that rely on I/O and other external factors make it impossible to guarantee the result of any function that relies on it - not great for a function's predictability.

Making tasks pure, arguably makes them reliable and then you don't need locking either. My argument then, is that this will make games perform better - and more reliably. Though my research looks to determine at what cost this comes at, particularly when it comes to the code itself such as readability and maintainability etc.

Interestingly if you do some reading about Memorization, this relies on this behaviour of a bijective function too ie. you never need to evaluate that function again in the future - provided of course you store its input and output.

Apart from Mathematics, I've upgraded my Investment Management project to .net core 3.1 which takes it right up to the latest supported version. It was a bit of a pain doing it, as I had to go from .net core 2.0 -> 2.1 -> 2.2 -> 3.0 separately and then finally to 3.1. It wasn't that complicated but it wasn't seamless either. 

I've also done some more Canal-side runs lately, which I've enjoyed.

Although I don't use functional programming for my day-to-day work in C# anymore, I've written a prototype game in C# which I'd like to 'functionalize'. I've come to appreciate the ideas and would like to explore its applicability to game development now.  I'm slowly reading through Functional Programming in C# and I'm weaving it in with the other readings I have going on. I've got through the first 2 chapters so I've yet to make real headway. I produced a tutorial about functional programming in C# (which got good feedback) and this, I guess is an extension of that.

There is scope to incorporate Scala into my future work and there are functional aspects to Ruby (see later) - so the trajectory is in the same direction, generally. So I'll not be dropping it quite yet.

I've also been playing around with latex, trying to get it working on my blog(which I've managed to do) and I think moving forward I'd like to use it to write up some of my work moving forward.

I've managed to get out my project proposal which is entitled "Evaluating and Applying Functional Programming Paradigms in Developing Computer Games using C# and MonoGame", though I had to chase up my supervisor to review the draft and by the time he'd done it, my proposal had diverged significantly and thankfully his comments were largely already covered in my revised version. I incorporated some of his comments however which was helpful. I'll need to start working on the delivery of it.

I'm slowly making it through A mind for numbers having made it through the first 3 chapters. I'm also learning more about Linear Equations and relationships between numbers, specifically the dependant and independent variables that constitute formulae (given my earlier foray into functions) such as trivial straight line equations in the form of \(y = mx +c \). I find it quite interesting going through it. I'm finding it quite useful for reinterpreting some of the fundamental algebraic ideas and others such as understanding the nature of proportional relationships (the meaning of gradients for example).

I've pretty much stalled on applying my linear algebra learning to 3D transformations (which is the stuff I need to do next and finish...DirectX math, coursework and some films) as I think I've been reading so much about it that I'm a little tired of it (I've read the first 6 chapters of 3D Game Programming Using DirectX 10 and OpenGL back-to-back as well as Frank D Luna's book - lots and lots of theory). 

As a distraction, I bought a book a while ago which is old (managed DirectX 9 in C#) which I thought might be useful to obtain an alternative perspective on viewing transformations and the like, so I started to read that. I've got through the first 3 chapters and now I'm at a point where viewing transformations are being discussed. So I've got 3 books ready to get into about this! This one's obviously old and managed direct X is no longer a product, but it's exciting none-the-less. I've got to avert my eyes when I see some of the device enumeration and selection code as some of it now does not apply to later versions of Direct X with the version I'm most familiar with (DX10) being the one that did away with the compatibility checking code that features in this book. It is however nice to be back in C#.

I created a nice little C++ vehicle that shows the current frames per second and I'll use this as the basis for my next work, which should be shortly. It will probably also include some HLSL and shader programming as that's required for the vertex transformations to occur.

I've also been learning Ruby and Ruby-On-Rails recently, not in a massive way yet. I've read the basic tutorial on the main website, followed 2 video tutorials on the subjects respectively, the first 4 chapters of "Eloquent Ruby" as well as the section on ruby in one of my programming books and created my first dummy rails application. I find text-based tutorials much more effective than a video, but I guess it depends on your time and motivations. My plan so far is to integrate it into my Investment Management project, using Resque and Redis as the basis of a background job management system, which I've already partially set up.

I've got Halo Wars, Metro Last Light, Dragons dogma and Dantes Inferno currently sprawled out on my couch and I've not played any of them yet. This means I've been pretty productive. I have played Mass Effect 3 though, that is until I got to a stage where I kept on getting killed and it started to annoy me - I stopped playing... You got to make games adaptively progressive!

There is still much to do, and only 2 more weeks to do it in!

 

More Articles …

  1. Time shifting, CS algorithms and Game Architecture
  2. Confidentiality by computation: The challenges of on relying on computational cryptography
  3. The Fourier transform, math, malware and decoupling
  4. Common network attacks and the shortcomings of standard network defences
  5. Encryption and network protocols
  6. BYOD and Implications for Network Security
  7. Mazer Game Design and Network Security
  8. Thoughts on Creativity And Originality
  9. Game Dev, Forensics, Math and stuff
  10. Fortune favours the brave
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23

Page 19 of 182