MM282-Business Applications Development

Module Provider: Business Informatics, Systems and Accounting
Number of credits: 20 [10 ECTS credits]
Level:5
Terms in which taught: Spring term module
Pre-requisites:
Non-modular pre-requisites: For Data Analytics pathway students, this module should be taken together with MM281
Co-requisites:
Modules excluded:
Current from: 2023/4

Module Convenor: Dr Giannis Haralabopoulos
Email: i.haralabopoulos@henley.ac.uk

Type of module:

Summary module description:

The development of full stack applications is becoming a core requirement for supporting day to day operations across increasingly diverse organisational entities. This is particularly true for digital businesses that primarily have an online presence and may rely heavily on their data-assets to construct solutions for customers and business partners. Entrepreneurs, business analysts, and technology consultants quickly find that a good understanding of web development can help them construct working user-friendly prototypes, as well as develop, manage, and maintain enterprise systems that would otherwise appear fairly incomprehensible. In short, this module introduces fundamentals of databases, development, and interaction design to business students.Ìý

Aims:

Ultimately the aim of this course is to provide students with the knowledge to implement and deploy interactive web apps, that are both data-driven and user friendly.Ìý

Assessable learning outcomes:

On completion of this module, the student should be able to:

• Explain programming constructs in a high-level scripting language


• Design and implement relational databases


• Explain the difference between front end and back end programming


• Implement interactive apps in web-based platforms


• Critically evaluate the usability and user experience of interactive apps

Additional outcomes:

Students will gain first-hand experience with computer programming. Emphasis is less on understanding how computers compile or interpret code, and more on functionality and solutions development. Therefore, by the end of the module, students will have a broad understanding of the processes and platforms that support application development, from coding to deployment. Moreover, students will understand the process of evaluating the usability of apps using heuristics and methods derived from interaction design literature.

Outline content:

1. Computing


2. Software


3. Programming


4. Back End Development


5. Front End Development


6. Interactive Web Applications


7. Usability Heuristics & Criteria


8. Data driven development


9. User experience evaluation


10. Business applications

Brief description of teaching and learning methods:

This module will be a combination of lectures and practical workshops that, within each two-hour ession,Ìýwill enable students to acquire key concepts and practical skills in business applications development. The module assumes no prior knowledge or experience in programming; therefore students are expected to do a fair amount of unsupervised learning.

Summative assessment- Examinations:

Summative assessment- Coursework and in-class tests:

Submission of individual report. Report is split into 3 sections. Theory, Design and Technical proficiency. Once report questions are released, students will have 3 hours to complete and submit the report to Blackboard.

Formative assessment methods:

Students will be given feedback on the progress of their individual project through practical sessions. Furthermore, online exercises will be made available on BB, which will provide students with the opportunity to assess their programming knowledge. These exercises will not be marked; feedback will be given in practical classes.

Penalties for late submission:

The Support Centres will apply the following penalties for work submitted late:ÌýÌý

• 
  

  where the piece of work is submitted after the original deadline (or any formally agreed extension to the deadline): 10% of the total marks available for that piece of work will be deducted from the mark for each working day (or part thereof) following the deadline up to a total of five working days;ÌýÌý

  
  


• 
  

  where the piece of work is submitted more than five working days after the original deadline (or any formally agreed extension to the deadline): a mark of zero will be recorded.Ìý

  
  

The University policy statement on penalties for late submission can be found at: /cqsd/-/media/project/functions/cqsd/documents/cqsd-old-site-documents/penaltiesforlatesubmission.pdfÌý

You are strongly advised to ensure that coursework is submitted by the relevant deadline. You should note that it is advisable to submit work in an unfinished state rather than to fail to submit any work.ÌýÌý

Assessment requirements for a pass:

40% in coursework

Reassessment arrangements:

Resubmission of courseworkÌý

Ìý

Additional Costs (specified where applicable):

Last updated: 12 April 2023