SWE Exam 1 - Questions Given

Software engineering ethics. There are areas where standards of acceptable behavior are not bound by laws, but more of professional responsibility. One of the ethics software engineers should be aware of is intellectual property rights. What are intellectual property rights?

• Software engineers should not knowingly accept work that goes beyond their competence

• Legal power given to an inventor or a creator to protect his/her invention. Such as patents, copyright, etc.

• Using technical skills to misuse others computers

• Respect the confidentiality of their employers or clients irrespective of whether or not a formal confidentialiy agreement has been signed.

• None of the above

• Requirements analysis and definition

• System and software design

• Implementation and unit testing

• Integration and system testing

• Operation and maintenance

• Software that is commissioned for specific customer needs

• Software that is developed to maintain the hardware in a specific factory

• Software made for any customer who wants to buy it

• Banking app made for a specific bank to manage its internal activities

• Requirements may be compromised due to reusable components not having everything the user needs

• Being able to deliver the software faster

• Loss of control over evaluation due to reused elements belonging to another company

• The programmers having to start writing new codes from scratch

• None of the above

What is extreme programming

• Because they can't deliver software fast enough

• Having the development team in the same location

• The whole team attends short daily meetings

• Hard to track the backlog to find the work that needs to be done

• Original developers will not stay at the same job

• Come up with a potentially shippable product

• Discuss the progress of the project and what has been done

• Estimate of how much of the product backlog the team can cover

• Prioritizes work to be done on that day

• Interview uses of the system

• Develop the system

• Refactoring

• Observe the existing system

• Improve reliability of the system

Functional requirement examples

• Allow login and sign up for a new account

• Pretty colors

• View account balance

• Transfer funds and pay bills

• Efficient login speed

Non-functional requirement examples (product, organizational, and external)

• Login within 4 seconds

• MySQL database from bank

• Login/sign up ability

• Accessible to people with disabilities