SOFTWARE ENGINEERING 1

BACHELOR OF SCIENCE IN COMPUTER SCIENCE

1ST SEMESTER SY 2020-2021
SOFTWARE ENGINEERING OVERVIEW

1st ONLINE CLASS DISCUSSION

Professor’s Name: JHAMIE TETZ INFANTE-MATEO, MSIT, MDM,
DM
Contact details: [email protected]
09157358752
 Do Do Do

Listen and Ask questions Respect

remember after the topic/s. individual
important tips. differences.
 Online Class Sign-in Instructions

Step 1: Create your Gmail account

Step 2: Proceed to Google Classroom

Step 3: Join the Class using the code czgrq5u

Step 4: Start exploring the topics and activities

 COURSE COURSE
COURSE CODE: SE101 SOFTWARE ENGINERING 1 3.0 UNITS
NAME: CREDITS:
FLEXIBLE LEARNING ONLINE M- PRE- OBJECT – ORIENTED TYPE OF Lecture &
MODE (Contact Hour): 7AM-12NN REQUISITE: PROGRAMMING COURSE: Lab
SOFTWARE
PRE-REQUISITE COURSE TOTAL NO. OF HOURS INCLUDING
ENGINEERING 90.0 hours (5 HOURS/WEEK)
TO: LAB SESSION:
2
This course allows the students to apply engineering and computer science concepts when developing
and maintaining robust, usable, user-friendly and dependable software. It is designed to utilize
COURSE software engineering methodologies of Software Development Life Cycle (SDLC) then by software
DESCRIPTION: modeling using Unified Modeling Language (UML) in parallel to create visual models of object-oriented
software. Alongside is the application of project management for the purpose of delivering (prototype)
high-quality, affordable software that satisfies client needs.
 
 PROGRAM
GRADUATE MC MC MC
ATTRIBUTES PROGRAM GRADUATE OUTCOMES (Applicable to the Course): LO LO LO
(Applicable to 1 2 3
the Course):
Manages complex system. Builds fully functioning applications while offering clients with
SOFTWARE analytical advices to help reach strategic outcomes. Collaborates with IT while managing
ENGINEER resources, coordinating roles and responsibilities and supervising technical project plan, P P P
utilizing the software development lifecycle.
Utilizes innovative idea to provide solutions to client’s problem and applies technical
AGILE
expertise to see issues before it even happens. Assesses current system, while working
SOFTWARE
closely with analysts, end users/marketing, and designers and produce improvements for P P P
DEVELOPERS
the system.
 MAJOR COURSE LEARNING
ATTRIBUTES OUTCOMES
OUTCOMES
INDICATORS DUE DATE

MCLO1: Creates efficient processes while Project Proposal Documentation

understanding pattern design to develop (Requirements Analysis/ September 2, 2020
SYSTEMS
resilient and fault tolerant systems with Specification) of a New or Re- https://bit.ly/2AifQ54
THINKING (K) PDF format not exceeding100MB
large-scale data stores and using cloud- Engineering of an existing
based technology. technology/system.

MCLO2: Applies the methodologies of object-

oriented analysis and design to determine the October 2, 2020
SOFTWARE
needs and conditions of a new or altered product https://bit.ly/2XFat7S
DESIGN or project, looking deeply into a possible Project Design
PDF, Video (mp4), Slide Deck and Audio
SPECIALIST(S) conflicting requirement by the different (mp3) files not exceeding100MB each file.
stakeholders

MCLO3: Participate as an individual to December 2, 2020

https://bit.ly/2ZpikSV
TEAMPLAYER deliver quality software system while Project Proposal Presentation with
PDF, Video, Document, Slide Deck, Image
(A) managing through change and Revalida and Audio files not exceeding 100MB
uncertainties. each file.
 Online
Face to Face
Total Student Learning Time Learning
SLPA TLT
(SLT) TL T P SCL/O A OL OA

TL = Traditional Lecture
T = Tutorial 4 4
P = Practical 30 6 36
SCL/O = Student Centered
12 12
Learning/Others
O = Others
A = Assessment 4 4 8
OL = Online Learning
OA = Online Assessment
SLPA = Self Learning Preparation &
30 30
Assessment
TLT = Total Learning Time 90
 EXPECTED OUTCOMES FOR
PRELIMS
1. Interpret the three major methodologies 4. Create the sequence of activities
in software engineering; and deliverables in an iterative life
2. Show an understanding of software cycle model;
engineering code of ethics in 5. Compare and contrast the two
professional practice. categories of life cycle models;
3. Illustrate the software development life and
cycle (SDLC);
6. Apply abstraction to the UML
4. Create the sequence of activities and artifacts to arrive at essential
deliverables in a sequential life cycle object-oriented modeling concepts.
model;
 COURSE OUTLINE FOR PRELIMS
(For Online Discussion)
Part 1: Introduction to Part 2: Software Part 3: Software Modeling
Software Engineering (5 Development Life Cycle (5 hours)
hours) Models (5 hours) ◦ 3.1: Object-Oriented
◦ 1.1: Software Engineering ◦ 2.1: Software Concepts
Overview Development Life Cycle ◦ 3.2: An Overview of UML
◦ 1.2: Software Engineering (SDLC) ◦ 3.3: Modeling Concepts
Methodologies ◦ 2.2: Sequential Life Cycle ◦ 3.4: UML 2.0
◦ 1.3: Software Engineering Model
Code of Ethics and ◦ 2.3: Iterative Life Cycle
Professional Practices Model
LEGENDS
 READING MATERIALS

Sommerville, I. (2007). Software Engineering 8th Edition. Addison-Wesley

Publishers Limited
Conger, S. (2008). The New Software Engineering. Creative Commons
Attributions 3.0
Sommerville, I. (2011). Software Engineering 9th Edition. Addison-Wesley
Publishers Limited
 TASKS DUE DATE ENDTIM
o (LONG) QUIZ 1 August 31, 2020 E
11:59PM
o CASE STUDY 1 September 1, 2020 5:00PM
o PBLO1 PAPER
September 2, 2020 5:00PM
SUBMISSION
o PRELIMINARY EXAM September 30,
11:59PM
2020
 10 Minutes

Think of an experience were you wished your

transaction(s) ended up quickly and you have all you
need with you in no more than an hour. Should you
have the “power” to create an online
application/software, what would that be?
 WHY do you do what
you do?

PURPOSE
HOW do you do
WHY? what you do?

PROCESS
HOW? WHAT do you do?

WHAT? RESULT
Software is more than just a program code. A
program is an executable code, which serves
some computational purpose.

Software is considered to be a collection of

executable programming code, associated
libraries and documentations.

Software, when made for a specific requirement

is called software product.
Engineering on the other hand, is all about
developing products, using well-defined,
scientific principles and methods.

Software Engineering as an engineering branch associated with the

development of software product using well-defined scientific
principles, methods and procedures. The outcome of software
engineering is an efficient and reliable software product.
 SOFTWARE ENGINEERING
PRINCIPLES
ABSTRACTION DECOMPOSITION

implies that a problem can complex problem is divided

be simplified by omitting into several smaller
irrelevant details problems and then the
smaller problems are solved
one by one
 10 Minutes

Using your “dream” application software, apply the

principles of ABSTRACTION and
DECOMPOSITION and share it among your
classmates
 10 Minutes

Why do you think there’s a need for Software

Engineering?
 NEED FOR SOFTWARE
ENGINEERING
The need of software engineering arises because of higher
rate of change in user requirements and environment on
which the software is working.
 NEED FOR SOFTWARE
ENGINEERING
1. Large software - It is easier to build a wall than to a house or
building, likewise, as the size of software become large engineering
has to step to give it a scientific process.
2. Scalability- If the software process were not based on scientific and
engineering concepts, it would be easier to re-create new software
than to scale an existing one.
 NEED FOR SOFTWARE
ENGINEERING
3. Cost- As hardware industry has shown its skills and huge
manufacturing has lower down the price of computer and
electronic hardware. But the cost of software remains high
if proper process is not adapted.
 NEED FOR SOFTWARE
ENGINEERING
4. Dynamic Nature- The always growing and adapting nature of
software hugely depends upon the environment in which the user
works. If the nature of software is always changing, new
enhancements need to be done in the existing one. This is where
software engineering plays a good role.
5. Quality Management- Better process of software development
provides better and quality software product.
 10 Minutes

In your own opinion, what are the characteristics of a

good software?
 CHARACTERISTICS OF GOOD
SOFTWARE
A software product can be judged by what it offers and how
well it can be used. This software must satisfy on the
following grounds:

OPERATIONAL TRANSITIONA MAINTENANCE

L
CHARACTERISTICS OF GOOD SOFTWARE
OPERATIONAL: This tells us how well software works in
operations. It can be measured on.
1. Budget
2. Usability
3. Efficiency
4. Correctness
5. Functionality
6. Dependability
7. Security
8. Safety
CHARACTERISTICS OF GOOD SOFTWARE
TRANSITIONAL: This aspect is important when the software is
moved from one platform to another.

1. Portability
2. Interoperability
3. Reusability
4. Adaptability
CHARACTERISTICS OF GOOD SOFTWARE
MAINTENANCE: This aspect briefs about how well a software
has the capabilities to maintain itself in the ever-changing
environment:

1. Modularity
2. Maintainability
3. Flexibility
4. Scalability
SOFTWARE ENGINEERING OVERVIEW

1st ONLINE CLASS DISCUSSION