0% found this document useful (0 votes)
74 views3 pages

Software Engineering Paradigms Software Development Life Cycle (SDLC)

The document discusses several software engineering paradigms including the Software Development Life Cycle (SDLC), Waterfall Model, Prototype Model, Iterative Model, Timeboxing Model, and RAD (Rapid Application Development) model. The SDLC describes the stages of a software development program. The Waterfall Model progresses in a linear fashion through requirements, design, implementation, testing, installation, and maintenance. The Prototype Model allows users to evaluate a developer's proposal through prototypes. The Iterative Model develops the software incrementally in parts or versions. Timeboxing allocates fixed time periods for planned activities. The RAD model uses prototyping, iterative development, and rapid delivery through workshops, testing, and reuse.

Uploaded by

Slate List
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
74 views3 pages

Software Engineering Paradigms Software Development Life Cycle (SDLC)

The document discusses several software engineering paradigms including the Software Development Life Cycle (SDLC), Waterfall Model, Prototype Model, Iterative Model, Timeboxing Model, and RAD (Rapid Application Development) model. The SDLC describes the stages of a software development program. The Waterfall Model progresses in a linear fashion through requirements, design, implementation, testing, installation, and maintenance. The Prototype Model allows users to evaluate a developer's proposal through prototypes. The Iterative Model develops the software incrementally in parts or versions. Timeboxing allocates fixed time periods for planned activities. The RAD model uses prototyping, iterative development, and rapid delivery through workshops, testing, and reuse.

Uploaded by

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

SOFTWARE ENGINEERING PARADIGMS

Software Development Life Cycle (SDLC)

- A framework that describes the activities performed at each stage of a software development
program.
- A life style of a typical software development must have.

Waterfall Model

- This one of the oldest model followed in software engineering.


- Progress is seen as flowing steadily downwards.
- Waterfall discourages revisiting and revising any prior phase once it’s complete.

1. Requirements Specifications – defines needed information, function, behavior, performance


and interfaces.
2. Design – data structures, software architecture, interface representations, algorithmic details.
3. Implementation – source code, database, user documentation, testing.
4. Testing and Integration – check if all code modules work together and if the system as a whole
behaves as per the specifications.
5. Installation – deployment of system, user-training.
6. Operation and Maintenance – bug fixes, added functionality (an on-going process).

Proto Type Model (Prototyping)

- Allow users of the software to evaluate developer’s proposal for the design.
- Me personally I should say in this modeling customer is always right.

Benefits

1. Misunderstandings between software developers and users may be identified as the system
functions are demonstrated.
2. Missing user services may be detected.
3. Difficult-to-use or confusing user services may be identified and refined.
4. Software development staff may find incomplete and/or inconsistent requirements as the
prototype is developed.
5. System is available quickly to demonstrate the feasibility and usefulness of the application to
management.

Iterative Model

- Developing part by part until the whole software are produce.


- Produces different version at the end of each iteration model.
- For me there’s a saying that if at first you did not succeed call it V1.0.
- Get-as-you-pay, feedback for improvement.
Timeboxing Model

- Allocates a fixed time period, called a timebox, to each planned activity.


- It is also used for individual use to address personal tasks in a smaller time frame.
- Involves having deliverables and deadlines.
- In short division of labor.

RAD (Rapid Application Development) model

- Based on prototyping and iterative development.


- Gathering customer requirements through workshops or focus groups , early testing of the
prototypes by the customer using iterative concept, reuse of the existing prototypes
(components), continuous integration and rapid delivery.
- Make sure that the prototype develop is reusable.

1. Business Modeling – A complete business analysis is performed to find the vital information for
business, how and when is the information processed and what are the factors driving
successful flow of information.
2. Data Modeling – The information gathered in the Business Modeling phase is reviewed and
analyzed to form sets of data objects vital for the business. The attributes of all data sets is
identified and defined. The relation between these data objects are established and defined in
detail in relevance to the business model.
3. Process Modeling – The data object sets defined in the Data Modeling phase are converted to
establish the business information flow needed to achieve specific business objectives as per the
business model . The process model for any changes or enhancements to the data object sets is
defined in this phase. Process descriptions for adding, deleting, retrieving or modifying a data
object are given.
4. Application Generation – The actual system is built and coding is done by using automation
tools to convert process and data models into actual prototypes.
5. Testing and Turnover – Because prototypes are independently tested during every iteration. In
result it reduces the risk of any major issues.

Some Comparisons

RAD Model Vs Traditional SDLC

- In traditional emphasis on requirement analysis and gathering before the coding starts.
- Puts a pressure on the customer that may cause major revision.
- In RAD focuses on iterative and rapid incremental delivery results in non-conformance with the
actual

You might also like