Download Ivan Marsic-Introduction to Software Engineering-Lecture 01 Slides-Computer Science and more Slides Introduction to Software Engineering in PDF only on Docsity!
INTRODUCTION TO
SOFTWARE ENG.
COURSE OBJECTIVES
PRACTICES IN SOFTWARE ENG. WITH
EMPHASIS ON DEVELOPMENT
PROCESS.
SOFTWARE LIFE CYCLE, PROJECT
MANAGEMENT, ANALYSIS, DESIGN,
TESTING, CASE TOOLS….
Overview
PROFESSORS: MANISH PARASHAR, IVAN MARSIC
WEB SITE:
www.ece.rutgers.edu/~parashar/Classes/ece452/
TA’s: Jasvinder Singh, Praveen Gopalakrishnan
TEXTS:
Primary: Applying UML and Patterns, Craig Larman Supplemental: See web page.
Project
Project-based course (>75%)
NOT A COURSE TO LEARN LANGUAGES - IT IS A
PREREQUISITE
For your project you will design, implement
and deploy and online service
You will work in teams of 5 member Emphasis will be on design, planning, management Deliverables every 3 – 4 weeks A team presentation is required with each deliverable
OO ANALYSIS & DESIGN
UML
WHY NEED DESIGN & ANALYSIS
Creation of well designed , robust,
manageable software
Not good enough to know an object
oriented language – JAVA, C++, SmallTalk.
UML – Unified Modeling Language
Graphic notation for modeling systems.
STEPS IN SOFTWARE DEV.
REQUIREMENT SPECIFICATIONS
ANALYSIS
DESIGN
CONSTRUCTION – CODE
TESTING
IMPLEMENTATION
ANALYSIS & DESIGN
REQUIREMENT SPECIFICATION –
Is the description of problem.
ANALYSIS –
Investigation of the problem and not the
solution.
DESIGN
Is finding a logical solution which fills the
requirements.
OO ANALYSIS & DESIGN
OO ANALYSIS –
Consider the problem domain in
perspective of objects(things, concepts,
entities)
OO DESIGN
Defining the objects in terms of attributes
& methods.
Analysis Design Construction
Investigation of problem Logical Solution^ Code
Results in concepts Books, Library & Users.
Library Management System Book object has Attributes as name & methods as getISBNno()
Responsibilities Design Class diagram.
Conceptual
model
Domain
analysis
Employees
roles
Requirement Use Cases
Analysis
Business
processes
Associated
Documents
OO Analysis &
Design
Business
Analogy
EXAMPLE OF OOAD
PROBLEM DEFINITION
A dice game where two players play two
die. If the total is seven, then the player
wins.
OO ANALYSIS
Investigation the problem – understanding
the problem and its external environment.
Expressed in “use case” – narrative
description of the problem.
USE CASE
Name of use case – Play a Game
External Environment (also called
Actors) - Players
Description – This use case begins
when the players pick up and roll the
dice. If the dice total seven, they win
otherwise they lose.