Reference no: EM132992313
ITAP2013 Software Engineering
Activity of Lesson - 5
Review Questions
1. What are the principles of the agile methods? Briefly explain each.
2. What are the problems with Agile methods?
3. Compare plan-based and agile methods
4. Explain the Extreme programming
5. What is a story?Explain with examples
6. What is the refactoring?Explain with examples.
Practice Problems
P.5.1. Explain how the principles underlying agile methods lead to the accelerated development and deployment of software.
P.5.2. When would you recommend against the use of an agile method for developing a software system?
P.5.3. Extreme programming expresses user requirements as stories, with each story written on a card. Discuss the advantages and disadvantages of this approach to requirements description.
P.5.4. Suggest four reasons why the productivity rate of programmers working as a pair might be more than half that of two programmers working individually.
P.5.5. It has been suggested that one of the problems of having a user closely involved with a software development team is that they ‘go native'. That is, they adopt the outlook of the development team and lose sight of the needs of their user colleagues. Suggest three ways how you might avoid this problem and discuss the advantages and disadvantages of each approach.
Activity of Lesson - 6
Review Questions
1. What is a requirement? What is requirements engineering?
2. Briefly explain the different types of requirements?
3. How to distinguish the user requirement definition and the system requirement definition? Explain with examples.
4. What are functional requirements? Give examples.
5. What are non-functional requirements? Give examples (Use the types of non-functional requirements).
6. What is requirements imprecision?
7. Why completeness of the requirements is important in software engineering?
8. List and briefly explain metrics for non-functional requirements.
9. What are the domain requirements? Explain briefly.
10. List the explain he different users of requirements document.
11. List and explain the structure if the requirement specification.
12. What is a structured specification?
13. What is a tabular specification?
14. Explain the spiral view of the requirements engineering process.
15. List and explain the problems of requirements analysis.
16. Explain the requirements elicitation and analysis process.
17. What are the principles of the agile methods? Briefly explain each.
18. What is ethnography?
19. Explain the steps of ethnography and prototyping for requirements analysis.
20. List and explain what you ae checking in requirements.
21. What are the requirements validation techniques?
22. What is requirements evolution?
Practice Problems (Submit only Practice problems)
P.6.1. 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."
P.6.2. Write a set of non-functional requirements for the ticket-issuing system, setting out its expected reliability and response time.
P.6.3. Suggest how an engineer responsible for drawing up a system requirements specification might keep track of the relationships between functional and non-functional requirements.
P.6.4. Using your knowledge of how an ATM is used, develop a set of use cases that could serve as a basis for understanding the requirements for an ATM system.
P.6.5. When emergency changes have to be made to systems, the system software may have to be modified before changes to the requirements have been approved. Suggest a model of a process for making these modifications that will ensure that the requirements document and the system implementation do not become inconsistent.
Activity of Lesson - 7
Review Questions
Q.1 Why project management is important software engineering project?
Q.2. What are the main activities in Software project management? Briefly explain each.
Q.3. What is risk management?
Q.4. Explain the common business risks with software engineering projects.
Q.5. Explain the steps of risk management process.
Q.6. Explain the different risks types with examples.
Q.7. What are the risk indicators? Explain each briefly.
Q.8. What are the people management factors? Briefly explain each.
Q.9. Why motivating people is important in project management?
Q.10. What are the personality types? Explain each briefly.
Q.11. Why teamwork is important in project management?
Q.12. What is group cohesiveness?
Q.13. What is an effective of a team?
Q.14. What is group composition?
Q.15. Why group communication is important in project management?
Practice Problems (Submit only Practice problems)
P.7.1. Explain why the best programmers do not always make the best software managers.
P.7.2. Identify at least six possible risks that could arise in software projects.
P.7.3. Fixed-price contracts, where the contractor bids a fixed price to complete a system development, may be used to move project risk from client to contractor. If anything goes wrong, the contractor has to pay. Suggest how the use of such contracts may increase the likelihood that product risks will arise.
P.7.4. What problems do you think might arise in extreme programming teams where many management decisions are devolved to the team members?
P.7.5. Write a case study (in the style used in textbook) to illustrate the importance of communications in a project team. Assume that some team members work remotely, and it is not possible to get the whole team together at short notice.
Attachment:- Software Engineering.rar