Scribd
Upload
13 views

Software_Engineering

Uploaded by

yemmanithish
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
13 views

Software_Engineering

Uploaded by

yemmanithish
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SOFTWARE ENGINEERING

V Semester: CSE (DS)


Course Code Category Hours / Week Credits Maximum Marks
L T P C CIA SEE Total
ACDC04 Core
3 0 0 3 30 70 100
Contact Classes: 45 Tutorial Classes: Nil Practical Classes: Nil Total Classes:45
Prerequisites: There are no prerequisites to take this course.
I. COURSE OVERVIEW:
Software engineering is a discipline that allows us to apply engineering and computer science concepts in the
development and maintenance of reliable, usable, and dependable software. This course is designed to present
software engineering concepts and principles in parallel with the Software Development Life Cycle. At the
end of this course, students will learn the project management for the purpose of delivering high-quality
software that satisfies customer needs and is within the budget.

II. COURSE OBJECTIVES:


The students will try to learn:
I The elicitated requirements for a software development life cycles.
II The design considerations for enterprise integration and deployment.
III Quality assurance techniques and testing methodologies.
IV The plan for a software project that includes the size , effort, schedule, resource allocation,
configuration control, and project risk.

III. COURSE OUTCOMES:


After successful completion of the course, students should be able to:
CO 1 Illustrate process models, approaches and techniques for managinga software Understand
development process.
CO 2 Summarize the importance of project planning activities that accurately help in Understand
selection and initiation of individual projects and portfolios of projects in the
enterprise.
CO 3 Explain software design model and behavior of a software system. Understand
CO 4 Develop the approaches for implementaion, verification and validation Apply
including static analysis and reviews.
CO 5 Demonstrate the concept of risk management through risk identification, Understand
risk measurement and mitigation.
CO 6 Make use of earned value analysis and project metric for scheduling and Analyze
improving the quality of software.

IV. SYLLABUS:
MODULE – I: SOFTWARE PROCESS AND PROJECT MANAGEMENT (08)
Introduction to software engineering, software process, perspective, and specialized process models; Software
project management: Estimation: LOC and FP based estimation, COCOMO model; Project scheduling:
Scheduling, earned value analysis, risk management

MODULE – II: REQUIREMENTS ANALYSIS AND SPECIFICATION (09)


Software requirements: Functional and nonfunctional, user requirements, system requirements, software
requirements document; Requirement engineering process: Feasibility studies, requirements elicitation and
analysis, requirements validation, requirements management; Classical analysis: Structured system analysis,
petri nets, data dictionary.

MODULE – III: SOFTWARE DESIGN (09)


Design process: Design concepts, design mode, design heuristic, architectural design architectural styles,
architectural design, and architectural mapping using data flow.

User interface design: Interface analysis, interface design; Component level design: Designing class-based
components, traditional components.

1|Page
MODULE – IV: TESTING AND IMPLEMENTATION (10)
Software testing fundamentals: Internal and external views of testing, white box testing, basis path testing,
control structure testing, black box testing, regression testing, MODULE testing, integration testing, validation
testing, system testing and debugging; Software implementation techniques: Coding practices, refactoring.

MODULE – V: PROJECT MANAGEMENT (09)


Estimation: FP based, LOC based, make/buy decision; COCOMO II: Planning, project plan, planning process,
RFP risk management, identification, projection; RMMM: Scheduling and tracking, relationship between
people and effort, task set and network, scheduling; EVA: Process and project metrics.
V. TEXTBOOKS:
1. Roger S. Pressman, “Software Engineering – A Practitioner’s Approach”, McGraw-Hill International
Edition, 7th Edition, 2010.
2. Ian Somerville, “Software Engineering”, Pearson Education Asia, 9 th Edition, 2011.

VI. REFERENCE BOOKS:


1. Rajib Mall, “Fundamentals of Software Engineering”, PHI Learning Private Limited, 3 rd Edition, 2009.
2. Pankaj Jalote, “Software Engineering, A Precise Approach”, Wiley India, 1 st Edition, 2010.

VII. WEB REFERENCES:


1. http://www.softwareengineerinsider.com/articles/what-is-software-engineering.html
2. https://www.udacity.com/courses/software-engineering
3. http://www.tutorialspoint.com/software_engineering
4. http://computingcareers.acm.org/?page_id=12
5. http://en.wikibooks.org/wiki/Introduction_to_Software_Engineering

2|Page

You might also like