Before Applying job posting in any websites or recruiting agencies or sending resumes to job recruiters or any other employment website you need to improve your skills on general knowledge, Aptitude, Puzzles, logical reasoning, general english, database, programming as per your job profile. Job recruiters or mostly preferring job candidates who are having more stuff in those categories mentioned above. So improving more skills on your job profile always boost up your career and your performance. Even hiring companies and job recruiters who are looking for many job posting websites actually they are looking and filtering on these activities. In these Java J2ee section you need to update more questions to perform well in front of job recruiters and companies. Java J2ee Interview questions are most important to score in interview, Update all questions to score well in all rounds in job interview.

JAVA / J2EE interview questions and answers

What are the two main advantages of modeling?

Readability : Representing your whole architecture in flowchart, class diagrams, ER diagrams etc makes your project more readable. Especially when programmer’s change jobs handover becomes easier. More the project is not readable more the dependencies

Reusability: After the system is more readable and broken down to pieces, it becomes easier to identity redundant and similar modules Thus increasing reusability.

What is the sequence of UML diagrams in project?

First let me say some fact about this question, you can not implement all the nine diagrams given by UML in one project: you can but can be very rare scenario. The way UML is implemented in project varies from project to project and company to company.
Second very important point to remember is normally all diagrams are not implemented in project, but some basic diagrams are important to have in order that project is readable.

Write about the Roll out and close over phases?

All document just to re-check that things are proper, example all modules deployed according to the deployment diagrams, are all business rules in use Cases satisfied.

Let us revise the following points:
Not all diagrams are compulsory.
The minimum diagrams according to software life cycle phases are :

  • Requirement phase : Use Case Diagrams
  • Design phase : Component diagrams, Class diagrams
  • Implementation phase : All diagrams derived from pervious phases specially class diagram for reverse engineering.
  • Testing phase : All diagrams derived from requirement and design phases for verification and preparing test plans.
  • Roll out and close over phase : All document derived from Design phase and requirement phases.
Give a small brief explanation of all Elements in activity diagrams?

Action State : It is a type of state that has an internal action and one outgoing event that would complete the internal action.
State : It is a condition when following events occur:
Object satisfies a condition
Or performs a action.
Or wait for a event to happen.

  • Initial State: It represents a state before any event occurs.
  • Final State: Represents completion of an activity.
  • Transition Fork: Denotes beginning of parallel path activities.
  • Transition Join: Denotes merging of parallel path activities.
  • Control Flow: Represents relationship between two states and actions. In short it indicates that an object in one state is entering some other state.
  • Object Flow: Connects an object flow state to control flow or action state.
  • Object in State: Indicate the object’s state after manipulation by multiple activities.
  • Decisions: Defines if there are any condition’s in the path.
  • Swim Lanes: Assigns responsibility to action states.
  • Signal receipt Shape: Used to replace an event label on a transition.
  • Constraint: Conditions that must be maintained true in order the system is valid.
  • 2-Element Constraint: It show a constraint on two classes or associations.
  • OR constraint: It show an OR constraint on two classes or associations.
Explain Different elements of a collaboration diagram?
  • Classifier Role: It classifies a role.
  • Association Role: It shows the relation between two classifier roles.
  • Multi-Object: It used to show operation related to entire set of objects rather than on a single object.
  • Constraint: Conditions which must be maintained as true in order that system is valid.
  • 2-Element Constraint: It shows a constraint on two classes or associations.
  • OR constraint: It shows an OR constraint on two classes or associations.