CS2013-final-report

• Explain why the creation of correct program components is important in the
production of high-quality software.
• Identify common coding errors that lead to insecure programs (eg, buffer
overflows, memory leaks, malicious code) and apply strategies for avoiding such
errors.
• Conduct a personal code review (focused on common coding errors) on a
program component using a provided checklist.
• Describe how a contract can be used to specify the behavior of a program
component.
• Refactor a program by identifying opportunities to apply procedural abstraction.
• Analyze the extent to which another programmer’s code meets documentation
and programming style standards.
• Apply consistent documentation and program style standards that contribute to
the readability and maintainability of software.
SE
Core-Tier1:
• List the key components of a use case or similar description of some behavior
that is required for a system.
• Describe how the requirements engineering process supports the elicitation and
validation of behavioral requirements.
• Interpret a given requirements model for a simple software system.
• Use a design paradigm to design a simple software system, and explain how
system design principles have been applied in this design.
• Within the context of a single design paradigm, describe one or more design
patterns that could be applicable to the design of a simple software system.
Core-Tier2:
• Discuss common behaviors that contribute to the effective functioning of a team.
• Create and follow an agenda for a team meeting.
• Identify and justify necessary roles in a software development team.
• Understand the sources, hazards, and potential benefits of team conflict.
• Apply a conflict resolution strategy in a team setting.
• Use an ad hoc method to estimate software development effort (e.g., time) and
compare to actual effort required.
• List several examples of software risks.
• Describe the impact of risk in a software development lifecycle.
• Describe different categories of risk in software systems.
• Describe the difference between centralized and distributed software
configuration management.
• Describe how version control can be used to help manage software release
management.
• Identify configuration items and use a source code control tool in a small teambased
project.
- 222 -