קורס הנדסת תכנה מכוונת עצמים

Discuss, Learn and be Happy דיון בשאלות

• «
• 1
• »

OOSE Homework-2: Coping with change (=Software requirements) Below is the list of correct/incorrect examples of software process activities that help predict changes and/or make the software being developed more resilient to change.

-

1

+

שאלה #25945

done		1. Recording of requirements rational so that the reason why a requirement is included is known. This helps future change.
done		2. Requirements traceability that shows dependencies between requirements and between the requirements and the design/code of the system.
done		3. Design modeling where the design model documents the structure of the software.
done		4. Code refactoring that improve code quality and so makes it more amenable to change.

• gavel
• mood_bad
• share

הגב

מיין לפי דירוג חדש ישן

2) OOSE Homework-1: Software Engineering What are the important differences between generics software product development and custom software development? Below is the list of correct/incorrect answers.

-

1

+

שאלה #25946

sentiment_very_satisfied		1. The essential difference is that in generic software product development, the specification is owned by the product developer
done		2. For custom product development, the specification is owned and controlled by the customer.
done		3. For users of generic products, this means they have no control over the software specification so cannot control the evolution of the product.
done		5. For users of generic products, it may limit the customer's flexibility to change their own business process.
done		4. For users of generic products, This could have implications for the user's business processes.

• gavel
• mood_bad
• share

הגב

מיין לפי דירוג חדש ישן

3) OOSE Homework-3: Agile Extreme programming expresses user requirements as stories, with each story written on the card. Consider the advantages of this approach to requirements description. Below is the list of correct/incorrect answers.

-

1

+

שאלה #25947

done		1. They represent real situation that commonly arise so the system will support the most common user operations.
done		It is easy for users to understand and critique the stories.2
done		3. They represent increments of functionality - implementing a story delivers some value to the user.
		They focus on functional requirements rather than non-functional requirements.4

• gavel
• mood_bad
• share

הגב

מיין לפי דירוג חדש ישן

OOSE Homework-4: Software Requirements Engineering Discover ambiguities or omissions in the following statement of requirements for part of a ticket-issuing system: An automated ticket-issuing system sells rail tickets. Users select their destination and input a credit card and a personal identification number. The rail ticket is issued and their credit card account charged. When the user presses the start button, a menu display of potential destinations is activated, along with a message to the user to select a destination. Once a destination has been selected, users are requested to input their credit card. Its validity is checked and the user is then requested to input a personal identifier. When the credit transaction has been validated, the ticket is issued. Ambiguities and omissions include:

-

1

+

שאלה #25948

		1. How should the system respond when a user presses the start button?
done		2. What happens if a user tries to buy several tickets for the same destination together?
		3. At what step are users requested to input a personal identifier?
done		4. Can users cancel a request if a mistake has been made?
done		5. How should the system respond if an invalid card is input?

• gavel
• mood_bad
• share

הגב

מיין לפי דירוג חדש ישן

5) OOSE Homework-5: Non-Functional Software Requirements Possible non-functional response time and reliability requirements may include:

-

1

+

שאלה #25949

done		1. After the customer presses a button on the machine, the display should be updated within 0.5 seconds.
done		2. The ticket issuing time after credit card validation has been received should not exceed 10 seconds.
mood		3. When validating credit cards, the display should provide a status message for customers indicating that activity is taking place.
		4. The maximum acceptable failure rare for ticket issue requests is 1:10000

• gavel
• mood_bad
• share

הגב

מיין לפי דירוג חדש ישן

6) OOSE Homework-6: System Modeling If you were developing a new software system you might use a model of a system that already exists. Possible reasons for using an existing system model may include:

-

1

+

שאלה #25950

done		1. To understand the architecture and operation of the existing system.
done		2. To act as the focus of discussion about possible changes to that system.
		3. To review in detail the implementation of all parts of the existing system.
done		4. To identify possible re-use of the existing system’s components.

• gavel
• mood_bad
• share

הגב

מיין לפי דירוג חדש ישן

• «
• 1
• »