Bolster Analysis for Software .


40 views
Uploaded on:
Description
DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT. 2. Presentation Overview. The Support Analysis for Software (SAS) Process OverviewSoftware Identification and BreakdownCategorisation of SoftwareSupportability AnalysisThe Support ConceptInterfaces to other disciplinesThe SAS databaseReference Documentation.
Transcripts
Slide 1

Bolster Analysis for Software A way to guarantee programming supportability R. Somoza ramon.somoza@software-supportability.org DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 2

The Support Analysis for Software (SAS) Process Overview Software Identification and Breakdown Categorisation of Software Supportability Analysis The Support Concept Interfaces to different controls The SAS database Reference Documentation Presentation Overview DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 3

Supportability Plan and Case It is helpful, keeping in mind the end goal to guarantee programming supportability, to outline the administration of programming supportability around two key segments: Software Supportability Plan: As a feature of the System Supportability Plan, it depicts the exercises to be attempted with a specific end goal to accomplish the product supportability destinations. It additionally portrays exercises to be embraced to demostrate accomplishment of those targets Software Supportability Case: A composed documenation about how item supportability was confirmed/created at every phase of programming improvement according to the SW Supportability Plan DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 4

A Process for Software Supportability Any procedure (in light of the Software Supportability Plan) must accomplish that the client necessities for programming supportability should be: resolved fulfilled exhibited Such a procedure has subsequently to decide those prerequisites impact outline with the goal that supportability is incorporated with the item build up the Support Concept and guarantee it is executed act naturally approved DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 5

The reaction: A methodological procedure that infers supportability necessities on the premise of the bolster capacities to be completed: Support Analysis for Software DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 6

What is SAS? It\'s self-evident: A trap of the contractual workers to request more cash another "pleasantness" of the legislature to squander considerably more cash (all things considered, it\'s quite recently the citizens who pay...) Both Some doltish elucubration from a scholarly that has never done such an investigation, has never bolstered programming, has never conversed with the casualties of terrible support (the poor clients), would not perceive programming on the off chance that it were put on his supper plate. A blend of all above (recall Murphy\'s Law...) DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 7

What is SAS? It is a steady philosophy that looks for the accomplishment of framework and programming supportability all through prerequisites, particular and configuration, with a specific end goal to characterize the most practical bolster idea that meets the operational necessities, and to guarantee that the essential bolster foundation is set up before the framework goes into administration. DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 8

Goals for a SAS Process Establish supportability necessities in the early program stages so they can be legitimately tended to Influence outline amid advancement with a specific end goal to guarantee programming supportability, both for operation and adjustment Ensure that supportability issues don\'t influence adversely the operation as well as the accessibility of the handled framework Ensure all needed help procedures and foundation are appropriately actualized preceding section into administration Reduce similarly as attainable the cost of possession Be itself financially savvy (i.e, the investment funds and additionally accomplished upgrades must exceed the cost of the SAS procedure) DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 9

PROGRAM PLANNING AND CONTROL Development of an early SAS Strategy – SAS Plan Program and Design Reviews MISSION, DEVELOPMENT & SUPPORT SYSTEMS DEFINITION Use Study – Technological Opportunities Standarization – Design Factors Comparative Analysis – Integration of ADP Systems PREPARATION AND EVALUATION OF ALTERNATIVES Functional and Non-Functional Requirements Support System Alternatives – Evaluation of Alternatives & Trade-Offs DETERMINATION OF SASR REQUIREMENTS Operational Task Analysis Software Exception/Problem Support Analysis (FRACAS) Software Modification Analysis Software Transition Analysis Post-Deployment Software Support (PDSS)/Logistics Management Analysis SOFTWARE SUPPORTABILITY ASSESSMENT (CASE) Operation – Modification – Problem Reaction – Logistics Management Lessons Learnd Structure for a SAS Process Project Life Cycle Pre Concept Development Post-Development But: It is advantageous to keep amid the administration stage! DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 10

Outline of a SAS Analysis Software Identification & Breakdown Use Study Categorisation Vendor Support Documentation of Support Concept, CRLCMP Evaluation of Support Alternatives Other Support Options Identification of Support Resources Selection of Support Option Trade-Offs DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 11

Identification of SW inside a Project The distinguishing proof/organizing of programming inside a venture has dependably been a noteworthy issue. One approach that has functioned admirably (e.g., in the EF-2000 venture) is the relationship of programming to the equipment where it executes in light of the fact that: That is the objective machine It is the place equipment/programming reconciliation testing will be done It is the place the product will live This procedure can be made reliable with the LSA breakdown This system, be that as it may, won\'t not work in systems or measured aeronautics But rather: It ought to be remembered that there are TWO unique breakdowns of programming, contingent upon the bolster capacity to be surveyed: Functional breakdown (i.e, how programming is planned) for adjustment Physical breakdown (i.e, the "loadable" components) for the operation DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 12

Functional Breakdown Principles The "Useful" Software are every one of those components that portray the practical/outline parts important to the product builds This is the Software that must be considered for Modification Support It is essential that this breakdowns takes after as nearly as conceivable the genuine programming outline Because else it will misrepresent your bolster contemplations Because an Audit Trail to the current outline is required Because that is the beginning stage for bolster Because the product documentation is organized that way BUT: You can incorporate "Dummy" Software Items to gathering sets of usefulness that are recorded all in all or which have a different Design, gave that: Dummy Items are utilized to give an extra level of deliberation Dummy Items don\'t change the general structure and usefulness of the Design DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 13

S1AB Functional Breakdown of Software Candidates for Separate Software Support are Framed S1 S1A S1B S1A S1B S1AB (S1AA) S1AA S1AAB S1AAC S1AAD S1AAE S1AAF S1ABA S1ABE S1AAG S1ABC S1ABB S1ABD S1AAA S1ABE incorporated into outline of S1ABA Notes: Shaded territories show finish plans (CSCIs) CSCI Candidates are encircled, Candidates for Integration in twofold casings, Dummy Candidate Numbers in sections. S1AA additionally incorporates the interfaces to alternate CSCIs & goes about as though it were the Top-Level Design; DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 14

S1A S1B Design point of view (Module coupling & attachment) Software S1 S1A Dependencies between the distinctive programming things exist both on a level plane and vertically. S1B Hierarchical point of view (Functional conditions) S1A S1B Functional Breakdown Perspectives The Software Breakdown is ONLY one of the conceivable perspectives of the Software. Bolster Decisions CANNOT be construct ONLY in light of this point of view. Structure DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 15

Physical Breakdown Principles The "Physical" Software is every one of those components that can be controlled independently by the administrator/client This is the Software that must be considered for Operational Support Two methodologies can be utilized here: It is a piece of the equipment component where it is stacked It is a piece of the equipment component where it dwells Similarly, a few levels of breakdown can be recognized: System Line-Replaceable Item (Computer) Shop-Replaceable Item (Computer Card) Component (Chip) DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 16

L12-L Application SW Load L122-S DVI Module SW Load L121-S Audio Module SW Load L121-F Audio Firmware Load L122-F DVI Firmware Load Physical Breakdown of Software Green designates "gatherings" of loadable components Other hues show individual loadable components L1 Comms System Load L12 Audio Mgr. LRI Load L11 Transceiver LRI Load Loading level L11-L Application SW Load LRI SRI L11-F Firmware Load Chip DLCSPM - Canadian Software Support Seminar - April 1998 - DAPSCT

Slide 17

Software Categorisation A base arrangement of data ought to be gathered for Categorisation. This data ought to show the principle parameters that would influence programming Support (e.g., Operational Importance, Property Rights, Frequency of Change, and so forth) The aftereffect of the Categorisation ought to be a choice to: Note that Categorisation can be made on: - Functional Units - Physical Units - Both Not proceed with the Analysis Collect a base Data Set Explore all conceivable Support Alternatives Categorisation criteria are vital! An excessive amount of examination (costly) Too little investigation (lousy support) DLCSPM - Canadian So

Recommended
View more...