IT Questions


Explain the software development life cycle

Requirements:


1.    How would you use a work breakdown structure to describe baking a birthday cake?  Draw an activity graph based on your structure and identify the critical path. (Hint:  Google “Birthday Cake with Hot Pink Butter Icing” to find your recipe – use the recipe from food network).
Type Response Here:
Reference:
 2.    What is the critical path on the activity chart below?
 

 Type Response Here:
Reference:

3.    If a project is behind, how does adding personnel to the project delay the project even more?
Type Response Here:
Reference:

4.    Consider the question above.  Brooks Law states that “adding manpower to a late software project makes it later".  However, some schedule estimation techniques state that adding personnel can decrease the time to develop a system.  Why this dichotomy of viewpoints?  Are they both true?  If so, how can this be?

Type Response Here:
Reference:

5.    Should projects be measured based on the number of lines of code per day that developers wrote on past projects?  In other words, if on past project, on average, developers wrote 500 lines of code per day, is it appropriate to assume they will do the same on upcoming projects?
a.    What if a program is written in a different language?
b.    Can productivity in terms of lines of code be measured before implementation?
c.    Does the way in which the code is structured affect productivity?

Type Response Here:
Reference:

Get answers now at a 30% discount



EmoticonEmoticon