Study Guide

Department of Electrical, Electronic and Computer Engineering

Computer Engineering: Software Engineering EPE 321

© Copyright reserved
 TABLE OF CONTENTS

1. WELCOME ................................................................................................................................... 3

2. EDUCATIONAL APPROACH................................................................................................... 3

3. ARTICULATION WITH ECSA GRADUATE ATTRIBUTES AND OTHER MODULES

IN THE DEGREE PROGRAM........................................................................................................... 4

4. LECTURERS, VENUES AND CONSULTING HOURS .......................................................... 4

5. STUDY MATERIALS AND PURCHASES............................................................................... 5

6. LEARNING ACTIVITIES ........................................................................................................... 6

7. RULES OF ASSESSMENT ......................................................................................................... 9

8. MODULE OBJECTIVES AND LEARNING OUTCOMES.................................................... 11

9. MODULE OBJECTIVES AND LEARNING OUTCOMES.................................................... 12

10. MODULE STRUCTURE ...................................................................................................... 14

11. STUDY THEMES .................................................................................................................. 14

12. SOFTWARE PROJECT ........................................................................................................ 17

2
 ORGANISATIONAL COMPONENT

This guide serves as Part 2 of the study guide for this module and provides content that is specific to
the learning content of the module. Part 1 of the study guide is a General EECE Study Guide available
from the EECE Undergraduate ClickUP page and provides rules and policies that are applicable to all
undergraduate modules presented by the Department of Electrical, Electronic and Computer
Engineering. If you cannot see or do not have access to the current-year EECE Undergraduate
Students ClickUP module, please arrange access as soon as possible by completing the form at
https://goo.gl/3KakBP. All undergraduate-related departmental policies, online resources and
communication are managed through this platform.

1. WELCOME
Over the last three decades software engineering has grown into a huge international enterprise
with an enormous impact on the community and our daily lives. It is deserving of formal academic
study and analysis. The module serves to introduce an engineering approach to the design and
development of software.

The overall objectives of this modules are to:

 familiarise students with the software process.

 Highlight the importance of modelling, design, quality and testing.
 teach students how to manage software projects.

These and various other aspects of software engineering are investigated to obtain a deeper
knowledge of how to implement a disciplined approach to software development.

2. EDUCATIONAL APPROACH
2.1 General approach
This module will be taught in a traditional lecture fashion, where lecture slides will be used to aid the
lecturer in his presentation of the module content. Students are encouraged to participate in the
lecture by preparing questions in advance and by submitting these using email.

You are expected to participate in discussions during lectures and tutorial classes. We focus on
insight and understanding, not mere memorisation of facts. As your fellow students depend on the
inputs you make, your participation is crucial. After all, you are also dependent on their
contributions.

The lecturers may make changes to the content of this study guide to better promote
understanding. Any such changes will be announced on during lectures and on the module’s
ClickUP page.

3
2.2 Online approach
ClickUP will be used in the module for lecture-to-student communication, to post class activities and
assessment. Additionally, the AMS will serve as our primary test and assignment platform. Lectures
will be made available on ClickUP in both a high data version (video) and in a low data version
(slides). Blackboard Collaborate Ultra will be used for lectures with the recording made available
afterwards. EPE 321 will also have a YouTube channel with links to unlisted videos posted on
ClickUP. A request for these to be zero rated via connect.up.ac.za will be made for each video. Please
note that this can take up to 24 hours to complete.

A combination of platforms and tools will be used for the software project. This will allow this aspect
of the module to be conducted fully online, by adapting the workflow of fully remote software
teams. Please visit ClickUP at least once daily to check for updates and ensure that your Tuks email
forwards to your primary inbox should it not be your primary email address.

3. ARTICULATION WITH ECSA GRADUATE ATTRIBUTES AND OTHER

MODULES IN THE DEGREE PROGRAM
The programs presented by the Department of Electrical, Electronic and Computer Engineering have
been designed to meet the eleven ECSA graduate attributes (GAs) that qualify the competencies
required by professional engineers. While most modules contain at least a small component of a
number of ECSA GAs, only the main attributes that are addressed in a module are indicated for the
specific module.

This module is presented at developmental level for GAs 3, 5 and 8. Refer to the General EECE Study
Guide (Part 1) for a complete overview of the association of ECSA GAs with the modules in each
degree program.

Diagrams that show the interrelationship and logical sequence of the various modules in the study
program and the module within the context of the programme, are available on the current year
EECE Undergraduate Student ClickUP (click on Modules and resources>Curricula and Prerequisites>
Electrical Engineering/Electronic Engineering/Computer Engineering).

4. LECTURERS, VENUES AND CONSULTING HOURS

Name Room number and building Telephone numbers and E-mail
address

Lecturer Mr JM Marais Appointments will be Refer to module website.

conducted online.
Assistant lecturers Mr P Kok & Mr G Appointments will be Refer to module website.
Naudé conducted online.
Secretary Ms R Herman Eng 1, 13-20 012 420 3735
[email protected]
Faculty Student Your Faculty Student Advisor can advise you on goal-setting,
Advisor adjustment to university life, time management, study
methods, stress management and career exploration. Book an
individual consultation or attend a workshop. For other support

4
 services see Paragraph 12 in the EECE General Study Guide.

4.1 Location of the Laboratories

It is expected that all practical aspects will be conducted online. That said, this module’s traditional
location is Engineering 3 building, Netlab A (refer to the module website for updates).

4.2 Consulting hours

Refer to the section on consultation and communication with lecturers in the General EECE Study
Guide.
Kindly refer to the module website for specific arrangements about consultation hours. Hours for
consultation of lecturers, tutors and teaching assistants will be announced at the beginning of the
semester, and will also be given on the announcement page of the module web page. Students may
consult lecturers, tutors and teaching assistants only during the consulting hours as indicated, or by
appointment. This policy also holds before tests and exams. In other words, lecturers, tutors and
teaching assistants are only available during their normal consulting hours on the day before a test
or examination. This policy aims to encourage students to plan their work and to work continuously.

4.3 Timetable
The lecture timetable can be found on your student portal or at chemeng.up.ac.za/timetables/.

5. STUDY MATERIALS AND PURCHASES

5.1 Prescribed textbooks
 Pressman, Roger S and Maxim, Bruce R. 2015. Software engineering, a practitioner’s approach.
Eighth Edition, McGraw-Hill. ISBN-13: 978-1259253157

5.2 Other prescribed material

A set of slides that will be presented during lectures will be loaded on to the module’s ClickUP page
during the course of the semester. Additional study resources will also be used. Details of the
additional resources will be made available during the semester on the module website.

5.3 Recommended material

There are a lot of relevant materials on the Internet and books in the library. Students will be
expected to make use of these sources to complete their tasks.

5.4 Components
Only software components will be required for this module. Every effort is made to use only open-
source software or software that can be used for free duration of the module. Students are expected
to do the required steps to register for the GitHub Student Developer Pack.

5
6. LEARNING ACTIVITIES
6.1 Contact time and learning hours
The allocation of time to teaching and learning activities in this table reflects that of
contact teaching and learning. Time allocation for online teaching and learning
activities as necessitated by the COVID-19 pandemic will be aligned with the revised
presentation structure of the module and may deviate from the time allocations in this
table. Lectures, tutorials and practicals (contact time)
Contact time Preparation Total time per Number Total time per
per week per week week (hours) of semester
(periods) (periods) weeks (hours)
Lectures* 3 0 2,5 12 30
Tutorials 0 0 0 12 0
Practicals 1 7 6,7 12 80
Assignments and assessment (non-contact time)
Assessment Preparation Total time per
time (hours) time (hours) semester
(hours)
Assignment(s) 0 20 20
Class Tests* 2,5 2,5 5
Semester test 1,5 7,5 9
1
Semester test 1,5 7,5 9
2
Examination 3 15 18
Module hours 166
Module credits 16
Note 1: The time allocation in this table represents nominal hours, i.e. some students
might require less and others more time to attain the pass requirements.
* Note 2: As class tests are written during lecture periods, the times allocated for class
tests are included in the total lecture time.

6.2 Lectures
Lectures are presented in a style of co-operative and student-centred learning. Lecture content and
structure will be based on the prescribed and recommended study material. Note, however, that
various problems and examples that are not in the textbook will be discussed during lectures.
Students are expected to prepare for classes as specified further on in this guide.
Attendance of lectures is compulsory and register of attendance may be taken to determine which
students bring their part and work consistently. Refer to the general EECE study guide for the
departmental strategy to deal with absence from lectures. Important announcements with respect
to laboratory sessions, assignments, tutorials and discussions of test content will be made during
lecture times. Students need to take note that only selected components of content, assessments
and arrangements delivered in face-to-face lectures will be made available online, e.g.
announcements regarding tests, assignments, memoranda (optional), lecture notes (optional),
etcetera. Lecturers are not obliged to publish all content delivered during lectures online as a hybrid

6
teaching and learning strategy will be followed where a significant component of the teaching and
learning activities is face-to-face.

Please note that lectures that cover the practical component of the module are considered as part of
the practical component of the course and attendance of these lectures is thus compulsory.

Progressive evaluation and presence tests: The lecturer may at any time take down a class test on
the material covered thus far in the module as well as the material that had to be prepared for that
specific lecture. These test marks may contribute to the semester mark.

6.3 Hybrid teaching and learning approach

Refer to the section on hybrid teaching and learning in the General EECE Study Guide.

In this module, a number of hybrid approaches to teaching and learning will be followed. The use of
each in the module will be discussed and explained during lecture periods. Hybrid tools that will be
used include:

 Extensive use of the module website to archive learning materials and additional materials.
 Grading through the AMS and ClickUP.
 Dedicated EPE321 YouTube channel for module related videos.
 Video messaging apps for meetings and project demonstrations.
 The use of several software development tools.

This list may be expanded during the semester if additional suitable hybrid teaching and learning
tools are discovered.

6.4 Tutorial classes

Tutorial classes will focus on discussing the software project as well as the software development
tools that must be used to complete the project. Additionally, the tutorial classes will intent to
prepare students for tests and examinations. Refer to the module website for details.

6.5 Assignments
All the assignments that have to be completed for this module and that could contribute to your
semester mark will be provided in due course. Due dates are given with each assignment and in the
module composition later in this guide. Failure to hand in assignments before the deadline will result
in the student receiving no marks for the assignment. Some of the assignments are compulsory –
details are given with each assignment. Please note that all assignments that are graded to
contribute to the semester mark must be handed in to gain entrance to the exam. All assignments
that may contribute to the semester mark, will be submitted electronically via ClickUP and the AMS.

Every assignment must be completed individually or in groups as specified in each assignment. You
may make use of your textbook and other resources on the web or in the library, excluding a
consultant. If you make use of program sections on the web or other sources, you must provide a
complete reference to each source. If there is suspicion that any part(s) of the work has been
copied from another student’s work or from another source, a mark of zero will be awarded. Please
refer to the plagiarism warning Part 1 of the guide. According to the University's regulations the

7
lecturer is obliged to charge guilty students with dishonesty that may lead to suspension. You will be
required to sign the following declaration on the front page of your assignments:

I, name and surname, hereby declare that the work herewith is completely my own and that no
parts have been copied in any way from current or previous students or other sources.

6.6 Project work

General approach and practical guide

Each student has to attend and complete all the required practical sessions during the
semester. The practical sessions are compulsory. Failure to attend a practical session, or to
hand in a document at the specified time, will result in your being denied permission to
write the final examination. Practicals will take the form of a multi-stage development of a
specified software product.

Project assignment and teams

Students will work in teams to study, implement, and document a project, which will require them
to apply the knowledge obtained during the course. Details of assignments and the project will be
provided at a later stage in a separate document.

The ‘contribution’ section of the prescribed cover page for group assignments does not have to be
completed for assignments in EPE 321 as they will all form part of the semester project. The
contributions of the various group members to the group project will be determined at the end of
the semester. The mark an individual student receives for group work is the product of the mark
allocated to the group and the portion of work done by that individual student as a ratio of the
portion that is expected of each student. For example, if there are five people in the team and
student A contributed 20% of the work, the actual mark awarded to the group will be awarded to
student A; if student A only contributed 10% of the total work, he/she will be awarded half the
mark awarded to the group.

Project fall-back strategy

The project in this module is completed in teams. In the event of team members deregistering, the
remaining group member(s) must immediately inform the lecturer. Depending on when this occurs,
it may be viable for these members to join other groups (they will not be forced onto other groups).

Should this not be the case, the following will apply.

 Students need to apply with reasons to the lecturer for explicit permission to continue with
the fall-back strategy.

 If the deregistered group member is partly or wholly responsible for the system’s
communication, the remaining group members may modify the project so that a single-
player version is presented with which a human can play against AI opponents.

 If the deregistered group member is partly or wholly responsible for the system’s
AI, the remaining group members may modify the project to remove the AI component.
Human players must still be able to have a game against each other.

8
  For the GUI, the team will be evaluated by excluding the GUI’s marks from the remaining
evaluations. The team will be required to develop a very basic GUI to allow the remaining
integrated subsystems to be marked during the Final Demo.

 For the game server, the team has the option to transfer ideally the AI member or,
otherwise, the GUI member to the game server role. That role will then be excluded from
the remaining evaluations. If that role was the GUI, a basic version will still be required. The
team may also decide to rather implement a basic version of the game server to allow the
remaining integrated subsystems to be marked during the Final Demo.

 Students will also be required to implement any additional functionality required to

demonstrate the functionality of the remaining and fully integrated subsystems.

Note that this fall-back strategy will not be implicitly followed should a group decide to consist from
the start of fewer members than the recommended amount (should this even be allowed). These
groups will still be required to deliver the full project. Further note that this fall-back strategy may be
updated should the need arise.

7. RULES OF ASSESSMENT
Refer to the section on assessment in the General EECE Study Guide. Also see the examination
regulations in the Year Books of the Faculty of Engineering, Built Environment and Information
Technology.

9
7.1 Requirements, subminima and calculation of marks

Primary Requirements 1. The examination schedule per module is compiled in

accordance with the Examination Regulations of the Faculty, as
well as the General Examination regulations of the University.
2. Minimum examination mark: To pass a module a student
must attain an examination mark of at least 40% and a final
mark of at least 50%.
3. Admission to examination: In order to be admitted to the
final examination in a module, a semester/year mark of at
least 40% is required, with the exception of first year modules
on the first semester level, where a semester mark of at least
30% is required. In addition, all other examination admission
requirements must be complied with, as applicable to the
specific module.

Calculation of final Semester mark: 50%

mark Examination mark: 50%
Calculation of semester Semester test 1: 17% (I)
(year) mark Semester test 2: 17% (I)
I = individual; G = group Class Tests: 6% (I)
ClickUP Quiz: 3% (I)

Software project:
Individual Work: 37% (I)
Group Work: 20% (G)
Specific requirements All scheduled practical sessions must be attended and all
practical assignments must be completed to a satisfactory
level. All semester projects and tasks must be completed to a
satisfactory level as per Departmental rules.

Failure to comply with any of the above will result in

examination refusal.
Subminimum As per primary requirements above.
requirements
Additional subminumum requirements (semester):
1. A mark of at least 50% must be attained for the project.
2. A mark of at least 50% must be attained for the individual
part of the project mark.
3. An average of more than 30% for the semester tests.

Additional subminimum requirements (examination/final

mark):
None
Requirements for No promotion allowed
promotion

10
7.2 Assessment details
Assessment approach
The department’s electronic grading system (assessment management system AMS) will be used to
manually grade nearly all assessments (documents, demos, class tests, semester tests and exams).
ClickUP test(s) will also be given and Turnitin will be used on documents and code submissions. Our
current intention is that all assessments (including demos) will be conducted online but this may
change as the semester progresses. Please regularly visit the module website as all changes will be
communicated there.

Class tests
The class test(s) will be, each, between 20 and 45 minutes in duration and will be written online
either in class time or during one of the practical periods.

Semester tests
Two tests of 90 minutes each will be written during the scheduled test weeks of the School of
Engineering. Dates, times and (perhaps) venues will be announced as soon as the timetables
become available.

Examinations
The duration of the examination is 3 hours.

Study material in tests and exams

All online tests and exams are OPEN BOOK unless stated otherwise.

8. MODULE OBJECTIVES AND LEARNING OUTCOMES

Refer to the EECE General Study Guide (Part 1 of the study guide) for procedures, policies and rules
about absence from formal evaluation opportunities and practical sessions, grievance procedures,
academic dishonesty and plagiarism.

11
 MODULE INFORMATION

9. MODULE OBJECTIVES AND LEARNING OUTCOMES

9.1 Purpose of the module
Software Engineering deals with the application of proper, well-defined engineering principles to
the development and maintenance of high-quality software, with the following goals in mind:
• production of fully functional software,
• within the given time constraints, and
• within budget.
Software Engineering also deals with the production by a team of large software systems where
no one person has complete knowledge of all the details. Clear written and verbal communication
among team members, clients and users is vital. The following disciplines are incorporated in any
software engineering project:
• computer science,
• engineering design,
• project management, and
• human interaction.

The general objective of this module is to place emphasis on understanding rather than
memorisation of software engineering principles. Students will be expected to implement these
principles in their semester project.

1. Learning is best facilitated when there is a genuine need to know! The purpose of lectures is to
facilitate and aid your learning by creating an awareness of a knowledge vacuum. However, the
process of meaningful learning is only possible when it is driven by your genuine enthusiasm and
desire to learn, and sparked by the challenge to acquire and master new concepts. It is not the
lecturer's responsibility to make you learn, but rather to work with you to help you make the
best use of an opportunity.
2. The lectures provide an important overview of the work, and as far as time allows, an
opportunity to understand the details of various techniques. However, due to the limited
contact time, self-study is an essential component of the course without which it will be
impossible to master the work.
3. This study guide provides only a rough outline of the work covered. Your most important source
of information is your textbook and lectures.
4. We assume that you attend class and therefore important announcements will be made in class,
such as arrangements for practical sessions, homework assignments and tutorials, and
discussions about the content of tests. Where possible, these will also appear on ClickUP.

12
9.2 Module outcomes
ECSA graduate attributes
The critical learning outcomes for the module are qualified through the ECSA graduate attribute
requirements as discussed in the General EECE Study guide. The following skills are developed at the
indicated level and a student must demonstrate competence in each to be able to pass the module.

ECSA GA 3: (developmental level)

Engineering Design
Perform creative, procedural and non-procedural design and synthesis of components, systems, engineering
works, products or processes.

The student must demonstrate competence in designing, implementing and testing a

complete software system and its various subsystems.

This outcome is explicitly assessed in the practical component of the module.

ECSA GA 5: (developmental level)

Engineering methods, skills and tools, including information technology
Demonstrate competence to use appropriate engineering methods, skills and tools, including those based on
information technology.

The student must demonstrate competence in the use of software engineering tools and
design principles when developing a complete software system.

Assessment of this outcome is distributed throughout all components of the module.

ECSA GA 8: (developmental level)

Individual, team and multidisciplinary working
Demonstrate competence to work effectively as an individual, in teams and in multidisciplinary environments.

Students have to work both individually and in teams on the practical component of the
module. They need to design develop and evaluate their own individual subsystems of the
prescribed software system. The students also need to work together to combine the
individual subsystems into a complete software solution.

This outcome is indirectly assessed in the practical component of the module.

9.3 Cognitive level of assessment

Refer to the section on the cognitive level of assessment in the General EECE Study Guide.

%* * Estimate of the % of the total assessment,

including all forms of assessment applied in this
1. Knowledge 10
module, devoted to the various levels of cognitive
2. Comprehension 10 thinking skills and of UP graduate attributes.

3. Application 10

13
 4. Analysis 10 ** Assessment UP graduate attributes:
 Practical skills
5. Synthesis 20
 Technical communication
6. Evaluation 10  Effective visual communication/"marketing"
skills
7. Other skills** 30  Team working skills
 Time management

10. MODULE STRUCTURE

The detailed structure and schedule for the module is available on the module website. Please check
the structure regularly so that you are aware of any changes.

11. STUDY THEMES

11.1 STUDY THEME 1: Introduction and software development processes
Learning outcomes
After completion of this study theme the student will:
 Know and understand what software and software engineering are and know the definitions of the
concepts.
 Understand the challenges in software development.
 Know the application domains of software.
 Understand how the quality focus and requirements are substantiated in the use of process
models, methods, techniques and tools.
 Know and understand the generic framework process model.
 Understand the role of different umbrella activities in the development process.
 Understand how and why process models can be adjusted.
 Know and understand Polya's description of the essence of software engineering practice.
 Know and understand David Hooker's principles for the development of software.
 Recognise and expose different myths that exist in software engineering

Study-units
 Pressman & Maxim, chapters 1 and 2.
 Supplementary material uploaded to ClickUP.

11.2 STUDY THEME 2: Software development processes

Learning outcomes
After completion of this study theme the student will:
 Understand the importance and role of software development processes.
 Be able to distinguish among different kinds of process model and be able to provide and
recognise examples of each.

14
 Know the different prescriptive software process models, the strengths and weaknesses of
each and know for which application each one would be suitable.
 Understand the need for agile development and the role thereof.
 Know and understand the agile manifesto and be able to conduct a debate on it.
 Explain the potential advantages of agile development in the correct application.
 Know and be able to use different agile development models and know their properties.

Study-units
 Pressman & Maxim, chapters 3 - 5.
 Supplementary material uploaded to ClickUP.

Self-study activities
Exercise on ClickUP.

11.3 STUDY THEME 3: Teamwork

Learning outcomes
After completion of this study theme the student will:
 Know the properties of a good software engineer and display the properties while working on the
group project.
 Understand the psychology of software engineering and be able to use the knowledge proactively
in the project development team.
 Know the qualities of a successful team and be able to encourage these qualities in the team of
which he/she forms part.
 Know and understand the different team/organisational structures and know when each one will
be more appropriate.
 Be able to identify team toxicity and know how to address and prevent it.
 Know the properties of agile teams and, where applicable, be able to promote that in a team.
 Be able to use social media effectively in team cooperation, understand the potential dangers of
social media on team cohesiveness and know how to prevent these.
 Have knowledge of collaborative development environments (CDEs).
 Understand and be able to explain the realities of global teams.

Study-units
 Pressman & Maxim, chapter 6.
 Supplementary material uploaded to ClickUP.

Self-study activities
Application in the group project.

11.4 STUDY THEME 4: Software engineering principles

Learning outcomes
After completion of this study theme the student will:
 Know and understand the different principles that must be applied during the software
development process and apply them effectively during the different phases of the project.

15
 Study-units
 Pressman & Maxim, chapter 7.
 Supplementary material uploaded to ClickUP.

Self-study activities
The principles must be reviewed as each phase of the development process is discussed and must be
applied in the group project.

11.5 STUDY THEME 5: Requirement analysis

Learning outcomes
After completion of this study theme the student will:
 Know and understand the different phases of requirement analysis and be able to carry them
out.
 Be able to compile a multi-faceted analysis model as an individual and in a group.
 Be able to compile a complete software requirement specification.
 Know, understand and be able to apply all study material contained in the study units below.

Study-units
 Pressman & Maxim, chapter 8-11.
 Supplementary material uploaded to ClickUP.

Self-study activities
The development of a proposal document and a software requirement specification working as an
individual. This theme must also be applied in the group project.

11.6 STUDY THEME 6: Design

Learning outcomes
After completion of this study theme the student will:
 Know and understand the different design concepts.
 Understand which properties are desirable in software design and understand which
advantages these properties have.
 Be able to draw relations between the desirable properties.
 Know the different design elements and models, understand the role of each one, and be able to
apply the different models to problems.
 With reference to the group project, be able to compile a relevant design specification that will
result in effective and high-quality implementation of the product.
 Know the properties of a good user interface, be able to evaluate a user interface, and be able to
design a good user interface.

Study-units
 Pressman & Maxim, chapter 12-16.
 Supplementary material uploaded to ClickUP.

Self-study activities
The completion of an individual and a group design specification.

16
11.7 STUDY THEME 7: Quality management
Learning outcomes
After completion of this study theme the student will:
 Understand the importance of software quality.
 Know and understand the cost of ensuring quality and the potential costs of a lack of quality.
 Know and understand the different definitions and factors related to software quality and
know how to apply these in the software development process.
 Know, understand and be able to apply reviewing methods, and know and be able to explain the
advantages of these methods.
 Know and be able to apply software quality assurance principles and approaches, and know the
relevant quality standards.
 Know the different test strategies and techniques, know the advantages and disadvantages of
each, and apply an appropriate approach to the group project.
 Apply configuration management to the group project.

Study-units
 Pressman & Maxim, chapter 19-24.
 Supplementary material uploaded to ClickUP.

Self-study activities
Application in the group project.

11.8 STUDY THEME 8: Managing software projects

Learning outcomes
After completion of this study theme the student will:
 Know the spectrum of management and understand the priorities.
 Know the W5HH principle and be able to apply it to any project
 Know the different approaches to project estimation and understand the advantages and
disadvantages of each approach.
 Understand the principles of project scheduling.
 Understand the relation between total effort, number of people and time allowed for the
development of various software projects.
 Understand what is meant by the ‘mythical man month’.

Study-units
 Pressman & Maxim, chapter 31, 33 - 35.
 Supplementary material uploaded to ClickUP.

Self-study activities
Application in the group project.

12. Software project

Details on the software project are available on ClickUP. The information, game rules, guides,
tutorials, announcements and any other content published on the module website form part of the
study guide for this module.

17