About Software Lifecycle

SDLC - Systems development life cycle

It is a framework used by professional software developers to make good quality software on a time-bound and client-oriented context. 
ISO/IEC 12207 defines systems lifecycle processes.

If you are not a reader, you may be interested in this video:



It includes 6 basic steps to develop, maintain, replace or alter software:
  • Planning
  • Defining
  • Designing
  • Building
  • Testing
  • Deploying

There are also more detailed steps for the SDLC:

  • Communication
  • Requireent Gathering
  • Feasibility Study
  • System Analysis
  • Software Design
  • Coding
  • Testing
  • Integration
  • Implementation
  • Operations and Maintenance 
  • Disposition
I will summarize in more detail the steps of the SDLC that is divided in 6 parts:
  1. Planning and Requirement Analysis: It is done between the developing company's experts and the client to determine the specifications and feasibility of a project, there are also risks that have to be taken into account. This includes not only the software aspect, also economic and operational aspects are reviewed.
  2. Defining Requirements: Doing a Software Requirement Specification (SRS) document that includes the clearly defined features, it must be approved by the customer.
  3. Design: The architects define clearly the solution to the problem, based on the SRS, in the Design Document Specification (DDS), it is reviewed by important stakeholders that take into account risks, robustness, modularity, and budget and time constraints.
  4. Building: Programmers code the application according to the DSS, using the tools that they are provided and appropriate high-level languages.
  5. Testing: The software is tested and corrected in order for it to comply to the specifications described in the (SRS).
  6. Deploying: The software is released to its meant environment, sometimes this stage includes field testing to correct and further improve the experience.
These are basic steps, but there's much more to software development than that, there are specific strategies to follow the steps that are standardized. I will post about them later this week.

Hope you learned something from this :)














About Software Lifecycle

SDLC - Systems development life cycle

It is a framework used by professional software developers to make good quality software on a time-bound and client-oriented context. 
ISO/IEC 12207 defines systems lifecycle processes.

If you are not a reader, you may be interested in this video:



It includes 6 basic steps to develop, maintain, replace or alter software:
  • Planning
  • Defining
  • Designing
  • Building
  • Testing
  • Deploying

There are also more detailed steps for the SDLC:

  • Communication
  • Requireent Gathering
  • Feasibility Study
  • System Analysis
  • Software Design
  • Coding
  • Testing
  • Integration
  • Implementation
  • Operations and Maintenance 
  • Disposition
I will summarize in more detail the steps of the SDLC that is divided in 6 parts:
  1. Planning and Requirement Analysis: It is done between the developing company's experts and the client to determine the specifications and feasibility of a project, there are also risks that have to be taken into account. This includes not only the software aspect, also economic and operational aspects are reviewed.
  2. Defining Requirements: Doing a Software Requirement Specification (SRS) document that includes the clearly defined features, it must be approved by the customer.
  3. Design: The architects define clearly the solution to the problem, based on the SRS, in the Design Document Specification (DDS), it is reviewed by important stakeholders that take into account risks, robustness, modularity, and budget and time constraints.
  4. Building: Programmers code the application according to the DSS, using the tools that they are provided and appropriate high-level languages.
  5. Testing: The software is tested and corrected in order for it to comply to the specifications described in the (SRS).
  6. Deploying: The software is released to its meant environment, sometimes this stage includes field testing to correct and further improve the experience.
These are basic steps, but there's much more to software development than that, there are specific strategies to follow the steps that are standardized. I will post about them later this week.

Hope you learned something from this :)














Software Engineering discussion


Participants, left to right:
Enrique, José Manuel, Frida, José Carlos
We discussed the topic on question and the following things surfaced:

  • It is a engineering branch that is dedicated to make software.
  • It includes developing, testing and maintaining software.
  • Software engineering is involved in design so it could be considered an art, in this aspect, the limit is the software engineer's imagination.
  • It is an applied science, and thus includes a methodology that can be followed in order to be successful.
  • Methodology is not all, there is also the developer's criteria that enables a project to be successful.
  • It can be used for a wide variety of things, from low-level stuff like compilers to big user software.
  • The applications are almost everything, some examples are: medicine, administration, construction, education, governments, etc.


We concluded that software engineering can be basically a methodology, but there a lot of possibilities that can expand the engineer's potential, it is one of the most flexible areas in engineering because it creates solutions to everyday problems, from the most simple to the craziest applications.

Software Engineering discussion


Participants, left to right:
Enrique, José Manuel, Frida, José Carlos
We discussed the topic on question and the following things surfaced:

  • It is a engineering branch that is dedicated to make software.
  • It includes developing, testing and maintaining software.
  • Software engineering is involved in design so it could be considered an art, in this aspect, the limit is the software engineer's imagination.
  • It is an applied science, and thus includes a methodology that can be followed in order to be successful.
  • Methodology is not all, there is also the developer's criteria that enables a project to be successful.
  • It can be used for a wide variety of things, from low-level stuff like compilers to big user software.
  • The applications are almost everything, some examples are: medicine, administration, construction, education, governments, etc.


We concluded that software engineering can be basically a methodology, but there a lot of possibilities that can expand the engineer's potential, it is one of the most flexible areas in engineering because it creates solutions to everyday problems, from the most simple to the craziest applications.