Software Architecture Interview Questions By Shivprasad Koirala Sham Sheikh Hard This PDF has sample questions which is extracted from my two books. Software Architecture Interview Questions - Ebook download as PDF File .pdf), Text File .txt) + SQL_Server_Interview_Questions - By Shivprasad Koirala. Software Architecture Interview Questions - Download as PDF File .pdf), Text File .txt) or + SQL_Server_Interview_Questions - By Shivprasad Koirala.
|Language:||English, Spanish, French|
|Genre:||Academic & Education|
|Distribution:||Free* [*Sign up for free]|
Software architecture interview questions shivprasad koirala pdf. Click here to get file. Buy software architecture interview questions book online at low prices in. Software Architecture: Interview Questions [Shivprasad Koirala] on rattribillvordo.cf *FREE* shipping on qualifying offers. If you are looking for an architecture job. Software Architecture Interview Questions Part 2 (Design pattern). In this article we will cover Interpreter pattern Shivprasad Koirala; Jan 29 2. 0; k.
Clarify it, rather than be surprised when you get your first pay packet. So, ask for a detail breakdown beforehand. Is the offer worth it? Give it a good thought. So be careful during interview, or be sportive, or be a good negotiator in the next interview. So, once you have an offer in hand, go back to your old employees, show them the offer, and only then make your next move.
It is my personal experience that negotiating with an old employer is easier than with a new one. Just do not be aggressive or egoistic that you have an offer in hand. So, if the difference is money is not that much, go for job satisfaction. It is, at times, worth more than money. Raju left his old organization where he had a package of INR and joined a new organization with a package of INR.
In his old company he was getting INR on hand. At the first glance Mr. First thing when you get your salary do not accept it, take it home and dissect it. Try to extract what you will get on hand rather than looking at the CTC. Note: - We have written this tutorial according to Indian corporate industry.
But the basic concept will hold true even for other geographical corporates. We will devise a simple methodology by which we can conclude our on-hand component easily. Figure: - Five categories On hand: - Salary components which you get on hand needs to be pushed in to this category. Some of the examples are basic, HRA etc.
This component is something which you get fixed every month and directly in to your hand. Claim from bill: - There are some salary components which we get after submitting bills. Some of the examples of this category are LTA and phone bills. After some months: - There are salary components like bonus or some organization call them as retention bonus which is received after some months.
This can be in a form of yearly or quarterly bonus. Bonuses depend on company policies and many companies add this to your CTC. Again this amount is not received in the same month itself and they do not form the monthly on-hand component.
After leaving company: - There are some salary components which we get after leaving the company. For example provident fund PF. Again this component does not add to your on- hand monthly, rather its something you will get after resignation.
You will never get this amount. Now that we have segregated our components in to the above five categories, its time to understand three principles CTC, Gross and Net. CTC is everything that company spends on us. Many professionals get carried by the CTC figure and hop the jobs.
CTC is the addition of all the five components. If you need to integrate or make an existing system as a business service, you just need to create loosely coupled wrappers which will wrap your custom systems and expose the systems functionality in a generic fashion to the external world. I Can you explain business layers and plumbing layers in SOA? In SOA we can divide any architecture in two layers.
The first which has direct relevance to the business as it carries out business functions. The second layer is a technical layer which talks about managing computer resources like database, web server, etc.
This division is needed to identify a service. It has various components which interact with each other to complete the order system functionality. Figure: Simple order system The simple order system can be divided in to two layers see figure 'business and plumbing layer' - one which is business related and second which is more technical related.
You can see the plumbing layer consisting of data access layer, AJAX, and yes more technical stuff. Services are logical grouping of components to achieve a business functionality. Components are implementation approaches to make a service. A Can you describe the complete architecture of SOA? Please note this architecture diagram is not tied up with implementations of Microsoft, IBM etc.
How they do it is completely their own technological implementation. In order that these disparate systems work they should message each other. ESB Enterprise Service Bus acts like a reliable post office which guarantees the delivery of messages between systems in a loosely coupled manner.
ESB is a special layer which delivers messages between applications. In the figure we have shown a huge plump pipe. SOA registry is like a reference database of services. It describes what each service does, where they are located, and how they can communicate.
We will read more about BPM in further questions. Service broker reads the work flow and takes services from the SOA registry and ties them together. SOA supervisor is a traffic cop ensuring that services do not have issues. It deals mainly with performance issues of the system so that appropriate service levels are met.
Only admin have rights to modify the customer. First lets define extend and include and then see how the same fits in this use case scenario. Include: - Include relationship represents an invocation of one use case by the other. If you think from the coding perspective its like one function been called by the other function. Extend: - This relationship signifies that the extending use case will work exactly like the base use case only that some new steps will inserted in the extended use case.
One of the requirements of the project was that when we add a customer, the system should send an email. This also helps us defining a technical road map regarding relationships between simple and admin user.
Can you explain class diagrams? Class diagram Class is basically a prototype which helps us create objects. Class defines the static structure of the project. A class represents family of an object.
By using Class we can create uniform objects. In the below figure you can see how the class diagram looks. Basically there are three important sections which are numbered as shown in the below.
Figure: - Three sections of the class Now in the next section we will have a look on Association relationship between these classes.
How do we represent private, public and protected in class diagrams? Protected properties can only be seen within the component and not outside the component. Figure: - Private, public and protected Associations in Class diagrams A single Class cannot represent the whole module in a project so we need one or more classes to represent a module.
So by grouping and relating between the classes we create module and these are termed as Association. In order to associate them we need to draw the arrowed lines between the classes as shown in the below figure. The left to right marked arrow basically shows the flow that order class uses the payment class. In case payment class using the order class then the marked arrow should be right to left showing the direction of the flow. Figure:- Order is paid by Payments class There are four signs showing the flow:- Figure: - Direction signs in UML Multiplicity Multiplicity can be termed as classes having multiple associations or one class can be linked to instances of many other classes.