Master of Computer Applications
FIFTH SEMESTER EXAMINATION
Paper ID
Paper
Paper
Code
044301
MCA 301 Linux Programming
044303
MCA 303 Software Testing
044305
MCA 305 Enterprise Computing with Java
Elective - I (Choose any One)
044307
MCA 307 Advanced Database Management Systems
044309
MCA 309 Numerical and Scientific Computing
044311
MCA 311 Software Project Management
044313
MCA 313 Multimedia Technologies
044315
MCA 315 Mobile Computing
044317
MCA 317 Artificial Intelligence
044319
MCA 319 Microprocessors
044321
MCA 321 Compiler Design
Elective - II (Choose any One)
044323
MCA 323 Operational Research
044325
MCA 325 Distributed Systems
044327
MCA 327 Financial Accounting
044329
MCA 329 Organizational Behavior
044331
MCA 331 Advanced Computer Architecture
044333
MCA 333 Software Quality Management
044335
MCA 335 Digital Signal Processing
044337
MCA 337 Research Project
Practical
044351
MCA 351 Linux Programming Lab
044353
MCA 353 Software Testing Lab
044355
MCA 355 Enterprise Computing with Java Lab
044357
MCA 357 Lab based on Elective - I
NUES
044361
MCA 361
General Proficiency V*
(It is suggested to have Intellectual
Property Rights - Software Systems
Oriented Course)
Total
T/P
Credit
3
3
3
1
1
1
4
4
4
0
0
0
0
2
2
4
2
1
1
2
1
15
17
26
* Non-University Examination System (NUES)
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Paper Code: MCA-301
Paper: Linux Programming
L TC
3 1 4
INSTRUCTIONS TO PAPER SETTERS:
1. Question No. 1 should be compulsory and cover the entire syllabus. There should be 10 questions
of short answer type of 2 marks each, having at least 2 questions from each unit.
2. Apart from Question No. 1, rest of the paper shall consist of four units as per the syllabus. Every
unit should have two questions to evaluate analytical/technical skills of candidate. However,
student may be asked to attempt only 1 question from each unit. Each question should be 10 marks
including subparts, if any.
OBJECTIVES: The main objective of this course is to provide Students
A comprehensive overview of the Linux operating system along with Shell commands
and shell scripting
Implementation of Linux System programmes through GCC compiler.
Understanding of basic concept of Socket programming (TCP and UDP)
PRE-REQUISTE:
Operating system
Computer Network
C /C++ Programming
UNIT I
Linux The Operating System: Linux history, Linux features, Linux distributions, Linuxs
relationship to Unix, Overview of Linux architecture, Installation, Start up scripts, system
processes (an overview),Linux Security, The Ext2 and Ext3 File systems :General Characteristics
of, The Ext3 File system, file permissions. User Management: Types of users, The powers of
Root, managing users (adding and deleting): using the command line & GUI tools.
[No. of Hrs.: 10]
UNIT II
Resource Management in Linux: file and directory management, system calls for files Process
Management, Signals, IPC: Pipes, FIFOs, System V IPC, Message Queues, system calls for
processes, Memory Management, library and system calls for memory.
[No. of Hrs.: 10]
UNIT III
Shell Programming:Available shells under Linux (viz. Bash, TCSH, Korn or so on), different
Shell features, editors, shell commands, shell scripts: shell variables, environmental variables,
purpose of shell scripts, writing, storing and executing scripts, Filters- The grep family, advanced
filters-sed and awk.
[No. of Hrs.: 10]
UNIT IV
Networking in LINUX: Socket Introduction, Elementary TCP Sockets (Socket Function,
Connect Function, Bind, Listen, Accept, Fork and Exec), TCP Client server Example, Elementary
UDP Sockets.
[No. of Hrs.: 10]
TEXT BOOKS:
1. Arnold Robbins, Linux Programming by Examples The Fundamentals, Pearson
Education, 2nd Ed., 2008.
2. Cox K, Red Hat Linux Administrators Guide, PHI, 2009.
3. R. Stevens, UNIX Network Programming, PHI, 3rd Ed., 2008.
4. Sumitabha Das, Unix Concepts and Applications, TMH, 4th Ed., 2009.
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
REFERENCES:
1. Ellen Siever, Stephen Figgins, Robert Love, Arnold Robbins, Linux in a Nutshell,
O'Reilly Media, 6th Ed., 2009.
2. Neil Matthew, Richard Stones, Alan Cox, Beginning Linux Programming, 3rd Ed.,
2004.
3. Robert Love, Linux System Programming ,O'Reilly Media, 2nd Ed., 2007.
4. Yashwant Kanetkar , Unix Shell Programming, BPB, 7th Ed., 2007.
5. Bach, The Design of the Unix Kernel, PHI, 2000.
6. Christopher Diaz, Introduction to Unix, Linux, Pearson 3rd Ed.2009.
7. Evi Nemeth, Garth Snyer, Trent R. Hein, Linux Administrator Handbook, Pearson, 2nd
Ed., 2007.
8. Mark G. Sobell, A Practical Guide to Ubuntu Linux, Pearson, 2nd Ed., 2008.
9. Cox K, Red Hat Linux Administrators Guide, PHI, 2001.
10. Peterson Richard, The Complete References Linux, 2nd Ed., Tata McGraw Hill, 2000.
11. Tammy Fox, Red Hat Enterprise Linux 5.0 Administrator Unleashed, SAMS.
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Code No. MCA 303
Paper: Software Testing
LTC
31 4
INSTRUCTIONS TO PAPER SETTERS:
1. Question No. 1 should be compulsory and cover the entire syllabus. There should be 10
questions of short answer type of 2 marks each, having at least 2 questions from each unit.
2. Apart from Question No. 1, rest of the paper shall consist of four units as per the syllabus.
Every unit should have two questions to evaluate analytical/technical skills of candidate.
However, student may be asked to attempt only 1 question from each unit. Each question should
be 10 marks including subparts, if any.
OBJECTIVE: At the end of this course the student will be able to:
Appreciate the fundamentals of software testing and its application through the software
life cycle.
Develop skills in designing and executing software tests suitable for different stages in
the software life cycle.
Understand and appreciate the role of software testing in systems development,
deployment and maintenance.
Develop a continuing interest in software testing, and obtain satisfaction from its study
and practice.
Appreciate the responsibilities of software testers within software projects, the profession
and the wider community.
PRE-REQUISITE:
Software Engineering Concepts
UNIT - I
Introduction: What is software testing and why it is so hard?, Some Software Failures, Error,
Fault, Failure, Incident, Test Cases, Testing Process, Limitations of Testing, V Shaped Software
Life Cycle Model, No absolute proof of correctness, Overview of Graph Theory.
Verification Testing: Verification Methods, SRS Verification, Software Design Document
Verification, Code Reviews, User Documentation Verification, Software Project Audits.
[No. of Hrs.: 08]
UNIT - II
Functional Testing: Boundary Value Analysis, Equivalence Class Testing, Decision Table
Based Testing, Cause Effect Graphing Technique.
Structural Testing: Identification of Independent Paths: Control Flow Graph, DD-Paths,
Cyclomatic Complexity, Graph Matrix, Control Flow Testing, Data Flow Testing, Slice Based
Testing, Mutation testing.
[No. of Hrs.: 10]
UNIT - III
Use Case Testing: Use Case Diagrams and Use Cases, Generation of Test Cases from Use Cases,
Applicability. Validity Checks: Strategy for Data Validity, Guidelines for Generating Validity
Checks. Database testing.
Selection, Minimization, Prioritization of test cases for Regression Testing: Regression
Testing, Regression Test Case Selection, Prioritization guidelines, Priority category Scheme,
Code Coverage Techniques for Prioritization of Test Cases, Risk Analysis.
[No. of Hrs.: 12]
UNIT - IV
Testing Activities: Unit Testing, Levels of Testing, Integration Testing, System Testing,
Debugging
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Object Oriented Testing: Issues in Object Oriented Testing, Path testing, Class Testing, state
based testing, Object Oriented Integration and System Testing.
Metrics and Models in Software Testing: What are Software Metrics, categories of Metrics,
object Oriented Metrics used in testing, What should we measure during testing?, Software Quality
Attributes.
Prediction Model: Reliability Modes, Fault Prediction Model.
[No. of Hrs.: 12]
TEXT BOOKS:
1. William Perry, Effective Methods for Software Testing, John Wiley & Sons, New
York, Van Nostrand Reinhold, New York, 2nd Ed., 1995.
2. Cem Kaner, Jack Falk, Nguyen Quoc, Testing Computer Software, Van Nostrand
Reinhold, New York, 2nd Ed., 1993.
3. Boris Beizer, Software Testing Techniques, Second Volume, Van Nostrand Reinhold,
New York, . 2nd Ed., 1990.
4. Louise Tamres, Software Testing, Pearson Education Asia, 2002.
5. Aditya P. Mathur, Foundation of Software Testing, Pearson, 2008.
REFERENCES:
1. Paul C. Jorgenson, Software Testing A Craftsmans approach, CRC Press, 1997.
2. Roger S. Pressman, Software Engineering A Practitioners Approach, , McGraw-Hill
International Edition, New Delhi, 5th Ed., 2001.
3. Boris Beizer, Black-Box Testing Techniques for Functional Testing of Software and
Systems, John Wiley & Sons Inc., New York, 1995.
4. K. K. Aggarwal & Yogesh Singh, Software Engineering, New Age International
Publishers, New Delhi, 3rd Ed., 2003.
5. Marc Roper, Software Testing, McGraw-Hill Book Co., London, 1994.
6. Gordon Schulmeyer, Zero Defect Software, McGraw-Hill, New York, 1990.
7. Watts Humphrey, Managing the Software Process, Addison Wesley Pub. Co. Inc.,
Massachusetts, 1989.
8. Boris Beizer, Software System Testing and Quality Assurance, Van Nostrand
Reinhold, New York, 1984.
9. Glenford Myers, The Art of Software Testing, John Wiley & Sons Inc., New York,
1979.
10. Elfriede Dustin, Effective Software Testing: 50 Specific ways to improve your Testing,
Pearson, 2003.
11. Dorothy Graham, Erik Van Veenendaal, Isabel Evans and Rex Black, Foundation of
Software Testing, ISTQB Certification, PHI, 8th Ed., 2009.
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Code No.: MCA 305
Paper: Enterprise Computing in Java
LTC
3 1 4
INSTRUCTIONS TO PAPER SETTERS:
1. Question No. 1 should be compulsory and cover the entire syllabus. There should be 10 questions
of short answer type of 2 marks each, having at least 2 questions from each unit.
2. Apart from Question No. 1, rest of the paper shall consist of four units as per the syllabus. Every
unit should have two questions to evaluate analytical/technical skills of candidate. However,
student may be asked to attempt only 1 question from each unit. Each question should be 10 marks
including subparts, if any.
OBJECTIVE: In this course student will learn about J2EE technology and will be able to
develop dynamic websites. This course will explain how Enterprise JavaBeans (EJBs)
contain the application's business logic and business data.
PRE-REQUISITES:
Core JAVA
UNIT I
Introduction to J2EE and building J2EE applications, MVC architecture, Introduction to
servlets and its life cycle , problems with cgi-perl interface , generic and http servlet , servlet
configuration, various session tracking techniques, servlet context, servlet configuration, servlet
colloboration.
[No. of Hrs. : 10 Hrs]
UNIT II
JSP Basics and Architecture: JSP directives, Scripting elements, standard actions, implicit
objects, jsp design strategies.
Struts: Introduction of Struts and its architecture, advantages and application of Struts.
[No. of Hrs. : 12 Hrs]
UNIT III
EJB fundamentals: Motivation for EJB, EJB Echo system, J2EE technologies, Enterprise beans
and types, distributed objects and middleware, developing EJB components, remote local and
home interface, bean class and deployment descriptor.
[No. of Hrs.: 10 Hrs]
UNIT IV
Introducing session beans: Session beans life time, statefull and Stateless session beans beans,
lifecycle of session beans.
Introducing Entity beans: persistence concepts, features of entitiy beans , entity context,
Introduction to JMS & Message driven beans.
[No. of Hrs. : 10 Hrs]
TEXT BOOKS:
1. Ed Roman, Scott W Ambler, Tyler Jewell, Mastering Enterprise Java Beans, Wiley, 2nd
Ed., 2005.
2. Govind Sesadri , Enterprise Java Computing: Application and Architectures,
Cambridge University Publications, 1999.
3. Subrahamanyam Allamaraju, Cedric Buest, Professional Java Server Programming,
J2EE, Apress, 1.3 Ed., 2005.
3. Ivan Bayross and Sharanam Shah, Java Server Programming , Shroff .
4. John Hunt and Chris Loftus, Guide to J2EE: Enterprise Java Springer Verlag
Publications.
5. Govind Seshadri, Enterprise Java Computing: Application and Architectures,
Cambridge University Press, 1999.
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
REFERENECES:
1. Ted Neward, Effective Enterprise Java, Eddison -Wesley, 2004.
2 Jim Farley, William Crawford, Java Enterprise in a Nutshell, OReilly and Associates,
3rd Ed.
3. Austin Sincock , Enterprise Java for SAP , A Press Publications.
4. Joe Wigglesworth and McMilan Paula, Java Programming: Advanced Topic, Thomson,
3rd Ed., 2003.
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Code No. MCA 315
Paper: Mobile Computing
L T C
3 1 4
INSTRUCTIONS TO PAPER SETTERS:
1. Question No. 1 should be compulsory and cover the entire syllabus. There should be 10 questions
of short answer type of 2 marks each, having at least 2 questions from each unit.
2. Apart from Question No. 1, rest of the paper shall consist of four units as per the syllabus. Every
unit should have two questions to evaluate analytical/technical skills of candidate. However,
student may be asked to attempt only 1 question from each unit. Each question should be 10 marks
including subparts, if any.
OBJECTIVE: This course will cover a broad selection of topics in data communications,
resource management, network protocols, distributed computing, information management, user
interfaces, applications/services, and security. Students will learn the principles of Mobile
Computing and its enabling technologies, and explore a young but rich body of exciting ideas,
solutions, and paradigm shifts.
PRE-REQUISITE:
Operating Systems
Networking
Distributed Computing.
Programming skill in C/C++
UNIT - I
Cellular Mobile Wireless Networks: Systems and Design Fundamentals, Propagation Models
Description of Cellular system, Frequency Reuse, Co channel and Adjacent channel interference,
Propagation Models for Wireless Networks, Multipart Effects in Mobile Communication, Models
for Multipart Reception Evolution of Modern Mobile Wireless Communication System - First
Generation Wireless Networks, Second Generation (2G) Wireless Cellular Networks, Major 2G
standards, 2.5G Wireless Networks, Third Generation 3G Wireless Networks, Wireless Local
Area Networks (WLANs), All-IP Network: Vision for 4GIssues in Mobile computing, Wireless
Multiple Access protocols , channel Allocation.
[No. of Hrs.: 12]
UNIT II
Data management issues: mobility, wireless communication and portability, data replication
Schemes , basic concept of multihopping, Adaptive Clustering for mobile Network , Multicluster
Architecture.
[No. of Hrs.: 10]
UNIT III
Location Management: Introduction, Location Based Services , Automatically Locating Mobile
Users, Locating and Organizing Services, Is Use and future directions, mobile IP, Comparison of
TCP wireless.
[No. of Hrs.: 10]
UNIT - IV
Transaction management: Introduction, Data Dissemination, Cache Consistency, Mobile
transaction processing, mobile database research directions, Security fault tolerance for mobile
N/W.
[No. of Hrs.: 10]
TEXT BOOKS:
1. Schiller, Mobile Communications, Pearson.
2. Shambhu Upadhyaya, Abhjeet Chaudhary, Keviven Kwiat,Mark Weises, Mobile
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Computing, Kliuwer Acadmic Publishers.
3. UIWE Hansmann, Other Merk , Martin-S-Nickious, Thomas Stohe, Principles of Mobile
computing, Springer international Edition.
REFERENCES:
1. C. K. TOH , Mobile Adhoc Networks, TMH.
2. Sipra DasBit, Biplab K. Sikdar, Mobile Computing, PHI, 2009.
3. Kumkum Garg, Mobile Computing, Pearson.
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Code No.: MCA 333
Paper: Software Quality Management
LTC
31 4
INSTRUCTIONS TO PAPER SETTERS:
1. Question No. 1 should be compulsory and cover the entire syllabus. There should be 10 questions
of short answer type of 2 marks each, having at least 2 questions from each unit.
2. Apart from Question No. 1, rest of the paper shall consist of four units as per the syllabus. Every
unit should have two questions to evaluate analytical/technical skills of candidate. However,
student may be asked to attempt only 1 question from each unit. Each question should be 10 marks
including subparts, if any.
OBJECTIVE: This course covers the issues and techniques related to the Quality Management
of software. The course will be helpful for the students and to get acquaint with the industry
prespective towards software Quality. The content covers:
Basic Concepts of Software Quality.
Software Quality Assurance.
Formal Technical Reviews.
How it can be implemented.
Describe how to conduct formal technical reviews and why they are the most important
SQA activity.
PRE-REQUISITE:
Concepts of Software Engineering
UNIT - 1
Concepts and Overview: Concepts of Software Quality, Quality Attributes, Software Quality
Control and Software Quality Assurance, Evolution of SQA, Major SQA activities, Major SQA
issues, Zero defect Software, Elements of a complete Software Quality System.
Software Quality Assurance: The Philosophy of Assurance, The Meaning of Quality, The
Relationship of Assurance to the Software Life-Cycle, SQA Techniques.
[No. of Hrs.: 10]
UNIT - II
Tailoring the Software Quality Assurance Program: Reviews, Walkthrough, Inspection, and
Configuration Audits.
Evaluation: Software Requirements, Preliminary design, Detailed design, Coding and Unit Test,
Integration and Testing, System Testing, types of Evaluations.
Testing: Types of testing, Test Planning and conduct, Who does the testing?
[No. of Hrs.: 12]
UNIT - III
Configuration Management: Configuration Management Components, Maintaining Product
Integrity, Change Management, Version Control, Metrics, Configuration Management Planning.
Error Reporting: Identification of Defect, Analysis of Defect, Correction of Defect,
Implementation of Correction, Regression Testing, Categorization of Defect, Relationship of
Development Phases.
[No. of Hrs.: 10]
UNIT - IV
Defect Analysis: Analyzing concepts, Locating data, Defect Repair and closure, Selecting
metrics, Collecting measurements, Quality tools, Implementing defect analysis, Program Unit
Complexity.
Corrective Action as to Cause: Identifying the Requirement for Corrective Action, Determining
the Action to be Taken, Implementing the Correcting the corrective Action, Periodic Review of
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
Actions Taken.
Traceability, Records, Software Quality Program Planning, Software Quality System Plan,
Software Documentation.
[No. of Hrs.: 10]
TEXT BOOKS:
1. Robert Dunn, Software Quality Concepts and Plans, Prentice-Hall, 1990.
2. Alan Gillies, Software Quality, Theory and Management, Chapman and Hall,
1992.
3. John W. Horch , Practical Guide to Software Quality System, Artech House, 2003.
REFERENCE:
1. K.K. Aggarwal & Yogesh Singh, Software Engineering, New Age International
Publishers, 3rd Ed., 2008.
2. Daniel Freedman, Gerald Weinberg, Handbook of Walkthroughs, Inspections and
Technical Reviews, Dorset House Publishing, 1990.
3. Tom Gilb, Principles of Software Engineering Management, Addison-Wesley,
1988.
4. Tom Gilb, Dorothy Graham, Software Inspection Addison-Wesley, 1993.
5. Watts Humphrey, Managing the Software Process, Addison-Wesley, 1990.
6. Watts Humphrey, A Discipline for Software Engineering, Addison-Wesley, 1995.
7. Arthur Lowell, Improving Software Quality An Insiders guide to TQM, Wiley &
Sons,1993.
8. Mordechai Ben-Menachem, Gary S. Marless,Software Quality Producing Practical
Consistent Software, Cengage Learning, 2nd Ed., 2009.
9. Stephen H. Kan, Metrics and Models in Software Quality Engineering, Pearson, 2nd
Ed., 2003.
Syllabus of Master of Computer Applications (MCA), approved by MCA Coordination Committee on 7th May 2010 &
Sub-Committee Academic Council held on 31st May 2010. W.e.f. academic session 2010-11
