Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
9 views2 pages

Software Development Questions

The document discusses various software development methodologies, highlighting the inflexibility of the Waterfall model and the benefits of the Rapid Application Development (RAD) approach, such as faster development cycles and increased user involvement. It also explains the iterative model, the concept of walkthroughs, the necessity of ongoing maintenance categorized into corrective, perfective, and adaptive types, and the differences between alpha and beta testing. Additionally, it defines acceptance testing as a means to demonstrate that the completed program meets customer requirements.

Uploaded by

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

Software Development Questions

The document discusses various software development methodologies, highlighting the inflexibility of the Waterfall model and the benefits of the Rapid Application Development (RAD) approach, such as faster development cycles and increased user involvement. It also explains the iterative model, the concept of walkthroughs, the necessity of ongoing maintenance categorized into corrective, perfective, and adaptive types, and the differences between alpha and beta testing. Additionally, it defines acceptance testing as a means to demonstrate that the completed program meets customer requirements.

Uploaded by

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

Software Development Questions

One significant drawback of using the Waterfall model for software development is its
inflexibility in the face of changing requirements. Once a phase is completed, it's very difficult
and costly to go back and make changes. This can be a major problem in real-world projects
where requirements often evolve during the development process due to new insights, market
shifts, or user feedback.

Benefits:

1. Faster Development Cycles: RAD's emphasis on prototyping, iterative development,


and the use of pre-built components can significantly speed up the development
process. For a new e-commerce platform aiming for a quick market entry, this
accelerated timeline could be a crucial competitive advantage.

2. Increased User Involvement: RAD heavily involves users throughout the development
lifecycle through workshops, focus groups, and continuous feedback on prototypes. For
an e-commerce platform, this close collaboration can lead to a final product that better
meets the needs and expectations of both the business and its potential customers.
Early and frequent feedback on the user interface, shopping cart functionality, and
overall user experience can be invaluable.

Drawback:

3. Due to the time-boxed nature of RAD and the focus on rapid prototyping, there might be
less emphasis on formal design and documentation compared to more traditional
methodologies.

Question: Explain iterative model? 3 marks

incremental development as the program development lifecycle is repeated

working programs are produced for part of the system at every iteration

high customer involvement, as part of the system can be shown to the customer after every
iteration
Question: What is a walkthrough? 2 marks

A walkthrough is a formalised version of a dry run using pre-defined test cases. This is where
another member of the development team independently dry runs the pseudocode, or the
developer takes the team members through the dry run process. This is often done as a
demonstration.

Question: Describe the need for continuing maintenance of a system and the differences
between each type of maintenance.

Programs do not wear out, but they might not work correctly in unforeseen circumstances.
Logic or run-time errors that require correction may occur from time to time, or users may want
to use the program in a different way. Program maintenance can usually be divided into three
categories:

» Corrective maintenance is used to correct any errors that appear during use, for example
trapping a run-time error that had been missed during testing.

» Perfective maintenance is used to improve the performance of a program during its use, for
example improving the speed of response.

» Adaptive maintenance is used to alter a program so it can perform any new tasks required by
the customer, for example working with voice commands as well as keyboard entry.

State two difference between Alpha and beta testing. 2 marks

In alpha testing the completed, or nearly completed, program is tested in-house by the
development team, whereas in beta testing the completed program is tested by a small group of
users before it is generally released.

In the typical software development lifecycle, alpha testing is usually conducted first, followed
by beta testing.

Explain acceptance testing? 2 marks

Acceptance testing is then used for the completed program to prove to the customer that it
works as required in the environment in which it will be used.

You might also like