KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK

Similar documents
Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1

Introduction to Software Engineering

A New Divide & Conquer Software Process Model

Lectures 2 & 3. Software Processes. Software Engineering, COMP201 Slide 1

Based on Software Engineering, by Ian Sommerville Coherent sets of activities for specifying, designing, implementing and testing software systems

SWE 211 Software Processes

SE420 Software Quality Assurance

Chapter. Redesigning The Organization With Information Systems

The Top Thrill Dragster

Pertemuan 2. Software Engineering: The Process

SDLC Models- A Survey

03. Perspective Process Models

This tutorial also elaborates on other related methodologies like Agile, RAD and Prototyping.

BABOK v3 Task to Technique Mapping

A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 2.0 Skillport

Testing. CxOne Standard

Object-Oriented & Classical Soft Engineering

Project Report Template (Sem 1)

System Engineering. Instructor: Dr. Jerry Gao

Volume 8, No. 1, Jan-Feb 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at

Object-Oriented and Classical Software Engineering

Project Management Context Outline

Tutorial Software is the differentiating characteristics in many computer based products and systems. Provide examples of two or three products

Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS 9/17/2017. CHAPTER 3 Slide 3.2. Stephen R. Schach. Overview Slide 3.

Introduction to Software Life Cycles and Agile. CSCI 5828: Foundations of Software Engineering Lecture 03 09/02/2014

Quizzes for 1 st Study Group Session

Service-Oriented Modeling (SOA): Service Analysis, Design, and Architecture

Component-Based Development in Geographically Dispersed Teams

Software Engineering II - Exercise

What are requirements? Basics of Requirement Engineering. Definition of a Stakeholder. Stated Vs. Real Requirements. Stated Vs.

Objectives. Rapid software development. Topics covered. Rapid software development. Requirements. Characteristics of RAD processes

Requirements Analysis and Design Definition. Chapter Study Group Learning Materials

Spiral Increment Reuse (SIR) Software Model

TECHNICAL REVIEWS AND AUDITS

Requirements Validation and Negotiation

Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling, tracking, and monitoring a comple

CONTENTS PART ONE FOUNDATIONS FOR SYSTEMS DEVELOPMENT. Preface 21

Requirements Engineering. Andreas Zeller Saarland University

UC Santa Barbara. CS189A - Capstone. Christopher Kruegel Department of Computer Science UC Santa Barbara

SE Notes Mr. D. K. Bhawnani, Lect (CSE) BIT

Secure Integration of the PersoApp-Open-Source-Library

18-642: Software Development Processes

Compliance driven Integrated circuit development based on ISO26262

LIFE-CYCLE MODELS AND PROCESS. Software Engineering 1/9/2008. CHAPTER 1, 2, and 3. Stephen R. Schach

IT Services Management Service Brief

SOFTWARE ENGINEERING

Major attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis

copyright Value Chain Group all rights reserved

Requirements for an MDM Solution

On the management of nonfunctional requirements

EVALUATION OF ARIS AND ZACHMAN FRAMEWORKS AS ENTERPRISE ARCHITECTURES

Introduction to Software Life Cycles. CSCI 5828: Foundations of Software Engineering Lecture 06 09/08/2016

Supply Chain MICROSOFT BUSINESS SOLUTIONS DEMAND PLANNER

Introduction to Software Engineering

Development of AUTOSAR Software Components with Model-Based Design

Software Development Life Cycle:

Enterprise Architecture: an ideal discipline for use in Supply Chain Management

Quality Assurance Plan D9.1.1

Integration and Testing

Software Lifecycle Models

Surviving the Top Ten Challenges of Software Testing

Building Information Systems

David. Director of Rational Requirements and Quality Management Products

Chapter 8. Systems Development. Ralph M. Stair George W. Reynolds

Chapter 6: Software Evolution and Reengineering

AUTOMOTIVE SPICE v3.1 POCKET GUIDE

Confident Software Development Process Model

HP Quality Center 10 Overview

CERTIFIED SOFTWARE QUALITY ENGINEER

Requirements Engineering and Agile Methodology

Intermediate Certificate in Software Testing Syllabus. Version 1.4

ISEB ISTQB Sample Paper

WebSphere. Enablement for WebSphere Industry Content Packs. Telecom Enablement

Introduction to Systems Analysis and Design

Vector Software W H I T E P A P E R. Using VectorCAST for Software Verification and Validation of Railway Applications

National Aeronautics and Space Administration Washington, DC 20546

Software Development Methodologies. CSC 440: Software Engineering Slide #1

INTERMEDIATE QUALIFICATION

ALM120 Application Lifecycle Management 12.x Essentials

What s New with the PlantPAx Distributed Control System

Software Life Cycle. Main Topics. Introduction

Product Line Engineering Lecture PL Architectures I

Jari Soini. Information Technology Department Pori, Finland. Tampere University of Technology, Pori

Introduction to Software Project Management. CITS3220 Software Requirements & Project Management

Chapter 3 Software Process Model

1) Introduction to Information Systems

The Product Creation Process

In-Process Automation

Requirements Engineering and Software Architecture Project Description

Redesigning the Organization with Information Systems

Chapter 10 CONCLUSIONS

Objective (c.f., p.58)

Sistemi ICT per il Business Networking

Methods in Enterprises

ISO/IEC JTC1/SC7 N2683

Why CIP? AIIM International's Certified Information Professional designation was designed to allow information professionals to:

Inception. Describe the vision and business case for this project. Determine if the enterprise should build or buy the necessary system.

System and it s Components

Architecture Development Methodology for Business Applications

Decentralized software development Pitfalls and challenges A software engineering viewpoint

Transcription:

KINGS COLLEGE OF ENGINEERING DEPARTMENT OF INFORMATION TECHNOLOGY QUESTION BANK Subject Code & Subject Name: IT1251 Software Engineering and Quality Assurance Year / Sem : II / IV UNIT I SOFTWARE PRODUCT AND PROCESS PART-A (2 MARKS) 1. What is meant by Software Engineering? 2. What are the characteristics of Software? 3. What are the phases of Problem solving Loop? 4. List out the activities of Linear Sequential Model. 5. Mention some of the drawbacks of RAD model. 6. What are the types of changes encountered during the Support phase? 7. Define Business process engineering. 8. What are the elements of Computer based Systems? 9. Define Software Lifecycle. 10. What are the functions of data architecture? 11. Define System Modeling? 12. State the System Engineering Hierarchy? 13. Mention some of the factors to be considered during System Modeling. 14. What are the different architectures developed during BPE? 15. Define Verification &Validation. 16. Write any two software engineering challenges. 17. Which software model leads to software reuse? Why? 18. Give at least two reasons for prototyping is problematic. 19. Differentiate system and computer based system. 20. Define software engineering and system engineering. 21. What is software process model? PART B 1. Explain the linear software life cycle model with suitable illustration. Bring out the demerits of this model. (16) 2. (a) How do you differentiate software engineering from system engineering? (6) (b) For each of the types of process models, identify the types of project suitable to implement. (6) (c) Distinguish between verification and validation process. (4)

3. (a) What is meant by generic view of software engineering? Brief it. (b) Explain the process model which is useful when staffing is unavailable for complete implementation. 4. (a) What is the difference between system and computer based system? (b) What is prototyping? Mention its types. Also explain this model with advantages and disadvantages. 5. Define Software process model? Explain any one of it with a neat diagram(16) 6. Explain the hierarchy of Business process Engineering. (16) 7. Explain Software Life cycle process (16) 8. Explain Evolutionary process model (16) 9. Explain the different layers of Software Engineering? (16) 10. (a) Describe the process model which defines a network of activities? (b) Why the first system s throw away system? Explain the concept with advantages and disadvantages. 11. (a) Draw a system engineering hierarchy diagram and explain the concept? (b) Explain the process model that combines the elements of waterfall and iterative fashion. UNIT-II SOFTWARE REQUIREMENTS Part- A (2 MARKS) 1. What is meant by System Requirements? 2. What are the types of Software system requirements? 3. Write down the functional requirement for a Library management system. 4. Mention some of the Notations for requirements specification. 5. Define the term product and process in software engineering 6. Define Requirement Engineering. 7. Mention some of the process activities of Requirement Elicitation & analysis. 8. What are the different types of checks carried out during Requirement Validation? 9. Define Traceability 10. Draw the principle stages of Change management process. 11. State the primary objectives of analysis Model. 12. Define Data objects, attributes & relationship. 13. Define Cardinality & Modality. 14. State Entity /Relationship diagram. 15. Define Data Flow Diagram. 16. What is meant by Information flow Continuity? 17. Define Behavioral Modeling. 18. What is meant by Data dictionary? 19. What does data dictionary contains? 20. What is meant by Throw away Prototyping? 21. Specify at least six context free questions. 22. What is the purpose of domain analysis?

23. List some non-functional requirements of software, with an example. Part - B 1. (a) With a suitable example explain about the application of use cases in deriving the scenarios. (b) Explain the various prototyping methods and tools used for requirements analysis. 2. Discuss in detail about the elements in data modeling. (16) 3. (a) Differentiate functional and nonfunctional requirements and explain. (b) Why the customer interaction is a difficult process? Explain one formal procedure used for customer interaction. 4. (a) Draw an E-R diagram for university information system. specify at least four Cardinality and modality relationships in this. (b) Explain the relationships between data and control models with diagram. 5. (a) Explain the feasibility studies. What are the outcomes? Does it have either explicit or implicit effects on software requirement collection? (b) What are prototyping techniques? How prototype models are prepared for software process? Discuss. 6. (a) Describe how software requirements are documented? State the importance of documentation. (b) Explain the software requirement analysis and modeling. 7. Explain Transform Mapping with Safe home Software. (16) 8. Explain briefly Functional Modeling. (16) 9. Explain the various Design concepts in detail. (16) 10. Discuss the various phases of Analysis Modeling. (16) UNIT-III ANALYSIS, DESIGN CONCEPTS AND PRINCIPLES Part- A (2 MARKS) 1. What is the use of Architectural design? 2. Define Software design. 3. Mention some of the Design principles. 4. State Procedural abstraction. 5. What does Data abstraction contains? 6. What does Modularity concept mean? 7. Mention some of the criteria are used to define effective modular design. 8. Define Fan-in & Fan-out. 9. Differentiate horizontal partitioning & vertical partitioning. 10 Write down the concept of Functional independence. 11. Distinguish between expected requirements and exciting requirements. 12. What is meant by software prototyping? 13. What is the work product of software design process and who does this? 14. Define the term software architecture. 15. What is meant by transaction mapping? How it is used in software design? 16. What are the criteria based on which the lower and upper bounds on the number of modules for a software is decided? 17. What re the types of coupling?

18. Name the three levels of abstraction, which re in practice for the design. 19. Why modularity is important in software projects? 20. Differentiate version control and change control. 21. Draw a ACD for safe home security system. 22. Differentiate Transform flow and Transaction flow. Part - B 1. (a) Which is a measure of interconnection among modules in a program structure? Explain. (b) What is he difference between Level-0 and Level-1 DFD? draw a Level-0 and Level-1 DFD for safe Home Security System. 2. (a) How the interrupts are handled in real time systems? Explain. (b) How to identify the objects in the software configuration? Explain in detail. 3. What are the different types of architectural styles exist for software and explain any one software architecture in detail. (16) 4. (a) Describe activities of SCM in detail. (b) Explain the user interfaces design activities. 5. (a) Explain data, architectural and procedural design for a software explain. One software architecture in detail. (b) Describe the design procedure for a data acquisition system. one software architecture in detail. 6. Discuss briefly Effective Modular Design. (16) 7. Explain Real Time Systems. (16) 8. What is Software Architecture? Explain it. (16) 9. (a) Draw a translating diagram for analysis model into a software design specification. (b) Given complete template for documentation design specification. 10.(a) How the interrupts are handled in real time systems? Explain. (b) Write a note on real time software design. UNIT-IV TESTING Part - A (2 MARKS) 1. Define black box testing strategy. 2. What is meant by software change? 3. Why testing is important with respect to software? 4. Write short notes on empirical estimation models. 5. Justify the term Software is engineered 6. Define software scope. 7. Define process maturity. 8. Distinguish between alpha testing and beta testing. 9. What is software architecture? 10. Assume a program for computing the roots of a quadratic equation. List out the test cases using equivalence partitioning method. 11. Write the steps involved in testing real time systems. 12. How the regression and stress tests are performed? 13. State the objectives and guidelines for debugging.

14. Which is called as glass box testing? What is the objective of this? 15. List out the data structure errors identified during unit testing. 16. What is regression testing? 17. What is smoke testing? 18. What is recovery testing? 19. What are the guidelines for equivalence classes? 20. What is software testing? 21. What is structural testing? 22. Define top-down testing. Part - B 1. (a) How to derive test cases for the given project? Explain with detail. (b) How the RST (Reflexive, Symmetric and Transitivity) condition is verified in black box testing? Explain with example. 2. (a) Why unit testing is so important? Explain the concept of unit testing in detail. (b) Write a note on regression testing. 3. (a) Explain the testing procedure for boundary conditions. (b) Describe verification and validation criteria for software. 4. (a) Describe unit testing and integration testing. How test plans are generated. (b) Suggest software testing sequence for 100% bug free software explains. 5. (a) Why is testing important? (6) (b) Narrate the path testing procedure in detail with a sample code. (10) 6. (a) Distinguish between black box and white box testing. (6) (b) Explain the different integration testing approaches. (10) 7. Explain in detail Black box testing in detail (16) 8. How Boundary test conditions are achieved? (16) 9. Explain in detail Structural testing? (16) 10. Explain in detail Software Testing Strategies. (16) 11. Explain the test coverage criteria based on Data flow mechanisms. (16) UNIT V SOFTWARE QUALITY ASSURANCE Part A (2 Marks) 1. Define Process. 2. Define Product. 3. Define Software quality. 4. Define software metrics. 5. Mention the types of metrics. 6. Define Quality control. 7. Define Software Quality Management 8. Define Software Configuration Management 9. List the steps involved in Process Improvement 10. Mention the types of software metrics. 11. What is software quality assurance? 12. Define Quality Planning.

Part B 1. Explain the Classification of metrics? (16) 2. Explain about CASE tools? (16) 3. Explain Process and Product Quality. (16) 4. Explain in detail about quality assurance and standards. (16) 5. Explain about complexity metrics and Models? (16) 6. Explain about the software metrics. (16) 7. Explain in detail about Quality planning and control. (16) 8. Explain about Software Configuration Management. (16) 9. What are all the formulas for cyclomatic compleity? Calculate cyclomatic Complexity for greatest of three numbers. (16) 10. Explain in detail about Process Improvement. (16)