Introduction to Software Development Process: Iterative Model and Use Cases, Slides of Introduction to Software Engineering

An introduction to the software development process, focusing on the iterative model and use cases. The iterative model is a method for organizing activities in software development, which involves successive enlargement and refinement of the application. The advantages of iterative development, the iterative development cycle, and the use of use cases in planning and elaboration. It also covers the major steps in delivering an application, including planning and elaboration, building, and deploying.

Typology: Slides

2011/2012

Uploaded on 03/11/2012

steven005
steven005 🇺🇸

4.3

(3)

22 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
INTRODUCTION TO
DEVELOPMENT PROCESS
INTRODUCTION
A PROCESS PROVIDES A FOUNDATION
OF MANAGEABLE, REPEATABLE &
SUCCESSFUL PROJECT.
METHOD TO ORGANISE ACTIVITIES
HOW OOAD ARE ORGANISED IN
THESE ACTIVITIES
RECOMMENDED PROCESS
& MODEL
DEVELOPER ACQUIRE DESIGN SKILL
THAN FOLLOW OFFICIAL PROCESS
SOME RECOMMENDED PROCESSES
ITERATIVE MODEL
INCREMENTAL MODEL
USE CASE DRIVEN MODEL
OFFER A STARTING POINT.
WHAT IS NOT TAUGHT
EMPHASIS ON BASIC ACTIVITIES &
NOT ADDRESSING BROADER ISSUES
ESSENTIAL PROCESS STEPS LIKE
PLANNING, PROJECT MANAGEMENT,
DOCUMENTATION WILL NOT BE
DISCUSSED IN DETAILS
MORE EMPHASIS ON APPLYING
SKILLS OF OOAD.
UML & DEV. PROCESS
UML IS STANDARD GRAPHICAL
NOTATION AND NOT COMMITED TO
ANY STANDARD PROCESS
AN APPROPRIATE PROCESS DEPENDS
ON STAFF SKILLS, NATURE OF
PROBLEM & TOOLS.
MAJOR STEPS
MAIN STEPS IN DELIVERING AN
APPLICATION
PLAN & ELABORATE
BLUID
DEPLOY.
pf3

Partial preview of the text

Download Introduction to Software Development Process: Iterative Model and Use Cases and more Slides Introduction to Software Engineering in PDF only on Docsity!

INTRODUCTION TO

DEVELOPMENT PROCESS

INTRODUCTION

Š A PROCESS PROVIDES A FOUNDATION

OF MANAGEABLE, REPEATABLE &

SUCCESSFUL PROJECT.

Š METHOD TO ORGANISE ACTIVITIES

Š HOW OOAD ARE ORGANISED IN

THESE ACTIVITIES

RECOMMENDED PROCESS

& MODEL

Š DEVELOPER ACQUIRE DESIGN SKILL

THAN FOLLOW OFFICIAL PROCESS

Š SOME RECOMMENDED PROCESSES

„ ITERATIVE MODEL „ INCREMENTAL MODEL „ USE CASE DRIVEN MODEL

Š OFFER A STARTING POINT.

WHAT IS NOT TAUGHT

Š EMPHASIS ON BASIC ACTIVITIES &

NOT ADDRESSING BROADER ISSUES

Š ESSENTIAL PROCESS STEPS LIKE

PLANNING, PROJECT MANAGEMENT,

DOCUMENTATION WILL NOT BE

DISCUSSED IN DETAILS

Š MORE EMPHASIS ON APPLYING

SKILLS OF OOAD.

UML & DEV. PROCESS

Š UML IS STANDARD GRAPHICAL

NOTATION AND NOT COMMITED TO

ANY STANDARD PROCESS

Š AN APPROPRIATE PROCESS DEPENDS

ON STAFF SKILLS, NATURE OF

PROBLEM & TOOLS.

MAJOR STEPS

Š MAIN STEPS IN DELIVERING AN

APPLICATION

„ PLAN & ELABORATE „ BLUID „ DEPLOY.

ITERATIVE DEVELOPMENT

Š SUCCESSIVE ENLARGEMENT &

REFINEMENT.

Š GROWS BY ADDING NEW FUNCTIONS

Š ADVANTAGES

„ COMPLEXITY IS NOT OVERWHELMING. „ FASTER FEEDBACK & IMPLEMENTATION.

ITERATIVE DEV. CYCLE

Analyze Design Construct

Develop. Cycle

Develop. Cycle2 ….

Refine Plan Test

FIXING A TIME

Š DEVELOPMENT CYCLE IS FRAMED

WITHIN A TIME BOX

Š RIGID TIME

Š GENERALLY A RANGE OF 2 WEEKS TO

2 MONTHS.

Š RESPONSIBLE DEVELOPMENT TEAM

USE CASES

Š USE CASE IS A NARRATIVE DESCRIPTION OF THE PROCESS Š A PROJECT COULD HAVE ONE OR SEVERAL USE CASES. Š EACH DEVELOPMENT CYCLE COULD HANDLE ONE OR MORE USE CASE. Š NON EVIDENT USE CASES. Š USE CASES SHOULD BE RANKED.

PLAN & ELABORATE

PHASE

Š DEFINE DRAFT PLAN

Š CREATE PRELIMINARY

Š INVESTIGATION REPORT

Š DEFINE REQUIREMENTS & RISKS

Š RECORD TERMS IN GLOSSARY.

Š IMPLEMENT PROTOTYPE

Š DEFINE USE CASES – HIGH LEVEL

Š DEFINE DRAFT CONCEPTUAL MODEL

Š DEFINE DRAFT ARCHITECTURE

Š REFINE PLAN