IT3203 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3

Transcription

1 Fundamentals of Software Engineering (Compulsory) BIT 2 nd YEAR SEMESTER 3 INTRODUCTION This course is designed to provide the students with the basic competencies required to identify requirements, document the system design and maintain a developed system. It presumes a general understanding of computers and programming which are covered in the first and second semester of the degree. Software engineering is a subject that emerged recently as a result of the need to manage software projects that are rising in demand day by day. Software is developed in diverse areas and the fact that a systematic approach is required to manage their development spawns this interesting subject of study. CREDITS: 04 LEARNING OUTCOME After successfully completing this module the student will be able to; explain the software engineering principles and techniques that are used in developing quality software products apply software engineering principles and techniques appropriately to develop moderately complex software system OUTLINE OF SYLLABUS Topic Minimum number of hours Introduction 06 Software Process Models 10 Requirements Analysis & Specification 10 Design 12 Coding 04 Testing 07 Maintenance 04

2 Computer Aided Software Engineering (CASE) 02 Software quality assurance 02 Managing Software Projects 03 Total for the Subject 60 SYNOPSIS/OVERVIEW Stakeholders always expect to build software by avoiding bad things that prowl in the shadow of failed efforts. Therefore it has become a necessity to follow a systematic, disciplined, quantifiable approach such as software engineering that includes designing and developing disciplines. This course is designed to teach the students the software developing process that includes requirements Analysis & Specification, designing, coding, testing and maintenance. Talk about different software engineering process models to identify the most appropriate software process model for a given problem. Further the students will learn basic software engineering principles such as software quality assurance. PEDAGOGICAL FRAMEWORK This course is delivered through video lectures, teacher s notes and learning activities. You have to submit your observations to databases in the LMS and participation in forum discussions to learn collaboratively. EXPECTATIONS/EXAMINATIONS/REQUIREMENTS The learners are expected to obtain knowledge and master necessary skills to apply software engineering principles and techniques when developing quality software products or a software system. A practice quiz is provided to the learner at the end of the content of each section and two assignments are provided one at the end of the first half of the syllabus and the other at the end of the full syllabus. Marks for the activities and practice quizzes are not counted but marks for the assignments are tracked by the LMS and a pass grade is issued. Obtaining pass grades for the two assignments and Final Exam are mandatory for the completion of Semester 3.

3 REQUIRED MATERIALS Main Reading Ref. 1: Software Engineering by Ian Sommerville, 7th edition, Addison-Wesley, Ref. 2: Software Engineering: A practitioner's approach by Roger S. Pressman, 6th edition, McGraw-Hill International edition, Web references Ref. 3: Ref. 4: DETAILED SYLLABUS Section 1: Introduction (06 hrs.) Describe what software is, different types of software and software quality attributes Describe with the problems associated with software and software development Define what software engineering is and explain why it is important State some professional issues related to software development 1.1. Software What is software? [Ref.1: pg ] Types of software [Ref.2: pg ] Characteristics of Software [Ref.2: pg ] [Ref.4] Attributes of good software [Ref.1: pg ] 1.2. Software Engineering What is software engineering? [Ref.1: pg. 29] Software engineering costs [Ref.1: pg ] What are the key challenges facing software engineering? [Ref.1: pg ] Systems engineering & software Engineering [Ref.1: pg ; Ref. 2: pg ] Professional Practice [Ref.1: pg ; Ref.2: pg ]

4 Section 2: Software Development Process Models (10hrs.) Describe different process models used for software development Teach to identify the most appropriate software process model for a given problem 2.1. The generic software lifecycle [Ref.1: pg. 30] 2.2. What is a process model? [Ref.1: pg , 87-88] 2.3. The waterfall model [Ref.1: pg ; Ref. 2: pg ] 2.4. Prototyping model [Ref.1: pg ; Ref.2: pg ] 2.5. Component-Based Software Engineering (CBSE) [Ref.1: pg ] 2.6. Incremental development [Ref.1: pg ; Ref.2: pg ] 2.7. Rational Unified Process (RUP) [Ref.1: pg ] 2.8. Spiral model [Ref.1: pg ; Ref. 2: pg ] 2.9. Agile methods [Ref.1: pg ] Extreme programming [Ref.1: pg ] Rapid Application Development (RAD) [Ref.1: pg ; Ref.2: pg ] Section 3: Software Requirement Analysis and Specification (10hrs.) Identify the types of requirements, which should be captured in a software project Describe and apply different requirement analysis and specification techniques Prepare a software requirement specification (SRS) for a given software problem 3.1. System and software requirements [Ref. 2: pg ] 3.2. Types of software requirements Functional and non-functional requirements [Ref.1: pg ] Domain requirements [Ref. 1: pg ] User requirements [Ref. 1: pg ] 3.3. Elicitation and analysis of requirements Overview of techniques [Ref. 1: pg ] Viewpoints [Ref. 1: pg ] Interviewing [Ref. 1: pg ] Scenarios [Ref. 1: pg ] Use-cases [Ref. 1: pg ]

5 Ethnography [Ref. 1: pg ] 3.4. Requirement validation [Ref. 1: pg ] 3.5. Requirement specification [Ref.1: pg ] 3.6. Feasibility [Ref. 1: pg ] Section 4: Software Design (12hrs.) Describe the important software design issues and concepts Compare different approaches to software design Apply suitable design approaches for a problem 4.1. Design concepts Abstraction [Ref. 2: pg. 265] Architecture [Ref. 2: pg ] Patterns [Ref. 2: pg. 266] Modularity [Ref. 2: pg ] Cohesion [Ref. 2: pg: ] Coupling [Ref. 2: pg: ] Information hiding [Ref. 2: pg. 268] Functional independence [Ref. 2: pg ] Refinement [Ref. 2: pg. 269] 4.2. Architectural design Repository model [Ref. 1: pg: ] Client-server model [Ref. 1: pg , ] Layered model [Ref. 1: pg ] Modular decomposition [Ref. 1: pg ] 4.3. Procedural design using structured methods [Ref. 2: pg ] 4.4. User Interface design Human-computer interaction [Ref. 1: pg ] Information presentation [Ref. 1: pg ] Interface evaluation [Ref. 1: pg ] 4.5. Design notations [Ref. 1: pg ]

6 Section 5: Coding (04hrs.) Select appropriate programming language and development tools for a given problem Identify the features of a good program, good programming practices and program documentation 5.1. Programming languages and development tools [Ref. 3] 5.2. Selecting languages and tools [Ref. 3] 5.3. Good programming practices [Ref. 2: pg ] Section 6: Testing (07hrs.) State the software testing process and required documentation Explain the different software testing techniques and integration strategies Design test cases and write test programs for a given simple software problem Describe the code verification techniques Write codes for a simple software project using good programming practices 6.1. Verification and validation [Ref. 1: pg ] 6.2. Techniques of testing Black-box and White-box testing [Ref. 2: pg ] Inspections [Ref. 1: pg ] 6.3. Levels of testing Unit testing [Ref. 1: pg ] Integration Testing [Ref. 1: pg ; Ref.2: pg ] Interface testing [Ref. 1: pg ] System testing [Ref. 2: pg ] Alpha and beta testing [Ref. 2: pg ] Regression testing [Ref. 2: pg. 401] 6.4. Design of test cases [Ref. 1: pg ]

7 Section 7: Software Maintenance (04hrs.) Describe the types of software maintenance Describe the software maintenance process Describe activities of configuration management 7.1. Evolving nature of software [Ref. 1: pg ] Different types of maintenance [Ref. 1: pg ] Re-engineering [Ref. 1: pg ] 7.2. Configuration Management (CM) Importance of CM [Ref. 1: pg ] Configuration items [Ref. 1: pg ] Versioning [Ref. 1: pg ] Section 8: Computer Aided Software Engineering (CASE) (02hrs.) Identify the need for use of appropriate CASE tool for software development Describe the features of a CASE tool 8.1. Overview of CASE approach [Ref. 1: pg ] 8.2. Examples of CASE tools [Ref. 1: pg ] Section 9: Software Quality Assurance (02hrs.) Describe the importance of software quality Distinguish the difference between product quality and process quality Describe some important quality standards with respect to software 9.1. Quality management activities [Ref. 1: pg ] 9.2. Product and process quality [Ref. 1: pg ] 9.3. Standards [Ref. 1: pg ] ISO9000 [Ref. 1: pg ] Capability Maturity Model (CMM) [Ref. 2: pg ]

8 Section 10: Managing Software Projects (03hrs.) State the requirement of managerial control of the development process Describe the main phases of software project management Describe project planning and project scheduling activities in detail Need for the proper management of software projects [Ref. 1: pg ] Management activities Project planning [Ref.1: pg ] Estimating costs [Ref.1: pg , 660] Project scheduling [Ref. 1: pg ] Risk management [Ref. 1: pg ] Managing people [Ref. 1: pg ]