analyzing a system and specifying the requirements

25
Analyzing a system and specifying the requirements

Upload: vikramgopale2

Post on 14-Jan-2017

37 views

Category:

Software


0 download

TRANSCRIPT

Page 1: Analyzing a system and specifying the requirements

Analyzing a system and specifying the requirements

Page 2: Analyzing a system and specifying the requirements

Analyzing a system and specifying the requirements:-

frequent communication with users .

Requirements analysis is a team effort.

demands a combination of hardware software

and human factors engineering expertise as well

as skills in dealing with people.

Page 3: Analyzing a system and specifying the requirements

There are two types:-

•Structured approach

•Object oriented approach

Page 4: Analyzing a system and specifying the requirements

STRUCTURED APPROACH :-

• Requirements

• Design

• Implementation

• Verification

• Maintenance

Page 5: Analyzing a system and specifying the requirements

REQUIREMENTS

DESIGN

IMPLEMENTATION

Verification

Maintenance

Page 6: Analyzing a system and specifying the requirements

Requirements :-bridging the gap between system requirements engineering and software design.Provides software designer with a model of : -• System information

• Function• BehaviorModel can be translated to data, architectural, and component-level designs.Expect to do a little bit of design during analysis and a little bit of analysis during design.

Page 7: Analyzing a system and specifying the requirements

Requirements :-

Types of Requirements - 1

Functional requirements:input/outputprocessing.error handling.

Non-functional requirements:Physical environment (equipment locations, multiple sites, etc.).Interfaces (data medium etc.).User & human factors (who are the users, their skill level etc.).

Page 8: Analyzing a system and specifying the requirements

Requirements :-

Types of Requirements - 2

Non-functional requirements (continued):Performance (how well is system functioning).Documentation.Data (qualitative stuff).Resources (finding, physical space).Security (backup, firewall).Quality assurance (max. down time, MTBF, etc.).

Page 9: Analyzing a system and specifying the requirements

Design:-

Plan

Architectural design

Logical design

Physical design

Page 10: Analyzing a system and specifying the requirements

Implementation :- Implementation is the realization of an application, or execution of :-

plan

model

Design

specification

standard

algorithm

Page 11: Analyzing a system and specifying the requirements

Verification :-

System Verifications a set of actions used to check

the correctness of any element

Dynamic verification

Static verification

There are two fundamental approaches to verification: -

Page 12: Analyzing a system and specifying the requirements

Maintenance :-

Service provider expertise

Emergency response times

Update new features

Page 13: Analyzing a system and specifying the requirements

OBJECT ORIENTED APPROACH :-

principles of object oriented (OO) approach is that

of abstraction, not of data structures and processes

separately but both together.

An object is a set of data structures and the methods

or operations needed to access those structures.

Page 14: Analyzing a system and specifying the requirements

The key ideas of the object oriented Approach are :-

Objects

Encapsulation

Class

Inheritance

Instances and Instantiation

Methods and Messages

Page 15: Analyzing a system and specifying the requirements

Objects :- In the class-based object-oriented "object" refers to a particular instance of a class .

where the object can be a combination of variables, functions, and data structures.

In relational database management, an object can be a table or column, or an association between data and a database entity.

The main purpose of object is reuse the code.

Page 16: Analyzing a system and specifying the requirements

Encapsulation :-

Encapsulation is manipulate the data, and

that keeps both safe from outside interference

and misuse.

Data encapsulation led to the important

OOP concept of data hiding.

Page 17: Analyzing a system and specifying the requirements

Encapsulation (continue) :-Example :-

class Account{private double accountBalance;

public withdraw();public deposit();public determineBalance();

} //class Account

Account balancedeposit

withdraw

determine Balance

Message

Message

Message

Page 18: Analyzing a system and specifying the requirements

Class :-

A class is a blueprint of prototype.

Class is the implementation of an abstract data type

and so encapsulate both data and operation.

Object is run time instance of class.

Classes just sit there ,Objects do the real work.

Memory is allocated for Objects not for classes.

Page 19: Analyzing a system and specifying the requirements

programming, computer programs are designed by making them out of objects that interact with one another.

here is significant diversity in object-oriented programming. most popular languages are class-based, meaning that objects are instances of classes which typically also determines their type.

Inheritance :-

Page 20: Analyzing a system and specifying the requirements

Instances and Instantiation :-

In programming, instantiation is the creation of a real instance or particular realization of an abstraction or template such as a class of objects or a computer process.

Page 21: Analyzing a system and specifying the requirements

Instance (computer science) :-In object-oriented programming (OOP), an instance is a concrete occurrence of any object, existing usually during the runtime of a computer program.

Formally, "instance" is synonymous with "object" as they are each a particular value (realization), and these may be called an instance object; "instance" emphasizes the distinct identity of the object. The creation of an instance is called instantiation.

Page 22: Analyzing a system and specifying the requirements

Methods and Messages :-

One of the most important capabilities that a method provides is method overriding.

Method in java programming sets the behavior of class object.

For example:- area .

Page 23: Analyzing a system and specifying the requirements

Methods and Messages (continue):-

Methods also provide the interface that other

classes use to access and modify the data

properties of an object.(encapsulation)

Encapsulation and overriding are the two

primary distinguishing features between

methods and procedure calls.

Page 24: Analyzing a system and specifying the requirements

Methods and Messages (continue):-

Class

1.Fields2.Constructors3.methods

class Account {int accountNumber;int accountBalance;

Public Account(double account) {accountBalance=Amount;}Public int getAccountNumber() {return accountNumber; //message}Public void deposit (double account) {accountBalance=Amount;}Public int getBalancer() {return accountBalance; //message}}

Page 25: Analyzing a system and specifying the requirements

Thank You…