REGULATIONS -2009 FOR M.TECH / MCA / M. Sc DEGREE PROGRAMMES (with modifications incorporated in June 2011) 1.0 PRELIMINARY DEFINITIONS AND NOMENCLATURE In these Regulations, unless the context otherwise requires i) ii) "Programme" means Post Graduate Degree Programme (M.Tech./ MCA / M.Sc.) "Course" means a theory or practical subject that is normally studied in a semester, like Applied Mathematics, Structural Dynamics, Computer Aided Design, etc. "University" means B.S.Abdur Rahman University, Chennai, 600048. "Institution" unless otherwise specifically mentioned as an autonomous or off campus institution means B.S.Abdur Rahman University. "Academic Council" means the Academic Council of the University. 'Dean (Academic Courses)' means Dean (Academic Courses) of B.S.Abdur Rahman University.

iii) iv) v) vi)

vii) 'Dean (Students)' means Dean(Students) of B.S.Abdur Rahman University. viii) "Controller of Examinations" means the Controller of Examinations of B.S.Abdur Rahman University who is responsible for conduct of examinations and declaration of results. 2.0 2.1 PROGRAMMES OFFERED, MODE OF STUDY AND ADMISSION REQUIREMENTS P.G. Programmes Offered The various P.G. Programmes and their modes of study are as follows:

M.Tech. M.Tech. M.C.A. M. Sc.


Full Time Part Time – Day / Evening Full Time Full Time



Sl. No. 01. Name of the Department Civil Engineering P.G. Programmes offered M.Tech. (Structural Engineering) M.Tech. (Construction Engineering and Project Management) 02. Mechanical Engineering M.Tech. (CAD - CAM) Qualifications for admission B.E / B.Tech. (Civil Engineering) / (Structural Engineering) B.E. / B.Tech. (Civil Engineering) / (Structural Engineering) B.E. / B.Tech. (Mechanical / Auto / Manufacturing / Production / Industrial Engineering) B.E. / B. Tech. (Mechanical / Auto / Manufacturing / Production / Industrial Engineering) B. E. / B. Tech. degree Mech./ Production / Polymer Science or Engg or Tech/Rubber Tech/ M.Sc(Polymer Sc./Chemistry Appl. Chemistry) B.E / B.Tech. in (EEE/ICE/EIE) B.E / B.Tech. in (EEE/ICE/EIE) B.E./ B.Tech. in ECE / Electronics / EIE B.E./ B.Tech. in ECE / Electronics / EIE B.E./B.Tech. (ECE/EEE/Electronics/ EIE/ICE) M.Sc (Physics/Materials Science/ Electronics/ Photonics) B.E./B.Tech. (EIE/ICE/Electronics/ ECE/EEE) B.E. /B.Tech. (CSE/IT/ECE/EEE/EIE/ ICE/Electronics / MCA) B.E. / B.Tech. (CSE / IT) MCA B.E /B.Tech. (IT/CSE/ECE/EEE/EIE/ ICE/Electronics) MCA Any degree. Must have studied Mathematics / Statistics /Computer oriented subject. Any degree. Must have studied Mathematics / Statistics /Computer oriented subject. B.Sc. (Mathematics) of B.Sc. (Applied Science) B.Sc (Chemistry) of B.Sc. (Applied Science)

M.Tech. (Manufacturing Engineering)


Polymer Technology

M.Tech. (Polymer Technology)


Electrical and Electronics Engineering Electronics and Communication Engineering ECE Department jointly with Physics Department Electronics and Instrumentation Engineering Computer Science and Engineering

M.Tech. (Power Systems Engg) M.Tech. (Power Electronics & Drives) M.Tech. (Communication Systems) M.Tech. (VLSI and Embedded Systems) M.Tech. (Optoelectronics and Laser Technology)




M.Tech. (Electronics and Instrumentation Engineering) M.Tech. (Computer Science and Engineering) M.Tech. (Software Engineering)


09 10

Information Technology Computer Applications

M.Tech. (Information Technology) M.C.A.

M.Tech. (Systems Engineering and Operations Research) 11 12 Mathematics Chemistry M.Sc. (Actuarial Science) M.Sc.(Chemistry)


the candidates are required to attend only evening classes.3. Such conversion is not permitted in the middle of a semester.Evening In this mode of study.2 A full time student.M.3 Part time . number of attempts in qualifying examination and physical fitness will be as prescribed by the Institution from time to time.2. Permission may be granted based on merits of the case. 2. Part Time . 2.1 Full-time 2.4 Part time . the candidates are required to attend classes for the courses registered along with full time students.Tech SOFTWARE ENGINEERING 2. ADMISSION REQUIREMENTS 2.3. he/she shall have a minimum level of proficiency in the appropriate programme/courses as prescribed by the institution from time to time. if the student satisfies the clause 2.Day time In this mode of study.2 MODES OF STUDY Candidates admitted under "Full-Time" shall be available in the institution during the complete working hours for curricular. 2. 2.2.3. shall apply to the Head of the Institution through the Head of the Department.Tech.2. 2.3. who has completed all non-project courses desiring to do the Project work in part-time mode for valid reasons.5 A part time student is not permitted to convert to the full time mode of study.3. 5 .5 A candidate eligible for admission to M.2. which may be prescribed by the institution from time to time.2..3.4 All part-time candidates should satisfy other conditions regarding experience. 2.3.1 Candidates for admission to the first semester of the Master's Degree Programme shall be required to have passed an appropriate degree examination of this University as specified in Table 1 or any other examination of any University or authority accepted by the University as equivalent thereto.2 Notwithstanding the qualifying examination the candidate might have passed. 2.3 Eligibility conditions for admission such as class obtained. co-curricular and extracurricular activities assigned to them.5 of this Regulations. 2. sponsorship etc. 2.Day Time programmeshall have his/her permanent place of work within a distance of 65km from the campus of the institution.

End-semester examinations will follow immediately after these working days.G.3 3. DURATION AND STRUCTURE OF THE P.4 HvÃI‚Âsà Tr€r†‡r…†Ã 4 6 6 4 Hh‘ÃI‚Âsà Tr€r†‡r…†Ã 8 12 12 8 The P.A.Tech.A. 3. programmes shall be approved by the Academic Council. vi. (Full Time) 3. programme.G.Tech SOFTWARE ENGINEERING 2.G. (Full Time) M. Practical training The curriculum and syllabi of all the P. iii. iv. He/ she shall have his/her place of work within a distance of 65 km from the campus of the institution. Part Time . programmes will consist of the following components as prescribed in the respective curriculum Core courses Elective courses Project work / thesis / dissertation Laboratory Courses Case studies Seminars vii. 6 3. v.3. (Full Time) M. PROGRAMME The minimum and maximum period for completion of the P.2 i.Tech. The number of credits to be earned for the successful completion of the programme shall be specified in the curriculum of the respective specialization of the P.M.(Part Time) M.G.B.5 .G. ii.6 A candidate eligible for admission to M.1. Programmes are given below: Q…‚t…h€€rà M.C.Evening programme shall have a working experience of 2 years at least at supervisory level.Sc. Each academic semester shall normally comprise of 75 to 80 working days spread over sixteen weeks. 3.0 3.

(Full Time) Non-project Semester 15 to 23 6 to 12 12 to 25 15 to 25 Project semester 12 to 20 12 to 16 12 to 20 12 to 20 3. Programmes either within a Department or from other Departments up to a maximum of three courses during the period of his/her study.Sc.G.Tech SOFTWARE ENGINEERING 3. programmes shall be so designed that the minimum prescribed credits required for the award of the degree shall lie within the limits specified below: Programme M.9 3.G. provided the Heads of the Departments offering such courses also agree.A.8 Credits will be assigned to the courses for all P. To help the students to take up special research areas in their project work and to enable the department to introduce courses in latest/emerging areas in the curriculum.Sc Minimum prescribed credit range 70 to 80 130 to 140 74 to 80 3.7 * * * * 3. A candidate may be permitted by the Head of the Department to choose electives offered from other P. Programme M.M. A candidate may be 7 3.G. (Full Time) M.G.Tech.A M.C. programmes as given below: One credit for one lecture period per week One credit for one tutorial period per week One credit each for seminar/practical session of two or three periods per week One credit for four weeks of practical training The number of credits registered by a candidate in non-project semester and project semester should be within the range specified below: P. M. (Full Time) M.Tech.Tech. "Special Electives" may be offered.11 .6 The curriculum of P.10 The electives from the curriculum are to be chosen with the approval of the Head of the Department.C. (Part Time) M.

following the preliminary work carried out in Phase-1 during the previous semester.14 3.14. Practical training or industrial attachment.) shall be pursued for a minimum of 16 weeks during the final semester.6 If a candidate fails to submit the Project Report / Thesis / Dissertation on or before the specified deadline he / she is deemed to have not completed the Project Work / Thesis / dissertation and shall re-register the same in a subsequent semester.14. 3. 8 .Tech SOFTWARE ENGINEERING permitted to register for a "Special Elective" up to a maximum of three credits during the period of his/her study.14. if specified in the curriculum shall be of not less than four weeks duration and shall be organized by the Head of the Department. In such cases.14. 3. Subsequently. 3.7 A student who has acquired the minimum number of total credits prescribed in the Curriculum for the award of the Masters Degree will not be permitted to enroll for more courses to improve his/her cumulative grade point average (CGPA). be permitted to work on the project in an Industrial/Research Organization. 3.M.5 The deadline for submission of final Project Report / Thesis / Dissertation is within 30 calendar days from the last working day of the semester in which Project / Thesis / Dissertation is done. in which the special elective course is offered. 3.4 The Project Report/Thesis / Dissertation report / Drawings prepared according to approved guidelines and duly signed by the supervisor(s) and the Head of the Department shall be submitted to the Head of the Institution. PROJECT WORK/THESIS/DISSERTATION 3. 3. such course shall be ratified by the Board of Studies and Academic Council.13 The medium of instruction. examination.II in the case of M.14. the project work shall be jointly supervised by a supervisor of the Department and an Engineer / Scientist from the organization and the student shall be instructed to meet the supervisor periodically and to attend the review committee meetings for evaluating the progress.12 3.3 Project work / Thesis / Dissertation (Phase .14.Tech. 3. with the approval of the Head of the Institution. provided the syllabus of this course is recommended by the Head of the Department and approved by the Dean (AC) before the commencement of the semester. on the recommendation of Head of the Department.1 Project work / Thesis / Dissertation shall be carried out under the supervision of a qualified teacher in the concerned Department. in certain cases.14. seminar and project/thesis/ dissertation reports will be English.2 A candidate may however.

The basic responsibilities of the Class Committee are to review periodically the progress of the classes.G.2 5.Ex-Officio Members Professor in-charge of the P. CLASS COMMITTEE Every class of the P.Tech SOFTWARE ENGINEERING 4. The Class Committee is required to meet at least thrice in a semester. COURSE COMMITTEE Each common theory course offered to more than one group of students shall have a "Course Committee" comprising all the teachers teaching the common course with one of them nominated as Course coordinator. Each Class Committee will communicate its recommendations to the Head of the Department and the Head of the Institution. to discuss problems concerning curriculum and syllabi and the conduct of the classes.3 The Class Committee shall be constituted by the respective head of the department of the students. The nomination of the Course coordinator shall be made by the Head of the Department / Head of the Institution depending upon whether all the teachers 9 5. The type of assessment for the course will be decided by the teacher in consultation with the Class Committee and will be announced to the students at the beginning of the semester. The class committee. One or two students of the class. iii. constituted by the Head of the Department as follows: Teachers of all courses of the programme One senior faculty preferably not offering courses for the class.0 . iv. v.0 5. once at the beginning of the semester. 5. will also be responsible for finalization of the semester results. 5.0 FACULTY ADVISER To help the students in planning their courses of study and for getting general advice on academic programme. the concerned department will assign a certain number of students to a faculty member who will be called the Faculty Adviser.Ex-Officio Member. Programme will have a Class Committee. as chairperson. and once in between.M.1 i.G.4 6. Programme . without the student members. nominated by the Head of the Department. ii. another time after the end-semester examination to finalise the grades. Faculty Advisers of the class .

6. For the subsequent semesters registration for the courses will be done by the student during a specified week before the end-semester examination of the previous semester. with the approval of Dean (AC). At the time of enrolment a student can drop a course registered earlier and also substitute it by another course for valid reasons with the consent of the Faculty Adviser.5 7. A student will become eligible for enrolment only if he/she satisfies clause 9 and in addition he/she is not debarred from enrolment by a disciplinary action of the Institution. The Registration form is filled in and signed by the student and the Faculty Adviser. 10 .6 Withdrawal from a course registered is permitted up to one week from the date of the completion of the first assessment test.2 7. The Course Committee shall meet as often as possible and ensure uniform evaluation of the tests and arrive at a common scheme of evaluation for the tests. 7. is permitted. Wherever it is feasible.1 Courses withdrawn will have to be taken when they are offered next if they belong to the list of core courses. project and seminar to be taken in different semester with the number of credits. The concerned Faculty Adviser will be present and guide the students in the registration/enrolment process. 7. From the second semester onwards all students shall pay the prescribed fees and enroll on a specified day at the beginning of a semester. Late registration will be permitted with a prescribed fine up to two weeks from the last date specified for registration. Late enrolment will be permitted on payment of a prescribed fine up to two weeks from the date of commencement of the semester.3 7. on the recommendation of the HOD. Change of a course within a period of 15 days from the commencement of the course. The curriculum gives details of the core and elective courses.1 REGISTRATION AND ENROLMENT For the first semester every student has to register and enroll for the courses he/she intends to undergo on a specified day notified to the student. The student should consult his/her Faculty Adviser for the choice of courses. 7.Tech SOFTWARE ENGINEERING teaching the common course belong to a single department or to several departments.4 7. the Course Committee may also prepare a common question paper for the test(s).0 7.M.

A student will have to register within the time stipulated in the announcement.4 Withdrawal from a summer term course is not permitted.1).0 TEMPORARY WITHDRAWAL FROM THE PROGRAMME A student may be permitted by the Head of the Institution to temporarily withdraw from the programme up to a maximum of two semesters for reasons of ill health or other valid grounds. 9.7.7 SUMMER TERM COURSES 7. 7.7. The assessment procedure in a summer term course will also be similar to the procedure for a regular semester course.7. A student has to pay the fees as stipulated in the announcement. They may also opt to redo such courses during regular semesters with slotted time-tables.M. No substitute examination will be held for the summer term courses. However the total duration for completion of the programme shall not exceed the prescribed number of semesters (vide clause 3. Students with U grades will have the option either to write semester end arrears exam or to redo the courses during summer / regular semesters with slotted time-table.Tech SOFTWARE ENGINEERING 7.3 Fast-track summer courses of 30 periods for 3 credit courses and 40 periods for 4 credit courses will be offered for students with I grades. if they wish to improve their continuous assessment marks also.2 Summer term courses will be announced by the Head of the Institution at the end of the even semester before the commencement of the end semester examinations. 7. 7.0 9.1 MINIMUM REQUIREMENTS TO REGISTER FOR PROJECT / THESIS / DISSERTATION A candidate is permitted to register for project semester. No student should register for more than three courses during a summer term. if he/she has earned the minimum number of credits specified below: 11 . 8.1 Summer term courses may be offered by a department on the recommendation by the Departmental Consultative Committee and approved by the Head of the Institution.7.

(Full time) M.2 12 . which will tend to bring down the prestige of the institution. Any act of indiscipline of a candidate reported to the Head of the Institution will be referred to a Discipline and Welfare Committee for taking appropriate action. (Full time) M. If the course is a core course.Tech. he/she has to earn the required credits (at least to the extent of minimum credit specified in clause 9.2 M.0 10.M. failing which the student shall be awarded "I" grade in that course. subject to a a maximum relaxation of 25% for genuine reasons like on medical grounds . DISCIPLINE Every candidate is required to observe discipline and decorous behaviour both inside and outside the campus and not to indulge in any activity. (Part-time ) M.3 11. M.1) and then register for the project semester. (Full-time) Hvv€ˆ€ÃI‚ÂsÃp…rqv‡†Ã‡‚ÃirÃrh…rqǂÃr…‚yÃs‚…à ƒ…‚wrp‡Ã†r€r†‡r… 18 (III semester) 18 (V semester) 45 (VI semester) 28 (IV semester) 9.3 10. 9. to become eligible to appear for the end-semester examination in that course.1 10.Sc. Every candidate should have been certified by the HOD that his / her conduct and discipline have been satisfactory..A.: If the candidate has not earned minimum number of credits specified. representing the University in approved events etc.C.Tech SOFTWARE ENGINEERING Q…‚t…h€€r M.1 11. A student shall earn 100% attendance in the contact periods of every course.: If the candidate has not earned the required minimum number of credits specified he/she has to earn the required credits (at least to the extent of minimum credits specified in clause 9.Tech.1) and then register for the project work in subsequent semesters.C.A.Tech.0 11. ATTENDANCE Attendance rules for all Full Time Programme and Part time .2 10. the candidate should register for and repeat the course when it is offered Time Programmes are given in the following sub-clauses.

A. the candidate shall submit a certificate from the organization where he/she has undergone training and also a brief report.Sc.2 12.4 13. at the end of the semester.1./ M.2 The markings for all tests. The evaluation of the Project work will be based on the project report and a Viva-Voce Examination by a team consisting of the supervisor concerned. normally a minimum of two assessments will be made during the semester. At the end of practical training or industrial attachment. / M. an Internal Examiner and External Examiner to be appointed by the Controller of Examinations.0 12.) For lecture-based courses.G. The evaluation will be made based on this report and a Viva-Voce Examination.C.1 ASSESSMENTS AND EXAMINATIONS The following rule shall apply to the full-time and part-time P.Tech SOFTWARE ENGINEERING 12. programmes (M.M.Tech. The assessments may be combination of tests and assignments. laboratory work and examinations will be on absolute basis. 13 .1 13. The assessment procedure as decided at the Class Committee will be announced to the students right at the beginning of the semester by the teacher and informed to Dean(AC) 12. tutorial assignments (if any). WEIGHTAGES The following shall be the weightages for different courses: i) Lecture based course Two sessional assessments End-semester examination ii) Laboratory based courses Laboratory work assessment End-semester examination iii) Project work Periodic reviews Evaluation of Project Report by External Examiner Viva-Voce Examination 50% 20% 30% 75% 25% 50% 50% 12. conducted internally by a Departmental Committee constituted by the Head of the Department. The final percentage of marks is calculated in each course as per weightages given in clause 13. in each lecture based course.0 13.3 There shall be one examination of three hours duration.

COURSEWISE GRADING OF STUDENTS AND LETTER GRADES: Based on the semester performance. denotes inadequate attendance and hence prevention from End Semester examination.M. denotes unsuccessful performance in a course.Tech SOFTWARE ENGINEERING 14.0 SUBSTITUTE EXAMINATION 14. such as accident or admissions to a hospital due to illness.2 15. However. permissions to take up a substitute examination will be given under exceptional circumstances. 14 .0 15. each student is awarded a final letter grade at the end of the semester in each course. but grading has to be relative grading 14. However the substitute tests and examination for a course will be conducted within two weeks after the last day of the end-semester examinations.. etc. A student who misses any assessment in a course shall apply in a prescribed form to the Dean(AC) through the Head of the department within a week from the date of missed assessment.1 Gr‡‡r…Ãt…hqrà S A B C D E U I W B…hqrÂv‡†Ã 10 9 8 7 6 5 0 - Flexible range grading system will be adopted "W" "I" "U" denotes withdrawal from the course.1 A student who has missed for genuine reasons any one of the three assessments including end-semester examination of a course may be permitted to write a substitute examination. The letter grades and the corresponding grade points are as follows.

The grade acquired by the student later will be indicated in the grade sheet of the appropriate semester.1 the Letter Grades awarded to the students in the each course shall be announced on the departmental notice board after duly approved by the Controller of Examinations. A letter grade U in any course implies unsuccessful performance in that course.2 A student is considered to have completed a course successfully and earned the credits if he / she secure five grade points or higher. he/she can apply for revaluation after paying the prescribed fee for the purpose. If the student is awarded "I". 15 16. A course successfully completed cannot be repeated for any reason.0 16. In case any student feels aggrieved.0 18. COURSE REPETITION AND ARREARS EXAMINATION A student should register to re-do a core course wherein "I" or "W" grade is awarded.2 18. or "W" grade in an elective course either the same elective course may be repeated or a new elective course may be taken. it may jointly revalue the answer script and forward the revised mark to the Controller of Examinations with full justification for the revision if any. A committee will be constituted by the Controller of Examinations comprising the Chairperson of the concerned Class Committee (Convener).1 16.1 . METHOD OF AWARDING LETTER GRADE: A final meeting of the Class Committee without the student member(s) will be convened within ten days after the last day of the semester end examination.0 17.2 17. containing the final grade and three copies with the absolute marks and the final grade should be submitted by the teacher to the concerned Class Committee Chairman. If the Committee finds that the case is genuine. After finalisation of the grades at the class committee meeting the Chairman will forward two copies of each to the Controller of Examinations and the other copies to the Head of the Department in which course is offered.1 17. The letter grades to be awarded to the students for different courses will be finalized at the meeting. The “U” grade once awarded stays in the grade sheet of the students and is not deleted when he/she completes the course successfully later.Tech SOFTWARE ENGINEERING 15. DECLARATION OF RESULTS: After finalisation by the Class Committee as per clause 16.M. within two weeks from the commencement of the semester immediately following the announcement of results. Three copies of the results sheets for each course. the teacher concerned and another teacher of the department who is knowledgeable in the concerned course.

the total credits earned in that semester. The grade sheet issued at the end of the semester to each student will contain the following: (i) (iii) the credits for each course registered for that semester.1 19. along with the regular examinations of next semester courses. (iv) the Grade Point Average (GPA) of all the courses registered for that semester and the Cumulative Grade Point Average (CGPA) of all the courses taken up to that semester.Tech SOFTWARE ENGINEERING 18. will be used for grading along with the marks earned in the end-semester arrear examination for the course.2 A student who is awarded “U” grade in a course shall write the end-semester examination as arrear examination .2 The GPA will be calculated according to the formula *3$ 6 & L . 19.M. The marks earned earlier in the continuous assessment tests for the course.0 GRADE SHEET 19. at the end of the next semester. (ii) the performance in each course by the letter grade obtained.

*3 .

Grade point obtained in the i th course For the cumulative grade point average (CGPA) a similar formula is used except that the sum is over all the courses taken in all the semesters completed up to the point in time.50 and above. having completed within a period of 2 semesters beyond the programme period. having completed in first appearance in all courses 6.50 and above. I and W grades will be excluded for CGPA calculations. All others 8yh††vsvph‡v‚Ã First class with Distinction First Class Second Class 16 . 19. U. I and W grades will be excluded for GPA calculations.3 Classification of the award of degree will be as follows: 8BQ6à 8. 6& L L L L where Ci is the number of credits assigned for i th course GPi .

of semesters reckoned from his/her commencement of study plus two semesters.0 registered for and undergone all the core courses and completed the Project Work. a candidate should have passed the examination in all courses within the specified minimum number. has no dues to the Institution. The candidates who do not satisfy the above two conditions will be classified as second class. To be eligible for First Class. to be eligible for First Class with Distinction. Programme within a minimum period covered by the minimum duration (clause 3.2 21. For the purpose of classification. a candidate should not have obtained U or I grade in any course during his/her study and should have completed the P.Tech SOFTWARE ENGINEERING However. the authorized break of study will not be counted. CGPA will be considered up to three decimal places. if any.1) plus authorized break of study.1 ELIGIBILITY FOR THE AWARD OF THE MASTERS DEGREE A student shall be declared to be eligible for the award of the Masters Degree. For the purpose of comparison of performance of candidates and ranking.M. the CGPA will be rounded to first decimal place. if any (clause 8). For this purpose. 20 20.G. the Academic Council has the right to modify any of the above regulations from time to time. Hostels and Library. if he/she has: i) ii) iii) iv) v) 20. POWER TO MODIFY: Notwithstanding all that have been stated above. successfully completed the field visit/industrial training. successfully acquired the required credits as specified in the Curriculum corresponding to his/her programme within the stipulated time. as prescribed in the curriculum. ********* 17 . no disciplinary action is pending against him/her The award of the degree must be approved by the University.

Tech SOFTWARE ENGINEERING (Four Semesters / Full time) CURRICULUM SEMESTER I Sl. No Subject Code Theory 1 2 3 4 5 6 1 2 MA621 CS621 CS622 CS623 CS624 CS625 CS626 CS627 Statistical Methods and Queuing Theory Object Oriented Software Engineering 3 3 1 0 0 0 0 0 1 1 0 0 0 0 0 0 3 3 4 3 3 3 3 3 2 2 23 Subject L T P C TC Software Requirements Analysis And Estimation 3 System Dynamics Computer Networks and Management Operating Systems Case Tools Lab Software Development Platforms and Languages 3 3 3 0 0 Practical 18 .Tech SOFTWARE ENGINEERING M.M.

M.IV 3 3 3 3 0 0 0 0 0 2 0 0 3 4 3 3 19 .II 3 3 3 3 3 3 0 0 0 0 0 0 0 0 0 0 0 0 3 3 3 3 3 3 Software Testing and Measurements Lab 0 SEMESTER III Theory 1 2 3 4 Practical 1 CS723 Project .Phase I 0 0 12 6* 13 CS721 CS722 Information Security Cloud Computing Elective .Tech SOFTWARE ENGINEERING SEMESTER II Theory 1 2 3 4 5 6 Practical 1 2 3 CS632 CS633 CS634 Case Study 1: Software Design Case Study 2: Software Project Management 0 0 0 0 1 2 2 3 1 1 2 22 CS628 CS629 CS630 CS631 Software Design and Architecture Integrated Software Project Management Software Testing and Quality Assurance Advanced Database Technologies Elective -I Elective .III Elective .

I) of III Semester will be accounted along with project work (Phase .M.Tech SOFTWARE ENGINEERING SEMESTER IV Practical 1 CS723 Project .II) of IV Semester. Total Total Credits Total Number of Theory Courses Total Number of Case Studies Total Number of Practical Courses 18 76 16 2 3 20 .Phase II 0 0 35 18* * Credits for project work (Phase .

No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Subject Code CSY 101 CSY 102 CSY 103 CSY 104 CSY 105 CSY 106 CSY 107 CSY 108 CSY 109 CSY 110 CSY 111 CSY 112 CSY 113 CSY 114 CSY 115 CSY 116 CSY 117 CSY 118 CSY 119 CSY 120 CSY 121 CSY 122 CSY 123 CSY 124 CSY 019 Subject L T P C Theory of Computation 3 0 0 3 Soft Computing 3 0 0 3 Mobile Computing 3 0 0 3 Distributed Systems 3 0 0 3 Web Technology 3 0 0 3 XML and Web Services 3 0 0 3 Formal Methods in Software Engineering 3 0 0 3 Multimedia Systems 3 0 0 3 Software Agents 3 0 0 3 Embedded Systems 3 0 0 3 IT Systems Management 3 0 0 3 Mobile Adhoc Networks 3 0 0 3 Data Warehousing and Data Mining 3 0 0 3 Performance Evaluation of Computer Systems and 3 0 0 3 Networks Agent Based Intelligent Systems 3 0 0 3 Personal Software Process 3 0 0 3 Team Software Process 3 0 0 3 Software Engineering for Image Processing 3 0 0 3 Service Oriented Architecture 3 0 0 3 Grid Computing 3 0 0 3 Pervasive Computing 3 0 0 3 User Interface Design 3 0 0 3 Software Maintenance 3 0 0 3 Multimodal Computing 3 0 0 3 Research Methodology for computer Scientist 3 0 0 3 21 .Tech SOFTWARE ENGINEERING LIST OF ELECTIVE COURSES Sl.M.

Freund J. and Mittal S. T. Gupta S. Uniform. Pragati Prakashan. Walpole R. Pearson Education. "Probability and Statistics for Engineers". 4. 2001.22 factorial design. 7th edition. Sultan Chand & Sons.Function of random variables. Pearson Education Edition. UNIT IV DESIGN OF EXPERIMENTS 9 Analysis of variance . Meerut. New Delhi. 2.Randomized block design . Exponential distributions .Tests based on Normal. "Fundamentals of Mathematical Statistics".Moments generating functions and their properties . Normal.H. . 2002. and Kapur V.S..Random variables .C.K.Moments . Asia. 2000.L.Customer impatience . "Fundamentals of Mathematical Statistics".M. 7th edition. Delhi.I MA 621 STATISTICAL METHODS AND QUEUING THEORY UNIT I PROBABILITY AND RANDOM L T P C 3 1 0 4 10 Probability .Binomial. 1999. Chi square and F distributions for mean.A. UNIT II ESTIMATION THEORY 8 Partial and Multiple correlations . 1994.Tech SOFTWARE ENGINEERING SEMESTER . Myer R.E. Gupta.. New Delhi. New Delhi.Queuing applications. UNIT V QUEUING THEORY 9 Single and Multiple server Markovian Queuing models .Latin square design .E. New Delhi. Goel B.Completely randomized design . "Operations Research". 3.K. 2. and Miller I. "Operations Research: An Introduction". UNIT III TESTING OF HYPOTHESIS 9 Basic definitions of statistical hypothesis . TOTAL = 45 TEXT BOOKS 1. 5th edition. 22 REFERENCES 1. 2002.Estimation of parameters using maximum likelihood estimator and method of moments. K. Sultan Chand and Sons.One way and two way classifications . Poisson. S. Prentice Hall of India. Taha H.R. "Probability and Statistics for Engineers and Scientists". variance and proportion.Partial and multiple regressions . Geometric. and Kapoor V.K.C. Myer S. and Ye.

M. 4.The testing process .Design model Implementation model-Test model. Addison Wisely. 1992. 2. Modeling with UML: Basic building blocks of UML.Software life cycle models .Basic structural modeling .Action & use cases . UNIT III ARCHITECTURE AND MODELING WITH UML 9 Model architecture . Tata McGraw . Bernd Bruegge and Alan H Dutoit. Pearson Education.Case studies.Tech SOFTWARE ENGINEERING CS 621 UNIT I OBJECT ORIENTED SOFTWARE ENGINEERING INTRODUCTION TO SOFTWARE ENGINEERING L T P C 3 0 0 3 9 Software engineering development . Ivar Jacobson and Magnus Christenson. "Classical & Object Oriented Software Engineering with UML and Java".Hill. Managing requirements elicitation. TOTAL = 45 REFERENCES 1.Managing testing -State based testing and Data flow testing for classes .Requirements model .Standards for developing life cycle models.Analysis model .Requirements elicitation activities.Hill. UNIT II OBJECT METHODOLOGY & REQUIREMENT ELICITATION 9 Introduction to Object Oriented Methodology . 23 .Overview of requirements elicitation. UNIT V TESTING OBJECT ORIENTED SYSTEMS 9 Introduction -Testing activities and techniques . "Object . Requirements model .Lethbridge and Robert Laganiere. Timothy C.System design: Design concepts and activities .Design models . Tata McGraw .Oriented Software Engineering". 2004.Dynamic modeling and testing . 2nd edition. 2004. 4th edition. 2001. Stephen R. "Object Oriented Software Engineering: A use Case Driven approach". 3. Scach.UML diagrams. "Object oriented Software Engineering: Practical Software development using UML and Java".A conceptual model of UML. UNIT IV SYSTEM ANALYSIS AND DESIGN 9 Analysis model .Block design -Testing.

Software development roles .Fact .Problems of scope .Stakeholders needs & analysis.An elicitation methodology framework A requirements elicitation process model .Requirements management Principles and practices .Requirements documentation .Requirements elicitation problems . UNIT III REQUIREMENTS ANALYSIS 9 Identification of functional and non functional requirements .Validation .Commercial life cycle model .Evaluation and rationalization .Requirements .Problems of volatility Current elicitation techniques . UNIT II REQUIREMENTS ELICITATION 9 The process of requirements elicitation . UNIT V SOFTWARE ESTIMATION & COSTING 9 Software Requirements Management . UNIT IV REQUIREMENTS DEVELOPMENT 9 Requirements analysis .Identification of performance requirements .Requirements expression and analysis .Use case specification document .attributes.Software development process kernels . Links in requirements chain TOTAL = 45 24 .finding .Supplementary specification document .Vision development .Information gathering .Analysis Feasibility and internal compatibility of system requirements .Methodology over method Integration of techniques . Requirements Traceability Matrix.Problems of understanding .Requirements gathering .Prioritization .Tech SOFTWARE ENGINEERING CS 622 UNIT I SOFTWARE REQUIREMENTS ANALYSIS AND ESTIMATION REQUIREMENTS ENGINEERING OVERVIEW L T P C 3 0 0 3 9 Software requirement overview .Identification of safety requirements .Methods for software prototyping .Requirements development workflow . Change Management Process.Integration and validation.Fundamentals of requirements development Requirements attributes guidelines document .Definition of human requirements baseline.Evolutionary prototyping -Throwaway prototyping.M.

1988. "Software Project management: A Unified Framework". 2004. "Requirements Engineering and Rapid Development". "Requirements Engineering: A Good Practice Guide". Microsoft Press. 3. "Managing Software Requirements: A Use Case Approach". Addison Wesley.2 Summer.R. 1998. Ian Graham. Addison Wesley.M. 4. No. 5.Based Cost System?" Journal of Cost Management. Cooper . "The Rise of Activity . 1998. Karl Eugene Wiegers. 2003. 7.Tech SOFTWARE ENGINEERING REFERENCES 1. 2nd edition. Vol. Ian Somerville and Pete Sawyer. 2. McConnell. "Software Project: Survival Guide". 25 . Dean Leffingwell and Don Widrig. 2000. Royce W. 1998. Addison Wesley. "Software Requirements". 6. Pearson Education. Word Power Publishers.Based Costing .Part One: What is an Activity . 6th edition. S.2.

2002.Problem understanding .Drifting goals . McGraw Hill/Irwin.Discovery and diagnosis. "The Art of System Thinking. 26 . UNIT II SYSTEM THINKING MINDSET 9 Holistic thinking .perspective .M.M.Shifting the burden. Dennis Sherwood. "Seeing the forest for the trees: A Manager's Guide to Applying Systems Thinking". 2000.Escalation . UNIT V SYSTEM ARCHETYPES 9 9 Limit to growth .Fixes that fail .Structure and behavior of dynamic systems. 1997.Success to the successful . 3. John D.Sterman.Structure Learning organization.Characteristics of complex problems . "Business Dynamics: Systems Thinking and Modeling from Complex World".Pattern . "The fifth Discipline: The Art and Practice of learning Organization".Alterable and Constraints .Learning in and about complex systems . TOTAL = 45 REFERENCES 1." Thorsons.Dynamics of simple structure. Senge P. Joseph O'Connor and Ian McDermott.Tech SOFTWARE ENGINEERING CS 623 UNIT I SYSTEM DYNAMICS COMPLEXITY IN REAL WORLD L T P C 3 0 0 3 9 Complexity . 1990. Doubleday. 2. UNIT IV TOOLS FOR SYSTEM THINKING Causal loop diagram . Nicolas Brealey.Multi levels of reasoning: Event . 4.Stakeholder needs .Stocks and flows . UNIT III MULTI MODELING APPROACH 9 Multi .

Securing TCP connections: SSL .peer applications .The Internet Protocol (IP): Routing algorithms .Securing wireless LANs .Connection . loss.History of computer networking and the internet.End -Point authentication .Multiplexing and demultiplexing Connectionless transport: User Datagram Protocol .Ethernet . UNIT II APPLICATION AND TRANSPORT LAYER 9 Principles of network applications .File Transfer: File transfer protocol .Message integrity .Networks under attack .Link virtualization: A Network as a link layer.Protocols for real-time interactive applications .Mobility Management: Mobile IP .Managing Mobility in Cellular Networks .Operational security: Firewalls 27 .WiFi: 802.Error Detection and Correction Techniques Multiple access protocols .Cellular Internet access .Wireless Links and Network Characteristics .Link .Link Layer: Services .Layer and services .Effort service .Network layer security: Ipsec .Tech SOFTWARE ENGINEERING CS 624 UNIT I COMPUTER NETWORKS AND MANAGEMENT COMPUTER NETWORKS AND THE INTERNET L T P C 3 0 0 3 9 The network edge .Delay.Link . UNIT III THE NETWORK LAYER AND THE LINK LAYER AND LOCAL AREA NETWORKS 9 Introduction . and throughput in packet .to -Point protocol .11 Wireless LANs . UNIT IV WIRELESS AND MOBILE NETWORKS AND MULTIMEDIA NETWORKING 9 Introduction .Securing e-mail .Broadcast and multicast routing . UNIT V SECURITY IN COMPUTER NETWORKS & NETWORK MANAGEMENT 9 Introduction .Socket programming -transport .oriented transport: Principles of congestion control Congestion control mechanism.DNS .The network core .Protocol layers and their service models .Quality of service guarantees.The Point .Switched networks .Virtual circuit and datagram networks .Principles of reliable data Transfer .Layer addressing .Streaming stored audio and video Making the best of the best .Peer .layer protocols .The Web and HTTP .Impact on higher .Principles of cryptography .Multimedia networking applications .Layer switches .Routing in the internet .

TOTAL = 45 TEXT BOOK 1. C. "Ad Hoc Wireless Networks: Architectures and Protocols".Tech SOFTWARE ENGINEERING and intrusion detection systems . 2. Addison Wesley. 2003. 4. 2007.Network management . Prentice Hall.Down Approach". Prentice Hall. 2007. 2005.Standard management framework . "Mobile Communications". James F. Addison Wesley. 2nd edition. 4th edition. "Computer Networks: A System Approach". 4th edition.M.S. Ross.Siva Ram Murthy and B. 28 . REFERENCES 1. Jochen Schiller.The Infrastructure for network management .1. "Computer Networking: A Top . 2004.The Internet . Morgan Kaufmann. William Stallings. 3.Manoj. Larry Peterson and Bruce Davie.ASN. 2nd edition." Wireless Communications & Networks". Kurose and Keith W.

Based protection Security: The Security problem .Segmentation with paging .Allocation of frames .Threads .system mounting .System and network threats . UNIT V PROTECTION AND SECURITY AND CASE STUDY 9 Goals of protection .Allocating kernel memory . UNIT IV STORAGE MANAGEMENT & I/O SYSTEMS 9 File concept .Example: The Intel Pentium virtual memory: Background .Other considerations .Access methods .Deadlock prevention .Principles of protection .The critical-section problem .Based systems .Process creation .Case Study : The Linux/ 29 .Tech SOFTWARE ENGINEERING CS 625 UNIT I OPERATING SYSTEMS OPERATING SYSTEMS OVERVIEW L T P C 3 0 0 3 9 Introduction .Operating system examples.Protection .File .Computer -security classifications .Semaphores .Processes .Application I/O Interface .Peterson's solution Synchronization hardware .Deadlock avoidance .Page replacement .Deadlock characterization .Swapping . UNIT III STORAGE MANAGEMENT 9 Memory management .Methods for handling deadlocks .Disk management .Streams.Contiguous memory allocation .Program threats .Implementing security defenses .Monitors .Recovery .Directory structure .NFS-example: The WAFL File System .Classic problems of synchronization.Implementation of access matrix .Memory .Access Matrix .Swap-space management .User authentication .Disk scheduling .Kernel I/O subsystem .Synchronization examples .Access control .Cryptography as a security tool .Capability .Atomic transactions -System model .Deadlock detection .Revocation of access rights .Recovery from deadlock.Tertiary Storage structure .Free-space management .Operating system structures .Transforming I/O requests to hardware operations .Mapped files .Allocation methods . UNIT II PROCESS MANAGEMENT 9 Process Management .Domain of protection .Directory implementation .Language .Storage implementation .Efficiency and Performance .An example: Windows XP.Demand paging .Fire walling to protect systems and networks .Thrashing .I/O hardware .Paging Segmentation .RAID structure stable .M.CPU scheduling.

Tech SOFTWARE ENGINEERING System . 2nd edition. Addison Wesley. Addison Wesley.Design principles .8th edition. "Operating System Concepts" . 30 . Galvin and Greg Gagne.System components .Memory management .Kernel modules .Windows XP .Process management. TOTAL = 45 REFERENCES 1. 2. 2001.Design principles . Tanenbaum. Andrew S. 2nd edition. "Modern Operating Systems".File system. 2009. Gary Nutt. Peter B. Scheduling . Addison Wesley.Environmental subsystems . 3. 2001. "Operating Systems".File systems . Abraham Silberschatz.M.

Automated Community Portal. 1. Online Bookshop Simulation of a small manufacturing Company. Database Design using Rational Products. 3. 7. File Management System Medical Imaging System 31 . Air traffic Simulation. Sequence Diagrams and State-Charts. 4.Tech SOFTWARE ENGINEERING CS 626 CASE TOOLS LAB L T P C 0 1 3 2 The student is expected to take up about Five mini .projects and model them and produce Use Cases. A Content Management System. Analysis documents . 2.both static and dynamic aspects. 5.M. 6.

Tech SOFTWARE ENGINEERING CS 627 SOFTWARE DEVELOPMENT PLATFORMS AND LANGUAGES LAB L T P C 0 1 3 2 Object Orientation v Design C++ classes with static members. v v v Web The students are advised to get exposed to web technologies like HTML. design matrix and vector classes with static allocation. destructor. Give proper constructor. methods with default arguments. Write a program to use XML and JavaScript for creation of your homepage. Design stack and queue classes with necessary exception handling. (For example. friend functions.vector multiplication) Implement Matrix class with dynamic memory allocation and necessary methods. XML and their variants as well as Java Programming v v v v v v v v Write HTML/Java scripts to display CV in Web Browser. Use JSP pages for sharing session and application data of HTTP Server. copy constructor. and overloading of assignment operator. Develop a template of linked . Create a Style sheet in CSS/XSL and display the document in Web Browser. Write a program in XML for creation of DTD which specifies a particular set of rules. Applications Develop Software for the applications like: v v v Online railway reservation system Payroll processing application Inventory system 32 .list class and its methods. and a friend function to do matrix . Creation and annotation of static web pages using any HTML editor.M. Write a program to use JDBC connectivity program for maintaining database by sending queries. Write a Java Servlet for HTTP Proxy Server.

Web sphere. 33 . NET etc. Net beans. Any front end tool (like VB. MS . Developer 2000) etc Any back end tool (Oracle.Tech SOFTWARE ENGINEERING Software required: v v v v Development Platform: Eclipse. SQL) etc. Languages: C/C++/Java/JSDK/Web browser.M. Delphi. VC++.Access.

Architecture structures for shared information systems.Design strategies . 1998. Mary Shaw David Garlan.Structured system analysis and structured design method.Prospects .Layered systems . design qualities . Ed Downs.Building modules. "Structured System Analysis and Design Methods Application and Context". PEI. 4th edition. 1996. SEI series in Software Engineering. David Budgen.User interface architecture. and Kazman R.Architecture design patterns .Tech SOFTWARE ENGINEERING SEMESTER . UNIT IV INTRODUCTION TO SOFTWARE 9 Introduction .DB integration .Integration and design of building . "Software Architectural Perspectives on an Emerging Discipline". 2003. 4. Prentice Hall.Jackson structural programming . 1994. 3. "Software Design". McGraw Hill Inc. UNIT II DESIGN METHODOLOGIES 9 Design practices . Clements P. constructs. UNIT V SHARED INFORMATION SYSTEMS 9 Shared information systems .II CS 628 UNIT I SOFTWARE DESIGN AND ARCHITECTURE DESIGN FUNDAMENTALS L T P C 3 0 0 3 9 The nature of design process .Assessing the design . EEE. PHI.SADT organizational design practices SSADM and design for real time systems .Rational for method .Top down and bottom up .Objectives . "Software Architecture in Practices".Organizational methods and design . TOTAL = 45 REFERENCES 1.State of art . 1996.based design .Software architecture . Pressman R.Object oriented organization . Addison Wesley. 2nd edition.Integration in software development environments .MASCOT. Bass L. 2. "Software Engineering".Architectural styles .Jackson system development . 5.S. UNIT III DESIGN MODELS 9 Traditional approach to design . 34 .Design viewpoints for software. Addison Wesley.Definition .Pipes and filters .M.Object-Oriented and Object . Peter Clare and Jan Coe.



L T P C 3 0 0 3 9

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 SOFTWARE ESTIMATION & COSTING 9

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 RISK MANAGEMENT 9

Risk definition - Risk categories - Risk assessment (Identification / Analysis / Prioritization) - Risk control (Planning / Resolution / Monitoring) - Failure Mode and Effects Analysis (FMEA). UNIT IV METRICS 9

Need for software metrics - Classification of software metrics: Product metrics (Size Metrics, Complexity Metrics, Halstead's Product Metrics, Quality Metrics), and Process metrics (Empirical Models, Statistical Models, Theory-based Models, Composite Models, and Reliability Models). UNIT V PEOPLE MANAGEMENT 9

Team Management - Client Relationship Management - Function organization - Project organization - Matrix organization - Staffing quality replacement Turnover management. TOTAL = 45 REFERENCES 1. 2. 3. McConnell's, "Software Project: Survival Guide", Microsoft Press, 1998. Royce W, "Software Project Management: A Unified Framework", Addison Wesley, 1998. Cooper R, "The Rise of Activity - Based Costing - Part One: What is an


Activity - Based Cost System?" Journal of Cost Management, Vol.2, No.2 Summer, 1988. 4. 5. 6. 7. 8. 9. Grant J.L, "Foundations of Economic Value Added", John Wiley & Sons, 1997. Kaplan R.S and Norton D.P, "The Balanced Scorecard: Translating Strategy into Action", Harvard Business School Press, 1996. Boehm B. W, "Software Risk Management: Principles and Practices" in IEEE Software, 1991. Fenton N.E and Pfleeger S.L, "Software Metrics: A Rigorous and Practical Approach, Revised", Brooks Cole, 1998. Demarco T. and Lister T., "People ware: Productive Projects and Teams, 2nd edition", Dorset House, 1999. Bob Hughes and Mike Cotterell, "Software Project Management", 4th edition, Tata McGraw Hill Publishing Company Ltd, New Delhi, 2005.



CS 630


L T P C 3 0 0 3

UNIT I SOFTWARE TESTING PRINCIPLES and TESTING STRATEGIES 10 Need for testing - Psychology of testing - Testing economics - White box, Black box, Grey box testing - White box testing techniques - Statement coverage - Branch coverage - Condition coverage -Decision/Condition coverage - Multiple condition coverage - Dataflow coverage - Mutation testing - Automated code coverage analysis - Black box testing techniques - Boundary value analysis - Robustness testing - Syntax testing - Finite state testing - Levels of testing - Unit, Integration and system testing. UNIT II TESTING OBJECT ORIENTED SOFTWARE, TESTABILITY AND RELATED ISSUES 10

Challenges - Differences from testing - Non-OO Software - Class testing strategies - Class Modality - State-based testing - Message sequence specification - Design for testability - Observability and Controllability Built-in test - Design by contract - Precondition, Post condition and Invariant - Impact on inheritance - Applying in the real world - Regression Testing Challenges - Test optimization. UNIT III QUALITY ASSURANCE MODELS 8

Models for Quality Assurance - ISO-9000 Series, CMM, SPICE, Malcolm Baldrige Award. UNIT IV SOFTWARE QUALITY ASSURANCE RELATED TOPICS 9

Software process - Definition and implementation - Internal auditing and assessments - Software testing - Concepts, Tools, Reviews, inspections and walkthroughs - P-CMM. UNIT V FUTURE TRENDS 8

PSP and TSP - CMMI - OO Methodology - Clean-room software engineering -Defect injection and prevention. TOTAL = 45



REFERENCES 1. 2. 3. 4. 5. 6. William E.Perry, " Effective Methods for Software Testing", 2nd edition, John Wiley & Sons, 2000. Robert Furtell, Donald Shafer and Linda Shafer, "Quality Software Project Management", Prentice Hall, 2001. Boris Bezier, "Black - Box Testing: Techniques for Functional Testing of Software and Systems", John Wiley & Sons, 1995. Marc Roper, "Software Testing", McGraw - Hill Book Co., London, 1994. Robert V.Binder, "Testing Object - Oriented Systems: Models Patterns and Tools", Addison Wesley, 2000. Philip B Crosby, "Quality is Free: The Art of Making Quality Certain", Mass Market, 1992.


SQL . Abort and Media failure . R. Elmasri and S.Architecture .Authorization . "Fundamentals of Database Systems". 39 2.Concurrency control . Abraham Silberschatz. Addison Wesley.Optimization and research issues. Henry. UNIT IV IMPLEMENTING AND ISOLATION 9 Schedules .OLAP and Data Mining . F.Atomic termination Distributed deadlock . Korth and S.Digital signatures . size estimation Models of transactions . "Database System Concepts". TMH.JDBC .Entity-Relationship model .XML and Web Data . UNIT V DATABASE DESIGN ISSUES 9 Security . 4.Encryption .Embedded SQL . 2004. Addison Wesley.TP monitor. 2003. .Recovery .XML Schema . UNIT II ADVANCED DATABASES 10 Object databases .Integrity . 2002.Consistency .Dynamic SQL . TOTAL = 45 REFERENCES 1.Authenticated RPC .B.ODBC. Lewis.Distributed transactions in real world. Tata McGraw Hill. Raghu Ramakrishna and Johannes Gehrke.Cost.Database design .M.Conceptual object data model .Replicated databases .Distributed data bases . Arthur Bernstein and Michael Kifer.Heuristic optimization .Transaction processing in a centralized and distributed system .Database tuning . 3. 2004.ROLAP and MOLAP UNIT III QUERY AND TRANSACTION PROCESSING 8 Query processing basics . 3rd edition. "Databases and Transaction Processing: An Application Oriented Approach". "Database Management Systems". Navathe.Global serialization .Tech SOFTWARE ENGINEERING CS 631 UNIT I ADVANCED DATABASE TECHNOLOGY DATABASE MANAGEMENT L T P C 3 0 0 3 9 Relational data model .Relational normalization . Philip M.Objects and semantic commutativity Locking -Crash. 3rd edition. 4th edition.Sudharsan.

Explain how patterns/ideas connect or do not connect to each other Can state the relation between two different things. Identify components of a software system.M. Restate SE knowledge in own words Can state all pre . Team building.conditions related to application of SE knowledge and skills. Refers to previous discussions/learning. Use of example Use of case studies for assessment 40 Analyze Synthesis Evaluation Communication . issues. LEARNING GOALS AND EVALUATION Learning Knowledge Understand Application Scoring Parameter Can state or identify Software engineering principles Can summarize the case study correctly. problems.Tech SOFTWARE ENGINEERING CS 632 Objective : CASE STUDY I: SOFTWARE DESIGN L T P C 0 0 2 1 To train the students for a systematic inquiry into an event or a set of related events which aims to describe and explain the phenomenon of interest by applying the principles and practices of Software Engineering. Justify the application of some knowledge/skill Can state n number of correct and most important pros and cons (from SE point) of two different proposals Clarity of presentation. good and bad practices. Combine ideas to produce an explanation. art of technical writing and presentation.conditions and post . Successful and complete application of SE procedure (skill) or tool to produce the specified deliverables Can identify patterns. The objective can be categorized as a) b) Use of the Software Engineering (SE) course learning goals to derive a set of parameters for objective assessment Soft skills such as communication. Differentiate root cause from symptom of a problem/ issue.

A foreman is also able to check the status of a customer order 2. Provide a feature for emergency mode. FOUR WAY TRAFFIC INTERSECTION. admin staff. Test plan document and so on. TRAFFIC LIGHT CONTROLLER SYSTEM The system is designed to control the four way traffic control system. and distributed within a warehouse by a forklift truck driver. WAREHOUSE MANAGEMENT SYSTEM The system will support warehouse management. Child. Should prepare and submit the deliverable documents such as Requirement Document. The goods are delivered by a truck driver between warehouses. goods using a database. Any other real time case study problems can also be considered. 41 . where there must be an option to set particular traffic direction to be considered on a priority basis for emergency situations. 1. The software should maintain a database of Family. l l Following are the sample case study examples. A warehouse worker loads goods from a truck and logs in and out. Design document. who is able to move goods between warehouses with or without a customer order. and Payroll information. The signals are designed to glow for fixed time duration. based on the parameters discussed above and other groups will act as the critics and can give their suggestions. Each group should present their own case study observations. etc.Tech SOFTWARE ENGINEERING Methodology of Assessment: l The class can be grouped into sets of students comprising of not more than five members each.) will be identified by a unique login ID and given a default password.M. teachers. adjustable pedestrian crossing time. Each warehouse is managed by a foreman. 3. All employees (managers. DAY CARE CENTER MAINTENANCE SYSTEM Your company has been awarded a contract to develop Child Care Software for a Day Care Center (DCC). The variation can be for free left turns. SRS. Users of the software shall have the ability to add/update/delete all information based on their access levels.

future reservation and cancellations. entrance test marks and choice of course. The hotel consists of 5 numbers of ten bed dormitories. Depending on the parameters such as Qualifications. 4 numbers of family rooms. optimum usage of room space. Design must take care of the various issues such as cost. The constraints to be considered are availability f course for that academic session. Hotel Reservation System Design a system for hotel reservation system for optimum space usage.Tech SOFTWARE ENGINEERING 4. 5.M. Discounts and season time offers may also be considered. 16 numbers of double bed rooms and 10 numbers of single bedrooms. Number of seats (available) and eligibility criteria. 3 numbers of executive suites. the charges for reservation. University Admission System Design a system to automate the admission procedures of the University system with automatic counseling feature. cancellation. the student is given the options for selecting a course. 42 .

issues.M. The objective can be categorized as a) b) Use of the SE course learning goals to derive a set of parameters for objective assessment Soft skills such as communication. Use of example Use of case studies for assess 43 Analyze Synthesis Evaluation Communication . Explain how patterns/ideas connect or do not connect to each other Can state the relation between two different things. art of technical writing and presentation. Successful and complete application of SE procedure (skill) or tool to produce the specified deliverables Can identify patterns.Configuration management .conditions and post . Justify the application of some knowledge/skill Can state n number of correct and most important pros and cons (from SE point) of two different proposals Clarity of presentation. good and bad practices.Tech SOFTWARE ENGINEERING CS 633 CASE STUDY 2: SOFTWARE PROJECT MANAGEMENT L T P C 0 0 2 1 The case studies Software Project Management cover the following topics: Project management .Project Planning . Team building. problems. Refers to previous discussions/learning. Combine ideas to produce an explanation. Objective : To train the students for a systematic inquiry into an event or a set of related events which aims to describe and explain the phenomenon of interest by applying the principles and practices of Software Engineering.Project management for India and Geographic distribution issues.conditions related to application of SE knowledge and skills. Learning Goals and Evaluation Learning Knowledge Understand Application Scoring Parameter Can state or identify Software engineering principles Can summarize the case study correctly. Identify components of a software system. Restate SE knowledge in own words Can state all pre . Differentiate root cause from symptom of a problem/ issue.

based on the parameters discussed above and other groups will act as the critics and can give their suggestions. VESSEL TRACKING SYSTEM Vessel tracking network used to track vessels to enhance maritime safety and security. The goods are delivered by a truck driver between warehouses. and distributed within a warehouse by a forklift truck driver. Should prepare and submit the deliverable documents such as Requirement Document. By applying this management system. 2. WAREHOUSE MANAGEMENT SYSTEM The system will support warehouse management. the time table production work was decreased and the check mistake became none at all. Each warehouse is managed by a foreman. environmental protection and emergency response. 44 3. 2. 3. This system is able not only to check the contradiction of the time table but also to make the management table concerning the lecturer. the classroom. A warehouse worker loads goods from a truck and logs in and out goods using a database. Following are the sample case study examples. The class can be grouped into sets of students comprising of not more than five members each. Vessel tracking systems can now also be found in consumers vessels as a theft prevention and retrieval device. The time table management system using the macro processing of the spreadsheet in a general personal computer system. The database thus records the data about the positions of the vessels from the port. who is able to move goods between warehouses with or without a customer order.M. the core class.Tech SOFTWARE ENGINEERING Methodology of Assessment: 1. A foreman is also able to check the status of a customer order. SRS. Current vessel tracking systems have their roots in the shipping industry. The navigation technology follows the basic principle of transmission and receiving the signals which are then stored in the database. and the lecture subject at the same time. 1. Each group should present their own case study observations. Corporations with large fleets of vessels required some sort of system to determine where each vessel was at any given time. TIME TABLE MANAGEMENT SYSTEM The time table production in university is very serious work. Test plan document and so on. Any other real time case study problems can also be considered. . Design document. The students can also try this case studies using Free Open Source Software.

Tech SOFTWARE ENGINEERING 4. Group Discussion is also used in the Course 45 . TRAFFIC LIGHT CONTROLLER SYSTEM The system is designed to control the four way traffic control system. The signals are designed to glow for fixed time duration. Provide a feature for emergency mode. where there must be an option to set particular traffic direction to be considered on a priority basis for emergency situations. adjustable pedestrian crossing time. The variation can be for free left turns.M. FOUR WAY TRAFFIC INTERSECTION.

Load Runner. As the assessment plays an extremely important role in the software development process the grab of measurement are as follows l Assessment: as evaluation of given situation in special environment Comprehension of used methods Identification of development problems 46 . Test Director.Tech SOFTWARE ENGINEERING CS 634 SOFTWARE TESTING AND MEASUREMENTS LAB SOFTWARE TESTING LAB 1. d. f. Library System Course Registration System Implement a Quiz System Student Marks Analyzing System Online Ticket Reservation System Stock Management System Real . Generate Test cases and Test Documentation in the following case studies a) b) c) d) e) f) g) MEASUREMENTS LAB Software measurements help to improve the understanding of software. L T P C 0 1 3 2 Study of various tools Study various tools such as Win Runner. Rational Rose Suite etc. Perform various types of testing: a. Unit Testing Regression Testing Integration Testing Validation Testing Acceptance Testing System Testing Prepare test plan and develop test case hierarchy. b.M. e. 2.Time Scheduler 3. c. It provides the necessary information for the assessment and management of software project.

M. For example in object oriented programming development l Compute method inheritance factor weighted method for class. ii. 47 . For a typical web application to calculate the following i. v. Weighted Method Count (WMC) No of Children (NoC) Depth of Inheritance (DIT) Response for a Class (RFC) Coupling and Cohesion between Objects (CCBO) 2.Tech SOFTWARE ENGINEERING l Indication as determination of certain factors or indicators for special characteristics Performance evaluation Lines of code analysis Reviews l CMM level 5 as a model for the integration of software measurement in the process important Measurement based method comparison 1. iii. iv.

IP security architecture .Denial of service . modification and fabrication) Security Services (confidentiality.Kerberos.Compartments . UNIT-IV 8 Secure Socket Layer (SSL) and Transport Layer Security (TLS) .Key distribution approaches of Message Authentication.Public key cryptography algorithms .End-end security (COMSEC) Link encryption (TRANSEC) . UNIT-III 8 Certificate authority and key management .509 directory authentication .Firewall design principles .Combining security associations and Key management web security requirements. access control and availability) and mechanisms .Non repudiation.SNMPv1 community facility and SNMPv3 . Public key cryptography principles .Making and 48 .M.IP security overview.Key and certificate management Secure binding of public and private values: DNS certificates .Route table modification .Location of encryption devices . integrity.Encapsulating security payload . UNIT V 9 Intruders. Security Models: Military and civil security.TCP session hijacking -ARP attacks.X.Digital signatures .UDP hijacking and man-in-the-middle attacks.Authentication Header .Tech SOFTWARE ENGINEERING SEMESTER III CS 721 UNIT I INFORMATION SECURITY L T P C 3 0 0 3 12 Security Attacks (interruption. interception.Trusted systems . Secure Hash Functions and HMAC.Digital Certificates.Conventional encryption algorithms Cipher block modes of operation.Buffer overflow & format string vulnerabilities .Basic concepts of SNMP.A model for Internet work security . Viruses and related threats . authentication.Authentication. UNIT II 8 Conventional encryption principles . viruses and related threats.Privacy .Internet Standards and RFCs .vulnerability and threat models.Service Email privacy: Pretty Good Privacy (PGP) and S/ MIME.Intruders. non-repudiation.Intrusion detection systems .Secure Electronic Transaction (SET) .

Steve W. Thomson Business Information.Key agreement protocols: STS protocol and IETF work orders.One-time passwords: schemes based on S/KEY. 2nd edition. "Hack Proofing your network ". 2004. Robert Bragg and Mark Rhodes . "Fundamentals of Network Security".PKI. 2004 Buchmann . ."Cryptography and network Security". Ryan Russell.Protocols. 2004 Schneier B. Prentice Hall of India. 49 . 2. David Ahmad. 2. Michael E.Key Escrow: the Clipper chip . 2nd edition. 3rd edition. 6.Tech SOFTWARE ENGINEERING distributing key media: randomization. 2002. 1st edition. 5. Algorithms and Source Code in C". Radia Perlman and Mike Speciner. Rain Forest Puppy. Hal Flynn Ido Dubrawsky. Charlie Kaufman. Pearson Education.. 7. Eric Maiwald. Pearson Prentice Hall of India. REFERENCES 1. 2004. "Network Security Essentials (Applications and Standards)". 2009 Stallings. "Network Security Private Communication in a Public World ". "Applied Cryptography .M. 2003. lifetime issues."Principles of Information Security". Joe Grand. Whitman . Tata Mgraw Hill."Network Security: The complete reference".Manzuik and Ryan Permeh. McGraw-Hill Osborne Media. 4. TOTAL = 45 TEXT BOOKS 1. Syngress. 3. Dan Kaminsky. 1995. 2004. William Stallings. Apress / Springer (india) Pvt Ltd. John Wiley and Sons."Introduction to Cryptography" .

M. Michael Miller. Emereo Pty Limited.Cloud services.Advantages of cloud computing Disadvantages of cloud computing .Collaborating on word processing . "Cloud Computing: Web .Discovering cloud services Development services and tools . Applications and Data Centers in the Cloud with SLAs".Cloud computing matters .Exploring online planning and Task management .Collaborating on event management . 2008. Que Publishing.Collaborating on project management .Companies in the cloud today .Cloud storage . UNIT III CLOUD COMPUTING FOR EVERYONE 10 Centralizing email communications .IBM clouds.Cloud computing for the corporation.Collaborating on To . UNIT II DEVELOPING CLOUD SERVICES 10 Web . UNIT V OTHER WAYS TO COLLABORATE ONLINE 9 Collaborating via Web .Based application .Based Applications that change the way you work and Collaborate Online".Collaborating on schedules .On-Demand computing . Haley lists .Exploring online scheduling applications .Software as a service . P : 15 TOTAL = 45 REFERENCES 1.Based communication tools . 2008.Collaborating on contact management . L : 45.Web services . 2.Pros and Cons of Cloud service development Types of cloud service development .demand Computing.Collaborating via Social Networks and Groupware .Cloud architecture .Collaborating on databases . 50 .Cloud computing for the community .Evaluating web conference tools .Collaborating on group projects and events .Collaborating contact lists .Collaborating via Blogs and Wikis. UNIT IV USING CLOUD SERVICES 10 Collaborating on calendars. Schedules and Task Management .Evaluating web mail services .Tech SOFTWARE ENGINEERING CS 722 UNIT I CLOUD COMPUTING UNDERSTANDING CLOUD COMPUTING L T P C 3 0 2 4 6 Cloud computing .Storing and sharing files.Platform as a service .Amazon EC2 . "Cloud Computing Best Practices for Managing and Measuring Processes for on .Google App engine .History of cloud computing .

Hopcroft. TOTAL= 45 REFERENCES 1.Regular expressions and Regular languages . UNIT II FINITE AUTOMATA AND REGULAR LANGUAGES 9 Finite automata and regular languages .Ambiguity in grammars and languages .D Ullman.Pumping lemma for regular languages. 2. Thomson Brooke/cole. TMH.Finite Automata with Epsilon transitions . Michael Sipser.Post's Correspondence Problem.Universal Turing machines .Non-deterministic Finite Automata (NFA) . J. UNIT III CONTEXT . "Introduction to Languages and the Theory of Computation".Equivalence of Pushdown automata and CFG . 1997.FREE GRAMMAR AND LANGUAGES 9 Context . UNIT IV PUSH DOWN AUTOMATA AND TURING MACHINES 9 Definition of the Pushdown automata .Martin.Undecidable problems about Turing Machine . "Introduction of the Theory and Computation".Rice theorem .M.Free Grammar (CFG) . R.Turing Machines Programming techniques for TM. 2003.Deterministic Finite Automata (DFA) . J. "Introduction to Automata Theory. 3. 51 .E.Motwani and J. 2003. 3rd edition.Equivalence and minimization of automata.Pumping lemma for CFL. Pearson Education. UNIT V UNSOLVABLE PROBLEMS AND UNDECIDABILITY 9 Recursive and recursively enumerable languages .Non .Languages of a Pushdown automata .Parse trees . 2nd edition.Tech SOFTWARE ENGINEERING ELECTIVES CSY101 UNIT I AUTOMATA THEORY OF COMPUTATION L T P C 3 0 0 3 9 Finite Automata (FA) .determinism and Kleene's theorem . Languages and Computations".Normal forms for CFG .

Automobile fuel efficiency prediction . 2004.Step size determination .Learning vector quantization .Adaline .M.Organizing networks .fertilize ANFIS and RBFN . "Neuro .Sun and E.Basic definition and Terminology .Architecture .Inverse kinematics problems .Hybrid learning algorithm .Tsukamoto fuzzy models .Theoretic operations .Competitive learning networks .Extension principle and Fuzzy relations .Multilayer perceptrons .Unsupervised learning and Other neural networks . UNIT II OPTIMIZATION 8 Derivative .Member function formulation and Parameterization .Mizutani.Sugeno fuzzy models .Jang.R.then rules .Neuron functions for adaptive networks Neuro fuzzy spectrum.Perceptrons .Derivative Free optimization .Based optimization .Tech SOFTWARE ENGINEERING CSY102 UNIT I SOFT COMPUTING FUZZY SET THEORY L T P C 3 0 0 3 10 Introduction to neuro .S.Coactive neuro-fuzzy modeling framework .Back propagation .Fuzzy inference systems .Fuzzy and soft computing".Random search .Fuzzy If .Fuzzy reasoning .Radial basis function networks . UNIT V APPLICATION OF COMPUTATIONAL INTELLIGENCE 8 Printed character recognition .The method of steepest descent . C.Downhill simplex search.Descent methods .Fuzzy and Soft computing .Fuzzy sets .Fuzzy inference systems .Input space partitioning and Fuzzy modeling. UNIT IV NEURO FUZZY MODELING 9 Adaptive neuro .Fuzzy rules and Fuzzy reasoning .Soft computing for color recipe prediction.Kohonen self . PHI.T. J. UNIT III NEURAL NETWORKS 10 Supervised learning neural networks .Set . 52 .Classical Newton's method .Genetic algorithms .Hebbian learning.Mamdani fuzzy models . Pearson Education.Simulated annealing .Learning methods that cross . TOTAL= 45 REFERENCES 1.

Boston 1996.A.Eberhart. R.Rajasekaran and G. 1989. Timothy J. 53 .M.Tech SOFTWARE ENGINEERING 2. PHI. 4."Genetic Algorithms: Search.Dobbins. Optimization and Machine Learning".simpson and R.Pai.Goldberg. "Neural Networks. "Computional Intelligence."Fuzzy Logic with Engineering Application ". 2003. Fuzzy Logic and Genetic Algorithms".V.Ross.Y. S. AP Professional. Davis E. McGraw Hill. 3. P. 5. 1977. N. Addison Wesley. PC Tools".

DSDV .11 standards . UNIT III WIRELESS NETWORKS 9 Wireless LAN .Applications and Limitations .Services .Tech SOFTWARE ENGINEERING CSY103 UNIT I MOBILE COMPUTING WIRELESS COMMUNICATION FUNDAMENTALS L T P C 3 0 0 3 9 Introduction .TDMA .Spread spectrum .FDMA . UNIT II TELECOMMUNICATION SYSTEMS 9 GSM & GPRS:GSM features and Architecture .WSP .Network operations .Fast retransmit / Fast recovery .WAE .Trust .Public key infrastructure .MAC .Wireless broadband (WiMAX) .Information security .WML -WML Script . UNIT V SECURITY ISSUES IN MOBILE COMPUTING 9 Introduction .Cellular wireless networks.GPRS features and Architecture .Adhoc network .Routing .Network aspects in GSM GSM frequency allocation .WTP .Modulations .WTLS .Snooping TCP .Adhoc networks .SDMA .Signal propagation .Security issues used in GSM .Security techniques and Algorithms security Protocols .Mobile TCP .Hand -off mechanisms Cell splitting .Indirect TCP .WAP architecture .Frequencies for radio transmission Signals . UNIT IV NETWORK LAYER AND TRANSPORT LAYER 9 Mobile IP .UMTS . TOTAL = 45 54 .Dynamic host configuration protocol .Blue tooth .DSR AODV -TCP over Wireless Networks .SMS and MMS services architecture and operation details.Wireless transmission .HIPERLAN .Sensor networks .Transmission/Timeout freezing Selective retransmission .CDMA .Security frameworks for mobile environment.Third generation networks and applications.Antennas .IEEE 802.EDGE .M.Mobility management .WTA.WAP .WDP .Security models .Transaction oriented TCP .Multiplexing .Data services in GPRS .Architecture .

55 .Toh. 2nd edition. Applications and Service Creation)". Jochen Schiller."Mobile Commerce: Technology. "Pervasive Computing". 6. Springer. Burkhardt. "Principles of Wireless Networks". Idea Group Publishing. 4. 1st edition. Pearson Education. 1st edition. 2003. Kaveh Pahlavan. Pearson Education. "Mobile Communications". Pearson Education. Lothar Merk. K Talukder and Roopa R. William Stallings.2002. 2002. Martin S."Mobile Computing (Technology. 2003. Pearson Education. Prasanth Krishnamurthy. Nicklons and Thomas Stober. Yavagal . Strader . C. Theory and Applications ". "Wireless Communications and Networks". Brian Mennecke and Troy J. 2.K.TATA McGraw Hill. 2002. Asoke. Pearson Education. 8. "Principles of Mobile Computing". 1st edition. 2006.Tech SOFTWARE ENGINEERING REFERENCES 1. 2003. 3. 7. 2003.M. Uwe Hansmann. "AdHoc Mobile Wireless Networks". 5.

"Advanced Concepts in Operating systems". "Distributed Systems Concepts and Design". Mukesh Singhal. Pearson Addison Wesley. Pearson Education Asia.Distributed transactions .Sun NFS.Distributed commit protocols .Impossibilities in fault tolerance. 3rd edition.L.Message Oriented communication Unicasting. 2004.S.Distributed coordination based system .Tanenbaum and M. 5.Clock synchronization . 3.Various paradigms in distributed applications .Agreement protocols.Liu.Tech SOFTWARE ENGINEERING CSY104 UNIT I DISTRIBUTED SYSTEMS COMMUNICATION IN DISTRIBUTED ENVIRONMENT L T P C 3 0 0 3 8 Introduction . Hagit Attiya and Jennifer Welch.Causal ordering . UNIT V CASE STUDIES 8 Distributed object .Group communication. "Distributed Computing: Fundamentals. McGraw . 1994.COM+ .CORBA . A. UNIT III DISTRIBUTED RESOURCE MANAGEMENT 10 Distributed shared memory . 2004. "Distributed Computing Principles and Applications". UNIT II DISTRIBUTED OPERATING SYSTEMS 12 Issues in distributed operating system .Based system . George Coulouris.JINI.Client Centric consistency models: Ivy .Global states .Data Centric consistency models . 56 . 4. 2004.Distributed deadlock .Remote Object Invocation .Threads in distributed systems .Hill Series in Computer Science. multicasting and broadcasting .Distributed file systems .Remote Procedure Call . M. Jean Dollimore and Tim Kindberg. Pearson Education.Van Steen.Byzantine fault tolerance . Simulations and Advanced Topics". Wiley publications.Election algorithms Distributed mutual exclusion . TOTAL = 45 REFERENCES 1. 2002.M.Munin . UNIT IV FAULT TOLERANCE AND CONSENSUS 7 Introduction to fault tolerance .Distributed scheduling . "Distributed Systems". 2.

On load Mouse rel -Form process . and IMAP.ASP .Online payments and security . Deitel & Deitel and Goldberg.On check . POP3. 2001.HTTP request types .HTTP. Children.XML 9 Database.Directives. UNIT IV DATABASE . "Java Network Programming".Creating motion with blur . UNIT II DYNAMIC HTML 9 Introduction . Structures .HTML 4 protocols . 2. Elliotte Rusty Harold. TOTAL = 45 TEXTBOOK 1. Navigator.Functions-Arrays-Objects.Handling HTTP request .Standard actions .Apache-web server.DTD-Vocabularies-DOM Methods.Dynamic styleDynamic position.XML Structure in data . "Internet and World Wide Web .Data binding .ADO Access a Database from ASP .M.Overview. UNIT III MULTIMEDIA 9 Audio and video speech synthesis and recognition .Electronic commerce . 2002 57 .IIS .Filters -. Event Model . Collection . O'Reilly Publishers. SQL .Tech SOFTWARE ENGINEERING CSY105 UNIT I WEB TECHNOLOGY INTRODUCTION L T P C 3 0 0 3 9 History of the internet and World Wide Web .Binding of an Image .ASP .Multi-tier applications .JSP . Frames.Client side scripting and Server side scripting Accessing Web servers .Event bubblers .File system objects .E -Marketing .Get and post request .Reference.Working of ASP .System architecture .Objects .Servlet overview architecture .Session tracking and cookies .Object based scripting for the web. MIME. UNIT V SERVLETS AND JSP 9 Introduction .Name spaces .Scripting . Introduction to Java Scripts .Simple data binding Moving with a record set .Web servers .Redirecting request .Creating images .Adding shadows -.Server side Active -X components .Sorting table data .How to program".Objects . SMTP.Overview . Relational database model .Objects . Pearson Education Asia.table.

"The Complete Reference HTML and XHTML". Tata McGraw Hill. 5.Wesley. 2004. "Head first HTML with CSS & XHTML". Eric Ladd and Jim O' Donnel. 58 . 7. Naughton. 8.Hill. Aferganatel. Sebesta. Krishnamoorthy and S. 9. Addison . Elisabeth Freeman and Eric Freeman. Basham.M. 2005. 1999. "The Complete Reference . 2. Powell. Rajkamal. Prentice Hall of India .Tech SOFTWARE ENGINEERING REFERENCES 1. R. Prabhu. 3rd edition. Sierra and Bates. "Programming the World Wide Web". 6. "Web Technology". 2006.2004. O'Reilly. 4th edition. Tata McGraw . "Head First Servlets and JSP". 3rd edition.1st edition. 1999. 3. XML and JAVA". Tata McGraw . PHI. 4. New Age International Publishers. Thomno A. 2003. 2004.Java2". "Internet and Java Programming".QUE. 2001. "Using HTML 4.Hill. "WebProgramming:".

Web Services and the Data Revolution".Resource description framework .XML encryption . UNIT III BUILDING XML .Anatomy of UDDI .Presentation technologies .Role of Meta data in web content .X -Files .XML schemas .Discovering web services .Transformation .Applied XML in vertical Industry.Architecture of semantic web .UDDI .XQuery Service Oriented Architecture (SOA). "XML and Web Services".Applied XML .Anatomy of WSDL .XSLT . 59 .Content management workflow.XSL .SAX .Protocols .RDF schema .Integrating XML with databases .Tech SOFTWARE ENGINEERING CSY106 UNIT I XML AND WEB SERVICES XML TECHNOLOGY FAMILY L T P C 3 0 0 3 9 XML .Formatting XML for the web . 2.Voice XML . Ron Schmeltzer.Ad . Pearson Education. 2002. UNIT V SEMANTIC WEB 9 Semantic web .Transport protocols for web services .Describing web services . UNIT II WEB SERVICES BUILDING BLOCKS 9 Architecting web services .Web service inspection . TOTAL = 45 REFERENCES 1.XLINK .XML Digital Signature .Canonicalization .XML in practice. UNIT IV XML SECURITY 9 Security overview .M.DOM . Frank P.Delivering wireless and Voice services with XML . 2002.Hoc discovery.Coyle.XFORMS XHTML .SOAP .XML processing .WSDL .Benefits .DTD .Web service policy .Guidelines for Signing XML documents .Manipulating . Pearson Education.Understanding XML standards .WSDL .BASED APPLICATIONS 9 Parsing XML .Advantages of XML .XKMS structure .XPATH .XML security framework . "XML.NET .Messaging with web services .Leveraging XML in Visual Studio .

"Beginning Java Web Services". Pearson Education. Keith Ballinger. 4. 2004. Russ Basiura and Mike Batongbacal.Tech SOFTWARE ENGINEERING 3.NET Web Services". 5.M. 6. Prentice Hall. 1st edition. 2004. "Professional ASP . "Developing Enterprise Web Services: An Architect's Guide".NET Web Services Architecture and Implementation". ". 2003. Apress. 60 . Apress. Sandeep Chatterjee and James Webber. Henry Bequet and Meeraj Kunnumpurath. 2003.

Prentice Hall International. Jim Woodcock. Formal Versus Informal programming . "Using Z Specification. 2.Based specifications Example specification languages.Denotation semantics .M.Additional constructs .Relationships and Functions.Data types .Axiomatic semantics proof editors .Propositional logic .Quote types . 1996. 61 .Basic types .Proof analyzer . 1996.Compound types . Refinement and Proof".Symbolic simulators -Translators .Requirements of formal system .Schemas .Predicate logic .Tech SOFTWARE ENGINEERING CSY107 UNIT I FORMAL METHODS IN SOFTWARE ENGINEERING INTRODUCTION L T P C 3 0 0 3 8 Need for formal methods .Operations .Modules.Test generation tools.Specifications . UNIT V FORMAL SEMANTICS AND TOOLS 9 Operational semantics . UNIT III VDM 10 Introduction to VDM . UNIT II FORMAL SPECIFICATION STYLE 8 Model . John Wiley and Sons.Types .Concurrency .User .Additional constructs.Compound types .Advantages of formal methods .Optional types . "Formal Methods: Fact File VDM and Z". UNIT IV THE Z NOTATION 10 The Interchange language .Oriented .Problems in natural language specifications.Functions .Basic types . Jim Davies.Defined identifiers . Andrew Harry. TOTAL = 45 REFERENCES 1.

Components databases . 1999. 62 . 1996.Multimedia databases.K.Video display systems .RAID .Audio compression . Andleigh P.Objects of multimedia systems . Vaughan T. 2.RIFF file format .Video image compression . Prentice Hall. 1999. "Multimedia Systems Design".User interface design Display/Playback issues .K and Thakrar .MPEG . UNIT IV STORAGE AND RETRIEVAL 9 Magnetic media ." Multimedia".TIFF file format .TWAIN. "Multimedia Systems".Types of systems .Virtual reality design . Addison Wesley Longman. 3.Authoring systems .MIDI .M.Video images and animation.System architecture .Hyper media .Cache management. Koegel Buford JFK.Image compression .Optical media . UNIT III INPUT/OUTPUT TECHNOLOGIES 9 Traditional devices .Hypermedia linking and embedding. Tata McGraw Hill.Tech SOFTWARE ENGINEERING CSY108 UNIT I MULTIMEDIA SYSTEMS INTRODUCTION L T P C 3 0 0 3 9 Multimedia applications .Scanners Digital audio .RTF format .WORM .Juke box .CCITT . UNIT V APPLICATION DESIGN 9 Application classes . UNIT II COMPRESSION AND FILE FORMATS 9 Types of compression .JPEG DIB .Pen input .CD ROM . TOTAL = 45 REFERENCES 1.JPEG .DVI technology .

"Multi Agent Systems . Bigus & Bigus.M.Interaction protocols .Tech SOFTWARE ENGINEERING CSY109 UNIT I SOFTWARE AGENTS AGENTS .Black box security .Actors and Agents .Aglets programming . Richard Murch.Agent negotiation . UNIT II JAVA AGENTS 9 Processes . 2003.Authentication for agents .ActiveX sockets .Belief desire intension . 4.OVERVIEW L T P C 3 0 0 3 9 Agent definition . 2.Security issues for aglets. 2nd edition.Agent communication languages . "Intelligent Software Agents". Tony Johnson.Reactive agents .Agent cooperation . UNIT V AGENTS AND SECURITY 9 Agent security issues .Mobile agent applications. 2000.A Modern approach to Distributed Artificial Intelligence".Protecting agents against malicious hosts .Agent organization . MIT Press. 63 . Prentice Hall. 2000. 5.Agent knowledge representation .Self-interested agents in Electronic commerce applications.Agent Vs Object .Threads .Agent adaptability .Agent reasoning. "Software Agents ".Untrusted agent . TOTAL= 45 REFERENCES 1.Agent frameworks . 3. Russel and Norvig. Bradshaw.Typed and proactive messages. 2000.Java Beans .Aglet Mobile agents .Cognitive agents .Mobile agents security .Agent coordination . UNIT IV INTELLIGENT SOFTWARE AGENTS 9 Interface agents . Wiley. Gerhard Weiss. "Constructing Intelligent agents with Java ".Jini architecture . Pearson Education. "Artificial Intelligence: A Modern Approach". UNIT III MULTI AGENT SYSTEMS 9 Interaction between agents .Components .Distributed computing .Agent programming paradigms . MIT Press. 1997.RPCs .Daemons .

Compiler . Algorithms.Instruction sets .Message queues .Interrupts .Memory Microprocessors Buses . frequency measurement .Memory management. UNIT III EMBEDDED MICROCOMPUTER SYSTEMS 9 Motorola MC68H11 family architecture registers .M.Parallel port interfaces .Interrupt basics . TOTAL= 45 64 .Initialization .Schematic.Interrupt routines in an RTOS environment .Shared data problem .Timer function .Gates .Interrupts . function .Interrupt latency.Timing diagram .Memory Interfacing.Built-ins on the microprocessor .485. Robin with Interrupts. complex systems and Microprocessor.I 2C Bus operation serial EEPROM . Rs.Baud Rate . Formalisms for system design.Direct Memory Access .Special features . tasks and data. Introduction to assembler . Interfacing methods parallel I/O interface .Parallel slave port.Addressing modes .Registers . The Embedded system design processor.Data handling .Events . output compare. Round-robin.Multi-tasking in real time systems-Scheduling. Object Oriented Interfacing.Simulators.Debugging strategies .Analog to digital converter -UART . Terminology .Conventions used on schematic . Interrupts microprocessor architecture .Tech SOFTWARE ENGINEERING CSY110 UNIT I EMBEDDED SYSTEMS INTRODUCTION L T P C 3 0 0 3 9 Embedded computing: Introduction.Analog interfacing and applications.Interrupts . UNIT V REAL TIME OPERATING SYSTEMS 9 Task and task states.Loop timing .Recursion .High speed I/O interfacing.Features of interrupts . semaphores and shared data operating system services .Timing generation and measurements .CPU architecture .Interrupt timing. UNIT IV SOFTWARE DEVELOPMENT TOOLS 9 Embedded system evolution trends.Basic design using RTOS.Cross compilers and Integrated Development Environment (IDE). UNIT II PIC MICROCONTROLLER AND INTERFACING 9 Introduction .Interrupt Service Routine . .Addressing modes Programs.One-Scheduling Architecture.Interrupt vector and Priority.Serial I/O devices Rs. Design examples.Timers .Serial programming .Input capture.232.I/O Expansion .

"Computers as Components.Tech SOFTWARE ENGINEERING TEXT BOOKS 1. Wayne Wolf. Morgan Kaufman Publishers.. Prentice Hall Inc. 5." Real Time Systems and software". David E Simon. 5. 2001. 1998.Bialey. 1st reprint. 4. "Embedded systems architecture. Thomson learning. 3.M." Design with Microcontroller ". 2. Harcourt India. 2003. 1998. "Embedded Micro computer Systems Real time Interfacing ". Principles of Embedded Computing System Design". Andy. Burns. 2nd edition. Addison Wesley Longman. " Real time Programming: A guide to 32 Bit Embedded Development. Rajkamal. Programming and Design".A. Pearson education Asia. Raymond J. 2001. Alan C. 2002. John Wiley. Reading ". 4. 1997. 2001." An Embedded Software Primer". Bhur and Donald L. John Wiley & Sons Inc. New Jersey. " An Introduction to real time systems: Design to networking with C/C++ ". Harlow: Addison Wesley Longman.A Unified Hardware/Software introduction". Pearson Education Asia. John B Peat man. Shaw." Embedded Systems Design . 2. Grehan Moore and Cyliax. 65 . 3. Alan and Wellings. TATA McGraw Hill. Valvano Brooks / cole. Jonartthan W. Frank Vahid and Tony Givargis. REFERENCE BOOKS 1. "Real -Time Systems and Programming Languages ". 1st indian reprint. 1999. 2001.

Hardware. solution deployment. 1992.Identifying the need for change. Stacey C.Application management. New Delhi..Tech SOFTWARE ENGINEERING CSY111 UNIT I IT SYSTEMS MANAGEMENT INTRODUCTION L T P C 3 0 0 3 5 Introduction to IT Systems management . Kelly. Capacity planning. "Using Information Technology . Rainer. Sawyer and Sarah E. UNIT II CHANGE MANAGEMENT 10 Change management processes . John Wiley. Performance management. R.Current and target architecture definitions. software. "Management of Information Technology". Tata McGraw Hill. Schiesser and Rich. Hutchinson. Problem management. tools. 2002.Mastering the information and Knowledge environment". "IT Systems Management". UNIT III CONFIGURATION MANAGEMENT 10 Configuration management processes . Oxford University Press. Williams. Davenport and Thomas H. 6. "Introduction to InformationTechnology". Turban.A practical introduction to computers and communications". 4. UNIT IV OPERATIONS MANAGEMENT I 10 Operations management processes .On track from start to finish". Efraim. 3rd edition. networks. Exception management. "Information Ecology . 2. UNIT V OPERATIONS MANAGEMENT II 10 Operations management processes .. TOTAL = 45 REFERENCES 1. Frenzel and Carol W. 1997. making a business case and measuring return on investment.Business continuity and Disaster recovery. Brian K. processes. Boyd and Fraser. Phillips and Joseph. vendor selection. 5.M. 1999. 2002. "IT Project Management . Potter and Richard E. managing change People. Prentice Hall of India. 66 . Tata McGraw Hill. storage.Scope and definitions. 2003. systems management frameworks. 3. current and future technology .

UNIT V PERFORMANCE ANALYSIS 9 ABR beaconing.First .Energy . On-demand and Hybrid routing protocols .Route reconfiguration/repair time .TCP over AdHoc wireless networks .M.Hierarchical and power .Wireless ATM.Tech SOFTWARE ENGINEERING CSY 112 UNIT I MOBILE AD HOC NETWORKS WIRELESS LAN.Based protocols with reservation and scheduling mechanisms .Transmission power management schemes -System power management schemes.WLL.Aware routing protocols. UNIT III TRANSPORT LAYER AND SECURITY PROTOCOLS 9 Transport layer protocol: Design issues.MAC layer solutions. MAC protocols .Network security attacks.Classification of QoS . PAN.Fundamentals of WLANs .HIPERACCESS. ROUTING AND MULTICAST ROUTING PROTOCOLS 9 MAC protocols: Design issues.Tree .End .Security .based protocols . Mesh . Quality of Service: Issues and challenges in providing QoS .TCP/IP based applications.11 standard . Classification of battery management schemes .Packet loss performance .Location discovery-Quality of a sensor network.16 standard. UNIT II MAC.IEEE 802.Network layer solutions-QoS frameworks.Efficient multicasting. Wireless Sensor Networks: Architecture .Classification .Goals and Classification .Security routing.Data dissemination . WAN AND MAN L T P C 3 0 0 3 9 Characteristics of wireless channel . TOTAL = 45 67 . Multicast Routing Protocols: Design issues and operationArchitecture reference model . second and third generation cellular systems.Contention .Discovery time .IEEE 802. Route .Routing protocols with efficient flooding mechanisms. Routing protocols: Design issues and classification Table-driven.Date gathering.HIPERLAN standard .based. Performance parameters.Protocols using directional antennas.Security requirements .Issues and challenges in security provisioning . UNIT IV ENERGY MANAGEMENT 9 Need. goals and classification .Ad Hoc Wireless Internet.Communication throughput performance .End delay performance .

CRC press.Toh. 5. 2002.S. 2004. Silvia Giordano and Ivan Stojmenovic. "The Handbook of AdHoc Wireless Networks". 68 . "AdHoc Networking". C. C. Mohammad Ilyas. 2000. Siva Ram Murthy and B. 4. Prentice Hall PTR. Mobile AdHoc Networking. Wiley IEEE press. 2001. Charles E. K. "AdHoc Wireless Networks: Architectures and protocols". Manoj. 3. Marco Conti. 2. "AdHoc Mobile Wireless Networks: Protocols and Systems".M.Tech SOFTWARE ENGINEERING REFERENCES 1. Addison Wesley. Perkins. 2004. Stefano Basagni. Prentice Hall PTR.

Stephen J.Classification by decision tree induction . 2002.Concept description: Data Generalization and Summarization based characterization . Integration.Prediction .Mining association rules in large databases.Other classification methods . "Data Mining: Concepts and Techniques". Data Mining. 2004. UNIT II DATA PREPROCESSING AND ASSOCIATION RULES 9 Data preprocessing . 2. Transformation.Overview of data mining techniques. Databases . Morgan Kaufmann Publishers.Data warehouse architecture .Data warehouse implementation . Micheline Kamber. 69 . Tata Mcgraw Hill.Categorization of OLAP Tools.OLAP . UNIT IV DATA WAREHOUSING 9 Data warehousing components .Steps in data mining process .Categorization of major clustering methods: partitioning methods Hierarchical methods.Architecture of a typical data mining systems . UNIT V APPLICATIONS 9 Applications of data mining WWW .Mining text database . Jiawei Han.M. "Data Warehousing.Multi dimensional data model .Need .Data cleaning.Classification of data mining systems .& OLAP".Mapping the data warehouse to multiprocessor architecture . TOTAL= 45 REFERENCES 1. Smith.Clusters analysis: types of data In cluster analysis .Tech SOFTWARE ENGINEERING CSY 113 UNIT I DATA WAREHOUSING AND DATA MINING INTRODUCTION L T P C 3 0 0 3 9 Relation to statistics. UNIT III PREDICTIVE MODELING 9 Classification and Prediction: Issues Regarding Classification and Prediction . Alex Berson.Bayesian classification .Data mining functionalities . Reduction Discretization concept hierarchies .Mining spatial databases.

M. "Data Warehousing In Action". 1998... "The Data Warehouse Life Cycle Toolkit". Padhrai Smyth and Ramasamy Uthurusamy. "Advances in Knowledge discovery and Data Mining". Gregory Piatetsky Shapiro. 4.Tech SOFTWARE ENGINEERING 3. Sean Kelly. John Wiley & Sons Inc. 1997. The M.I. 1996. Ralph Kimball. John Wiley & Sons Inc.Fayyad. 70 .T Press. Usama M. 5.

Networks of queues .Bayes theorem .Discrete and Continuous random variables . Howard E.Design . Fortier.Fundamental concepts and performance measures.Computer networks components .Estimating parameters and Distributions .Simulation Analysis .Birth death process .M.Time control Systems and Modeling.Probability generating functions (PGF) and Laplace Transforms (LST) numerous examples from computer networking. Michael.Database system performance .Computer architecture . 2003. TOTAL = 45 TEXTBOOK 1. Elsevier Science.Conditional probability .Simulation process .Performance metrics and Evaluation criteria .Role of performance evaluation Performance evaluation methods .Tech SOFTWARE ENGINEERING CSY 114 UNIT I PERFORMANCE EVALUATION OF COMPUTER SYSTEMS AND NETWORKS FUNDAMENTALS L T P C 3 0 0 3 9 Need for performance evaluation .Common distributions .CPU and I/O architectures .Random variables .Timed petri nets .Workloads .Classical petri nets . UNIT V ANALYSIS 9 OS components .Computational methods . Discrete Time Markov chains (DTMC) .Priority-based petri nets Colored petri nets .Distributed and Network architectures Secondary storage .Total probability .Markov process.Topologies .Multiple server computer system analysis.Performance metrics .Tool selection . Paul J. 71 .Workloads .Generalized petri nets . UNIT III QUEUING THEORY 9 Queuing systems .Stochastic processes .Validation of results .Densities -Expectation .Poisson process .Probability distributions . "Computer Systems Performance Evaluation and Prediction".Simulation modeling of LAN.Evaluation . UNIT II PROBABILITY AND STOCHASTIC PROCESSES 9 Scheduling algorithms .System architecture . UNIT IV PETRI NETS AND SYSTEM PERFORMANCE 9 Petri nets .

"Measurement & Tuning of Computer Systems ".M. 4. 3. Robertazzi. Michael F. McGraw -Hill. 72 .Tech SOFTWARE ENGINEERING REFERENCES 1. Mories and Paul F. Giuseppe Serazzi and Alexandra Zeijher. Domenico Ferrari. "Computer system performance". K. Herbert Hellerman and Thomas F. "Introduction to computer system performance Evaluation". 2000.Kant and M. "Computer Networks and Systems Queing theory and Performance Evaluation". 1982. 1983. Springer.Srinivasan. "Tools and techniques Computer Performance Evaluation". Thomas G. Roth. 2. Prentice Hall Inc. 5. 1992.M. Van Nostrand. 1992.Conroy. 3rd edition. McGraw Hill.

Stuart Russell and Peter Norvig.Search strategies . Vol.A Modern Approach".Building a knowledge base . 2938. Prentice Hall. "Artificial Intelligence". Zili Zhang.Logic . 4.Value of information . AW.Environment .General model .Representation of planning .Preplanning agents. Patrick Henry Winston. 1995.Types of communicating agents .Structure . "Agent-Based Hybrid Intelligent Systems".Formulating .M.First order logic . UNIT V HIGHER LEVEL AGENTS 9 Learning agents ."Principles of Artificial Intelligence".Nilsson.Future of AI. Chengqi (editions.Conditional planning .Partial order planning Practical planners .Learning decision trees .Utility theory . UNIT IV AGENTS AND UNCERTAINTY 9 Acting under uncertainty . 2.Communicative agents . TOTAL= 45 REFERENCES 1.Tech SOFTWARE ENGINEERING CSY 115 UNIT I AGENT BASED INTELLIGENT SYSTEMS INTRODUCTION L T P C 3 0 0 3 9 Definitions .) 2004. 1992.Decision theoretic agent design. 3.J. 73 .General ontology . " Artificial Intelligence .Probability Bayes rule and use . Narosa Publishing House. Nils.Intelligent search .Knowledge in learning . UNIT II KNOWLEDGE BASED AGENTS 9 Representation . 1999.Decision network .Reflex agent .Belief networks .Complex problem solving . UNIT III PLANNING AGENTS 9 Situational calculus .Game playing as search.Reinforcement learning .Inductive learning .Logical recovery.Intelligent agents .Basic problem solving agents . Zhang.History . 3rd edition.Inference .

Boston. Microsoft Press. 2.Economics of defect removal UNIT V QUALITY 9 Design defects . Watts S." Software Engineering: A Practitioner's Approach". UNIT IV DEFECT HANDLING 9 Finding defects . "PSP: A Self .Tech SOFTWARE ENGINEERING CSY 116 UNIT I PERSONAL SOFTWARE PROCESS INTRODUCTION L T P C 3 0 0 3 9 Software engineer's job . UNIT III PLANNING 9 Managing schedules .Wesley. MA: Addison .Projecting defects . 2004. 6th edition.Product size .Project plan . 4.Tracking time .Product quality .M. Steve McConnell.Function points .Software development process Defects . 1997.Wesley.Updated PSP. 3. Humphrey. "Code Complete: A Practical Handbook of Software Construction".Managing commitments. Pressman and Associates.Code review checklist .A personal commitment to quality. 2005. 2005. Watts S.Improvement Process for Software Engineers". Roger S Pressman. R.Period and Product planning. 74 .. Humphrey. TOTAL = 45 REFERENCES 1. UNIT II ESTIMATION AND MANAGEMENT 9 Case study . Addison .Time management . "Introduction to the Personal Software Process".Managing your time .Process quality .S.

Integration and System testing .Launching a Team Project .. 2. " Introduction to the Team Software Process".S. Pressman and Associates.Wesley. 2005. "TSP . 1997.Quality/ Process Manager .Managing yourself . UNIT V WRAPPING UP 8 Documentation .Planning Manager . Watts S.Wesley.Development Manager .Product implementation. Humphrey.. Roger S Pressman. Humphrey.Support Manager. 2000.Being on a team Teamwork.Designing with teams .SCM.Leading a Development Team".R. UNIT II TEAM ROLES 9 Team leader . UNIT III STRATEGY & PLANNING Development strategy . UNIT IV DEVELOPMENT 10 10 Defining the requirements .Tech SOFTWARE ENGINEERING CSY 117 UNIT I TEAM SOFTWARE PROCESS INTRODUCTION L T P C 3 0 0 3 8 PSP overview . Watts S. TOTAL = 45 REFERENCES 1. .Software inspections.Need statements for sample exercises . MA: Addison . "Introduction to the Personal Software Process".Development plan . Boston. Boston. 75 . 6th edition.Wesley. 4. Humphrey. 2005.Postmortem . 3.M. Watts S. MA: Addison . "Software Engineering: A Practitioner's Approach". Boston. MA:Addison .TSP overview .Logic of the TSP .

The spiral modelEvolutionary model.organizing the requirements document. UNIT V 9 Management of software project: Software project management .Case study .CMM Software standards.A software reengineering process model .M.System integration tools.Managing and Mitigating risks.General project maintenance .Software Integration and maintenance: Goals of system integration . Hardware .Personnel managementAssessment of project personnel . UNIT III 9 Software system design: The design activity. Software Requirements: Requirements engineering process. Imaging software and its properties: Classification of software qualities .Case study: A visual inspection system.Basic software engineering principles. Philip A.The role of the software engineer.Requirements users-Formal methods in software specifications.Specification of imaging systems .The Software production process: Programming languagesWriting and testing code.Unified process mode .Software integration . CRC Press.Lightweight methodologies.Faults .System verification .The role of testing .V model . 2003. UNIT IV 12 Software measurements and testing: The role of metrics .Object oriented analysis.code and program maintenance.Tech SOFTWARE ENGINEERING CSY 118 SOFTWARE ENGINEERING FOR IMAGE PROCESSING L T P C 3 0 0 3 UNIT I 6 Software engineering an overview: Introduction .Post integration software optimization . 76 . USA.Coding standards.Testing techniques.Software reuse .Software life cycle models .A case for a software engineering approach to building an imaging system .The second system effect.Types of requirements . UNIT II 9 Software Process and life cycle models: Software processes and methodologies ."Software Engineering for Image Processing".Hardware considerations in imaging system .Tracking and reporting progress-Cost estimation using COCOMO.Failures and bugs.A maintenance process model.Fountain model .Fault tolerant design.Procedural oriented designObject oriented design . TOTAL = 45 REFERENCES 1.Requirements validation and reviews. Laplante .Design of testing plans.System Unification.The nature of software for imaging system.

WS .guidelines .WS notification and eventing.WS co ordination .WS .WSOA platform . UNIT III SERVICE ORIENTATION 9 Service oriented architecture .Orchestration and coordination .WS policy framework .NET.Service layers .WSDL language basis .BPEL elements .Service modeling .Collaboration.Classifications of service models. UNIT IV TECHNOLOGIES AND DESIGN FOR SOA 11 Service oriented design .Different services layers .WSDL and SOA .Messaging with SOA.Common misperception .Message exchange patterns .Service orientation VS object orientation .Standards for SOA Comparison of SOA vs Past architecture .Interrelationship among principles .M.SOA comparison guide lines .Business process design .Benefits Pitfalls of adopting SOA .Tech SOFTWARE ENGINEERING CSY 119 UNIT I SERVICE ORIENTED ARCHITECTURE SOA AND WEB SERVICES FUNDAMENTALS L T P C 3 0 0 3 5 Fundamentals of SOA . SOA delivery life cycle phases .Security language basis .Policy assertions and alleviates policies relationship to activity management . TOTAL = 45 77 .Coordination .SOAP language basis .Related XML schema .Service activity .Configuration scenarios of service layers.Business protocols .Common principles of service Orientation .Business activities .Characteristics .SOA extension.Agile strategy .Process definitions . Addressing . UNIT II SECOND GENERATION WEB SERVICES 9 Activity management and comparison .Web service description language (WSDL) .Web services frame work .SOAPAWAOA .SOA support in J2EE and . UNIT V SERVICE DESIGN AND SECURITY 11 Service design .WS .Components .Industry standards XML AWSOA .Atomic transactions .SOA analysis .Guidelines .BPEL language basics .Service description .WS addressing language and messaging basis .Service oriented process design .Process services .Meta data exchange .Reliable messaging .Transition from XML to web service to SOA Reshaping of XML and web service through SOA .Service interface design tools .Metadata exchange security .

"SOA in Practice. Prentice Hall / Pearson. 2004. Thomas Erl. 2008. Nicolai M. 2005. 2nd edition. 4. REFERENCES 1. Wiley India Private Limited. Kevin T. The Art of Distributed System Design". 2009. Shankar Kambhampaty.Tech SOFTWARE ENGINEERING TEXT BOOK 1. Thomas Erl . 78 . "Applied SOA Service Oriented Architecture And Design Strategies". Balcer. 2. Pearson Education. 7. C. 6. 3. "Implementing SOA Total Architecture in Practice". Wiley India Private Limited. Mike Rosen. "Service-Oriented Architecture: Concepts. Boris Lublinsky. 2007. 2008. 1st edition.M. "SOA Principles of Service Design". 2nd edition. Paul. Technology & Design". Smith and Marc J. Brown. Prentice Hall ServiceOriented Computing Series. Eric Newcomer Greg Lomow. "Understanding SOA with Web Services". 2008. Service-Oriented Computing Series. Josuttis. 5. Thomas Erl. "Service Oriented Architecture for Enterprise Applications". Pearson Education. 2008. "Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services ". The Prentice Hall.

Case studies: Globus toolkit Architecture. QoS. 79 . UNIT III GRID SECURITY AND RESOURCE MANAGEMENT 9 Grid Security . "The Grid 2: Blueprint for a New Computing Infrastructure".Other monitoring systems.Federation services . Elsevier management challenges .Web and grid services .Grid security .MDS .X.PKI . 2005. "Grid Computing for Developers".Grid Computing .Grid scheduling and resource management.Grid ICE . TOTAL= 45 REFERENCES 1. components and features .M. 2004.Tech SOFTWARE ENGINEERING CSY 120 UNIT I GRID COMPUTING CONCEPTS AND ARCHITECTURE L T P C 3 0 0 3 9 Introduction .Parallel and distributed computing .Categories and origins of structured data . 3.Cluster computing . High Performance Computing: Paradigm and Infrastructure. challenges and applications. Deepa Nayar. Grid way and Grid bus broker principles of local schedulers.Collective data management services . Laurence Yang and Minyi Guo (editors)". Vladimir Silva.509 certificates . 2. USA. "Global Grids and Software Toolkits: A Study of Four GridMiddleware Technologies. Parvin Asadzadeh. trends. UNIT V GRID MIDDLEWARE 9 List of globally available middleware .A brief security primer . Wiley Press. Ian Foster and Carl Kesselman. Rajkumar Buyya. and Srikumar Venugopal.Generations of grid portals. Charles River Media. UNIT II GRID MONITORING 9 Grid Monitoring Architecture (GMA) . New Jersey. 2006.Anatomy and physiology of grid .An Overview of Grid Monitoring Systems .Features of next generation grid.Architectural approaches .Grid standards. Chun Ling Kei.Grid portals .Service Level Agreements (SLAs) . UNIT IV DATA MANAGEMENT AND GRID PORTALS 9 Data management .

Srikumar Venugopal. " Grid Resource Management:State of the Art and Future Trends ". Schopf and Jan Weglarz. 1st edition. The Elsevier Series in Grid Computing". Jennifer M. Borja Sotomayor and Lisa Childers. 5. 2005. Hey. 80 .G. 2004. Geoffrey Fox and Anthony J. "Globus Toolkit 4: Programming Java Services.Tech SOFTWARE ENGINEERING 4. Jarek Nabrzyski. 9. 7. "Grid Computing". "Grid Computing: Making The Global Infrastructure a Reality". USA. Maozhen Li and Mark Baker. Wiley Press. Hussein Gibbins and Rajkumar Buyya. 8. "Designing a Resource Broker for Heterogeneous Grids. International Series in Operations Research & Management Science. Krishna Nadiminti. Wiley. Joshy Joseph and Craig Fellenstein. Springer.M. 6. 2005. Morgan Kaufmann. IBM Press. Software: Practice and Experience". 2003. 2008. "The Grid: Core Technologies". 2003. New York. Fran Berman . Wiley.

Airline check in and Booking . UNIT IV MIDDLEWARE AND DEVICE TECHNOLOGY 9 Middleware support .Human Machine Interface .Car information systems .Embedded Linux Comparison .Operating systems: Palm OS .Data dissemination .Windows CE .Displays . UNIT V PERVASIVE APPLICATION ARCHITECTURE AND EXAMPLES 9 Background .mail access via WAP and voice.Health care .Tracking .Pervasive information technology .Hardware: Batteries . UNIT III DATA DISSEMINATION.EPOC .Mobile cache maintenance schemes .Mechanisms for adaptation: spectrum of adaptation .Agents .Infrastructure . MANAGEMENT AND CONTEXT AWARE COMPUTING 9 Publish subscribe mode .Resource monitoring .Mobile web caching .Diversification .Sales force automation .Processor . UNIT II ADAPTATION IN MOBILE AND PERVASIVE COMPUTING 9 Adaptability .Tech SOFTWARE ENGINEERING CSY 121 UNIT I PERVASIVE COMPUTING FUNDAMENTALS L T P C 3 0 0 3 9 Evolution .Mobile middleware .QNX Neutrino .Incorporating adaptations in applications .E .Use of the framework .Applied pervasive computing .Usage examples: Retail .Types Core capabilities for context awareness .Mobile data caching .Scenarios .Mobile agents .Support for adaptive applications.Information caching -Challenges for distributed data management . TOTAL = 45 81 .Puppeteer .Types of context aware applications.Roaming Environment .Characterizing adaptation strategies .Ubiquitous computing .Connectivity Simplification .Securing pervasive computing applications .Adaptation middleware .Context: Definitions .Personalized services and the virtual pervasive home.BeOS .M.Java for pervasive devices.Example application architecture: Odyssey . Principles: Decentralization .Overview of classes .Scalability and Availability .Pervasive computing.Application architecture .Memory .Service discovery .

. Rindtorff. Nicklous and Thomas Stober . 82 .Technology and architecture of mobile internet applications". J. Buckhardt. H. Pearson Education. 3.2003.. 2.Hill.Sandeep Gupta."Pervasive Computing .Tech SOFTWARE ENGINEERING TEXT BOOKS 1.M.2002. Lother Merk. Uwe Hansmann.. Golde Richard and Loren Schweibert "Fundamentals of mobile and pervasive computing". Schack and T. Low Price Edition. Henn. Tata McGraw . Hepper."Pervasive Computing . Frank Adelstein. Martin S.The Mobile World". First Edition. Springer Professional Computing .Second Edition. S.

Dream Tech Ltd.Web user interface .M. 83 REFERENCES 1.Custom control .Operations .Design standards .Based controls: Characteristics .Image. . John Wiley& Sons.Computer interface .Usability . "The Essential of User Interface Design".Human interaction speed .Screen .Importance . Wilbent.Components .Tech SOFTWARE ENGINEERING CSY 122 UNIT I USER INTERFACE DESIGN INTRODUCTION AND OVERVIEW L T P C 3 0 0 3 9 Introduction .Presentation control.Presentation styles .Human characteristics in design .Business functions . Alan Cooper.Web systems .Text boxes .Accessibility . O.Selecting menu choice .Direct .Obstacles .. UNIT II THE GUI SCREEN DESIGN PROCESS 9 User interface design process .Phrasing the menu .Guidance & assistance Internationalization .Contents of menu .System timings . Wiley .Organizations . 2001.Navigating menus . UNIT IV WINDOW COMPONENTS 9 Windows: Characteristics .Formatting .Graphical menus. Galitz.Human consideration in screen design.Human . UNIT III MENU DESIGN 9 Structures of menus .Combination control .Basic business functions .Based controls: Operate control .Requirement analysis .Icons .Effective feedback .Types Managements .Characteristic & principles.Popularity . "The Essential Guide to User Interface Design".Selection control .Characteristics of graphics interface . 2002.Direct manipulation graphical system .Functions of menus .Indirect methods . UNIT V TEXT AND DESIGN PAGE 9 Text for web pages . TOTAL = 45 TEXT BOOK 1.Device .

Reengineering.Case Studies.Software maintenance frame work . Alain April .Forward engineering .Ltd. 84 . Wiley . UNIT IV 9 Maintenance Measures .Reuse oriented model .Armstrong A Takang .Documentation ." Software Maintenance Management: Evaluation and Continuous Improvement". REFERENCES 1..Maintenance manual ." Software Maintenance: Concepts and Practice".IEEE Computer Society Press.2nd edition.Limitations and economic implications.Reverse Engineering .Restructuring .Quick Fix Model .M.Guidelines for building maintenance measures Building and sustaining maintainability. UNIT III 9 Program understanding .Levels of reverse engineering . UNIT II 9 Maintenance Process . UNIT V 9 Maintenance tools . World Scientific Publishing Co.Process maturity. 2008.2003.Ptc.Iterative enhancement model .The need for software maintenance .Categorizing software change .Program comprehension .Other supporting techniques .Comprehension process models .Tech SOFTWARE ENGINEERING CSY 123 UNIT I SOFTWARE MAINTENANCE L T P C 3 0 0 3 9 Introduction . TOTAL=45 TEXTBOOK 1.Fundamentals of software change .Alain Abran. Panygrub.Models .Boehm's model .Osborne's Model .

Unification multimodal integration and Parsing. VisualBasics of data acquisition: Audio. GUI. Audio enhancement techniques for forensics: Objectives of forensic analysis. Multimodal Interfaces: Unimodal. UNIT V SECURITY AND SURVEILLANCE APPLICATIONS 9 Security and surveillance applications: Requirements analysis.M. Multimedia interfaces. UNIT III AUDIO RECOGNITION AND CLASSIFICATION 9 Audio recognition and classification: Feature extraction. Video-Single microphone source separation. Fusion of audiovisual attention. UNIT II AUDIO ATTENTION MODELLING AND DATA FUSION 9 Audio attention modelling and data fusion: Types of attention. Multimodal Dialog management. Multimodal synchronization. Modality recognition. 85 . Training and pattern matching. Interaction Modalities: Acoustic. Source separation. Tactile. Multimodal integration and understanding: Early approaches. Hidden Markov Modelling. Audio-based human computer interaction: Audio scene analysis. ?Measuring attention. Case study: Gaze recognition UNIT IV ISSUES IN THE DESIGN AND IMPLEMENTATION OF MULTIMODALITY 9 Issues in the design and implementation of Multimodality: Multimodal user interface client. Admissibility of audio evidence.Tech SOFTWARE ENGINEERING CSY 124 Aim: w w w w MULTIMODAL COMPUTING L T P C 3 0 0 3 Intoduction to Multimodal systems Motivations for Multimodality Applications of Multimodality Building Multimodal Interfaces INTRODUCTION TO MULTIMODAL SYSTEMS 9 UNIT I Introduction to Multimodal systems. Acquisition of digital evidence. Multimodal generation: Multimodal output planning. Audio analysis as part of larger systems. Training and pattern matching. Challenges. Source localisation. Modality integration and understanding.

Algorithms and Applications Springer. 2. Damiano. 26. Algorithms. Intelligent Environments: Methods. E. 2006. Video. Case Study involving Gesture recognition. Algorithms and Systems. Wang. TOTAL: 45 TEXTBOOKS 1. Jeong. Gros. Wiley . P. Springer. J. and Applications. W. Brown.M. Vol. Maragos. Text. P. Potamianos. Image and Video Analysis: Theory and Applications Springer. C. Maher. pp. New Directions in Intelligent Interactive Multimedia. D.IEEE Press. L. 2007. D. Y. 2010. A. IEEE Signal Processing Magazine. 86 . 2009. Machine Audition: Principles. G. IGI Global. No.Tech SOFTWARE ENGINEERING Performance analysis and comparison. Audio Forensic Examination. R. 2009. Machine Learning for Audio. P. Remagnino. Multimodal Processing and Interaction: Audio. Computational Auditory Scene Analysis: Principles. F. 3. 2010. Camastra. 2. Springer. Kuno. 84-94. 3. Monekosso. Wang. Jain. REFERENCES 1. 2. 4. 2008.

UNIT IV QUEUING THEORY 9 Single and Multiple server Markovian queuing models .Chranes method of penalties . UNIT II PROBABILITY.Nature and use of arguments.Simplex method .Binomial.Moments generating functions and their properties . Poisson. Sequencing problems . UNIT V CASE STUDIES 9 Presentation by students on their area of interest. Exponential distributions . 2005. Geometric. New Delhi .Processing each of n jobs through m machine.Graph theory.M. 87 .Latin square design -22 factorial design.Stimulation and Graphical solution canonical and standard terms of Linear programming problem . 2nd edition.Connected graph Tree.Function of random variables. Nicholas Walliman. STATISTICAL INFERENCE AND ANALYSIS 9 Probability . UNIT III OPERATIONS RESEARCH AND OPTIMIZATION TECHNIQUES 9 Basic of operation research : Characteristic of OR-OR and Decision making Linear programming .Moments .Customer impatience -Queuing applications. how to deal with it .Completely randomized design .Linear Programming . Uniform.Basic definitions .Tech SOFTWARE ENGINEERING CSY 019 UNIT I RESEARCH METHODOLOGY FOR COMPUTER SCIENTIST L T P C 3 0 0 3 9 RESEARCH PROBLEM The Research problem . .Introduction to supervised and unsupervised learning .Types of research . TOTAL = 45 TEXT BOOKS 1.Formulation and solution of transportation models. "Your Research Project". Vistaar Publications. Normal.Randomized block design .Algebraic solution . Design of experiments: Analysis of variance .Random variables .One way and two way classifications.Information.Errors in selecting a good research problem .Concept of duality .Sources of research problem .properties of duality -Transportation model: Definition .Criteria / Characteristics of a good research problem .

. "Operations Research: An Introduction". Myer R.. 2000. 3. Pragati Prakashan. Pearson Education Edition. 2002. and Ye.. "Probability and Statistics for engineers and Scientists". Delhi. 3.H. 7th edition.. New Delhi.M. Freund.L... REFERENCES 1. J. "Fundamentals of Mathematical Statistics". 2.C.K. 2001.K. Asia. S. New Delhi. Sultan Chand and Sons.Tech SOFTWARE ENGINEERING 2. "Operations Research". K. 88 . H. I.R. Taha. 5th edition.S. Prentices Hall of India.. V. Meerut. B. and Miller.E. Walpole. New Delhi. Goel. and Mittal S.E. 1994. Myer.A. Pearson Education. Gupta. R. "Probability and Statistics for Engineers". S. and Kapoor. 7th edition. 2002.