Software Engineering 1

Karen Cate “KC” Arabit

karen.arabit@iacademy.edu.ph
M02
AGENDA [RECAP]

• Schedule
• About the course
• Course Output
• Class (breakdown)
• Grading Components
• Collaboration Tool
• Course Outline

• Team-up | Brainstorming | Presentation

2
AGENDA

• Final Proposal Presentation

• Team-up | Brainstorming

• Discussion
• Software Engineering
• Software Characteristics
• Software Myth

• Brainstorming | Presentation

3
TEAM UP AND BRAINSTORM

• Should be minimum of 3 and max 5 members

• Prepare at least 2 to 3 topics

• Template:
Team Name:
Members:

TOPIC #1:
Main Idea: - gist/summary of what system you want to develop
Objective: - what is the purpose of the system you want to develop
Scope & Limitation: - what are the things that are included and not included
the range of your system, who will benefit the system?
the limitation of your system, who will not be included?
TOPIC #2:
Main Idea:
Objective:
Scope & Limitation:

4
PRESENTATION OF PROJECT PROPOSAL

EcoSquad 8:00AM - 8:10AM

Generic Team Name #27 8:15AM - 8:25AM

Null 8:30AM - 8:40AM

JJCD 8:45AM - 8:55AM

CatWalkers 9:00AM - 9:10AM

NoName 9:15AM - 9:25AM

5
Software Engineering
Software Engineering

❏ the computer science discipline concerned with developing large applications

❏ covers not only the technical aspects of building software systems

but also management issues, such as directing programming teams, scheduling, and
budgeting

7
Why is it important?

to optimize the use of resources

throughout the lifecycle of software systems

8
Data collection Data analysis Initial design

Documentation Final design

9
Software Characteristics
Scenario

❏ There is a baker who is adept at making cakes. We go and order a cake. Say we want him to
bake a two kilogram chocolate cake with lots of nuts and flakes on it and with a special
message written on it.

❏ The baker conforms to the specifications given by us, “developing” the cake with a lot of
effort. He develops the cake independently. He does not join various pieces of different
cakes already made and present it to you.

11
Scenario

❏ There is a baker who is adept at making cakes. We go and order a cake. Say we want him to
bake a two kilogram chocolate cake with lots of nuts and flakes on it and with a special
message written on it.

❏ The baker conforms to the specifications given by us, “developing” the cake with a lot of
effort. He develops the cake independently. He does not join various pieces of different
cakes already made and present it to you.

12
Software Characteristics

Software ….

❏ is custom built

❏ is engineered, not manufactured

❏ never “wears out”

13
Software Quality

❏ Reliability ❏ Maintainable

❏ Robust ❏ Evolvable

❏ Reusable ❏ Portable

❏ Efficient ❏ Usable (User-friendly)

14
Software Myth
Software Myth #1

MYTH
We have a book of standards following which we are guaranteed to get perfect software.

REALITY
The book of standards is rarely used, incomplete, and most people are not even aware of
its existence.

16
Software Myth #2

MYTH
If we are behind schedule we can add more programmers and catch up.
(Mongolian horde)

REALITY
Software development is not like manufacturing. Adding people to a late software project
makes it later because you will need to educate the new people and it will eat time.

17
Software Myth #3

MYTH
A general statement of objectives is enough to start a software project; details can be filled
in later.

REALITY
Description is the heart of software development. Therefore, a detailed description of the
requirements is essential at the start in order to come up with a correct solution.

18
Software Myth #4

MYTH
Project requirements continuously change which can be easily accommodated because the
software is flexible.

REALITY
Changes in software under development stage are difficult to make, costly, can lead to
bugs, and can make the software error-prone.

19
Software Myth #5

MYTH
Once we write the program and get it working, the job is over.

REALITY
Around 50 – 70% of all the effort in the software will be spent after it is delivered to the
customer for the first time.

20
Software Myth #6

MYTH
The only thing to be delivered successfully is the working program.

REALITY
A working program is only a part of software. Documentation is also needed and is even
the foundation of a successful development.

21
RECAP.

- What is Software Engineering?

- What are the Software Characteristics?
- What are the Software Qualities?
- What are the Software Myths?

22
Team that will report next meeting...

Team Name Topic Date

TEAM CatWalkers SOFTENG1 - M02 Jan 24, 2023

23
Brainstorming
Document : Brainstorm

• Overview of Current State of Technology

• state problem
• state solution

25
TEAM UP AND BRAINSTORM | PRESENT

Generic Team Name #27 AM - AM

Null AM - AM

JJC AM - AM

CatWalkers AM - AM

AM - AM

EcoSquad AM - AM

2
6