SOFTWARE CONFIGURATION MANAGEMENT - 2018/9
Module code: COM2035
Software configuration management aims to build, test and deliver services to the customers specified by service design. The goal of release policies and deployment plans is to deploy releases into operation and establish effective use of the service in order to deliver value to the customer. The documented management of release and deployment processes also ensures handover to service operations takes place and that suitable training and documentation exists to ensure ongoing support of the new service.
WESEMEYER S Dr (Computer Sci)
Number of Credits: 15
ECTS Credits: 7.5
Framework: FHEQ Level 5
Module cap (Maximum number of students): N/A
Prerequisites / Co-requisites
Indicative content includes:
The need for software configuration management in supporting patterns of business activity
Practical aspects of using modern software configuration tools (like subversion, git, etc)
Release Policy, Release Unit, Release Identification
Release design options and considerations
The release and deployment process activities
Build and test prior to deployment into production/live environment
Release packaging and build documentation
Continuous Integration (CI) tools for software configuration management; Hudson - Continuous Integration Server (Eclipse)
|Assessment type||Unit of assessment||Weighting|
|Oral exam or presentation||Group presentation||20|
|Coursework||Individual Release and Deployment Plan||40|
Write a short report(1000 words) on the importance of software configuration management and the need for establishing release and deployment processes. Qualifying Condition(s) A weighted aggregate mark of 40% is required to pass the module.
The assessment strategy is designed to provide students with the opportunity to demonstrate
Their understanding of the benefits for a business / organisation of a careful consideration of the software configuration procedures and activities
Their ability to determine a most appropriate release policy and produce a deployment plan and testing pilots for a small-scale application
Their competency with applying a CI tool to implement a release and deployment plan, and document the configuration management procedure
Thus, the summative assessment for this module consists of:
A group presentation describing the role of software configuration management and the need for establishing release and deployment processes (during week 6 and 7). This addresses LO1.
An individual deployment plan for implementing the release policy (for week 8). This addresses LO2 and LO3.
An individual report documenting the implementation of the release and deployment processes in realising the chosen release policy and planning pilot for a small-scale application, including an evaluation of how this will make a difference on the business / organisation costs (for week 10). This addresses LO3 and LO4.
Formative assessment and feedback:
One of the lab sessions (around week 4) will include a formative test in which the students will be given tasks involving the use of a range of open-source software configuration systems (eg git, subversion, etc). This addresses LO5.
Further formative feedback is provided as part of the summative assessment as well as in the lab sessions. Formative feedback will also be informally obtained through extensive class discussions and any individual follow-up subsequently.
- Describe the necessary software configuration management in order to build, test and deliver services to the customers as specified by service design
- Demostrate the importance of deploying releases into operation and establishing effective use of the service in order to deliver value to the customer
- Investigate the challenges that different types of users, deployment resources as well as business outcomes pose with respect to configuration managemment
- Introduce different release policies and release design options and considerations
- Review different release policies and deployment plans
|001||Discuss the benefits of ensuring that handover to service operations takes place and that suitable training and documentation exists to ensure ongoing support of the new system.||KCP|
|002||Evaluate the pros and cons of a number of different release policies and factors in deciding deployments plans||KCT|
|003||Demonstrate the ability to devise deployment plans, and apply standard methodologies in the documentation and tracking of the necessary processes in a the service configuration package||PT|
|004||Apply tools and checklists to ensure that the release package is built in a standard and controlled way in line with the solution design defined in the service design package||KCPT|
|005||Understand the importance of software version control and be able to apply modern software version control processes, including the ability to use a version control system to manage software versions||KP|
C - Cognitive/analytical
K - Subject knowledge
T - Transferable skills
P - Professional/Practical skills
Overall student workload
Methods of Teaching / Learning
The learning and teaching strategy is designed to:
Help students understand the importance of software configuration management
Provide students with the opportunity to devise release policies, deployment plans, testing pilots, tracking and documentation procedures
Develop students’ ability to critically evaluate different approaches and policies in a range of release and deployment scenarios
Encourage students to research software configuration management practices and methodologies
The learning and teaching methods include:
Lectures (11 weeks @ 2h) with class discussions to introduce the theoretical background
Labs (9 weeks @ 2h) to put the theory into practice
Indicated Lecture Hours (which may also include seminars, tutorials, workshops and other contact time) are approximate and may include in-class tests where one or more of these are an assessment on the module. In-class tests are scheduled/organised separately to taught content and will be published on to student personal timetables, where they apply to taken modules, as soon as they are finalised by central administration. This will usually be after the initial publication of the teaching timetable for the relevant semester.
Reading list for SOFTWARE CONFIGURATION MANAGEMENT : http://aspire.surrey.ac.uk/modules/com2035
Programmes this module appears in
|Software Development for Business BSc (Hons)||2||Compulsory||A weighted aggregate mark of 40% is required to pass the module|
Please note that the information detailed within this record is accurate at the time of publishing and may be subject to change. This record contains information for the most up to date version of the programme / module for the 2018/9 academic year.