58
M.Tech. (Full Time) - SOFTWARE ENGINEERING CURRICULUM & SYLLABUS 2013 – 2014 DEPARTMENT OF SOFTWARE ENGINEERING FACULTY OF ENGINEERING AND TECHNOLOGY SRM UNIVERSITY SRM NAGAR, KATTANKULATHUR – 603 203

M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

  • Upload
    voduong

  • View
    229

  • Download
    1

Embed Size (px)

Citation preview

Page 1: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

M.Tech. (Full Time) - SOFTWARE ENGINEERING

CURRICULUM & SYLLABUS

2013 – 2014

DEPARTMENT OF SOFTWARE ENGINEERING

FACULTY OF ENGINEERING AND TECHNOLOGY

SRM UNIVERSITY

SRM NAGAR, KATTANKULATHUR – 603 203

Page 2: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

1

DEPARTMENT OF SOFTWARE ENGINEERING

M.Tech. (SOFTWARE ENGINEERING)

CURRICULUM – 2013-2014

COURSE CODE COURSE NAME L T P C

I SEMESTER

MA2011 Stochastic Processes & Queuing Theory

3 0 0 3

SE2001 Software Engineering 3 0 2 4

SE2002 Pattern Oriented Software Architecture 3 0 2 4

SE2003 Software Project Management 4 0 0 4

Elective – I 3 0 0 3

II SEMESTER

SE2004 Agile Software Process 4 0 0 4

SE2005 Software Testing 3 0 2 4

SE2006 Software Process Maturity Model 4 0 0 4

Elective– II 3 0 0 3

Elective-III 3 0 0 3

III SEMESTER

Elective – IV 3 0 0 3

Elective – V 3 0 0 3

Elective –VI 3 0 0 3

Elective –VII (Interdisciplinary) 3 0 0 3

SE2047 Seminar 0 0 1 1

PROJECT

SE2049 Project Work Phase – I 0 0 12 6

IV SEMESTER

SE2050 Project Work Phase – II 0 0 32 16

TOTAL CREDITS 71

TOTAL CREDITS TO BE EARNED FOR THE AWARD OF M.TECH DEGREE: 71

CONTACT HOUR/CREDIT:

L: Lecture Hours per week T: Tutorial Hours per week

P: Practical Hours per week C: Credit

Page 3: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

2

ELECTIVES FOE FIRST SEMESTER

COURSE CODE COURSE NAME L T P C

SE2101 Database Management System 3 0 0 3

SE2102 Principles of Compiler Design and Operating Systems

3 0 0 3

SE2103 Object Oriented Programming (C++ , JAVA)

3 0 0 3

SE2104 Computer Networks & Network Security

3 0 0 3

ELECTIVES FOE SECOND SEMESTER

COURSE CODE COURSE NAME L T P C

SE2105 Distributed Operating Systems 3 0 0 3

SE2106 E-Commerce 3 0 0 3

SE2107 Software Reliability 3 0 0 3

SE2108 Software Agents 3 0 0 3

SE2109 Design Patterns 3 0 0 3

SE2110 Software Measurements and Metrics 3 0 0 3

SE2111 Data Warehousing and Data Mining 3 0 0 3

SE2112 Internet Programming 3 0 0 3

ELECTIVES FOE THIRD SEMESTER

COURSE CODE COURSE NAME L T P C

SE2113 Software Quality Management 3 0 0 3

SE2114 Component Based System Design 3 0 0 3

SE2115 Human Interface System Design 3 0 0 3

SE2116 Service Oriented Architecture 3 0 0 3

SE2117 Software Configuration Management 3 0 0 3

SE2118 Decision Support Systems 3 0 0 3

SE2119 Web Services 3 0 0 3

SE2120 Language Technologies 3 0 0 3

SE2121 Analysis of Software Artifacts 3 0 0 3

SE2122 Cloud Computing 3 0 0 3

Page 4: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

3

COURSE CODE COURSE NAME L T P C

SE2123 Personal Software Process 3 0 0 3

SE2124 Embedded System 3 0 0 3

Supportive Course

COURSE CODE COURSE NAME L T P C

MA2011 Stochastic Processes & Queuing Theory

3 0 0 3

Inter Disciplinary Electives

Course code Course Name L T P C

(Elective is offered in Third Semester) 3 0 0 3

NOTE:

Students have to register for the courses as per the following guidelines:

Sl.

No.

Category Credits

I

Semester

II

Semester

III

Semester

IV

Semester

Category

total

1. Core courses 12 ( 3 courses)

12 ( 3 courses)

--- --- 24

2. Program Elective courses

18 (in I to III semesters) --- 18

3. Interdisciplinary elective courses (any one program elective from other programs)

3 (One course to be taken in Semester I or II or III)

3

4. Supportive courses - mandatory

3 (One course to be taken in Semester I or II or III)

--- 3

5. Seminar --- --- 1 --- 1

6. Project work --- --- 06 16 22

Total 71

Page 5: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

4

SEMESTER-I

MA2011

STOCHASTIC PROCESSES & QUEUEING

THEORY L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Nil

PURPOSE

To impart knowledge on probability concepts to study their applications in stochastic processes & queueing theory

OBJECTIVES

1. Compute the characteristics of the random variable given the probabilities

2. Understand and apply various distribution

3. Solve cases of different Stochastic processes along with their properties.

4. Use discrete time finite state Markov chains

5. Gain sufficient knowledge in principles of queueing theory

UNIT I-RANDOM VARIABLES (9 hours)

One dimensional and two dimensional Random Variables – Characteristics of Random Variables : Expectation, Moments.

UNIT II-THEORETICAL DISTRIBUTIONS (9 hours)

Discrete : Binomial, Poisson, Negative Binomial, Geometric, Uniform Distributions. Continuous: Uniform, Exponential, Erlang and Gamma, Weibull Distributions.

UNIT III-STOCHASTIC PROCESSES (9 hours)

Classification of Stochastic Processes – Bernoulli process – Poisson process – Pure birth process – Birth and Death process.

UNIT IV-MARKOV CHAINS (9 hours)

Introduction – Discrete-Parameter Markov Chains – Transition Probability Matrix – Chapman Kolmogorov Theorem – State classification and limiting distributions.

Page 6: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

5

UNIT V-QUEUING THEORY (9 hours)

Introduction – Characteristics of Markovian Single server and Multi server queuing models [(M/M/1) : (∞ / FIFO), (M/M/1) : (N / FIFO), (M/M/s) : (∞ /FIFO)] – M/G/1 Queuing System – Pollaczek Khinchin formula.

REFERENCES

1. Kishore.S.Trivedi, “Probability & Statistics with Reliability, Queuing and Computer Science Applications, PHI, New Delhi, 1995.

2. Veerajan T, Probability, “Statistics and Random Processes”, 3rd Edition Tata McGraw Hill, New Delhi,2002.

3. Gupta S.C and Kapoor V.K, “Fundamentals of Mathematical Statistics”, 9th revised edition, Sultan Chand & Co., New Delhi 2003.

4. Gross.D and Harris.C.M. “Fundementals of Queuing theory”, John Wiley and Sons, 1985.

5. Allen.A.O., “Probability, Statistics and Queuing Theory”, Academic Press, 1981.

SE2001

SOFTWARE ENGINEERING L T P C

Total Contact Hours - 75 3 0 2 4

Prerequisite

Nil

PURPOSE

The main purpose of this course is to impart knowledge on the basic principles of software development life cycle.

INSTRUCTIONAL OBJECTIVES

1. To understand the software life cycle models

2. To understand the importance of the software development process

3. To understand the importance of modeling and modeling languages

4. To design and develop correct and robust software products

5 To understand business requirements pertaining to Software development

UNIT I - INTRODUCTION (9 hours)

Software Engineering-Software Process- Generic process model-Prescriptive process model-specialized, unified process-Agile development-Agile Process-Extreme Programming- Other agile Process models-Software engineering Knowledge-core Principles-Principles that guide each framework Activity.

Page 7: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

6

UNIT II - SOFTWARE REQUIREMENTS AND ANALYSIS (9 hours)

Requirements Engineering-Establishing the Groundwork-Eliciting Requirements-Developing use cases-Building the requirements model-Negotiating, validating Requirements-Requirements Analysis-Requirements Modeling Strategies.

UNIT III - SOFTWARE DESIGN (9 hours)

Design Diagrams: Use Case Diagrams - Class Diagrams - Interaction Diagrams - State chart Diagrams - Activity Diagrams - Package Diagrams - Component Diagrams – Deployment Diagrams - Diagram Organization- Diagram Extensions. Design Process- Design concepts : Abstraction, Architecture, patterns, Separation of Concerns, Modularity, Information Hiding, Functional Independence, Refinement, Aspects, Refactoring, Object Oriented Design Concepts, Design Classes- Design Model: Data, Architectural, Interface, Component, Deployment Level Design Elements .

UNIT IV - SOFTWARE IMPLEMENTATION (9 hours)

Structured coding Techniques- Coding Styles-Standards and Guidelines- Documentation Guidelines-Modern Programming Language Features: Type checking-User defined data types-Data Abstraction-Exception Handling-Concurrency Mechanism.

UNIT V - SOFTWARE TESTING AND MAINTENANC (9 hours)

TESTING - Software Quality- Software Quality Dilemma- Achieving Software Quality- Testing: Strategic Approach to software Testing- Strategic Issues- Testing: Strategies for Conventional Software, Object oriented software, Web Apps-Validating Testing- System Testing- Art of Debugging. MAINTENANCE - Software Maintenance-Software Supportability- Reengineering- Business Process Reengineering- Software Reengineering- Reverse Engineering- Restructuring- Forward Engineering- Economics of Reengineering LIST OF EXPERIMENTS (30 hours)

Using Rational Rose do the following for a given source code. 1. Understand SRS concept and its documentation. 2. Design a Use Case Diagram for the application. 3. Design an Activity Diagram. 4. Design a Sequence, Collaboration, and Class Diagram. 5. Source Code analysis. 6. Testing the application by Rational Functional Tester.

Page 8: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

7

7. Understand Maintenance activity (change, configuration management) and document it.

REFERENCES

1. Roger S. Pressman, “Software Engineering – A Practitioner’s Approach”, Tata McGraw-Hill seventh edition, 2009.

2. Richard Fairley, “Software Engineering Concepts” –, Tata Mcgraw Hill, 2008.

3. Ian Sommerville, “Software Engineering”, Seventh Edition, Pearson Education Asia, 2007.

4. Gopalaswamy Ramesh, Ramesh Bhattiprolu, “Software Maintenance” Tata Mcgraw Hill,2003.

5. Shari Lwarence Pfleeger, Joanne M.Atlee “Software Engineering Theory and Practice” , Third Edition, Pearson Education, 2006.

6. Alistair Cockburn, "Agile Software Development”, First Edition, Pearson Education Asia, 2001.

7. Hans Van Vliet “Software Engineering: Principles and Practices” –, Wiley; 3 edition, 2008.

SE2002

PATTERN ORIENTED SOFTWARE

ARCHITECTURE L T P C

Total Hours - 75 3 0 2 4

Prerequisite

Nil

PURPOSE

The course gives an insight of the most commonly used software architecture and design patterns and their applications

INSTRUCTIONAL OBJECTIVES

1. The students get basic knowledge of patterns and description of patterns

2. To understand basic architectural patterns

3. To get an insight on the design patterns and mining.

UNIT I-INTRODUCTION TO SOFTWARE ARCHITECTURE (9 hours)

Introduction – Software architecture – An engineering discipline for software - Architectural Styles – Pipes and filters – Layered Systems - Black board –Repositories - Process control - Distributed system – Interactive system – Adaptive system

Page 9: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

8

UNIT II-DESIGN PATTERNS & PATTERN SYSTEM (9 hours)

Introduction to patterns – Pattern category – Relationship between patterns – Pattern Description – Patterns software architecture -Structural decomposition – Organization of work – Access control – Management and Communication – Idioms, Pattern system – Pattern Classification – Pattern Selection – implementation – Evolution – Patterns in Software architecture – Non –functional properties – Techniques of Software architecture. UNIT III-COMMUNITY, MINING, CONCURRENT & NETWORKED (9 hours)

Roots – Community – Pattern Mining - Organizing and Indexing – Methods and tools – Algorithm – Data Structures and Patterns – Formalizing Patterns, Concurrent and Networked Objects, Service Access and Configuration Patterns UNIT IV-EVENT HANDLING & SYNCHRONIZATION PATTERNS (9 hours)

Event Handling Patterns – Reactor, Proactor, Asyn Completion Tokens, Acceptor-Connector, Synchronization Patterns – Locking – Scoped, Strategized, Thread - safe Interface, Double-Checked Locking Optimization. UNIT V-CONCURRENCY & WEAVING PATTERNS (9 hours)

Objects – Active, Monitor, Half- Sync, Async, Leader/ Followers, Threads, Weaving – Individual Patterns, Middleware, Concurrency and Networking, Patterns Language Vs Pattern System. Past, Present and Future of Patterns. PRACTICAL: The laboratory shall include development of systems by applying the Software Engineering principles and methods for specific applications (30 hours)

REFERENCES

1. Frank Buschmann, Kelvin Henney & Douglas Schimdt, “Pattern-Oriented Software Architecture - A System of Patterns”, Volume 1, Wiley,2007.

2. Frank Buschmann, Kelvin Henney & Douglas Schimdt, “Pattern-Oriented Software Architecture – Pattern for Concurrent and Networked Objects”, Volume 2 ,Wiley,2000.

3. Mary Shaw , David Garlan , “Software architecture perspectives on a Emerging Dicipline”,EEE,PH1,1996.

Page 10: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

9

SE2002

SOFTWARE PROJECT MANAGEMENT L T P C

Total Contact Hours - 60 4 0 0 4

Prerequisite

Software Engineering Principles

PURPOSE

The course gives an insight of the most commonly used software architecture and design patterns and their applications

INSTRUCTIONAL OBJECTIVES

1. To understand Software Project Models and Software Management Concepts.

2. To understand the various methods of Cost Estimation.

3. To Study about Software Quality Management.

4. To Study about Software Metrics.

5. To understand Project Evaluation.

UNIT I - PROJECT CONCEPTS AND ITS MANAGEMENT (12 hours)

Project life cycle models-ISO 9001 model-Capability Maturity Model-Project Planning-Project tracking-Project closure. Evolution of Software Economics – Software Management Process Framework: Phases, Artifacts, Workflows, Checkpoints – Software Management Disciplines: Planning / Project Organization and Responsibilities / Automation / Project Control – Modern Project Profiles UNIT II - COST ESTIMATION (12 hours)

Problems in Software Estimation – Algorithmic Cost Estimation Process, Function Points, SLIM (Software Life cycle Management), COCOMO II (Constructive Cost Model) – Estimating Web Application Development – Concepts of Finance, Activity Based Costing and Economic Value Added (EVA) – Balanced Score Card.

UNIT III - OFTWARE QUALITY MANAGEMENT (12 hours)

Software Quality Factors – Software Quality Components – Software Quality Plan – Software Quality Metrics – Software Quality Costs – Software Quality Assurance Standard – Certification – Assessment.

UNIT IV - SOFTWARE MANAGEMENT AND METRICS (12 hours)

Software Configuration Management – Risk Management: Risk Assessment: Identification / Analysis / Prioritization – Risk Control: Planning / Resolution / Monitoring – Failure Mode and Effects Analysis (FMEA) – Defect Management –

Page 11: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

10

Cost Management.Software Metrics – Classification of Software Metrics: Product Metrics: Size Metrics, Complexity Metrics, Halstead’s Product Metrics, Quality Metrics, and Process metrics.

UNIT V - PROJECT EVALUATION AND EMERGING TRENDS (12 hours)

Strategic Assessment–Technical Assessment–Cost Benefit Analysis–Cash Flow Forecasting–Cost Benefit Evaluation Technique–Risk Evaluation–Software Effort Estimation. Emerging Trends: Import of the internet on project Management –people Focused Process Models. REFERENCES

1. Ramesh Gopalaswamy , “Managing and global Software Projects”, Tata McGraw Hill Tenth Reprint, 2011.

2. Roger S.Pressman, “Software Engineering- A Practitioner’s Approach“, 7th Edition ,McGraw Hill, 2010.

3. Daniel Galin, “Software Quality Assurance: from Theory to Implementation”, Addison-Wesley, 2003.

4. Bob hughes and Mike Cotterell, “Software Project Management” second edition,1999.

5. Royce, W. “Software Project Management: A Unified Framework”, Addison-Wesley, 1998.

6. Demarco, T. and Lister, T. “Peopleware: Productive Projects and Teams, 2nd Ed.”, Dorset House,1999.

7. Fenton, N.E., and Pfleeger, S.L.. “Software Metrics: A Rigorous and Practical Approach, Revised” Brooks Cole, 1998.

8. Kaplan, R.S., Norton, D.P. “The Balanced Scorecard: Translating Strategy into Action”, Harvard Business School Press, 1996.

9. Boehm, B. W. "Software Risk Management: Principles and Practices" in IEEE Software, January 1991, pp32-41.

10. Grant, J.L. “Foundations of Economic Value Added”, John Wiley & Sons, 1997.

11. Cooper, R., “The Rise of Activity-Based Costing- PartOne: What is an Activity-Based Cost System” Journal of Cost Management, Vol.2, No.2 (Summer 1988), pp.45 – 54.

ELECTIVE - I L T P C

Total Contact Hours - 45 3 0 0 3

Students to choose one Elective course from the list of courses mentioned in the curriculum

Page 12: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

11

SEMESTER – II

SE2004

AGILE SOFTWARE PROCESS L T P C

Total Hours : 60 4 0 0 4

Prerequisites:

Software Engineering Principles

PURPOSE

This course imparts knowledge to students in the basic concepts of Agile Software Process, methodology and its development.

OBJECTIVES

1. To understand the basic concepts of Agile Software Process.

2. To gain knowledge in the area of various Agile Methodologies.

3. To develop Agile Software Process

4. To know the principles of Agile Testing

UNIT I-INTRODUCTION (12 hours)

Software is new product development – Iterative development – Risk-Driven and Client-Driven iterative planning – Time boxed iterative development – During the iteration, No changes from external stakeholders – Evolutionary and adaptive development - Evolutionary requirements analysis – Early “Top Ten” high-level requirements and skilful analysis – Evolutionary and adaptive planning – Incremental delivery – Evolutionary delivery – The most common mistake – Specific iterative and Evolutionary methods.

UNIT II-AGILE AND ITS SIGNIFICANCE (12 hours)

Agile development – Classification of methods – The agile manifesto and principles – Agile project management – Embrace communication and feedback – Simple practices and project tools – Empirical Vs defined and prescriptive process – Principle-based versus Rule-Based – Sustainable discipline: The human touch – Team as a complex adaptive system – Agile hype – Specific agile methods. The facts of change on software projects – Key motivations for iterative development – Meeting the requirements challenge iteratively – Problems with the waterfall. Research evidence – Early historical project evidence – Standards-Body evidence – Expert and thought leader evidence – A Business case for iterative development – The historical accident of waterfall validity.

Page 13: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

12

UNIT III-AGILE METHODOLOGY (12 hours)

Method overview – Lifecycle – Work products, Roles and Practices values – Common mistakes and misunderstandings – Sample projects – Process mixtures – Adoption strategies – Fact versus fantasy – Strengths versus “Other” history.

UNIT IV-CASE STUDY (12 hours)

Agile – Motivation – Evidence – Scrum – Extreme Programming – Unified Process – Evo – Practice Tips.

UNIT V-AGILE PRACTICING AND TESTING (12 hours)

Project management – Environment – Requirements – Test – The agile alliances – The manifesto – Supporting the values – Agile testing – Nine principles and six concrete practices for testing on agile teams.

REFERENCES

1. Elisabeth Hendrickson, “Agile Testing” Quality Tree Software Inc 2008. 2. Craig Larman “Agile and Iterative Development – A Manager’s Guide”

Pearson Education – 2004. 3. Alistair “Agile Software Development series” Cockburn - 2001. 4. www.agileintro.wordpress.com/2008 5. www.serena.com/docs/repository/solutions/intro-to-agile-devel.pdf 6. www.qualitytree.com

SE2005

SOFTWARE TESTING L T P C

Total Hours - 75 3 0 2 4

Prerequisite

Nil

PURPOSE

The student should develop the basic skills in software testing by implementing various strategies of software testing in their project. They need to bring out the ways and means of controlling and monitoring testing activity

OBJECTIVES

1. The students learn to apply the testing strategies and methodologies in their projects

2. To understand test management strategies and tools for testing

3. A keen awareness on the open problems in software testing and maintenance

Page 14: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

13

UNIT I-TESTING BASICS (9 hours)

Testing as an engineering activity – Role of process in software quality – Testing as a process – Basic definitions – Software testing principles – The tester’s role in a software development organization – Origins of defects – Defect classes – The defect repository and test design – Defect examples – Developer / Tester support for developing a defect repository.

UNIT II-TEST CASE DESIGN (9 hours)

Introduction to testing design strategies – The smarter tester – Test case design strategies – Using black box approach to test case design – Random testing – Equivalence class partitioning – Boundary value analysis – Other black box test design approaches – Black box testing and COTS – Using white box approach to test design – Test adequacy criteria – Coverage and control flow graphs – Covering code logic – Paths – Their role in white box based test design – Additional white box test design approaches – Evaluating test adequacy criteria.

UNIT III-LEVELS OF TESTING (9 hours)

The need for levels of testing – Unit test – Unit test planning – Designing the unit tests – The class as a testable unit – The test harness – Running the unit tests and recording results – Integration tests – Designing integration tests – Integration test planning – System test – The different types – Regression testing – Alpha, beta and acceptance tests.

UNIT IV-TEST MANAGEMENT (9 hours)

Basic concepts – Testing, debugging goals, policies – Test planning – Test plan components – Test plan attachments – Locating test items – Reporting test results – The role of three groups in test planning and policy development – Process and the engineering disciplines – Introducing the test specialist – Skills needed by a test specialist – Building a testing group. UNIT V-CONTROLLING AND MONITORING (9 hours)

Defining terms – Measurements and milestones for controlling and monitoring – Status meetings – Reports and control issues – Criteria for test completion – SCM – Types of reviews – Developing a review program – Components of review plans – Reporting review results.

PRACTICAL (30 hours)

Page 15: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

14

LIST OF EXPERIMENTS

Using Testing Tool do the following Experiments for the given source code

1. Test Principles and Concepts 2. Test Management 3. Build the Test Environment 4. Test Planning Process 5. Test Design 6. Performing Tests 7. Defect Tracking and Correction 8. Acceptance Testing 9. Status of Testing 10. Test Reporting

REFERENCES

1. SrinivasanDesikan, Gopalaswamy Ramesh, “Software Testing: Principles and Practices”, Pearson 2012

2. Aditya P. Mathur, “Foundations of Software Testing”, Pearson, 2008 3. Paul Ammann, Jeff Offutt, “Introduction to Software Testing”, Cambridge

University Press, 2008 4. Paul C. Jorgensen, “Software Testing: A Craftsman's Approach”, Auerbach

Publications, 2008

SE2006

SOFTWARE PROCESS MATURITY

MODEL L T P C

Total Hours - 60 4 0 0 4

Prerequisite

Software Engineering Principles

PURPOSE

To know about the software process and Software Process Maturity Models

OBJECTIVES

1. To study about various Software process maturity models

2. To study about how to assess software process

3. To know about the key process areas of the software process

4. To study about software improvement sequences

Page 16: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

15

UNIT I - INTRODUCTION (12 hours) Software Process - Software Maturity Framework – Software process Improvement – Process Maturity levels – Principles of Software process Change – Software Process Assessment

UNIT II - CMM (12 hours) CMM Introduction – CMM Maturity Levels - Initial process- Repeatable Process – Defined Process – Managed Process – Optimizing Process. UNIT III - CMMI (12 hours)

Evolution of CMMI – CMMI Framework – CMMI for Development – Capability level – Maturity levels – Case Study

UNIT IV - TMM (12 hours)

Introduction to TMM – Structure of the TMM – Components of TMMi – Generic Goals and Generic Practices – Process areas for Generic practices - TMMi Maturity Levels – Initial – Managed – Defined – Management and Measurement – Optimization.

UNIT V - AGILE MATURITY MODEL (12 hours) Agile Software Development – Process Improvement framework for Agile Software Development – Intial Level – Explored Level – Defined level – Improved Level – Sustained Level - Software Process Improvement for Agile Software Development Practices.

REFERENCES

1. Watts S. Humphrey “Managing the Software Process”, Pearson Education, 2008

2. Marry Beth Chrissis, Mike Konnard and Sandy Shrum, “CMMI : guidelines for Process Integration and Product Improvement”, Addison Wesley, 3rd Edition, 2011.

3. Mark. C. Paulk, “CMM: Guidelines for Improving the Software Process” Addison-Wesley, 2011.

Page 17: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

16

L T P C

ELECTIVE - II 3 0 0 3

Total Contact Hours - 45

L T P C

ELECTIVE - III 3 0 0 3

Total Contact Hours - 45

SEMESTER III

L T P C

ELECTIVE – IV 3 0 0 3

Total Contact Hours - 45

L T P C

ELECTIVE – V 3 0 0 3

Total Contact Hours - 45

L T P C

ELECTIVE - VI 3 0 0 3

Total Contact Hours - 45

L T P C

ELECTIVE – VII (Inter Disciplinary) 3 0 0 3

Total Contact Hours - 45

Page 18: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

17

SE2047 SEMINAR L T P C

0 0 1 1

PURPOSE

To train the students in preparing and presenting technical topics.

INSTRUCTIONAL OBJECTIVES

The student shall be capable of identifying topics of interest related to the program of study and prepare and make presentation before an enlightened audience.

The students are expected to give at least two presentations on their topics of interest which will be assessed by a committee constituted for this purpose. This course is mandatory and a student has to pass the course to become eligible for the award of degree. Marks will be awarded out of 100 and appropriate grades assigned as per the regulations L T P C

SE2049 PROJECT WORK PHASE I

(III SEMESTER)

0 0 12 6

SE2050 PROJECT WORK PHASE II

(IV SEMESTER)

0 0 32 16

PURPOSE

To undertake research in an area related to the program of study

INSTRUCTIONAL OBJECTIVE The student shall be capable of identifying a problem related to the program of study and carry out wholesome research on it leading to findings which will facilitate development of a new/improved product, process for the benefit of the society.

M.Tech projects should be socially relevant and research oriented ones. Each student is expected to do an individual project. The project work is carried out in two phases – Phase I in III semester and Phase II in IV semester. Phase II of the project work shall be in continuation of Phase I only. At the completion of a project the student will submit a project report, which will be evaluated (end semester assessment) by duly appointed examiner(s). This evaluation will be based on the project report and a viva voce examination on the project. The method of assessment for both Phase I and Phase II is shown in the following table:

Page 19: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

18

Assessment Tool Weightage

In- semester I review 10% II review 15% III review 35%

End semester Final viva voce examination

40%

Student will be allowed to appear in the final viva voce examination only if he / she has submitted his / her project work in the form of paper for presentation / publication in a conference / journal and produced the proof of acknowledgement of receipt of paper from the organizers / publishers.

ELECTIVES FOR FIRST SEMESTER

SE2101

DATABASE MANAGEMENT SYSTEM L T P C

Total Hours – 45 3 0 0 3

Prerequisite

Nil

PURPOSE

The student should develop skills and understanding in the design methodology for databases and verifying their structural correctness

INSTRUCTIONAL OBJECTIVES

1. To learn the fundamentals of data models and to conceptualize and depict a database system using ER diagram

2. To make a study of SQL and relational database design.

3. To know the fundamental concepts of transaction processing- concurrency control techniques and recovery procedure

4. To learn about Object Oriented databases and Web databases

UNIT I-INTRODUCTION (9 hours)

Overview of file systems and Database Systems - Software Architecture of a typical DBMS-Data Models, Schemas and Instances- ER and EER diagrams and Data Flow Diagrams. Database Administration and Control

UNIT II-RELATIONAL MODEL (9 hours)

The relational Model – The catalog- Types– Keys - Relational Algebra – Domain Relational Calculus – Tuple Relational Calculus - Fundamental operations –

Page 20: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

19

Additional Operations- SQL fundamentals - Integrity – Triggers - Security – Advanced SQL features –Embedded SQL– Dynamic SQL- Missing Information– Views – Introduction to Distributed Databases and Client/Server Databases

UNIT III-DATABASE DESIGN (9 hours)

Functional Dependencies – Non-loss Decomposition – Functional Dependencies – First, Second, Third Normal Forms, Dependency Preservation – Boyce / Codd Normal Form- Multi-valued Dependencies and Fourth Normal Form – Join Dependencies and Fifth Normal Form

UNIT IV-TRANSACTIONS (9 hours)

Transaction Concepts - Transaction Recovery – ACID Properties – System Recovery – Media Recovery – Two Phase Commit - Save Points – SQL Facilities for recovery – Concurrency – Need for Concurrency – Locking Protocols – Two Phase Locking – Intent Locking – Deadlock- Serializability – Recovery Isolation Levels – SQL Facilities for Concurrency.

UNIT V-ADVANCED DATABASE SYSTEMS (9 hours)

Semi-structured and Web databases - The World Wide Web- HTML- Architecture -XML, XML/QL - Database Connectivity-OODBMS - ORDBMS- Deductive Databases- Data Mining and Warehousing- Temporal and Spatial Databases - Mobile Databases.

REFERENCES

1. Abraham Silberschtz, Henry. F. Korth, and S.Sudharsan, “Database System Concepts”, 6th Edition, Tata McGraw Hill, 2010.

2. Ramez Elmasri, Shamkant B. And Navathe, “Fundamentals of Database Systems”,5th Edition, Addison Wesley,2008

3. Thomas Conolly, Carolyn Begg, “Database Systems”, 4th edition, Pearson Education, 2009

4. Seema Kedar, “Database Management Systems”, Technical Publications, 2008.

5. Chaanda Ray, “Distributed Database Systems”, Pearson Education, 2009.

Page 21: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

20

SE2102

PRINCIPLES OF COMPILER DESIGN AND

OPERATING SYSTEM L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Computer Organization and Architecture

PURPOSE

Every computer professional should have a basic understanding of how an operating system controls the computing resources and provide services to the users. This course provides an introduction to the operating system functions, design and implementation of a lexical analyzer & parser.

OBJECTIVES

1. To apply Structure and functions of OS

2. To apply Processes and Threads, Scheduling algorithms

3. The student needs to understand the Principles of concurrency and Memory management

4. The student will learn the fundamentals of I/O management and File systems

5. To understand, design and implement Lexical analyzer & parser

UNIT –I - INTRODUCTION TO COMPILER DESIGN (9 hours)

Compilers – Analysis of the source program – Phases of a compiler – Cousins of the Compiler – Grouping of Phases – Compiler construction tools – Lexical Analysis – Role of Lexical Analyzer – Specification of Tokens. UNIT II - PARSER & SYNTAX ANALYSIS (9 hours)

Role of the parser –Writing Grammars –Context-Free Grammars – Top Down parsing – Recursive Descent Parsing – Predictive Parsing – Bottom-up parsing – Shift Reduce Parsing – Operator Precedent Parsing – LR Parsers – SLR Parser – Canonical LR Parser- Syntax directed definitions – Construction of syntax trees

UNIT III - INTRODUCTION TO OPERATING SYSTEM (9 hours)

Computer System Overview-Basic Elements, Interrupts, Operating system overview-objectives and functions, Evolution of OS- Process States, Process Description and Process Control. Processes and Threads, Types of Threads, Multithreading.

Page 22: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

21

UNIT IV - CONCURRENCY & MEMORY MANAGEMENT (9 hours) Principles of Concurrency - Mutual Exclusion, Semaphores, Deadlocks – prevention- avoidance – detection .Scheduling: Types of Scheduling – Scheduling algorithms. Memory management - Partitioning, Paging and Segmentation-Virtual memory UNIT V - INPUT/OUTPUT AND FILE SYSTEMS (9 hours)

I/O management and disk scheduling – I/O devices, organization of I/O functions; OS design issues, I/O buffering, disk scheduling, Disk cache. File management – Organization, Directories, File sharing, and Record blocking, secondary storage management. REFERENCES

1. William Stallings, “Operating Systems – Internals and Design Principles”, Prentice Hall, 7th Edition, 2011.

2. Andrew S. Tannenbaum & Albert S. Woodhull, “Operating System Design and Implementation”, Prentice Hall , 3rd Edition, 2006.

3. Alfred Aho, Ravi Sethi, and Jeffrey D Ullman, “Compilers Principles, Techniques and Tools”, Pearson Education Asia, 2010.

4. Allen I. Holub, “Compiler Design in C”, Prentice Hall of India, 2003. 5. C. N. Fischer and R. J. LeBlanc, “Crafting a compiler with C”, Benjamin

Cummings, 2003. 6. Andrew S. Tannenbaum, “Modern Operating Systems”, Prentice Hall,3rd

Edition,2007. 7. Gary J.Nutt, “Operating Systems”, Pearson/Addison Wesley, 3rd Edition

2004. 8. http://os-book.com

SE2103 OBJECT ORIENTED PROGRAMMING

( C++ , JAVA) L T P C

Total Hours – 45 3 0 0 3

Prerequisite

Programming in C

PURPOSE

The course provide insight knowledge about programming language (C++ and JAVA)

Page 23: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

22

INSTRUCTIONAL OBJECTIVES

1. To learn the fundamentals of Object Oriented Programming

2. To understand the concepts of Classes & Objects in C++ and Java

3. To understand the concept of static and dynamic polymorphism in C++ and Java.

4. To understand the concept of streams in C++ and Java.

5. To understand the concept of exception handling technique in C++ and Java

UNIT I-INTRODUCTION TO OOP (9 hours) Overview of C++ - classes - structures - union - friend function - friend class - inline function - constructors - static members - scope resolution operator - passing objects to functions - function returning objects -Arrays - pointers - this pointer - references - dynamic memory allocation UNIT II-OVERLOADING & INHERITANCE (9 hours) Function overloading - default arguments - overloading constructors - pointers to functions Operator overloading - member operator function - friend operator function - type conversion - inheritance - types of inheritance - virtual base class - polymorphism - virtual function. UNIT III-TEMPLATES & EXCEPTION (9 hours)

Class templates and generic classes - function templates and generic functions - - exception handling - derived class exception - exception handling functions - Streams - formatted I/O with its class functions and manipulators - creating own manipulators - file I/O - conversion functions- standard template library. UNIT IV-INTRODUCTION FOR JAVA (9 hours)

JAVA Basics: Importance and features of java- Modifiers- Access Controls-Data types- Expressions-Declarations-Statements- classes and objects and Control Structures-Program Structures-String handling-Packages-Interfaces-Working with java.util Package- Garbage Collection-Object Class - Exception Handling, I/O and JDBC: Exception Handling: Fundamentals exception types- uncaught exceptions-throw- throw final- built in exception- creating your own exceptions.

UNIT V-JAVA APPLET (9 hours) Input Stream and Output Stream: Streams,-Byte and Character stream- Predefined streams-AWT & Event Handling: Creating User interface with AWT- Applets-

Page 24: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

23

Applet Life Cycle- Simple Graphics-Fonts and Colors- Events- Listeners- Components- Containers- Working with Layouts-Image Processing- AWT Exceptions Delegation Event Model- Event Classes- Event Listener Interfaces- Adapter and Inner Class. REFERENCES

1. Balagurusamy E, “Object Oriented Programming with C++”, 4/E, TMG, 2011.

2. Hubbard, “Programming with C++”, 3/e, Schaum Outline Series, TMH, 2010.

3. Thomas Wu- “An Introduction to Object Oriented Programming with Java – Special” Indian Edition 5th 2010.

4. Balagurusamy E, “Programming with Java: A Primer”, 4th Edition, Tata Mcgraw Hill, 2009.

SE2104

COMPUTER NETWORKS & NETWORKS

SECURITY L T P C

Total Hours – 45 3 0 0 3

Prerequisite

Nil

PURPOSE

This course provides an understanding of various principles, protocols and design aspects of computer networking. Also emphasizes about the various security techniques in networks

INSTRUCTIONAL OBJECTIVES

1. To understand the concepts of data communications and the functions of different layers.

2. To make the students to get familiarized with different protocols and network components.

3. To introduce IEEE standards employed in computer networking.

4. To Apply Encryption techniques and key generation techniques

5. To learn about Authentication, Intrusion, Filtering Analysis and Security measures

UNIT I-COMPUTER NETWORKS & DATA LINK LAYER (9 hours)

Network Hardware - Network Software - Reference Models - Physical Layer – Data link layer, Design issues – Error Detection and Correction – Elementary data

Page 25: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

24

link protocol – Sliding window protocol. Medium Access Control - Channel Allocation Problem – Multiple Access protocol – Ethernet – Wireless LANs – Broadband wireless - Blue tooth – Data Link Layer Switching- Wireless Communications. UNIT II-NETWORK LAYER (9 hours)

Design Issues – Routing Algorithms: Optimality principle, shortest path routing, flooding, distance vector routing, link state routing, hierarchical routing, broadcast routing, multicast routing –routing for mobile hosts –Routing in adhoc networks- Congestion Control Algorithms – QOS – Internetworking - Network Layer in Internet. UNIT III-TRANSPORT & APPLICATION LAYER (9 hours)

Transport Service – Elements of Transport Protocol - Simple transport Protocol – Internet transport Protocols: TCP and UDP – Performance Issues, DNS – Electronic Mail – WWW – Multimedia. Security: Digital Signature – Mail Security – Web Security-- Firewalls. UNIT IV-NETWORK SECURITY AND CRYPTOGRAPHY (9 hours)

Network security issues - Basic Network security objective & Threats - Security services the trusted N/W interpretation & Distributed systems. Firewalls - Network firewalls – Gateway and Types. Security attacks– services and mechanism, encryption model - Steganography - classical encryption techniques and Algorithms – DES, public key cryptosystems, RSA, Diffie- Hellman key exchange – Hash & Kerberos. UNIT V-WEB SECURITY (9 hours)

E-mail security – PGP, S/MIME - IP security, web security- SSL - TLS - secure electronic transactions - intruders- higher wall design principles - trusted systems, Personal Computer Security Management - Unix Security Management - Risk Analysis - Security Planning Legal and Ethical Issues : Computer Crime, Ethical Issues in Computer Security REFERENCES

1. James F. Kurose and Keith W. Ross, “Computer Networking: A Top-Down Approach Featuring the Internet”, Pearson Education, Fifth Edition 2013.

2. Andrew S. Tanenbaum, “Computer Networks”, Pearson, Fifth Edition, 2012. 3. Behrouz A. Forouzan, “Data communication and Networking”, Tata McGraw-

Hill, Fourth Edition 2011.

Page 26: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

25

4. William Stallings, “Data and Computer Communication”, Eighth Edition, Pearson Education, 2008.

5. William Stallings, “Cryptography and network security” - Principles and practice, fifth edition Pearson education Asia, Prentice Hall of India, 2011.

6. Stallings, “Network security: Essentials, applications and standards”, fourth edition Pearson education, 2011.

7. Gregory B. White; Eric A. Fisch; Udo W. Pooch, “Computer System & Network Security”, CRC press, 1995.

8. Cormac Long, “IP network design”, Tata McGraw Hill, 2001.

ELECTIVES FOR SECOND SEMESTER

SE2105

DISTRIBUTED OPERATING SYSTEM L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Operating Systems

PURPOSE

This course provides in-depth knowledge in Advanced Operating System concepts

OBJECTIVES

1. To apply the basic concepts of Operating System principles

2. To emphasizes on Distributed Computing Techniques, Synchronous and Processes

3. The students must fundamentally understand about the Shared Data Access, Files

UNIT I-OVERVIEW OF OPERATING SYSTEMS (9 hours) Introduction – overview of operating system concepts – Process management and Scheduling, Memory management :partitioning, paging, segmentation, virtual memory, Device and File management Databases. UNIT II-DISTRIBUTED COMPUTING (9 hours)

Introduction - Distributed Systems – Hardware and Software concepts – Design issues; Communication in Distributed systems: Layered protocols - ATM networks - Client Server model – Remote Procedure Calls- Group communication Tools

Page 27: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

26

UNIT III-SYNCHRONIZATION AND PROCESSES (9 hours) Synchronization: Clock synchronization – Mutual exclusion – Election algorithms, - Atomic transactions – Deadlocks; Processes: Threads – System models – processor allocation –Scheduling – Fault tolerance – Real time distributed systems. UNIT IV-SHARED MEMORY AND FILE SYSTEMS (9 hours) Shared memory : Consistency models – Page based distributed shared memory – Shared variables– Object based distributed shared memory; Distributed File Systems : Design and Implementation UNIT V-CASE STUDY AMOEBA & MACH (9 hours) Introduction to Amoeba – Object and Capabilities – memory management – Communication –Amoeba Servers. Introduction to Mach – Process management – Memory Management – Communication REFERENCES

1. Andrew S Tanenbaum , “Distributed Operating Systems”, Pearson Education India, 2008

2. Mukesh Singhal, Niranjan G Shivratri “Advanced Concepts in Operating Systems”, McGraw Hill International 2002.

3. Pradeep K Sinha , “Distributed Operating Systems Concepts and Design”, PHI, 2002.

4. http://www.seas.gwu.edu/~jstanton/courses/cs251/ 5. http://cse.yeditepe.edu.tr/~sbaydere/courses_new/cse532/ 6. http://www.cs.odu.edu/~price/cs471/notes/index.html

SE2106

E-COMMERCE TECHNOLOGY L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Computer Networks

PURPOSE

The purpose of the course is to impart knowledge on E-Commerce and its various applications

INSTRUCTIONAL OBJECTIVES

1. Student will able to understand the impact of E-Commerce and applications of E-Commerce

Page 28: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

27

2. Student will able to understand E-Commerce framework and business model applications of E-Commerce

3. Student will able to understand e-payment mechanisms

4. Student will able to apply security algorithms

5. Student will able to familiar with marketing and advertising techniques

UNIT I-INTRODUCTION AND APPLICATIONS (9 hours)

Introduction to E- Commerce – Benefits and Impact of E- Commerce - Classification of E- Commerce – Application of E-Commerce Technologies.

UNIT II-E COMMERCE MODELS AND PAYMENT SYSTEMS (9 hours)

Business Model – Classification of Business Models - Electronic Payment Systems – Online Payment Systems – Pre-paid and Post-paid Electronic Payment Systems – Case Study: SBI eRail and Online Payment for Railway Tickets.

UNIT III-ORGANIZATIONAL COMMERCE AND EDI (9 hours)

Electronic Data Interchange – EDI Applications in Business – EDI and E-Commerce– EDI standardization and Implementation – Internet based EDI – Case Study: Indian Customs and Excise Adopts Electronic Data Exchange.

UNIT IV-SECURITY (9 hours)

Security Issues – Security Services – Cryptology - Encryption Techniques – Security Protocols for Web Commerce – Case Study: Deployment of Information Security Infrastructure: Experience of IIM.

UNIT V-AGENTS AND MOBILE COMMERCE (9 hours)

Agents in E-Commerce – Types – Technologies – Standards and Protocols – Advertising and Marketing on the Internet – Overview of Mobile Commerce and its Applications – E-Commerce Strategy in Business Models and Internet Start-ups: A Business Case Study.

REFERENCES

1. Ravi Kalakota and Andrew B Whinston, “Frontiers of Electronic Commerce”, (Chapters 1,2,3,6-10,13) Pearson Education Asia, 2009

2. Bharat Baskar “Electronic commerce Framework, Technologies and Applications”, (Chapters 1,2,9,10,14,15) 3rd Edition Tata McGraw-Hill Edition, 2009

3. Judy Strauss and Raymond Frost , “ E Marketing “, PHI, 2008.

Page 29: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

28

SE2107

SOFTWARE RELIABILITY L T P C

Total Contact Hours – 45 3 0 0 3

Prerequisite

Software Testing , Software Quality Management

PURPOSE

This course will look at professional techniques for understanding, assessing and applying the software reliability models in software development systems.

INSTRUCTIONAL OBJECTIVES

1. To appreciate and understand scientific concepts of Software and Hardware Reliability

2. To apply Software Reliability Growth Models in Software Development

3. To emphasize the Application of Software Reliability Models

UNIT I-INTRODUCTION (9 hours)

Need and Concepts of Software Reliability, Failure and Faults – Prevention, Removal, Tolerance, Forecast, Dependability Concept – Failure Behavior, Characteristics, Maintenance Policy, Reliability and Availability Modeling, Reliability Evaluation UNIT II-SOFTWARE RELIABILITY MODELS (9 hours)

Introduction - Historical Perspective and Implementation, classification, limitations and issues, Exponential Failure Models – Jelinski-moranda model, Poisson, Musa, Exponential models, Weibull Model, Musa-okumoto Model, Bayseian Model – Littlewood verral Model, Phase Based Model

UNIT III-PREDICTION ANALYSIS (9 hours)

Model Disagreement and Inaccuracy – Short & Long Term Prediction, Model Accuracy, Analyzing Predictive Accuracy – Outcomes, PLR, U & Y Plot, Errors and Inaccuracy, Recalibration – Detecting Bias, Techniques, Power of Recalibration, Limitations in Present Techniques, Improvements. UNIT IV-THE OPERATIONAL PROFILE (9 hours)

Concepts and Development Procedures – Customer Type, User Type, System Mode, Functional and Operational Profile, Test Selection - Selecting Operations, Regression Test, Special Issues – Indirect Input Variables, Updating, Distributed

Page 30: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

29

system, CASE STUDY - Application of DEFINITY & FASTAR, Power Quality Resource System

UNIT V-TESTING FOR RELIABILITY MEASUREMENT (9 hours)

Software Testing – Types, White and Black Box, Operational Profiles – Difficulties, Eatimating Reliability, Time/Structure based software reliability – Assumptions, Testing methods, Limits, Starvation , Coverage, Filtering, Microscopic Model of Software Risk.

REFERENCES

1. Patric D. T.O connor, “Practical Reliability Engineering”, 4th Edition, John Wesley & sons, 2003.

2. John D. Musa, “Software Reliability Engineering”, Tata McGraw Hill, 1999. 3. Michael Lyu, “Handbook of Software Reliability Engineering”, IEEE Computer

Society Press, ISBN: 0-07-039400-8, 1996.

SE2108

SOFTWARE AGENTS L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Engineering Principles

PURPOSE

This course provides a thorough understanding of agent related system development

INSTRUCTIONAL OBJECTIVES

1. To understand Agent development

2. Gain Knowledge in Multi agent and Intelligent agents

3. To Understand Agents and security

4. Gain Knowledge in Agent Applications

UNIT I-INTRODUCTION (9 hours) The agent landscape – The smart agent framework: Introduction – Initial concepts – Entities-Objects – Agents – Autonomy – Tropistic agent – Specification structure of SMART. – Agent relationships – An operational analysis of Agent relationships.

Page 31: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

30

UNIT II-SOCIOLOGICAL AGENTS (9 hours)

Sociological Agents - Autonomous Interaction - Contract Net as a global directed system – Computational Architecture for BDI agents – Evaluating social dependence networks – Normative agents.

UNIT III-INTELLIGENT AUTONOMOUS AGENTS AND COMMUNICATION

(9 hours)

Intelligent Agents –Deductive Reasoning Agents – Practical reasoning agents - Reactive agents – Hybrid Agents – Understanding Each other – Communicating – Methodologies

UNIT IV-AML (9 hours)

Modeling multi agent system with AML – JADE:Java Agent development frame work –wireless sensor networks and software Agents – Multi agent Planning Security and anonymity in agent systems.

UNIT V-APPLICATIONS OF AGENTS (9 hours) Multi Agent system: Theory approaches and NASA applications – Agent based control for multi-UAV information collection- Agent based decision support system for Glider pilots – Multi agent system in E- Health Territorial Emergencies – Software Agents for computer network security- Multi-Agent Systems, Ontologies and Negotiation for Dynamic Service Composition in Multi-Organizational Environmental Management.

REFERENCES 1. Mohammad Essaaidi, Maria Ganzha, and Marcin Paprzycki, “Software

Agents, Agent Systems and Their Applications”, IOS Press, 2012. 2. Mark d Inverno and Michael Luck, “Understanding Agent Systems”,

Springer,2010. 3. Michael Wooldridge, “An Introduction to Multi Agent Systems”, John Wiley &

Sons Ltd., 2009. 4. Lin Padgham, Michael Winikoff, “Developing Intelligent Agent Systems: A

Practical Guide”, John Wiley & Sons Ltd., 2004. 5. Bradshaw , “Software Agents” , MIT Press, 1997. 6. Richard Murch, Tony Johnson, “Intelligent Software Agents”, Prentice Hall,

2000.

Page 32: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

31

UNIT I-INTRODUCTION TO DESIGN PATTERNS (9 hours)

Design Patterns Arose from Architecture and Anthropology - Architectural to Software Design Patterns - Advantages of Design Patterns - Adapter Pattern - Strategy Pattern - Bridge Pattern - Abstract Factory Pattern

UNIT II-NEW PARADIGM OF DESIGN (9 hours)

Principles and Strategies of Design Patterns - Open-Closed Principle - Designing from Context - Encapsulating Variation. Commonality and Variability Analysis - Analysis Matrix - Decorator Pattern - Open Closed Principle – The Principle of encapsulating variation – Abstract Classes vs Interfaces

UNIT III-VALUES OF PATTERNS (9 hours)

Observer Pattern - Categories of Patterns - Template Method Pattern - Applying the Template Method to the Case Study - Using Template Method Pattern to Reduce Redundancy

UNIT IV-APPLYING DESIGN PATTERNS (9 hours) Design Patterns: Factories - Singleton Pattern and the Double-Checked Locking Pattern - Applying Singleton Pattern to Case Study. Object Pool Pattern -

SE2109

DESIGN PATTERNS L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Design , Software Architecture

PURPOSE

In software engineering, a design pattern is a general reusable solution to a commonly occurring problem in software design. This course teaches students advanced skills in object-oriented design and programming through learning common design patterns and refactoring software source code

INSTRUCTIONAL OBJECTIVES

1. Understand and be able to apply incremental/iterative development

2. Understand common design patterns

3. Be able to identify appropriate patterns for design problems

4. Be able to evaluate the quality of software source code

5. Be able to refactor badly designed program by properly using design patterns

Page 33: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

32

Management of Objects. Factory Method Pattern - Factory Method Pattern – Object Oriented Pool Pattern -

UNIT V-CASE STUDIES (9 hours)

What to Expect from Design Patterns - The Pattern Community An Invitation - A Parting Thought - A Case Study : Designing a Document Editor : Design Problems, Document Structure, Formatting, Embellishing the User Interface, Supporting Multiple Look-and-Feel Standards, Supporting Multiple Window Systems, User Operations Spelling Checking and Hyphenation.

REFERENCES

1. Jason McC. Smith, “Elemental design Patterns”, Pearson, 2012. 2. Alan Shalloway and James R.Trott, “Design Patterns explained: A new

perspective on Object-Oriented Design, 2006. 3. Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, “Design

Patterns: Elements of Reusable Object-Oriented Software”, Addison-Wesley, 2003.

4. Eric Freeman, Elisabeth Freeman, Kathy Sierra, Bert Bates, “Head First Design Patterns”, O'Reilly Media, Inc., 2004.

SE2110

SOFTWARE MEASUREMENTS AND

METRICS

L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Engineering Principles

PURPOSE

The purpose of this course is to provide the knowledge about Software Metrics, Essentials of software metrics and practical knowledge to assess software.

INSTRUCTIONAL OBJECTIVES

1. To provide a solid background knowledge about software Metrics.

2. To educate various metrics and models to assess software.

3. To provide hands on experience to use and implement metrics.

UNIT I-THE HISTORY AND EVOLUTION OF SOFTWARE METRICS (9 hours)

Evolution of the software industry and evolution of software measurements – The cost of counting function point metrics – The paradox of reversed productivity for high-Level languages- The Varieties of functional metrics – Variations in

Page 34: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

33

application size and productivity rates – Future Technical Developments in Functional Metrics- Software measures and metrics not based on function points.

UNIT II-MEASURING SOFTWARE QUALITY (9 hours)

Quality control and international competition – Defining quality for measurement and estimation – Five steps to software quality control- Measuring software defect removal- Measuring Defect removal efficiency – Measuring the costs of defect removal – Evaluating defect prevention methods – Measuring customer reported defects- Measuring invalid defects, Duplicate defects and special cases- Reliability Models - The Rayleigh Model- Reliability Growth Models.

UNIT III-PROCESS METRICS (9 hours)

In-Process Metrics for Software Testing - Test Progress S Curve - Testing Defect Arrivals Over Time - Product Size Over Time - CPU Utilization - Effort/Outcome Model. Complexity Metrics and Models - Lines of Code - Halstead's Software Science - Cyclomatic Complexity. - Syntactic Constructs - Structure Metrics. Metrics for Object-Oriented Projects - Concepts and Constructs - Design and Complexity Metrics - Lorenz Metrics and Rules of Thumb - CK OO Metrics Suite - Productivity Metrics.

UNIT IV-MECHANICS OF MEASUREMENT (9 hours)

Software Assessments – Software Baselines – Software Benchmarks- What a Baseline analysis covers – Developing or Acquiring a baseline data collection Instrument – Administering the data collection questionnaire – Analysis and aggregation of the Baseline data. Measuring and Analyzing Customer Satisfaction - Surveys - Data Collection - Sampling Methods - Analyzing Satisfaction Data. Conducting In-Process Quality Assessments - Preparation - Evaluation - Quantitative Data - Qualitative Data - Evaluation Criteria - Overall Assessment.

UNIT V-MEASUREMENTS, METRICS AND INDUSTRY LEADERSHIP (9 hours)

Measures and metrics of industry leaders – Measures, metrics and innovation – Measurements, metrics and outsource litigation – Measurements, metrics and behavioral changes – Commercial software measurement tools. Measuring Process Maturity - Process Capability - Value of Process Improvement - Process Adoption – Process Compliance. Function Point Metrics to Measure Software Process Improvement - Software Process Improvement Sequences.

Page 35: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

34

REFERENCES

1. Caper Jones, “Applied Software Measurement: Global Analysis of Productivity and Quality” , Third Edition, McGraw Hill Companies, 2008.

2. Stephen H. Kan, “Metrics and Models in Software Quality Engineering”, Addison Wesley, 2011.

3. Mark Lorenz, Jeff Kidd, “Object-Oriented Software Metrics”, Prentice Hall, 2000.

4. Naresh Chauhan, “Software Testing Principles and Practices”, Oxford University Press, 2010.

5. Ravindranath Pandian C., “Software Metrics A Guide to planning, Analysis, and Application”, Auerbach, First Indian Reprint, 2011.

SE2111

DATA WAREHOUSING AND DATA MINING L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Database Management Systems

PURPOSE

This course enable to understand the concepts of Data Warehousing and Data Mining. INSTRUCTIONAL OBJECTIVES 1. To learn the fundamentals of designing a large-scale data warehouse using

relational technology. 2. To understand the Data Warehouse and OLAP Technology in Data Mining 3. To study the Mining Association Rules in Large Databases, Classification

and Prediction. 4. To know Cluster Analysis and its Application Trends in Data Mining.

UNIT I-DATA WAREHOUSING AND BUSINESS ANALYSIS (9 hours)

Data Warehousing and Business Analysis: - Data warehousing Components –Building a Data warehouse – Mapping the Data Warehouse to a Multiprocessor Architecture – DBMS Schemas for Decision Support – Data Extraction, Cleanup, and Transformation Tools –Metadata – reporting – Query tools and Applications – Online Analytical Processing (OLAP) – OLAP and Multidimensional Data Analysis. UNIT II-DATA MINING (9 hours)

Data Mining: - Data Mining Functionalities – Data Preprocessing – Data Cleaning – Data Integration and Transformation – Data Reduction – Data Discretization and Concept Hierarchy Generation. Association Rule Mining: - Efficient and Scalable

Page 36: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

35

Frequent Item set Mining Methods – Mining Various Kinds of Association Rules – Association Mining to Correlation Analysis – Constraint-Based Association Mining.

UNIT III-CLASSIFICATION AND PREDICTION (9 hours)

Classification and Prediction: - Issues Regarding Classification and Prediction – Classification by Decision Tree Introduction – Bayesian Classification – Rule Based Classification – Classification by Back propagation – Support Vector Machines – Associative Classification – Lazy Learners – Other Classification Methods – Prediction – Accuracy and Error Measures – Evaluating the Accuracy of a Classifier or Predictor – Ensemble Methods – Model Section.

UNIT IV-CLUSTER ANALYSIS (9 hours)

Cluster Analysis: - Types of Data in Cluster Analysis – A Categorization of Major Clustering Methods – Partitioning Methods – Hierarchical methods – Density-Based Methods – Grid-Based Methods – Model-Based Clustering Methods – Clustering High-Dimensional Data – Constraint-Based Cluster Analysis – Outlier Analysis

UNIT V-APPLICATIONS OF DATA MINING (9 hours)

Mining Object, Spatial, Multimedia, Text and Web Data: Multidimensional Analysis and Descriptive Mining of Complex Data Objects – Spatial Data Mining – Multimedia Data Mining – Text Mining – Mining the World Wide Web.

REFERENCES

1. Jiawei Han and Micheline Kamber “Data Mining Concepts and Techniques” Second Edition, Elsevier, Reprinted 2008.

2. Sam Anahory & Dennis Murray, “Data Warehousing in the real world”, Pearson Education Ltd, 2011.

3. Alex Berson and Stephen J. Smith “Data Warehousing, Data Mining & OLAP”, Tata McGraw – Hill Edition, Tenth Reprint 2007.

4. K.P. Soman, Shyam Diwakar and V. Ajay “Insight into Data mining Theory and Practice”, Easter Economy Edition, Prentice Hall of India, 2006.

5. Gupta G. K. “Introduction to Data Mining with Case Studies”, Easter Economy Edition, Prentice Hall of India, 2006.

6. Pang-Ning Tan, Michael Steinbach and Vipin Kumar “Introduction to Data Mining”, Pearson Education, 2007.

7. Jiawei Han & Micheline Kamber “Data Mining Concepts and Techniques” , Morgan Kaufmann Publishers, Elsevier,2nd Edition, 2006.

Page 37: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

36

SE2112

INTERNET PROGRAMMING L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Nil

PURPOSE

The student should develop the skill in internet Programming concepts and related scripting languages

INSTRUCTIONAL OBJECTIVES

1. To describe basic Internet Protocols

2. Understand JAVA and HTML tools for Internet programming

3. Describe scripting languages – Java Script.

4. Understand Ajax , silver light , flash programming

5. Understand Server Side Programming tools

UNIT I-BASIC NETWORK AND WEB CONCEPTS (9 hours)

Internet standards – TCP and UDP protocols – URLs – MIME – CGI – Introduction to SGML Java basics – I/O streaming – files – Socket programming –client/server programs – E-mail client – SMTP - POP3 programs – web page retrieval – protocol handlers – content handlers - applets – image handling - Remote Method Invocation.

UNIT II-SCRIPTING LANGUAGE (9 hours)

HTML5 introduction – Introduction to JavaScript and DOM – Event Handler – Javascript functions – objects – simple web applications – Talking to the Web – Web Storage and Workers. UNIT III-AJAX (9 hours)

Introduction to AJAX on ASP.NET – DHTML – JavaScript and DOM – Data Communication: XML, XSLT, and JSON UNIT IV-SILVERLIGHT & FLASH (9 hours)

Introduction to Silverlight – Silverlight User interface control – Content integration in silverlight application – Network Communication – Working with data-Introduction to Flash – working with object editor – Publishing flash files

Page 38: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

37

UNIT V-SERVER SIDE PROGRAMMING (9 hours)

Servlets – deployment of simple servlets – web server (Java web server / Tomcat / Web logic) – HTTP GET and POST requests – session tracking – cookies – JDBC – simple web applications – multi-tier applications. REFERENCES

1. Deitel, Deitel and Nieto, “Internet and World Wide Web – How to program”, 4th Edition, Pearson Education Publishers, 2009.

2. Elliotte Rusty Harold, “Java Network Programming”, O’Reilly Publishers, 2009.

3. R. Krishnamoorthy & S. Prabhu, “Internet and Java Programming”, New Age International Publishers, 2004.

4. Eric Freeman ,Elisabeth Robson, “HTML5 Programming”, First edition, O’Reilly Publishers, 2011.

5. Ashish Ghoda , “Introducing Silverlight 4”, A Press , 2010. 6. Wallace B. McClure, Scott Cate, Paul Glavich, Craig Shoemaker, “Beginning

Ajax with ASP.NET”, Wiley Publishing, Inc , 2006. 7. Ellen finkelstein , Gurdy leete “Macromedia flash 8”, TEAM LinG For

Dummies; 1 edition, 2005.

ELECTIVES FOR THIRD SEMESTER

SE2113

SOFTWARE QUALITY MANAGEMENT L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Engineering Principles, Software Testing

PURPOSE

This course covers the principles of software development emphasizing processes and activities of quality assurance.

INSTRUCTIONAL OBJECTIVES

1. The student must relate to quality assurance plan

2. The students must apply quality assurance tools & techniques in their project

3. To learn about standards and certifications

4. To describe procedures and work instructions in software organizations

Page 39: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

38

UNIT I-INTRODUCTION (9 hours)

The Software Quality Challenge - Software Quality Factors - Components of the Software Quality Assurance System. Pre-Project Software Quality Components - Contract Review - Development and Quality Plans UNIT II-SOFTWARE QUALITY ASSURANCE COMPONENTS IN THE PROJECT

LIFE CYCLE (9 hours)

Integrating Quality Activities in the Project Life Cycle – Reviews - Software Testing – Strategies - Software Testing –Implementation - Assuring the Quality of Software Maintenance - Assuring The Quality of External Participants' Parts - Case Tools and their Affect on Software Quality. UNIT III-SOFTWARE QUALITY INFRASTRUCTURE COMPONENTS (9 hours)

Procedures and Work Instructions - Supporting Quality Devices - Staff Training, Instructing and Certification - Preventive and Corrective Actions - Configuration Management - Documentation and Quality Records Controls

UNIT IV-SOFTWARE QUALITY MANAGEMENT COMPONENTS (9 hours)

Project Progress Control- Components, Internal & External Participants, Progress control regimes, Computerized tools, Software Quality Metrics – Objective, Classification, Process & Product Metrics, Implementation & Limitation of Software Metrics - Software Quality Costs – Objective, Classification Model of cost, Extended Model and Applications UNIT V-STANDARDS, CERTIFICATION AND ASSESSMENT (9 hours)

SQA Standards – ISO9001 Certification - Software Process Assessment. Organizing for Quality Assurance -Management and its Role in Quality Assurance - The Software Quality Assurance Unit - SQA Trustees and Committees REFERENCE

1. Daniel Galin, “Software Quality Assurance: From Theory to Implementation”, Pearson Addison-Wesley, 2012.

2. Roger S. Pressman, “Software Engineering-A Practitioner’s Approach”, McGraw Hill pub.2010.

3. Allen Gilles “Software quality: Theory and management”, International Thomson, Computer press 1997.

4. Stephen H.Kan, “Metrics and models in software quality Engineering”, Addison –Wesley 2003.

Page 40: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

39

5. Humphrey Watts, “Managing the Software Process” Addison Wesley, 1986.

SE2114

COMPONENT BASED SYSTEM DESIGN L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Object Oriented Programming , Java Programming

PURPOSE

The course gives an insight of the most commonly used software component technologies and their applications INSTRUCTIONAL OBJECTIVES

1. To understand the various software components in Java, CORBA, COM and .NET

2. Be able to use the above technologies in solving problems in the development of software

3. To understand the component framework and its development.

UNIT I-INTRODUCTION (9 hours) Introduction – Standards – Terms and Concepts – Standardization and Normalization – Components and Interfaces – Callbacks – Contracts – Examples – Processes and multithreading. UNIT II-JAVA BASED COMPONENT TECHNOLOGIES (9 hours)

Overview and history of java components – Java the language – Java Beans – Java Services – Applets, Servlets, Beans and Enterprise Beans – Advanced Java Services – Interfaces vs Classes in java - JXTA and Jini – Java and Web services. UNIT III-CORBA (9 hours)

Object and component “wiring” standards – CORBA – The object request broker – CORBA Services – CORBA Component Model – Portable object Adapter – CCM Components, Containers – CORBA Complaint implementations – CORBA facilities– Application objects –CORBA, UML, XML and MDA-Case Study. UNIT IV-NET BASED COMPONENT TECHNOLOGIES (9 hours)

COM - Object reuse - Interfaces and Polymorphism – COM object creation and COM Library – initializing objects, persistence, structural storage, monikers – From COM to distributed COM -Meta-information and Automation – Other COM services- OLE containers and servers - Active X controls - Contextual

Page 41: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

40

Composition and Services - .NET framework -.NET components -Assemblies - Common language Frameworks. UNIT V-COM OVERVIEW AND COMPONENT FRAMEWORKS (9 hours)

Component Architecture - Component Frameworks - Contribution of contextual component frameworks - Frameworks for contextual composition - Black box component framework - Black box and OLE - Portos - Component Development: Component oriented programming - Tools - Component Distribution and Acquisition - Component Assembly-Case Study.

REFERENCES

1. Clemens Szyperski. Dominik Gruntz and Stephan Murer. “Component Software: Beyond Object-Oriented Programming”, Addison-Wesley Professional, 2nd edition, 2011.

2. Ed Roman , “Mastering Enterprise Java Beans”, 3rd edition, John Wiley Publications, 2005.

3. Mowbray, “Inside CORBA”, Pearson Education, 2006. 4. Hortsamann, Cornell, “ CORE JAVA Vol- II”, 8th edition, 2008. 5. Sudha Sadasivam, “Component Based Technology”, John Wiley and Sons,

2008. 6. Freeze, “Visual Basic Development Guide for COM & COM+”, BPB

Publication, 2001.

SE2115

HUMAN INTERFACE SYSTEM DESIGN L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Engineering, System Design

PURPOSE

This course on user Interface Design provides a basic understanding of interface design and principles

INSTRUCTIONAL OBJECTIVES

1. Students learn about the design process management

2. To understand about Interaction devices and windows strategies

3. To understand about how to Manage Virtual Environments

Page 42: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

41

UNIT I-INTRODUCTION (9 hours)

Goals of System Engineering – Goals of User Interface Design – Motivations of Human factors in Design – High Level Theories –Object-Action Interface Design - Three Principles – Guidelines for Data Display and Data Entry UNIT II-MANAGING DESIGN PROCESS (9 hours)

Introduction- Organizational Design to Support Usability – The Three Pillars of Design- Development Methodologies- Ethnographic Observation – Participating Design- Scenario Development- Social Impact Statement for Early Design – Legal Issues- Reviews – Usability Testing and laboratories- Surveys- Acceptance tests – Evaluation during Active use- Specification Methods- Interface – Building Tools- Evaluation and Critiquing tools

UNIT III-MANIPULATION AND VIRTUAL ENVIRONMENTS (9 hours)

Introduction-Examples of Direct Manipulation Systems –Explanation of Direct Manipulation- Visual Thinking and Icons – Direct manipulation Programming – Home Automation- Remote Direct manipulation- Virtual Environments- Task-Related Organization – Item Presentation Sequence- Response Time and Display Rate – Fast Movement Through Menus- Menu Layouts- Form Fillin – Dialog Box – Functionality to Support User’s Tasks – Command Organization Strategies – Benefits of Structure- Naming and Abbreviations – Command Menus- Natural Language in Computing. UNIT IV-INTERACTION DEVICES (9 hours)

Introduction – Keyboards and Functions – Pointing Devices- Speech recognition ,Digitization and Generation – Image and Video Displays – Printers –Theoretical Foundations –Expectations and Attitudes – User Productivity – Variability – Error messages – Non anthropomorphic Design – Display Design – color-Reading from Paper versus from Displays- Preparation of Printed Manuals- Preparation of Online Facilities.

UNIT V-WINDOWS STRATEGIES AND INFORMATION SEARCH (9 hours)

Introduction- Individual Widow Design- Multiple Window Design- Coordination by Tightly – Coupled Widow- Image Browsing- Personal Role Management and Elastic Windows – Goals of Cooperation – Asynchronous Interaction – Synchronous Distributed – Face to Face- Applying Computer Supported Cooperative Work to Education – Database query and phrase search in Textual documents – Multimedia Documents Searches – Information Visualization – Advance Filtering Hypertext and Hypermedia – World Wide Web- Genres and

Page 43: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

42

Goals and Designers – Users and their tasks – Object Action Interface Model for Web site Design

REFERENCE

1. Alan Dix et al, " Human - Computer Interaction ", Pearson , 2010. 2. Ben Shneiderman , "Designing the User Interface”, 4th Edition, Pearson,

2010. 3. Dr. Jonathan Lazar, Dr. Jinjuan Heidi Feng, Dr. Harry Hochheiser, “Research

Methods in Human Computer Interaction” –John Wiley 2010. 4. Wilbert O. Galiz , “The Essential guide to User Interface Design”, Wiley

Dreamtech, 2009. 5. Jef Raskin , “The Human Interface ", Addison – Wesley – 2008.

SE2116

SERVICE ORIENTED ARCHITECTURE L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Web Services

PURPOSE

To gain understanding about the basic principles of service oriented architecture

INSTRUCTIONAL OBJECTIVES

1. To learn service oriented analysis techniques

2. To learn technology underlying the service design

3. To learn advanced concepts such as service composition, orchestration and Choreography

4. To know about various Web Service specification standards

UNIT I-INTRODUCTION (9 hours)

Roots of SOA – Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures – Anatomy of SOA- How components in an SOA interrelate - Principles of service orientation

UNIT II-SERVICE ORIENTED ARCHITECTURE IN WEB SERVICES

(9 hours)

Web services – Service descriptions – Messaging with SOAP –Message exchange Patterns – Coordination – Atomic Transactions – Business activities –

Page 44: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

43

Orchestration – Choreography - Service layer abstraction – Application Service Layer – Business Service Layer – Orchestration Service Layer

UNIT III-BUILDING SOA (9 hours)

Service oriented analysis – Business-centric SOA – Deriving business services- service modeling - Service Oriented Design – WSDL basics – SOAP basics – SOA composition guidelines – Entity-centric business service design – Application service design – Task centric business service design.

UNIT IV-SOA PLATFORMS (9 hours)

SOA platform basics – SOA support in J2EE – Java API for XML-based web services (JAX-WS) - Java architecture for XML binding (JAXB) – Java API for XML Registries (JAXR) - Java API for XML based RPC (JAX-RPC)- Web Services Interoperability Technologies (WSIT) - SOA support in .NET – Common Language Runtime - ASP.NET web forms – ASP.NET web services – Web Services Enhancements (WSE).

UNIT V-SOA DESIGN (9 hours)

Web Service-BPEL- process, elements, functions – Web Service-Coordination overview –elements, web service business activity & atomic transaction coordination type , -Business process design Web Service - Choreography, Web Service-Policy-elements - Web Service Security- XML –Signature element

REFERENCES

1. Thomas Erl, “Service-Oriented Architecture: Concepts, Technology, and Design”,Pearson Education, 2009.

2. Thomas Erl, “SOA Principles of Service Design” (The Prentice Hall Service-Oriented Computing Series from Thomas Erl), 2005.

3. Newcomer, Lomow, “Understanding SOA with Web Services”, Pearson Education, 2005.

4. Sandeep Chatterjee, James Webber, “Developing Enterprise Web Services, An Architect’s Guide”, Pearson Education, 2005.

Page 45: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

44

SE2117

SOFTWARE CONFIGURATION MANAGEMENT L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Quality Management

PURPOSE

This course enables to understand the importance and the benefits of software configuration and change management.

INSTRUCTIONAL OBJECTIVES

1. To learn the changing nature of software and need for change management

2. To study the different phases involved in software configuration management

3. To learn about the SCM plans, audits and reviews

4. To study the various SCM tools and implementation techniques

5. To study the SCM different scenarios and future directions

UNIT I-OVERVIEW TO SOFTWARE CONFIGURATION MANAGEMENT (9 hours)

SCM: Concepts and definitions – SCM Plan – Software development life cycle models – SDLC Phases – Need and importance of Software configuration management – Increased complexity and demand – Changing nature of software and need for change management – Lower maintenance costs and better quality assurance – Faster problem identification and bug fixes - SCM: Basic concepts – Baselines – Check-in and Check-out- Versions and Variants –System Building - Releases

UNIT II-DIFFERENT PHASES OF SOFTWARE CONFIGURATION MANAGEMENT

(9 hours)

Different Phases Of Scm – SCM System design - SCM Plan preparation - SCM Team organization – SCM Infrastructure organization – SCM Team training – Project team training – Configuration identification – Configuration Control – Configuration status accounting – Configuration audits

UNIT III-CONFIGURATION AUDITS AND MANAGEMENT PLANS (9 hours)

When, what and who of auditing - Functional Configuration audit – Physical Configuration audit – Auditing the SCM System – Role of SCM Team in

Page 46: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

45

configuration audits – SCM plan and the incremental approach – SCM Plan and SCM Tools – SCM Organization

UNIT IV-SOFTWARE CONFIGURATION MANAGEMENT TOOLS AND

IMPLEMENTATION (9 hours)

Advantages of SCM tools – Reasons for the increasing popularity of SCM tools – SCM Tools and SCM Functions – SCM tool selection – Role of Technology – Selection criteria – Tool implementation – SCM implementation plan – implementation strategy – SCM Implementation team

UNIT V-TRENDS IN SCM: FUTURE DIRECTIONS (9 hours)

SCM in different scenarios – SCM and project size – SCM in integrated development environments – SCM In distributed environments – SCM and CASE Tools - Trends in SCM - Hardware and Software Management – Better integration with IDE’S and CASE environments – Customization – Better decision making capabilities – Reduction in SCM Team size – Market snapshot

REFERENCES

1. Jessica Keyes, Software Configuration Management, Auerbach Publications, 2008.

2. Alexis Leon, Software Configuration Management Handbook, Artech Print on Demand; 2 edition , 2009.

3. Robert Aiello and Leslie Sachs Configuration Management Best Practices: Practical Methods that work in Real World, , Addison-Wesley Professional; 1 edition, 2010.

4. Stephen P. Berczuk, Brad Appleton and Kyle Brown , “Software Configuration Management Patterns: Effective Teamwork and Practical Integration”, Addison-Wesley , 2003.

SE2118

DECISION SUPPORT SYSTEMS L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Database Management Systems

PURPOSE

The purpose of this course is to impart concepts of decision making, decision processes and its implementation in a Development Environment.

Page 47: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

46

INSTRUCTIONAL OBJECTIVES

1. To appreciate and understand DSS and its Characteristics

2. To apply the Decision Makers and styles

3. To educate about Knowledge management

4. To emphasize on Intelligent DSS

5. To provide a modest experience in Implementation of DSS

UNIT I-INTRODUCTION TO DSS AND DECISION MAKERS (9 hours)

DSS definition- characteristics- History of DSS- Components of DSS- Data and Model Management-DSS knowledge base- user interfaces- DSS user- categories and classes of DSS’s- Decision and Decision Makers : Decision Makers- Decision styles- Decision effectiveness- Hardness of Decisions, CASE STUDY: Mini-Case: Mervyn's Department Store, Mini-Case: Disaster at Tenerife.

UNIT II-DECISION MAKING AND ORGANIZATION DECISION (9 hours) Typology of Decisions: Decision theory- Rational Decision Making- Bounded Rationality-Process of choice – Cognitive processes-Heuristics in Decision Making- Effectiveness and efficiency- Decisions in the Organization: Understanding the Organization- Organization culture- power and politics- organization Decision making, CASE STUDY - Mini-Case: Philips Petroleum Product Pricing, The Cuban Missle Crisis. UNIT III-DECISION PROCESSES (9 hours)

Decision Processes: Problem definition and its structure – decision models- types of probability and its forecasting techniques- sensitivity analysis- Group Decision Support : Group Decision making- the problem with groups- concepts and definition of MDM technology – MDM activities- virtual workplace-Executive Information system(EIS):history of EIS-characteristics of executives- EIS components-making EIS workfuture of executive Decision making and EIS, CASE STUDY : What Were the Odds of This Happening? The Exxon Valdez, Plano Police Department, AlliedSignal.

UNIT IV-SYSTEM PERSPECTIVE OF DSS (9 hours) Perspective of DSS: System – DSS in the context of information system- Information quality issues in DSS design- DSS information system architecture- role of Internet in DSS development and use- Designing and Building DSS: Strategies of DSS Analysis and Design- DSS Developer-tools for DSS development- DSS user Interface Issues

Page 48: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

47

UNIT V-IMPLEMENTATION AND INTEGRATION OF DSS (9 hours)

Implementing DSS : DSS Implementation- Patterns of Implementation- System Evaluation-Importance of Integration-Creativity Decision making: Definition of creativity- occurrence of creativity- Creative Problem Solving Techniques-introduction to intelligent DSS (AI, Expert system and Knowledge based systems)– DSS in the 21st century-future of DSS, EIS and DSS technologies.

REFERENCES

1. Vicki L. Sauter, “Decision Support Systems for Business Intelligence”,2nd Edition, Wiley, 2011.

2. George M .Marakas , "Decision Support Systems in the 21st century",2nd Edition, PHI, 2009.

3. V.S.Janakiraman, K.Sarukesi, “Decision Support Systems”, PHI, 2009 4. Efraim Turban, Jay E.Aronson, Ting-Peng Liang, "Decision Support

Systems and Intelligent Systems", 7th Edition, Pearson Education ,2006. 5. Daniel J Power, “Decision Support Systems : Concept and Resources for

Managers”, Praeger, April 2002.

SE2119 WEB SERVICES L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Nil

PURPOSE

To study and highlight the features of different technologies involved in web services and Xml.

INSTRUCTIONAL OBJECTIVES

1. To understand basics in XML Concepts

2. To understand the concepts of web services

3. To gain knowledge in WSDL and UDDI

4. To apply methods for constructing and evaluating architectures

UNIT I-XML TECHNOLOGY FAMILY (9 hours)

XML – benefits – Advantages of XML over HTML – EDI – Databases – XML based standards – DTD –XML Schemas – X – Files – XML processing – DOM – SAX –

Page 49: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

48

presentation technologies – XSL –XFORMS – XHTML – voice XML – Transformation – XSLT – XLINK – XPATH – XQ

UNIT II-ARCHITECTING WEB SERVICES (9 hours)

Business motivations for web services – B2B – B2C – Technical motivations – limitations of CORBA and DCOM – Service – oriented Architecture (SOA) – Architecting web services – Implementation view –web services technology stack – logical view – composition of web services – deployment view – from application server to peer to peer – process view – life in the runtime UNIT III-WEB SERVICES BUILDING BLOCK (9 hours)

Transport protocols for web services – messaging with web services – protocols – SOAP – describing web services – WSDL – Anatomy of WSDL – manipulating WSDL – web service policy – Discovering web services – UDDI – Anatomy of UDDI – Web service inspection – Ad – Hoc Discovery – Securing web services.

UNIT IV-IMPLEMENTING XML IN E – BUSINESS (9 hours)

B2B – B2C Applications – Different types of B2B interaction – Components of e – business XML systems – eb XML – Rosetta Net Applied XML in vertical industry – web services for mobile devices.

UNIT V-XML AND CONTENT MANAGEMENT (9 hours)

Semantic Web – Role of Meta data in web content – Resource Description Framework – RDF schema – Architecture of semantic web – content management workflow – XLANG – WSFL . REFERENCES

1. Ron Schmelzer et al, “XML and Web Services Unleashed”, Pearson Education, 2011.

2. Frank P.Coyle, “XML, Web Services and the Data Revolution”, Pearson Education, 2002.

3. Keith Ballinger, “.NET Web Services Architecture and Implementation”, Pearson Education, 2003.

4. Henry Bequet and Meeraj Kunnumpurath, “Beginning Java Web Services”, Apress, 2004.

5. Russ Basiura and Mike Batongbacal, “Professional ASP .NET Web Services”, Apress, 2009.

Page 50: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

49

SE2120

LANGUAGE TECHNOLOGIES L T P C

Total Contact Hours - 45 3 0 0 3

Prerequisite

Text Mining

PURPOSE

This course enables to understand the importance and the benefits of software configuration and change management.

INSTRUCTIONAL OBJECTIVES

1. To learn the basic concepts of natural language processing

2. To study the different techniques involved with information retrieval

3. To learn about text mining

4. To explore some the generic issues such as multilingual information retrieval and speech processing.

5. To study the SCM different scenarios and future directions

UNIT I-INTRODUCTION (9 hours)

Natural Language Processing – Linguistic Background- Spoken language input and output Technologies – Written language Input - Mathematical Methods - Statistical Modeling and Classification Finite State methods Grammar for Natural Language Processing – Parsing – Semantic and Logic Form – Ambiguity Resolution – Semantic Interpretation. UNIT II-INFORMATION RETRIEVAL (9 hours)

Information Retrieval architecture - Indexing- Storage – Compression Techniques – Retrieval Approaches – Evaluation - Search engines- commercial search engine features- comparison- performance measures – Document Processing - NLP based Information Retrieval – Information Extraction. UNIT III-TEXT MINING (9 hours)

Categorization – Extraction based Categorization- Clustering- Hierarchical Clustering- Document Classification and routing- finding and organizing answers from Text search – use of categories and clusters for organizing retrieval results – Text Categorization and efficient Summarization using Lexical Chains – Pattern Extraction.

Page 51: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

50

UNIT IV-GENERIC ISSUES (9 hours)

Multilingualism – Multilingual Information Retrieval and Speech processing - Multimodality – Text and Images – Modality Integration - Transmission and Storage – Speech coding- Evaluation of systems – Human Factors and user Acceptability.

UNIT V-APPLICATIONS (9 hours)

Machine Translation – Transfer Metaphor - Interlingua and Statistical Approaches - Discourse Processing – Dialog and Conversational Agents – Natural Language Generation – Surface Realization and Discourse Planning.

REFERENCES

1. Daniel Jurafsky and James H. martin, “Speech and Language Processing”, Pearson Prentice Hall; 2 edition, 2008.

2. Ron Cole, J.Mariani, et.al “Survey of the State of the Art in Human Language Technology”, Cambridge University Press, 2007.

3. Michael W. Berry “Survey of Text Mining: Culstering, Classification and Retrieval”, Springer Verlag, 2003.

4. Christopher D.Manning and Hinrich Schutze, “Foundations of Statistical Natural Language Processing “, MIT Press, 2000.

SE2121

ANALYSIS OF SOFTWARE ARTIFACTS L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Engineering, Software Testing

PURPOSE

To enhance students software testing and analysis skills.

INSTRUCTIONAL OBJECTIVES

1. To understand the concepts of quality models, frame work and testing

2. To Gain knowledge in analysis of software under various dimensions

3. To Gain knowledge in the area of evaluating an architecture & verification & validation of software.

UNIT I-QUALITY MODELS (9 hours)

Introduction-views on quality-cost of quality-quality models-Statistics and measurements-Statistics and measurements-Analysis of given source code using SQALE and Sonar models.

Page 52: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

51

UNIT II-QUALITY FRAMEWORK AND TESTING (9 hours)

Quality framework characteristics – verification- Measuring test adequacy-overview of black box testing techniques-decision tables-combinatorial testing-classification tree method- white box testing- Random and exploratory. UNIT III-SOFTWARE ANALYSIS (9 hours)

Introduction to Static analysis- Static analyzer for finding dynamic programming errors-dataflow testing – procedure to apply data flow testing- examples-performance analysis and verification- Security analysis and verification – Software vulnerabilities and exploitation. UNIT IV-QUASAR METHOD (9 hours)

Applying the Design structure matrix to system decomposition and integration problems- achieving Agility through Architecture visibility-Recovering and verifying architecture through design structure matrices.

UNIT V-QUALITY MANAGEMENT (9 hours)

Project quality management- Essential Testing-Test driven development – guidance for software verification and validation plans-Master test planning. REFERENCES

1. Kshirasagar Naik and Priyadarshi Tripathy “Software testing and Quality Assurance: theory and practice, edited by copyright John wiley & sons Inc, 2008.

2. Daniel Galin “Software Quality Assurance from Theory to Implementation”, Pearson Education Ltd., 2004.

3. Marc-Alexis Côté M. Ing , Witold Suryn Elli Georgiadou “Quality models to engineeri quality requirements” published in journal of object technology, chair of Software engineering, Vol.2 , No. 5 Sep. – October 2003. Online at http://www.jot.sm.

4. Tyson R. Browning, “Applying the design structure matrix to system decomposition and integration problems”, A review and new directions IEEE transactions on Engineering management, Vol. 48, No.3, August 2001.

5. Neeraj sangal and Frank Waldman “Dependency models to manage software Architecture: journal of Defense software engineering, November 2005. Online at www.stsc.hill.af.mil.

Page 53: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

52

SE2122

CLOUD COMPUTING L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Computer Networks

PURPOSE

To provide a comprehensive introduction to cloud computing and about cloud services

INSTRUCTIONAL OBJECTIVES

1. To understand Cloud Computing basics and its models.

2. To learn the fundamentals of Data Centers.

3. To understand the Architecture of Data Centers and Design Principles

4. To understand the Security aspects and security framework.

UNIT I-INTRODUCTION (9 hours)

Cloud Computing Introduction, From, Collaboration to cloud, Working of cloud computing, pros and cons, benefits, developing cloud computing services, Cloud service development, discovering cloud services. UNIT II-CLOUD COMPUTING FOR EVERYONE (9 hours)

Centralizing email communications, cloud computing for community, collaborating on schedules, collaborating on group projects and events, cloud computing for corporation, mapping schedules managing projects, presenting on road. UNIT III-USING CLOUD SERVICES (9 hours)

Collaborating on calendars, Schedules and task management, exploring on line scheduling and planning, collaborating on event management, collaborating on contact management, collaborating on project management, collaborating on word processing, spreadsheets, and databases.

UNIT IV-OUTSIDE THE CLOUD (9 hours)

Evaluating web mail services, Evaluating instant messaging, Evaluating web conference tools, creating groups on social networks, Evaluating on line groupware, collaborating via blogs and wikis

Page 54: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

53

UNIT V-STORING AND SHARING (9 hours)

Understanding cloud storage, evaluating on line file storage, exploring on line book marking services, exploring on line photo editing applications, exploring photo sharing communities, controlling it with web based desktops.

REFERENCES 1. Michael Miller, “Cloud Computing”, Pearson Education, New Delhi, 2009. 2. Toby Velte, Anthony Velte, Robert Elsenpeter, "Cloud Computing: A Practical

Approach", McGraw Hill, 2009. 3. Mauricio Arregoces,Maurizio Portolani, "Data Center Fundamentals", Cisco

Press,2004. 4. Scott Lowe, Jason W, Mc. Carty and Mathew K. Johnson, “VMware, Vsphere

4 Administration, Instant Reference", Published by Sybex, 2009. 5. George Reese, "Cloud Application Architectures Building Applications and

Infrastructure in the Cloud", O'Reilly Media, 2009. 6. Grantt Sauls "Introduction to Data Centers", Certified Data Centers Specialist,

Tutorial. 7. Brendan O’Brien, Alberto Rodriguez, Stephen Sutherland and Mark Wheatley,

“Server Virtualization Software”, Tutorial, 2009.

SE2123

PERSONAL SOFTWARE PROCESS L T P C

Total Hours - 45 3 0 0 3

Prerequisite

Software Engineering Methodologies

PURPOSE

To learn about how a software professional personally manages the software processes in all aspects

INSTRUCTIONAL OBJECTIVES

1 To study how to manage and track the time for software processes

2. To study how to plan a product and how to measure size of a product

3. To learn how to schedule the process and manage the commitment

4. To learn about software Development process

5. To learn how to estimate the product and process quality.

UNIT I-INTRODUCTION AND TIME MANAGEMENT (9 hours)

Software Engineering – Personal Software Process – Improvement Process – Time Management – Logic of Time Management - Elements of Time

Page 55: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

54

Management – Categorizing your Activities – Gather Data on time spent by Activity – Evaluating your Time Distribution – Setting Ground rules – Prioritizing your time – Track Time – Recording your Time Data – Tracking your time – Handling Interruptions – Tracking Completed tasks. UNIT II-PRODUCT PLANNING AND PRODUCT SIZE (9 hours)

Product Plan - Need for product Planning – Planning Small Jobs – Job Number Log – Product Planning Process – Size Measurement - Program Size – Estimating Program Size UNIT III-MANGING COMMITMENTS AND SCHEDULES (9 hours)

Defining Commitment – Responsibly made Commitment – Handling Missed Commitments – Importance of Managing Commitments – Consequences of not Managing Commitments – Way to Manage Commitments – Need for Schedules – Gantt Chart – Making a Project Schedule – Checkpoints – Tracking Project Plans – Tracking Earned Value UNIT IV-SOFTWARE PROCESSES AND QUALITY (9 hours)

Need for Processes – Process Script – Checkpoints and phases – Updated Project Plan Summary Form - Defects – Software Quality – Defects and Quality – Defects Versus Bugs – Defect Types – Understanding Defects – Defect Recording Log – Steps in Finding Defects – Ways to Find and Fix Defects.

UNIT V-PRODUCT AND PROCESS QUALITY (9 hours)

Product Quality – Testing – The Filter view of Testing - Calculating yield values – Estimating the Ultimate Yield – Prototyping – Process Quality – Process Measures – Defect Removal Paradox – Defect Removal strategy – Appraisal/Failure ratio. REFERENCES

1. Watts.S.Humphery, “PSP: A Self-Improvement Process for Software Engineers”, Addison Wesley, 2005.

2. Watts.S.Humphery, “Introduction to the Personal Software Process”, Addison Wesley, 1997.

3. http://www.sei.cmu.edu/library/abstracts/reports/00tr022.cfm 4. http://repository.cmu.edu/cgi/viewcontent.cgi 5. http://dl.acm.org/citation.cfm?id=650271

Page 56: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

55

SE2124

EMBEDDED SYSTEMS L T P C

Total Hours – 45 3 0 0 3

Prerequisite

Microprocessors, Computer Architecture

PURPOSE

The course aims at introducing basic concepts in Embedded Systems with focus on Embedded System development, Hardware architecture and Embedded Operating System.

INSTRUCTIONAL OBJECTIVES

1. To understand the basics of Embedded Systems

2. Students get the basic knowledge of Hardware and the Software architecture of any Embedded System

3. To apply the basic productivity and development tools commonly used in Embedded design

4. Students get an insight on various Kernel objects of Embedded operating system.

UNIT I-INTRODUCTION TO EMBEDDED SYSTEMS (9 hours)

Introduction: What is an Embedded System – Basic Embedded System Design – Introduction to Embedded System Architecture – Embedding Computers – Characteristics of embedded computing applications – Challenges in embedded computing system design – Performance of Embedded computing systems – Embedded System Design – Requirements – Specification – Architecture Design – Designing Hardware and Software Components – System Integration – Formalism for System Design – Structural Description – Behavioral Description. UNIT II-EMBEDDED PROCESSOR AND COMPUTING PLATFORM

(9 hours)

Instruction Set - ARM Processor – The ARM Design Philosophy - Embedded System Hardware and Software – ARM Processor and Memory Organization – Data Operations – Flow Control – Advanced ARM Features – Computing Platforms – Basic Computing Platforms – CPU Bus – Memory Devices and Systems – Designing with Computing Platforms – Consumer Electronics Architecture – Design Example – Audio Player.

Page 57: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

56

UNIT III-PROCESSES, OPERATING SYSTEMS AND NETWORKS (9 hours)

Processes and Operating Systems – Multiple Tasks and Multiple Processes – Multirate Systems – Preemptive real–time operating system – Priority-based scheduling – Interprocess communication mechanism – Example real-time operating system – Windows CE – Design Example – Telephone Answering Machine – Why Networks and Multiprocessor – Distributed Embedded System – Design example – Video Accelerator.

UNIT IV-EMBEDDED C PROGRAMMING (9 hours)

C-looping structures – Register allocation – Function calls – Pointer aliasing – structure arrangement – bit fields – unaligned data and endianness – inline functions and inline assembly – Portability issues. UNIT V-EMBEDDED SYSTEM DEVELOPMENT AND (9 hours)

Embedded software development tools – Emulators and debuggers - Design Methodologies, Requirement Analysis, Specification, System Analysis and Architecture Design, Quality Assurance, Design Example: Telephone PBX- System Architecture, Ink jet printer- Hardware Design and Software Design, Personal Digital Assistants, Set-top Boxes. REFERENCES

1. Marilyn Wolf, “Computers as Components – Principles of Embedded Computing System Design”, Elsevier, Third Edition, 2012.

2. Andrew N. Sloss, Dominic Symes,et., “ARM Developer’s Guide – Designing and Optimizing System Software”, Elsevier, 2004.

3. Tammy Noergaard, “Embedded Systems Architecture – Comprehensive Guide for Engineers and Programmers”, Elsevier, 2005.

Page 58: M.Tech. (Full Time) - SOFTWARE ENGINEERING · PDF filem.tech. (full time) - software engineering curriculum & syllabus 2013 – 2014 department of software engineering faculty of engineering

57

AMENDMENTS

S.No. Details of Amendment Effective from Approval with

date