Scribd
Upload
43 views

Assignment Software Enginering

The document discusses three software development models: 1) The waterfall model which divides development into sequential phases of requirements analysis, design, implementation, testing, deployment, and maintenance. 2) The incremental model which breaks development into standalone modules that are successively built to produce the final system. 3) The spiral model which provides support for risk handling and allows for additional functionality or changes later with room for customer feedback.

Uploaded by

Mr Muriidi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
43 views

Assignment Software Enginering

The document discusses three software development models: 1) The waterfall model which divides development into sequential phases of requirements analysis, design, implementation, testing, deployment, and maintenance. 2) The incremental model which breaks development into standalone modules that are successively built to produce the final system. 3) The spiral model which provides support for risk handling and allows for additional functionality or changes later with room for customer feedback.

Uploaded by

Mr Muriidi
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Assignment Of Software Engineering

Name: Ahmed Abdulkadir Muriidi


Course: IT ID: 10850 Semister: Five

Software Models
1. Waterfall Model:
The Software Development activity divided into different phases and
each phase consists of series of tasks and has different objectives .
In Waterfall . Development of one phase. starts only when the
previous phase is complete.
 The sequential phase in waterfull model
a. Requirement analysis :also called requirements Engineering is the
process of determining user expectation for anew or modified
product. Must be quantifiable. Is an important aspect of project
management.
b. System design is the process of defining architecture, product
design, and data for a system to satisfy specified requirements,
Could seen as the application of system theory to prodect
development.
c. Implementation:  is the realization of an application, or
execution of a plan, idea, model, design, specification, or
standard.
d. Testing: is a method to check whether the actual software
product matches expected requirements and to ensure that
software product is Defect free
e. Deployment:  refers to the process of running an application
on a server or device.
f. Maintenance: is a part of Software Development Life
Cycle. Its main purpose is to modify and update software
application after delivery to correct faults and to improve
performance.
2. Incremental Model
is a process of software development where requirements divided
into multiple standalone modules of the software development
cycle.
Characteristics of an Incremental module includes

 System development is broken down into many mini development


projects
 Partial systems are successively built to produce a final total
system
 Highest priority requirement is tackled first
 Once the requirement is developed, requirement for that increment
are frozen

Three of Advantages

 The software will be generated quickly during the software life


cycle.
 Errors are easy to be identified.
 A customer can respond to each building.

Three of Disadvantages

 It requires a good planning designing.


 Each iteration phase is rigid and does not overlap each other.
 Rectifying a problem in one unit requires correction in all the units
and consumes a lot of time.

3. Spirtal Model
 is one of the most important Software Development Life Cycle
models, which provides support for Risk Handling.
Two of Advantages

 Additional functionality or changes can be done at a later stage


 There is always a space for customer feedback

Two of Disadvantages

 Risk of not meeting the schedule or budget


 Documentation is more as it has intermediate phases

4. Agile Software Develop Model


It is a software development model that uses scheduled and
repetitive tasks to build software gradually instead of making it all at
once.

You might also like