Scribd
Upload
80 views4 pages

Assignment No 1: Linear Sequential Model

The document compares different process models for software engineering. It provides details on the Linear Sequential, Incremental, Spiral, RAD, Prototyping, WINWIN Spiral, Concurrent Development, and Component Based Development models. Each model is described based on 10 criteria such as administration control, team size, development objective, availability, time frame, reusability, and framework type.

Uploaded by

Meena Jadoon
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
80 views4 pages

Assignment No 1: Linear Sequential Model

The document compares different process models for software engineering. It provides details on the Linear Sequential, Incremental, Spiral, RAD, Prototyping, WINWIN Spiral, Concurrent Development, and Component Based Development models. Each model is described based on 10 criteria such as administration control, team size, development objective, availability, time frame, reusability, and framework type.

Uploaded by

Meena Jadoon
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/ 4

ASSIGNMENT NO 1

NAME ZARMINA NAZIR


ROLL NO 166
SUBJECT S.W ENGINEERING
SEMESTER 5TH
DEPARTMENT COMPUTER SCIENCE
Write differences and similarities among process models.

Linear sequential model:


1. It has very low control over administration.
2. It has a large team.
3. Its objective is high assurance.
4. Its availability is till at the end of the cycle.
5. Its time frame is very long.
6. Its reusability is least possible.
7. It is least maintainable.
8. Does not have over lapping phases.
9. Testing is done after completion of code.
10. Its framework type is linear.

Incremental model:
1. Do have proper control over administration.
2. Does not have a large team.
3. Its objective is rapid development.
4. Its availability is till the end of every iteration.
5. Its time frame is long.
6. It is reusable to some extent.
7. It is maintainable.
8. It does have overlapping phases.(parallel development)
9. After every iteration.
10. Its framework type is linear + iterative.
Spiral model:
1. Do have proper control over administration.
2. Has a large team.
3. Its objective is high assurance.
4. Its availability is till the end of every iteration.
5. Its time frame is long.
6. It is reusable to some extent.
7. More maintainable than incremental.
8. Does not have over lapping phases.
9. Testing is done at the end of the engineering phase.
10. Its framework type is linear + iterative.

Rad model:
1. Do have proper control over administration.
2. Has a very small team.
3. Its objective is rapid development.
4. Its availability is till at the end of the cycle.
5. Its time frame is short.
6. It is reusable.
7. Easily maintainable.
8. Does have over lapping phases.
9. Testing is done after completion of code.
10. Its framework type is linear.

Prototyping model:
1. Clients have a preview of the system early.
2. Can be modified after it is built.
3. Complexity of an error is low.
4. Enables developers detect deficiency early.
5. It is divided into phases with different objectives.
6. High development and maintenance cost as compared to waterfall model.
7. Life span is short.
8. Used for the development of the user interface.
9. Evolutionary approach is used instead of linear.
10. Constant interaction with clients is required.

WINWIN spiral model:


1. Provides Framework activity used for costumer communication.
2. It is a set of negotiation activities.
3. Identification of system’s key “stakeholders” is defined.
4. Determination of stakeholders’ “win condition” is defined.
5. Negotiation of the stakeholders’ win condition is done.
6. Introduces three process milestones, called anchor points.
7. First anchor point defines a set of objectives.
8. Second defines objectives for software architecture.
9. The third represents a set of objectives regarding installation/distribution of software.
10. It is used to Elaborate the definition of the product and process.
11. It is the expansion of the spiral model.

Concurrent development model:


1. Multiple phases are performed simultaneously in this model.
2. In this model the communication activity has completed in the first iteration and exits in
the awaiting changes state.
3. The modeling activity completed its initial communication and then go to the
underdevelopment state.
4. If costumers specifies a change the activity moves to awaiting change state.
5. The concurrent process model activity moves from one state to another state.
6. This model is applicable to all types of software development processes
7. It is easy for understanding and use.
8. It gives immediate feedback from testing.
9. It provides an accurate picture of the current state of a project.
10. It requires to remember the status of the different activities.

Component based development model:


1. Procedure that accentuates the design and development of computer-based systems with the
help of reusable software components.
2. The main focus is software system composing.
3. It chooses ideal off-the-shelf components and then assembling them using a well-defined
software architecture.
4. It delivers better quality and output.
5. It integrates the related parts and reuse them collectively.
6. Consist of non-conventional development routines.
7. It includes component evaluation, component retrieval, etc.
8. It Enhances the software quality: The component quality is the key factor behind the
enhancement of software quality.
9. Finding defects is hard.
10. It reduces development time.

You might also like