quartz/content/notes/20-SE-in-IA.md

title	aliases	tags	sr-due	sr-interval	sr-ease
20-SE-in-IA		comp210 lecture	2022-10-13	3	250

why

• apps for IoT devices contain security flaws
  • smart home security breaches
  • kindles
  • vulnerable libraries lead to vulnerable devices
• software helps us to use hardware
  • need to make the software secure

overview

combines computer science, engineering, and maths to make software

• software engineering coined in 1968-1969 when discussing 'software cirsis'
  • security breaches
  • bugs etc

different from individual programming because of the Audience

• types
  • generic software
    • stand alone systems e.e.g, word etc
  • customized software
    • designed specifically for a customer
  • generic can transistion to customised

dev process

• tried to mirror engineering process
• software is different
  • needs to be flexible

timeline

• waterfall
• spiral
• agile

stages

design

• feasability
  • 
  • financial, legal, time, etc
• requirements specification
  • stakeholders
    • anyone affected by the system
    • 
  • features, requirements
    • 
    • 
    • 
• system design
  • 
  • databse design
    • er model etc
  • architectural design
    • structure of application
    • 
      • view model controller
  • security
    • during development not after

develop

• 
• version control
  • 
  • 
• issue tracking
  • keep track of tasks, bugs, feature requests etc
• unit testing
• code reviewing

validation

• checking if system conforms to specs
  • unit testing
  • component testing
  • system testing
  • user acceptance testing (UAT)
    • 
    • finds issues that devs dont see
• 
• code reviews
  • better than one single person
  • different perspectives

evolution

• new requirements derived through software use
• change in business processes occur as a result of new business opportunities
• errors in software surface later
• upgrade to new hardware,
• need for improved system performance

for Information assurance

• security should be central
• think of security every step of the way
• code resure and (SDKs) should be critically evaluated
  • often flaws are inherited from reused llibraries or copied online code
• where are the security knowledge gaps
  • use tools to detect vulnerabilities