Part One: Agile Software Engineering
- Study the Agile Manifesto until you have it committed to memory: then write it here. Between each line explain in your own words what each line means and what benefits it provides ( especially benefits leading to the accelerated development and deployment of software.
- Describe what test-first development is. Use the following words in your answer: automated, system requirements, implementation, input, and output.
- Describe the benefits of User Stories. Use the following words in your answer: elicitation, requirements, test skeleton, release, back log, sprint, and test-first development.
- Compare and contrast the Scrum approach to project management with
conventional plan-based approaches as discussed in Chapter 23. Your
comparison should be based on the effectiveness of each approach for
planning the allocation of people to projects, estimating the cost of projects,
maintaining team cohesion and managing changes in project team
Part Two: System Modeling
- Briefly define each of the following: Use the following words at least once in your answers: sequence, use-case, activity
- Context Models
- Interaction Models
- Structural Models
- Behavioral Models
- Model-Driven Architecture
- Assume your library project has the following features:
- Search by Dewey number
- Search by subject
- Place books on reserve
- Inter-library loan
Also assume you have defined the following user types
- Research Librarian
- Technical Librarian/System Administrator
Here is what you need to do (relate these as much as possible to your Library Project): (review chapters 5 and 7)
- Develop a sequence diagram showing the interactions involved when a professor places a book on reserve.
- Draw an activity diagram that models the processing involved when a student searches by subject.
- Draw state diagrams of the control software for an inter-library loan system. This system:
- Checks local availability
- Checks avalability elsewhere
- Automates delivery process
Part Three: Object Oriented Design
7.Using the UML graphical notation for object classes, design object classes, identifying attributes and operations. Use your own experience to decide on the attributes and operations that should be associated with these objects.
Hint: Diagram 7.6 from the book is a good place to start.