The Software Development Standards
The Software DevelopmentStandardsInstructor: Dr. Hany H. AmmarDept. of Computer Science andElectrical Engineering, WVU
OUTLINE The System Life Cycle Model and the SystemDevelopment Process.Software Engineering and the SoftwareDevelopment ProcessSoftware Development standardsThe ICASE EnvironmentsICASE Tool: Teamwork (see notes of Ch. 2), andSoftware through Pictures (StP)
Software Development StandardsThree standards for software development arediscussed The software engineering standard (PSS-05-0) ofthe European Space Agency (ESA ) The MIL-STD-498 standard for softwaredevelopment of the US Department of Defense IEEE/EIA 12207 Standard for InformationTechnology-software life cycle processes
The ESA standard The ESA standard consists of two parts namely,the product standards part and the procedurestandards part.The product standards part contains standards,recommendations and guidelines concerning thesoftware product,The procedure standards part describes theprocedures used to manage the softwaredevelopment project.
The ESA standardThe ESA product standard mandates that all softwareprojects shall have a life cycle approach consistingof the following basic phases: User Requirements (UR) definition Software Requirements (SR) specification Architectural Design (AD) specification Detailed Design (DD) and production of thecode Transfer (TR) of software to operation, and Operations and Maintenance (OM).
The ESA standard The UR phase is the problem definition phase inwhich the scope of the software is clearlyspecified by the users in cooperation with thedeveloper’s teams of software engineers, hardwareengineers, and managers.In the UR phase, the operational environment ofthe software is determined.The users requirements are captured anddocumented in a User Requirements Doc (URD).The review of the URD (UR/R) is performed bythe same teams who have already worked onsoftware specifications in the UR phase.
The ESA standardThe SR phase is the software requirementsanalysis and specification phase A logical model of the software is produced (usingStructured analysis or Object-Oriented Analysis) andused to analyze the completeness, consistency, andtestability of the requirements Software Requirements Document (SRD) isproduced and is formally reviewed (SR/R) by theusers, software engineers, hardware engineers, andmanagers concerned.
The ESA standard The Architecture Design (AD) phase deals withthe construction of what is termed as “the physicalmodel” of the software. It defines the architectureor structure of the software in terms ofcomponents or modules and their interfacesThe software components as well as the data flowand control flow between them are defined.The deliverable produced in this phase is theArchitectural Design Document (ADD). The ADDis again formally reviewed (AD/R) by the sameteams mentioned above.
The ESA standard The activities of the DD phase include moduledesign, coding, unit testing, integration testing andsystem testing.A Detailed Design Document (DDD) and theSoftware User Manual (SUM) are producedconcurrently with coding and testingUnit, integration, and system testing is performedaccording to verification plans established in theSR and AD
The ESA standard The code, DDD, and SUM documents are reviewed inthe formal Detailed Design Review (DD/R) bysoftware engineers and the management concernedThe TR phase includes the installation and theprovisional acceptance testing activities to establishthat the software fulfils the requirementsA Software Transfer document (STD) is producedwhich contains the description of the activitiesperformed and the transfer of the software to theoperation team.In the OM phase, the software is monitored forenough time to establish the final acceptance testing
Software Development StandardsThree standards for software development arediscussed The software engineering standard (PSS-05-0) ofthe European Space Agency (ESA ) The MIL-STD-498 standard for softwaredevelopment of the US Department of Defense IEEE/EIA 12207 Standard for InformationTechnology-software life cycle processes
The MIL-STD-498 The software engineering process shall include thefollowing major activities (system view) (notes:page 2-61) System requirements analysis (SYSRA) generates Operational Concept Description document (OCD), the System/Subsystem Specification (SSS) doc, and the Interface Requirement Specification (IRS) doc System Design (SYSD), defines the system as SW/HWconfiguration items, and generates the System/Subsystem Design Description (SSDD)document, and the Interface Design Description (IDD) document
The MIL-STD-498 Parallel development threads are then shown for eachComputer SW Configuration Item (CSCI) Software Requirements Analysis (SWRA) generatesthe SW Requirements. Specifications (SRS) and InterfaceRequirements Specifications (IRS) documents Software Design (SWD) generates Software DesignDescription (SDD), IDD (interfaces), and DBDD docs Software Implementation & Unit Testing (SWIUT)Unit Integration and Testing (UIT) generates SWTest Description (STD) doc CSCI Qualification Testing (CSCIQT) generatesSoftware Test Report (STR) doc
The MIL-STD-498The parallel threads of development merge into asequential development thread in the following CSCI/HWCI Integration and Testing (IT)generates the system Test Description (SYSTD) doc System Qualification Testing (SYSQT) generatesthe system Test report (SYSTR)The last two phases are accomplished in parallel Preparing for Software Use (PSWU) Preparing for Software Transition (PSWT)Notes:See Figures 2.8, 2.9, and 2.10 for the threemodels
Software Development StandardsThree standards for software development arediscussed The software engineering standard (PSS-05-0) ofthe European Space Agency (ESA ) The MIL-STD-498 standard for softwaredevelopment of the US Department of Defense IEEE/EIA 12207 Standard for InformationTechnology-software life cycle processes
IEEE/EIA 12207 Standard for InformationTechnology-software life cycle processesIEE/EIA 12207.0Clause 1-Scope.Purpose: This International Standard establishes acommon framework for software life cycle processes,with well-defined terminology, that can be referencedby the software industry.It contains processes, activities, and tasks that are tobe applied during the acquisition of a system thatcontains software, a stand-alone software product, andsoftware service and during the supply, development,operation, and maintenance of software products.Software includes the software portion of firmware.20
IEEE/EIA 12207 Standard for InformationTechnology-software life cycle PERATIONSUPPLYDEVELOPMENTCMDOCUMENTATIONPROB. RES.VERIFICATIONQAJOINT REVIEWAUDITVALIDATIONSUPPORTING TIONAL PROCESSES21
The 12207 Primary ProcessesThe Five Primary Processes (see Clause 5 for details)AcquisitionDefines the activities of the acquirer, the organization that acquiresa system, software product, or software service.SupplyDefines the activities of the supplier, the organization that providesthe system, software product or software service to theacquirer.Development Defines the activities of the developer, the organization thatdefines and develops the software product.OperationDefines the activities of the operator, the organization that providesthe service of operating a computer system in its liveenvironment for its users.MaintenanceDefines the activities of the maintainer, the organization thatprovides the service of maintaining the software product; that is,managing modifications to the software product to keep itcurrent and in operational fitness. This process includes themigration and retirement of the software product.22
The IEEE 12207 Development ProcessActivityTasks (paraphrased)12207.1 Information Item guidelines5.3.1 ProcessImplementation.1 Define software life cycle model.2 Document and control outputs.3 Select and use standards, tools,languages.4 Document development plans.5 Deliver all needed products---Plan, Desc-----6.5 DPP, 6.17 SDSD--5.3.2 Systemrequirements analysis.1 Specify system requirements.2 Evaluate requirements against criteriaSpecificationSpec, Record6.26 SRS6.26 SRS, 6.6 SRER5.3.3 Systemarchitectural design.1 Establish top-level architecture.2 Evaluate architecture against criteriaDescriptionDesc, Record6.25 SARAD6.25 SARAD, 6.6 SAER5.3.4 Softwarerequirements analysis.1 Document software requirements.2 Evaluate requirements against criteria.3 Conduct joint reviews iaw 6.6DescDesc, Record--6.22 SRD, 6.30 UDD6.22 SRD, 6.6 SRER--5.3.5 Softwarearchitectural design.1 Transform requirements intoarchitecture.2 Document top-level design forinterfaces.3 Document top-level design fordatabase.4 Document preliminary userdocumentation.5 Document preliminary testrequirements.6 Evaluate architecture against criteria.7 Conduct joint reviews iaw nDesc, Record--6.12 SAD6.19 SIDD6.4 DBDD6.30 UDD6.27 T/VP6.12 SAD, 6.6 SAER--23
5.3.6Softwaredetaileddesign.1 Document design for eachcomponent.2 Document design for interfaces.3 Document design for database.4 Update user documentation.5 Document unit test requirements.6 Update integration test requirements.7 Evaluate detailed design againstcriteria.8 Conduct joint reviews iaw nPlanRec, Desc--6.16 SDD6.19 SIDD6.4 DBDD6.30 UDD6.27T/VP6.27T/VP6.6 DDER, 6.16 SDD--5.3.7Softwarecodingandtesting.1 Document each unit, database andtests.2 Conduct and document unit testing.3 Update user documentation.4 Update integration test requirements.5 Evaluate code and test resultsDesc, Rec,ProcReportDescriptionPlanRec, Plan6.4 DBDD, 6.24 SCR, 6.28 T/VPr6.29 T/VRR6.30 UDD6.27T/VP6.7 EOCR,6.6 SCTRE, 6.24SCR,6.27T/VP5.3.8Softwareintegration.1 Document integration plans.2 Conduct and document integrationtests.3 Update user documentation.4 Document qualification tests.5 Evaluate plans and tests againstcriteria.6 conduct joint reviews iaw 6.6Plan, ProcReportDescriptionProcProc, DescRecord,Plan6.18 SIP, 6.28 T/VPr6.29 T/VRR6.30 UDD6.28 T/VPr6.28 T/VPr, 6.30 UDD6.6 SIER, 6.18 SIP24
5.3.9 Softwarequalification testing.1 Conduct and document qualificationtesting.2 Update user documentation.3 Evaluate tests against criteria.4 Support audits iaw 6.7.5 Prepare product for next phaseReportDescriptionRecord-Record6.29 T/VRR6.30 UDD6.6 SIER-6.24 SCR5.3.10 Systemintegration.1 Integrate software with hardware &others.2 Document integration tests.3 Evaluate integrated system againstcriteriaReportProcedureRecord6.29 T/VRR6.28 T/VPr6.6 SQTER5.3.11 Systemqualification testing.1 Conduct and document qualificationtests.2 Evaluate system against criteria.3 Support audits iaw 6.7.4 Prepare product for installationReportRecord-Record6.29 T/VRR6.6 SER-6.24 SCR5.3.12Softwareinstallation.1 Plan installation in target environment.2 Install software iaw plan------5.3.13Softwareacceptance support.1 Support acquirer's acceptance tests.2 Deliver product per contract.3 Provide training per contractReportRecord--6.29 T/VRR6.24 SCR--25
The IEEE 12207 Development Process: The SystemArchitecture Design Activity 5.3.3 System architectural design. This activity consists of thefollowing tasks, which the developer shall perform or support as requiredby the contract:5.3.3.1 A top-level architecture of the system shall be established. Thearchitecture shall identify items of hardware, software, and manualoperations. It shall be ensured that all the system requirements areallocated among the items. Hardware configuration items, softwareconfiguration items, and manual operations shall be subsequentlyidentified from these items. The system architecture and the systemrequirements allocated to the items shall be documented.5.3.3.2 The system architecture and the requirements for the itemsshall be evaluated considering the criteria listed below. The results ofthe evaluations shall be documented.a) Traceability to the system requirements;b) Consistency with the system requirements;c) Appropriateness of design standards and methods used;d) Feasibility of the software items fulfilling their allocated requirements;e) Feasibility of operation and maintenance.26
The IEEE 12207 Development Process: TheSoftware Architecture Design Activity5.3.5 Software architectural design. For each software item (or software configuration item, i fidentified), this activity consists of the following tasks:5.3.5.1 The developer shall transform the requirements for the software item into an architecture thatdescribes its top-level structure and identifies the software components. It shall be ensured that alltherequirements for the software item are allocated to its software components and further refined tofacilitate detailed design. The architecture of the software item shall be documented.5.3.5.2 The developer shall develop and document a top-level design for the interfaces external to thesoftware item and between the software components of the software item.5.3.5.3 The developer shall develop and document a top-level design for the database.5.3.5.4 The developer should develop and document preliminary versions of user documentation.5.3.5.5 The developer shall define and document preliminary test requirements and the schedule forSoftware Integration.5.3.5.6 The developer shall evaluate the architecture of the software item and the interface anddatabase designs considering the criteria listed below. The results of the evaluations shall bedocumented.a) Traceability to the requirements of the software item;b) External consistency with the requirements of the software item;c) Internal consistency between the software components;d) Appropriateness of design methods and standards used;e) Feasibility of detailed design;f) Feasibility of operation and maintenance.5.3.5.7 The developer shall conduct joint review(s) in accordance with 6.6.27
The IEEE 12207 Development ProcessOne example of applying 12207 to the Waterfall development strategyProcess Implementation ActivityDPP, SDSDSARADSys estIntegraSoftwaretion SCR, T/VRRCodeSoftware Item 1:Software & TestSIP,T/VPrSoftware DetailedDesign EOCR, SCR,T/VPr, T/VRRArch.SoftwareDesignReqts.SRD, UDDAnalysisSoftwareSAD, SIDD, DBDD, T/VPQualSRD, UDDSoftwareTestIntegraSoftwaretionCodeSoftware Item 2:Software & TestSoftware VRRSCRT/VPrT/VRRSRSHardware itemsSoftwareAcceptanceSupportT/VRRSCRSupporting Processes: Documentation, CM, QA, Verification, Validation, Joint Review, Audit, Problem resolutionSCMP, SCMR, SCIR, SQAP, SQAR, SVRR, PR/PRROrganizational Processes: Management, Infrastructure, Improvement, Training28
OUTLINE The System Life Cycle Model and the SystemDevelopment Process.Software Engineering and the SoftwareDevelopment ProcessSoftware Development standardsThe ICASE EnvironmentsICASE Tool: Teamwork (see notes of Ch. 2), andSoftware through Pictures (StP)
The ICASE Environments ICASE stands for Integrated Computer-AidedSoftware Engineering EnvironmentsThese environments support a variety ofdevelopment techniques and notations in anintegrated environmentAll the tools used in the development process arepresented through a common user interface.Data and diagrams developed in a tool during aparticular phase in the development process can beused by another tool in a different phase ofdevelopment (analysis tools, design tools, etc.)
The ICASE Environments
The IEEE 12207 Development Process Activity Tasks (paraphrased) 12207.1 Information Item guidelines 5.3.1 Process Implement ation.1 Define software life cycle model.2 Document and control outputs.3 Select and use standards, tools, languages.4 Document development plans.5 Deliver all needed products-----Plan, Desc-----6.5 DPP, 6.17 SDSD--
May 02, 2018 · D. Program Evaluation ͟The organization has provided a description of the framework for how each program will be evaluated. The framework should include all the elements below: ͟The evaluation methods are cost-effective for the organization ͟Quantitative and qualitative data is being collected (at Basics tier, data collection must have begun)
Silat is a combative art of self-defense and survival rooted from Matay archipelago. It was traced at thé early of Langkasuka Kingdom (2nd century CE) till thé reign of Melaka (Malaysia) Sultanate era (13th century). Silat has now evolved to become part of social culture and tradition with thé appearance of a fine physical and spiritual .
On an exceptional basis, Member States may request UNESCO to provide thé candidates with access to thé platform so they can complète thé form by themselves. Thèse requests must be addressed to esd rize unesco. or by 15 A ril 2021 UNESCO will provide thé nomineewith accessto thé platform via their émail address.
̶The leading indicator of employee engagement is based on the quality of the relationship between employee and supervisor Empower your managers! ̶Help them understand the impact on the organization ̶Share important changes, plan options, tasks, and deadlines ̶Provide key messages and talking points ̶Prepare them to answer employee questions
Dr. Sunita Bharatwal** Dr. Pawan Garga*** Abstract Customer satisfaction is derived from thè functionalities and values, a product or Service can provide. The current study aims to segregate thè dimensions of ordine Service quality and gather insights on its impact on web shopping. The trends of purchases have
Chính Văn.- Còn đức Thế tôn thì tuệ giác cực kỳ trong sạch 8: hiện hành bất nhị 9, đạt đến vô tướng 10, đứng vào chỗ đứng của các đức Thế tôn 11, thể hiện tính bình đẳng của các Ngài, đến chỗ không còn chướng ngại 12, giáo pháp không thể khuynh đảo, tâm thức không bị cản trở, cái được
Le genou de Lucy. Odile Jacob. 1999. Coppens Y. Pré-textes. L’homme préhistorique en morceaux. Eds Odile Jacob. 2011. Costentin J., Delaveau P. Café, thé, chocolat, les bons effets sur le cerveau et pour le corps. Editions Odile Jacob. 2010. Crawford M., Marsh D. The driving force : food in human evolution and the future.
Le genou de Lucy. Odile Jacob. 1999. Coppens Y. Pré-textes. L’homme préhistorique en morceaux. Eds Odile Jacob. 2011. Costentin J., Delaveau P. Café, thé, chocolat, les bons effets sur le cerveau et pour le corps. Editions Odile Jacob. 2010. 3 Crawford M., Marsh D. The driving force : food in human evolution and the future.
