mirror of
https://github.com/jackyzha0/quartz.git
synced 2026-03-24 15:05:42 -05:00
vault backup: 2022-10-10 10:57:45
This commit is contained in:
parent
ed79f5fc5a
commit
91d508e64e
@ -4,6 +4,9 @@ aliases:
|
|||||||
tags:
|
tags:
|
||||||
- comp210
|
- comp210
|
||||||
- lecture
|
- lecture
|
||||||
|
sr-due: 2022-10-13
|
||||||
|
sr-interval: 3
|
||||||
|
sr-ease: 250
|
||||||
---
|
---
|
||||||
|
|
||||||
# why
|
# why
|
||||||
@ -42,30 +45,64 @@ timeline
|
|||||||
- agile
|
- agile
|
||||||
|
|
||||||
# stages
|
# stages
|
||||||
- design
|
## design
|
||||||
- feasability
|
- feasability
|
||||||
- 
|
- 
|
||||||
- financial, legal, time, etc
|
- financial, legal, time, etc
|
||||||
- requirements specification
|
- requirements specification
|
||||||
- stakeholders
|
- stakeholders
|
||||||
- anyone affected by the system
|
- anyone affected by the system
|
||||||
- 
|
- 
|
||||||
- features, requirements
|
- features, requirements
|
||||||
- 
|
- 
|
||||||
- 
|
- 
|
||||||
- 
|
- 
|
||||||
- system design
|
- system design
|
||||||
- 
|
- 
|
||||||
- databse design
|
- databse design
|
||||||
- er model etc
|
- er model etc
|
||||||
- architectural design
|
- architectural design
|
||||||
- structure of application
|
- structure of application
|
||||||
-
|
- 
|
||||||
- develop
|
- view model controller
|
||||||
- validaion
|
- security
|
||||||
- evolution
|
- during development not after
|
||||||
|
|
||||||
may go by different names
|
## 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
|
# 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
|
||||||
|
-
|
||||||
14
content/notes/21-SE-in-IA-2.md
Normal file
14
content/notes/21-SE-in-IA-2.md
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
title: "21-SE-in-IA-2"
|
||||||
|
aliases:
|
||||||
|
tags:
|
||||||
|
- comp210
|
||||||
|
- lecture
|
||||||
|
---
|
||||||
|
|
||||||
|
# need in all phases
|
||||||
|
- often overlooked in feasability stages
|
||||||
|
- security requirements not defined
|
||||||
|
- built without thinking about security
|
||||||
|
- tests do not take security into account
|
||||||
|
- without security evolution can become cumbersome
|
||||||
@ -39,4 +39,6 @@ No final exam
|
|||||||
- [16-cloud-security](notes/16-cloud-security.md)
|
- [16-cloud-security](notes/16-cloud-security.md)
|
||||||
- [17-ML-in-IA-1](notes/17-ML-in-IA-1.md)
|
- [17-ML-in-IA-1](notes/17-ML-in-IA-1.md)
|
||||||
- [18-ML-in-IA-2](notes/18-ML-in-IA-2.md)
|
- [18-ML-in-IA-2](notes/18-ML-in-IA-2.md)
|
||||||
- [19-deepfakes](notes/19-deepfakes.md)
|
- [19-deepfakes](notes/19-deepfakes.md)
|
||||||
|
- [20-SE-in-IA](notes/20-SE-in-IA.md)
|
||||||
|
-
|
||||||
Loading…
Reference in New Issue
Block a user