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

Flashcards

ENG1003

Katherine Moffat English 31 cards

Cards in this deck (31)

  1. 1Version controlPiece of software that tracks versions of files.
    -Allows to restore and review previous versions of software
    -Allows to work on files concurrently with others
    This is helpful for big projects and when you encounter bugs
  2. 2Storing data: cookiesCookies are data that is downloaded when you visit a website and are stored locally by browser.
    -Very small amounts of text
    -Have expiry
    This is not appropriate solution for web apps to store data
  3. 3Local storage-Browser can store up to 5MB of data per domain
    - Web domain and app must share same local storage in order for domain to support web app
    - Local storage is not transferred to a server (cookies are)
    - only supports key/string pair
  4. 4Cloud storageRemote server option for data server
    - Benefit is you can use on multiple devices
    - limited as they usually need internet connection
  5. 5Software development methodologies: AgileAgile: Design, implement and test something, then consult with client and repeat
    + Delivers something useful almost immediately
    + Requirements dont have to be nailed down at beginning
  6. 6software development methodology: WaterfallWaterfall: Requirements, design, implement, verify and maintain
    This method is not always appropriate for software building since assumes requirements are clear and less chance for changes to occur
    People prefer agile method
  7. 7Project management planA PMP is a document that is meant to be a good intro to a project including
    -Project info
    -Personnel
    -Decisions on process
    -communication management
    -quality management
    -risk management
  8. 8Requirement elicitationThe process of collecting requirements of a system from users, customers, and other stake holders.
    Important to note the language variance between clients and SE
  9. 9User storyAs a , I want [so that ]
    User story is a succinct description of what they want from a system.
    The client will choose user storied to be implemented next, they can also be annotated with time estimation
  10. 10Guide to production of user guide INVESTIndependent - Should be self contained only one feature being implemented
    Negotiable- Possible to revise later and produce same outcome
    Valuable - Beneficial to user
    Estimable - Need estimation of difficulty
    small - small enough feature to be schedules independently
    Testable - Can come up with a test to see if implemented satisfactorily
  11. 11KansanIn agile method a Kansan is a signboard that allows us to see implementation at a glance
    You will have to do, doing and one user stories
  12. 12BacklogA back log breaks down user stories into individual developer tasks. Prioritises tasks and assigns to developers
  13. 13Class diagramEasy to read visual representations of class system
    Explains the associations between classes and the attributes, methods and name of classes
  14. 14Cohesion and couplingAim to maximise cohesion and minimise coupling
    Cohesion: How conceptually related functionality is
    Coupling: Refers to dependency between classes. Classes ideally should be self contained and have minimal dependency
  15. 15Activity diagramAre used to document workflow and overall system behaviour. Like flow charts for software.
  16. 16Wire framesWire frames are sketches of user interface showing mock data. They are a skeletal view of an app. They are beneficial as they I’ve a sense of the user interface before any code is written
  17. 17Story boardsA sequence of user interface steps and connecting transitions used for stimulating interaction between screens
  18. 18Software testing: StaticCode review: Looking through code by eye and looking for errors
    Walkthrough: following a process and looking for problem cases. his can be done using the code or technical documentation.
  19. 19Dynamic testsTesting approaches that perform test on running code. This ranges from calling individual functions with specific input and checking return through to simulations gestures and taps of a user using an app
  20. 20Black box testingInvolves testing code while knowing what it is supposed to do but not how it does it. These are created directly from requirements since you are testing expected behaviour
    Oracles: Software specifications determined during requirement analysis
    These tests are done without seeing source code hence ‘black box’ = cant see inside
  21. 21White box testingTests are written knowing how the code works. Tests are written based on structure and design of code.
  22. 22Levels of testingUnit testing: Testing a portion/ unit of code usually a unit test tests a function or method of a class
    Integration testing: Examine the behaviour between two or more components of a system
    System testing: Involves testing the complete system to check it satisfies its requirements
  23. 23Coverage testingInvolves running a special tool that executes your app many times and as it does this it counts how many times each line of code is executed. Goal is to have 100% coverage
  24. 24Internet protocolsIP is responsible for the delivery of messages between devices. IP is the postal service of the internet
  25. 25NAT - network address translationNat lets pool of devices such as those in one house, share one IP address. Solves the problem of too many devices for the amount of IP addresses that exist.
  26. 26Domain namesDomain names provide more user friendly equivalents to IP addresses
  27. 27Donald Norman principleVisibility
    Affordable
    Constraints
    Cognitive aids
    Transfer effects
    Natural mapping
  28. 288 golden rules to interface design1) consistency
    2) universal usability
    3) offer informative feedback
    4) design dialog to yield closure
    5) prevent errors
    6) permit easy reversal of actions
    7) support internal locus of control
    8)reduce short term memory load
  29. 29Storage and memoryFrom fastest, smallest, expensive to slow, large and inexpensive
    Register
    Cache
    Ram
    Flash memory
    Hard disk
  30. 30Assembly languageAssembly language is a human readable form of low level machine code
  31. 31Interpreted languageLanguages where the instructions are interpreted and their actions performed by another piece of software which the interpreted software is running

Information

Description
Flashcards on ENG1003, created by Katherine Moffat on 28/05/2018.
Views
4
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?