IEEE Computer Society Software Engineering Standards Book Series Software Engineering Standards Book Series Deborah E. Plummer Group Manager, CS Press

IEEE Computer Society Software Engineering Standards Book Series

Software Engineering Standards Software Engineering Standards Book SeriesBook Series

Deborah E. PlummerDeborah E. PlummerGroup Manager, CS PressGroup Manager, CS Press

August 6 & 7 2001August 6 & 7 2001

April 19, 2023 IEEE Computer Society Software Engineering Standards Book Series

2

Program ProgressProgram Progress

Financial Projections approved by Financial Financial Projections approved by Financial CommitteeCommittee

Negotiated 50% standard reuse terms of agreement w/ Negotiated 50% standard reuse terms of agreement w/ IEEE Standards group and a bulk sales agreementIEEE Standards group and a bulk sales agreement

Negotiated copyright terms of agreement with IEEE Negotiated copyright terms of agreement with IEEE copyrights managercopyrights manager

Book 1 – telecon completed, revised schedule, Book 1 – telecon completed, revised schedule, manuscript in developmentmanuscript in development

Book 2- telecon date -TBDBook 2- telecon date -TBD Book 3-telecon completed, revised schedule, Book 3-telecon completed, revised schedule,

manuscript in development-(ahead of schedule)manuscript in development-(ahead of schedule)


3

PurposePurpose

Under leadership of Roger Fujii, Software Engineering Under leadership of Roger Fujii, Software Engineering Standards Book Series Editor:Standards Book Series Editor:

Recap mission & strategic focusRecap mission & strategic focus GoalsGoals Manuscript Development Review Manuscript Development Review SponsorshipSponsorship Finding a Distribution ChannelFinding a Distribution Channel Conclude with action plan and assigned responsibilities for Conclude with action plan and assigned responsibilities for

August –December 2001August –December 2001 Schedule next board meeting for 2002 Schedule next board meeting for 2002


4

SWE Standards Book SeriesSWE Standards Book SeriesMissionMission

Develop SE standards-based knowledge products to increase the use of the Develop SE standards-based knowledge products to increase the use of the standards and benefit software engineering professionals and their standards and benefit software engineering professionals and their organizations. organizations.

Objectives:Objectives: Increase awareness, influence, and sales of standards-based products for the Increase awareness, influence, and sales of standards-based products for the

IEEE Computer SocietyIEEE Computer Society Support the goals of all involved (IEEE Standards sales group, IEEE CS SESC, Support the goals of all involved (IEEE Standards sales group, IEEE CS SESC,

IEEE CS)IEEE CS) Make a significant contribution to the professionMake a significant contribution to the profession


5

Organizational Meeting for the Software Organizational Meeting for the Software Engineering Standards Book SeriesEngineering Standards Book Series

Roger U. FujiiRoger U. Fujii

IEEE Computer Society Software Engineering IEEE Computer Society Software Engineering Standards Book Series EditorStandards Book Series Editor

Sheraton Reston HotelSheraton Reston Hotel

6& 7 August 20016& 7 August 2001


6

AgendaAgenda

TimeTime ItemItem PresenterPresenter

9:00-9:459:00-9:45 Welcome and IntroductionsWelcome and Introductions

Recap & Scribe assignmentRecap & Scribe assignment

Status & Progress since last meetingStatus & Progress since last meeting

Author Kit Q&AAuthor Kit Q&A

D. PlummerD. Plummer

A.JacobsA.Jacobs

9:45 – 11:009:45 – 11:00 Software Engineering Stds Book SeriesSoftware Engineering Stds Book Series PurposePurpose Mission and Strategic Focus-RecapMission and Strategic Focus-Recap GoalsGoals Financials & pending considerationsFinancials & pending considerations

R. FujiiR. Fujii

11:00-12:3011:00-12:30 Manuscript Development ReviewManuscript Development Review 12-207 considerations12-207 considerations Content considerationsContent considerations

J.HorchJ.Horch

12:30 – 1:3012:30 – 1:30 Lunch-57Lunch-57thth Street Grill, 2 Street Grill, 2ndnd floor floor

1:30 – 2:001:30 – 2:00 Manuscript Review (cont’d)Manuscript Review (cont’d) Manuscript developmentManuscript development Q&AQ&A

J.HorchJ.Horch


7

Agenda (cont’d)Agenda (cont’d)

TimeTime ItemItem PresenterPresenter

2:00 - 3:002:00 - 3:00 Need for SponsorshipNeed for Sponsorship DiscussionDiscussion Forming a consortiumForming a consortium commitmentscommitments

R. FujiiR. Fujii

3:00 – 3:303:00 – 3:30 Coffee BreakCoffee Break

3:30 4:303:30 4:30 Finding a distribution partnerFinding a distribution partner Author preferencesAuthor preferences Possible contactsPossible contacts Discussion of manuscript review Discussion of manuscript review

considerationsconsiderations Assigned staff support- Dick PriceAssigned staff support- Dick Price

R. FujiiR. Fujii

4:30 – 5:004:30 – 5:00 Software Reuse: A Standards Based Software Reuse: A Standards Based Guide- Buy NOWGuide- Buy NOW

A.JacobsA.Jacobs


8

PurposePurpose

Develop a series of books for the Develop a series of books for the software engineering standards software engineering standards to serve as reference to serve as reference ‘companion books’‘companion books’

Enhance the publication and Enhance the publication and sales of standards by developing sales of standards by developing a book series that helps the a book series that helps the practitioner more effectively practitioner more effectively use the IEEE Computer Society use the IEEE Computer Society software engineering standards.software engineering standards.

Answer typical questions from Answer typical questions from industry: “Explain 12207 and industry: “Explain 12207 and how SQA, V&V, project how SQA, V&V, project management, etc are management, etc are implemented using 12207 for a implemented using 12207 for a specific project.”specific project.”

Using the book series products, Using the book series products, develop related products and develop related products and services including hypertext services including hypertext linked electronic books, book linked electronic books, book series seminars, and professional series seminars, and professional development and accreditation development and accreditation certificate programs.certificate programs.


9

Mission StatementMission Statement

Provide products that promote the sale and Provide products that promote the sale and development of IEEE Computer Society software development of IEEE Computer Society software engineering standards.engineering standards.

Establish an effective process to provide the correct Establish an effective process to provide the correct product, at the right time and price, to the customer. product, at the right time and price, to the customer. This effective work process includes volunteers in vital This effective work process includes volunteers in vital roles (product development) and results in a revitalized roles (product development) and results in a revitalized CS Press.CS Press.

Provide the computer science professional with Provide the computer science professional with standards related products and services to enable standards related products and services to enable software developers with the knowledge and tools to software developers with the knowledge and tools to produce software in compliance with 12207 and IEEE produce software in compliance with 12207 and IEEE software standards.software standards.


10

GoalsGoals Complete (in pipeline) the initial set of the IEEE Complete (in pipeline) the initial set of the IEEE

Computer Society software engineering standards book Computer Society software engineering standards book series by Q4 2001.series by Q4 2001. ISO/IEC 12207 OverviewISO/IEC 12207 Overview Software Project ManagementSoftware Project Management Software Quality AssuranceSoftware Quality Assurance Software Verification and ValidationSoftware Verification and Validation Software TestingSoftware Testing Software Engineering Standards RoadmapSoftware Engineering Standards Roadmap Software ReuseSoftware Reuse

Require first product in editing by Q4 2001.Require first product in editing by Q4 2001. Establish distribution partner and sponsorship by Establish distribution partner and sponsorship by

November 1 2001.November 1 2001.


11

Basic Parameters to the Book SeriesBasic Parameters to the Book Series Written as guidebooks following the 12207 process and Written as guidebooks following the 12207 process and

IEEE Computer Society software engineering IEEE Computer Society software engineering standards - Provide interpretation of the standards, standards - Provide interpretation of the standards, describe the meaning/intent of the standard (examples describe the meaning/intent of the standard (examples for different industry sectors), provide techniques and for different industry sectors), provide techniques and methods to implement the standard process, provide methods to implement the standard process, provide examples, and supply sample exercise problems examples, and supply sample exercise problems (optional)(optional)

All books will have the same look (cover)All books will have the same look (cover) Use 7x10 page sizeUse 7x10 page size Book size can be up to 500 or more sheets (1000 pages)Book size can be up to 500 or more sheets (1000 pages) Bundling the standard with the bookBundling the standard with the book


12

Book Series CategoriesBook Series Categories

Integrative (Overview)Integrative (Overview)

Core StandardsCore Standards

Derivative StandardsDerivative Standards

Roadmap to ISO/IEC 12207Roadmap to ISO/IEC 12207 Software TaxomonySoftware Taxomony

Software Quality AssuranceSoftware Quality Assurance Software Verification and ValidationSoftware Verification and Validation Software Project ManagementSoftware Project Management Software TestingSoftware Testing Software DesignSoftware Design

Software ReuseSoftware Reuse Software Risk ManagementSoftware Risk Management


13

Format of the Book Series*Format of the Book Series*

[ISO/IEC 12207 Cross Reference][ISO/IEC 12207 Cross Reference]

[IEEE Standard [IEEE Standard -- Requirement Citation]Requirement Citation]

Interpretation(s) of IEEE Standard Interpretation(s) of IEEE Standard Reqm’ts Reqm’ts CitationCitationa)

b)

Techniques / Methods To Implement Techniques / Methods To Implement Reqm’tReqm’ta)

b)

c)

d)

Sample Problem(s) or IllustrationsSample Problem(s) or Illustrations

Figure 1: Structure of guidebook

* Excludes the Integrative * Excludes the Integrative book series category.book series category.


14

Book Series: Management and Sponsor Book Series: Management and Sponsor RelationshipRelationship

IEEE Computer Society IEEE Computer Society Press (Sponsor)Press (Sponsor)

Book Series Editorial Book Series Editorial BoardBoard

Technical Content Technical Content Authority – SESC ChairAuthority – SESC Chair

Book Series EditorBook Series EditorR. FujiiR. Fujii

Technical Content Technical Content ReviewersReviewers

Book Book AuthorAuthor




15

Members of the Editorial BoardMembers of the Editorial Board

Roger U. Fujii (Chair)Roger U. Fujii (Chair) Paul CrollPaul Croll James MooreJames Moore Mark ChristensenMark Christensen Richard ThayerRichard Thayer CS Press (Angela Burgess, Deborah Plummer, CS Press (Angela Burgess, Deborah Plummer,

Dick Price, Anne Jacobs, Bob Werner)Dick Price, Anne Jacobs, Bob Werner)


16

Evolution from Book Series to Product LineEvolution from Book Series to Product Line

Book SeriesBook Series

Checklists & Checklists & At A Glance At A Glance ChartsCharts




Electronic Electronic Book SeriesBook Series

Training Training SeminarsSeminars

Accreditation Accreditation CertificatesCertificates

Southeast AsiaSoutheast Asia Alliances with Industry SectorsAlliances with Industry Sectors


17

CS Press SupportCS Press Support

Facilitate achievement of goals set by the SWE Standards Book Facilitate achievement of goals set by the SWE Standards Book Series Board and the CS Press Publisher Series Board and the CS Press Publisher

Establish an effective working process to produce knowledge Establish an effective working process to produce knowledge products developed by the SWE Standards Book Series products developed by the SWE Standards Book Series

Partner with each volunteer author in their vital role as product Partner with each volunteer author in their vital role as product developersdevelopers

Produce books according to the required scheduleProduce books according to the required schedule


18

Suggested Timing of Books for Availability Suggested Timing of Books for Availability to the Marketto the Market

Book 1 & 2: Authors complete manuscript by 1 Book 1 & 2: Authors complete manuscript by 1 October 2001; In print May 2002October 2001; In print May 2002

Book 3 & 4: Authors complete manuscript by 1 Book 3 & 4: Authors complete manuscript by 1 January 2002; In print August 2002January 2002; In print August 2002

Book 5, 6 & 7: Author completes manuscript by 1 April Book 5, 6 & 7: Author completes manuscript by 1 April 2002; In print November 20022002; In print November 2002


19

RoyaltyRoyalty

Terms: Author meets mutually agreed upon schedules and Terms: Author meets mutually agreed upon schedules and facilitates CS Press process requirements to ensure the facilitates CS Press process requirements to ensure the book is produced and in print on time.book is produced and in print on time.

0-2,500 copies=12% royalty0-2,500 copies=12% royalty

2,500-7,000 copies = 15% royalty2,500-7,000 copies = 15% royalty

7000-10,000 copies=17.5% royalty7000-10,000 copies=17.5% royalty

10,000 & up copies = 20% royalty10,000 & up copies = 20% royalty


20

Author KitAuthor Kit

Contract Contract IEEE copyright formIEEE copyright form Project ScheduleProject Schedule Standardized MS Word template Standardized MS Word template Copy of the appropriate standards (for author use only)Copy of the appropriate standards (for author use only) Author Marketing questionnaireAuthor Marketing questionnaire


21

Specific Manuscript Requirements for the Specific Manuscript Requirements for the Series: Requirements Interface AnalysisSeries: Requirements Interface Analysis

ISO/IEC 12207.0ISO/IEC 12207.05.3 Development Process5.3 Development Process

5.3.4 Software Requirements Analysis. 5.3.4 Software Requirements Analysis. For each software item (or software For each software item (or software configuration item, if identified), this activity consists of the following configuration item, if identified), this activity consists of the following tasks:tasks:

5.3.4.1 The developer shall establish and document software requirements, 5.3.4.1 The developer shall establish and document software requirements, including the quality characteristics specification, described below. including the quality characteristics specification, described below. Guidance for specifying quality characteristics may be found in ISO/IEC Guidance for specifying quality characteristics may be found in ISO/IEC 9126.9126.b)b) Interfaces external to the software item.Interfaces external to the software item.f) Human factors engineering (ergonomics), including those related to f) Human factors engineering (ergonomics), including those related to

manual operations, human-equipment interactions, constraints on manual operations, human-equipment interactions, constraints on personnel, and areas needing concentrated human attention, that are personnel, and areas needing concentrated human attention, that are sensitive to human errors and training.sensitive to human errors and training.


22


ISO/IEC 12207.0ISO/IEC 12207.05.3.4.2 The developer shall evaluate the software requirements considering the 5.3.4.2 The developer shall evaluate the software requirements considering the

criteria listed below. The results of the evaluation shall be documented.criteria listed below. The results of the evaluation shall be documented.b)b) External consistency with system requirementsExternal consistency with system requirementsc)c) Internal consistencyInternal consistency

IEEE Std 1012-1998IEEE Std 1012-19985.4.2 Requirements V&V Activity5.4.2 Requirements V&V Activity(3) Interface Analysis. Verify and validate that the requirements for software (3) Interface Analysis. Verify and validate that the requirements for software

interfaces with hardware, user, operator, and other systems are correct, interfaces with hardware, user, operator, and other systems are correct, consistent, complete, accurate, and testable. The task criteria are as consistent, complete, accurate, and testable. The task criteria are as follows:follows:

The role of software V&V is to provide objective evidence, analysis, or The role of software V&V is to provide objective evidence, analysis, or conclusions that the developer has complied with ISO/IEC 12207 processes. The conclusions that the developer has complied with ISO/IEC 12207 processes. The IEEE Standard for Software Verification and Validation (IEEE Std 1012) IEEE Standard for Software Verification and Validation (IEEE Std 1012) addresses the ISO/IEC 12207 requirements in the following manner.addresses the ISO/IEC 12207 requirements in the following manner.


23


IEEE Std 1012-1998IEEE Std 1012-1998(3.1) Correctness(3.1) Correctness

a.a. Validate the external and internal system and software interface Validate the external and internal system and software interface requirements.requirements.

(3.2) Consistency(3.2) Consistencya.a. Verify that the interface descriptions are consistent between the SRS Verify that the interface descriptions are consistent between the SRS

and IRSand IRS(3.3) Completeness(3.3) Completeness

a.a. Verify that each interface is described and includes data format and Verify that each interface is described and includes data format and performance criteria (e.g., timing, bandwidth, accuracy, safety, and performance criteria (e.g., timing, bandwidth, accuracy, safety, and security).security).

(3.4) Accuracy(3.4) Accuracya.a. Verify that each interface provides information with the required Verify that each interface provides information with the required

accuracy.accuracy.(3.5) Testability(3.5) Testability

a. Verify that there are objective acceptance criteria for validating the a. Verify that there are objective acceptance criteria for validating the interface requirements.interface requirements.


24

Specific Manuscript Requirements for the Specific Manuscript Requirements for the Series: Requirements Interface AnalysisSeries: Requirements Interface AnalysisInterpretation of the Standards.Interpretation of the Standards. V&V must verify and validate all requirements V&V must verify and validate all requirements originating from and sent to all interfaces of the software under examination. originating from and sent to all interfaces of the software under examination. These interfaces include the user, operator, external and internal hardware These interfaces include the user, operator, external and internal hardware components, external and internal software components, database systems, and components, external and internal software components, database systems, and environmental or physical laws that influence system behavior. The sources of the environmental or physical laws that influence system behavior. The sources of the interface descriptions can be found in many documents and specifications interface descriptions can be found in many documents and specifications including:including:

1.1. Software Requirements Specification (SRSs)Software Requirements Specification (SRSs)2.2. Interface Requirements Specifications (IRSs)Interface Requirements Specifications (IRSs)3.3. Concept DocumentationConcept Documentation4.4. Interface Control Documents (ICDs)Interface Control Documents (ICDs)5.5. Hardware SpecificationsHardware Specifications6.6. COTS Technical SpecificationsCOTS Technical Specifications7.7. User Documentation and ManualsUser Documentation and Manuals8.8. Operator ManualsOperator Manuals9.9. Database Manuals and Database Use Case DescriptionsDatabase Manuals and Database Use Case Descriptions

Figure 5.3.1-1 is a system block diagram that illustrates the different types of Figure 5.3.1-1 is a system block diagram that illustrates the different types of interfaces existing in a system. The output of the interface analysis consist of interfaces existing in a system. The output of the interface analysis consist of anomaly reports and task summary reports for each analysis conducted.anomaly reports and task summary reports for each analysis conducted.


25


Operating System Interface

Hardware Hardware

Software Program

Operating SystemOperating System

Software Program

Database

External Hardware Interfaces

External Software Interfaces

Database Interfaces

Internal Software Interfaces

Users

Operator Interfaces

F1 F3

F2F4

F5

User Interfaces

Operator(s)


26

Specific Manuscript Requirements for the Specific Manuscript Requirements for the Series: Requirements Interface AnalysisSeries: Requirements Interface AnalysisAn example of a task summary report is illustrated in Figure 5.3.1-2. An example of a task summary report is illustrated in Figure 5.3.1-2.

Techniques/MethodsTechniques/Methods..The system block diagram showing each of the different interfaces is a good The system block diagram showing each of the different interfaces is a good starting point to analyze the interface requirements. The most widely used starting point to analyze the interface requirements. The most widely used techniques and methods for analyzing the interface requirements are:techniques and methods for analyzing the interface requirements are:

• Interface Input/Output Requirements MatrixInterface Input/Output Requirements Matrix• Interface Control Flow DiagramsInterface Control Flow Diagrams• Interface Data Flow DiagramsInterface Data Flow Diagrams• Hierarchical Input/Process/Output (HIPO) ChartsHierarchical Input/Process/Output (HIPO) Charts

A disciplined V&V approach is applied to analyze each interface shown in the A disciplined V&V approach is applied to analyze each interface shown in the system block diagram using an interface analysis technique such as the ones listed system block diagram using an interface analysis technique such as the ones listed above. A detailed checklist of questions and analysis are applied to each interface above. A detailed checklist of questions and analysis are applied to each interface as a rigorous method of verifying and validating the interfaces for correctness, as a rigorous method of verifying and validating the interfaces for correctness, consistency, completeness, accuracy, and testability. The sample checklist of consistency, completeness, accuracy, and testability. The sample checklist of questions and analysis to apply to each interface are listed in Figure 5.3.1-3.questions and analysis to apply to each interface are listed in Figure 5.3.1-3.


27

Specific Manuscript Requirements for the Specific Manuscript Requirements for the Series: Requirements Interface AnalysisSeries: Requirements Interface AnalysisThe Interface Input/Output Requirements Matrix is a straightforward detailing of The Interface Input/Output Requirements Matrix is a straightforward detailing of key parameters and characteristics of each interface which vary from project to key parameters and characteristics of each interface which vary from project to project. A standard interface input/output requirements matrix is show below.project. A standard interface input/output requirements matrix is show below.

ItemItem DescriptionDescription RangeRange UnitsUnits I//OI//O SourceSource DestinationDestination

Axis SelAxis Sel Collimator axis Collimator axis to set targetto set target

X,YX,Y

Y1, Y2Y1, Y2

N/AN/A Ext InputExt Input TerminalTerminal N/AN/A

Number Number Entered Entered EventEvent

Flag for Flag for numerical inputnumerical input

True, True, FalseFalse

N/AN/A InputInput Numeric Numeric Input FncInput Fnc

N/AN/A

NumberNumber Collimator Collimator target positiontarget position

-9999 to -9999 to 9999999999

cmcm InputInput Numeric Numeric Input FncInput Fnc

N/AN/A

X minX min Minimum Minimum allowable Xallowable X

0.5 0.5 .03.03 cmcm InputInput Global Global constantconstant

N/AN/A

X maxX max Maximum Maximum allowable Xallowable X

40.0 40.0 .5.5 cmcm InputInput Global Global constantconstant

N/AN/A


28

Specific Manuscript Requirements for the Specific Manuscript Requirements for the Series: Requirements Interface AnalysisSeries: Requirements Interface AnalysisThe V&V analysis process of constructing the matrix (if not already provided in one The V&V analysis process of constructing the matrix (if not already provided in one of the development specifications) affords the V&V analyst the ability to question of the development specifications) affords the V&V analyst the ability to question and analyze the data. For example, one can ask whether the precision and range of and analyze the data. For example, one can ask whether the precision and range of values listed for each item accurate and consistent with the performance of the values listed for each item accurate and consistent with the performance of the software and system requirements. Does the precision of the values impose software and system requirements. Does the precision of the values impose constraints on the accuracy of computations performed by program functions constraints on the accuracy of computations performed by program functions (double precision or precision to the correct decimal point). Are the units of (double precision or precision to the correct decimal point). Are the units of measure consistent with the units of measure used by the software functions and measure consistent with the units of measure used by the software functions and system. Are the inputs and outputs correctly specified or are there missing system. Are the inputs and outputs correctly specified or are there missing input/outputs. Does the source of the interface have the same consistency of the input/outputs. Does the source of the interface have the same consistency of the interface as required by the software (for example, will any interfacing hardware or interface as required by the software (for example, will any interfacing hardware or software system provide the data to the accuracy and precision as stated in the software system provide the data to the accuracy and precision as stated in the interface?). Are any constraints identified by the source or destination consistent interface?). Are any constraints identified by the source or destination consistent with the system requirements and are testing of such constraints feasible. By with the system requirements and are testing of such constraints feasible. By following an orderly process of analysis of each interface, a thorough V&V following an orderly process of analysis of each interface, a thorough V&V examination and analysis is achieved. Typical checklists of questions and analyses examination and analysis is achieved. Typical checklists of questions and analyses are shown in Figure 5.3.1-3. are shown in Figure 5.3.1-3.


29

Specific Manuscript Requirements for the Specific Manuscript Requirements for the Series: Requirements Interface AnalysisSeries: Requirements Interface AnalysisSample Problems and Illustrations.Sample Problems and Illustrations.


30

SummarySummary

Return appropriate forms from the author’s kit to CS Return appropriate forms from the author’s kit to CS PressPress

Work on book schedule with Book Series Editor and Work on book schedule with Book Series Editor and CS PressCS Press

Develop draft material with Book Series Editor and Develop draft material with Book Series Editor and prepare a sample section/chapter for review.prepare a sample section/chapter for review.

Work with Book Series Editor, Assistant Publisher and Work with Book Series Editor, Assistant Publisher and Group Manager, Press to solicit Distribution partners Group Manager, Press to solicit Distribution partners and sponsorship for series.and sponsorship for series.

Help evolve the concept of the software engineering Help evolve the concept of the software engineering standards book series product linestandards book series product line


31

V&V Book OutlineV&V Book Outline

Chapter 1: Basic Principles of Verification and ValidationChapter 1: Basic Principles of Verification and Validation History of V&VHistory of V&V V&V ObjectivesV&V Objectives Relationship of V&V to PM, QA, CM, Testing, and DevelopmentRelationship of V&V to PM, QA, CM, Testing, and Development

• Independent V&VIndependent V&V

• Audience/Field of ApplicationAudience/Field of Application Chapter 2: Relationship of V&V to Software Engineering Chapter 2: Relationship of V&V to Software Engineering

StandardsStandards V&V to ISO/IEC 12207.0V&V to ISO/IEC 12207.0 V&V to IEEE Software Engineering StandardsV&V to IEEE Software Engineering Standards Organization of Book to ISO/IEC 12207.0 Life Cycle ProcessesOrganization of Book to ISO/IEC 12207.0 Life Cycle Processes


32


Chapter 3: Acquisition Process V&VChapter 3: Acquisition Process V&V InitiationInitiation Request-for-proposal (tender) preparationRequest-for-proposal (tender) preparation Supplier monitoringSupplier monitoring Acceptance and completionAcceptance and completion

Chapter 4: Supply Process V&VChapter 4: Supply Process V&V InitiationInitiation Preparation and Response (??)Preparation and Response (??) ContractContract PlanningPlanning Execution and ControlExecution and Control Review and EvaluationReview and Evaluation Delivery and Completion (??)Delivery and Completion (??)


33


Chapter 5: Development Process V&VChapter 5: Development Process V&V Process ImplementationProcess Implementation Systems Requirements AnalysisSystems Requirements Analysis System Architecture DesignSystem Architecture Design Software Requirements AnalysisSoftware Requirements Analysis Software Architecture Design/Software Detailed DesignSoftware Architecture Design/Software Detailed Design Software Coding and TestingSoftware Coding and Testing Software IntegrationSoftware Integration Software Qualification TestingSoftware Qualification Testing System IntegrationSystem Integration System Qualification TestingSystem Qualification Testing Software InstallationSoftware Installation Software Acceptance SupportSoftware Acceptance Support


34


Chapter 6: Operation Process V&VChapter 6: Operation Process V&V Process ImplementationProcess Implementation Operational TestingOperational Testing System Operation (??)System Operation (??) User SupportUser Support

Chapter 7: Maintenance Process V&VChapter 7: Maintenance Process V&V Process ImplementationProcess Implementation Problems and Modification AnalysisProblems and Modification Analysis Modification ImplementationModification Implementation MigrationMigration Software RetirementSoftware Retirement


35


Chapter 9: Management of V&VChapter 9: Management of V&V Chapter 10: Support Life Cycle Processes V&VChapter 10: Support Life Cycle Processes V&V

Documentation ProcessDocumentation Process Configuration ProcessConfiguration Process Quality AssuranceQuality Assurance Joint Review ProcessJoint Review Process Audit ProcessAudit Process Problem Resolution ProcessProblem Resolution Process

IEEE Computer Society Software Engineering Standards Book Series