Introduction to Enterprise Architecture (EntrArch) part 2

I have recently completed the Introduction to Enterprise Architecture on Open2Study. This is my first experiment into the world of MOOCs (Massively Open Online Courses) with Open2Study and overall my experience was very much a positive one.

The course itself was 4 weeks and included a number of short videos as content and multiple choice quizzes as assessment. You needed to get over 60% in all 4 quizzes (each containing only 5 questions) to complete the course. While enterprise architecture might not be the most exciting topic, instructor Craig Martin manages to keep content interesting and successfully ties together all of the content into a series of interested videos.

I found that I needed to take notes through each of the videos in order to have success answering the quizzes at the end of each module without googling the answer to each question.

The course URL can be found at:

If you are interested, you can watch the first topic of module 1 below.

Introduction to Enterprise Architecture (EntrArch)

Massively Online Open Courses (MOOCs) are a big thing in my sector, and as such I thought it was about time I actually enrolled in one.

I’ve enrolled in Introduction to Enterprise Architecture through Open2study is site offering free 4 week introductory courses and is an initiative of Open Universities Australia (

I’ve only watched the first half of the first module, but in all, I’m pretty excited to be finding out a little more about Enterprise Architecture.

Link to course:

Application development life cycle

I am a fan of the traditional waterfall model for application development. I know agile development is the current hype within the software development community, and like all programmers, I hate documentation, but there is something elegant in creating a perfect design for an application before you even fire up your favourite IDE. Below is an example of my typical application development life cycle…

Application development life cycle
1. Requirements! Gather requirements from the client and create a requirements specification.

2. Design! From the confirmed requirements, begin to creation a technical design for the application.

3. Implementation! Development includes looking through the current range of applications and applications templates and picking a similar one as a template. Commit the copy into SVN as the trunk of a new project. From here, start designing your new building block to fit with the technical design. This may involve looking through the any APIs, tag libraries and web services as well as any required third party services.

4. Quality Assurance! Code review and testing.

5. Release! Change control (follow any ITIL processes), Communication and eventually deployment into production.

6. Maintenance! Repeat the above steps for enhancements and bug fixes.

Jira: An issue tracker for developers

Like most programmers, I’ve used a range of issue tracking tools over the years to track bugs and enhancement requests in my applications and to be blunt, most of these have been terrible. Usually, I’ve been forced to use a new tool for a few weeks, then moved back to a trustworthy excel file buried deeply in a corporate network drive to keep track of any bugs I deemed worthy of tracking. This was until I discovered a product called Jira which is created by Australian company Atlassian. Jira is an issue tracking tool designed specifically for IT projects and is designed with developers in mind.

The tool itself is completely customisable. You can create issues, tasks, enhancements or something completely custom and then build specific queries to search for these items. A good example is you could create a project and have a range of sub components within that project, each with its own list of bugs and enhancements. It even has a range of agile development tools if this is what you are after. Better yet, it has a way to track issues with specific builds of an application, and even has a way to integrate itself with Bamboo (atlassian’s continuous code integration tool) and wiki (attlassian’s wiki tool).

It features some handy import tools, so if you are already using something else, you can use a built in import plugin or as long as you can export it as a csv you can use the in built csv importer to move everything into Jira.

The link below takes you to the Jira website where you can purchase various licenses of the tool depending on your needs.