Follow Us on FaceBook
CS507 ASSIGNMETN # 2
solution
QUESTION NO 1
Answer
QUESTION NO 2
Answer:
We know
that Prototyping is the process of building a model of a system. In case of
information system, prototypes are employed to help the system designers build
an information system.
Prototypes have so many forms including many lower sketches to complicated designs. It leads to highly tech operational system CASE (Computer Aided Software Engineering). The organizations many types prototypes tools. Prototyping used in engineering as followings:-
a. Prototyping can reduce the development timings to a great extent.
b. It also minimise the development cost.
c. It needs the user requirement as well.
d. Important feedback can be obtained.
e. Best user satisfaction in this system.
f. It leads to future requirements as well.
Prototypes have so many forms including many lower sketches to complicated designs. It leads to highly tech operational system CASE (Computer Aided Software Engineering). The organizations many types prototypes tools. Prototyping used in engineering as followings:-
a. Prototyping can reduce the development timings to a great extent.
b. It also minimise the development cost.
c. It needs the user requirement as well.
d. Important feedback can be obtained.
e. Best user satisfaction in this system.
f. It leads to future requirements as well.
QUESTION NO 3
Answer:
part A
(a) What is meant by non-rigidity of the software development model?
• This model is straightforward and simple to know and use.
• It is simple to manage owing to the rigidity of the model – every section has specific deliverable and a review method.
• In this model phases ar processed and completed one at a time. Phases don't overlap.
• Waterfall model works well for smaller comes wherever needs ar fine understood.
Part B
1. the body of water Model was 1st method Model to be
introduced. it's additionally mentioned as a linear-sequential life cycle
model. it's terribly straightforward to grasp and use. during a body of water
model, every part should be completed before future part will begin and there's
no overlapping within the phases.
2. body of water model is that the earliest SDLC approach that was used for code development .
3. The body of water Model illustrates the code development method during a linear successive flow; thence it's additionally mentioned as a linear-sequential life cycle model. this suggests that any introduce the event method begins provided that the previous part is complete. In body of water model phases don't overlap.
ii. progressive Model
The progressive build model may be a methodology of code development wherever the model is intended, enforced and tested incrementally (a very little a lot of is adscititious every time) till the merchandise is finished. It involves each development and maintenance. the merchandise is outlined as finished once it satisfies all of its needs. This model combines the weather of the body of water model with the unvaried philosophy of prototyping.
The product is rotten into variety of elements, every of that area unit designed and engineered on an individual basis (termed as builds). every element is delivered to the consumer once it's complete. this enables partial utilization of product and avoids an extended development time. It additionally creates an outsized initial capital outlay with the following long wait avoided. This model of development additionally helps ease the traumatic result of introducing utterly new system all promptly.
iii. Spiral Model
The spiral model starts with Associate in Nursing initial withstand a customary body of water life cycle, employing a set of the overall needs to develop a sturdy epitome.
After Associate in Nursing analysis amount, the cycle is initiated once more, adding new practicality and emotional future epitome. This method continues, with the epitome changing into larger and bigger with every iteration. Hence, the “Spiral Model.”
The theory is that the set of needs is hierarchic in nature, with further practicality building on the primary efforts. this is often a sound apply for systems wherever the whole downside is well outlined from the beginning, like modeling and simulating code.
Business-oriented information comes don't fancy this advantage. Most of the functions during a information resolution area unit basically freelance of 1 another, though they'll build use of common information.
2. body of water model is that the earliest SDLC approach that was used for code development .
3. The body of water Model illustrates the code development method during a linear successive flow; thence it's additionally mentioned as a linear-sequential life cycle model. this suggests that any introduce the event method begins provided that the previous part is complete. In body of water model phases don't overlap.
ii. progressive Model
The progressive build model may be a methodology of code development wherever the model is intended, enforced and tested incrementally (a very little a lot of is adscititious every time) till the merchandise is finished. It involves each development and maintenance. the merchandise is outlined as finished once it satisfies all of its needs. This model combines the weather of the body of water model with the unvaried philosophy of prototyping.
The product is rotten into variety of elements, every of that area unit designed and engineered on an individual basis (termed as builds). every element is delivered to the consumer once it's complete. this enables partial utilization of product and avoids an extended development time. It additionally creates an outsized initial capital outlay with the following long wait avoided. This model of development additionally helps ease the traumatic result of introducing utterly new system all promptly.
iii. Spiral Model
The spiral model starts with Associate in Nursing initial withstand a customary body of water life cycle, employing a set of the overall needs to develop a sturdy epitome.
After Associate in Nursing analysis amount, the cycle is initiated once more, adding new practicality and emotional future epitome. This method continues, with the epitome changing into larger and bigger with every iteration. Hence, the “Spiral Model.”
The theory is that the set of needs is hierarchic in nature, with further practicality building on the primary efforts. this is often a sound apply for systems wherever the whole downside is well outlined from the beginning, like modeling and simulating code.
Business-oriented information comes don't fancy this advantage. Most of the functions during a information resolution area unit basically freelance of 1 another, though they'll build use of common information.
Comments
Post a Comment