Republic of the Philippines

PARTIDO STATE UNIVERSITY

Camarines Sur
PSY-SYL-___-___

COLLEGE OF ARTS AND SCIENCES

Module 10
SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

Name of Student: ________________________ Week No.: 10 - 12

Course Code: ITP5 Name of Faculty: Salvador V. Briones II
Course Title: Methods of Research in Computing

I. INTRODUCTION
Successful IT research conduction requires proper planning and execution. While there are
multiple reasons and aspects behind a successful research completion, choice of best research
software development methodology is one of the most significant phase in software
development.
Software Development Life Cycle (SDLC) is a framework that defines the steps involved
in the development of software at each phase. It covers the detailed plan for building, deploying
and maintaining the software.
SDLC defines the complete cycle of development and all the tasks involved in planning,
creating, testing, and deploying a Software Product.

II. OBJECTIVES

1. Setting the Software Development Life Cycle Model (SDLC) to be use.

III. 2. Writing the Requirements Specification.
3. Writing the Analysis Specification
4. Creating the Conceptual and Logical Design of the system
LESSON

Software Development Life Cycle

The Software Development Life Cycle (SDLC) refers to a methodology with clearly
defined processes for creating high-quality software. In detail, the SDLC methodology focuses
on the following phases of software development:
 Requirement analysis
 Planning
 Software design such as architectural design
 Software development
 Testing
 Deployment

1|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

SDLC is a process that produces software with the highest quality and lowest cost in the
shortest time possible. SDLC provides a well-structured flow of phases that help an organization
to quickly produce high-quality software which is well-tested and ready for production use.
The SDLC involves six phases as explained in the introduction. Popular SDLC models
include the waterfall model, spiral model, and Agile model.

Waterfall Model
In "The Waterfall" approach, the whole process of software development is divided into
separate phases. In this model, typically, the outcome of one phase acts as the input for the next
phase sequentially.

The following illustration is a representation of the different phases of the Waterfall Model.

Figure 4: Waterfall Model

The sequential phases in Waterfall model are −

 Requirement Gathering and analysis − All possible requirements of the system to be
developed are captured in this phase and documented in a requirement specification
document.
 System Design − The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system architecture.
 Implementation − With inputs from the system design, the system is first developed in
small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
 Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is
tested for any faults and failures.

2|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

 Deployment of system − Once the functional and non-functional testing is done; the
product is deployed in the customer environment or released into the market.
 Maintenance − There are some issues which come up in the client environment. To fix
those issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.

All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the defined
set of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model".
In this model, phases do not overlap.

Waterfall Model - Application

Some situations where the use of Waterfall model is most appropriate are −
 Requirements are very well documented, clear and fixed.
 Product definition is stable.
 Technology is understood and is not dynamic.
 There are no ambiguous requirements.
 Ample resources with required expertise are available to support the product.
 The project is short.

Spiral Model
The spiral model combines the idea of iterative development with the systematic,
controlled aspects of the waterfall model. This Spiral model is a combination of iterative
development process model and sequential linear development model i.e. the waterfall model
with a very high emphasis on risk analysis. It allows incremental releases of the product or
incremental refinement through each iteration around the spiral.
The spiral model has four phases. A software project repeatedly passes through these
phases in iterations called Spirals.
 Identification
 Design
 Construct or Build
 Evaluation and Risk Analysis

3|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

Figure 5: Spiral Model

 Identification - This phase starts with gathering the business requirements in the baseline
spiral. In the subsequent spirals as the product matures, identification of system
requirements, subsystem requirements and unit requirements are all done in this phase.
This phase also includes understanding the system requirements by continuous
communication between the customer and the system analyst. At the end of the spiral, the
product is deployed in the identified market.
 Design - The Design phase starts with the conceptual design in the baseline spiral and
involves architectural design, logical design of modules, physical product design and the
final design in the subsequent spirals.
 Construct or Build - The Construct phase refers to production of the actual software
product at every spiral. In the baseline spiral, when the product is just thought of and the
design is being developed a POC (Proof of Concept) is developed in this phase to get
customer feedback. Then in the subsequent spirals with higher clarity on requirements
and design details a working model of the software called build is produced with a
version number. These builds are sent to the customer for feedback.
 Evaluation and Risk Analysis - Risk Analysis includes identifying, estimating and
monitoring the technical feasibility and management risks, such as schedule slippage and
cost overrun. After testing the build, at the end of first iteration, the customer evaluates
the software and provides feedback.

Agile Model
Agile SDLC model is a combination of iterative and incremental process models with
focus on process adaptability and customer satisfaction by rapid delivery of working software
product. Agile methods break the product into small incremental builds. These builds are
provided in iterations. Each iteration typically lasts from about one to three weeks. Every
iteration involves cross functional teams working simultaneously on various areas like −

4|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

 Planning
 Requirements Analysis
 Design
 Coding
 Unit Testing and
 Acceptance Testing.

At the end of the iteration, a working product is displayed to the customer and important
stakeholders.
Agile model believes that every project needs to be handled differently and the existing
methods need to be tailored to best suit the project requirements. In Agile, the tasks are divided
to time boxes (small time frames) to deliver specific features for a release. Iterative approach is
taken and working software build is delivered after each iteration. Each build is incremental in
terms of features; the final build holds all the features required by the customer.

Requirements Specifications
The requirements specification is a part of the BSIT Capstone project manuscript that
describes what the software will do and how it will be expected to perform. It also describes the
functionality the product needs to fulfill all stakeholders’ needs. Basically, the discussion of the
functions of the system is supported by Functional Diagram and Data Flow Diagram or Use case
diagram.

Figure 6: Functional Diagram

5|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

Figure 7: Functional Diagram

Figure 8: Use Case Diagram

Analysis Specifications

6|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

This part discusses the behavioral properties that the system must have. These behavioral
properties should follow the PIECES framework. PIECES framework focuses on the actual work
of doing requirements determination. This model is used to classify identified requirements into
one of six subject areas:
 Performance
 Information
 Economy
 Control
 Efficiency
 Services

 Performance – this area address how the system needs to perform for the user. Issues of
throughput (the amount of work performed over some period of time) and response time
(the average delay between a transaction or user request and the response to that
transaction or user request) are considered. The questions about the needed response time
or throughput required on the network, the quality of print needed, or the need to have a
graphical user interface or a menu or text type of interface should be answered in this
part. It address the question "How does the system need to perform in this environment?"
Its answer can be multifaceted depending on the needs of the user.
 Information and Data - this area provides the basis for the information or data model
that the system needs to maintain. Issues dealing with input data, output data, and stored
data are considered. The question about "What information is required by the users of the
system?" or "What outputs are required?" and "What do these outputs need to look like?"
should be to be addressed and answered in this part. Similarly, questions related to input
data required in order to produce the outputs are also included in this category, for
example, "What input screens are needed?" or "What is the source for the input (where
does it come from)?" and "Can the input enter the system with source data acquisition
equipment such as bar code scanners, laser guns, mouse, and so on?" Ultimately, the data
need to be defined with a high degree of detail.
 Economy - This subject area addresses project development and operational cost
information along with any objectives that may relate to economy or savings associated
with the system. Questions related to, "What is the budget for this project?", "What is a
workable solution to the problem worth to the user of this system?", "What are some
anticipated cost savings associated with this system?" and "Are there current manual
activities that an automated solution to the problem may affect?" should be discussed in
this part.
 Control – this area is closely associated with system security issues as well as the editing
required on the incoming data. For example, questions may be asked related to needed
accounting controls for some processes, or at what levels (workstation, user, screen, file,
data element, and so on) security is needed. Any issue related to controlling the use of the
system, its outputs and inputs, or required controls over the data can be included in this
area.

7|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

 Efficiency - Efficiency is a measure of method correctness. In other words, "Are things

being done right?" Efficiency's impact is usually measured at least at one of three levels
—corporate-wide, department, or individual. Questions related to efficiency are primarily
directed toward the impact that any solution must have on the environment. For example,
"How can the operations in the office be improved by this system?" and "What values
can be added to the environment by using an automated solution to the problem?" are two
questions that should be addressed in this subject area.
 Services - "What does the system need to do in order to solve the problem?" and "What
processes need to be performed?" or "How are the objects expected to perform?" and
"What do the objects need to be able to do?" are typical questions that should be
answered in this subject area. In addition to functional requirements, services may also
include implementation concerns, such as ease of use and needed support for ongoing use
of the system, maintenance of the system, and training and documentation requirements.

Conceptual and logical design of the system

Conceptual design is a framework for establishing the underlying idea behind a design
and a plan for how it will be expressed visually. It is the first step of the multiphase process
involved in creating a new product. Whether it’s a building, software application or gadget,
it’s important to come up with a general concept before proceeding. 
Logical design is a conceptual, abstract design. Researcher do not deal with the physical
implementation details yet; instead, researcher deal only with defining the types of information
that he need.
This part of the IT Capstone manuscript is supported by System Flowchart, Entity-
Relationship Diagram, Data Dictionary and System Prototype.

Conclusion
Research methodology simply refers to the practical “how” of any given piece of
research. More specifically, it’s about how a researcher systematically designs a study to ensure
valid and reliable results that address the research aims and objectives. In other words, the
methodology should justify the design choices, by showing that the chosen methods and
techniques are the best fit for the research aims and objectives, and will provide valid and
reliable results. A good research methodology provides scientifically sound findings.

8|Page
 Republic of the Philippines
PARTIDO STATE UNIVERSITY
Camarines Sur
PSY-SYL-___-___

IV. ASSESSMENT
1. The Methodology presents how a researcher systematically designs a study to ensure valid
and reliable results that address the research aims and objectives. Using the working
research title you conceptualized in module 3, write the Methodology (Chapter IV) of your
research study. Following the suggested format below, present your Chapter IV.
Research Title
Author/s
METHODOLOGY
Requirements Specifications (include a Functional (Write your preparation here.)
Diagram and Data Flow Diagram or Use Case Model)
Analysis (Use the PIECES Framework) (Write your preparation here.)
Design (Flowcharts, ERD, Data Dictionary and Prototype) (Write your preparation here.)
Development and Testing (Write your preparation here.)
Statistical Tools (Write your preparation here.)

Submit your answer in a PDF document titled “ITP5_Assessment7_YOURNAME.pdf” on

our VLE. Thank you and enjoy your online learning experience.

V. REFERENCES
1. Importance of Research Design. Universal Teacher. Retrieved from
https://universalteacher.com/1/importance-of-research-design/
2. Bhosale, U. (2022). How to Choose Best Research Methodology for Your Study. Enago academy.
Retrieved from https://www.enago.com/academy/choose-best-research-methodology/
3. Thattamparambil, N. (2020). How to choose the research methodology best suited for your study. Editage
ensights. Retrieved from https://www.editage.com/insights/how-to-choose-the-research-methodology-best-
suited-for-your-study
4. Ritchey, R. C. (1994). The developmental research: The definition and Scope. Retrieved from
https://eric.ed.gov/?id=ED373753
5. McCombes, S. (2022). Sampling Methods: Types and Techniques Explained. Retrieved from
https://www.scribbr.com/methodology/sampling-methods/
6. Bhandari, P. (2022). Data Collection | A Step-by-Step Guide with Methods and Examples. Retrieved from
https://www.scribbr.com/methodology/data-collection/
7. Nibrad, G. M. (2019). The Importance of Statistical Tools in Research. Retrieved from
https://www.indianjournals.com/ijor.aspx?target=ijor:ijrss&volume=9&issue=11&article=006
8. Tutorials Point. SDLC-Waterfall Model. Retrieved from
https://www.tutorialspoint.com/sdlc/sdlc_waterfall_model.htm

Prepared by: Reviewed by: Approved by:

SALVADOR V. BRIONES II SALVADOR V. BRIONES II HAZEL JEAN C. PESINO

Faculty Chairman, Review Committee Dean

9|Page