Quiz #1 covered chapters 1 and 4 in the text book. The solutions below are culled from student quizzes and are examples of "good" answers to the questions. Some of the questions may have alternate answers, so this page is intended as a guide and does not represent the only definitive solutions.
Grade Scale|
This quiz was worth 5 points total: 1 point per question, with
There were 6 questions in all and students had the option of either choosing 5 of the 6 questions to answer or answering all 6, in which case the lowest scoring answer was dropped. Letter grades were assigned according to this table. |
|
Software Engineering is concerned with process and planning in order to manage software development. The activities of SE include modeling, problem solving, knowledge acquisition and rationale management. SE is useful because it helps us to manage the complexity of the software development process.Question #2: What is the purpose of modeling?
The purpose of modeling is to create an abstraction of a system (or part of a system) which allows us to deal with complexity by focusing on the relevant details while ignoring those which are irrelevant.Question #3: What is the difference between a method and a methodology?
A method is a repeatable set of steps to solve a problem. A methodology is a collection of methods to solve a class of problems.Question #4: Give 2 reasons why requirements elicitation is difficult.
Clients must describe the requirements of a system but are usually not familiar with the software development process (solution domain). Software engineers must understand the requirements but are often not familiar with the clients' area of expertise (problem domain).Question #5: Define and give an example of a non-functional requirement.
Non-functional requirements describe user-visible aspects of the system which are not directly related to functional behavior of the system. Common examples of non-functional requirements include performance considerations such as response time, quality issues such as reliability, and hardware considerations such as the platform on which the system must operate.Question #6: What is the difference between a scenario and a use case?
A scenario is a concrete description of a single feature illustrating a specific user's interaction with the system, while a use case is a generalization of a set of scenarios which captures all possible user interactions for that feature.