Download Free Templates http://bigtheme.net/ Websites Templates

 

 

APPENDIX C

Total Design procedure

Procedure is divided into 2 sub procedures

 

a)   Architecture Design Procedure

Purpose

The objectives of the design process are to develop a coherent, well-organized representation of the software product that meets the customer’s requirements and satisfies the predefined quality criteria. The process comprises the architectural design that will be followed by the detailed design in the next procedure. Architectural design provides the infrastructure for this detailed design. The importance of software design can be defined with the phrase,  ‘quality design is the place where quality is fostered in software engineering’. It is an iterative process through which requirements are translated into a ‘blueprint’ for constructing the software.

Definitions

No

Term

Definition

1

Software Architectural

Software architecture is a representation of a software system, as well as the process and discipline for effectively implementing the design(s) for such a system. It is a representation because it is used to convey the information content of the related elements comprising a system, the relationships among those elements, and the rules governing those relationships.

Entry Criteria (OR)

No

Criteria

Exit Criteria Of

1

Requirements Baselined

RITS_PD_Requirements_Validation_Procedure

2

Rework From Detailed Design

RITS_PD_Detailed_Design_Procedure

3

Rework From Integration Test

RITS_PD_Integration_Test_Preparation_Procedure

Inputs

No

Input

Coming from/Output Of

1

Approved Software Development Plan

RITS_PD_Planning_Procedure

2

Baselined SRS and RTM

RITS_PD_Requirements_Validation_Procedure

3

Reused Components Specifications

Reuse library (if exists).

Activities

No

Activity

Responsible

Input

Output

Temp/Form

1

Determine the system overview and context.

Des

Baselined SRS and Software Development Plan

System Overview and Context

RITS_PE_ Architectural_ Design_ Template

2

Determine the high level system architecture.

Des

Baselined SRS and Software Development Plan

High Level System Architecture

RITS_PE_ Architectural_ Design_ Template

3

Perform architectural design by transforming the software requirements and system architecture into candidates high-level  design architecturals. This design contains components.

Des

High Level System Architecture

Candidates High-Level Design Architecture

RITS_PE_ Architectural_ Design_ Template

4

Determine the attributes of each component such as description, type, purpose, function and dependencies.

Des

Candidates High-Level Design Architecture

Candidates Components

 

5

Evaluate candidates’ high-level design architectural and select the suitable one.

Des

Candidates High-Level Design Architectural

Selected High-Level Design Architecture

RITS_PE_ Architectural_ Design_ Template

6

Check and review the reusable components library and select the reused components.

Des

Reused Components Specifications

Selected Reused Components

RITS_PE_ Architectural_ Design_ Template

7

Identify design parameters such as data, relationships, constrains, and all the internal interfaces (among components).

Des

Selected High-Level Design Architectural

High-Level Design Architecture

RITS_PE_ Architectural_ Design_ Template

8

Update the RTM.

Des

Baselined RTM

Updated RTM

RITS_PD_ Requirements_ Management_ Form

9

Conduct peer review as per the peer review process and plan.

PR

As per the process

As per the process

As per the process

10

Conduct QA audit as per the QA process and plan.

QAR

As per the process

As per the process

As per the process

11

Conduct CM activities as per the CM process and plan.

CC

As per the process

As per the process

As per the process

12

Collect measurements as per the measurement plan.

MC

As per the process

As per the process

As per the process

13

Monitor the progress as per the PM process and plan.

PM

As per the process

As per the process

As per the process

14

Approve the outputs of the procedure.

PM

High-Level Design Architecture and Updated RTM

Approved High-Level Design Architecture

 

Outputs

No

Output

Going To/Input Of

1

Approved High-Level Design Architectural

RITS_PD_Detailed_Design_Procedure

RITS_PD_Integration_Test_Execution_Procedure

RITS_PD_Implementation_Procedure

2

Updated RTM

RITS_PD_Implementation_Procedure

RITS_PD_Integration_Test_Execution_Procedure

Exit Criteria

No

Criteria

Entry Criteria Of

1

High-Level Design Architecture Approval

RITS_PD_Detailed_Design_Procedure RITS_PD_Integration_Test_Execution_Procedure

Metrics

These measures can be useful to support the process enactment, or future enactments:

·         Actual versus planned time and effort

Subjects for Review

·         High-Level Design Architecture

·         Requirements Traceability Matrix (RTM)

Records

·         None

Configurable Items

·         High-Level Design Architecture

·         Requirements Traceability Matrix (RTM) (Not mandatory)

 

 

 

 

Purpose

The objectives of the design process are to develop a coherent, well-organized representation of the software product that meets the customer’s requirements and satisfies the predefined quality criteria. The process comprises of architectural design and detailed design. Architectural design and detailed design are usually carried out in sequence because detailed design is largely dependent on the architectural design. The importance of software design can be defined as ‘quality design is the place where quality is fostered in software engineering’. It is an iterative process through which requirements are translated into a ‘blueprint’ for constructing the software.

Definitions

·         None

Entry Criteria

No

Criteria

Exit Criteria Of

1

High-Level Design Architecture Approval

RITS_PD_Architecture_Design_Procedure

Inputs

No

Input

Coming from/Output Of

1

Approved High-Level Design Architecture

RITS_PD_Architecture_Design_Procedure

2

Updated RTM

RITS_PD_Requirements_Validation_Procedure

3

Baselined SRS

RITS_PD_Requirements_Validation_Procedure

4

Reused Components Specifications

Reuse library (if exist)

Activities

No

Activity

Responsible

Input

Output

Temp/Form

1

Determine the components’ overview and context.

Des

All Procedure Inputs

Components Overview and Context

RITS_PE_ Detailed_ Design_ Template

2

Determine the required standards and conventions.

Des

Baselined SRS and Software Development Plan

Standards and Conventions

RITS_PE_ Detailed_ Design_ Template

3

Design the detailed attributes of each component such as description, type, purpose, function and dependencies.

Des

High-Level Design Architecture

Components Design

RITS_PE_ Detailed_ Design_ Template

4

Check and review the reusable components library and select the reused components.

Des

Reused Components Specifications

Selected Reused Components

RITS_PE_ Detailed_ Design_ Template

5

Identify design parameters such as data, relationships, constrains, and all the internal interfaces (among components).

Des

Selected High-Level Design Architectural

High-Level Design Architecture

RITS_PE_ Detailed_ Design_ Template

6

Update and modify the High-Level Design Architectural

Des

High-Level Design Architecture

Updated High-Level Design Architectural

RITS_PE_ Architectural_ Design_ Template

7

Update to RTM.

Des

Baselined RTM

Updated RTM

RITS_PD_ Requirements_ Management_ Form

8

Conduct peer review as per the peer review process and plan.

PR

As per the process

As per the process

As per the process

9

Conduct QA audit as per the QA process and plan.

QAR

As per the process

As per the process

As per the process

10

Conduct functional configuration audit according to the RITS_CM_Functional_ Configuration_Audit_Procedure.

As Per The Process

As Per The Process

As Per The Process

As Per The Process

11

Conduct physical configuration audit according to the RITS_CM_Physical_ Configuration_Audit_Procedure.

As Per The Process

As Per The Process

As Per The Process

As Per The Process

12

Baseline all planning outputs according to the RITS_CM_Baselining_ Procedure.

As Per The Process

As Per The Process

As Per The Process

As Per The Process

13

Collect measurements as per the measurement plan.

MC

As per the process

As per the process

As per the process

14

Monitor the progress as per the PM process and plan.

PM

As per the process

As per the process

As per the process

15

Approve the outputs of the procedure.

PM

Baselined Design

Approved Baselined Design

 

Outputs

No

Output

Going To/Input Of

1

Baselined High-Level Design Architecture

RITS_PD_Implementation_Procedure

RITS_PD_Unit_Test_Execution_Procedure

2

Baselined Detailed Design

RITS_PD_Implementation_Procedure

RITS_PD_Unit_Test_Execution_Procedure

3

Baselined RTM

RITS_PD_Implementation_Procedure

RITS_PD_Unit_Test_Execution_Procedure

Exit Criteria (OR)

No

Criteria

Entry Criteria Of

1

Design Baselined

RITS_PD_Implementation_Procedure

RITS_PD_Unit_Test_Execution_Procedure

2

Architecture Design Rework

RITS_PD_Architecture_Design_Procedure

3

Development Planning Rework

RITS_PD_Development_Planning_Procedure

Metrics

These measures can be useful to support the process enactment, or future enactments:

·         Actual versus planned time and effort

Subjects for Review

·         High-Level Design Architecture

·         Detailed Design

·         Requirements Traceability Matrix (RTM)

Records

·         None

Configurable Items

·         High-Level Design Architecture

·         Detailed Design

·         Requirements Traceability Matrix (RTM) (Not mandatory)

 

 

Quality Management System (QMS)