Bachelor of Electrical and

Electronics Engineering Year 3 -

Evening (BEEE3E) - Honours

Introduction to Software Engineering (ISE-311)

Prepared by:
T. Chadza
Lecturer in Telecommunications
School of Engineering – Department of Electrical Engineering
Malawi University of Business and Applied Sciences (MUBAS)
 Lesson Intended Learning Outcome
• By the end of this lesson, the student should
develop a good understanding of the course
content and requirements.

2/10/2022 TChadza2022 2
 Outline
• Introduction
• Module aim
• Module intended learning outcomes
• Prerequisites
• Assessment
• Indicative content
• Teaching and learning methods
• Prescribed texts
• Recommended resources
• MUBAS project database
• Summary
• Next lesson

2/10/2022 TChadza2022 3
 Introduction
• Software engineering
– systematic approach to development, operation,
maintenance, and retirement of software.
– focuses on general software unlike other
Computer science topics (OS , DBMS , Compilers
etc) which talk about specific types of software
product
– basic question is “How to develop an industrial-
strength software?”

2/10/2022 TChadza2022 4
• A student software system is built primarily
for demonstration and not for later use
• Industrial-strength software system solves
some client problem and is used by the
client’s organization for operating some part
of business:
– Malfunctioning can have huge impact in terms of
financial or business loss, inconvenience to users,
or loss of property and life.
2/10/2022 TChadza2022 5
 Software System
Issue Student Industrial Strength
Developer User Others
Bugs Tolerable Not tolerated
UI Not important Very important
Documentation Not needed needed for the user, organization and project
Software Not in critical use Supports important functions / business
Reliability Not important very important
Robustness Not important very important
Investment None Heavy
Portability Not necessary is key

2/10/2022 TChadza2022 6
• Quality Attributes– ISO standard

2/10/2022 TChadza2022 7
• Functionality
– capability to provide functions which meet stated
and implied needs for software use
• Reliability
– capability to provide failure-free service
• Usability:
– capability to be understood, learned, and used

2/10/2022 TChadza2022 8
• Efficiency.
– capability to provide appropriate performance relative
to the amount of resources used.
• Maintainability
– capability to be modified for purposes of making
corrections, improvements, or adaptation.
• Portability.
– capability to be adapted for different specified
environments without applying actions/means other
than those provided for the product purpose

2/10/2022 TChadza2022 9
 Module aim
• To equip students with knowledge and skills in
software development

2/10/2022 TChadza2022 10
 Module Intended learning outcome
• On completion of this module, the student
should be able to:
– describe the programming stages and techniques
used in software development;
– apply techniques of software development to an
engineering problem; and
– classify levels of software development.

2/10/2022 TChadza2022 11
 Prerequisites
• CIT-ITC-1-1

2/10/2022 TChadza2022 12
 Assessment
• Final Exam: 70%
• Coursework: 30%
– Project: 20%
• Documentations
• Presentation
• group grade: marks for documentation equally divided unless the
team specifies a different distribution (based on contribution)
• individual mark: presentation, meeting with client
– Mid-Sem exam: 10%

2/10/2022 TChadza2022 13
 Indicative content
• Software life cycle
• Software process and other models
• Software project management
• Software project planning
• Risk analysis and management
• Data Management
• Programming Languages

2/10/2022 TChadza2022 14
 Teaching and Learning
Methods
• Lectures, tutorials and group discussions

2/10/2022 TChadza2022 15
 Prescribed Texts

2/10/2022 TChadza2022 16
 Recommended Resources

2/10/2022 TChadza2022 17
 MUBAS Project Database
• Students at the MUBAS conduct final year projects in
their 5th year. For years all these projects have been
stored at the library in hardcopy format as well
softcopy version shared to the individual lecturers. This
has made it hard to keep track on the progress of the
projects as years have passed. Also, students tend to
repeat projects with exact requirements that their
colleagues did because they have no database of
previous projects.
– Goal is to design and plan the development of this system.
– System should work like GitHub where students can search
projects easily and even download projects
documentation.

18
 Summary
• In this lesson, we have developed a good
understanding of the course content and
requirements.

2/10/2022 TChadza2022 19
 Next Lesson
• In the next lesson, we will discuss the
software life cycle

2/10/2022 TChadza2022 20
 References
• Jalote P. (2008). A Concise Introduction to
Software Engineering. Springer.
• Kamwendo, L.Y. 2021. Introduction to Software
Engineering Lecturer Notes. MUBAS
• Masi, F. 2022, Introduction to Software
Engineering Lecturer Notes. MUBAS

2/10/2022 TChadza2022 21
 Thank you!
Src: IFC 2002

2/10/2022 TChadza2022 22