Software Development and Management

This form of transformation in software development process translates the users needs into system requirements and responsibilities.

This common mechanism in the UML have a unique and direct graphical notation that provides a visual representation of the most important aspect of the element.

This method of system evaluation measures how well the delivered system matches the needs of the operational environment.

This semantic rule in UML shows how things properly and consistently relate to one another.

These things in UML are mostly static parts of a model representing elements that are either conceptual or physical.

This prototype is an aid for the incremental development of the ultimate software solution.

This technique in problem solving methodology divides the given problem into a number of self contained independent program segments.

Modularity refers to breaking down of a whole problem into small sub modules which can be handled separately. Each module exhibits different behaviour.

In this approach, there is a direct interaction between the customer and the developer in all phases, until the project's completion.

Feasibility study is of various types such as technical, economical, operational, legal, etc. and all are required if you wish to complete the project successfully.

The last step in linear approach is to support the end user who uses the system. This phase is called maintenance.

In this stage, a designer basically handles all the issues related to database design, front end design, programming, etc.

This is the correct option. Option (4) is correct. 

He is responsible for putting various logics needed to solve a customer's problem.

System analyst performs all of the above mentioned steps in order to find the exact information for the system.