2nd slide: Yung purpose ng detailed design is to produce a detailed description of the

proposed system na magsasatisfy sa system requirements identified during systems

analysis and to see if yung proposed system na yun ay in accordance sa conceptual
design. Next slide please.
3rd slide: So, during this phase,
- All system components are specified. Kapag sinabi nating system components,
we are referring to the user views, database tables, processes, and controls.
- At the end of the detailed design phase, yung mga components na yun ay
pinepresent formally sa isang detailed design report.
- Yung mga completed plan ay nagpoproceed sa final phase ng SDLC, which is the
systems implementation. Sa phase na to physically kinoconstruct yung system.
Another presenter will further discuss this topic later. Next slide please.
4th slide: Yung detailed design report na nabanggit ko kanina ay naglalaman ng set of
blueprints that specify input screen formats, output report layouts, database structures,
and process logic. (Add further details para di ka lang nagbasa sa part na to.)
5th slide: After ma-complete yung detailed design, the development team usually
performs a system design walkthrough para ma-ensure na yung design ay free from
conceptual errors that could become programmed into the final system. So, ayun yung
iniiwasan natin kaya nagpeperform ng system design walkthrough, para maiwasan na
maisama yung errors, kung meron man, doon sa final system. There are a lot of
companies na meron talagang formal and structured walkthroughs that are conducted
by a quality assurance group. Next slide please.
6th slide: A quality assurance group is
- An independent group that consists of programmers, analysts, users, and
internal auditors.
- What they do is they simulate the operation of the system para ma-uncover
yung errors, omissions, and ambiguities in the design.
- Majority ng mga system error stem from poor designs rather than
programming mistakes. So, detecting these errors and correcting them in the
design phase are important because it reduces the costly reprogramming later
on.
7th slide:
Under the detailed design phase, we also review the system documentation.
The detailed design report documents and describes the system to this point. This
report includes:
 • Designs for all screen inputs and source documents for the system.
• Designs of all screen outputs, reports, and operational documents.
• Normalized data for database tables, wherein all data elements are specified.
• Database structures and diagrams which includes:
o Entity relationship (ER) diagrams describing the data relations in the system;
o Context diagrams for the overall system;
o Low-level data flow diagrams of specific system processes;
o Structure diagrams for the program modules in the system – including a
pseudocode description of each module.
• An updated data dictionary kung saan nakadescribe yung each data element in
the database.
• Processing logic or the flowcharts.
Nest slide please.
8th slide: Yung quality control group yung nag-eexamine nung mga documents that I
mentioned earlier, and any errors na nadetect nila from those documents are recorded
in a walkthrough report. The quality control group will make a recommendation
depending sa extent ng system errors.
So, their recommendation on the system design will either be:
- Accepted without modification
- Accepted subject to modification of minor errors, or
- Rejected because of material errors
At this point, a decision is made either to return the system for additional design or to
proceed na to the next phase – which is called the system coding and testing.
Assuming na the design goes forward, the documents in the design report constitute the
blueprints that will guide application programmers and the database designers in
constructing the physical system. Next slide please.
9th slide: We now proceed to the 6th phase of the SDLC which is the Application
Programming and Testing. Next slide please.
10th slide: Yung next stage ng SDLC ay yung pagpili ng programming language from
among the various languages available and suitable to the application.
These include procedural languages like COBOL, event-driven languages like Visual
Basic, or object-oriented programming (OOP) languages like Java or C++. In the next
slides, we will go over these program approaches briefly.
Yung mga systems professional yung madedecide on the most suitable programming
language to use based sa in-house standards, architecture, and user needs. Next slide
please.
11th slide: One of the programming languages that system professionals use is the
procedural languages.
- A procedural language requires the programmer to specify the precise order in
which the program logic is executed.
- They are often called third-generation languages (3GLs).
- Examples of 3GLs include COBOL, FORTRAN, C, and PL1. Next slide please.
12th slide: One of the examples of procedural languages that we will focus on is the
COBOL.
- Sa mga business application, particularly sa accounting, COBOL yung pinaka-
dominant language for years.
- It has great capability for performing highly detailed operations on individual
data records and COBOL also handles large files very efficiently.
- However, system professionals consider COBOL as an extremely “wordy”
language which makes programming a time-consuming task.
- Nagsurvive yung COBOL as a viable language dahil marami sa mga “legacy
systems” na naisulat during 1970s and 1980s, na coded in COBOL, are still in
operation today. When we say legacy systems, ito yung mga outdated
computing software and/or hardware that are still in use today.
- Major retrofits and routine maintenance to these systems need to be coded in
COBOL.
- A 2009 survey revealed that upwards of 200 billion lines of COBOL code were in
use within 5 billion new lines being added each year.
13th slide: Moving forward, we have event-driven languages which is another type of
programming language.
- Programs written in event-driven languages are designed to respond to
external actions or “events” that are initiated by the user.
- For example, kapag pinress ni user yung key or may kinlick siya na icon sa
computer screen, the program automatically executes the code associated with
that event.
- This is a fundamental shift from the 3GL era or the procedural language,
because, instead of designing applications that execute sequentially from top
to bottom in accordance with the way the programmer thinks they should
 function, yung user na yung nagdedetermine ng order of code execution under
the programs written in an event-driven language. Next slide please.
14th slide: Meanwhile, we have the Microsoft’s Visual Basic as an example of an event-
driven language.
- The syntax of the language is simple yet powerful.
- Visual Basic is used to create real-time and batch applications that can
manipulate flat files or relational databases.
- It has screen-painting feature that greatly facilitates the creation of
sophisticated graphical user interfaces or GUIs. Next slide please.