GIT: Living in the IT Era

SYSTEMS DEVELOPMENT LIFE CYCLE

MODULE 2 - UNIT 04 to UNIT 07

BABALA
DISCLAIMER: This is a RECAP of the VIDEO MATERIALS that you were asked to watch which covers the
primary topics presented in each UNIT of MODULE 2 in our course notes.

Wow, parang mahaba ito…

Make sure na napanood niyo yung mga video links na binigay ko.
I’ll just point out some important matters covered in each video.

Okay.
Here’s the FIRST VIDEO:
UNIT 4: Systems Development Life Cycle - PLANNING
Link: https://www.youtube.com/watch?v=G8ZfiO0hj5A

Question: Where do INFORMATION SYSTEM (IS) PROJECTS come from?

Answer: They come from a BUSINESS NEED

In other words, IS PROJECTS is initiated to optimize BUSINESS OPERATIONS.

Gumagawa ka ng IS PROJECT para matukoy kung paano ma-accomplish yung mga BUSINESS OPERATIONS ng
isang organization.
If the BUSINESS OPERATION is on SALES, then gumawa ka ang INFORMATION SYSTEM to describe how the
organization should perform its SALES OPERATIONS.
Kung kelangan mo ng ENROLMENT SYSTEM, then gawa ka ng INFORMATION SYSTEM to show how STUDENTS
can ENROL in a particular academic institution.
I’m 100% sure na magkakaiba yung ENROLMENT SYSTEM ng other universities compared to SLU kasi each have
their unique INFORMATION SYSTEMS to do ENROLMENT.

Furthermore, the video also mentioned something about BUSINESS PROCESS MANAGEMENT or BPM.
Sabi sa video: BPM is a methodology used by organizations to continuously IMPROVE […] BUSINESS PROCESSES
In other words, the BUSINESS PROCESSES of an ORGANIZATION is MANAGED by initiating an IS PROJECT.

Yung unang ENROLMENT SYSTEM ng SLU was manual – forms were accomplished by hand in triplicate copies
and, everywhere, maghihintay ka sa mahabang pila
By initiating an IS PROJECT to IMPROVE the enrolment process via automation, SLU was able to develop its own
ONLINE ENROLMENT SYSTEM – ngayon computer encoded na yung forms and walang physical na pila.
“IMPROVED” na yung ONLINE ENROLMENT sa lagay na yan?
Well, admittedly, it’s not yet perfect.

But that’s why BUSINESS PROCESS MANAGEMENT exists.

The idea is to continuously IMPROVE […]
Sabi ni Kuya Jordan Barlow sa video, the BENEFIT of BPM includes:
• Enhanced PROCESS AGILITY
Example: Traditional sales are enhanced using online sales via the Internet
• PROCESS ALIGNMENT with industry BEST PRACTICES
Example: Paggamit ng Google Classroom due to its popularity with other schools here and abroad
• Increased PROCESS EFFICIENCIES
Example: Yung pag-gamit ng barcode and barcode readers increases yung efficiency ng cashier sa grocery

Naks! “Kuya”?!? Close kayo?

Kunwari lang.
Anyway, for example, with continuous improvement, we will expect that the ONLINE ENROLMENT SYSTEM of
SLU will only get better in the future.

Similarly, ganun din yung mga applications sa phone mo --- walang katapusang update… it never stops.
Updates are needed to continuously improve the system.

Also, part of the BPM CYCLE includes the following:

• Create ways to IMPROVE STEPS within business processes that ADD VALUE
Example: Yung added value ng CASHLESS TRANSACTIONS is that it makes the PAYMENT PROCESS faster
• Find ways to ELIMINATE or CONSOLIDATE STEPS within business processes that DON’T ADD VALUE
Example: Yung PALABAS ka na sa PUREGOLD, tapos pipila ka pa sa GUARD para i-VALIDATE niya yung resibo
ng KABIBILI mong grocery items. Ewan ko, but I find that VALIDATION STEP irrelevant.
• Create or adjust E-WORKFLOWS to match the IMPROVED PROCESS MAPS
Example: To improve SECURITY, online transactions require AUTHENTICATION via ONE-TIME PIN or
BIOMETRICS

Oh. Gets!
Also, BPM identifies the following BUSINESS NEEDS:
• Business process AUTOMATION --- what steps need to be computerized?
• Business process IMPROVEMENT --- what steps need to be improved?
• Business process RE-ENGINEERING --- what steps need to be overhauled?

And here’s the SECOND SET OF VIDEOS:

UNIT 5: Systems Development Life Cycle – ANALYSIS
Feasibility Analysis
Link: https://www.youtube.com/watch?v=47ssXvPjIuY
 This video answers the question: PWEDE BA? KAKAYANIN BA NATIN?
Is the I.S. PROJECT you are trying to initiate FEASIBLE?
FEASIBILITY ANALYSIS outlines the BENEFITS, COSTS, and RISKS that are associated with the PROJECT

May COST and RISKS?!?

Ganun talaga.
Ang IMPORTANT ay MAHALAGA.
I mean, what’s important is that BENEFIT must outweigh whatever COSTS and RISKS that goes with the PROJECT
Sabi ni kuya, there are THREE COMPONENTS to consider in FEASIBILITY ANALYSIS:
• TECHNICAL --- Can we be build the system? Do we have the technical means?
• ECONOMIC --- Should be build it? Do the BENEFITS outweigh the COST? What’s the ROI?
• ORGANIZATIONAL --- Is the project aligned with the business strategy?

Business strategy?
Here’s an example: SLU is an ACADEMIC ORGANIZATION.

Therefore, lahat ng IS PROJECTS ng SLU should try to focus towards the IMPROVEMENT of the UNIVERSITY as an
ACADEMIC INSTITUTION.
It is NOT within the BUSINESS STRATEGY of SLU to sell LAND or go into the RETAIL INDUSTRY
Pero nasa BUSINESS STRATEGY ng SLU to invest in different HEALTH CARE SYSTEMS kasi meron tayong SLU
HOSPITAL OF THE SACRED HEART
Therefore, ORGANIZATIONAL FEASIBILITY is achieved kung tugma sa BUSINESS STRATEGY ng isang
ORGANIZATION yung IS PROJECT

Ahhh. Ganun pala ‘yon.

Yes. An ORGANIZATION can proceed with its planned IS PROJECT if it is TECHNICALLY, ECONOMICALLY and
ORGANIZATIONALLY FEASIBLE
• TECHNICAL FEASIBILITY means that merong kang TAUHAN [employed or hired] and
tools/equipments/infrastructure to implement the project
• ECONOMIC FEASIBLITY naman kung may sapat na BUDGET yung company to fund the entire project and
siguradong kikita ng PROFIT when the project is implemented
• ORGANIZATIONAL FEASIBILITY means that the project is aligned with the type of business that the
company engages in

Copy that!
Now we discuss the next video.
This video is still under UNIT 5 - ANALYSIS:

Development Techniques
Link: https://www.youtube.com/watch?v=6-GbY4Asgf8

Sabi sa video: METHODOLOGY is a FORMALIZED APPROACH to IMPLEMENTING the SYSTEMS DEVELOPMENT

LIFE CYCLE (SDLC)
And SDLC refers to the process of developing the INFORMATION SYSTEM which follows these five PHASES:

PLANNING → ANALYSIS → DESIGN → IMPLEMENTATION → MAINTENANCE

Video mentioned something about SYSTEMS DEVELOPMENT METHODOLOGIES.

The “methodology” refers to the sequence of how each PHASE in the SDLC will be performed.

These are the three SYSTEMS DEVELOPMENT METHODOLOGIES mentioned:

• WATERFALL DEVELOPMENT --- moves from PHASE-to-PHASE; complete a project phase before moving to
the next phase
STRENGTHS:
▪ System requirements identified long before construction begins
▪ Requirements are “frozen” as projects proceeds – no moving requirements allowed
WEAKNESS:
▪ Must wait a long time before there is “visible” evidence of the new system
▪ Takes a long time to complete from start to finish

• RAPID APPLICATION DEVELOPMENT (RAD) --- get some portion of the system developed quickly and in the
user’s hands
RAD Tools
▪ CASE (Computer Aided Software Engineering) Tools – used to automate some of the software
development process
▪ JAD (Joint Application Development) Sessions – session where USERS, ANALYSTS and DESIGNERS
come together in one MEETING to DISCUSS THE REQUIREMENTS and DESIGN THE SYSTEM

THREE RAD APPROACHES

o ITERATIVE DEVELOPMENT – a series of versions developed sequentially
STRENGTHS:
▪ Users get a system to use quickly
▪ Users identify additional needs for later versions based on real experiences with the current version
WEAKNESSES:
▪ Users faced with using an incomplete system for a time
▪ Uses must be patient and wait for the fully-functional system to be ready
o SYSTEM PROTOTYPING – create a prototype (model of system) and “grow” it into the final system
STRENGTHS:
▪ Users get to work with the prototype very quickly
▪ Feedback cycles let users identify changes and refine real requirements
 WEAKNESSES:
▪ Superficial analysis may cause problems
▪ Initial design decisions may be poor
▪ Overlooked features may be hard to add later
o THROW-AWAY PROTOTYPING – prototyping alternative designs in an experimental way and are
discarded before the actual system is built
STRENGTHS:
▪ Uncertainty is minimized
▪ Important issues are understood before building the system
WEAKNESSES:
▪ May take longer because the actual system isn’t being developed during the iterative process

• AGILE DEVELOPMENT --- several iterations of full “mini-SDLCs” over time until the system is completed
STRENGTHS:
o Fast delivery results
o Works well in projects with undefined or changing requirements
WEAKNESS:
o Requires discipline
o Significant user involvement is essential
o Initial high learning curve
o Works best in smaller projects
o More coordination required because analysts/designers/users all work together in every iteration

Anu daw? Don’t ENGLISH me. I’M PANIC!

Ikaw naman. Ganito lang yun.
Kunwari, you plan to construct a HOUSE.

THREE DEVELOPMENT METHODOLOGIES

• WATERFALL DEVELOPMENT
Construct the house from start to finish before it can be used. The end!
Pwede ka lang tumira sa bahay kung fully constructed na siya.

• RAPID APPLICATION DEVELOPMENT

o Iterative Approach
Initially construct the house.
Tawagin yung may-ari at patirahin na sa bahay.
Get feed back from the owner.
I-renovate yung part ng bahay na kelangang ayusin.
Get feedback ulit and mag-renovate hangga’t kelangan.

o System Prototyping
Gumawa ka ng life-size na bahay-bahayan na gawa sa plywood
Tawagin yung may-ari at patirahin na sa bahay.
Get feed back from the owner.
Yung parts ng bahay na okay na, palitan ng matibay na semento
Yung parts na kailangan ayusin, i-renovate pero gamit pa rin ay plywood
Get feedback ulit and repeat – sementuhin yung okay na parts at i-renovate yung kailangang i-renovate
(gamit pa rin ng plywood)
NOTE: In the ITERATIVE APPROACH, yung bahay ay gawa na kaagad sa matibay na semento
 o Throw-Away Prototyping
Gawa ka ng laruang bahay-bahayan na gawa sa cheap cardboard
Ipakita yung laruang bahay-bahayan sa may-ari
Get feedback from the owner
Ayusin yung laruang bahay-bahayan hangga’t gusto ng may-ari
Kung kelangan ng full-renovation, okay lang na itapon yung buong cardboard prototype (kasi cheap lang
naman) and gawa ka na lang ng panibagong laruang bahay-bahayan
Kung okay na yung prototype – saka mo palang gawin yung full size na bahay na gawa sa semento.
After construction, patirahin yung may-ari sa bahay

• AGILE DEVELOPMENT
Tapusin mo muna yung banyo
Ipagamit agad sa owner, mag renovate kung hindi maayos ang pagkakagawa
Kung OK na yung banyo, construct the next part of the house and ipagamit sa owner
Repeat the entire process hanggang matapos yung buong bahay

Nice. Got it!

Oh di ba? Simple lang!
Next video:
Requirement Elicitation Techniques
Link: https://www.youtube.com/watch?v=NxUDV0ShSvQ

FIVE REQUIREMENTS ELICITATION TECHNIQUES

• Interview
• Questionnaire
• Joint Application Development (JAD)
• Observation
• Document Analysis
Self explanatory. Haha!

Yup. I understood that part of the video series.

JAD is included in the list kasi it’s a MEETING between the USERS and the SYSTEM ANALYSTS + DESIGNERS
Magkakaroon sila ng open forum to discuss how the system should be built.
Understood.
Nice! Next video:
UNIT 6: Systems Development Life Cycle - DATA FLOW DIAGRAM (DFD)

Elements of a DFD + DFD Hierarchy

Link #1: https://www.youtube.com/watch?v=StwBh8iQkEs
Link #2: https://www.youtube.com/watch?v=SNPqm59WPkk

Again, KEY DEFINITIONS from the video:

• PROCESS MODEL – a formal way of representing how a business process operates
• LOGICAL PROCESS MODEL – describes processes without suggesting how they are conducted
• PHYSICAL PROCESS MODEL – include process implementation information
• DATA FLOW DIAGRAMMING – a technique for creating process models
 Oh! Questions?

Hala? Of course – anu yan?

That’s your DFD or DATA FLOW DIAGRAM
It illustrates the FLOW of DATA within an INFORMATION SYSTEM.
 See the CONTEXT DIAGRAM?
It’s an OVERVIEW of the entire SYSTEM --- it shows the data that flows between the SYSTEM and the EXTERNAL
ENTITIES it interacts with

We can see that the system is named SAMPLE INFORMATION SYSTEM.

This system interacts with three (3) EXTERNAL ENTITIES – Entity A, Entity B and Entity C
The system accepts the data V and X as input from the entities A and B respectively.
Tapos, this system outputs the data W, Y and Z to entities A, B, and C respectively.

And then we have the LEVEL 0 DIAGRAM.

The LEVEL 0 DIAGRAM shows the MAIN PROCESSES that occur in the SAMPLE INFORMATION SYSTEM.
For example, see PROCESS 1.
Makikita natin sa PROCESS 1 -- named PROCESS AA -- that it processes the data V from ENTITY A to produce two
new data A and B …
… where data A is kept in a DATA STORE -- named DATA STORE P -- and the data B is passed to the PROCESS 2 --
named PROCESS BB – for further processing.

Here’s another DFD that I Googled from the Internet.

Saan?

Saan?

Saan po?
Hello!?
 Here… hindi na kasi yung dalawang diagram sa previous page

CONTEXT LEVEL DIAGRAM

LEVEL 0 DIAGRAM

We can see from the CONTEXT LEVEL DIAGRAM that the INFORMATION SYSTEM is a FOOD ORDERING SYSTEM
And the LEVEL 0 DIAGRAM, shows this FOOD ORDERING SYSTEM involves FOUR MAIN PROCESSES namely:
• Process 1.0: Receive and Transform Customer Food Order
• Process 2.0: Update Goods Sold File
• Process 3.0: Update Inventory File
• Process 4.0: Produce Management Reports

Saan dyan yun NILUTO ng CHEF yung order ng CUSTOMER?

Ba’t wala dyan yung BINIGAY sa CUSTOMER yung inorder niya?
Is that DINE-IN? TAKE-OUT? DELIVERY?
 Ewan ko. Na-download ko lang yan sa INTERNET.
But that’s a very good observation.
You can ANALYZE an INFORMATION SYSTEM just by looking at the DFD of the system.
I would agree, that there should at least be a “PROCESS 5” that shows that food ordered is being “SERVED” from
the KITCHEN to the CUSTOMER

The point is from this DFD you can actually describe how this establishment processes orders from the customer.
And with proper ANALYSIS you can identify kung ano pa yung pwedeng ma-IMPROVE sa system na yan.

Ano yung pinagkaiba nung dalawang DATA STORES labeled D1 and D2?
Those DATA STORES?
Here’s my guess …
• The GOODS SOLD FILE contains a list of “menu” item that was ordered by the customer
Example: 1-piece Chicken McDo Value Meal
• The INVENTORY FILE contains a list of “inventory” item that came with the “menu” item
Example: 1 PIECE CHICKEN + 200 GRAMS FRENCH FRIES + 1 REGULAR COKE + 1 RICE assuming na ito
yung composition ng isang 1-piece Chicken McDo Value Meal.

Hindi indicated, but the DATA STORE may be a LOG BOOK kung saan nakasulat yung data or a COMPUTER HARD
DISK kung saan naka-save yung data na ‘yon.

Okay. Medyo nakuha ko yung general concept.

I somewhat understand the idea behind DFDs.
Very good.

And finally, the last video:

UNIT 7: Systems Development Life Cycle - Systems Development Strategies
Link: https://www.youtube.com/watch?v=dOy-GLXCdwg

We’ll just keep this short.

There are THREE (3) WAYS to acquire the system.
• CUSTOM DEVELOPMENT – build the system from scratch in-house
ADVANTAGES:
o We get exactly what we want
o New system built consistently with existing technology and standards
o Allows team flexibility and creativity
o Unique solutions created for strategic advantage
 DISADVANTAGE:
o Requires significant time and effort
o May add to existing backlogs
o Often costs more
o Often takes more calendar time
o Risk of project failure

• PURCHASE SOFTWARE PACKAGE (and possibly customize it) – installing something on your computer or
subscribe to the software as a service (SAAS)
ADVANTAGE:
o No need to “reinvent the wheel” for common business needs
o Tested, proven product
o Cost savings
o Time savings
o Utilize vendors’ expertise
o Some customization may be possible
DISADVANTAGE:
o Rarely a perfect fit
o Organizational processes must adapt to software
o Reliance on vendor for maintenance and future enhancements
o Won’t develop in-house functional and technical skills
o Unique needs may go unmet
o May require system integration

• OUTSOURCE DEVELOPMENT TO THIRD PARTY – build or purchase the system for the organization
ADVANTAGE:
o Hire expertise we don’t have
o May save time and money
o Lower risk
o Some consultants specialize in systems integration
DISADVANTAGE:
o No opportunity to build in-house expertise
o Reliance on vendor
o Future options limited
o Security – potential loss of confidential information
o Performance based on contract terms
Ayos?

Ayos! Understood!
Here’s a very relatable analogy.

PROBLEM: Gusto mong kumain ng ADOBO!

SOLUTION:
• CUSTOM DEVELOPMENT
Ikaw mismo magluto ng ADOBO according to your taste
• PURCHASE […]
Maraming nagbebenta ng adobo sa mga carinderia, piliin mo na lang kung saan yung pinakamarasap
• OUTSOURCE […]
Magpaluto ka kay mama [kasi masmarasap yung timpla ng kanyang adobo compared sa ’yo]

Ayy oo nga no? I can see the ADVANDATES and DISADVANTAGES in that analogy!