Back to Module List

CMPC3B10 - SYSTEMS ENGINEERING

Module Code:
CMPC3B10
Department:
Computing Sciences
Credit Value:
20
Level:
3
Organiser:
Dr. Pam Mayhew
This module draws together a wide range of material and considers it in the context of developing modern large-scale computer systems. Topics such as Outsourcing, Process Improvement, System Failure, Project Management, Configuration Management, Maintainability, Legacy Systems and Re-engineering, Acceptance and Performance Testing, Metrics and Human Factors are covered in this module. The module is supported by a series of industrial case studies and includes speakers from industry.

The majority of the lectures in this course can be given through use of a standard overhead projector. No other special teaching resources are envisaged.


Module Text

There is no specific text to purchase for this module as the literature will be made available when you need it.

Suggested Background Reading

  • DeMarco and Lister, Waltzing with Bears: Managing Risks on Software Projects, Dorset House Publishing, 2003.
  • DeMarco and Lister, Peopleware: Productive Projects and Teams, Dorset House Publishing, 1999.
  • Galin, Software Quality Assurance: From theory to implementation, Pearson/Addison Wesley, 2004.
  • Hall and Fernandez-Ramil, Managing the Software Enterprise, Thomson, 2007.
  • Pressman, Software Engineering: A Practitioner's Approach, (6th Ed), McGraw Hill 2004.
  • Somerville, Software Engineering, (8th Ed.), Addison Wesley, 2006.
  • Stevens, Brook, Jackson, Arnold, Systems Engineering: Coping with Complexity, Prentice Hall, 1998.

Web-based material:
There is a wealth of comprehensive material on the web, including:


Submission:

Written coursework should be submitted by following the standard CMP practice. Students are advised to refer to the Guidelines and Hints on Written Work in CMP.

Deadlines:

If coursework is handed in after the deadline day or an agreed extension:
 

 

Work submitted Marks deducted
After 15:00 on the due date and before 15:00 on the day following the due date 10 marks
After 15:00 on the second day after the due date and before 15:00 on the third day after the due date 20 marks
After 15:00 on the third day after the due date and before 15:00 on the 20th day after the due date.  All the marks the work merits if submitted on time (ie no marks awarded) 
After 20 working days Work will not be marked and a mark of zero will be entered


Saturdays and Sundays will NOT be taken into account for the purposes of calculation of marks deducted.

All extension requests will be managed through the LTS Hub. A request for an extension to a deadline for the submission of work for assessment should be submitted by the student to the appropriate Learning and Teaching Service Hub, prior to the deadline, on a University Extension Request Form accompanied by appropriate evidence. Extension requests will be considered by the appropriate Learning and Teaching Service Manager in those instances where (a) acceptable extenuating circumstances exist and (b) the request is submitted before the deadline. All other cases will be considered by a Coursework Coordinator in CMP.

For more details, including how to apply for an extension due to extenuating circumstances download Submission for Work Assessment (PDF, 39KB)
 

Plagiarism:

Plagiarism is the copying or close paraphrasing of published or unpublished work, including    the work of another student; without due acknowledgement. Plagiarism is regarded a serious offence by the University, and all cases will be investigated. Possible consequences of plagiarism include deduction of marks and disciplinary action, as detailed by UEA's Policy on Plagiarism and Collusion.


 


Module specific :

  • To introduce the concept of systems and to consider the domain of computer-based systems engineering (CBSE)
  • To investigate the nature of both systems and computer-based systems failure and how the systems approach may be used to better understand such failures
  • To introduce students to the various aspects of quality which have to be taken into consideration in CBSE
  • To investigate the levels of risk inherent in the domain of CBSE projects
  • To examine the use of product and process metrics in CBSE
  • To examine testing strategies in CBSE
  • To investigate the principles of managing large scale CBSE projects
  • To explore the concept of software process improvement as a means of effecting continual improvement to the CBSE process
  • To assess the importance of adopting a configuration management approach to CBSE projects
  • To investigate the concept of software maintenance
  • To explore the concept of peopleware
  • Learn to use case studies to reflect on a range of industrial examples

Transferable skills:

  • Written Communication: Students have to write a paper for inclusion in the unit's mock conference
  • Oral Communication: Students are encouraged to participate in workshop discussions, and have to present their coursework paper at the module's mock conference
  • Gain experience of identifying and interpreting factors which affect the industrial environment and thereby be a more immediately useful employee, even from first employment.

On completion of the module students should be able to:

 

  1. Describe the importance of examining systems from a holistic viewpoint rather than concentrating purely on the software component.
  2. Describe, with the use of examples, some of the common failures associated with computer-based systems.
  3. Describe the role of project management and risk management in the system development process.
  4. Explain the relationship between metrics, quality, and reliability, and whole life cycle testing.
  5. Explain the importance of, and issues surrounding, testing, configuration management, and maintenance.
  6. Explain the meaning and relevance of software process maturity models.
  7. Explain the importance of peopleware considerations to successful systems development.
  8. Have a clear understanding of the factors which affect an industrial environment
  9. Have acquired skills to help with the identification and interpreting of factors which affect the development, manufacture, distribution, marketing and sales of products

Total hours: 48

Lectures: 36 hours (with provisional weekly schedule)

  1. Systems Engineering: Investigating systems engineering as a discipline. The systems approach. Computer-based systems engineering (CBSE). The CBSE functions: process, quality, and project. Systems Failure: the nature of systems failure; the use of the systems approach to understand systems failure
  2. Outsourcing
  3. Project Management
  4. Quality: Quality control; Quality assurance; Total quality management; Quality documents; Audits; Validation and verification; software quality characteristics
  5. Risk Assessment: what is risk: systems engineering risks; the 5 fundamental risk factors in CBSE; risk management
  6. Metrification: the need for measurement in software and systems engineering; measuring the unmeasurable; GQM framework; classification of software measures; components of software measures; scope of software metrics; cost and effort estimation; metrification models; data collection; the human issues with metrification
  7. Spare / Reading Time
  8. Process Improvement: the software process; a 'defined' process; immature and mature organisations; the capability maturity model; ISO9000 series of standards; Bootstrap; SPICE;
  9. Configuration Management: the nature of systems changes; what is configuration management; configuration control; configuration audits and reviews. Maintenance: motivations for maintenance; types of maintenance activity; reducing the maintenance problem; image of maintenance; organising maintenance activities
  10. Testing: Testers, verification, validation, organising for testing
  11. Peopleware: The project manager's point of view, "quality is the key", improving productivity, making work fun!
  12. Coursework presentations
  13. Coursework presentations

Seminars:  12 hours (with provisional weekly schedule)    

  1. Understanding the inherent nature of software, and themes from Brooks' No silver bullet paper.
  2. Globally Distributed Software Development
  3. Examining a systems failure
  4. Risk - investigating the London Ambulance Systems debacle
  5. Metrification exercises
  6. Spare / Reading Week
  7. Software Product Line
  8. Looking at departmentalisation in software maintenance
  9. Comparison of traditional engineering and systems engineering
  10. People Issues
  11. Coursework presentations
  12. Coursework presentations

Laboratory work: 0 hours


This module is assessed by both coursework and examination. The coursework consists of two elements. Firstly, students are expected to write a 2,500 word paper on a selected topic within the computer-based systems engineering remit which they will then be expected to formally present in a presentation attended and marked by both faculty and their peers. This piece is worth 30% (20% for the report, and 10% for the presentation) Secondly, they will be assessed on their attendance of, and contribution to, workshops. This is worth 10%. The written coursework is given out in week 3 and is to be submitted in week 12. It will be returned after Easter.  

Setting of Coursework:

Coursework will be set in week 3. A copy of the coursework will be handed to students during the week 3 lecture but will also be made available on Blackboard for students to download and print. The written report should be posted in the appropriate coursework boxes in CMP during week 11 The presentations will take place in week 12.