Scribd
Upload
23 views4 pages

CS507

The document describes Assignment No. 02 for CS507. It provides 10 terms/names and asks the student to match each with one of 10 scenarios by writing the number against each scenario in the answer sheet. The scenarios describe situations relating to software development processes like system analysis diagrams, design activities, adopting new technologies, documentation, testing, incremental development, safety critical projects, prototyping, and bad practices.

Uploaded by

Miralkhan003 Miralkhan003
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
23 views4 pages

CS507

The document describes Assignment No. 02 for CS507. It provides 10 terms/names and asks the student to match each with one of 10 scenarios by writing the number against each scenario in the answer sheet. The scenarios describe situations relating to software development processes like system analysis diagrams, design activities, adopting new technologies, documentation, testing, incremental development, safety critical projects, prototyping, and bad practices.

Uploaded by

Miralkhan003 Miralkhan003
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.

02
CS507

Assignment

Question No 1

You are required to choose the most appropriate name/term against each scenario given in the below table. You
are required to write only index numbers (1 to 10) of terms/names against each scenario in the below table.

Terms/Names

1. Polymorphism
2. Inheritance
3. Prototyping
4. Safety critical projects
5. Incremental Model
6. Testing
7. Technical Manual
8. Organizations should adopt latest technology to get more benefits.
9. Bad practices
10. Data Flow Diagram and Entity relationship diagram.
Answer Sheet
Solution:
Scenario/Description Term/Names (The scenario refers to)
A software designer reflects system analysis using
different diagrams. Software designer reveals through 10
these diagrams that he understands the system
completely that is going to develop.

Software developer does not care about any design


activity. The developer should understand the 9
software requirements directly from client and start
development without breaking large projects into
smaller components.

An organization should stick with legacy systems


while latest technology is available in the market. 8
Because organization hesitate to adopt latest
technology because its employees are not willing to
adopt.

A document contains guidance regarding system


troubleshooting, setup information, maintenance, 7
databases details and exceptions details.

A phase in entire software development activity is


very critical and important as it validates the 6
developed software with respect to requirements

A big application is decomposed into meaningful


components and each component is developed just 5
like a small application (in the form of a release)

A software application in which human life risks are


involved. 4

Listen to the customer, build a demo and get it


evaluated from the customer. 3

Grouping together common actions and attributes of


objects into a parent group. For example, extracting 2
common methods and fields from the classes and
grouping into a parent class.
A single interface applicable to a number of different
types. Precisely, A way of allowing similar 1
operations to be grouped together under the same
name. For example, a function can take multiple
types of parameters.

You might also like