1
Q
Software Engineering
A
Study of using tools to make coding more efficient
2
Q
Characteristics of Software Engineering
A
- development of large programs
- evolution of a code base: involves documentation
- personnel management
- balance
3
Q
Process Model of Software Development
A
- Problem
through Requirements Engineering leads to - Requirements Specification through Design leads to
- Specification through Implementation leads to
- Program through Testing leads to
- Working Program which has Maintenance
4
Q
Problem
A
obstacle that gets in the way of an achievement
5
Q
requirements engineering
A
process of getting a complete description of the problem.
at the end of the engineering, a specification document is produced
6
Q
specification document
A
- function of the software
- possible future extensions
- documentation
- response time
7
Q
Problem Defining Process
A
1) Elicitation: figure out what the user wants
2) Speicifcation: use cases and scenarios to determine what is the best route for getting the want
3) Validation: review and go back and see if the solution came up with is a valid solution that meets clients needs
8
Q
Requirements Speicfication
A
decomposing problem into components or interfaces
- produces requirements specification document
9
Q
Requirement
A
what the customer needs in a software
10
Q
Types of Requirements
A
- Functional Requirement
- Nonfunctional Requirement
11
Q
Functional Requirement
A
specify what the software does
12
Q
Nonfunctional Requirement
A
specify the qualities of the software
13
Q
Requirements Specification Document
A
- problem definition
- functional requirements
- nonfunctional requirements
- resources
- data
14
Q
Nonfunctional requirements
A
- robustness: do when error occurs
- security: who has access
- safety: can it kill
- performance: constraints on performance
15
Q
Design
A
needs to solve the problem outlined in the requirements specification document
- create models to stimulate problem through architectural design
16
Q
architecture
A
- how components of a decomposed problem relate to each other
17
Q
Purpose of architecture
A
- communicate design
- capture early design decisions
- establish reusable abstract representation
18
Q
Types of Architecture
A
- Centralized (standard)
- Distributed
19
Q
Centralized Architecture
A
pipes and filters - takes a data stream of input and manipulates it
20
Q
Distributed Architecture
A
- uses shared repository with a central data store
21
Q
3 Layered Architecture
A
- Presentation
- Application Logic Layer
- Domain
22
Q
3 Layer Architecture: Presentation Layer
A
- receives user input and displays output
23
Q
3 Layer Architecture: Application Logic Layer
A
- calls to domain and decides what to show user
- Business Logic: process UI commands
- Data Access: allows us to interface with the domain
24
Q
3 Layer Architecture: Domain
A
remote database
25
documents from Design Phase
- design specification document
- user manual for the system
- system test plan
26
Software Implementation
use design to construct a solution to the problem
27
deliverables from software implementation phase
- program
- refined user manual
- refined test plan
28
4 types of software testing
- unit testing
- systemwide testing
- integration testing
- acceptance testing
29
Unit Testing
sending dummy values into functions
30
systemwide testing
reading what the program poops out at the end
31
integration testing
makes sure that all the components communicate with other another properly
32
acceptance testing
giving the program to the user and having them test it
33
General Kinds of Testing
- black box
| - white box
34
Black Box Testing
cannot see the source code, testing by putting in inputs and observing the outputs
35
White Box Testing
occurs when you are able to see the source codes
36
Deliverables from Testing
- working program
| - polished user manual
37
4 Types of Maintenance
- Corrective
- Adaptive
- Evaluative/Performance
- Preventative
38
Waterfall Process Model
- requirements -> specification -> design -> implementation -> testing -> maintenance
- does not take into account validation or verification
- rigid sequences that are rare in real life
39
Modified Waterfall Process Model
- same as the original, but includes validation and verification at every step
- if either come back negative, they go back to the previous step and revise
40
Agile Development
- emphasizes the ability to change course and have user involvement at every step
- encourages poor documentation
41
4 tenants of agile development
- individuals and interactions > tools and processes
- working software > documentation
- costume collaboration > contract negotiation
- responding to change > following a plan
42
Types of Agile Development
- prototyping
- rapid agile development
- dynamic systems development method
- extreme programming
43
Prototype process
- designing
- building a prototype
- user testing
- feedback
- refining
- user testing
44
Types of Prototyping
- evolutionary
- throw away
- incremental
45
Evolutionary Prototyping
- occurs when the prototype may evolve into the final product
- user gives programmer list of requirements and the programmer creates the prototype
- prototypes are tested, user comes back with more requirements
46
Throw-away Prototyping
- create prototype that will be discarded before designing final prototype
47
Incremental Prototyping
- allows features to be added and taken out slowly
48
Rapid Application Development (RAD) Stages
- requirements planning
- user design phase
- construction
- cut over
49
RAD Requirements Planning
- stage ends when everyone is happy with the requirements
50
RAD User Design Phase
- clients sitting with analysts and analysts send the info to the coders
51
RAD Construction
programming of the program
52
RAD Cut-Over
- finished project and users are trained on it
53
RAD time box
- x weeks to get something done
54
Dynamic Systems Development Methods (DSDM) phases
- feasibility study
- business study
- functional model iteration
- design and build iteration
- implementation
55
DSDM Feasibility Study
- asking, with clients, "is a solution possible", "can we come up with the solution", "is DSDM model appropriate"
56
DSDM Business Study
- solution employee friendly
57
DSDM Functional Model Iteration
- design prototype
58
DSDM Design and Build Iteration
- official system based off functional and nonfunctional requirements
59
DSDM Implementation
- deploy to userr
60
Extreme Programming (XP)
- goal is to have smaller increments of time in between prototypes with prototypes being delivered to client as soon as possible
61
XP Core Principles
- rapid feedback
- simplicity
- incremental change
- embracing change
- quality work
62
Scrum Sprints
individual time boxed goals
63
Scrum Pomodoro Method
- don't work on anything for too long
64
Scrum concepts
- product backlog
- sprint backlog
- increment/sprint goal
65
Scrum Product Backlog
- master list of work that needs to be done
66
Scrum Sprint Backlog
- list of items selected for implementation
67
Scrum Increment/Sprint Goal
- goal to complete in timeframe given
68
Scrum Steps
- product back log organized by product owner
- sprint planning meeting where team decides on sprint goal
- daily scrum - daily meeting to check on progress
- sprint review - after sprint happens and involves show and tell
- sprint retrospective - involves discussions of doing better
69
Classifications of Software Engineering Qualities
- External vs Internal
| - Product vs Process
70
External vs Internal
- where product is visible
- external is visible to the user and is verified during run time
- internal is invisible to the user and concerns only the developer
71
Product vs Process
- performance of a product vs productivity of a process
CS 372
flashcards
Decks in class (1)
# Cards
