Text book 1: Chapter7, Chapter8 – 8.1, Chapter9 – 9.1, 9.2, 9.3 RBT: L1, L2, L3 08 Course Outcomes: The student will be able to :•Explain the basic organization of a computer system. •Demonstrate functioning of different sub systems, such as processor, Input/output,and memory. •Illustrate hardwired control and micro programmed control, pipelining, embedded and other computing systems. •Design and analyse simple arithmetic and logical units. Question Paper Pattern:•The question paper will have ten questions. •Each full Question consisting of 20 marks •There will be 2 full questions (with a maximum of four sub questions) from each module. •Each full question will have sub questions covering all the topics under a module. •The students will have to answer 5 full questions, selecting one full question from each module.Textbooks: 1.Carl Hamacher, Zvonko Vranesic, Safwat Zaky, Computer Organization, 5th Edition, Tata McGraw Hill, 2002. (Listed topics only from Chapters 1, 2, 4, 5, 6, 7, 8, 9 and12) Reference Books: 1.William Stallings: Computer Organization & Architecture, 9thEdition, Pearson, 2015.
SOFTWARE ENGINEERING (Effective from the academic year 2018 -2019) SEMESTER – IIISubject Code 18CS35 CIE Marks 40 Number of Contact Hours/Week 3:0:0 SEE Marks 60 Total Number of Contact Hours 40 Exam Hours 3 Hrs CREDITS –3 Course Learning Objectives: This course (18CS35) will enable students to:•Outline software engineering principles and activities involved in building large software programs. •Identify ethical and professional issues and explain why they are of concern to software engineers. •Describe the process of requirements gathering, requirements classification, requirements specification and requirements validation. •Differentiate system models, use UML diagrams and apply design patterns. •Discuss the distinctions between validation testing and defect testing. •Recognize the importance of software maintenance and describe the intricacies involved in software evolution. •Apply estimation techniques, schedule project activities and compute pricing. •Identify software quality parameters and quantify software using measurements and metrics. •List software quality standards and outline the practices involved. •Recognize the need for agile software development, describe agile methods, apply agile practices and plan for agility. Module 1 Contact Hours Introduction: Software Crisis, Need for Software Engineering. Professional Software Development, Software Engineering Ethics. Case Studies. Software Processes: Models: Waterfall Model (Sec 2.1.1), Incremental Model (Sec 2.1.2)and Spiral Model (Sec 2.1.3). Process activities. Requirements Engineering: Requirements Engineering Processes (Chap 4). Requirements Elicitation and Analysis (Sec 4.5).Functional and non-functional requirements (Sec 4.1). The software Requirements Document (Sec 4.2). Requirements Specification (Sec 4.3).