Scribd
Upload
15 views13 pages

Lecture 7 CS101

Uploaded by

moquddasjamshed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
15 views13 pages

Lecture 7 CS101

Uploaded by

moquddasjamshed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Course Code: CS 101

Course Title: IT For Managers

Lecture / Week No. 17 and 18 Week 9th

Department of Science and Technology


Contents

1. Software engineering Definition


2. Software engineering process
3. SDLC definition
4. SDLC working
5. SDLC stages
• References No 1 Topic: What is Engineering

 Engineering isthe application of scientific


and practical knowledge in order to invent,
design, build, maintain, and improve
systems, processes,etc.
• References No 1 Topic: What is software

 The software is collection of Integrated programs

 Software consists of carefully-organized instructions and


code written by programmers in any of various special
computer languages.

 Computer programs and associated documentation such


as requirements, design models and user manuals.
• References No 1 Topic: What is software engineering

 Software engineering is an engineering discipline that is


concerned with all aspects of software production.

 According to IEEE's definition software engineering can be


defined as the application of a systematic, disciplined,
quantifiable approach to the development, operation, and
maintenance of software, and the study of these
approaches; that is, the application of engineering to
software.
• References No 1 Topic: What is a software process

 A framework that describes the activities performed at each stage of a


software development project.
 A set of activities whose goal is the development or evolution of
software.
 Generic activities in all software processes are:
 Specification - what the system should do and its development
constraints
 Development - production of the software system
 Validation - checking that the software is what the customer
wants
 Evolution - changing the software in response to changing
demands.
• References No 1 Topic: SDLC

Definition
SDLC or the Software Development Life Cycle 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
• References No 1 Topic: How SDLC worls
How SDLC Works
SDLC works by lowering the cost of software development while simultaneously
improving quality and shortening production time. SDLC achieves these
apparently divergent goals by following a plan that removes the typical pitfalls of
software development projects. That plan starts by evaluating existing systems for
deficiencies.
Next, it defines the requirements of the new system. It then creates the software
through the stages of analysis, planning, design, development, testing, and
deployment. By anticipating costly mistakes like failing to ask the end-user or client
for feedback, SLDC can eliminate redundant rework and after-the-fact fixes
It’s also important to know that there is a strong focus on the testing phase. As
the SDLC is a repetitive methodology, you have to ensure code quality at
every cycle. Many organizations tend to spend few efforts on testing while a
stronger focus on testing can save them a lot of rework, time, and money. Be
smart and write the right types of tests
• References No 1 Topic: Phases Of SDLC
• References No 1 Topic: Stages of SDLC

Stages of SDLC
1. Identify the Current Problems
“What are the current problems?” This stage of the SDLC means getting input
from all stakeholders, including customers, salespeople, industry experts, and
programmers. Learn the strengths and weaknesses of the current system with
improvement as the goal.

2. Plan
“What do we want?” In this stage of the SDLC, the team determines the
cost and resources required for implementing the analyzed requirements. It
also details the risks involved and provides sub-plans for softening those
risks
• References No 1 Topic: Stages of SDLC

3. Design
“How will we get what we want?” This phase of the SDLC starts by turning the
software specifications into a design plan called the Design Specification. All
stakeholders then review this plan and offer feedback and suggestions. It’s
crucial to have a plan for collecting and incorporating stakeholder input into this
document. Failure at this stage will almost certainly result in cost overruns at
best and the total collapse of the project at worst
4. Build
“Let’s create what we want.”
At this stage, the actual development starts. It’s important that every developer sticks
to the agreed blueprint. Also, make sure you have proper guidelines in place about
the code style and practices.
For example, define a nomenclature for files or define a variable naming style such
as camelCase. This will help your team to produce organized and consistent code
that is easier to understand but also to test during the next phase.
• References No 1 Topic: Stages of SDLC
5. Code Test
“Did we get what we want?” In this stage, we test for defects and
deficiencies. We fix those issues until the product meets the original
specifications.
In short, we want to verify if the code meets the defined requirements.

6. Software Deployment
“Let’s start using what we got.”
At this stage, the goal is to deploy the software to the production environment
so users can start using the product. However, many organizations choose to
move the product through different deployment environments such as a testing
or staging environment.
This allows any stakeholders to safely play with the product before releasing it
to the market. Besides, this allows any final mistakes to be caught before
releasing the product.
References / Resources

• All material is taken from text/reference books mentioned in course outline


Introduction to Computers By Perter Norton

You might also like