CC5006 - Project Management, Systems Development and Usability (2017/18)
Module specification | Module approved to run in 2017/18 | ||||||||||||||||||||
Module status | DELETED (This module is no longer running) | ||||||||||||||||||||
Module title | Project Management, Systems Development and Usability | ||||||||||||||||||||
Module level | Intermediate (05) | ||||||||||||||||||||
Credit rating for module | 30 | ||||||||||||||||||||
School | School of Computing and Digital Media | ||||||||||||||||||||
Total study hours | 300 | ||||||||||||||||||||
|
|||||||||||||||||||||
Assessment components |
|
||||||||||||||||||||
Running in 2017/18(Please note that module timeslots are subject to change) |
|
Module summary
The concept behind this module is that it provides an understanding of project management tools, techniques and responsibilities in order to run a project from initiation through to successful completion. The module uses case study material in order to allow students to formulate plans for the introduction of a web-based application in a business environment. Students’ will work as a team to develop a prototype web-based application using web authoring tools and scripting languages.
Module aims
This module aims to give students knowledge of and experience in using the tools and techniques in order to manage an information systems project successfully and to gain experience in developing a prototype web-based system that meets the needs of a client based on a case study.
Syllabus
The major topics of study of this module are:
- Project life cycle, and its relationship with the systems development life cycle
- Project planning tools, techniques and methods
- Risk analysis and management
- Work breakdown structure and work allocation principles
- Principles of team dynamics and communication
- Team and meeting management
- Reporting and presenting results
- Systems analysis techniques – requirements elicitation (e.g. interviews, surveys, JAD workshops, prototyping etc); modelling (e.g. DFM, LDM, etc; use case model, class diagram, etc)
- Aspects of system design with an emphasis on web based applications, including interaction design (e.g. storyboards, wireframes, testing, evaluation of usability, etc.), database (e.g. normalisation, EAR modelling etc), human activities (e.g. task analysis)
- Theory, practice and principles of interaction design , including relevant standards e.g. ISO 13407 Human-centred Design Processes for Interactive Systems
- Implement web based system using a variety of web development tools and scripting languages including html, css, php, asp.
Learning and teaching
Topics will be introduced through the medium of formal lectures, supported by tutorial and workshop sessions, and blended learning as follows:
- Lecture (1 hour / week):
Introduction of the major topics identified in the syllabus, plus for practical exercises, directed reading and other further study
- Tutorial/ Workshop (2 hour / week):
Consolidating understanding of topics introduced in the lecture via class and group discussions, informal presentations and other activities in the tutorial sessions.
Data analytic skills will be further developed through lab-based workshops.
- Blended learning:
Using the University’s VLE and online tools to deliver content, assessment and feedback, to encourage active learning, and to enhance student engagement and learning experience.
Students will be expected and encouraged to produce reflective commentaries on the learning activities and tasks that they carry out to complete their work.
Learning outcomes
On successful completion of this module students will be able to:
LO 1: Use key project management tools and techniques, e.g. Gantt chart, network diagrams, critical path analysis, cost-benefit analysis, earned value, work breakdown structure, risk analysis and management
LO 2: Understand a number of system development methods and analysis techniques, and make an appropriate selection for a given context
LO 3: Make a realistic plan in teams, with timings and costings, for a project
LO 4: Monitor the progress of a project plan, and be able to recommend corrective actions if necessary
LO 5: Identify and evaluate risks associated with a project plan, identify and evaluate suitable containment actions and contingency plans, monitor risk
LO 6: Identify stakeholders and make a coherent analysis of their needs and engage them in the development process.
LO 7: Develop a prototype web-based application that meets the client requirements stated in the case study.
Assessment strategy
The assessment method consists of four assessed components and an attendance requirement at learning manager meetings. Coursework 1 assignment (Interim Report) and coursework 2 assignment (Final Report), Coursework 3 Prototype Web-based, Coursework 4 Weekly in class test (week 2 to week 26). All coursework except the weekly in class test will be teamwork but assessed as individual work.
Students need to be assessed on their ability to absorb and apply theoretical material. Additionally, students need to be assessed on their ability to demonstrate practical proficiency of a software environment. The learning outcomes encompass both theoretical and practical aspects and the assessment strategy reflects both these elements.
The assessment strategy ensures that students can demonstrate practical knowledge that they will have acquired during workshop sessions, with the use of a practical coursework element which will include the use of appropriate software. The assessment strategy also allows students to demonstrate their knowledge of the wider subject area, e.g. risk analysis, team management, cost-benefit analysis, resource allocation and scheduling, system installation etc. by means of a weekly in class test. The assessment strategy also allows students as a team to demonstrate that they can translate a plan into a prototype web based application and apply relevant evaluation techniques to recommend improvements, but students will be assessed as individuals.
An in class test will be available via weblearn for reassessment, this will consist of a range of questions covering topics that students covered during weeks 2 to 26.
Learning Manager Meetings: in order to pass this module, students must attend at least two meetings with their Learning Manager (one in Autumn and one in Spring) in order to reflect upon, discuss and plan their approach to learning and organisation of their study.
Bibliography
Beynon-Davies, P., 2013, Information Systems, Palgrave, ISBN 978-1-137-26580-7
Burke, R. (2003 or subsequent editions) Project Management: Planning and Control Techniques, 4th edition. Wiley, Chichester. [CORE]
Cadle J & Yeates D (2001) Project Management for Information Systems, 3rd Edition, Prentice-Hall.
Czegel, B., 1998, Running an Effective Help Desk, Wiley, ISBN 0-471-24816-9 Gray CF & Larson EW (2000) Project Management: The Managerial Process, McGraw-Hill (includes CD-ROM).
Hughes, B. & Cotterell, M. (2002), Software Project Management, 3rd edition, McGraw-Hill, Maidenhead.
Lockyer K & Gordon J (1996) Project Management and Project Network Techniques, 6th edition, Prentice-Hall, Harlow.
Maylor H (2003) Project Management, 3rd edition, Pearson Education, Harlow.
Meredith, J. R, & Mantel Jr, S. J., (2003), Project Management: A Managerial Approach, 5th edition, John Wiley & Sons, New York.
O’Connell, F. (2001) How to Run Successful Projects III: The Silver Bullet, Addison-Wesley, Harlow.
Sharp H, Rogers Y and Preece J, (2015) Interaction Design: Beyond Human-computer Interaction. John Wiley & Sons; 4th Edition. [CORE]
JAMSA, K. (2014). Introduction to Web development using HTML 5. Jones and Bartlett Learning. [CORE]
Castiro, E., Hyslop, B., & Castiro, E. (2012). HTML5 and CSS3: visual quickstart guide. Berkeley, CA, Peachpit Press.
Shneiderman, Ben (2010) Designing the user interface: strategies for effective human-computer interaction. 5th ed. Pearson Education,
Heim, Steven G (2008) The resonant interface: HCI foundations for interaction design, Boston: Pearson/Addison Wesley.
Paul Bocij, Andrew Greasley, Simon Hickie (2015) Business Information Systems : technology, development and management for the e-business. [CORE]