Module Catalogue 2019/20

CSC1035 : Programming Portfolio 2

  • Offered for Year: 2019/20
  • Module Leader(s): Dr Jennifer Warrender
  • Lecturer: Mr Jordan Barnes
  • Other Staff: Dr Sergiy Bogomolov
  • Owning School: Computing
  • Teaching Location: Newcastle City Campus
Semester 2 Credit Value: 30
ECTS Credits: 15.0
Pre Requisites
Code Title
CSC1034Programming Portfolio 1
Pre Requisite Comment


Co Requisites
Code Title
CSC1031Fundamentals of Computing
CSC1032Computer Systems Design and Architectures
CSC1033Information Storage and Retrieval
Co Requisite Comment

In this module students will practise, in a practical situation using synoptic assessment, material covered in the co-requisites. As such it will provide a coherence to all material covered in Stage 1.


By the end of this module students will have gained further experience in, and a knowledge of the basic concepts of all stages of the software engineering lifecycle, both as individuals and as members of a team, namely requirements analysis, design, coding, testing and maintenance, building on the experience gained in Programming Portfolio 1. Particular emphasis will be placed on the development of programming skills. An active learning, problem-based approach is adopted. Students will be given a series of practical problems that relate to various stages of the software engineering lifecycle. Supplementary lectures and online materials will introduce the topics to be tackled, and how to tackle them, but these topics will relate to aspects of the material presented in one or more of the co-requisite modules Computer Systems Design, Information Storage and Retrieval, and Fundamentals of Computing, thus giving students practical enrichment of that material, and/or to specialisms that can be studied at Stages 2 and 3 (HCI, Security, Bio, Games, Software Engineering, Data Analytics) , thus enabling students to gain a flavour of what is available in the later stages of their programme of study and allowing them to make an informed choice towards the end of Stage 2. Students will have gained further awareness of the legal, social, ethical and professional aspects of being a practising software engineer.

Outline Of Syllabus

•       Students expand their knowledge and experience in all stages of the software engineering life-cycle.
•       Lectures and tutorials expand upon general principles of:
-       Variables: types, names, values, storage
-       Arrays and strings
-       Selection and looping
-       Functions
-       Object oriented programming: Classes,Inheritance and Interfaces      
-       Data structures, collection classes, generic types and iteration
-       Time, space, speed trade-offs in program design
-       Understanding programming abstraction
-       Exploring and realising higher level abstractions
-       Error checking/programming with exception handling
-       Recursion with examples from sorting and searching
-       Event Driven Programming
-       Design patterns: immutability, factories, singleton, composition.
-       Students will gain further insight into the legal, social, ethical and professional aspects of being a software engineer

Learning Outcomes

Intended Knowledge Outcomes

After completing this module students will be able to articulate, at a basic level, the wider engineering context that applies to developing complex software systems. They will be able to:

•       Explain the relationship between data abstractions and computer memory.
•       Identify opportunities to use abstraction for code refactoring to promote efficiency and maintainability
•       Outline the advantages and disadvantages of different programming approaches (abstractions, data structures, program flow)
•       Describe the impact on resource usage (time, space, processor) of their design decisions
•       Summarise the legal, social, ethical and professional issues arising in real situations.
•       Report on the processes involved in developing software as part of a team

Intended Skill Outcomes

After completing this module students will be able to tackle all aspects of the software engineering lifecycle, and will be able to

•       Translate a design into well formatted, well documented, efficient piece of software using appropriate abstractions
•       Develop and deploy an appropriate error handling strategy for their software
•       Choose and use appropriate storage mechanisms for data
•       Evaluate online sources of supporting material
•       Schedule their work effectively
•       Reflect on their role as part of a software development team

Teaching Methods

Teaching Activities
Category Activity Number Length Student Hours Comment
Guided Independent StudyAssessment preparation and completion361:0036:00Background reading using online material
Guided Independent StudyAssessment preparation and completion242:0048:00N/A
Guided Independent StudyAssessment preparation and completion241:0024:00Lecture follow up
Scheduled Learning And Teaching ActivitiesLecture242:0048:00N/A
Scheduled Learning And Teaching ActivitiesPractical362:0072:00Computer classroom
Scheduled Learning And Teaching ActivitiesSmall group teaching122:0024:00Tutorial in computer classroom
Guided Independent StudyProject work481:0048:00Working independently or in teams
Teaching Rationale And Relationship

Lectures will be used to introduce each project, and aspects of software engineering, particularly programming. These will be supplemented with tutorials at which discussions will take place on tackling the projects set. During their independent study time, students will review online materials providing further support for development of programming skills. They will also use this time tackle the problems set, as individuals or in teams. The practical sessions will provide support for developing the skills they need for these activities.

Reading Lists

Assessment Methods

The format of resits will be determined by the Board of Examiners

Other Assessment
Description Semester When Set Percentage Comment
Case study2M90Five software artefacts and reports equivalent to 5000 words total.
Report2M10Reflective report. 1000 words.
Assessment Rationale And Relationship

Students will produce a portfolio of evidence that they have mastered practical skills in software development applied to a variety of problems chosen to reflect real world applications but targeted at the skill level of the students when the work is set.

For each topic/problem students will provide a report that contributes to their portfolio of evidence of the activities they have undertaken, either as individuals, or as part of a team. Five software artifacts and reports equivalent to 5000 words total will be required with a single reflective report on the skills gained summarising the portfolio of evidence produced by the problem-based activities equivalent to 1000 words.


Past Exam Papers

General Notes


Disclaimer: The information contained within the Module Catalogue relates to the 2019/20 academic year. In accordance with University Terms and Conditions, the University makes all reasonable efforts to deliver the modules as described. Modules may be amended on an annual basis to take account of changing staff expertise, developments in the discipline, the requirements of external bodies and partners, and student feedback. Module information for the 2020/21 entry will be published here in early-April 2019. Queries about information in the Module Catalogue should in the first instance be addressed to your School Office.