Final Year Project – Final Entry

This week we have started finalising our documents, we ran into teamwork issues again but we aim to overcome these problems. The only section that primarily remains to be done is the ending of our technical specification.

Since we have found a tech advisor we can trust, we aim to start testing and prototyping our app as soon as possible. In our final document, we have included a disclaimer, stating that we have outsourced as a means of collaborating with other DCU students.

The formatting of a document this size is taking a lot of time and patience, Luke enjoys this type fo work, therefore, he has agreed to do this section of the work.

Overall My experience has been up and down throughout the year, I believe this a critical aspect to finishing an IT related course. It gives students the option to believe in their research or to pursue an entrepreneurial future.

I would like to thank the faculty of the computing school of DCU for giving me this opportunity and allowing me to realise there are endless amounts of educational resources available to myself and to all students aiming to better themselves


Final Year Project – Eleventh Entry

As we are preparing our final document, we are moving down through our technical specification. This week I have looked at the user interface.

I found a great application called Marvel that allows users to easily create a mock-up of the interface for their app, this application can be applied to websites also. The designs that I have created will be used in our final document as it stands.

I wished to keep the app as basic as possible, to allow users the option to easily navigate throughout the app. I applied basic design standards in terms of its interface.

Some key features would be consistency, the reverse of actions, error messages etc.

Below two images that have been created using Marvel.

Final Year Project – Tenth Entry

This week we have put in motion plans for our Technical delivery. No specifics have been decided but I and luke realised the scope of our project and other difficulties within the team has affected our technical delivery.

We began researching all the applications and frameworks used in creating smartphone applications. These applications include Android studio, Swift, React Native etc.

We felt it necessary to understand all the components of creating our app as we need to provide feedback and constant evaluation of the ongoing development of our app.

Our app is aiming to provide features such as realtime and geolocator. The functional process of providing this service is unknown to us, therefore we wanted to research this process.

We feel as enterprise students we need to thoroughly understand all processes as a means of positive collaboration.


Final Year Project – Ninth Entry

This week I looked at the functional specification as I find it quite interesting, we had a module in the second year using Argo UML which I found interesting, then this year we had a module called enterprise architecture. This module exposed our class to Signavio which allowed us to create BPMN diagrams.

At this point, I plan to start sketching are use case diagrams and creating use cases using cockburns templates.

They will be changed more than likely when we are finalising our final year document. use cases will allow our team to assess the use of our service and allow us to run step by step through the services we provide

LuckyHour Sign up (1)

Final Year Project – Eighth Entry

This week I and luke discussed the functionality of our app. Earlier in the year, we had exposure people’s capabilities of using apps and website. This was essentially a user persona and a usability analysis. We re-evaluated the services we were going to offer to our users and created scenarios in which the users would use these services.

From this rough work, we aim to create a clear functionality which will be used in our final business case.

Our system functionality section will discuss processes used in our app, highlighting technical difficulties and dependencies.


Final Year Project – Seventh Entry

Throughout the next few weeks are team plan on evaluating our business plan further. We felt that were several improvements to be made in areas such as our market research, and financial projections. Luke prized himself of analysing our financial projections, therefore, he ensured the team this would be his responsibility. I am happy with this decision as I found working with a team of three has grown difficult. Deadlines, individual goals have been set but we plan to overcome these objections and deliver our intended app.

We have consistently spoken of taking our project and changing our priority roles to project managers, Ideally, to show we can bridge the gap between technical personnel and business personnel

To summarise, our individual work for this isn’t set but I have taken upon myself to research topics that may be useful to our team. I broke down the software specification page and realised several of the diagrams needed are diagrams I successfully created in the past. Therefore my individual goal is to create mock use case diagrams and logical database designs.

Final Year Project – Sixth entry

The most recent piece of work we have submitted was our mid-term delivery. As mentioned before it generally made up of our business case that we have been working on since October. Additional features such as Technical delivery, Functional specification, Project timeline and a responsibility matrix. Overall the work was a collaborative effort except for areas we wanted to gain experience in or areas we were most comfortable in.

I, myself, took the task of the project plan, timeline, and division of work. From this we allocated our individual time to each of the assigned technical deliveries features. The intended outcome of this task was to present a clear scope of our project from start to finish.

The business case was a collaborative effort, improving particular areas such as financial projections, marketing, and sales strategy. Other features added to our business case included:

Below is an image of the timeline used in our mid-term delivery.

Copy of lucky-hour-timeline-proposal.png

We received a grade of 71%, overall we were very happy because we found working as a group of three can be difficult due to technical but also social aspects. That being said, I am grateful for this new experience when in comparison to my previous group work in college and team leadership in my job profession.

We met with our supervisor Maria, she expressed concern in certain areas of our work and presentation which we plan to change promptly so we are kept ahead of schedule with all submissions.