Software Design and Development (A guide) is help you how to managed IT Project. Especially for Design and Develop software project.

Day 2 - Software DesignApproving the design - objective  To ensure that the software design activity is sufficiently thorough whether the project is ready to proceed... Day 2 - Softwar

Trang 1

Software Design and Development

( A guide )

Trang 2

Software Design & Development

Day 1 - Definitions and Overview

Day 2 - Software Design

Software Development

Trang 3

Day 1 - Definitions & Overview

Definitions

 What is software ?

 What is software design ?

Trang 4

Definitions

 Software development life-cycle

 Software development process

 Software development models

Trang 5

What is software ?

Software is computer programs that provide instructions for individual machines to function and for

Trang 6

What is software design ?

Consisting of 3 parts :

 Conceptual design

 Logical design

Trang 7

Software design - 3 parts

Conceptual

Logical

Physical Scenarios Services &

Objects, UI Components,

Trang 8

Part 1 of Software Design

Conceptual

Scenarios

• Identify business needs

• Understand users’ requirements

• Generate scenarios that reflect

complete & accurate requirements

by involving the customers, users and other stakeholders

Trang 9

Logical

Services &

Objects, UI,

logical DB

• Organize the solution

• Formulate an abstract model

• Take the scenarios from conceptual

and produces objects & services,

Trang 10

Physical

Components,

UI &

Physical DB

• Apply real-world technology

constraints incl implementation

& performance considerations,

to the outputs of Logical design by specifying the details of the solution

• Take the outputs of Logical Design

Trang 11

What is software development ?

Software development is a process of developing a software system from

requirements ie System, Information

Trang 12

What is software development ?

Software development comprises many individual tasks and activities that are performed in a fairly standard manner,

Trang 13

• Regulatory

- legal

- government

Trang 14

What is a CASE tool ?

S oftware E ngineering

A software engineering process which

provides a disciplined approach to

Trang 15

Why do you use a CASE tool ?

Its goal is to ensure the production of

high-quality software, meeting the needs

Trang 16

Requirement Mission analysis

stage

Concept Dev Stage

Initiation Phase

Development Phase

System analysis

stage

System design stage

Construct

& acq.

stage

User accept stage

Software development life-cycle

Trang 17

Software development life-cycle

Installation, Operation

& maintenance Design, Development,

Production & testing

Trang 18

Users / Developers

Software development process

Trang 19

Software development models

Trang 20

Software development models

Planning &Analysis Design

Assessment Implementation

Trang 21

Planning & Mgmt SOW Architecture Plans

Software req Architecture Func Spec Review,sign

Life cycle phases Input Output Controls

Pre Design Func spec Detailed doc Review,sign Detailed Pre Design Detailed spec Review,sign Code & test Detailed spec Final spec Walk-thru

Trang 22

Node A

Node B Node C

Node D

Node E Node F

Software Life Cycle

Trang 23

Node A

Node B Node C

Node D

Node E

has been identified and an initial

set of software requirements has been prepared

Trang 24

Node A

Node B Node C

Node D

Node E Node F

per-formed prior to node B is a DRR where commitments are made.

S/W dev is ready

to begin

Trang 25

agreements have been obtained

Trang 26

Node A

Node B Node C

Node D

Node E Node F

has been fully reviewed and accepted The component and software test dev.

activities are ready

to begin

Trang 27

have been unit tested

Trang 28

and all have been tested

Trang 29

Trang 30

Node A

Node B Node C

Node D

Node E Node F

is ready for full deployment or general customer availability (GCA)

Trang 31

Software Design & Development

Day 1 - Definitions and Overview

Trang 32

Software Design

Trang 33

Software design is the activity which produces details about software being

developed Its objective is to fully characterize how the software will

function in its operational

Trang 34

The design activity includes an

analysis of the component requirements plus create, lay out and

describe, review, improve, and approve the design

Trang 35

Design includes an evaluation of the adequacy of the detailed technical requirements, an evaluation of the design choices, and a verification that the design satisfies all requirements

Trang 36

Software Design Inputs

 Software structure diagram & the

Trang 37

Analyze requirements Create design

Analyze and review

Correct and improve

Reused Designs

D B

Trang 38

Day 2 - Software Design Analyzing the requirements

 To ensure that requirement is

complete

so that design decision is not left to the developer

 Assurance that all requirements will

Trang 39

What is Prototyping ?

 Constructing a simplified version of a

portion of the product, possibly a

simulation, to be able to evaluate

various choices and to answer the

Trang 40

Prototyping - its benefits

 Valuable task to address & resolve

various requirements & design issues

prototyping

tasks begun during planning or new

Trang 41

Prototyping - its benefits

 Multiple prototyping tasks may be

conducted to simultaneously to address various alternative design issues

Trang 42

Creating the design

 By a single person, however various

help are encouraged appropriately in order to obtain good & solid design

Trang 43

Creating the design - reused design

 Reusing previously created & proven

designs is strongly encouraged; it is

frequently beneficial

Trang 44

Reviewing the design - objective

 The objective is to increase the

likelihood that the design is the best

possible, and of high caliber

Trang 45

Reviewing the design - by

 A group of people representing

various software & development skills

possessing special expertise may be

Trang 46

Reviewing the design - how

 In a group setting to the extent

possible

pre-sents & walks thru’ details as needed

 Designer responsible for correctness,

Trang 47

Reviewing the design - why

 Will the product satisfy its intended

objectives ?

 Does the design satisfy all of its

Trang 48

Reviewing the design - why

 Has expensive, unneeded functionality

or capability been added to the design ?

 Could key software requirements be

expanded if requested ?

Trang 49

Reviewing the design - finally

 Scrutinize the list of planned activities

and test activities to ascertain whether any changes or additions are needed

Trang 50

Correcting & improving the design

 Reworked to correct the problems

uncovered, & to implement the

improvements recommended

Trang 51

Approving the design - objective

 To ensure that the software design

activity is sufficiently thorough

whether the project is ready to proceed

Trang 52

Approving the design

 Involves a check to make sure that all

of the outputs are present, and a review

of the revised project activity list to

determine whether some replanning

Trang 53

Approving the design

need for changing the project plan

 The effort spent in revising the project

plan is charged to project structuring

Trang 54

Design Outputs

 The primary output for each design

activity is the design diagram or

equivalent articulation of the design

D

Trang 55

Design Outputs

as inputs to lower level design activities till they are ready for distribution to

the appropriate programming

D

Trang 56

Design Outputs

 After the design has been approved,

the design artifacts ( usually the design diagram, and possibly an

implementation specification ) are

D

Trang 57

Analyze requirements Create design

Analyze and review

Correct and improve

Reused Designs

D B

SUMMARY

Trang 58

Trang 59

Day 2 - Software Development

Software development is the activity which creates software and confirms

that the software satisfies its

requirements

Trang 60

Design the components

Code the components Components Test the

Develop component Tests

Reused components design

E D

Reused components

Component

Trang 61

Design the software tests

Code the software tests

Test the software tests Prepare

Reused test designs

F D

Reused software tests

Trang 62

Software Development Inputs

 Design diagram ( or equivalent )

matrix

 Information about the appropriate

technologies

D

Trang 63

Designing the component - micro

 The software design needs to be

further decomposed to show the details about the program flow, and to handle all of the abnormal processing

Trang 64

Designing the component - micro

another design activity @ micro level

 The standard design activity process

should be used, as modified, to

Trang 65

Designing the component - includes

 Selection of algorithms

 Provides all the detail information

Trang 66

Designing the component - test unit

 At this juncture, the requirements for

developing the unit test are known, & the unit test development task is

spawned

Trang 67

Coding the component - reuse

 Reused component design is

encouraged as it increases productivity, reduces development time, and

provides a higher quality

Trang 68

Coding the component

another means for attaining greater

productivity, reduced development

time, and increased quality as well

Trang 69

Coding the component - language

 Which language will enable the

program to achieve its best

performance ?

Trang 70

 Which language is the most

understandable to all who will have to read the source ?

Trang 71

 Which language will facilitate

achieving the greatest productivity ?

The choice of programming language

Trang 72

Testing the component

 An informal operability test is

conducted to confirm that the program will execute

Trang 73

Inspecting the code

 A formal inspection of the code is

made

by a team of skilled code reviewers

Trang 74

 Code inspections search for hidden

Trang 75

 Addresses some key issues :

- does the codes do what the design indicates it should ?

- does the codes satisfy the

Trang 76

- does the code impact any other

components in an unexpected way ?

- how readily understandable is the

Trang 77

- does the codes adhere to all

applicable standards ?

- How good is the code ?

Trang 78

A list of standard code inspection issues

as a guide for future code inspections

The list should identify the specific things

Trang 79

Correcting and improving the

component

 This task reworks the software to

correct the problems uncovered, & to implement the improvements

Trang 80

Preparing the Component Test

 This activity may be performed

concurrently with the component

coding activity, and can begin when the component design is completed and

Trang 81

Preparing the Component Test

evaluates the adequacy of the detailed

component testing requirements, and

verifies that the test design satisfies all its

Trang 82

Testing the component

 Unit test using the standard testing

activity

results for each test have been obtained

Trang 83

Approving the component

 To ensure that the component is

operational and fully tested

made

Trang 84

Approving the component

 A strategy for not approving the

component until there is a good

indication that as many defects as possible have been discovered and

Trang 85

Component Development Outputs

 Primary output for each programming

activity is the software

it is libraried and comes under change

Trang 86

Design the components

Code the components Components Test the

Develop component Tests

Reused components designs

E D

Reused components

Component

SUMMARY

Trang 87

Users / Developers

Day 2 - Software Design & Development

Trang 88

Software Design and Development

( END !! )

Tiêu đề	Software Design and Development (A Guide) Is Help You How To Managed IT Project. Especially For Design And Develop Software Project.
Trường học	Standard University
Chuyên ngành	Information Technology
Thể loại	Hướng dẫn
Năm xuất bản	2023
Thành phố	City Name

Định dạng
Số trang	88
Dung lượng	351,5 KB