Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Software Eng > Book 1 > Flashcards

Book 1 Flashcards

1
Q

Important aspects of software

A
  • Malleability
  • Complexity
  • Size
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Three layered architecture

A
  • Presentation
  • Application Domain
  • Infrastructure
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Development of software

A
  • Domain modelling
  • Requirements
  • Design
  • Implementation
  • Testing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Domain modelling

A
  • Understanding environment in which system may be introduced
  • Business processes and rules
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Requirements

A
  • Requirements elicitation

- Requirements analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Design

A
  • Determining how you will solve problem
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Implementation

A
  • Acting upon decisions made at design stage
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Testing

A
  • Testing what you have done so you can determine if you have solved problem
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Waterfall model

A
  • Work through ADIT only once
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Iteration and incremental development

A
  • Do small iterations (timeboxed)

- Adds complexity till final product reached

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Agile

A
  • Light-weight, faster development
  • Adapts to changes in customer requirements
  • People and working software at forefront
  • Delivers quicker working software
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Scrum

A
  • Form of agile
  • The sprint - Development phase, no longer than a month
  • Sprint planning meeting - Last no more than 8 hours
  • Daily scrum - Daily meeting of 15 mins
  • Product backlog - List of things still to do
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Spiral process

A
  • Determine objectives, alternatives and constraints
  • Evaluate objectives, identify and resolve risks
  • Develop and verify (partial) solution
  • Review solution and plan activities for next iteration
  • Repeat
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Structural (static) models

A
  • Describe objects in real world

- Describes their relationships to other objects

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Behaviour (dynamic) models

A
  • Describe behaviour in real world of system over time
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Unified Process (UP)

A
  • Popular OO IID process agile development
17
Q

UP organisation

A
  • Inception
  • Elaboration
  • Construction
  • Transition
18
Q

Views in UP

A
  • Use case view
  • Logical view
  • Implementation view
  • Deployment view
  • Process view
19
Q

Domain modelling

A
  • Glossary
  • Problem statement
  • Business process
  • Business rules
  • Domain structural model
20
Q

Requirements

A
  • Glossary
  • Problem statement
  • Use case model
  • Elaborated use cases
  • FR and NFRs
21
Q

Analysis

A
  • Glossary
  • System operations
  • Analysis structural model
22
Q

Design

A
  • Glossary
  • Behaviour model
  • Design structural model
23
Q

Requirements

A

Need to be:

  • Necessary and traceable
  • Non-ambiguous and realistic
  • Complete
  • Consistent
  • Verifiable and validated
24
Q

Requirements engineering process

A
  • Requirements elicitation
  • Requirements analysis and negotiation
  • Requirements documentation
  • Requirements validation
25
Q

Requirements elicitation

A
  • Identify requirements

- consult stakeholders, read documents, understand domain

26
Q

Requirements analysis and negotiation

A
  • Requirements categorised, prioritised and examined

- Involves negotiations around conflicting interests and requirements

27
Q

Requirements documentation

A
  • Usually done through template document
28
Q

Requirements validation

A
  • Careful check of overall requirements doc
29
Q

NFR’s

A
  • Look and feel
  • Usability and humanity requirements
  • Performance requirements
  • Operational and environmental requirements
  • Maintainability and support requirements
  • Cultural requirements
  • Legal requirements
  • Security requirements
30
Q

Security requirements

A
  • Access
  • Privacy
  • Integrity
  • Audit
  • Immunity
31
Q

Verification

A
  • Ensures solution being correctly developed
32
Q

Validation

A
  • Ensures what is being built satisfies business
33
Q

Use case diagram

A
  • Actors (Stick figures)
  • Use cases (Ovals)
  • Relationships/associations (lines)
  • System boundary (Box round boundary of use cases)
34
Q

Use case description

A
  • Identifier and name
  • Actor initiating use case
  • Short description on goal
  • Single sequence of steps describing main success scenario
  • Textual description of pre and post conditions
35
Q

Agile modelling practices

A
  • Follow iterative and incremental approach
  • Use models effective in team work and communication
  • Model with simplicity in mind
  • Think about how you can test what you model
36
Q

Use cases relationships

A
  • Inclusion - Two or more use cases have common overlapping functionality
  • Extension - Use case has main scenario and alternative scenarios

Software Eng (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions