Reference no: EM13903580

In your own words, define and discuss the terms cohesion and coupling. Both terms can be measured against a spectrum or range (from "low" to "high"): for each of these terms, describe the advantages and/or disadvantages as the range is traversed. How do these concepts relate to the design and implementation of programs in an object-oriented environment? Use your knowledge of Java and other OO languages to reinforce your answer. (length: minimum ½ page)

The definition of the term quality in software engineering depends on who is defining the term. Provide two definitions of "quality": as it is defined in engineering disciplines in general, and as it is defined by a client in a software engineering project. Discuss the differences in the definitions: include the terms validation and verification in your discussion, relating both terms to each definition. (length: minimum ½ page)

In general, open source software can be downloaded, compiled, installed, and executed for free, making it appear to many to be an attractive alternative to licensed software. Compare the pros and cons of open source vs. licensed software across all stages of the software lifespan. (length: minimum ½ page)

There are many software "tools" available to make software development more efficient and effective, each tool falling into one or occasionally multiple categories. One specific category is code analysis tools. Define and discuss what code analysis is, then elaborate on how the availability and integration of code analysis tools in IDEs affects:
short-term efficiency (detecting existing problems) (length: minimum ? page)

long-term efficiency (minimizing the likelihood of future problems) (length: minimum ? page)

One aspect of the process of "testing" software is determining the behavioral properties that are to be evaluated. Classically, the properties are correctness, utility, reliability, robustness, and performance. Discuss each of these properties. (length: ¾ page, maximum 1 page)

Discuss the objectives and expected outcomes of the requirements workflow of systems development. What activities are associated with this workflow (be thorough!)? How can requirements be tested? One particular technique discussed was prototyping of GUIs: discuss this technique in the overall context of the requirements workflow and explain its potential benefits and pitfalls. (length: minimum ¾ page, maximum 1 ½ page)

Scenario: you have been invited to interview for a software developer position and have been talking to various people for the past four hours, ranging from human resource personnel to multiple project managers. Your current interviewer, the head of the software engineering area, asks you to react to the statement "increment and iterate" and "agile" are nothing more than two labels for the same process model. She follows up by saying that her decision on recommending you forward to the final stage of interviewing hinges on your answer, so you should take your time and be thorough with your answer. She then sits back and waits... ( length: minimum 1 page, maximum 2 pages)