Scribd
Upload
87 views17 pages

Introduction To Software Engineering Course Outline: Naveed Anwer Butt Office: A-207 Lab: CS/IT Research Lab

This document outlines the course "Introduction to Software Engineering". The course aims to teach students how to develop high-quality software using software engineering practices. It will cover topics like requirements engineering, software design, testing, project management, and processes. Students will learn to analyze and evaluate CASE tools. The expected learning outcomes are that students will be able to develop information systems following a disciplined approach and proper documentation. They will also learn the importance of quality, testing, and project management.

Uploaded by

zaheergtm
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
87 views17 pages

Introduction To Software Engineering Course Outline: Naveed Anwer Butt Office: A-207 Lab: CS/IT Research Lab

This document outlines the course "Introduction to Software Engineering". The course aims to teach students how to develop high-quality software using software engineering practices. It will cover topics like requirements engineering, software design, testing, project management, and processes. Students will learn to analyze and evaluate CASE tools. The expected learning outcomes are that students will be able to develop information systems following a disciplined approach and proper documentation. They will also learn the importance of quality, testing, and project management.

Uploaded by

zaheergtm
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 17

Introduction to Software Engineering

Course Outline

Naveed Anwer Butt


naveed@uog.edu.pk
Office: A-207
Lab: CS/IT Research Lab
Aims & Objectives
 Application of SE practices to the
development of software in
information system development
domain where professionalism,
quality, schedule, and cost are
important in producing an information
system.
Objectives
 Understand the importance and need
 Discuss different software development
 Project management concepts for of a high-
quality product Development
 Comprehensive knowledge regarding
software development lifecycle-SDLC
 Demonstrate, an appropriate set of tools to
support the development.
 Hands on Training for CASE Tools and
Testing tools.
Before Taking This Course…
You should be comfortable with…
 Software and Types of Software!

 You should be comfortable with software


descriptions and implementations in different
areas
 Databases
 Understanding of the database concept and
familiarity with database terms and terminology
 Basic System development life cycle
background
Outline Syllabus

 Introduction to Software Engineering


 Software models
 Requirements Engineering
 Software Design and Implementation
 Software verification, validation and
testing
 Management of Software Projects &
Cost Estimation
After Taking this Course…
You should be able to …
 The students will be able to develop information systems in a
disciplined way, to meet their educational and
professional requirements.
 Students will develop the necessary documentation and
follow the phase-by-phase approach towards software
development.
 The students will be proficient enough to analyze, evaluate
and apply a set of CASE tools in a given area of software
development in order to compete local and international
market.
 The execution of term project in order to implement the
software engineering concepts.
 The students will be proficient enough to analyze, evaluate
and apply a set of CASE tools
 Importance and need of software engineering to cope with
the modern trends in software industry
 Understanding quality, testing issues
Textbook and References
 Textbook: Ian Sommerville. Software E
ngineering, 7th or 8th edition. Addison
Wesley. 2004. ISBN: 0-321-21026-3

 References
 Roger S. Pressman. Software Engineeri
ng: a practitioner’s approach, 5th or 6th
edition. McGRAW-HILL. 2005.
Course Web Site
 For announcements, lecture slides,
handouts, assignments, quiz
solutions, web resources:
 Students will have Download from
UOGIS
Other Stuff
 Philosophy
 Knowledge cannot be taught; it is learned.
 Be excited. That is the best way to learn. I
cannot teach everything in class. Develop
an inquiring mind, ask questions, and go
beyond what is required.
 I don’t believe in strict grading. But… there
has to be a way of rewarding performance.
Course Outline
 Introduction (FAQs about SE)
 Software Processes
 Requirements
 Design
 Verification and Validation
 Project Management
 Other Topics
Software Processes
 Activities concern about Software Development
 Software Specification
 Design
 Implementation
 Validation (what customer wants, Testing, Quality
Assurance)
 Software Evolution (must evolve to meeting changing
needs of customers, maintenance)
 Process Models
 Waterfall model, evolutionary development (concurrent
activities), component-based software engineering
(design with reuse)
 CASE tools for aiding the evolving of processes
Requirements
 Detailed Descriptions of what the
system should do.
 Functional (service provided) and
non-functional requirements
(constraints)
 User Requirements (external behavior
of the system)
 System Requirements (starting points
for system design)
Design
 Architecture Design
 Subsystem identifications
 Subsystem Control and Communication
 Output the Software Architecture
 Object-oriented Design
 Design as a set of interacting objects
 User interface Design
 Interface code constitutes the major part of
system
 Judging the system from UI instead of
Functionality
 External Behaviors of the system
Verification and Validation
 Validation: Building the right product ?
 Software meets the user’s expectations
 Verification: Building the product right ?
 Software conforms to the specification
 Software Testing
 Formal Methods
Project Management
 Project Scheduling
 Software Metrics
 Cost Estimation
 Quality Management
 Risk Management
 Change Management
Other Issues
 Software Outsourcing
 Open source Software Engineering
 Building for Trustworthy
 Component-based development
Term Project

 Propose a software system to be


developed (either from scratch or the
existing GPL projects)
 Evaluate the project from the
analysis, design, and various
documents among the processes

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy