GoConqr has a new look! Let us know what you think.

Flashcards

CE202

B O U Y B O Y English 34 cards

CE202

Cards in this deck (34)

  1. 1Types of Diagram and where they're usedTypes of Diagram and where they're used
  2. 2Static ModelsDescribe Structural Aspects
    • Class Diagrams
    • Package Diagrams
    •Type Diagrams
  3. 3Dynamic ModelsDescribe behavioural Aspects
    • Use Case Diagrams
    • Sequence Diagrams
    • Collaboration Diagrams
    • Activity diagrams
  4. 4UML Use-case diagrams• Specify only user views of essential system behaviour
    • Do not specify the flow of processes in the implementation
    • Box is the system boundary
    • Users are actors
    • Ovals inside are use cases
    • Lines to connect actors and use cases
    UML Use-case diagrams
  5. 5UML Class Diagram NotationUML Class Diagram Notation
  6. 6UML Package Diagram• Views system as small collection of packages
    • Each can be expanded to larger set of classes
  7. 7UML Collaboration DiagramUML Collaboration Diagram
  8. 8UML Pros• Industry standard
    • A standard of communication
  9. 9UML Cons• No well-defined semantics
    • Low level of abstraction
    • Little integration between sub-notations
  10. 10Waterfall• Requirements
    • Analysis
    • Design
    • Implementation
    • Testing
    • Deployment
  11. 11Things in Analysis Phase• Use Case
    • Type diagrams
    • Prototypes
    • Class diagrams
    • Interaction Diagrams
  12. 12Things in Design Phase• Prototypes
    • Class diagrams
    • Interation diagrams
    • Package Diagrams
  13. 13Things in Implementation• Coding
    • Unit Testing
    • Version Control
  14. 14Testing in Implementation• Integration testing
    • Unit testing
  15. 15Activity Diagram Notation 1Activity Diagram Notation 1
  16. 16Activity Diagram Notation 2Activity Diagram Notation 2
  17. 17Aggregation• Something is a part of something else
    • Empty diamond
  18. 18Composition• Something is completely a part of something else
    • If the larger thing is deleted so is the thing
    • Filled diamond
  19. 19Logical Design• Independent of the implementation
  20. 20Physical Design• Based on implementation and language to be used
  21. 21Qualities of Design• Secure
    • Flexible
    • General
    • Buildable
    • Manageable
    • Maintainable
    • Usable
    • Reusable
  22. 22Static Validation• Carried out without executing the program
  23. 23Dynamic Validation• Carried out by executing the program
  24. 24validatino Testing• Ensure the system meets client expectation
  25. 25Defect Testing• Detect defects
  26. 26White Box• Testing form inside the system
    • Concerned with internal structures
  27. 27Black Box• Testing from outside the system
    • Concerned with input/outputs
  28. 28Alpha Testing• Verification
    • Inputs and outputs
  29. 29Beta Testing• Validation
    • User environment
  30. 30performance Testing• Test the system performance
  31. 31Functinoal Testing• Conducted against functional specification
    • Test function
  32. 32Top-down testing• Start with high-level system
    • Go to individual components
  33. 33Bottom-up testing• Integrate individual components in levels until the complete system is created
  34. 34Concrete Class• Implements an abstract class or interface

Information

Description
Flashcards on CE202, created by B O U Y B O Y on 12/05/2019.
Created by
B O U Y B O Y
Views
3
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?