Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management...

MODELMODEL TESTin the small

TESTin the small

GENERALIZEGENERALIZE PROGRAMPROCESSPROGRAMPROCESS

allocated maintenance

changes

management documentsinitial requirementproject infrastructureproject fundingproject charter

potential roles during this phase:

project managerproject manager

software applicationdocumentationrequirement allocation matrixmodels, source codemanagement documents

team leaderteam leader

software conf. managersoftware conf. manager

test managertest manager

architectural modelerarchitectural modeler

domain programmerdomain programmer

subject matter expertsubject matter expert

quality assurance quality assurance engineerengineerdomain modelerdomain modeler

mentormentor

infrastructure engineerinfrastructure engineer

technical writertechnical writer

component engineercomponent engineer

reuse engineerreuse engineer

test engineertest engineer

proof-of-concept engineerproof-of-concept engineer

from maintain & support phaseCONSTRUCT PHASE

The main goal of the construct phase is to build working software that is ready to be tested and delivered to its user community.

MODEL MODEL

ARCHITECTU-RAL

MODELING

ARCHITECTU-RAL

MODELING

requirement documentationmodeling standards

TECHNICALMODELING

TECHNICALMODELING

HUMAN INTERACTION

DOMAINMODELING

HUMAN INTERACTION

DOMAINMODELING

PROBLEMDOMAIN

MODELING

PROBLEMDOMAIN

MODELING

MANAGEMETRICSMANAGEMETRICS

TASKMODELING

TASKMODELING

models (diagrams, docs)test planrequirement alloc. matrix

The developers first need to understand what the are supposed to build. This “software analysis and design” process should be performed iteratively, because of developers do not need to do all of the analysis first time, then do all of the design and then all of the coding.

PROGRAM PROCESS PROGRAM PROCESS

UNDERSTANDMODELS

UNDERSTANDMODELS

modelsproject infrastructure

MAKESOURCE

CODE

MAKESOURCE

CODE

PREPAREPROJECT

INTEGRATIONPLAN

PREPAREPROJECT

INTEGRATIONPLAN

PREPARECODE FOR

INSPECTIONS

PREPARECODE FOR

INSPECTIONS

INTEGRATEAND

PACKAGE

INTEGRATEAND

PACKAGE

SYNCHRONIZESOURCE CODE

WITHMODELS

SYNCHRONIZESOURCE CODE

WITHMODELS

packaged applicationsource codesoftware components

OPTIMIZE CODE

OPTIMIZE CODE

BUILDSOFTWARE

APPLICATION

BUILDSOFTWARE

APPLICATION

REUSEEXISTING

CODE ANDCOMPONENTS

REUSEEXISTING

CODE ANDCOMPONENTS

DOCUMENTSOFTWARE

APPLICATION

DOCUMENTSOFTWARE

APPLICATION

DOCUMENTSOURCE

CODE

DOCUMENTSOURCE

CODE

PERFORMMETRICS

PERFORMMETRICS

During this process the source code is written, documented, reviewed, tested and packaged for delivery. For this to be successful, the models must drive the development of the source code. This process is far more to writing source code of programs.

GENERALIZE GENERALIZE

IDENTIFYPOTENTIALREUSABLE

ITEMS

IDENTIFYPOTENTIALREUSABLE

ITEMS

project deliverables

HOLDGENERALIZA-

TIONSESSIONS

HOLDGENERALIZA-

TIONSESSIONS

RELEASERELEASEMAKE

DOCUMENTA-TION

MAKEDOCUMENTA-

TION

PERFORMMETRICS

PERFORMMETRICS

REFACTORCODE

REFACTORCODE

reusable items

This is the recognition that the short-term pressures of software development result in the temptation for developers to settle for specific, non-reusable solutions. In this process, application specific items are identified and then reworked to be reusable by other development teams.

TEST IN THE SMALL TEST IN THE SMALL

DEVELOPTESTPLAN

DEVELOPTESTPLAN

modelssource coderequirementsmaster test quality assurance plan

SCENARIOAND

PROCESSTEST

SCENARIOAND

PROCESSTEST

RECORDDEFECTSRECORDDEFECTS

WALK-THROUGHMODELS

WALK-THROUGHMODELS

USERINTERFACE

TESTING

USERINTERFACE

TESTING

PROGRAMCODE

TESTING

PROGRAMCODE

TESTING

REVIEWTECHNICAL

DESIGN

REVIEWTECHNICAL

DESIGN

INSPECTSOURCE

CODE

INSPECTSOURCE

CODE

REVIEWPROTOTYPES

REVIEWPROTOTYPES

tested artifactstest resultsmaster testquality assurance plan

This process focuses on the verification, validation, and testing of documents, models, and source code produced. In many ways it is quality assurance techniques such as peer reviews and inspections combined with unit testing techniques for validating code.

CONSTRUCT to be performed checklist

the models for the application have been developed and validated

the source code for the application have been developed and validated

reusable artifacts have been identified

potential artifacts to be generalized for reuse have been identified and potentially generalized

user documentation has been developed decisions (both made and forgone) were documented into group

memory metrics have been collected

CONSTRUCT exit conditions checklist

requirement allocation matrix has been updated

project plan was updated appropriately

models, source code and documentation were baselined

test plan has been updated for for the test in the large

user, support and operations documentation is ready for testing

application has been packaged for testing

training, release, and project plans have been updated appropriately

CONSTRUCT PHASE

model

Model entrance conditions checklist

initial requirements have been documented and accepted

modeling and programming tools were prepared

subject matter experts have been scheduled

team members have been given the appropriate training

Model to be performed checklist

models were assembled and validated user interface prototype was developed and validated assumptions made during modeling were challenged and documented

appropriately manual processes, legacy applications, and new system development

was identified and modeled accordingly requirement allocation matrix was updated/developed

reusable artifacts have been identified and used

risk assessment document has been updated decisions (both made and forgone) were documented into group


Model exit conditions checklist

models have been appropriately documented

models have been validated

test plan has been updated

models have been accepted by the team

models have been accepted by senior management

CONSTRUCT PHASE

program

Program entrance conditions checklist

appropriate models are available

development tools are installed

professional programmers are available

team members have appropriate training

Program to be performed checklist

programmers worked with the designers to understand models

source code was written and documented

source code was synchronized with models

source code was prepared for inspection during test in the small

integration plan was prepared

reusable artifacts have been used



CONSTRUCT PHASE

generalize

Generalize entrance conditions checklist

project deliverable

experienced reuse engineers are available

organizational support for reuse exists

team members have been given the appropriate training

Generalize to be performed checklist

potential reusable items have been identified generalization sessions were held potentially reusable items were refactored reusable items were documented examples of how to reuse reusable items were documented reusable items were released into the repository and made accessible

to all developers



Generalize exit conditions checklist

generalized items have been submitted to the reuse repository

all developers have been made aware of new items

CONSTRUCT PHASE

Test in the small

Test in the small entrance conditions checklist

there are artifacts to be tested

test plan exists

requirements have been documented

team members have appropriate training

Test in the small to be performed checklist

test plan was updated appropriately

models were reviewed and walked through and accepted

user interface prototypes were reviewed and tested

source code was inspected and improved before being tested

perform software testing

defects were recorded and analyzed

risk assessment document has been updated decisions (both made and forgone) were documented into group memory metrics have been collected

Test in the small exit conditions checklist

all items have been tested, reviewed and updated accordingly

master test has been updated for “test in the large”

Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management...

Documents

Transcript of Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management...