CT41 (ALCCS) SOFTWARE ENGINEERING JUN 2015

Similar documents
ADIKAVI NANNAYA UNIVERSITY B. A Computer Applications / B.Sc Computer Science/B.Sc IT Syllabus Under CBCS w.e.f

SRM ARTS AND SCIENCE COLLEGE SRM NAGAR, KATTANKULATHUR

Software Engineering (CSC 4350/6350) Rao Casturi

Study of Component Based Software Engineering

VETRI VINAYAHA COLLEGE OF ENGINEERING AND TECHNOLOGY DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

INSTITUTE OF AERONAUTICAL ENGINEERING (Autonomous) Dundigal, Hyderabad

Software Design And Modeling BE 2015 (w. e. f Academic Year )

CS SOFTWARE ENGINEERING QUESTION BANK SIXTEEN MARKS

QUESTION BANK UNIT 1 SOFTWARE PROCESS AND PROJECT MANAGEMENT Part A

PPSC Competitive Exam for the Post of System Analyst

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING CS SOFTWARE ENGINEERING

Ms. Bhawna Sharma 1, Ms. Kavita Choudhary 2, Mr Rajendra Purohit 3 1 M.Tech. Scholar, 2 Associate professor, 3 Research Scholar

Govt. of Karnataka, Department of Technical Education Diploma in Information Science & Engineering. Sixth Semester

Simply Java Programming: An Application Driven, Tutorial

Testing Object-Oriented Applications. Slide Set to accompany. Software Engineering: A Practitioner s Approach, 7/e by Roger S.

Level: M.Ed. Credit Hour: 3 (2+1) Semester: Second Teaching Hour: 80(32+48)

Systems Analysis and Design in a Changing World, Fourth Edition

Sample Exam Syllabus

Introduction to Software Engineering p. 1 The Scope of Software Engineering p. 3 Historical Aspects p. 4 Economic Aspects p. 7 Maintenance Aspects p.

Software Testing Strategies. Slides copyright 1996, 2001, 2005, 2009, 2014 by Roger S. Pressman. For non-profit educational use only

Lecture 15 Software Testing

Testing Object-Oriented Applications. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only

STUDY ON VARIOUS PHASES OF SOFTWARE TESTING LIFE CYCLE

Object-Oriented Systems Analysis and Design Using UML

SRM ARTS AND SCIENCE COLLEGE SRM NAGAR, KATTANKULATHUR

ADDMISSION-CALL / / WEBSITE:-

26. Object-Oriented Design. Java. Summer 2008 Instructor: Dr. Masoud Yaghini

SESSION M12-S12 INTERNAL ASSIGNMENT

Subject: Software Engineering & UML (MCA 401)

Helix Test Case Management Best Practices

SOFTWARE ENGINEERING. Lecture 6. By: Latifa ALrashed. Networks and Communication Department

KINGS COLLEGE OF ENGINEERING

Design Concepts. Slide Set to accompany. Software Engineering: A Practitioner s Approach, 7/e by Roger S. Pressman

MLR Institute of Technology

Component-Level Design. Slides copyright 1996, 2001, 2005, 2009 by Roger S. Pressman. For non-profit educational use only

CS485/540 Software Engineering Architecture and Component Design (Chs. 9,10)

CS 424 Software Quality Assurance & Testing LECTURE 3 BASIC CONCEPTS OF SOFTWARE TESTING - I

Verification and Validation. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 22 Slide 1

Software Metrics 2.1 INTRODUCTION 2.2 PROJECT MANAGEMENT PROCESS ACTIVITIES

Verification and Validation. Assuring that a software system meets a user s needs. Verification vs Validation. The V & V Process

Roll No. :. Invigilator's Signature :.. CS/MCA/SEM-4/MCA-401/ SOFTWARE ENGINEERING & TQM. Time Allotted : 3 Hours Full Marks : 70

Structured Analysis and Design

Discovering Computers Living in a Digital World

Chapter : Analysis Modeling

SOFTWARE ENGINEERING IT 0301 Semester V B.Nithya,G.Lakshmi Priya Asst Professor SRM University, Kattankulathur

SHRI ANGALAMMAN COLLEGE OF ENGINEERING & TECHNOLOGY (An ISO 9001:2008 Certified Institution) SIRUGANOOR,TRICHY

Identify the guidelines for system development. Discuss the purpose of the activities performed in the analysis phase

(Complete Package) We are ready to serve Latest Testing Trends, Are you ready to learn? New Batches Info

UNIT 1-SOFTWARE PROCESS AND PROJECT MANAGEMENT

Examination Questions Time allowed: 1 hour 15 minutes

TEXAS DEPARTMENT OF INFORMATION RESOURCES. Test Scenario. Instructions. Version DEC 2006

(Team Name) (Project Title) Software Design Document. Student Name (s):

Darshan Institute of Engineering & Technology for Diploma Studies

SE310 Analysis and Design of Software

Software Testing Techniques

Darshan Institute of Engineering & Technology for Diploma Studies Rajkot Unit-1

System development, design & implementation

VEER NARMAD SOUTH GUJARAT UNIVERSITY

1 Visible deviation from the specification or expected behavior for end-user is called: a) an error b) a fault c) a failure d) a defect e) a mistake

A Data Modeling Process. Determining System Requirements. Planning the Project. Specifying Relationships. Specifying Entities

In this Lecture you will Learn: Testing in Software Development Process. What is Software Testing. Static Testing vs.

Software Documentation

System Analysis and Design

(A Very Brief) Introduction to Software Engineering

IMS1002/CSE1205 Lectures 1

Part 5. Verification and Validation

OBJECT-ORIENTED MODELING AND DESIGN. Introduction

International Journal of Computer Engineering and Applications, Volume XII, Special Issue, April- ICITDA 18,

[IT6004-SOFTWARE TESTING] UNIT 2

Probabilistic Models of Software Function Point Elements

Syllabi & Scheme of Examination BCA-3 rd Year. Website:-

Examples. Object Orientated Analysis and Design. Benjamin Kenwright

Unit-3 Software Design (Lecture Notes)

Workshop 2: Function Point Analysis. Marlon Dumas

Object-Oriented and Classical Software Engineering

A Proposal to Develop a Testing Framework for Agile Software Process

Introduction to System Design

CS6403 SOFTWARE ENGINEERING Year / Sem : II / IV Sub. Code &Subject : CS6403 SOFTWARE ENGINEERING QUESTION BANKWITH ANSWERS

International Journal of Computer Engineering and Applications, Volume XII, Special Issue, September 18, ISSN SOFTWARE TESTING

Existing Model Metrics and Relations to Model Quality

Business Analysis for Practitioners - Requirements Elicitation and Analysis (Domain 3)

Lecture 14: Chapter 18!

ITC213: STRUCTURED PROGRAMMING. Bhaskar Shrestha National College of Computer Studies Tribhuvan University

Object Oriented Programming

Syllabi of the Comprehensive Examination in Computer Science

OBJECT-ORIENTED SOFTWARE DEVELOPMENT Using OBJECT MODELING TECHNIQUE (OMT)

Testing is executing a system in order to identify any gaps, errors, or missing requirements in contrary to the actual requirements.

Object-Oriented and Classical Software Engineering DESIGN 11/12/2017. CET/CSC490 Software Engineering Design CHAPTER 14. Stephen R. Schach.

Verification and Validation

Information Systems. Software Engineering. MCQ - Part 2

SOFTWARE ENGINEERING DECEMBER. Q2a. What are the key challenges being faced by software engineering?

Introduction to Software Engineering

Comparison Study of Software Testing Methods and Levels- A Review

System models Abstract descriptions of systems whose requirements are being analysed. System modelling. Structured methods

Design Concepts and Principles

Syllabi & Scheme of Examination MCA/Msc-2 nd Year. Website:-

Basics : the Requirements Engineering Process

copyright 1996, 2001, 2005 R.S. Pressman & Associates, Inc.

UNIVERSITY OF CALICUT SCHEME AND SYLLABUS FIFTH SEMESTER BACHELOR OF TECHNOLOGY INFORMATION TECHNOLOGY

International Function Point Users Group References: Capers Jones: Applied Software Measurement (1997) Estimating Software Costs (1998)

Transcription:

Q.1 a. What is the role of software engineering? (4) Role of software engineering with reference to producing good quality software, maintainable software, and on time within budget. b. Differentiate between reviews, walkthroughs and inspections. (4) Inspection process is a formal in-process manual examination of an item to detect bugs. It may be applied to any product or partial product of the software development process. This process is carried out by a group of peers with the help of checklists. A walkthrough is less formal, has fewer steps, and does not use a checklist to guide or a written report to document the team s work. A technical review is intended to evaluate the software in light of development standards, guidelines, and specifications and to provide management, with evidence that the development process is being carried out according to the stated objectives. A review is similar to an inspection or walkthrough, except that the review team also includes management. c. List any four software design concepts that span both traditional and objectoriented software development. (4) Abstraction, modularity, structural partitioning, information hiding, etc. d. What is structured programming? (4) The structural constructs to limit the procedural design of software to smaller number of predictable operations e. What is regression testing? Why is regression testing considered a problem for testers? (4) The purpose of regression testing is to ensure that bug fixes and new functionality introduced in a new version of a software do not adversely affect the correct functionality inherited from the previous version. Regression testing is considered as a problem as the existing test suite with probable additional test cases needs to be tested again and again whenever there is modification. The following difficulties occur in retesting: Large systems can take a long time to retest It can be difficult and time consuming to create the tests. It can be difficult and time consuming to evaluate the tests. Sometimes requires a person in the loop to create and evaluate the results. Cost of testing can reduce resources available for software improvements. IETE 1

f. What is software configuration management? (4) It is an umbrella activity applied throughout the software process. Define Baselines Define Software configuration items g. Explain the COCOMO model in brief. (4) Constructive cost model Software cost estimation model implemented in three models: basic, intermediate and detailed. Q.2 a. Why is software engineering considered a layered technology? Explain, with the help of a suitable diagram, the various layers of software engineering. (4) b. What is requirement elicitation? Explain, in brief, the various methods of requirement elicitation. (6) Activity that that helps to understand the problem to be solved, requirements are gathered by various methods Most communication intensive activity of software development. Name all methods of requirement elicitation c. Explain the waterfall model in detail. In what kind of projects this model is applicable? (8) Waterfall model is a sequential model. Its phases like requirement analysis & specification, design, implementation & unit testing, Integration and system testing, maintenance with diagram The model is applicable to only those projects where requirements have been settled as it expects complete and accurate requirements. Q.3 a. What is a data dictionary? Explain its purpose. (4) Repositories to store information about all data items defined in DFD. Define customer data items information including name, aliases, description, related data items, range of values, data structure definition. Used to create an ordered listing of all data items, create an ordered listing of a subset of data items, find a data item name from a description, design the software and test cases. IETE 2

b. Explain different symbols used for DFD. (4) symbols for data flow, process, source/sink, data store. c. The student result management system of an institute needs to be automated. Draw a context diagram for this system. (10) Q.4 a. What is a structured chart? What are the various notations used in a structured chart? (5) Method used for system design. Partitions a system into black boxes. Hierarchical format of a structured chart with diagram Notations for data, module, library module, physical storage, conditional call of module, repetitive call of module b. What is an interaction diagram in UML? Explain its all notations. What is its role in object oriented design? (6) shows an interaction consisting of a set of objects and their relationships including the messages. IETE 3

Address the dynamic view of the system Notations for entity object, interface object and control object. c. What is module cohesion? Identify & briefly explain various levels of module cohesion. (7) Measure of degree to which the elements of a module are functionally related. Types: Functional, sequential, communicational, procedural, temporal, logical and coincidental. Q.5 a. Explain any two concepts of object oriented programming. (4) Two concepts of object oriented programming like inheritance and polymorphism. b. What is basis path testing when is it used? Define an independent path. (4) Basis path testing is used for white box testing when there are thousands of paths in a flow graph of a program. Basis path testing provides a reduced set of paths to test the software. Basis path testing is the technique of selecting the paths that gives a basis set of execution paths through the program. An independent path is any path through the graph that introduces at least one new set of processing statements or new conditions. An independent path must move along at least one edge that has not been traversed before the path is defined c. A program takes an angle as input within range [0,360] and determines in which quadrant the angle lies. Design all test cases for this problem using equivalence class partitioning method. (10) 1. First we partition the domain of input as the valid input values and invalid values, getting the following classes: I 1 = {<Angle> : 0 Angle 360} I 2 = {<A,B,C> : Angle < 0} I 3 = {<A,B,C> : Angle >0} The test cases designed from these classes are shown below: Test Case Angle Expected Results Classes Covered Id by the test case 1 50 I Quadrant I 1 2-1 Invalid Input I 2 3 361 Invalid Input I 3 2. The classes can also be prepared based on the output criteria as shown below: IETE 4

O 1 = {<Angle>: First Quadrant, if 0 Angle 90 } O 2 = {<Angle>: Second Quadrant, if 91 Angle 180 } O 3 = {<Angle>: Third Quadrant, if 181 Angle 270 } O 4 = {<Angle>: Fourth Quadrant, if 271 Angle 360 } O 5 = {<Angle>: Invalid Angle}; However, O 5 is not sufficient to cover all invalid conditions this way. Therefore it must be further divided into equivalence classes as shown below: O 51 = {<Angle>: Invalid Angle, if Angle < 0} O 52 = {<Angle>: Invalid Angle, if Angle > 360} Now the test cases can be designed from above derived classes as shown below: Test Case Angle Expected Results Classes Covered Id by the test case 1 50 I Quadrant O 1 2 135 II Quadrant O 2 3 250 III Quadrant O 3 4 320 IV Quadrant O 4 5 370 Invalid Angle O 51 6-1 Invalid Angle O 52 Q.6 a. What is the need of coding standards in an organization? List any four commonly used conventions for naming followed in Java Programming. (6) b. Explain Boehm s model for software maintenance. (6) model as a closed loop cycle with diagram. c. Explain the change control process as a part of software configuration management. (6) version. Change control process flow starting from the need for change to distribute the new Q.7 a. Consider a project with following parameters: EI = 50, EO = 40, EQ = 35, ILF = 06, ELF = 04. Assume all weighing factors are average. In addition system requires, critical performance, average end user efficiency, moderate distributed data processing, and critical data communication. Other GSCs are incidental. Compute the function points using FPA. (8) UFP = 50*4+40*5+35*4+6*10+4*7 = 628 TDI = 4+3+2+4+10*1 = 130 VAF = 130*0.01 +0.065 = 1.365 AFP = 628*1.365 = 857.22 IETE 5

b. How do PERT and CPM helps in project scheduling? (4) program evaluation & review technique critical path method with appropriate diagrams. Help in tracking the project with timelines. N = 100 i = 60 Ø = 0.03 c. There are 100 errors estimated to be present in a program. However, 80 errors have been experienced. Use Jelinski-Moranda model to calculate failure intensity with a given Ø = 0.03. What will be the failure intensity after the experience of 80 errors? (6) Since ƛ(t) = Ø (N i + 1) = 0.03 (100 60 + 1) = 1.23 failures/cpu hr. After 80 failures ƛ(t) = 0.03(100 80 + 1) = 0.63 failures/cpu hr Hence there is continuous decrease in the failure intensity as the number of failures experienced increases. TEXT BOOKS I. Roger Pressman, Software Engineering: A Practitioners approach, Sixth Edition, McGraw- Hill International Edition II. Ian Sommerville, Software Engineering, Seventh Edition, Pearson Education India III. Carlo Ghezzi, Mehdi Jazayeri and Dino Mandrioli, Fundamental of Software Engineering, Second Edition, Pearson Education India IETE 6