Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
35 Cards in this Set
- Front
- Back
|
3 types of readers of software engineering documents
|
management, users/customers, developers/testers/maintainers
|
|
|
3 components and software types of the semester project
|
student submission - transactional, assignment collection - batch processing, web ui - interactive/transactional
|
|
|
define cognitive ergonomics and how it's important to software engineering
|
making things easy to use, minimizing strain on users
|
|
|
POST
|
creates a new resource under the source of the given URI
|
|
|
GET
|
retrieves data
|
|
|
DELETE
|
delete resource
|
|
|
PUT
|
update resources with an existing URI
|
|
|
3 primary concepts expressed in an ERD
|
entities, relationships, attributes
|
|
|
5 characteristic goals in software engineering
|
maintainability, dependability, security, efficiency, acceptability/compatibility
|
|
|
penetration testing
|
finding security weakenesses
|
|
|
unit testing
|
testing program components at the smallest functional unit
|
|
|
integration testing
|
testing program components integrate and interact as expected
|
|
|
regression testing
|
did the latest bug fix or enhancement cause a regression in the software
|
|
|
user acceptance testing
|
quality assurance, final testing before release
|
|
|
scalibility testing
|
how does the system handle the increased user or data load?
|
|
|
corrective maintenance
|
fix bugs or erroneous behavior
|
|
|
adaptive maintenance
|
adapt to changes in the operational environment of the software
|
|
|
perfective maintenance
|
functional/operational enhancements
|
|
|
preventative maintenance
|
increase life-span of software
|
|
|
refactoring
|
restructuring of existing code without changing its external behavior
|
|
|
3 types of project management
|
traditional, process-based, agile
|
|
|
agile software development
|
founded on a process view of human collaboration. composed of test-driven development, rapid application development, and scrum.
|
|
|
agile vs waterfall
|
waterfall: linear/sequential approach, testing happens at end of process
agile: iterative approach, testing happens throughout process |
|
|
engineering
|
application of scientific, economic, social, and practical knowledge in order to design, build and maintain structures, machines, devices, systems, materials, and processed
|
|
|
software
|
computer programs and related documentation
|
|
|
software engineering
|
engineering discipline that is concerned with all aspects of software production
|
|
|
4 concepts of OOD
|
encapsulation, polymorphism, inheritance, abstraction
|
|
|
model
|
data and supported actions of the data
|
|
|
view
|
user interface. informs controller of user input
|
|
|
controller
|
logic. interact with data models and directs views
|
|
|
functional requirement
|
details of the services the software must provide. project: students must be able to submit from babbage
|
|
|
non-functional requirement
|
constraints on the functionality of the software. project: must adhere to FERPA
|
|
|
4 steps of requirements analysis
|
discover, classify and organize, prioritize, specify
|
|
|
4 types of maintenance
|
corrective, adaptive, preventative, perfective
|
|
|
6 types of testing
|
regression, scalability, user acceptance (QA), integration, penetration, unit
|
