Module Study Guide AY2015-2016 Group Project Ealing Module Code CP50081E Level 5 Credits 20 School of Computing and Technology Group Project Module Study Guide Contents EALING 1 SCHOOL OF COMPUTING AND TECHNOLOGY 1 MODULE LEADER ,TEACHING TEAM AND MODULE ADMINISTRATOR DETAILS 3 EXTERNAL EXAMINER(S) 3 FURTHER INFORMATION 4 OVERVIEW AND CONTENT 5 1. WELCOME AND INTRODUCTION TO THE MODULE 5 2. TIMETABLE/VENUE/ROOMS 5 3. AIMS OF THE MODULE 5 4. LEARNING OUTCOMES 6 5. CONTENT OF THE MODULE 6 6. LEARNING RESOURCES 7 ASSESSMENT AND FEEDBACK 9 7. ASSESSMENT: GENERAL INFORMATION 9 8. DETAILS OF ASSESSMENT 9 9. SUMMATIVE ASSESSMENT GRID 11 10. STATEMENT ON PLAGIARISM 11 11. EVALUATION OF THE MODULE 12 12. PERSONAL DEVELOPMENT PLAN (PDP) 12 MODULE SCHEDULE 13 13 GUIDE TO LEARNING SESSIONS 13 Module Leader ,Teaching Team and Module Administrator Details Module Leader Dr Samia Oussena Field/Subject and School Undergraduate field, Computing and Technology Email [email protected] Phone 020 8280 2541 Location Name Job title Email Phone Location Name Job title Email Phone Location Name Job title Email Phone Location External Examiner(s) The External Examiner(s) for this module are listed below. Please note that this is provided for information only; students are not permitted to enter into any correspondence about their marks with External Examiners. Name Job Title Institution Further Information Total Guided Learning Hours 200 Consisting of: Teaching Contact Hours 56 Independent Study Hours 144 Placement Hours 0 Assessment: Percentage of final marks assessed by: Exam NA Coursework 100% Practical NA Section A Overview and Content 1. Welcome and Introduction to the Module Welcome to the module study guide for Group Project. In this guide you will find all the information you need regarding the purpose of the module and its role in the course you are studying. You will also find details of the module content, the assessment requirements and lists of further resources. All this information and a good deal more besides, is also available on-line on the Blackboard E-Learning platform which can be found at: www.online.uwl.ac.uk Resources on the web site are constantly updated so we recommend that you make regular visits to the site. Finally – we think we have covered most things here but if you have any suggestions for inclusion please let us know. Enjoy and Learn! 2. Timetable/Venue/Rooms First Point of Contact If you need to discuss any issue to do with this module, the first point of contact is the module leader, who is named at the start of this guide. If the module leader is unable to deal with the problem, you should then raise it with your course leader, and then with your Head of School. The Head of School responsible for this module is Amir Alani, and can be contacted at [email protected] 3. Aims of the Module The overall aim is to take a practitioners approach to the problems of developing software applications using Agile approaches. This module attempts to raise an awareness of the appropriate methodology required for given contexts. This module aims to introduce students to Agile development and their importance in the implementation of information systems. Business Process Analysis, Business Rules and other techniques are introduced as a means of establishing the system requirements. A number of Agile approaches are investigated in order to develop an understanding of the principles involved and practical examples are considered. The module aims to establish the framework for, and where the tools and techniques are used for the identification of business requirements, in conventional development. 4. Learning Outcomes On completion of this module students will be able to: LO1 Understand the inherent problems associated with information systems developments LO2 Evaluate the options for delivering an information system e.g. SDLC, agile method LO3 Select and apply techniques to analyse business processes, which are the target for system development. LO4 Understand and evaluate appropriate agile methods to develop a high fidelity prototype LO5 Understand and apply test driven development to a scenario LO6 Understand and apply user centric system evaluation LO7 Understand the importance and approaches to quality, risk management, configuration management and evaluation in the context of system development. LO8 Evaluate the usefulness of each method for different given industrial scenarios. 5. Content of the Module This module is designed to bring together the tools and techniques covered in earlier modules dealing with industrially recognised development frameworks that incorporate prototyping. It draws upon concepts from object oriented and relational design. It looks at the problems of analysing a business process and subsequently highlights the process of utilising the different software development process models, which can be applied in the realisation of a software solution. In particular it addresses the issues raised through following iterative and incremental development approaches. 6. Learning Resources School of Computing Computer Labs • You will have access to the School's PC labs for practical work. Materials to be provided • Handouts and Notes for most sessions will be provided • Solutions to exercises and activities will be given to support the theoretical parts. • The Blackboard e-learning platform for discussion groups, distribution of information and email. • Web page with links to relevant on-line resources. • Case studies from current practice. Recommended text: Sommerville, I. (2015), Software Engineering, 10th Edition, Addison Wesley, 2015, ISBN-13: 978-0133943030 Cockburn, A. (2006), Agile Software Development: The Cooperative Game, 2nd edition, pages 504, paperback, Addison-Wesley Professional, ISBN 0-321-48275-1, ISBN 978-0-321-48275- Other recommended reading: Cohn, M., 2004. User stories applied: For agile software development. Addison-Wesley Professional. Schwaber, K., 2004. Agile project management with Scrum. Microsoft Press. Martin, R. (2008) Clean Code: A Handbook of Agile Software Craftsmanship, Prentice Hall Pearlson, K. and Saunders, C. (2013) Strategic management information systems. 5th ed. London: Wiley Beck, K. (2002) Test Driven Development. Addison-Wesley Evans, E. (2003) Domain Driven Design: Tackling Complexity in the Heart of Software Smart, J.F., 2014. BDD in Action. Manning ISBN 9781617291654 Websites There are many on-line resources focussed on software development methodologies and associated concepts/issues. Key websites with lots of useful content include: 1. http://agilemanifesto.org/ The Original Agile Software Development Resource 2. http://www.scrumstudy.com/index.asp SCRUM resources 3. https://www.scrumalliance.org/why-scrum/getting-started-with-scrum SCRUM resources 4. http://www.dsdm.org/: DSDM Consortium home page, resource and links 5. http://www.extremeprogramming.org/ Extreme Programming resource and introduction 6. http://www.xprogramming.com/ Extreme Programming resource 7. http://www.scrumalliance.org/learn_about_scrum/ scrum resources 8. http://www.agilealliance.org/ The Agile Alliance 9. http://www.w3.org/2001/sw/WebOnt/#Membership Semantic web site web –ontology Specific sites for topic areas will introduce to students as required by each session. Key Journals for this area include: 1. Journal of Systems and Software 2. Journal of Systems Architecture 3. Communications of the ACM 4. Information and Software Technology 5. IEEE Software Software Requirements All the software necessary for the module is available at UWL but you can try JIRA tool (https://www.atlassian.com/software/jira/features)   Section B Assessment and Feedback 7. Assessment: General Information There are two components to the assessment: 1. The assessment has two elements: a. Group Work: This element requires you to work in groups to identify and document both the latent and practical characteristics and business attributes of the software system you are developing. (30%). b. Individual: This element consists of an individual report. The overall element requires you to produce a report, which reflects on your learning during the module. Specifically you are required to evaluate and critique the development process you have undertaken using the theories, methodologies etc. introduced in the module. (70%) 8. Details of Assessment Elements 1 and 2 are to be submitted via the Assessments area of Blackboard. You will need to ensure that each element is uploaded as a single document and in the correct format (PDF). Assessment Assessment task You are to be given a scenario from SEGA and you will need to develop a working system. You will work in-group and will be allocate different roles to the group members. Your clients will be SEGA and you will have a number of meetings with them for requirements elicitation and show and tell. Individually, you will need to provide a reflective report on the development process and your role as member of the development team or as a user. Weighting: Element 1: 30% Element 2: 70% Word count or equivalent: N/A Assessment brief: See Appendix A Marking grid: See Appendix A Timing of feedback: within 15 working days   9. Summative Assessment Grid Type of assessment Module learning outcomes Word count or equivalent Due date (week no.) Pass mark Weighting Course Work LO1-LO8 N/A 12 40 100% 10. Statement on Plagiarism Plagiarism is defined as the practice of taking someone else's work and passing them off as their own. It is presenting someone else's work as one's own irrespective of intention. Close paraphrasing; copying from the work of another person, including another student; using the ideas of another person without proper acknowledgement; and repeating work that you have previously submitted – at the University of West London or at another institution - without properly referencing yourself (known as 'self-plagiarism') shall also constitute plagiarism. For further information please refer to the Student Handbook. For further advice on plagiarism go to the UWL website: http://www.uwl.ac.uk/students/current-students/Advice-students-plagiarism 11. Evaluation of the Module The module is evaluated in three stages. Stage 1 Student Committee Meetings (one at each level) Students are encouraged to raise positive and negative feedback via their representative on the relevant Student Committee Meetings (one held each semester) at which the module leader, programme leader and Head of Subject will normally be present Stage 2 Student evaluation Towards the end of the module you will be invited to complete an on-line feedback form; this form allows for quantitative analysis of student feedback. After this stage the tutor can use the feedback to make changes to the module if necessary. Comments on the module from students can also be sent via the Blackboard messaging system. Stage 3 Formal Module Evaluation Additional feedback on the design of the module and its content is sought from the external examiner responsible for the module. Formal module feedback is summarised in the Module Report produced by the module leader. These reports are presented to the Course Leader and Head of School and actions are noted in the Programme Annual Monitoring report which is reviewed by the Academic Standards Committee. 12. Personal Development Plan (PDP) There is no explicit PDP requirement in this module.   Section C Module Schedule 13 Guide to Learning Sessions Session 1 Programme content The Software Development Lifecycle (SDLC) , Agile Software Development Key concepts / issues SDLC, its benefits and weaknesses Learning and teaching Lecture Assignment 1 broad requirements discussed and groups formed PhP Exercises Concepts of teams Design exercises Pre session reading Pearlson, Keri & Saunders, Carol, Managing and Using Information Systems, Wiley Chapter 10 Literature for this session Module study guide. Disseminated module materials Independent study Review and access your team role(s) 2 Programme content Business process analysis. Key concepts / issues Introduction to Business Process Analysis/PICTIVE Learning and teaching Lecture Case Studies issued to both teams (users and developer pair teams) Business analysis exercises. Technical Coordinators and Ambassador Users identified. Pre session reading Provided module material including lecture notes and recommended texts Literature for this session Module study guide. Disseminated module materials Independent study Work for assignment: Independent development and review of process and business rules 3 Programme content Behaviour driven development/user stories Key concepts / issues User acceptance tests, user stories , scenarios Learning and teaching Lecture Pre session reading Material posted on VLE (North, D., 2006. Introducing BDD. Available at: http://dannorth.net/introducing-bdd/) Literature for this session Independent study Review personal information seeking skills Work for assignment: Independent development and review user stories and BDD specification 4 Programme content SCRUM Key concepts / issues Key features of Agile SCRUM Support for Iteration workshops Learning and teaching Lecture Iteration workshops Pre session reading Provided module material including lecture notes and recommended texts Literature for this session Disseminated module materials. Independent study Revision of material completed to date, continued work on assignment. 5 Programme content Evaluation and usability Key concepts / issues Lifecycle feedback, evaluating the current project. Product usability and HCI factors influencing further refinement. Learning and teaching Lecture Review assignment using techniques discussed in preparation for the report Pre session reading Lecture referenced material Literature for this session Module study guide. Disseminated module materials. Independent study Evaluation and usability. 6 Programme content Test driven development/ Key concepts / issues Feature driven development RAD tools & techniques Testing and integration Support for Iteration workshops Learning and teaching Lecture Iteration workshops Pre session reading Provided module material including lecture notes and recommended texts. Literature for this session Module study guide. Disseminated module materials. Independent study Revision of material completed to date, prepare report for part 2 submission These are indications of what are scheduled in each session. Some sessions might take 2 weeks. The last sessions are reserved for the group work project.