ANALYSIS

REQUIREMENT

ANALYSIS

DESIGN

IMPLEMENTATIONTEST

Introduction - 1

Analyze the requirements Captured. Refine and Structure them. Achieve more precise understanding of the

requirements. Achieve description of the requirements

that is easy to maintain that helps us give structure to the whole system.

Introduction - 2

To communicate with customer efficiently Use cases must be kept as independent to

each other as possible. Use case must be described using the

language of the customer. Use case must be structured to form a

complete and intuitive specification of functionality.

Introduction - 3

The above considerations leads to unresolved issues regarding the system requirements. The main purpose of the Analysis is to resolve them by analyzing the requirements more in depth.The language of the developers is used to describe the system.Internal View of the System.

Characteristics - 1

Described using language of the developers. Internal View of the System. Developed for developers to understand the system. Should not contain inconsistencies and redundancies. Outlines how to realize functionality of the system. Defines use-case realizations each one representing the

analysis of a use case from the usecase model Provides input for shaping up the architecture of the

system as a whole.

Characteristics – 2

Language used in Analysis is called the Analysis Model.

Provides a structure that focuses on maintenance.

Feeds input to the Design and Implementation Phase.

Makes abstractions and avoids solving problems

Purpose of Analysis

Yields a more precise specification of the requirements.

Described using the Language of the developers. Structure the requirements in a way that facilitates

understanding them, preparing them and changing them and in general maintaining them.

First Cut at Design Model and is an essential input when the system is shaped in design and implementation.

Role of Analysis in S/W Life Cycle

The Analysis Model

* *

1

Analysis Model

Analysis Package

AnalysisClasses

Use CaseRealization Analysis

**

**

Analysis System

Artifact - The Analysis Model

Analysis Classes Boundary Classes Control Classes Entity Classes

Use Case Realization Analysis Class Diagram Interaction Diagram Flow of Events Special Requirements

Analysis Packages Service Package

Architectural Description.

Artifact – Analysis Classes

Represents an abstraction of one or several classes. The abstraction has the following characteristics. Focuses on handling functional requirement. Analysis class defines behavior by responsibilities on a

higher and less formal level. Defines Attributes at a higher Level. Are involved in relationships. Classes fit into one of three basic stereotypes

Boundary Class, Control Class and Entity Class

ANALYSIS CLASSES

ResponsibilitiesAttributes

RelationshipsSpecial requirements

Analysis Class

Boundary Class Control Class Entity Class

Boundary Classes

Used to model interaction between system and actor. Represent abstraction of windows , forms, panes,

communication Interface, sensors, terminals and API. Each boundary class relate at least one actor and visa versa

Payment HandlerBuyer

Entity Classes Used to model classes that is long lived and often

persistent. Entity classes model information and associated behavior of some Phenomena or Concepts such as real

time object, individual or real life event.

Payment Handler UIBuyer

Invoice

Browses

Payment Scheduler

Control Classes

Represent coordination, sequencing, transactions and control of other objects and are often used to encapsulate control related to a specific usecase.

Payment Handler UIBuyer

Invoice

Browses