Question 1) What do you mean by requirement elicitation? Describe the significance of requirement elicitation in the analysis phase?
b) A software organization has DRE data for 15 projects over the past two years. The values collected are 0.81, 0.71, 0.87, 0.54, 0.63, 0.71, 0.90, 0.82, 0.61, 0.84, 0.73, 0.88, 0.74, 0.86, 0.83. Create mR and individual control charts to determine whether these data can be used to assess trends.
Question 2)a) Define and describe data modelling, function modelling and behaviour modelling in detail?
b) Describe the various notations used in DFD? Develop the DFD for library management system?
Question 3)a) Describe the concept of designing? Also describe the significance of data structure in data design.
b) Design project database system that would enable a software engineer to store, cross reference, trace, update, change, and so forth all significant software configuration items. How would the database handle various versions of the same program? Would source code be handled differently than documentation? How will two developers be precluded from making different changes to the same SCI at the same time?
Question 4)a) Describe the rules for mapping user requirements into software architecture?
b) Define and distinguish between cardinality and modality with the help of suitable example?
Question 5)a) Distinguish between validation and verification? Also explain the strategic issues in software testing?
b) Write down at least three examples in which black-box testing might give the impression that “everything’s OK,” while white-box tests might uncover an error. Give at least three examples in which white-box testing might give the impression that “every-thing’s OK,” while black-box tests might uncover an error.