Final Exam: Programmer - apply architectural design
- apply component level design
- apply good coding practices
- apply good programming in Java
- apply good programming in JavaScript
- apply good programming in Python
- apply integration testing
- apply modular design
- apply pattern based design
- apply regression testing
- apply resiliency design
- apply software metrics
- apply specific UML diagrams including class, activity, use case, and sequence diagrams
- apply testing methodologies
- apply the IEEE Std 730 standard for software quality
- apply unit testing
- apply user acceptance testing
- define basic programming & software engineering concepts
- describe and apply testing methodologies
- describe bug tracking concepts
- describe modular design
- describe resiliency design
- describe software verification and validation
- describes roles and responsibilities in testing
- describe the quality and the change management process
- describe unit testing
- identify architectural design
- identify bad JavaScript programming
- identify IEEE programming standards including general, testing and quality, and maintenance and documentation standards
- identify requirements gathering techniques such as brainstorming, interviews, focus groups, and reverse engineering
- identify software design concepts
- identify software requirement types, the FURPS model, and methods for gathering requirements
- identify the Unified Modeling Language
- identify user acceptance testing
- implement good coding practices
- implement good programming in Java
- implement good programming in JavaScript
- implement good programming in Python
- implement unit testing
- perform software estimation of resources and time
- recall IEEE and ISO programming standards
- recall IEEE programming standards including general, testing and quality, and maintenance and documentation standards
- recall IEEE programming standards including NIST SP 800-27, ISO/IEC 15504 and 24744:2014, and ISO 29110
- recognize bad Java programming
- recognize bad JavaScript programming
- recognize bad Python programming
- recognize component level design
- recognize IEEE and ISO programming standards
- recognize IEEE programming standards including general, testing and quality, and maintenance and documentation standards
- recognize model driven design
- recognize software design concepts
- recognize the Unified Modeling Language
- recognize well designed Java code
- recognize well-designed JavaScript
- recognize well designed Python code
- specific testing methods
- understand test cases and reporting
- use bug tracking methods
- use specific UML diagrams
- use specific UML diagrams including class, activity, use case, and sequence diagrams
|
