Applying UML to TestStand and LabVIEW

Similar presentations

1 Applying UML to TestStand and LabVIEWMatthew KennedyEngineering ManagerTitle Slide GuidelinesTitle Slide should be in Arial Narrow and always 38 point BOLD. This section contains the title of the presentation (consequently, the presentation file should be saved as the SAME name of the title).There should be a space between the Title and the Presenter Name.The next text should be Arial Narrow and always 32 point NORMAL. This line contains the presenters name and title if they choose.The last line (s) should still be Arial Narrow and always 32 point NORMAL. These line/lines can reflect the presentation date, time, room, etc.

2 Software project problems Why UML? AgendaSoftware project problemsWhy UML?Useful UML tools for TestStand and LabVIEWConclusionResources* This is not a UML course. Just not enough time.Slide Page and Graphic GuidelinesThe Slide Title can be 36 point or 32 point (but never smaller), and always BOLD.The Slide Title should not be underlined or italicized.The body of the slide should follow the above format with regards to size and bullet format.The body CAN be emphasized in anyway you need it to be (bold, italics, underline, and so on).Total text area should be limited to the space defined by the ruler guides (click on the slide and you should see a dotted line top, bottom and sides.)Graphics belong below the major text, not above it. (Captions may be below the graphics).Graphics go to the right of the body text.COLOR- Select colors that are darker and not muted, do not use yellow, orange, or other light colors for important information. Keep in mind this needs to show when printed in black and white.Do not use colors to “define” something in the text. You will not be able to match the color definition when printing in black and white.

3 Software Project ProblemsSoftware functionalityRequirements definitionEnd users and programmers exist in different worlds and speak different languagesRequirements get lost or misunderstoodSoftware programmers don’t have clear requirements, skip design, and go straight to code developmentSlide Page and Graphic GuidelinesThe Slide Title can be 36 point or 32 point (but never smaller), and always BOLD.The Slide Title should not be underlined or italicized.The body of the slide should follow the above format with regards to size and bullet format.The body CAN be emphasized in anyway you need it to be (bold, italics, underline, and so on).Total text area should be limited to the space defined by the ruler guides (click on the slide and you should see a dotted line top, bottom and sides.)Graphics belong below the major text, not above it. (Captions may be below the graphics).Graphics go to the right of the body text.COLOR- Select colors that are darker and not muted, do not use yellow, orange, or other light colors for important information. Keep in mind this needs to show when printed in black and white.Do not use colors to “define” something in the text. You will not be able to match the color definition when printing in black and white.

4 Minimize Software Project Cost“Just complete the software THEN fix it.”Three simple rules:State requirementsCreate system designCode to the designUnitsStage.1-.2Requirements.5Design1Coding2Unit test5Acceptance test20MaintenanceSlide Page and Graphic GuidelinesThe Slide Title can be 36 point or 32 point (but never smaller), and always BOLD.The Slide Title should not be underlined or italicized.The body of the slide should follow the above format with regards to size and bullet format.The body CAN be emphasized in anyway you need it to be (bold, italics, underline, and so on).Total text area should be limited to the space defined by the ruler guides (click on the slide and you should see a dotted line top, bottom and sides.)Graphics belong below the major text, not above it. (Captions may be below the graphics).Graphics go to the right of the body text.COLOR- Select colors that are darker and not muted, do not use yellow, orange, or other light colors for important information. Keep in mind this needs to show when printed in black and white.Do not use colors to “define” something in the text. You will not be able to match the color definition when printing in black and white.1 unit=Effort required to detect and repair a error during coding

5 UML can help software programmers and project engineers to:Where Does UML Come In?UML can help software programmers and project engineers to:Define customer requirementsCreate basic designsSet of notation and meta-model language toolsDefined notationApplicable to many programming languagesMakes programmers put pencil to paper and diagram/plan systemsSlide Page and Graphic GuidelinesThe Slide Title can be 36 point or 32 point (but never smaller), and always BOLD.The Slide Title should not be underlined or italicized.The body of the slide should follow the above format with regards to size and bullet format.The body CAN be emphasized in anyway you need it to be (bold, italics, underline, and so on).Total text area should be limited to the space defined by the ruler guides (click on the slide and you should see a dotted line top, bottom and sides.)Graphics belong below the major text, not above it. (Captions may be below the graphics).Graphics go to the right of the body text.COLOR- Select colors that are darker and not muted, do not use yellow, orange, or other light colors for important information. Keep in mind this needs to show when printed in black and white.Do not use colors to “define” something in the text. You will not be able to match the color definition when printing in black and white.

10 Use Cases – Final ThoughtOf all UML tools, use cases are arguably the most importantKey to ensure a successful requirements stageActors are not always easy to identifyActor could be the test system itself, a sequence, etc.Meant to be simple but detailed enough to manage project scope

11 Stage 2: Design Sequence diagram Activity diagram State diagramDescribes how groups of objects or processes behave in a sequential and concurrent mannerTypically defines a single use caseActivity diagramA state of doing somethingDescribes sequence of activityState diagramDescribes all possible states that can occur in a system

15 Software design must be implemented Obvious implementationsStage 3: CodingSoftware design must be implementedObvious implementationsState diagrams: LabVIEW state machinesSequence diagrams: TestStand sequenceLabVIEW dataflow programmingSequence structuresActivity diagrams: LabVIEW state machinesTestStand sequencesUsing a state diagram does not mean you must use a LabVIEW state machine

16 Isn’t UML just another flowchart? Widely accepted standard Fancy Flowcharts?Isn’t UML just another flowchart?Widely accepted standardIntuitive to useMany end users already have familiarity with UMLInstantly start talking the same languagePlenty of resources to helpFlowcharts and more with standardized notation

19 Keep use cases detailed Lessons LearnedKeep use cases detailedAvoid using language-specific information of software design in use casesUse swimlanes with activity diagrams to assist in modularizing TestStand sequence developmentFinish state machine diagram before writing LabVIEW codeUse only what you needUnnecessary to use every diagram tool to adequately design a software system

20 ConclusionUML is an industry-accepted standard for developing software architecturesMore and more people are becoming aware of the benefits of using UMLUML is an excellent tool for developing LabVIEW and TestStand architectures BEFORE codingUse appropriate UML toolsUML can save time and money by preventing costly rework