Transcription

1 CLASS/YEAR: II MCA SUB.CODE&NAME: MC7303, SOFTWARE ENGINEERING. 1. Define Software Engineering. Software Engineering: 2. What is a process Framework? Process Framework: UNIT-I 2MARKS QUESTIONS AND ANSWERS The application of systematic, disciplined, quanifier approach. To the development, operations, and maintenance of software. Establishes foundation for a complete software process. By identifying a small number of framework activities that are applicable for all software projects regardless of their size and complexity. 3. What are the Generic Framework Activities? Generic Framework Activities: Communication. Planning. Modelling. Construction. Deployment. 4. Define Stakeholder. Anyone who has stake in successful outcome of project. Business managers, end users, software engineer, support people. 5. How the process models differ from one another? Based on flow of activities. Inter dependencies between activities. Manner of quality assurance. Manner of project tracking. Team organization and roles. Work products identify an requirement identifier. 1

2 6. Write out the reasons for the failure of water fall model? Real project rarely follow sequential flow. Iterations are made in indirection manner. Difficult for customer to state all requirements explicitly. Customer needs more patients as working product reach only at deployment phase. 7. What are the drawbacks of RAD model? Require sufficient number of human resources to create enough number of teams. Developers and customers are not commited, system result in failure. Not properly modularized building component may problematic. Not applicable when there is more possibility for technical risk. 8. Why formal methods are not widely used? Quite time consuming and expensive. Extensive expertise is needed for developers to apply formal methods Difficult to use as they are technically sophisticated maintenance may become risk. 9. Define verification and validation. Verification refers to the set of activities that ensure that s/w correctly implements a specific function. Validation refers to a difference set of activities that ensure that the s/w that has been built is traceable to customer requirements. 10. What are the different phases of unified process? Inception phase. Elaboration phase. Construction phase. Transition phase. Production phase. 11. What is the objective of the project planning process? To provide framework that enables manager to make reasonable estimates of resources, cost and schedule. 12. What are the decomposition techniques? Software sizing. Problem-Based estimation. Process-Based estimation. Estimation with use Cases. Reconciling estimation. 2

3 13. How do we compute the Expected Value for software size? Excepted value for estimation variable(size), S, can be compute as weighted average of optimistic(sopt), most likely(sm), and pessimistic(spess) estimates 14. What is an object point? S=(Sopt+4Sm+Spess)/6 Count is determined by multiplying original number of object instances by weighting factor and summing to obtain total object point count. 15. List out the basic principles of software project scheduling? Compartmentalization. Interdependency. Time Allocation. Effort Validation. Defined Responsibilities. Defined Outcomes. Defined Milestones. 16. What are the classifications of system engineering? Business process engineering[bpe]. Product engineering. 17. What are the drawbacks of water fall model? 1. It does not adequately address changes. 2. It assumes a relatively uniform and orderly sequence of development steps. 3. It does not provide for such methods as rapid prototyping or advanced languages. 18. What are the fundamental activities of a software process? Specification. Design and implementation. Validation. Evolution. 19. What are the Drawbacks of spiral model? It is based on customer communication. If the communication is not proper then the software product that gets developed will not be the up to the mark. It demands considerable risk assessment. If the risk assessment is done properly then only the successful product can be obtained. 20. Define software prototyping. 3

4 Software prototyping is defined as a rapid software development for validating the requirements. 21. What are the benefits of prototyping? 1. Prototyping serves as a basis for deriving system specification. 2. Design quality can be improved. 3. System can be maintained easily. 4. Development efforts may get reduced. 5. System usability can be improved. 22. What are the various rapid prototyping techniques? 1. Dynamic high level language development. 2. Database programming. 3. Component and application assembly. 16MARKS QUESTIONS 1. Write a short notes on i. Waterfall Model, ii. Spiral Model, iii. Prototype Model. 2. Explain the fourth generation techniques. 3. What is the necessary of planning? Explain the planning cycle. 4. Explain the cost estimation procedure using COCOMO model. 5. Explain the organizational structure of the software development. 6. Why software project scheduling in needed discuss the advantages and disadvantages of it. 7. Explain the process of Risk Analysis and Management. 8. Explain the concept of requirements and specification. 9. Write a short note on Rapid prototyping. 4

5 1. List of principles of a software design. UNIT-II 2MARKS QUESTIONS AND ANSWERS i. The design process should not suffer from tunnel vision. ii. The design should be traceable to the analysis model. iii. The design should exhibit uniformity and integration. iv. Design is not coding. v. The design should not reinvent the wheel. 2. What are the characteristics of a good design? A good design should be interesting to any software engineering. They include general principles and functionality. A good design methodology is one that implements the principles of design. 3. List out the advantages of structured design. A natural approach to modularization. An apt emphasis on data in the design process. A semi algorithmic way of defining software organization. A natural and widely understood notation. Easy integration with specification and detailed design. 4. Define Abstraction. Abstraction is a process of consolidating on entire set of detailed attributed by using a few central traits or even a single name to represent them. It is a tool that allows us to deal with concepts apart from particular instances or those concepts. 5. List out the types of Abstraction? a. Function al abstraction. b. Data abstraction. c. Control abstraction. 6. Define Modularity. 7. What is DFD? Module is a small functional routine. It can stand on itself or it can be coupled with other application also. Modular systems incorporate collections of abstraction. A modular system consists of well-defined manageable units with welldefined interface among units. Dataflow diagram depicts the information flow and the transforms that are applied on the data as it moves from input to output. 5

6 8. Define Quality Function Deployment [QFD]? Technique translates needs of customer into technical requirements. Concentrates on maximizing customer satisfaction from the software engineering process. 9. How the architecture design can be represented? Architecture design can be represented by one or more different models. They are: a. Structural Models. b. Framework Models. c. Dynamic Models. d. Process Models. 10. What is coupling? Quantitative measure of degree to which classes are connected to one another keep coupling as low as possible. 11. What is cohesion? Indication of relative functional strength of a module. Natural extension of information hiding. Performs a single task, requiring little integration with other components. 12. What are the different types of coupling? a. Content Coupling. b. Common Coupling. c. Control Coupling. d. Stamp Coupling. e. Data Coupling. f. Routine Call Coupling. g. Type Use Coupling. h. Inclusion or Import Coupling. i. External Coupling. 13. What is the various design notations are there? 1. Dataflow diagram. 2. Structure charts. 3. HIPO diagram. 4. Pseudo code. 6

7 16 MARKS QUESTIONS 1. Explain the concept of Software Design. 2. Write a short note on abstraction. 3. Explain software architecture. 4. Discuss the advantages of the Modularity in software design. 5. Explain the types of coupling and cohesion. 6. Explain the various design concepts and notations. 7. Explain Top-down design and bottom up design. 8. Explain the software design documentation in detail. 9. Design procedure for real time and distributed system software. 10. Explain the Jackson System Development with an example. 7

8 UNIT-III 2 MARKS QUESTIONS AND ANSWERS 1. Define Metrics for software. 2. Mention the different types of software matrices. 1. Productivity Metrics. 2. Quality Metrics. 3. Technical Metrics. 4. Size-Oriented Metrics. 5. Function oriented Metrics. 6. Human-oriented Metrics. 3. What is Direct Measure? Direct measures in software focus on attributes that can be measured directly by examining the process product on the resources applied. 4. What is Indirect Measure? Indirect measures are determined by establishment on empherical relationship between the measure desired and other attributes of the entity. 5. What is Software Quality Assurance? Set of auditing and reporting functions. Assess effectiveness and completeness of quality control activities. 6. What is the objective of formal technical reviews? Uncover errors in function, logic and implementation for representation of software. Software represented according to predefined standard. Verify software under review meets requirements. Achieve software developed in uniform manner. Make projects more manageable. 7. What steps are required to perform statistical SQA? Information about software defects is collected and categorized. Attempt is made trace each defect. Using pare to principle, isolate 20%. Once vital causes are identified, correct problems that cause defects. 8

9 8. Define SQA plan. 9 Provides roadmap for instituting SQA. Plan serves as template for SQA activities that instituted for each software project. 9. Define Software Reliability? Software Reliability: Probability of failure-free operation of computer program in a apecified environment for a specified time. 10. How the registration process of ISO 9000 certification is done? Registration process of ISO 9000 certification has the following stages 1. Application. 2. Pre-assessment. 3. Document review and adequacy of audit. 4. Compliance audit. 5. Registration. 6. Continued Surveillance. 11. What are the factors of software Quality? Factors of software Quality. Portability. Usability. Reusability. Correctness. Maintainability. 16 MARKS QUESTIONS 1. Mention the different types of software matrices and explain them. 2. Explain Direct and indirect measure. 4. Write a short notes o function point analysis. 5. Write a short note on reliability. 6. Mention the responsibilities of SQA. 7. Why software standards are needed.

10 UNIT-IV 2 MARKS QUESTIONS AND ANSWERS 1. What are the Basic Principles of Software Testing? 1. Traceable to customer requirements. 2. Planned long before testing begins. 3. Pareto principle applied to software testing. 4. Begin small and progress towards testing. 5. Exhaustive testing is not possible. 6. Conducted by independent third party. 2. List out the characteristics of testability of software? Operability. Controllability. Decomposability. Simplicity. Stability. Understand ability. 3. Define smoke Testing? Integration Testing commonly used when software products are being developed. 4. What are the attributes of good test? a. High probability of finding errors. b. Not redundant. c. Best of breed d. Neither too simple nor too complex. 5. Define White box testing. Also called glass box testing. 10

11 6. Define basic path testing. Test case design uses control structure of procedural design to derive test cases. White box testing. Enable test case designer to drive a logical complexity measure of a procedural design. Use this measure as a guide for defining a basis sec of execution paths. 7. What is behavioural testing? 1. Also known as black box testing. 2. Focuses on functional requirement of software. 3. Enables software engineering to derive set of input condition that fully exercise all functional requirements of a software. 8. What are the benefits of conducting smoke testing? 1. Integration risk is minimized. 2. Quality of end-product is improved. 3. Error diagnosis and correction are simplified. 4. Progress is easy to assess. 9. What errors are commonly found during Unit Testing? a) Misunderstood or incorrect arithmetic precedence. b) Mixed Mode Operations. c) Incorrect Initialization. d) Precision Accuracy e) Incorrect Symbolic representation of expression. 10. What problems may be encountered when Top-Down Integration is chosen? Delays are test until stubs replace with actual modules. Develop stubs that perform limited functions that simulate the actual module. Integrate the software from the bottom of the hierarchy upward. 11

12 11. What are the steps in bottom-up integration? Low level components are combined into clusters perform specific software sub function. Driver is written to coordinate test case input and output. Cluster is tested. Drivers are removed and clusters are combined moving inward in program structure. 12. What is regression testing? Re-execution of some subset of tests that have already been conducted. To ensure changes have not propagated unintended side effects. 13. What are the characteristics of Critical Module? Addresses several software requirements. Has high level of control. Complex or error prone. Has a definite performance requirement. 14. What is flow graph notation? Simple notation for representing control flow. Draw only when logical structure of component is complex. 15. List out the possible errors of black box testing? Incorrect or missing functions Interface errors. Errors in data structures or external databases. Behavioural or performance errors. Initialization or termination errors. 12

13 16 MARKS QUESTIONS 1. Explain the software testing strategies. 2. Write a short note testing tools. 3. Explain in details about top-down approach and bottom approach. 4. Explain the concept of test case management. 5. Write a note on management report. 6. Explain the types of maintenance. 13 UNIT-V

14 2 MARKS QUESTIONS AND ANSWERS 1. What is software configuration management? The software configuration management is a mechanism for Identifying. Controlling. Tracking. 2. What are the components of the cost of quality? Quality costs. Prevention costs. Appraisal costs.\ 3. What is software quality control? Involves series of inspections, reviews and tests. Used throughout software process to ensure each work product meets requirements placed upon it. 4. What are baseline criteria in SCM? a) Help to control change. b) Specification or product that has been formally. c) Reviewed and agreed upon serves as basis for future development. d) That can be change only through formal change control procedures. 5. Define status reporting? Also called configuration status reporting Is a SCM task that answers 1. What Happened? 2. Who did it? 3. When did it happen? 4. What else will be affected? 14

15 6. What is the origin of changes that are requested for software? New business or market condition. New customer needs. Reorganization or business growth/downsizing. Budgetary or scheduling constraints. 7. List out the elements of SCM? Component elements. Process elements. Construction elements. Human elements. 8. What are the features supported by SCM? Versioning. Dependency tracking and change management. Requirements tracking. Configuration Management. Audit trails. 9. What are the objectives of SCM process? Identify all items, collectively define software configuration. Manage changes to one or more these items. Facilitate construction of different version of an application. Ensure that the software quality is maintained. 10. What are the issues to be considered for developing tactics for WebApp configuration management? 1. Context. 2. People. 3. Scalability. 15

16 11. Define CASE Tools. It is system software. Provide automated support for software process activities. Includes program used to support software process activities such as requirement analysis, system modelling, debugging and testing. 12. How do we define software quality? Conformance to explicitly stated functional and performance requirements, explicitly documented development standards. Implicit characteristics, expected for professional developed software. 13. What are the types of CASE Tools? Types of CASE Tools. 1. Upper CASE Tools. 2. Lower CASE Tools. 16 MARKS QUESTIONS 1. Describe the various software configuration management tasks in details. 2. Explain the need for SCM. 3. Write notes on version control and change control. 4. Explain CASE repository in details. 5. Explain building blocks for CASE. 16