Skip to content

Commit 18d4edc

Browse files
gflazgflaz
authored
Merge pull request #13 from mutable-learning/dev
Finish Software Development notes
2 parents 009b6d1 + 1365039 commit 18d4edc

30 files changed

Lines changed: 437 additions & 18 deletions

‎assets/physical_security_zones.png‎

373 KB
Loading

‎pages/Analysing Iterative Algorithms.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ algo:: Unit 4 Outcome 1
3030
- is the term that grows the fastest as the size of the input grows
3131
- for example, the dominant term in the [[Time Complexity]] of bubble sort is $n^2$
3232
- the number of comparisons grows quadratically as the size of the input grows
33-
- Use Big $O$ notation to express the [[time complexity]]
33+
- Use Big $O$ notation to express the [[Time Complexity]]
3434
- use Big $O$ notation to express the time complexity of the algorithm
3535
- for example, the time complexity of bubble sort is $O(n^2)$
3636
- Here are some additional tips for determining time complexity of iterative algorithms:

‎pages/Analysis Actions.md‎

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,12 @@ softdev:: Unit 3 Outcome 2
55
-
66
- detail the problem or need as part of the [[Analysis Stage]] of the [[Problem-solving Methodology]]
77
- examine how [[Organisational and System Goals]] along with [[Organisational and System Objectives]] impact a solution
8-
- recognize the importance of creating a [[Software Requirement Specification]]
98
- examine different tools to enable [[Data Collection]]
10-
- decide what will be and won't be a part of the [[Solution Scope]]
11-
- understand the difference between [[Functional Requirements]] and [[Non-functional Requirements]] that will make up the [[Solution Requirements]]
9+
- create a [[Design Brief]]
10+
- recognize the importance of creating a [[Software Requirement Specification]]
11+
- decide what will be and won't be a part of the [[Solution Scope]]
12+
- understand the difference between [[Functional Requirements]] and [[Non-functional Requirements]] that will make up the [[Solution Requirements]]
13+
- analyse the requirements and scope to determine any impacts or needs imposed by [[Solution Constraints]]
1214
- depict interfaces between solutions, users and networks using tools such as a [[Use Case Diagram]], a [[Data Flow Diagram]] and a [[Context Diagram]]
1315
- select a [[Development Model]] from choices including the [[Waterfall Model]], [[Agile Model]] and [[Spiral Model]]
1416
-

‎pages/Backup and Recovery.md‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,4 +37,7 @@ softdev:: Unit 4 Outcome 1
3737
- check that backups are correctly made regularly
3838
- have a clear set of instructions for restoring systems from backup
3939
- periodically run the restoration process in an environment that resembles the live one as closely as possible
40-
- make sure backup media is protected from loss, damage and is stored securelylo
40+
- make sure backup media is protected from loss, damage and is stored securely
41+
- consider carefully where backups are stored
42+
- impacts on the recovery process
43+
- resistance to ((65718797-21ee-420b-b49d-befd0c9e975f))

‎pages/Data Integrity.md‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
tags:: Software Development
2+
topic:: [[Security Strategies]]
3+
softdev:: Unit 4 Outcome 2
4+
5+
-
6+
- secure systems ensure that confidentiality, integrity and availability are maintained
7+
- Threats to Data Integrity
8+
id:: 65718797-21ee-420b-b49d-befd0c9e975f
9+
- Accidental
10+
id:: 65718797-7672-45da-bb63-2c6c4aa27597
11+
- users accidentally damage systems
12+
id:: 65718797-df32-4efc-a1ef-5f2494f66da5
13+
- poor interfaces
14+
- lack of training
15+
- inappropriate permissions
16+
- user inattention or carelessness
17+
- modifications of data are too easy to make
18+
- Event-based
19+
id:: 65718797-1f10-4fb9-898b-05d0fe33150a
20+
- hardware failure, such as storage
21+
- power failure
22+
- file corruption
23+
- third-party software issues
24+
- acts of nature such as fire, floods or a lightning strike
25+
- Deliberate
26+
id:: 65718797-cd9d-42f0-8279-a3ee06ce164b
27+
- an attack is made on the system or data through [[Malware]], [[Social Engineering]] or other [[Security Vulnerabilities]]
28+
- Characteristics of Data Integrity
29+
- Accuracy
30+
- Content
31+
- Correctness
32+
- data is entered correctly, such as correct birthdate, name spellings
33+
- Completeness
34+
- the entire data set is intact
35+
- Form
36+
- Clarity
37+
- data is formatted to avoid misinterpretation
38+
- using ISO date formats, for example
39+
- Consistency
40+
- data within a system and the same data stored in multiple systems is consistent
41+
- if not consistent, which data is 'accurate'?
42+
- Authenticity
43+
- comes from the source it is known to be from
44+
- has not been corrupted or changed
45+
- is not faked or disguised as something else
46+
- Reasonableness
47+
- the data meaning is consistent with the values
48+
- meaning is determined by understanding the acceptable extent of the data
49+
- dates are within a range
50+
- ages are consistent
51+
- possibility of data occurring, such as playing so many games within a time period
52+
- Relevance
53+
- data is appropriate for the use it is being applied
54+
- Timeliness
55+
- data must be processed while it is current
56+
- processing must complete before the data is actually needed
57+
- a machine alerts that the patient's heartbeat has stopped five minutes after it actually stopped
58+
- Failure to protect Data Integrity
59+
- can result in prosecution and/or penalties
60+
- loss of business and reputation
61+
- normal business can be seriously disrupted
62+
- trade secrets can be stolen and sensitive information, such as encryption keys, may be stolen
63+
- business severely impacted may no longer be able to operate

‎pages/Design Brief.md‎

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,15 @@
1-
- [[Testing]]
1+
tags:: Software Development
2+
topic:: [[Analysis Stage]]
3+
softdev:: Unit 3 Outcome 2
4+
5+
-
6+
- document or statement that outlines the nature of the problem, opportunity or need
7+
- describes in brief
8+
- processes
9+
- systems
10+
- users
11+
- contains an initial overview of
12+
- [[Solution Requirements]]
13+
- [[Solution Constraints]]
14+
- [[Solution Scope]]
15+
- is used as the initial starting point for the [[Software Requirement Specification]]

‎pages/Economic Constraints.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
tags:: Software Development
2+
topic:: [[Analysis Stage]]
3+
softdev:: Unit 3 Outcome 2
4+
5+
-
6+
- include **time** and **cost**
7+
- a lack of time and/or a lack of money mean re-evaluating how requirements in the [[Solution Requirements]] can be met
8+
- the project deadline will define the time available for the solution
9+
- time spent on a project is an economic measure
10+
- funds available impacts aspects of the solution available
11+
- number and range of staff
12+
- hardware and software available
13+
- even purchasing data or 3rd party assistance from other companies

‎pages/Ethical Software Development.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
tags:: Software Development
2+
topic:: [[Ethical and Legal Considerations]]
3+
softdev:: Unit 4 Outcome 2
4+
5+
-
6+
- software can have intended and unintended negative effects, impacting people's rights
7+
- consider the real and potential negative effects and remove or reduce these as much as possible
8+
- ethical considerations are different from legal considerations, but they often go together
9+
- they are both concerned with societal good
10+
- as part of the [[Risk Management Plan]], ethical and social issues should be identified and assessed
11+
- new issues may increase after a solution has been in use for a period of time, leading to conflict between users and developers
12+
- collection and use of private information
13+
- copying software (for backup)
14+
- ergonomics of using the solution
15+
- bias and accountability
16+
- developers must account for ethical issues when building solutions, balancing these with legal requirements and the business requirements
17+
- avoid unethical practices
18+
- adding backdoors
19+
- monitoring users excessively
20+
- including malware
21+
- promoting discriminatory features and content

‎pages/Ethical Software Use.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
tags:: Software Development
2+
topic:: [[Ethical and Legal Considerations]]
3+
softdev:: Unit 4 Outcome 2
4+
5+
-
6+
- respect intellectual property and [[Copyright Act 1968]]
7+
- follow the license terms for the software
8+
- pay for the right to use commercial software
9+
- respect the restrictions of the license for open source software
10+
- don't try to circumvent security measures put in place to protect the copyright of software
11+
- cracked software
12+
- de-compiling code to see the source
13+
- removing watermarks

‎pages/Ethical and Legal Considerations.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ softdev:: Unit 4 Outcome 2
44

55
-
66
- why do individuals and organisations develop software and the idea of [[Ethical Software Development]]
7+
- software may not be available for purchase or may need customisation
8+
- custom software is needed to meet the [[Organisational and System Goals]] and the [[Organisational and System Objectives]] of an organisation
79
- considerations about [[Ethical Software Use]] after a solution has been created
810
- impacts of the legislation that affects the collection, storage and communication of data
911
- [[Copyright Act 1968]]

0 commit comments

Comments
 (0)