Agile Development and Software Security B - CO553

Looking for a different module?

Module delivery information

Location Term Level1 Credits (ECTS)2 Current Convenor3 2020 to 2021
Spring 5 15 (7.5) DR F Otero checkmark-circle


Students will apply Agile Development techniques to a prescribed problem that involves the development of a software solution.


Contact hours

33 Contact hours
117 private study hours
Total hours 150

Method of assessment

13.1 Main assessment methods
Group project 75% (60 hours)
2 page Individual evaluation report 25%

13.2 Reassessment methods: Project reassessment instrument

Indicative reading

• Beck, K; Extreme Programming Explained: Embrace Change, 2e Addison-Wesley, 2005
• Beck, K; Fowler, M; Planning Extreme Programming (XP),1e, Addison Wesley, 2001
• Schwaber, K; Agile Project Management with Scrum, Microsoft Press, 2004
• Layton, MC; Agile Project Management For Dummies, John Wiley & Sons, 2012
• Pham, A; Pham, P-V Scrum in Action, 1e Delmar Cengage Learning, 2012
• Cohn, M; Succeeding with Agile: Software Development Using Scrum, 1e, Addison Wesley, 2010
• Fowler, M; UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3rd edition, Addison-Wesley, 2004
• Rumbaugh, J; Jacobson, I; Booch, G; The Unified Modeling Language Reference Manual, 2nd edition, Addison-Wesley, 2004

Learning outcomes

8. The intended subject specific learning outcomes.
On successfully completing the module students will be able to:
8.1. Identify and evaluate alternative solution strategies to a multi-tiered software problem;
8.2. Identify the roles and responsibilities of members of a software development team and the methods of intercommunication;
8.3. Plan and document the process by which a software solution is achieved using Agile software development and UML;
8.4. Construct a solution to an approved multi-tiered software problem;
8.5. Verify the solution to an agreed specification;
8.6. Present and demonstrate system software solution.
8.7. Critically evaluate the proposed solution and the means by which it was achieved;
8.8. Demonstrate a commitment to quality in the production of project deliverables;
8.9. Demonstrate a commitment to being a responsible member of a software development team.

9. The intended generic learning outcomes.
On successfully completing the module students will be able to:
9.1. Develop a strategy for solving a problem;
9.2. Develop a strategy for working with others;
9.3. Monitor progress and modify strategies to achieve agreed objectives;
9.4. Evaluate the realized solution;
9.5. Evaluate the experience of working as part of a team and suggest alternative actions that might have improved the eventual outcome.
9.6. Explain the role and importance of considering security when developing software, from the perspective of the system as well as the user.


  1. Credit level 5. Intermediate level module usually taken in Stage 2 of an undergraduate degree.
  2. ECTS credits are recognised throughout the EU and allow you to transfer credit easily from one university to another.
  3. The named convenor is the convenor for the current academic session.
Back to top

University of Kent makes every effort to ensure that module information is accurate for the relevant academic session and to provide educational services as described. However, courses, services and other matters may be subject to change. Please read our full disclaimer.