11. Why do we need documentation?

Project documentation is used to define the way in which a project will be managed and the governance surrounding it. During the life cycle of a typical project, a project manager can produce up to fifty different types of documents to facilitate the planning, tracking and reporting of the project. Documents range from feasibility studies, resource plans, financial plans and project plans, to supplier contracts, post-implementation reviews, change request forms and project status reports.

12. What is Subversion?

Subversion is a free/open-source version control system. That is, Subversion manages files and directories, and the changes made to them, over time. This allows you to recover older versions of your data, or examine the history of how your data changed. In this regard, many people think of a version control system as a sort of “time machine”. Subversion can operate across networks, which allows it to be used by people on different computers.

13. What is dd? Why do we need it?

Detailed design is such a fundamental necessity to manufacturers that it exists at the intersection

of many product development processes. And given this broad influence, as well as the

impact of prevailing industry dynamics such as distributed product development, shortening

product development lifecycles and increased product complexity, companies are feeling

immense pressure to improve their detailed design process. Since many companies operate in a distributed environment, among partners and design teams, and across time-zones and language

barriers, fast, secure information access is essential. It’s an absolute necessity to ensure that everyone is working on the correct version of the data while tracking team decisions and having real-time visibility into the team’s progress.

14. What is Use-Case? Why do we need it?

A way to systematically elicit functional requirements.

A way to organize or group requirements.

A way to START thinking of the interfaces of the system – and also about system design.

• A use case describes

- Sequences of actions (it is a set of actions)

- Initiated by an actor

- That a system performs that

- Yield an observable value

A use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be a human or an external system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular environment and related to a particular goal.

15.(Context: Design patterns) Describe Builder pattern. Give an example

Builder pattern is used to construct a complex object step by step and the final step will return the object. The process of constructing an object should be generic so that it can be used to create different representations of the same object. For example, you can consider construction of a home. Home is the final end product (object) that is to be returned as the output of the construction process. It will have many steps, like basement construction, wall construction and so on roof construction. Finally the whole home object is returned. Here using the same process you can build houses with different properties.