Agile software development Placement Paper
Company: Agile software development
java:
(1)find out three keywords
(a)synchronized
(b)implement
(c)throws
etc
(2)which are not keywords
(a)NULL
(b)synchronize
etc
(3)two to three questions on legal array declaration
(a)int a[][]=new int[3][3];
(b)int[] a[]=new int[3][3];
(c)int a[3][4]=new int[3][4];wrong
(d)int[3][4] a=new int[3][4];wrong
(e)int a[][]=new int[3][4];
(4)++i+++j is equivalent to
(a)i+j+1
(b)i+j+2
(c)i+j
(d)can’t be compiled(correct)
(5)the content of the array after execution of following statement:int a[][]=new int[3][3];
(a)all elements contain zeros
(6)find legal statements
(a)int a=30;
(b)float f=1.4;(error)
(c)double d=34.5;
(d)byte b=128;(error)
(7)find illegal statements
(a)int i=’2′;
(b)char a=12;
(8)some 5 questions on collection interfaces
(9)to find the length of array
(a)arr.length-1
(b)arr.length(correct)
(c)arr.length()
(10)write code for accessing array length without assigning it to another variable
(11)recursion is
(a)any function which refer itself
(12)the sorting method which don’t generally use recursion
(a)heap sort
(b)bubble sort(ans)
(c)quick sort
(d)bubble sort
(13)one questions regarding abstract
(14)some 2 questions on hash table
C++:
(1)the difference b/w pure virtual fn.& virtual fn.
(a)pure virtual function. is initialized to zero.
(b)
(2)virtual destructor’s are used for
(a)
(3)find legal statement
(a)cout>>”name”>>endl;
(b)cout<<”name<
(c)cout<<”name”<
(4)find the o/p of the program void main() { int a=10;b; if(a<=10) b=4; if(a>10)
b=5;
cout< }
(a)it don’t be compiled
(b)it compiles and o/p’s 10 4
(ans)
(5)a question on copying or assigning
(6)early or static binding means
(a)at runtime
(b)at compile time
(ans)
(7)one question on global variables,one qn on globally declared static variable
(8)two question on “vector” type
(9)the branch of a tree which has no childs is called
(10)when a node c is inserting b/w nodes a and b how many pointer will be modified
(a)2(check)
Agile software development Placement Paper
About Agile software development
Agile software development is more than frameworks such as Scrum, Extreme Programming, or Feature-Driven Development (FDD).
Agile software development is more than practices such as pair programming, test-driven development, stand-ups, planning sessions, and sprints.
Agile software development is an umbrella term for a set of frameworks and practices based on the values and principles expressed in the Manifesto for Agile Software Development and the 12 Principles behind it. When you approach software development in a particular manner, it’s generally good to live by these values and principles and use them to help figure out the right things to do given your particular context.
One thing that separates Agile from other approaches to software development is the focus on the people doing the work and how they work together. Solutions evolve through collaboration between self-organizing cross-functional teams utilizing the appropriate practices for their context.
There’s a big focus in the Agile software development community on collaboration and the self-organizing team.
That doesn’t mean that there aren’t managers. It means that teams have the ability to figure out how they’re going to approach things on their own.
It means that those teams are cross-functional. Those teams don’t have to have specific roles involved so much as that when you get the team together, you make sure that you have all the right skill sets on the team.
There still is a place for managers. Managers make sure team members have, or obtain, the right skill sets. Managers provide the environment that allows the team to be successful. Managers mostly step back and let their team figure out how they are going to deliver products, but they step in when the teams try but are unable to resolve issues.
When most teams and organizations start doing Agile development, they focus on the practices that help with collaboration and organizing the work, which is great. However, another key set of practices that are not as frequently followed but should be are specific technical practices that directly deal with developing software in a way that helps your team deal with uncertainty. Those technical practices are essential and something you shouldn’t overlook.visit offical Website of Agile software development for more details